[Starman01]

Hey Guys,

I have a problem since the earliest days of the SCP-Release.

I haven't posted it yet, cause I think that this problem is certainly
not very spread in the community, and I have not too much hope
of solution.

The problem is : Every time FS2 crashes due to some problem
(missing file, wrong tbl-entry, doesn't matter which) then my system
will freeze when I touch anything FS-related related (launcher, modelview,
aniview, doesn't matter either) without rebooting. So I
have to reboot after every crash, and this is really, really annoying
because of this "long" windows loading prozess.

Because the crashes are related everytime I touch a freespace
programm, maybe it is a problem with the Descent-Dll-Pack ?

Because I'm working on a mod myself, and crashes are "normal",
this is really freaking me out.

My System :

Intel P4, 2,0 GHZ
512 MB RAM
GF4 TI 4200
W98 SE   ( I know, but I really like it, and it worked fine for my all the time )

Has anyone encountered something similar, and can give me a hint ?
(Windows Reinstall does not work, and I have nothing special else
installed).

Thanks.

[kasperl]

win98SE + >256MB RAM = asking for trouble IIRC.

[Kazan]

win98 NON SE and > 256mb looking for trouble

i had 3/4G of ram on win98SE and was doing development .. no problem

but upgrade to win2k

[kasperl]

meh, but if it ain't the issue, it seems to be a bug, right?

[Flipside]

You may find that while FS2 has 'crashed' it is still running in your task list.

Hit CTRL ALT DEL and look at your running tasks, see if FS2.exe is in there and end it if it is.

That used to work for me sometimes anyway

[Starman01]

Nope, no unusual task is running. Only 3 or 4 windows related
standard task.

Bad thing is, when I touch the FS2-related programm after a FS2-CTD
the systems freezes instantly, without any error. I can only press the
reset-button (and punish the keyboard sometimes )

[Sticks]

It's probably because the memory isn't freed always in a CTD, so FS2 will be trying to access the same memory when it loads again.

Not sure there's a fix for that. I'd recommend using a debug build when doing testing with new mod stuff, that should elminate the issue.