Shulou(Shulou.com)06/03 Report--

This article mainly introduces "Why DUSE makes DOS support USB drive". In daily operation, I believe many people have doubts about why DUSE let DOS support USB drive. The editor consulted all kinds of materials and sorted out simple and easy-to-use operation methods. I hope it will be helpful to answer the doubt of "why DUSE let DOS support USB drive"! Next, please follow the editor to study!

I don't know how many people think that DOS does not support USB devices. Because the USB device standard was set after Windows 95, when Microsoft, the former owner of DOS, decided to give up and continue to develop its MS-DOS. As a result, when you want to operate USB devices under DOS, you often have to sigh. Even if the system you are using is Windows, when Windows crashes to back up or recover data, the usual USB devices such as USB hard drives become equipment.

Fortunately, Microsoft does not decide everything. DUSE developed by Pocketec provides us with support for USB storage devices (USB hard disk, floppy drive, CD-ROM drive) under DOS, but it does not support the more common USB ThumbDrive (USB disk) at present. To drive the USB USB drive under DOS, use the Motto Hairu driver. In addition, if you want to use other USB devices under pure DOS, such as USB mouse, USB printer, etc., you can use other USB drivers, such as OHCI/UHCI in USB_Link, and USB4DOS, etc., you can find the corresponding links in the "drivers" of this site, and you can see some information about using USB devices under DOS in the "frequently asked questions in use of DOS (FAQ)".

DUSE is the driver for USB storage devices under DOS. The latest version is 4.2, which was just launched this year. Its use is very simple, it can be loaded in CONFIG.SYS, or it can use its own DUSELDR.COM program to load under the DOS command line (including batch files). For example, add a line to CONFIG.SYS: DEVICE=C:\ DOS\ DUSE.EXE or execute DUSELDR C:\ DOS\ DUSE.EXE under the DOS command line.

If you are loading a USB optical drive, you need to run the optical drive extension driver in addition to the DUSE driver, and you can usually use the MSCDEX.EXE that comes with DOS. The default optical drive device name for DUSE is USBCDROM, and you can run MSCDEX.EXE from the DOS command line as follows:

MSCDEX / D:USBCDROM / K

If you want to better use and control DUSE, you can use the parameters it provides. The running parameters of DUSE are as follows:

(note: the following are the parameters of version 4.2, and the latest version 4.4 adds parameters such as EMUIRQ, UBNU, DDWAIT and so on. [] can be omitted, take VER [BOSE] as an example, VERBOSE is the complete writing of parameters, while VER is abbreviated, that is, the BOSE in [] can be omitted. )

VER [BOSE] [= x] allows status information to be displayed. The legal 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 the information is displayed in a pop-up window. The default value is 0, and the default value is 2 if the VERBOSE parameter is entered but the value of x is not set.

WAI [T] = x, sets the time (in seconds) between the time the pop-up window is displayed and the window is closed. The legal value of x is between 0 and 255, and the default value is 3. This parameter is valid only if the value of VERBOSE is 2.

DRI [VES] = x, sets the number of USB drives allowed. The value of X is from 0 to 3. If set to 0, it disables support for USB drives. The default value is 1.

NOD RIVES, disable support for USB drives. This parameter overrides the DRIVES parameter setting.

NOC [DROM], disable support for USB CD-ROM optical drives.

MEM [POOL] = x, sets the amount of additional memory allocated. DUSE calculates the number of USB controllers, the speed of transmission, and so on, to determine the size of the best memory allocation. Setting this parameter will be up to the user to determine the size of the memory allocation, the unit of x value is KB, and the legal value is between 0 and 128.

XFER [SIZE] = x, sets the maximum allowable transfer buffer. The value of x is measured in KB. Increasing the transport buffer will enhance transport performance, but it also requires more memory. The default value is 16.

SEC [TORSIZE] = x, sets the sector size of the USB drive. The value of x is expressed in bytes. The legal value is 5120.1024 or 2048, and the default is 512.

APM [STATE] = x, sets the level of APM in USB devices where the APM (Advanced Power Management) feature is enabled. Increasing this level will increase the performance of the device, but increase the loss of power supply. The status x values of the legitimate APM are listed below:

* maximum performance FEh

* Intermediate power management level 81h-FDh without suspend function

* minimum power loss for 80h without suspend function

* intermediate power management level 02h-7Fh with suspend function

* minimum power loss of 01h with hang function

The default value for x is 0x7F.

INT [13], enable hard disk INT13 function support. This feature supports some disk tools, such as FDISK.

DMA SAFE, allocating the DMA security buffer used in data transfer. This parameter must be specified when running applications that need buffers allocated from extended memory.

NOU HCI to prevent initialization of the UHCI USB controller.

NOO HCI to prevent initialization of the OHCI USB controller.

NOE HCI to prevent initialization of the EHCI USB controller.

15: UHCN=x, which specifies that the maximum number of UHCI controllers initialized by DUSE is x.

16: OHCN=x, which specifies that the maximum number of OHCI controllers initialized by DUSE is x.

17: EHCN=x, specifying that the maximum number of EHCI controllers initialized by DUSE is x.

LATE INIT, enable the delay initialization function. When using this feature, the driver loads from the CONFIG.SYS file during the DOS startup phase, but the USB device is not officially enabled until you run DUSE with the INIT parameter in the DOS command, typically at the end of the AUTOEXEC.BAT file. See the "deferred initialization" and "running DUSE as an application" section below.

19: EBAR=x, specifying the address to which the EHCI BAR (base address register) will be assigned to memory. The value of x must be a four-digit hexadecimal number with the prefix 0x. For example, to set the address of EHCI BAR to 0xE000, the correct command line option is EBAR=0xE000. The legal address area is between 0xA000 and 0xF400.

20: OBAR=x, which specifies the address to which OHCI BAR will be assigned to memory. The description of EBAR on the can be applied to OBAR.

21: UBAR=x, which specifies the address to which UHCI BAR will be assigned to memory. The description of EBAR on the can be applied to UBAR, but its legal address area is between 0x0400 and 0xF400.

CDW [AIT] [= x] instructs DUSE initialization to wait until the drive letter of the first USB CD-ROM drive is assigned, or not to end within x seconds. The legal value of x is between 0 and 30. Xroom0 is a special value that indicates that 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 no value of x is specified, the default is xroom0.

CDD [EVICE] =, specify the device name of the USB CD-ROM optical drive. The default device name is USBCDROM.

VFLOP PY, which creates a virtual image of the boot floppy disk during initialization.

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

DEVICE=C:\ DUSE\ DUSE.EXE VERBOSE DRIVES=2 XFER=8 SEC=2048 NOCD

This example setting:

* Show pop-up status window

* two USB drives are supported

* set the maximum transfer buffer size to 8K

* set the default sector size to 2048 bytes

* support for USB CD-ROM optical drives is prohibited

* about the function of "delay 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 real initialization method is to use the DUSE INIT command under the DOS command line (including in the batch file).

* about the function of "running DUSE as an application"

When you run DUSE as an application under the DOS command line, DUSE only supports the INIT parameter. This parameter is loaded on the DOS command line after the delay initialization above, so that DUSE actually initializes the USB device to actually use the USB device.

At this point, the study on "Why DUSE let DOS support USB drives" is over. I hope to be able to solve your doubts. The collocation of theory and practice can better help you learn, go and try it! If you want to continue to learn more related knowledge, please continue to follow the website, the editor will continue to work hard to bring you more practical articles!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.