msls31.dll and others

  • Thread starter Thread starter Dirk Bruere at NeoPax
  • Start date Start date
D

Dirk Bruere at NeoPax

Windows bombed, couldn't find the old disc so got a new OEM copy of XP
to install. However, some 8 .dll files could not be copied when updating
the OS. One of them was the above. Seems that XP needs it to do its
activation stuff.

Looked in system32 and there was an old version not overwritten. Could
not delete, rename, overwrite it manually from Explorer. XP things it is
a damaged file since I get a data error message involving a failed CRC.
Same with the others.

However good versions of these files seems to reside in system32/dllcache

How can I fix this problem?
The other uncopied files are:

capesnpn.dll
cards.dll
cbidf2k.sys
ccdecode.inf
msjint40.dll
msjter40.dll
mslwvtts.dll

Dirk
 
Dirk said:
Windows bombed, couldn't find the old disc so got a new OEM copy of XP
to install. However, some 8 .dll files could not be copied when
updating the OS. One of them was the above. Seems that XP needs it to
do its activation stuff.

Looked in system32 and there was an old version not overwritten. Could
not delete, rename, overwrite it manually from Explorer. XP things it
is a damaged file since I get a data error message involving a failed
CRC. Same with the others.

However good versions of these files seems to reside in
system32/dllcache

How can I fix this problem?
The other uncopied files are:

capesnpn.dll
cards.dll
cbidf2k.sys
ccdecode.inf
msjint40.dll
msjter40.dll
mslwvtts.dll

Dirk

Generally failure to copy files during an install is caused by faulty
hardware - bad cd, bad cd drive, bad RAM, bad hard drive. Since
"Windows bombed" perhaps that's why.

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

Testing hardware failures often involves swapping out suspected parts
with known-good parts. If you can't do the testing yourself and/or are
uncomfortable opening your computer, take the machine to a professional
computer repair shop (not your local equivalent of BigStoreUSA).

Malke
 
Malke said:
Dirk Bruere at NeoPax wrote:




Generally failure to copy files during an install is caused by faulty
hardware - bad cd, bad cd drive, bad RAM, bad hard drive. Since
"Windows bombed" perhaps that's why.

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

Testing hardware failures often involves swapping out suspected parts
with known-good parts. If you can't do the testing yourself and/or are
uncomfortable opening your computer, take the machine to a professional
computer repair shop (not your local equivalent of BigStoreUSA).

There aren't exactly many parts to swap out and even that may not tell
me anything if it was (say) a power glitch. By the time I've swapped out
everything and replaced it with known good stuff I'd have bought a new
computer. Any s/w I can use to scan the HDD for errors?

Dirk
 
Dirk said:
There aren't exactly many parts to swap out and even that may not tell
me anything if it was (say) a power glitch. By the time I've swapped
out everything and replaced it with known good stuff I'd have bought a
new computer. Any s/w I can use to scan the HDD for errors?

Dirk

If you go to the link I gave you, you will see the suggested software
(all free) and methods.

Malke
 
Malke said:
Dirk Bruere at NeoPax wrote:




If you go to the link I gave you, you will see the suggested software
(all free) and methods.

I did a check disc and found a load of bad sectors etc.
Not sure if its the HDD, motherboard or even cable.
I've replaced the cable, and I'll replace the HDD later.
Could the MB be at fault?

Dirk
 
Dirk said:
I did a check disc and found a load of bad sectors etc.
Not sure if its the HDD, motherboard or even cable.
I've replaced the cable, and I'll replace the HDD later.
Could the MB be at fault?

As I already told you, go to the hard drive mftr.'s website and download
the drive diagnostic utility. You will make either a bootable cd or
floppy with the file you download.

Boot with the media you created (change the boot order in the BIOS if
necessary) and do a thorough test. If the hard drive shows any physical
errors, replace it.

The motherboard would not normally produce bad sectors on a hard drive.
When troubleshooting, you must do everything methodically or your work
will be scattershot and useless.

If you do not feel comfortable working with hardware and/or you have
difficulty in troubleshooting, take the machine to a local professional
(not your equivalent of BigStoreUSA).

Malke
 
Back
Top