Team, hi,

(I hope y'all don't mind me calling you that. We're in this together)

OK, got a tip from a reader last night, then did an RTFM in DOSBox. Seems that you just have to drill a bit closer down to the hardware, and then all the disk recognition problems in DOSBox 0.62 go away. Specifically, the following mount command:

mount D D:\ -t cdrom -usecd 0 -ioctl

whereas previously we had:

mount D D:\ -t cdrom

Seems to do the trick for *all* PCs. Two people who previously had problems confirm that they are now working fine. So, here's just a shortlist of great games we've got running in DOSBox 0.62 now:

Gabriel Knight: Sins of the Fathers
Under a Killing Moon
Pandora Directive
System Shock
Realms of the Haunting
Ultima VII
Space Quest 5

All the games that are working via ScummVM seem to work too! So, do we need a more compelling reason to go with this?! Yo, people, this singular solution seems to solve most problems with running old DOS games in XP, without having to treat each game as a separate case

What DOSBox does is emulate a certain amount of old PC instructions per millisecond. So, if a game is running too fast for you, you can even slow it down by adjusting its 'cycles' parameter. Once a game is up and running, you can use function keys to do the fine tuning.

DOSBox comes with a configuration file called dosbox.conf that is pretty easy to use. You can edit it with Notepad. What I do is get the dosbox.conf working for a particular game, then save that copy of it off in the game's install directory. Then when you want to run that game, just copy its dosbox.conf up into the main DOSBox directory and you're away. There are only really three areas in dosbox.conf you ever need to touch:

fullscreen=true (I always have this set)
cycles=9272 (you have to experiment. This value is for GK1 in VESA mode)

And the third area is at the very bottom of the file:

[autoexec]
# Lines in this section will be run at startup.
mount D D:\ -t cdrom
mount C C:\
C:

What's happening there? Well, we're mapping virtual drives to physical ones. You have to do all that gunk because DOSBox is so versatile that it will run on Linux, and Linux knows nothing about C:! If your CD-ROM letter was E:, that line above would look like this instead:

mount D E:\ -t cdrom

So that's it in a nutshell. I've got some pages here that cover various game set-ups in full detail:

See: Steve\'s XP Corner

Finally, a caveat:

DOSBox won't run *Windows* games, so don't expect it to solve your AMBER in XP problem But it is really good at running 'crossover' games that were made between 1995 - 1997 (like Pandora Directive) that have both DOS and Windows install options. Just install the DOS version of the game and away you go.

Well, that's about it. Hope that was helpful

------------------------

Comments? (as if... :-)

Steve

Ok, Dumb question--

I have read a lot about Dosbox--freeware-shareware--retail?????

Also, does it work only in XP--or if, like me, you have a 98 system also, would it be of benefit to install there???

And is Dosbox all you usually need to install--or is there another program you need to install with it??

Thanks

looney4labs, hi,

DOSBox is freeware!

It doesn't work on Win 98. You don't need it for Win 98 because Win 98 has a native DOS mode. The whole idea was to create a DOS environment for operating systems that don't have any, or have poor, DOS support. These are:

Windows 2000 and XP
BeOS
Linux
MacOS X

And to answer your last question... all you need is DOSBox. It only takes 10 minutes to install and configure. For instance, here are my set-up instructions for Under a Killing Moon:

-------------------------------------------------

1. Download and install DOSBox version 0.62 (or later). Get the Win32 installer version, which at the time of writing was called:

Dosbox0.62-win32-installer.exe

2. Wherever you installed DOSBox to, go there and edit the file dosbox.conf, replacing the section at the very bottom of the file with the following (Note: if your CD-ROM drive is letter 'E', then replace the 'D:' below with 'E:'):

[autoexec]
# Lines in this section will be run at startup.
mount D D:\ -t cdrom -usecd 0 -ioctl
mount C C:\
C:

Another note: you have to get that exactly right, so it's best just to copy and paste right out of this web page and into the dosbox.conf file using Notepad or a text editor. While you're in that file, you should also set: fullscreen=true (it's set to false by default) and cycles=13908. Note: you may have to experiment with the number of instruction cycles DOSBox emulates every millisecond, depending on the speed of your processor. I arrived at this figure by using multiples of 9272 (the setting which was recommend for DOSBox 0.60). I have a 2GHZ Pentium IV. Generally, the higher you can set this value to the better. You'll know you've set it too high though if the sound begins to stutter!

3. Open a Command Prompt (Start -> All Programs -> Accessories -> Command Prompt) and Install Under a Killing Moon to its default folder, C:\MOON

4. Manually copy the file: TEX197.EXE from the CD to the C:\MOON folder.

5. And now we're ready to roll! In a Command Prompt, switch to the folder where you installed DOSBox (for instance: cd \Program Files\DOSBox-0.62). Start up DOSBox by entering:

dosbox

Then enter the following 2 commands after it starts up:

cd moon
tex197

...and we're away!

6. The very first time you start the game, you are taken directly to the sound setup page. It's best to set up the sound manually. Use the following settings for the DIGITAL SOUND DEVICE:

SoundBlaster Pro, I/O Port: 220, Interrupt: 7, DMA Channel: 1

Accept the defaults for the MIDI MUSIC DEVICE: SoundBlaster, I/O Port: 388.

7. When it comes time to set up the screen and so forth, try setting the Window Size to: 640 x 480, and the Rendering Quality to: HIGH. If the in-game motion turns out to be not fluid enough for you, then you can set these parameters to lower values later.

-------------------------------------------------

So, what are you waiting for? I'm willing to help anyone who is having trouble getting a particular game running!

And one other thing. It's also a perfect tool for slowing down games that run too fast. Just keep reducing the 'cycles=' parameter until the game becomes playable

Regards,
Steve

Thanks a lot--will print this and put it in my file--so I can find it when I am ready to play all the older games I have been BAAGing

True DOS (what you find in ME and earlier versions of Windows) allows programs to directly access the hardware of the computer. With Windows NT/2K/XP/2K3 Server, you get NTVDM which is New Technology, Virtual DOS Machine. Virtual DOS does not allow programs to directly access the hardware of the computer. Old games, programmed to directly access the hardware, won't run on newer versions of windows for this reason. DOSBox is used, on games without copy protection, to bypass the NTVDM restriction.

I thought I'd clarify.


Gamehound

Thanks Gamehound!

I thought my explanation was long enough as it was, and didn't want to get too tech. I suppose I'm only willing to show so much of my 'geekness'

Hey, moderator! (I guess that's you, Inferno ) Any way we can make this thread semi-permanent? A lot of people are starting to experiment with DOSBox and it would be nice to have a place on GameBoomers to point them at.

Cheers,
Steve

Amen to that..........DOSBOX is a great little program!!

I'll "sticky" it so it will appear as "featured" thread near the top of the list.

Thanks Jenny!

On the DOSBox site I've seen references to dynamic core. Has anyone tried using that?

Using DOSBox on Mac OSX the things I can easily vary are the CPU cycles and frame skips. Has anyone found modifying frame skips useful?

Also is there much difference between DOSBox 0.61 (which I currently have) and 0.62?

Thanks Peter.

Peter, hi!

No, haven't tried it.

'frameskip' is useful if your machine can't keep up with the game, even on a high 'cycles' setting.

They are fixing bugs all the time, so I'd definitely get 0.62. It's quite possible that games that wouldn't run at all on 0.60 and 0.61 will run fine on 0.62.

BTW, I'm curently compiling a comprehensive FAQ on DOSBox that will be hosted here permanently. Give me a few days...

Cheers,
Steve

Thanks Steve! Look forward to seeing your FAQ. There is a lot of good stuff on the DOSBox site and the Wiki.

Steve...DOSBox 0.63 is available now..Glynn

Glynn, hi,

Excellent! I shall have to check it out. I believe they were trying to get this release out quickly to fix the CD-ROM reading problems they were having.

Thanks for the tip
Steve

You are welcome, Steve! I just downloaded it a couple of days ago. Thanks for all your help on the DOS games! Glynn

I hope, one day, that they get around the not being able to play games with copy protection. I don't see it happening anytime soon though.


Gamehound

Gamehound, hi,

Which games have you fell afoul of in this respect? I'd be interested to know...

TIA,
Steve

Hello Metzomagic,

It might be a dumm thing to ask
(have no techno knowledge whatsoever)
but I have windows XP and got the "7th guest"
to run. Is this already old news or is it worth
mentioning in a gameslist? I think I also had
a dos-Box (I installed everything that sounded
interesting from the internet!Have no idea what it all is though!)

I think the last time I tried DOSBox was v.57, so it is been a good while. I forgot what games I tried, but they wouldn't load because they had copy protection. I got them to load in 98 just fine though. If I remember them, I'll post.

One might have been Shadow of the Comet.


Gamehound

Was it the Windows or the DOS version of 7th Guest?

Inferno has a setup walkthrough for the DOS version here
7th Guest in DOS Mode

but the Windows version is easier to get running.

Hello Jenn,

I think it is the DOS version. My brilliant
tactic was to try out every file and every combination. Finally something happenend.
Have to start the game from an install file
though.

I've been running games in DosBox (version 0.61) with Windows 98 and it has worked perfectly. Getting the sound to work in DOS games in Windows 98 is often very hard, especially when using the DOS mode in Windows. And using the "pure" DOS that comes with Windows 98 often requires special drivers for your CD-player, and your USB devices, such as any modern mouse, won't work. Since DosBox emulates an entire DOS computer it's much easier to get DOS games to work than if you use any of the DOS options Windows 98 provides. And you can't alter the speed in the native DOS modes either.

So, DosBox is a good thing for Windows 98 users too!

frazap, hi,

This is great news! I suppose this must have happened when they introduced protected mode support in version 0.60? Either that, or DOSBox has always worked with Win 98 and I'm confusing it with VDMSound, which I'm pretty sure does not.

In any case, I will be sure to add this information to the FAQ I'm preparing for DOSBox.

BTW, this Win 98 machine you are running on... it must be a pretty high spec to get any kind of performance out of DOSBox! Are you running dual boot Win 98/XP or something?

Thanks,
Steve

Hello Metzomagic,

I have another question,

When i

Hi Steve,
Don't know whether this is a similar way of getting round the same problem. I have a slave drive of 500mb that is only set up with Dos, for some progs. I'm TRYING to write in Dos and Pascal. If a game won't load, or run, I tell 'puter to load them on Drive G (the Dos only drive) and I've not had any problems with them either loading or running.
Dave.