Name: Silver_A Date: January 15, 2004 at 01:28:32 Pacific Subject: DOS boot disk with USB,LFN,NTFS,ZIP OS: DOS CPU/Ram: P4M + 512Mb
Comment:
Two or three months ago in this forum were asked some questions on using “motto hairu” driver. I have decision on this problem. My desktop has SCSI hard disk and I’ve installed additional USB Jet Flash Drive (USB 1.1). Motherboard (ASUS P4T-E) has one UHCI controller. When I put into my CONFIG.SYS these lines:
WORNING : Found many ASPI host adapters. Please put on adapter number by option switch (/H).
So, I’ve changed this line to
DEVICE=DI1000DD.SYS /H1
and the driver was installed and I’ve got next LETTER for my SCSI disk.
After this experience I’ve tested with this modified line my notebook with only USB devices (external Sarotech Hard Disk and USB Jet Flash Drive). Both of these devices were identified successfully by USBASPI.SYS driver and DI1000DD.SYS-driver has assigned TWO different letters for them. The same result I had when used DI1000DD.SYS WITHOUT /H swith.
IMPORTANT notice: my notebook BIOS NOT ASSIGN address of the I/O port for UHCI controller and USBASPI.SYS ver.2.07 (thanks for madmaxUSB) failed to load due to this reason (with indication: I/O port for UHCI/OHCI/EHCI not assign). With any keys! And only last ver.2.15 (downloaded from MATSUs---A site) has total success! With this version we can - to indicate the particular address of I/O port by switch /P=FFE0 (this is address shown in the Windows XP at the Resource list of the UHCI Properties) - receive an ”ERROR: I/O port for UHCI not assign” and nevertheless LOAD driver successfully!
And only my Canon G5 digital photo with Compact Flash and USB interface doesn’t work as Mass Storage! Information on the SilverDisk project located on http://www.amparo.com.ru/silver_disk.htm (unfortunatelly on russian now. In some days it will on English).
Since DOS can support all of these features, it's very easy to make such a boot disk with USB,LFN,NTFS,ZIP support, isn't it? In the past a few months, we have made so many different kinds of DOS boot disks for different uses (e.g. networking, system maintenance, Chinese support, etc) in my own DOS forum.
Although USBASPI 2.15 runs a little faster than USBASPI 2.06, it seems to have an obvious bug(!?): it doesn't unload itself even if it totally fails to detect/load the USB devices. Thus, USBASPI 2.06 still seems to be the best version of USBASPI so far.
Microsoft doesn't have a page about USB for DOS, of course. But there is a lot of information and downloads about USB for DOS on the web. x86's USB and IEEE1394 page is one example:
1. Now brief information on SilverDisk project can be founded on http://www.amparo.com.ru/silver_disk_eng.htm. 2. I have published this post as answer on question from getafix2027 on using /H switch for “motto hair” driver (http://www.computing.net/dos/wwwboard/forum/13764.html). From http://dosbbs.2ya.com/ I didn’t receive any answer. 3. Also I have information to Geppo who’s response number 27 from http://www.computing.net/dos/wwwboard/forum/13679.html concerned the speed of file transferring when USB 2.0 devices are used.
I’ve tested Sarotech External Hard Box with inner Samsung HDD and USB 2.0 interface. Firstly I’ve checked the speed in Windows XP: 124 Mbs (Mbit per second)=15,5 MB/s (MB per second). It used NEC USB 2.0 chipset in my notebook. Then I tested this device without any other USB external devices (but unfortunately I didn’t reject USB touchpad in my notebook. It use OHCI as FastSpeed device). In my config.sys and autoexec.bat were loaded:
Now your new brief information page is much better than your old one. In fact, there is much useful and valuable information and answer from http://dosbbs.2ya.com/, but since you just don't understand that language, you can't find the information and answer you need. Similarly, your old page was written in a language that we could not understand, and you only wrote some information about the switch /H in your post, but the title of your thread was "DOS boot disk with USB,LFN,NTFS,ZIP", so it was obviously not very appropriate and was vague. Anyway, your new information is better and more specific/useful.