New York Hotels | Hen Night | Payday Loan | Vegas Hotel | Personal Loans
C++ Runtime errors [Archive] - PCMech Forums

PDA

View Full Version : C++ Runtime errors


mac_22
11-01-2000, 10:11 PM
Can someone give a newbie some advice? I bought a video game that runs bad on my machine. It runs better on a friends machine if you bump the resolution to 800X600. I tried this and I get the error message "Microsoft Visual C++ Runtime Error abnormal program termination." The game stops and goes back to the desktop. I suspect my machine ain't up to the task, but I've run more complex games with no problems. P166mmx, 96Megs ram, 2meg video card. Sorry if I posted in the wrong section, I'm just curious what that particular error message means.

Thanks

rickman
11-10-2000, 07:17 AM
what game is it?
what are the reqirements for hardware and software?
possibly there are answers on the game's web page, or even a patch for the game.
personaly i would upgrade the video card. you can get a 8mg for about $30.
I have had games that won't run on my pc either I have 650mhz athalon with 327mb of ram 32mb video. it could be other software you have on the pc.

mac_22
11-11-2000, 09:41 PM
The game is Brunswick Pro Pool 11 from headgames.net and activision.com. My machine meets the minimum requirements, but I know i'm pushin it. They didn't have a patch for it or an answer why it won't play, but they did offer to send me a different game if I send this one back. It plays good on a celery 500, but only at 800X600. I know a 2meg video card is pretty lame, but I'm saving my pennies for a new machine, I'm running windows 98 and directx 7.0a. I don't know what other software to mention. I was hoping that someone could tell me what C++ runtime errors mean, generally.

Thanks alot,

mac_22

Cymbeline
11-25-2000, 08:54 PM
C++ runtime errors could be caused by a variety of things:

1. Division by zero, underflow, or other ludicrous arithmetic operations.

2. Stack overflow. Basically, the program had a recursive routine that had no base case, causing the stack to overflow and program termination.

3. Page fault. Accessing a NULL pointer. Dereferencing a NULL pointer. Basically, things that involve incorrect things to do with NULL pointers. (I know, I have to mess around with this in the graphics programming I do.) It could also be caused by running out of disk space for memory paging and swapping.

4. Segmentation fault. Basically, the program attempted to access memory that is "forbidden". This could be caused by uninitialized pointers, NULL pointers, and anything that could cause a page fault.

Cymbeline

mac_22
11-25-2000, 09:38 PM
Thanks Cymbeline, I think. I'm pretty sure it's not a disc space or swap file problem. The rest is over my head. I need to learn some programming. I appreciate your answers.

Many thanks,

mac_22