Path: utzoo!attcan!uunet!bu.edu!rpi!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!emory!hubcap!ncrcae!usceast!yarnall
From: yarnall@usceast.UUCP (Ken Yarnall)
Newsgroups: comp.sys.amiga
Subject: Re: JrComm 1.0
Summary: Problem with the 2091
Message-ID: <3339@usceast.UUCP>
Date: 17 Jul 90 17:31:01 GMT
References: <31705@cup.portal.com> <619@cbnewsb.ATT.COM>
Distribution: na
Organization: Math Department, University of South Carolina (ahem; The USC)
Lines: 27

In article <619@cbnewsb.ATT.COM> mab@druwy.ATT.COM (Alan Bland) writes:
+
+There is a note on Radigan's BBS that there is indeed a problem using
+1.0 with a 2091 controller, causing a guru at some point.  I don't have
+that configuration, so I didn't pay attention to the details, but you
+might try calling his BBS to find out the real scoop: 609-625-2453.

Well, I have not called Jack's BBS, but The copies of JRcomm I have had
contact with (A friend has a registered copy of 1.0, and I have a
distribution copy through him) both crashed quickly on machines equipped with
a 2091.  By running a tiny little program I wrote to clear location zero, the
problem goes bye-bye.  Being careful with those nasty NULL pointers?

Other than this (bad) problem, JRcomm 1.0 seems stable enough.  I have
noticed some oddities about editing pallettes in the phonebook (If you are on
an 8 color screen, and you edit the pallette of a phonebook entry with a 4
color palllette, you are presented with an 8 color pallette requester).
Also, my jrcomm.phones file has disappeared twice now, forcing me to recreate
the whole thing.  Ugh.

+-- Alan Bland

kenny
-- 
         Ken Yarnall                 ///   yarnall@cs.scarolina.EDU
          Math Department, USC   \\\///   yarnall@ucseast.UUCP
           Columbia, S.C. 29208   \\\/   (803)777-6686