Question about USB drivers and memory virtualization. - China DOS Union Forum

Recently I suddenly became interested in DOS, and found my way here by searching on GOOGLE.
I sincerely thank the webmaster for the work you've done.
I have a question here.
After booting into DOS with a boot disk, I used the command
DUSELDR a:\DUSE.EXE VERBOSE XFER=64 NOCD
to load the USB driver. It works very well; my 20G mobile hard disk can now be recognized. Many thanks to the webmaster for introducing this software (unfortunately it doesn't recognize USB flash drives, which is really a pity).
Then I used XMSDSK.exe to virtualize a 5120KB space, and this is where the problem came up.
It displayed
Insufficient Memory
saying my memory was insufficient?? (My machine currently has 128M of memory)
What's going on here??

After rebooting I changed the command to
DUSELDR a:\DUSE.EXE MEM=32 NOCD
(MEM=64 doesn't work either)
and then virtualized a 3840KB space.
This time it was fine, no problem.
But when I then ran list.exe, it showed
Program too big to fit in memory

memory allocation error
cannt loadCommand,system halted
and then the system stopped just like that, and I could only reboot
This kind of problem never happened when the USB driver was not loaded.
Can anyone tell me what's going on? How can I solve it? Where did all my memory go?? How is it calculated??

It's probably a conventional memory configuration problem. You can load some programs into UMB to save conventional memory.

Sorry, what exactly do you mean by UMB?
It seems that sometimes this happens even without virtual memory.

Also, I've now found that this USB driver seems not very stable.
It crashes very easily. I don't know whether it's because of how I'm using it.
Is there anything I need to pay attention to?

It is definitely a memory configuration problem. UMB is upper memory. For details, please see DOS-related materials, and also here:
http://www.cn-dos.net/newdos/dosuse.html#doscfg

Excellent, really excellent, thank you very much.

I'll try it first, and if there are still problems I'll come back and ask.

You said that using DUSELDR a:\DUSE.EXE VERBOSE XFER=64 NOCD
to load the USB driver works very well, and that your 20G mobile hard disk can be recognized. You were very grateful to the webmaster for introducing this software. What I want to ask is whether this software is DUSE4.4? How exactly is it used? Is DUSELDR a:\DUSE.EXE VERBOSE XFER=64 NOCD loaded from drive A?

It is DUSE 4.4. It can be loaded either from the hard disk or from a floppy disk.

Floor1　大屁股超人	Posted 2003-01-26 00:00
初级用户　Posts 5　Credits 116
Recently I suddenly became interested in DOS, and found my way here by searching on GOOGLE. I sincerely thank the webmaster for the work you've done. I have a question here. After booting into DOS with a boot disk, I used the command DUSELDR a:\DUSE.EXE VERBOSE XFER=64 NOCD to load the USB driver. It works very well; my 20G mobile hard disk can now be recognized. Many thanks to the webmaster for introducing this software (unfortunately it doesn't recognize USB flash drives, which is really a pity). Then I used XMSDSK.exe to virtualize a 5120KB space, and this is where the problem came up. It displayed Insufficient Memory saying my memory was insufficient?? (My machine currently has 128M of memory) What's going on here?? After rebooting I changed the command to DUSELDR a:\DUSE.EXE MEM=32 NOCD (MEM=64 doesn't work either) and then virtualized a 3840KB space. This time it was fine, no problem. But when I then ran list.exe, it showed Program too big to fit in memory memory allocation error cannt loadCommand,system halted and then the system stopped just like that, and I could only reboot This kind of problem never happened when the USB driver was not loaded. Can anyone tell me what's going on? How can I solve it? Where did all my memory go?? How is it calculated??

Floor2　Wengier	Posted 2003-01-26 00:00
系统支持　Posts 10,521　Credits 27,736
It's probably a conventional memory configuration problem. You can load some programs into UMB to save conventional memory.

Floor3　大屁股超人	Posted 2003-01-27 00:00
初级用户　Posts 5　Credits 116
Sorry, what exactly do you mean by UMB? It seems that sometimes this happens even without virtual memory. Also, I've now found that this USB driver seems not very stable. It crashes very easily. I don't know whether it's because of how I'm using it. Is there anything I need to pay attention to?

Floor4　Wengier	Posted 2003-01-27 00:00
系统支持　Posts 10,521　Credits 27,736
It is definitely a memory configuration problem. UMB is upper memory. For details, please see DOS-related materials, and also here: http://www.cn-dos.net/newdos/dosuse.html#doscfg

Floor5　大屁股超人	Posted 2003-01-27 00:00
初级用户　Posts 5　Credits 116
Excellent, really excellent, thank you very much. I'll try it first, and if there are still problems I'll come back and ask.

Floor6　lxging	Posted 2003-02-19 00:00
初级用户　Posts 43　Credits 238
You said that using DUSELDR a:\DUSE.EXE VERBOSE XFER=64 NOCD to load the USB driver works very well, and that your 20G mobile hard disk can be recognized. You were very grateful to the webmaster for introducing this software. What I want to ask is whether this software is DUSE4.4? How exactly is it used? Is DUSELDR a:\DUSE.EXE VERBOSE XFER=64 NOCD loaded from drive A?

Floor7　Wengier	Posted 2003-02-20 00:00
系统支持　Posts 10,521　Credits 27,736
It is DUSE 4.4. It can be loaded either from the hard disk or from a floppy disk.