Hi Jim,
This will tell ya what you need to know...and a LOT more, very nice small
footprint utility that all the pc builders have used
https://drive.google.com/file/d/1Z3wG5IuuxMfHf538P3_Z4UT2R_kXbzuC/view?usp=sharing
>From my Google drive, it's safe. 73
N0AN
Hasan
On Wed, Jun 9, 2021 at 12:30
Another Linux way is to use the "lscpu" command.
An easy way to see the flags would be "lscpu | grep -i avx".
-David, N9KT
On Wed, Jun 9, 2021 at 2:53 PM Michael Pittaro wrote:
> Intel provides tools to do the feature identification for you. See:
>
> https://www.intel.com/content/www/us/en/
Intel provides tools to do the feature identification for you. See:
https://www.intel.com/content/www/us/en/support/articles/05607/boards-and-kits/desktop-boards.html
The Intel processor identification utility provides the information
directly. (I believe this is windows only, but didn't dig
Hi Jim,
the generic names server to show roughly when features like AVX were
introduced but specific models may or may not have support since the CPU
manufacturers support a range of price, performance, and power
consumption points. You must either use a tool that reports the
capabilities or
I strongly agree with George.
FWIW, I found the link Bill provided in his initial post with
development names for processor versions useless -- looking at my
machines, they don't show those names.
73, Jim K9YC
On 6/9/2021 9:49 AM, George J Molnar wrote:
I’d definitely support development usi
Sorry,
Il 04/08/2017 21:17, Wolfgang ha scritto:
Hello Alessandro,
did you read this message, before you wrote yours ? ;-)
73 de Wolfgang
OE1MWW
Friday, August 4, 2017, 8:20:08 PM, Bill wrote:
Re: [wsjt-devel] WSJT-X: development branch has double line spacing of decodeds
Hi All,
I
Hi joe have now rered the manuel and i need to ask santa for a faster
computer hi thanks for your time i like to use jwsjt program have had
over 3000 qso in 125 dxcc with limited wire ae i to can work the dx
happy xmas
73 gordon thanks again
On 22 December 2016 at 15:53, Joe Taylor wrote
On 12/22/2016 9:43 AM, Gordon Higgins wrote:
> hi joe i have used the early version with out any problem if i put in
> 7305 the clock runs fine on msk144 but when i try to use 7405 the clock
> is eratic
... because you did not read the manual at the place I directed you to.
-- Joe, K1J
G3WDG HI CHARLIE HAVE NOW SWITCHED TO FAST DECODE AND ALL SEAMS OK THANKS
FOR HINT DID NOT NOTICE THIS ON EARLER VERSIONS
73 GORDON
On 22 December 2016 at 14:43, Gordon Higgins wrote:
> hi joe i have used the early version with out any problem if i put in
> 7305 the clock runs fine on msk14
hi joe i have used the early version with out any problem if i put in 7305
the clock runs fine on msk144 but when i try to use 7405 the clock is
eratic
On 22 December 2016 at 14:31, Joe Taylor wrote:
> Gordon --
>
> On 12/22/2016 9:23 AM, Gordon Higgins G3PXT wrote:
> > Hello using wsjt-x v1.7.
0.
>> >
>> > Will advise...
>> >
>> > Dan n5tm
>> >
>> >
>> > -Original Message-
>> > From: Joe Taylor [mailto:j...@princeton.edu]
>> > Sent: Tuesday, December 20, 2016 3:46 PM
>> > To: WSJT software devel
Gordon --
On 12/22/2016 9:23 AM, Gordon Higgins G3PXT wrote:
> Hello using wsjt-x v1.7.0r7405
> on jt65 jt9 etc works fine when i sellect msk144 the clock does not
> tick evenly ie goes 48-49-50-55-8-10-14- sec etc ie missing tick any
> help have reloaded program go back to jt 65 clock tic
inal Message-
> > From: Joe Taylor [mailto:j...@princeton.edu]
> > Sent: Tuesday, December 20, 2016 3:46 PM
> > To: WSJT software development
> > Subject: Re: [wsjt-devel] WSJT-X Development
> >
> > Dan --
> >
> > On 12/20/2016 2:31 PM, Dan Ba
6 PM
> To: WSJT software development
> Subject: Re: [wsjt-devel] WSJT-X Development
>
> Dan --
>
> On 12/20/2016 2:31 PM, Dan Bates N5TM wrote:
>> Joe, 7405 seemed to have a major bug when trying to run QRA64. The
>> Decode button would stick in "blue" a
Joe, yes, I was able to see the same issue on 7412.. will keep testing.
Dan n5tm
-Original Message-
From: Joe Taylor [mailto:j...@princeton.edu]
Sent: Tuesday, December 20, 2016 3:46 PM
To: WSJT software development
Subject: Re: [wsjt-devel] WSJT-X Development
Dan --
On 12/20/2016 2
Joe,
Some of us have been testing QRA64 on 160 late at night, 1839 or 1840.
Will advise...
Dan n5tm
-Original Message-
From: Joe Taylor [mailto:j...@princeton.edu]
Sent: Tuesday, December 20, 2016 3:46 PM
To: WSJT software development
Subject: Re: [wsjt-devel] WSJT-X Development
Dan --
On 12/20/2016 2:31 PM, Dan Bates N5TM wrote:
> Joe, 7405 seemed to have a major bug when trying to run QRA64. The Decode
> button would stick in "blue" and no decode would appear. I'm now testing
> 7412 and QRA seems ok.
Yes, you can get r7405 into the state you describe. Also 7412. I
Joe, 7405 seemed to have a major bug when trying to run QRA64. The Decode
button would stick in "blue" and no decode would appear. I'm now testing
7412 and QRA seems ok.
Dan n5tm
-Original Message-
From: Joe Taylor [mailto:j...@princeton.edu]
Sent: Tuesday, December 20, 2016 1:02 PM
To
hi joe as a user off jt i keep up with latest soft ware is it possible to
be able to select call sign and leave ones tx freqence where it is as on
30m you can soon be out off band allocation chasing the dx higher up the
waterfall have had nearly 3000 qso with jt in 125 dxcc some times on
dead
3:57 PM
> To: wsjt-devel@lists.sourceforge.net
> Subject: Re: [wsjt-devel] WSJT-X Development Status
>
> On 27/05/2015 21:43, Alessandro Gorobey wrote:
>> Hi Bill,
> Hi Sandro,
>> I hope you refer only the server side of message_aggregator see below
> Oh yes. The client c
Thanks Bill,
all good news
73
Sandro
IW3RAB
Il 27/05/2015 22:57, Bill Somerville ha scritto:
> On 27/05/2015 21:43, Alessandro Gorobey wrote:
>> Hi Bill,
> Hi Sandro,
>>
>> I hope you refer only the server side of message_aggregator
>> see below
> Oh yes. The client code in WSJT-X is definitely s
I know JTAlert is working on it. What are the other two?
73
Mike W9MDB
-Original Message-
From: Bill Somerville [mailto:g4...@classdesign.com]
Sent: Wednesday, May 27, 2015 3:57 PM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] WSJT-X Development Status
On 27/05/2015
On 27/05/2015 21:43, Alessandro Gorobey wrote:
> Hi Bill,
Hi Sandro,
>
> I hope you refer only the server side of message_aggregator
> see below
Oh yes. The client code in WSJT-X is definitely staying in. At least
three applications that I know of are already using it ready for when
v1.5 goes to
Hi Bill,
I hope you refer only the server side of message_aggregator
see below
Il 27/05/2015 20:40, Bill Somerville ha scritto:
> On 27/05/2015 19:24, Alessandro Gorobey wrote:
>> Hi Bill,
> Hi Sandro,
>>
>> I perfectly understand the status.
>>
>> But I hope that some very good software will no
On 27/05/2015 19:24, Alessandro Gorobey wrote:
> Hi Bill,
Hi Sandro,
>
> I perfectly understand the status.
>
> But I hope that some very good software will no be lost.
>
> Eg jt9sim.exe is compiled but not installed.
> Eg All the FMT suite present in WSPR that using PY only for marginal
> operatio
Hi Bill,
I perfectly understand the status.
But I hope that some very good software will no be lost.
Eg jt9sim.exe is compiled but not installed.
Eg All the FMT suite present in WSPR that using PY only for marginal
operations and use some library of WSJTX
why not maintain these as installed p
Hi All,
further to Joe's comments below, we have now reintegrated his WSPR mode
work in the wsjtx_exp branch into the main WSJT-X development branch.
Currently wsjtx_exp is dormant and the latest and greatest WSJT-X is to
be found on the main development branch ^/branches/wsjtx .
The main deve
Hi Bill and all,
Next topic...
On 5/25/2015 6:12 AM, Bill Somerville wrote:
> Joe, are you proposing that the JT4 and other VHF and up features are
> released along with the WSPR features? I am a little uncomfortable with
> that as it is a lot of new content for one release and I suspect that
> b
On 26/05/2015 16:21, Joe Taylor wrote:
> Hi Bill,
Hi Joe,
>
> On 5/25/2015 6:12 AM, Bill Somerville wrote:
>> we currently have the v1.5 branch of WSJT-X awaiting some documentation
>> updates before making a new release candidate, although unrelated it
>> would be nice to get that moving as well.
Hi Bill,
On 5/25/2015 6:12 AM, Bill Somerville wrote:
> we currently have the v1.5 branch of WSJT-X awaiting some documentation
> updates before making a new release candidate, although unrelated it
> would be nice to get that moving as well. The v1.5 branch has a few bug
> fixes since the RC1 rel
On 22/05/2015 23:37, KI7MT wrote:
Hi Greg & Joe, a few comments from me below:
> Hi Joe,
>
> I am not familiar HSHV, so I can't comment on it directly. However, I do
> have a few comments that me be of some use while considering a new path(s).
>
> The major Debian based derivatives have already p
Hi Joe & All,
we currently have the v1.5 branch of WSJT-X awaiting some documentation
updates before making a new release candidate, although unrelated it
would be nice to get that moving as well. The v1.5 branch has a few bug
fixes since the RC1 release which need to be published. I would also
On Sat, 23 May 2015 13:19:35 +0200
"Peter Frenning [OZ1PIF]" wrote:
> Den 22-05-2015 kl. 22:51 skrev Joe Taylor:
> Hi all,
>
> I have some further thoughts on topics raised in my message earlier today.
>
> As I stated there, the planned incorporation of all WSJT "slow modes"
> (JT4, JT9, JT65,
Den 22-05-2015 kl. 22:51 skrev Joe
Taylor:
Hi all,
I have some further thoughts on topics raised in my message earlier today.
As I stated there, the planned incorporation of all WSJT "slow modes"
(JT4, JT9, JT65, and WSPR) in WSJT-X is nearing completion.
Some t
Hi Joe,
I am not familiar HSHV, so I can't comment on it directly. However, I do
have a few comments that me be of some use while considering a new path(s).
The major Debian based derivatives have already pushed past Qt5.2. Most
are on 5.3 and Ubuntu, for their next LTS release will be on 5.4 at
Hi all,
I have some further thoughts on topics raised in my message earlier today.
As I stated there, the planned incorporation of all WSJT "slow modes"
(JT4, JT9, JT65, and WSPR) in WSJT-X is nearing completion.
Some time ago we noted that the usage and program behavior in the WSJT
"fast mode
36 matches
Mail list logo
