| |
G0FTD > AGW 24.05.04 20:00l 33 Lines 968 Bytes #999 (0) @ WW
BID : B90173G0FTD
Read: DJ6SS GUEST DM3ER
Subj: Re:Windows,Packet,Baycom,AGW
Path: DB0FHN<DB0FOR<DB0MRW<DB0SON<DB0ERF<DB0FBB<DB0GOS<ON0AR<ON0AR<7M3TJZ<
ZL2TZE<GB7YFS<GB7WIG
Sent: 040524/1043Z @:GB7WIG.#34.GBR.EU #:52658 XFBB7.03 Bid:B90173G0FTD
From: G0FTD@GB7WIG.#34.GBR.EU
To : AGW@WW
>> If your using the latest version of AGW then I hope you have infinate
>> amounts of RAM, because it WILL eventually crash ;-)
>>
>> SOLUTION: Run an older version if you can that doesn't have the memory
>> release bug.
>>
>> - Andy -
>
> Am using 2002.10. No problems to date.
Thats why then ;-)
Test done here and with RU3BB have concluded:
v2002.308 = Memory release bug. AGW uses a pice of memory for a task but
forgets to release it afterwards. Instead it then steals another piece of
RAM and so on. Eventually it crashes. More RAM = longer time BEFORE eventual
crash. Crash also hold PTT lin high and your tx will be on all the time
until PC reboots. Your rigs PA might get hot and meets it's maker if you
don't notice it quick enough.
v2002.10 = so far so good, no memory bug and takes a little less ram
anyway. No crashes discovered after long term use.
73 - Andy
Message timed: 11:41 on 2004-May-24
Read previous mail | Read next mail
| |
