Valid image repair install problem?

[Gareth]

Could someone provide advice with the following problem?

I've created what I believe to be a working slipstreamed XP SP2 install CD
using my original SP1 install disk and SP2.

I've followed the easily available instructions for carrying out a repair
install: booting the CD, *not* selecting recovery console but selecting a
repair install over the existing installation.

The process starts okay but when the install files are being copied from CD
I get an error message saying something like:

"the application or DLL c\windows\blue_ss.dll is not a valid windows image".
The error appears in relation to several other dll files before the install
crashes.

I am then forced to restore to an earlier restore point (which doesn't fix
the system problems that prompted the need for a repair install in the first
place).

Would a full reinstall using the slipstreamed CD be the only solution?

Gareth.

 

[Kerry Brown]

It sounds like you may have a bad burn on the slipstreamed CD or something
went wrong in the slipstreaming process. Try creating the slipstreamed CD
again. If it still doesn't work then test the RAM in your computer.

www.memtest.org

You may have a hardware problem. Testing the RAM is a good starting point
for troubleshooting. Why are doing a repair install? Knowing this may help
us pinpoint your problems.

 

[Gareth]

It sounds like you may have a bad burn on the slipstreamed CD or something
went wrong in the slipstreaming process. Try creating the slipstreamed CD
again. If it still doesn't work then test the RAM in your computer.

www.memtest.org

You may have a hardware problem. Testing the RAM is a good starting point
for troubleshooting. Why are doing a repair install? Knowing this may help
us pinpoint your problems.

Thank you for your help Kerry. I swapped/took out various RAM cards and the
problem was fixed - it seems that it was caused by either faulty or
incompatible memory.

Thanks again!

Gareth.

 

[Kerry Brown]

Thank you for your help Kerry. I swapped/took out various RAM cards
and the problem was fixed - it seems that it was caused by either
faulty or incompatible memory.

Thanks again!

Gareth.

You're welcome.