You need to call Mok's System Shock EXE with DOS4GW.EXE as such: DOS4GW.EXE CDSHOCK.EXE He kept his nifty debugger extender in there and it fucks up a lot. Nah, it's not my extender. It's an ex-commercial (now free) dos4gw replacement: causeway dos extender, used by quite a lot of games in the past …

Yes, that's why I said "going to be a long time" If I had the access to working source code, I could (probably) fix the game to work on newer computers/systems. Unfortunately I don't have time (or maybe enough abilities) to make a portable C version, so I won't ask the scummvm team for the sources …

What would be great would be if someone (Mok?) wrote a program that could replace ALL major DOS extenders, that was both DPMI 0.9 and 1.0 compliant (if possible?) and that was DEFINITELY Windows 2000/XP happy. A Good Project, IMHO. Ooh - it could maybe automatically detect executables that have …

So what exactly was the issue that was causing the mouse problem and was fixed in the patch? Sorry, I am really busy lately, and I had no free time to visit the forum. Right after reading the current mouse coordinates and checking if they are within the boundaries, the mouse handler callback was …

Snover wrote: Mok, just upload it here if you can. 😀 Ok. It's the executable from the patch, so you need to install the game, patch it and then replace the exe file. I haven't tested the game much, but I hope the mouse problem is gone for good 😉 -Mok

Had a problem with my mouse. peter's excellent utility fixed it. W00t to peter. W00t to Mok. W00t. Vlad, mouseset is officially phased out. :D Bah. Now the DOS extender craps out on me. Are you sure you uploaded the correct EXE? ;) Heh... Indeed I forgot to change back Causeway to big'n'ugly dos4gw …

VCPI Titles[/b] Dungeon Master II Wing Commander: Armada Strike Commander (Origin) Pacific Strike Privateer Wings of Glory Of course, if VCPI wasn't the issue, then maybe they really aren't fixable. Origin's memory manager - JEMM - requires VCPI so these titles aren't fixable without major changes. …

What throws me is that it used VCPI memory and that was supposedly a dead-end for running within Windows without some form of (real) DOS emulation. Only thing I can guess is that the modifications you made were related to the only parts of VCPI that were incompatible (if you know what I mean). No, …

IMHO, this is normal. The game attempts to access both com ports on its own (no idea why, but the code is definitely there...), so if you disabled them, you'll get that dialog box. Not only in this game but in anything that tries to access com ports directly from dos. As for fixing the game... I …

Email me and I'll send you fixed executable without the mouse problem. -Mok

Actually, it wasn't really hard to get SS1 running under XP. But it's badly written and attempts to read memory outside of allocated areas causing crashes after few minutes of playing. I solved it by allocating additional 4kb of memory for each block and so far it works, at least here. I used: - …

I have recently examined BASS, looking for the reasons why it doesn't work at all under XP. The problem is Flashtek/DosX/X-32 Dos Extender and shitty implementation of DPMI host in XP. Flashtek uses nasty hack to allow client program to access low 1MB of memory and it's simply not compatible with XP …