Made a second call to Ten-Tec and they feel it is not a problem with the radio but with the logging program. Whenever I tab from different portions of the qso window entering the logging data such as callsign, rst, etc there is hesitation and many times this lag effect will last for a couple of seconds. Many times I will be typing the callsign of the station and nothing appears and it will seem to be locked up then everything will appear. Ten-Tec asks does the DX4WIN logging program have the Orion II as a specific radio in the preferences /radio tab and the answer is no and they say that is the problem. The tab only says Orion and data is for the 565 not the Orion 566. I spoke to Paul Clinton, the service manager for Ten-Tec and he is going to review this scenario with his people but in the meantime has anyone else encountered this with their Orion II and DX4WIN?
john-n4dsp ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ "I would rather have a German division in front of me than a French one behind me." --General George S. Patton From [EMAIL PROTECTED] Wed Oct 25 10:59:24 2006 From: [EMAIL PROTECTED] (Jim Reisert AD1C) Date: Wed Oct 25 11:05:53 2006 Subject: [Dx4win] Orion II with dx4win In-Reply-To: <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> --- n4dsp <[EMAIL PROTECTED]> wrote: > Made a second call to Ten-Tec and they feel it is not a problem with the > radio but with the logging program. Whenever I tab from different portions of > the qso window entering the logging data such as callsign, rst, etc there is > hesitation and many times this lag effect will last for a couple of seconds. It's not your radio! I never had this problem in DX4WIN, until I recently (within last couple of months) had to install Windows XP from scratch. Now I have the problem occasionally. My CPU usage is near 0%. I have an ICOM, not Orion radio. I'm using the microHAM microKeyer as my radio interface. I have McAfee AntiVirus running, but that's about it. As I said, the problem just developed recently. I wonder if one of Microsoft's recent updates cause it? 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] Wed Oct 25 11:16:59 2006 From: [EMAIL PROTECTED] (wo2n) Date: Wed Oct 25 11:23:33 2006 Subject: [Dx4win] CW Announce? References: <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> Thanks for the replies I have ver 5.03 the voice announce works via external speakers, BUT the CW announce only works via internal computer speaker. From the replies, I'm assuming an wav file was written for the CW announce via external speaker??? Thank you, 73 de Bernie/WO2N.> ----- Original Message ----- From: "wo2n" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Tuesday, October 24, 2006 7:07 PM Subject: [Dx4win] CW Announce? > Hi, > With the latest versions, has the CW Announce (DX Spotting) able come thru > the stereo speakers yet? > You see I like to be able to control the volume (crank it up) so I can > hear the spots while in another room. > Thank you 73, Bernie/WO2N.> > _______________________________________________ > Dx4win mailing list > [email protected] > http://mailman.qth.net/mailman/listinfo/dx4win
