JFX

The copying done in beta2 will not cause any problems. But it actually should solve the problem, at least it does here with unchanged English and German ONEPIECE update packs.

Yes, the 6 files (you forget sqmapi.dll) seams to be the only problem. Beta 2 is online making copies of these files after copying them. Also I removed EFI boot files creation if no EFI system partition is selected as boot drive. If no further issues, this one will be final.

OnePiece is absolutely correct here, it's a WInNTSetup issue. I only parse dosnet.inf to create the boot files, but not txtsetup.sif to create $WIN_NT$.~LS folder. Instead the complete folder is copied. While this is of course not the right solution, it much faster. But It only works flawless as long no files are renamed or new created during $WIN_NT$.~LS population. And so it always was with official and unchanged sources. Well, I won't change that anymore, but adding a small check for these 6 files shouldn't be a problem.

If I remember right, the problem with these double entries could be fixed by adding these files in both states (compressed and uncompressed). so you would have 2 files in i386 or AMD64 folder \i386\ie4uinit.mui \i386\ie4uinit.mu_ ie4uinit.mu_ could be a simple copy of ie4uinit.mui and doesn't have to be compressed ie4uinit.mui needs to be decompressed (using expand.exe)

Hmm, I said a bit more complicated not that it's all too much work. And since XP did not get updates any more, you will only have to create it a single time.

Well, main advantage is that the setup time, is reduced. The disadvantage is that is a bit more complicated to create a hardware independent image of XP than Vista and later. The HAL has to be set to oldest require standard. Some drivers like intel processor driver needs to be deactivated else AMD machines could blue screen. All mouse and Keyboard drivers needs to be set to run. Maybe you find some good info, search for "universal XP image ghost"

New Beta version 3.4 Beta 1 So for the end of Windows XP, WinNTSetup now finally supports syspreped WIM images for NT5 systems. Just select them using right - click and setup as usual. one requirement for XP wims: ntldr and ntdetect.com needs to be in the root of an image

Tranngocyd, I'm not really sure I understand you. This version is not experimental, it just have a new and still not completed feature. Only reason for using it would be the new command line switch. Everyone else should wait for the next final version, which is coming soon.

Hi Joseph, There shouldn't be such a problem with The EFI loader on MBR disks. But actually very EFI seems to following it's own will. I don't want to add check boxes for everything, so for now I added just a new switch run it like this WinNTSetup_x86.exe NT6 -nombrefi and it will not create EFI on MBR disks https://onedrive.live.com/?cid=0053f5d45a736673&id=53F5D45A736673%21219&action=Share

Yes, sadly that's normal or "windows 8 normal". Makes sense, if you removed app packages or have them updated already. There's no need to update them at end of setup.

Hmm, only if the pc is online, you said. Don't tell me you mean the app updates on end of setup? If so you need to disable the update options:

Hope I got them all tweaks.zip

Hmm, wasn't the devcon sourcecode not available somewhere? So compiling it with another name should be enough to have a redistributable one. Also, I could properly add devcon download to GWT Done! Run GetWaikTools -devcon

Yes, it's as simple as it looks on the picture. Bootice will subtract 100MB for the EFI and 32MB for MSE partition.

Yeah, next version will accept the new names. Thanks reminding about the name changes. WinNTSetup v3.3 - fixed sfc disable patch did not delete *.cat in dllcache folder - removed dll dependencies: imagehlp, netapi32, psapi - removed all deprecated win32 API's - fixed xp user creation, when setup an x64 OS from WinNTSetup_x86.exe - accepts bootice???.exe names in Tools folder and appdir - fixed swm files where detected by extention instead of attributes - fixed updating bootsector could use wrong tool

Bootsect.dat is not used anymore, it was a useless trouble maker. Setupldr is now renamed to ntldr, the text mode phase cleans this up. EDIT: Version 3.2.2 uploaded! this just a small bugfix version, the last subst fix could effect iso/vhd mounting

My, my it's just gone from the zip file, not killed or made it impossible to use it anymore. Users can still download and put it in the tools folders themselves. But it saves me same minutes uploading a new version. Why don't you have reported that bootsect.exe is not working for you, before? There is always a WinNTSetup.log file in the new Windows folder that contains bootsect's stdout. If you discover this problem again please upload the log.

Well even bootice can do this:

A good partition program should help creating one. But you can also use classic diskpart tool. http://technet.microsoft.com/en-us/library/hh825686.aspx

xcv150, it's no real difference to normal BIOS. Just make sure you create a EFI system partition and select this one as boot drive.

Okay done, you now can run it like this: "WinNTSetup_x86.exe download". It will silently download the adk tools and close with exitcode 0 if successful. WinNTSetup v3.2.1 - reduced ADK download size by 600KB - new download command line option to download ADK silently - added links to about gui - removed bootice from tools

Ah, that evil first page, I always forgot there something. I'll add a download command line, with the next version

You can't change the Windows folder path since Vista. Doing it manually will only break your windows installation.

@jaclaz With an x86 recovery environment you can't do some things on an x64 windows - access all hardware due to lack of drivers available - servicing with dism - sfc checking/repairing - using offline system restore - remove a troublesome hotfix - reinstall windows without 3rd party apps

Ok, so this took a while but should adress all problems. WinNTSetup v3.2 - fixed problem with "subst" drives - fixed drive label still not displayed on some systems - new support for esd files - command line accept relative pathes - on windows 8.1 system32 wimgapi.dll will be preferred - admin check now token based - updated offreg library to latest version