Using a F6 Driver with USB Floppy

Unattended CD/DVD Guide Homepage · MSFN Forum Rules

3 Pages
1
2
3
→

You cannot start a new topic
You cannot reply to this topic

Using a F6 Driver with USB Floppy This is the fix for using USB Floppy drives for F6 drivers in Textmode Rate Topic:

#1 spiff

Newbie

Group: Members
Posts: 13
Joined: 14-September 06

Posted 14 September 2006 - 02:35 PM

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.

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 an example file

#//////////////////////////////////////////////////////////////////

[Disks]
d1 = "Intel Embedded Server RAID Technology",\MegaSR,\

[Defaults]
scsi = MegaSR

[scsi]
MegaSR ="Intel Embedded Server RAID Technology (Windows XP/2003 64-bit)", MegaSR

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

[HardwareIds.scsi.MegaSR]
id="PCI\VEN_8086&DEV_2682&SUBSYS_10901734", "MegaSR"
id="PCI\VEN_8086&DEV_2683&SUBSYS_10901734", "MegaSR"
id="PCI\VEN_8086&DEV_2682&SUBSYS_81FF1043", "MegaSR"
#--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

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

#//////////////////////////////////////////////////////////////////

This post has been edited by spiff: 31 October 2006 - 12:50 PM

#2 jerry7

Group: Members
Posts: 1
Joined: 26-September 06

Posted 26 September 2006 - 08:45 AM

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.

#3 spiff

Newbie

Group: Members
Posts: 13
Joined: 14-September 06

Posted 08 October 2006 - 09:27 PM

That's exactly why I made the fix, I searched everywhere for a solution, and after about a day of research I realized the txtsetup.oem used the same formatting as txtsetup.sif. Which made sense, 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.

This post has been edited by dencorso: 11 September 2010 - 03:25 AM

#4 spiff

Newbie

Group: Members
Posts: 13
Joined: 14-September 06

Posted 13 October 2006 - 03:46 PM

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.

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

#5 5eraph

Update Packrat

Group: Supreme Sponsor
Posts: 954
Joined: 04-July 05
OS:XP Pro x64
Country:

Posted 13 October 2006 - 05:27 PM

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?

#6 vpn-user

Newbie

Group: Members
Posts: 46
Joined: 12-May 04

Posted 16 October 2006 - 11:59 PM

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

#7 spiff

Newbie

Group: Members
Posts: 13
Joined: 14-September 06

Posted 20 October 2006 - 03:34 PM

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.

#8 MrRoberts

Group: Members
Posts: 2
Joined: 22-October 06

Posted 22 October 2006 - 04:19 AM

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

[Disks]
D-I386-NT5-RAID="VIA V-RAID Driver Diskette",\I386\VIAMRAID, \I386\NT5
D-I386-NT4-RAID="VIA V-RAID Driver Diskette",\I386\VIAMRAID, \I386\NT4

[Defaults]
scsi = VCOMBORAID_I386_NT5


[SCSI]
VCOMBORAID_I386_NT5="VIA V-RAID Controller Series(Windows XP)"
VCOMBORAID_I386_WIN2K="VIA V-RAID Controller Series(Windows 2K)"
VCOMBORAID_I386_NT4="VIA V-RAID Controller Series(Windows NT4)"

[Files.SCSI.VCOMBORAID_I386_NT5]
driver = D-I386-NT5-RAID, viamraid.sys, CFG_NT5
inf = D-I386-NT5-RAID, viamraid.inf
catalog = D-I386-NT5-RAID, viamraid.cat

[Files.SCSI.VCOMBORAID_I386_WIN2K]
driver = D-I386-NT5-RAID, viamraid.sys, CFG_NT4
inf = D-I386-NT5-RAID, viamraid.inf
catalog = D-I386-NT5-RAID, viamraid.cat

[Files.SCSI.VCOMBORAID_I386_NT4]
driver = D-I386-NT4-RAID, viamraid.sys, CFG_NT4
inf = D-I386-NT4-RAID, viamraid.inf



[config.CFG_NT5]
value = parameters\PnpInterface,5,REG_DWORD,1

[config.CFG_NT4]
value = "", Tag, REG_DWORD, 1

[HardwareIds.scsi.VCOMBORAID_I386_NT5]
id = "PCI\VEN_1106&DEV_3349&CC_0104","viamraid"
id = "PCI\VEN_1106&DEV_6287&CC_0106","viamraid"
id = "PCI\VEN_1106&DEV_0591&CC_0104","viamraid"
id = "PCI\VEN_1106&DEV_3249&CC_0104","viamraid"
id = "PCI\VEN_1106&DEV_3149&CC_0104","viamraid"
id = "PCI\VEN_1106&DEV_3164&CC_0104","viamraid"
id = "PCI\VEN_1106&DEV_0581&CC_0104","viamraid"
#--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

[HardwareIds.scsi.VCOMBORAID_I386_WIN2K]
id = "PCI\VEN_1106&DEV_3349&CC_0104","viamraid"
id = "PCI\VEN_1106&DEV_6287&CC_0106","viamraid"
id = "PCI\VEN_1106&DEV_0591&CC_0104","viamraid"
id = "PCI\VEN_1106&DEV_3249&CC_0104","viamraid"
id = "PCI\VEN_1106&DEV_3149&CC_0104","viamraid"
id = "PCI\VEN_1106&DEV_3164&CC_0104","viamraid"
id = "PCI\VEN_1106&DEV_0581","viamraid"

[HardwareIds.scsi.VCOMBORAID_I386_NT4]
id = "PCI\VEN_1106&DEV_3349","viamraid"
id = "PCI\VEN_1106&DEV_5287","viamraid"
id = "PCI\VEN_1106&DEV_6287","viamraid"
id = "PCI\VEN_1106&DEV_0591","viamraid"
id = "PCI\VEN_1106&DEV_5337","viamraid"
id = "PCI\VEN_1106&DEV_3249","viamraid"
id = "PCI\VEN_1106&DEV_3149","viamraid"
id = "PCI\VEN_1106&DEV_3164","viamraid"
id = "PCI\VEN_1106&DEV_0581","viamraid"
id = "PCI\VEN_1106&DEV_5324","viamraid"

#9 MrRoberts

Group: Members
Posts: 2
Joined: 22-October 06

Posted 22 October 2006 - 06:10 AM

Nevermind. It is working nicely.

Thanks.

#10 etepalusip

Group: Members
Posts: 2
Joined: 30-June 05

Posted 28 October 2006 - 01:16 AM

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

#11 pattheman0119

Group: Members
Posts: 1
Joined: 28-October 06

Posted 29 October 2006 - 08:28 AM

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

#12 nicklad

Group: Members
Posts: 3
Joined: 06-June 05

Posted 29 October 2006 - 08:43 PM

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...

#13 etepalusip

Group: Members
Posts: 2
Joined: 30-June 05

Posted 31 October 2006 - 06:23 AM

Spiff,

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

Pete

#14 Cobravox

Group: Members
Posts: 7
Joined: 16-February 04

Posted 26 November 2006 - 05:40 PM

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!

Attached File(s)

usbstor.inf (28.75K)
Number of downloads: 108

This post has been edited by Cobravox: 26 November 2006 - 05:52 PM

#15 nikscap

Group: Members
Posts: 2
Joined: 21-July 06

Posted 19 January 2007 - 04:47 AM

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 :unsure:

, any ideas ?

#16 Bilou_Gateux

Group: Members
Posts: 766
Joined: 03-January 04

Posted 25 April 2007 - 10:12 AM

nikscap, on Jan 19 2007, 12:47 PM, said:

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.

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

#17 vpn-user

Newbie

Group: Members
Posts: 46
Joined: 12-May 04

Posted 10 May 2007 - 01:25 AM

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? :wacko:

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?

#18 Shape

Group: Members
Posts: 1
Joined: 09-August 07

Posted 09 August 2007 - 04:00 PM

Thanx Spiff,
this saved my night. :thumbup

#19 cdob

Friend of MSFN

Group: Members
Posts: 876
Joined: 29-September 05

Posted 10 August 2007 - 04:56 AM

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

Quote

USB\VID_08BD&PID_1100\5&1795AA7&0&2
Name: X1DE-USB
Hardware ID's:
USB\Vid_08bd&Pid_1100&Rev_0000
USB\Vid_08bd&Pid_1100
Compatible ID's:
USB\Class_08&SubClass_04&Prot_00
USB\Class_08&SubClass_04
USB\Class_08

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.

Quote

USB\Class_08&SubClass_02&Prot_50 = "usbstor"
USB\Class_08&SubClass_05&Prot_50 = "usbstor"
USB\Class_08&SubClass_06&Prot_50 = "usbstor"

USB\Class_08&SubClass_04&Prot_00 is missing.
Hence the txtsetup.oem addon.

What about: add Compatible ID to txtsetup.oem?

#--The following lines give additional USB floppy support
id = "USB\Class_08&SubClass_04&Prot_00", "usbstor" #Compatible ID

#20 guiambros

Group: Members
Posts: 1
Joined: 11-December 07

Posted 11 December 2007 - 02:07 AM

awesome thread, indeed!

A friend of mine saw her brand new Sony Vaio VGN-FZ140E have a major hard disk crash last week. You know the story: no back-up (because it 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 comes 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