major gameports bug

darkthorn · Apr 30, 2003, 04:26 PM

Hi!

I've experienced this problem under both Windows 2000 and Windows XP (recently updated). I never had the problem until I updated the driver under win2k, I think I upated from 3528 to 3531, and on XP i installed 3531 from the start and got the same bug on both systems. I even tried uninstalling 3531 and going back but it didn't help. I see a lot of topics here that concern the "No midi input" problem and this is the WHY of that.

When you install any of the newer versions of the kX driver on certain systems it will install 2 devices, one is the regular "kX Gamepad port", and the other is "Standard Gamepad Device". (I might have misspelled them, I am not looking in the device manager now). But the thing is that the kX gamepad port properties tells you where it's physically located, what IRQ and so forth. While the "Standard Gamepad Device" has no such info, it just says "No info available" or something like that.

I think that the computer is listening to either the wrong one of the two ports (for midi signals), or it's having trouble working at all since there are two ports when there should be one so it just disables midi in.

Midi out works and I think that's due to the fact that on output you specify which port to send the data to.

NOTE:
1) I have tried removing both kX Gamepad and Regular Gamepad and rebooting and they are both installed at reboot.
2) None of them have an exclamation mark.
3) I have tried removing the driver files, removing the devices, rebooting, and it still doesn't work. This has to do with the kX driver setup not replacing the Gamepad driver correctly. I see no other explanation. But I'm in desperate need of help since I have a lot of melodies in my head right now that I must write down.

And finally, my system:
P3B 1Ghz - Coppermine (i think it's called that)
512mb of sdram
160gb hd.
Windows XP with all updates and service pack 1
kX driver v3531 and older
Soundblaster live ct4670 value

All who have something to add, please do so, take the time to register and tell us about your similiar problems, this is something that I know some people suffer from and I think it needs urgent attention, I can't even roll back to Creative Drivers

Other than this complaint, your drivers are awesome! =) They make my life bearable while saving up for a $2000 soundcard!

// Chris!

darkthorn · May 2, 2003, 01:15 PM

Ermmm Come on? Surely at least Eugine must know what I can do. I have had this problem for 1 month now, no reformatting helps. Others have it aswell. Help!

**Eugene Gavrilov** · May 2, 2003, 05:16 PM

I suggest you remove the drivers (by running kxsetup and choosing 'remove')
re-install them again after reboot (make sure that nothing is 'automatically installed' by Windows!)
do NOT install any drivers for your joystick (that is, answer 'no' for kxsetup questions)

now, find your original Creative drivers, select the joystick device in the Computer Management console and manually update the drivers, pointing to the Creative .inf files

/Eugene

darkthorn · May 2, 2003, 08:32 PM

I made you a picture showing everything you could possibly ask for, and I'm hoping you will be able to help me (and the others) who have this problem.

http://hem.passagen.se/betamix/gameportproblem.gif

RIGHT CLICK, SAVE AS.

**Eugene Gavrilov** · May 3, 2003, 02:13 AM

wrong URL

/E

darkthorn · May 3, 2003, 02:15 AM

I told you, you must right click and "Save as"... It wont work otherwise, the server doesnt support outside linking. Thanks for taking your time providing support for your software btw, must be tedious.

http://hem.passagen.se/betamix/gameportproblem.gif

RIGHT CLICK, SAVE AS.

**Eugene Gavrilov** · May 3, 2003, 05:04 PM

of course I've tried both ways

- no luck; maybe because I'm behind a proxy

pls use any less-restrictive web servers

/E

darkthorn · May 3, 2003, 07:57 PM

Alrightey, try this.

http://www.pulseforce.com/darkthorn/gameportproblem.gif

**Eugene Gavrilov** · May 4, 2003, 03:35 AM

well, so, what's the problem?

'MPU-401 Compatible MIDI Device' and 'Standard Game Port' are located on your motherboard!
(as a joystick connector)

there's no problem with Windows detecting them (unless you disable them in BIOS)

resource allocation is a little bit strange (should be simply 0x200 or 0x201), but anyway...

the same happens with your kX/Creative joysticks/MIDI ports
they all seem to be ok

make sure you select correct device in your program: it should be called 'kX Uart' or 'kX Uart 2' depending your audio card (well, Lives generally lack 'Uart 2').

you mention that 'midi recording just stopped' -- well, if it happened during recording, perhaps, something happend with your MIDI device and / or the -physical- port or cable.

/Eugene

Apr 30, 2003, 04:26 PM	#1
darkthorn DriverHeaven Newbie Join Date: Apr 2003 Posts: 7 Rep Power: 0	major gameports bug Hi! I've experienced this problem under both Windows 2000 and Windows XP (recently updated). I never had the problem until I updated the driver under win2k, I think I upated from 3528 to 3531, and on XP i installed 3531 from the start and got the same bug on both systems. I even tried uninstalling 3531 and going back but it didn't help. I see a lot of topics here that concern the "No midi input" problem and this is the WHY of that. When you install any of the newer versions of the kX driver on certain systems it will install 2 devices, one is the regular "kX Gamepad port", and the other is "Standard Gamepad Device". (I might have misspelled them, I am not looking in the device manager now). But the thing is that the kX gamepad port properties tells you where it's physically located, what IRQ and so forth. While the "Standard Gamepad Device" has no such info, it just says "No info available" or something like that. I think that the computer is listening to either the wrong one of the two ports (for midi signals), or it's having trouble working at all since there are two ports when there should be one so it just disables midi in. Midi out works and I think that's due to the fact that on output you specify which port to send the data to. NOTE: 1) I have tried removing both kX Gamepad and Regular Gamepad and rebooting and they are both installed at reboot. 2) None of them have an exclamation mark. 3) I have tried removing the driver files, removing the devices, rebooting, and it still doesn't work. This has to do with the kX driver setup not replacing the Gamepad driver correctly. I see no other explanation. But I'm in desperate need of help since I have a lot of melodies in my head right now that I must write down. And finally, my system: P3B 1Ghz - Coppermine (i think it's called that) 512mb of sdram 160gb hd. Windows XP with all updates and service pack 1 kX driver v3531 and older Soundblaster live ct4670 value All who have something to add, please do so, take the time to register and tell us about your similiar problems, this is something that I know some people suffer from and I think it needs urgent attention, I can't even roll back to Creative Drivers Other than this complaint, your drivers are awesome! =) They make my life bearable while saving up for a $2000 soundcard! // Chris!

May 3, 2003, 02:15 AM	Thread Starter #6
darkthorn DriverHeaven Newbie Join Date: Apr 2003 Posts: 7 Rep Power: 0	I told you, you must right click and "Save as"... It wont work otherwise, the server doesnt support outside linking. Thanks for taking your time providing support for your software btw, must be tedious. http://hem.passagen.se/betamix/gameportproblem.gif RIGHT CLICK, SAVE AS. Last edited by darkthorn; May 3, 2003 at 03:49 PM.

May 2, 2003, 01:15 PM	Thread Starter #2
darkthorn DriverHeaven Newbie Join Date: Apr 2003 Posts: 7 Rep Power: 0	Ermmm Come on? Surely at least Eugine must know what I can do. I have had this problem for 1 month now, no reformatting helps. Others have it aswell. Help!

May 2, 2003, 05:16 PM	#3
Eugene Gavrilov kX Project Lead Programmer and Coordinator Join Date: Dec 2002 Posts: 3,119 Rep Power: 75	I suggest you remove the drivers (by running kxsetup and choosing 'remove') re-install them again after reboot (make sure that nothing is 'automatically installed' by Windows!) do NOT install any drivers for your joystick (that is, answer 'no' for kxsetup questions) now, find your original Creative drivers, select the joystick device in the Computer Management console and manually update the drivers, pointing to the Creative .inf files /Eugene

May 2, 2003, 08:32 PM	Thread Starter #4
darkthorn DriverHeaven Newbie Join Date: Apr 2003 Posts: 7 Rep Power: 0	I made you a picture showing everything you could possibly ask for, and I'm hoping you will be able to help me (and the others) who have this problem. http://hem.passagen.se/betamix/gameportproblem.gif RIGHT CLICK, SAVE AS.

May 3, 2003, 02:13 AM	#5
Eugene Gavrilov kX Project Lead Programmer and Coordinator Join Date: Dec 2002 Posts: 3,119 Rep Power: 75	wrong URL /E

May 3, 2003, 05:04 PM	#7
Eugene Gavrilov kX Project Lead Programmer and Coordinator Join Date: Dec 2002 Posts: 3,119 Rep Power: 75	of course I've tried both ways - no luck; maybe because I'm behind a proxy pls use any less-restrictive web servers /E

May 3, 2003, 07:57 PM	Thread Starter #8
darkthorn DriverHeaven Newbie Join Date: Apr 2003 Posts: 7 Rep Power: 0	Alrightey, try this. http://www.pulseforce.com/darkthorn/gameportproblem.gif

May 4, 2003, 03:35 AM	#9
Eugene Gavrilov kX Project Lead Programmer and Coordinator Join Date: Dec 2002 Posts: 3,119 Rep Power: 75	well, so, what's the problem? 'MPU-401 Compatible MIDI Device' and 'Standard Game Port' are located on your motherboard! (as a joystick connector) there's no problem with Windows detecting them (unless you disable them in BIOS) resource allocation is a little bit strange (should be simply 0x200 or 0x201), but anyway... the same happens with your kX/Creative joysticks/MIDI ports they all seem to be ok make sure you select correct device in your program: it should be called 'kX Uart' or 'kX Uart 2' depending your audio card (well, Lives generally lack 'Uart 2'). you mention that 'midi recording just stopped' -- well, if it happened during recording, perhaps, something happend with your MIDI device and / or the -physical- port or cable. /Eugene