Re: FW: NeTraMet 2.1 now available

nevil@ccu1.auckland.ac.nz Thu, 10 February 1994 00:02 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa21320; 9 Feb 94 19:02 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa21312; 9 Feb 94 19:01 EST
Received: from wugate.wustl.edu by CNRI.Reston.VA.US id aa21710; 9 Feb 94 19:02 EST
Received: by wugate.wustl.edu (5.67b+/WUSTL-0.3) with SMTP id AA12912; Wed, 9 Feb 1994 17:55:32 -0600
Message-Id: <199402092355.AA12912@wugate.wustl.edu>
Date: Thu, 10 Feb 1994 12:55:01 +1300
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: nevil@ccu1.auckland.ac.nz
X-Orig-Sender: "ONC List Processor V0.2" <listserv@wugate.wustl.edu>
Reply-To: accounting-wg@wugate.wustl.edu
To: accounting-wg@wugate.wustl.edu
Errors-To: accounting-wg-errors@wugate.wustl.edu
Subject: Re: FW: NeTraMet 2.1 now available

> can you help ?
> ----------
> does the ne tramet use winsock ? on pc's

The current implementation runs on a bare DOS system, using only the
CRYNWR packet drivers.  It runs its own IP stack, using Waterloo TCP.
This isn't really a limitation - since NeTraMet is the only thing the
PC is running, there's no advantage in using Windows!

> will it work on win3.1 or wfw3.1 or winnt3.1 ?

Again, there's no point in running NeTraMet under Windows.  It would
be nice to have a Windows NeMac, using WinSock for its IP support, but
I haven't considered doing this (so far).  This would be a great
project for someone ...

Cheers, Nevil

+----------------------------------------------------------------------------+
|  Nevil Brownlee:        n.brownlee@auckland.ac.nz         Deputy Director  |
|     FAX: 64 9 373 7425        Computer Centre, The University of Auckland  |
|   Phone: 64 9 373 7599 x8941     Private Bag 92019, Auckland, New Zealand  |
+----------------------------------------------------------------------------+