duse--lets DOS support USB drives

I wonder how many people think that DOS does not support USB devices. Since the USB device standard was developed after Http://www.aliyun.com/zixun/aggregation/13559.html ">windows 95, At that time, the old owner of the dos Microsoft had decided to give up its continued development of MS-DOS. As a result, when you want to operate a USB device under DOS, it is often only exclaiming. Even if the system you are using is Windows, when Windows crashes to back up or restore data, USB devices such as USB hard disks that you use usually become a device.


Fortunately, Microsoft does not decide everything, 16886.html ">pocketec company developed Duse provides us with a DOS for USB storage devices (USB hard disk, floppy drive, optical drive) support, but it currently does not support the more common USB Thumbdrive (that is, U disk). To drive USB drives in DOS, use the motto Hairu driver. In addition, if you want to use other USB devices in pure DOS, such as USB mouse, USB printer, etc., you can use other USB drivers, such as the OHCI/UHCI in Usb_link, as well as Usb4dos, can be found in the "Driver" of the corresponding link, and can be in the " DOS in use FAQ (FAQ), see some DOS using USB device information.


Duse is a DOS USB storage device driver, currently the latest version of 4.2, is just launched this year. Its usage is simple, can be loaded in the Config.sys, also can use its own duseldr.com program to implement in the DOS command line (including batch file) load. For example, add a line to the Config.sys: Device=c:\dos\duse. EXE or execute Duseldr C:\DOS\DUSE on the DOS command line. EXE can be.


if you want to load a USB drive, in addition to loading the Duse driver, you also need to run the optical drive expansion driver, you can usually use the MSCDEX.EXE with DOS. The default optical drive device name for Duse is Usbcdrom, and you can run MSCDEX.EXE like this under the DOS command line:

mscdex/d:usbcdrom/k

If you want to better use and control Duse, you can use the parameters it provides, Duse run parameters as follows:


(Note: The following for its 4.2 version of the parameters, its latest 4.4 edition and added Emuirq, UBNU, ddwait and other parameters. [] In the case of Ver[bose] as an example, the verbose is the complete formulation of parameters, and Ver is abbreviated, that is, [] The BOSE can be omitted. ）





1:ver[bose][=x], allowing display of status information. The legal values for X are 0, 1, and 2. 0 indicates that no information is displayed, 1 indicates a text message, and 2 indicates a pop-up window to display the information.  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.


2:wai[t]=x, sets the time (in seconds) to display the pop-up window to close the window. 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.


3:dri[ves]=x, set the number of allowed USB drives. X takes values from 0 to 3. If set to 0, the support for USB drives is prohibited.  The default value is 1.


4:nod[rives], disable support for USB drives. This parameter overrides the drives parameter setting.


5:noc[drom], disables support for USB CD-ROM drives.


6:mem[pool]=x, sets the size of the allocated additional memory. Duse the number of USB controllers, the speed of transmission, and so on, to determine the optimal allocation of memory size.  Setting this parameter will determine the size of the memory allocation by the user, the unit of x value is KB, and the legal value is between 0 and 128.


7:xfer[size]=x, sets the maximum allowable transfer buffer, and the X value Unit is KB. Increasing the transport buffer will enhance transport performance, but it also requires 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.  The legal value is 512,1024 or 2048, and the default is 512.


9:apm[state]=x, set the level of APM in the USB device enabled by the APM (Advanced Power Management) feature. Increasing this level increases the performance of the device, but increases the loss of power. The status x values of the legitimate APM are listed below:


* Maximum Performance FEh


* Power management level in the middle when no suspend function 81h-fdh


* Minimum power loss 80h
without suspend function

* with suspend function in the middle of the power management level 02H-7FH


* Minimum power loss 01h
with suspend function
The default value for
x is 0x7f.


10:int[13], enable INT13 feature support for the hard disk.  This feature provides support for some disk tools, such as Fdisk.


11:dma[safe], allocating DMA security buffers used in data transfer.  This parameter must be specified when running some buffered applications that need to be allocated from extended memory.


12:NOU[HCI] To prevent initialization of the UHCI USB controller.


13:NOO[HCI] To prevent initialization of the OHCI USB controller.


14:NOE[HCI] To prevent initialization of the EHCI USB controller.


15:uhcn=x, specifies that the maximum number of UHCI controllers initialized by Duse is x.


16:ohcn=x, specifies that the maximum number of OHCI controllers initialized by Duse is x.


17:ehcn=x, specifies that the maximum number of EHCI controllers initialized by Duse is x.


18:late[init], enable the "Delay initialization" feature. When this feature is used, the driver is loaded from the Config.sys file during the DOS boot phase, but the USB device is not officially enabled until the Duse is run using the init parameter in the DOS command, typically at the end of the Autoexec.bat file. See the section "Delay initialization" and "run Duse as an application" below.


19:ebar=x, specifies that the EHCI BAR (the base address register) will be assigned to an address in memory. The value of x must be a four-bit 16-digit number with a prefix of 0x, for example, to place the address of EHCI Bar to 0xe000, the correct command-line option is ebar=0xe000. The legal address area between 0xa000 and 0xf400.


20:obar=x, specifies that OHCI bar will be assigned to an address in memory.  The above description of Ebar can be applied to Obar.


21:ubar=x, specifies that UHCI bar will be assigned to an address in memory. The above description of Ebar can be applied to Ubar, but its legal address area is between 0x0400 and 0xf400.


22:cdw[ait][=x], indicates that the initialization of Duse waits until the letter of the first USB CD-ROM drive is assigned, or does not end within X seconds. The legal value of x is between 0 and 30. X=0 is a special value that indicates that Duse will wait until the 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 is x=0.


23:cdd[evice]=< device Name, specify the device name of the USB CD-ROM drive. The default device name is Usbcdrom.


24:vflop[py], initializes a virtual image of a boot floppy disk.





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\duse. EXE VERBOSE drives=2 xfer=8 sec=2048 nocd





This example setting:


* Display pop-up status window


* supports two USB drives


* Sets maximum transfer buffer size to 8K


* Sets the default sector size to 2048 bytes


* Prohibit support for USB CD-ROM drive





* about "delay initialization" function


run Duse with the Late[init] parameter in Config.sys (for example, using Device=duse. EXE LATE), it takes a real initialization to actually use a USB device. The real initialization approach is to use the Duse init command on the DOS command line, including in a batch file.





* About the "run Duse as an application" feature


Duse as an application to run under the DOS command line, Duse only supports init parameters. This parameter is loaded on the DOS command line after "delayed initialization" above, allowing the duse to really initialize the USB device to actually use the USB device.