[Dx4win] CW Key Booard Operation

2002-05-05 Thread Jim Reisert AD1C
I tried to use the function keys this weekend to call CQ, and set up a 
simple exchange buffer.

@ is supposed (?) to send the callsign, but all DX4WIN sent was "?" 
instead.  Did something change, are the examples wrong?  Using 5.03.

- Jim

-- 
Jim Reisert AD1C, 7 Charlemont Court, North Chelmsford, MA 01863
USA +978-251-9933, <[EMAIL PROTECTED]>, http://www.ad1c.com



[Dx4win] External Program Callsign Address Lookup

2002-05-05 Thread <[EMAIL PROTECTED] (John F. Samuels)
First, I think the bat file and manager.res file should be in the
DX4Wxxx\Extdata folder.  Works mostly for me, although having some trouble
on Windows XP Home.  I am using this:

This file is called QSL.BAT

ECHO OFF
GOLIST.EXE %1>TMPQSL1.TXT
FGREP.COM %1 WWHAM.TXT>TMPQSL2.TXT
COPY TMPQSL*.TXT MANAGER.RES

FGREP is just a text search tool which outputs any line with a matching
search argument.

F3 calls QSL.BAT -- the name and path is set under File | Preferences | Ext
Data | QSL Manager Search | Executable Program.

Your program will only output the last line since manager.res is only called
once.  You can copy | append the lines and output all to manager.res.

73, John, K2CIB

>From: "Goody" <[EMAIL PROTECTED]>
>To: 
>Date: Sat, 4 May 2002 22:16:19 -0400
>Subject: [Dx4win] External Program Callsign Address Lookup
>
>I'm going to attempt to write a program to lookup addresses for DX4WIN.  I
>tried to test out the interface described in the help file using a simple
>batch program.  I had it output to both stdout and a manager.res file, but
>neither seems to work.  The batch file is in c:\test.bat and looks like
>this:
>
>echo off
>echo Joe Ham > c:\manager.res
>echo 123 North St >> c:\manager.res
>echo Somewhere, PA 17001 >> c:\manager.res
>
>Any ideas ?
>
>Thanks and 73
>Goody
>K3NG





[Dx4win] Multiple QSL managers for different modes on same callsign

2002-05-05 Thread Barry
We didn't chase every band/mode combination, so we didn't need such 
exhaustive record keeping. I recall having 3 DXCC lists, one for each 
mode. A check mark next to the country meant worked, and if/when I 
got a card, it was crossed off.
Barry W2UP


On 5 May 2002 Bob Naumann - N5NJ wrote:

> Shelby,
> 
> I agree with you.
> 
> Remember just a few years ago when we actually did all of this manually?
> How did we ever manage it?
> 
> 73,
> Bob N5NJ
> - Original Message -
> From: "Shelby Summerville" <[EMAIL PROTECTED]>
> To: 
> Sent: Sunday, May 05, 2002 10:08 AM
> Subject: Re: [Dx4win] Multiple QSL managers for different modes on same
> callsign
> 
> 
> > Dang..have y'all become so spoiled with the automation of logging,
> that
> > y'all have forgotten what was done using "paper logs"? Remember them? Why
> > not just use the "notes for this QSO" box for situations such as this, and
> > move on! Is it really necessary to have the manager printed on the label
> for
> > "direct" QSL's? Bureau QSL's are another situation, and would require some
> > "alteration"?
> > C'Ya, Shelby - K4WW
> > - Original Message -
> > From: "Roger Borowski" <[EMAIL PROTECTED]>
> > To: 
> > Sent: Sunday, May 05, 2002 10:38 AM
> > Subject: [Dx4win] Multiple QSL managers for different modes on same
> callsign
> >
> >
> > What I've found to work for me is to alter the callsign such as; K1B/SSB
> for
> > SSB QSO's and list the manager for that callsign as RZ3AA and all other
> > modes for K1B QSO's QSL to YT1AD. You do have to remember to alter the
> > callsign for any SSB QSO but if you set the first SSB QSO with K1B to
> > K1B/SSB and also make the Baker & Howland Island exception for K1B/SSB in
> > the prefix box, then set the QSL manager to RZ3AA, all subsequent QSO's
> with
> > K1B/SSB will have the correct QSL manager. 73, -=Rog-K9RB=-
> >
> >
> > --- 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.
> > Please post in Plain-Text only.---
> > ___
> > 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

--
Barry Kutner, W2UP  Internet: [EMAIL PROTECTED]
Newtown, PA Frankford Radio Club
 



[Dx4win] IOTA update OC182, OC089

2002-05-05 Thread rz6hgg
Hello!


Here is update for DX4WIN5.03 IOTA Island data.
You need copy island data and save as text file ,for
example,"IOTA.txt"
Then add it to DX4WIN usual way:File|Databases|IOTA
then
File|Import IOTA Data|open "IOTA.txt"
Then SAY "NO" (VERY IMPORTANT SAY - NO)
then OK and SAVE&EXIT.
You can use DX4win manual for update of course.


OC182,"Ducie Island",-124.48,-24.39
OC089,"Baker Island",-176.5417,0.2292



 Alexander
---
RZ6HGG
Stavropol  
E-mail: [EMAIL PROTECTED]
E-mail: [EMAIL PROTECTED]
5 ìàÿ 2002 ã.
15:22:08




[Dx4win] Multiple QSL managers for different modes on same callsign

2002-05-05 Thread <[EMAIL PROTECTED] (Roger Borowski)
The "notes for QSO" box never gets seen again after the QSO is entered in the
log unless you go back and select that particular QSO for review! When printing
QSL labels, if the QSO's aren't segregated by the manager/mode, multiple QSO's
will print on the same label while they need to go to different managers!
Besides, some people, like myself, rarely send any QSL's out direct to
managers, but use a service, such as WF5E provides. At this point, I am in no
hurry for any QSL's as they are only various band and mode "fillers" for me. I
now have over 60,000 QSL cards over the past 41 years in my files representing
#1 DXCC Honor Roll, Mixed, Phone, and CW (since 1994) but I still QSL 100%. If
you are just a casual operator, paper logs and manual QSL'ing could still work
fine for you. I'm sure there are many others who can also appreciate the
benefits of computerized logging and accurate QSL label printing. Besides the
system I described in my original message, time consuming manual QSL'ing would
be the only other option of getting the right QSO's to the right manager in
this particular case. 73, -=Rog-K9RB=-


- Original Message -
From: Shelby Summerville <[EMAIL PROTECTED]>
To: 
Sent: Sunday, May 05, 2002 11:08 AM
Subject: Re: [Dx4win] Multiple QSL managers for different modes on same
callsign


> Dang..have y'all become so spoiled with the automation of logging, that
> y'all have forgotten what was done using "paper logs"? Remember them? Why
> not just use the "notes for this QSO" box for situations such as this, and
> move on! Is it really necessary to have the manager printed on the label for
> "direct" QSL's? Bureau QSL's are another situation, and would require some
> "alteration"?
> C'Ya, Shelby - K4WW
> - Original Message -
> From: "Roger Borowski" <[EMAIL PROTECTED]>
> To: 
> Sent: Sunday, May 05, 2002 10:38 AM
> Subject: [Dx4win] Multiple QSL managers for different modes on same callsign
>
>
> What I've found to work for me is to alter the callsign such as; K1B/SSB for
> SSB QSO's and list the manager for that callsign as RZ3AA and all other
> modes for K1B QSO's QSL to YT1AD. You do have to remember to alter the
> callsign for any SSB QSO but if you set the first SSB QSO with K1B to
> K1B/SSB and also make the Baker & Howland Island exception for K1B/SSB in
> the prefix box, then set the QSL manager to RZ3AA, all subsequent QSO's with
> K1B/SSB will have the correct QSL manager. 73, -=Rog-K9RB=-
>
>
> --- 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.
> Please post in Plain-Text only.---
> ___
> 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] Re: Help with Com Ports.

2002-05-05 Thread <[EMAIL PROTECTED] (Ron Bracklow)
Gentlemen,

I am a new user of Dx4win Ver. 5.03 and I need some help in set of the
Packet window. Specifically opening Comport 4 on the Packet 1 Window.

On all other programs, Radio etc. I have no problem opening Comport 4,
however when I attempt to open Comport 4 on Packet 1, nothing happens. When
I select Comport 2, the Packet window opens, however no information is
transmitted.

Does anyone have any suggestions??

Thank you for your help.

Ron, N6PWW



[Dx4win] Multiple QSL managers for different modes on same callsign

2002-05-05 Thread David Tilley

Shelby Summerville wrote:

>Dang..have y'all become so spoiled with the automation of logging, that
>y'all have forgotten what was done using "paper logs"? Remember them? Why
>not just use the "notes for this QSO" box for situations such as this, and
>move on! Is it really necessary to have the manager printed on the label for
>"direct" QSL's? Bureau QSL's are another situation, and would require some
>"alteration"?
> 
>
For one thing, in addition to the manager printed on the label, it also 
prints the address label for the envelope.  The reason they make 
computer logging programs is so you don't have to mess with paper logs 
and hand addressing envelopes.   Hey, the features are there, why not 
use them?

- David, W4HPW

-- 
"Flying is of the Spirit.  The Spirit wants to fly!"
  - Amazon jungle pilot

"They shall mount up with wings, as eagles"  Isaiah 40:31

"Out of the night, into the morn, drawing us gently through the eye of the 
storm.
 Out of the sorrow, into the joy, where we'll dwell in the Highlands with Him 
evermore."

  from the CD "Journey Into The Morn"
  "Journey Into The Morn"
   Iona
  
 





[Dx4win] Multiple QSL managers for different modes on same callsign

2002-05-05 Thread Shelby Summerville
Dang..have y'all become so spoiled with the automation of logging, that
y'all have forgotten what was done using "paper logs"? Remember them? Why
not just use the "notes for this QSO" box for situations such as this, and
move on! Is it really necessary to have the manager printed on the label for
"direct" QSL's? Bureau QSL's are another situation, and would require some
"alteration"?
C'Ya, Shelby - K4WW
- Original Message -
From: "Roger Borowski" <[EMAIL PROTECTED]>
To: 
Sent: Sunday, May 05, 2002 10:38 AM
Subject: [Dx4win] Multiple QSL managers for different modes on same callsign


What I've found to work for me is to alter the callsign such as; K1B/SSB for
SSB QSO's and list the manager for that callsign as RZ3AA and all other
modes for K1B QSO's QSL to YT1AD. You do have to remember to alter the
callsign for any SSB QSO but if you set the first SSB QSO with K1B to
K1B/SSB and also make the Baker & Howland Island exception for K1B/SSB in
the prefix box, then set the QSL manager to RZ3AA, all subsequent QSO's with
K1B/SSB will have the correct QSL manager. 73, -=Rog-K9RB=-


--- 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.
Please post in Plain-Text only.---
___
Dx4win mailing list
Dx4win@mailman.qth.net
http://mailman.qth.net/mailman/listinfo/dx4win



[Dx4win] Multiple QSL managers for different modes on same callsign

2002-05-05 Thread David Tilley

Roger Borowski wrote:

>What I've found to work for me is to alter the callsign such as; K1B/SSB for 
>SSB QSO's and list the manager for that callsign as RZ3AA and all other modes 
>for K1B QSO's QSL to YT1AD. You do have to remember to alter the callsign for 
>any SSB QSO but if you set the first SSB QSO with K1B to K1B/SSB and also make 
>the Baker & Howland Island exception for K1B/SSB in the prefix box, then set 
>the QSL manager to RZ3AA, all subsequent QSO's with K1B/SSB will have the 
>correct QSL manager. 73, -=Rog-K9RB=- 
>
> 
>
That sounds like a winner, Roger.  I had thought of the notes field as a 
couple of others mentioned, but that wouldn't make the labels print 
properly.  Setting the start and stop dates wouldn't work either because 
some of the CW and SSB contacts are on the same day.

Presumably the K1B QSL manager won't object to seeing a "/SSB" after the 
callsign.  I doubt seriously they keep the cards anyway.  In fact, I 
THINK it was KU9C who said just to stick the labels on a piece of paper 
and send that to him.  Thanks again Roger and to everybody else who replied.

- David

-- 
"Flying is of the Spirit.  The Spirit wants to fly!"
  - Amazon jungle pilot

"They shall mount up with wings, as eagles"  Isaiah 40:31

"Out of the night, into the morn, drawing us gently through the eye of the 
storm.
 Out of the sorrow, into the joy, where we'll dwell in the Highlands with Him 
evermore."

  from the CD "Journey Into The Morn"
  "Journey Into The Morn"
   Iona
  
 





[Dx4win] YT1AD/WF5E QSL Service (was: Multiple QSL Managers...)

2002-05-05 Thread Larry Burke WI5A
Comment made in an earlier thread:

 > Besides, some people, like myself, rarely send any QSL's out direct to
 > managers, but use a service, such as WF5E provides.

Just a reminder that, according to the WF5E QSL Service web site,  YT1AD 
(one of the K1B managers) does not accept cards via the WF5E QSL Service. I 
suspect frequent users and the original author know this, but trying to 
save some folks who didn't know some delay and disappointment. This is not 
a commentary on YT1AD... he is free to reply to cards any way he wishes.

Further info on Les' service can be found at:  http://www.qsl.net/wf5e/

It's a great way to send cards.



Larry Wi5A




[Dx4win] Multiple QSL managers for different modes on same callsign

2002-05-05 Thread Bob Naumann - N5NJ
Actually, many of us did.

I used the 5BDXCC sheets that Cuschcraft used to give out in Dayton every
year.

I color coded SSB qsos red, cw qsos blue, and a black dot indicated when it
was confirmed.  5BDXCC all on one 11x14 sheet of paper with 3 'Flair' pens.
Very low-tech.

It was all done on paper - and - imagine this - much of the details were by
memory!

It was not uncommon for people to remember facts like who the QSL manager
was for an operation - even two of them - one per mode like for this K1B
operation.

73,
Bob N5NJ
QCWA, DXCC

- Original Message -
From: "Barry " <[EMAIL PROTECTED]>
To: "Bob Naumann - N5NJ" <[EMAIL PROTECTED]>; 
Sent: Sunday, May 05, 2002 10:33 AM
Subject: Re: [Dx4win] Multiple QSL managers for different modes on same
callsign


> We didn't chase every band/mode combination, so we didn't need such
> exhaustive record keeping. I recall having 3 DXCC lists, one for each
> mode. A check mark next to the country meant worked, and if/when I
> got a card, it was crossed off.
> Barry W2UP
>
>
> On 5 May 2002 Bob Naumann - N5NJ wrote:
>
> > Shelby,
> >
> > I agree with you.
> >
> > Remember just a few years ago when we actually did all of this manually?
> > How did we ever manage it?
> >
> > 73,
> > Bob N5NJ
> > - Original Message -
> > From: "Shelby Summerville" <[EMAIL PROTECTED]>
> > To: 
> > Sent: Sunday, May 05, 2002 10:08 AM
> > Subject: Re: [Dx4win] Multiple QSL managers for different modes on same
> > callsign
> >
> >
> > > Dang..have y'all become so spoiled with the automation of logging,
> > that
> > > y'all have forgotten what was done using "paper logs"? Remember them?
Why
> > > not just use the "notes for this QSO" box for situations such as this,
and
> > > move on! Is it really necessary to have the manager printed on the
label
> > for
> > > "direct" QSL's? Bureau QSL's are another situation, and would require
some
> > > "alteration"?
> > > C'Ya, Shelby - K4WW
> > > - Original Message -
> > > From: "Roger Borowski" <[EMAIL PROTECTED]>
> > > To: 
> > > Sent: Sunday, May 05, 2002 10:38 AM
> > > Subject: [Dx4win] Multiple QSL managers for different modes on same
> > callsign
> > >
> > >
> > > What I've found to work for me is to alter the callsign such as;
K1B/SSB
> > for
> > > SSB QSO's and list the manager for that callsign as RZ3AA and all
other
> > > modes for K1B QSO's QSL to YT1AD. You do have to remember to alter the
> > > callsign for any SSB QSO but if you set the first SSB QSO with K1B to
> > > K1B/SSB and also make the Baker & Howland Island exception for K1B/SSB
in
> > > the prefix box, then set the QSL manager to RZ3AA, all subsequent
QSO's
> > with
> > > K1B/SSB will have the correct QSL manager. 73, -=Rog-K9RB=-
> > >
> > >
> > > --- 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.
> > > Please post in Plain-Text only.---
> > > ___
> > > 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
>
> --
> Barry Kutner, W2UP  Internet: [EMAIL PROTECTED]
> Newtown, PA Frankford Radio Club
>
>
>



[Dx4win] Multiple QSL managers for different modes on same callsign

2002-05-05 Thread <[EMAIL PROTECTED] (Roger Borowski)
What I've found to work for me is to alter the callsign such as; K1B/SSB =
for SSB QSO's and list the manager for that callsign as RZ3AA and all =
other modes for K1B QSO's QSL to YT1AD. You do have to remember to alter =
the callsign for any SSB QSO but if you set the first SSB QSO with K1B =
to K1B/SSB and also make the Baker & Howland Island exception for =
K1B/SSB in the prefix box, then set the QSL manager to RZ3AA, all =
subsequent QSO's with K1B/SSB will have the correct QSL manager. 73, =
-=3DRog-K9RB=3D-=20


--- 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.
Please post in Plain-Text only.---


[Dx4win] Multiple QSL managers for different modes on same callsign

2002-05-05 Thread Bob Naumann - N5NJ
Shelby,

I agree with you.

Remember just a few years ago when we actually did all of this manually?
How did we ever manage it?

73,
Bob N5NJ
- Original Message -
From: "Shelby Summerville" <[EMAIL PROTECTED]>
To: 
Sent: Sunday, May 05, 2002 10:08 AM
Subject: Re: [Dx4win] Multiple QSL managers for different modes on same
callsign


> Dang..have y'all become so spoiled with the automation of logging,
that
> y'all have forgotten what was done using "paper logs"? Remember them? Why
> not just use the "notes for this QSO" box for situations such as this, and
> move on! Is it really necessary to have the manager printed on the label
for
> "direct" QSL's? Bureau QSL's are another situation, and would require some
> "alteration"?
> C'Ya, Shelby - K4WW
> - Original Message -
> From: "Roger Borowski" <[EMAIL PROTECTED]>
> To: 
> Sent: Sunday, May 05, 2002 10:38 AM
> Subject: [Dx4win] Multiple QSL managers for different modes on same
callsign
>
>
> What I've found to work for me is to alter the callsign such as; K1B/SSB
for
> SSB QSO's and list the manager for that callsign as RZ3AA and all other
> modes for K1B QSO's QSL to YT1AD. You do have to remember to alter the
> callsign for any SSB QSO but if you set the first SSB QSO with K1B to
> K1B/SSB and also make the Baker & Howland Island exception for K1B/SSB in
> the prefix box, then set the QSL manager to RZ3AA, all subsequent QSO's
with
> K1B/SSB will have the correct QSL manager. 73, -=Rog-K9RB=-
>
>
> --- 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.
> Please post in Plain-Text only.---
> ___
> 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] Multiple QSL managers

2002-05-05 Thread Jim Rhodes
It will help you remember, but not the program. The automated manager 
function would not work. This is not a problem if you handle these cards 
manually,  The correct manager will not print on the label. I suppose the 
absolute best way to handle it is with multiple entries is the manager file 
with appropriate to your log start & stop dates. That way the right 
manager's call would be printed.

At 07:17 AM 5/5/02, Bob Naumann - N5NJ wrote:
>For this unusual situation would it be OK to put that in the "Notes for this
>call field?
>
>- Original Message -
>From: "David Tilley" <[EMAIL PROTECTED]>
>To: "DX4WIN List" 
>Sent: Saturday, May 04, 2002 11:21 PM
>Subject: [Dx4win] Multiple QSL managers
>
>
> > For K1B, you have to QSL to one manager for SSB QSO's and another one
> > with a different address for all other modes.  How do you get DX4WIN to
> > accept different QSL managers for the same call under different modes?
> >  If I try to change QSO, it wants to change all of them.
> >
> > - David, W4HPW
>___
>Dx4win mailing list
>Dx4win@mailman.qth.net
>http://mailman.qth.net/mailman/listinfo/dx4win

Jim Rhodes K0XU
[EMAIL PROTECTED]



[Dx4win] CW Keyboard question

2002-05-05 Thread Bob Naumann - N5NJ
Mike,

This is true for most modern radios - aside from the 1/8" size of the plug
although I think the FT-100 and IC706 uses a 1/8" stereo as well.

All Yaesu's, Icom's, Kenwood's use a stereo connector now so that the jack
can be used for both a paddle input to the built-in keyer or for a straight
key.  A notable exception is the Kenwood 950SDX that has an unusual
provision for straight key (or computer interface) which is paired with the
remote keypad jack which is also 1/8" stereo.  This allows you to use the
built-in keyer along with an external device.

73,
Bob N5NJ


- Original Message -
From: "Mike Rioux" <[EMAIL PROTECTED]>
To: 
Sent: Saturday, May 04, 2002 8:59 PM
Subject: RE: [Dx4win] CW Keyboard question


> Thanks for all the responses! I put a scope on the keying line and found
out
> that the interface was working fine. Hmmm, what else could it be? Turns
out
> the
> Elecraft K2 REQUIRES a stereo 1/8" plug even if you are using a hand key
or
> an
> external keyer (i.e. computer). I replaced the mono 1/8" plug with a
stereo
> plug and voila, it works like a champ! The clue came to me when keying
> DX4Win
> caused the menu button on the K2 not to work. So I went back and read the
> fine
> manual that comes with the K2 and saw the notice about using a stereo
plug.
> Helps to RTFM!
> Thanks again, Mike W1USN
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Mike Rioux
> Sent: Friday, May 03, 2002 3:26 AM
> To: dx4win@mailman.qth.net
> Subject: [Dx4win] CW Keyboard question
>
>
> Finally got around to building the interface to key the rig from DX4Win.
> Used
> a 1k resister in series with the base of a 2n, emitter to ground,
> collector
> to the key jack on my K2. Circuit built into db25 d-shell on LPT1. When I
> use
> the keyboard window to send anything the key line goes to ground and the
K2
> stays in transmit (no make/break on the keying line from LPT1). If I pull
> the
> key jack out of the plug the rig goes back to receive (if the keyboard
> doesn't
> have anything left to send).
> 1. When using the keyboard interface the keying line sees 'stuck' in send.
> 2. when I pull the jack out, it goes back to receive.
> What am I missing here? Did I miss a config somewhere? (I did tell DX4Win
> LPT1 in the Preferences dialog box). BTW, the computer interface to the
> rig works fine (serial).
> Any ideas?
> Thanks, Mike W1USN
>
>
> ___
> 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] Multiple QSL managers

2002-05-05 Thread Bob Naumann - N5NJ
For this unusual situation would it be OK to put that in the "Notes for this
call field?

- Original Message -
From: "David Tilley" <[EMAIL PROTECTED]>
To: "DX4WIN List" 
Sent: Saturday, May 04, 2002 11:21 PM
Subject: [Dx4win] Multiple QSL managers


> For K1B, you have to QSL to one manager for SSB QSO's and another one
> with a different address for all other modes.  How do you get DX4WIN to
> accept different QSL managers for the same call under different modes?
>  If I try to change QSO, it wants to change all of them.
>
> - David, W4HPW
>
> --
> "Flying is of the Spirit.  The Spirit wants to fly!"
>   - Amazon jungle pilot
>
> "They shall mount up with wings, as eagles"  Isaiah 40:31
>
> "Out of the night, into the morn, drawing us gently through the eye of the
storm.
>  Out of the sorrow, into the joy, where we'll dwell in the Highlands with
Him evermore."
>
>   from the CD "Journey Into The Morn"
>   "Journey Into The Morn"
>Iona
>
>
>
>
>
> ___
> Dx4win mailing list
> Dx4win@mailman.qth.net
> http://mailman.qth.net/mailman/listinfo/dx4win



[Dx4win] CW Keyboard question

2002-05-05 Thread Mike Rioux
Thanks for all the responses! I put a scope on the keying line and found out
that the interface was working fine. Hmmm, what else could it be? Turns out
the
Elecraft K2 REQUIRES a stereo 1/8" plug even if you are using a hand key or
an
external keyer (i.e. computer). I replaced the mono 1/8" plug with a stereo
plug and voila, it works like a champ! The clue came to me when keying
DX4Win
caused the menu button on the K2 not to work. So I went back and read the
fine
manual that comes with the K2 and saw the notice about using a stereo plug.
Helps to RTFM!
Thanks again, Mike W1USN

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Mike Rioux
Sent: Friday, May 03, 2002 3:26 AM
To: dx4win@mailman.qth.net
Subject: [Dx4win] CW Keyboard question


Finally got around to building the interface to key the rig from DX4Win.
Used
a 1k resister in series with the base of a 2n, emitter to ground,
collector
to the key jack on my K2. Circuit built into db25 d-shell on LPT1. When I
use
the keyboard window to send anything the key line goes to ground and the K2
stays in transmit (no make/break on the keying line from LPT1). If I pull
the
key jack out of the plug the rig goes back to receive (if the keyboard
doesn't
have anything left to send).
1. When using the keyboard interface the keying line sees 'stuck' in send.
2. when I pull the jack out, it goes back to receive.
What am I missing here? Did I miss a config somewhere? (I did tell DX4Win
LPT1 in the Preferences dialog box). BTW, the computer interface to the
rig works fine (serial).
Any ideas?
Thanks, Mike W1USN


___
Dx4win mailing list
Dx4win@mailman.qth.net
http://mailman.qth.net/mailman/listinfo/dx4win



[Dx4win] Multiple QSL managers

2002-05-05 Thread David Tilley
For K1B, you have to QSL to one manager for SSB QSO's and another one 
with a different address for all other modes.  How do you get DX4WIN to 
accept different QSL managers for the same call under different modes? 
 If I try to change QSO, it wants to change all of them.

- David, W4HPW

-- 
"Flying is of the Spirit.  The Spirit wants to fly!"
  - Amazon jungle pilot

"They shall mount up with wings, as eagles"  Isaiah 40:31

"Out of the night, into the morn, drawing us gently through the eye of the 
storm.
 Out of the sorrow, into the joy, where we'll dwell in the Highlands with Him 
evermore."

  from the CD "Journey Into The Morn"
  "Journey Into The Morn"
   Iona