[Dxspider-support] disconnect

charlie carroll k1xx at cfl.rr.com
Wed Nov 7 02:06:00 CET 2007


Jack:
There are several ways you can go...

1. When connected as the sysop, use the command set/debug raw.  This 
will give you the most detailed information for further analysis.
2. Look at the debug files (spider\data\debug\2007\xxx.dat) after you've 
had a complete connect/disconnect cycle from the problem station.  A 
word of caution... you will get a ton of data to plod through, 
especially with the raw switch set for debug.  BTW, when you're done the 
tests, do a unset/debug raw command.
3. The other approach is to open a cmd window (this assumes you're using 
Windows as the OS), cd to \spider\perl, and then run the command "perl 
watchdbg <callsign of problem station>.  Now watch the real-time data 
through a complete connect/disconnect cycle.  The watchdbg command is a 
real-time method of watching info going into the debug file.  Putting 
the callsign afterwards filters the info so that you only see info 
associated with that callsign.  In this case, it's real time watching, 
but a whole lot less data.  The other advantage is that once the 
disconnect happens, you can use the scroll back buffer to examine the 
deter for the source of the disconnect.

Good luck... I've chased a lot of disconnects over the years and they're 
aren't easy to find.

73 charlie, k1xx



More information about the Dxspider-support mailing list