Return-Path: Received: (qmail 18237 invoked from network); 13 Oct 2002 14:38:04 -0000 Received: from marstons.services.quay.plus.net (212.159.14.223) by mailstore with SMTP; 13 Oct 2002 14:38:04 -0000 Received: (qmail 11844 invoked by uid 10001); 13 Oct 2002 15:42:42 -0000 Received: from post.thorcom.com (193.82.116.70) by marstons.services.quay.plus.net with SMTP; 13 Oct 2002 15:42:42 -0000 Received: from majordom by post.thorcom.com with local (Exim 4.10) id 180jro-00059v-00 for rsgb_lf_group-outgoing@blacksheep.org; Sun, 13 Oct 2002 15:37:16 +0100 Received: from [216.93.66.204] (helo=mail5.mx.voyager.net) by post.thorcom.com with esmtp (Exim 4.10) id 180jrn-00059m-00 for rsgb_lf_group@blacksheep.org; Sun, 13 Oct 2002 15:37:15 +0100 Received: from k6500 (d26.as3.mpls.mn.voyager.net [169.207.249.250] (may be forged)) by mail5.mx.voyager.net (8.11.6/8.10.2) with SMTP id g9DEaOk89020 for ; Sun, 13 Oct 2002 10:36:24 -0400 (EDT) From: "WE0H" To: rsgb_lf_group@blacksheep.org Date: Sun, 13 Oct 2002 09:37:25 -0500 Message-ID: MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Importance: Normal In-reply-to: <000201c2729b$65a1e000$b4e5fc3e@l8p8y6> Subject: LF: RE: ARGO Content-Type: text/html; charset=windows-1252 X-Spam-Status: No, hits=1.7 required=5.0tests=BIG_FONT,HTML_70_90,HTML_FONT_COLOR_BLUE, HTML_FONT_COLOR_NAME,IN_REP_TO,MAY_BE_FORGED, SPAM_PHRASE_00_01,USER_AGENT_OUTLOOKversion=2.42 X-Spam-Level: * Sender: Precedence: bulk Reply-To: rsgb_lf_group@blacksheep.org X-Listname: rsgb_lf_group Content-transfer-encoding: 8bit

No problems here on Windows 95 OSR-2 or Windows 2000 SP-2.

 

Mike>WE0H

http://www.we0h.us/lf.html

 

-----Original Message-----
From: owner-rsgb_lf_group@blacksheep.org [mailto:owner-rsgb_lf_group@blacksheep.org]On Behalf Of hamilton mal
Sent: Sunday, October 13, 2002 2:41 AM
To: rsgb_lf_group@blacksheep.org
Subject: LF: ARGO

 

Hello All

I am getting Fatal Error VXD messages and crashes with ARGO on my main PC/Windows.

The same thing is happening on my Portable PC so it looks like a bug in ARGO. Does anyone else have this problem.

All other s/ware runs ok and no crashes. Is there a cure for an otherwise excellent prog.

Re starting the prog only lasts a short time before another crash but if the computer is closed down completely ie restarted then it runs longer before a crash.

 

73 de Mal/G3KEV