Re: Trouble running Grand Prix Circuit (1988) in DosBox
Posted on 2010-06-16, 12:03
The problem described in the first post appears to have been fixed in DOSBox 0.74.
Re: Trouble running Grand Prix Circuit (1988) in DosBox
Posted on 2010-01-02, 11:13
I wasn't trying to be dismissive if you really want to know why the problem occurs; it's just that not everyone does. ;) SP=2 causes a 16-bit segment wrap of the stack pointer that DOSBox doesn't take into account. The CPU flags that were lost in the wrap with IRET were inconsequential, but the …
Re: Trouble running Grand Prix Circuit (1988) in DosBox
Posted on 2010-01-01, 20:46
the news stuff is a selection of what we think is interesting to write down. It is nowhere complete. DOSBox has lots of changes each version. Specificly this problem was introduced when the way to start executables was changed from an IRET to a RETF. One game needed this (this saves a byte on the …
Re: Trouble running Grand Prix Circuit (1988) in DosBox
Posted on 2010-01-01, 20:08
In DOSBox versions after 0.72 there is an issue with GP.EXE regarding an unusually low initial stack pointer specified in the executable header. I have reported specifics of the issue to the devs, and a fix may be made at some point. Thanks for posting about the problem. I see. According to the …
SOLVED - Trouble running Grand Prix Circuit (1988) in DosBox
Posted on 2010-01-01, 11:51
Hello, I'm having some minor trouble running the game Grand Prix Circuit (by Accolade - 1988) in DosBox 0.73. The game itself actually runs with no problems; however the program gp.exe which displays a menu allowing you to select a graphics mode always freezes immediately after being launched. All I …
SOLVED - Problem with Supaplex in DOSBox 0.73
Posted on 2009-10-10, 10:10
When playing Supaplex (by: Dream Factory, 1991) with DOSBox 0.73 running in EGA (instead of SVGA_s3) mode, there's an annoying bug: 9 out of 10 times Murphy (the character controlled by the player) immediately dies (explodes) when I enter a level. Also, the few times this didn't happen I have …
Re: Sound effects not being playing in Quest for Glory IV Shadows of Darkness
Posted on 2009-04-29, 16:52
Post the contents of your RESOURCE.CFG. You can also try my QfG4 DOSBox installer . That installer helped me figure it out, for some reason the Quest For Glory setup program "forgets" some critical entries in the resource.cfg file. Which should look like this: videoDrv = VGA.DRV soundDrv = ADL.DRV …
Re: Sound effects not being playing in Quest for Glory IV Shadows of Darkness
Posted on 2009-04-29, 12:20
Here is my resource.cfg: videoDrv = VGA.DRV soundDrv = ADL.DRV audioDrv = DACTHUND.DRV joyDrv = NO cmd = QG4CD mouseDrv = NONE memoryDrv = NONE minMemory = 1600k brightness = 0 language = 1 minCPU = 386 CD = yes EDIT: I forgot to mention that the music is fine (at least for the most part) and I can …
SOLVED - Sound effects not being playing in Quest for Glory IV Shadows of Darkness
Posted on 2009-04-28, 19:49
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 …
Re: No joystick support in Rampage and Striker
Posted on 2007-01-17, 20:10
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. …
Re: Keyboard ctrl-alt-shift commands not working
Posted on 2006-05-27, 15:16
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 …
Re: Keyboard problems in Microsoft Debug and a few other similair programs->
Posted on 2006-03-27, 20:39
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. …
Re: Keyboard problems in Microsoft Debug and a few other similair programs->
Posted on 2006-03-27, 20:12
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 …
Re: DOSBox terminating without warning and no error message when switching from a full screen to a window.
Posted on 2006-03-26, 10:07
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.
Re: Keyboard problems in Microsoft Debug and a few other similair programs->
Posted on 2006-03-26, 10:02
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 …
Re: DOSBox terminating without warning and no error message when switching from a full screen to a window.
Posted on 2006-03-25, 21:36
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 …
Keyboard problems in Microsoft Debug and a few other similar programs->
Posted on 2006-03-25, 21:05
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 …
SOLVED - DOSBox terminating without warning and no error message when switching from a full screen to a window.
Posted on 2006-03-25, 19:38
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 …
Re: Shift key doesn't work.
Posted on 2005-11-18, 14:46
Well, I installed DirectX 9.0 and it didn't help. It should be the most recent version according the Microsoft DirectX homepage.
Re: Shift key doesn't work.
Posted on 2005-11-18, 14:40
Capslock does work for alphabetic keys. Did you mean that updating DirectX helped fix a problem with the keyboard in DosBox for you?
Page 14 of 15