For me, it wasn't truly full screen, it was closer to a wide-screen make-shift full screen. However, when I used my monitor's controls, I expanded the v. size and it, of course, went full screen. Ironically, with this game, anyway (Master of Magic), total full screen didn't quite look right. So I …

I used the controls on the monitor to adjust the v. size. That finally forced a true full screen. Fortunately, it did not mess with my typical Windows settings. I do the very same thing with misbehaving Win games. I am fortunate to have such an easily adjusted monitor. I can have independent …

robertmo wrote: have you tried reading my previous post? I would think that was *very* obvious. But, if not, yes, I read that guide and used various ideas within to no success.

I've tried everything that I could find to get DOSBox in true full screen mode instead of the wide screen mode to no success. Is there a way to get it to truly take up the entire screen? If so, how? These are the config settings, if they might be helpful: fullscreen=true fulldouble=false fullfixed= …

If you start dosbox with the -noconsole option, the output is redirected to stdout.txt. After a crash, it is filled with error messages that give info about the crash. It may help the developers if you tell what messages appear. JAL That's something to keep in mind if I run into any other problems. …

Indeed. Same for GF3Ti200. I have a GF3Ti200 and still use 4x.xx drivers. If it ain't broke, don't fix it. I commonly use several different Nvidia drivers. I like 30.82 (my oldest version) and 45.23. I was involved in a beta test of a recently released game. So I tried numerous versions. Every …

Mine is a GeForce 3 Ti 200.

Well, it simply may be because I have a different Nvidia-based graphics card than you.

FYI: Alt-tabbing DOSBox with Nvidia's newest drivers (66.93) causes DOSBox to crash (for me, anyway). My OS is WinXP SP2. I reverted back to the 61.77 drivers which corrected the problem.

It is very important when you ask for help here ... Even better are some strange log messages reported by DOSBOX (if there are any). Ultima 7 works in DOSBOX. Things to try 1. As with any DOS game - check sound configuration 2. One thing to try when Ultima 7 or 8 is crashing: delete content of …

Qbix wrote: right and we can all guess the error message ? Well, of course not! Geez! My work around was to use Exult instead. That solved the issue. I frankly did not think the abtruse DOS error message would be helpful, that was why I did not copy it down.

I got Ultima 7 and Forge of Virtue to install. I turned EMS off in DOSbox's config file. However, I get an error after I start a game, dropping me to the DOSbox desktop. Any ideas?

Maybe they do, but I cannot install Ultima 7. When trying to run the install program from U7's 1st floppy, it gives a DOS error of drive D not being ready, and make sure the drive latch is closed. Odd, drive D is CD ROM drive and only 5 1/4 inch floppy drives had a latch. This is 3 1/2 inch drive …

With DOSbox v. 0.62, changing cycles to 4000, and only allowing Soundblaster enabled, in fullscreen mode, the game plays very near perfectly. I wonder what kind of luck I will have with Ultima VII and Betrayal at Krondor. I miss being able to play those games. Thanks to all involved in providing …

Well, after I uninstalled DOSbox, then installed it again, it went back to working. Odd, since its config file was at its defaults in both cases.

My system: Asus P3B-F BIOS v. 1006 P3 850 MHz 576 MB RAM Nvidia GeForce 3 Ti 200 64 MB SB live DOSbox v. 0.62 DOSbox once worked. But no longer. No changes to my system. None, including no installations of any programs. It started 3 different times. Then no longer. All settings are DOSbox's defaults …