From: jasper@vax.path.ox.ac.uk
Newsgroups: comp.os.vms
Subject: Re: Need VMS Gopher Client
Date: 22 Dec 92 23:26:55 GMT
Organization: Oxford University Molecular Biology Data Centre
Nntp-Posting-User: jasper

In article <1992Dec21.203600.1@vax.path.ox.ac.uk>, jasper@vax.path.ox.ac.uk writes:
> In article <1992Dec21.082642.365@news.uwyo.edu>, rtravsky@news.uwyo.edu (Rich Travsky) writes:
>> How many VMS gopher clients are there? I'm aware of and have the
>> one from boombox at the University of Minnesota. Do any others
>> exist that I can access?   TIA,
> 
> Two that I am aware of: Both are at their current revision courtesy of David 
> Jones at Ohio State:
> 
> The Gopher client (character cell) is at version 0.6D (as of this week) and is
> derived from the version 0.6B code at Boombox. I think it supports UCX,
> Multinet and Wollongong. It has a variety of important fixes compared with
> version B. 

Just when I thought I was up to date..... and this pops up! 

>X-NEWS: oxpath comp.infosystems.gopher: 1617
>Subject: Announcing VMS Gopher V1.1 Client (Beta release)
>Message-ID: <1h7lb0INNpe2@access.usask.ca>
>From: fogel@jester.usask.ca (Earl Fogel)
>Date: 22 Dec 92 18:04:16 GMT
>Organization: University of Saskatchewan
>NNTP-Posting-Host: jester.usask.ca
>Originator: fogel@jester.usask.ca
>Lines: 53
>
>We have just placed the first (beta) release of the VMS gopher V1.1 client
>software in the /pub/gopher/incoming directory on boombox.micro.umn.edu,
>in the file gopher1.1v.tar.Z.
>
>This VMS gopher client was ported from the Unix gopher V1.1 client by
>JQ Johnson <jqj@phloem.uoregon.edu> and Earl Fogel <fogel@jester.usask.ca>.
>It works with the UCX, Multinet and Wollongong versions of TCP/IP for VMS.
>
>
>Making the VMS Gopher Client
>----------------------------
>
>Makefiles are provided in the gopher & object directories for those of
>you with a VMS MAKE utility, and compile.com and link.com files are
>provided for those who do not.
>
>To make the VMS gopher client, edit conf.h to reflect your local environment.
>
>If you are using MAKE, edit the makefiles to specify your TCPVERSION (UCX,
>MULTINET, or WOLLONGONG).  Run MAKE in the object directory first, then
>in the gopher directory.
>
>If you are not using MAKE, the TCP version is specified on the
>compile.com & link.com command lines (eg. "@COMPILE UCX").  Execute the
>compile.com and link.com procedures in the object directory first, then
>do the ones in the gopher directory.
>
>
>Known Problems
>--------------
>
> - sounds are not supported on VMS
> - images are not transfered properly on UCX
> - interrupts (^C and ^Y) are not handled properly
>
>Please let us know if you find other problems, or if you fix any of
>these ones.
>
>
>Earl Fogel & JQ Johnson
>
>------------------------------------------------------------------------
>Earl Fogel
>fogel@jester.usask.ca		Computing Services, Room 56 Physics
>Phone: (306) 966-4861		University of Saskatchewan
>Fax:   (306) 966-4938		Saskatoon, Sask. CANADA, S7N 0W0
>------------------------------------------------------------------------
>JQ Johnson
>Director of Network Services            Internet: jqj@oregon.uoregon.edu
>University of Oregon                    voice:  (503) 346-1746
>250E Computing Center                   BITNET: jqj@oregon
>Eugene, OR  97403-1212                  fax: (503) 346-4397
>------------------------------------------------------------------------
>

 regards,    jasper
 
 Jasper Rees
 
 Oxford University Molecular Biology Data Centre
 
 jasper@vax.path.ox.ac.uk