JFX

Well, there is no real way to detect a "system" partition. Until Vista properly nobody has hidden his active partition, so i don't think the boot partition should be hidden by winntsetup in general. Currently it checks if the drive label is called ""system reserved" and if the partition is smaller than 1 GB. If both true it will be hidden for the new installation. Personally, I would suggest the change the partition id with diskparts setid command. This way, any windows will never assign a drive letter to it @lama & komital I don't plan to add anymore tweaks to it. It's a simple setup tool not a tuning and tweaking suite It should be possible to get most of these things done with the "Runafter" switch.

Hmm, that really strange, but remember I also had a funny board that act often different. It often switched between USB 1.0 and 1.1 Speed, even with same USB disk. On a cold boot, it never was able to boot from USB. Guess most problems are related to stupid BIOS, Lately had one machine that could not boot an XP boot sector on a 2K aligned partition. After changing some BIOS settings it worked.

@Tihiy How about adding 7 shell32.dll.mui to explorer7 folder and load pin/unpin text from it? 2 things I've noticed while using explorer7 : 1 - The MRU programs and the start menu pinned list missing the pin/unpin text in context menu 2 - The "nice" closing of explorer doesn't work, the process remains in memory

Update: Version 2.3.0.0 - full Windows 8 support - rewritten command line parsing - rewritten WIM file operations (up to 10% faster NT6.x install) - System Reserved partition now hidden in new installation - added system menu tools - automatically creates a pagefile if not enough RAM available - new file patching engine, 5 times faster - UEFI support Thanks to Atari800XL for reporting so many bugs

@johnhc If every PC you want to boot this WinPE has 2GB RAM, you can set WinPECacheThreshold to the maximum of 512MB. Sometimes driverinstall copies the uncompressed drivers twice, but 512MB freespace on systemdrive should be enough to install the driver. if still not enough, I've reduced the driver package to ~ 10MB ATI_12.8_x64.7z @submix8c driver integration will not add the complete package, dism parses the .inf files and copies only the result.

You really need to add this registry and files to an offline winpe, so everything is ready at boot time. The out of space error could mean you don't have enough space on systemdrive to copy the very big ati drivers. Try to increase WinPECacheThreshold.

I guess the kernel creates it, if winpe is set in boot options. Hmm, there was some registry settings to disable it, but can't remember what. Maybe disable the Plug n play service. But properly MS has removed that option, as options don't fit into the windows 8 concept. Let's assume the the SystemSetupInProgress set to "0" is causing the hardware seach. - maybe you could just remove trouble some infs from the \Windows\Inf folder (disk.inf, volume.inf, volsnap.inf) - or setting a SystemSetupInProgrest value to 1 and change the UNICODE strings SystemSetupInProgress to SystemSetupInProgrest inside some modules that start the hardware detection (umpnpmgr.dll, services.exe)

In your full windows you have "SystmSetupInProgress" set to 0 during logon, to be able to login as admin directly? But the winpe option in BCD store is set to true and creates the MININT key, so you be able to boot from read-only wim files? If both true than I had similar situation few years ago. Only solution to avoid "drive disappearance" was disable automatic driver search. Maybe if helps to play with SystmSetupInProgress and MININT key.

Good idea If there are different architectures inside a wim file, they now marked in the dropdown box.

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.