S
Steve Evans
I have been running 2k on a hard drive with 2 primary partitions (c:
windows, d: data) for some time now, and recently decided it was time
for a fresh install.
i Went through the usual process of booting from the win2k cd,
deleting and fat32 formatting the existing windows partition and then
installing windows. The install process didn't give me any options as
to where I wanted the boot files and proceeded as normal.
After installation and about 2 hours of updates/program installs etc,
I discovered that it had put the boot files on d: and made that drive
active but the \winnt was on c: as normal.
After much faffing with partition magic and boot files, and making the
system completely unbootable, I gave up and restored a drive image of
the system - phew!
I have never seen this problem when installing on another system,
however, that system has 1 primary and 1 extended partition. Could it
be that win2k gets confused when there are 2 primary partitions
involved?
Cheers
windows, d: data) for some time now, and recently decided it was time
for a fresh install.
i Went through the usual process of booting from the win2k cd,
deleting and fat32 formatting the existing windows partition and then
installing windows. The install process didn't give me any options as
to where I wanted the boot files and proceeded as normal.
After installation and about 2 hours of updates/program installs etc,
I discovered that it had put the boot files on d: and made that drive
active but the \winnt was on c: as normal.
After much faffing with partition magic and boot files, and making the
system completely unbootable, I gave up and restored a drive image of
the system - phew!
I have never seen this problem when installing on another system,
however, that system has 1 primary and 1 extended partition. Could it
be that win2k gets confused when there are 2 primary partitions
involved?
Cheers