Duse exe

A Quick way to get oneself started. Though autoexec. And the disk doesn't have many useful dos files like edit. But he didn't mention what didn't work.. It's more like, "this just works" "look, no hands". DUSE is quirky, so who knows why certain things don't work. But he didn't mention what didn't work. In one example of getting it working , he mentions [config. So i'd do it a bit differently to get the cdrom working,. So no need for the mscdex line. So, can be blank autoexec.

If I load duse. A popup comes up, and detects USB devices.. The hard drive will be detectable readable. Although I seem to recall the stefan boot disk one time when it worked, it saw my cdrom and not my USB hard drive.

And it had no generic cdrom driver. So I don't know how that happened. I look at that as an exception, and however it happened, it's no use anyway 'cos I couldn't see my usb hard drive, and i haven't been able to repeat that Consider this a hypothesis! What DUSE has done, is effectively made it a bit like as if you had an internal cdrom drive.

You can't read it yet, you need a driver for it. And there are generic drivers. An old one, is oakcdrom. In short, you'd do something like this in autoexec. THe important thing was only that they matched, that you used the same identifier for config. The computerhope site mentions using that, but with DUSE you don't load that, as mentioned. But didn't mention that that file is not part of DUSE. And some have used that with usbaspi.

I presume he said that because they are alternatives. I don't think you need to use that though. You can just make a win98 boot disk e. If the verbose parameter is entered but the value of X is not set, the default value is 2.

The legal value of X is between 0 and , and the default value is 3. This parameter is valid only when verbose is 2. The value of X is from 0 to 3. If set to 0, it means that the support of USB drive is disabled.

The default value is 1. This parameter overrides the drives parameter setting. Duse will calculate according to the number of USB controllers and transmission speed to determine the optimal size of allocated memory.

Setting this parameter will determine the size of memory allocation by the user. The unit of x value is KB, and the legal value is between 0 and The unit of x value is KB. Increasing the transmission buffer will enhance the transmission performance, but it also needs to occupy more memory.

The default value is The value of X is expressed in bytes. The legal value is or , and the default value is Increasing this level will increase the performance of the device, but will increase the loss of power supply.

This parameter must be specified when running some applications that need to allocate buffers from extended memory. The value of X must be a four digit hexadecimal number with the prefix 0x. The legal address range is 0xa to 0xf The above description of Ebar can be applied to obar.