Thanks Ed,
Its definitely something in TCP/IP and not in NetDDE for me. I had the
problem in previous versions and switched back to NetDDE. After reading
about successful operations with IP, I switched back and it still did the
same thing. After changing back over to NetDDE, it didn't fault again the
remainder of the contest.
About the computer browser, yeah I know what you mean. 2000 and XP now use
DNS for name resolution instead of of netbios names, if the information is
available. I don't have a DNS server running, but did fill out the Host
file on both machines with all the names and addresses of all workstations
on the network.
I need to get out to the camp and get that errorlog file and read over it to
see what failed at what time.
Charlie
Ki5xp
> -----Original Message-----
> From: J. Edward (Ed) Muns [mailto:w0yk@msn.com]
> Sent: Tuesday, March 06, 2007 7:01 PM
> To: cfmorris@bellsouth.net
> Cc: writelog@contesting.com; W8AV@aol.com
> Subject: RE: [WriteLog] Writelog 10.62 TCP/IP Networking
>
> I experienced this same thing during WPX RTTY and all through
> the preceding week of testing, with 10.62h. In Round-Up, I
> used 10.62g and the problem was less severe, i.e., occurred
> less frequently. In my case, I am using three identical
> laptops, all with Windows XP, SP2 and all with the latest
> Windows updates. The three are networked together using
> TCP/IP, with the third computer as a spare, only recording the log.
>
> In my experience, it seemed that the disconnect happened more
> often when there was no logging taking place or other
> explicit network activity going on. After a network
> disconnect/reconnect within WriteLog, the problem would not
> occur until about an hour later if it occurred at all. But,
> it almost always occurred if the network was idle. Many
> times, if there was logging going on at both computers, the
> time-to-disconnect was delayed.
>
> One well-known problem with Windows TCP/IP networking is that
> the computer browser (NOT the Internet browser) that scans
> the network for connected computers, often will not list all
> the computers on the network even though they are all
> accessible when addressed by another computer on the network.
> This is disconcerting but doesn't keep the network from
> working. I don't know if this is related to this problem
> we're seeing with WriteLog.
>
> I have not tried NetDDE to see if that works better. I
> suppose that is the next step. However, I will note that I
> had none of these problems in NAQP RTTY using 10.62h on old
> (identical) tower computers also running Windows XP, SP2.
>
> 73,
> Ed - W0YK
>
> > -----Original Message-----
> > From: writelog-bounces@contesting.com
> > [mailto:writelog-bounces@contesting.com] On Behalf Of
> Charles Morrison
> > Sent: Tuesday, 06 March, 2007 06:37
> > To: W8AV@aol.com; writelog@contesting.com
> > Subject: Re: [WriteLog] Writelog 10.62 TCP/IP Networking
> >
> > Goose,
> >
> > They're two "non-identical" (read: Ham shack computers!! hi
> > hi) running fully patched, Windows 2000, SP4. No other
> problems with
> > any other part of Writelog except that. Both are configured with
> > static addresses, both have all entries for all workstations on the
> > network in the Hosts file, both have a CORRECTLY configured lmhosts
> > file for netbios resolution (guess that's why
> > NetDDE works). Not running any A/V on it.
> >
> > Since they're non identical, I don't want to start out blaming
> > hardware.
> > The motherboards are different (Gigabyte and an Asus), the
> processors
> > are different (Athlon XP and Duron), both have over 512mb ram, but
> > different video cards, different onboard sound chips,
> different size
> > hard drives.
> >
> > The only time I have this crash is when they're networked
> via TCP/IP.
> > NetDDE does not cause a crash. And it doesnt take down the entire
> > program, only the networking portion of it, forcing a
> restart of the
> > networking services.
> >
> > ki5xp
> >
> >
> >
> > _____
> >
> > From: W8AV@aol.com [mailto:W8AV@aol.com]
> > Sent: Tuesday, March 06, 2007 6:10 AM
> > To: cfmorris@bellsouth.net; writelog@contesting.com
> > Subject: Re: [WriteLog] Writelog 10.62 TCP/IP Networking
> >
> >
> >
> > Charlie:
> >
> > I used TCP/IP in the ARRL CW contest to link six computers with
> > Writelog
> > 10.55 running on a Windows XP platform and had none of the problems
> > you described. Oh I had a computer "lose its way" once or twice in
> > the contest, but for the most part everything was rock solid.
> > Furthermore, when I operate from PJ2T, we link computers in
> teh same
> > way that I do it at home and it is pretty much bullet proof. Sounds
> > like you have some kind of conflict in the networking or
> some problem
> > in the operating system. What O/S are you using on your computers?
> >
> > 73............de Goose, W8AV
> >
> >
> >
> >
> > _____
> >
> > AOL now offers free email to everyone. Find out more about
> what's free
> > from AOL at
> > <http://pr.atwola.com/promoclk/1615326657x4311227241x429808213
> > 7/aol?redir=ht
> > tp%3A%2F%2Fwww%2Eaol%2Ecom> AOL.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/
|