Install XP from USB AFTER Booting with PE from HDD or USB, Install from USB without Booting from USB by using U_XP_SET External links Rating Options

[allanf]

I have no experience with Adding Drivers this way.
But you can do a few checks before actually Rebooting for launching TXT mode XP Setup.
When still in LiveXP After running USB_XP_Setup.exe
you can check if the winnt.sif file in XP setup Bootfolder $WIN_NT$.~BT made on your Target Install drive corresponds to what you intended it to be.

I have no timeline of TXT-mode of XP setup,
but the way that you describe is correct AFAIK.
Loading the drivers from $WIN_NT$.~BT in the initial phase of TXT-mode is extremely fast from Harddisk as compared to reading from CD, so that explains that individual drivers are no longer displayed in the bottom white rule.

Yes! It is all very quick. I'm sure the RAID drivers are installed at the beginning of TEXTMODE, so I don't get the 7b (b7?) blue screen.

THe $OEM$ folder containing TXTSETUP.OEM and the driver files is added during LiveXP pe21 session before boot to TEXTMODE. Like so:

<Boot_XP Drive>\$WIN_NT$.~BT\$OEM$\TXTSETUP.OEM, KR10N.sys, KR10N.INF, KR10N.CAT, VIRTUAL.INF

Also:

<Boot_XP Drive>\$WIN_NT$.~BT\winnt.sif

... with added sections:

[MassStorageDrivers]
"TOSHIBA RAID Driver for Windows XP" = "OEM"

[OEMBootFiles]
TXTSETUP.OEM
KR10N.CAT
KR10N.INF
KR10N.sys
VIRTUAL.INF

And:

<Boot_XP Drive>\txtsetup.sif

... unchanged.


Nothing else. Note there is no TEXTMODE sub-directory of $OEM$ as is normally required. Also I have not found a place for a second directory containing the RAID drivers.

My feeling is that it is the installation of the secondary or PNP drivers that is causing the error. I have an idea that the directory structure when Windows is starting is non-Standard, so that one of the .SIF files or the .OEM file is not valid. But I don't know why ... ...


Regards

[wimb]

The $OEM$ folder should NOT be added to Bootfolder $WIN_NT$.~BT on Target Drive, but should have been Added twice to XP Source Folder on USB-stick as described in your reference on this subject. Could this be the problem.
I don't know exactly how to treat this case, but
can you try to follow http://communities.intel.com/message/9523
May be ilko can comment on this.

Also txtsetup.sif in root and in Bootfolder $WIN_NT$.~BT on target drive were modified by USB_XP_Setup.exe to identify XP Setup source on USB-stick using SetupSourcePath and SetupSourceDevice in Section [SetupData]

It is also important to connect USB-stick before Booting with pe21.iso
This assures that the correct harddisk nr as given by BIOS is used in txtsetup.sif in SetupSourceDevice
Connecting USB-stick after booting with PE may result in change of harddisk nr of USB-stick on Reboot for XP setup so that SetupSource is NOT found.

[allanf]

@wimb

I hope you don't mind speculations from a novice in your otherwise well-structured Tutorial ... ...

I have another hypothesis! ...

TEXTMODE is divided into two phases.

The $OEM$ folder should NOT be added to Bootfolder $WIN_NT$.~BT on Target Drive...

In my case, in order to avoid the bluescreen, the $OEM$ folder containing TXTSETUP.OEM and driver files (no TEXTMODE sub-directory) MUST be added to Bootfolder $WIN_NT$.~BT on Target Drive. This is the first phase where required Mass Storage Drivers are installed.

Again, in my case, the only required Mass Storage Device is the Toshiba RAID Controller.

Now I speculate that the RAID Controller is NOT the only Mass Storage Device required. When first boot to TEXTMODE, the Boot Partition is the Target Drive, and when TXTSETUP.OEM is found in the $OEM$ folder on the Boot Partition, the RAID Drivers are loaded as instructed by TXTSETUP.OEM, BUT the TXTSETUP.SIF is ignored/excluded!!

In the second phase of TEXTMODE, the RAID Controller is installed, BUT the USB Device is missing ... ... It may be necessary to add more Driver descriptions to the [MassStorageDrivers] and [OEMBootFiles] Sections of WINNT.SIF with the value equal "RETAIL", so that the additional Drivers are installed in accordance with the [SCSI] Section of TXTSETUP.SIF. Is this the secret? ... ...

EDIT: When Mass Storage Drivers = "RETAIL", no need to add corresponding Driver Files List to [OEMBootFiles]. "RETAIL" refers to [SCSI] Section and Driver Files List in TXTSETUP.SIF. ? .

... but should have been Added twice to XP Source Folder on USB-stick as described in your reference on this subject. Could this be the problem?

I have tried every possible variation ... ... that I can think of! Trial-and-Error, and eliminating possibilities that have no effect.

... can you try to follow http://communities.intel.com/message/9523

In another post:
http://communities.intel.com/thread/2699

bdwilcox states:

Make sure to add the "IDE CD-ROM (ATAPI 1.2)/PCI IDE Controller" = "RETAIL" line to the [MassStorageDrivers] section in your WINNT.SIF or else the Windows install won't find the hard drive after reboot.

Hmmm... This sets up the Controllers for use in the second phase of TEXTMODE. However, rather than a CD-ROM Controller found in [SCSI] Section of TXTSETUP.SIF, this should be the USB Controller? Which is ... ? Still confused ... ...

Regards

[wimb]

In my case, in order to avoid the bluescreen, the $OEM$ folder containing TXTSETUP.OEM and driver files (no TEXTMODE sub-directory) MUST be added to Bootfolder $WIN_NT$.~BT on Target Drive.

Good, you have found this to work for your way of Adding MassStorage Drivers using winnt.sif

In the second phase of TEXTMODE, the RAID Controller is installed, BUT the USB Device is missing ...
.....
EDIT: When Mass Storage Drivers = "RETAIL", no need to add corresponding Driver Files List to [OEMBootFiles]. "RETAIL" refers to [SCSI] Section and Driver Files List in TXTSETUP.SIF. ? .

So it might be that your problem is finding the XP Setup Source folder on USB-stick.
Did you check if SetupSourcePath and SetupSourceDevice in Section [SetupData] in txtsetup.sif in root and in Bootfolder $WIN_NT$.~BT on target drive correspond to your situation ?

Again I have NO experience in Adding MassStorage Drivers using winnt.sif file.
May be you can test first if the Install from USB-stick works for you when BTS DriverPack Massstorage with TXT Mode Enabled is integrated in your XP Setup Source.
If this works for you then you are sure that NO other factors are giving the trouble.

Searching for previous versions of Windows
The manufacturer provided file that setup is trying to use is either corrupt or invalid.
Line 1 contains a syntax error.
Setup cannot continue.

I understand that in TXT-mode XP Setup you do not reach the point where the list of Drives for Install of XP is displayed.
That is in fact the strange point.

You might also simply add your MassStorage Drivers to your I386 folder on USB-stick so that these files are also available in that path.
It might be that the message you get means File Not found,
so you can provide your files at more locations,
at I386 folder and may be also in I386\$OEM$ folder.

It could be that NTDETECT.COM for detecting your hardware fails to work, because the driver files are not found.
Did you try already a modified NTDETECT.COM ?

[allanf]

Good, you have found this to work for your way of Adding MassStorage Drivers using winnt.sif

So it might be that your problem is finding the XP Setup Source folder on USB-stick.
Did you check if SetupSourcePath and SetupSourceDevice in Section [SetupData] in txtsetup.sif in root and in Bootfolder $WIN_NT$.~BT on target drive correspond to your situation ?

The device was wrong, because I had attached a USB HDD after running your program and before booting to TEXTMODE. ... ... Maybe this is one reason why the RAID Controller Drivers were being installed. The attached USB HDD became the HardDisk1, which was previously occupied by the USB Flash Drive.

I understand that in TXT-mode XP Setup you do not reach the point where the list of Drives for Install of XP is displayed.
That is in fact the strange point.

That is correct. I believe that the step after 'Searching for previous versions of Windows' would be the list of Drives. Instaed, there is a message saying that the syntax of line 1 in some file is corrupt or invalid. Press F3 to Quit, then countdown to restart.

You might also simply add your MassStorage Drivers to your I386 folder on USB-stick so that these files are also available in that path.

I discovered that the $OEM$ folder containing TXTSETUP.OEM and the RAID driver files (no TEXTMODE sub-directory) was also present in the I386 folder on the USB Flash Drive. Left over from a previous experiment. Sorry. I was not aware of it.

It might be that the message you get means File Not found,
so you can provide your files at more locations,
at I386 folder and may be also in I386\$OEM$ folder.

There is no message saying that 'File is not found' and no bluescreen. Initiallly, there was until I eliminated the cause.

It could be that NTDETECT.COM for detecting your hardware fails to work, because the driver files are not found.
Did you try already a modified NTDETECT.COM ?

No.


Thanks for all the help and guidance. I'll let you know if ever I have success.

Regards

[allanf]

A quick upddate...

Performed the entire U_XP_SET procedure from scratch with clean SP3-slipstreamed Source.

1. SetupSourceDevice in both <Boot_XP>\txtsetup.sif and <Boot_XP>\$WIN_NT$.~BT\txtsetup.sif was correct.

2. Tried a number of configurations for the $OEM$ folder on the USB Flash Drive, including removing it altogether.

Makes no difference! I cannot progress beyond the syntax error in line 1. All I need to do is find line 1! ... ...

Regards

[cdob]

I cannot progress beyond the syntax error in line 1.

Drivers are missing at textmode setup.
Setup does search $WIN_NT$.~LS\$OEM$\Textmode.

A example:

\$WIN_NT$.~BT\winnt.sif
\$WIN_NT$.~BT\$OEM$\TXTSETUP.OEM
\$WIN_NT$.~BT\$OEM$\iaahci.cat
\$WIN_NT$.~BT\$OEM$\iaAHCI.inf
\$WIN_NT$.~BT\$OEM$\iastor.cat
\$WIN_NT$.~BT\$OEM$\iaStor.inf
\$WIN_NT$.~BT\$OEM$\IaStor.sys
\$WIN_NT$.~LS\$OEM$\Textmode\TXTSETUP.OEM
\$WIN_NT$.~LS\$OEM$\Textmode\iaahci.cat
\$WIN_NT$.~LS\$OEM$\Textmode\iaAHCI.inf
\$WIN_NT$.~LS\$OEM$\Textmode\iastor.cat
\$WIN_NT$.~LS\$OEM$\Textmode\iaStor.inf
\$WIN_NT$.~LS\$OEM$\Textmode\IaStor.sys

I like winnt.sif MassStorageDrivers too.
Using this at BartPE still http://www.911cd.net/forums//index.php?showtopic=13174

[wimb]

Drivers are missing at textmode setup.
Setup does search $WIN_NT$.~LS\$OEM$\Textmode.

@allanf
Since there is no $WIN_NT$.~LS folder for this way of Install of XP from USB-stick, you can try to put the drivers additionally in $OEM$\TEXTMODE folder on Target Install Drive and if not successful may be in TEXTMODE folder (or in $WIN_NT$.~LS\$OEM$\TEXTMODE folder) on Target Drive.

And as you found already the drivers must be added to $WIN_NT$.~BT\$OEM$ folder on Target Drive.

[cdob]

One step back:
Official statement: You can't use OEMBootFiles and MassStorageDrivers at CD
http://support.microsoft.com/kb/234536/

Well this was resolved http://www.msfn.org/board/index.php?showtopic=19792

copy ALL of the driver files to these 2 directories:
$OEM$\TEXTMODE\
I386\$OEM$\

$OEM$\TEXTMODE goes nearby XP Source I386

This seems to be required at USB too.
This maybe at root or at a subdirectory.

In addition http://support.microsoft.com/kb/816299/

Make sure that OemPreinstall=Yes is in the [Unattended] section of your unattend file. If it is not, Setup does not recognize the drive

[allanf]

@allanf
Since there is no $WIN_NT$.~LS folder for this way of Install of XP from USB-stick, you can try to put the drivers additionally in $OEM$\TEXTMODE folder on Target Install Drive and if not successful may be in TEXTMODE folder (or in $WIN_NT$.~LS\$OEM$\TEXTMODE folder) on Target Drive.

... ...
I must admit I missed the ~LS from cdob. Now I have tried most variations of ~LS and ~BT including copying and renaming the entire ~BT directory so that there are two $WIN_NT$.~xx directories. I've tried the driver files in the root, in the $WIN_NT$.~xx directory(s), in the $OEM directories, and in a TEXTMODE directory, and I've tried it with those directories in all different places on the Target HDD and on the USB Flash Drive, and combinations of all.

Perhaps I have missed some variation - the missing link? I think I should leave it to someone else who might have an inkling of what's going on, because I am just stabbing in the dark. Surely an expert with a RAID controller can step forward.

And as you found already the drivers must be added to $WIN_NT$.~BT\$OEM$ folder on Target Drive.

This is the one single thing that avoids the 'file not found, press any key to continue' errors (two of) then the 7B blue screen of death. Without this directory containing the driver files and TXTSETUP.OEM, any directory structure, including the recommended TEXTMODE directory, will cause the BSOD.

The way I see the TEXTMODE is in two phases.

Firstly, 'Setup is loading files...' If I use the Pause/Break key to step through it, I see my RAID driver by name among many other things. Then the line chnges to 'Setup is starting Windows' (not absolutely sure of the wording), and there is a brief pause.

Then there is a little flicker like a mini/quasi-Reboot (into RAM?). This starts the second phase. The line changes to 'Processing..... [too quick to read]', then 'Examining disk ...MB' The sizes mentioned are correct for my 160GB RAID-0 Array which stripes across two 80GB physical HDD. In other words, the drivers are loaded and installed at this point.

Everything seems OK until 'Searching for previous versions of Windows' is completed when the '... Line #1 contains a syntax error. Setup cannot continue.... F3 to quit.' appears. It's a bluescreen, but a friendly bluescreen. Pressing F3 causes a reddish progress bar for 15-second countdown to restart.

And that's about all that I know ... ...