This is a very old device, and the optical drive can barely read discs anymore. When I connect a USB optical drive, the system fails to recognize it.
I wanted to modify the optical drive driver on the installation disc, but USB drives turned out to be more complicated than I thought.
In config.sys, after running `device=usbaspi.sys`, the files on the boot disk become unreadable. As a result, subsequent commands like `device=usbcd.sys /d:usbcd001` fail to execute, and even `command.com` cannot reload.
A workaround I found is to first load `ramdrive.sys`, then copy all files to the virtual drive in `autoexec.bat`, and finally use `devload` to load `usbaspi.sys` and `usbcd.sys`.
However, the drive letter for the ramdrive cannot be specified; it automatically follows the existing partitions. For example, if there are already drives C and D, the ramdrive becomes E. If the hard drive is unpartitioned and the boot disk is drive A, the virtual drive becomes drive C.
The problem is that the installation program on this disc checks for the existence of drive C. If drive C does not exist, it automatically creates two partitions and proceeds with the installation. If drive C exists, it installs directly to drive C. This causes the ramdrive to interfere with the drive letter assignment, leading to issues.
I wonder if any experts here have a solution to this problem. Either avoiding the use of ramdrive or specifying the ramdrive as drive B would work.
I wanted to modify the optical drive driver on the installation disc, but USB drives turned out to be more complicated than I thought.
In config.sys, after running `device=usbaspi.sys`, the files on the boot disk become unreadable. As a result, subsequent commands like `device=usbcd.sys /d:usbcd001` fail to execute, and even `command.com` cannot reload.
A workaround I found is to first load `ramdrive.sys`, then copy all files to the virtual drive in `autoexec.bat`, and finally use `devload` to load `usbaspi.sys` and `usbcd.sys`.
However, the drive letter for the ramdrive cannot be specified; it automatically follows the existing partitions. For example, if there are already drives C and D, the ramdrive becomes E. If the hard drive is unpartitioned and the boot disk is drive A, the virtual drive becomes drive C.
The problem is that the installation program on this disc checks for the existence of drive C. If drive C does not exist, it automatically creates two partitions and proceeds with the installation. If drive C exists, it installs directly to drive C. This causes the ramdrive to interfere with the drive letter assignment, leading to issues.
I wonder if any experts here have a solution to this problem. Either avoiding the use of ramdrive or specifying the ramdrive as drive B would work.