Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!cs.utexas.edu!sun-barr!newstop!exodus!lvs.Eng.Sun.COM!karl
From: karl@lvs.Eng.Sun.COM (Karl Auerbach)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: 'C' - Packet Driver interface
Message-ID: <13651@exodus.Eng.Sun.COM>
Date: 20 May 91 19:08:43 GMT
References: <1991May20.150430.3739@waikato.ac.nz>
Sender: news@exodus.Eng.Sun.COM
Organization: Sun Microsystems, Mt. View, Ca.
Lines: 31

In article <1991May20.150430.3739@waikato.ac.nz> slang@waikato.ac.nz writes:
>I am trying to modify a program written by a previous employee. It sits on a
>packet driver and watches the net, logging information about each packet it
>sees. Now, unfortunately, the PC has run out of memory, and a recompilation
>under a LARGE memory model is required. It uses ET_PKT (from Epilogue
>Technology) as it's C-interface to the packet driver. This was successfully
>modified to use the Medium model (Code > 64K) but not Large (data > 64K.)
>Now for my question:
>
>Does anybody out there know of a similar set of Assembler routines that sit
>between C and a Packet Driver that will run in a LARGE memory model? Any hints
>would be greatly appreciated etc. etc.

Hi -- I wrote the Epilogue interface code.  It's in assembly language
and ought to be easy to change.  I didn't use any of the model macros,
1) because the code was originally only for my own consumption, 2) MASM
was a much weaker animal at the time I wrote it, and 3) I'm lazy and never
really learned how to use masm very well.

That interface code was written for the original packet driver specification
and is somewhat out-of-date (for instance, it grabs a handle on a bogus packet
type so it can get the driver information.  That hack isn't needed with "modern"
packet drivers, but the code still does it.

The interface also didn't support any but the basic packet driver operations.

If you do modify my code, I'd appreciate it if you would post it back to the
near-public-domain.

				Good luck
					--karl--