You have an AMD AM486DX4 so you need to set your jumpers according to option (E) AMD DX/DX2/DX4 (NV8T) (pdf page 7) and set the voltage to 3V (4V if 3V doesn't do it).

The weird cable on the PSU is meant to power a turbo display.

Let us know how it went! 😀

Oh, and JP18 needs to be set 1-2 to select the 33MHz FSB.
And welcome to the forum! 😀

The manual/board does not show which direction the jumpers go.
Maybe re-seat the jumper - it could be an "illegal" setting instead of the 33mhz clock. My old manual gives 5-6 closed for 33mhz your's shows 1-2 closed for the same setting.

Doornkaat wrote on 2021-07-27, 08:36:

You have an AMD AM486DX4 so you need to set your jumpers according to option (E) AMD DX/DX2/DX4 (NV8T) (pdf page 7) and set the voltage to 3V (4V if 3V doesn't do it).

The weird cable on the PSU is meant to power a turbo display.

Let us know how it went! 😀

Thanks for the reply!

I have an enhanced AMD 486 with writeback, and the manual says there are specific jumper settings for that processor compared to the settings shown for the write-through chips (NV8T). I will try changing the voltage to 4v though!

Update: So I got the turbo display working, so thanks for that, but none of the other stuff you suggested worked. The FSB is set to 33mhz, and changing the voltage to 4v produced no results.

Something odd though...The turbo display is reading 50mhz and when I hit the button it ramps down to 33mhz...I've got a 100mhz processor in there...Is it possible my processor is not seated all the way, or is this just default behavior for the turbo display when it's not getting any information from the system? It's a ZIF socket, but I did notice there seems to be a little bit of space in-between the socket and the chip? I'm really out of my depth here...

Baby steps are good! I'd really like to keep making progress with this.

Thank you!

amadeus777999 wrote on 2021-07-27, 09:24:

The manual/board does not show which direction the jumpers go.
Maybe re-seat the jumper - it could be an "illegal" setting instead of the 33mhz clock. My old manual gives 5-6 closed for 33mhz your's shows 1-2 closed for the same setting.

Yes, I think this might be the issue. I saw a video with the exact same problem recently: https://www.youtube.com/watch?v=VC6BtL_6jhQ.

From your picture I can see that the jumper is in the configuration that was not working for the guy in the video. Try swapping the FSB jumper to the other side of the jumper block.
The board revision in the video is C2, I'm not sure if that makes a difference.

Otherwise, a PCI/ISA post card could help diagnose the issue.

watson wrote on 2021-07-27, 13:50:

Yes, I think this might be the issue. I saw a video with the exact same problem recently: https://www.youtube.com/watch?v=VC6BtL […]
Show full quote

amadeus777999 wrote on 2021-07-27, 09:24:

The manual/board does not show which direction the jumpers go.
Maybe re-seat the jumper - it could be an "illegal" setting instead of the 33mhz clock. My old manual gives 5-6 closed for 33mhz your's shows 1-2 closed for the same setting.

Yes, I think this might be the issue. I saw a video with the exact same problem recently: https://www.youtube.com/watch?v=VC6BtL_6jhQ.

From your picture I can see that the jumper is in the configuration that was not working for the guy in the video. Try swapping the FSB jumper to the other side of the jumper block.
The board revision in the video is C2, I'm not sure if that makes a difference.

Otherwise, a PCI/ISA post card could help diagnose the issue.

Tried with no luck. I noticed that the guy in the video was also using shorting two pins on something called "w2" which I don't seem to have on my board at all? So strange!

Update: I was able to get a post beep by setting the FSB to 25 or 40. One long beep followed by two short ones. I suppose that's something? /shrug

resetsmith wrote on 2021-07-27, 12:43:

Something odd though...The turbo display is reading 50mhz and when I hit the button it ramps down to 33mhz...I've got a 100mhz processor in there...Is it possible my processor is not seated all the way, or is this just default behavior for the turbo display when it's not getting any information from the system? It's a ZIF socket, but I did notice there seems to be a little bit of space in-between the socket and the chip? I'm really out of my depth here...

Don't overthink the turbo display. If the turbo switch connector is connected right, it really will tell the board to run fast or slow, but the numbers are just for decoration... the RGB of its time. They are set using jumpers on the turbo display; it isn't sophisticated enough to read out the speed from the board or anything. (In fact, the only way these BIOSes can determine the clock rate is to run a brief benchmark).

The motherboard power connector wires look slightly weird because there is a black wire on the far end and there is that ribbon cable in the way, but I assume both connectors have the black wires in the middle. Since the visible connector is in correctly I assume the other one is too.

You did verify the RAM is FPM not EDO?

jakethompson1 wrote on 2021-07-27, 14:15:

Don't overthink the turbo display. If the turbo switch connector is connected right, it really will tell the board to run fast o […]
Show full quote

resetsmith wrote on 2021-07-27, 12:43:

Something odd though...The turbo display is reading 50mhz and when I hit the button it ramps down to 33mhz...I've got a 100mhz processor in there...Is it possible my processor is not seated all the way, or is this just default behavior for the turbo display when it's not getting any information from the system? It's a ZIF socket, but I did notice there seems to be a little bit of space in-between the socket and the chip? I'm really out of my depth here...

Don't overthink the turbo display. If the turbo switch connector is connected right, it really will tell the board to run fast or slow, but the numbers are just for decoration... the RGB of its time. They are set using jumpers on the turbo display; it isn't sophisticated enough to read out the speed from the board or anything. (In fact, the only way these BIOSes can determine the clock rate is to run a brief benchmark).

The motherboard power connector wires look slightly weird because there is a black wire on the far end and there is that ribbon cable in the way, but I assume both connectors have the black wires in the middle. Since the visible connector is in correctly I assume the other one is too.

You did verify the RAM is FPM not EDO?

Thank you for the explanation of the turbo display. I definitely would have continued to wig out about that.

AT power is connected correctly with the black cables on the inside.

As for the ram, I'm not sure, but the board's manual says it supports EDO?

Looks like long-short-short is video card related, so perhaps try moving it around in different pci slots.

jakethompson1 wrote on 2021-07-27, 14:24:

Looks like long-short-short is video card related, so perhaps try moving it around in different pci slots.

25Mhz FSB is what produced this post beep code, but that's not the right setting for my chip? I saw that that Award bios beep code mentions a long + two short beeps is video related...and I'm definitely not getting video...but if the FSB setting is wrong, should I even bother?

I've gotta go to work now, but I will try this when I get home if you say it's worth a shot.

Thanks everyone! I feel like I'm slowly makin' my way.

resetsmith wrote on 2021-07-27, 14:34:

25Mhz FSB is what produced this post beep code, but that's not the right setting for my chip? I saw that that Award bios beep co […]
Show full quote

jakethompson1 wrote on 2021-07-27, 14:24:

Looks like long-short-short is video card related, so perhaps try moving it around in different pci slots.

25Mhz FSB is what produced this post beep code, but that's not the right setting for my chip? I saw that that Award bios beep code mentions a long + two short beeps is video related...and I'm definitely not getting video...but if the FSB setting is wrong, should I even bother?

I've gotta go to work now, but I will try this when I get home if you say it's worth a shot.

Thanks everyone! I feel like I'm slowly makin' my way.

25 MHz just means it will run at 75 instead of 100, so underclocked. Video card problem is (I think) pretty late in the POST process so it's a good sign if you could at least get video and then get back to troubleshooting the 33 MHz issue.
If you continue to have problems it would be helpful to dismantle the system and take a picture of the board with nothing in the way to show all jumpers.

At certain angles the graphics card won't work...keep in mind that without a rail it will sometimes wander to the sides.

jakethompson1 wrote on 2021-07-27, 14:51:

resetsmith wrote on 2021-07-27, 14:34:

25Mhz FSB is what produced this post beep code, but that's not the right setting for my chip? I saw that that Award bios beep co […]
Show full quote

jakethompson1 wrote on 2021-07-27, 14:24:

Looks like long-short-short is video card related, so perhaps try moving it around in different pci slots.

25Mhz FSB is what produced this post beep code, but that's not the right setting for my chip? I saw that that Award bios beep code mentions a long + two short beeps is video related...and I'm definitely not getting video...but if the FSB setting is wrong, should I even bother?

I've gotta go to work now, but I will try this when I get home if you say it's worth a shot.

Thanks everyone! I feel like I'm slowly makin' my way.

25 MHz just means it will run at 75 instead of 100, so underclocked. Video card problem is (I think) pretty late in the POST process so it's a good sign if you could at least get video and then get back to troubleshooting the 33 MHz issue.
If you continue to have problems it would be helpful to dismantle the system and take a picture of the board with nothing in the way to show all jumpers.

The plot thickens! So I can even get the post beep code consistently and I think it may just be due to me letting the card sag while I was testing things. I'm still not getting any video and I'm so confused and frustrated. Tried cleaning card and the PCI slots with no luck. Help? T^T

Edit: I tried messing with the FSB settings, and I've been able to get the post beep code on 25 and 33mhz...

resetsmith wrote on 2021-07-27, 23:26:

jakethompson1 wrote on 2021-07-27, 14:51:

resetsmith wrote on 2021-07-27, 14:34:

25Mhz FSB is what produced this post beep code, but that's not the right setting for my chip? I saw that that Award bios beep code mentions a long + two short beeps is video related...and I'm definitely not getting video...but if the FSB setting is wrong, should I even bother?

I've gotta go to work now, but I will try this when I get home if you say it's worth a shot.

Thanks everyone! I feel like I'm slowly makin' my way.

25 MHz just means it will run at 75 instead of 100, so underclocked. Video card problem is (I think) pretty late in the POST process so it's a good sign if you could at least get video and then get back to troubleshooting the 33 MHz issue.
If you continue to have problems it would be helpful to dismantle the system and take a picture of the board with nothing in the way to show all jumpers.

The plot thickens! So I can even get the post beep code consistently and I think it may just be due to me letting the card sag while I was testing things. I'm still not getting any video and I'm so confused and frustrated. Tried cleaning card and the PCI slots with no luck. Help? T^T

Edit: I tried messing with the FSB settings, and I've been able to get the post beep code on 25 and 33mhz...

Can we get a closer look at your RAM simm, or maybe verify what happens if you try with no ram at all

resetsmith wrote on 2021-07-27, 04:04:

I've got the jumpers set for "enhanced AMD with writeback cache", but I don't get a post beep, video, and the turbo LED doesn't show anything. Can anyone help me troubleshoot this? I'd really appreciate it.

Wait, if the turbo LED doesn't show anything, and you don't have it connected backward, maybe it's in non-turbo mode? It could be working just so excruciatingly slow you never notice except when the video card is missing Never mind

jakethompson1 wrote on 2021-07-28, 00:14:

resetsmith wrote on 2021-07-27, 23:26:

jakethompson1 wrote on 2021-07-27, 14:51:

25 MHz just means it will run at 75 instead of 100, so underclocked. Video card problem is (I think) pretty late in the POST process so it's a good sign if you could at least get video and then get back to troubleshooting the 33 MHz issue.
If you continue to have problems it would be helpful to dismantle the system and take a picture of the board with nothing in the way to show all jumpers.

The plot thickens! So I can even get the post beep code consistently and I think it may just be due to me letting the card sag while I was testing things. I'm still not getting any video and I'm so confused and frustrated. Tried cleaning card and the PCI slots with no luck. Help? T^T

Edit: I tried messing with the FSB settings, and I've been able to get the post beep code on 25 and 33mhz...

Can we get a closer look at your RAM simm, or maybe verify what happens if you try with no ram at all

I'm so sorry I doubted you! It was the ram! I swapped it out for some sticks I had in another machine and it booted immediately! Correct bus speed and everything B)

Thanks to everyone for your help!

Update: The video card is still giving me issues...Seems like it's VERY particular about how it's sitting in the slot. I can't even get the case put back together without making it angry and losing video...Seems like I'll need to replace it. Progress though! Not mad about that.

Good to see it's working - some slots are looser some are tighter.
Maybe try a different video card or use some hot-glue to fasten it appropriately.

You can also try rubbing the video card's edge connector with a pencil eraser.

Don't forget to install a cooler on the cpu. It won't last long without 😀