ScoobyNet.com - Subaru Enthusiast Forum

ScoobyNet.com - Subaru Enthusiast Forum (https://www.scoobynet.com/)
-   Computer & Technology Related (https://www.scoobynet.com/computer-and-technology-related-34/)
-   -   Widows ME won't boot up (https://www.scoobynet.com/computer-and-technology-related-34/315925-widows-me-wont-boot-up.html)

Jer 02 April 2004 03:07 PM

Widows ME won't boot up
 
I plugged in a network card on a Windows ME computer it started to boot and came up with the message "changing current configuration" or something like that. I left it for about ten minutes and it stayed on this screen (DOS). On this screen it displayed a list of devices with IRQ's (four of the divices had duplcate IRQ's one pair with IRQ 9 another with IRQ 11). I switched the PC off, took out the card and tried a reboot. All I am getting now is three or four beeps it checks the drives then nothing happens. I put the card back in but am getting the same thing.

HELP how can I get the PC to boot up again.

Thanks

Jer

Phil Harrison 02 April 2004 04:42 PM

"Rescue Disk"?
Boot from original CD?
Boot with F8 pressed

are three ways in.

Phil

kelvin 02 April 2004 05:16 PM

How many beeps? And what Bios are you running?

If you count the number of beeps, and post up here it'll be easier to trace where the problem lies...

K.

Jer 02 April 2004 05:46 PM

hi

It's one long beep then two shorter ones. it then scans the drives and does another four. Don't know what BIOS it's running but it's a 350mhz and I see a sticker with the date 1999.
I have also disconnected all drives and it still beeps. I have tried a boot disk with no joy, no ME disk and no F keys work.

LeeMac 03 April 2004 03:11 PM

memory might have gone, change it or take one out if more than one

LeeMac 03 April 2004 03:15 PM

or gfx card
take all out and try another

GC8 03 April 2004 05:59 PM

The beeps that you hear are a BIOS error beep code. Count the number and frequency of the beeps then go to www.bioscentral.com to find out exactly what the problem is. You will need to know the BIOS manufacturer for your system board.

There will be no way around an error like this; your system is failing to POST (Power On Self Test). All of this happens before the BIOS loads the operating system so F8 keys and bootable diskettes are totally irrelevant.

I'd recommend removing the battery from the system board for a few minutes too; it'd be easier to wipe the CMOS data using the appropriate jumper but if you aren't sure what's what, pulling the 32mm lithium cell battery for a minute or two will achieve the same thing.

If the error beep code indicates a component like the video adapter or memory you could try removing and re-seating after cleaning with denatured alchohol; but there's little chance of actually repairing anything

Simon

GC8 03 April 2004 06:05 PM

One long and two short sounds like either an AMI or an Award BIOS and they both use that for a video adapter error of some sort if I remember correctly; Phoenix use all short beeps in groups.

Simon

jods 04 April 2004 12:31 AM

Where are you based ? I can probably sort this out for you in 1/2 hour
;)

Jer 04 April 2004 07:23 PM

Thanks for all the replies.

Thanks for the offer jods but im in Glasgow. Any ideas would be appreciated though.


Simon
I pulled the battery out as you suggested with no joy. What's the easiest way to find out what BIOS or MoBo I am using. I had a look but can't see any names printed on it. It does have a small blue box with small white switches on it. Are these the jumpers you mentioned?
Leemac I have tried new memory but not gfx card. It's a strange one as the pc was working okay up until I put the NIC in.

LeeMac 05 April 2004 12:44 AM

strange things pc's, try and get an old gfx card just to try, take all other cards out and just use minimum to boot up ie. spare or different gfx card, wouldn't mess with jumpers myslf unless adjusted beforehand, make sure all leads are correct

Tony_W 05 April 2004 12:20 PM

Have you checked that the bios hasn't been set up to boot via network?
hit del on boot and check "boot up" options to make sure. Also go into the section for peripherals/IDE and reset the configuration and tell it you have a plug n play OS.

(Can't remember the exact section titles off the top of my head but look under each one until you find plug n play and above it should be reset configuration y/n...select yes.)

It sounds like a bios prob as has already been said. Also check all the cards, memory and IDE cables have not been loosened when you put the NIC in.

bioforger 05 April 2004 01:42 PM

Did u wear an antistatic strap or earth yourself b4 u put the NIC in? If not you might have tweaked the RAM or a chip on the gfx card or motherboard by the sounds of it :(

Jer 05 April 2004 01:59 PM


Originally Posted by Tony_W
Have you checked that the bios hasn't been set up to boot via network?
hit del on boot and check "boot up" options to make sure. Also go into the section for peripherals/IDE and reset the configuration and tell it you have a plug n play OS.

(Can't remember the exact section titles off the top of my head but look under each one until you find plug n play and above it should be reset configuration y/n...select yes.)

It sounds like a bios prob as has already been said. Also check all the cards, memory and IDE cables have not been loosened when you put the NIC in.

Tony, It was a stand alone machine.

Bioforger, no I didn't have strap on. I think you may be right.

Thanks

Jeremy

Jer 05 April 2004 07:05 PM

Result, it was the graphics card.

Thanks all

bioforger 07 April 2004 03:48 PM


Originally Posted by Jer
Tony, It was a stand alone machine.

Bioforger, no I didn't have strap on.

Thanks

Jeremy

:o Way too much info :D lol

Jer 07 April 2004 05:38 PM

LOL

GC8 08 April 2004 02:58 AM

From the description that you gave then Id say that the BIOS error beep code indicates a video adapter problem; to find out what BIOS you have look on the system board, theres likely to be a sticker on the BIOS chip, either AMI (American Megatrends) or AWARD. The only way forward is to remove the video adapter or disable it if its on board, and then try a replacement.

Simon

GC8 08 April 2004 03:00 AM

NOW I see that youve solved it; Im half asleep, sorry, look at the time ffs.....


All times are GMT +1. The time now is 11:29 PM.


© 2024 MH Sub I, LLC dba Internet Brands