Path: utzoo!attcan!uunet!snorkelwacker!usc!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!gvlv2!faatcrl!jprad
From: jprad@faatcrl.UUCP (Jack Radigan)
Newsgroups: comp.sys.amiga
Subject: Re: JrComm 1.0
Message-ID: <1500@faatcrl.UUCP>
Date: 18 Jul 90 14:29:28 GMT
References: <31705@cup.portal.com> <619@cbnewsb.ATT.COM> <5213@darkstar.ucsc.edu>
Distribution: na
Organization: FAA Technical Center, Atlantic City NJ
Lines: 21

terry@helios.ucsc.edu (Terry Ricketts) writes:

>   I also have been 'trying' to use Jr-Comm 1.0 for about a week now. I have a
>2091 & that may be the problem.  Could someone post the gist of the message on
>Jack's board. That is a long distance call from here. 

You have to run the 590FIX program or any little utility that resets memory
location zero to 0.  I still haven't been able to figure out what is doing
this as MemGuard III does not report a low memory stomp on my A1000.  More
distressing is that when I stomp on location zero with ZeroMung, it continues
to work fine on my A1000...  Damndest thing I ever seen...

>  I have had no problems using 1.0 on local BBS's and in calling the Sun
>workstation at work using the VT100 emulation. BUT when I try to use 1.0 in
>conjunction with PCP_EZ to call via PC Pursuit 1.0 will completly freeze up. I
>have temporarily given up on it and am using Baud Bandit for PC pursuit calls.

Could you have Bill contact me?  I'd like to work with him to determine the
cause of this problem as well.

  -jack-