Thanks for your post!
I only mentioned the byte ordering because, well, I’ll confess I’ve tripped
up there myself - so for long time now, if anyone says to me “these ports
numbers are foobar”, it’s like my first thought, and it’s been more often
right than wrong. We’ll that’s been my experience, for what it’s worth.
“J. J. Farrell” wrote in message news:xxxxx@ntdev…
> xxxxx@yahoo.co.uk wrote:
>> Lyndon,
>>
>> You have been precisely 0/6 help all evening. Of course I use google ffs.
>> I have persisted with this as I dumped one line of code, and said what’s
>> wrong with it? Postulation and sniping aside there has been a few people
>> who have been (IMVHO) helpful. You are not one of them. It is late here
>> so I’m off to bed.
>
> Interesting. Your question is timed at 5.33 PM on my system, and Lyndon’s
> first reply is timed at 5.51.
>
> You asked for the correct formatting string to use with DbgPrint,
> suggesting inability to read documentation. Lyndon answered that it was
> the same as printf, answering the core question for someone too lazy to
> look up DbgPrint, and providing more than enough information for someone
> who wasn’t lacking in C skills. Most of those whose C skills don’t extend
> to knowing the printf formats would then think of looking at its
> documentation.
>
> You asked how to compare a UINT16 to an int, wondering about a cast, and
> demonstrating a remarkable lack of self-help skills, or of C skills, or of
> both. Despite the gob-smacking nature of the question, Lyndon’s first
> message gave you a full answer. He reminded you that a UINT16 is an
> ‘unsigned short’ just in case you’d forgotten that since you looked it up
> in the header files.
>
> He even gave you a hint about byte-ordering though you didn’t ask anything
> about that area. This risked him being considered patronizing since no-one
> writing TCP/IP-related code should need to be told about that, but all the
> same …
>
> You owe Lyndon an apology for insulting him after he wasted his time
> trying to help you.
>
> Learning the basics of self-help (such as looking at header files and
> documentation), C, and TCP/IP before tackling a network packet inspector
> would probably help you get where you need to be more quickly. Learning
> how to ask questions effectively would save time for you and others -
> http://www.catb.org/~esr/faqs/smart-questions.html is an excellent
> resource for this.
>