What "flavor" of networking are you using for your MM or M2 station (or SO2R for that matter) in Writelog? NetDDE or TCP/IP? I commented to Don on the phone just last week that my previous attempts t
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"
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 wit
Hey Charles, Since XP(and VISTA) are really NT why does any logging program try to control networking? NT allows you to store the program on a CPU and share it with the connecting PC's. You can use N
Dave, Its not a matter of the program trying to control the networking, it's the method by which the log's between the two computers are shared across the network. Im not a programmer so I cant speak
Dave, Its not a matter of the program trying to control the networking, it's the method by which the log's between the two computers are shared across the network. Im not a programmer so I cant speak
Thanks George, its not a problem of connecting, its a problem of the link disconnecting and causing a Network error log to be produced. I dont have the log with me, its out at the camp, but I did loo
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. I
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 switch