Date   

FT920 Again

Jim Steel <jim.steel@...>
 

Hi Dave,
Me again [nightmare]. . . . .just noticed on the radio during the qsy process when using the upper L/R buttons on Commander the CAT indicator on the radio stays on but when qsying using the lower L/R buttons the CAT indicator on the radio doesn't come on at all untill the qsy stream has been sent to the radio from Commander, auto poll does not take place during either process.


Re: FT920 something to read before bedtime

Jim Steel <jim.steel@...>
 

Hi Dave,
>Well, that's different behavior, but certainly not what we
want. Back to the
drawing board. I wish the local library stocked Yaesu transceivers; all I
need is to borrow an FT920 for a few hours, and this problem would be
history.
or improve my reporting / communication skills.

But a scroll bar provides more functionality
point taken.

Here's what's happening when using both upper left [x2] and upper right
[x2] qsy buttons [forgive the simplification];

Click on qsy button. . . . .
Commander to radio > change
from this frequency 28,025.00 to this frequency 28,025.10 < radio to
Commander >confirm and awaiting next instruction,
Commander to radio > change
from this frequency 28,025.10 to this frequency 28,025.20 < radio to
Commander > confirm and awaiting next instruction,
etc etc etc until the
desired frequency is attained [all be it at the speed of light HI] unclick
qsy button, both Commander and radio qsy in synch.

Here's what is happening when using the lower L/R qsy buttons and scroll
bar / scroll bar button;

Click on qsy button. . . . .
Commander to radio >
change from this frequency 28,025.00 to this frequency 28,025.10 <

Commander to radio >
change from this frequency 28,025.10 to this frequency 28,025.20 <

Commander to radio >
change from this frequency 28,025.20 to this frequency 28,025.30 <

Commander to radio >
change from this frequency 28,025.30 to this frequency 28,025.40 <

Commander to radio >
change from this frequency 28,025.40 to this frequency 28,025.50 < radio to
Commander > confirm and awaiting next instruction. The radio receives a
block of commands, which it carries out, rather than a stream of
commands.[ Eureka that's it ???}

Again my apologies for the simplification but I work on the principle. . . .
. if you dont understand what I'm trying to convey, it's not your fault its
mine for not putting it in a way you can understand, hence my rather back to
basics approach.

Take care

Jim -
M0ZAK






----- Original Message -----
From: "Dave, AA6YQ" <dhb@...>
To: <dxlab@...>
Sent: Sunday, December 16, 2001 6:39 PM
Subject: RE: [dxlab] FT920


Well, that's different behavior, but certainly not what we want. Back to
the
drawing board. I wish the local library stocked Yaesu transceivers; all I
need is to borrow an FT920 for a few hours, and this problem would be
history.

It is indeed tempting to replace the scroll bar below the VFO with a set
of
buttons like the ones to the left and right of the VFO. But a scroll bar
provides more functionality -- you can grab the slider and move it an
arbitrary distance in either direction, you can click to either side of
the
slider to effect a large change, or you can click on the arrow buttons on
either end to effect a small change. I'm not ready to give up just yet...

73,

Dave, AA6YQ
-----Original Message-----
From: Jim Steel [mailto:jim.steel@...]
Sent: Sunday, December 16, 2001 6:48 AM
To: dxlab@...
Subject: [dxlab] FT920


Hi Dave,
How Things? well here goes. . . . . . not quite right this
end
with the way the info is sent to the rig. Single click [click / let go]
results in a single command being sent to the radio and a qsy of 1khz.
Click
and hold to qsy 25khz, for example, results in a block command being sent
to
the radio. Seems Commander stores large command blocks [>2] until the
command is finished [unclicked]. Other qsy buttons both sides of the
readout
work great, just the qsy buttons below the readout. ? Idea [hear me out].
.
. . . could the qsy buttons to the lower left and lower right of the
readout
behave differently because of the scroll bar function directly below
Commanders readout????? seems to be no trouble with the other qsy buttons.
What about doing away with the scroll bar and add two more buttons??????
perhaps in this configuration << [10khz], < [1khz] and > [1khz], >>
[10khz],
perhaps I'm blind but dont see the point in the scroll bar when a button
will do [looks nice?].


Take care

Jim - M0ZAK





Yahoo! Groups Sponsor
ADVERTISEMENT




To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.







To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/


Re: FT920

Dave, AA6YQ <dhb@...>
 

Well, that's different behavior, but certainly not what we want. Back to the
drawing board. I wish the local library stocked Yaesu transceivers; all I
need is to borrow an FT920 for a few hours, and this problem would be
history.

It is indeed tempting to replace the scroll bar below the VFO with a set of
buttons like the ones to the left and right of the VFO. But a scroll bar
provides more functionality -- you can grab the slider and move it an
arbitrary distance in either direction, you can click to either side of the
slider to effect a large change, or you can click on the arrow buttons on
either end to effect a small change. I'm not ready to give up just yet...

73,

Dave, AA6YQ

-----Original Message-----
From: Jim Steel [mailto:jim.steel@...]
Sent: Sunday, December 16, 2001 6:48 AM
To: dxlab@...
Subject: [dxlab] FT920


Hi Dave,
How Things? well here goes. . . . . . not quite right this end
with the way the info is sent to the rig. Single click [click / let go]
results in a single command being sent to the radio and a qsy of 1khz. Click
and hold to qsy 25khz, for example, results in a block command being sent to
the radio. Seems Commander stores large command blocks [>2] until the
command is finished [unclicked]. Other qsy buttons both sides of the readout
work great, just the qsy buttons below the readout. ? Idea [hear me out]. .
. . . could the qsy buttons to the lower left and lower right of the readout
behave differently because of the scroll bar function directly below
Commanders readout????? seems to be no trouble with the other qsy buttons.
What about doing away with the scroll bar and add two more buttons??????
perhaps in this configuration << [10khz], < [1khz] and > [1khz], >> [10khz],
perhaps I'm blind but dont see the point in the scroll bar when a button
will do [looks nice?].


Take care

Jim - M0ZAK





Yahoo! Groups Sponsor
ADVERTISEMENT




To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.


Re: Don't upgrade to DXKeeper 1.3.6

Dave, AA6YQ <dhb@...>
 

Ouch. My apologies to all - this was unintended. I have corrected the update
files for all DXLab applications to eliminate the ...&#92;XYZUpdate folder.

Regarding DXKeeper 1.3.6, the "new QTH table" upgrade process failed for
Mike K9UW -- the table was created, but was populated with a null entry. The
null entry caused the program error he reported. I have sent him a version
of DXKeeper that tolerates the null QTH table entry, but haven't yet
determined what created the null entry to begin with. When I've identified
and corrected that defect, I will release an update accordingly.

73,

Dave, AA6YQ

-----Original Message-----
From: Richard B. Drake [mailto:rich@...]
Sent: Sunday, December 16, 2001 9:49 AM
To: dxlab@...
Subject: RE: [dxlab] Don't upgrade to DXKeeper 1.3.6


Dave,

Most all of your update installs have been doing this for quite some time
now. I thought you were doing it purposely, though I couldn't figure why.
But, it's just a small matter of copying the files from the ...&#92;XYZUpdate
directory to the main program directory in order to complete the install.
After doing this, DXKeeper 1.3.6 is running fine here.

----
73, Rich - W3ZJ

-----Original Message-----
From: Dave, AA6YQ [mailto:dhb@...]
Sent: Saturday, December 15, 2001 11:18 PM
To: dxlab@...
Subject: [dxlab] Don't upgrade to DXKeeper 1.3.6


The archive file was evidently misconstructed -- I will correct this
tomorrow. Sorry...

If you've installed 1.3.6, just delete c:&#92;Program
Files&#92;dxkeeper&#92;DXKeeperXYZUpdate and resume using the previous version in
c:&#92;Program Files&#92;dxkeeper

73,

Dave, AA6YQ

-----Original Message-----
From: Mike & Lara Pagel [mailto:pagel@...]
Sent: Saturday, December 15, 2001 22:56 PM
To: dhb@...
Subject: DXKeeper 1.3.6 error


Hi Dave!

Prior to this evening's install of the 136 upgrade, I had these folders
associated with the DXKeeper Directory:
c:&#92;Program Files&#92;dxkeeper
c:&#92;Program Files&#92;dxkeeper&#92;databases
c:&#92;Program Files&#92;dxkeeper&#92;install
c:&#92;Program Files&#92;dxkeeper&#92;reports

Installing the DXKeeper 136 update seems to have created several
new folders
called:

c:&#92;Program Files&#92;dxkeeper&#92;DXKeeperXYZUpdate
c:&#92;Program Files&#92;dxkeeper&#92;DXKeeperXYZUpdate&#92;databases
c:&#92;Program Files&#92;dxkeeper&#92;DXKeeperXYZUpdate&#92;help

These co-exist with the previous folders.

I concluded that the "DXKeeperXYZUpdate" folder was an error, and that its
contents should have gone into c:&#92;Program Files&#92;dxkeeper. I
decided to see
if I could fix this by copying the new "databases" and "help" folders over
the existing folders with the same names under c:&#92;program
files&#92;dxkeeper and
copying DXKeeper136.exe into the c:&#92;Program Files&#92;dxkeeper
folder. By doing
so, I thought I'd preserve the consistent content while adding the new
content to folders with the historical names.

No soap. It isn't working. I get an error message telling me that the
program is "Unable to open log database C:&#92;Program
Files&#92;dxkeeper&#92;Databases&#92;K9UW.mdb

Error file attached. I'm probably screwing up something very basic, but
can't seem to figure it out on my own.

Sorry to keep you up with such things.

73, de Mike, K9UW



To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/




To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/


WinWarbler 2.1.6

Richard B Drake
 

Dave,

Up until now, whenever I made a contact with WinWarbler, I always used pane
0. But a few minutes ago I happened to lock on to OK1AW calling CQ in pane 1
so just decided to stay there. Big trouble! My transmitted text was not
showing up anywhere so I couldn't tell what macros I was sending. On the
next transmission I tried switching to pane 0. When I did that, the callsign
and name of the station I had previously contacted went into the logging
fields and I didn't notice it. So, when I went back the next time my macros
called the wrong station and gave the wrong name. Boy, I won't do that
again! But, the real problem is, why didn't pane 1 show my transmitted text
while that was the active pane?

73, Rich - W3ZJ

-----Original Message-----
From: Richard B. Drake [mailto:rich@...]
Sent: Sunday, December 16, 2001 9:49 AM
To: dxlab@...
Subject: RE: [dxlab] Don't upgrade to DXKeeper 1.3.6


Dave,

Most all of your update installs have been doing this for quite some time
now. I thought you were doing it purposely, though I couldn't figure why.
But, it's just a small matter of copying the files from the ...&#92;XYZUpdate
directory to the main program directory in order to complete the install.
After doing this, DXKeeper 1.3.6 is running fine here.

----
73, Rich - W3ZJ

-----Original Message-----
From: Dave, AA6YQ [mailto:dhb@...]
Sent: Saturday, December 15, 2001 11:18 PM
To: dxlab@...
Subject: [dxlab] Don't upgrade to DXKeeper 1.3.6


The archive file was evidently misconstructed -- I will correct this
tomorrow. Sorry...

If you've installed 1.3.6, just delete c:&#92;Program
Files&#92;dxkeeper&#92;DXKeeperXYZUpdate and resume using the previous
version in
c:&#92;Program Files&#92;dxkeeper

73,

Dave, AA6YQ

-----Original Message-----
From: Mike & Lara Pagel [mailto:pagel@...]
Sent: Saturday, December 15, 2001 22:56 PM
To: dhb@...
Subject: DXKeeper 1.3.6 error


Hi Dave!

Prior to this evening's install of the 136 upgrade, I had these folders
associated with the DXKeeper Directory:
c:&#92;Program Files&#92;dxkeeper
c:&#92;Program Files&#92;dxkeeper&#92;databases
c:&#92;Program Files&#92;dxkeeper&#92;install
c:&#92;Program Files&#92;dxkeeper&#92;reports

Installing the DXKeeper 136 update seems to have created several
new folders
called:

c:&#92;Program Files&#92;dxkeeper&#92;DXKeeperXYZUpdate
c:&#92;Program Files&#92;dxkeeper&#92;DXKeeperXYZUpdate&#92;databases
c:&#92;Program Files&#92;dxkeeper&#92;DXKeeperXYZUpdate&#92;help

These co-exist with the previous folders.

I concluded that the "DXKeeperXYZUpdate" folder was an error,
and that its
contents should have gone into c:&#92;Program Files&#92;dxkeeper. I
decided to see
if I could fix this by copying the new "databases" and "help"
folders over
the existing folders with the same names under c:&#92;program
files&#92;dxkeeper and
copying DXKeeper136.exe into the c:&#92;Program Files&#92;dxkeeper
folder. By doing
so, I thought I'd preserve the consistent content while adding the new
content to folders with the historical names.

No soap. It isn't working. I get an error message telling me that the
program is "Unable to open log database C:&#92;Program
Files&#92;dxkeeper&#92;Databases&#92;K9UW.mdb

Error file attached. I'm probably screwing up something very basic, but
can't seem to figure it out on my own.

Sorry to keep you up with such things.

73, de Mike, K9UW



To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/




To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/


Re: Don't upgrade to DXKeeper 1.3.6

Richard B Drake
 

Dave,

Most all of your update installs have been doing this for quite some time
now. I thought you were doing it purposely, though I couldn't figure why.
But, it's just a small matter of copying the files from the ...&#92;XYZUpdate
directory to the main program directory in order to complete the install.
After doing this, DXKeeper 1.3.6 is running fine here.

----
73, Rich - W3ZJ

-----Original Message-----
From: Dave, AA6YQ [mailto:dhb@...]
Sent: Saturday, December 15, 2001 11:18 PM
To: dxlab@...
Subject: [dxlab] Don't upgrade to DXKeeper 1.3.6


The archive file was evidently misconstructed -- I will correct this
tomorrow. Sorry...

If you've installed 1.3.6, just delete c:&#92;Program
Files&#92;dxkeeper&#92;DXKeeperXYZUpdate and resume using the previous version in
c:&#92;Program Files&#92;dxkeeper

73,

Dave, AA6YQ

-----Original Message-----
From: Mike & Lara Pagel [mailto:pagel@...]
Sent: Saturday, December 15, 2001 22:56 PM
To: dhb@...
Subject: DXKeeper 1.3.6 error


Hi Dave!

Prior to this evening's install of the 136 upgrade, I had these folders
associated with the DXKeeper Directory:
c:&#92;Program Files&#92;dxkeeper
c:&#92;Program Files&#92;dxkeeper&#92;databases
c:&#92;Program Files&#92;dxkeeper&#92;install
c:&#92;Program Files&#92;dxkeeper&#92;reports

Installing the DXKeeper 136 update seems to have created several
new folders
called:

c:&#92;Program Files&#92;dxkeeper&#92;DXKeeperXYZUpdate
c:&#92;Program Files&#92;dxkeeper&#92;DXKeeperXYZUpdate&#92;databases
c:&#92;Program Files&#92;dxkeeper&#92;DXKeeperXYZUpdate&#92;help

These co-exist with the previous folders.

I concluded that the "DXKeeperXYZUpdate" folder was an error, and that its
contents should have gone into c:&#92;Program Files&#92;dxkeeper. I
decided to see
if I could fix this by copying the new "databases" and "help" folders over
the existing folders with the same names under c:&#92;program
files&#92;dxkeeper and
copying DXKeeper136.exe into the c:&#92;Program Files&#92;dxkeeper
folder. By doing
so, I thought I'd preserve the consistent content while adding the new
content to folders with the historical names.

No soap. It isn't working. I get an error message telling me that the
program is "Unable to open log database C:&#92;Program
Files&#92;dxkeeper&#92;Databases&#92;K9UW.mdb

Error file attached. I'm probably screwing up something very basic, but
can't seem to figure it out on my own.

Sorry to keep you up with such things.

73, de Mike, K9UW



To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/


FT920

Jim Steel <jim.steel@...>
 

Hi Dave,
How Things? well here goes. . . . . . not quite right this end with the way the info is sent to the rig. Single click [click / let go] results in a single command being sent to the radio and a qsy of 1khz. Click and hold to qsy 25khz, for example, results in a block command being sent to the radio. Seems Commander stores large command blocks [>2] until the command is finished [unclicked]. Other qsy buttons both sides of the readout work great, just the qsy buttons below the readout. ? Idea [hear me out]. . . . . could the qsy buttons to the lower left and lower right of the readout behave differently because of the scroll bar function directly below Commanders readout????? seems to be no trouble with the other qsy buttons. What about doing away with the scroll bar and add two more buttons?????? perhaps in this configuration << [10khz], < [1khz] and > [1khz], >> [10khz], perhaps I'm blind but dont see the point in the scroll bar when a button will do [looks nice?].

Take care
Jim - M0ZAK


Re: DXView

Dave, AA6YQ <dhb@...>
 

So far, Chris, no one has reported any OS conflicts with DXView.

73,

Dave, AA6YQ

-----Original Message-----
From: Chris BONDE [mailto:ve7hcb@...]
Sent: Saturday, December 15, 2001 23:35 PM
To: dxlab@...
Subject: Re: [dxlab]DXView


Upon reading the instructions for installing DXView, I read that parts of
the operating system are updated and shouldnot upset things BUT NOT
Guaranteed. I am running WIN98SE.

Anyone have any troubles with this??
Chris opr VE7HCB


Yahoo! Groups Sponsor
ADVERTISEMENT




To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.


Re: DXView

Chris BONDE <ve7hcb@...>
 

Upon reading the instructions for installing DXView, I read that parts of the operating system are updated and shouldnot upset things BUT NOT Guaranteed. I am running WIN98SE.

Anyone have any troubles with this??
Chris opr VE7HCB


Don't upgrade to DXKeeper 1.3.6

Dave, AA6YQ <dhb@...>
 

The archive file was evidently misconstructed -- I will correct this
tomorrow. Sorry...

If you've installed 1.3.6, just delete c:&#92;Program
Files&#92;dxkeeper&#92;DXKeeperXYZUpdate and resume using the previous version in
c:&#92;Program Files&#92;dxkeeper

73,

Dave, AA6YQ

-----Original Message-----
From: Mike & Lara Pagel [mailto:pagel@...]
Sent: Saturday, December 15, 2001 22:56 PM
To: dhb@...
Subject: DXKeeper 1.3.6 error


Hi Dave!

Prior to this evening's install of the 136 upgrade, I had these folders
associated with the DXKeeper Directory:
c:&#92;Program Files&#92;dxkeeper
c:&#92;Program Files&#92;dxkeeper&#92;databases
c:&#92;Program Files&#92;dxkeeper&#92;install
c:&#92;Program Files&#92;dxkeeper&#92;reports

Installing the DXKeeper 136 update seems to have created several new folders
called:

c:&#92;Program Files&#92;dxkeeper&#92;DXKeeperXYZUpdate
c:&#92;Program Files&#92;dxkeeper&#92;DXKeeperXYZUpdate&#92;databases
c:&#92;Program Files&#92;dxkeeper&#92;DXKeeperXYZUpdate&#92;help

These co-exist with the previous folders.

I concluded that the "DXKeeperXYZUpdate" folder was an error, and that its
contents should have gone into c:&#92;Program Files&#92;dxkeeper. I decided to see
if I could fix this by copying the new "databases" and "help" folders over
the existing folders with the same names under c:&#92;program files&#92;dxkeeper and
copying DXKeeper136.exe into the c:&#92;Program Files&#92;dxkeeper folder. By doing
so, I thought I'd preserve the consistent content while adding the new
content to folders with the historical names.

No soap. It isn't working. I get an error message telling me that the
program is "Unable to open log database C:&#92;Program
Files&#92;dxkeeper&#92;Databases&#92;K9UW.mdb

Error file attached. I'm probably screwing up something very basic, but
can't seem to figure it out on my own.

Sorry to keep you up with such things.

73, de Mike, K9UW


Re: SpotCollector 1.1.3 is available

Richard B Drake
 

Dave,

The "+" still seems to be getting stripped out of the notes. Just posted a
spot
"JA1SCW +2.125 PSK31" and the note showed in the spot window without the
"+". Bye the way I worked him on 10 meters from Maryland with the 5 watt
radio - Pretty cool!

----
73, Rich - W3ZJ

-----Original Message-----
From: Dave, AA6YQ [mailto:dhb@...]
Sent: Friday, December 14, 2001 10:02 PM
To: dxlab@...
Subject: [dxlab] SpotCollector 1.1.3 is available


This release corrects the "delimiters are stripped from spot notes"
defect that Rich reported below.

To upgrade, see http://www.qsl.net/spotcollector/development.htm --
you'll be downloading
http://www.qsl.net/spotcollector/SpotCollector113Update.exe .

73,

Dave, AA6YQ


-----Original Message-----
From: Richard B. Drake [mailto:rich@...]
Sent: Tuesday, December 04, 2001 6:36 AM
To: dxlab@...
Subject: [dxlab] SpotCollector 112

Dave,

I just posted a spot with a comment that read "S9+ in MD". The telnet
window
shows my spot exactly as I posted it but SpotCollector stripped off the
"+"
and showed "S9 in MD" in the notes field. IS "+" a special character?

----
73, Rich - W3ZJ









To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/



Re: WinWarbler modes.

Richard B Drake
 

Dave,

Yes, I think that's the right idea. BTW: I always use upper side band with
reverse tones for RTTY. On the Omni VI+ this is necessary in order to use
the narrow CW filters. On the 817 it's not necessary but it saves having to
make a bunch of adjustments when switching between PSK and RTTY. I never
noticed any ill affect from the fact that WinWarbler thinks it's in LSB
mode, but perhaps the frequency arithmetic is wrong? I never paid any
attention to it.

-----
73, Rich - W3ZJ

-----Original Message-----
From: Dave, AA6YQ [mailto:dhb@...]
Sent: Saturday, December 15, 2001 1:28 AM
To: dxlab@...
Subject: RE: [dxlab] WinWarbler modes.


You can choose between AFSK (LSB) and FSK (RTTY) for Soundcard RTTY and
External RTTY Modem operation - use the transceiver mode radio buttons
WinWarbler's Config Soundcard RTTY and External RTTY Modem tabs. When
switching to PSK, WinWarbler instructs Commander to put the rig in USB
mode - sounds like I need to make this configurable, with choices of
USB, LSB, and RTTY. Assuming I can get all the frequency display
arithmetic to work in each case, will that be acceptable?

73,

Dave, AA6YQ

-----Original Message-----
From: Richard B. Drake [mailto:rich@...]
Sent: Friday, December 14, 2001 9:55 PM
To: dxlab@...
Subject: [dxlab] WinWarbler modes.

When in WinWarbler in RTTY (Digital) mode, and PSK mode is selected, it
switches the rig (The FT-817 at least) to USB mode. When WinWarbler is
started up, it switches the rig to USB mode. When in PSK mode and
selecting
RTTY mode it switches the rig to LSB mode. None of this is desirable. I
suggest that WinWarbler should not attempt to do any mode settings,
leave
that to Commander and the users selections or make it completely user
configurable within WinWarbler. In the case of the FT-817 it always
wants to
be in digital mode for both PSK and RTTY.

---
73, Rich - W3ZJ






Yahoo! Groups Sponsor


ADVERTISEMENT

<http://rd.yahoo.com/M=218059.1783662.3300202.1261774/D=egroupweb/S=1705
063108:HM/A=904006/R=0/*http:/movies.yahoo.com/movies/feature/spiderman.
html> See the Trailer!


<http://us.adserver.yahoo.com/l?M=218059.1783662.3300202.1261774/D=egrou
pmail/S=1705063108:HM/A=904006/rand=266052560>

To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to the Yahoo!
<http://docs.yahoo.com/info/terms/> Terms of Service.






To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/



Re: DXKeeper 1.3.6 is available

Kurt Brandstetter <kurt.brandstetter@...>
 

Sorry !

I wanted only to rename the link:

To upgrade, follow the instructions in
http://www.qsl.net/dxkeeper/upgrade.htm -- you'll be downloading
http://www.qsl.net/dxkeeper/DXKeeper136Update.exe .
and used the send button too soon.
Pse excuse !
Kurt

--
73 de Kurt OE 1002419 ICQ-UIN 43074273
CCA member AC01-01249 NCDXF #4175 INDEXA #1720
Homepage: http://www.swl.net/oe1002419
***********************************************
The latest QSL's I've received at my homepage:
Pse use link "Latest QSL cards arrived at my postbox"
FK8KAB/p (OC-058); GB0HI; C98DC (AF-066); XU7ABN; OJ0J
4T0I (SA-052); RA1QQ/A (RR-2211);3Y0C;RA1TC/1 (EU-162)
***********************************************


DXKeeper 1.3.6 is available

Kurt Brandstetter <kurt.brandstetter@...>
 

This release

- enables award checking for all bands and modes after initial
installation

- provides keyboard shortcuts for navigating among the Capture window
fields (see
http://www.qsl.net/dxkeeper/Help/Log.htm#CaptureKeyboardShortcuts )

- updates SpotCollector's Spot Callsign field when you enter a
callsign in DXKeeper Main or Capture windows and then strike the Enter
key (requires SpotCollector version 1.1.2 or later) - this makes it
easy to spot a station after you've logged your QSO.

- provides support for printing QSL cards when you operate from more
than one QTH (see http://www.qsl.net/dxkeeper/Help/MultipleQTHs.htm )

The last item required the addition of a new database table to each log.
This is performed automatically by DXKeeper. While I have tested this in
several configurations, I strongly urge that you make a backup copy of
your log files before upgrading to this release. Even better would be to
make a backup copy of your log files AND export all of your QSOs to an
ADIF file. Its not that I lack confidence - but if your attachment to
your log data is anything like mine, then you cannot possibly be too
careful.

To upgrade, follow the instructions in
http://www.qsl.net/dxkeeper/upgrade.htm -- you'll be downloading
http://www.qsl.net/dxkeeper/DXKeeper136Update.exe .

73,

Dave, AA6YQ






To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/


DXKeeper 1.3.6 is available

Dave, AA6YQ <dhb@...>
 

This release

- enables award checking for all bands and modes after initial
installation

- provides keyboard shortcuts for navigating among the Capture window
fields (see
http://www.qsl.net/dxkeeper/Help/Log.htm#CaptureKeyboardShortcuts )

- updates SpotCollector's Spot Callsign field when you enter a
callsign in DXKeeper Main or Capture windows and then strike the Enter
key (requires SpotCollector version 1.1.2 or later) - this makes it
easy to spot a station after you've logged your QSO.

- provides support for printing QSL cards when you operate from more
than one QTH (see http://www.qsl.net/dxkeeper/Help/MultipleQTHs.htm )

The last item required the addition of a new database table to each log.
This is performed automatically by DXKeeper. While I have tested this in
several configurations, I strongly urge that you make a backup copy of
your log files before upgrading to this release. Even better would be to
make a backup copy of your log files AND export all of your QSOs to an
ADIF file. Its not that I lack confidence - but if your attachment to
your log data is anything like mine, then you cannot possibly be too
careful.

To upgrade, follow the instructions in
http://www.qsl.net/dxkeeper/upgrade.htm -- you'll be downloading
www.qsl.net/dxkeeper/DXKeeper136Update.exe .

73,

Dave, AA6YQ


Re: WinWarbler modes.

Dave, AA6YQ <dhb@...>
 

You can choose between AFSK (LSB) and FSK (RTTY) for Soundcard RTTY and
External RTTY Modem operation - use the transceiver mode radio buttons
WinWarbler's Config Soundcard RTTY and External RTTY Modem tabs. When
switching to PSK, WinWarbler instructs Commander to put the rig in USB
mode - sounds like I need to make this configurable, with choices of
USB, LSB, and RTTY. Assuming I can get all the frequency display
arithmetic to work in each case, will that be acceptable?

73,

Dave, AA6YQ

-----Original Message-----
From: Richard B. Drake [mailto:rich@...]
Sent: Friday, December 14, 2001 9:55 PM
To: dxlab@...
Subject: [dxlab] WinWarbler modes.

When in WinWarbler in RTTY (Digital) mode, and PSK mode is selected, it
switches the rig (The FT-817 at least) to USB mode. When WinWarbler is
started up, it switches the rig to USB mode. When in PSK mode and
selecting
RTTY mode it switches the rig to LSB mode. None of this is desirable. I
suggest that WinWarbler should not attempt to do any mode settings,
leave
that to Commander and the users selections or make it completely user
configurable within WinWarbler. In the case of the FT-817 it always
wants to
be in digital mode for both PSK and RTTY.

---
73, Rich - W3ZJ






Yahoo! Groups Sponsor


ADVERTISEMENT

<http://rd.yahoo.com/M=218059.1783662.3300202.1261774/D=egroupweb/S=1705
063108:HM/A=904006/R=0/*http:/movies.yahoo.com/movies/feature/spiderman.
html> See the Trailer!


<http://us.adserver.yahoo.com/l?M=218059.1783662.3300202.1261774/D=egrou
pmail/S=1705063108:HM/A=904006/rand=266052560>

To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to the Yahoo!
<http://docs.yahoo.com/info/terms/> Terms of Service.


WinWarbler modes.

Richard B Drake
 

When in WinWarbler in RTTY (Digital) mode, and PSK mode is selected, it
switches the rig (The FT-817 at least) to USB mode. When WinWarbler is
started up, it switches the rig to USB mode. When in PSK mode and selecting
RTTY mode it switches the rig to LSB mode. None of this is desirable. I
suggest that WinWarbler should not attempt to do any mode settings, leave
that to Commander and the users selections or make it completely user
configurable within WinWarbler. In the case of the FT-817 it always wants to
be in digital mode for both PSK and RTTY.

---
73, Rich - W3ZJ


Re: WinWarbler version 2.1.6 is available

Richard B Drake
 


One click is a standard Windows gesture that means "select"; clicking in
a WinWarbler receive pane designates its channel as the one on which you
will transmit. Changing this to "a receive pane is selected whenever the
mouse pointer is overhead" would be very inconvenient -- for example,
you'd have to be very careful about moving the mouse from the QSO Info
panel to the Macros panel without inadvertently changing the selected
receive pane.
Yes, I have used windows systems (Xwindows on Sun Solaris) that did that and
it was absolutely horrible. You were constantly accidentally popping up
windows you didn't want.


At three or for double-clicks per SO, you'd have to work a lot of PSK31
to put a dent in a mouse switch's service lifetime..
I have worn out many a mouse ball which is why I now have an optical mouse,
but I never worn out a switch. Maybe now that I have no ball to wear out and
the switch is the only mechanical part left, the switches will be the first
to go but I think it will take a very long time.

73, Rich - W3ZJ


73,

Dave, AA6YQ

-----Original Message-----
From: Chris BONDE [mailto:ve7hcb@...]
Sent: Friday, December 14, 2001 4:00 PM
To: dxlab@...
Subject: RE: [dxlab] WinWarbler version 2.1.6 is available

Why have the double click at all? Just wears the mouse out twice as
fast. I try to remove all needs thereof. Place the pointer over, it
highlights itself or you highlight, then one click, why two?


SpotCollector 1.1.3 is available

Dave, AA6YQ <dhb@...>
 

This release corrects the "delimiters are stripped from spot notes"
defect that Rich reported below.

To upgrade, see http://www.qsl.net/spotcollector/development.htm --
you'll be downloading
http://www.qsl.net/spotcollector/SpotCollector113Update.exe .

73,

Dave, AA6YQ

-----Original Message-----
From: Richard B. Drake [mailto:rich@...]
Sent: Tuesday, December 04, 2001 6:36 AM
To: dxlab@...
Subject: [dxlab] SpotCollector 112

Dave,

I just posted a spot with a comment that read "S9+ in MD". The telnet
window
shows my spot exactly as I posted it but SpotCollector stripped off the
"+"
and showed "S9 in MD" in the notes field. IS "+" a special character?

----
73, Rich - W3ZJ


WinWarbler version 2.1.8 is available

Dave, AA6YQ <dhb@...>
 

In this release, "period" and "underscore" are used as delimiters when
you double-click on callsigns, names, and QTHs appearing in a receive
pane; "minus" (aka "hyphen") is no longer a delimiter, so clicking on
Jean-Paul should work properly. I didn't test this change; reports that
its working properly would be appreciated.

To upgrade, follow the instructions in
http://www.qsl.net/winwarbler/development.htm -- you'll be downloading
http://www.qsl.net/winwarbler/WinWarbler218Update.exe
<http://www.qsl.net/winwarbler/WinWarbler217Update.exe> .

73,

Dave, AA6YQ

-----Original Message-----
From: Richard B. Drake [mailto:rich@...]
Sent: Thursday, December 13, 2001 2:32 PM
To: dxlab@...
Subject: RE: [dxlab] WinWarbler version 2.1.6 is available

I have a pet peeve on PSK31. It's not WinWarbler's fault Dave, but
perhaps
WinWarbler could fix it. People who type their callsigns as W3ZJ...W3ZJ
and
give their names as Rich...Rich. Do you know what happens when you try
to
click that into the log? :-) We could holler at them and ask them to
stop
that nonsense or we could make "." a delimiter since it doesn't normally
appear in callsigns or names. What do you think?

----
73, Rich - W3ZJ



To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to the Yahoo!
<http://docs.yahoo.com/info/terms/> Terms of Service.