🚀 go-pugleaf

>     250MB Primary - DOS/Windows.
>       2MB Boot Manager
>     120MB Logical HPFS (for installing Warp Connect)
>     700MB Free space
>     120MB Logical (to be formatted as HPFS after installation)
> 
> After the installation program copies whatever it requires from the
> CD ROM, it tells me to press enter to restart the machine. Instead of being
> rebooted into OS/2 to complete the install, the following happens:
> 
>     - The message "Error reading Disk 2. Press any key" appears (I only
>       have one disk).

Odd.

>     - After I press a key, the boot manager shows a menu. Only the DOS/Win
>       partition appears on the menu.
> --------------------------------------------------------------------
> 
> Since then I've discovered that my 1.08 GB disk has 4896 cylinders and
> that Boot Manager must be loaded in the first 1024.

If your BIOS cannot remap the drive (which it appears it cannot) all of your OS's 
must reside in partitions which begin and end in the first 1024 cylinders (or the 
first ~200 megabytes of your drive (wait a minute, 4896 cylinders can't be right 
if you've got a 250 meg dos primary - check this).  This because the BIOS 
contains a 10 bit pointer which can address 2^10, or 1024 cylinders.  BootMan 
uses the BIOS.  If your OS resides outside this range, you can't get at its boot 
sector.  With newer geometry remapping BIOS's, this problem becomes moot, since 
the drive mapping scheme is altered, and a > 1024 cylinder drive can be made to 
appear as a < 1024 cylinder drive at the BIOS level.

> Some questions:
> 
> + Do I have to put OS/2 in a partition which is *fully* within the first
> 1024 cylinders? If yes, I assume that this means that it must be a primary
> partition.

Yes, you do - if you're not using BIOS remapping (i.e. LBA).  If you remap, you 
can place an OS outside the first 1024 physical drive cylinders (not to be 
confused the number of cylinders emulated by the BIOS).  On-Track will not help 
you here - it only helps DOS access above 1024 cyls.

OS/2 may reside on an extended partition which meets the above 1024 constraint.

> + What are the implications if I want to run Windows programs on the
> first partition? (my OS/2 version is without Windows)?

I'm not sure what you mean here.  If you already own Windows 3.x, you should be 
able to run it just fine in both seamless and fullscreen sessions.  In fact, the 
OS/2 install should detect it, and add it's icons to a folder in your desktop.

But you can't run windows if both it and OS/2 are on separate primaries.  You 
can only map one primary at a time (unless you're very devious).  
 
> + I had hoped to have several operating systems running on my PC but the
> cylinder problem could make this difficult. Would System Commander overcome
> the difficulties?

Probably not.  System Commander overcomes a few limitations with BootMan, but 
still uses the BIOS to address the drive.
 
> + Can the OS/2 version of Partition Magic function in a DOS environment? i.e.
> can I use it to further shrink my first partition before I install OS/2.


That's a good question.  PM-DOS can manipulate drives that fall in the 
aforementioned 1024 cylinder limit.  If you can't get at the whole drive, then 
how can you partion it correctly?


I think your best bet is to:

I. back up your system

II.  if your bios is not capable of remapping you drive:

(b) load OS/2 off of your installation diskettes, "exit to command prompt"

(c) run partion magic (OS/2 does not use the bios to address the drive, so you 
should see the whole thing)

i.  Create a 1 meg primary partition for BootMan at the front of the drive.

ii.  Shrink your existing primary C: to a bare minimum; you've only got ~200 megs 
of bootable space to play with (PM should help you figure out exactly where your 
boot cut-off is), don't waste it with windows crap.  A full DOS install shouldn't 
need over 10 megs.  Since XDFCopy uses drive C:, make sure you leave a couple 
megs free (if you've got PC-Dos 7).

iii.  Create a second primary partion for OS2, in the remaining space under your 
determined "boot cap".  Red connect will probably fit in 100 megs.  Format it in 
HPFS.

iv.  Create an extended partion to encompass the remainder of the drive.  Create 
a Drive D: and format it in FAT.  Use this one for all of your DOS/Windows 
applications.  Create a Drive E: and format it in HPFS.  This will contain your 
OS/2 apps and whatever else you won't mind hiding from DOS.

(d)  Quit PM and run OS/2's FDISK.  Install BM on the first 1 meg partition.  Set 
the large primary partition as Active.

(e)  Quit FDISK and run the OS/2 install, sticking it on your large HPFS C:.

(f)  Reload Windows on your new D: FAT drive.  I assume you were already running 
On-Track disk manager under DOS, so you shouldn't have a problem accessing this 
drive.

III.  if your bios can remap your drive, forget the above, figure out how to 
remap the drive under 1024, and re-set-up your system however you please.


I've just given you a hack solution to your problem, and have undoubtedly left 
out many finer details.  In the interests of time though, you should have enough 
to get started.