Okay - here is the data I have so far from stations that experience the
flashing-bandmap-followed-by-crash problem. I suspect more will come in
after this weekend. Ill continue to collect private email from those
having the problem for a few more days. Being neither a computer expert
nor software expert, my ability to help past facilitating is limited.
My only suggestion at this point to those with the problem is to go into
writelog.ini and under [Bandmap] change
DefaultTimeoutSeconds=1800 to a much smaller number. This may help if
the problem is related to handling large numbers of spots. If the
bandmap flashing is a symptom of the machines bogging down for some
other reason, this will probably not help.
Call, OS, # computers, CPU, RAM, network
WW4LL, 2000NT, 2, 1G+, ??, Ethernet, TCP/IP, WL10.55D
PJ2T, 98SE, 3, ~500MHz, ??, Ethernet TCP/IP, WL10.55D
PI4CC, 98SE, 7, 266MHz, 64M, Ethernet TCP/IP
W4MYA, 98SE, 7, 500MHz, ??, All wireless TCP/IP, WL10.55D
K5NA, XP, 7, 1G or better, 1G, Ethernet & wireless TCP/IP, WL10.55D
K5NA, same as above but with 2 computers
K5NA, same as above with WIN98SE
VE3XD, XP-SP2, 2, 2G, 512M, Ethernet TCP/IP, WL10.55D
Notes:
At K5NA the fastest machine crashes as often as the slowest
Several report shutting off the bandmap stops the crashes
Several report using their fastest machine as the hub - doesn't help
Several report problem for at least a year
W4MYA attempting to go back to WL 10.47
K7VIT reports inability to network WIN95 machine with XP machines -
unsure if flashing bandmap related.
Observations
Predates WL 10.55D
All popular OS: 98, 2K, XP
No correlation to machine speed
No correlation to RAM size
No correlation to Ethernet vs. wireless
Correlated to TCP/IP, but may not be causal
Hopefully, Writelog-Central will wade in on this shortly.
73
Hal
N4GG
_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web: http://www.writelog.com/
|