Well, it sounds like it is your SB gameport that makes the resource collision.
You have tried disabling the SB gameport? I am using a PDPI and a PCI64 myself,
works like a charm. I'm not sure if I turned off the gameport of the SB by hand
or if the PDPI installer did it for me. I think I did it by hand and rebooted
before I installed the PDPI.
If this don't work, you can try removing the sound card altogether from the
computer, install the PDPI and make sure it works properly, then install the SB
card (pysical and drivers). Windows should mark the gameport address as used,
and certainly should not allocate it to the SB gameport. After installing the
SB, you should have a red cross on the gameport of the SB card.
And there is a small testprogram to report if the PDPI is working or not, it is
in the L4 folder in your Program Files folder. I think it was called
testport.exe.
---Asgeir---
> Okay, Okay, I've followed all the instructions but I'm having a problem
> installing my new PDPI L4 Game card into my Gateway G6-450 PC.
> The problem is that I can either enable my PDPI game card or my Soundblaster
> PCI 64D soundcard, but never both at the same time.
> If I disable the soundcard the PDPI L4 works perfectly, (with my Nascar
> Pro/separate pedals), and vice -versa.......
> I have checked the input/output resource ranges for these devices in the
> device manager, (1040 - 107F for the sound card and 0201-0201 for the PDPI
> L4), and there appears to be no conflict.
> Whatever input/output range I select for my soundcard, it still knocks out
> my game controller.
> Any help anyone can give would be greatly appreciated.
> SteveG
