Zipped Installer for Dosbox/2 0.74 (built 6).Zipped Installer for Dosbox/2 0.74 (built 0).Zipped Installer for Dosbox/2 0.74 (built 5).Zipped Installer for Dosbox/2 0.74 (built 1).(3) I did a build of DOSBOX/2 from CVS as of 2.Installer for Dosbox 0.65 including the Debug versions.(8) The 0.65 release of DOSBOX/2 is out!.PLEASE download this package if you really, This package also includes the debugging bins including the internal debugger versions.īe aware that you need the /usr/share/terminfo directory from libncurses.KEYB.EXE from FreeDOS plus precompiled keyboard layout and some language files for DOSBOX. This package just gives you what need to run Dosbox.I have build two installers, based on the template by Martin Iturbide, and with some help from dargndorp: I submitted a patch against the 0.63 source tree.

For the naming convention of the binaries see above. The release binaries of DOSBOX/2 Beta 3.This package will stay the same in the future. The binaries are now splitted into three packages: This version fixes the mispainted key mapper.the debug version of dosboxd.exe is dosboxd_d.exe. Now included in the package are debug versions of the three executables. This version fixes a bug, that prevented some installers to work and made DOSBOX/2 crash.Until the new SDL/2 binaries show up on Netlabs, use the DLLs included. The integrated midi emulation is good enough. MPU401 support is dropped, because it's not feasible at the moment. This version now contains direct serial support.Also, pressing and releasing ALT doesn't activate theĪs always only use the included DLLs. The mouse is now captured if you press CTRL+F10. DOSBOXHD.EXE: This is the heavy debugging version.Īn explanantion of the internal debugger can be found on the FAQ pages of the.DOSBOXD.EXE: This is the debugging version.DOSBOX.EXE: This is the normal version.The package now includes three executables: to 'ANSI', if you use the debugging versions. You need to set the environment variable 'TERM', e.g. This version now supports the internal Dosbox debugger through ncurses.This version fixes a bug with internal command copy and capturing screenshots.This version includes untested support for serial passthrough and cdrom ioctl.This version fixes the problems with the crashing keymapper and the shifted keys.This version now contains support for MPU401.Zipped Installer for Dosbox/2 0.74-3 (trunk - built 4).Installer for Dosbox/2 0.74-3 (trunk - built 4).You can find more informations about Dosbox here. File size: 302,982 bytes, Time/date stamp: 21 July 1992, 9:52:34 AMĪttached is the most recent game (Canberra about to build Oracle) and the screenshot of what happens when I click on the 'CHANGE' button.Īn error creeping into Civ's code, or how it produces games? Or something I've induced recently - did upgrade DOSBox from 0.72 when installing new O/S.This is the home of the Dosbox port to OS/2. Is CIV.EXE unadulterated? Hmmm, possibly not - may've been stripped of usurper challenger's teeth with CRACK.EXE sometime in the mid 90s. Attempts to change the construction from a game saved prior to the error also produce the same error.ĭOSBOX: 0.74 (running under Win7 Enterprise *OR* Ubuntu 12.04 LTS)ĬIV Ver: 474.04 (listed upon running - INTRO.TXT & INTRO3.TXT give. The screen locks as it's about to display the Selection screen for the city, offering the Military Advisor advice, but nothing else. For one game, it was the Pyramids, in another the Oracle. On all games I've played on my original 3.5' disk copy of Civ - originally installed on my 386 but copied across to newfangled PC recently went it finally died - since the beginning of this year (2013) will lock-up when reaching the city screen post -construction of a (apparently) random wonder. Still OT about freezing, but seemingly for new causes. 05 so long ago I dont remember why I didnt like. 03 modify the INTRO.TXT file data on the screen display only, with no reference to 474 or 475 The reason I mention this in that all of the version after. They appear to do this by reading INTRO.TXT and replacing the 214th byte (again from zero) with the version number in the screen display only. 05 display the number corresponding with their version number. I ask this because CIV 474.01 just reads this file to show the first screen. What are the properties on your copy of INTRO.TXT?īyte 209 (first byte numbered 0) is the version string. What is the file date & time stamp on CIV.EXE?Īlso the following file, its properties should be I have always been fascinated by version 475.

Dosbox debugger installer 0.72