If controller is working properly outside DOSBox, but doesn't calibrate properly inside DOSBox, try different 'timed' setting in DOSBox's configuration file. It is important to remember that if you saved the mapperfile without joystickĬonnected, or with a different joystick setting, your new setting will not work properly, or not work at all, until you reset DOSBox's mapperfile. You also have to configure controller properly inside the game. With 4-axes, 6 buttons and 1 hat, but you cannot press more With 4 axis and 4 buttons or a gamepad with 2axis and 6 buttons.Ĥaxis_2 - supports only second controller.įcs - supports only first controller, emulates ThrustMasterįlight Control System, with 3-axes, 4 buttons and 1 hat.Ĭh - supports only first controller, emulates CH Flightstick, It will emulate a joystick with only 2 axis and 2 buttons.Ĥaxis - supports only first controller, emulates a joystick Thats probably because the DOS debug program is in the current directory. If you have only one controller connected, I think the DOSBox debugger is sufficient, because the game doesnt require a protected mode extender, but on the other hand, because of my lack of experience in debugging, Id like to get a call stack while I am debugging, so I want to use Watcom Debugger side-by-side with the DosBox debugger. If you have two - '2axis' setting is used.Ģaxis - If you have two controllers connected, each will emulate a joystick If you have one - '4axis' setting is used, To force DOSBox to use a different type of emulated joystick/gamepad, the entry"joysticktype" in the section of the DOSBox configuration file can be used.Īuto - (default) autodetects whether you have one or two controllers connected: For more, different modifications of that configuration were used. This points at the check being something else, for something that only exists or is only in the correct format in a real MS-DOS (or PC DOS) version.ĭoes anyone here have any idea what WIN386 could be checking for? Could it be a case of an ancient equivalent to the AARD code? Or something else? Any help is welcome.The standard joystick port in DOS supports a maximum of 4 axes and 4 buttons. For debugging purposes, if the game is a DOS game, the DosBox Debugger is the best tool Ive found for executing and debugging DOS programs. In addition, the error message doesn't appear when running the OS under real MS-DOS 6.0 in Virtual PC 2007. Using ver set to set the DOS version reported by DOSBox doesn't fix the issue, and after debugging WIN386.EXE, I found out that the version number itself does not get checked at all, despite the fact int 21h/ah=30h (Get DOS version) is called. configure -enable-debug If you want a heavydebug version, edit config.h after running configure and define CHEAVYDEBUG. i extended my Dosbox Staging version to print the loading-segment of the DOS exe, calculate the 32bit offset from that loadseg 16 loadofs32. Of course by booting the proper DOS boot disk, you can get it to run but for some reason when you try to run it in DOSBox with nothing else, it gives the following error message: "Error: Unsupported DOS Version". Compiling the debug / heavydebug version of DOSBOX In order to get a debug version, add the switch '-enable-debug' when calling configure. My friend TheCollector1988 and I have been trying to get Windows 2.x/386 to run in DOSBox, without having to boot a DOS floppy image.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |