中国DOS联盟

There are many kinds of drivers for USB flash drives (mass storage disks) under DOS, but I found that only duse can support plug and play. However, when actually driving the USB flash drive, it only recognizes insertion and removal. That is, it cannot be driven normally.
I hope everyone can give some suggestions, or share experiences in this regard.
Another thing: I am using DOS ver6.22, and the configuration file config.sys is
device=a:\duse.exe nocd driver=1 ver=2 sec=2048 xfer=8

DUSE takes up too much memory and identifies few USB drive types. If there's no special need, it's better to use USBASPI.SYS.

Originally posted by fastslz at 2006-6-17 15:43:
DUSE takes up too much memory, and it identifies few USB drive types. If there's no special need, it's better to use USBASPI.SYS.

But if we use USBASPI.SYS, it doesn't support plug and play. Have you ever done something to make it support plug and play?

Hehe, I mean if there is no special need, unless the work environment only has the DOS system and can't be shut down. After all, restarting DOS only takes 4 to 8 seconds. However, USBASPI.SYS can also be loaded by command or batch processing.

DEVLOAD /H /Q /A USBASPI.SYS /V
DEVLOAD /H /Q /A DI1000DD.SYS

Originally posted by fastslz at 2006-6-17 19:41:
Hehe, I mean if there is no special need, unless the working environment only has the DOS system and cannot be powered off. After all, restarting DOS only takes 4-8 seconds. However, USBASPI.SYS can also be loaded by command or batch processing method

DEVLO ...

I am working under DOS and want to read files from the USB flash drive at any time. Plug and play is not supported. Every time I read a file, I have to restart the machine once, which is very troublesome.

Last edited by amamnn on 2006-6-18 at 12:50 ]

The working environment of the landlord is quite demanding. It has to work under DOS and also transfer large amounts of data. Why not install an MS client?

Originally posted by Michael at 2006-6-18 14:29:
The working environment of the original poster is very demanding. You have to work under DOS and also transfer large amounts of data. Why not install an MS client?

I mainly want to achieve USB plug-and-play function under DOS.

You can use loadsys to manually repeatedly load and unload USBASPI.SYS and DI1000DD.SYS.

Originally posted by fujianabc at 2006-6-19 15:41:
You can manually repeatedly load and unload USBASPI.SYS and DI1000DD.SYS using loadsys.

I have used usbaspi.sys and DI1000DD.SYS, but it doesn't support plug and play. The config.sys file is like this:
device=a:\usbaspi.sys
device=a:\di1000dd.sys
But I haven't tried repeatedly loading and unloading using loadsys. Can you be more specific about how to achieve plug and play with this as well?

Last edited by amamnn on 2006-6-19 at 16:55 ]

Originally posted by fujianabc at 2006-6-19 15:41:
You can manually repeatedly load and unload USBASPI.SYS and DI1000DD.SYS using loadsys.

I tried this loadsys in the afternoon and found a problem.
First, I loaded the USB driver (which are the above two files) in config.sys, and I could access the USB flash drive.
Then, I unplugged the USB flash drive and inserted another one. When I then tried to manually repeatedly load and unload USBASPI.SYS and DI1000DD.SYS, the system crashed.
I found that when unloading di1000dd.sys, there was a warning!!!!warning NO TSR or device driver name di1000dd.sys found!
After that, when reloading, the warning: Failed to load di1000dd.sys.

The second method, I did not load in the config.sys file, but when loading manually, I found it worked.
I don't know what the problem is. Is it a memory allocation issue.

Originally posted by amamnn at 2006-6-19 05:38 PM:

The second method, I didn't load it in the config.sys file, but when I loaded it manually, it worked.
I don't know what the problem is. Is it related to memory allocation?

It's not a memory allocation issue. The key point is that loadsys can only unload drivers loaded by itself, not those loaded in the config.sys file. Can't you just make it a batch file to load?

Originally posted by Wengier at 2006-6-19 21:16:

It's not a matter of memory allocation. The key point is that loadsys can only unload drivers loaded by itself, not those loaded in the config.sys file. Why not just make it into a batch script to load...

The administrator above, I saw that you are very familiar with this aspect in the forum. Have you ever used DUSE to drive a USB flash drive?
The above method is still a bit inconvenient. I really want to use DUSE, a software that supports plug and play. I wonder if you can give me some pointers?

Originally posted by amamnn at 2006-6-19 11:16 PM:

Administrator above, I see that you are very familiar with this aspect. Have you ever used DUSE to drive a USB flash drive?
The above method is still a bit inconvenient. I really want to use DUSE, which supports plug and play...

Unfortunately, DUSE indeed does not support USB flash drives. It mainly supports USB floppy/hard drives and USB optical drives, and is indeed powerless for USB flash drives. To support USB flash drives, basically only the USBASPI method is feasible.

Originally posted by Wengier at 2006-6-19 23:20:

It's a pity that DUSE doesn't support USB flash drives. It mainly supports USB floppy/hard drives and USB CD-ROM drives, and is indeed powerless against USB flash drives. To support USB flash drives, basically only the USBASPI method is feasible.

I also saw that in the DUSE manual, but someone told me that he had achieved it. Then I went to ask him, and he said it was a long time ago and he forgot.
It makes me think about how to achieve it every day. I've looked for many materials but can't achieve it. Really depressed.

But can USBASPI drive some USB devices with multiple LUNs? Some USB devices can have both USB-CDROM and USB-HDD at the same time.