|
Oh boy—my ignorance could show through here J This is my guess, note, ONLY A GUESS, at what COULD be happening. It’s been a long time since my computer science classes, and documentation on this stuff is non-existent. But here I go (anyone may certainly correct me on my blunders):
This does a "binary AND", not to be confused with a "&&", or "Logical AND".
A logical AND (&&) would be used in a statement, something like "if($this && $that)".
A binary AND works like this:
Suppose you have two numbers, in binary 1st: base 2(binary)=0011 or base 10(decimal)=3 2nd: base 2(binary)=1010 or base 10(decimal)=10
If we do a binary AND on these 2 numbers, we get 0010: 1010 0011 ----- 0010
In binary, the result ANDed is true ONLY if both placeholders are 1's. In this example, our end result is base 2(binary)=0010 or base 10(decimal)=2.
0xffff is hex for the binary equivilant of 16 1’s.
So in our eventlog issue, the number was -1073740770. I can only assume that possibly this is coming from the MS box as a signed int (the left-most binary place holder signifies +/-), or something to that effect. Doing the binary AND is just cleaning up the data, and making it a normal readable number like we are used to seeing.
Clear as mud? I could be way out in left field. If anyone else has a better idea, I’m all ears. But I do know this: it worksJ.
Scott Campbell Senior Software Developer Somix Technologies http://www.somix.com
-----Original Message-----
Scott, for those of us math-impaired readers, could you explain what's happening?
\\Greg
************************************************************************** This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited. Thank you for your compliance. |
- Weird event log ids Foster, Ken
- RE: Weird event log ids Scott Campbell
- RE: Weird event log ids Foster, Ken
- RE: Weird event log ids Martin, Greg \(CSC\)
- Scott Campbell
