Xref: utzoo comp.protocols.tcp-ip:15814 comp.protocols.tcp-ip.ibmpc:5635 comp.sys.ibm.pc.hardware:8035 comp.sys.ibm.pc.misc:9017
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!caen!ox.com!emory!gatech!prism!ce1zzes
From: ce1zzes@prism.gatech.EDU (Eric Sheppard)
Newsgroups: comp.protocols.tcp-ip,comp.protocols.tcp-ip.ibmpc,comp.sys.ibm.pc.hardware,comp.sys.ibm.pc.misc
Subject: Packet driver over NDIS
Message-ID: <27269@hydra.gatech.EDU>
Date: 25 Apr 91 04:14:04 GMT
Followup-To: comp.protocols.tcp-ip
Organization: Georgia Institute of Technology
Lines: 14

I've been experimenting lately with the packet->NDIS converter from 
FTP Software.  I cannot seem to get the converter bound to the NDIS
driver; netbind.exe just hangs my machine.  One machine can load the
modules in and initialize the ethernet card, but no binding can take
place.   Another machine with a different (3Com 3c523) ethernet board
cannot get initialized (using the elnkmc.dos file dated April 9 at
FTP's site).   I would appreciate any pointers on putting the pieces
together in the right order; I feel I'm extremely close to a solution.
Has anyone successfully used this combination?
-- 
Eric Sheppard      Georgia Tech    |   "Of course the US Constitution isn't
Atlanta, GA                        | perfect; but it's a lot better than what
ARPA: ce1zzes@prism.gatech.edu     |             we have now." -Unknown
uucp: ...!{allegra,amd,hplabs,seismo,ut-ngp}!gatech!prism!ce1zzes