Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!tektronix!reed!omen!caf
From: caf@omen.UUCP (Chuck Forsberg WA7KGX)
Newsgroups: comp.sys.ibm.pc
Subject: Re: More Procomm Problems
Message-ID: <605@omen.UUCP>
Date: Fri, 16-Oct-87 21:54:21 EDT
Article-I.D.: omen.605
Posted: Fri Oct 16 21:54:21 1987
Date-Received: Sun, 18-Oct-87 08:08:06 EDT
References: <1745@gryphon.CTS.COM> <4330006@hpindda.HP.COM> <197@megatek.UUCP>
Reply-To: caf@omen.UUCP (Chuck Forsberg WA7KGX)
Organization: Omen Technology Inc, Portland Oregon
Lines: 37

In article <197@megatek.UUCP> hollen@mana.UUCP (Dion Hollenbeck) writes:
:In article <4330006@hpindda.HP.COM> hardin@hpindda.HP.COM (John Hardin) writes:
:>I use PROCOMM to access CompuServe and have been successfully using
:>the XMODEM protocol to download files.  The version of PROCOMM I
:>have been using is 2.4.1.  I have had no luck using the 
:>CompuServe B protocol and have also found no way to get back other
:>than to hang up and dial in again.  I have noticed that the .NEW
:>file in the PROCOMM package cites Compuserve B fixes in 2.4.1 and
:>2.4.2, but the problems I have seem so severe that "fixes" seems
:>an understatement of what it needs.
:
:Are you just complaining or are you asking for help?  You never say.
:If you are asking for help, are you a registered user?  If you are, call
:up the registered user BBS and download yourself 2.4.2 and see if it 
:fixes your problem.  If you are not a registered user, either register or
:quit complaining!  I am sure other registered users would be happy to
:help you with a work-around if they have it, but try going to the source
:first, they are helpful and much more knowledgeable than any of us about 
:the package they wrote.  Also, they deserve to have you register.

The traditional "shareware ethic" is for one to pay for it after it has
been verified as reasonably functional.  As a reward for registration,
the user gets better support, better documentation, extra features, and
a clear conscience.  I don't think it fair to insist users register in
the hope of getting bugs fixed, especially well known bugs.

I certainly wouldn't suggest that a potential customer who had identified a
major bug in ZCOMM's file transfer protocol support code register his copy
before fixing the bug.  (Especially since reliable file transfers is the
cornerstone of Omen's corporate image)

Chuck Forsberg WA7KGX Author of Pro-YAM communications Tools for PCDOS and Unix
...!tektronix!reed!omen!caf  Omen Technology Inc "The High Reliability Software"
17505-V Northwest Sauvie Island Road Portland OR 97231  VOICE:503-621-3406:VOICE
    TeleGodzilla BBS: 621-3746 19200/2400/1200  CIS:70007,2304  Genie:CAF
  omen Any ACU 2400 1-503-621-3746 se:--se: link ord: Giznoid in:--in: uucp
  omen!/usr/spool/uucppublic/FILES lists all uucp-able files, updated hourly