DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=btinternet.com;
  h=DKIM-Signature:Received:X-Yahoo-SMTP:X-YMail-OSG:X-Yahoo-Newman-Property:Message-ID:From:To:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-Antivirus:X-Antivirus-Status;
  b=c/VAwCsNBG7oS5dY7RfIzW683e9ChHm/ivDsmikTUKtwEKwJ/tZzC53jqAqDeCLV8DpcoU3eQw30GVow4FDhcsKWYLfBr3k89vT0iJuHl0gI9uVeVYwmUBilXwQcRv643mMMq9nI0dD3jCwHqjIoDGOR9Pd1aKaz8zQkDZ1B4yw=  ;
Message-ID: <002001cbbbbd$dca22ce0$4001a8c0@lark>
From: "Alan Melia" <alan.melia@btinternet.com>
To: <rsgb_lf_group@blacksheep.org>
References: <BLU146-W8C90B06E70218E706101FCFFD0@phx.gbl>
Date: Mon, 24 Jan 2011 11:57:11 -0000
MIME-Version: 1.0
DomainKey-Status: good (testing) 
Subject: LF: Re: Argo 134 lurker
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Sender: owner-rsgb_lf_group@blacksheep.org
Precedence: bulk
Reply-To: rsgb_lf_group@blacksheep.org


Hi Laurence I might have had something similar in the past. I have a feeling
that for some of these things a gentle registry edit is called for :-)) I
guess Alberto would be the best source of info.

I think I removed the registry references to Argo and then reinstalled it.
It was a long time ago!

Alan G3NYK


----- Original Message ----- 
From: "Laurence KL7UK" <hellozerohellozero@hotmail.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 clear a floating error on Argo  134I  gained
when I added too many noughts 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 -
trouble 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 "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.

Laurence