Well subhuman's update seems promising, and the word that i've been hearing is that mpx increases pci bandwidth again (although it still uses pci only for the nort/south connection thereby reducing bandwidth again).
I think i'm going to go xeon tho, unless someone can confirm that pulsar works well with mp real fast. I simply need to write music, even if it means throwing money at the issue.
Tiger MP
Well if your only problem was the PCI error, then it is definitely your Tyan board, Havoc, because it's 100% GONE with our new Tiger rev1.03. And guess what? No copyprotectionviolation errors at all yet.
This is under WinXP, LunaV3.01, ACPI MultiProcessor.
In fact it was almost <i>too</i> easy to install and get it working! I'll update with more info as I find out more.
Note to Havoc: if you can, RMA your Tiger for the new revision (or as you're trying now, RME it
)
This is under WinXP, LunaV3.01, ACPI MultiProcessor.

Note to Havoc: if you can, RMA your Tiger for the new revision (or as you're trying now, RME it

I should amend that to 'parts for a new machine' in general. I'm still too wary of the MP/MPX chipset until I hear more positive reviews from the Pulsar camp...(or Scope/Luna yadda yadda).
But I will have to admit that having an entire machine built for the cost of the xeon mobo/1 proc/memory is certainly attractive.
Btw, current scuttlebutt is that the Asus MPX is shipping with USB 2.0 cards as the USB on the MPX chipset is having problems...
http://www.theinquirer.org/17120108.htm
Just a heads up...
But I will have to admit that having an entire machine built for the cost of the xeon mobo/1 proc/memory is certainly attractive.
Btw, current scuttlebutt is that the Asus MPX is shipping with USB 2.0 cards as the USB on the MPX chipset is having problems...
http://www.theinquirer.org/17120108.htm
Just a heads up...
Yep, only got the pci error. Only with some tweaks I got the copyprotectionerror.
I will try it, but as the problem is only with one, to be honest quite obscure card (look at it as a hardware dealer), I doubt they will change it. They will just argue that as the board works fine with every other card you use, it must be the card that's faulty. I know I would do the same if I were in the shop.
I will try it, but as the problem is only with one, to be honest quite obscure card (look at it as a hardware dealer), I doubt they will change it. They will just argue that as the board works fine with every other card you use, it must be the card that's faulty. I know I would do the same if I were in the shop.
Well Havoc, if you're saying you're not sure you can RMA the board, I'd suggest going back to the 2cpu forums and gathering a list of things wrong with the pre-rev1.03 boards and using those as your reasons.
Not *entirely* ethical, but when I need IRC to work calling tech support and telling them that realplayer is having QOS problems with rtsp links due to an inability to communicate over ports 6540-7100. *Viola* ports 6667-7000 open ;]
Doubtful I'd get the same response if I called up "Ummm, like, my homies are all on this chat thing called irc..."
Not *entirely* ethical, but when I need IRC to work calling tech support and telling them that realplayer is having QOS problems with rtsp links due to an inability to communicate over ports 6540-7100. *Viola* ports 6667-7000 open ;]
Doubtful I'd get the same response if I called up "Ummm, like, my homies are all on this chat thing called irc..."