• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Lite-On 48x CD ROM Possible Errors?

aeonrevolution

aeonrevolution

2[H]4U
Joined
Aug 30, 2004
Messages
2,664
Ok in the past I've been having problems isntalling BF2 getting MD5 errors and whatnot. My understanding on this problem is that the files are not being copied over correctly. Well I haven't played a audio cd in ages. I pop one in today and on each song it will play a second or two then pause for a second or two then play the rest just fine. I'm wondering if something is goofy with the drive which is also causing BF2 to fail installing.

I opened up Everest and it seemed to show the drive as being fine. :confused:

I have a old maxtor burner in the computer too but its messed up from someone falling on it while it was open :rolleyes:


Anyone have any ideas?
 
aeonrevolution said:
but its messed up from someone falling on it while it was open
Click to expand...

Ouch. Maybe try swapping out the cable and/or try one of those lense cleaners.
Any other software installation problems?
New 52x cd burners are $20 nowadays. Or you could splurge and get a dl dvd burner for under $40.
 
Well Diablo 2 acted funky every once in while saying there was no disc in the drive....but I just kept nailing retry until it worked. But then again it started having random crashes "Unkown Exception" type of thing. I did a wtf on that situation and installed starcraft :D Its worked fine so far.
 
It could either be cables or the drive - getting a new drive (which should come with a cable) will solve either one of those problems.
 
Sometimes those wierd issues are caused by a cable that has somehow 'gone bad' even though it has been stationary inside a closed case :confused: .

Dont exactly know why it happens but once you blow enough time troubleshooting while overlooking the simplest component thinking "it has to be the drive or controller" and it ends up being the *&^$!@ cable, you'll keep a spare ide ribbon laying around and try that first :)
 
You must log in or register to reply here.
Back
Top