Path: utzoo!attcan!uunet!ogicse!ucsd!usc!petunia!news
From: cambler@polyslo.CalPoly.EDU (Fubar's Carbonated Hormones)
Newsgroups: comp.mail.uucp
Subject: Re: FSUUCP to VMS DECUS uucp initalization problem
Message-ID: <272362e9.7424@petunia.CalPoly.EDU>
Date: 22 Oct 90 21:21:45 GMT
References: <2590.271890d8@miavx1.acs.muohio.edu> <71.2722b72c@wrglex.uucp>
Organization: Fantasy, Incorporated: Reality None of Our Business.
Lines: 32



j_prigot@wrglex.uucp recently informed us:
>In article <2590.271890d8@miavx1.acs.muohio.edu>, pemurray@miavx1.acs.muohio.edu (Peter Murray) writes:
>> I have a problem connecting a FSUUCP version 1.1 (Release 5) host to a VMS
>> host running DECUS uucp version 1.1.  The MS-DOS machine is calling the
>> VMS host.  The problem happens when they first get connected.
>> 
>> Apparently, the VMS slave is sending "Shere", but the MS-DOS master is
>> looking for "Shere=hostname".  The VMS documentation seems to say that
>> either "Shere" or "Shere=hostname" is acceptable (page F-13 of DECUS uucp
>> documentation).  But, MS-DOS wants "Shere=hostname" (in the "Error Messages"
>> section).
>> 
>	[Stuff deleted]
>
>Probably the best fix all around is to convince your DECUS uucp site to
>upgrade to V1.2. This situation has been "fixed" in that release, along with a
>number of other improvements.

I'd appreciate it if someone from the DECUS side could send me information on
this "problem" and the "fix" so that I might make FSUUCP more compatible with
older versions. Sounds like it could be fixed with just a switch.


>Jonathan M. Prigot      j_prigot@wrglex or ...!drilex!wrglex!j_prigot


-- 
++Christopher(); --- cambler@polyslo.calpoly.edu --- chris@erotica.fubarsys.com
---
A feature is a bug with seniority.