1  |   Order by index

Mar 11, 2003, 2:35am

I recently got a Nvidia GForce2 MX400 and everytime I get in AW it crashes
like crazy. At first I thought it was windows XP and there was no way I was
going to let that stop me from coming to AW....so I downgraded to
Win2K....same problem. It says it created an error log for me, so I go look
at it....all the same thing. DrWatson error 4907. I dont really understand
what it means but it says it is a binding issue. I have tried upgrading my
video driver, I have changed to every video setting in AW, I have upgraded
to directx9. Anyway...is this just this stupid video card has a problem
with AW, or is this some strange bug I have in AW on that other machine?
Any ideas, anyone? I am at my wits end over here. I can run the server,
just not the client program.

I have f-disked the machine, started over 3 times....same problem. I had
one video card, now this one...same problem. I am not beta, I am AW 3.3
build 419.

Any ideas, I'm open.

Thanks in advance for any ideas!!

Mar 11, 2003, 3:33am

Make AW generate its own log file, open the aworld.ini and add this into it.

[debug]
all=1

When you crash, use this program to get the last 50 lines from the log
file.
http://oct31.de/tmp/tail.zip (GNU tail)
A command line tool.
tail -50 aworld.log > 50lines.txt
extracts the last 50 lines from the aworld.log.

After you get that, go back in that ini file and change the all=1 to all=0
to turn the logging off as that log will eat up your hard drive space fast
(about 50 MB per min.)

Once you have the last 50 lines, send a copy of them to ActiveWorlds tech
support, make sure you tell them your system specs and what video mode you
are in and what you where doing just before the crash.

After your done, you can delete that log file as it takes up a lot of space.




[View Quote]

Mar 11, 2003, 8:34am

When I origonally built this PC that i'm useing now I built it to use in AW
specs are 2 gig p4 500mb ram and 64 mb nvidia chipset vid card.

After trying XP , 2000 and ME and having exactly the same problem you are I
tried the PC on a few 3D intensive Games and found out that it wasnt a
problem with just AW, after starting to play a game or use AW the PC would
either blue screen or just switch off with no warning at all.


In the end I tried a non nvidia based vid card that was in my brothers PC
and it ran totally stable, so I changed my vid card for a non nvidia based
one and the PC has been totally stable on XP since.


It's worth trying out on a few games to see if its just AW it doesnt like.

Mar 11, 2003, 10:39am

Check out my reply to Goober Kings post on this subject in the Beta NG
about this problem, i too had the same problem and managed to fix
it... however if you follow my advice - be warned - either make sure
110% what you are doing or get someone who knows to do it for you.

On 11 Mar 2003 05:34:17 -0500, "chiana" <stonkingv8 at hotmail.com>
[View Quote] >When I origonally built this PC that i'm useing now I built it to use in AW
>specs are 2 gig p4 500mb ram and 64 mb nvidia chipset vid card.
>
>After trying XP , 2000 and ME and having exactly the same problem you are I
>tried the PC on a few 3D intensive Games and found out that it wasnt a
>problem with just AW, after starting to play a game or use AW the PC would
>either blue screen or just switch off with no warning at all.
>
>
>In the end I tried a non nvidia based vid card that was in my brothers PC
>and it ran totally stable, so I changed my vid card for a non nvidia based
>one and the PC has been totally stable on XP since.
>
>
>It's worth trying out on a few games to see if its just AW it doesnt like.
>

Mar 11, 2003, 12:12pm

It had nothing to do with my Bios version or settings it was a
compatabillity issue with the nvidia chipset on the vid card and the intel
chipset on the mother board.

Mar 11, 2003, 8:14pm

Well before you go out and buy a new video card... see if you can't borrow
a friend's to see if Jernau's idea is correct. Then if it is, and you still
have a warranty on the card, trade it in for a different model because
chances are some component on it is fried.

Chris

[View Quote]

1  |   Order by index