X-Envelope-to: WIN3-L%UICVM.BITNET@HKUVM1.BITNET
Newsgroups: bit.listserv.win3-l
Date:         Fri, 31 Jul 1992 14:04:11 -0500
From:         whlee@HKUEEE.HKU.HK
Subject:      PCTCP & QVTNET
X-To:         WIN3-L%UICVM.BITNET@HKUVM1.BITNET

Well, the bulletin board seems to be flooded by discussions on tcp/ip
protocols and qvtnet for these few days. I found it to be very
interesting.

I am now using a PC running PCNFS ver 3.5 and Win 3.1. I need to access
some workstation for my research project. At the very beginning I have
to use Telent from NFS. However, under win3.1 I can only open one dos
session running telnet. Opening another will crash the system.

Suddenly, I heard from my U-mate that there is a wonderful product
called QVTNET out there which acts as a tcp/ip server under windows and
support multiple login session. I got it and is frustated that it cannot
co-exists with PCNFS. I have mounted several network drive using NFS and
I cannot give them up just for that sake of QVT.

Now I am using an X server under window (X11/AT). It's performance is
great though it still has bugs.

Today I read the bulletin board and find a terrific software called the
pktmux. Some says that using it we can run nfs and qvtnet together. I
downloaded it and test, this time really fascinated by pktmux.

Here, I would like to answer some questions posted and clear some
misinterpretations. I am not gaurantee all my claimings and some are
just guesses. Pls don't be hesitate in correcting me through e-mail. Any
corrections are greatly appreciated.

1)In a posting Wile E. Coyote writes :
>
> >Most PC-NFS applications use an NDIS driver/lower stack.....

Well, Sun Microsystem also provides a packet driver interface ,
pktd.sys, so that PCNFS can work with a packet driver e.g. 3C503.com

2)In a posting Jeffrey R Kell writes:
>You can only mix dissimilar protocols (TCP, UDP, IPX, etc).  Reflection
>and WinQVT both use TCP/IP stacks and there is no way for the "hack" to
>know what packet goes where.

Well, that is not true in using pktmux. Pktmux allows you to share
different protocols (e.g. TCP, UDP, ICMP, etc) on top of the IP layer.
Besides, it allow multiplex using the port no. under TCP, UDP and ICMP.
That means you CAN runs two applications using same TCP, UDP or ICMP
protocols. I am now running PCNFS using a packet driver as wells as
QVTNET (which I use to type this mail under win 3.1).

3)Verheulpen W. writes:
>Winqvt/net could not be used properly with PC-NFS because PC-NFS
>was not allowing the use of the ethernet card by the packet driver
>(simplified explanation) PC-NFS 3.5 provided some more or less
>workable version of a (pseudo?) packet driver (pktd.sys) that
>could live together with winqvt/net

pktd.sys is not a packet driver, it is just a packet driver INTERFACE
(like pktint for QVTNET) only. You still need a packet driver (e.g.
3C503.com for 3COM). Even when you use pktd.sys, you still cannot
run PCNFS and QVTNET together without using pktmux. It is simply
because both of them uses the same TCP protocol but the packet driver
go no deeper that sorting different packet types. They do not work
together because packet driver does not multiplex port number and IP
protocol stacks.



My configuration is:
25MHz 386DX, PCNFS 3.5, QVTNET 2.6, 3Com net card,
X11/AT for windows

config.sys:
................
DEVICEHIGH = c:\dos\ansi.sys
DEVICEHIGH = C:\NFS\PCNFS.SYS /i:5 /b:350
DEVICEHIGH = C:\NFS\SOCKDRV.SYS
DEVICEHIGH = c:\drivers\pktd.sys
................

autoexec.bat:
.................
loadhigh c:\drivers\3c503 0x60 5 0x350 1
c:\drivers\pktmux
c:\drivers\pktdrv 63
PRT *
NFSRUN
loadhigh nfs30gdv.exe
c:\drivers\pktdrv 65
d:\qvt26\pktint
.................


Any comment are welcome.
Pls send email to:
h8715902@hkucc.hku.hk
or
whlee@hkueee.hku.hk

Ammon Lee Wing Hong
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU