Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!rutgers!faatcrl!jprad
From: jprad@faatcrl.UUCP (Jack Radigan)
Newsgroups: comp.sys.amiga
Subject: Re: JrComm 1.0
Message-ID: <1508@faatcrl.UUCP>
Date: 20 Jul 90 04:46:04 GMT
References: <31705@cup.portal.com> <619@cbnewsb.ATT.COM> <3339@usceast.UUCP>
Distribution: na
Organization: FAA Technical Center, Atlantic City NJ
Lines: 30

yarnall@usceast.UUCP (Ken Yarnall) writes:

>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?

I'm fairly certain that it isn't a dereferenced NULL pointer that is causing
this since MemGuard III isn't complaining.  It manifested itself after adding
the title screen during startup.  I wonder if Intuition can't deal with closing
one lores screen and immediately opening a custom hires screen behind it when
location zero is set to a non-zero value.  I have to write some example code
to be sure of this though.

>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).

Hmm, the code *should* be only showing the first four colors, I'll have to 
check this again...

>Also, my jrcomm.phones file has disappeared twice now, forcing me to recreate
>the whole thing.  Ugh.

Could you try to find a sequence of events that causes this so that I can
duplicate it?  Thanks.

  -jack-