New SATA2 drive

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Got XP home with Office 2003 pro on an Athlone 64 system with 1 gig of ram,
200 gig c: drive and 30 gig backup. Installed new SATA2 Western Digital HD.
Used WD's software to copy all of IDE c: drive to new SATA drive. Tried 4 or
5 times and each time there are at least 5 or more file not copied as well as
15 or more files copied with mistakes. Win xp seems ok but Office 2003 has
many errors altough Word and Excel seem to run ok in spite of error message
when you start them up.(I get a message saying to run setup again and select
repair) When I try this I get refered to a file called 512263.mainsp2op.msp
that is needed but does not exist anywhere in my system or on the original
install discs. What to do?
 
I've never used the disk copy software, but are you sure you're in the proper
mode when using the software, is it supposed to be in safe mode first?
I've seen file not copied errors when making backups while windows is still
running some files not copied etc..because they were in use at the time.
 
I'll try that. By the way there were 5802 errors in 183 files and 5 files
were not copied. Hum....
 
RogerRamjet said:
I'll try that. By the way there were 5802 errors in 183 files and 5
files were not copied. Hum....
Click to expand...

Errors like you describe are usually caused by faulty hardware:

1. Installation CD (burned copy - bad burn; retail disk - scratches,
etc.)
2. Optical drive
3. Bad hard drive
4. Bad RAM
5. Other

Even though the hard drive is new, test it with the mftr.'s diagnostic
utility. It is completely possible for a drive to fail out of the box.

http://www.elephantboycomputers.com/page2.html#Hardware_Troubleshooting

Malke
 
Defective on arrival isn't that uncommon - A new Dell Dimension
C2D came in Tuesday with a "Dead" DVD-RW unit. Could have
walked to Round Rock for a replacement for the time it took to
get pas the "Battery Replacement" queue and reach Tech Support.
 
Good news!! Found my own solution.
The drive is OK! The tech where I bought the hardware told me Win XP has a
lot of built in anti hacking code that CAN cause this sort of erratic
behaviour. The Win XP setup was intact. Just the Office 2003 install that was
slightly damaged although it was still running.
How I fixed it:
Hunted down the missing *.msp files with the search engine on the
Microsoft.com site. Downloaded the update files(KBXXXXXXX) containing these
files(the *.msp files) Extracted the msp file with winrar. I beleive winzip
works too. Copied the msp file to the proper directory requested by the
setup.exe from the Office 2003 install disc. After replacing 5 missing files:
EXCELff.msp, OUTLOOKFF.MSP, OLKINTLff.MSP, OUTLFLTR.msp, OTKLOADR.msp, ...the
reinstall, repair options finally appeared and I successfully repaired my
Office install. Be patient. Some of the msp file come in many flavours. You
have to find the one for your version of Office, whether it be 2000, 2003, or
XP. You also have to find the correct revision level for it such as
OUTFLTR.msp which is a junk email filter. Trial and error!! Oh yah!! Good
luck.
Good help is available on this site as well as at www.petri.co.il
RogerRamjet out!
 
Well...not so quick. I since found that some of my other programs are in need
of repair-reinstall. This MAY include Win XP although I am not sure. WD's HD
test says all my drives are OK. Is there a way to check a Win XP install to
know if is intact?
I'm going to get a second SATA drive and set it up in a raid 1 array as and
external drive, but I want to clear up these program glitches first.
Thanks again,

Roger and out
 
Back
Top