Path: utzoo!utgpu!watserv1!watmath!att!pacbell.com!decwrl!sun-barr!newstop!jethro!mock From: mock@watt.support.Corp.Sun.COM (Joseph Mocker) Newsgroups: comp.protocols.tcp-ip Subject: Re: Packet driver over NDIS Message-ID: Date: 30 Apr 91 19:39:07 GMT References: <27269@hydra.gatech.EDU> <1991Apr26.195757.47576@cc.usu.edu> Sender: news@jethro.Corp.Sun.COM Followup-To: comp.protocols.tcp-ip Organization: Sun Microsystems Inc. Lines: 23 In-reply-to: jrd@cc.usu.edu's message of 27 Apr 91 01:57:57 GMT In article <1991Apr26.195757.47576@cc.usu.edu> jrd@cc.usu.edu writes: I'd suggest you try the next iteration of the dis_pkt routine, version 1.6, which can be found on my VMS VAX netlab.usu.edu 129.123.1.11 in directory [anonymous.netwatch] as file dis_pkt.asm (a uuencoded archive). The top of the .asm file shows example config.sys and protocol.ini files. Joe D. I just tried this version of dis_pkt, and I saw something strange happening. I have a Ethernet Packet watcher program that I wrote, and when using DIS_PKT, I would say the first 14 bytes of the ethernet frame are zeroed out. (which would be the source ethernet addr, destination ethernet addr, and type fields). It does display what appears to be valid packet lengths, but that is about it. Anyone have an explanation for this? -- Joe -- ------------------------------------------------------------------------------ Joe Mocker//USAC//PC-NFS Support :: mock@Corp.Sun.COM :: Sun Microsystems Inc. :: there's still lofty dreams :: meager desires :: still sillyness ::