Jump to content

Using a F6 Driver with USB Floppy


spiff

Recommended Posts

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

Link to comment
Share on other sites

  • 2 weeks later...

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?

Link to comment
Share on other sites

  • 2 months later...

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

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.

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

Link to comment
Share on other sites

  • 4 months later...

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

Link to comment
Share on other sites

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.

Edited by bigefficient
Link to comment
Share on other sites

  • 1 month later...

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

Edited by dunginhawk
Link to comment
Share on other sites

  • 2 weeks later...
  • 2 weeks later...

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"

Link to comment
Share on other sites

  • 3 weeks later...
  • 1 month later...

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.

Edited by dprundle
Link to comment
Share on other sites

  • 1 month later...

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!

Link to comment
Share on other sites

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

Link to comment
Share on other sites

  • 2 months later...

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.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...