| |
G0FTD > AGW 02.05.04 17:08l 38 Lines 1318 Bytes #999 (0) @ WW
BID : BE5033G0FTD
Read: DC3RJ GUEST
Subj: Re: Win98,AGW and RAM
Path: DB0FHN<DB0FOR<DB0SIF<DB0FSG<DB0RGB<OK0PPL<DB0RES<ON0AR<7M3TJZ<LZ3NP<
HA3PG<IK1ZNW<GB7CRV<GB7CIP<GB7SXE
Sent: 040502/1329Z @:GB7SXE.#38.GBR.EU #:46338 [Hastings] FBB7.00i $:BE5033G0FT
From: G0FTD@GB7SXE.#38.GBR.EU
To : AGW@WW
GM7HUD wrote:-
> The Duke Of Kent wrote:
>>My Celeron 466Mhz and 32 meg runs Win98se superbly.
>
> No it doesn't! The little red light on your disk will be on almost all
> the time. 64MB and it runs acceptably, 128MB and its quite slick.
>
> There is no substitute for memory on modern operating systems and its peanuts
> to buy nowadays. These OSes are designed to have lots of memory available
> and believe me, they dont work well when there isn't.
Surprisingly the disk hardly seems to be accessed.
I can run multiple copies of antenna modelling programs, all number
crunching at the same time, run Excel, view pictures,Windows Commander,
RFSIM, AGSatracker all day longs without a hitch.
Run just Winpack and AGW and it will crash within the hour.
I'm convinced AGW leaks memory.
It seems to use a pice of memory to do a task but it then fails to
release it. The result is that when it's leaked away all the memory it
crashes. Adding memory would just prolong the time before the next crash
which I'm sure we'd both agree is not the solution.
I suspect AGW holds recieved data in memory and processes it instead of
writing to disk and processing it. Well I suppose the former is the correct
way, but the memory needs to be released afterwards.
- Andy -
Read previous mail | Read next mail
| |
