Thanks John BDQ, Alan and others - Yes once I ran regedit from the cmd line and removed Argo from there and also another lurking .pf file and reinstalled Im now back working - thanks Chaps.
Laurence
> From: [email protected]
> To: [email protected]
> 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 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" <[email protected]>
> To: <[email protected]>
> 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
>
>
=
|
|
