CD-ROM drive unsupported or remote on network
Last Updated: 8 July, 1997
No CD-ROM device detected.
Machines with an unsupported CD-ROM drive, for example a really new or
a very old one. Or you have a CD-ROM on the network, but not on the machine
you wish to install OS/2 on.
No driver for CD-ROM device or no CD-ROM drive available in machine connected
to the network.
First make sure your CD-ROM drive is really unsupported. For instance,
there are drivers for
CD-ROM drives and even for oddball drives like the
Storage Dolphin AT-800.
If all else fails, follow these steps to trick OS/2 into installing
from the harddisk.
Boot DOS in a configuration where you can access the CD-ROM drive. Let's
G: is the drive letter of your (networked) CD-ROM.
Change this in the following to reflect your situation.
Locate a partition with ~45MB of free space. We'll assume this is drive
D:. This should not be the partition to which you
plan to install OS/2 Warp, unless there will be enough space left to complete
From the root of drive D:
XCOPY G:\os2image os2image /s
COPY G:\os2se20.src D:\
Insert Diskette 1.
Modify the SET CDINST line to read
If there is none (Warp 4?), don't change anything at all.
Save the file. Insert Installation Diskette #0. Reboot.
When the OS/2 install program boots, it looks on every drive letter it
can detect for the file OS2SE20.SRC in the root directory. See if the install
routine now detects the installation files in \OS2IMAGE (without having
to have the CD in the CD-ROM). If not, you could try pressing F3 at the
installation to get the Command Line prompt. Then, execute SYSINST2.EXE
(located on A: or in one of the subdirectories in \OS2IMAGE).
If the installation routine happily continues, go on and Warp your machine!
This was a Tip of the Month, July '95 of the Grassroots
Gazette, by Kris Kwilas - IBM BESTeam
firstname.lastname@example.org. (Great tip, Kris!)
Jacco de Leeuw