As I start DX4WIN V6.02, I occasionally get the message:
An exception Occured! Access violation at address 0046B64F in module =
'DX4WIN.EXE'. Read at address .
Pressing OK on the message proceeds to take me into DX4WIN demo mode. =
Coming out of the application and starting it again
If your cluster is using CLX software, use the command
SET/ALIVE. The cluster (I'm told) will then do the pinging to you. Seems to
work!
73, Duke
I have the same problems.. With my telnet cluster of first preference. I
can't stay connected beyond a couple of hours. I asked this same question
In DX4WIN 5.x, the PSK SettingsTx screen allowed you to select the =
PSK keying com port from 1-8, and either RTS or DTR as the keyed line. =
The 5.x PSK selection was completely independent of the keyed line for =
CW. In DX4WIN 6.02, it seems that your only choices for PSK keying are =
either
Yes, Larry, I share this dilemma with you and any others that work CW and
PSK31 modes and use different ports for control of CW keying and PSK31 PTT.
I brought this problem to the attention of Paul just days after the release
of Ver 6...
It is a real pain now and was so simple in Ver. 5.02/5.03
Mel,
Thanks for the note - and I agree that, theoretically, you should be able to
key the rig from the same port that you use for CW (at least that's what the
config menu says ;-). I am only using 1 rig here, so my work-around #1
_should_ work.
However, in DX4WIN 6.02, the software has a bug. If
I am sure glad to see this subject being discussed. I felt why if it isn't
broke fix it but then was kind of told I was an idiot for thinking this
wasn't a better way.
I still feel IF IT AIN'T BROKE DON'T FIX IT. and it wasn't broke.
But thankfully there are other PSK-31 program.
Rod WC7N
Rod,
That old adage if it ain't broke, don't fix it is covered by a corollary
of Murphy's law that hits programmers especially hard. I believe the main
law states something to the effect of In order for something to become
clean, something else must become dirty. The programmers corollary is In
You haven't got it hooked up correctly...
On the LPT port...
Pin 1 keys CW
Pin 16 keys PTT
It sounds like you are using pin 1 for PTT
I don't know anything about Rigblasters...
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Roger Borowski
Sent: March
Yes it does... I'm doing it here... Hooked it up to LPT1 pin 1 and 16
just to try it out... Usually use a COM port...
Who says there is a bug?
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Larry Gauthier
Sent: March 16, 2003 4:16 PM
To: [EMAIL
I don't see it's broken now... I've tried it here and it works fine on
the COM port... It works fine on the LPT port...
The only issue that I've seen raised is if one is using a different
radio for digital modes... Otherwise why would you need more than one
port to handle PTT. What am I missing?
Now the world knows why I am an idiot. I don't care, it worked fine before
so why fix what ain't broke.
Enough on the subject.
Rod WC7N
- Original Message -
From: Mel Martin (VE2DC) [EMAIL PROTECTED]
To: 'WC7N' [EMAIL PROTECTED]; 'DX4WIN Group' dx4win@mailman.qth.net
Sent: Sunday,
I don't use LPT port as early on I found that CW doesn't work as well as
with COM port.
I use COM 3 for rig control and also CW keying, COM 5 is dedicated for PTT
w/PSK31
RigBlaster is commonplace with PSK31 and requires use of a separate COM port
for PTT
Rig control and CW keying work well on the
Duke - Can you provide a list of clusters to us that use the CLX software. The
nodes that I usually connect to do not recognize this command.
Greg
K9IG
Duke Knief W4DK wrote:
If your cluster is using CLX software, use the command
SET/ALIVE. The cluster (I'm told) will then do the pinging to
13 matches
Mail list logo
