This fix will add support for USB floppy disks in the text mode portion of Windows Setup, and allow you to load F6 drivers.
This fix should work on Windows 2000 and up.
I have only tested it with a Sony USB floppy drive on Windows XP and Windows Server 2003 x64

EDIT: Thanks go out to everyone who has added more drives to this fix.

---

Windows Setup F6 USB Floppy Drive Fix

Create your Storage device driver disk and open textsetup.oem
Add the following lines to the bottom of [HardwareIds.scsi.(device name)]
If this section does not exist you must create it!
If your USB floppy drive still does not work, look for the hardware ID in the floppy drive driver's .inf file, and make sure any legacy floppy drives are disabled in the bios.



Here is an example file

You are an absolute legend man. I googled everywhere for the answer to this, and it was all about slipstreaming the drivers to a new WinXP CD. Cheers man you saved me so much time.

That's exactly why I made the fix, I searched everywhere for a solution, and after about a day of research I reaized the txtsetup.oem used the same formatting as txtsetup.sif. Which made sence since MS likes to recycle code. This fix is more intened for people who can't make new windows CDs, like me. I couldn't make a new windows setup disc and tell my customer to install with it, not to mention the licencing issues. In a manufacturing setting this fix has saved me a ton of time.

It seems I left off the hardware id for NEC drives ( thanks to Greg for pointing that out)
Added Iomega drives ( thanks to Jammin )

updated list of hardware ids.

I don't understand.

You're putting the newly modified driver on a floppy, right? So how will the floppy be read from when its driver is not installed yet?

Can this method be extended to support USB thumb drives or HDDs? THAT would be really helpful.

vpn-user
I believe this method can be extended to USB thumb drives and USB hard drives, IF they are supported by the USBSTOR driver that is included in windows. You just need to find the hardware ID of your device, which can be found in the device manager. Look under the Universal Serial Bus controllers section for your device, goto it's properties, the details tab, then Hardware Ids, the bottom one should be the one you want. then just duplicate the formatting and add it to your txtsetup.oem file. I have not had a chance to test this, but I have loaded various other drivers via the F6 floppy method.

5eraph
When text mode first loads, it lets the system BIOS tell it what the floppy drives are, but once text mode finishes loading windows it no longer sees the USB floppy drives as a legacy floppy drive, instead it sees it as a USB device. This fix works because it tells windows what the USB device is, it exactly the same a loading a regular Mass Storage Device driver, Windows knows the device is there, it just doesn't know what it is. I hope that makes sence.

Am I doing this correctly? I use Freecom NEC USB floppy drive.

Nevermind. It is working nicely.

Thanks.

Can't wait to try this on Monday....have a new server build/install giving loads of grief.

[Disks]
d1 = "Adaptec SAS RAID Windows 2003 Device Driver", \raidisk1, \
d2 = "Adaptec RAID Windows 2003 Device Driver", \raidisk1, \

[Defaults]
scsi = arcsas

[Scsi]
arcsas = "Adaptec SAS RAID Controller", arcsas
arc = "Adaptec RAID Controller", arc

[Files.Scsi.arcsas]
driver = d1, arcsas.sys, arcsas
catalog = d1, arcsas.cat
inf = d1, arcsas.inf

[Config.arcsas]
value = "", Type, REG_DWORD, 1
value = "", Start, REG_DWORD, 0
value = "", Group, REG_SZ, "SCSI miniport"
value = "", ErrorControl, REG_DWORD, 1
value = Parameters\Device, NumberOfRequests, REG_DWORD, 0fe

[HardwareIds.scsi.arcsas]
id = "PCI\VEN_9005&DEV_0285&SUBSYS_02989005", "arcsas"
id = "PCI\VEN_9005&DEV_0285&SUBSYS_02f21014", "arcsas"
id = "PCI\VEN_9005&DEV_0285&SUBSYS_02999005", "arcsas"
id = "PCI\VEN_9005&DEV_0285&SUBSYS_029A9005", "arcsas"
id = "PCI\VEN_9005&DEV_0285&SUBSYS_02A49005", "arcsas"
id = "PCI\VEN_9005&DEV_0285&SUBSYS_02A59005", "arcsas"
id = "PCI\VEN_9005&DEV_0286&SUBSYS_95801014", "arcsas"
id = "PCI\VEN_9005&DEV_0286&SUBSYS_95401014", "arcsas"
id = "PCI\VEN_9005&DEV_0286&SUBSYS_02A29005", "arcsas"
id = "PCI\VEN_9005&DEV_0286&SUBSYS_02A39005", "arcsas"
id = "PCI\VEN_9005&DEV_0286&SUBSYS_02AC9005", "arcsas"
id = "PCI\VEN_9005&DEV_0286&SUBSYS_02A79005", "arcsas"
id = "PCI\VEN_9005&DEV_0286&SUBSYS_02A99005", "arcsas"

[Files.Scsi.arc]
driver = d2, arc.sys, arc
catalog = d2, arc.cat
inf = d2, arc.inf

[Config.arc]
value = "", Type, REG_DWORD, 1
value = "", Start, REG_DWORD, 0
value = "", Group, REG_SZ, "SCSI miniport"
value = "", ErrorControl, REG_DWORD, 1
value = Parameters\Device, NumberOfRequests, REG_DWORD, 0fe

[HardwareIds.scsi.arc]
id = "PCI\VEN_9005&DEV_0285&SUBSYS_02859005", "arc"
id = "PCI\VEN_9005&DEV_0285&SUBSYS_02869005", "arc"
id = "PCI\VEN_9005&DEV_0285&SUBSYS_02879005", "arc"
id = "PCI\VEN_9005&DEV_0285&SUBSYS_028A9005", "arc"
id = "PCI\VEN_9005&DEV_0285&SUBSYS_028E9005", "arc"
id = "PCI\VEN_9005&DEV_0285&SUBSYS_028B9005", "arc"
id = "PCI\VEN_9005&DEV_0285&SUBSYS_028F9005", "arc"
id = "PCI\VEN_9005&DEV_0285&SUBSYS_02909005", "arc"
id = "PCI\VEN_9005&DEV_0285&SUBSYS_02929005", "arc"
id = "PCI\VEN_9005&DEV_0285&SUBSYS_02939005", "arc"
id = "PCI\VEN_9005&DEV_0286&SUBSYS_028C9005", "arc"
id = "PCI\VEN_9005&DEV_0286&SUBSYS_028D9005", "arc"
id = "PCI\VEN_9005&DEV_0285&SUBSYS_3227103C", "arc"
id = "PCI\VEN_9005&DEV_0286&SUBSYS_029B9005", "arc"
id = "PCI\VEN_9005&DEV_0286&SUBSYS_029C9005", "arc"
id = "PCI\VEN_9005&DEV_0286&SUBSYS_029D9005", "arc"
id = "PCI\VEN_9005&DEV_0286&SUBSYS_029E9005", "arc"
id = "PCI\VEN_9005&DEV_0286&SUBSYS_029F9005", "arc"
id = "PCI\VEN_9005&DEV_0286&SUBSYS_02A09005", "arc"
id = "PCI\VEN_9005&DEV_0286&SUBSYS_02A19005", "arc"
#--The following lines give additional USB floppy support
id = "USB\VID_03F0&PID_2001", "usbstor" #--HP
id = "USB\VID_054C&PID_002C", "usbstor" #--Sony
id = "USB\VID_057B&PID_0001", "usbstor" #--Y-E Data
id = "USB\VID_0409&PID_0040", "usbstor" #--NEC
id = "USB\VID_0424&PID_0FDC", "usbstor" #--SMSC
id = "USB\VID_08BD&PID_1100", "usbstor" #--Iomega

What files go on the disk? Is it Just TXTSETUP.OEM?

id = "USB\VID_03F0&PID_2001", "usbstor" #--HP
id = "USB\VID_054C&PID_002C", "usbstor" #--Sony
id = "USB\VID_057B&PID_0001", "usbstor" #--Y-E Data
id = "USB\VID_0409&PID_0040", "usbstor" #--NEC
id = "USB\VID_0424&PID_0FDC", "usbstor" #--SMSC
id = "USB\VID_08BD&PID_1100", "usbstor" #--Iomega
id = "USB\VID_055D&PID_2020", "usbstor" #--Samsung

Samsung added to the list...

Spiff,

Thanks. The fix worked great. Server is up and running!!

Pete

I found in my usbstor.inf following entries:

[Generic]
%GenericBulkOnly.DeviceDesc%=USBSTOR_BULK, USB\Class_08&SubClass_02&Prot_50
%GenericBulkOnly.DeviceDesc%=USBSTOR_BULK, USB\Class_08&SubClass_05&Prot_50
%GenericBulkOnly.DeviceDesc%=USBSTOR_BULK, USB\Class_08&SubClass_06&Prot_50

[Mitsumi]
%USB\VID_03EE&PID_0000.DeviceDesc%=USBSTOR_CBI, USB\VID_03EE&PID_0000
%USB\VID_03EE&PID_6901.DeviceDesc%=USBSTOR_CBI, USB\VID_03EE&PID_6901

[HP]
%USB\VID_03F0&PID_0107.DeviceDesc%=USBSTOR_BULK, USB\VID_03F0&PID_0107
%USB\VID_03F0&PID_2001.DeviceDesc%=USBSTOR_CBI, USB\VID_03F0&PID_2001
%USB\VID_03F0&PID_4002.DeviceDesc%=USBSTOR_BULK, USB\VID_03F0&PID_4002
%USB\VID_03F0&PID_6102.DeviceDesc%=USBSTOR_BULK, USB\VID_03F0&PID_6102

[NEC]
%USB\VID_0409&PID_002C.DeviceDesc%=USBSTOR_BULK, USB\VID_0409&PID_002C
%USB\VID_0409&PID_0040.DeviceDesc%=USBSTOR_CBI, USB\VID_0409&PID_0040

[SMSC]
%USB\VID_0424&PID_0FDC.DeviceDesc%=USBSTOR_CBI, USB\VID_0424&PID_0FDC

[IBM]
%USB\VID_04B3&PID_4427.DeviceDesc%=USBSTOR_BULK, USB\VID_04B3&PID_4427

[IOData]
%USB\VID_04BB&PID_0301.DeviceDesc%=USBSTOR_CBI, USB\VID_04BB&PID_0301

[FujiFilm]
%USB\VID_04CB&PID_0100.DeviceDesc%=USBSTOR_CBI, USB\VID_04CB&PID_0100

[ScanLogic]
%USB\VID_04CE&PID_0002.DeviceDesc%=USBSTOR_BULK, USB\VID_04CE&PID_0002

[Panasonic]
%USB\VID_04DA&PID_0B01.DeviceDesc%=USBSTOR_CBI, USB\VID_04DA&PID_0B01
%USB\VID_04DA&PID_1B00.DeviceDesc%=USBSTOR_CB, USB\VID_04DA&PID_1B00
%USB\VID_04DA&PID_0B03.DeviceDesc%=USBSTOR_BULK, USB\VID_04DA&PID_0B03

[SCM]
%USB\VID_04E6&PID_0001.DeviceDesc%=USBSTOR_CB, USB\VID_04E6&PID_0001
%USB\VID_04E6&PID_0002.DeviceDesc%=USBSTOR_BULK, USB\VID_04E6&PID_0002
%USB\VID_04E6&PID_000A.DeviceDesc%=USBSTOR_BULK, USB\VID_04E6&PID_000A
%USB\VID_04E6&PID_0101.DeviceDesc%=USBSTOR_BULK, USB\VID_04E6&PID_0101

[Sony]
%USB\VID_054C&PID_0022.DeviceDesc%=USBSTOR_BULK, USB\VID_054C&PID_0022
%USB\VID_054C&PID_0023.DeviceDesc%=USBSTOR_CB, USB\VID_054C&PID_0023
%USB\VID_054C&PID_0024.DeviceDesc%=USBSTOR_CB, USB\VID_054C&PID_0024
%USB\VID_054C&PID_0025.DeviceDesc%=USBSTOR_CB, USB\VID_054C&PID_0025
%USB\VID_054C&PID_002C.DeviceDesc%=USBSTOR_CBI, USB\VID_054C&PID_002C
%USB\VID_054C&PID_0032.DeviceDesc%=USBSTOR_CBI_NR, USB\VID_054C&PID_0032
%USB\VID_054C&PID_0037.DeviceDesc%=USBSTOR_CBI, USB\VID_054C&PID_0037
%USB\VID_054C&PID_0046.DeviceDesc%=USBSTOR_CBI, USB\VID_054C&PID_0046
%USB\VID_054C&PID_004A.DeviceDesc%=USBSTOR_CBI, USB\VID_054C&PID_004A
%USB\VID_054C&PID_0056.DeviceDesc%=USBSTOR_CBI_NR, USB\VID_054C&PID_0056
%USB\VID_054C&PID_0058.DeviceDesc%=USBSTOR_CBI, USB\VID_054C&PID_0058
%USB\VID_054C&PID_0069.DeviceDesc%=USBSTOR_CBI_NR, USB\VID_054C&PID_0069

[YEData]
%USB\VID_057B&PID_0000.DeviceDesc%=USBSTOR_CBI, USB\VID_057B&PID_0000
%USB\VID_057B&PID_0001.DeviceDesc%=USBSTOR_CBI, USB\VID_057B&PID_0001
%USB\VID_057B&PID_0010.DeviceDesc%=USBSTOR_BULK, USB\VID_057B&PID_0010

[Iomega]
%USB\VID_059B&PID_0001.DeviceDesc%=USBSTOR_BULK, USB\VID_059B&PID_0001
%USB\VID_059B&PID_0030.DeviceDesc%=USBSTOR_BULK, USB\VID_059B&PID_0030
%USB\VID_059B&PID_0031.DeviceDesc%=USBSTOR_BULK, USB\VID_059B&PID_0031
%USB\VID_059B&PID_0032.DeviceDesc%=USBSTOR_BULK, USB\VID_059B&PID_0032
%USB\VID_059B&PID_0060.DeviceDesc%=USBSTOR_BULK, USB\VID_059B&PID_0060

[LaCie]
%USB\VID_059F&PID_A601.DeviceDesc%=USBSTOR_CB, USB\VID_059F&PID_A601
%USB\VID_059F&PID_A602.DeviceDesc%=USBSTOR_CB, USB\VID_059F&PID_A602

[TEAC]
%USB\VID_0644&PID_0000.DeviceDesc%=USBSTOR_CBI, USB\VID_0644&PID_0000
%USB\VID_0644&PID_1000.DeviceDesc%=USBSTOR_BULK, USB\VID_0644&PID_1000

[Hagiwara]
%USB\VID_0693&PID_0002.DeviceDesc%=USBSTOR_BULK, USB\VID_0693&PID_0002
%USB\VID_0693&PID_0003.DeviceDesc%=USBSTOR_BULK, USB\VID_0693&PID_0003
%USB\VID_0693&PID_0005.DeviceDesc%=USBSTOR_BULK, USB\VID_0693&PID_0005
%USB\VID_0693&PID_0006.DeviceDesc%=USBSTOR_BULK, USB\VID_0693&PID_0006
%USB\VID_0693&PID_0007&MI_00.DeviceDesc%=USBSTOR_BULK, USB\VID_0693&PID_0007&MI_00
%USB\VID_0693&PID_000A.DeviceDesc%=USBSTOR_BULK, USB\VID_0693&PID_000A

[Imation]
%USB\VID_0718&PID_0002.DeviceDesc%=USBSTOR_BULK, USB\VID_0718&PID_0002
%USB\VID_0718&PID_0003&MI_00.DeviceDesc%=USBSTOR_BULK, USB\VID_0718&PID_0003&MI_00

[SanDisk]
%USB\VID_0781&PID_0001.DeviceDesc%=USBSTOR_CB, USB\VID_0781&PID_0001
%USB\VID_0781&PID_0002&MI_00.DeviceDesc%=USBSTOR_BULK, USB\VID_0781&PID_0002&MI_00
%USB\VID_0781&PID_0100.DeviceDesc%=USBSTOR_CB, USB\VID_0781&PID_0100

[Casio]
%USB\VID_07CF&PID_1001.DeviceDesc%=QV2KUX, USB\VID_07CF&PID_1001

[DioGraphy]
%USB\VID_0892&PID_0101.DeviceDesc%=USBSTOR_BULK, USB\VID_0892&PID_0101

[M-Sys]
%USB\VID_08EC&PID_0010.DeviceDesc%=USBSTOR_BULK, USB\VID_08EC&PID_0010

[Addonics]
%USB\VID_0BF6&PID_1234.DeviceDesc%=USBSTOR_BULK, USB\VID_0BF6&PID_1234
%USB\VID_0BF6&PID_0103.DeviceDesc%=USBSTOR_BULK, USB\VID_0BF6&PID_0103

[OnSpec]
%USB\VID_55AA&PID_0102.DeviceDesc%=USBSTOR_BULK, USB\VID_55AA&PID_0102
%USB\VID_55AA&PID_0103.DeviceDesc%=USBSTOR_BULK, USB\VID_55AA&PID_0103
%USB\VID_55AA&PID_1234.DeviceDesc%=USBSTOR_BULK, USB\VID_55AA&PID_1234
%USB\VID_55AA&PID_B004.DeviceDesc%=USBSTOR_BULK, USB\VID_55AA&PID_B004
%USB\VID_55AA&PID_B200&MI_00.DeviceDesc%=USBSTOR_BULK, USB\VID_55AA&PID_B200&MI_00
%USB\VID_55AA&PID_B204&MI_00.DeviceDesc%=USBSTOR_BULK, USB\VID_55AA&PID_B204&MI_00
%USB\VID_55AA&PID_B207&MI_00.DeviceDesc%=USBSTOR_BULK, USB\VID_55AA&PID_B207&MI_00

Is this possible to add this also in txtsetup.sif and/or dosnet.inf if needed?
Example:

Add following lines under section:

[HardwareIdsDatabase]

...

I don't know the correct syntax to implement this, maybe someone else has better knowledge to add those extra usb-floppy devices?

Greets from Belgium!

Hi guys,

I tried this solution with a USB KEY and it doesn't work at all ! It's weird because the USB KEY use exactly the same principle.

1) - Get the USB\VID adress :

With Devcon I list all the " hardware ID's of devices. " with the command line : Devcon /hwids * > OUT.TXT

#-----------------------------------------------------#

USB\VID_0930&PID_6540F8125605192D91E
Name: USB Mass Storage Device
Hardware ID's:
USB\Vid_0930&Pid_6540&Rev_0200
USB\Vid_0930&Pid_6540

#-----------------------------------------------------#

2) - Add the new ID within the " txtsetup.oem "

#--The following lines give additional USB floppy support

id = "USB\VID_03F0&PID_2001", "usbstor" #--HP
id = "USB\VID_054C&PID_002C", "usbstor" #--Sony
id = "USB\VID_057B&PID_0001", "usbstor" #--Y-E Data
id = "USB\VID_0409&PID_0040", "usbstor" #--NEC
id = "USB\VID_0424&PID_0FDC", "usbstor" #--SMSC
id = "USB\VID_08BD&PID_1100", "usbstor" #--Iomega
id = "USB\VID_055D&PID_2020", "usbstor" #--Samsung
id = "USB\Vid_0930&Pid_6540", "usbstor" #--MY USB KEY *

3) - Go to the BIOS configuration and enable the floppy emulation over the USB KEY

On theory everything is fine, except the fact that it doesn't work , any ideas ?

try to use 'USB floppy/mass storage support for ProLiant servers during the TxtSetup phase of installation' dummyUSB driver here

Just to understand this right: To support USB Floppy drivers for F6 function, you don't have to change anything on the CD but in txtsetup.oem on the floppy?

I wonder because windows setup is never told to load any usb floppy drivers? Or is USB support already enabled by default and just has to be "used"? My USB floppy drive LED never lights up when using F6 so how would changing txtsetup.oem make any difference?

Thanx Spiff,
this saved my night.

There are Compatible ID's too. A Iomega USB floppy

XP txtsetup.sif contain some USB floppy Hardware ID's VID_*&PID_* . Some USB floppy drives are missing.
In addtition there are some usbstor Compatible ID's already.USB\Class_08&SubClass_04&Prot_00 is missing.
Hence the txtsetup.oem addon.

What about: add Compatible ID to txtsetup.oem?

awesome thread, indeed!

A friend of mine saw her brand new Sony Vaio VGN-FZ140E to have a major hard disk crash last week. You know the story: no back-up (because was new, she said), physical problem with the disk, a data recovery company charging tons of money, etc.

Anyway, I was trying to reinstall the OS (and downgrade from vista do Windows XP at the same time). As I didn't have a usb floppy I tried first with a usb pen drive, but didn't have much luck. Decided to give nlite a try, and was blown away by the program's capabilities.

Not only it recognized that I was using a Media Center's edition of Win XP, but also asked for the 2nd disk that cames with it, and nicely packed the drivers for my SATA controller (intel 82801HEM/HBM SATA AHCI) and turned the 3-cd's hassle into a nice custom DVD instead. Everything went smooth and in 10 minutes I was back on the game.

So, if you are stuck as many others here with F6 issue, etc, give nlite a try.

best,

guilherme ambros

Yes! Lets keep this going. Here's my contrib.

SanDisk U3 Cruizer Micro USB Device

id = "usb\VID_0781&PID_5406", "usbstor" #--sandisk

Haven't tested it yet but I'm sure this method can be refined even more; including more thurough instructions especially with thumb drives.

BTW Which txtsetup do you modify, the .oem that comes with the drivers (and if so where do you put it) or the txtsetup.sif in the i386 directory of the windows installation.

hi. im having a BIG problem here.. Im at a clients, ive wasted a full day. they want to boot from san, but I cant get the drivers for the qlogic fibre card working.
here is the full OEM file, please review and tell me where I am going wrong.
First off, It says insert disk in to drive a: am i missing something where I can use something else? im trying to use a USB drive.

The last line is obviously my USb cruzer drive/
PLEASE HELP, CLIENT ISNT HAPPY WITH ME

EDIT I got my lacie floppy drive to work THANKS for that. BUT the qlogic drive sys file says its corrupted... ive downloaded it 5 times... Do you think its actually corrupt? or just the way windows is reading it?
And actually, it fines the qlogic driver etc, and then it says "windows had a driver already, would you like to use the floppy, or microsofts" If i choose floppy it says the sys file is corrupt, if i choose micrsofts it says "no hard drive disks found"
what a freakin disaster


EDIT 2 - issues resolved. first off, diskette driver worked this time. driver from qlogic, recommended by tech support, was corrupt.. used a different driver from their site and im off and running.
wow am I thrilled.
thanks for pointing me in the right directions guys and gals

can someone please post the latest version of the files on the net? i am in terrible need of them for my intel 82801 sata.

thank you,
korsuas

I'm using the 512 MB Memorex TravelDrive USB 2.0...
This is exactly what I see in the device manager for hardware ID:

USBSTOR\DISK&PROD_MEMOREX_TD_2B&REV_PMAP\07521C9238B9&0

Now my question is where specifically I insert this string in the txtsetup.oem file ?
Do I need the entire string ?
Please see my setup file below and indicate how I do this. Greatly appreciated !!!



; ****************************************************************************
; ****************************************************************************
; ** Filename: TxtSetup.OEM
; ****************************************************************************
; ****************************************************************************

[Disks]
disk1 = "Intel Matrix Storage Manager driver", iaStor.sys, \

[Defaults]
scsi = iaStor_ICH8R

;----------- Component Section -----------

[scsi]
iaStor_ICH8R = "Intel® 82801HR/HH/HO SATA RAID Controller (Desktop ICH8R)"
iaAHCI_ICH8R = "Intel® 82801HR/HH/HO SATA AHCI Controller (Desktop ICH8R)"
iaStor_ESB2 = "Intel® 631xESB/632xESB SATA RAID Controller (Server/Workstation ESB2)"
iaAHCI_ESB2 = "Intel® 631xESB/632xESB SATA AHCI Controller (Server/Workstation ESB2)"
iaStor_ICH7MDH = "Intel® 82801GHM SATA RAID Controller (Mobile ICH7MDH)"
iaStor_ICH7DH = "Intel® 82801GR/GH SATA RAID Controller (Desktop ICH7R/DH)"
iaAHCI_ICH7R = "Intel® 82801GR/GH SATA AHCI Controller (Desktop ICH7R/DH)"
iaAHCI_ICH7M = "Intel® 82801GBM SATA AHCI Controller (Mobile ICH7M/DH)"
iaStor_ICH6R = "Intel® 82801FR SATA RAID Controller (Desktop ICH6R)"
iaAHCI_ICH6R = "Intel® 82801FR SATA AHCI Controller (Desktop ICH6R)"
iaAHCI_ICH6M = "Intel® 82801FBM SATA AHCI Controller (Mobile ICH6M)"

;-------------------------------------------

[Files.scsi.iaStor_ICH8R]
driver = disk1, iaStor.sys, iaStor
inf = disk1, iaStor.inf
catalog = disk1, iaStor.cat

[Files.scsi.iaAHCI_ICH8R]
driver = disk1, iaStor.sys, iaStor
inf = disk1, iaAHCI.inf
catalog = disk1, iaAHCI.cat

[Files.scsi.iaStor_ESB2]
driver = disk1, iaStor.sys, iaStor
inf = disk1, iaStor.inf
catalog = disk1, iaStor.cat

[Files.scsi.iaAHCI_ESB2]
driver = disk1, iaStor.sys, iaStor
inf = disk1, iaAHCI.inf
catalog = disk1, iaAHCI.cat

[Files.scsi.iaStor_ICH7DH]
driver = disk1, iaStor.sys, iaStor
inf = disk1, iaStor.inf
catalog = disk1, iaStor.cat

[Files.scsi.iaAHCI_ICH7R]
driver = disk1, iaStor.sys, iaStor
inf = disk1, iaAHCI.inf
catalog = disk1, iaAHCI.cat

[Files.scsi.iaStor_ICH7MDH]
driver = disk1, iaStor.sys, iaStor
inf = disk1, iaStor.inf
catalog = disk1, iaStor.cat

[Files.scsi.iaAHCI_ICH7M]
driver = disk1, iaStor.sys, iaStor
inf = disk1, iaAHCI.inf
catalog = disk1, iaAHCI.cat

[Files.scsi.iaStor_ICH6R]
driver = disk1, iaStor.sys, iaStor
inf = disk1, iaStor.inf
catalog = disk1, iaStor.cat

[Files.scsi.iaAHCI_ICH6R]
driver = disk1, iaStor.sys, iaStor
inf = disk1, iaAHCI.inf
catalog = disk1, iaAHCI.cat

[Files.scsi.iaAHCI_ICH6M]
driver = disk1, iaStor.sys, iaStor
inf = disk1, iaAHCI.inf
catalog = disk1, iaAHCI.cat


;-------------------------------------------

[Config.iaStor]
value = "", tag, REG_DWORD, 1b
value = "", ErrorControl, REG_DWORD, 1
value = "", Group, REG_SZ, "SCSI miniport"
value = "", Start, REG_DWORD, 0
value = "", Type, REG_DWORD, 1

;-------------------------------------------------------

[HardwareIds.scsi.iaStor_ICH8R]
id = "PCI\VEN_8086&DEV_2822&CC_0104","iaStor"

[HardwareIds.scsi.iaAHCI_ICH8R]
id = "PCI\VEN_8086&DEV_2821&CC_0106","iaStor"

[HardwareIds.scsi.iaStor_ESB2]
id = "PCI\VEN_8086&DEV_2682&CC_0104","iaStor"

[HardwareIds.scsi.iaAHCI_ESB2]
id = "PCI\VEN_8086&DEV_2681&CC_0106","iaStor"

[HardwareIds.scsi.iaStor_ICH7DH]
id = "PCI\VEN_8086&DEV_27C3&CC_0104","iaStor"

[HardwareIds.scsi.iaStor_ICH7MDH]
id = "PCI\VEN_8086&DEV_27C6&CC_0104","iaStor"

[HardwareIds.scsi.iaAHCI_ICH7R]
id = "PCI\VEN_8086&DEV_27C1&CC_0106","iaStor"

[HardwareIds.scsi.iaAHCI_ICH7M]
id = "PCI\VEN_8086&DEV_27C5&CC_0106","iaStor"

[HardwareIds.scsi.iaStor_ICH6R]
id = "PCI\VEN_8086&DEV_2652&CC_0104","iaStor"

[HardwareIds.scsi.iaAHCI_ICH6R]
id = "PCI\VEN_8086&DEV_2652&CC_0106","iaStor"

[HardwareIds.scsi.iaAHCI_ICH6M]
id = "PCI\VEN_8086&DEV_2653&CC_0106","iaStor"

SPIFF, You are a god man! Your hack worked great the first time.
Nothing less than FANTASTIC! I wish I would have found this years ago.
Thank You, Thank You, Thank You!

Thank you, Spiff, et al!

You have saved me from running around the building, screaming (though, it would likely have been amusing to watch).

Cheers!

how do you create the storage device driver disk? I have Y-E and when I plug it in vista auto-recognizes it.

I'm confused on the process. I want to install Raid drivers using a USB floppy.

Is this correct:

#1) Create a Device storage driver disk for the usb floppy drive?

#2) Loading windows press F6..

#3) Remove disk in floppy drive and put in floppy disk that contains raid drivers??


Sorry for the questions but i'm really confused.

A connected USB floppy disk drive does not work when you press F6 to install mass storage drivers during the Windows 2003 installation process

I have found a solution.
In a microsoft website ( http://support.microsoft.com/kb/916196 ) you can see only a part of solution. Below is full info:

You need to modify txtsetup.sif in i386 folder of your windows 2003 setup disks (this will work with windows 2003 R2 installation!).
See Microsoft website:
--------------------
The following USB floppy disk drives are included in the Txtsetup.sif file and are therefore supported for use during Windows XP installation:
USB\VID_03EE&PID_6901 Mitsumi
USB\VID_057B&PID_0000 Y-E Data; Sony part number 09K9835
USB\VID_0644&PID_0000 TEAC; IBM option part number 27L4226, FRU 05K9283
------------------------------------
Find in txtsetup.sif:
USB\VID_03EE&PID_6901
or
USB\VID_057B&PID_0000
or
USB\VID_0644&PID_0000

and, below, add for USB floppy disk drive models (HP, Sony, Y-E Data, NEC, SMSC):

USB\VID_057B&PID_0001 = "usbstor"
USB\VID_0409&PID_0040 = "usbstor"
USB\VID_0424&PID_0FDC = "usbstor"
USB\VID_08BD&PID_1100 = "usbstor"
USB\VID_055D&PID_2020 = "usbstor"

It is easy, BUT, this is not all! You need to change another block!

Find (these strings will be below strings that you have added):
USB\Class_08&SubClass_02&Prot_50 = "usbstor"
or
USB\Class_08&SubClass_05&Prot_50 = "usbstor"
or
USB\Class_08&SubClass_06&Prot_50 = "usbstor"

and, below, add:
USB\Class_08&SubClass_04&Prot_00 = "usbstor"

Das it alles! That's all!
Just write new distributive to a CD and boot!

Just for the record, since you have to re-burn the CD anyway, this method initially devised by d4vr0s:
http://www.911cd.net/forums//index.php?showtopic=20543
works very well, at least for a limited number of machines, eliminating the actual USB floppy drive.

Basically you re-create the CD using a bootloader (I use grldr directly) instead of the "standard" "Microsoft Corporation.img" or "Arnes Boot record", and you add to the CD the needed floppy image(s), which can also be gzipped and thus will occupy a very small amount of space on cd.

jaclaz

Hopefully someone is still monitoring this thread. I have tried this solution but I do not know where to get the files listed in the section copied below.? I am trying this using a Sony MPF82E USB Floppy Drive. (The only files on the CD for Windows XP are SonyMSDK.sys & SonyFDMS.W2K. There are other files in the Win98 and Win2000.ME folders.

[Files.scsi.MegaSR]
driver = d1, MegaSR.sys, MegaSR
inf = d1, MegaSR.inf
inf = d1, NODEV.inf
catalog = d1, MegaSR.cat

also as far as I can tell when connecting this drive to a computer already running it looks like WinXP is using a sfloppy.sys for the driver.

Please help I need to get this incorporated into a raid installation.

Why Microsoft insists on pulling these files from a floppy instead of letting you choose the drive and path that are detected in the bios is a mystery and a pain to me. How can the largest technology company in the world be so backwards?

the board I am installing on does not even have a floppy connector. So I can't even use a regular floppy if I wanted to.

Thank you in advance.

Carl.

im trying to get this to work on my .OEM file. But i see theres multible HardwareIds.scsi's heres what my file looks like.

where should i add the code? Im using XP 2005 Media Center Edition.

#
# format for txtsetup.oem.
#
# General format:
#
# [section]
# key = value1,value2,...
#
#
# The hash ('#') introduces a comment.
# Strings with embedded spaces, commas, or hashes should be double-quoted
#


# This section lists all disks in the disk set.
#
# <description> is a descriptive name for a disk, used when
# prompting for the disk
# <tagfile> is a file whose presence allows setup to recognize
# that the disk is inserted.
# <directory> is where the files are located on the disk.
#

[Disks]

d1 = "VIA RAID Combo Driver Diskette", \RAID\winxp\VIAMRAID.SYS, \RAID\winxp
d2 = "VIA RAID Combo Driver Diskette", \RAID\win2000\VIAMRAID.SYS, \RAID\win2000
d3 = "VIA RAID Combo Driver Diskette", \RAID\Winnt40\VIAMRAID.SYS, \RAID\Winnt40
d4 = "VIA RAID Combo Driver Diskette", \RAID\2003ia32\VIAMRAID.SYS, \RAID\2003ia32
#d9 = "VIA RAID Combo Driver Diskette", \RAID\x64\VIAMRAID.SYS, \RAID\x64

d5 = "VIA ATA/ATAPI Host Controller Driver", \PIDE\winxp\viapdsk.sys, \PIDE\winxp
d6 = "VIA ATA/ATAPI Host Controller Driver", \PIDE\win2000\viapdsk.sys, \PIDE\win2000
d7 = "VIA ATA/ATAPI Host Controller Driver", \PIDE\winnt40\viapdsk.sys, \PIDE\winnt40
d8 = "VIA ATA/ATAPI Host Controller Driver", \PIDE\2003ia32\viapdsk.sys, \PIDE\2003ia32

# This section lists the default selection for each 'required'
# hardware component. If a line is not present for a component,
# the default defaults to the first item in the [<component_name>]
# section (see below).
#
# <component_name> is one of computer, display, keyboard, mouse, scsi
# <id> is a unique <within the component> string to be associated
# with an option.

[Defaults]

scsi = VIARAID_MULTIPLE_XP


# This section lists the options available for a particular component.
#
# <id> is the unique string for the option
# <description> is a text string, presented to the user in a menu
# <key_name> gives the name of the key to be created for the component in
# HKEY_LOCAL_MACHINE\ControlSet001\Services

[scsi]
VIARAID_MULTIPLE_2003IA32 = "VIA RAID Controller(Windows 2003 IA32)"
VIARAID_MULTIPLE_XP = "VIA RAID Controller(Windows XP)"
VIARAID_MULTIPLE_2K = "VIA RAID Controller(Windows 2000)"
VIARAID_MULTIPLE_NT = "VIA RAID Controller(Windows NT4)"
#VIARAID_MULTIPLE_2003K864 = "VIA RAID Controller(Windows 2003 AMDx86-64)"

VIAPDSK_VT4149_2003IA32 = "VIA ATA/ATAPI Host Controller(Windows 2003IA32)"
VIAPDSK_VT4149_XP = "VIA ATA/ATAPI Host Controller(Windows XP)"
VIAPDSK_VT4149_2K = "VIA ATA/ATAPI Host Controller(Windows 2000)"
VIAPDSK_VT4149_NT = "VIA ATA/ATAPI Host Controller(Windows NT4)"

# This section lists the files that should be copied if the user
# selects a particular component option.
#
# <file_type> is one of driver, port, class, dll, hal, inf, or detect.
# See below.
# <source_disk> identifies where the file is to be copied from, and must
# match en entry in the [Disks] section.
# <filename> is the name of the file. This will be appended to the
# directory specified for the disk in the [Disks] section to form the
# full path of the file on the disk.
#=======================================#

[Files.scsi.VIARAID_MULTIPLE_XP]
driver = d1, viamraid.sys, VIAMRAID_NT5
inf = d1, viamraid.inf
## Cat file directive. It should be marked with non-digital signed driver
catalog = d1, viamraid.cat

[Files.scsi.VIARAID_MULTIPLE_2K]
driver = d2, viamraid.sys, VIAMRAID_NT4
inf = d2, viamraid.inf
## Cat file directive. It should be marked with non-digital signed driver
catalog = d2, viamraid.cat

[Files.scsi.VIARAID_MULTIPLE_NT]
driver = d3,viamraid.sys,VIAMRAID_NT4
inf = d3,viamraid.inf

[Files.scsi.VIARAID_MULTIPLE_2003IA32]
driver = d4, viamraid.sys, VIAMRAID_NT5
inf = d4, viamraid.inf
## Cat file directive. It should be marked with non-digital signed driver
catalog = d4, viamraid.cat

#[Files.scsi.VIARAID_MULTIPLE_2003K864]
#driver = d9, viamraid.sys, VIAMRAID_NT5
#inf = d9, viamraid.inf

#[HardwareIds.scsi.VIARAID_MULTIPLE_2003K864]
#id = "PCI\VEN_1106&DEV_3249","viamraid"
#id = "PCI\VEN_1106&DEV_3149","viamraid"
#id = "PCI\VEN_1106&DEV_3164","viamraid"

[HardwareIds.scsi.VIARAID_MULTIPLE_2003IA32]
id = "PCI\VEN_1106&DEV_3249","viamraid"
id = "PCI\VEN_1106&DEV_3149","viamraid"
id = "PCI\VEN_1106&DEV_3164","viamraid"

[HardwareIds.scsi.VIARAID_MULTIPLE_XP]
id = "PCI\VEN_1106&DEV_3249","viamraid"
id = "PCI\VEN_1106&DEV_3149","viamraid"
id = "PCI\VEN_1106&DEV_3164","viamraid"

[HardwareIds.scsi.VIARAID_MULTIPLE_2K]
id = "PCI\VEN_1106&DEV_3249","viamraid"
id = "PCI\VEN_1106&DEV_3149","viamraid"
id = "PCI\VEN_1106&DEV_3164","viamraid"


# This section lists the files that should be copied if the user
# selects a particular component option.
#
# <file_type> is one of driver, port, class, dll, hal, inf, or detect.
# See below.
# <source_disk> identifies where the file is to be copied from, and must
# match en entry in the [Disks] section.
# <filename> is the name of the file. This will be appended to the
# directory specified for the disk in the [Disks] section to form the
# full path of the file on the disk.
#=======================================#

[Files.scsi.VIAPDSK_VT4149_XP]
driver = d5, viapdsk.sys, VIAMRAID_NT5
inf = d5, viapide.inf
## Cat file directive. It should be marked with non-digital signed driver
catalog = d5, viapdsk.cat

[Files.scsi.VIAPDSK_VT4149_2K]
driver = d6, viapdsk.sys, VIAMRAID_NT4
inf = d6, viapide.inf
## Cat file directive. It should be marked with non-digital signed driver
catalog = d6, viapdsk.cat

[Files.scsi.VIAPDSK_VT4149_NT]
driver = d7, viapdsk.sys, VIAMRAID_NT4
inf = d7, viapide.inf

[Files.scsi.VIAPDSK_VT4149_2003IA32]
driver = d8, viapdsk.sys, VIAMRAID_NT5
inf = d8, viapide.inf
## Cat file directive. It should be marked with non-digital signed driver
catalog = d8, viapdsk.cat

[HardwareIds.scsi.VIAPDSK_VT4149_2003IA32]
id = "PCI\VEN_1106&DEV_4149","viapdsk"

[HardwareIds.scsi.VIAPDSK_VT4149_XP]
id = "PCI\VEN_1106&DEV_4149","viapdsk"

[HardwareIds.scsi.VIAPDSK_VT4149_2K]
id = "PCI\VEN_1106&DEV_4149","viapdsk"

#===============================================================================
# This section specifies values to be set in the registry for
# particular component options. Required values in the services\xxx
# key are created automatically -- use this section to specify additional
# keys to be created in services\xxx and values in services\xxx and
# services\xxx\yyy.
#
# <key_name> is relative to the services node for this device.
# If it is empty, then it refers to the services node.
# If specified, the key is created first.
# <value_name> specifies the value to be set within the key
# <value_type> is a string like REG_DWORD. See below.
# <value> specifies the actual value; its format depends on <value_type>

[Config.VIAMRAID_NT5]
value = Parameters\PnpInterface, 5, REG_DWORD, 1

[Config.VIAMRAID_NT4]
value = "", Tag, REG_DWORD, 1

HI ALL

Im using Windows server 2003 OS on Dell power edge 2850 server.
Earlier i have done ASR backup on Server #1 using ntbackup utility ASR wizard.
ASR backup have created files in (tape and diskette).
Then, right now im trying to restore (server #1 ASR) on another server which is (server #2).

During the asr restore, my server #2 was unable to detect the ASR tape.
it looks like i need to install Dell PowerVault 100T DAT72 tape driver during the much earlier process where
i need to press F6 to install 3rd part driver and scsi card.
I do have the driver downloaded in below link (folder name DAT72DRV and the content: pvdatw2k.inf , pvdatw2k.sys , pvdatw2k.cat )

http://support.dell.com/support/downloads/...mp;fileid=93032

When i tried to install (press S specify the 3rd parcty driver on the blue screen), "txtsetup.oem file not found" error pop up

i have contacted the DELL and Quantum guys and they told me that they doesnt have txtsetup.oem file for Dell PowerVault 100T DAT72 tape drive.


Do u know how to create the txtsetup.oem file for Dell Power Vault 100T tape drive to point to pvdatw2k.inf , pvdatw2k.sys , pvdatw2k.cat

Below is the txtsetup.oem file for Adaptec 39160 SCSI - Family Manager Set
Can anyone help to change below txtsetup.oem file to use for Dell PowerVault 100T DAT72 tape drive ??



#-------------------------------------------------------------
# Copyright © Adaptec Inc. 2007
#
#-------------------------------------------------------------

#
# General format:
#
# [section]
# key = value1,value2,...
#
#
# The hash ('#') introduces a comment.
# Strings with embedded spaces, commas, or hashes should be double-quoted
#

#-------------------------------------------------------------
#
# [Disks]
#
# This section lists all disks in the disk set.
#
# <description> is a descriptive name for a disk, used when
#
# prompting for the disk
# <tagfile> is a file whose presence allows setup to recognize
# that the disk is inserted.
#
# <directory> is where the files are located on the disk.
#
#-------------------------------------------------------------
[Disks]
d1 = "Adaptec Ultra160 Windows 32-bit FMS4.0 SP5 S5", \u160dsk1, \

#-------------------------------------------------------------
#
# [Defaults]
#
# This section lists the default selection for each 'required'
# hardware component. If a line is not present for a component,
# the default defaults to the first item in the [<component_name>]
# section (see below).
#
# <component_name> is one of computer, display, keyboard, mouse, scsi
# <id> is a unique <within the component> string to be associated
# with an option.
#
#-------------------------------------------------------------
[Defaults]
scsi = a7899NT60

#-------------------------------------------------------------
#
# [scsi]
#
# This section lists the options available for a particular component.
#
# <id> is the unique string for the option
# <description> is a text string, presented to the user in a menu
# <key_name> gives the name of the key to be created for the component in
# HKEY_LOCAL_MACHINE\ControlSet001\Services
#
#-------------------------------------------------------------
[scsi]
a7899NT60 = "Adaptec Ultra160 Windows 32-bit FMS4.0 SP5 S5"

#-------------------------------------------------------------
# [Files.scsi.a78xxNT40]
#
# This section lists the files that should be copied if the user
# selects a particular component option.
#
# <file_type> is one of driver, port, class, dll, hal, inf, or detect.
# See below.
#
# <source_disk> identifies where the file is to be copied from, and must
# match en entry in the [Disks] section.
#
# <filename> is the name of the file. This will be appended to the
# directory specified for the disk in the [Disks] section to form the
# full path of the file on the disk.
#
#-------------------------------------------------------------
[Files.scsi.a7899NT60]
driver = d1, adpu160m.sys, adpu160m
inf = d1, adpu160m.inf
catalog = d1, adpu160m.cat


#-------------------------------------------------------------
#
# [Config.adpu160m]
#
# This section specifies values to be set in the registry for
# particular component options. Required values in the services\xxx
# key are created automatically -- use this section to specify additional
# keys to be created in services\xxx and values in services\xxx and
# services\xxx\yyy.
#
# <key_name> is relative to the services node for this device.
# If it is empty, then it refers to the services node.
# If specified, the key is created first.
#
# <value_name> specifies the value to be set within the key
#
# <value_type> is a string like REG_DWORD. See below.
#
# <value> specifies the actual value; its format depends on <value_type>
#
#-------------------------------------------------------------
#
[Config.adpu160m]
value = "", tag, REG_DWORD, 20
value = Parameters\PnpInterface,5, REG_DWORD,1

[HardwareIds.scsi.a7899NT60]
id = "PCI\VEN_9005&DEV_00C0", "adpu160m"
id = "PCI\VEN_9005&DEV_00C0&SUBSYS_F6209005", "adpu160m"
id = "PCI\VEN_9005&DEV_00C0&SUBSYS_F6200E11", "adpu160m"

id = "PCI\VEN_9005&DEV_0080", "adpu160m"
id = "PCI\VEN_9005&DEV_0080&SUBSYS_E2A09005", "adpu160m"
id = "PCI\VEN_9005&DEV_0080&SUBSYS_E2A00E11", "adpu160m"
id = "PCI\VEN_9005&DEV_0080&SUBSYS_62A09005", "adpu160m"
id = "PCI\VEN_9005&DEV_0080&SUBSYS_E2209005", "adpu160m"

id = "PCI\VEN_9005&DEV_00CF", "adpu160m"
id = "PCI\VEN_9005&DEV_008F", "adpu160m"

HELP!!

Hi Spiff -

I am terribly unfamiliar with syntax and I am trying desperately to add a Raid 0 driver to a fresh WinXp install. I am having the same troubles as those in this thread and I have tried to add the new commands that will allow Windows to read various USB floppies, but I don't seem to be having any luck. My floppy drive seems to work fine under all circumstances, except during the install. At what point exactly should the disk be accessed to read the new commands? My understanding is that the driver disk is not inserted until after you press "S" to add drivers - at this point it is too late how ever, because my floppy will not read at this point.

Can someone please point to the location where I should add the new commands and let me know when I should put the disk in the floppy:

; A HardwareIds.scsi.Service section specifies the hardware IDs of
; the devices that a particular mass-storage driver supports.
;
; [HardwareIds.scsi.Service]
; id = "deviceID","service"
;
; HardwareIds.scsi.Service
; Service specifies the service to be installed.
;
; <deviceId > Specifies the device ID for a mass-storage device.
; <service > Specifies the service to be installed for the device.
;The following example excerpt shows a HardwareIds.scsi.Service section for a disk device:
;

[HardwareIds.scsi.RAIDCLASS_2KXP]
id = "GenNvRaidDisk","nvraid"
id = "*_NVRAIDBUS","nvraid"

[HardwareIds.scsi.BUSDRV_2KXP]
id = "PCI\VEN_10DE&DEV_008E", "nvatabus"
id = "PCI\VEN_10DE&DEV_0085", "nvatabus"
id = "PCI\VEN_10DE&DEV_00D5", "nvatabus"
id = "PCI\VEN_10DE&DEV_00EE", "nvatabus"
id = "PCI\VEN_10DE&DEV_00E3", "nvatabus"
id = "PCI\VEN_10DE&DEV_00E5", "nvatabus"
id = "PCI\VEN_10DE&DEV_0035", "nvatabus"
id = "PCI\VEN_10DE&DEV_0036", "nvatabus"
id = "PCI\VEN_10DE&DEV_003E", "nvatabus"
id = "PCI\VEN_10DE&DEV_0053", "nvatabus"
id = "PCI\VEN_10DE&DEV_0054", "nvatabus"
id = "PCI\VEN_10DE&DEV_0055", "nvatabus"

[HardwareIds.scsi.RAIDCLASS_2003]
id = "GenNvRaidDisk","nvraid"
id = "*_NVRAIDBUS","nvraid"

[HardwareIds.scsi.BUSDRV_2003]
id = "PCI\VEN_10DE&DEV_008E", "nvatabus"
id = "PCI\VEN_10DE&DEV_0085", "nvatabus"
id = "PCI\VEN_10DE&DEV_00D5", "nvatabus"
id = "PCI\VEN_10DE&DEV_00EE", "nvatabus"
id = "PCI\VEN_10DE&DEV_00E3", "nvatabus"
id = "PCI\VEN_10DE&DEV_00E5", "nvatabus"
id = "PCI\VEN_10DE&DEV_0035", "nvatabus"
id = "PCI\VEN_10DE&DEV_0036", "nvatabus"
id = "PCI\VEN_10DE&DEV_003E", "nvatabus"
id = "PCI\VEN_10DE&DEV_0053", "nvatabus"
id = "PCI\VEN_10DE&DEV_0054", "nvatabus"
id = "PCI\VEN_10DE&DEV_0055", "nvatabus"

Also - I have an ABIT Mobo with Phoenix Bios - I'm wondering if I have something askew in the bios - I tried to identify where my floppy disk is, but I am unable to find it and thus, I can not see if there is a legegacy drive turned on.

Thanks in advanced to anyone that can help me out!

press "S" ?

Put the floppy disk in the floppy drive, with the compuiter off.
Boot from CD.
Press F6 at the very beginning of the booting, you will be prompted in the lower white bar and have a handful of seconds to press F6.

Chack this if in doubt:
http://pcsupport.about.com/od/operatingsys...xprepair1_3.htm


About BIOS there won't probably be a "USB floppy" related entry, there might be a "generic" USB legacy support" or a "USB keyboard support"

jaclaz

Thanks Jaclaz.

The Press "S" refers to the point at the beginning of the install (after the F6 blue screen) where Windows states press S if you need to install 3rd party drivers or enter to continue.

I think my issue may lie in the placement of the additional text in the driver file. I will follow your instructions and try again.

Thanks so much.

Heida1

jaclaz ->

The floppy disk was left in the usb drive from the beginning and I disabled the USB keyboard and Mouse options in the BIOS.

When my WinXP CD booted, I pressed F6. After windows loaded some drivers, it asked me if I had a 3rd party disk to load the mass storage drivers. (If so press "s"). I pressed S and nothing happened. I hit "enter".

This error message came up:

Section Files.scsi.raidclass_2k of the INF file is Invalid

I pressed "Enter"

This error message came up:

File caused an error (0) at
Line 2166 in d:\xpsprtm\base\boot\setup\oemdisk.C.

More drivers loaded and then it said Windows is starting.

A message came up stating that Windows could not find a hard drive.... and the system rebooted.

I am totally clueless as to what to do. Any help would be very much appreciated.

THANKS!!!