316 replies to this topic

[ilko]

Have you looked deeper for the exact cause? Anything interesting in setup logs?

[wimb]

Have you looked deeper for the exact cause? Anything interesting in setup logs?

Yes, I have looked deeper, but it was in the early days, when being successful already with USB-stick and NOT yet with USB-Harddisk. In july 2008 I concluded that without rdummy.sys the harddisk number of USB-harddisk was not known and this caused that the entry of SetupSourceDevice in TXTSETUP.SIF could not be used to identify the Source location. I have to look at it again to be sure.

[wimb]

hi ilko,

Did some tests.

The setuplog.txt and setupact.log reveal that without rdummy.sys the USB-Harddisk is not appearing in the log's with Volume: DriveLetter and harddisk number e.g. in setupact.log we have:

without rdummy.sys

Device Path: \\?\usbstor#disk&ven_st332082&prod_0a&rev_0000#def10ce422df&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}



1. ST332082 0A USB Device

instead of with rdummy.sys

Volume: I:\ 



Device Path: \\?\storage#removablemedia#7&35b17784&0&rm#{53f5630a-b6bf-11d0-94f2-00a0c91efb8b}



PhysicalDeviceObjectName: \Device\Harddisk2\DP(1)0-0+d

   HardwareId: STORAGE\Volume

2. ST332082 0A USB Device

Without rdummy.sys the device is known but not by number.
That means that TXTSETUP.SIF SetupSourceDevice entry is NOT working to find the XP Source files in GUI XP Setup mode.

[ilko]

This is interesting find, thanks.
When you get a chance have a look at differences in \Windows\System32\$WINNT$.INF as well. There are entries about source path.
When you install not using rdummy, and you enter command prompt during GUI, does the USB hard disk have drive letter at all?

[wimb]

$winnt$.inf without rdummy.sys

sourcepath = "\device\harddisk2\partition1\XP3_812M\"

dospath=GLOBALROOT\Device\HarddiskVolume7\XP3_812M\

$winnt$.inf with rdummy.sys

sourcepath=\device\harddisk2\partition1\XP3_812M\

dospath=I:\XP3_812M\

How do I get command prompt during GUI Setup ?
Have seen it somewhere, but forgot it.

[cdob]

How do I get command prompt during GUI Setup ?

Press SHIFT+F10.
http://support.micro....com/kb/242380/

Be aware $winnt$.inf is changed at first reboot.
sourcepath is changed slightly:

Line
sourcepath = "\device\harddisk2\partition1\XP3_812M\"
may get
sourcepath=\device\harddisk2\partition1\XP3_812M\


Added:
Fixed letter U: may fail because of rdummy.sys at migrate.inf.

[wimb]

Thanks to ddlistw.cmd of jaclaz, I can give the complete DriveList for the case of GUI XP Setup asms Error STOP and then using Shift F10 (thanks to cdob) where XP Source is on USB-Harddisk - harddisk2 - and
without using rdummy.sys

Drives by drive letter:

 ,  \Volume \

c: 1,1 FIX \Volume{d7892256-fc4f-11dd-b883-806d6172696f} \HarddiskVolume4

d: 0,1 FIX \Volume{d7892253-fc4f-11dd-b883-806d6172696f} \HarddiskVolume1

f: 1,2 FIX \Volume{d7892257-fc4f-11dd-b883-806d6172696f} \HarddiskVolume5

g: 1,3 FIX \Volume{d7892258-fc4f-11dd-b883-806d6172696f} \HarddiskVolume6

h: 0,2 FIX \Volume{d7892254-fc4f-11dd-b883-806d6172696f} \HarddiskVolume2

i: 0,3 FIX \Volume{d7892255-fc4f-11dd-b883-806d6172696f} \HarddiskVolume3

l: 3,1 REM \Volume{d789224f-fc4f-11dd-b883-806d6172696f} \Harddisk3\DP(1)0-0+10

m: 4,1 REM \Volume{d7892250-fc4f-11dd-b883-806d6172696f} \Harddisk4\DP(1)0-0+11

n: 5,1 REM \Volume{d7892251-fc4f-11dd-b883-806d6172696f} \Harddisk5\DP(1)0-0+12

o: 6,1 REM \Volume{d7892252-fc4f-11dd-b883-806d6172696f} \Harddisk6\DP(1)0-0+13

p: x,x CDR \Volume{d789224d-fc4f-11dd-b883-806d6172696f} \CdRom0

q: x,x CDR \Volume{d789224e-fc4f-11dd-b883-806d6172696f} \CdRom1

Druk op een toets om door te gaan. . . 



Drives by connection:

 ,  \Volume \

d: 0,1 FIX \Volume{d7892253-fc4f-11dd-b883-806d6172696f} \HarddiskVolume1

h: 0,2 FIX \Volume{d7892254-fc4f-11dd-b883-806d6172696f} \HarddiskVolume2

i: 0,3 FIX \Volume{d7892255-fc4f-11dd-b883-806d6172696f} \HarddiskVolume3

c: 1,1 FIX \Volume{d7892256-fc4f-11dd-b883-806d6172696f} \HarddiskVolume4

f: 1,2 FIX \Volume{d7892257-fc4f-11dd-b883-806d6172696f} \HarddiskVolume5

g: 1,3 FIX \Volume{d7892258-fc4f-11dd-b883-806d6172696f} \HarddiskVolume6

l: 3,1 REM \Volume{d789224f-fc4f-11dd-b883-806d6172696f} \Harddisk3\DP(1)0-0+10

m: 4,1 REM \Volume{d7892250-fc4f-11dd-b883-806d6172696f} \Harddisk4\DP(1)0-0+11

n: 5,1 REM \Volume{d7892251-fc4f-11dd-b883-806d6172696f} \Harddisk5\DP(1)0-0+12

o: 6,1 REM \Volume{d7892252-fc4f-11dd-b883-806d6172696f} \Harddisk6\DP(1)0-0+13

p: x,x CDR \Volume{d789224d-fc4f-11dd-b883-806d6172696f} \CdRom0

q: x,x CDR \Volume{d789224e-fc4f-11dd-b883-806d6172696f} \CdRom1

Druk op een toets om door te gaan. . .

harddisk2 was at TXT-mode XP Setup visible as Drives E: (J: K:) and is as you can see invisible at GUI XP setup.
Each harddisk has 3 partitions and I am installing on harddisk 1 partition 1 (the C: bootdrive)
(Vista is at Harddisk 0 and has in BIOS lower boot priority)
Harddisk 3,4,5 and 6 correspond to my internal Cardreader.

BTW migrate.inf is not used in the case of USB-harddisk and is only made when selected for case of USB-stick.

[wimb]

When rdummy.sys is used then ddlistw.cmd reveals in GUI XP Setup the USB-harddisk as harddisk2 and as Removable Drive I:\
This is the situation which we can use in TXTSETUP.SIF to find the XP Setup Source files with

[SetupData]

SetupSourcePath ="\XP3_812M\"

SetupSourceDevice=\device\harddisk2\partition1

with rdummy.sys

Drives by drive letter:

 ,  \Volume \

c: 1,1 FIX \Volume{adbd1357-fcc2-11dd-9cbe-806d6172696f} \HarddiskVolume4

d: 0,1 FIX \Volume{adbd1354-fcc2-11dd-9cbe-806d6172696f} \HarddiskVolume1

e: 1,2 FIX \Volume{adbd1358-fcc2-11dd-9cbe-806d6172696f} \HarddiskVolume5

f: 1,3 FIX \Volume{adbd1359-fcc2-11dd-9cbe-806d6172696f} \HarddiskVolume6

g: 0,2 FIX \Volume{adbd1355-fcc2-11dd-9cbe-806d6172696f} \HarddiskVolume2

h: 0,3 FIX \Volume{adbd1356-fcc2-11dd-9cbe-806d6172696f} \HarddiskVolume3

i: 2,1 REM \Volume{adbd134f-fcc2-11dd-9cbe-806d6172696f} \Harddisk2\DP(1)0-0+d

j: 3,1 REM \Volume{adbd1350-fcc2-11dd-9cbe-806d6172696f} \Harddisk3\DP(1)0-0+e

k: 4,1 REM \Volume{adbd1351-fcc2-11dd-9cbe-806d6172696f} \Harddisk4\DP(1)0-0+f

l: 5,1 REM \Volume{adbd1352-fcc2-11dd-9cbe-806d6172696f} \Harddisk5\DP(1)0-0+10

m: 6,1 REM \Volume{adbd1353-fcc2-11dd-9cbe-806d6172696f} \Harddisk6\DP(1)0-0+11

n: x,x CDR \Volume{adbd134d-fcc2-11dd-9cbe-806d6172696f} \CdRom0

o: x,x CDR \Volume{adbd134e-fcc2-11dd-9cbe-806d6172696f} \CdRom1

Druk op een toets om door te gaan. . . 



Drives by connection:

 ,  \Volume \

d: 0,1 FIX \Volume{adbd1354-fcc2-11dd-9cbe-806d6172696f} \HarddiskVolume1

g: 0,2 FIX \Volume{adbd1355-fcc2-11dd-9cbe-806d6172696f} \HarddiskVolume2

h: 0,3 FIX \Volume{adbd1356-fcc2-11dd-9cbe-806d6172696f} \HarddiskVolume3

c: 1,1 FIX \Volume{adbd1357-fcc2-11dd-9cbe-806d6172696f} \HarddiskVolume4

e: 1,2 FIX \Volume{adbd1358-fcc2-11dd-9cbe-806d6172696f} \HarddiskVolume5

f: 1,3 FIX \Volume{adbd1359-fcc2-11dd-9cbe-806d6172696f} \HarddiskVolume6

i: 2,1 REM \Volume{adbd134f-fcc2-11dd-9cbe-806d6172696f} \Harddisk2\DP(1)0-0+d

j: 3,1 REM \Volume{adbd1350-fcc2-11dd-9cbe-806d6172696f} \Harddisk3\DP(1)0-0+e

k: 4,1 REM \Volume{adbd1351-fcc2-11dd-9cbe-806d6172696f} \Harddisk4\DP(1)0-0+f

l: 5,1 REM \Volume{adbd1352-fcc2-11dd-9cbe-806d6172696f} \Harddisk5\DP(1)0-0+10

m: 6,1 REM \Volume{adbd1353-fcc2-11dd-9cbe-806d6172696f} \Harddisk6\DP(1)0-0+11

n: x,x CDR \Volume{adbd134d-fcc2-11dd-9cbe-806d6172696f} \CdRom0

o: x,x CDR \Volume{adbd134e-fcc2-11dd-9cbe-806d6172696f} \CdRom1

Druk op een toets om door te gaan. . .

[magic12kenneth]

I don't know what is causing BSOD STOP 6B

Preparing your C-drive for Install of XP using the Batch Program USB_XP_Setup.cmd 4.01 or using the latest GUI Program USB_XP_Setup of U_XP_SET package should NOT make any difference.

In LiveXP environment after Quick Format of your C-drive and After running USB_XP_Setup then you can compare if there are any differences in the XP Setup Bootfolder $WIN_NT$.~BT for both cases.
Therefore e.g. After Using Batch USB_XP_Setup safe the content of C-drive in folder somewhere and compare this folder using Total Commander Synchronize Dirs (see HelpInfo) with the result for GUI USB_XP_Setup.

There should not be any difference and If so, please report the difference to me.
I assume you are using everything the same like XP Source and Computer and that the only difference is the USB_XP_Setup program.

After the Reboot and then running TXT-mode XP Setup there is no influence anymore of USB_XP_Setup version.
Everything is determined by the files which were generated on the Install drive usually C:\

EDIT: May be can you give as Attachment your I386\dosnet.inf file, so that I can see if there is any issue ?

Ok, here is a copy of the dosnet.inf you requested. I should also mention that I use nlite to integrate ryanvm sp3 post hotfixes and other addons and then use DriverPacks to integrate the driverpack.

Attached Files

•  DOSNET.INF   157.47K   613 downloads

[ilko]

There are unexpected quotes:

d1,ntdll.dll,"system32\ntdll.dll"

d1,usetup.exe,"system32\smss.exe"

This brings the unanswered question again:

0x0000006B rings a bell- do you have smss.exe and ntdll.dll in $WIN_NT$.~BT\system32\ ?

[wimb]

There are unexpected quotes:

d1,ntdll.dll,"system32\ntdll.dll"

d1,usetup.exe,"system32\smss.exe"

This brings the unanswered question again:

Yes you are right ilko and it is a nLite related problem.
Also the [Directories] Section has quotes in directory entries.

@magic12kenneth
The files system32\ntdll.dll and system32\smss.exe are missing in C:\$WIN_NT$.~BT folder when using your dosnet.inf

I will try to fix the program for this nLite issue.
For the moment you can remove the quotes in the above given entries in your DOSNET.INF file. That solves the problem.

[magic12kenneth]

Yes you are right ilko and it is a nLite related problem.
Also the [Directories] Section has quotes in directory entries.

@magic12kenneth
The files system32\ntdll.dll and system32\smss.exe are missing in C:\$WIN_NT$.~BT folder when using your dosnet.inf

I will try to fix the program for this nLite issue.
For the moment you can remove the quotes in the above given entries in your DOSNET.INF file. That solves the problem.

Sweet...I'll keep an eye on an updated version for this fix and test it for you.

Ken

[wimb]

=
PROGRAM UPDATE - U_XP_SET Package - Install XP from USB

Changes in Make_USB.exe and USB_XP_Setup

• Fixed : effect of double quotes in dosnet.inf file as made by nLite causing BSOD 0x0000006B - due to files system32\ntdll.dll and system32\smss.exe were missing in C:\$WIN_NT$.~BT XP Setup BootFolder.

Thanks to magic12kenneth for reporting the BSOD 6B Error and thanks to ilko for indicating the cause and solution to the problem.
=

[magic12kenneth]

=
PROGRAM UPDATE - U_XP_SET Package - Install XP from USB

Changes in Make_USB.exe and USB_XP_Setup

• Fixed : effect of double quotes in dosnet.inf file as made by nLite causing BSOD 0x0000006B - due to files system32\ntdll.dll and system32\smss.exe were missing in C:\$WIN_NT$.~BT XP Setup BootFolder.

Thanks to magic12kenneth for reporting the BSOD 6B Error and thanks to ilko for indicating the cause and solution to the problem.
=

Nice... I'll test it tonight and let you know the result.

Also, the cmdhide.exe is trigger as a virus which we know it is not. You might interest in replacing this with cWnd

Ken

[magic12kenneth]

Nice... I'll test it tonight and let you know the result.

Also, the cmdhide.exe is trigger as a virus which we know it is not. You might interest in replacing this with cWnd

Ken

I tested on three computers and it works fine after the fix. Thanks.

Ken

[wimb]

=
PROGRAM UPDATE - U_XP_SET Package - Install XP from USB

Changes in BOOT_IMG.exe - Make_USB.exe and USB_XP_Setup

• Fixed : Improvement for making GRUB4DOS Menu Entries taking possible Hidden Partitions into account.
  
• Changed : WARNING instead of ERROR Message for Missing WINNT32.EXE due to nLite Manual Setup Removal.
  Allows to Continue and make use of Copy Existing XP Setup BootFolder to Target Drive Option instead of Parsing DOSNET.INF
  
• Added : New Program BOOT_ISO.exe for Install of ISO File as GRUB4DOS Boot Option in menu.lst Menu on Harddisk or USB-Drive.
  Enables to Boot with VistaPE or Windows PE 2.1 ISO into RAMDISK via boot.ini Menu and GRUB4DOS grldr with menu.lst Menu.
  Enables to Boot with CD-ISO files from RAM using GRUB4DOS Menu, suitable for UBCD - Acronis - Paragon HD manager or LiveXP_RAM ISO Files

Thanks to jaclaz for Help with GRUB4DOS menu to boot with Windows PE 2.1 ISO file.

Thanks to allanf for making WinBuilder Project to make Windows PE 2.1 ISO having GUI interface
http://www.boot-land...?showtopic=7053
Download WAIK 1.1 Vista SP1 from
http://www.microsoft...;displaylang=en

Booting in 40 sec with pe21.iso loaded by GRUB4DOS from HD into RAMDISK X:
allows then to Launch Vista or Windows 7 Setup.exe from folder on USB-stick.
http://www.boot-land...?...=6800&st=37

Procedure for Install of Vista or Windows 7 from USB-stick

• Download and Extract U_XP_SET package making U_XP_SET folder on your Harddisk
  
• Launch PStart.exe in U_XP_SET folder
  
• Run BOOT_ISO.exe from PStart Menu to Install Windows PE 2.1 ISO
  as GRUB4DOS Boot Option in menu.lst Menu on Harddisk Boot Drive e.g. C:\
  
• Reboot in 40 sec with Windows PE 2.1 ISO loaded by GRUB4DOS from HD into RAMDISK X:
  
• Run Vista Setup from folder on USB-stick by using e.g. Free Commander in PE 2.1 Environment
  
• Select and Format your Install Drive e.g. C:\
  
• Proceed with Install of Vista from USB (Copy + Extract)
  
• Disconnect USB-stick precisely at First Reboot (just at the BIOS Beep when the screen is black).
  Without Removal there is 10 min Extra Install time.
  
• Proceed with Install of Vista - Totally in about 18 min

The present approach is Install of Vista from USB without booting from USB.
So you don't need BIOS USB Boot Support and you don't need to change BIOS Settings.
Moreover, Vista Setup Source can be located in a folder on USB-stick so that it does not interfere with other Setup Sources like folders with Vista x64 or Windows 7 Setup Source.

Instead of Windows PE 2.1 we can also use VistaPE ISO,
but booting with VistaPE will take several minutes.
http://www.boot-land...hp?showforum=51
=

=

[wimb]

=
PROGRAM UPDATE - U_XP_SET Package - Install XP from USB

• Minor Changes : BOOT_IMG.exe - BOOT_ISO.exe and Make_USB.exe
  can be used now also in GUI Windows PE 2 Environment made with WinBuilder Project of allanf
  http://www.boot-land...?showtopic=7053

Summary
After preparing your USB-stick with Make_USB.exe we have two cases,
each of them needs Booting from HD into RAMDISK with a compatible PE Boot Image.

• XP needs Booting with LiveXP - IMG allowing to format Install Drive with NTLDR type BootSector.
  
• Vista and Windows 7 need Booting with Windows PE 2 - ISO allowing to format Install Drive with BOOTMGR type BootSector.

Procedure - Install XP from USB-stick

• Connect USB-stick and Run BOOT_IMG.exe
  
• Install LiveXP IMG in boot.ini / GRUB4DOS Menu on Harddisk
  
• HD Boot LiveXP into Ramdisk - Quick Format and Run USB_XP_Setup.exe
  
• HD Reboot and Select XP Setup from boot.ini Menu
  
• Keep USB-stick Connected Until AFTER Logon XP

Procedure - Install Vista or Windows 7 from USB-stick

• Run BOOT_ISO.exe
  
• Install Windows PE 2 ISO in GRUB4DOS Menu on Harddisk
  
• HD Boot Windows PE 2 into Ramdisk - Start Vista Setup from USB
  
• Precisely on First Reboot - Remove USB-stick

The present approach is Install from USB without booting from USB.
So you don't need BIOS USB Boot Support and you don't need to change BIOS Settings.
Moreover, Unchanged Setup Sources can be used and can be located in a folder on USB-stick so that they do not interfere with eachother.


=

[wimb]

=
PROGRAM UPDATE - U_XP_SET Package - Install XP from USB

• Changed : FORMAT Button was made in USB_XP_Setup.exe
  which allows to Quick Format Selected Target Drive for Install of XP.
  Format of Target Drive can be used in LiveXP or Windows PE 2 Environment AFTER Booting from RAMDISK.
  Booting with Windows PE 2.1 ISO and then using Format would result in BOOTMGR-type BootSector, which is recognised and proposed for Change in NTLDR-type BootSector necessary for Install of XP.
  
• Changed : USB_XP_Setup.exe and Make_USB.exe
  Instead of LiveXP BootSDI.img one can Select now also to Add Windows PE 2.1 ISO file as RAMDISK Boot Option as being made with WinBuilder Project of allanf
  http://www.boot-land...?showtopic=7053

Comparison of LiveXP BootSDI.img IMG with Windows PE 2.1 ISO
migrate.inf made in Windows PE 2.1 Environment does NOT make USB-stick getting Preferred Drive Letter U: in XP Setup.
LiveXP provides handy Disk Management (viewing partitioning) which we miss in Windows PE 2.1
So in these respects LiveXP is preferred, but Windows PE 2.1 can be used as PE Environment for Install of XP - Launch Vista or Windows 7 Setup, whereas LiveXP can only be used to prepare Target Drive for Install of XP.

=

=

[allanf]

@wimb,

Thanks for the mention. ... ...

The screenshot looks very nice. Thanks to emergeDesktop and damian666's wallpaper. ... ...

A new version of pe21.003 will be along soon. I can't wait to test your programs (as soon as I can get my XP MCE Source organised. ... ...)

Regards

[AtomicKitten]

with the new version of usb_xp_setup.exe i got error in livexp, "target drive not listed in \makebt\dplist.txt".

Target drive used is C: and is made active.

[wimb]

WARNING
In an older Stable Project lx51808cx of amalux I noticed that the Drive Letters of Harddisk Partitions
are NOT present in the makebt\dplist.txt as produced by makebt\MBRWiz.exe /list
The result is that when USB_XP_Setup.exe is used in the lx51808cx LiveXP Environment,
then identification of Harddisk Partition from Drive Letter using makebt\dplist.txt fails,
so that USB_XP_Setup.exe cannot Continue.
It is known now that Acronis True Image Workstation 9.1 script in this build is causing the problem.

The Solution is to use another LiveXP BootSDI.img File e.g from Stable Project lx101408cxs
I can confirm that lx101408cxs works fine with USB_XP_Setup.exe
and Acronis True Image PE does NOT give the previously reported Drive Letter issue.

May be this can solve your problem.

And Target drive needs to be a Primary Partition,
and NOT a Logical drive of Extended Partition.

There was no change regarding this subject.

[wimb]

=
PROGRAM UPDATE - U_XP_SET Package - Install XP from USB

• Changed : GRUB4DOS Updated to latest grub4dos-0.4.4-2009-03-07
  GRUB4DOS Boot Problem was possible with previous version grub4dos-0.4.4-2009-03-04 when Installed in Vista bootmgr Menu.

[allanf]

@wimb

Is there an easy way to add a single RAID driver for the Setup? I have the files.

I have had to borrow an XP Pro SP2 disk, because my OEM-supplied XP Media Center source is too large for a 4GB USB device. The original OEM Installtion came from a two-disk set. I cannot see an '$OEM$' directory in the XP Media Center source. However, there is an 'OemDir' with the RAID drivers and two .inf files, whose names do not actually match the drivers or the .inf files in the driver package.

I cannot see the RAID Manufacturer listed in the Drivers Pack collection. Perhaps I should try it anyway, because I'm hoping to not have to edit too many files due to my poor vision.

Everything seems to be going OK - performing all the initial setting up from WinPE.

The target partition was created on a disk that was dual-booting XP and Windows PE 2.1/3.0, so I had bootmgr. The program did not recognize the target partition as ACTIVE until I used 'bootsect /nt52 <driveletter>'.

I believe the RAID driver is the only obstacle left.

Thanks

[wimb]

@wimb

Is there an easy way to add a single RAID driver for the Setup? I have the files.

Personally I don't have experience with RAID Drivers.
But I think in general that Integrating in your XPSOURCE the latest BTS DriverPack Massstorage with TXT Mode Enabled will do.
They claim too cover all cases ....

From the tutorial:

Supports the use of BTS DriverPacks located in OEM Folder on USB-Drive
http://driverpacks.net/DriverPacks/
For Install of XP on a modern system with SATA Drives it is needed to use DPsBase.exe
for Integrating in your XPSOURCE BTS DriverPack Massstorage with TXT Mode Enabled.
In that case a lot of Extra RAID SCSI and SATA Drivers (about 120 extra) are Integrated which appear in the
XP Setup BootFolder $WIN_NT$.~BT on Install-Drive and can prevent a lot of XP Install Boot Problems.
First use RyanVM Integrator and then use DPsBase to Improve your XP-Source.
The program supplies a Customised presetup.cmd and changes the winnt.sif file for use of DriverPacks.

[allanf]

They claim too cover all cases ....

I found a tutorial here for editing TXTSETUP.SIF.

So I'll try that first. The Driver Pack seems so much - not too big tho - for just one driver.

Let me know if this is a wrong approach for some reason.

Regards