-
Posts
5,661 -
Joined
-
Last visited
-
Days Won
243
Content Type
Profiles
Forums
Events
Everything posted by Legolash2o
-
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.
-
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?
-
Any news? If confirmed working then i will release v23 with a few other bug fixes?
-
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.
-
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.
-
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."
Legolash2o replied to testplayer's topic in Win Toolkit
I think DISM does the checking. Either way it's hard to tell which update would cause the problem -
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?
-
Thanks, looking forward for the results
-
"Setup cannot continue due to a corrupted installation file."
Legolash2o replied to testplayer's topic in Win Toolkit
That error sounds like it is related to ISO creation, try just integrating updates, if that boots, then remove packages/features -
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.
-
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.
-
After a bit of testing, even having the folder 'expanded' but not viewing it causes the problem.
-
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.
-
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!
-
Your server is configured a bit differently than SoLoR's so it requires some effort to get it to work with WT
-
No idea, just change it to .txt
-
Thank god it's now working! I'll just wait for Thiersee to reply to his topic and have a look at the issue before i release.
-
Even if you have that folder open in explorer it causes the problem. Either way i need to know what you did? i.e. Just mount the image in WIM Manager? Use it with All-In-One Integrator? Is there a last session.ini or error log?
-
[Solved] Apply Unattended via WIM Manager question
Legolash2o replied to NiceGuy's topic in Win Toolkit
Glad you manage to figure this out, sorry for the late reply. -
If more people confirm this working (test 2) then i will release v22 Thanks
-
It will only show as corrupt if you had a file or folder within the mount path open whilst Win Toolkit was unmounting. It also happens if you have other programs such as RT7Lite using the same mount folder as well.
-
So it worked? :dancing:
-
Who knows, blame DISM.