Chris W <(E-Mail Removed)> wrote in news:(E-Mail Removed):
> I had my system set up with a triple boot. With the following layout.
> SCSI disk 0 partition 1: win2k fat32 drive letter C
> SCSI disk 1 partition 1-3 linux linux file systems
> SCSI disk 1 partition 4: win2k NTFS Drive letter M
>
> SCSI disk was dieing so I boot into win2k on scsi disk 0 and used true
> image to make an image of partition 4 of scsi disk 1 and saved it on
an
> ide disk I had in there. I then finaly got fixmbr to get rid of the
> grub boot loader that wouldn't work because it's config data was on
the
> dead disk. After replacing scsi 1 with a new scsi disk I couldn't
> restore the partition image I made with true image because there were
> errors. I could however mount that image file as a drive letter and
> coppied most of the files over the the new scsi disk 1 that I formated
> with NTFS (the files that were corrupted wern't important). I changed
> the boot.ini to reflect the changes in the partition from 4 to 1 on
the
> new scsi disk. I rebooted, picked the option to boot to the drive I
> just replaced and it worked. . . well sortof. The drive letter for
SCSI
> disk 1 partition 1 is now K not M so some stuff doesn't work right. I
> couldn't even get the administrator tools to work to try and change
the
> drive letter. So then I thought, what if I share that drive and then
> map it as a drive and use M for the drive letter. Well that made
> everything work so I ran the admin tools and was about to change the
> drive letter. But now I am stuck for 2 reasons, one I can't change it
> to M because that letter is maped to a "network" drive, and it just
> won't let you change the drive letter of the system drive. So anyone
> have any clever ideas?
>
http://support.microsoft.com/default...b;en-us;223188
Leonard Severt
Windows 2000 Server Setup Team
--
This posting is provided "AS IS" with no warranties, and confers no
rights.