Message-ID: <4F68BF62.8020205@usa.net>
Date: Tue, 20 Mar 2012 18:33:22 +0100
From: Alberto di Bene <dibene@usa.net>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:11.0) Gecko/20120312 Thunderbird/11.0
MIME-Version: 1.0
To: rsgb_lf_group@blacksheep.org
References: <571D6C34075B42A09EFF57E5E25659BB@IBM7FFA209F07C>
In-Reply-To: <571D6C34075B42A09EFF57E5E25659BB@IBM7FFA209F07C>
Z-USANET-MsgId: XID245qcTRhZ6672X39
Subject: Re: LF: New Argo - Lock up
Content-Type: multipart/alternative;
 boundary="------------080005040905040406050906"
Sender: owner-rsgb_lf_group@blacksheep.org
Precedence: bulk
Reply-To: rsgb_lf_group@blacksheep.org
X-AOL-SCOLL-URL_COUNT: 0  
x-aol-sid: 3039ac1db4074f68c2e625ec
X-AOL-IP: 195.171.43.25
X-AOL-SPF: domain : blacksheep.org SPF : none


This is a multi-part message in MIME format.
--------------080005040905040406050906
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit

On 3/20/2012 5:33 PM, Chris wrote:
> Somebody else (not on here) who uses Argo has just told me his system locks up like mine in NDB mode. I thought the
> problem might be made worse by lack of memory here (the computer's, not mine, although come to think of it....), but
> he has 3gig so that appears to be nothing to do with it, just processor.
>  
Hi Chris,

   thanks for the report. Argo uses a lot of memory only in the very slow modes (QRSS600 and QRSS1200),
at least until I will have completed the changes I intend to do.   But not in the NDB mode....
The NDB mode taxes  the CPU as far as speed is concerned... even in Slow speed,  to have a decent flow
of the waterfall to allow seeing the CW dots and dashes, a new FFT is computed every 40 ms.  That means
25 FFTs of 2048 samples (for the NDB mode) each second, with the annex magnitude and color mapping
computations.  

The PC must be fast enough for this....  as said, I have no problems with a slow Atom mainboard, but I can well
understand that PCs slower than this can balk...   the apparent lock up is probably caused by the fact that there
are no more CPU cycles left to execute user commands.

Of course, if you and/or your friend are using a modern, fast PC, then what written above is no more valid,
and the cause of the lock ups must be elsewhere...

73  Alberto  I2PHD


--------------080005040905040406050906
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<html>
  <head>
    <meta content=3D"text/html; charset=3Dwindows-1252"
      http-equiv=3D"Content-Type">
  </head>
  <body bgcolor=3D"#FFFFFF" text=3D"#000000">
    On 3/20/2012 5:33 PM, Chris wrote:
    <blockquote
      cite=3D"mid:571D6C34075B42A09EFF57E5E25659BB@IBM7FFA209F07C"
      type=3D"cite">
      <meta content=3D"text/html; charset=3Dwindows-1252"
        http-equiv=3D"Content-Type">
      <meta name=3D"GENERATOR" content=3D"MSHTML 8.00.6001.19190">
      <style></style>
      <div><font face=3D"Arial" size=3D"2">Somebody else (not on here) wh=
o
          uses Argo has just told me his system locks up like mine in
          NDB mode. I thought the problem might be made worse by lack of
          memory here (the computer's, not mine, although come to think
          of it....), but he has 3gig so that appears to be nothing to
          do with it, just processor.</font></div>
      <div>=A0</div>
    </blockquote>
    Hi Chris,<br>
    <br>
    =A0=A0 thanks for the report. Argo uses a lot of memory only in the v=
ery
    slow modes (QRSS600 and QRSS1200),<br>
    at least until I will have completed the changes I intend to do. =A0
    But not in the NDB mode....<br>
    The NDB mode taxes=A0 the CPU as far as speed is concerned... even in
    Slow speed,=A0 to have a decent flow<br>
    of the waterfall to allow seeing the CW dots and dashes, a new FFT
    is computed every 40 ms.=A0 That means <br>
    25 FFTs of 2048 samples (for the NDB mode) each second, with the
    annex magnitude and color mapping <br>
    computations.=A0=A0 <br>
    <br>
    The PC must be fast enough for this....=A0 as said, I have no problem=
s
    with a slow Atom mainboard, but I can well<br>
    understand that PCs slower than this can balk... =A0 the apparent loc=
k
    up is probably caused by the fact that there<br>
    are no more CPU cycles left to execute user commands.<br>
    <br>
    Of course, if you and/or your friend are using a modern, fast PC,
    then what written above is no more valid,<br>
    and the cause of the lock ups must be elsewhere... <br>
    <br>
    73=A0 Alberto=A0 I2PHD<br>
    <br>
  </body>
</html>

--------------080005040905040406050906--