Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!pollux.usc.edu!papa
From: papa@pollux.usc.edu (Marco Papa)
Newsgroups: comp.sys.amiga
Subject: Re: VLT v4.824 bugs?
Message-ID: <27289@usc.edu>
Date: 26 Sep 90 07:28:48 GMT
References: <26692@mimsy.umd.edu> <90268.120314CJC105@psuvm.psu.edu> <1990Sep25.192903.11909@csun.edu>
Sender: news@usc.edu
Organization: Felsina Software, Los Angeles, CA
Lines: 22
Nntp-Posting-Host: pollux.usc.edu

In article <1990Sep25.192903.11909@csun.edu> srw@csun.edu writes:
>In article <90268.120314CJC105@psuvm.psu.edu> CJC105@psuvm.psu.edu writes:
>>One more bug to report:  When changing the KERMIT block size to a number that
>>is too big it activates the kermit SEND window....  strange.  I am using the
>>latest xprkermit.
>
>I am the co-author, with Marco Papa, of XPR Kermit Version 1.5, the latest
>(actually only) public release.  Willy Langeveld reported to me some
>time ago that XPR Kermit trips warnings from "enforcer" (a developer's
>tool which uses the MMU to trap and report access to memory which is
>on the free list).  I have not yet tracked down the problem;  meanwhile,
>stick with packet sizes of less than 1000 and you should have no trouble.

One other thing to remember is that if I recall correcly, xprkermit 1.5 is 
still not  reentrant, and therfore one should not run more than one concurrent
copy at a any one time, in case you have a multi-serial card.

-- Marco
-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
"Xerox sues somebody for copying?" -- David Letterman
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=