I am using Dosbox .65 and have Windows Vista.

The first part might be solvable, ie. upgrading to dosbox 0.70.
After that be sure you configure the sound correctly, at first
maybe try with nosound.

I noticed the DosBox .7 version as I was reading this forum. I downloaded the new DosBox and experienced the same problems. For Apocalypse, the sound was stuttery with no video except the occasional garbled flash. I disabled the sound on both 2 and 3 and still get no video - just a blank screen.

Thanks for the thought, tho! I appreciate the feedback...any other suggestions?

thrasha88

Am I right in thinking that the first X-Com game doesn't use the DOS4GW extender? If so, I think you have the cause to your problems.

Perhaps a broken copy? My old floppies from that time tend to die already, among them was my X-Com 2 floppy set. You could have a corrupted file without noticing it.

You could try to replace DOS4GW with DOS32a (see the sticky topic in the forum for details). Apart from that and playing with configuration settings like memory and core, there should be no special action required. I have all three working.

For the sound stuttering in xcom3, try some high fixed value for the
cycles (also see the readme).

Hello everyone. I'm not sure if this is the right topic to post, but here is the problem: I got problems with running setup.exe to configure sound card of X-COM Apocalypse - it just hangs (with both versions 0.70 and 0.72) so I decided to try another distro and recently I got one, but when I tried to install the game using dosbox 0.72 the install has entered endless loop (seems like continuously checking files/directories on cd) with "Checking CD-ROM speed..." message, so I had to use 0.70 (there is no such problem, install works perfectly) to install the game but installed game refused to work with 0.70, but again the game successfully started when I used 0.72 to launch it (game works without problems except some crashes - I experienced them a long time ago when we all were gaming in dos/win95 so I think it's not dosbox problem).

It seems that something has changed in findfirst/findnext so they return one of the previous entries in directory what leads the program (X-COM's install.exe) to check the files again and again. - It's only my guess-work so there might be something else... The one thing I'm trying to say is that install works with 0.70 and hangs with 0.72 while with the game itself we see inversed situation 😉

Anyway - thanks a lot for your great work! 😎

hmm weird. I recall installing Xcom not that long before 0.71/72 and all was well then (bypassing the cdrom check by playing with the cycles)