It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
Ok, my whole life I have been a console gamer and still am. I do like PC gaming and have always been drawn to the entire decade of the 90s when it comes to PC gaming. However, I know very little about DOS or how it works. One of my big questions is, what was the native resolution for DOS games? Did it vary? I've seen where sometimes the windows were very small, like ~300x200. Back in the day, were DOS games just played on a black/blank monitor with a small window for the game? I ask because now if you enlarge the resolution, you get a really grainy, pixelated display, making me wonder what the resolution is truly supposed to be. I also have a hard time knowing if a game I'm running in dosbox is running properly or at the right speed. Sometimes it seems the music/video is off, but having almost no experience with the program, I can't really tell. Dosbox does emulate old games and is rather finicky it seems, so does anyone have any generalized tips for me as a beginner? I use both the GOG games and outside abandonware type stuff on dosbox. Thanks!
This question / problem has been solved by Rakuruimage
I use DosBox all the time for older games and abandonware. I even use Dosbox mounted with a CD so I can experience the "talkie" version. However, I have no idea about the about the resolution but I did google and these are two of the right things that fit the questions.. I think. lol

http://www.classicdosgames.com/tutorials/advanceddosbox.html

and this one talks about exactly what you are asking from what I am reading.

http://forums.anandtech.com/archive/index.php/t-2171210.html

^this one is talking about gog and the native resolution.
Post edited July 12, 2014 by Sage103082
avatar
Ultra_DTA: One of my big questions is, what was the native resolution for DOS games? Did it vary? I've seen where sometimes the windows were very small, like ~300x200. Back in the day, were DOS games just played on a black/blank monitor with a small window for the game? I ask because now if you enlarge the resolution, you get a really grainy, pixelated display, making me wonder what the resolution is truly supposed to be.
DOS supported different video modes/resolution depending on the game and graphics card. See this section of the DOSBox wiki for some details on the video modes that DOSBox supports. For example, very early DOS games typically used CGA which was 4 colors and 320x200 resolution. Later, VGA was common -- 16 colors at 640x480 or 256 colors at 320x200. Other modes include EGA, which was between CGA and VGA, and SVGA (Super VGA) which came after VGA and supports up to 32-bit color at 1024x768 on DOSBox. Once you figure out what graphics mode(s) the game you want to run supports, you can change the setting in the dosbox.conf file to whatever it needs, if different than default. (Though the default SVGA is pretty backwards compatible, so you can often leave it on that.)

Pixelated graphics are to be expected to some extent with DOS games, but it will probably be worse if you're using a huge new LCD screen (especially if it's widescreen). Back in the DOS era 15" and 17" monitors were pretty common. I use a 17" 4:3 CRT for my fullscreen DOS gaming and it works fine, although you can still have fun with DOS games on an LCD monitor and get them looking pretty good if you don't need 100% historical accuracy.
avatar
Ultra_DTA: I also have a hard time knowing if a game I'm running in dosbox is running properly or at the right speed. Sometimes it seems the music/video is off, but having almost no experience with the program, I can't really tell. Dosbox does emulate old games and is rather finicky it seems, so does anyone have any generalized tips for me as a beginner? I use both the GOG games and outside abandonware type stuff on dosbox. Thanks!
Getting certain games running on DOSBox can be tricky even after you've used it for a while. The trick to getting anything running properly in DOSBox almost always lies with the Dosbox.conf file, so familiarize yourself with that. You can have different .conf files for each game and use a command flag on the shortcut of the game so it knows to use that conf instead of the general dosbox.conf -- useful if you have several games that require something other than default settings.

If you don't know what needs to be changed for the game (especially if you don't have much experience with DOSBox yet), it's best to do some research on the internet and figure out what settings work best for that game -- Google "DOSBox" plus the name of the game plus "conf" or "cycles" or whatever you're trying to figure out. DOSBox has a pretty good Compatibility section on their website that will tell you how well a game is supported by the latest version of DOSBox and often has useful comments about the number of cycles that's best or other settings that may need to be changed.

Most common .conf settings that will need to be changed:
cycles (speed the game runs at, older games especially will need to be set manually to a lower number of cycles; newer games often work okay with auto -- this can be tricky to get just right and is often a matter of using the DOSBox hotkeys while running the game to change the number of cycles on the fly until the game 'feels right', which can be difficult if you've never played the game)
machine setting (graphics mode: CGA, EGA, VGA, SVGA, etc)
fullscreen (set to true if you want it to default to fullscreen. use ALT+Enter to toggle fullscreen and windowed mode at any time)

Since emulation is less efficient and requires more processing power than running directly on the native hardware, some later DOS games (mid-late 90s) can be a pain to get working at acceptable speeds on most machines, so don't feel bad if you can't get every game working flawlessly right away. Sometimes it's a choice of spending hours and hours on obscure forums trying to figure out which hidden settings you need to tweak to get the game playable or just giving up and doing something else. Thankfully most popular games will have plenty of information out there to help you configure DOSBox for them, so unless your tastes run very obscure, it shouldn't be too hard.
Post edited July 12, 2014 by Rakuru
avatar
Rakuru: machine setting (graphics mode: CGA, EGA, VGA, SVGA, etc)
There's another graphics mode you haven't mentioned. When Windows 95/98 were around VESA was an option. VESA added support allowing more video options, resolutions, etc. I tried out the API (in assembly language) and it wasn't bad; However it came out too late. Windows and XWindows were becoming more popular (allowing 32bit addressing) so VESA became pointless.

Thinking back the only program i can think of that used VESA, was FractInt
Thanks for the replies, especially your thorough one Rakuru. I was born in 92, and my experience with PC gaming runs about as deep as Runescape, Age of Empires, and a couple of Civ games, haha, So, as you can imagine, DOS gaming is completely alien to me. There's just something about it though. Maybe it's the fact that it is relatively difficult to use, making DOS gaming sort of cult-like, if that makes sense. I've grown annoyed with what console gaming has become, with things like DRM, day one DLC, and mandatory installs, so I find a lot of these older PC games refreshing in a way. I really wish I had grown up in that era, with those games. It seems like a daunting task trying to familiarize myself with DOSbox, and to a lesser extent, post-DOS PC gaming. Thanks again. I'm all for keeping up the conversation however, every thing I can learn helps!
avatar
Ultra_DTA: It seems like a daunting task trying to familiarize myself with DOSbox, and to a lesser extent, post-DOS PC gaming. Thanks again. I'm all for keeping up the conversation however, every thing I can learn helps!
It shouldn't be all that daunting. I find it so surprising that so few use the command-line to do things. Sure you have to memorize like 30 basic commands in order to get around while everything else you refer to a manual (or for unix, man pages). In my opinion, the command-line is vastly superior to GUI's, and most of that is through the usage of batch file programming and piping (sending the output from one program as the input to another).

Making computers easier to use (1982)
Well like I said, I'm used to taking a disc or cartridge and popping it in and having it work. It was very bizarre the first time I had to enter commands into a window to get a game to work. I'm not all that familiar with the vocabulary or abbreviations either. Lol.
I use a DosBOX frontend, which makes things much easier for me.

D-Fend Reloaded
avatar
Ultra_DTA: Well like I said, I'm used to taking a disc or cartridge and popping it in and having it work. It was very bizarre the first time I had to enter commands into a window to get a game to work.
Oh, also you can use shortcuts so you don't have to type in commands every time you want to play a game. When I first started using DOSBox I would always just go to the main DOSBox executable and have to try to remember what folder I needed to mount and where the game was, but once I took a little time to figure out how to automate things it ended up saving a lot of time in the long run.

For example, here's the 'target' for my shortcut to Elder Scrolls: Arena:

"C:\Program Files\DOSBox-0.74\DOSBox.exe" -conf "C:\Documents and Settings\*myusername*\Local Settings\Application Data\DOSBox\arena.conf" "C:\ARENA\ARENA.BAT"

The first part is the location of the DOSBox executable, the second part is the location of the conf file you want to use (omit this if you want to use DOSBox defaults), and the last part is the program you want DOSBox to run. The actual locations of the files will vary depending on your version of Windows and how you've installed and organized things. You can set up a shortcut quickly by copying the shortcut to DOSBox or an existing DOSBox game shortcut, right clicking on the shortcut, clicking on Properties, and editing the Target field. (At least in Windows XP, although I believe it's pretty similar for any version of Windows.)

If the game requires running some more advanced commands in DOSBox before starting the program, you can use the section at the end of the conf file. Any commands in that section will automatically run when DOSBox is loaded with that conf file. I don't have to use [autoexec] often, but sometimes games like Elder Scrolls: Battlespire will do something funky like require a virtual CD for music, so I have to put something like this in there:

mount c "F:\Games\PC Downloads\An Elder Scrolls Legend Battlespire\"
imgmount d "F:\Games\PC Downloads\An Elder Scrolls Legend Battlespire\Battlespire.cue" -t iso
c:
cd batspire
spire.bat

and the shortcut just points to "C:\Program Files\DOSBox-0.74\DOSBox.exe" -conf "C:\Documents and Settings\*myusername*\Local Settings\Application Data\DOSBox\battlespire.conf"

Or you could look into a frontend like Sabin_Stargem suggested above. I don't have any experience with DOSBox frontends specifically, but they usually require a little bit of effort up front to set up and then things are pretty easy.
Post edited July 13, 2014 by Rakuru
avatar
Rakuru: but sometimes games like Elder Scrolls: Battlespire will do something funky like require a virtual CD for music, so I have to put something like this in there:
Looks more complicated than it should be...

I can't help but wish that games were more like modules on Slax, where you mount it and it's ready to go, all pre-ready... unmount it and it's gone like it was never there..
avatar
rtcvb32: Looks more complicated than it should be...

I can't help but wish that games were more like modules on Slax, where you mount it and it's ready to go, all pre-ready... unmount it and it's gone like it was never there..
Yes, Battlespire was an absolute pain to get running, even ignoring how it required streaming music from the (virtual) CD. It's one of those late-era DOSBox games that requires a ton of horsepower to emulate; even after researching the optimum conf settings to squeeze out maximum performance I was only able to manage a just barely playable framerate (and I have a pretty high pain threshold to begin with). On top of that, I had to go down to about 50,000 cycles during FMV cutscenes to keep them from stuttering like crazy, but had to jump back up to 100,000 cycles afterwards to get smoother gameplay (and even then the higher cycles caused some audio glitches).

Luckily most games are much easier to get running, although I have to admit that sometimes half the fun is figuring out how to get a stubborn game to behave! And the nice thing about emulation is that it will ideally get easier and easier as time passes and support is added for more games and more user-friendly methods are discovered. Already there are some good frontends that make playing emulated games very easy once they're set up; it seems that the developers of the actual emulators tend to focus on the technical stuff and make sure the games actually run well and leave the actual user-friendly part to third parties.
Low-resolution graphics will look blocky. They were always blocky, but when the screens were smaller, so were the blocks, so it's a bit worse now than it used to be.

There are some graphics scalers in dosbox that attempt to hide it a bit. Obviously it won't then look authentic, but it may look more pleasant to you, depending on your preferences and the game in question. Check out this.

I prefer it blocky, sometimes with scanlines.

EDIT: I meant to also mention that the games in 320x200 don't have square pixels, and will thus look vertically compressed without any scaling.
Post edited July 13, 2014 by Rixasha
avatar
Rixasha: I prefer it blocky, sometimes with scanlines.
Hmmm reminds me of the genesis emulators i used to love playing...
avatar
Rixasha: I prefer it blocky, sometimes with scanlines.
avatar
rtcvb32: Hmmm reminds me of the genesis emulators i used to love playing...
Ha, relatively speaking genesis emulators are a total breeze.

I don't mind "blocky" graphics. I understand and appreciate the age of the games, and I've never been one to really care about graphics. I am more concerned with playing the games as it was meant to be, at least to some capacity. I'm mainly concerned with getting the game to run smoothly, and in the correct resolutions/aspect ratios. There just seems to be quite a bit to learn. Are resolutions; say 320x200 a window size or what? I guess I associate resolutions with window sizes just from adjusting my monitor's display. What resolutions were most common for dos games? Should the game screen I'm playing on be really small, or will I be able to increase the size of the window and maintain the resolution/aspect ratio?

Thanks for tolerating my lack of knowledge! Thanks again.
avatar
Ultra_DTA: I'm mainly concerned with getting the game to run smoothly, and in the correct resolutions/aspect ratios. There just seems to be quite a bit to learn. Are resolutions; say 320x200 a window size or what? I guess I associate resolutions with window sizes just from adjusting my monitor's display. What resolutions were most common for dos games? Should the game screen I'm playing on be really small, or will I be able to increase the size of the window and maintain the resolution/aspect ratio?

Thanks for tolerating my lack of knowledge! Thanks again.
Well in DOS naturally there was no 'windowed mode', those only came with Windows, and not all of them worked right. Early on most higher resolutions were still 256 colors and the color palette had to be replaced so everything OTHER than the game were funky, sorta the way things were...

I hate tiny screens so window mode seems stupid.You could double resolution and add scanlines and games will actually look better, video too although it's not as bright. I think this is a trick partially due to the brain fills in the details and makes it work for you, and there just wasn't that much data for your brain to figure out or fill in.

So common resolutions. There's really two sets, 320x200 and 320x240, then there's 640x400 and 640x480. I think the only reason the heights of 200 & 400 exist were because it kept the memory location for doing the graphical programming in1 and 2 segments keeping it relatively small and easy to program, while the resolution you'd prefer would be the other two (240 & 480). I'm not sure how much cleaner games are especially with aspect ratio but the more resolution the better it looked since there was just more you could put there.

I'm not sure what all DosBox brings for dealing with resolutions, but if there's resolution enhancing features then the true resolution DosBox translates for the games is considerably higher than what was originally there. Raising resolution is easier and cleaner if you keep it at powers of 2, so either 2x or 4x larger. With the SNES I know they added a bunch of filters that do the same thing, and for the most part they made the games look bad in my opinion (and run a lot slower) I'd rather run them blocky than enhanced and weird...

But that's a bunch of side stuff that doesn't mean it is very useful...