DUSE allows DOS to support USB drives

I wonder how many people think DOS does not support USB devices. Because the USB device standard was developed after Windows 95, and at that time DOS's old house Microsoft had decided to give up continuing to develop its MS-DOS. In this way, when you want to operate a USB device in DOS, you can only sigh. Even if you are using a Windows system and want to back up or restore data when Windows crashes, USB hard disks and other USB devices are usually used.
Fortunately, Microsoft cannot decide everything. The DUSE developed by Pocketec provides us with support for USB storage devices (USB hard drives, soft drives, and optical drives) under DOS, however, it currently does not support common USB ThumbDrive (USB flash drive ). To drive a USB flash drive under DOS, use the Motto Hairu driver. In addition, if you want to use other USB devices such as USB mouse and USB printer under pure DOS, you can use other USB drivers, such as OHCI/UHCI in USB _link and USB 4dos, you can find the corresponding link in the "driver" on this site, and you can see some information about using USB devices in DOS in "FAQ in DOS usage.
DUSE is the driver of the USB storage device under DOS. The latest version is 4.2, which was just launched this year. Its usage is very simple. It can be loaded in CONFIG. SYS, or it can be loaded in the doscommand line (including the batch files) using its built-in DUSELDR. COM program. For example, add the following line in CONFIG. SYS: DEVICE = C: \ DOS \ DUSE. EXE or execute duseldr c: \ DOS \ DUSE. EXE under the doscommand line.
If you want to load a USB optical drive, in addition to loading the DUSE driver, you also need to run the optical drive extension driver. Generally, you can use the built-in dos mscdex. EXE. The default Optical Drive Device Name of DUSE is USBCDROM. Run MSCDEX. EXE as follows in the doscommand line:

MSCDEX/D: USBCDROM/K

To better use and control DUSE, you can use the parameters provided by DUSE. The running parameters of DUSE are as follows:
(Note: The following are the parameters of Version 4.2. parameters such as EMUIRQ, UBNU, and DDWAIT are added to version 4.4. [] Indicates that VERBOSE can be omitted. For example, VERBOSE is the complete syntax of the parameter, while VER is short for it, that is, BOSE in [] can be omitted .)

1: VER [BOSE] [= x]. status information can be displayed. Valid values of x are 0, 1, and 2. 0 indicates that no information is displayed, 1 indicates that text messages are displayed, and 2 indicates that information is displayed in a pop-up window. The default value is 0. If the VERBOSE parameter is input but the value of x is not set, the default value is 2.
2: WAI [T] = x. Set the time (in seconds) for displaying the pop-up window to closing the window ). The valid value of x is between 0 and 255. The default value is 3. This parameter is valid only when VERBOSE is set to 2.
3: DRI [VES] = x. Set the number of allowed USB drives. The value of X ranges from 0 to 3. If it is set to 0, the USB drive is not supported. The default value is 1.
4: NOD [RIVES]. Do not support USB drives. This parameter will overwrite the DRIVES parameter settings.
5: NOC [DROM], do not support USB CD-ROM drive.
6: MEM [POOL] = x, set the size of the allocated additional memory. DUSE calculates the size of the allocated memory based on the number of USB controllers and transmission speed. Setting this parameter determines the size of memory allocation. The unit of x is KB and the valid value ranges from 0 to 128.
7: XFER [SIZE] = x, which sets the maximum allowed transmission buffer. The unit of x is KB. Increasing the transmission buffer will enhance the transmission performance, but it also needs to occupy more memory. The default value is 16.
8: SEC [TORSIZE] = x, set the sector size of the USB drive. The value of x is expressed in bytes. Valid values: 2048, 512, or. The default value is.
9: APM [STATE] = x, which sets the APM level in the USB device enabled by APM (Advanced Power Management. Increasing this level will increase the performance of the device, but will increase the power loss. The following lists the valid APM status x values:
* Maximum performance FEh
* Power management level 81h-FDh
* Minimum power loss of 80 h when no suspension function is available
* Power management level 02h-7Fh in the middle when the function is suspended
* Minimum power loss of 01 h with suspension Function
The default value of x is 0x7F.
10: INT [13], enabling the INT13 feature of the hard disk. This feature provides support for some disk tools (such as FDISK.
11: DMA [SAFE], which is allocated to the DMA security buffer used in data transmission. This parameter must be specified when running applications that need to allocate buffer from the extended memory.
12: NOU [HCI] to prevent uhci usb controller from being initialized.
13: NOO [HCI] to prevent ohci usb controller from being initialized.
14: NOE [HCI] to prevent ehci usb controller from being initialized.
15: UHCN = x. Specify that the maximum number of UHCI controllers initialized by DUSE is x.
16: OHCN = x. specify the maximum number of OHCI controllers initialized by DUSE as x.
17: EHCN = x. specify the maximum number of EHCI controllers initialized by DUSE as x.
18: LATE [INIT], enable the "delayed initialization" function. when this function is used, the driver starts from CONFIG. the SYS file is loaded, but the USB device is not officially enabled until you run DUSE with the INIT parameter in the doscommand, typically in AUTOEXEC. the end of the BAT file. You can see the following section "delayed initialization" and "Running DUSE as an application.
19: EBAR = x. The specified ehci bar (base address register) will be allocated to the memory address. The value of x must be a four-digit hexadecimal number with the prefix 0x. For example, to set the ehci bar address to 0xE000, the correct command line option is EBAR = 0xE000. Valid address ranges from 0xA000 to 0xF400.
20: OBAR = x. Specify the address that the ohci bar will be allocated to the memory. The preceding description of EBAR can be applied to OBAR.
21: UBAR = x. Specify the address that uhci bar will be allocated to the memory. The preceding description of EBAR can be applied to UBAR, but its valid address ranges from 0x0400 to 0xF400.
22: CDW [AIT] [= x], indicating that DUSE initialization will wait until the drive letter of the first USB CD-ROM drive is allocated, or do not end in x seconds. The valid value of x ranges from 0 to 30. X = 0 is a special value that means DUSE will wait until the drive letter of the first USB CD-ROM drive is assigned or the user presses the ESC key on the keyboard. If the value of x is not specified, the default value is x = 0.
23: CDD [EVICE] = <Device Name>, specifies the device name of the USB CD-ROM drive. The default device name is USBCDROM.
24: VFLOP [PY]. A virtual image of the boot floppy disk is created during initialization.

The following is an example of using a command line parameter. You can refer to this line to add DUSE to the CONFIG. SYS file:

DEVICE = C: \ DUSE. exe verbose drives = 2 XFER = 8 SEC = 2048 NOCD

In this example, set:
* Display the pop-up status window
* Two USB drives are supported.
* Set the maximum transmission buffer size to 8 K.
* Set the default sector size to 2048 bytes.
* Do not support USB CD-ROM drive

* Delayed Initialization
When running DUSE with the LATE [INIT] parameter in CONFIG. SYS (for example, using DEVICE = DUSE. exe late), a real Initialization is required to actually use the usb device. The actual initialization method is to use the duse init command under the doscommand line (including the batch files.

* About "Running DUSE as an application"
When DUSE is used as an application to run in the doscommand line, DUSE only supports the INIT parameter. This parameter is loaded on the doscommand line after the above "delayed initialization", so that DUSE can truly initialize the USB device to actually use the USB device.