> I don't see it. The old code used to _decode_ the error class into a > human-readable string, and the new code seems to just print decimals.
Ah, I get what you mean. Well... it used to "decode" nonsense. There are basically no clients left in the world using the old-style error class/code format, so there's no value in trying to maintain that decoding. It's also more consistent to just print the number(s) for both error formats. Both can easily be found by searching MSDN. (Or use wireshark:) That's the thing: We really don't want to be investing much in this snoop decoding now that wireshark is around, but this particular bug has caused too much confusion to not fix. Gordon _______________________________________________ networking-discuss mailing list [email protected]
