On Thu, 24 Aug 2000, [ISO-8859-1] Vesa J��skel�inen wrote:
> On Thu, 24 Aug 2000, Niels-Ole Gram wrote:
>
> > I've just installed Mandrake v7.1 and everything went well - except
> > for one thing; when I load Windows NT v4.0 SP5 my d-drive is
> > missing! Before I installed Mandrake I had a c-drive, d-drive and
> > f-drive (my e-drive was the cd-rom). Now after installing Mandrake my
> > c-drive is intact, but my previously f-drive is now my d-drive, and my
> > previously d-drive is not accessible any more from NT.
>
> I do not know how NT handles driveletter mapping but probably it is
> sameway as OS/2 WSeB does it. Before GRUB installation I had OS/2 boot
> manager to boot OS/2, linux and windows. But after GRUB installation I
> didn't see WSeB in OS/2 boot manager anymore. So can't boot OS/2 now
> anymore. I'll think at begining of driver there is stored LVM (in
> OS/2) information which maps different drives to different places.
> And on GRUB installation this information probably gets destroyed.
> In general this isn't GRUBs fault but OS itself since data wasn't in
> secure place. Maybe GRUB could be installed in this case to partition not
> to MBR... and set that partition active...
>
Yeah. Microsoft created rules just to break them months later. NT stores
some magic information in MBR about letters mapping. You can restore
mapping with "Disk Administrator" (it's in Administrative utilities): this
beast works in both Windows NT and Windows 2000 (even if it's not included
in Windows2000).
In LiLo CHANGES file:
-- cut --
- now only 0x1b8 bytes of the boot sector are overwritten, which preserves
some magic numbers NT stores there
-- cut --
