Been posting on anyone running protools thread for a while.
I have successfully configured a hackintosh, running Protools HD 8.0.3 with 1 PCI Core and 1 PCI Accel card. I made a stress test session with 72 stereo tracks, some 40 TDM plugins and over 60 RTAS plugins. Although Protools is pretty loaded, the CPU isn't really bothered with any of it. Only drawback was the harddrive not able to deal with the load on the I/O on loop cycle (get a drive with higher than normal burst ratio). Solid as a rock.
Alot of people seem to be skeptic, because 'DigiDesign' states that it does not work. I do not blame anyone for being skeptic, but a little internal computer knowledge before stating anything would be very appreciated
First of all, localization of hardware (interupt requests) is done by the BIOS, not the OS. This does not differ from any Macintosh. The drivers written to communicate with some protocol, aren't written to specifically communicate with a slot (let it be VESA, ISA, PCI, PCIe), they are written to communicate with a certain hardware layer.
-- edit
Unless of course, the manufacturer has specifically put some eprom, or whatever rom to recognize the slot, therefor the driver could decide to work, or not. But in many cases this is just some luxury overhead many manufactures do not really care about and do not implement unless the card is made for some specific performance issue, and requires therefor some sort of detection mechanism.
--
To make things worse for a computer. If a PCI slot and a PCIe slot share the same bus (which in most cases is a fact) the driver doesn't even know in which slot the card is in. This might sound very stupid, but it's a fact. There is only one communication channel to the bus, not every slot has it's own bus with it's personal communication channel. You can read the problems some people have when they have this specific order of which card goes into which slot in order to get the system stable and work properly. This is the side effect of sharing a bus over several slots. Although bus sharing is not the real problem, the driver written to communicate with the card could get in trouble when more cards are calling the same communication line (bus) and the company/programmers/idiots didn't properly write the driver to distinct the two. You can write a driver (which in most cases on every University is a standard procedure for students who start writing abstraction layers for hardware) where you claim the bus for just one card. Most test cases only have one card (the test card) and therefor, they never run into any trouble. Until you put a ethernet card on the shared bus, and you'll at some point, notice instability.
I could go on and on about this topic, but I won't
The VirtuaVia (or any expansion company, Magma, Cyclone, etc) PCIe => PCI expansion, unless the expansion (or any expansion) was poorly designed, which would make it impossible/improbable for the BIOS to detect any hardware, shares the same principle.
The PCIe bus get's shared over multiple PCI's. In theory, if the PCI cards work on a shared bus locally (mainboard) on the computer, they should work on the shared bus in the PCIe expansion. The principle is the same because if the expansion is a 4x PCI to 1 PCIe slot, you share 4 PCI's on one PCIe bus. If the PCIe bus is again locally (mainboard) shared with another slot, and this one is filled too, you are just asking for trouble.
Always check the specifications of your motherboard how the setup of the busses are configured. Every mainboard has one
A VirtuaVia PCIe => 4x PCI ATX expansion kit (24v ATX connector) is on it's way from france. Will post some detailed tests and performance issues when it arrives.
-- edit
It arrived and worked, check post below
--
Cheers



Sign In
Create Account














