JFX

Yep, but it has to check all winnt.sif files, - one created by driverpacks before winntsetup -.one create by the MSSTMake integration - one create by the driverpacks integration - the one in the root of the XP source - and the one supplied by user

Sure it will be done in next version, but there is much more I have to change here. Next version have to wait a bit longer (holidays are over ....)

Well that I'm not the one how wrote it, should be clear by now. Nonetheless I'm the one behind the development for over a year now. Technically v2 does only work in your case by mistake, it's not designed to accept 2 different driver integrations on one source,

Okay, that great these missing entries in OemPnpDriversPath could explain the BSOD after last reboot. We will know if you fix the line in winnt.sif after running v3, with the correct data one form v2. BTW: In v2 doe you have selected an winnt.sif file?

Depending on the used Driverpacks method the actual install should be executed through: \$WIN_NT$.~BT\winnt.sif [GUIRunOnce] command9="%SystemDrive%\DPsFnshr.exe" Well there have to be any difference in the \$WIN_NT$.~BT\winnt.sif files

@adacom This is an Autoit3 script, you have to install Autoit3 and then compile this script or just run the script.

Seams I just forgot to add the drive letter to \$OEM$ Rev 1 uploaded.

So we talking the whole time about different thing. 1. I thought it was about the msstmake way of driver integration Then I thought it was about driver pack integration via driverpackbase. Now it seems it's all about the $OEM$ folder on your CD/ISO that's not being copied in v3. Well the good thing is that it could fixed some bugs i had not found else. Anyway next version will copy this folder, too.

Both version of Winntsetup setting the method 2 in DPbase ini file. And it's DPBase that creates the \$WIN_NT$.~LS\$OEM$\$1\D folder. No version should copy this folder in the root, it will be copied later by the real setup.

This folder is created if you choose integration Method 1 in DPBase. Both versions actually setting Method 2, in DP_Base. I get pretty much the same output here ...

Added attachment on first post.

Could reproduce it in XP VM, it didn't move the folder \$WIN_NT$.~LS\OEM to \OEM. Also the winnt.sif update doesn't happens cause I mess up the file attributes. WinNTSetup v3 (WIP 04/09/2013) - fixed drvbase option not working in some cases - fixed cmdline SaveDriveLetters, uxtheme

Well, i tried to make NT5 setup more correct, so it would have worked with some of these insane nlite mods. But in the end it just resulted in more questions and problems, so I revert it mostly back. No sure actually why i thought about decompression boot files Will fix the command line! At least this means that boot files and driver integration was successful But in TXT phase the driver isn't installed for some reason. Do you see any difference in DRV folder or in $WIN_NT$.~BT\winnt.sif between v2 and the v3WIP?

GWT version 1.5.1 released! - added windows 8.1 RTM files

WinNTSetup v3 (WIP 03/09/2013) - changed XP boot folder creation back to v2 version - fixed BCDBoot XP compatibility - fixed buffer overflow in Product key decoding http://sdrv.ms/13YWwCY

I didn't mean support for installing WinXP. The problem is running (winnt)setup from inside XP to install latest windows version. I can fix the BCDBoot.exe incompatibility like I did in v2. However driver integration is another story. You can't integrate driver to Win 8.1, if you run from Vista or earlier.

Hi amitri, don't tell me you still use WinXP!? XP support will be re-added, but you should upgrade to Windows 7, if you want full functionality.

Don't worry I enjoy my weekend. Next version will have to wait a few days. For RunAfter I'm wonder too, should have been hidden (maybe forgot it while debugging).

I changed the driver integration and bootfolder stuff a bit and it worked with my notebook. I'll change it back to the old version. (1) -drivers:"L:" and -drivers:L: are the same, the quotes get's stripped in the very beginnig. The problem I remember was L:\ is a valid windows path, but dism wants L: (which is actully wrong) (2) yellow exclamation replaces the red cross for MBR and PBR now. like a traffic light: - green means drive - yellow is just a warning but means drive - red means stop

BootToDesktop might have been set somewhere else but not by WinNTSetup. 1) added the return hotkey for setup button 2) yes new bug and fixed again WIP 08/31/2013 Rev 1 uploaded!

Ok next version is ready. WIP 08/31/2013 - change winhttp linking to dynamic - removed winmm.dll dependency - fixed F1 and Escape hotkey not working - fixed cmdline source not updating description text - fixed cmdline reboot, addotheros, nobootsect doesn't click respected checkbox - fixed unattend file not copy if \Windows\Panther folder is missing - fixed BootToDesktop was not integrated http://sdrv.ms/13YWwCY

Yes, your right some command line options are not take in the check boxes and therefor maybe don't work. Your the number one bug hunter again

Seems I forgot F1 hot key for the Help page. Your command line example actually works, it just forgets to update the description label.

Hi Atari800XL, yes this one is complete rewritten in a different language. So far not to much changes since v2. - VHDX is fully supported (but no instant creation of fixed ones, yet) - language file is now a resource dll with much better loading speed as a simple text file. - command line now have options and switches, well not much changed but more parameters are planed - Windows Product key finder and password reset are integrated

Here you have the addresses for bootmgr.exe version 6.3.9600.16384 (RTM) 0000065E: 0F 900000065F: 88 9000000660: AE 9000000661: 02 9000000662: 00 9000000663: 00 900002B1C1: 74 EB0002B1EB: 75 EBAt address 8AF90 you have the \Boot\BCD string that you can change. @Mods Maybe this topic would be better places in WinPE or Multi boot sub forum.