HDTenEightyP/NetNews huggingface dataset:
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Eight bit characters with CUTCP?
From: mark@gopher.dosli.govt.nz (Mark Wright)
Date: Thu, 3 Sep 1992 00:46:40 GMT
Organization: Dept. of Survey & Land Information, NZ.

An application I'm trying to use, seems to use eight bit characters to draw
some screen lines etc.

When the application is accessed via cutcp, it looks to me like the eighth bit
is being ignored (I get text instead).

Anyone know of a way to get eight bit graphics with cutcp? I can't see
anything about it in the documentation.

Are there any pc implementations of tcp-ip that support eight bit characters?

Thanks for any help.

                  =========================================
                  ||             Mark Wright.            ||
                  ||    Phone: 64 4 4710-380 ext 8688    ||
                  ||          Fax: 64 4 495-8466         ||
                  =========================================
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: mcsun!sunic!lth.se!axisab!martin@uunet.uu.net (Martin Gren)
Subject: Re: TCP/IP printer server with LPD
Organization: Axis Communications AB, Lund Sweden
Date: Thu, 3 Sep 92 01:21:01 GMT


Alan Luchuk> In article <16851C670.PA9690@utkvm1.utk.edu>, PA9690@utkvm1.utk.edu
Alan Luchuk>  (Alan Luchuk) wrote:
Alan Luchuk> 
Alan Luchuk> >Are special purpose devices available that do LPD?  Something
Alan Luchuk> >that plugs into an Ethernet on one side and a printer on the
Alan Luchuk> >other and doesn't require additional software/hardware.
Alan Luchuk> 

My company makes a TCP/IP printer server that supports lpd as well as many
other TCP/IP protocols. Further to this it also support Novell IPX
concurrently - with a lot of features. The box takes up to 4 printers.
If you have any further interest - please send me an email, or to
"info@axis.se" or "info@axisinc.com".

/ Martin

Martin Gren                email: martin@axis.se
Axis Communications AB     Tel: +46 46 19 18 38
S - 223 70 LUND,  SWEDEN   Fax:   +46 46 13 61 30
-- 
Martin Gren                email: martin@axis.se
Axis Communications AB     Tel: +46 46 19 18 38
S - 223 70 LUND,  SWEDEN   Fax:   +46 46 13 61 30
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: alistair@microsoft.com (Alistair Banks)
Subject: Re: Windows Socket API
Date: 24 Aug 92 18:04:13 GMT
Organization: Microsoft Corporation

In article <1592@anagld.analytics.com> sammy@anagld.analytics.com (Sam Blackburn) writes:
>PIRARD@VM1.ULG.AC.BE (Andre' PIRARD) writes:
>
>>On Thu, 11 Jun 1992 00:34:41 EDT Roger Fajman said:
>>>The Windows Socket API sounds like a big step forward.  I wish that
>>>it dealt with DOS applications too, however.
>
>I just ordered the TCP/IP SDK from Microsoft and the salesman said that it
>covers Windows, DOS and OS/2 (probably 1.3).  This is the SDK that implements
>WinSock API.

Sadly, this isn't right. The kit you were offerrred implements a sockets API
for ms-dos, windows & os/2, but it isn't yet "Windows Sockets" compliant.

Our "Preliminary Win32 SDK for Windows NT" implements Win16 & Win32 APIs
compliant with the "Windows Sockets" standard, but both implementations are
for use in Windows NT - we're working on Windows 3.x "Windows Sockets" i/f,
but haven't completed that yet, and have nothing to announce today.

If you remember, please give me the name of the salesman and I will give
him the correct information. This is a very esoteric area, and
its hard to explain that a sockets lib for Windows is not always "Windows
Sockets" compliant. Things should get simpler as a few implementations
hit the market - I'm hoping fall Interop related demonstrations will
sort things out -- Alistair
From: rjc@crosfield.co.uk (roger clark)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Problems with NCSA ftpbin !
Keywords: NCSA,ftp
Date: 28 Aug 92 15:32:58 GMT
Organization: Crosfield Electronics, Hemel Hempstead, United Kingdom.

Hi all,
       I'm having some problems with NCSA ftp.  I can ftp to and from sun
sparkstations without any problems, but when I try to ftp to a 68020 based
unix system which we developed inhouse, the ftp locks up and occasionally
fills the screen with strange characters (almost if has gone into another
graphics mode). Also it only happens on files above about 50K or so.

I wondered if anyone else has had similar problems, and found a solution.
My full system configuration is a intel 386 25Mhz, 4M ram, ega mono video,
adaptec 1542 disk controller, 380Mb scsi disk and 3c503 ethernet card, using
thin ethernet.

Any suggestions would be gratefully received.


Thanks in advance      Roger Clark.
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: FTP PC/TCP as transport for eXceed Plus
From: steven@gopher.dosli.govt.nz (Steven Brydon)
Date: Tue, 1 Sep 1992 05:13:57 GMT
Distribution: comp
Organization: Dept. of Survey & Land Information, NZ.


I am using FTP's PC/TCP as a transport for exceedp Plus (X11 server for
DOS). When I have exceed plus logging transport errors lots of the
following error messages are logged:

	Read error 19 on socket N

where N is usually 1, 2, 10 or 15.

Has anyone encountered this ?
What does error number 19 mean ?

I would turn the logging off and forget about it except for the fact
that I have two PC's running this software which crash unexplainably very
frequently (and also have another 4 PC's with no problems)


Cheers
Steven Brydon
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: hillman@sfu.ca (Steve Hillman)
Subject: Re: slip8250 packet driver : works ?
Organization: Simon Fraser University, Burnaby, B.C., Canada
Date: Tue, 1 Sep 1992 17:39:12 GMT

rsemenof@ee.ubc.ca (SEMENOFF ROBERT) writes:

>If there's anyone out there who's used this packet driver,
>I'd really appreciate a quick note saying that it does
>actually work as advertised.

The packet driver works fine - until you need hardware handshaking (usually)
at rates > 9600 bps). The latest mod to the driver was to remove transmitter
interupts. Unfortunately, as near as I can tell, this inadvertantly disabled
hardware handshaking because the old code used to turn the transmitter 
interrupt flag off and on in response to CTS changing state.
 
As far as I know, this bug has not yet been fixed (the newest version that I
have is dated Jan'92, and this is the version with the bug).



-- 
Steve "Skillman" Hillman                "Everyone generalizes"
hillman@sfu.ca
skillman@tz.wimsey.bc.ca

Newsgroups: comp.protocols.tcp-ip.ibmpc
From: usenet@nosc.mil (Network News)
Subject: FTPBIN and auto-login problem
Organization: Naval Ocean Systems Center, San Diego, CA
Date: Tue, 1 Sep 1992 18:00:40 GMT


Could anyone tell me if it is possible to have FTPBIN 
automatically login with my username and password without 
interacting with me?  I cannot for the life of me figure out 
how to do it if it is possible.   When I type in the following 
: USER <user-name> <password>, it takes the user-name and 
password as a single string as the user-name and then prompts 
me for a password.  However, when I try this on a UNIX machine 
to a VAX and vice versa, it works.  It just doesn't seem to 
work with a PC.

  	 	I would like to be able to put a periodic ftp 
session on an launch scheduler to automatically transfer files 
unattended.  Or is it possible to find a background ftp server 
to do this on the PC?  Please let me know if you can help me.
From: gts@MICA.BERKELEY.EDU (Greg Small)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: WinQVT/Net and LanManager not cooperating
Date: 28 Aug 92 17:36:10 GMT
Distribution: world
Organization: The Internet

= From pcip-request@louie.udel.edu Thu Aug 27 21:44:32 1992
= From: Bob Baggerman <prism!comlab.gatech.edu!bob@gatech.edu>
= I have noted this problem with the Ungermann-Bass NDIS driver.  In the case
= of NCSA Telnet, the solution is to turn on the "noarpme" switch.  The UB
= driver is the only NDIS driver I have found that exhibits this aberrent,
= abhorrent behavior but there may be others.  It would be nice if QVTnet
= also supported "noarpme".

Actually, the UB NDIS driver is receiving all packets with an Ethernet broadcast
address or with the Ethernet address of the adapter (and presumably multicast
also), even if they were sent by the adapter.  This is proper behavior (how
else can you do loopback tests!).  In any case, the applications should be
robust enough to filter these packets, if inappropriate, as they should for any
inappropriate packet.

The self ARP is a great feature (every TCP kernel or standalone application
should use it at startup).  Duplicate IP address are a real headache.  It is
simple enough to filter or note the receipt of an ARP from your own system.

Gregory T Small                                      1-510-642-5979
Personal Computer Networking & Communications        gts@violet.Berkeley.EDU
Workstation Software Support Group, IST/WSS          216 Evans Hall
University of California, Berkeley, Ca 94720         1-510-643-5385 (Fax)

Newsgroups: comp.protocols.tcp-ip.ibmpc
From: robert@swanee.ee.uwa.edu.au (Roberto Togneri)
Subject: NCSA telnet does not free packet driver -- pktmux problem
Organization: Elec Eng, Univ of Western Australia
Date:  2 Sep 92 07:39:40 GMT


Hi,

I just tried running all of the following together using pktmux/pktdrv:

PC-NFS with pktd.sys
WinQvtNet
NCSA telnet

and it works! Well sort of ....
Apparently if I run any NCSA programs the packet channel is marked as
busy when I exit and I can't get back in again unless I do:

pktdrv 66 /r

which frees the channel. 

Is this an expected problem?

Thanks for your help,

--
Dr. Roberto Togneri                        Phone: +61-9-380-2535     _--_|\
Centre for Intelligent Information Processing Systems               /      \ 
Dept. of Electrical & Electronic Engineering                        *_.--._/
The University of Western Australia        Fax:   +61-9-380-1101          v 
NEDLANDS WA 6009 Australia                 Email: robert@swanee.ee.uwa.edu.au
From: jbvb@FTP.COM ("James B. Van Bokkelen")
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Good TCP/IP package for NFS and with SCO ansi emulation.
Date: 1 Sep 92 17:05:27 GMT
Reply-To: jbvb@ftp.com
Distribution: world
Organization: The Internet


    ...has good SCO ansi terminal emulation.  We are currently using FTP's
    PC/TCP, but it is virtually useless for terminal emulation and remote
    printing.  I tried using Procomm Plus as a terminal emulator and never
    got it to work with 8 bits instead of 7 bits...

If your emulator asks TNGLASS for an 8-bit data path, we try to negotiate
the Telnet Binary option.  I *know* this works, because of the number of
emulators that do so automatically, and the number of Unices that map it
to "raw mode".

James B. VanBokkelen		2 High St., North Andover, MA  01845
FTP Software Inc.		voice: (508) 685-4000  fax: (508) 794-4488
*note new address & phone*

Newsgroups: comp.protocols.tcp-ip.ibmpc
From: eengelke@sail.uwaterloo.ca (Erick Engelke)
Subject: Re: tcp-ip library for WINDOWS/DOS (Berkeley compatible)
Keywords: tcp-ip, rpc, DOS, Windows. 
Organization: University of Waterloo
Date: Tue, 25 Aug 1992 18:33:16 GMT

> vijghen@fynu3.fynu.ucl.ac.be (Philippe Vijghen) writes:
>
>	Could anybody out there give me some information about tcp-ip and
>rpc libraries for WINDOWS/DOS programming? 
>
>	I have a dwonloaded copy of wattcp from the university of Waterloo. 
>Unfortunatly, this package is not compatible with the Berkeley BSD interface.
>We want to write code portable to our UNIX machines...
>

I hate to tell you this, but even the nicest BSD emulation libraries
lack a lot of the BSD feel which you would want if you expect total
BSD compatibility.  The developers had to go to great lengths to
simulate the BSD environment because they had to do it all on top
of little old DOS, and that is quite a different beast.

Novell LWP includes a nice BSD 4.2 Windows emulation library.  FTP is just
offerring a new release, so I expect they added Windows support, ask
at info@ftp.com.  B&W's otherwise attractive product is lacking BSD 4.2
emulation in either DOS or Windows, I immagine their market niche is
more toward production environments, something they do very well.

Under LAN manager environments, HP ARPA services offers good Windows
BSD emulation, but it's rarly used outside the LanMan environment. 

I think the first three I mentioned will all be supporting WinSock
at some time, and they are quite widely used.  But don't wait for
products not yet available, it can be discouraging.  Your best bet
is to develop for a specific vendor's TCP and then adapt it as 
WinSock becomes available and during the refining process as various
implementations resolve small compatibility problems.


>	I have got some information from NetManage. Their package looks quite
>interesting although I think it is quite expensive (around $2000).
>

Sorry, I've had no experience with developing for NetManage or Distinct.
And I don't remember how Sun's PC-NFS system copes with Windows.

Erick
-- 
Erick Engelke					  Engineering Computing
						 University of Waterloo
Waterloo TCP Architect		 erick@development.watstar.uwaterloo.ca
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: tannerc@cu18.crl.aecl.ca (Chris Tanner)
Subject: INT14 tsr in PC/TCP (FTP)
Organization: AECL-Research
Date: Thu, 27 Aug 1992 23:15:43 GMT

Hi Greetings

We have PC/TCP running on a PC and would like to use a windows based
terminal emulator (from KEA) that needs an INT14 based telnet tsr that
is loaded before its own tsr.

I could not see how to do this from the manual.  Does anybody know how
to do this. (I hope that all this makes sense).

THanks for your help.

Chris

-- 
Chris Tanner                  Email: tannerc@CU18.CRL.AECL.CA
AECL Research                 Phone: (613) 584-3311 X4053       
Chalk River, Ont.             FAX:   (613) 584-1082
Canada, K0J 1J0
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: jiliu@silver.ucs.indiana.edu (Jian Liu)
Subject: Re: WinQVT/Net and LanManager not cooperating
Organization: Indiana University
Date: Thu, 27 Aug 1992 19:24:24 GMT

>	I can't seem to get QVTnet running with along with LanManager.
>It always responds to it's own ARP and then complains about a conflict
>with itself.

It doesn't run with FTP's PC/TCP kernal as well.
From: timmi@asylum.sf.ca.us (Timothy G. Reynolds)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Trumpet over FTP Software
Keywords: trumpet pc/tcp ftp
Date: 27 Aug 92 18:00:46 GMT
Reply-To: timmi@babyoil.ftp.com
NNTP-Software: PC/TCP NNTP

One of the developers here thinks he may have found the problem
running the Trumpet-PC/TCP shim under Windows.

Sean, if you could get in touch with me, I'll pass on what he's had
to say.
--
Timothy G. Reynolds					FTP Software
FTP Technical Support					26 Princess St.
timmi@ftp.com						Wakefield, MA
(617) 246-2920							01880

	"We're well into the later half of the twentieth century,
	 paranoid misogyny is just plain out of style."

Xref: sparky comp.protocols.tcp-ip.ibmpc:4910 comp.protocols.tcp-ip:4202
From: br.pct@RLG.Stanford.EDU (Peter C. Tam)
Newsgroups: comp.protocols.tcp-ip.ibmpc,comp.protocols.tcp-ip
Subject: KA9Q NOS LPD
Keywords: LPD
Date: 27 Aug 92 01:36:12 GMT
Organization: Research Libraries Group, Inc.

Hi,
    I have been trying to configure KA9Q NOS lpd to work. My system
  consists of:  Victor 286 AT-compatible (8mhz) w LPT1, COM1.,
                3C503 ethernet card,
                HP LaserJet II printer connected to Parallel Port,

                MS-DOS 5.0,
                CryNwr 3c503.com "3c503 0x65 9 0x300 1"

    I was successful in printing a small output file, a file the size
  of an average CONFIG.SYS, but when I try to print a bigger file (2 or
  more pages), Computer will hang. Even after I get into lpc in NOS,
  stop the printer, & just try print file transfer to print queue
  under /spool/lpd/lp1, it still hangs. The Data File of "DFAAxxx" is
  created, & of 0 file length when it hangs. Seems to be hanging in the
  recv() loop in receive_data_file() in lpd.c of NOS LPD.

    Am I missing something here? NOS ftp works, even though it is slower
  than NCSA/CUTCP ftp. So, my network configuration is ok.

    Following is content of my /etc/printcap file:

#
# example printcap for NOS LPD
#

#
# HP LaserJet II
#
lp1|p1:\
	:af=/spool/lpd/lp1-acct:\
	:lf=/spool/lpd/lpd-log:\
	:lp=LPT1:\
	:pl#64:\
	:pw#0:\
	:sd=/spool/lpd/lp1:\
	:sh:

  Thanks for any HELP !!!!

+---------------------------------------------------------------------------+
| Peter C. Tam                         InterNet: br.pct@RLG.Stanford.EDU    |
| Fax: (415) 964-0943                  BitNet:   br.pct@RLG.BITNET          |
+---------------------------------------------------------------------------+
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: eengelke@steam.uwaterloo.ca (Erick Engelke)
Subject: Re: Problems with NCSA ftpbin !
Keywords: NCSA,ftp
Organization: University of Waterloo
Date: Tue, 1 Sep 1992 14:46:18 GMT

 pechter@ocpt.ccur.com (Bill Pechter) writes:
> rjc@crosfield.co.uk (roger clark) writes:
>>       I'm having some problems with NCSA ftp.  I can ftp to and from sun
>>sparkstations without any problems, but when I try to ftp to a 68020 based
>>unix system which we developed inhouse, the ftp locks up and occasionally
>>fills the screen with strange characters (almost if has gone into another
>>graphics mode). Also it only happens on files above about 50K or so.
>
>
>Got the same kind of problems - I went to the Waterloo TCP/IP
>(or was it the PC/IP stuff) and had no problem.  NCSA Telnet also
>locks up occasionally.
>

Try reducing the NCSA window size to 512 bytes and see if that prevents 
the crashes. I've noticed problems with NCSA ftp grinding to a halt,
and that's why I wrote the WATTCP FTP with its tendancy to speed up
with larger file transfers, but I haven't seen NCSA crash.

Erick
-- 
Erick Engelke					  Engineering Computing
						 University of Waterloo
Waterloo TCP Architect		 erick@development.watstar.uwaterloo.ca
From: ig@siesoft.co.uk (Ignatius Tan)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: FTP site for Crynwr
Date: 28 Aug 92 15:18:06 GMT
Organization: Siemens Nixdorf Information Systems Ltd.
X-Newsreader: Tin 1.1 PL4

Hi net,

This is an FAQ I'm sure - apologies.

Can someone pls mail me ftp sites that hold the current Packet Drivers
set? Mirrors/sites in the UK preferred but not essential. Thanks!

ig
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: ballan@fraser.sfu.ca (Bruce Allan)
Subject: Re: SLIP (dos <-> unix)
Organization: Simon Fraser University, Burnaby, B.C., Canada
Date: Thu, 27 Aug 1992 18:02:02 GMT

A good application is NuPop v0.9.9F available by ftp from 
ftp.acns.nwu.edu.  A very good mail client programme.



Xref: sparky comp.protocols.tcp-ip.ibmpc:4929 bit.listserv.novell:13159 comp.sys.novell:6811
From: tony@scotty.dccs.upenn.edu (Anthony Olejnik)
Newsgroups: comp.protocols.tcp-ip.ibmpc,bit.listserv.novell,comp.sys.novell
Subject: HELP: UB ODI drivers don't work w/ XT class machines
Date: 27 Aug 92 17:43:34 GMT
Followup-To: comp.protocols.tcp-ip.ibmpc
Distribution: usa
Organization: University of Pennsylvania


I'm trying to use Novell's Lan Workplace for DOS product with
Ungermann-Bass PC-NIU and PC-NIU/ex adapters.  UB has just
come out with ODI drivers for these cards.

The documentation is limited, but I'm able to get things going
on 80286, 80386, and 80486 class of machines.  However, I have
a number of 8086 class machines on which the UB ODI drivers
don't work.

Is this a known problem?
Am I doing something wrong?
Has anyone else experienced this problem?
Has anyone gotten this to work?

I've tried calling UB for these, however I've been unsuccessful in
getting a response.

Any help would be *GREATLY* appreciated.
Thanks in advance.

--tony
From: pechter@ocpt.ccur.com (Bill Pechter)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Problems with NCSA ftpbin !
Keywords: NCSA,ftp
Date: 1 Sep 92 15:57:38 GMT
Organization: Concurrent Computer Corp.,Information Services

In article <BtwMD7.264@watserv1.uwaterloo.ca> eengelke@steam.uwaterloo.ca (Erick Engelke) writes:
>
> pechter@ocpt.ccur.com (Bill Pechter) writes: 
>>NCSA Telnet also locks up occasionally.

>Try reducing the NCSA window size to 512 bytes and see if that prevents 
>the crashes. I've noticed problems with NCSA ftp grinding to a halt,
>and that's why I wrote the WATTCP FTP with its tendancy to speed up
>with larger file transfers, but I haven't seen NCSA crash.


No such luck - I had it set to 512 bytes from the beginning.

Thanks for your help.

Bill


--------------------------------------------------------------------------------
        Bill Pechter, N2RDI           | The postman always pings twice.
        Concurrent Computer Corp.     | pechter@ocpt.ccur.com
        2 Crescent Place, Oceanport, NJ 07757 - Tel:908-870-4780 
-- 
--------------------------------------------------------------------------------
        Bill Pechter, N2RDI           | The postman always pings twice.
        Concurrent Computer Corp.     | pechter@ocpt.ccur.com
        2 Crescent Place, Oceanport, NJ 07757 - Tel:908-870-4780 
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: pnguyen@maui.qualcomm.com (P. Nguyen)
Subject: PC/TCP Packet Driver Spec.
Organization: Qualcomm, Inc., San Diego, CA
Date: Wed, 2 Sep 1992 22:52:27 GMT

	Hi,

	Does anyone know where I can get a copy of the
	Packet Driver Specification for PC/TCP?

	Please let me know via email to pnguyen@qualcomm.com.
	Thank you very much.

	--pn
-- 
	;-------------------------------------------------------;
	;	Mo^.t con ngu+.a ddau, ca? ta`u bo? ... cha.y	;
	;				-- my little brother --	;
	;-------------------------------------------------------;
From: jbvb@FTP.COM ("James B. Van Bokkelen")
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: WinQVT/Net and LanManager not cooperating
Date: 1 Sep 92 17:05:24 GMT
Reply-To: jbvb@ftp.com
Organization: The Internet


    The thing that was not mentioned was the ethernet hardware and NDIS 
    driver used.  I have noted this problem with the Ungermann-Bass NDIS
    driver.  In the case of NCSA Telnet, the solution is to turn on the 
    "noarpme" switch.  The UB driver is the only NDIS driver I have found
    that exhibits this aberrent, abhorrent behavior but there may be others.

Echoing broadcast packets back to the sender was *required* by some
versions of the NDIS spec, and the PDS doesn't specify any behaviour.
NCSA should be smarter about checking the sender's MAC address...

James B. VanBokkelen		2 High St., North Andover, MA  01845
FTP Software Inc.		voice: (508) 685-4000  fax: (508) 794-4488
*note new address & phone*
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: catstyle@deja-vu.aiss.uiuc.edu (CatStyle )
Subject: Wanted: nntp options for PC/TCP v1.1 pl1 for OS/2 2.0
Organization: University of Illinois at Urbana-Champaign
Date: Sat, 29 Aug 1992 02:59:47 GMT

Does anyone have a list of configurable opions for
my pctcp.ini file?

Please e-mail me, I'll post a summary.

Thanks,

Jason R. Heimbaugh, AISS
jrh@uiuc.edu
Newsgroups: comp.protocols.tcp-ip.ibmpc
From: stare@lonexb.rl.af.mil (Edward M. Starczewski)
Subject: Re: Help needed with QVTNET27
Organization: RL
Date: Mon, 24 Aug 92 10:59:33 GMT

In article <hippo.10.0@sonoma.edu> hippo@sonoma.edu (Michel Davidoff) writes:
>Can you tell me where you got this? I've version 2.6 and I'm looking for 2.7

I got mine at ftp.cica.indiana edu in the /win3/uploads subdirectory

-- 
Edward M. Starczewski     Fax: 315-330-2139
Rome Laboratory           Com: 315-330-4431
E-mail: stare@lonex.rl.af.mil