Link to home
Start Free TrialLog in
Avatar of csd32129
csd32129Flag for United States of America

asked on

Help recovering a gateway laptop

I have a gateway mx6625 that I to do a full system restore on but I am unable to get the recovery partition to run correctly. My first problem was I was not able to boot from the recovery partition. I was not prompted to press r, F10 or F11 for recovery as I would expect. So I searched this site and found this:
https://www.experts-exchange.com/questions/23560704/Unable-to-boot-to-Recovery-Partition-in-Compaq-Desktop.html?sfQueryTermInfo=1+boot+partit+recoveri+unabl

I did as suggested, making the D: recovery partition active, and was able to boot to windows setup BUT once it attempted to run setup it gave me this error:
Setup cannot find the temporary installation files.
The hard drive on which setup placed temporary files is not currently avalable to windows XP. You may need a manufacturer-supplied device driver, or you may need to run setup again ...

So what am I missing? I know that there are files on the d: drive including the i386 and other windows install files but I not sure where I'm going wrong.
SOLUTION
Avatar of noxcho
noxcho
Flag of Germany image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of csd32129

ASKER

There is a recovery partition with what looks the file that are needed by windows to do a restore, but I have not been able to get it ask if I would like to run the recovery. As most PC's I've seen prompt during boot to press "r" or "F10, F11". It does not do this. What make it do this, MBR?
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I made the recovery partition active by using disk management in windows. It did boot to the recovery partition but it was unable to complete windows setup. It seemed that something was missing.
So it seems the problem may have been that the recovery files may have been damaged.
My work around for this was to reinstall from another windows disk I had and and download the drivers. Not what I really wanted to do but the job had to get done.
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial