Hellwolf_36
01-13-2004, 10:53 PM
I am afriad that this topic may be a little confusing but I will try to explain my problem.
I recently installed Serious Sam: The first encounter and when I started using the game for multiplayer capabilities. The game would crash and the error report contents would say the Modname is: Engine.dll. This is a program that is used to make Serious Sam work, not turn on me and crash my system.
My configurations are:
Intel Pentium 4 2.6 GhZ Processor
ATI Radeon 9600 Pro 128 MB DDR RAM
Windows XP Professional
MSI SiS648FX Neo Series Motherboard
Sis-900 Based PCI Fast paced Ethernet Card
Intel 537 Modem #2 (do not use this)
Maxtor 80 GB Hard Drive
LG Dvd Rom 16x combined with 52x24x52 CD-R capabilities
I have attached the log from my dedicated server to allow the people that are helping me to get a glance at what was going on. I crashed at the end before the end.ini triggers were initiated. Can someone give me a solution to this problem, it has not happened on Diablo 2 yet (I own that). I have tried re-installing it once already so that is the only solution not worth using :(
NOTE:Run this protocol on Notepad for a text documentation of what happened
I recently installed Serious Sam: The first encounter and when I started using the game for multiplayer capabilities. The game would crash and the error report contents would say the Modname is: Engine.dll. This is a program that is used to make Serious Sam work, not turn on me and crash my system.
My configurations are:
Intel Pentium 4 2.6 GhZ Processor
ATI Radeon 9600 Pro 128 MB DDR RAM
Windows XP Professional
MSI SiS648FX Neo Series Motherboard
Sis-900 Based PCI Fast paced Ethernet Card
Intel 537 Modem #2 (do not use this)
Maxtor 80 GB Hard Drive
LG Dvd Rom 16x combined with 52x24x52 CD-R capabilities
I have attached the log from my dedicated server to allow the people that are helping me to get a glance at what was going on. I crashed at the end before the end.ini triggers were initiated. Can someone give me a solution to this problem, it has not happened on Diablo 2 yet (I own that). I have tried re-installing it once already so that is the only solution not worth using :(
NOTE:Run this protocol on Notepad for a text documentation of what happened