I
Ian R
Hi
My brother bought a new (larger/faster) HDD to replace his current Master on
primary IDE - so the idea was to clone the partitions from the old drive to
the new. Did that and then replaced the old HDD with the new i.e. as Master
on primary IDE channel.
(Note XP itself wasnt cloned as this is installed on the slave drive on the
primary IDE channel)
All seemed to go well then got the error message...
"missing or corrupted hal.dll"
Hmm how could that happen we didnt touch the slave drive?
Just for the hell of it we put back the original HDD back as master and we
got the same error!
Again why would that happen as nothing changed on the original drive or the
slave?
After reading up on various articles via Google we attempted to extract
hal.dl_ from the CD to the system32 folder via recovery console - but it
didnt work.
So decided to do a repair install.
But the hurdle we came across next was that the the repair option (not to be
confused with recovery console) couldnt see the original installation!!
Does anyone know why the recovery console can see J:\WINDOWS but the repair
install cant???
Very frustrating.
What should have been a fairly straighforward task is now causing a big
headache.
Thanks for any info and advice.
Ian
My brother bought a new (larger/faster) HDD to replace his current Master on
primary IDE - so the idea was to clone the partitions from the old drive to
the new. Did that and then replaced the old HDD with the new i.e. as Master
on primary IDE channel.
(Note XP itself wasnt cloned as this is installed on the slave drive on the
primary IDE channel)
All seemed to go well then got the error message...
"missing or corrupted hal.dll"
Hmm how could that happen we didnt touch the slave drive?
Just for the hell of it we put back the original HDD back as master and we
got the same error!
Again why would that happen as nothing changed on the original drive or the
slave?
After reading up on various articles via Google we attempted to extract
hal.dl_ from the CD to the system32 folder via recovery console - but it
didnt work.
So decided to do a repair install.
But the hurdle we came across next was that the the repair option (not to be
confused with recovery console) couldnt see the original installation!!
Does anyone know why the recovery console can see J:\WINDOWS but the repair
install cant???
Very frustrating.
What should have been a fairly straighforward task is now causing a big
headache.
Thanks for any info and advice.
Ian