where have you got dosbox from?

post content of "DOSBox Status Window" (in Windows: right click on its title bar -> edit)
enclose your dosbox's config file

Dunno about OS X, but USB controllers usually don't need to be calibrated, especially when they don't have analog sticks.

Not a Mac user, so I'm shooting in the dark. Usually DOSBox will use the analog stick of a gamepad as "joystick". If you want to use the dpad you have to map the inputs manually, as the default way of using a dpad in DOS was as a "coolie hat" (used for example in flight sims to change views to the left, rear, etc.). My guess is that DOSBox is somehow looking for an analog stick on your controller which of course isn't there. You probably could use the DOSBox keymapper to first delete all joystick 1 mappings and then assign the dpad to the joystick. But to be frank I don't even know if the keymapper is available in the OS X build.

Oh, and DOSBox will output some info about the controller(s) it has identifed in the status window. Paste that info here so we can see what DOSBox thinks your controller is (; . Probably not connected to your problem, but you should upgrade to DOSBox 0.74, too.

If that's not the problem you could try changing the "timed" parameter in DOSBox. You should also calibrate the controller in every game you want to play. This in-game calibration usually happens when starting a game, sometimes there's an in-game hotkey.

first of all: does joystick work properly outside dosbox in macos?

Yes it does work in mac os. It also works on other emulators such as snes, gameboy and nes in mac os x. I am using DosBox 0.73.

ADDiCT wrote:

upgrade to DOSBox 0.74

And:

Oh, and DOSBox will output some info about the controller(s) it has identifed in the status window. Paste that info here so we can see what DOSBox thinks your controller is (; .

Sorry but do I read this correctly that you are running Dosbox in a VM? Why are you doing this?
This is very likely the source of your problem.
Run the native OS X port of dosbox and not the windows version inside a vm running Windows...
Running an emulator inside an emulator (yeah, simplyfying virtualization here 😉) is bound to lose something somewhere...

Thanks. Yeah I have it for both and it does the same thing on the Mac OS version also.

I have upgraded to DosBox 0.74 I am still getting the same results I will post the suggested screen also.

Here is the status screen.

Here is the config file from windows parallel.

The status screen is the one underneath the dosbox screen 😉

robertmo wrote:

where have you got dosbox from?

post content of "DOSBox Status Window" (in Windows: right click on its title bar -> edit)
enclose your dosbox's config file

and by the way follow the guide
60 seconds guide to getting your game to run in DOSBox

Dominus wrote:

The status screen is the one underneath the dosbox screen 😉

Indeed (; . guruNS, we need a screenshot of the other screen.

By the way: why are you running DOSBox in an emulator? It's not clear yet that this is the source of your problem, but it definitely doesn't make things easier or more stable. Why aren't you running the native OS X DOSBox version?

P.S.: disregard robertmo's post about the guide for now. One step after the other please. First the controller problem, then the other stuff.

It does the same thing in OS X DosBox also I was trying the Windows Parallel to see if it would work. I know people aren't used to working with OS X so I thought the Windows XP would be easier.

How do I get the status screen in Mac Os X?

Here is the OS X config file.

My OS X DosBox does not have a second screen it only has one screen.

irq doesn't seem to be right.
should be 7

We don't need the ssw cfg file, we need Dosbox config file. On OS X this is the file ~/Library/Preferences/DOSBox 0.74 Preferences
The status window of Dosbox can be seen on OS X by right clicking on dosbox.app and choosing "Show Package content", then in the new finder window go into contents/macos/ and double click on dosbox. (alternatively the console.app will show you the output as well, but only after closing dosbox again).