From: "G4WGT" <g4wgt@talkgas.net>
To: rsgb_lf_group@blacksheep.org
Cc: dibene@usa.net
Date: Fri, 29 Nov 2002 18:45:04 -0000
Message-ID: <LNEDLBPBBNGOKDMCCGJNMECMCCAA.g4wgt@talkgas.net>
MIME-Version: 1.0
Importance: Normal
In-reply-to: <3DE63D31.5090202@usa.net>
Subject: LF: RE: Status report about Argo on XP and slow PCs
Content-Type: text/plain; charset=Windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Sender: <owner-rsgb_lf_group@blacksheep.org>
Precedence: bulk
Reply-To: rsgb_lf_group@blacksheep.org

Alberto,

I have had the Argo 130 test version & screen capture running for 24 hours
with no problems at all, I have been using the PC normally for my usual
daily routines including MS Word, telephone fax & voice mail, internet
access, photo display & printing during this time. It looks like you have
got to the root of the problems. My earlier runs with Argo 130 & Windows
2000 Pro (as I reported to you) were going faulty within 1 hour.

Thank you for your attention and making the corrections.

73

Gary G4WGT.

-----Original Message-----
From: owner-rsgb_lf_group@blacksheep.org
[mailto:owner-rsgb_lf_group@blacksheep.org]On Behalf Of Alberto di Bene
Sent: 28 November 2002 15:59
To: LF Mailing List; lf; lowfer@mailman.qth.net
Subject: LF: Status report about Argo on XP and slow PCs


Good afternoon all,

  I received a few reports about problems that Argo has on Win XP and/or
2000,
and a few others where similar problems seemed to surface when running on
slow laptops, usually Pentium 166 MHz with Win 95.

After some trials, and thanks to a suggestion of Wolf, I succeeded in
reproducing
the problem on my PC, which, by today standards, is also a slow machine
(an Athlon
750 MHz), but fast enough to prevent me to spot the problem earlier.

What apparently happened was a buffer starvation during high CPU load peaks,
where the buffer pool I had allocated was emptied before the program had
a chance
to requeue them to the sound subsystem, after processing.
I have changed the logic of the program in this section, and now it
seems to work ok,
at least on my PC. This means that I am now unable to reproduce the
problem,
but I can't have an absolute certainty.
This is where I need your cooperation, expecially from those who
reported the
malfunction, no matter whether on Win 95 or XP or 2000.

I have uploaded a test version on
 http://www.weaksignals.com/bin/argo130test.zip
Please unzip it in your Argo directory, so that it can use the DLL,
which hasn't changed.
If your reports will be positive, then I will change the released version.

BTW, while at this, I discovered a quirk of the Borland compiler
TRegistry class under XP,
which forced me to not use it, calling instead directly the Windows APIs.
This has the unfortunate consequence that the format of the settings has
changed,
so you will have to save them again, using the same or a different name.
 Sorry, but
in this case the culprit is not me.

Thanks,

73  Alberto  I2PHD


---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.423 / Virus Database: 238 - Release Date: 25/11/2002

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.423 / Virus Database: 238 - Release Date: 25/11/2002