Everything posted by Legolash2o
- McRip Updates
-
Component problem Remover to remove update
I'm assuming your saying that you've used component removal and your image has some how gotten bigger. No problem, open WIM Manager and press 'Rebuild Image'.
- McRip Updates
-
Component problem Remover to remove update
Sorry, i can quite figure of what your wanting help with?
- [Solved + Merged] Silent Installer Issues
-
WintoolKit process order?
foreach image { -Mount Image- 1. Updates 2. Remove Components 3. Copy 'Files' 4. Drivers 5. Theme Packs 6. Gadgets 7. Wallpapers -Load registry- 8. Services 9. Silent Installers 10. Addons 11. Tweaks -Unload registry then image- } boot wim stuff if required... I don't touch config.exe
- McRip Updates
-
.NET 3.5 Offline Install
This feature will be in v24 of Win Toolkit, that means .NET Framework will be pre-installed
- McRip Updates
-
.NET 3.5 Offline Install
Nope, it's not part of Windows 8 just .Net 4.0 or 4.5 (one of those). You have to manually install 2.5, 3.0 and 3.5 with the command above.
-
[Solved] Corrupted install.wim
The session name box will not appear if you 'imported' a session you used previously, but it will appear if you make changes to it. Releasing v23 now.
-
.NET 3.5 Offline Install
I'm thinking of adding a simple button in Win Toolkit which does this for the user before Windows installation so that it's pre-installed, what do you guys think?
-
[Solved] Corrupted install.wim
Any news? If confirmed working then i will release v23 with a few other bug fixes?
-
[Solved] LANG.INI problem in boot.wim
Glad it's now working. If you're wondering what i changed i will explain below. BEFORE -------------------------- Win Toolkit would check the wim information to determine if there was image #2 ([1].xml) but sometimes it could not get the information or at least get it correctly, so then it would mount #1 even if #2 existed. AFTER ------------------------- It no longer tries to get the information before hand and just attempts to mount #2 regardless if that information is there or not, only if that fails it will try and mount #1.
-
[Notice] Requests
Please make a new topic about the bug. @Everyone. Just going through my inbox and noticed quite a lot of people message me about problems, can i please remind you to always post bugs and requests in the forum as other people may have information about the specific problem and also so that my PM box does not get cluttered. Thanks.
-
[Solved] LANG.INI problem in boot.wim
Just an update: I've fixed the bug which make language packs appear red instead of green
- "Setup cannot continue due to a corrupted installation file."
-
[Solved] LANG.INI problem in boot.wim
You can only integrate Language Packs into Ultimate and Enterprise editions. If it works then don't worry about it. So did it mount the 2nd boot image instead of the 1st?
-
[Solved] LANG.INI problem in boot.wim
Thanks, looking forward for the results
- "Setup cannot continue due to a corrupted installation file."
-
[Solved] LANG.INI problem in boot.wim
I made some changes with v21, so please test that first Thanks for looking at the files, i'll have a look now but please try the latest version.
-
[Solved] Corrupted install.wim
I managed to replicate the issue, try the test version below. It will still show as 'corrupt' on first use as the issue was with the unmount code so please test unmounting images. http://www.mediafire.com/download.php?ngtqt44rr8zjlwt I only seem to have this issue on Windows 8 lol.
-
[Solved] Corrupted install.wim
After a bit of testing, even having the folder 'expanded' but not viewing it causes the problem.
-
[Solved] LANG.INI problem in boot.wim
I need to things if you don't mind. 1) You're last_session.ini for when you tried to integrate the LP 2) Open your boot.wim with 7zip and attach the [1].xml 3) Have you tried v21 or v22? Thanks.
-
Shutdown, reboot
I agree, i won't be recommending this to anyone. However if it did install Windows 8, i would also install it with Classic Shell 3.5 (mentioned in another post). Another problem is that when you install applications, Metro gets very very messy and full quickly!