Ok folks, here's the issue. When using a USB 1.1 thumb drive (64MB) I can load the USBASPI.SYS and NJ32DISK.SYS with no issues. But if I try to load them with a USB 2.0 (512MB) thumb drive anything after the usbaspi.sys is unrecognizable.
When booting to any USB drive the drive gets auto-assigned to c:. But after loading the usbaspi.sys on a USB 2.0 device c: is no longer available. Odd, but this doesnt happen on the USB 1.1 device.
I want to set up menus and options when booting but after loading the usbaspi.sys everything craps out. The only was I have found to get around it is to put basic loads in the config.sys and autoexec.bat then copy everything to a ramdrive and run programs from there. I'm using the boot files for a Win98 disk and usbaspi.sys and nj32disk.sys, so if anyone has any ideas I'd love to hear 'em. Thanks.

Des

You probably need a different driver, many
have been mentioned in this forum, time for
a search as this has been asked before...

See this for a definitive discussion:
http://www.computing.net/dos/wwwboard/forum/15928.html

Ok, if I'm reading everything correctly, everything works for everyone, if you boot from a floppy. That would work for me too except I'm not booting from a floppy. 2.) I have tried several other drivers (duse, aspiehci, and a couple different usbaspi's) and the only one that comes close to working is the usbaspi. But here's my question: Why does it corrupt the initial drive when the aspi driver is loaded? I have gotten around some of it by copying everything to a ramdrive before loading the usbaspi, but ehn I'm having problems there too. All I want is to be able to boot and run from my USB flash drive, no floppies, no ramdrives, etc.

Des