MoO1 trying to run in XP, help !? - Page 2

boolybooly · January 27, 2004, 13:42

Garth the Apolyton ad takes 15 secs then the CPUID servers are v slow, it works but takes about a minute to load the page here in the UK. DL is swift.

Garth Vader · January 27, 2004, 16:08

I emailed it home from work so it will be there when I get home.

boolybooly · January 28, 2004, 07:45

http://www.columbia.edu/~em36/wpdos/emsxp.html

a chap in nForcers HQ suggested this so I am passing it on, might works for some people, but it didnt work for me.

I have got DuneII to run on this setup, but that uses extended memory instead of expanded. However there is another glitch with the music on that though the unit voices work fine in most SB emulation modes !? (nForce2 uses soundstorm).

I think this chipset has a lot of kinks to work out.

Garth Vader · January 28, 2004, 20:01

My specs from CPUID

Athlon XP 2400+ 2Ghz

Epox MB, nForce2 Ultra 400, 512MB PC2700 RAM

Bios date is 3/5/2003

vmxa1 · January 28, 2004, 21:50

I had PC2700 in my current PC until I replaced it with pc3200, so I doubt if it is the problem.
I have had AMD cpu's work, so I would suspect that nforce2 MB combo.

boolybooly · January 29, 2004, 05:02

alglove on nForcersHQ Epox forum turned up this little gem

http://www.zeuxworld.com/index.php?act=article&id=58

here is something to freeze your blood, Award have allegedly decided not to support EMS anymore. So if true all nForce2 boards will have problems and there is no work around.

Quote:

newer PCs with an Award/Phoenix BIOS (this INCLUDES ALL nForce2 chipsets) will not be able to run MZX on Windows XP, XP SP1, 2000 SP3,4, 2003 because resource allocation was changed in these builds of windows and the BIOS no longer reserves the EMS base page frame address. No game requiring EMS will run on these configurations on these machines. There is no known fix at this time

vmxa1 · January 29, 2004, 12:48

That is nasty. I will have to be careful in the future about any new rigs.
The funny thing is I have had two recent vintage motherboards for hyper threading and they both supported EMS.

Ljube · February 1, 2004, 17:28

Obviously it only concerns newer operating systems.
Try installing a partition with windows 98 SE.

I always have one on each of my computers, just in case.

Ljube · February 1, 2004, 17:29

Quote:

Originally posted by Garth Vader
My specs from CPUID

Athlon XP 2400+ 2Ghz

Epox MB, nForce2 Ultra 400, 512MB PC2700 RAM

Bios date is 3/5/2003

Garth, you were able to run MOO on your computer at work?

boolybooly · February 2, 2004, 01:27

ljcvetko, I understand your incredulity, however...

Quote:

Originally posted by boolybooly

I tried a win98 OEM bootdisk and a win95B bootdisk and in both cases, with both copies of the game ie vmxa1's as well as mine it gave exactly the same 1024 EMS error message.

I also have an installation of WinME full OS on a different IDE on the same machine and that will not run MoO either. However WinME will run MoO on my P3 backup machine.

vmxa1 · February 2, 2004, 03:30

Man you guy are scaring me. oh well I will keep my Win98SE system for as long as it will last so I can always play all the games I have.

boolybooly · February 2, 2004, 04:58

well it could be just me overlooking something, but I asked around and got confirmation its a problem so I am assuming its for real.

I had trouble running another game (Imperium Galactica 2) and found I had to reduce the page file to 300-450 Mb to get it running (which puzzles me, but it works and some people need to go down to 200 for some reason). (I checked on MoO again after I got this running but no luck.) I employed the same methods of googling it (hasnt that got a bit unreliable lately?) and then doggedly working through the links and came up with the fix in a few minutes, not so for MoO, but maybe JavaMoO will plug the gap !

I like having new toys but I dont like it when they stop me playing with my old toys

Ljube · February 2, 2004, 10:34

Quote:

Originally posted by boolybooly
well it could be just me overlooking something, but I asked around and got confirmation its a problem so I am assuming its for real.

I had trouble running another game (Imperium Galactica 2) and found I had to reduce the page file to 300-450 Mb to get it running (which puzzles me, but it works and some people need to go down to 200 for some reason). (I checked on MoO again after I got this running but no luck.) I employed the same methods of googling it (hasnt that got a bit unreliable lately?) and then doggedly working through the links and came up with the fix in a few minutes, not so for MoO, but maybe JavaMoO will plug the gap !

I like having new toys but I dont like it when they stop me playing with my old toys

If it's page file on windows 98 or ME than the problem is with the lack of memory because of the way virtual memory is functioning in these operating systems.

Ljube · February 2, 2004, 13:01

A friend of mine has got nForce2 chipset and I am going to run exhaustive tests on his computer one of these days. Who knows, I may find a solution to this problem

boolybooly · February 2, 2004, 16:49

good luck

boolybooly · February 9, 2004, 05:14

I started a new thread on this topic as Soubriquet over at nForcers HQ and someone seems to have found ways to run MoO1 on a Shuttle nF2 system; if any of you can make sense of it at all then maybe you can explain it to me !! I am having a slow brain day, er week .

Ljube · February 9, 2004, 06:27

I studied the thread and it's just like the guy says: Disable unessential motherboard resources to free up enough of conventional memory to allow for the page file of expanded memory to be stored there. Try disabling the onboard network card if you have one and usb and other ports and then try the procedure with VDMSound.

Please inform me of your results as I didn't have the time to check it myself on my friend's computer.

boolybooly · February 9, 2004, 10:34

yaay !

it runs nice and fast with sound now

I had to disable USB keyboard support and the mac lan(nVidia) in BIOS integrated peripherals

then I had to instal VDMSound 2.04 and I turned off DPMI in AUTOEXEC.VDMS for luck (actually this is essential)

Quote:

REM Install DPMI support
REM lh %SystemRoot%\system32\dosx.exe

then I had to run the Instal.exe and Orion.exe with VDMS using right click on the exe, and then I had to configure for Soundblaster Original with port 220 and IRQ 7 and other thing (1) because it runs slow unless you get the sound card right.

I am still double checking the critical elements, brb.

Edit checked, runs better without any pif fiddles (ie not Win95 compatible mode)

Ljube · February 9, 2004, 12:27

Enjoy your Master of Orion !!!!!

vmxa1 · February 9, 2004, 14:49

Glad it is working now and the other thing is DMA.

boolybooly · February 9, 2004, 15:43

thanks for your help, everyone