I received a reply back from Fabrizio on the problem I was having
getting the WriteLog packet screen to work on a networked PC
while using DXTelnet to generate the packetcluster spots.
It appears Fab did not test this feature himself. He has, however,
been working on a different approach that has yet to be released
to the public.
Since it appears I am the only one trying to do this, I get to be the
lucky one and beta test his new approach. I have received the 3
files necessary and will start setting it up today since it's raining.
YES!!! It hasn't rained in over 5 weeks. I haven't washed my truck in
six months. So yesterday I told my girlfriend that if I washed my
truck it would rain and I washed my truck. This morning it raining cats
and dogs and there are poodles all over the place! hi
I'll publish the results of the network testing here.
73, Don AA5AU
----- Original Message -----
From: Don Hill <aa5au@msn.com>
To: WriteLog Reflector <Writelog@contesting.com>
Cc: IK4VYX Fabrizio <rac2610@racine.ra.it>
Sent: Saturday, June 03, 2000 9:54 AM
Subject: [WriteLog] DXTelnet with WriteLog Networked
>
> OK, I finally got DXTelnet to work with WriteLog on the PC that
> has DXTelnet and the Internet connection. Many thanks to Jim
> and Pawel and others. I'm not sure what I did differently other
> than when I started WriteLog, I opened the packet spots window
> first, then opened up the packet window. Anyway it works, tks guys.
>
> Now I have to get it to work on a networked PC that I use with
> WriteLog on my main radio. I use WriteLog everyday and network
> the two computers every day so I have all that working and am
> familiar with it.
>
> I can't get the packet spots to go to that computer. I have a feeling
> I need to set up the DDE Links part of DXTelnet, but I'm not sure
> how to do this. I have MSVBVM50.DLL in the \windows\system\
> subdirectory on both PC's and they appear to be the same file
> since they have the same number of bytes.
>
> It didn't work right off the bat, so I made some changes and it still
> doesn't work. I have gone to regedit on the networked PC and changed
> WLOGPKT to "DXT2WL". (I had to do this on the PC with DXTelnet
> to get it to work initially with WriteLog). Since DXT2WL is not on the
> networked PC, how does it know where DXT2WL is located?
>
> I also added the same lines to WriteLog.ini on the networked PC that I
> did on the PC with DXTelnet to get it to work initially:
> [OBJECTS]
> pktObject=DXT2WL.clsWIPacket
>
> I think the key to all this is in the following text from DXT2WL.TXT:
>
> "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."
>
> This is where I am hung up. How do I choose the network link as the
> source?
>
> Any help?
>
> This looks like it will be a VERY valuable tool once I get it all working.
>
> Thanks,
> Don, AA5AU
>
>
>
>
>
>
> --
> 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
|