VOGONS


First post, by YesAffinity

User metadata
Rank Newbie
Rank
Newbie

General System Specs:
ECS P6LX-A+ v1.1 440LX motherboard
Pentium II 233mhz, Slot 1
-Noisy cooler fan replaced with Noctua NF-A4x10 FLX
2 x 32MB no-name PC-66 SDRAM (I assume it's PC-66, there are no labels on it)
AGP video card, ISA audio card, 2 x CD/DVD-RW's, 3.5" floppy, 5.25" floppy (finer details on peripherals I don't think is important)

I had the motherboard/CPU clocked at 75mhz CPU bus and 4x multiplier (300 mhz CPU speed). I stress tested it for a couple hours when initially testing this setting, no issues whatsoever. I proceeded to use the system with these settings for a week, with no issues whatsoever.

I got concerned that the overclock may overstress the RAM, and changed BIOS settings to 66mhz CPU bus and 4.5x multiplier (297 mhz CPU speed). Upon rebooting, the system would not POST.

I have reset BIOS settings via the CMOS jumper, pulled the battery, still no POST. I have tried many different attempts to reset BIOS setting, up to removing everything from the motherboard, setting the CMOS jumper in the reset position and removing the battery, and leaving it like this for over 8 hours. Putting CMOS jumper back to 'normal' setting, re-installing the battery, and re-installing only CPU, RAM, AGP video card and ATX power connection, I am still getting no POST.

If there has been a failure, it seems the CPU is the likely culprit and the 4.5x muliplier killed it, even though CPU speed is less than or equal to where it was operating just fine through stress testing and normal usage as noted above. Does that seem logical?

Is there some other trick that I'm unaware of that might bring this system back to life?

I already had some upgraded RAM coming, and should have that today (2x256 PC-100). I bought a replacement CPU and should have that within the next day or two. Will continue the effort of pinpointing the failure as I get those. Really hoping it's not the motherboard...or there's some other trick to be tried.

Reply 1 of 12, by kmeaw

User metadata
Rank Member
Rank
Member

Do you get the beeps when you try to power on the system without RAM and AGP card?
Do you have a POST analyzer card? If you do, does the system go out of the reset state and are there any POST codes sent over port 80h?

Another thing to try is forcing the BIOS into recovery mode from the bootblock code by shorting two highest address lines on the flash chip.

Reply 2 of 12, by YesAffinity

User metadata
Rank Newbie
Rank
Newbie

Thanks @kmeaw!

Good question - I get no beeps whatsoever. Fans spin up, and I can hear hard drives spin up, but no other indications of normal operation.

I forgot to mention - I also burned a replacement BIOS rom and swapped that in. The stock BIOS was udpated to version 3.1d, with hard drive support (https://www.wimsbios.com/biosupdates/la ... #gsc.tab=0). This is a 128kb BIOS. I burned official BIOS 3.3, which is a 256kB BIOS (https://www.ecs.com.tw/en/Product/Motherboard … A_Plus/download). No difference with either BIOS installed.

I don't have a POST analyzer.

To force BIOS into recovery mode, would that be shorting pins 2 and 3, for A16 and A15 respectively?

Reply 3 of 12, by YesAffinity

User metadata
Rank Newbie
Rank
Newbie

:edit: Well shoot, for less than $15 with the fastest amazon shipping and arrival by 8 a.m. tomorrow, I also have a POST analyzer on the way. 😁 Seems like a good tool for the toolkit.

to clarify, the BIOS eprom is either a 27c010 or 27c020, so if I understand it correctly, the highest address pins would be A15 adn A16, pins 3 and 2 respectively.

Reply 5 of 12, by YesAffinity

User metadata
Rank Newbie
Rank
Newbie
tauro wrote on 2024-11-07, 19:00:

The processor is probably fine. I think the motherboard couldn't take the stress. Hopefully it's not the chipset. Maybe a transistor. You could try recapping the board.

Damn. Why would they put that option in the bios if the motherboard can't handle it. I guess it was a misconception on my part. I knew the risks with the cpu, didn't think there was risk for the motherboard because of that.

Reply 6 of 12, by rasz_pl

User metadata
Rank l33t
Rank
l33t

75MHz never killed anything. If anything it might be caps finally dying of old age. You would need an oscilloscope to peek at Vcore and see if there is huge ripple on it.

https://github.com/raszpl/FIC-486-GAC-2-Cache-Module for AT&T Globalyst
https://github.com/raszpl/386RC-16 memory board
https://github.com/raszpl/440BX Reference Design adapted to Kicad
https://github.com/raszpl/Zenith_ZBIOS MFM-300 Monitor

Reply 7 of 12, by kmeaw

User metadata
Rank Member
Rank
Member
YesAffinity wrote on 2024-11-07, 17:37:

To force BIOS into recovery mode, would that be shorting pins 2 and 3, for A16 and A15 respectively?

That is correct, on a PDIP-32 2Mbit flash chip it would be pins 2 and 3. Short them before connecting the power, short them with some metal tool, power it on and remove the tool in a second or a two. The bootblock code would fail the checksum test and go into recovery, initializing only the bare essentials needed to boot DOS from a floppy disk. On some boards even a PCI video won't work but you should see and hear floppy activity if it worked.

Reply 8 of 12, by YesAffinity

User metadata
Rank Newbie
Rank
Newbie

I'm happy to report that this PC has resumed normal operation. I'm not certain if it was forcing BIOS into recovery mode that worked or not. I tried it twice, power cycled a couple times with no improvement and no life from the floppies. I was simultaneously testing a Hercules 4500 AGP card, specifically the fan which was seized when I got it, but back to functional with a drop of 3-in-1 oil. Unknowingly, the video card was only partially seated in the AGP slot due to the retention clip of one of the IDE connectors interfering with the card fully inserting. Anyhoo, there were some error beeps, I think 1 long and 2 short, and the system booted.

I subsequently sorted everything out, the system is fully re-assembled with the 512MB of PC-1oo and Hercules 4500 card, and back at 75mhz CPU bus and 300mhz CPU speed. Well, I've got a 350mhz on the way, so that'll be getting upgraded soon. 😀

Thanks all for the help. Truly appreciated!

Reply 9 of 12, by Linoleum

User metadata
Rank Member
Rank
Member
kmeaw wrote on 2024-11-07, 20:11:
YesAffinity wrote on 2024-11-07, 17:37:

To force BIOS into recovery mode, would that be shorting pins 2 and 3, for A16 and A15 respectively?

That is correct, on a PDIP-32 2Mbit flash chip it would be pins 2 and 3. Short them before connecting the power, short them with some metal tool, power it on and remove the tool in a second or a two. The bootblock code would fail the checksum test and go into recovery, initializing only the bare essentials needed to boot DOS from a floppy disk. On some boards even a PCI video won't work but you should see and hear floppy activity if it worked.

Is there a thread/post with instructions to do this on any type of BIOS (award, phoenix, etc)?

Athlon64 3200+, HD3650, SB X-FI
P4 1.8Ghz, V3, SBLive
P3 866Mhz, Riva TNT2, SB Audigy
P2 266Mhz, TNT, V2, Audigy 2ZA
P233 MMX, Mystique 220, SB 32
P100, S3 Virge GX, AWE64, WavetablePi & PicoGus
Prolinea 4/50, ET4000, SB 16, WavetablePi

Reply 11 of 12, by kmeaw

User metadata
Rank Member
Rank
Member
Linoleum wrote on 2024-11-08, 13:37:

Is there a thread/post with instructions to do this on any type of BIOS (award, phoenix, etc)?

I am not able to locate the instructions I have seen back then but here is another page that looks good to me: https://mastermindloltricks.blogspot.com/2012 … e-you-dont.html

It won't work with any type of BIOS - most uncompressed BIOSes (the older ones, usually 64kB or less) don't have a recovery procedure, they just beep and halt the machine if the checksum is bad.
A normal PC maps the rom chip so the last byte of ROM is available at F000:FFFF in 16-bit real mode (the mode the CPU is in when it is reset). The first instruction fetched from the ROM is F000:FFF0 (the reset vector) - 16 bytes before the last byte.
This instruction usually jumps into the middle (around F000:C000) of the F000 segment. If the BIOS is compressed, it would be the boot block - a piece of code which enables DRAM, ROM shadowing with write access and runs the decompressor, then checks the integrity of the decompressed code. If the integrity check fails, it is capable of running a very limited set of services to boot DOS from floppy.

All that code is located at the end of the ROM, so by pulling any high (A15 and above) address line would prevent the lower half of the ROM to be read causing a checksum failure and forcing the bootblock code to go into recovery. On an 8-bit data wide 2Mbit chip pulling A15 high would cause reads of 0x0000..0x7FFF,0x10000..0x1FFFF to be misdirected to 0x8000..0xFFFF,0x18000..0x1FFFF. Pulling A16 high would cause 0x0000.0xFFFF to go to 0x10000..0x1FFFF. Shorting A15 and A16 together would have a similar effect because A16 would be initially high as the reset vector points to the higher half of the ROM.

Reply 12 of 12, by YesAffinity

User metadata
Rank Newbie
Rank
Newbie
konc wrote on 2024-11-08, 14:07:

How are you setting all these different multipliers, is your Pentium II unlocked?

I assume so, 🤣. Setting them in the BIOS. It shows as 300mhz in Win98.

Attachments