Official forums for BZFlag.org

ok i heard and tested that with windows you can only have a certain number of flags. now is that bzflag related or is it just windows. thanks

windows, it seem to happen sporadically tho

are you 100% sure, cause theme(he has number's here but i dunno them) is runny a server on xp pro(like me) and he had 48 flags in and was running a public server successfuly. hmm

it affects the player limit, I can have about 7-12 peoplw with +f good 3

in my 2.0.5 b4 I can have +f good 3 and I can have 25 people.

did u see my post ^ because he had 48 flags with 10+ people in his server

oh and in your sig, whered u get the thing that says solarflare owner?

as I said in my first post, it is SPORADIC.

Matt? wrote:oh and in your sig, whered u get the thing that says solarflare owner?

totally OT but...

I made it

hmm, soemone needs to make some sort of patch for windows that lets it have more than x amount of connections, that would be neat. dunno if that would be legal or not

its open source software, it seems to have something to do with the connection limit of windows for some reason, at least thats what my examinations show.

yea, i know but what i mean was that someone could make a patch for WINDOWS, not bzflag. hmm dunno

you have to hack your operating system to do that, and remove the part that limits connections, I did try, once, but I still had a connection limit.

it is legal, as long as you don't re-distribute the windows after you have hacked it.

Yeh, I had my IK server with around 50 flags and 8 people. Get past 8 and you get that nasty write error.
But now HT is hosting my server! (Check my siggy)

Win Xp wrote:its open source software, it seems to have something to do with the connection limit of windows for some reason, at least thats what my examinations show.

There was a patch bought in with XP SP2 that limited you to 10 TCP connections.

This can be bypassed illegally by disabling Windows File protection and installing a patched tcp.sys.

If you look in your error log you will see a TCP warning when you try and go over your connections limit.

Matt, either use Windows Server or install linux on a spare machine

Win Xp's problem was bandwith and server funk, not an actual limitation in the code.

The windows server supports the SAME number of flags as any other OS. It's the same code.

Non server versions of the windows OS have a connection limit of 10 users by default. There are ways to change it.

if you flood your bandwith then the messages for things get droped, like flag updates, and player updates, hence why it's "sporatic".

It can be passed legally, too.
Let me search the Introduction for this...

It needs Windows XP SP2

1) open windows registry editor. (Start->run and type regedit)
2) Goto:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

3) create a new DWORD-entry with that name: "TcpNumConnections"
and give him the value "fffffe"

Now, you can have up to 16.777.214 simultaneos connections open.

JeffM2501 wrote:Win Xp's problem was bandwith and server funk, not an actual limitation in the code.

The windows server supports the SAME number of flags as any other OS. It's the same code.

Non server versions of the windows OS have a connection limit of 10 users by default. There are ways to change it.

if you flood your bandwith then the messages for things get droped, like flag updates, and player updates, hence why it's "sporatic".

Please xaplin while then when I am in linux I can have 100 flags and 20 players?

also, alex135 can only have 10 flags on his T1 connection.....

hard to say with out debuging the exact problem.

I'm just saying it's NOT something that is in the code ( like a limit ). It could have been problems on your windows system, or your nic driver, or some other system process screwing it up.

if you realy want to find out why, then it it needs to be debuged, not you guessing that it's just "something windows does sometimes". All things happen for a reason.

I think ill check that out now, I have time.

JeffM2501 wrote:hard to say with out debuging the exact problem.

I'm just saying it's NOT something that is in the code ( like a limit ). It could have been problems on your windows system, or your nic driver, or some other system process screwing it up.

if you realy want to find out why, then it it needs to be debuged, not you guessing that it's just "something windows does sometimes". All things happen for a reason.

I can say for sure its not a b/w issue, and it is also not the 10 connection limit in SP2 (I've had the problem in SP1, plus I am almost positive the 10 connection limit is only on lan networking, not HTTP or UDP internet connections). If it helps, in the server console output logs I have of the problem I get EAGAIN errors. Also I do not remember the problem occuring before 2.0.2, making me think Windows doesn't like a bzflag server code change made from that time. (Not saying its not a bug in Window's code that doesn't like something newer in BZflag)

ok, well i quit trying. i am gunna wait until i use BZanywhere by Saturos