JFX

Okay fixed now, no version changed this time.

Yes, it's time to add "8" and "2012" to the tab, as fully supported OS. Oh, could reproduce it. Must have happed while I changed the WIM stuff. Combo box starts with 0, but wim index start with 1. Seems I put that vice versa again Booth should be fixed now in RC1.

Hi Sampy82, Error: 2 usually means that an error occurred while read or write from disk. Maybe there is a problem with your harddisk or an antivirus software blocking the apply process

Can't say, as I not sure how MSSTMake works exactly, WinNTSetup only merges the information into the windows source. How to decide what is a problematic driver? Just guessing that a driver rejected by MSSTMake can be integrated with force (as IntegrateDrv does) is OK, could cause other problems. Well, if someone is volunteer to create an improved and small app, I would like to integrated it, but personally have no free time at all.

MSSTMake can integrate Massstorage drivers, for physically existing devices and so far is the best app to do this. It just don't recognize drivers like WinVBlock. IntegrateDrv surely is interesting, but has a few week points: - it's only thought to integrate 1 single driver, no recrusiv adding of drivers - no silent automation, it ask my to choose 1 of 23 "drivers" for my Intel Storage - accepts only one target, but $WIN_NT$.~BT and $WIN_NT$.~LS can be on different partitions

Seems the driver integration don't work for a virtual driver like winvblock, it will be skipped and Txtsetup will get a problem. But if you boot this img with Grub4Dos, why not use a virtual F6 floppy with winvblock files?

Should be possible, if WinVBlock has a correct inf file accepted by the msstmake tool. Adding VHD options for Windows older than 7, would be way to much work. Properly can't even be done fully automated. Sorry I don't have any plans to add support for alternative VHD drivers as WinVBlock, Firadisk or Vboot. @Mr001 Hmm, that's strange Have you tried to disable AHCI in the bios? If this also not works, i'm out of ideas

Updated for Windows 8 RTM ADK !

Thanks for the infos. It really seams to be a sata driver issue. To integrate a driver just check the "Add Driver" checkbox and select the folder in the showing up dialog. But if you don't have / know the exact driver needed you can use Driverpacks Base to integrate the drivers. 1. Download DPs_BASE_1006.exe and DP_MassStorage_wnt5_x86-32_1206.7z http://driverpacks.net/downloads 2. Run DPs_BASE_1006.exe and select C:\DPsBase for extracting 3. Copy DP_MassStorage_wnt5_x86-32_1206.7z to C:\DPsBase\DriverPacks 4. Run Winntsetup and select "Run DriverPacks BASE (x86 only)" checkbox 5. Push the setup button and wait for winntsetup to copy the files 6. You will be asked to select DPs_BASE.exe, browse to C:\DPsBase and select that file. 7. DriverPacks BASE will launch, select Settings --> DriverPacks in the treeview 8. Select the Driverpacks Massstorage checkbox and hit Slipstream button 9. The driver integration will take a few minutes, wait and hit okay in the success message that show up in the end

ha ha, yeah this happens quite often lately Good to hear that the RTM works fine. Windows 8 should be fully supported now.

Update: Version 2.3 Beta 4 - Windows 8 Professional edition recognized for nativeVHDBoot - file patching 5x faster - UxTheme generic patcher for Windows 8 - System Reserved partition now hidden in new installation - *caution "hidden feature" language.ini extended

Hmm, a bit more information would help Which windows version you trying to install? What number was displayed on the BSoD? At which state of the installation the BSoD occured? I can only assume the dell pc is running in AHCI mode and your windows CD doesn't have the required SATA driver. You could try to disable AHCI inside the BIOS or you will need to integrate the driver. WinNTSetup can integrate SATA driver for all windows version, if you select a folder containing the right driver in unpacked form.

You right this is only for GPT and don't work with MBR. So i guess while the Windows Setup create the system reserved it also set a new registry setting for the new Windows installation, that prevents a drive letter.

change your line: to:

Thanks for the update Works great

Try to delete the HKLM\SYSTEM\CurrentControlSet\Control\MiniNT registry key before starting Paragon software. Maybe they disabled some features in WinPE mode. But don't forget to create the MiniNT key after running paragon as it's required for shutdown/restart.

As far as i remember yes, just run it after boot. It's a silent installer and should create a log file next to it. But I have not used it for a long time cause it makes trouble with the shadowprotect driver I use.

It's a virtual driver, not connected to real hardware, so dism will only add it to the driver store. There should be an uim exe file with the installation files that can install that driver.

Yes, if a drive already has a windows installation inside, it's better to format it.

1. Yes the drive letter of your xp setup drive. A real CD/DVD or a mounted iso image 2. A Primary partition (dark blue) on "Disk 0" with "(System)" in Status register 3. Can be any partition, even the one you selected under 2.

Great work If Pinning will work, this will be a perfect shell replacement. Enjoying a Metro free Win8 now.

Hi testplayer, sorry I can not make an update until weekend, but you can enable/disable that check with right-click on "VHD >>>" button.

The v2.3 versions have disk management (or if not available diskpart) link in system menu (ALT + SPACE) Can't really remember how to create fully hardware independent Windows XP sysprep images. But yes, this is indeed a great and fast way to install WinXP. Currently WinNTSetup is more or less a frozen project for the next months, but maybe I add full support for this way of installation.

Hi Escorpiom, You could do this indeed with the runafter parameter. But no need, I have added a check that will automatically write the right Bootsector. be careful installing that way, winntsetup don't understand that currently, so any GUI option will not work WinNTSetup2.3 beta3

Only 1 real advantage: the x64 version will always be a bit faster. my average time to apply an install.wim: x86 : 40 seconds x64 : 37 seconds So with SSD's or RAMDisk's one can noticed a slightly faster install, but with normal hard disk there won't be.