This is for anyone interested in getting as close as possible to the real 1990’s MS-DOS6 experience using the DOSBox MS-DOS emulator under Windows. I prefer using my main offline WinXP desktop, back when Windows was designed to be a productive desktop-only experience (missing only Win7’s file copy/replace feature, destroyed in Win10). But I need my online Win10 laptop to post, and Win10 is more relevant.
Note that I have not tested any of this with DOSBox for Linux, MAC OS, etc.
++++++++++
First, when you install DOSBox, you should create and assign a root directory (folders are called directories in DOS) for DOSBox to see as your C drive. You do this, as well as mount your CD-ROM drive, in the DOSBox configuration file which is located here (just replace my name for yours)…
[autoexec] # Lines in this section will be run at startup. # You can put your MOUNT lines here. MOUNT C: C:\DOS MOUNT D E:\ -t cdrom PATH C:\DOS C:
My root directory is C:\DOS, which DOSBox will see as C:, but I also have a second DOS directory under my root, for MS-DOS files supported under DOSBox...
So when I execute a DIR (directory) command, I see...
Next post: MS-DOS6 files supported under DOSBox...
The rusty wire that holds the cork that keeps the anger in Gives way and suddenly it’s day again The sun is in the east Even though the day is done Two suns in the sunset, hmph Could be the human race is run
I don't know where you would find MS-DOS6 today, but I'm sure you can find it somewhere. I purchased mine from CompUSA in 1994...
Here is a listing of the MS-DOS6.22 files which I found will function under DOSBox, just as you would have used them in DOS...
++++++++++
The following (shown under Spoiler tag) are the internal DOSBox DOS commands, as well as external MS-DOS6 commands (from the above files) that are supported under DOSBox...
Internal (common usage): DOSBox Commands Internal (batch files): DOSBox Batch Commands (more on batch files in next post).
Internal (other): Obscure DOSBox Commands Internal (duplicate function): serves same function as common usage commands (MD and MKDIR are same command).
External MS-DOS 6.22: MS-DOS6.22 files supported under DOSBox (the files in the C:\DOS\DOS folder [Windows], or C:\DOS [DOSBox prompt]).
Internal (common usage) =======================
DIR Directory view. CD Displays/changes the current directory. CLS Clears the screen. COPY Copies one or more files. DEL Removes one or more files. EXIT Exits from shell. MD Makes a directory. RD Removes a directory. REN Renames one or more files. TYPE Displays the contents of a text-file. VER View and set the reported DOS version.
Internal (batch files) ======================
CALL Starts a batch file from within another batch file. CHOICE Waits for a keypress and sets ERRORLEVEL. ECHO Displays messages and enables/disables command echoing. GOTO Jumps to a labeled line in a batch script. IF Performs conditional processing in batch programs. PAUSE Waits for keystroke to continue. REM Adds comments in a batch file. SHIFT Leftshift commandline parameters in a batch script.
Internal (other) ================
ATTRIB Does Nothing, provided for compatibility. HELP Shows help. LH Loads a program into upper memory (requires xms=true,umb=true). PATH Provided for compatibility. SET Changes environment variables. SUBST Assigns an internal directory to a drive.
CHDIR Displays/changes the current directory. DELETE Removes one or more files. ERASE Removes one or more files. LOADHIGH Loads a program into upper memory (requires xms=true,umb=true). MKDIR Makes a directory. RMDIR Removes a directory. RENAME Renames one or more files.
Why? Because you can't have a true DOS experience without DOSSHELL! ...
Next post, using batch files for various DOSBox configurations...
The rusty wire that holds the cork that keeps the anger in Gives way and suddenly it’s day again The sun is in the east Even though the day is done Two suns in the sunset, hmph Could be the human race is run
Thank you, Chucky, for letting me know that at least one person finds this interesting! Nah, I figured some would at least enjoy some DOS nostalgia, but there's a reason for posting this which I'll get into later.
But first, I skipped an important part before getting into batch files which I'm working on now...
The rusty wire that holds the cork that keeps the anger in Gives way and suddenly it’s day again The sun is in the east Even though the day is done Two suns in the sunset, hmph Could be the human race is run
Due to DOSBox support, I finally had to retire Windows 2000 for XP (SP2) on my main desktop, although I still have a Win2K (w/DOS6.22 dual-boot) PC which is temporarily put away to make room for my wife's monster 3-screen setup (she's working from home in my office). This post will cover WinXP as it's what I mainly use (my DOSBox "C:\DOS" 'C-drive' on main PC is *much* larger!), but I assume that Win Vista+ has similar support (I can't imagine Microsoft has done much with the built-in DOS commands).
Except that in Win10, the Command Line is being phased out for Windows PowerShell. I haven't fooled with it much and still use the regular Command Line.
At the end of the file listing in above post (under the Spoiler tag) are the WinXP DOS commands supported under DOSBox and were copied from my WinXP "C:Windows\System32" folder to my DOS folder...
This was the reason for even starting this project, as I needed a working DEBUG under DOSBox to complete Jeff Duntemann's 2nd ed. of "Assembly Language: Step-By-Step", and now Michael Abrash's "Zen of Graphics Programming". Jeff's code is supported under NASM (included w/book CD, along with the ALINK linker), while Michael's code is MASM-compatible and I've had no problem assembling/compiling his samples with Open Watcom at the DOSBox DOS prompt.
++++++++++
The following (shown under Spoiler tag) are the internal WinXP DOS commands (assuming it's not much different for Vista+), as well as external MS-DOS6 commands (located in C:\DOS\DOS) that are supported under the Windows Command Line...
Included: Included with Windows Included (batch files): Windows Batch Commands (more on batch files in next post).
External MS-DOS 6.22: MS-DOS 6.22 files supported under Windows Command Line (run from C:\DOS\DOS folder), some having duplicate internal function.
Included ========
APPEND Allows programs to open data files in specified directories as if they were in the current directory. ASSOC Displays or modifies file extension associations. AT Schedules commands and programs to run on a computer. ATTRIB Displays or changes file attributes. BREAK Sets or clears extended CTRL+C checking. CACLS Displays or modifies access control lists (ACLs) of files. CD Displays the name of or changes the current directory. CHCP Displays or sets the active code page number. CHDIR Displays the name of or changes the current directory. CHKDSK Checks a disk and displays a status report. CHKNTFS Displays or modifies the checking of disk at boot time. CLS Clears the screen. CMD Starts a new instance of the Windows command interpreter. COLOR Sets the default console foreground and background colors. COMP Compares the contents of two files or sets of files. COMPACT Displays or alters the compression of files on NTFS partitions. CONVERT Converts FAT volumes to NTFS. You cannot convert the current drive. COPY Copies one or more files to another location. DATE Displays or sets the date. DEBUG Runs program testing and editing tool. DEFRAG Defragments drive. DEL Deletes one or more files. DIR Displays a list of files and subdirectories in a directory. DISKCOMP Compares the contents of two floppy disks. DISKCOPY Copies the contents of one floppy disk to another. DOSKEY Edits command lines, recalls Windows commands, and creates macros. EDIT Edits text files. ERASE Deletes one or more files. EXIT Quits the CMD.EXE program (command interpreter). EXPAND Expands one or more compressed files. FC Compares two files or sets of files, and displays the differences between them. FIND Searches for a text string in a file or files. FINDSTR Searches for strings in files. FOR Runs a specified command for each file in a set of files. FORMAT Formats a disk for use with Windows. FTYPE Displays or modifies file types used in file extension associations. GRAFTABL Enables Windows to display an extended character set in graphics mode. GRAPHICS Loads a program that can print graphics. HELP Provides Help information for Windows commands. LABEL Creates, changes, or deletes the volume label of a disk. MD Creates a directory. MEM Displays amount of used and free memory. MKDIR Creates a directory. MODE Configures a system device. MORE Displays output one screen at a time. MOVE Moves one or more files from one directory to another directory. NLSFUNC Loads country specific information. PATH Displays or sets a search path for executable files. POPD Restores the previous value of the current directory saved by PUSHD. PRINT Prints a text file. PROMPT Changes the Windows command prompt. PUSHD Saves the current directory then changes it. RD Removes a directory. RECOVER Recovers readable information from a bad or defective disk. REN Renames a file or files. RENAME Renames a file or files. REPLACE Replaces files. RMDIR Removes a directory. SET Displays, sets, or removes Windows environment variables. SETVER Sets the version number that MS-DOS reports to a program. SORT Sorts input. START Starts a separate window to run a specified program or command. SUBST Associates a path with a drive letter. TIME Displays or sets the system time. TITLE Sets the window title for a CMD.EXE session. TREE Graphically displays the directory structure of a drive or path. TYPE Displays the contents of a text file. VER Displays the Windows version. VERIFY Tells Windows whether to verify that your files are written correctly to a disk. VOL Displays a disk volume label and serial number. XCOPY Copies files and directory trees.
Included (batch files) =======================
CALL Calls one batch program from another. ECHO Displays messages, or turns command echoing on or off. ENDLOCAL Ends localization of environment changes in a batch file. GOTO Directs the Windows command interpreter to a labeled line in a batch program. IF Performs conditional processing in batch programs. PAUSE Suspends processing of a batch file and displays a message. REM Records comments (remarks) in batch files or CONFIG.SYS. SETLOCAL Begins localization of environment changes in a batch file. SHIFT Shifts the position of replaceable parameters in batch files.
Included for compatibility (does nothing) =========================================
Next post, using batch files for various DOSBox configurations...
The rusty wire that holds the cork that keeps the anger in Gives way and suddenly it’s day again The sun is in the east Even though the day is done Two suns in the sunset, hmph Could be the human race is run
Cool Blastman, except that I do have a genuine MS-DOS6.22 box, just no soundcard. So when I run a SCANDISK and DEFRAG, I get those Symantec (Norton Utilities) PC speaker triple-beeps!
Oh man, forget DOSSHELL, where's my XTREE?!
The rusty wire that holds the cork that keeps the anger in Gives way and suddenly it’s day again The sun is in the east Even though the day is done Two suns in the sunset, hmph Could be the human race is run
You might have noticed that in the file listings above (shown under Spoiler tags), there are batch file commands, rudimentary QBASIC-like programming functionality for creating complex batch files. We won't be using them. Our batch files will be simple, and will allow us to quickly setup a single version of DOSBox any way we want.
But first, here's my current Win10 laptop desktop (technically my wife's laptop, there's no hiding that with this post )...
I have three GOG games temporarily installed for testing (three games I'll be focusing on for a long time). Sometimes I'll copy the original DOS files from my C:\GOG Games folder to my C:\DOS folder, and then uninstall my GOG setup. Why? Because with some games I want a cleaner smaller purer DOS experience, as if I had just installed the original game under DOS. But not always. For games I play only occasionally, I stay with the GOG setup which makes it easy to install and uninstall on a whim. So I only dissect games that I'm really interested in at any given time.
Before I continue, as a retro gamer I very much appreciate the service that GOG provides, and I'll often purchase a game from them that I already own just to have a WinXP/Win10 supported setup. This support includes a fully configured DOSBox that usually works perfectly without any tweaking. Plus there's additional content that GOG provides, like PDF documentation and other cool extras. So I don't always make a pure DOS version of a game (I won't call it a "standalone" game because my GOG games are already fully independent).
++++++++++
With all that said, we want to create some configuration batch files for a single DOSBox install, making it easy to configure DOSBox with a simple double-click.
First, remember where the DOSBox configuration file is located (in Win10, WinXP is different)...
What we need to do is to copy this file multiple times, giving each copy a filename that reflects what we want the settings used for. For example, my copies reside in the Source folder of my DOSBox Config folder on my desktop...
Each one of these files is nothing but a full DOSBox configuration file, just like "dosbox-0.74.conf", just named differently to reflect whatever I'll be using it for (i.e. ASM, F14, Original, WATCOM).
So what I want is for the single DOSBox configuration file...
...to be replaced with one of the files in the above screenshot, and we do this by using a simple batch file, like the ones stored in the DOSBox Config folder on my desktop...
Notice that each batch file corresponds to a Source file, so when I double-click on the batch (BAT) file, it replaces the DOSBox configuration file with one of my own, renaming it in the process.
...copies and renames z_org_dosbox-0.74.txt to dosbox-0.74.conf". So when I start DOSBox (program icon located below folder on my desktop), the settings have all been reset to their original default values.
Another example would be double-clicking Watcom.bat (replacing dosbox-0.74.conf with z_watcom_dosbox-0.74.txt)...
# This is the configurationfile for DOSBox 0.74. (Please use the latest version of DOSBox) # Lines starting with a # are commentlines and are ignored by DOSBox. # They are used to (briefly) document the effect of each option.
[sdl] # fullscreen: Start dosbox directly in fullscreen. (Press ALT-Enter to go back) # fulldouble: Use double buffering in fullscreen. It can reduce screen flickering, but it can also result in a slow DOSBox. # fullresolution: What resolution to use for fullscreen: original or fixed size (e.g. 1024x768). # Using your monitor's native resolution with aspect=true might give the best results. # If you end up with small window on a large screen, try an output different from surface. # windowresolution: Scale the window to this size IF the output device supports hardware scaling. # (output=surface does not!) # output: What video system to use for output. # Possible values: surface, overlay, opengl, openglnb, ddraw. # autolock: Mouse will automatically lock, if you click on the screen. (Press CTRL-F10 to unlock) # sensitivity: Mouse sensitivity. # waitonerror: Wait before closing the console if dosbox has an error. # priority: Priority levels for dosbox. Second entry behind the comma is for when dosbox is not focused/minimized. # pause is only valid for the second entry. # Possible values: lowest, lower, normal, higher, highest, pause. # mapperfile: File used to load/save the key/event mappings from. Resetmapper only works with the defaul value. # usescancodes: Avoid usage of symkeys, might not work on all operating systems.
[dosbox] # language: Select another language file. # machine: The type of machine tries to emulate. # Possible values: hercules, cga, tandy, pcjr, ega, vgaonly, svga_s3, svga_et3000, svga_et4000, svga_paradise, vesa_nolfb, vesa_oldvbe. # captures: Directory where things like wave, midi, screenshot get captured. # memsize: Amount of memory DOSBox has in megabytes. # This value is best left at its default to avoid problems with some games, # though few games might require a higher value. # There is generally no speed advantage when raising this value.
[render] # frameskip: How many frames DOSBox skips before drawing one. # aspect: Do aspect correction, if your output method doesn't support scaling this can slow things down!. # scaler: Scaler used to enlarge/enhance low resolution modes. # If 'forced' is appended, then the scaler will be used even if the result might not be desired. # Possible values: none, normal2x, normal3x, advmame2x, advmame3x, advinterp2x, advinterp3x, hq2x, hq3x, 2xsai, super2xsai, supereagle, tv2x, tv3x, rgb2x, rgb3x, scan2x, scan3x.
frameskip=0 aspect=false scaler=normal2x
[cpu] # core: CPU Core used in emulation. auto will switch to dynamic if available and appropriate. # Possible values: auto, dynamic, normal, simple. # cputype: CPU Type used in emulation. auto is the fastest choice. # Possible values: auto, 386, 386_slow, 486_slow, pentium_slow, 386_prefetch. # cycles: Amount of instructions DOSBox tries to emulate each millisecond. # Setting this value too high results in sound dropouts and lags. # Cycles can be set in 3 ways: # 'auto' tries to guess what a game needs. # It usually works, but can fail for certain games. # 'fixed #number' will set a fixed amount of cycles. This is what you usually need if 'auto' fails. # (Example: fixed 4000). # 'max' will allocate as much cycles as your computer is able to handle. # # Possible values: auto, fixed, max. # cycleup: Amount of cycles to decrease/increase with keycombo.(CTRL-F11/CTRL-F12) # cycledown: Setting it lower than 100 will be a percentage.
[mixer] # nosound: Enable silent mode, sound is still emulated though. # rate: Mixer sample rate, setting any device's rate higher than this will probably lower their sound quality. # Possible values: 44100, 48000, 32000, 22050, 16000, 11025, 8000, 49716. # blocksize: Mixer block size, larger blocks might help sound stuttering but sound will also be more lagged. # Possible values: 1024, 2048, 4096, 8192, 512, 256. # prebuffer: How many milliseconds of data to keep on top of the blocksize.
[midi] # mpu401: Type of MPU-401 to emulate. # Possible values: intelligent, uart, none. # mididevice: Device that will receive the MIDI data from MPU-401. # Possible values: default, win32, alsa, oss, coreaudio, coremidi, none. # midiconfig: Special configuration options for the device driver. This is usually the id of the device you want to use. # See the README/Manual for more details.
mpu401=intelligent mididevice=default midiconfig=
[sblaster] # sbtype: Type of Soundblaster to emulate. gb is Gameblaster. # Possible values: sb1, sb2, sbpro1, sbpro2, sb16, gb, none. # sbbase: The IO address of the soundblaster. # Possible values: 220, 240, 260, 280, 2a0, 2c0, 2e0, 300. # irq: The IRQ number of the soundblaster. # Possible values: 7, 5, 3, 9, 10, 11, 12. # dma: The DMA number of the soundblaster. # Possible values: 1, 5, 0, 3, 6, 7. # hdma: The High DMA number of the soundblaster. # Possible values: 1, 5, 0, 3, 6, 7. # sbmixer: Allow the soundblaster mixer to modify the DOSBox mixer. # oplmode: Type of OPL emulation. On 'auto' the mode is determined by sblaster type. All OPL modes are Adlib-compatible, except for 'cms'. # Possible values: auto, cms, opl2, dualopl2, opl3, none. # oplemu: Provider for the OPL emulation. compat might provide better quality (see oplrate as well). # Possible values: default, compat, fast. # oplrate: Sample rate of OPL music emulation. Use 49716 for highest quality (set the mixer rate accordingly). # Possible values: 44100, 49716, 48000, 32000, 22050, 16000, 11025, 8000.
[gus] # gus: Enable the Gravis Ultrasound emulation. # gusrate: Sample rate of Ultrasound emulation. # Possible values: 44100, 48000, 32000, 22050, 16000, 11025, 8000, 49716. # gusbase: The IO base address of the Gravis Ultrasound. # Possible values: 240, 220, 260, 280, 2a0, 2c0, 2e0, 300. # gusirq: The IRQ number of the Gravis Ultrasound. # Possible values: 5, 3, 7, 9, 10, 11, 12. # gusdma: The DMA channel of the Gravis Ultrasound. # Possible values: 3, 0, 1, 5, 6, 7. # ultradir: Path to Ultrasound directory. In this directory # there should be a MIDI directory that contains # the patch files for GUS playback. Patch sets used # with Timidity should work fine.
[speaker] # pcspeaker: Enable PC-Speaker emulation. # pcrate: Sample rate of the PC-Speaker sound generation. # Possible values: 44100, 48000, 32000, 22050, 16000, 11025, 8000, 49716. # tandy: Enable Tandy Sound System emulation. For 'auto', emulation is present only if machine is set to 'tandy'. # Possible values: auto, on, off. # tandyrate: Sample rate of the Tandy 3-Voice generation. # Possible values: 44100, 48000, 32000, 22050, 16000, 11025, 8000, 49716. # disney: Enable Disney Sound Source emulation. (Covox Voice Master and Speech Thing compatible).
[joystick] # joysticktype: Type of joystick to emulate: auto (default), none, # 2axis (supports two joysticks), # 4axis (supports one joystick, first joystick used), # 4axis_2 (supports one joystick, second joystick used), # fcs (Thrustmaster), ch (CH Flightstick). # none disables joystick emulation. # auto chooses emulation depending on real joystick(s). # (Remember to reset dosbox's mapperfile if you saved it earlier) # Possible values: auto, 2axis, 4axis, 4axis_2, fcs, ch, none. # timed: enable timed intervals for axis. Experiment with this option, if your joystick drifts (away). # autofire: continuously fires as long as you keep the button pressed. # swap34: swap the 3rd and the 4th axis. can be useful for certain joysticks. # buttonwrap: enable button wrapping at the number of emulated buttons.
[serial] # serial1: set type of device connected to com port. # Can be disabled, dummy, modem, nullmodem, directserial. # Additional parameters must be in the same line in the form of # parameter:value. Parameter for all types is irq (optional). # for directserial: realport (required), rxdelay (optional). # (realport:COM1 realport:ttyS0). # for modem: listenport (optional). # for nullmodem: server, rxdelay, txdelay, telnet, usedtr, # transparent, port, inhsocket (all optional). # Example: serial1=modem listenport:5000 # Possible values: dummy, disabled, modem, nullmodem, directserial. # serial2: see serial1 # Possible values: dummy, disabled, modem, nullmodem, directserial. # serial3: see serial1 # Possible values: dummy, disabled, modem, nullmodem, directserial. # serial4: see serial1 # Possible values: dummy, disabled, modem, nullmodem, directserial.
[dos] # xms: Enable XMS support. # ems: Enable EMS support. # umb: Enable UMB support. # keyboardlayout: Language code of the keyboard layout (or none).
xms=true ems=true umb=true keyboardlayout=auto
[ipx] # ipx: Enable ipx over UDP/IP emulation.
ipx=false
[autoexec] # Lines in this section will be run at startup. # You can put your MOUNT lines here.
MOUNT C: C:\DOS MOUNT D E:\ -t cdrom
PATH C:\WATCOM\BINW;%PATH%;C:\DOS SET INCLUDE=C:\WATCOM\H SET WATCOM=C:\WATCOM SET EDPATH=C:\WATCOM\EDDAT SET WIPFC=C:\WATCOM\WIPFC C:
...to include all of the path settings that WATCOM requires...
And that's all there is to it. Double-click the BAT file to setup your settings and then start DOSBox with the new settings.
The rusty wire that holds the cork that keeps the anger in Gives way and suddenly it’s day again The sun is in the east Even though the day is done Two suns in the sunset, hmph Could be the human race is run
^ Whew, finished the above post I think, taking a break now. I have some other things to add later, but the main thing is that I want to use this thread as a reference for some upcoming projects I want to share that may require DOSBox with specific settings.
The rusty wire that holds the cork that keeps the anger in Gives way and suddenly it’s day again The sun is in the east Even though the day is done Two suns in the sunset, hmph Could be the human race is run
Joined: Apr 2001 Posts: 121,469PanzerMeyer
Pro-Consul of Florida
PanzerMeyer
Pro-Consul of Florida
King Crimson - SimHQ's Top Poster
Joined: Apr 2001
Posts: 121,469
Miami, FL USA
Originally Posted by Chucky
I think the last version I remember using was DOS 6.22. I also dabbled with DR-DOS for a while.
I'm pretty sure my last DOS-only PC game was "Apache" in 1995.
“Whoever fights monsters should see to it that in the process he does not become a monster. And if you gaze long enough into an abyss, the abyss will gaze back into you.”
I think the last version I remember using was DOS 6.22. I also dabbled with DR-DOS for a while.
I'm pretty sure my last DOS-only PC game was "Apache" in 1995.
What, "Apache" and no "Hind"?
Wanted to add that if it wasn't for DOSBox's memory management, I might not have been so keen on playing with DOS again. Even today I find it entertaining to watch MemMaker do its thing on my DOS PC (I actually used Quarterdeck QEMM), but I have no desire to deal with memory and compatibility headaches like back in the day, always trying to free up every byte of conventional memory. Nope, I don't miss that at all. Maybe a little.
EDIT: If you look closely at my Win95 receipt above, you'll see that I was one of those goobers at the CompUSA midnight grand release! :sheep:
Last edited by MarkG; 06/01/2007:52 PM.
The rusty wire that holds the cork that keeps the anger in Gives way and suddenly it’s day again The sun is in the east Even though the day is done Two suns in the sunset, hmph Could be the human race is run
But why go through the trouble you have to play these games in a simplistic windowed experience?
I have a real DOS only machine with CRT that I almost never use, because my emulation is so authentic and close to the real thing it is almost impossible to tell the difference, all the way down to the virtual display.
Mr_Blastman, I'm only using Windowed boxes for this thread as it shows I'm running DOSBox (I thought it would make things clearer while adding only a few border pixels to the pic).
Although sometimes I do run DOSBox Windowed if I'm needing to read something else off the screen (docs or code), and it's nice to have that option (in config file or Alt+Enter). I play my games full-screen unless I'm reading about or working on them.
The rusty wire that holds the cork that keeps the anger in Gives way and suddenly it’s day again The sun is in the east Even though the day is done Two suns in the sunset, hmph Could be the human race is run
Whew... I don't need to start a new "DosBox" thread in CH And MarkG seems to be really "up" on this stuff... Mark... are you there..... ?
I'll copy/paste the question I posted on the DosBox subreddit verbatim:
I bought "Task Force 1942" on Steam and it runs in DosBox. It runs fine except for no sound, which I can live with, but about an hour into the game my mouse started scrolling diagonally from lower right to upper left at a rapid rate. I can still move it some but I don't have real control over it as it is continually trying to make its way to the upper left corner of my monitor. This doesn't happen every time I play the game but often enough that it is ruining the experience, very frustrating to be over an hour into a campaign and have this happen.
Once it happens I have found NO WAY to make it stop, so game over at that point.
I did just get one reply on reddit:
"Got a touch screen? Disable it. Might need to use Device Manager to disable it. I'm not positive, as I switched to Linux.
Got a touch pad? Disable it with key combination.
Check what inputs the game is reading. Mouse, joystick, game pad, touch screen, touchpad, keyboard... might be reading multiples..."
I have no touchscreen or touchpad, running on desktop PC.
I guess I could try unplugging my CH stick, throttle and rudders while running TF1942.
HELP!
"In the vast library of socialist books, there’s not a single volume on how to create wealth, only how to take and “redistribute” it.” - David Horowitz
There was a 'mouse going haywire' issue with Dosbox on Windows if the display scaling was set to anything other than 100%. Probably not the issue here, but maybe worth a try.
Doesn't the game have a configuration program to set up sound etc?
There was a 'mouse going haywire' issue with Dosbox on Windows if the display scaling was set to anything other than 100%. Probably not the issue here, but maybe worth a try.
Doesn't the game have a configuration program to set up sound etc?
I will check those items, thanks!
"In the vast library of socialist books, there’s not a single volume on how to create wealth, only how to take and “redistribute” it.” - David Horowitz
It has diverged from Dosbox 0.74 quite a bit and a lot of these sorts of problems go away. ...with the potential for new ones of course.
I installed DosBox-x and ran TF1942 under it, ran well for a quick scenario with no issues other than still no sound. Well.. I have sound in the start up menus but not in game. Later I'll try the campaign and see if it can run for a couple of hours without losing mouse control.
Thanks again
"In the vast library of socialist books, there’s not a single volume on how to create wealth, only how to take and “redistribute” it.” - David Horowitz