Is the directory containing the registration file mounting correctly under Linux? Remember that the path delimiter in Linux is a forward slash (/) instead of a backslash, and that file and directory names are case sensitive. If you're using the same mount command on both OSes, confirm that the path …

I've also been able to get 132x60 to work using UNIVBE and MODE.COM (from FreeDOS) on the Daum build.

Ctrl+Drag in Win 3.1's file manager.

If you are trying to upscale your video and get proper aspect correction, the best way to do that is to upscale to 1600x1200 using a nearest-neighbor/point filter. 320x200 graphics meant for 4:3 display require upscaling to 1600x1200 or an exact multiple thereof to view without artifacts or …

Unfortunately, I don't think ANSI keyboard remapping is actually supported by DOSBox, even with an external ANSI driver loaded. Given that it's an EGA game with PC speaker audio, you probably won't lose anything by using QEMU or VirtualBox to play, and you can use FreeDOS -- it includes NANSI.SYS, …

I don't get the point of having synthesizers built internally (except on phones due to platform limitations). Running Munt or Fluidsynth as a MIDI service on your computer is not hard. There's one major benefit: with the synth integrated into DOSBox, the MT-32 or GM music is included in the audio …

I've got a pretty simple solution for this. I start DOSBox via a shell script that launches both Munt and Timidity, then uses aconnect to determine the ALSA ports for each, and finally launches DOSBox with parameters to assign them to environment variables (e.g. dosbox -c "set munt=$munt_port" -c " …

DOSEMU with the '-dumb' argument will run DOS executables within the host shell and map the DOS stdio streams back to the host stdio streams. I don't know how compatible DOSEMU is with BSD, though -- it's primarily developed for Linux, although there was a port to NetBSD at one point. It might take …

If you are using the builtin capture it will be the original resolution of 320x200. You will have to resize after the fact or use a 3rd party capture utility. The best solution is to use VirtualDub or FFMpeg to upscale the 320x200 to 1600x1200 using a point/nearest-neighbor scaler, then downscale …

Just a quick note: the reason I asked about 10 FPS above is that in Sierra SCI games, like SQ1 VGA, I believe the actual game's framerate is limited to 10 FPS. Capturing at a greater rate will result in superfluous frames in your video.

Daum runs fine in 64-bit Linux: if you're running the prebuilt binaries from YKHWong's web site, just make sure you've got the 32-bit versions of the needed libraries installed. How you do this will vary from distro to distro -- in Arch, you'd enable the multilib repos, then install the 'lib32' …

What happens if you record at 10 fps?

If you're using Mint, the Munt package that's in the repo should already include the GUI. Install it with sudo apt-get install munt , then run mt32emu-qt to launch it. Open "ROM Configuration..." from the "Options" menu, and point it to the directory where you've got the ROM images stored. Then all …

I suspect that this may be the source of the problem: > mount e h:\ -t cdrom Try unmounting the image from the virtual CD drive on the host system, and mounting the image directly within DOSBox, using the imgmount command, e.g.: imgmount e image.iso -t cdrom

SendSX works fine with Munt, but Munt instantiates a separate emulated synth for each process that connects to its driver. So you can send the sysex to Munt with SendSX, but since you must play the midi file through some other program, the midi will actually be playing in a different synth than the …

I'm sorry to dig up such an ancient, ancient thread, but I actually got here via a Google search while looking for a solution to this exact problem. I've found a way to do this, so I figured I'd post my solution in case anyone else stumbled across this thread the same way I did. My method was to …

The standard way of passing arguments through batch files (either DOS .bat or Windows .cmd) is to use the variables that the OS automatically assigns to all parameters after the command, beginning at %1. For example, if I had a batch file called foo.bat, and ran it with parameters after the command …