Moo2 Xp

[shmily_dana]

My problem is when I run the orion95 executable, it locks up during the "refit ship" menu. Sometimes the mouse is slow or sticks in other screens, but I can hit "return".

If I run the orion2 executable, everything is normal, but I get no sound.

[Berserker]

Thanks for the info on the DOS install. I went ahead and installed MOO2 on a pure MSDOS 6.22 machine I have and the combat lockup at the last fatal shot still happened.

This was running the 1.31 DOS version of the executable program and starting a brand new game.

What puzzles me is that up until about 4-6 months ago it worked under Windows98SE as advertised and also under WinXP SP1. I Tried installing it in a new Win98SE partition using only the version of DX that comes with MOO 2, but still had problems.

I'm totally stumped and will probably just settle for non-tactical combat.

Thanks for the help and suggestions

Bill

[vmxa1]

Originally posted by shmily_dana
My problem is when I run the orion95 executable, it locks up during the "refit ship" menu. Sometimes the mouse is slow or sticks in other screens, but I can hit "return".

If I run the orion2 executable, everything is normal, but I get no sound.

I have had the problem with a sticky mouse. I can often get the coursor to move by holding the control key, but it is very hard to get it to line up properly.

I could not get it to work for the taxes.

I finally used Moslo and now have no problems, running at about 47%.

[vmxa1]

Berserker, the combat lock up has been around forever. I have not sen it in a long time, but I have run into it.

The last time was on a game I downloaded and it had been modified via Corion.

If you have saved before the combat, you can replay the round. In the next atempt, alter the fighting pattern a bit and you can often avoid the abend.

Sometimes, I will figure the ship that seems to trigger the aborting and attack it first or use a different weapon on it.

Good luck.

[siron]

hmmm....i thought berserker meant that he ALWAYS had this combat lock up.

Editing with corion doesnt help much in this case.....

mebbe some of is lbx files is corrupted?

[vmxa1]

I was saying that corion was the cause of the bug in the last one I saw. But. I have never seen it occur for all combat, only with some large ones and in that case it always occurred for that battle, unless I altered how I did the combat.

[Berserker]

Well, I've done some experimenting (again) and I can't solve the combat lockup problem. Happens 100% of the time under all conditions.....

Conditions include early in the game with a couple of destroyers taking on an Eel to late in the game with Death Stars blowing away the Antarans, games modified with Corion and not, WinXP, Win98SE and pure MSDOS 6.22, and 4 different graphics cards (all nVidia), but ranging from an FX-5700 256MB down to an MX-200 32MB one and 4 different machines from a P4 3GhZ to a Pentium II 400MhZ one. And I've played with various versions of DX, from the 2.0 that MOO2 installs up through DX9C.

I've re-installed the game several times, just to make sure nothing was corrupted. I've also copied ALL the files from the CD to the game directory and then pointed the Orioncd.Ini file to the drive on which the game is installed......makes for fast loading, but doesn't prevent the lockup.

Anyway, thanks for the feedback, helpful hints, etc. It's too bad that instead of offering us the disaster that was/is MOO3, they didn't just do a complete rewrite of MOO2 and bring it up to today's standards of graphics and sound and coding while leaving the gameplay alone!!

Bill

[siron]

Hmmm.
Last try:
make sure sound is off too
Some crashes are caused by sound cards.
But problems with 4 different sound cards seems unusual.
-----------------------------
So i guess that your CD is broken.

Try that demo here:

http://download.softwrap.com/NCBuy/MOO2.exe

and the 1.31 patch:
ftp://ftp.infogrames.net/patches/moo2/

U should try if these files work.

[vmxa1]

Do you have a save just before the crash? If you do, post it and we can see if it crashes on our systems.

[Berserker]

Don't have a save game with Tactical Combat enabled right now. When I do, I'll get it to a point where I'm going into a fight and I will post it.

In looking back over the 1.31 Readme, I think I might try that Z key to speed the combat and see if it still locks up. I'll also see what effect turning off sound has. I've got a SB Audigy ZS which is pretty common so I don't think it's the problem, but worth a try for troubleshooting purposes.

Bill

[vmxa1]

Just in case you have not used the "Z" before, you have to use it at the start. IOW you cannot initiate it during the battle.

[Berserker]

Originally posted by vmxa1
Just in case you have not used the "Z" before, you have to use it at the start. IOW you cannot initiate it during the battle.

I found that one out the hard way!

Thanks for all the help........

Bill

[Aabraxan]

Originally posted by Lostnwoods
I have a diffrent problem with xp that i can't find any help with out there so i am hoping some one hear can help me i get a a error message thats says
"C:\WINDOWS\SYSTEM32\AUTOEXECT.NT the system file is not suitable for running MS-DOS and Microsoft Windows applications." but thats my only error so i can even install the games can some one please help ?

I have this same probem. When that box comes up, I have two choices: "Cancel," which does the obvious," and "Ignore," doesn't allow it to install, either.

I've tried installing using compatibility modes for Windows, to no avail. I've searched the web for sites to tell me something about compatibility, and they all seem to indicate that MOO2 should be compatibile with my system.

I've also seen the posts regarding editing the autoexec.nt file . . . Problem is, I can't even install the files necessary to make that work. (And, historically, it's proven to be a *really* bad idea for me to go tinkering in files like that.)

Any other suggestions?

[siron]

have u tried the latest 1.40 b18 patch?

(u find it here:

http://masteroforion2.blogspot.com/2004_02_01_masteroforion2_archive.html#107792119255475969

step3 there)

it is now easier to apply:

Oct 27, 2004 - version 1.40b18
******************************

- New patcher engine
- Improved autoexec2.nt in XP
- Patcher should now detect the path to Kali correctly when generating autoexec2.nt
- Improved dosx version checking. It will only patch SP2 dosx.
- Detects orion2 version. Now it will only patch the DOS v1.31 english version
- Modem Comm Info button is now greyed out.
- Fix for some video cards misreporting "missing vesa.com"
- Now patcher creates the orion2v140.pif file automatically in game directory.
- Patcher now creates a .lnk file on the desktop rather than a .pif file

[vmxa1]

You can copy the autoexec.nt into any directory that you wish and eidt it. It will have no effect on the system or any apps, until you point that app to that path.

You can only do this in a DOS program, so Orion95 will not allow it. Orion2.exe will and you need to use properties and then the program tab.

There you replace the default path to the one you wish it to us.