On 10/14/1999 in OS/2 (F) Jonathan De Boyne Pollard wrote to John
Hentsch:

JD> If it's the amount of free space, and not the overall size of the
JD> volume, that the installation program doesn't like, then simply
JD> eat up enough free space by creating large dummy files to take it
JD> below the 2GiB line.


Hi Jonathan, I recently installed SYSTEM COMMANDER boot manager
software that should solve my problem.  I don't know if your are
familiar with it, but it has some additional feature over IBM's OS/2
boot manager.

I had a tough time getting OS/2 Warp Connect installed though. It was
to be the third OS on the hard drive and I couldn't get past the install
program. Apparently, it saw through SYSTEM COMMANDER'S hidden partition
trickery and didn't want to continue. The OS/2 Warp Connect install
reported it didn't have enough space to install the system.

I eventually, installed OS/2 Connect on another hard drive, without
SYSTEM COMMANDER, and then had PARTITION MAGIC copy it over to the
SYSTEM COMMANDER partition. I had to run SYSINSTX and then was able to
get it to boot, OS/2 seeing itself on C: drive even through it was
on the third partition on the drive.


jh -
--- Platinum Xpress/Wildcat! v1.3e
2401/0