I've been playing Quest for Glory IV Shadows of Darkness (cd version) in DosBox 0.72 and suspect that sound effects are not being played. I remember hearing these while playing the game on older computers (which I no longer own/have access to) I could be mistaken, but shouldn't these sound effects …

I am having problems with Striker in Dosbox as well. I seem to be unable to select a skill level by pressing either the a, b, c, or d key. I can easily select a skill level when running the game in Windows XP's dos environment (ntvdm), but the game runs way too fast then. I am using Dosbox 0.65. …

I have been having similair problems in DOSBox 0.65. Prince of Persia II doesn't work properly when started with the "makinit" command line option (which starts the game in cheater/trainer mode.) One of the things that happen is that the prince looses all of his health when trying to move to the …

I think that whether any one thinks "What.exe" stores the user's choice in a bad or good way is irrelevant. It works in any DOS based operating system and if DOSBox is supposed to emulate DOS, the badly written (in your opinion) programs should also work in DOSBox... Then our opinions differ. …

The what.exe issue is a known issue, and I seem to recall that Qbix has no plans to address it. What.exe does not work in DOSBox nor the Win2K/XP NTVDM (Windows command prompt) because it stores the result in an environment variable (a bad way to do it - they should have used an error code instead …

Qbix wrote: should be fixed/improved in the next version. Problem was that the dosbox kept on drawing in the fullscreen buffer after the os switched to windows mode. That's great news. Hopefully the bug will be fixed then.

The batch file and "What.exe" are not crappy. They work just fine under Windows 9x and MS-DOS. I checked if they would work under Windows 98 and they did. When running the batch file under Windows XP using "Cmd.exe" or "Command.com" outside DOSBox, the batch file responds when I select a language …

I found some new information: When running DOSBox with the -NoConsole command line switch, I find the following in the "StdErr.txt" file after the provoking the error I described in the previous post: Fatal signal: Segmentation Fault (SDL Parachute Deployed) Hope this helps. EDIT: I did some …

When running Microsoft Debug in DOSBox, Debug does not respond properly to my keystrokes. The Backspace key does not erase the input, the Delete, Insert, Home, End, Page Up, Page Down and arrow keys cause a letter preceded by a space to be displayed rather than performing the intended function. (btw …

DOSBox always terminates without warning when I press the Windows key (Causes the Start Menu to appear and forces DOSBox to use a window instead of the entire screen.) or when a program displays a message box, for example, while running DOSBox in a full screen. DOSBox does not crash when it is …

Well, I installed DirectX 9.0 and it didn't help. It should be the most recent version according the Microsoft DirectX homepage.

Capslock does work for alphabetic keys. Did you mean that updating DirectX helped fix a problem with the keyboard in DosBox for you?

The Shift key doesn't work at all. After some more testing I found out that the Alt and Num(ber) Lock keys don't work either. I also hooked up a United States layout keyboard to the PS/2 port of my laptop. DosBox responded in the same way as with my laptop's internal keyboard. So I don't think it's …

I don't want another layout, I want the United States layout and if that's what DosBox gives me, that's great. The problem is that the keyboard works fine in DosBox except for the Shift key. Where can I get this Keyb utility and what does AFAIK mean? I only pointed out that my keyboard actually has …

I've just installed DosBox version 0.63 for Windows. All keys seem to be working except for the shift key. My keyboard is set to the following language: English (United States) although it's actually an English (British) keyboard, the only difference being that the @ and " characters have switched …