Howard Kaikow
November 8th, 2009, 08:32 AM
In the past month or so, I've had a number of failed attempts at installing Paragon software, each resulting in a BSOD.
Not sure if this isrelated, but after the failed attept, I am unable to boot to the partitition in which I had attempted to install th ePatagon software.
My system is multiboot wit 4 Windos OS as folllows:
Drive 1: C-D, OS on C
Drive 2: F-H, OS on each of F and G
Drive 3: I=M, OS on J
Drine 4: S-T and Ubuntu, no Windows OS.
I tried to install the Paragon software in G and F.
Afte rtrybg G, I could not boot to G,
The start up got stuck in a loop, likely because drive letters were screwed up.
I fixed G by going back to a clean G, which restored the drive letters.
Last night, I tried installing on F.
Guess what, same problem, drive letters are likely screwed up.
My boot.ini has:
-{ Quote: "[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(2)partition(2)\WINNT
[operating systems]
multi(0)disk(0)rdisk(2)partition(2)\WINNT="J: Microsoft Windows 2000 Professional" /fastdetect
signature(32a7e53f)disk(1)rdisk(0)partition(3)\WINNT="G: Microsoft Windows 2000 Professional" /fastdetect
signature(32a7e53f)disk(1)rdisk(0)partition(2)\WINNT="F: Microsoft Windows 2000 Professional" /fastdetect
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="C: Microsoft Windows 2000 Professional" /fastdetect
C:\grubboot.lnx="Ubuntu Linux"" }-
I've heard that there is a way to fix drive letters either via the Recovery Console, or via a remote registry.
Pointers on how to do this?
In the meantime, I'll try restoring an older version of the F drive.
Not sure if this isrelated, but after the failed attept, I am unable to boot to the partitition in which I had attempted to install th ePatagon software.
My system is multiboot wit 4 Windos OS as folllows:
Drive 1: C-D, OS on C
Drive 2: F-H, OS on each of F and G
Drive 3: I=M, OS on J
Drine 4: S-T and Ubuntu, no Windows OS.
I tried to install the Paragon software in G and F.
Afte rtrybg G, I could not boot to G,
The start up got stuck in a loop, likely because drive letters were screwed up.
I fixed G by going back to a clean G, which restored the drive letters.
Last night, I tried installing on F.
Guess what, same problem, drive letters are likely screwed up.
My boot.ini has:
-{ Quote: "[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(2)partition(2)\WINNT
[operating systems]
multi(0)disk(0)rdisk(2)partition(2)\WINNT="J: Microsoft Windows 2000 Professional" /fastdetect
signature(32a7e53f)disk(1)rdisk(0)partition(3)\WINNT="G: Microsoft Windows 2000 Professional" /fastdetect
signature(32a7e53f)disk(1)rdisk(0)partition(2)\WINNT="F: Microsoft Windows 2000 Professional" /fastdetect
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="C: Microsoft Windows 2000 Professional" /fastdetect
C:\grubboot.lnx="Ubuntu Linux"" }-
I've heard that there is a way to fix drive letters either via the Recovery Console, or via a remote registry.
Pointers on how to do this?
In the meantime, I'll try restoring an older version of the F drive.