Guys, sorry to rehash this old thread, but I think you could find this interesting: http://veg.by/en/projects/syxg50/ Some guy reverse engineered the Yamaha S-YXG50 SoftSynth as a VSTi Plugin! You can then use it on applications which support VSTi Plugins like foobar2000 to play MIDI files. It was …

Jesus man. I would either upgrade the CNC software or use FreeDOS. DOSBox wasn't made to run DOS hardware device drivers... Half of the hardware devices you are talking about do not even exist on modern PC hardware. I do not have a 1.44 floppy drive, nor serial and parallel ports. It's all USB.

Cathegorized, best game first in each row. Turn-Based Strategy: Master of Magic (variety, balance) , Master of Orion II (MoM reloaded) , Civilization I (CivII only had a better combat system and I dislike isometric) Real-Time Strategy: Warcraft III (variety is the spice of life) , Starcraft (*the* …

I guess not all games are CPU heavy. Some really old games seem to be murder on I/O and I suppose a dynamic CPU core will not help with that. But for the more recent games, it usually rocks. When it works 😁.

Oh yeah, perhaps one of the cracks the other folks mentioned in the compatibility list will give you less trouble, since some of those patch the .EXE rather than running some TSR. The YCG crack is one of these.

You do not need fakecd per se since DOSBox does that work. What you need is the TSR called 'xcom3_cd.com' in that zipfile to remove the copy protection. I use this batchfile to start the game: xcom3_cd.com xcomapoc.exe SKIP rem *** UNINSTALL *** xcom3_cd.com With DOSBox 0.61 it seems the TSR gets …

Texture upload speeds in opengl are quite horrible though, using an nvidia extension helps it alot, but for non-nvidia people they'd better use the overlay support i think. How about using ARB_pbuffer and ARB_render_texture, at least on the cards which support the extensions?

I'm not using it anymore. 😁 Went back to v2.

With all that stuff you have inside your PC box, I would check if the case or CPU isn't overheating. Try getting a thermal monitor program and running CPUBurn in it for a while to see what happens. Oh yeah, the nForce drivers can be a problem, buggy as hell. Try the latest nForce drivers at the …

I have WinXP, a slower Athlon than you have and onboard graphics. MoM runs fine and fast here. Just press CTRL+F12 to speed up and CTRL+F11 to speed down. When the sound effects start stuttering, it is time to stop speeding up.

The game checks for the CD-ROM. The movies (intro, success, failure) are there, among other things. Even with a full install. I mounted the CD-ROM as drive D: using 'mount -t cdrom d d:/'. Then installed the game in 'c:/xcoma'. If you do not have the no CD-ROM patch it will not work. The patch to …

X-COM: Apocalypse works well with current CVS. I assume the recent dpmi.c changes did the trick by fixing function calls. That is a much better fix, probably solving problems elsewhere, for other function calls, rather than my hack. Two thumbs up for the quick problem solving. 😉

Got it working, both sound and graphics this time. Turns out that the minfo.WinFuncPtr field returned in VESA_GetSVGAModeInformation is the problem. If I return NULL instead, the game calls Function 05h and that works. I added some printfs. Turns out that if that field is set, somehow that function …

Be sure to use the latest patch on it. MOM is buggy like hell, even with that patch, without it, doom is certain to await you. Lovely game. Shame about the bugs. Never could finish as a Chaos wizard because Armageddon kept crashing the game.

BTW, here is some more info. The X-COM: Apocalypse game calls VESA_GetSVGAInformation with "VBE2" in the start of the passed buffer, calls VESA_GetSVGAModeInformation with mode=0x101, calls VESA_SetVGAMode with mode=0x8101. Hope it helps.

This time the UFOpedia.

Just suffered one of the strangest experiences in my life :eek:. Got the latest code from CVS, compiled it to see if that would work since 0.60 didn't. It was the same as expected. Then I started adding printf's all over int10_vesa.cpp to see what X-COM: Apocalypse was doing. By some strange twist …

I get exactly the same problem with X-COM: Apocalypse in DOSBox 0.60 that this guy had with the CVS versions: http://www.vogons.org/showthread.php?s=&threadid=2455 Unsuported Vesa mode? How can I check? BTW, the intro also seems to have some sort of problem. In that case, it is as if the screen …