Continuous beeping at boot up.

[DVelasquez]

A friend of mine in town has recently returned from Bolivia to find
her computer is now corrupted. It did work earlier in the week, but
now the computer refuses to boot.

She runs Windows 95 and the computer just stalls on the "Windows 95"
bitmap screen and beeps repeatedly. The beeping is rapid and
continuous.

Can anyone tell me why this would have happened?

Thanks,
DVelasquez.

[fishboy]

Check to see if all the cards on the board are seated properly. Was this computer moved at all? Any shift could creep up the cards or dislodge something

[skywalker[TSG]]

hmm fishboy if the cards were lose then the comp wouldent even boot just beep u would see a black screen and the beeping

this sounds like something else dough i dont know what try contacting the place of purchase maybe they will look it over for free ?

[fishboy]

It still could not hurt to make sure everying is where it should be. I would also boot up on a boot disk and run a virusscan\scandisk. The original post did not provide a lot of info. Maby someone kicked it or dropped it out the window while the girl was in Bolivia.

[Eli]

Almost sounds like my brothers computer when he rebooted after he, uh, accidentally deleted his program files directory. Maybe something was moved or deleted on the hard drive before she shut it down earlier that week? Just a thought. Good luck.

[Jin Vitas]

Go into safe mode see if it beeps.. if it doesnt.. then turn off.. the startup windows chimes sound.

[DVelasquez]

Hi everyone.

Thanks for everyone who wrote in with advice.

I was able to fix the problem. It was a
corrupt AUTOEXEC.BAT file. I was able to
replace the corrupt file with an older
backup AUTOEXEC.BAT file.

I booted in line by line mode and tried
booting each line. The config.sys worked
great, the first line of the autoexec.bat
failed.

So I looked at the autoexec.bat file. It
was 300 kilobytes! I thought this was crazy.
So I looked at the contents. The file was
garbled with binary data. This was the
problem (or part of it).

I found a backup in the same directory and
overwrote the corrupt file, (after taking
a copy of it). This apparently fixed the
entire mess.

Thanks again,
D.