home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.os2.misc
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!eff!ssd.intel.com!ichips!pdxgp1!jburns
- From: jburns@pdxgp1 (John Justin Burns Jr.)
- Subject: Re: NT won't co-exist with OS/2?
- Message-ID: <1992Dec17.205703.16772@ichips.intel.com>
- Sender: jburns@ichips.intel.com
- Organization: Intel Corp., Hillsboro, Oregon
- References: <hatton.724365933@cgl.ucsf.edu> <1992Dec16.195913.2231@ultb.isc.rit.edu> <HMEYERS.92Dec17102138@mipos2.intel.com>
- Date: Thu, 17 Dec 1992 20:57:03 GMT
- Lines: 16
-
- In article <HMEYERS.92Dec17102138@mipos2.intel.com> hmeyers@mipos2.intel.com (Harris Meyers) writes:
- >
- >When OS/2's FDISK creates a boot manager partation it gives it a type
- >of hex 0a in the partation table. It turns out the the October
- >release of nt will not boot in this case. If you patch this byte to
- >00 then everything works fine EXCEPT OS/2's FDISK gets confused. If
- >the type byte is 0a you can run OS/2, OS/2's FDISK and DOS, but not
- >nt. If the type byte is 0, you can run OS/2, DOS, and nt, but not
- >OS/2's FDISK.
- >
-
- So what you are saying is that not only will NT not install with the
- BM present, it won't even run?
-
- John
-
-