from Cristian Burneci:
> So it was only a DOS/Windows FDISK limitation then?
(referring to only one primary partition on one hard disk being accessible at
one time)
I checked again the manual.user's guide for OS/2 Warp 3, only one partition on
one hard drive could be visible at one time. In the case of one hard drive, all
these partitions would share drive letter C: OS/2 Boot Manager could be one
primary partition, but that was not a readable file system, so that would not be
accessible after booting into the desired OS. So if straight DOS (DR, PC, MS,
for instance) were in one primary partition, and OS/2 Warp in another, OS/2
could not read the DOS partition. Normally OS/2 can read/write FAT16 (DOS) and
HPFS.
Now, in response to Tony Butka, if I try to boot either the old or updated
OS/2 Warp 4 installation diskettes, I get TRAP 000d on the second of three
diskettes (this is disk 1, counting 0, 1, 2). Maybe my computer has become
allergic? I was able to boot Linux Slackware 7.1 N_5380_S kernel and COLOR.GZ
root disk image, using LOADLIN, and use fdisk to reconstruct the partition table
of my first hard disk, and then I successfully mounted the DOS and old Linux
partitions, but second hard disk, with three logical partitions (FAT, HPFS,
Linux native) remains inaccessible.
