Yes this is a bug
So the work around is:
Do not open a packet window unless you start a telnet session.
If setting up for a contest just save the configuration without packet checked.
If you do open Writelog with packet, just remember to start a telnet session.
It is not too bad once you get used to the problem.
Hopefully this will be fixed with the next update.
73 John wa5zup
> Date: Thu, 3 Dec 2009 09:43:34 -0500
> From: lists@w1nr.net
> To: jmaass@k8nd.com
> CC: writelog@contesting.com
> Subject: Re: [WriteLog] "Zombie" Packet Windows Writelog 10.73D
>
> I have run into this problem too. I was able to reproduce it as follows:
>
> Start up a session that was saved to open the packet window at startup.
> Open a log and close WriteLog without logging in to the cluster (leave
> the connection dialog window alone)
> You now have a zombie packet window that cannot be closed.
> Starting WriteLog again will create another instance.
>
> Mike, W1NR
>
>
> Jeff Maass wrote:
> > Has anyone else experienced Writelog packet windows being left running
> > after Writelog is
> > terminated, and which will not die when clicking the "X'?
> >
> > At PJ2T, we installed the Writelog 10.73D release on four PCs running
> > Windows XP and
> > Windows 98 SE2. All had this problem. It seemed to happen when the packet
> > window was
> > started automatically at startup, but no telnet connection was made before
> > Writelog was
> > terminated.
> >
> >
> > 73, Jeff K8ND
> >
> >
> >
>
> _______________________________________________
> 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/
|