New error message

DirectorTsaarx · #1 April 12th, 2001, 04:01 PM

I haven't run into these errors yet, and I've played a couple games out beyond 100 turns. I also switch between multiple computers while playing (play a couple turns at work when I have time, then play a few at home, etc.). Of course, I'm using the standard game (no modpack, no downloaded races; only change is some tweaking of the population bonuses in Settings.txt and using the expanded system names file because I like galaxies with 200+ systems).

The one thing I've noticed about the system error-related complaints is they always come from people with high-speed CPU's and lots of RAM. I'm using a three-year-old P-233 with 64M RAM, and SE4 has yet to cause problems. I have trouble with Netscape sometimes, and occasionally problems with MS Excel, plus some things running in the background that I can't completely turn off, but SE4 has not caused any problems yet.

Dracus · #2 April 12th, 2001, 04:20 PM

I have this problem sometimes also.
I have WinMe, P4 1.5 with 256 meg memory. It happens when I am in a battle. I have already sent the files off to MM and gave them my system parms. I have no moded files on this system. I do the modding on my NT station with no problems. and my p3 400 win 98 runs it fine so far.
{I have a Packard Bell p100 overdriven, that has given me no problems at all with any software /win95, I have a gateway P3 400m that has given me no problems with this game w/win98. I have a P3
GB w/ NT 850m(this one uses scud Drive) that has given me no problems with this game. I have a GB K6 300m that does have problems with most games.
My newest is a P4 1.5g gateway that every now and then I get a range check error during battles.

I also have a p133 but I have not tryed anything on it in a long time. (thinking about using it as a game host.)}

[This message has been edited by Dracus (edited 12 April 2001).]

dogscoff · #3 April 12th, 2001, 05:00 PM

The overheating suggestion is a good one- even if that's not the casue it wouldn't hurt to open it up and remove any dust. Also, make sure you aren't blocking any ventilation holes, and your machine isn't situated by a sunny window / above a radiator / behind the fridge / in the oven etc.

A duff memory chip is another possibility I suppose. If you can get hold of similar chips (from a similar computer, maybe) swap them over and see if the problem goes away.

I don't think it happens on modern motherBoards / gfc cards but some older Boards had jumper settings to tell the computer how much memory was fitted. If those jumpers were wrong the computeer might try to use memory that wasn't there.

Just FYI - my machine is also a P133 (40meg ram, Voodoo 3/16meg), but it's my main computer, not my spare.
It does everything I ask it to just fine.

------------------
There is an exception to every rule. Including this one.

capnq · #4 April 13th, 2001, 01:33 AM

quote:
My friends laugh and say the fact that the computer is a 'packard bell' is the problem right there

They could be right. Back when I was researching which computer to buy before I picked my current one, Packard Bell came in dead Last in a _PC World_ customer survey in almost every Category. That was three years ago, though, and ISTR hearing that PB has improved somewhat since then.

------------------
Cap'n Q

Paranoid Android · #5 April 13th, 2001, 05:29 AM

I've gotten this error too in our simultaneous game. We tried having 2 other players try to execute as host on their PCs and the game still errored out, so I don't think this is a hardware problem or antivirus problem at all.

the error I got was:
"Access violation at address 004DECA4 in module 'se4.exe'. Read of address 000001F4." We are using 1.30 and TDM 1.70.

Procyon · #6 April 14th, 2001, 12:51 PM

quote:
Originally posted by Samurai:
Does anyone know what causes a message like: Access violation at address 00000038. Read of address FFFFFFFF or Access violation at address 0045A6E3 in module "SE4.EXE". Read of address 72617521?

Access violations are generally a programmer error, although they can be caused by hardware. It simply means that the program in question tried to access a place in memory that the operating system did not give it permission to access. #1 cause is a mis-indexed array.