Just been at my mates to do what should have been a reasonably routine job...
A file had corrupted, windows would not boot, and the file needed to be replaced (HAL.DLL was the file).
Now usually, this is a case of getting a working version of the file, putting it on a floppy and then copying it over in the windows recovery console. The hard drive however, denied access to itself.
So, step two - put my own hard drive in as the master, and boot off that, copy the file over to the other hard drive....but it was rejecting my hard drive, which is strange cos I have done it loads of times....just went over in a continuous loop, and would not boot. Why would this happen?
On going back into recovery, i wanted to look at the list of files present on the dodgy hard disk -
And it said it was unable to enumerate the list...which is weird and I have never seen an error of that kind, and made me think the hard drive was shot....
Went to windows installation, and noticed that there was one megabyte in use..out of 50gb....not looking good..I brought it home, put it in my pc and its not even formatted.
This is the second time this has happened, last time the file was config.sys but I was able to replace that easily.
So...opinons? I think his hard disk might well be bust, especially since it's wiped itself for no reason......incidently, how can it just wipe itself?? Its showing up as being RAW formatted!
Next question is - why wouldn't the machine boot with my hard drive in? I checked in the bios, and it was recognised.... Like I say, I have not had this happen before.
All jumpers were correctly set and the correct cables were connected.
Ideas?
TIA
A file had corrupted, windows would not boot, and the file needed to be replaced (HAL.DLL was the file).
Now usually, this is a case of getting a working version of the file, putting it on a floppy and then copying it over in the windows recovery console. The hard drive however, denied access to itself.
So, step two - put my own hard drive in as the master, and boot off that, copy the file over to the other hard drive....but it was rejecting my hard drive, which is strange cos I have done it loads of times....just went over in a continuous loop, and would not boot. Why would this happen?
On going back into recovery, i wanted to look at the list of files present on the dodgy hard disk -
And it said it was unable to enumerate the list...which is weird and I have never seen an error of that kind, and made me think the hard drive was shot....
Went to windows installation, and noticed that there was one megabyte in use..out of 50gb....not looking good..I brought it home, put it in my pc and its not even formatted.
This is the second time this has happened, last time the file was config.sys but I was able to replace that easily.
So...opinons? I think his hard disk might well be bust, especially since it's wiped itself for no reason......incidently, how can it just wipe itself?? Its showing up as being RAW formatted!
Next question is - why wouldn't the machine boot with my hard drive in? I checked in the bios, and it was recognised.... Like I say, I have not had this happen before.
All jumpers were correctly set and the correct cables were connected.
Ideas?
TIA