In our case it was the MMTTY process itself that was acting up. At least
this is what Task Manager on Win2k was showing us.
Norton AV was disabled all the time. Nothing else other that WL and MMTTY
was running + whatever processes Win2k itself would generate.
CPU Performance Graph ( Performance Tab from Task Manager) would average
somewhere around 10-20 % all the time while logging with MMTTY and Writelog.
Whenever the "hick-up" occurs , the graph would jump to 100 % and stay
there. When this condition clears (MMTTY becomes responsive again) the CPU
graph would drop back to normal.
We are planning to use this combination for upcoming expedition to Sable
Island (CY0MM in November) for RTTY activities. We are hoping we will be
able to figure this out before we go.
73, Nick
ve3ey
WA9ALS - John writes:
>> Will just mention this although I think I have brought it up before,
>> but on all of my machines, I have taken control of "virtual memory",
>> and set it manually. I have a minimum of 256K on all my machines and
>> usually find that setting the SWAP file to 384 does fine.
>
> A number of "solutions" like above might seem to help, but I'm not sure they
> get at the root of whatever problem is being discussed. I used to use WL
> with an old Gateway P166 with only 48K RAM. I could use it SO2R and still
> email and browse, with my AV program still active. If I could do all that
> with that "old" computer, it seems to me like one wouldn't have to go out of
> his way to disable a bunch of stuff to get WL working properly, especially
> on a newer, faster, more-RAM computer.
>
> Just my obs in case it helps. I don't know the answer to the problems being
> discussed, but I thought it might help to know that RAM limitations,
> processor speed, and the number of programs running isn't all there is to
> the consideration. 73
>
>
>
> _______________________________________________
> WriteLog mailing list
> WriteLog@contesting.com
> http://lists.contesting.com/mailman/listinfo/writelog
|