Application erorr: divide by zero

S

Shadowbird

Where'd That 6th Toe Come From?
I had put Fallout on a shelf for quite some time, due to both my real life and newer games (Arcanum, Bloodlines, Heroes of Might and Magic), but recently I really wanted to play it again. And I couldn't. Still can't.

Here's the deal:

When I run Fallout, everyhing's great until I get to Shady Sands. In Shady Sands, I can talk/steal from Set and Katrina, but that's about it. As soon as I start even scrolling deeper into the village, Windows closes (well, not really closes, since I have to manually stop it through Ctrl+Alt+Del, but "disables" or smth) Fallout with a message "An integer divide by zero was encountered". And I'm screwed. There are other messages (in Fallout 2, too), but this one is the most constant up to now.

Help?

P.S. I'm running Windows XP SP2.
 
elderwf.jpg
 
How can he not find a tech help forum? There's like ten of them here.

Of course, only one of them would be correct...
Mwuhaha! Teh complicatedness!

(not)
 
OK, OK, alright already. I get the message, should have slept more than 2 hours last night. ;) Now can someone [edit - deleted] try to help me solve problem with the game?
 
Wait, wait - I think there are still a couple dozen more member who want to say 'wrong forum'.

Give them a chance too, will ya? You selfish prick.
 
I'd like to, but I'll save it on someone with a higher account number than I.

As for the issue, have you disabled everything running in the background? This sounds like some memory allocation fault... Or maybe a corrupt file?
 
Silencer said:
As for the issue, have you disabled everything running in the background? This sounds like some memory allocation fault... Or maybe a corrupt file?
Click to expand...
Corrupt file? Don't think so. I apply the same patch that always worked. About the memory - I have 1GB of RAM, so I don't believe that the background programs affect that much. But yeah, I got a memory allocation fault error once, too, but that was at random (didn't re-accure after quickload). This "zero division" error is constant and 100% replicable.

Ratty said:
You need to run WGAS shell and enable multithreading in IHNFC environment.
Click to expand...
IsweartoGodIdidn'tundersandawordyoujustsaid. Could you please explain in a more humane way (unless you're just trying to pull one over me, in which case - don't bother)?
 
Ratty said:
You need to run WGAS shell and enable multithreading in IHNFC environment.
Click to expand...
:eyebrow:
I thought you were a computer science major? You could have at least posted how to run a bouncing ball program in PASCAL and really confused him.
 
Have you tried running it in different compatibility modes? It's been a long time since I've encountered an error like that but I remember getting it a lot when trying to run DOS games in Windows, so I wouldn't be surprised if this has a similar cause - ie, XP not being fully backwards compatible with Win95.
 
Dove said:
I thought you were a computer science major? You could have at least posted how to run a bouncing ball program in PASCAL and really confused him.
Click to expand...
Oh, but l33t abbrevations WGAS and IHNFC have a witty meaning - too bad I forgot what it was in the meantime. Crap. And PASCAL sucks.

So anyway, Shadowbird, don't eliminate the possibility of data corruption so quickly, because this totally seems like a corrupt file. I doubt it's a bug, because someone would surely have experienced something similar by now. Try reinstalling the game and re-downloading the patches, then play without patching, see if it works, then patch. But before doing any of that, run the game in a compatibility mode like Montez recommended.
 
Shadowbird said:
Corrupt file? Don't think so. I apply the same patch that always worked. About the memory - I have 1GB of RAM, so I don't believe that the background programs affect that much. But yeah, I got a memory allocation fault error once, too, but that was at random (didn't re-accure after quickload). This "zero division" error is constant and 100% replicable.
Click to expand...

Which patch would this be?

You know you're going to regret this if the answer is wrong. :D
 
For the entirely clueless:

WGAS -- Who Gives A Shit?
IHNFC -- I Have No Fucking Clue

If you didn't know that before, you may now GFYS. :P
 
Sorry for gravedigging, but an e-mail aksing about wether I've resolved this problem reminded me that I haven't "finished" this thread and made it useful to anyone having the same prob. Basically Ratty and Silencer were right, it was a corrupt master.dat file. As soon as I got a replacement, everything worked.
 
You must log in or register to reply here.
Back
Top