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 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.
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
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 :)
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!
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.
The magic man... brings me back to the days I setup and sold these computers. Nice job!
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
nice repair, Tony, really enjoyed it
Thank you! Glad you enjoyed it!
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.
It was challenging but looks easy from your outstanding soldering skills!
Thank you!
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.
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!
We use Reolink cameras and DVR at the rugby club and they seem to be really good.
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 :)
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!
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
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.
Was this motherboard from the made for the European market? Thank you Danke
First! 😂😂 Like your videos, keep up with the good work!
What percentage of people back in the jumper day ran their PC on less capacity because of bad jumpering/BIOS settings..
Or with the BIOS you may have troubles.
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 👍