bloodem wrote on 2022-02-15, 06:47:

Well, you guys can consider yourselves lucky. :-D Some years ago I won a VLB I/O Controller for $2 + shipping (another $5 or so) […]
Show full quote

Well, you guys can consider yourselves lucky. 😁
Some years ago I won a VLB I/O Controller for $2 + shipping (another $5 or so). The seller did send it to me, but the card had been modified (intentional short - which was not present on the eBay pics).
As you can imagine, I did not think to thoroughly check it before inserting the controller in the VLB slot, so I destroyed a Biostar MB1433 motherboard and the Intel 486DX2-66 CPU.
Suffice to say that there was not much that eBay could do about it (I did get my $7 back - yey! 🤣 ).

At least I delidded the CPU and got some nice pics out of it (I think the small round black spots that are visible in the second pic are probably caused by the short):

The pictures are nice but what an asshole of a seller!😡

I did some experiments last evening, to see how far I could push the FSB on these K6-2+/570. 😀
Motherboard is a FIC VA-503+, used 2 sticks of PC133 SDRAM (256MB total), and a Gf2GTS video card which I know from previous experiments works on an AGP of 83MHz. Also a 4GB CF card with Win98 freshly installed. I tested for stability by running 3DMark 99 and 3DMark2000 at least twice each in a row. Voltage was the default 2V.

95MHz x6 (default for the CPU): boots and rock stable
100MHz x6: boots but some programs crash; sometimes Win98 freezes during booting.
100MHz x5.5: boots and rock stable
112Mhz x5: boots and rock stable
124MHz x4.5: no POST
124MHz x4: POSTs OK, but Win98 freezes during booting.

(and of course, the highest scores it got in the benchmarks were at 112x5) Note that at none of these settings was I overclocking the CPU (kept it between 550 and 570MHZ), only the FSB was overclocked.

stamasd wrote on 2022-02-15, 11:56:

Voltage was the default 2V.

So it looks like 600Mhz is out of reach at 2V. Are you thinking about trying again with a higher voltage?

douglar wrote on 2022-02-15, 14:47:

stamasd wrote on 2022-02-15, 11:56:

Voltage was the default 2V.

So it looks like 600Mhz is out of reach at 2V. Are you thinking about trying again with a higher voltage?

I’ve noticed that sometimes the motherboard is to blame for crappy core overclocks. Try replacing all the capacitors

The 570 should do 100x6 600 easy.

I even had it where the cpu wouldn’t go over a specific mhz until I updated the bios of all things…

douglar wrote on 2022-02-15, 14:47:

So it looks like 600Mhz is out of reach at 2V.

Not at all!
Hirsch has one which can run 6x100MHz at 1.85V!

RaiderOfLostVoodoo wrote on 2022-02-15, 16:48:

douglar wrote on 2022-02-15, 14:47:

So it looks like 600Mhz is out of reach at 2V.

Not at all!
Hirsch has one which can run 6x100MHz at 1.85V!

I think that statement was in regard to that individual chip not being able to reach 600MHz @2V.
Would be nice to test through a large batch to find golden samples.😃

Maybe that guy has gone through all 27,000+ and picked out the good ones 🤣

Note that I'm not trying to overclock the CPU. The goal of this experiment was to find how far I can push the FSB at default voltage.
Or else I'd be pushing voltages, install monster Peltiers etc

In the end I want to run a series of benchmarks to see exactly how much a higher FSB contributes to performance, all other things being equal (including as much as possible the CPU clock)

stamasd wrote on 2022-02-15, 20:28:

Note that I'm not trying to overclock the CPU. The goal of this experiment was to find how far I can push the FSB at default voltage.
Or else I'd be pushing voltages, install monster Peltiers etc

6x100MHz isn't overclocking? You seem to have a strange definition of overclocking.
Overclocking isn't overvolting. Overclocking does often involve overvolting, but doesn't necessary have to.

Hey, I've been overclocking since the days of the Celeron 300A. But this time I decided not to. Yes 6x100 is an overclock but a tiny one. Nothing compared to 300->504 on the 300A. 😀
It was just to see what kind of CPU I got and how compliant it was going to be with other things I was going to do to it.

I wouldn't call it overclocking really either, it's still 570mhz +/- 10% 😜

stamasd wrote on 2022-02-15, 11:56:

I did some experiments last evening, to see how far I could push the FSB on these K6-2+/570. :) Motherboard is a FIC VA-503+, us […]
Show full quote

I did some experiments last evening, to see how far I could push the FSB on these K6-2+/570. 😀
Motherboard is a FIC VA-503+, used 2 sticks of PC133 SDRAM (256MB total), and a Gf2GTS video card which I know from previous experiments works on an AGP of 83MHz. Also a 4GB CF card with Win98 freshly installed. I tested for stability by running 3DMark 99 and 3DMark2000 at least twice each in a row. Voltage was the default 2V.

95MHz x6 (default for the CPU): boots and rock stable
100MHz x6: boots but some programs crash; sometimes Win98 freezes during booting.
100MHz x5.5: boots and rock stable
112Mhz x5: boots and rock stable
124MHz x4.5: no POST
124MHz x4: POSTs OK, but Win98 freezes during booting.

(and of course, the highest scores it got in the benchmarks were at 112x5) Note that at none of these settings was I overclocking the CPU (kept it between 550 and 570MHZ), only the FSB was overclocked.

We're mobo-buddies! I have the same motherboard. Based on my research, I was going to set this cpu at 2x with 100mhz fsb for 600mhz. Is it ok if I use you as a resource in case I run into trouble?

Even at 600mhz it's not exactly a PIII 600mhz by any stretch. It might be eqiuvelent to a 450Mhz PII with slower FPU. Probably slower considering a BX chipset is so much faster than a VIA ss7 chipset.

BitWrangler wrote on 2022-02-14, 20:57:

Also a screenshot of your 3Dmark 2000 at 1024x768 is gonna be needed if we're going to address that at all.

If a picture is worth a thousand words, then a video is equivalent to all of the "Lord of the Rings" books. 🤣
VIDEO BENCHMARKS (Original title: Settling the VIA C3 performance debate once and for all)

The aiming for the stars thing is fake btw. Theres a bug in the very specific nvida driver version when its run on a K6 that cause the score of 3dmark to be high. But in reality if you use like quake as the benchmark its still the same shitty cpu.

Warlord wrote on 2022-02-16, 07:26:

The aiming for the stars thing is fake btw. Theres a bug in the very specific nvida driver version when its run on a K6 that cause the score of 3dmark to be high. But in reality if you use like quake as the benchmark its still the same shitty cpu.

I’m really curious how my new ti500 (if I can get it to work) will do in halo.. it’s very similar to the actual gpu that halo was designed for.

Sphere478 wrote on 2022-02-16, 07:54:

I’m really curious how my new ti500 (if I can get it to work) will do in halo.. it’s very similar to the actual gpu that halo was designed for.

Halo... on a K6-2/3(+)? 😀
Well, don't expect any miracles, I can tell you that. 😁
IIRC, that one is only playable on 1 GHz Pentium 3/Athlon (and that's "playable" by old, not modern standards). You probably want at least an Athlon XP/Athlon64/Pentium 4 for 60 FPS or above 😁
Playing it on a K6 will be a pain (which might be enjoyable if you're a masochist 🤣 )

Anyway, I'm the one to talk... Back in the day, I played half of Return to Castle Wolfenstein on a normal K6-2 500 (this was the game that made me upgrade to a Thunderbird 1.33 GHz - BY FAR the biggest perceived speed jump that I got with any upgrade ever since).

bloodem wrote on 2022-02-16, 08:08:

Halo... on a K6-2/3(+)? :-) Well, don't expect any miracles, I can tell you that. :-D IIRC, that one is only playable on 1 GHz P […]
Show full quote

Sphere478 wrote on 2022-02-16, 07:54:

I’m really curious how my new ti500 (if I can get it to work) will do in halo.. it’s very similar to the actual gpu that halo was designed for.

Halo... on a K6-2/3(+)? 😀
Well, don't expect any miracles, I can tell you that. 😁
IIRC, that one is only playable on 1 GHz Pentium 3/Athlon (and that's "playable" by old, not modern standards). You probably want at least an Athlon XP/Athlon64/Pentium 4 for 60 FPS or above 😁
Playing it on a K6 will be a pain (which might be enjoyable if you're a masochist 🤣 )

Anyway, I'm the one to talk... Back in the day, I played half of Return to Castle Wolfenstein on a normal K6-2 500 (this was the game that made me upgrade to a Thunderbird 1.33 GHz - BY FAR the biggest perceived speed jump that I got with any upgrade ever since).

it's actually playable on k6-3+ 600 with radeon 9800 pro and this freeway mobo

I'm now attempting to set up the freeway ultra version of the mobo and a gf3 which I'm hoping will be faster

Sphere478 wrote on 2022-02-16, 08:44:

it's actually playable on k6-3+ 600 with radeon 9800 pro and this freeway mobo

I'm now attempting to set up the freeway ultra version of the mobo and a gf3 which I'm hoping will be faster

I guess that, as always, "playable" is in the eye of the beholder. 😁
In this day and age, for me "playable" means somewhere around 45 FPS average, with 1% lows that should stay above 25 - 30 FPS.
During my younger years, playable for me was 15 - 20 FPS AVG, and I would even tolerate dips below 10 FPS. Those were the days...

bloodem wrote on 2022-02-16, 11:31:

I guess that, as always, "playable" is in the eye of the beholder. :-D In this day and age, for me "playable" means somewhere ar […]
Show full quote

Sphere478 wrote on 2022-02-16, 08:44:

it's actually playable on k6-3+ 600 with radeon 9800 pro and this freeway mobo

I'm now attempting to set up the freeway ultra version of the mobo and a gf3 which I'm hoping will be faster

I guess that, as always, "playable" is in the eye of the beholder. 😁
In this day and age, for me "playable" means somewhere around 45 FPS average, with 1% lows that should stay above 25 - 30 FPS.
During my younger years, playable for me was 15 - 20 FPS AVG, and I would even tolerate dips below 10 FPS. Those were the days...

Workin with 15+ usually, spurts to 40 dips to 1

I don’t have a fps counter but that’s my guess.

Made it from the pillar of autumn past the truth and reconciliation.