Super PSJOY USB adapter causing black screen in Zsnes

[Transen]

When I have my Super PSJOY adapter plugged in and start ZSNES Windows version (1.51), all I get is a black screen (a windowed black screen if it was set to start in windowed mode and in full black screen if set to start in fullscreen mode).

If I Ctrl+Alt+Delete my way out of Zsnes, unplug the adapter, then restart Zsnes, it runs fine.

If I start Zsnes first and then plug in the adapter, it runs fine but the controller I have hooked up through the adapter doesn't register within Zsnes. I'm using a standard Playstation 2 dualshock controller with the adapter





------------------
System Information
------------------
Time of this report: 1/21/2008, 16:57:31
Machine name: LUNARIS
Operating System: Windows XP Professional (5.1, Build 2600) Service Pack 2 (2600.xpsp_sp2_qfe.070227-2300)
Language: English (Regional Setting: English)
System Manufacturer: Dell Inc.
System Model: Dell DM061
BIOS: Phoenix ROM BIOS PLUS Version 1.10 2.0.5
Processor: Intel(R) Core(TM)2 CPU 6300 @ 1.86GHz (2 CPUs)
Memory: 2046MB RAM
Page File: 483MB used, 3454MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 9.0c (4.09.0000.0904)
DX Setup Parameters: Not found
DxDiag Version: 5.03.2600.2180 32bit Unicode


---------------
Display Devices
---------------
Card name: Radeon X1300/X1550 Series
Manufacturer: ATI Technologies Inc.
Chip type: ATI Radeon Graphics Processor (0x7183)
DAC type: Internal DAC(400MHz)
Device Key: Enum\PCI\VEN_1002&DEV_7183&SUBSYS_03021028&REV_00
Display Memory: 256.0 MB
Current Mode: 1024 x 768 (32 bit) (75Hz)
Monitor: Plug and Play Monitor
Monitor Max Res: 1600,1200
Driver Name: ati2dvag.dll
Driver Version: 6.14.0010.6734 (English)
DDI Version: 9 (or higher)
Driver Attributes: Final Retail
Driver Date/Size: 11/1/2007 20:09:00, 268288 bytes
WHQL Logo'd: Yes
WHQL Date Stamp: n/a
VDD: n/a
Mini VDD: ati2mtag.sys
Mini VDD Date: 11/1/2007 21:52:04, 2644480 bytes
Device Identifier: {D7B71EE2-32C3-11CF-D669-0823A1C2CB35}
Vendor ID: 0x1002
Device ID: 0x7183
SubSys ID: 0x03021028
Revision ID: 0x0000
Revision ID: 0x0000
Video Accel: ModeMPEG2_C ModeMPEG2_D ModeWMV8_B ModeWMV8_A ModeWMV9_B ModeWMV9_A
Deinterlace Caps: {6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{3C5323C1-6FB7-44F5-9081-056BF2EE449D}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{552C0DAD-CCBC-420B-83C8-74943CF9F1A6}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
Registry: OK
DDraw Status: Enabled
D3D Status: Enabled
AGP Status: Enabled
DDraw Test Result: Not run
D3D7 Test Result: Not run
D3D8 Test Result: Not run
D3D9 Test Result: Not run

-------------------
DirectInput Devices
-------------------
Device Name: Mouse
Attached: 1
Controller ID: n/a
Vendor/Product ID: n/a
FF Driver: n/a

Device Name: Keyboard
Attached: 1
Controller ID: n/a
Vendor/Product ID: n/a
FF Driver: n/a

Device Name: PSX/USB Pad Adaptor (4-axis, 12-button, POV,effects)
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x0190, 0x0028
FF Driver: psxff.dll
FF Driver Date:
FF Driver Version: 1.00.0000.0000
FF Driver Size: 0 bytes

Poll w/ Interrupt: No
Registry: OK

[odditude]

Does the adapter work without the bundled drivers that came with it? Usually they're only necessary for the force-feedback (rumble) support.

[Transen]

Not sure. I've tried uninstalling it from the Game Controller window in Control Panel and it tells me I need to remove it from the device manager.

So I go to the Device Manager and remove both USB interfaces that deal with the controller's functions.

At this point, I try to use the controller within Zsnes but it doesn't read any input from the controller.

I then disconnect and reconnect the controller but Windows automatically reinstalls the drivers which of course, causes the original problem when starting Zsnes up.


**Edit: Hold that thought**
I don't know where the dll files the bundled drivers for the adapter are being installed to nor can I find any info in regards to what the name of the drivers are (yes, I checked in device manager for driver information).
**Edit: Hold that thought**

One thing I did notice while I was looking in the Game Controllers window in control panel was that when I clicked on properties, then click on the tab for rumble control, I get a rundll32.exe error.



*Afterthought*

Removed the hardware again in Device Manager, deleted "psxff.dll" from system32 directory along with another file right next to it that is associated with the adapter. Then unplugged and replugged in the adapter, it's using some file I missed but not the ones I deleted. The properties window off of the game controller window is different now but functional and the controller works in Zsnes windows again.

[odditude]

I would check with the manufacturer for updated drivers; if none exist, at least the pad works now.

[Palin]

I have a PSJOY controller adapter, the drivers are incredibly dodgy. I would stick with the default windows game controller interface since it does everything except force feedback. Besides, I never had the force feedback work correctly using the manufacturer's drivers anyhow.