I started using this program a few days ago. Now I can establish a single DX cluster connection on the ham computer, and share that connection among applications (DX4WIN/Writelog) and other computers in the house (so I can monitor spots remotely). I recommend it.
You MUST train yourself NOT to use BYE to exit the cluster from DX4WIN. This is unnecessary, and if you do it from a remote computer, you'll have to go to the computer running VE7CC software and connect again. For me, this is a trip down and up the basement stairs. 73 - Jim AD1C ===== Jim Reisert AD1C, 7 Charlemont Court, North Chelmsford, MA 01863 USA +978-251-9933, <[EMAIL PROTECTED]>, http://www.ad1c.us From [EMAIL PROTECTED] Thu Jan 20 14:15:18 2005 From: [EMAIL PROTECTED] (Joe - =?iso-8859-1?Q?WD=D8M?=) Date: Thu Jan 20 14:21:01 2005 Subject: [Dx4win] Connecting DX4WIN to the VE7CC cluster program In-Reply-To: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> I've been using VE7CC's software with DX4WIN for some time now, and it works VERY well. 73, Joe WD?M At 12:08 PM 1/20/2005, Paul B. Peters, VE7AVV wrote: >In this past week I responded to a few queries regarding DX4WIN not having >provision or settings within the program for enabling any type of >auto-reconnect to a cluster once you've been dropped. The very slick >workaround is to use the VE7CC program: http://www.ve7cc.net/ in tandem with >DX4WIN. This free program has a host of tremendous features not found in any >other cluster program. > >In off-line emails with a few of you, I provided information about the >settings for inter-connecting between VE7CC and DX4WIN. Here is a link to >screen shots showing the three key screens that you'll use in this process. >http://www.bcdxc.org/ve7cc/logging.htm > >Remember to save your changes once you've updated the dx4win.tcp file. > >73 de Paul, VE7AVV -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 265.6.13 - Release Date: 1/16/2005
