SEIV and winME

PvK · #1 May 15th, 2001, 03:31 AM

Mail a large explosive device to One MicroSoft Way, Redmond, WA?

Disclaimer:
This message should not be construed as an endorsement by anyone of the idea of blowing up Microsoft.

Wolverine · #2 May 15th, 2001, 09:26 AM

SEIV seems to work fine on WinME (I play it both on a desktop and a laptop).

The only things I can think of is check that all the SEIV files are NOT read-only, and check the disk drive for physical errors (i.e. Run Scandisk with Surface Check).

Wolverine · #3 May 15th, 2001, 09:27 AM

Then if that doesn't work, try sending a large explosive device to Bill.

dogscoff · #4 May 16th, 2001, 09:52 AM

I did read somewhere that SEIV is *not* WinME compatible. I think Wolverine's trouble free usage on ME is the exception rather than the rule. I have a friend who can't run it on ME.

QUOTE:
Disclaimer:
This message should not be construed as an endorsement by anyone of the idea of blowing up Microsoft.
/QUOTE

But do it anyway...

------------------
"Pinky, are you pondering what I'm pondering?"
"Uh, I think so, Brain, but balancing a family and a career ... oooh, it's all too much for me. "

Wolverine · #5 May 16th, 2001, 10:36 AM

quote:
Originally posted by dogscoff:
I think Wolverine's trouble free usage on ME is the exception rather than the rule.

Hahahahahaha, trouble free usage. Good one. I've never seen those words associated with a Microsoft product before.

If ME works better for me than anyone else, then GOD HELP YOU

zen. · #6 May 18th, 2001, 06:17 PM

He's apparently helping you more than anyone ELSE.

It's sad when you need divine intervention to make a program work. *sigh*

zen

Dracus · #7 May 18th, 2001, 07:18 PM

It runs alright on WinMe, except for when you use tach combat and then decide to resolve the conflict when there are a lot of ships/fighters involved(you get a range check error) You have to finish the battle one turn at a time.
This is verision 1.35

It use to error around 300 turns also. I have about 30 more turns to go to see if 1.35 has addressed this issue.

1.02 has other problems on winme which dis-appeared in 1.35

What kind of Proccessor do you have?

[This message has been edited by Dracus (edited 18 May 2001).]