Return-Path: Received: (qmail 5497 invoked from network); 13 Oct 2002 22:31:08 -0000 Received: from warrior.services.quay.plus.net (212.159.14.227) by mailstore with SMTP; 13 Oct 2002 22:31:08 -0000 X-Priority: 3 X-MSMail-Priority: Normal Received: (qmail 2763 invoked from network); 13 Oct 2002 22:30:25 -0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Received: from post.thorcom.com (193.82.116.70) by warrior.services.quay.plus.net with SMTP; 13 Oct 2002 22:30:25 -0000 Received: from majordom by post.thorcom.com with local (Exim 4.10) id 180rES-0007Dg-00 for rsgb_lf_group-outgoing@blacksheep.org; Sun, 13 Oct 2002 23:29:08 +0100 Received: from [64.12.136.164] (helo=imo-m09.mx.aol.com) by post.thorcom.com with esmtp (Exim 4.10) id 180rES-0007DX-00 for rsgb_lf_group@blacksheep.org; Sun, 13 Oct 2002 23:29:08 +0100 Received: from MarkusVester@aol.com by imo-m09.mx.aol.com (mail_out_v34.13.) id l.73.277c350f (18707) for ; Sun, 13 Oct 2002 18:28:58 -0400 (EDT) From: MarkusVester@aol.com Message-ID: <73.277c350f.2adb4daa@aol.com> Date: Sun, 13 Oct 2002 18:28:58 EDT To: rsgb_lf_group@blacksheep.org MIME-Version: 1.0 X-Mailer: AOL 7.0 for Windows DE sub 10501 Subject: LF: Re: ARGO Content-Type: text/html; charset=windows-1252 X-Spam-Status: No, hits=1.9 required=5.0tests=NO_REAL_NAME,SPAM_PHRASE_00_01,USER_AGENT_AOLversion=2.42 X-Spam-Level: * Sender: Precedence: bulk Reply-To: rsgb_lf_group@blacksheep.org X-Listname: rsgb_lf_group Content-transfer-encoding: 8bit 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.

Anyhow, even if there was a bug somewhere in there, it doesn't seem to cause big trouble here, and certainly does not compromize Argo's value as an extremely useful tool and a great piece of work.

Regards
Markus, DF6NM