From - Wed Oct 29 11:12:57 1997 Path: news.mitre.org!blanket.mitre.org!agate!newsgate.duke.edu!nntprelay.mathworks.com!howland.erols.net!news.maxwell.syr.edu!nntp.ntr.net!uunet!in1.uu.net!lard.ftp.com!not-for-mail From: Slava Monich Newsgroups: comp.os.ms-windows.programmer.nt.kernel-mode Subject: Re: NdisMIndicateReceivePacket Date: Tue, 28 Oct 1997 14:28:53 -0500 Organization: FTP Software, Inc. Lines: 32 Message-ID: <34563CF5.AD8848A1@ftp.com> References: <01bce0c1$bc738ad0$d0b262c7@dcxsys02> <3452C97D.192C@ftp.com> <632m9s$76e@news.microsoft.com> <34560CA5.3F9E@spam.com> NNTP-Posting-Host: smonich-3.ftp.com Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 4.03 [en] (WinNT; U) Russell Johnson wrote: > > kyleb wrote: > > > > indicate packet works fine. > > the first buffer in the packet must contain at least the lookahead size that > > was set by the protocols. > > > > NdisMIndicateReceivePacket() does not work with > 1 buffer in NT 4.0 or > NT 4.0 SP1. I traced into the code and it only reports the first buffer > with a total length of the entire packet to each protocol. The code > does something like the following: which puts you and other developers in a very difficult position. When you are developing and selling "Software X for Windows NT 4.0" customers usually assume that it's supposed to work on all variants of NT 4.0 including all possible combinations of service packs and hot fixes. which is nearly impossible. That's why I ended up using IndicateReceive/TransferData because it's an old code and they have stopped (hopefully!) making changes to it. Unfortunately new code often gets released long before it becomes usable. And it sells pretty well. Power of marketing... ------------NOT-RELATED-TO-THE-SUBJECT---------- BTW did you know that domain SPAM.COM actually exists and has something to do with food marketing? Their mail server must be overloaded if they have one... -Slava