[Dx4win] DX4WIN with DXTELNET

Stu [email protected]
Thu, 19 Dec 2002 06:31:10 -0500


Can not get into the local packet repeaters comfortably so got 
DXTELNET.  Followed directions for setting up which require running 
DXTELNET,  DXT4WIN and DX4WIN.  I set up DXTELNET IAW the included help 
file below,  nothing to do for DXT4WIN and in DX4WIN followed directions 
which had me. DXTELNET runs fine, I get real nice info form any of the 
clusters, but I can not get the two to talk.  I can not get DX4WIN to 
recognize DXTELNET.   The two work independently , but if I click on a call 
in TELNET, it is not transferred to DX4WIN

The program which provides an interface between DX4WIN and DXTelnet is 
named DXT4WIN.EXE and is located into C:\DXTELNET\DXT4WIN\

Step by step:

1) Start DXTelnet, go to "Configuration" menu then, "Links" and in the 
"Link to DXHUNTER" section set the "DXHUNTER installation path" string to: 
C:\DXTELNET\DXT4WIN\ Check the "Enable Link" check box, press "Save", quit 
and restart DXTelnet connecting to any site,
for instance connect to CQDX-IRC.

2) Run C:\DXTELNET\DXT4WIN\DXT4WIN.EXE

3) Nothing special must be done at DX4WIN side.If DXTelnet is your unique 
spot source, set the packet port to "MSG".The link between DXTelnet and 
DX4WIN can nowbe two way (before it was ione way: DXT > DX4WIN): in DX4WIN, 
set the "message handshake" string to:
ThunderRT5Form|DXTelnet<>DX4WIN You can also use any other port value and 
DXTelnet spots will still be analysed by DX4WIN together
with the other spots coming from the port you've set.

Note:
DXT4WIN.EXE requires that the MSVBVM50.DLL library file is present in your 
C:\WINDOWS\SYSTEM directory If you get an error message after running 
DXT4WIN.EXE this might be due to a missing MSVBVM50.DLL