This isn't going to help but: I have been able to get both games working fine under Windows 2000...without sound, of course, because NTVDM does not support sound. They SHOULD work fine WITH sound with this program: http://ntvdm.cjb.net/ (This program enables sound under NTVDM boxes for DOS games). I have not verified if they work with VdmSound but I do know that they work fine without any tampering with memory settings in Windows 2000. Just extract and run the .exe
 
Now as for NT4....that's a different story. I haven't tried those games under NT4 so I'll see if I can find the time to do so. I do not see why they would not work however.
 
The problem of why the games are not working could be as simple as your telling the game to use sound (which errors it out) or a messed up game.

Thank you for taking a look at this problem for me, i appreciate it. I did install the NTVDM sound support. It did not fix the problem, but it does allow me to use sound in some other dos apps, so that is a nice change.... The problem with both MoM and MOO is the same,(they both use a virtually identical version of the same engine, namely expanded memory. Having played around and experimented with the memory settings for DOS programs in the NT .pif file. I have found that the settings in the .pif file have little to no effect at all.. for instance, if you set expanded memory to any setting whatesoever, the program completely ignores it... even when you go to the command line after setting your various memory options, the MEM command reveals that no changes actually take place. I hate to sound like a microsoft conspiracy theorist, but it seems as tho microcrap only put the memory setting windows in NT4 as a placebo to placate us old DOS folk and hoped that no one would look too closely. I am running NT4.0 with SP6 and all the latest updates. If anyone out there can help me out with whatever i am overlooking here.. I would greatly appreciate the enlightenment as this problem seems like such an easy fix on the surface.
 
Frustrated,
Michael R. Taylor
SGT, US Army
Soto Cano AFB, Honduras

That problem I can explain! The memory setting do apply! But ONLY for the .pif that the executable goes to. When you do a start/run/cmd it uses the _default.pif in the \winnt or \windows directory (for XP).
 
Simply modify the _default.pif and config.nt/autoexec.bat to alter your memory settings.
 

Quote:Frustrated,
Michael R. Taylor
SGT, US Army
Soto Cano AFB, Honduras

Army on an AFB. I bet that's fun!
I'm currently in the AF station in the UK.

Well, actaully i had already tried modifying the _default.pif file when i read about it in the NT help. I currently have it set to provide about 16 megs of expanded memory and I have set the EMM=RAM line in config.nt and yet it seems to do nothing. I just went through and double checked everything i just stated and then went to the command prompt and typed MEM again with the follwing result.
 
655360 bytes total conventional memory
655360 bytes available to MS-DOS
596416 largest executable program size
 
28311552 bytes total contiguous extended memory
0 bytes available contiguous extended memory
16619520 bytes available XMS memory
MS-DOS resident in High Memory Area
 
as you can see, depite all the settings in the _default.pif file the computer still seems to think that all the extended memory is used.... also note that the total contigous extended memory number is no where near the 16Mb i had specified in the .pif it was these results that so initially confused me. I am completely baffled as to why NT seems to think that all available extended memory is gone. Also, older DOS progs are not too attached to *extended* memory, they are hungry for *expanded* memory of which i apparently have none despite the 16Mb specified in the *.pif
 
Contemplating urinating over my NT system,
Michael R. Taylor
SGT US Army
Soto Cano AFB
 
P.S. I love working for the AF actually.....

Have you tried to run the game using "Run with VDMS", from Explorer (right-click on the .exe) ? Does the memory problem still persist ? If so then you may have a messed-up NT4 installation; I have such an installation at work, where no matter what values I put for EMS it won't take it. I know (at least) MOO1 works fine under NT4, and the memory settings should also work fine, i.e. they are not "placebos". Have you removed any files, even if they looked totally useless, from the SYSTEM or SYSTEM32 directories since you installed NT ?
 
Vlad.

I tried running it on the other two comps in our office both running nt$.0 sp6 and got the same results... however when I had the opportunity to abuse another offices computer with the same nt4.0 sp6 setup all the EMS hungry games worked great! Now I just have to figure out a good excuse to have the IT guy come over and reinstall NT Thanks for the suggestion....

In terms of NT4 machines that work and those that do not work with EMS: do those that do *not* work have the third-party '4NT' shell installed (as opposed to those that work with EMS)? Just a wild guess.