I wasn’t aware of the difference, I do have a DX2 66 (I think) but might not be working. The DX4 is the only one I have unfortunately! Thanks for the tip about the L1 cache!
It seems that if you move the battery socket to a different place then you can put in a MiniDIN-6 port for mouse next to keyboard DIN-5. ;) NB! It's great to pay attention to the speedsys' CPU identification. Before you fixed the cache, it showed DX4 with code 484. That's DX4 with write-through cache. Once you fixed the cache, it showed DX4WB with code 494. That's the DX4 with write-back cache. NB2! 486 type can't be really checked. All the software can do is show you assumed CPU type based on motherboard's settings. The motherboard defines the CPU, it just has to "align" with the real world. :P
I used to work for PC Magazine, lots of memories here! Back in the day, you could get programs called TSRs or 'Terminate Stay Resident', WordCraft's screen grabbing utility was one such thing, run it in DOS, it loaded into higher memory and sat waiting for a key press - I used it for grabbing screen shots of fractal landscape software I wrote. anyhow, the multitasking that started with the 386 wasn't very good and programs would apparently close but stayed in RAM running. The Landmark appears to sort of halve in speed thus it might staying resident and eating half your CPU. Just a guess. Oh BTW, I'm no gamer but the cheat codes for Doom are (from memory) IDDFQ - Infinite Health IDFKA - All weapons and infinite ammo ID for ID Games and I'll let you guess what the KFA stood for!
Great video as always and I will say I use those cameras in my own home as well as at my business I've installed them in several places and I have always been very very impressed
It seems like you've got a 5x86 rebranded as a DX4. I have one of these specimens. It does display SV8B, but it also shows up 16KB of cache and if I configure it for 4x multiplier, it POSTs as a 5x86 at 133MHz and works perfectly ! Just like a 5x86 the dark number in the corner next to pin 1 says "25544", other DX4 show up a different number Try the x4 multiplier :)
My 486 & socket 7 era days were spent doing a lot of tinkering to get certain jumpers or settings dialed in just right when I did hardware changes like a CPU upgrade. On one hand I don't miss that in order to get a properly working PC but on the other it sometimes did lead to some interesting discoveries!
I have a pair of ReoLink RLC-510A cameras in and around the home/workshop and have to say they are rock solid IP/PoE, very dependable cameras. I use them with QVR-PRO on my NAS as the server.
I used to think 'fine solder tip for fine work' until I tried a large chisel shape. You wouldn't think it would work well, but it retains its heat so well everything flows nicely.
Yes the tip you see is the biggest I can use without bridging things. That’s why I was thinking of a knife one, I can keep it sideways, have more thermal mass and not have bridges
Great repair video! Not very complex, but the issue with cache was bit tricky to resolve. How a small setting has big impact, and could lead you into very different paths. One thing that remained in my mind, you only re-soldered the bigger chip, right? The smaller chip was actually ok?
Thanks! I re soldered both just to be on the safe side. It’s not super clear from the video but at some point I mentioned I could use the solder tip sideways on the southbridge
I really like the way you troubleshoot the broken vintage stuff systematically, keep on going! And a quick question, where can we find that diagnostic BIOS in discord server? I also have a battery damaged, repaired but still stone dead 486 board that doesn't show anything on the POST card.
Ah...seeing that graphical BIOS brings back memories. Endless seas of jumpers, poorly marked, no documentation, no internet, sadly no friends who knew better than I did. At the time it was all trial and error for me, not hindered by any baseline knowledge. Nice work on the L1 settings, it could have fooled me as well!
I have a socket 7 mobo with a CMOS error. Even when i replace the CMOS battery, the issue stays. I checked the traces around it and i have seen continuity all around it. Although, I haven't tested it super indepth, I probably should. What do you think the issue could be?
@@czel3 Even with no battery you should be able to save, restart and keep the settings so you should not have checksum error. Do you enter the BIOS and save and exit? That should clear the error. If it persists... if not mistaken the BIOS settings live somewhere else, not in the BIOS. You might need to find what IC has that settings and make sure it's powered? I might say rubbish here :)
@@tony359 thank you for the tips! I can definitely check the Bios chip for power. I have an Pentium at 90mhz, the one which is variable from 90mhz-200mhz. Every time I turn on the computer, it resets to factory bios settings which turn the CPU from 200mhz to 90mhz. Then I'll put it back to 200, save and exit, it'll do a restart, and be back at 90mhz. After a bit of trial and error, it'll finally stay at 200mhz with a save and exit. This is the main issue, since the computer would be quite slow at 90mhz for most games I want to play on Windows 98.
Not the BIOS chip - you definitely have voltage there if the board posts. I don't think the BIOS settings are stored on the BIOS. Those UV-Erasable in particular are not writable once they've been written once. Why not opening a thread on Vogons? Probably easier than here and you'll have a bigger audience. Don't forget to mention what motherboard that is! :)
When you restarted speedsys and had the lower 360 something Mhz speed the cpu was completely misdetected it wrote DX 386 and the frequency was also wrong. I believe it needs more investigation jumper wise and bios wise cause I feel it has something to do with the turbo circuit, I would try a different bios version... Great video, ad was very long, cheers from Greece! Jim
It might use different code optimized for 486 when it detects that it is available. I don't think that this is a bios or hw issue though but just a buggy cpu detection in that program.
At 29.37 when you come back to Landmark and it's slower, the CPU and FPU have changed to 386DX and 387DX respectively, so it is not correctly detecting the CPU by the looks of things.
Yes something’s happened there. Though I don’t think how the cpu is detected would change the speed - I feel it’s something else, or a combination of things
this weird behavior indicates ram crashes. is your ram clock and voltage correct? is it the right ram type? i remember there was a difference between EDO and FPM ram. another thing to consider, is your voltage stable enough under full load? possibly just some bad caps (high esr).
You know how it is, TH-cam ad revenue pays peanuts and Tony is doing this full-time. Also we have to commend him for a clever integration and he's been using their products personally, so it's all good 😊
Finally, an ad with a product that's not garbage and will have me remember them in the future.
You can use setmul for toggling L1 cache via software and for diagnostics I would start with a plain Intel 486 DX.
I wasn’t aware of the difference, I do have a DX2 66 (I think) but might not be working. The DX4 is the only one I have unfortunately! Thanks for the tip about the L1 cache!
Great repair, well done 🎉
It seems that if you move the battery socket to a different place then you can put in a MiniDIN-6 port for mouse next to keyboard DIN-5. ;)
NB! It's great to pay attention to the speedsys' CPU identification. Before you fixed the cache, it showed DX4 with code 484. That's DX4 with write-through cache. Once you fixed the cache, it showed DX4WB with code 494. That's the DX4 with write-back cache.
NB2! 486 type can't be really checked. All the software can do is show you assumed CPU type based on motherboard's settings. The motherboard defines the CPU, it just has to "align" with the real world. :P
I thought I’d notice something - thanks for that! And apparently the cpu was completely mis-detected at the end when it slowed down!! I didn’t notice!
nice repair, Tony, really enjoyed it
Thank you! Glad you enjoyed it!
I used to work for PC Magazine, lots of memories here! Back in the day, you could get programs called TSRs or 'Terminate Stay Resident', WordCraft's screen grabbing utility was one such thing, run it in DOS, it loaded into higher memory and sat waiting for a key press - I used it for grabbing screen shots of fractal landscape software I wrote. anyhow, the multitasking that started with the 386 wasn't very good and programs would apparently close but stayed in RAM running. The Landmark appears to sort of halve in speed thus it might staying resident and eating half your CPU. Just a guess.
Oh BTW, I'm no gamer but the cheat codes for Doom are (from memory)
IDDFQ - Infinite Health
IDFKA - All weapons and infinite ammo
ID for ID Games and I'll let you guess what the KFA stood for!
ahah I remember IDDQD?
486 takes me back to my 3rd ever PC build back in the day. 486DX100, VLB m/b (visa local bus), SFX3000 sound card.......fun times. Nice repair Tony.
Those were fun times indeed! Thank you for watching!
Great repair. 16 Mb is a huge amount of RAM for an old 486 board. I was living it up when I had 8 Mb on a motherboard with a Pentium 90 🤣
Oh yes I had 2MB on my 386!! It was painful!
Well done Tony, that was fun 🙂
Thank you!
Great video as always and I will say I use those cameras in my own home as well as at my business I've installed them in several places and I have always been very very impressed
I’m glad that you are! I don’t sponsor items I don’t like myself 🙂
It was challenging but looks easy from your outstanding soldering skills!
Thank you!
It seems like you've got a 5x86 rebranded as a DX4.
I have one of these specimens. It does display SV8B, but it also shows up 16KB of cache and if I configure it for 4x multiplier, it POSTs as a 5x86 at 133MHz and works perfectly !
Just like a 5x86 the dark number in the corner next to pin 1 says "25544", other DX4 show up a different number
Try the x4 multiplier :)
Ahh interesting! I shall try that thanks!
Great job, sir!
Thank you!
The magic man... brings me back to the days I setup and sold these computers. Nice job!
Those nostalgic moments indeed! Thank you!
My 486 & socket 7 era days were spent doing a lot of tinkering to get certain jumpers or settings dialed in just right when I did hardware changes like a CPU upgrade.
On one hand I don't miss that in order to get a properly working PC but on the other it sometimes did lead to some interesting discoveries!
Yes it was a love/hate thing indeed 🙂
I have a pair of ReoLink RLC-510A cameras in and around the home/workshop and have to say they are rock solid IP/PoE, very dependable cameras. I use them with QVR-PRO on my NAS as the server.
Yes they are more or less ‘set and forget’ indeed!
I used to think 'fine solder tip for fine work' until I tried a large chisel shape. You wouldn't think it would work well, but it retains its heat so well everything flows nicely.
Yes the tip you see is the biggest I can use without bridging things. That’s why I was thinking of a knife one, I can keep it sideways, have more thermal mass and not have bridges
You really should feature a "3,2,1,go" counter in your videos :D
uhm... interesting! I'll think about that! Thanks!
Great repair video! Not very complex, but the issue with cache was bit tricky to resolve. How a small setting has big impact, and could lead you into very different paths.
One thing that remained in my mind, you only re-soldered the bigger chip, right? The smaller chip was actually ok?
Thanks! I re soldered both just to be on the safe side. It’s not super clear from the video but at some point I mentioned I could use the solder tip sideways on the southbridge
Thank you.
Nice video!. I had this board, one of best for 486. Any news about 5ALI61?
The ICs I got from Ali were fake... Need to find another source...
I really like the way you troubleshoot the broken vintage stuff systematically, keep on going! And a quick question, where can we find that diagnostic BIOS in discord server? I also have a battery damaged, repaired but still stone dead 486 board that doesn't show anything on the POST card.
Thanks!
I’ll add a download link in the description - tomorrow or Monday likely.
@@tony359Really appreciated, thanks!
We use Reolink cameras and DVR at the rugby club and they seem to be really good.
Yes I’m honestly pretty happy with them!
Ah...seeing that graphical BIOS brings back memories. Endless seas of jumpers, poorly marked, no documentation, no internet, sadly no friends who knew better than I did. At the time it was all trial and error for me, not hindered by any baseline knowledge. Nice work on the L1 settings, it could have fooled me as well!
A friend of mine had a 386 board where the BIOS was a table of hex codes. The wrong code would have bricked the board! 😂
Did you add more RAM at 23:39 or is it being detected as 64 MB due to some sort of a glitch?
I did test several different RAM sticks, I've probably forgot that that final configuration was different than when I started! Thanks for watching!
Do you have a link to the Dexter Bios you used?
Yes, I just added it to the description: 1drv.ms/u/s!AukePwK7XyEPhO88mwU5XxiB_X98Uw?e=niiRvZ
I have a socket 7 mobo with a CMOS error. Even when i replace the CMOS battery, the issue stays. I checked the traces around it and i have seen continuity all around it. Although, I haven't tested it super indepth, I probably should. What do you think the issue could be?
what is the exact error message?
@@tony359 Pretty sure its just CMOS Checksum Error
@@czel3 Even with no battery you should be able to save, restart and keep the settings so you should not have checksum error. Do you enter the BIOS and save and exit? That should clear the error. If it persists... if not mistaken the BIOS settings live somewhere else, not in the BIOS. You might need to find what IC has that settings and make sure it's powered? I might say rubbish here :)
@@tony359 thank you for the tips! I can definitely check the Bios chip for power. I have an Pentium at 90mhz, the one which is variable from 90mhz-200mhz. Every time I turn on the computer, it resets to factory bios settings which turn the CPU from 200mhz to 90mhz. Then I'll put it back to 200, save and exit, it'll do a restart, and be back at 90mhz. After a bit of trial and error, it'll finally stay at 200mhz with a save and exit.
This is the main issue, since the computer would be quite slow at 90mhz for most games I want to play on Windows 98.
Not the BIOS chip - you definitely have voltage there if the board posts. I don't think the BIOS settings are stored on the BIOS. Those UV-Erasable in particular are not writable once they've been written once.
Why not opening a thread on Vogons? Probably easier than here and you'll have a bigger audience. Don't forget to mention what motherboard that is! :)
When you restarted speedsys and had the lower 360 something Mhz speed the cpu was completely misdetected it wrote DX 386 and the frequency was also wrong. I believe it needs more investigation jumper wise and bios wise cause I feel it has something to do with the turbo circuit, I would try a different bios version...
Great video, ad was very long, cheers from Greece! Jim
Ahh I didn’t notice that thanks!!
This is the only Bios available for this board unfortunately…
It might use different code optimized for 486 when it detects that it is available. I don't think that this is a bios or hw issue though but just a buggy cpu detection in that program.
Bits under Bolts had a similar issue with System Information. Yes it could be a software bug, a register somewhere which doesn’t reset… funny!
Nice repair !
It's strange that SpeedSys reports 16KB L1 tho, the marking on your CPU clearly indicates SV8B.
So much the better ! but weird anyway :D
Vswitchzero has found those are ‘blessed’ CPUs from AMD, sold with twice the cache for stocking reasons! Amazing
At 29.37 when you come back to Landmark and it's slower, the CPU and FPU have changed to 386DX and 387DX respectively, so it is not correctly detecting the CPU by the looks of things.
Yes something’s happened there. Though I don’t think how the cpu is detected would change the speed - I feel it’s something else, or a combination of things
[29:45] Why does it display "80386DX"? Half a minute earlier it displayed "80486DX".
Someone else noticed - no idea, somethings weird with the bios or a software bug…
I didn’t change anything!
And this is why I'm put off from buying a 486 board and rather go straight for Pentiums. The freaking jumpers!
ahah yes! The sea of jumpers!
Not that Socket 7's are any better...
You definitely had to *jump* around to find the answer!
😂 took me a few seconds to understand the joke 🙂
Was this motherboard from the made for the European market? Thank you Danke
I do not know unfortunately but it came from a supporter in France!
@tony359 thank you
I got a Batman - with 60mhz P1
but.. it's in sleep mode
I’m working on my Batman…
this weird behavior indicates ram crashes. is your ram clock and voltage correct? is it the right ram type? i remember there was a difference between EDO and FPM ram. another thing to consider, is your voltage stable enough under full load? possibly just some bad caps (high esr).
What weird behaviour?
@@tony359 random crashes and freezes
Am I on the wrong end of the stick here? Did I show crashes and freezes on this video?
@@tony359 haha, no sorry... my mistake. i think i commented at the wrong video.
I think YT does weird things sometimes. :)
Or with the BIOS you may have troubles.
What percentage of people back in the jumper day ran their PC on less capacity because of bad jumpering/BIOS settings..
Quite a few I suppose 🙂
I am a doctor not a electronic technician (you asked for it).
LOOL! The best comment so far! :D
First! 😂😂 Like your videos, keep up with the good work!
Yay, thank you!
5 min ad IS NOT OK.
You need to be a bit more positive, Sir, it’s not good for health! Thanks for watching!
Just skip past it and get in with life 👍
Get SponsorBlock addon.
You know how it is, TH-cam ad revenue pays peanuts and Tony is doing this full-time. Also we have to commend him for a clever integration and he's been using their products personally, so it's all good 😊
It’s 3 minutes BTW 😉