Probably, this is right...
We downgraded to the old, trusty, 10.40J and our 3 computers worked
perfectly for 50 hours.
On SSB, with the same HW and 10.55, it was a nightmare.
Ciao and 73
Guido, ik2bcp (iu2r)
----- Original Message -----
From: "Branislav Panak" <brano@panak.org>
To: <writelog@contesting.com>
Sent: Saturday, November 26, 2005 7:24 PM
Subject: Re: [WriteLog] Network Instability--some data to gather
> Imho problems with network started as writelog introduced tcp/ip
> networking.
> And I think it is not a problem of os .. Based on our experiments I think
> it
> is an application problem.
> We tried several os, hw, memory and cpu configs and it happens all the
> time
> regardless of hw and os.
>
> 73, Brano, OM2KW
>
> -----Original Message-----
> From: writelog-bounces@contesting.com
> [mailto:writelog-bounces@contesting.com] On Behalf Of Wayne Wright, W5XD
> Sent: Saturday, November 26, 2005 5:15 PM
> To: writelog@contesting.com
> Subject: Re: [WriteLog] Network Instability--some data to gather
>
> Some data that might help figure this problem out:
> This can only be done on XP (or Windows 2000--not Win 98).
> Bring up the Windows Task Manager. This can be done with a
> right click in the "Task Bar" (which by default is the bar
> at the bottom of the screen all the time, but users can
> change that). In the menu that pops up from the right click
> is a "Task Manager" entry--click it.
>
> One of the tabs in the Task Manager is "Processes". Choose it.
>
> In the "View" Menu is a "Select columns" entry. Choose it.
> In the window that comes up, make sure that all these are turned on:
>
> Memory Usage
> USER objects
> Virtual Memory Size
> Handle Count
> GDI Objects
>
> When the machine gets stressed (but before you have killed any of the
> offending processes) note the values for the various WriteLog processes:
>
> Bandma32.exe
> WriteL32.exe
> WlogNetDde.exe
>
> I suspect that on at least one of those processes that at usage of
> at least one of those system resources is growing without limit.
>
> How it came to be that starting happening now for code written
> years ago is a mystery at this time.
>
> Wayne, W5XD
>
> _______________________________________________
> WriteLog mailing list
> WriteLog@contesting.com
> http://lists.contesting.com/mailman/listinfo/writelog
> WriteLog on the web: http://www.writelog.com/
>
> _______________________________________________
> WriteLog mailing list
> WriteLog@contesting.com
> http://lists.contesting.com/mailman/listinfo/writelog
> WriteLog on the web: http://www.writelog.com/
>
_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web: http://www.writelog.com/
|