Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!texbell!uhnix1!sugar!ssd
From: ssd@sugar.hackercorp.com (Scott Denham)
Newsgroups: comp.sys.amiga
Subject: Re: JrComm 1.0
Summary: JrComm 1.0 Lockups
Message-ID: <6081@sugar.hackercorp.com>
Date: 24 Jul 90 04:01:18 GMT
References: <31705@cup.portal.com> <23847@uflorida.cis.ufl.EDU> <31747@cup.portal.com>
Distribution: na
Organization: Sugar Land Unix - Houston
Lines: 18

In article <31747@cup.portal.com>, LordBah@cup.portal.com (Jeffrey J Vanepps) writes:
> JR-Comm 1.0 is working beautifully for me.  Nothing I've done has been
> able to break it.  I've only had one lockup, probably due to running out
> of chip memory when I had JR-Comm, PKAZIP, C-Robots, interlaced morerowsed
> 
> Of course, this is a registered copy, obtained from the author on a
> floppy.  Someone might have gotten to the distributable copy that the
> first poster was running.

 I missed the start of this thread, but I can report that JR-COMM 1.0 as
I received it here appears to have some problems.  I had 3 lockups in the
first day of using it, all on a system using the SkyPix feature (thought
for one of these lockups Skypix was NOT enabled).  Subsequently to that I
had two lockups in Z-Modem transfers - in both cases on the last block of
a fairly large file.  As a result I went back to 0.94, which has worked
flawlessly for me for some time on the same system.  Perhaps the memory
requirments for 1.0 are signifigantly higher?? My system's a 1 megger,
without much in the way of "extras" running.....