WriteLog
[Top] [All Lists]

[WriteLog] Packet in WL

To: <writelog@contesting.com>
Subject: [WriteLog] Packet in WL
From: scot@k9jy.com (Scot Herrick)
Date: Wed, 18 Apr 2001 14:06:11 -0500
Hi Erik,

I see two possibilities:

First, the com port has to be identified in the Packet Window for the TNC.
If it's 'none' and your tnc is on 'Com1,' you won't get anything in the
window.

Second, the Com parameters in the WriteLog.ini file have to match your
settings. So if your TNC is at 1200 baud on Com 1, the WriteLog.ini file
defaults to 9600 and you won't see it on the screen either.

Hum us back a few bars after checking; it's something simple in the setup.

CU...Scot, K9JY

See the complete WriteLog user guide at http://www.k9jy.com

mailto:scot@k9jy.com

-----Original Message-----
From: owner-writelog@contesting.com
[mailto:owner-writelog@contesting.com]On Behalf Of erik.hyllander
Sent: Wednesday, April 18, 2001 6:22 PM
To: writelog@contesting.com
Subject: [WriteLog] Packet in WL



Hello WL-gang,
I'm new to WL and have a problem with the packet grab window.
I have WL v 10.32 on a pc with W98SE. Packet is interlinked via Kantronics
KAM v 8.0. If I have the packet window on the screen I can follow the
transmissions from the local DX-cluster. But nothing shows in the packet
grab window. I have put
'DefaultTimeoutSeconds=1200' in the pktspotbar-section of the ini-file to no
use.

FYI, I have also DX4WIN as my overall logging program and there the spots
enter the corresponding window so I can click on them and control the radio.

So what am I missing?
Any help will be appreciated.
73 Erik
--------------------------------
Erik Hyllander, SM0LZT
packet: SM0LZT@SK0MK
E-mail: sm0lzt@svessa.se


--
WWW:                      http://www.writelog.com/
Submissions:              writelog@contesting.com
Administrative requests:  writelog-REQUEST@contesting.com
Problems:                 owner-writelog@contesting.com


--
WWW:                      http://www.writelog.com/
Submissions:              writelog@contesting.com
Administrative requests:  writelog-REQUEST@contesting.com
Problems:                 owner-writelog@contesting.com


<Prev in Thread] Current Thread [Next in Thread>