Xref: utzoo comp.windows.ms:7870 comp.protocols.tcp-ip.ibmpc:4484
Path: utzoo!attcan!uunet!cs.utexas.edu!yale!mintaka!snorkelwacker.mit.edu!think.com!zaphod.mps.ohio-state.edu!caen!umich!sharkey!aucis!nickless
From: nickless@andrews.edu (Bill Nickless)
Newsgroups: comp.windows.ms,comp.protocols.tcp-ip.ibmpc
Subject: Re: QVTNET and DEPCA card
Summary: What about the inverse?
Keywords: PCSA Packet
Message-ID: <660923583wkn3013@elrond.cs.andrews.edu>
Date: 11 Dec 90 00:00:00 GMT
References: <87295@lll-winken.LLNL.GOV> <269@rc6.urc.tue.nl>
Reply-To: nickless@elrond.cs.andrews.edu (Bill Nickless)
Organization: Andrews University, Berrien Springs, Michigan
Lines: 13

In article <269@rc6.urc.tue.nl> rcstack@urc.tue.nl writes:
>The DLL driver gives you the same functionality as an extended, high
>performance Packet Driver. However, it has a different calling convention.
>To overcome this problem, I wrote a DLL to Packet Driver converter,
>which allows you to use programs that call the Packet Driver over DLL,
>the driver of DEC's PCSA.

Has anyone done precisely the inverse of this--written so that a DEC 
program that calls DLL will operate with a packet-driven Ethernet card?
--
---
Bill Nickless     nickless@peter.cs.andrews.edu or nickless@flash.ras.anl.gov