VOGONS


First post, by Dougal

User metadata
Rank Newbie
Rank
Newbie

It worked fine but was losing the bios settings due to the battery/clock ODIN (like Dallas).

Anyway, stupidly I removed the ODIN clock damaging it in the process and then it would no longer boot. Nothing, no display, no POST beeps nothing.

So, ordered a new ODIN clock with same model number etc and soldered a socket while waiting for the ODIN clock to arrive.

Today the ODIN clock arrived, so I installed it and tried to boot. NOTHING, no POST beeps, no display 🙁

I am lost as what to try out.

I also did another mistake, while trying to diagnose before realizing that it wont boot or POST without the clock I accidently put the CPU the wrong way and powered it up. The CPU is a 100Mhz DX4 AMD CPU 486.

I have another two CPU's to test if I damaged the CPU but I doubt that managed to damaged the CPU.

Attachments

  • 486_2.jpg
    Filename
    486_2.jpg
    File size
    108.07 KiB
    Views
    1367 views
    File license
    Fair use/fair dealing exception
  • 486_1.jpg
    Filename
    486_1.jpg
    File size
    126.99 KiB
    Views
    1367 views
    File license
    Fair use/fair dealing exception

Win 7 : Core2Quad 2.4Ghz, 4Gb Ram, Audigy 4 Pro
Win 98: Pentium III 600Mhz, 448MB Ram, Matrox Millenium DualHead 32MB, Sound Blaster 32, Roland MT-32
Win 98: Compaq Armada 7400 P2 333Mhz, 192MB Ram, ESS AudiDrive 1879 with Wavetable

Reply 2 of 16, by Dougal

User metadata
Rank Newbie
Rank
Newbie

Oh crap 🙁

Win 7 : Core2Quad 2.4Ghz, 4Gb Ram, Audigy 4 Pro
Win 98: Pentium III 600Mhz, 448MB Ram, Matrox Millenium DualHead 32MB, Sound Blaster 32, Roland MT-32
Win 98: Compaq Armada 7400 P2 333Mhz, 192MB Ram, ESS AudiDrive 1879 with Wavetable

Reply 3 of 16, by amadeus777999

User metadata
Rank Oldbie
Rank
Oldbie

I once put in a cpu the wrong way too - it was on a LS486E.

Due to hours of testing and repetitious in/out(not the good way) I made formerly mentioned mistake. Both the cpu and the board survived but the voltage regulator was fryed. I initially thought the board was toast(no sign of life on power on), but due to the gods' retro fetish I tested a 5V cpu and voila... it came back from the dead.

Try a 5V cpu + good luck.

Reply 4 of 16, by BLockOUT

User metadata
Rank Member
Rank
Member
amadeus777999 wrote:

I once put in a cpu the wrong way too - it was on a LS486E.

Due to hours of testing and repetitious in/out(not the good way) I made formerly mentioned mistake. Both the cpu and the board survived but the voltage regulator was fryed. I initially thought the board was toast(no sign of life on power on), but due to the gods' retro fetish I tested a 5V cpu and voila... it came back from the dead.

Try a 5V cpu + good luck.

so
Board not fried?
CPU not fried ?
only broken voltage regulator?
only that is broken or other components suffered too?

did you replace the regulator later on? did it boot a 3.45 cpu after that?

Reply 5 of 16, by amadeus777999

User metadata
Rank Oldbie
Rank
Oldbie

No, both survived.

I'm running the board with an Evergreen 5x86 x133 cpu now and it's been working for hours on end since. It even runs at 50mhz fsb with all settings maxed out, so I doubt there's other components fried.

I'm in the process of installing the voltage mod, so that I can regulate the voltage from 5 down to to 1.xV(theoretically).

Reply 6 of 16, by kixs

User metadata
Rank l33t
Rank
l33t

I once inserted the cpu in the wrong way and everything turned out fine. I guess it depends which way you turned it.

Recently one of my better 486 VIP motherboards and POD5V83 that worked fine at 100MHz just froze at booting. After that no life whatsoever. Both dead 😵 I searched long time to find POD5V83 that works fine at 100MHz without mods. 😢

In the end this is old hardware and I guess everything is possible..

Requests are also possible... /msg kixs

Reply 7 of 16, by Eleanor1967

User metadata
Rank Member
Rank
Member
amadeus777999 wrote:

I once put in a cpu the wrong way too - it was on a LS486E.

Due to hours of testing and repetitious in/out(not the good way) I made formerly mentioned mistake. Both the cpu and the board survived but the voltage regulator was fryed. I initially thought the board was toast(no sign of life on power on), but due to the gods' retro fetish I tested a 5V cpu and voila... it came back from the dead.

Try a 5V cpu + good luck.

I did the exact same thing: inserted a CPU the wrong way on a LS486e and my voltage regulator was dead... Board and CPU survived though too. So OP you maybe should do some more testing before scraping the board

Reply 8 of 16, by feipoa

User metadata
Rank l33t++
Rank
l33t++

I think it also depends on how long you had the motherboard turned on while the CPU is inserted incorrectly. I have friend a motherboard once because I turned on the board with the CPU inserted incorrectly, but looked the other way. I had the PSU engaged for about 10 seconds. The board (or CPU) started smoking. The CPU survived and the board died. Since then, and before, I have accidently powered on about half a dozen times with the CPU inserted incorrectly, but I always keep my finger on the power button now until I see a CMOS screen. If I don't see a sign of life within about 3 seconds, I shut the PSU off. This habit I've developed has saved those half dozen other boards/CPUs.

When you get tired and just want to run a quick test is when the CPU goes in backwards. Developing a habit to hold your finger on the power button for test beds might save yourself some hardware in the future.

Plan your life wisely, you'll be dead before you know it.

Reply 9 of 16, by Dougal

User metadata
Rank Newbie
Rank
Newbie

I have 3 CPU's - The original one it had a AMD DX4-100, a Intel DX2 66 and a AMD 486 DX 40

How do I know what voltages these are ?

Win 7 : Core2Quad 2.4Ghz, 4Gb Ram, Audigy 4 Pro
Win 98: Pentium III 600Mhz, 448MB Ram, Matrox Millenium DualHead 32MB, Sound Blaster 32, Roland MT-32
Win 98: Compaq Armada 7400 P2 333Mhz, 192MB Ram, ESS AudiDrive 1879 with Wavetable

Reply 11 of 16, by dogchainx

User metadata
Rank Member
Rank
Member

My brother, on upgrading the family's business computer back in early 90's, fried a $450 486dx2-66 cpu along with the motherboard because he put it in the wrong way. Oops.

386DX-40MHz-8MB-540MB+428MB+Speedstar64@2MB+SoundBlaster Pro+MT-32/MKII
486DX2-66Mhz-16MB-4.3GB+SpeedStar64 VLB DRAM 2MB+AWE32/SB16+SCB-55
MY BLOG RETRO PC BLOG: https://bitbyted.wordpress.com/

Reply 12 of 16, by feipoa

User metadata
Rank l33t++
Rank
l33t++

Do you think not keying the CPUs was a deliberate attempt to sell more CPUs [because users have to buy again when they fry 'em]?

Plan your life wisely, you'll be dead before you know it.

Reply 13 of 16, by amadeus777999

User metadata
Rank Oldbie
Rank
Oldbie

That would be a pretty efficient scam... sometimes, when changing cpus, exactly the same thoughts came to mind.

Alex Jones@InfoWars
"Intel states that not keying cpus was a vital step to world dominance!"

Reply 14 of 16, by ATauenis

User metadata
Rank Member
Rank
Member

Did you tried to use a PC Analyzer card to see if there are really no signs of life or the board simply stops on yearly steps of POST? I've successfully 😀 damaged a Odin RTC on Socket-7 board and now it is looking like your - nothing is smoking and nothing works. The board is stopping at 07 POST code (the firmware is Award 4.51). It is dead only due to RTC chip.

Also broken or fried CPUs sometimes may lock RESET signal, so the Reset LED will not blink on the PC Analyzer (POST Card) when cpu is installed.

2×Soviet ZX-Speccy, 1×MacIIsi, 1×086, 1×286, 2×386DX, 1×386SX, 2×486, 1×P54C, 7×P55C, 6×Slot1, 4×S370, 1×SlotA, 2×S462, ∞×Modern.

Reply 15 of 16, by Dougal

User metadata
Rank Newbie
Rank
Newbie

There was two or 3 damaged pads where the RTC/Battery (ODIN) sits. They are fixed now and it POSTS but still more issues which it did not have before.

It says something about the BIOS checksum failing and system halted. I can get into bios settings but it cannot detect hard disks when using a controller card (i tried 2) but it detects it on the onboard IDE connector but then it freezes when I try to save the bios settings and when I reboot I get the same checksum failed and system halted.

Win 7 : Core2Quad 2.4Ghz, 4Gb Ram, Audigy 4 Pro
Win 98: Pentium III 600Mhz, 448MB Ram, Matrox Millenium DualHead 32MB, Sound Blaster 32, Roland MT-32
Win 98: Compaq Armada 7400 P2 333Mhz, 192MB Ram, ESS AudiDrive 1879 with Wavetable

Reply 16 of 16, by amadeus777999

User metadata
Rank Oldbie
Rank
Oldbie

Hey, at least it "lives" and there's chance of repairing it.

I also had the freeze issue with an GA486 AMS board which later refused to boot up again... it's kept in a safe place but "dead". So this could mean it's just the battery?