home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: biz.sco.general
- From: fred@genesis.demon.co.uk (Lawrence Kirby)
- Path: sparky!uunet!pipex!demon!genesis.demon.co.uk!fred
- Subject: SCO Compability with OS/2?
- Distribution: world
- References: <68@jptcs.COM>
- Organization: BT
- Lines: 28
- Date: Mon, 28 Dec 1992 19:44:40 +0000
- Message-ID: <725571880snx@genesis.demon.co.uk>
- Sender: usenet@demon.co.uk
-
-
- In article <68@jptcs.COM> wolfman@jptcs.COM writes:
-
- >
- >I currently own a 486DX-50 with 32 MB ram, and 2 200+ HD. I have found
- >out that the os/2 2.0 boot manager does not work with sco unix. And that
- >IBM is not planning to fix this small problem. Does SCO, have a solution
- >for it?
- >
-
- This is certainly a known problem. There may be several problems to solve
- here. In addition to the active partition problem I've seen another explanation
- where the Unix boot program amkes a false assumption as to where the memory
- copy of the boot sector (or something like that) is. OS/2 boot manager puts it
- in a different place but correctly passes the address in a register/segment
- pair.
-
- I was trying out OS/2 at one point and hit this problem. My solution was to
- create patched versions of the /dos file which allowed me to start the
- partitions I wanted. So that, for example, typing bm at the Boot: prompt would
- start up OS/2 Boot Manager. This worked. I'm not using OS/2 now but if you like
- I could fish out the script. It means booting OS/2 is a 2-3 stage process but
- it is much easier than messing around with FDISK.
-
- -----------------------------------------
- Lawrence Kirby | fred@genesis.demon.co.uk
- Wilts, England | 70734.126@compuserve.com
- -----------------------------------------
-