Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!sri-unix!ctnews!pyramid!hplabs!hp-sdd!megatek!mana!hollen
From: hollen@mana.megatek.uucp (Dion Hollenbeck)
Newsgroups: comp.sys.ibm.pc
Subject: Re: More Procomm Problems
Message-ID: <197@megatek.UUCP>
Date: Wed, 14-Oct-87 09:04:33 EDT
Article-I.D.: megatek.197
Posted: Wed Oct 14 09:04:33 1987
Date-Received: Sat, 17-Oct-87 02:52:29 EDT
References: <1745@gryphon.CTS.COM> <4330006@hpindda.HP.COM>
Sender: news@megatek.UUCP
Reply-To: hollen@mana.UUCP (Dion Hollenbeck)
Organization: Megatek Corporation, San Diego, Ca.
Lines: 23

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.
	Dion Hollenbeck             (619) 455-5590 x2814
	Megatek Corporation, 9645 Scranton Road, San Diego, CA  92121
			    ames!scubed!
		{sdcsvax,hplabs}!hp-sdd!megatek!hollen
			 sdcsvax!esosun!