Return-Path: Received: (qmail 10103 invoked from network); 14 Oct 2002 14:37:35 -0000 Received: from murphys.services.quay.plus.net (212.159.14.225) by mailstore with SMTP; 14 Oct 2002 14:37:35 -0000 Received: (qmail 6812 invoked from network); 14 Oct 2002 14:36:50 -0000 X-Priority: 3 X-MSMail-Priority: Normal Received: from post.thorcom.com (193.82.116.70) by murphys.services.quay.plus.net with SMTP; 14 Oct 2002 14:36:50 -0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-SQ: A Received: from majordom by post.thorcom.com with local (Exim 4.10) id 1816Ix-0002s2-00 for rsgb_lf_group-outgoing@blacksheep.org; Mon, 14 Oct 2002 15:34:47 +0100 Received: from [165.212.11.1] (helo=cmsoutbound.mx.net) by post.thorcom.com with smtp (Exim 4.10) id 1816Iw-0002rt-00 for rsgb_lf_group@blacksheep.org; Mon, 14 Oct 2002 15:34:46 +0100 Received: from uadvg137.cms.usa.net (HELO cmsoutbound.mx.net) (165.212.11.137) by cmsoutbound.mx.net with SMTP; 14 Oct 2002 14:34:39 -0000 Received: from usa.net [213.217.175.249] by uadvg137.cms.usa.net (ASMTP/dibene@usa.net) via mtad (CM.1201.1.04A) with ESMTP id 210gJNoIK0016M37; Mon, 14 Oct 2002 14:34:37 GMT Message-ID: <3DAACD5C.40006@usa.net> Date: Mon, 14 Oct 2002 15:57:48 +0200 From: "Alberto di Bene" User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0 X-Accept-Language: en-us, en MIME-Version: 1.0 To: rsgb_lf_group@blacksheep.org References: <73.277c350f.2adb4daa@aol.com> Subject: Re: LF: Re: ARGO Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 8bit X-Spam-Status: No, hits=-0.7 required=5.0tests=CTYPE_JUST_HTML,MAILTO_LINK,REFERENCES,SPAM_PHRASE_01_02, USER_AGENT,USER_AGENT_MOZILLA_UA,X_ACCEPT_LANGversion=2.42 Sender: Precedence: bulk Reply-To: rsgb_lf_group@blacksheep.org X-Listname: rsgb_lf_group MarkusVester@aol.com wrote:

Hi Alberto and all,

on two computers, I did experience Argo (build 128) crashing Windows 98 occasionally but not often, and I couldn't make out a connection to any specific activity. However there is a strange effect about the peak readout, once in a while it overwrites the top left corner of the screen instead of staying in its place in Argo's window. - On a 233 MHz PII, all modes down to 90s dots (10mHz) produce nice lines, whereas 120s dots tends to be blurred by glitches, presumably caused by lost audio data.

Hi Markus and the group,

yes, I am aware of a couple of bugs present in the distributed version of Argo.
One is an infrequent hang caused by a memory leak, the second is what you describe,
i.e. an erroneous writing of the peak value in the upper left corner of the desktop,
caused by a timing glitch between different threads.

Both have been corrected, but I haven't distributed the updated version yet, as I
was intending to do some other modifications as well, but then it was all left in
a suspended-animation status, due to a variety of reasons, whose list is of
no relevance here.

I am intending to resurrect that project, at least up to the point of releasing
a version with those errors corrected. Just give me a couple of weeks.
Sorry for any inconvenience.

73 Alberto I2PHD