中国DOS联盟

My x22 has no external CD drive.
So I want to use a USB CD drive (Newman Clone King + Liteon 40x) under DOS.
Downloaded msdos7.1o.
Copied it to a dual-boot USB flash drive and booted the machine.
But after selecting options 3 and 4, config.sys had an error.
Could not enter DOS normally.
Selected option 2 to enter DOS.
But it didn't work.
device duse.exe drivers=2
As soon as it runs, it shows cpu error.
Used device usbaspi.sys.
Recognized the CD drive.
But said that drive A could not be found. I estimate that the system can only use one USB device.
How to solve this problem?

Have you used it? Compare the differences with self-made later. Thanks

Mainly it's about driving the printer??? Unfortunately, there's no way.

Hello everyone, I'm new here.
But I've been paying attention to boot disks all the time. I'm very happy to find this forum this time, and I hope to communicate and learn together with you.
My email:wangguangxin333@163.com

A few days ago, I saw someone say that the floppy disk image used to burn bootable CDs in Nero supports NTFS, USB, 1394, etc. after booting. I took a look and sure enough, so I extracted the drivers inside.

The drivers can make DOS support USB optical drives, external hard drives, and flash drives, as well as 1394 external hard drives.

There are several types of drivers. The ones in the drdosusb directory are extracted from the boot software image of Ahead Nero. There are file system drivers for FAT32 and NTFS, which can support USB/1394 optical drives and USB drives.

For example, a machine has an NTFS partition, a USB drive, and an optical drive. After loading the respective drivers, ntfsread.exe will assign a drive letter to the NTFS partition, fat32.exe will assign a drive letter to the USB drive, and mscdex.exe will assign a drive letter to the optical drive.

Using this driver program from Nero is another way to drive USB storage devices under DOS. Everyone can also try combining it with other drivers.

http://bbs.wuyou.com/cgi-bin/topic.cgi?forum=34&topic=3055&show=0

I can't upload attachments, and there is a download in the URL in the above post.

@ECHO Off
rem Tool extracted from the Nero - provided dr dos boot disk, supports fat32 ntfs, usb/1394 removable hard drives and optical drives
Rem First load the usb hd/flash memory driver usbd.sys, then fat32.exe can assign a drive letter.
rem Load ordinary IDE optical drive
ECHO Loadng IDE CDROM driver
ctload ECSCDIDE.SYS /D:MSCD001
echo.
echo Loading USB Mass storage driver
ctload USBD.SYS
echo Loading 1394/fireware driver
ctload SCDD.SYS /D:USBCD001
echo.
echo Loading NTFS Filesystem Driver for DOS
NTFSREAD
echo.
echo Loading FAT32 Filesystem Driver for DOS, mount USB disk
FAT32
echo.
mscdex /D:MSCD001 /D:USBCD001
rem mscdex /D:USBCD001

Thank you, received.

DEVICE=USBASPI.SYS /R /V /NORST
DEVICE=ASPIOHCI.SYS /INT /ALL
DEVICE=ASPIUHCI.SYS /INT /ALL
DEVICEHIGH=DI1000DD.SYS

I tested and analyzed Wengier's super MS-DOS 7.10 bootable disk and found that there is an issue with the usage above. There are two drivers that both support my flash drive, and as a result, DI1000DD.SYS doesn't know which one to choose and doesn't use either, so the flash drive isn't assigned a drive letter. This is probably the reason many people mentioned that they found the USB drive but there's no drive letter.

The following is the error message during startup
DI1000 ASPI DISK Driver Ver 2.00
...
WARNING: Found many ASPI host adapters.Please put on dadapter number by option switch /h
HA #0: USB MASS Storage
HA #1:
Driver install abourt.
So only one of the drivers should be used, or add parameters to di1000. It is recommended to use ctload to dynamically load drivers in the future, which is more flexible.

The following is the statement quoted by bbcat on June 17, 2004, 01:16:30 AM:
My x22 has no external CD - ROM.
So I want to use a USB CD - ROM under DOS (Newman Clone King + Liteon 40x).
Downloaded msdos7.1o.
Copied it to a dual - boot USB flash drive and booted the machine.
But after selecting items 3 and 4, the config.sys had an error.
Could not enter DOS normally.
Selected 2 to enter DOS.
But it could not be used.
device duse.exe drivers = 2
As soon as it was run, it showed cpu error.
Used device usbaspi.sys.
Could recognize the CD - ROM.
But said that drive A could not be found.
I estimated that the system could only use one USB device.
How to solve this problem?

After booting from the USB flash drive and loading the USB driver, drive A cannot be found. This is related to the method of loading devices and USB drivers in the config.sys and autoexec.bat of Wengier's boot disk. The following are some experiments I did on USB drivers last night.
Using and Coordinating Methods of USB Drivers under DOS by jetsun
Relationship between the file size of the driver program and the version: Many files downloaded online have different sizes but are the same version because they are compressed by tools (upx, pklite, diet) to reduce space.
Coordinating methods:
①、DUSE is used alone to detect USB Disk Drive, USB CDROM.
②、USBASPI.SYS + DI1000DD.SYS (64Mb flash OTi Ultra Floppy can be used).
③、USBASPI.SYS + NJ32DISK.SYS (used for flash experiments, the capacity is not recognized correctly, the drive letter is assigned, but it prompts that the disk is not formatted).
④、USBASPIN.SYS + DI1000DD.SYS (64Mb flash OTi Ultra Floppy can be used).
⑤、USBASPIN.SYS + NJ32DISK.SYS (used for flash experiments, the capacity is not recognized correctly, the drive letter is assigned, but it prompts that the disk is not formatted).
⑥、USBD.SYS + FAT32.EXE (64Mb flash OTi Ultra Floppy can be used).
⑦、ASPIUHCI.SYS + DI1000DD.SYS
ASPIOHCI.SYS + DI1000DD.SYS
⑧、USBASPI.SYS + USBCD.SYS drives the USB CD - ROM.
SBP2ASPI.SYS + NJ32DISK.SYS /R 1394

The driver can be loaded using ctload.exe or device.com, which can be done to load from autoexec.bat or the command prompt after the system starts, instead of loading from config.sys.
--------------------------------------------------------------------------------
There are the following types of ASPI managers:
USBASPI.SYS Panasonic(TM) USB to ASPI driver v2.06, Supports UHCI/OHCI (USB 1.x) and EHCI (USB 2.0)
USBASPIN.SYS ASPI for UHCI/OHCI USB mass - storage Version 1.07, Copyright(C) 2001 NOVAC Co.,Ltd.
ASPIOHCI.SYS Iomega ASPI USB - OHCI 1.1 V.32 2002/08/06
ASPIUHCI.SYS Iomega ASPI USB - UHCI 1.1 V.21 2002/08/06 (supports flash)
ASPIEHCI.SYS Iomega ASPI USB - EHCI USB 2.0
aspi1394.sys Iomega ASPI 1394 - Firewire 1.0 V.01 : 06 Aug 2002. Copyright (C) 2002 Iomega Corporation.
SBP2ASPI.SYS ASPI Manager for 1394(SBP2) device Version 1.02, Copyright (C) 2001 - 2002 Medialogic Corp
provides ASPI mapping of Firewire storage devices.
CDSDMINI.SYS CD - SD Mini / ASPI Version 6th Release 94/07/02, Copyright(C)Uno 1992 - 94
--------------------------------------------------------------------------------
There are the following types of Disk Driver:
USBCD.SYS USB CD - ROM Device Driver Version 1.00,(C)Copyright Panasonic Communications Co., Ltd.
NJUSBCDA.SYS NinjaUSB ASPI CD - ROM Driver (ATAPI) Ver 3.09, Copyright(C)2000 Workbit Corporation.
IBMUSBCD.SYS ???
aspicd.sys ???

DI1000DD.SYS DI1000 ASPI Mass Storage Device Driver Ver 2.00, Copyright(C)2001 NOVAC Co.,Ltd.
NJ32DISK.SYS Ninja SCSI - 32 UDE SCSI DISK DRIVER Ver1.06, Copyright(C) 1999 - 2002 Workbit Corporation.

ASPIDISK.SYS ASPI Disk Driver for DOS, Version 4.01, Copyright 1989 - 1996 Adaptec, Inc
EXTCD.SYS USB/1394 CD - ROM Driver 1.00, Copyright 2003 Dell Computer Corporation
--------------------------------------------------------------------------------
guest.exe Iomega Guest Driver Version 8.5 , file size 14,874
RAMFD.SYS RAM FD DRIVER Version 1.00 from NOVAC(possibly only supports standard 1.44Mb floppy disks)
DUSE.EXE
--------------------------------------------------------------------------------
Drivers and NTFS/FAT32 file system drivers for USB/1394 storage devices in Ahead's boot disk:
USBD.SYS USB Driver
SCDD.SYS FireWire/Serial - CD driver
NTFSREAD.EXE NTFS Filesystem Driver for DR - DOS, v1.200, also has the function of assigning drive letters to NTFS partitions of IDE HDD/USB HDD devices
FAT32.EXE FAT32LFN Driver for DR - DOS, v1.200, has the function of assigning drive letters to FAT32 partitions of IDE/USB disks
--------------------------------------------------------------------------------

If you boot from a USB device and then load the USB device driver, the DOS boot disk needs to use ramdisk, put command.com of the DOS system in it, and reset COMSPEC. For example, boot from an external USB CD - ROM or flash.

Bad or Missing USBCD1.SYS
Error in CONFIG.SYS line 3
Bad or Missing Command Interpreter
Enter correct name of Command Interpreter (eg. C:\COMMAND.COM
A>

If RAMFD boots the system from a certain simulated floppy medium (flash/USB floppy drive/USB CD - ROM) and then loads the driver placed on that medium, there may be a situation where command.com cannot be found. I think the reason may be that the access right to that medium is replaced by the new driver under DOS. So create a virtual disk in memory, then put the files that may be used later, such as command.com, in it, and set COMSPEC to point to the memory disk. RAM FD copies boot floppy disk contents into a RAM disk, write protects and remaps drive letters to RAM disk. This /w switch of USBASPI.SYS is typically used on portable systems with an external USB floppy drive connected to the single USB port for boot - up. Used in conjunction with RAMFD.SYS so after the boot floppy is copied to a RAM drive, (and after the /W pause...) the USB floppy can be removed, and the target mass storage device can be attached and detected。
Q:I'm booting from a USB CD ROM disk which creates a RAM drive and loads the USB CD ROM drivers. Once this happens, I can no longer access the boot files on the CD ROM disk (A:).
A:This happens when you trying to install a Driver for the device which you are using to boot from. It's just like you boot with a floppy disk, and before the boot is complete, you take out the floppy suddenly when you still need the files on it, of course, it will prompt that the files on drive A cannot be found.
It would be better to have the system copy all the contents of the boot floppy to the ramdisk before activating the USB drivers.
This is a common problem that I have ran into myself. When the USB drivers take control of the USB ports the BIOS is unable to have control. As of yet I have not found a work around for this problem.
Best to just copy all bootfiles from the bootloader to the ramdisk then activate the usbdriver then you should be good to go.
After the USB driver under DOS gains control of the USB device, the BIOS can no longer have control like during boot - up, simulating the USB device as a floppy disk or IDE hard disk.
Booting from a normal CD - ROM or normal floppy disk, loading the USB driver, and supporting USB hard disk or flash. Then this problem will not exist.

Well the problem is that the DOS based drivers take over the USB controller and ports and the BIOS is unable to use them one the controller is taken over.
There is a reason that you are still trying to access the A: drive. When booting from the A: drive you still have the COMSPEC set to A: drive for loading the COMMAND.COM when it needs to be reloaded. You will need to also make sure you have COMMAND.COM copied to the RAM drive and the COMSPEC updated to point at the new location for COMMAND.COM.




"Advanced USB Boot
The Advanced USB Boot provides enumeration and configuration of an USB CD - ROM, Zip, and Hard Disk drive during POST that enables the ability to boot to DOS from an USB CD - ROM, Zip, or Hard Disk drive that is connected to a system either directly or through a hub(s). Additionally USB CD - ROM, Zip, or Hard Disk drive support enables the use of an USB CD - ROM, Zip, or Hard Disk drive while in a DOS environment"


As USBASPI.SYS merely maps USB devices to an ASPI device, additional driver is needed to map the ASPI mass storage to a DOS drive letter. The famous "Motto Hairu" driver includes this important piece。

Regarding the USB mouse, there is a post saying:
The "USB Mouse Support" in the BIOS is Enabled, the mice works in DOS with the BIOS PS/2 Emulation with a standard DOS mice driver.
If I load the usbaspi.sys with device=usbaspi.sys /V the LED of the optical mice going off, when the usbaspi.sys scan the UHCI controller interface.
If I try now to load the mice driver under DOS the computer hang. When I use device=usbaspi.sys /V /NORST, the LED of the mice going NOT OFF and the mice works fine.
(When I use device=usbaspi.sys /E /V, without scanning the UCHI controllers,
the usbaspi.sys only scanning the EHCI controller and the mice works fine too,
but I can not use UHCI mass storage devices)
Conclusion: Adding /norst can continue to use the USB mouse

USB Legacy Support option, USB Emulation in BIOS setup
In your PhoneixBIOS, you have a USB Legacy Support option which, when enabled, allows your system to recognize the USB hard disk as an internal IDE drive. However, it seems that it cannot deliver USB2.0 speeds at this mode. If you really want to try USBASPI.SYS or ASPIEHCI.SYS, you need to disable the Legacy Support mode as the two conflict. If these two are turned off, the USB mouse, keyboard, and floppy may not be able to be used directly under DOS. Enabling USB Legacy mode will affect the speed of USB.
In case the driver reports an error "Cannot set memory mode I/O" please disable Legacy USB device support in system BIOS setup.

Example: Using USB 2.0 hard disk/flash
If you want to enable only the high - speed USB controller and the mass storage drive, try
device=USBASPI.SYS /e
device=DI1000DD.SYS

> For USB floppy drive, If you have only a single USB port and no internal floppy, use this CONFIG.SYS combination:
device=RAMFD.SYS
device=USBASPI.SYS /w /v /r
Reference articles:
http://www.computing.net/dos/wwwboard/forum/13679.html
http://www.computing.net/dos/wwwboard/forum/13681.html Installing the system from a USB hard disk, first copy the installation files to the partition on the internal hard disk, then install.
http://www.computing.net/dos/wwwboard/forum/13447.html USB 2.0 drivers for DOS by madmaxUSB
http://www.computing.net/dos/wwwboard/forum/13654.html After booting from a USB CD - ROM, load the USB hard disk driver. The boot disk needs to use ramdisk to place the USB driver and COMMAND.COM
http://www.computing.net/dos/wwwboard/forum/14618.html
http://www.computing.net/dos/wwwboard/forum/14818.html Accessing USB storage in DOS
USBASPI.SYS Panasonic(TM) USB to ASPI driver v2.06 and v2.15 Reference Rev 4.1 updated 2 May, 2004 by madmaxUSB
http://newdos.yginfo.net/usbdos.htm
http://www.bootdisk.com/usb.htm
http://www.stefan2000.com/darkehorse/PC/DOS/Drivers/USB/ USB Resources

So it is suggested that Wengier use ctload or device.com to load the USB driver in autoexec.bat, and establish a ramdisk in between, put command.com and the USB driver on the ramdisk, and modify comspec, so that the above problem will not occur. In this way, the application range of this floppy disk will be wider, it can be used in the USB floppy drive, and can also be put into the multi - boot CD and used from the peripheral USB CD - ROM. I have made a modified version of the Wengierdos 7.1 boot floppy disk, in order to put it into my multi - boot CD.

USB driver selection menu for DosY boot disk
http://bbs.wuyou.com/non-cgi/usr/34/34_3055_27.png
Download address of modified DOS 7.1 boot disk. I have been unable to use the image posting and file attachment functions of this forum. It always says the URL is incorrect when uploading files.

http://bbs.wuyou.com/cgi-bin/topic.cgi?forum=34&topic=3055&start=24&show=0

Hey guys, hello everyone. Why can't I find my flash drive in DOS? My motherboard is P4, and then I have a USB floppy drive, and a 128M flash drive with built-in WIN98 boot. Please help me, everyone........

Moderator, I don't know how to use that DUSE. How to use it. I've been working on my notebook hard drive for two days!!! I just can't find that USB hard drive under the desktop computer!! So annoying!! Hurry up and teach me!!