W
Waguih Boctor
Hi,
I have a strange situation that I can't figure out at all. I have a Windows
Me system that was experiencing many problems with the IDE Controller in the
Device Manager showing an exclamation point on bith primary and secondary
IDEs, resulting on the CD-ROM not being visible in Windows Explorer. I ran a
thorough check on the C drive which reported no errors. I tried
re-installing Windows Me on the C Drive with no success (it blew up with
GPFs). In an effort to save the multiGB of data that was on the hard drive,
I added a slave D drive, which because of the IDE problem wasn't even
visible. So I installed Windows Me on the D Drive. This ran successfully and
I could see both drives and CD-ROM/CD-RW. I copied all the data to be
protected to teh D drive and removed it.
I then upgraded to Windows XP. I ran it as a new install to make sure
nothing was left over from the old Windows Me. This ran to completeion
without any problem. I then reconnected the D Drive to restore the saved
files. When rebooting, the system ignores the Windows XP installation on the
C drive and goes straight to the Windows Me on the D drive. The problem is
that the Windows Me installation is now somehow broken and does not complete
the boot. So I either have a failure on booting to the D drive with both
drives connected, or I can boot to the C drive by disconetting the D drive,
but then I cannot retrieve the files. I checked the boot.ini file and its
contents don't suggest anything different than I've seen on any other
Windows XP system. I've listed them here:
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP
Professional" /fastdetect
There are also MSDOS.SYS and WINBOOT.INI files which contain references to
the D drive in the root of the C drive. Editing them to remove these
references does make any difference.
Is there anything else I should be checking? Any help would be greatly
appreciated.
Thanks
I have a strange situation that I can't figure out at all. I have a Windows
Me system that was experiencing many problems with the IDE Controller in the
Device Manager showing an exclamation point on bith primary and secondary
IDEs, resulting on the CD-ROM not being visible in Windows Explorer. I ran a
thorough check on the C drive which reported no errors. I tried
re-installing Windows Me on the C Drive with no success (it blew up with
GPFs). In an effort to save the multiGB of data that was on the hard drive,
I added a slave D drive, which because of the IDE problem wasn't even
visible. So I installed Windows Me on the D Drive. This ran successfully and
I could see both drives and CD-ROM/CD-RW. I copied all the data to be
protected to teh D drive and removed it.
I then upgraded to Windows XP. I ran it as a new install to make sure
nothing was left over from the old Windows Me. This ran to completeion
without any problem. I then reconnected the D Drive to restore the saved
files. When rebooting, the system ignores the Windows XP installation on the
C drive and goes straight to the Windows Me on the D drive. The problem is
that the Windows Me installation is now somehow broken and does not complete
the boot. So I either have a failure on booting to the D drive with both
drives connected, or I can boot to the C drive by disconetting the D drive,
but then I cannot retrieve the files. I checked the boot.ini file and its
contents don't suggest anything different than I've seen on any other
Windows XP system. I've listed them here:
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP
Professional" /fastdetect
There are also MSDOS.SYS and WINBOOT.INI files which contain references to
the D drive in the root of the C drive. Editing them to remove these
references does make any difference.
Is there anything else I should be checking? Any help would be greatly
appreciated.
Thanks