China DOS Union

How to release a large amount of memory consumed by loading USB drivers under pure DOS?

I have loaded XMS under MS-DOS 8.0, and after loading the USB driver, I can effectively recognize USB drives and external hard drives under pure DOS. However, a large amount of memory is consumed because the USB driver searches for USB drives. I would like to ask all the experts, what good solutions are there?

I connected an 80G external hard drive and correctly identified three external drive letters. Then under DOS, I wanted to enter these three external drive letters respectively and DIR them. As a result, I just entered the second external drive letter and then the computer crashed!

Then I restarted the computer and used MEM.EXE to check the memory usage:

Total = Used + Free
Conventional 636K 48K 588k
Total Memory 519420 154 519266
Total Under 1Mb 636K 48K 588k

Largest executable program size 584K
Largest free upper memory block 0K
Available space in High Memory Area 2K
MS-DOS is resident in the high memory area.

Then under DOS, I entered these three external drive letters respectively, and could see the file names in their respective drives. Then I executed a COPY command to copy a very small notepad file from one external drive to another, and then the computer crashed again!

May I ask why this is happening and why it always crashes? Is it a bug in the USB driver or because of insufficient memory? If it is insufficient memory, how can I release it?


Attached is the latest version of "dos4usb".

Re martin325:

It is speculated that there is a compatibility issue with the USB driver. You can determine the problem by the following method: when DOS starts, press F4 to skip the configuration of the CONIG/AUTOEXEC files. Then observe the result when loading USB. If everything is normal, it means that there is a conflict between the USB driver and one or some memory configuration programs in the C/A files. Debug line by line or by the dichotomy method until the problematic statement is found. If the system still freezes, it proves that the USB driver itself is not perfect and cannot fully support your external hard drive or motherboard.

It should be mentioned that I have tried a small number of boot disks and DOS USB drivers, but there are no successful records. Whether it is a desktop or a notebook, a flash drive or an external hard drive. Because there is no special need in this regard, I haven't studied it deeply, but I always think it is a very worthy topic for discussion in DOS technology research. I hope to get more test and usage reports to improve everyone's understanding of DOS USB drivers.

When loading USB, CONFIG.SYS only loads the following several:
Device=himem.sys /testmem:off
Device=break.sys
Device=break.sys /c
files=10
buffers=10
dos=high,umb
stacks=9,256
lastdrive=z

There is nothing loaded in AUTOEXEC.BAT either:

@echo off
goto %config%

:help
call WINMEDOS.BAT
goto quit

:usb
call LOADUSB.BAT
goto quit

:cd
call WINMEDOS.BAT
goto quit

:nocd
call WINMEDOS.BAT
goto quit

:quick
call WINMEDOS.BAT
goto quit

:quit
ECHO.

I've been using USBASPI.SYS and Di1000dd.SYS for loading, and there are no problems when using them.

I also often use USBASPI.SYS and DI1000DD.SYS drivers to drive USB flash drives under MS-DOS 7.1, and I haven't had this kind of problem either.

Encountered a similar situation, and it feels like it's still due to loading too much, resulting in insufficient memory.

For example, the phenomena I encountered:
1. Load the CD-ROM driver, Tianhui Chinese system, ntfsdos, then USBMASS fails;
Load the CD-ROM driver, Tianhui Chinese system, USBMASS, then ntfsdos fails.
2. Do not load the CD-ROM driver, only load the Tianhui Chinese system, ntfsdos, then USBMASS succeeds;
Do not load the CD-ROM driver, only load the Tianhui Chinese system, USBMASS, then ntfsdos succeeds.

It is suggested that you first optimize the boot configuration, or use the traditional boot method. Don't make the boot too fancy.

Originally, I was using LOADUSB.EXE from dos4usb to load in a batch script, and encountered the situation described in post #1.

Today, I tried directly loading Usbaspi.sys and DI1000DD.SYS in config.sys, and everything worked normally!

Now there's a problem I need to ask everyone:
How to load Usbaspi.sys and DI1000DD.SYS in a batch script?

You can use loadsys.exe to load and unload usbaspi.sys and di1000dd.sys, and then write a batch script to achieve an operation similar to plug and play under DOS. Plug in the USB flash drive and run the batch script to load the driver; before unplugging the drive, use the batch script to unload the driver.

Please ask fujianabc to provide loadsys.exe!

Found it, heh heh.
A bit large, it's 64.4K!

Because the volume of loadsys.exe is too large! I still chose devload.com to load the USB driver. Abandoned using LOADUSB.EXE in the dos4usb compressed package.

Write in the batch processing:

@echo off
echo.
echo Please insert your USB device firstly.
echo.
echo Press any key to continue...
pause >nul
echo.
echo Loading USB. Please Wait About 30 Seconds...
echo.
cd dos4usb
lh devload.com usbaspi.sys /V /NORST
lh devload.com DI1000DD.SYS
cd\

The test is all normal!

For some Atmel - based MP3 players, the speed of Panasonic USBASPI.sys is too slow. And DI1000DD.sys is very likely to have partition names with??? characters, failing to be driven or even directly exiting due to division errors when dealing with MP3 players.

Test environment: MS-DOS V8.0
It is estimated that it is a compatibility issue caused by LOADUSB.EXE.

Now there is a new problem:

How to use devload.com to uninstall the USB driver?

Please study this.

Re martin325:

It's strange that you just discovered the command-line loading method for the USB driver now, because in the readme.txt of the dos4usb.rar you provided , it clearly states that Loadusb.exe is itself a product of batch compilation. And its command-line content description has also been given.

There isn't much substantial difference between your batch file and it, except that two parameters are missing and LH is added. Maybe your problem is exactly here. Of course, using your driver and parameters, my USB flash drive still can't be recognized.

readme.txt

1 This program is a plug-and-play USB 2.0 driver under DOS;
2 After the computer is booted with DOS, insert the USB flash drive (or before booting) into any USB port of the computer;
3 Run Loadusb.exe to load the driver of the USB flash drive, and then you can read and write the data of the USB flash drive;
4 Usbaspi.sys (version 2.2) is Panasonic's latest dos USB driver.
5 devload.com is used to load the driver program; DI1000DD.sys is used to assign drive letters; loadusb.exe is actually a batch file, and its content is:
devload usbaspi.sys
devload di1000dd.sys