Return-Path: Received: from mtain-md06.r1000.mx.aol.com (mtain-md06.r1000.mx.aol.com [172.29.96.90]) by air-dd06.mail.aol.com (v129.4) with ESMTP id MAILINDD063-865c4d3d6b0dc8; Mon, 24 Jan 2011 07:05:33 -0500 Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by mtain-md06.r1000.mx.aol.com (Internet Inbound) with ESMTP id 7D599380000A1; Mon, 24 Jan 2011 07:05:26 -0500 (EST) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1PhL9s-0007rY-Ro for rs_out_1@blacksheep.org; Mon, 24 Jan 2011 12:04:32 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1PhL9s-0007rP-7v for rsgb_lf_group@blacksheep.org; Mon, 24 Jan 2011 12:04:32 +0000 Received: from blu0-omc1-s11.blu0.hotmail.com ([65.55.116.22]) by relay1.thorcom.net with esmtp (Exim 4.63) (envelope-from ) id 1PhL9r-0002io-D8 for rsgb_lf_group@blacksheep.org; Mon, 24 Jan 2011 12:04:32 +0000 Received: from BLU146-W11 ([65.55.116.9]) by blu0-omc1-s11.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 24 Jan 2011 04:04:24 -0800 Message-ID: X-Originating-IP: [64.197.174.145] From: Laurence KL7UK To: Date: Mon, 24 Jan 2011 03:04:24 -0900 Importance: Normal In-Reply-To: <002001cbbbbd$dca22ce0$4001a8c0@lark> References: ,<002001cbbbbd$dca22ce0$4001a8c0@lark> MIME-Version: 1.0 X-OriginalArrivalTime: 24 Jan 2011 12:04:24.0590 (UTC) FILETIME=[D79F1AE0:01CBBBBE] X-Spam-Score: 0.0 (/) X-Spam-Report: autolearn=disabled,HTML_MESSAGE=0.001 Content-Type: multipart/alternative; boundary="_65df95f4-2d0c-4ee2-ad30-2ac6b920218a_" Subject: RE: LF: Re: Argo 134 lurker X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.0 required=5.0 tests=FORGED_HOTMAIL_RCVD, HTML_MESSAGE autolearn=no version=2.63 X-SA-Exim-Scanned: Yes Sender: owner-rsgb_lf_group@blacksheep.org Precedence: bulk Reply-To: rsgb_lf_group@blacksheep.org X-Listname: rsgb_lf_group X-SA-Exim-Rcpt-To: rs_out_1@blacksheep.org X-SA-Exim-Scanned: No; SAEximRunCond expanded to false x-aol-sid: 3039ac1d605a4d3d6b062e10 X-AOL-IP: 195.171.43.25 X-Mailer: Unknown (No Version) --_65df95f4-2d0c-4ee2-ad30-2ac6b920218a_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Thanks John BDQ, Alan and others - Yes once I ran regedit from the cmd lin= e and removed Argo from there and also another lurking .pf file and reinst= alled Im now back working - thanks Chaps. =20 Laurence =20 > From: alan.melia@btinternet.com > To: rsgb_lf_group@blacksheep.org > Date: Mon, 24 Jan 2011 11:57:11 +0000 > Subject: LF: Re: Argo 134 lurker >=20 > Hi Laurence I might have had something similar in the past. I have a fee= ling > that for some of these things a gentle registry edit is called for :-))= I > guess Alberto would be the best source of info. >=20 > I think I removed the registry references to Argo and then reinstalled= it. > It was a long time ago! >=20 > Alan G3NYK >=20 >=20 > ----- Original Message -----=20 > From: "Laurence KL7UK" > To: > Sent: Monday, January 24, 2011 3:58 AM > Subject: LF: Argo 134 lurker >=20 >=20 >=20 >=20 > Im looking for suggestions to clear a floating error on Argo 134I gained > when I added too many noughts into the freq offset- or something odd. Iv= e > done this a couple of times in the past and recall its an oddity only wh= en > certain numbers are added - and it doesnt let you forget or correct - > trouble is I get the blank 134 screen up with the error message and it > locks. >=20 > I tried deinstalling and reinstalling, removing the prefetch but no matt= er > where I look I reckon there is a "lurkalot" file which I need to clear= which > is still retaining my error - it doesnt appear to be spec4 dll. Any > suggestions gratefully received. Its compounded by being on one of the > remote PC up in Alaska. This is the non hijacked version of 134 - with > thanks. >=20 > Laurence >=20 >=20 =3D --_65df95f4-2d0c-4ee2-ad30-2ac6b920218a_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Thanks John BDQ, Alan and others - Yes once I ran regedit from t= he cmd line and removed Argo from there and also another lurking .pf= file and reinstalled Im now back working - thanks Chaps.
 
Laurence
 
> From: alan.melia@btinternet.com
> To: rsgb_lf_group@blacksheep.= org
> Date: Mon, 24 Jan 2011 11:57:11 +0000
> Subject: LF: Re:= Argo 134 lurker
>
> Hi Laurence I might have had something= similar in the past. I have a feeling
> that for some of these thin= gs a gentle registry edit is called for :-)) I
> guess Alberto would= be the best source of info.
>
> I think I removed the regist= ry references to Argo and then reinstalled it.
> It was a long time= ago!
>
> Alan G3NYK
>
>
> ----- Original= Message -----
> From: "Laurence KL7UK" <hellozerohellozero@hotm= ail.com>
> To: <rsgb_lf_group@blacksheep.org>
> Sent:= Monday, January 24, 2011 3:58 AM
> Subject: LF: Argo 134 lurker
= >
>
>
>
> Im looking for suggestions to cle= ar a floating error on Argo 134I gained
> when I added too many noug= hts into the freq offset- or something odd. Ive
> done this a couple= of times in the past and recall its an oddity only when
> certain= numbers are added - and it doesnt let you forget or correct -
> tro= uble is I get the blank 134 screen up with the error message and it
>= ; locks.
>
> I tried deinstalling and reinstalling, removing= the prefetch but no matter
> where I look I reckon there is a "lurk= alot" file which I need to clear which
> is still retaining my error= - it doesnt appear to be spec4 dll. Any
> suggestions gratefully re= ceived. Its compounded by being on one of the
> remote PC up in Alas= ka. This is the non hijacked version of 134 - with
> thanks.
>=
> Laurence
>
>
=3D --_65df95f4-2d0c-4ee2-ad30-2ac6b920218a_--