Main purpose of this pack to provide IEEE1394 SBP2 (FireWire) support for DOS in form of ASPI driver. Also include driver for ASPI HDD devices. For CD-ROM support, description of USBASPI.SYS parameters and many other useful links see http://www.mwpms.uklinux.net/usbfire.txt Content: README.TXT SBP2ASPI.SYS USBASPI.SYS DI1000DD.SYS ASPIHSTS.exe README.TXT: This file. SBP2ASPI.SYS: IEEE1394 SBP2 (FireWire) ASPI provider. Unlocked for working with all SBP2 IEEE1394 (FireWire) devices driver. Also this parameters for SBP2ASPI.SYS discovered: DEVICE=SBP2ASPI.SYS [/V] [/H:x] [/RES] [/RBC] [/B] [/M:xxxx] [/I:xx] /V - verbose mode /H:x - x is number from 0 to 9 - OHCI1394 controller number to which driver will linking, by default - 0 /RES - force to stay resident, even without devices /RBC - very important key. There is SCSI command set for HDD was splitted in 2 standard - full(SBC) and reduced (RBC). By default old programs for working with SCSI through ASPI like DI1000DD.SYS process only SBC devices. This key helps mimic RBC devices for such old programs as SBC. My Sarotech USB2.0+FW combobox is RBC device - so this key for me. /B - ??? /M:xxxx - xxxx - hexadecimal two byte number, ??? /I:xx - xx - hexadecimal one byte number, ??? USBASPI.SYS: USB Mass Storage Devices on OHCI, UHCI and EHCI controllers ASPI provider. Version 2.15. DI1000DD.SYS: Driver for ASPI HDD devices. INT 13h extended support. Original version report INT13h disk size = (real disk size size - 1) sectors in INT 13h handler so patched to report full size. ASPIHSTS.EXE: This is my program to display all ASPI hosts and devices on it. Also work with WINASPI32 in DOS BOX of Win 9x. My CONFIG.SYS example for USB 2.0: device=C:\ANY\USB\usbaspi.sys /e /v /noprt /norst devicehigh=C:\ANY\USB\di1000dd.sys My CONFIG.SYS example for FireWire: device=C:\ANY\USB\sbp2aspi.sys /v /rbc devicehigh=C:\ANY\USB\di1000dd.sys This file locate at: http://sweetlow.at.tut.by/download/sbp2dos.zip --- SweetLow ---

To rogerashley: Thanks, but I'm also interested in response if anybody test my patched drivers to confirm validity.

Hmm, but where previous post from rogerashley? Weirding :(

I had previously tried the only FireWire driver available, but it had never recognised the FireWire PCI card, though will experiment again. I will contact x86 and ask him to look at it as well. I have had several posts removed as I do not like Windows questions in the DOS Forum.

I have had a quick perusal, though do not have any FireWire Devices, the PCI Card was recognised, which is OHCI complient. I have two other different make PCI Cards and will try your software to see if they are recognised, will post back soon...

I have three different PCI Firewire Cards OHCI complient and they are all recognised. I have no requirement for FireWire devices, but would be interested in peer to peer firewire networking as would x86.