I'm having problems installing a Motu PCI card. The card is recognized in the device manager, where it says it's working, but when trying to open the Motu console or cuemix I get a message saying either that "the card probably is faulty" or that "there is not enough memory to perform the operation" (the computer has 512 mb ram. I've tried with 3 different Motu cards and 2 different motherboards (Abit KT7A and ASUS A7V) with the same result. It worked fine installing it on a computer with a Microtech VIA 133 mb. Ideas anyone? Best regards Bauer

--- In logic-users@y..., Andreas Bauman <bauer@a...> wrote: > I'm having problems installing a Motu PCI card. The card is > recognized in the device manager, where it says it's working, but when trying to open the Motu console or cuemix I get a message saying either that "the card probably is faulty" or that "there is not enough memory to perform the operation" (the computer has 512 mb ram. I've tried with 3 different Motu cards and 2 different motherboards (Abit KT7A > and ASUS A7V) with the same result. It worked fine installing it on a computer with a Microtech VIA 133 mb. > Ideas anyone? Oh boy, I hope you are a tweakhead, ;-). The VIA chips seem to cause troubles for some while it works ok with others. You mention it worked fine with a Microtech VIA 133 motherboard. Why not use that then? If not then here I have a long story from someone from the Pulsar-Scope mailing list(very informative post): "Hi there fellow Pulsrians, Pulsar II doesn't work reliably on VIA chipset motherboards right? WRONG!! Here's how this sick little puppy convinced his Pulsar II card to run reliably on a MSI 694D Pro motherboard alongside a SCSI card and a Delta1010 audio card. The MSI 694D Pro mobo uses the Apollo Pro 133a Chipset. When I first installed the Pulsar II card it would only run in the first 3 slots. It seemed fine until I pushed the DSP usage over 25%. Then I would be harrassed by "PCI-Master Overflow" messages. If I pushed the DSP to 75% I would get an error every 30 seconds or so. I had tried everything. BIOS settings, slot juggling, RAM & software tweaking. Nothing seemed to help. In fact most BIOS changes made it worse. Finally I remembered the utilities I was already using to tweak my RAM settings. This pair of utilities, called 'Wpcredit' and 'Wpcrset' allow you to alter the chipset registers themselves, much the same way the BIOS does. I used these utilities to change 2 registers. These are: "Arbitration Mechanism Priority" changed from CPU/PCI to PCI, and "PCI-Master Read Caching" changed from disabled to enabled. Either of these 2 settings on their own fixed the problem! I enabled both. After changing these registers I could run Nuendo at 75% CPU plus PulsarII at 95% DSP (mostly reverbs). If I push the computer CPU any more than 75% windows becomes very sluggish. This does NOT occur in Win2000 with dual CPU (Creamware where are those Win2000 drivers???) I left the computer looping like this for 12 hrs without one error!! Instructions on how to use these 2 utilities can be found at http://viahardware.com/memtweakguide1.shtm These instructions are for tweaking memory settings, but they will explain how to use the utilities. The utilities can be downloaded from http://hp.vector.co.jp/authors/VA002374/src/download.html You will have to also get the correct WPCREDIT PCR Files for your motherboard chipset. The WPCRSET program can still be obtained at ftp://ftp.vector.co.jp/pack/win95/hardware/other/wpcrs120.exe The registers I changed for Apollo Pro 133a Chipset were: Register: 70 HEX: 44 (PCI-Master Read Chaching > ENABLED) Register: 75 HEX: 21 (Arbitration Mechanism Priority > Change from CPU/PCI to PCI. Remember EITHER of these changed registers fixed the problem on my motherboard. For different manufacturers and different VIA chipsets these register & HEX numbers may be different. You will have to use WPCREDIT to find the registers called 'PCI-Master Read Chaching' and 'Arbitration Mechanism Priority' and change them as required. You can change registers in WPCREDIT while windows is running, which makes tinkering very easy. Once found, you should enter these settings into WPCRSET, then they will be autoloaded every time windows boots. I know this seems complicated. Truthfully this tweak ISN'T for the PC newbie. By changing the wrong registers you may even damage your motherboard (although unlikely). If in doubt get a friend to help, or email me if you must at reaktor@m... . In my case I wasn't ready to throw away a dual P3 866 plus motherboard without exploring all possibilities. Besides, if you can work out the Pulsar environment you should be able to use these utilities. By the way, the fact that changing 'Arbitration Mechanism Priority' from CPU/PCI to PCI fixes the problem tells me that this problem has more to do with the way the VIA chipset controls the PCI bus, rather than being a PCI BUS bandwidth problem. The PCI devices themselves obviously have a better idea of how to run the bus than the VIA chipset does. I hope this can be of help to some of you using VIA chipset motherboards. Your fellow Pulsarian, trying to make the road a little less rocky, Spliffy." Hope this can help your problem. Regards, Yoonchi.