Valhalla Legends Archive

When using BNCSMon (the latest) it crashed on me several times when logging my client..and also starting going into spasms kept writing SID_NILL Received....and it just got angry....

Quote from: ChR0NiC on March 16, 2004, 08:43 PM
When using BNCSMon (the latest) it crashed on me several times when logging my client..and also starting going into spasms kept writing SID_NILL Received....and it just got angry....

If i'm not mistaken, isn't your client the one that sends a bunch of SID_NULLs to 'spoof' your ping?

Quote from: ChR0NiC on March 16, 2004, 08:43 PM
When using BNCSMon (the latest) it crashed on me several times when logging my client..and also starting going into spasms kept writing SID_NILL Received....and it just got angry....

Quote from: UserLoser. on March 16, 2004, 08:53 PM
If i'm not mistaken, isn't your client the one that sends a bunch of SID_NULLs to 'spoof' your ping?

If you are talking about 0ms then I suppose but I am talking about using the game client Brood War....and the logger filled up 900kb worth of SID_NULL in my capture log...

I've had 25MB files (would've been larger but i killed BNCSMON) from the same thing. Not sure what it is. IIRC, it was only on Diablo II.

This happened to me while I logged a Diablo II Realm login in an attempt to see a valid 0x3E packet.

*takes notes on what might be a part of Stealth's new version of Stealth Bot*

hmm. Is this reproducable? Could someone with the wherewithall possibly make a BNCSMon log and take a packet capture at the same and send me the logs from both? I've never seen this problem.

It's not very common for this to occur......but next time it happens I will do just that

Edit: When logging D2 and sometimes BW, the BNCSMon will crash on me. I am not quite sure what causes this, but perhaps an overflow of some sort.

Bump.