Re: Gigabyte P35 chipset motherboard
You are indeed fortunate to have a USB floppy recognized by the XP installer at F6 time.
You can correct this easily enough, and do it on the floppy itself, not the XP cdrom.
Open the TXTSETUP.OEM file on the floppy.
Find the [HardwareIds.scsi.xxxxx] section at the bottom of the file.
Add these lines at the bottom:
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
Here is how it works:
During the text setup phase (before the GUI starts), the system BIOS tells the XP installer there is a floppy disk present. XP opens the floppy at F6 time and reads the TXTSETUP.OEM file. It also reads in the additional support you added for USB floppies.
When protected mode (GUI) Windows starts after rebooting, it loads USB support native in the OS, and recognizes the floppy drive as a USB device, and not a real floppy drive. At this point, it would ignore almost all USB floppies due to very limited support. However, you added support at F6 time, so the GUI Windows installer will continue using your USB floppy to read the RAID drivers during 32-bit setup.
This is the quick 'n dirty way to handle it for the occasional user. Those who do a lot of installing should slipstream the above USB support into txtsetup.sif file and rebuild their install CD.
You are indeed fortunate to have a USB floppy recognized by the XP installer at F6 time.
You can correct this easily enough, and do it on the floppy itself, not the XP cdrom.
Open the TXTSETUP.OEM file on the floppy.
Find the [HardwareIds.scsi.xxxxx] section at the bottom of the file.
Add these lines at the bottom:
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
Here is how it works:
During the text setup phase (before the GUI starts), the system BIOS tells the XP installer there is a floppy disk present. XP opens the floppy at F6 time and reads the TXTSETUP.OEM file. It also reads in the additional support you added for USB floppies.
When protected mode (GUI) Windows starts after rebooting, it loads USB support native in the OS, and recognizes the floppy drive as a USB device, and not a real floppy drive. At this point, it would ignore almost all USB floppies due to very limited support. However, you added support at F6 time, so the GUI Windows installer will continue using your USB floppy to read the RAID drivers during 32-bit setup.
This is the quick 'n dirty way to handle it for the occasional user. Those who do a lot of installing should slipstream the above USB support into txtsetup.sif file and rebuild their install CD.
Comment