Communication error

An area for people to discuss Scope related problems, issues, etc.

Moderators: valis, garyb

Post Reply
synthetic
Posts: 159
Joined: Tue Oct 12, 2004 4:00 pm
Location: Sweden
Contact:

Communication error

Post by synthetic »

Nowdays I have got a lots of communication errors with my Pulsar2 and SRB (15 DSP) card. I have re-installed the computer a couple of times with same result.
Using both XP SP1 and SP2. Installed as ordinary XP, not as Standard PC.
If I press "...reloading DSP" it continues to load the plug but there is no sound for that plug. Mostly it is PRO-12 which does not work.
Have re-installed only PRO-12 too.
Not a big project either, STM1632 and PRO12 gives me 7.1% load in just one DSP of totally 21 DSP!!!!


I have fiddles around with different settings in cset.ini (all combos, both "empty") with same result.
It has worked before. I have removed the cards and STDM-cables to get rid of oxide too.

I have NOT tried to move PCI-slot yet, because of space in box.

My system is:
Asus P4P800-E Deluxe, I865PE, 2Gb RAM, Pulsar2, SRB, a lots of harddisks. EMU 1820M.

The Device manager telling me that Firewire (IE1394) shares the same IRQ, I have no connected HW to FW but I sometimes use it to my DV-cam.

Someone elso who have similar problem or a solution?
Attachments
Error message
Error message
1.JPG (16.53 KiB) Viewed 1243 times
Device Manager
Device Manager
2.JPG (79.14 KiB) Viewed 1243 times
CarvinGuitarFreak
Posts: 130
Joined: Wed Sep 20, 2006 4:00 pm

Post by CarvinGuitarFreak »

Hi synthetic,

I had some problems recently but not this one for a while, I reset everything and done the following... dont know if this will helps

1. Cleaned all contacts, reseated cards, fresh install (and replaced PSU?)
2. No sharing IRQ with anything... switch off any you arent using
3. PCI latency of graphics reduced to 92 or 128 (using doubledawg)
4. Increase PCI latency to 128 in bios

I think thats all.... these are the tips from planetz dwellers I recieved

Good luck
CGF
User avatar
garyb
Moderator
Posts: 23380
Joined: Sun Apr 15, 2001 4:00 pm
Location: ghetto by the sea

Post by garyb »

the FW controller shared with scope probably isn't a problem when you're not using fw and scope at the same time, but you'll probably want to move the card to another slot to try and get an unshared irq. there may be other devices to disable such as some of the extra usb controllers, but only if they conflict. the FW that is shared looks like one of 2. if itr is, just disable it and use the other FW port(looks like a FW card as well as a port on the motherboard).

if that message only comes up occasionally, i'd just do the reset and continue. a restart would likely help as well.
synthetic
Posts: 159
Joined: Tue Oct 12, 2004 4:00 pm
Location: Sweden
Contact:

Post by synthetic »

Have tried to move the cards with same result, it is ONLY when I try to load PRO-12 I got this error message, strange.

I tried to fill the DSP-power up with other devices such as:
- Modular3 (Kaegi synth)
- NordXTC
- Modular3 (OB-X)
- Modular3 (Poly wave synth)
- EDSI16i
- Minimax
- Prodyssey
- WC Pro-One V3
- ProTone
- Lightwave
- SB404
- Sixstring

And the DSP-power is now red, but no error message whatsoever, only PRO12 causing this and my Prohpet-Plus, seems that those plugs using some strange resources, anyone knows?
User avatar
astroman
Posts: 8455
Joined: Fri Feb 08, 2002 4:00 pm
Location: Germany

Post by astroman »

maybe the disk file is corrupted or the project contains some garbage related to the Prophets ? Can't remember a problem with one of them ...

cheers, Tom
synthetic
Posts: 159
Joined: Tue Oct 12, 2004 4:00 pm
Location: Sweden
Contact:

Post by synthetic »

Now it's working again, seems that a DSP-file was corrupt, hope the fault will not return again. Now it's time to do some test on Wine Country's Pro-One V.3 which I borrowed from John last week. It has both SSM, CEM, Minimax and "ordinary" filters.
Post Reply