Jim,
My "dxt2wl.exe" is located inside DXTelnet folder as
C:\DXTelnet\DXT2WL\dxt2wl.exe.
I have not tried to put the "exe" file out of DXTelnet folder, but think it
should work.
You should be careful to put "dxt2wl.exe" the same folder as F9 key tells...
If you have to change the link in DXTelnet, you can do it with new location.
I do not have problems to link DXTelnet to WriteLog and DX4WIN. Of course
each time I change the program (DX4WIN and WL) I have to change the setting
of DX-Hunter Installation Patch in configuration of DXTelnet.
And remember, that the spots will be available for WL or DX4WIN if you open
the small programs "dxt4win.exe" or "dxt2wl.exe" before start using the
general logging program and its DX Spot Window.
Best 73's
Pawel, SP7NMW / SN7N
----- Original Message -----
From: "Jim FitzSimons" <cherry@neta.com>
To: "Writelog Reflector" <Writelog@contesting.com>
Sent: Thursday, June 01, 2000 2:01 PM
Subject: Re: [WriteLog] DXTelnet with WriteLog?
>
> Pawel, F9 gives me C:\DXTELNET\DXT2WL\
> That is the original location of the program.
> Is that a good location to use?
> You said C:\DXT2WL\
> I tried the general DX log and it does not seem to work.
> Is there some test I can do to check it out?
> The standard telnet works OK but DxTelnet give more
> freedom.
> I only tested it using port 80. I like that one better.
> Regards, Jim FitzSimons W7ANF
>
> -----Original Message-----
> From: Pawel SP7NMW <sp7nmw@bonus.com.pl>
> To: Writelog Reflector <Writelog@contesting.com>; Don Hill <aa5au@msn.com>
To: <writelog@contesting.com>
> Date: Thursday, June 01, 2000 5:31 AM
> Subject: Re: [WriteLog] DXTelnet with WriteLog?
>
>
> >
> >Hello WL Users and Don,
> >
> >It was me.
> >I use DXTelnet and WriteLog. They work perfectly together. To work with
> >DXTelnet you have to start this program, connect with DX Cluster, open
> >another small program called DXT2WL and next open Packet Window of
> WriteLog.
> >
> >In DXTelnet you can set the filters you need, bands you want to turn off
> >from the spot.
> >To allow receive spots in WriteLog's Packet Window you have to do
following
> >steps:
> >(these information are from the DXTelnet help file):
> >
> >1) Create a new folder named DXT2WL and place DXT2WL.EXE into it
> >
> >2) Run DXT2WL.EXE once so that it registers itself in the system
register,
> >nothing will happen at this step
> >
> >3) If you are linking WriteLog and DXTelnet on two separate networked PCs
> >you will have to run DXT2WL on DXTelnet side and the standard WriteLog
> >packet window on the other then choose the network link as source.Before
> >doing this run C:\WINDOWS\REGEDIT and change the following registry key:
>
>HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NetDDE\DDEShares\WLOGPKT%\Application
> =
> >"DXT2WL" instead of "wlogpkt" .
> >
> >>>>!!!!!! ATTENTION: in my registry it was WLOGPKT instead of WLOGPKT%
> >(Pawel SP7NMW)
> >
> >
> >DXTelnet side:
> >
> >4) Start DXTelnet, go to "Configuration" menu then, "Links" and in the
> "Link
> >to DXHUNTER" section set the "DXHUNTER installation path" string to:
> >C:\DXT2WL\
> >Check the "Enable Link" check box, press "Save", quit and restart
DXTelnet
> >connecting to any site, for instance connect to CQDX IRC.
> >
> >--------
> >
> >WriteLog side
> >
> >5) Edit the C:\WINDOWS\WRITELOG.INI file and add the following couple of
> >lines:
> >
> >[OBJECTS]
> >pktObject=DXT2WL.clsWlPacket
> >
> >This opertaion must not be done if point #3 is true (that is when linking
> >DXTelnet and WriteLog on 2 separate networked PCs).
> >
> >>>>!!!!ATTENTION: I have stand-alone computer, but have to put this line
> >into INI file due to my Windows 95 configuration (Pawel, SP7NMW)
> >
> >6) Start WriteLog and from the "View" menu choose "Packet Window"
> >
> >7) The next DXTelnet spots should appear in the packet window and thus
sent
> >to WriteLog; if in WL you choose "View" then "Packet Spots", spots should
> >start flowing.
> >
> >8) To send text to the DXTelnet session from WriteLog choose "Entry" then
> >"Send Packet Spot"
> >
> >Note:
> >DXT2WL.EXE requires that the MSVBVM50.DLL library file is present in your
> >:\WINDOWS\SYSTEM directory If you get a WriteLog error message saying
> "Could
> >not create OLE object" this might be due to a missing MSVBVM50.DLL
> >
> >If the packet window appears but spots are not exchanged, Press F9 on the
> >packet window: you will see the path where DXT2WL was registered by the
> >system; if it does not match with the path that you've set above in step
3,
> >you will have to repeat step 3 with the new path you got with F9.
> >
> >...............................
> >
> >I hope, this help you to get spots from DX Telnet. If you need more
> >information, feel free to contact me.
> >
> >Best 73's
> >Pawel, SP7NMW / SN7N
> >
> >
> >----- Original Message -----
> >From: "Don Hill" <aa5au@msn.com>
> >To: "WriteLog Reflector" <Writelog@contesting.com>
> >Sent: Thursday, June 01, 2000 3:15 AM
> >Subject: [WriteLog] DXTelnet with WriteLog?
> >
> >
> >>
> >> I must have missed something, but I thought I saw someone
> >> mention they are using DXTelnet in conjunction with WriteLog.
> >>
> >> If so, how do you do it? Please explain to the reflector if possible.
> >> Perhaps others can learn as well. Or perhaps I misunderstood
> >> what I read.
> >>
> >> Thanks,
> >> Don AA5AU
> >>
> >>
> >>
> >>
> >>
> >> --
> >> WWW: http://www.contesting.com/writelog
> >> Submissions: writelog@contesting.com
> >> Administrative requests: writelog-REQUEST@contesting.com
> >> Problems: owner-writelog@contesting.com
> >>
> >
> >
> >--
> >WWW: http://www.contesting.com/writelog
> >Submissions: writelog@contesting.com
> >Administrative requests: writelog-REQUEST@contesting.com
> >Problems: owner-writelog@contesting.com
> >
> >
>
>
> --
> WWW: http://www.contesting.com/writelog
> Submissions: writelog@contesting.com
> Administrative requests: writelog-REQUEST@contesting.com
> Problems: owner-writelog@contesting.com
>
--
WWW: http://www.contesting.com/writelog
Submissions: writelog@contesting.com
Administrative requests: writelog-REQUEST@contesting.com
Problems: owner-writelog@contesting.com
|