Spider2 freezes amiga

[amipower]

Hi all,

My current setup:

Amiga 1200 kickstart 3.1 (with timing fixes, 1d4)
Mediator LT 4
Voodo banshee
SB 128
Spider 2 USB
Apollo 1230@40Mhz with 48MB RAM
Buffered IDE device
CF 4GB and DVD ROM
Modern ATX PSU.

PCI slots:
1: is empty
2: GFX
3: Spider
4: SB

OS 3.9 BB1,2 and 3
MMCD and latest update have been installed
Spider.device v3.22 and Poseidon 4.4
Picasso96 2.1c Alpha

MMU=yes
voodoomem=13 (tried many settings)

Als long as I do not initiate/start Trident to configure the Spider USB, the amiga works fine. As soon as I connect a USB device it takes 10 sec, to a minute before the amiga freezes completly.

Any tips or hints?

[amipower]

I haven't gotten any further with this. Any hints or tips?

[amipower]

genuine one.

[amipower]

Still no go. As soon as I start to use any device on the mediator it starts to act up. (I thought it was the spider2, but it only speeds up the hanging issues).

[amipower]

Thanks for the advise. I bought the mediator and the spider 2nd hand. Do not now if I will get support.

However I have had some progress in stability.

I removed the SB128 and set Warp3D to no in my envarc. It seems to work much more stable now. I also changed the voodoo mem from 12 to 13 again.

I still freezes, but I can use it for minutes now (10 to 15).

I places back the SB128 and now the freezing issues ar back immediately.

[amipower]

I use a SB128 in my setup with no issues, but mine is A4000 based.

PM me your email address if you like and I'll send you the Spider driver I'm using (I found it on my laptop).

Pm send.

I use v3.22.

What i did notice was, that on the MMCD a serial number is handwritten. De new driver on fdisk has also a sn written on it. But the numbers do not match at all. Could that mean anything?

[amipower]

Well, I installed the driver and poseidon stack, but still the same issue.

After a few usb mousemovements the system freezes.

I did try a decent 500 watt atx psu, but still the same problem.

Grrr...

Edit:

I noticed a slight change in trident. It now tells me that I m not using the right input.device v50 and that I might experience some oddities. Duh!!

Will try this input.device v50 And see what happens.

Edit 2: can't find input.device at all.