Jump to content

Welcome to MSFN Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account



Photo

Using a F6 Driver with USB Floppy

- - - - -

  • Please log in to reply
43 replies to this topic

#26
rocketjuice

rocketjuice
  • Member
  • 1 posts
  • Joined 09-April 08
Thank you, Spiff, et al! :hello:

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

Cheers!


How to remove advertisement from MSFN

#27
dprundle

dprundle
  • Member
  • 2 posts
  • Joined 13-April 08
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, 13 April 2008 - 01:25 PM.


#28
mikhed

mikhed
  • Member
  • 1 posts
  • Joined 27-May 08
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!

#29
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,830 posts
  • Joined 23-July 04
  • OS:none specified
  • Country: Country Flag
Just for the record, since you have to re-burn the CD anyway, this method initially devised by d4vr0s:
http://www.911cd.net...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

#30
jctcom

jctcom
  • Member
  • 1 posts
  • Joined 03-August 08
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.

#31
dirtaddshp

dirtaddshp
  • Member
  • 3 posts
  • Joined 23-August 08
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

#32
satya3010

satya3010
  • Member
  • 4 posts
  • Joined 01-September 08
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....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"

#33
Heida1

Heida1
  • Member
  • 3 posts
  • Joined 10-November 08
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!

#34
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,830 posts
  • Joined 23-July 04
  • OS:none specified
  • Country: Country Flag
press "S" ? :unsure:

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

#35
Heida1

Heida1
  • Member
  • 3 posts
  • Joined 10-November 08

press "S" ? :unsure:

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

#36
Heida1

Heida1
  • Member
  • 3 posts
  • Joined 10-November 08

press "S" ? :unsure:

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


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

#37
ductbutter

ductbutter
  • Member
  • 1 posts
  • Joined 22-July 10
  • OS:none specified
  • Country: Country Flag
Thanks for the help!
Adding USB\Vid_08bd&Pid_1100&Rev_0000 did the trick for me.....saved my a**!




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



#38
bradhs

bradhs
  • Member
  • 1 posts
  • Joined 20-October 10
  • OS:none specified
  • Country: Country Flag
4 years later and wow thank god I found this! I'm in shock that I had to add those lines to keep the usb floppy drive loaded when SBS 2003 attempts to do a repair and has to copy the controller drivers from floppy but cant anymore because the usb floppy drive is no longer.

#39
tonik22

tonik22
  • Member
  • 3 posts
  • Joined 08-May 11
  • OS:XP Pro x86
  • Country: Country Flag
For everyone who wants to install Windows XP on SATA controller I recommend the following application:
LINK REMOVED

The best method so far!
1. is free
2. not require modification of the Windows installation files
3. is rapid
4. is easy
5. no floppy emulator or USB floppy is required

Posted Image

The method involves using a USB drive to load F6 drivers, they are put in FDD.ISO floppy image.
The application comes with "UniATA driver" that works with a lot of SATA controllers.
You can add your drivers editing the image FDD.ISO.

Installation involves booting from USB drive and choosing the location corresponding to the Windows XP installation files.

Good luck!

Edited by cluberti, 07 January 2012 - 12:07 PM.
This application redistributes UltraISO, which is shareware/non-free. Forum rules prohibit redistributing files or linking to programs that do this, as we are covered by US law and redistribution without copyright is illegal.


#40
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,830 posts
  • Joined 23-July 04
  • OS:none specified
  • Country: Country Flag

For everyone who wants to install Windows XP on SATA controller I recommend the following application:
.....

Seemingly nice :thumbup , but also Opera cannot seemingly download it :w00t:.
If you can, you should provide an alternate download.

Additionally, you may want to start a NEW thread here:
http://www.msfn.org/...ndows-from-usb/
where it is likely it would get more visibility.

jaclaz

Edited by jaclaz, 07 January 2012 - 07:08 AM.


#41
tonik22

tonik22
  • Member
  • 3 posts
  • Joined 08-May 11
  • OS:XP Pro x86
  • Country: Country Flag


For everyone who wants to install Windows XP on SATA controller I recommend the following application:
LINK REMOVED

Seemingly nice :thumbup , but also Opera cannot seemingly download it :w00t:.
If you can, you should provide an alternate download.

Additionally, you may want to start a NEW thread here:
http://www.msfn.org/...ndows-from-usb/
where it is likely it would get more visibility.

jaclaz



Yes you're right, I provided a alternative link for download :yes:

Please try again LINK REMOVED

Thanks for the feedback!

Edited by cluberti, 07 January 2012 - 12:08 PM.
Violation of forum rules to redist or link to redist of non-redist and non-free material (see previous post edit for further info).


#42
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,830 posts
  • Joined 23-July 04
  • OS:none specified
  • Country: Country Flag

Yes you're right, I provided a alternative link for download :yes:

Please try again .....

Thanks for the feedback!

There are IMHO SEVERAL problems with the contents of the file you supplied, including distribution/redistribution issues.

Please, remove (temporarily) the file from public distribution, as is it contains NON-REDISTRIBUTABLE software, before some of the Mods/Admins ban you for infringement of Rules :ph34r: .
Be VERY AWARE of Rule #1a:
http://www.msfn.org/...tion=boardrules

1.a This is not a warez site! Links/Requests to warez and/or illegal material (e.g., cracks, serials, etc.) will not be tolerated. Discussion of circumventing WGA/activation/timebombs/license restrictions, use of keygens, or any other illegal activity, including, but not limited to, requests for help where pirated software is being used or being discussed, will also not be tolerated. Offenders may be banned on first violation.


You may want to go through the licenses of the various software you included.

You can PM me if you want some assistance in replacing the software with something redistributable (if possible).

Also the grub4dos version you are distributing is an obsolete (and also actually deprecated) one. :w00t:

jaclaz

#43
S1L3nCeWB

S1L3nCeWB
  • Member
  • 1 posts
  • Joined 14-February 13
  • OS:none specified
  • Country: Country Flag
I just registered to this forum to give special thanks to spiff.

You are the man dude... I'm so grateful for finding this thread! Can't thank you enough!! ^___^

#44
Brock

Brock
  • Member
  • 1 posts
  • Joined 27-November 13
  • OS:XP Pro x86
  • Country: Country Flag

11-27-2013 Brock Reports:
I installed XP in AHCI mode on a Z77 mainboard using spiff's method.
I modified TXTSETUP.OEM to include the third line below:

 

[HardwareIds.scsi.iaAHCI_7]
id = "PCI\VEN_8086&DEV_1E02&CC_0106","iaStor"
id = "USB\VID_054C&PID_002C", "usbstor" #--Sony

(I did this on a second computer.)

I knew that my controller device was iaAHCI_7 as defined early in the TxtSetup.oem because I had seen the description "Intel® 7 Series/C216 Chipset Family" for the IDE controller when XP was installed in IDE mode. 
Tested by installing XP on an 11GB SATA HDD partition.
The install was just as fast as on a SSD, completing XP's "39 minute" setup in 3 minutes.

I had verified in Device Manager (on second computer) under USB Controllers, Sony USB Floppy, Properties, Details tab, that Hardware Ids was
USB\VID_054C&PID_002C  just as stated by spiff.
There was a second Hardware Id, USB\VID_054C&PID_002C&Rev_0601, but I ignored this.
The USB floppy is a Sony Model MPF82E.
Included the following files in the root directory of the floppy, as described in the readme that came with the files.
    iaAhci.inf, iaAhci.cat, iaStor.inf, iaStor.cat, iaStor.sys, and (the modified) TxtSetup.oem
The files were downloaded from Intel. Identical files were included on the GigaByte motherboard disc.
I had tried the F6 method before modifying TXTSETUP.OEM, and it seemed to work for the first half of the install, then later gave a message like "Insert the driver disk in the floppy", but it was already still in there. (As reported by others.)
My purpose was to use a modern motherboard, GigaByte Z77M-D3H, with XP and 4000MB (only) of RAM. The build is a successful dead silent fanless machine using a NOFAN CR95c cooler on a SandyBridge i3 2120T CPU rated 35W TDP. That is a story for another time.
In fact I had successfully installed a SSD under AHCI by creating a slipstreamed disc with the drivers using nLite, but I did not want to be bound to this method, and I wanted to prove the Sony USB floppy would work for a traditional F6 install.
A deep bow and a handshake to spiff for figuring this out. I have confirmed that "Golden USB floppies" are a myth, and the Sony works just fine when XP can recognize its hardware ID.

 

-Captain Brock


Edited by Brock, 30 August 2014 - 12:27 AM.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users