Op 6-6-2012 17:08, cordat...@aol.com schreef:

> On most OHCI drivers (including DOSUSB), the driver will load but then
> the keyboard starts acting erratically. (I'm using PS2 keyboard not
> USB)  Effectively the computer is not usable at this point - I suppose I
> could write a batch file to test whether it is strictly a keyboard
> problem or if there are other problems.

I've succesfully used Georg's DOSUSB v2.0 with USB flash drive 
containing a single active primary FAT32 partition. Problem is my USB 
keyboard then typically gets disabled as DOSUSB replaces BIOS drivers by 
its own stack, but a keyboard driver isn't present currently within DOSUSB.

My final solution was to get a PCI-express USB 3.0 controller card. As 
add-in cards aren't bootable (no bootrom, no driver in BIOS) nor seen in 
DOS, I'm booting from some slow USB flash drive, which loads DOSUSB 3.0 
and thus gains access to the fast flash drive connected to the add-in card.

As all other devices are on USB1/USB2 ports, they don't get disabled by 
the USB3-only DOSUSB 3.0 driver. All in all, this works pretty well for me.

The downside is that the slow USB stick that I boot from, gets drive C: 
assigned, which I dislike. Messing around with Syslinux, Memdisk and 
floppy image files works around this nicely, so I can keep C: available 
for either a ramdisk drive, or for the USB3.0 flash drive.

Alternative options are loading this driver from a floppy drive, or 
cdrom or something, but that's slower. If this device you're loading 
from is USB as well, you're in trouble as soon as loading DOSUSB v2.0 
(it resets the controller, thus also the connected drives, and you end 
up with a hung system).

> DOSUSB will find the device and set up a drive.  If I use a FAT16 device
> I can get things working reasonably well but a directory listing will
> wind up crashing the system and creating all sorts of bad behavior.
> (Yes, I understand that directory listing may take a long time but my
> expectation is that it would not crash the OS)

I've experienced that DOSUSB sometimes needs a bit longer initialisation 
time. You might also want to check the errorcode generated by it. My way 
of solving it was to load and unload DOSUSB a few times, once no more 
errorcode, I load USBDISK.SYS so the USB flash disk gets mapped.

> If I use a FAT32 device all hell breaks loose when trying to access the
> USB disk, "FCB error" messages or other scrolling messages pop up and
> the computer must be reset.

Any other older kernels or MSDOS suffering the same behaviour?
I've got most luck with JEMMEX combined with DOSUSB.

Anyway, I'm hoping my next machine can boot natively from USB3.0 
ports/devices in UEFI (and BIOS!) at above-USB2.0 speeds. Heck, Apple 
even made FireWire (and Thunderbolt?) bootable on years old EFI.

Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
Freedos-user mailing list

Reply via email to