home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!cs.utexas.edu!qt.cs.utexas.edu!yale.edu!spool.mu.edu!olivea!inews.Intel.COM!inews!hmeyers
- From: hmeyers@mipos2.intel.com (Harris Meyers)
- Newsgroups: comp.os.os2.misc
- Subject: Re: NT won't co-exist with OS/2?
- Message-ID: <HMEYERS.92Dec17102138@mipos2.intel.com>
- Date: 17 Dec 92 18:21:38 GMT
- References: <1992Dec13.230422.9540@ichips.intel.com>
- <1992Dec14.033956.24885@netcom.com> <hatton.724365933@cgl.ucsf.edu>
- <1992Dec16.195913.2231@ultb.isc.rit.edu>
- Sender: news@inews.Intel.COM (USENET News System)
- Organization: ADL Performance Center, INTeL Corporation, Santa Clara, CA
- Lines: 24
- In-Reply-To: djs6015@ultb.isc.rit.edu's message of 16 Dec 92 19:59:13 GMT
- Nntp-Posting-Host: mipos2
-
- There has been a lot of discussion of this problem on Compuserv. With
- the July release of nt, you could wipe out the boot manager, install
- nt, then reinstall the boot manager. unfortunatly, this does not work
- with the October release on nt.
-
- 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.
-
- Microsoft is aware of the problem and there is reason to hope the next
- release of nt will do better.
-
- Obviously patching the partation table is something you should only
- undertake with great care and only after you are sure you know exactly what
- you are doing.
-
-
- Good Luck
- Harris
- Harris_Meyers@ccm.hf.intel.com
-