G
geezer
I tried both. The top one repeated the no-boot scenario. Acted just
like without the diskette.
I am about to give up and simply do a clean install. Life shouldn't
be this hard.
G
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
like without the diskette.
I am about to give up and simply do a clean install. Life shouldn't
be this hard.
G
J
John
I missed the original post but I have had a similar experiense four
times. The first three times I had to resore a disk image (drive Image
7) but the last time all I did was restore a copy of the Master Boot
Record with my Western Digital - Data Lifeguard bootable utility disk.
-
____ _
| __\_\_o____/_|
<[___\_\_-----<------------------<no spam please><
| o'
times. The first three times I had to resore a disk image (drive Image
7) but the last time all I did was restore a copy of the Master Boot
Record with my Western Digital - Data Lifeguard bootable utility disk.
Sorry!
Yes it is XP PRO bought and paid for
Yes I used the 'restore'
Yes I use same dir (c:\windows)
Yes It installed in same partition
Yes I have not lost any files or data so far - except that the drive
no longer boots.
Thanks
Geezer
Please place you response above mine!! It is easier for me to read. Thanks!!
Did you have e full retail version of XP? this is not an MFG OEM version?
When you did repair? you stated that you used "restore" option?
When asked, did you install in same directory, create new directory, or
install in a separate partition?
"The re-install gave me the option of restoring - which I chose in order not
to lose
the current contents."
geezer said:On Sat, 3 Dec 2005 10:25:01 -0800, "Dixonian69"
Well I thought I was following yuo until I got to your ver las t sentecne!!
and then:
This post (and the others) are from a different machine entirely.
Put it another way, I have two machines. One (this one) is fine. The
other has all the problems. On that machine, there are two drives.
One drive will not boot. The other drive is just a small one with XP
and nothing else, least of all internet access.
Thanks
G
:
On Sat, 3 Dec 2005 09:02:02 -0800, "Dixonian69"
Your best bet for help is to only make changes made and reply about add'l
problems before making those changes!!!
Everyone is trying to help but only do what is suggested. Do not proceed w/o
psoting new problems and waiting for assisstance before maiking changes!!
Are working with only one computer? OR are yuo putting bad drive in a
different computer?
The bad "C" drive is primary master with jumper set as master and is Only HD
in computer?
You had ntldr and ntdetect.com and a boot.ini file with entries that yuo
provided.
You booted up. You received an error message. You should have stopped and
reposted problem!!
You said at one time bad drive would boot normally but not in safe mode?
Is that still true?
:
On Sat, 3 Dec 2005 14:51:09 -0000, "John Barnett MVP"
Geezer, visit my website http://xphelpandsupport.mvps.org Click the Win XP
Faq button and take a look at question 10 'How do i create an emergency
start up disk for XP' You will need a floppy disk for this. Once you have
created the floppy disk reboot your computer with the floppy in the floppy
drive. If all goes well you should be able to boot to the windows desktop.
If the emergency floppy has booted to the desktop then go to Windows
explorer and click on the floppy drive. The contents of the floppy disk will
become visible (you must have 'show hidden files and folder, etc enabled
otherwise you will not be bale to see the boot.ini file (see question 11 on
my site). Now copy the contents - boot.ini. NTDetect, NTLDR from the floppy
to your C: drive and then reboot again. Hopefully, assuming the floppy
worked, this should repair the problem and you should be able to boot as
normal.
Thanks
You sound very knowledgable and your site is one to keep accessible on
this end.
I tried what it says to do, which really is to grab the 'ntldr' and
ntdetect.com files from the hard drive - then create a new boot.ini
file with content
[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="Windows XP"
I can find no ntldr or ntdetect file. Remember I have my skeleton
drive as c drive and the bad drive as d drive. Both have what look to
be valid XP structures. I looked (searched) on both drives. Yes, I
have view set to see hidden & system files.
However, I did find the 2 files on my XP installation CD. So I used
them to make the so-called emergency startup diskette.
With the bad drive as c drive, and the only drive, I booted up from
the floppy. It told me that a so-called 'hal.dll' file is missing or
corrupt. I copied that file from my skeleton XP drive, and placed it
on both the floppy and in the bad drive's c:\windows\system32 (which
was a 'replace'). I re booted from the floppy again, with only the
bad drive in place (as c drive), and I get the same error.
What now?
Thanks again
Geezer
Up thru yesterday the drive booted okay, but different apps were
failing, so I opted to try a XP re-install (not fresh). I did not
want to lose any of my apps or data. I run with this drive as the
only drive (c).
After I did the re-install, the drive would no longer boot.
I made it a second (slave) drive (d), and mounted a spare small drive
(c) I had from the past that had just a copy of XP on it - nothing
else. I just wanted to see if the drive that wouldn't boot still had
my data and apps. It did. It still does in fact. It was in this
mode that I could not find ntldr or ntdetect.com on either drive - so
I copied them from the installation CD.
All of my trials have been with the failing drive as c drive alone.
This post (and the others) are from a different machine entirely.
Sorry for any confusions I may have caused.
Geezer
-
____ _
| __\_\_o____/_|
<[___\_\_-----<------------------<no spam please><
| o'
G
Guest
Had a problem like this last year, it turned out to be a faulty IDE cable
that was giving the problem.
that was giving the problem.
G
geezer
My drive is a MAXTOR, so the WD Lifeguard disk is of no use. I
downloaded Maxtor's POWERMAX utility, and the quick check program
shows no errors. I see no provision for a MBR re-write.
I have a friend who says he has had a similar problem and it turned
out that when he restored, using Ghost, he failed to check the box
that would render his target bootable. When he redid the Ghost
restore, the target became bootable. I don't have Ghost, nor do I
have a restorable image.
Thanks
Geezer
downloaded Maxtor's POWERMAX utility, and the quick check program
shows no errors. I see no provision for a MBR re-write.
I have a friend who says he has had a similar problem and it turned
out that when he restored, using Ghost, he failed to check the box
that would render his target bootable. When he redid the Ghost
restore, the target became bootable. I don't have Ghost, nor do I
have a restorable image.
Thanks
Geezer
I missed the original post but I have had a similar experiense four
times. The first three times I had to resore a disk image (drive Image
7) but the last time all I did was restore a copy of the Master Boot
Record with my Western Digital - Data Lifeguard bootable utility disk.
Sorry!
Yes it is XP PRO bought and paid for
Yes I used the 'restore'
Yes I use same dir (c:\windows)
Yes It installed in same partition
Yes I have not lost any files or data so far - except that the drive
no longer boots.
Thanks
Geezer
Please place you response above mine!! It is easier for me to read. Thanks!!
Did you have e full retail version of XP? this is not an MFG OEM version?
When you did repair? you stated that you used "restore" option?
When asked, did you install in same directory, create new directory, or
install in a separate partition?
"The re-install gave me the option of restoring - which I chose in order not
to lose
the current contents."
:
On Sat, 3 Dec 2005 10:25:01 -0800, "Dixonian69"
Well I thought I was following yuo until I got to your ver las t sentecne!!
and then:
This post (and the others) are from a different machine entirely.
Put it another way, I have two machines. One (this one) is fine. The
other has all the problems. On that machine, there are two drives.
One drive will not boot. The other drive is just a small one with XP
and nothing else, least of all internet access.
Thanks
G
:
On Sat, 3 Dec 2005 09:02:02 -0800, "Dixonian69"
Your best bet for help is to only make changes made and reply about add'l
problems before making those changes!!!
Everyone is trying to help but only do what is suggested. Do not proceed w/o
psoting new problems and waiting for assisstance before maiking changes!!
Are working with only one computer? OR are yuo putting bad drive in a
different computer?
The bad "C" drive is primary master with jumper set as master and is Only HD
in computer?
You had ntldr and ntdetect.com and a boot.ini file with entries that yuo
provided.
You booted up. You received an error message. You should have stopped and
reposted problem!!
You said at one time bad drive would boot normally but not in safe mode?
Is that still true?
:
On Sat, 3 Dec 2005 14:51:09 -0000, "John Barnett MVP"
Geezer, visit my website http://xphelpandsupport.mvps.org Click the Win XP
Faq button and take a look at question 10 'How do i create an emergency
start up disk for XP' You will need a floppy disk for this. Once you have
created the floppy disk reboot your computer with the floppy in the floppy
drive. If all goes well you should be able to boot to the windows desktop.
If the emergency floppy has booted to the desktop then go to Windows
explorer and click on the floppy drive. The contents of the floppy disk will
become visible (you must have 'show hidden files and folder, etc enabled
otherwise you will not be bale to see the boot.ini file (see question 11 on
my site). Now copy the contents - boot.ini. NTDetect, NTLDR from the floppy
to your C: drive and then reboot again. Hopefully, assuming the floppy
worked, this should repair the problem and you should be able to boot as
normal.
Thanks
You sound very knowledgable and your site is one to keep accessible on
this end.
I tried what it says to do, which really is to grab the 'ntldr' and
ntdetect.com files from the hard drive - then create a new boot.ini
file with content
[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="Windows XP"
I can find no ntldr or ntdetect file. Remember I have my skeleton
drive as c drive and the bad drive as d drive. Both have what look to
be valid XP structures. I looked (searched) on both drives. Yes, I
have view set to see hidden & system files.
However, I did find the 2 files on my XP installation CD. So I used
them to make the so-called emergency startup diskette.
With the bad drive as c drive, and the only drive, I booted up from
the floppy. It told me that a so-called 'hal.dll' file is missing or
corrupt. I copied that file from my skeleton XP drive, and placed it
on both the floppy and in the bad drive's c:\windows\system32 (which
was a 'replace'). I re booted from the floppy again, with only the
bad drive in place (as c drive), and I get the same error.
What now?
Thanks again
Geezer
Up thru yesterday the drive booted okay, but different apps were
failing, so I opted to try a XP re-install (not fresh). I did not
want to lose any of my apps or data. I run with this drive as the
only drive (c).
After I did the re-install, the drive would no longer boot.
I made it a second (slave) drive (d), and mounted a spare small drive
(c) I had from the past that had just a copy of XP on it - nothing
else. I just wanted to see if the drive that wouldn't boot still had
my data and apps. It did. It still does in fact. It was in this
mode that I could not find ntldr or ntdetect.com on either drive - so
I copied them from the installation CD.
All of my trials have been with the failing drive as c drive alone.
This post (and the others) are from a different machine entirely.
Sorry for any confusions I may have caused.
Geezer
-
____ _
| __\_\_o____/_|
<[___\_\_-----<------------------<no spam please><
| o'
J
John
It sounds like a lot of us are having the same problem. I never had
this problem before WinXP (since 1993) so I think it's an XP related
problem because it's happened four times in one year and my drive
checks out OK.
It always happens the same way - I come home and the computer has
rebooted on it's own and it's stuck at a "no boot dis found" (or
something like that)
Now - If we could only figure out what's CAUSING it.
In your case - can you boot from CD and see your files and folders so
that you can back them up to another drive and then Fdisk and start
over? I had to do that the first time this happened to me. I only lost
a few weeks of data but was able to get up and running in a few hours
-
____ _
| __\_\_o____/_|
<[___\_\_-----<------------------<no spam please><
| o'
this problem before WinXP (since 1993) so I think it's an XP related
problem because it's happened four times in one year and my drive
checks out OK.
It always happens the same way - I come home and the computer has
rebooted on it's own and it's stuck at a "no boot dis found" (or
something like that)
Now - If we could only figure out what's CAUSING it.
In your case - can you boot from CD and see your files and folders so
that you can back them up to another drive and then Fdisk and start
over? I had to do that the first time this happened to me. I only lost
a few weeks of data but was able to get up and running in a few hours
My drive is a MAXTOR, so the WD Lifeguard disk is of no use. I
downloaded Maxtor's POWERMAX utility, and the quick check program
shows no errors. I see no provision for a MBR re-write.
I have a friend who says he has had a similar problem and it turned
out that when he restored, using Ghost, he failed to check the box
that would render his target bootable. When he redid the Ghost
restore, the target became bootable. I don't have Ghost, nor do I
have a restorable image.
Thanks
Geezer
I missed the original post but I have had a similar experiense four
times. The first three times I had to resore a disk image (drive Image
7) but the last time all I did was restore a copy of the Master Boot
Record with my Western Digital - Data Lifeguard bootable utility disk.
Sorry!
Yes it is XP PRO bought and paid for
Yes I used the 'restore'
Yes I use same dir (c:\windows)
Yes It installed in same partition
Yes I have not lost any files or data so far - except that the drive
no longer boots.
Thanks
Geezer
On Sat, 3 Dec 2005 11:15:02 -0800, "Dixonian69"
Please place you response above mine!! It is easier for me to read. Thanks!!
Did you have e full retail version of XP? this is not an MFG OEM version?
When you did repair? you stated that you used "restore" option?
When asked, did you install in same directory, create new directory, or
install in a separate partition?
"The re-install gave me the option of restoring - which I chose in order not
to lose
the current contents."
:
On Sat, 3 Dec 2005 10:25:01 -0800, "Dixonian69"
Well I thought I was following yuo until I got to your ver las t sentecne!!
and then:
This post (and the others) are from a different machine entirely.
Put it another way, I have two machines. One (this one) is fine. The
other has all the problems. On that machine, there are two drives.
One drive will not boot. The other drive is just a small one with XP
and nothing else, least of all internet access.
Thanks
G
:
On Sat, 3 Dec 2005 09:02:02 -0800, "Dixonian69"
Your best bet for help is to only make changes made and reply about add'l
problems before making those changes!!!
Everyone is trying to help but only do what is suggested. Do not proceed w/o
psoting new problems and waiting for assisstance before maiking changes!!
Are working with only one computer? OR are yuo putting bad drive in a
different computer?
The bad "C" drive is primary master with jumper set as master and is Only HD
in computer?
You had ntldr and ntdetect.com and a boot.ini file with entries that yuo
provided.
You booted up. You received an error message. You should have stopped and
reposted problem!!
You said at one time bad drive would boot normally but not in safe mode?
Is that still true?
:
On Sat, 3 Dec 2005 14:51:09 -0000, "John Barnett MVP"
Geezer, visit my website http://xphelpandsupport.mvps.org Click the Win XP
Faq button and take a look at question 10 'How do i create an emergency
start up disk for XP' You will need a floppy disk for this. Once you have
created the floppy disk reboot your computer with the floppy in the floppy
drive. If all goes well you should be able to boot to the windows desktop.
If the emergency floppy has booted to the desktop then go to Windows
explorer and click on the floppy drive. The contents of the floppy disk will
become visible (you must have 'show hidden files and folder, etc enabled
otherwise you will not be bale to see the boot.ini file (see question 11 on
my site). Now copy the contents - boot.ini. NTDetect, NTLDR from the floppy
to your C: drive and then reboot again. Hopefully, assuming the floppy
worked, this should repair the problem and you should be able to boot as
normal.
Thanks
You sound very knowledgable and your site is one to keep accessible on
this end.
I tried what it says to do, which really is to grab the 'ntldr' and
ntdetect.com files from the hard drive - then create a new boot.ini
file with content
[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="Windows XP"
I can find no ntldr or ntdetect file. Remember I have my skeleton
drive as c drive and the bad drive as d drive. Both have what look to
be valid XP structures. I looked (searched) on both drives. Yes, I
have view set to see hidden & system files.
However, I did find the 2 files on my XP installation CD. So I used
them to make the so-called emergency startup diskette.
With the bad drive as c drive, and the only drive, I booted up from
the floppy. It told me that a so-called 'hal.dll' file is missing or
corrupt. I copied that file from my skeleton XP drive, and placed it
on both the floppy and in the bad drive's c:\windows\system32 (which
was a 'replace'). I re booted from the floppy again, with only the
bad drive in place (as c drive), and I get the same error.
What now?
Thanks again
Geezer
Up thru yesterday the drive booted okay, but different apps were
failing, so I opted to try a XP re-install (not fresh). I did not
want to lose any of my apps or data. I run with this drive as the
only drive (c).
After I did the re-install, the drive would no longer boot.
I made it a second (slave) drive (d), and mounted a spare small drive
(c) I had from the past that had just a copy of XP on it - nothing
else. I just wanted to see if the drive that wouldn't boot still had
my data and apps. It did. It still does in fact. It was in this
mode that I could not find ntldr or ntdetect.com on either drive - so
I copied them from the installation CD.
All of my trials have been with the failing drive as c drive alone.
This post (and the others) are from a different machine entirely.
Sorry for any confusions I may have caused.
Geezer
-
____ _
| __\_\_o____/_|
<[___\_\_-----<------------------<no spam please><
| o'
G
geezer
John - I tried your emergency diskette with same results - namely the
drive won't boot (into XP anyway). I think the problem is elsewhere.
Maybe deeper within XP's files.
I borrowed a friend's copy of Ghost, made an image of the bad drive,
then did a restore, but WITH Ghost's boot-up option checked. I
thought just maybe this would fix it. The result was still the same.
I guess I am done. Or is it done in?
Thanks for your help. Same for you others.
Geezer
drive won't boot (into XP anyway). I think the problem is elsewhere.
Maybe deeper within XP's files.
I borrowed a friend's copy of Ghost, made an image of the bad drive,
then did a restore, but WITH Ghost's boot-up option checked. I
thought just maybe this would fix it. The result was still the same.
I guess I am done. Or is it done in?
Thanks for your help. Same for you others.
Geezer
It sounds like a lot of us are having the same problem. I never had
this problem before WinXP (since 1993) so I think it's an XP related
problem because it's happened four times in one year and my drive
checks out OK.
It always happens the same way - I come home and the computer has
rebooted on it's own and it's stuck at a "no boot dis found" (or
something like that)
Now - If we could only figure out what's CAUSING it.
In your case - can you boot from CD and see your files and folders so
that you can back them up to another drive and then Fdisk and start
over? I had to do that the first time this happened to me. I only lost
a few weeks of data but was able to get up and running in a few hours
My drive is a MAXTOR, so the WD Lifeguard disk is of no use. I
downloaded Maxtor's POWERMAX utility, and the quick check program
shows no errors. I see no provision for a MBR re-write.
I have a friend who says he has had a similar problem and it turned
out that when he restored, using Ghost, he failed to check the box
that would render his target bootable. When he redid the Ghost
restore, the target became bootable. I don't have Ghost, nor do I
have a restorable image.
Thanks
Geezer
I missed the original post but I have had a similar experiense four
times. The first three times I had to resore a disk image (drive Image
7) but the last time all I did was restore a copy of the Master Boot
Record with my Western Digital - Data Lifeguard bootable utility disk.
Sorry!
Yes it is XP PRO bought and paid for
Yes I used the 'restore'
Yes I use same dir (c:\windows)
Yes It installed in same partition
Yes I have not lost any files or data so far - except that the drive
no longer boots.
Thanks
Geezer
On Sat, 3 Dec 2005 11:15:02 -0800, "Dixonian69"
Please place you response above mine!! It is easier for me to read. Thanks!!
Did you have e full retail version of XP? this is not an MFG OEM version?
When you did repair? you stated that you used "restore" option?
When asked, did you install in same directory, create new directory, or
install in a separate partition?
"The re-install gave me the option of restoring - which I chose in order not
to lose
the current contents."
:
On Sat, 3 Dec 2005 10:25:01 -0800, "Dixonian69"
Well I thought I was following yuo until I got to your ver las t sentecne!!
and then:
This post (and the others) are from a different machine entirely.
Put it another way, I have two machines. One (this one) is fine. The
other has all the problems. On that machine, there are two drives.
One drive will not boot. The other drive is just a small one with XP
and nothing else, least of all internet access.
Thanks
G
:
On Sat, 3 Dec 2005 09:02:02 -0800, "Dixonian69"
Your best bet for help is to only make changes made and reply about add'l
problems before making those changes!!!
Everyone is trying to help but only do what is suggested. Do not proceed w/o
psoting new problems and waiting for assisstance before maiking changes!!
Are working with only one computer? OR are yuo putting bad drive in a
different computer?
The bad "C" drive is primary master with jumper set as master and is Only HD
in computer?
You had ntldr and ntdetect.com and a boot.ini file with entries that yuo
provided.
You booted up. You received an error message. You should have stopped and
reposted problem!!
You said at one time bad drive would boot normally but not in safe mode?
Is that still true?
:
On Sat, 3 Dec 2005 14:51:09 -0000, "John Barnett MVP"
Geezer, visit my website http://xphelpandsupport.mvps.org Click the Win XP
Faq button and take a look at question 10 'How do i create an emergency
start up disk for XP' You will need a floppy disk for this. Once you have
created the floppy disk reboot your computer with the floppy in the floppy
drive. If all goes well you should be able to boot to the windows desktop.
If the emergency floppy has booted to the desktop then go to Windows
explorer and click on the floppy drive. The contents of the floppy disk will
become visible (you must have 'show hidden files and folder, etc enabled
otherwise you will not be bale to see the boot.ini file (see question 11 on
my site). Now copy the contents - boot.ini. NTDetect, NTLDR from the floppy
to your C: drive and then reboot again. Hopefully, assuming the floppy
worked, this should repair the problem and you should be able to boot as
normal.
Thanks
You sound very knowledgable and your site is one to keep accessible on
this end.
I tried what it says to do, which really is to grab the 'ntldr' and
ntdetect.com files from the hard drive - then create a new boot.ini
file with content
[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="Windows XP"
I can find no ntldr or ntdetect file. Remember I have my skeleton
drive as c drive and the bad drive as d drive. Both have what look to
be valid XP structures. I looked (searched) on both drives. Yes, I
have view set to see hidden & system files.
However, I did find the 2 files on my XP installation CD. So I used
them to make the so-called emergency startup diskette.
With the bad drive as c drive, and the only drive, I booted up from
the floppy. It told me that a so-called 'hal.dll' file is missing or
corrupt. I copied that file from my skeleton XP drive, and placed it
on both the floppy and in the bad drive's c:\windows\system32 (which
was a 'replace'). I re booted from the floppy again, with only the
bad drive in place (as c drive), and I get the same error.
What now?
Thanks again
Geezer
Up thru yesterday the drive booted okay, but different apps were
failing, so I opted to try a XP re-install (not fresh). I did not
want to lose any of my apps or data. I run with this drive as the
only drive (c).
After I did the re-install, the drive would no longer boot.
I made it a second (slave) drive (d), and mounted a spare small drive
(c) I had from the past that had just a copy of XP on it - nothing
else. I just wanted to see if the drive that wouldn't boot still had
my data and apps. It did. It still does in fact. It was in this
mode that I could not find ntldr or ntdetect.com on either drive - so
I copied them from the installation CD.
All of my trials have been with the failing drive as c drive alone.
This post (and the others) are from a different machine entirely.
Sorry for any confusions I may have caused.
Geezer
-
____ _
| __\_\_o____/_|
<[___\_\_-----<------------------<no spam please><
| o'
D
David Candy
You haven't listed symptoms anywhere.
A
ANONYMOUS
John,
Don't trust your HD manufacturer. The HDs are more often than not the
culprits. Changing the HD to that of seagates solves most problems.
HDs these days don't last that long. I always thought that HDs are
supposed to last forever but this is no longer the case. What happened
to tht famous phrase "lifetime guaranteed" god knows!
hth
Don't trust your HD manufacturer. The HDs are more often than not the
culprits. Changing the HD to that of seagates solves most problems.
HDs these days don't last that long. I always thought that HDs are
supposed to last forever but this is no longer the case. What happened
to tht famous phrase "lifetime guaranteed" god knows!
hth
It sounds like a lot of us are having the same problem. I never had
this problem before WinXP (since 1993) so I think it's an XP related
problem because it's happened four times in one year and my drive
checks out OK.
It always happens the same way - I come home and the computer has
rebooted on it's own and it's stuck at a "no boot dis found" (or
something like that)
Now - If we could only figure out what's CAUSING it.
In your case - can you boot from CD and see your files and folders so
that you can back them up to another drive and then Fdisk and start
over? I had to do that the first time this happened to me. I only lost
a few weeks of data but was able to get up and running in a few hours
My drive is a MAXTOR, so the WD Lifeguard disk is of no use. I
downloaded Maxtor's POWERMAX utility, and the quick check program
shows no errors. I see no provision for a MBR re-write.
I have a friend who says he has had a similar problem and it turned
out that when he restored, using Ghost, he failed to check the box
that would render his target bootable. When he redid the Ghost
restore, the target became bootable. I don't have Ghost, nor do I
have a restorable image.
Thanks
Geezer
I missed the original post but I have had a similar experiense four
times. The first three times I had to resore a disk image (drive Image
7) but the last time all I did was restore a copy of the Master Boot
Record with my Western Digital - Data Lifeguard bootable utility disk.
Sorry!
Yes it is XP PRO bought and paid for
Yes I used the 'restore'
Yes I use same dir (c:\windows)
Yes It installed in same partition
Yes I have not lost any files or data so far - except that the drive
no longer boots.
Thanks
Geezer
On Sat, 3 Dec 2005 11:15:02 -0800, "Dixonian69"
Please place you response above mine!! It is easier for me to read. Thanks!!
Did you have e full retail version of XP? this is not an MFG OEM version?
When you did repair? you stated that you used "restore" option?
When asked, did you install in same directory, create new directory, or
install in a separate partition?
"The re-install gave me the option of restoring - which I chose in order not
to lose
the current contents."
:
On Sat, 3 Dec 2005 10:25:01 -0800, "Dixonian69"
Well I thought I was following yuo until I got to your ver las t sentecne!!
and then:
This post (and the others) are from a different machine entirely.
Put it another way, I have two machines. One (this one) is fine. The
other has all the problems. On that machine, there are two drives.
One drive will not boot. The other drive is just a small one with XP
and nothing else, least of all internet access.
Thanks
G
:
On Sat, 3 Dec 2005 09:02:02 -0800, "Dixonian69"
Your best bet for help is to only make changes made and reply about add'l
problems before making those changes!!!
Everyone is trying to help but only do what is suggested. Do not proceed w/o
psoting new problems and waiting for assisstance before maiking changes!!
Are working with only one computer? OR are yuo putting bad drive in a
different computer?
The bad "C" drive is primary master with jumper set as master and is Only HD
in computer?
You had ntldr and ntdetect.com and a boot.ini file with entries that yuo
provided.
You booted up. You received an error message. You should have stopped and
reposted problem!!
You said at one time bad drive would boot normally but not in safe mode?
Is that still true?
:
On Sat, 3 Dec 2005 14:51:09 -0000, "John Barnett MVP"
Geezer, visit my website http://xphelpandsupport.mvps.org Click the Win XP
Faq button and take a look at question 10 'How do i create an emergency
start up disk for XP' You will need a floppy disk for this. Once you have
created the floppy disk reboot your computer with the floppy in the floppy
drive. If all goes well you should be able to boot to the windows desktop.
If the emergency floppy has booted to the desktop then go to Windows
explorer and click on the floppy drive. The contents of the floppy disk will
become visible (you must have 'show hidden files and folder, etc enabled
otherwise you will not be bale to see the boot.ini file (see question 11 on
my site). Now copy the contents - boot.ini. NTDetect, NTLDR from the floppy
to your C: drive and then reboot again. Hopefully, assuming the floppy
worked, this should repair the problem and you should be able to boot as
normal.
Thanks
You sound very knowledgable and your site is one to keep accessible on
this end.
I tried what it says to do, which really is to grab the 'ntldr' and
ntdetect.com files from the hard drive - then create a new boot.ini
file with content
[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="Windows XP"
I can find no ntldr or ntdetect file. Remember I have my skeleton
drive as c drive and the bad drive as d drive. Both have what look to
be valid XP structures. I looked (searched) on both drives. Yes, I
have view set to see hidden & system files.
However, I did find the 2 files on my XP installation CD. So I used
them to make the so-called emergency startup diskette.
With the bad drive as c drive, and the only drive, I booted up from
the floppy. It told me that a so-called 'hal.dll' file is missing or
corrupt. I copied that file from my skeleton XP drive, and placed it
on both the floppy and in the bad drive's c:\windows\system32 (which
was a 'replace'). I re booted from the floppy again, with only the
bad drive in place (as c drive), and I get the same error.
What now?
Thanks again
Geezer
Up thru yesterday the drive booted okay, but different apps were
failing, so I opted to try a XP re-install (not fresh). I did not
want to lose any of my apps or data. I run with this drive as the
only drive (c).
After I did the re-install, the drive would no longer boot.
I made it a second (slave) drive (d), and mounted a spare small drive
(c) I had from the past that had just a copy of XP on it - nothing
else. I just wanted to see if the drive that wouldn't boot still had
my data and apps. It did. It still does in fact. It was in this
mode that I could not find ntldr or ntdetect.com on either drive - so
I copied them from the installation CD.
All of my trials have been with the failing drive as c drive alone.
This post (and the others) are from a different machine entirely.
Sorry for any confusions I may have caused.
Geezer
-
____ _
| __\_\_o____/_|
<[___\_\_-----<------------------<no spam please><
| o'
J
John
All that does is images the corupt MBR and re-writes it to the drive
during restore.
Did you read Article ID : 307545 "How to recover from a corrupted
registry that prevents Windows XP from starting"?
____ _
| __\_\_o____/_|
<[___\_\_-----<------------------<No Spam Please><
| o'
during restore.
Did you read Article ID : 307545 "How to recover from a corrupted
registry that prevents Windows XP from starting"?
John - I tried your emergency diskette with same results - namely the
drive won't boot (into XP anyway). I think the problem is elsewhere.
Maybe deeper within XP's files.
I borrowed a friend's copy of Ghost, made an image of the bad drive,
then did a restore, but WITH Ghost's boot-up option checked. I
thought just maybe this would fix it. The result was still the same.
I guess I am done. Or is it done in?
Thanks for your help. Same for you others.
Geezer
It sounds like a lot of us are having the same problem. I never had
this problem before WinXP (since 1993) so I think it's an XP related
problem because it's happened four times in one year and my drive
checks out OK.
It always happens the same way - I come home and the computer has
rebooted on it's own and it's stuck at a "no boot dis found" (or
something like that)
Now - If we could only figure out what's CAUSING it.
In your case - can you boot from CD and see your files and folders so
that you can back them up to another drive and then Fdisk and start
over? I had to do that the first time this happened to me. I only lost
a few weeks of data but was able to get up and running in a few hours
My drive is a MAXTOR, so the WD Lifeguard disk is of no use. I
downloaded Maxtor's POWERMAX utility, and the quick check program
shows no errors. I see no provision for a MBR re-write.
I have a friend who says he has had a similar problem and it turned
out that when he restored, using Ghost, he failed to check the box
that would render his target bootable. When he redid the Ghost
restore, the target became bootable. I don't have Ghost, nor do I
have a restorable image.
Thanks
Geezer
I missed the original post but I have had a similar experiense four
times. The first three times I had to resore a disk image (drive Image
7) but the last time all I did was restore a copy of the Master Boot
Record with my Western Digital - Data Lifeguard bootable utility disk.
Sorry!
Yes it is XP PRO bought and paid for
Yes I used the 'restore'
Yes I use same dir (c:\windows)
Yes It installed in same partition
Yes I have not lost any files or data so far - except that the drive
no longer boots.
Thanks
Geezer
On Sat, 3 Dec 2005 11:15:02 -0800, "Dixonian69"
Please place you response above mine!! It is easier for me to read. Thanks!!
Did you have e full retail version of XP? this is not an MFG OEM version?
When you did repair? you stated that you used "restore" option?
When asked, did you install in same directory, create new directory, or
install in a separate partition?
"The re-install gave me the option of restoring - which I chose in order not
to lose
the current contents."
:
On Sat, 3 Dec 2005 10:25:01 -0800, "Dixonian69"
Well I thought I was following yuo until I got to your ver las t sentecne!!
and then:
This post (and the others) are from a different machine entirely.
Put it another way, I have two machines. One (this one) is fine. The
other has all the problems. On that machine, there are two drives.
One drive will not boot. The other drive is just a small one with XP
and nothing else, least of all internet access.
Thanks
G
:
On Sat, 3 Dec 2005 09:02:02 -0800, "Dixonian69"
Your best bet for help is to only make changes made and reply about add'l
problems before making those changes!!!
Everyone is trying to help but only do what is suggested. Do not proceed w/o
psoting new problems and waiting for assisstance before maiking changes!!
Are working with only one computer? OR are yuo putting bad drive in a
different computer?
The bad "C" drive is primary master with jumper set as master and is Only HD
in computer?
You had ntldr and ntdetect.com and a boot.ini file with entries that yuo
provided.
You booted up. You received an error message. You should have stopped and
reposted problem!!
You said at one time bad drive would boot normally but not in safe mode?
Is that still true?
:
On Sat, 3 Dec 2005 14:51:09 -0000, "John Barnett MVP"
Geezer, visit my website http://xphelpandsupport.mvps.org Click the Win XP
Faq button and take a look at question 10 'How do i create an emergency
start up disk for XP' You will need a floppy disk for this. Once you have
created the floppy disk reboot your computer with the floppy in the floppy
drive. If all goes well you should be able to boot to the windows desktop.
If the emergency floppy has booted to the desktop then go to Windows
explorer and click on the floppy drive. The contents of the floppy disk will
become visible (you must have 'show hidden files and folder, etc enabled
otherwise you will not be bale to see the boot.ini file (see question 11 on
my site). Now copy the contents - boot.ini. NTDetect, NTLDR from the floppy
to your C: drive and then reboot again. Hopefully, assuming the floppy
worked, this should repair the problem and you should be able to boot as
normal.
Thanks
You sound very knowledgable and your site is one to keep accessible on
this end.
I tried what it says to do, which really is to grab the 'ntldr' and
ntdetect.com files from the hard drive - then create a new boot.ini
file with content
[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="Windows XP"
I can find no ntldr or ntdetect file. Remember I have my skeleton
drive as c drive and the bad drive as d drive. Both have what look to
be valid XP structures. I looked (searched) on both drives. Yes, I
have view set to see hidden & system files.
However, I did find the 2 files on my XP installation CD. So I used
them to make the so-called emergency startup diskette.
With the bad drive as c drive, and the only drive, I booted up from
the floppy. It told me that a so-called 'hal.dll' file is missing or
corrupt. I copied that file from my skeleton XP drive, and placed it
on both the floppy and in the bad drive's c:\windows\system32 (which
was a 'replace'). I re booted from the floppy again, with only the
bad drive in place (as c drive), and I get the same error.
What now?
Thanks again
Geezer
Up thru yesterday the drive booted okay, but different apps were
failing, so I opted to try a XP re-install (not fresh). I did not
want to lose any of my apps or data. I run with this drive as the
only drive (c).
After I did the re-install, the drive would no longer boot.
I made it a second (slave) drive (d), and mounted a spare small drive
(c) I had from the past that had just a copy of XP on it - nothing
else. I just wanted to see if the drive that wouldn't boot still had
my data and apps. It did. It still does in fact. It was in this
mode that I could not find ntldr or ntdetect.com on either drive - so
I copied them from the installation CD.
All of my trials have been with the failing drive as c drive alone.
This post (and the others) are from a different machine entirely.
Sorry for any confusions I may have caused.
Geezer
-
____ _
| __\_\_o____/_|
<[___\_\_-----<------------------<no spam please><
| o'
____ _
| __\_\_o____/_|
<[___\_\_-----<------------------<No Spam Please><
| o'