Amigaz wrote:

Today I put the final touches on my AMD K6-2+ 500mhz box by adding a diamond monster sound MX300 card in it. It also has a Sound […]
Show full quote

Today I put the final touches on my AMD K6-2+ 500mhz box by adding a diamond monster sound MX300 card in it.
It also has a Sound Blaster 16 ISA (CT1740) + a GUS ACE
What puzzles me is that in pure DOS no matter what Sound Blaster card I put in it the joystick button doesn't work..tried different joysticks, games and SB ISA cards

I'm completely clueless, do you guys have any tips?

Did the joystick work before adding the MX300? If that's the case, you probably have conflicting joystick ports. Try disabling the joystick port on the Diamond MX300 card (or any sound card other than your SB ISA, for that matter --including the one on your mobo if any).

By the way, it's better to use SB's joystick port instead of Diamond MX300's, because of this:

f you're a joystick user, check to make sure your stick will work with the MX300's subtly non-standard game port. Apparently because of the card's 3.3 volt architecture, the game port is incompatible with some older sticks. The original 1997 Monster Sound was renowned for being incompatible with pretty much any joystick you care to name; the MX300 is much, much better but still not perfect.

Kreshna Aryaguna Nurzaman wrote:

Did the joystick work before adding the MX300? If that's the case, you probably have conflicting joystick ports. Try disabling t […]
Show full quote

Amigaz wrote:

Today I put the final touches on my AMD K6-2+ 500mhz box by adding a diamond monster sound MX300 card in it. It also has a Sound […]
Show full quote

Today I put the final touches on my AMD K6-2+ 500mhz box by adding a diamond monster sound MX300 card in it.
It also has a Sound Blaster 16 ISA (CT1740) + a GUS ACE
What puzzles me is that in pure DOS no matter what Sound Blaster card I put in it the joystick button doesn't work..tried different joysticks, games and SB ISA cards

I'm completely clueless, do you guys have any tips?

Did the joystick work before adding the MX300? If that's the case, you probably have conflicting joystick ports. Try disabling the joystick port on the Diamond MX300 card (or any sound card other than your SB ISA, for that matter --including the one on your mobo if any).

By the way, it's better to use SB's joystick port instead of Diamond MX300's, because of this:

f you're a joystick user, check to make sure your stick will work with the MX300's subtly non-standard game port. Apparently because of the card's 3.3 volt architecture, the game port is incompatible with some older sticks. The original 1997 Monster Sound was renowned for being incompatible with pretty much any joystick you care to name; the MX300 is much, much better but still not perfect.

I don't think I've ever tried a joystick on this system

Same problem when the MX300 is removed

Amigaz wrote:

I don't think I've ever tried a joystick on this system

Same problem when the MX300 is removed

Does your mobo has onboard sound card? If that's the case, try disabling onboard joystick port (through BIOS).

Kreshna Aryaguna Nurzaman wrote:

Amigaz wrote:

I don't think I've ever tried a joystick on this system

Same problem when the MX300 is removed

Does your mobo has onboard sound card? If that's the case, try disabling onboard joystick port (through BIOS).

It has none

what stick is it ?

Er, he has tried different joysticks, so I don't think the problem lies on the stick itself.

Kreshna Aryaguna Nurzaman wrote:

Er, he has tried different joysticks, so I don't think the problem lies on the stick itself.

Yeah, I think it must be component failure on my Via MPV3 based Epox mobo or a bug
This mobo has given me so much different problems anyway so I'm thinking of ditching it and going for an ALi Alladin based instead

I don't suppose you've tried another card? Or even have one?
<long_shot>You could run Windows and see what Device Manager says about it; if it can make them play nice, then you should be good; if those changes don't hold outside of Windows, you could probably write them down and make them manually in DOS.

I'd be happy to take it off your hands!!!

general_vagueness wrote:

I don't suppose you've tried another card? Or even have one?
<long_shot>You could run Windows and see what Device Manager says about it; if it can make them play nice, then you should be good; if those changes don't hold outside of Windows, you could probably write them down and make them manually in DOS.

I'd be happy to take it off your hands!!!

It win98 device manager the joyport is "disabled" and I can't change it
It doesn't work in pure DOS either

ps. since I've become a mad GUs collector it's not for sale 😁

An update to this thread..

I got another version of this Epox mootherboard which has 2mb cache and an AMD K6-III+ 500mhz for even more horsepower

Still the same joystick problem though....WTF!!! 😵

Are these VIA MVP3 based mobo's totally bugged out or what?

would still be nice to know what stick it is

could this be the problem
Q. My Rage 3D gamepad does not work with my new soundcard. How can I fix this?

A. The Rage 3D will not work with newer soundcards using 3v logic. The Rage 3D will only work with soundcards and gameports with 5v logic.

what voltage does your stick use ?

Davros wrote:

would still be nice to know what stick it is […]
Show full quote

would still be nice to know what stick it is

could this be the problem
Q. My Rage 3D gamepad does not work with my new soundcard. How can I fix this?

A. The Rage 3D will not work with newer soundcards using 3v logic. The Rage 3D will only work with soundcards and gameports with 5v logic.

what voltage does your stick use ?

Voltage?

I've tried with a Saiktek gamepad, CH Flightstick (regular), CH Flightstick Pro + my Thrustmaster flightstick

Maybe check in the Windows device manager if some hardware uses I/O-Port 201.

h-a-l-9000 wrote:

Maybe check in the Windows device manager if some hardware uses I/O-Port 201.

Going to check that 😀

I hear Ch's tech support is really good try emailing them

Why not try the opposite and disable the SB's joystick port and use the MX300's if the joystick is of fairly recent vintage?

Great Hierophant wrote:

Why not try the opposite and disable the SB's joystick port and use the MX300's if the joystick is of fairly recent vintage?

Is the MX300 "Legacy" enough for the joystick to work in pure DOS?

Great Hierophant wrote:

Why not try the opposite and disable the SB's joystick port and use the MX300's if the joystick is of fairly recent vintage?

Just tried this, didn't help

I'm at a loss here, please help me out guys 🙁

Seems like a very strange problem indeed.

I would start from scratch and test one component at a time: Begin with an empty board (except video card). Try if you can get the joystick buttons to work on a random gameport (soundcard, I/O card, whatever). If it works, you can rule out the mainboard. Then continue adding/replacing the cards you want to use in the machine and see where it stops working.

I've got a sneaking suspicion about the GUS ACE...

[Edit:] Check out this old usenet thread!