[bf1942] BF1942 Linux 1.6 server starts then exits

[AIX Gaming]

Getting the new binary that you mentioned fixed the problem without any
further complications.  Thanks for your help on this.



> Content checking should be working with the new EoD version (0.3).  I
> think you have to set it to 2 or 'unpure' mode on the server.
>
> There is a problem with the dedicated server posted on the EOD website and
> coop, but that is fixed in belloq's server version:
> http://belloqsdomain.net/bf1942/eod_alpha_v0.3a-full-server.tar.bz2
> Even this version does not work with a couple of the EoD coop maps
> (Charlie don't surf and Que Son Valley).  This problem will be fixed in
> the next EoD release.
>
> Did you delete the EoD folder before installing the new version?  There
> may be some residual from a previous version that is messing things up.
>> For loading a mod like EOD, make sure the content check setting is off,
>> as
>> for running plain old BF you've likely got it set on.
>>
>> -----Original Message-----
>> From: AIX Gaming [mailto:webmaster at aixgaming.com]
>> Sent: Thursday, 26 February 2004 10:11 a.m.
>> To: bf1942 at icculus.org
>> Subject: Re: [bf1942] BF1942 Linux 1.6 server starts then exits
>>
>> You're the man.  I cleared out the maplist and started fresh and that
>> did
>> it.  Here's my next problem, I hope it's something obvious.  When I run
>> BF1942 maps, people can connect and everything's great.  But when I load
>> up
>> EOD maps, the server runs fine (no errors in the logs) but when people
>> go to
>> connect, they get dropped back to the desktop after 3/4 of the loading
>> screen.  No one can connect.  Thoughts? Thanks again.
>>
>>
>>
>> > AIX Gaming wrote:
>> >
>> >>Hey guys, first time posting here, sorry if this is in the wrong spot.
>> >>Having trouble with the 1.6 server running on debian linux.  I've got
>> >>everything installed by when I go to run it, it just goes for a few
>> >>seconds, then goes back to the prompt with no remaining process.
>> >>Independent of log settings, I can't manage to get any error codes or
>> >>log entries out of it.  Any ideas?  Thanks.
>> >>
>> >>
>> >>
>> >>
>> > Check for an invalid map entry. That will kill the server with no log
>> > or error anywhere.
>> >
>> > InCisT
>> >
>>
>>
>