INTRODUCTION -> WINDOWS 2000
Since Release Candidate 3 Windows 2000 destroys the OS/2 Bootmanager everytime it is booted, the use of Windows 2000 together with OS/2 is in general no good idea.
One solution could be to toggle with an diskeditor (e.g. from the Gammatech Utilities) a byte in the first sector of the Bootmanager Partition OFFSET 0Eh (decimal 14), from 0x01 to 0x2d. This reserves an greater amount of reserved Sectors, so Windows 2000 changes only unassigned Sectors not needed by the Bootmanager. DFSee 3.32 available at http://www.fsys.demon.nl can do this for your without the need to poke around with an diskeditor.
Or call the Microsoft Support and ask for the Hotfix Q265003, it will be included in Servicepak 2 for Windows 2000.
Or use this tip from - Daniela Engert from VOICE 8/2000
"Maybe you are interested in patching FP13 FDISK so that it writes out a modified BootManager which will not be affected by Win2K":
For FP13 FDISK use this script file (the Bootmanager sector image is at file offset 13404h)
--- FDISK.PAT ------
FILE FDISK.COM
VER 13411 04
CHA 13411 00
VER 13412 01
CHA 13412 20
VER 13414 02
CHA 13414 00
VER 13416 02
CHA 13416 00
VER 1341A 0C
CHA 1341A 00
VER 1343A 46415420202020
CHA 1343A 424F4F544D4752
--- FDISK.PAT ------
and run "PATCH FDISK.PAT /A" from the x:\OS2 directory. Then run FDISK and recreate the Bootmanager. Other FDISK versions may
have the sector image at another offset.