Yes me too. Its only the last couple of releases I finally decided to look
(hoping for an instruction manual!!)
Terry
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Mike Dennison
Sent: 28 January 2012 16:08
To: [email protected]
Subject: RE: LF: Re: Opera query
OK. Red face, here, then.
I must admit to ignoring readme files, as they are usually just
adverts, or state the absolutely obvious.
Thanks for the useful tip.
Mike
====
> Just in case you haven't read it, the "readme.txt" file issued with
> each release lists the change in the latest release + a very brief
> description of all updates since 1.0.0
>
> Terry
>
> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]] On Behalf Of Graham
> Sent: 28 January 2012 14:29
> To: [email protected]
> Subject: Re: LF: Re: Opera query
>
> I think last time JR documented anything it went up in sheet of
> flames ,
>
> a sort of James Cagney , white heat moment , but as of 24.00z 1
> Feb There are 7 + special hf Tx permits issued by the fcc ,
> with the intent of slaying the Spread Spectrum dragon... after that
> normality should return.. what ever that is !
>
> Call qrz link That's one of the ROS package features .
>
> Changes 119 > 120 added the last hf bands to the list
> 14/7/5 MHz
>
> I think 2 / 8 mins would be better for 500 , 15 really is
> masking rx reports and the band propagation can change in 2
> cycles , op8 is giving good results on 136 , but there is yet to
> be a real long haul
>
> attempt to prove op32 (or op64)
>
> G..
>
> --------------------------------------------------
> From: "Mike Dennison" <[email protected]>
> Sent: Saturday, January 28, 2012 2:07 PM
> To: <[email protected]>
> Subject: Re: LF: Re: Opera query
>
> > Ah, that's interesting. A feature completely hidden by the fact that
> > the software does not alter the cursor when it hovers over the
> > clickable link, unlike the convention for most Windows software.
> >
> > Thanks to all for your help. I can't help thinking that all of this
> > discussion would have been unnecessary if the software was properly
> > documented. I am now using Op 1.2.0. and I have no idea what, if
> > anything, is different from 1.1.9.
> >
> > Mike, G3XDV
> > ==========
> >
> >
> >> Yes but click on a Call Sign in the interweb list and all is
> >> revealed.
> >>
> >> Eddie
> >>
> >> On 27/01/2012 21:02, Gary G4WGT wrote:
> >> > Mike,
> >> >
> >> > I presume because it only relates to the beam heading at your
> >> > station. Showing it on other reports is meaningless to you.
> >> >
> >> > Gary.
> >> >
> >> > ----- Original Message ----- From: "Mike Dennison"
> >> > <[email protected]>
> >> > To: <[email protected]>
> >> > Sent: Friday, January 27, 2012 8:47 PM
> >> > Subject: Re: LF: Re: Opera query
> >> >
> >> >
> >> >> OK, Gary, but why don't I see it on anyone else's reports?
> >> >>
> >> >> MIke
> >> >> ====
> >> >>
> >> >>> That is beam heading.
> >> >>>
> >> >>> 73, Gary - G4WGT.
> >> >>>
> >> >>> ----- Original Message ----- From: "Mike Dennison"
> >> >>> <[email protected]>
> >> >>> To: <[email protected]>
> >> >>> Sent: Friday, January 27, 2012 7:53 PM
> >> >>> Subject: LF: Opera query
> >> >>>
> >> >>>
> >> >>> > Can any of the Opera experts here tell me why my distance
> >> >>> > report has an apparently spurius "@:nnn" where 'nnn' is a
> >> >>> > number from 001 to about 500. The number is different for
> >> >>> > different stations received, but stays the same each time
> >> >>> > that station is heard. The left hand side of the screen looks
> >> >>> > like:
> >> >>> >
> >> >>> > 19:00 136 M0DTS Op8 -28dB 305km @ 347
> >> >>> >
> >> >>> > and the right hand side (the web report) repeats this before
> >> >>> > my location.
> >> >>> >
> >> >>> > This appeared when I upgraded to Op 1.1.7 and is still there
> >> >>> > with Op 1.1.9.:
> >> >>> >
> >> >>> > Any thoughts?
> >> >>> >
> >> >>> > Mike, G3XDV
> >> >>> > ==========
> >> >>> >
> >> >>> >
> >> >>>
> >> >>
> >> >>
> >> >>
> >> >>
> >> >
> >> >
> >> >
> >>
> >>
> >
> >
> >
> >
>
>
|
