Bug 255 - Serious Sam fails on startup (Cannot initialize player Class)
Status: RESOLVED INVALID
Alias: None
Product: Serious Sam
Classification: Unclassified
Component: ssam client
Version: Serious Sam betas
Hardware: PC Linux
: P2 blocker
Assignee: Ryan C. Gordon
QA Contact:
URL:
Depends on:
Blocks:
 
Reported: 2002-12-09 22:32 EST by Jeff Mrochuk
Modified: 2002-12-11 10:49:02 EST
0 users

See Also:

Attachments
md5sums of all files in ssamtfe installation dir (10.16 KB, text/plain)
2002-12-10 11:32 EST, Jeff Mrochuk

Description Jeff Mrochuk 2002-12-09 22:32:32 EST 
System:
Athlon XP 1400
Geforce4 Ti
SBLive!
Debian Unstable
Kernel 2.4.18
Standard version of SS:TFE

Upon running ssamtfe from the ssamtfe dir, or anywhere else.  It quits on error.
The error is shown below:

----
STUB: load window icon in SeriousSam/MainWindow.cpp, line 153.
STUB: Need SDL invisible window or something in SeriousSam/MainWindow.cpp, line 356.
FATAL ERROR:
  "Cannot initialize classes:
Cannot open file `/usr/local/games/ssamtfe/Classes/Player.ecl' (No such file or
directory) ()"
Comment 1 Jeff Mrochuk 2002-12-09 22:33:32 EST 
I've uninstalled and reinstalled several times, with no change.
Comment 2 Ryan C. Gordon 2002-12-10 11:15:23 EST 
Can you run this command (from the directory where you installed the game):

md5sum `find .` > ssammd5sums.txt

And attach "md5sums.txt" to this email? There's about a million variants of the
retail CD, and it's possible that the installer isn't handling yours correctly,
so I want to see 1) the checksums of the files and 2) what files actually got
installed.

Thanks,
--ryan.
Comment 3 Jeff Mrochuk 2002-12-10 11:32:13 EST 
Created attachment 40 [details]
md5sums of all files in ssamtfe installation dir

md5sums of all files in ssamtfe installation dir
Comment 4 Jeff Mrochuk 2002-12-11 00:14:32 EST 
This bug dissapears if I have the cd mounted at run time.
It now open a wm window and crashes.  Will investigate further, and post results.
Comment 5 Jeff Mrochuk 2002-12-11 00:32:29 EST 
.gro files were not copied properly, looks like it was due to a scratched/dirty
cd.  You can probably ignore this bug.
Comment 6 Ryan C. Gordon 2002-12-11 10:49:02 EST 
Noted.

I'll ask the loki_setup people about how to handle a failed copy in the installer.

--ryan.