Cool, always wanted one of those rare dual P1 systems (or even rarer dual 486).

2 things.

Please tell me your jumper settings, I was under the impression that 200 non-mmx was the fastest this board would take.

Would you be kind enough to run a speedsys benchmark and post the result? thanks!

due to some changes in the split voltage but staying on 66 mhz bus allows the 1.5x multiplier to be interpreted as 3.5x for MMX processors 😎

I've finally been able to do some rounds of testing:

p233 dual HX results

Cachechk W: 92,9
Cachechk R: 88,2
Speedsys Throughput: 85,42
Speedsys R: 80,73
Speedsys W: 85,31

Strangely, the writing speed is higher than the read speed.

The system beats my dual Ppro Overdrive on these memory write results. The PR440FX is faster on reads (about 100MB/s) but puts down a poorly 70 MB/s on the speedsys reads.

I have a similar board running. So do you have problems with the Linear Voltage Regulator overheating after about half an hour if you push both P233MMX in NT4 f.e.
I also noticed the problem that with a full memory setup, EDO RAM produces memory errors if accessed from CPU 1. You can't detect this with memtest86, as it runs on CPU0 only.

elianda wrote:

I also noticed the problem that with a full memory setup, EDO RAM produces memory errors if accessed from CPU 1. You can't detect this with memtest86, as it runs on CPU0 only.

wait... WHAT? Do you have any more data on this? I benched mine because I kept getting random memory errors during mem-test86 (smp version).

I came to the conclusion that I had a bad memory socket and was going to replace them all one day. Please tell me you have more information.

Well actually I got the board fully equipped with 256 MB, Bank 1,2 with EDO and 3,4 with FPM DRAM.
So I changed the FPM to EDO DRAM, memtest86 was good (non SMP), DOS etc. ran fine too.
But as soon as I installed NT4 and it booted up first it went quickly BSOD. The typical random BSODs that point to memory errors.
It actually took me a while to realize that this must be a memory error on CPU 1, while memtest86 showed that everything was working nicely.
Then a rather tedious testing started with changing memory, starting NT4, changing memory timing, starting NT4... (a bit more than a week at least)
In the end it worked out for me, that the original config with split EDO/FPM was on purpose, because it worked. So someone who setup the system originally must have known of this issue.
It is a Tyan S1563 with two P233MMX.

For that system I'd be more likely to go with Windows 2K than NT. 2K raises the bar for DirectX support all the way to DX9, making a larger number of video cards available for use. You'll be stuck with using the DX5 beta release with NT 4. I am using 2K on my dual PPro machine and it's not heavy on that system.

WOW thats rare and i have never seen a P1 Duel cpu system before and i use http://imageshack.us/a/img96/3053/20130320171509.jpg

My Socket7 system has a similar Tyan board in it:

The very good Socket 7 system!

the question on my mind is what os you will run? i'm certain it had some form of linux or unix on it back the day, oooohh or some sort of sunmicrosystems os. did they even have windows server back then?

elianda wrote:

Well actually I got the board fully equipped with 256 MB, Bank 1,2 with EDO and 3,4 with FPM DRAM. So I changed the FPM to EDO D […]
Show full quote

Well actually I got the board fully equipped with 256 MB, Bank 1,2 with EDO and 3,4 with FPM DRAM.
So I changed the FPM to EDO DRAM, memtest86 was good (non SMP), DOS etc. ran fine too.
But as soon as I installed NT4 and it booted up first it went quickly BSOD. The typical random BSODs that point to memory errors.
It actually took me a while to realize that this must be a memory error on CPU 1, while memtest86 showed that everything was working nicely.
Then a rather tedious testing started with changing memory, starting NT4, changing memory timing, starting NT4... (a bit more than a week at least)
In the end it worked out for me, that the original config with split EDO/FPM was on purpose, because it worked. So someone who setup the system originally must have known of this issue.
It is a Tyan S1563 with two P233MMX.

This is curious. I've noticed many pre-millennium boards don't like to have their memory size maxed out or have all banks filled and use fast timings- as if the chipset cannot cope. For your system, do you get errors in NT4 if you fill all banks with, say, only 8 MB EDO sticks? Also, what happens if you use only 4 sticks of 64 MB EDO for 256MB total, or 4 sticks of 64 MB FPM, or 8 sticks of 64 MB FPM, or how about just 2 128 MB EDO sticks? That last option is probably unsupported.

I experienced strange behaviour when I tried running a dual CPU setup with the S1562 board.
Running one CPU with cache module installed --> no problems
Running two CPUs with cache module not installed --> no problems
Running two CPUs with cache module installed --> permanent lockups and freezes

After some research and digging around in some old newsgroups I figured out that TYAN equipped some of these boards with incompatible cache modules. The only module that works with a dual processor setup on this board is called "S1543-PCB-04" !

That must be irritating!

Hi, I'm really keen to understand the jumper settings you used here.
Are you sure you not using the S1564 ? that has VIO ?
I can't get my Single S1562 to post at 233 for my 233mmx with any combination of jumpers.
Can you share some more info if you are still active?

I hope I am allowed to resurrect this old topic.

I've recently pulled out the MB from storage to test and install Windows 2K on a CF-to-IDE.

As I haven't installed an OS before, the system's slowness only recently became apparent. Turns out the 512kb COAST cache module is either dead or not recognised by the system. Any ideas how to test what is wrong? I'd like to have this as a working system. Although the install in the end went without any hiccups, and the system is stable with the 128 MB of ram and both P233MMX, it is too slow due to the L2 cache being absent.

Slow replies, my apologies:

- Settings for the dual P233MMX to be detected are:

J13: 1-2
J19: OFF
J20: OFF

I suppose you also need the latest BIOS. On the board I have V4.02 is installed (V4.02 - 07/09/098-i430HX-2A59FT59C-00).

- Update on the cache question.

The COAST module S1543-PCB-04 is not faulty, it simply does not make proper contact anymore in the slot where it is seated. With some fiddling, I managed to find a position in which the module is at least detected at boot.

Windows 2K (vanilla installation) is not stable with the cache detected at boot. It boots, but with all sorts of .exe crashes after which the system usually self-reboots. Without the cache module, the system is stable, but very slow as you can imagine.

I suppose a system does not like it when the L2 cache is suddenly disappearing and that this causes the .exe errors?

Update, fixed the issue with the COAST module more or less by a thread:

CPU-0 gets 219 on Integer and 135 on Floating
CPU-1 gets 209 on Integer and 136 on Floating

System seems to behave now with the cache all bound up.

I love it!