[Dx4win] PSK31 config change in DX4WIN 6.02?
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 same COM port, can't use LPT port for Rig control. Also, I don't care to re-engineer what use to work well and still works well with Writelog and other programs. That would create more problems when using other software. As I said before, It wasn't broke before and now it is. Ver 5.02/03 did this all fine by allowing a separate port selection. If you don't use a RigBlaster, or separate COM ports for CW and PTT for PSK31 that's what you are missing! If what you are doing works for you, thats great. Many others want it as it was before V.6 - Original Message - From: "Mel Martin (VE2DC)" <[EMAIL PROTECTED]> To: "'Roger Borowski'" <[EMAIL PROTECTED]>; "'Larry Gauthier'" <[EMAIL PROTECTED]> Cc: "'DX4Win Reflector'" Sent: Sunday, March 16, 2003 8:13 PM Subject: RE: [Dx4win] PSK31 config change in DX4WIN 6.02? > 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 16, 2003 4:07 PM > To: [EMAIL PROTECTED]; 'Larry Gauthier' > Cc: 'DX4Win Reflector' > Subject: Re: [Dx4win] PSK31 config change in DX4WIN 6.02? > > > That doesn't work either, Mel. The PTT relay in the RigBlaster then keys > with every dit and dah or the radio PTT keys with every dit and dah in > the CW mode. It would likely work if you were to disconnect and > re-connect the PTT line for PSK31 but why not just allow the individual > software control for individual selection of ports for CW and PSK31 PTT > as it was in Ver 5.02/03 That wasn't broke and didn't need fixing! Now > its broke! -=Rog-K9RB=- > > - Original Message - > From: "Mel Martin (VE2DC)" <[EMAIL PROTECTED]> > To: "'Larry Gauthier'" <[EMAIL PROTECTED]> > Cc: "'DX4Win Reflector'" > Sent: Sunday, March 16, 2003 3:24 PM > Subject: RE: [Dx4win] PSK31 config change in DX4WIN 6.02? > > > > Hi Larry... You CAN use the LPT port to key both CW and PSK31/CW > > PTT... I would think this would only be a problem if you are using a > > different radio for PSK31... So work-around 1 should work... Obviously > > > workaround 2 won't unless you define a 2nd COM PTT interface for mmty > > and hook them up in parallel... > > > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] > > On Behalf Of Larry Gauthier > > Sent: March 16, 2003 1:41 PM > > To: dx4win@mailman.qth.net > > Subject: [Dx4win] PSK31 config change in DX4WIN 6.02? > > > > > > In DX4WIN 5.x, the PSK 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 the CW interface or VOX. What happened to the > > ability to independently choose a com port? > > > > In my 5.03 configuration, I had been using the LPT port for CW keying, > > > and the com port for keying in either PSK31 or MMTTY. As long as I did > > > not attempt to simultaneously open the PSK window and run MMTTY, this > > arrangement worked fine. > > > > Under 6.02, I attempted to work-arounds... neither which seem to work: > > > First work-around: telling DX4WIN to use the LPT CW interface for PSK > > keying. It doesn't work. PSK does not key via the LPT port... although > > > CW still works fine. > > > > Second work-around: Re-configure for CW keying via the com port. This > > allows CW and PSK to work properly, but prevents MMTTY from running. > > (DX4WIN grabs control of the CW port upon launch, and if you try to > > subsequently launch MMTTY you get a port conflict error.) > > > > > > Has anyone else encountered these problems? Does anyone have a > > suggestion on how to solve them? > > > > -larry > > K8UT > > > > --- StripMime Report -- processed MIME parts --- multipart/alternative > > text/plain (text body -- kept) > > text/html > > The reason this message is shown is because the post was in HTML or > > had an attachment. Attachments are not allowed. To learn how to post > > > in Plain-Text go to: http://www.expita.com/nomime.html --- > > ___ > > Dx4win mailing list > > Dx4win@mailman.qth.net http://mailman.qth.net/mailman/listinfo/dx4win > > > > ___ > > Dx4win mailing list > > Dx4win@mailman.qth.net http://mailman.qth.net/mailman/listinfo/dx4win > > ___ > Dx4win mailing list > Dx4win@mailman.qth.net http://mailman.qt
[Dx4win] PSK change is DX4WIN 6.02
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? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of WC7N Sent: March 16, 2003 4:47 PM To: DX4WIN Group Subject: [Dx4win] PSK change is DX4WIN 6.02 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 ___ Dx4win mailing list Dx4win@mailman.qth.net http://mailman.qth.net/mailman/listinfo/dx4win
[Dx4win] PSK31 config change in DX4WIN 6.02?
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 PROTECTED] Cc: 'DX4Win Reflector' Subject: Re: [Dx4win] PSK31 config change in DX4WIN 6.02? 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 you configure to key the rig in CW from a COM port, PSK is also keyed from the same COM port. If you configure to key the rig in CW from the LPT port, PSK keying via the same LPT port does not work. -larry K8UT - Original Message - From: "Mel Martin (VE2DC)" <[EMAIL PROTECTED]> To: "'Larry Gauthier'" <[EMAIL PROTECTED]> Cc: "'DX4Win Reflector'" Sent: Sunday, March 16, 2003 3:24 PM Subject: RE: [Dx4win] PSK31 config change in DX4WIN 6.02? > Hi Larry... You CAN use the LPT port to key both CW and PSK31/CW > PTT... I would think this would only be a problem if you are using a > different radio for PSK31... So work-around 1 should work... Obviously > workaround 2 won't unless you define a 2nd COM PTT interface for mmty > and hook them up in parallel... > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > On Behalf Of Larry Gauthier > Sent: March 16, 2003 1:41 PM > To: dx4win@mailman.qth.net > Subject: [Dx4win] PSK31 config change in DX4WIN 6.02? > > > In DX4WIN 5.x, the PSK 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 the CW interface or VOX. What happened to the > ability to independently choose a com port? > > In my 5.03 configuration, I had been using the LPT port for CW keying, > and the com port for keying in either PSK31 or MMTTY. As long as I did > not attempt to simultaneously open the PSK window and run MMTTY, this > arrangement worked fine. > > Under 6.02, I attempted to work-arounds... neither which seem to work: > First work-around: telling DX4WIN to use the LPT CW interface for PSK > keying. It doesn't work. PSK does not key via the LPT port... although > CW still works fine. > > Second work-around: Re-configure for CW keying via the com port. This > allows CW and PSK to work properly, but prevents MMTTY from running. > (DX4WIN grabs control of the CW port upon launch, and if you try to > subsequently launch MMTTY you get a port conflict error.) > > > Has anyone else encountered these problems? Does anyone have a > suggestion on how to solve them? > > -larry > K8UT > > --- StripMime Report -- processed MIME parts --- multipart/alternative > text/plain (text body -- kept) > text/html > The reason this message is shown is because the post was in HTML or > had an attachment. Attachments are not allowed. To learn how to post > in Plain-Text go to: http://www.expita.com/nomime.html --- > ___ > Dx4win mailing list > Dx4win@mailman.qth.net http://mailman.qth.net/mailman/listinfo/dx4win > ___ Dx4win mailing list Dx4win@mailman.qth.net http://mailman.qth.net/mailman/listinfo/dx4win
[Dx4win] PSK31 config change in DX4WIN 6.02?
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 16, 2003 4:07 PM To: [EMAIL PROTECTED]; 'Larry Gauthier' Cc: 'DX4Win Reflector' Subject: Re: [Dx4win] PSK31 config change in DX4WIN 6.02? That doesn't work either, Mel. The PTT relay in the RigBlaster then keys with every dit and dah or the radio PTT keys with every dit and dah in the CW mode. It would likely work if you were to disconnect and re-connect the PTT line for PSK31 but why not just allow the individual software control for individual selection of ports for CW and PSK31 PTT as it was in Ver 5.02/03 That wasn't broke and didn't need fixing! Now its broke! -=Rog-K9RB=- - Original Message - From: "Mel Martin (VE2DC)" <[EMAIL PROTECTED]> To: "'Larry Gauthier'" <[EMAIL PROTECTED]> Cc: "'DX4Win Reflector'" Sent: Sunday, March 16, 2003 3:24 PM Subject: RE: [Dx4win] PSK31 config change in DX4WIN 6.02? > Hi Larry... You CAN use the LPT port to key both CW and PSK31/CW > PTT... I would think this would only be a problem if you are using a > different radio for PSK31... So work-around 1 should work... Obviously > workaround 2 won't unless you define a 2nd COM PTT interface for mmty > and hook them up in parallel... > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > On Behalf Of Larry Gauthier > Sent: March 16, 2003 1:41 PM > To: dx4win@mailman.qth.net > Subject: [Dx4win] PSK31 config change in DX4WIN 6.02? > > > In DX4WIN 5.x, the PSK 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 the CW interface or VOX. What happened to the > ability to independently choose a com port? > > In my 5.03 configuration, I had been using the LPT port for CW keying, > and the com port for keying in either PSK31 or MMTTY. As long as I did > not attempt to simultaneously open the PSK window and run MMTTY, this > arrangement worked fine. > > Under 6.02, I attempted to work-arounds... neither which seem to work: > First work-around: telling DX4WIN to use the LPT CW interface for PSK > keying. It doesn't work. PSK does not key via the LPT port... although > CW still works fine. > > Second work-around: Re-configure for CW keying via the com port. This > allows CW and PSK to work properly, but prevents MMTTY from running. > (DX4WIN grabs control of the CW port upon launch, and if you try to > subsequently launch MMTTY you get a port conflict error.) > > > Has anyone else encountered these problems? Does anyone have a > suggestion on how to solve them? > > -larry > K8UT > > --- StripMime Report -- processed MIME parts --- multipart/alternative > text/plain (text body -- kept) > text/html > The reason this message is shown is because the post was in HTML or > had an attachment. Attachments are not allowed. To learn how to post > in Plain-Text go to: http://www.expita.com/nomime.html --- > ___ > Dx4win mailing list > Dx4win@mailman.qth.net http://mailman.qth.net/mailman/listinfo/dx4win > > ___ > Dx4win mailing list > Dx4win@mailman.qth.net http://mailman.qth.net/mailman/listinfo/dx4win ___ Dx4win mailing list Dx4win@mailman.qth.net http://mailman.qth.net/mailman/listinfo/dx4win
[Dx4win] PSK change is DX4WIN 6.02
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'" Sent: Sunday, March 16, 2003 5:19 PM Subject: RE: [Dx4win] PSK change is DX4WIN 6.02 > 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? > > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > On Behalf Of WC7N > Sent: March 16, 2003 4:47 PM > To: DX4WIN Group > Subject: [Dx4win] PSK change is DX4WIN 6.02 > > > 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 > > ___ > Dx4win mailing list > Dx4win@mailman.qth.net http://mailman.qth.net/mailman/listinfo/dx4win > > ___ > Dx4win mailing list > Dx4win@mailman.qth.net > http://mailman.qth.net/mailman/listinfo/dx4win
[Dx4win] PSK change is DX4WIN 6.02
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 order for one bug to be fixed, a minimum of two unrelated bugs must be introduced." Mike / W8DN - Original Message - From: "WC7N" <[EMAIL PROTECTED]> To: "DX4WIN Group" Sent: Sunday, March 16, 2003 4:46 PM Subject: [Dx4win] PSK change is DX4WIN 6.02 > 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 > > ___ > Dx4win mailing list > Dx4win@mailman.qth.net > http://mailman.qth.net/mailman/listinfo/dx4win >
[Dx4win] PSK31 config change in DX4WIN 6.02?
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 you configure to key the rig in CW from a COM port, PSK is also keyed from the same COM port. If you configure to key the rig in CW from the LPT port, PSK keying via the same LPT port does not work. -larry K8UT - Original Message - From: "Mel Martin (VE2DC)" <[EMAIL PROTECTED]> To: "'Larry Gauthier'" <[EMAIL PROTECTED]> Cc: "'DX4Win Reflector'" Sent: Sunday, March 16, 2003 3:24 PM Subject: RE: [Dx4win] PSK31 config change in DX4WIN 6.02? > Hi Larry... You CAN use the LPT port to key both CW and PSK31/CW PTT... > I would think this would only be a problem if you are using a different > radio for PSK31... So work-around 1 should work... Obviously workaround > 2 won't unless you define a 2nd COM PTT interface for mmty and hook them > up in parallel... > > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > On Behalf Of Larry Gauthier > Sent: March 16, 2003 1:41 PM > To: dx4win@mailman.qth.net > Subject: [Dx4win] PSK31 config change in DX4WIN 6.02? > > > In DX4WIN 5.x, the PSK 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 the CW interface or VOX. What happened to the ability to > independently choose a com port? > > In my 5.03 configuration, I had been using the LPT port for CW keying, > and the com port for keying in either PSK31 or MMTTY. As long as I did > not attempt to simultaneously open the PSK window and run MMTTY, this > arrangement worked fine. > > Under 6.02, I attempted to work-arounds... neither which seem to work: > First work-around: telling DX4WIN to use the LPT CW interface for PSK > keying. It doesn't work. PSK does not key via the LPT port... although > CW still works fine. > > Second work-around: Re-configure for CW keying via the com port. This > allows CW and PSK to work properly, but prevents MMTTY from running. > (DX4WIN grabs control of the CW port upon launch, and if you try to > subsequently launch MMTTY you get a port conflict error.) > > > Has anyone else encountered these problems? Does anyone have a > suggestion on how to solve them? > > -larry > K8UT > > --- StripMime Report -- processed MIME parts --- multipart/alternative > text/plain (text body -- kept) > text/html > The reason this message is shown is because the post was in HTML or had > an attachment. Attachments are not allowed. To learn how to post in > Plain-Text go to: http://www.expita.com/nomime.html --- > ___ > Dx4win mailing list > Dx4win@mailman.qth.net http://mailman.qth.net/mailman/listinfo/dx4win >
[Dx4win] PSK31 config change in DX4WIN 6.02?
That doesn't work either, Mel. The PTT relay in the RigBlaster then keys with every dit and dah or the radio PTT keys with every dit and dah in the CW mode. It would likely work if you were to disconnect and re-connect the PTT line for PSK31 but why not just allow the individual software control for individual selection of ports for CW and PSK31 PTT as it was in Ver 5.02/03 That wasn't broke and didn't need fixing! Now its broke! -=Rog-K9RB=- - Original Message - From: "Mel Martin (VE2DC)" <[EMAIL PROTECTED]> To: "'Larry Gauthier'" <[EMAIL PROTECTED]> Cc: "'DX4Win Reflector'" Sent: Sunday, March 16, 2003 3:24 PM Subject: RE: [Dx4win] PSK31 config change in DX4WIN 6.02? > Hi Larry... You CAN use the LPT port to key both CW and PSK31/CW PTT... > I would think this would only be a problem if you are using a different > radio for PSK31... So work-around 1 should work... Obviously workaround > 2 won't unless you define a 2nd COM PTT interface for mmty and hook them > up in parallel... > > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > On Behalf Of Larry Gauthier > Sent: March 16, 2003 1:41 PM > To: dx4win@mailman.qth.net > Subject: [Dx4win] PSK31 config change in DX4WIN 6.02? > > > In DX4WIN 5.x, the PSK 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 the CW interface or VOX. What happened to the ability to > independently choose a com port? > > In my 5.03 configuration, I had been using the LPT port for CW keying, > and the com port for keying in either PSK31 or MMTTY. As long as I did > not attempt to simultaneously open the PSK window and run MMTTY, this > arrangement worked fine. > > Under 6.02, I attempted to work-arounds... neither which seem to work: > First work-around: telling DX4WIN to use the LPT CW interface for PSK > keying. It doesn't work. PSK does not key via the LPT port... although > CW still works fine. > > Second work-around: Re-configure for CW keying via the com port. This > allows CW and PSK to work properly, but prevents MMTTY from running. > (DX4WIN grabs control of the CW port upon launch, and if you try to > subsequently launch MMTTY you get a port conflict error.) > > > Has anyone else encountered these problems? Does anyone have a > suggestion on how to solve them? > > -larry > K8UT > > --- StripMime Report -- processed MIME parts --- multipart/alternative > text/plain (text body -- kept) > text/html > The reason this message is shown is because the post was in HTML or had > an attachment. Attachments are not allowed. To learn how to post in > Plain-Text go to: http://www.expita.com/nomime.html --- > ___ > Dx4win mailing list > Dx4win@mailman.qth.net http://mailman.qth.net/mailman/listinfo/dx4win > > ___ > Dx4win mailing list > Dx4win@mailman.qth.net > http://mailman.qth.net/mailman/listinfo/dx4win
[Dx4win] PSK31 config change in DX4WIN 6.02?
Hi Larry... You CAN use the LPT port to key both CW and PSK31/CW PTT... I would think this would only be a problem if you are using a different radio for PSK31... So work-around 1 should work... Obviously workaround 2 won't unless you define a 2nd COM PTT interface for mmty and hook them up in parallel... -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Larry Gauthier Sent: March 16, 2003 1:41 PM To: dx4win@mailman.qth.net Subject: [Dx4win] PSK31 config change in DX4WIN 6.02? In DX4WIN 5.x, the PSK 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 the CW interface or VOX. What happened to the ability to independently choose a com port? In my 5.03 configuration, I had been using the LPT port for CW keying, and the com port for keying in either PSK31 or MMTTY. As long as I did not attempt to simultaneously open the PSK window and run MMTTY, this arrangement worked fine. Under 6.02, I attempted to work-arounds... neither which seem to work: First work-around: telling DX4WIN to use the LPT CW interface for PSK keying. It doesn't work. PSK does not key via the LPT port... although CW still works fine. Second work-around: Re-configure for CW keying via the com port. This allows CW and PSK to work properly, but prevents MMTTY from running. (DX4WIN grabs control of the CW port upon launch, and if you try to subsequently launch MMTTY you get a port conflict error.) Has anyone else encountered these problems? Does anyone have a suggestion on how to solve them? -larry K8UT --- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html The reason this message is shown is because the post was in HTML or had an attachment. Attachments are not allowed. To learn how to post in Plain-Text go to: http://www.expita.com/nomime.html --- ___ Dx4win mailing list Dx4win@mailman.qth.net http://mailman.qth.net/mailman/listinfo/dx4win
[Dx4win] PSK31 config change in DX4WIN 6.02?
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 and makes PSK31 changeover so difficult that I've gone back to using Ver. 5.02 here. Paul told me that he would work on the problem and I anticipate that fix in the next maintenance release, hopefully soon. Ver. 6.xx would then be a real nice enhancement for us multimode CW/PSK users. 73, -=Rog-K9RB=- - Original Message - From: "Larry Gauthier" <[EMAIL PROTECTED]> To: Sent: Sunday, March 16, 2003 1:41 PM Subject: [Dx4win] PSK31 config change in DX4WIN 6.02? In DX4WIN 5.x, the PSK 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 the CW interface or VOX. What happened to the ability to independently choose a com port? In my 5.03 configuration, I had been using the LPT port for CW keying, and the com port for keying in either PSK31 or MMTTY. As long as I did not attempt to simultaneously open the PSK window and run MMTTY, this arrangement worked fine. Under 6.02, I attempted to work-arounds... neither which seem to work: First work-around: telling DX4WIN to use the LPT CW interface for PSK keying. It doesn't work. PSK does not key via the LPT port... although CW still works fine. Second work-around: Re-configure for CW keying via the com port. This allows CW and PSK to work properly, but prevents MMTTY from running. (DX4WIN grabs control of the CW port upon launch, and if you try to subsequently launch MMTTY you get a port conflict error.) Has anyone else encountered these problems? Does anyone have a suggestion on how to solve them? -larry K8UT --- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html The reason this message is shown is because the post was in HTML or had an attachment. Attachments are not allowed. To learn how to post in Plain-Text go to: http://www.expita.com/nomime.html --- ___ Dx4win mailing list Dx4win@mailman.qth.net http://mailman.qth.net/mailman/listinfo/dx4win
[Dx4win] PSK change is DX4WIN 6.02
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
[Dx4win] PSK31 config change in DX4WIN 6.02?
In DX4WIN 5.x, the PSK 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 the CW interface or VOX. What happened to the ability to = independently choose a com port? In my 5.03 configuration, I had been using the LPT port for CW keying, = and the com port for keying in either PSK31 or MMTTY. As long as I did = not attempt to simultaneously open the PSK window and run MMTTY, this = arrangement worked fine. Under 6.02, I attempted to work-arounds... neither which seem to work: First work-around: telling DX4WIN to use the LPT CW interface for PSK = keying. It doesn't work. PSK does not key via the LPT port... although = CW still works fine. Second work-around: Re-configure for CW keying via the com port. This = allows CW and PSK to work properly, but prevents MMTTY from running. = (DX4WIN grabs control of the CW port upon launch, and if you try to = subsequently launch MMTTY you get a port conflict error.) Has anyone else encountered these problems? Does anyone have a = suggestion on how to solve them? -larry K8UT --- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html The reason this message is shown is because the post was in HTML or had an attachment. Attachments are not allowed. To learn how to post in Plain-Text go to: http://www.expita.com/nomime.html ---
[Dx4win] PSK31 config change in DX4WIN 6.02?
Yep I found the same problem and had the same experience as you did. My work around was to stop using DX4WIN for PSK-31. Rod WC7N - Original Message - From: "Larry Gauthier" <[EMAIL PROTECTED]> To: Sent: Sunday, March 16, 2003 10:41 AM Subject: [Dx4win] PSK31 config change in DX4WIN 6.02? In DX4WIN 5.x, the PSK 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 the CW interface or VOX. What happened to the ability to independently choose a com port? In my 5.03 configuration, I had been using the LPT port for CW keying, and the com port for keying in either PSK31 or MMTTY. As long as I did not attempt to simultaneously open the PSK window and run MMTTY, this arrangement worked fine. Under 6.02, I attempted to work-arounds... neither which seem to work: First work-around: telling DX4WIN to use the LPT CW interface for PSK keying. It doesn't work. PSK does not key via the LPT port... although CW still works fine. Second work-around: Re-configure for CW keying via the com port. This allows CW and PSK to work properly, but prevents MMTTY from running. (DX4WIN grabs control of the CW port upon launch, and if you try to subsequently launch MMTTY you get a port conflict error.) Has anyone else encountered these problems? Does anyone have a suggestion on how to solve them? -larry K8UT --- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html The reason this message is shown is because the post was in HTML or had an attachment. Attachments are not allowed. To learn how to post in Plain-Text go to: http://www.expita.com/nomime.html --- ___ Dx4win mailing list Dx4win@mailman.qth.net http://mailman.qth.net/mailman/listinfo/dx4win
[Dx4win] DX4WIN and Pinging
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 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 > about 6 months ago, and what I was told is that although many have asked for > the feature, for some reason, it is not perceived as necessary.. So, we > just keep getting disconnected. > > > > > > > > Paul.. Please relent and give us a pinging feature in a future upgrade > (and I will quickly upgrade to the newest edition.. ! J ). Add a > switch to make it something that people that don't want it can turn it off, > but all of us who could really use it, could turn it on. variable ping > interval 10 minutes to 2 or 3 hours.. Sounds like a plan.. > > > > > > > > > > > > > > > > 73 > > > > > > > > Gary > > > > > > > > --- StripMime Report -- processed MIME parts --- > > multipart/mixed > > multipart/alternative > > text/plain (text body -- kept) > > text/html > > text/x-vcard > > The reason this message is shown is because the post was in HTML > > or had an attachment. Attachments are not allowed. To learn how > > to post in Plain-Text go to: http://www.expita.com/nomime.html --- > > ___ > > Dx4win mailing list > > Dx4win@mailman.qth.net > > http://mailman.qth.net/mailman/listinfo/dx4win > > > > ___ > Dx4win mailing list > Dx4win@mailman.qth.net > http://mailman.qth.net/mailman/listinfo/dx4win
[Dx4win] DX4WIN and Pinging
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 about 6 months ago, and what I was told is that although many have asked for the feature, for some reason, it is not perceived as necessary.. So, we just keep getting disconnected. > > > > Paul.. Please relent and give us a pinging feature in a future upgrade (and I will quickly upgrade to the newest edition.. ! J ). Add a switch to make it something that people that don't want it can turn it off, but all of us who could really use it, could turn it on. variable ping interval 10 minutes to 2 or 3 hours.. Sounds like a plan.. > > > > > > > > 73 > > > > Gary > > > > --- StripMime Report -- processed MIME parts --- > multipart/mixed > multipart/alternative > text/plain (text body -- kept) > text/html > text/x-vcard > The reason this message is shown is because the post was in HTML > or had an attachment. Attachments are not allowed. To learn how > to post in Plain-Text go to: http://www.expita.com/nomime.html --- > ___ > Dx4win mailing list > Dx4win@mailman.qth.net > http://mailman.qth.net/mailman/listinfo/dx4win >
[Dx4win] Access Violation
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 always sorts it out. I am running Windows 98 SE level 4.10.222.A on a Pentium II 400MHz = machine. The error seems to happen randomly and now I recognise it, is = not causing a nuisance. Sounds like a programming issue to me. Any ideas? John G4IRN. --- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html The reason this message is shown is because the post was in HTML or had an attachment. Attachments are not allowed. To learn how to post in Plain-Text go to: http://www.expita.com/nomime.html ---
