Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!ucsd!ucbvax!yalemed.bitnet!BEEBE
From: BEEBE@yalemed.bitnet (Rick Beebe)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: RE: WIN TCP R4.1 w/packet driver
Message-ID: <0F15D783EC9F000126@Venus.YCC.Yale.Edu>
Date: 1 Nov 90 15:10:00 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 28

>I regularly see references to using WIN TCP w/PD - in fact, there is a
>file pktdrv.exe (or something like that) in the distribution. What I
>do not see is anything in the documentation about how to do so. I
>tried the obvious (??) things like
> 
>1) loading the appropriate PD (3c505), then the WIN TCP kernel
> 
>2) loading the PD, then running pktdrv.exe, then the kernel
 
Basically #2 is right. Pktdrv.exe takes the place of the hardware specific 
driver. For example, instead of running 3c505 then the kernal, you run pktdrv 
then the kernal. In order for pktdrv to work, the packet driver must be loaded. 
I did have to play around with which interrupts were used. I'm sorry, but I 
don't remember now which one's I used. I _think_ I used 0x60 for the packet 
driver and 0x61 for pktdrv. (It took me a while to realize that I didn't want to
    
use the same interrupt for them both).
 
-----------------------------------------------------------------------------
                                Rick Beebe                    (203) 785-4566
 *****  *****  *****  *   *     Biomedical Computing Unit
   *      *    *      **  *     Yale University School of Medicine
   *      *    ***    * * *     333 Cedar Street, New Haven, CT 06514
   *      *    *      *  **
   *      *    *      *   *     BEEBE@YALEMED.BITNET
                                beebe%biomed.decnet@venus.ycc.yale.edu
-----------------------------------------------------------------------------