Date   

how many people actually use DXLab applications?

Dave, AA6YQ <dhb@...>
 

There's no way to know how many people actually use these applications; in
fact, there's no way to know exactly how many people downloaded them. The
closest we can come is to know how many unique visitors there were to each
application's download page. Obviously someone can visit a download page and
then decide not to download the application; or they can download an
application and never install it, or install it and never use it. On the
other hand, there appear to be several sites that have chosen to "mirror"
WinWarbler and DXView; who knows how many people have downloaded the
applications from those sites.

At any rate, the "download page" counters serve as a reasonable proxy for
interest level. You can navigate to each download page and scroll to the
bottom to see its counter, or you can look at
http://www.qsl.net/dxlab/status.htm where I've aggregated all of the
download counters. I also added the counter for visits to DXLab's main page.

73 and Happy Holidays to all,

Dave, AA6YQ


Re: SpotCollector 1.1.5

tim holmes <kc8pea@...>
 

thanks a bunch, I sent a message to my friend with a transcript of our chant
and the original message in it, we will see what he can do

----- Original Message -----
From: "Dave, AA6YQ" <dhb@...>
To: <dxlab@...>
Sent: Friday, December 21, 2001 11:30 PM
Subject: RE: [dxlab] SpotCollector 1.1.5


1. Jet (MS Access)

2. Visual Basic 6.0

73,

Dave, AA6YQ
-----Original Message-----
From: tim holmes [mailto:kc8pea@...]
Sent: Friday, December 21, 2001 23:05 PM
To: dxlab@...
Subject: Re: [dxlab] SpotCollector 1.1.5


Dave:

Hi, 2 questions for you

1. what database are you using for spotcollector?

and

2. What language is it programmed in?

TIM
KC8PEA

----- Original Message -----
From: "Dave, AA6YQ" <dhb@...>
To: <dxlab@...>
Sent: Friday, December 21, 2001 10:57 PM
Subject: [dxlab] SpotCollector 1.1.5


> This release properly aligns spot notes in the spot database window.
It
will
> also inform you when an error log has been generated, which previous
> versions failed to do.
>
> Previous releases of SpotCollector were designed to retain spot notes
of
up
> to 29 characters. During my testing of this release, it became
apparent
that
> spot notes can contain up to 30 characters; full-length spot notes
were
> stored absent the 30th character. I know its possible to expand the
> field-size of an existing database -- I can do this using Microsoft
Access,
> for example -- but have so far been unable to do make SpotCollector do
this.
> What I have done is modify SpotCollector so that any new spot database
it
> creates will be capable of storing 30-character spot notes. So you
have
the
> following choices:
>
> 1. decide that you can continue to live without seeing the 30th
character
of
> 30-character spot notes -- e.g. do nothing
>
> 2. realize that the 30th character of a spot note could well contain
> life-or-death information about when or where a valid P5 will next
appear --
> e.g. force SpotCollector to create a new spot database by shutting
down
> SpotCollector, deleting the old spot database, and restarting
SpotCollector.
>
> If you choose the second alternative, you'll find the spot database in
the
> Databases folder within your SpotCollector folder; the spot database
file
is
> named Spots.mdb . When you restart SpotCollector, the spot database it
> creates will handle 30-character spot notes. This new spot database
will
> start out empty -- so what ever you'd previously "recorded" will be
gone.
>
> If you have a spot database containing vital information (like the
P5's
> listening pattern) that you can't lose, then don't delete it -- let me
know
> and I'll explain how to preserve access to it.
>
> To upgrade, see http://www.qsl.net/spotcollector/development.htm --
you'll
> be downloading
http://www.qsl.net/spotcollector/SpotCollector115Update.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/
>
>
>
>


Yahoo! Groups Sponsor



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: SpotCollector 1.1.5

Dave, AA6YQ <dhb@...>
 

1. Jet (MS Access)

2. Visual Basic 6.0

73,

Dave, AA6YQ

-----Original Message-----
From: tim holmes [mailto:kc8pea@...]
Sent: Friday, December 21, 2001 23:05 PM
To: dxlab@...
Subject: Re: [dxlab] SpotCollector 1.1.5


Dave:

Hi, 2 questions for you

1. what database are you using for spotcollector?

and

2. What language is it programmed in?

TIM
KC8PEA

----- Original Message -----
From: "Dave, AA6YQ" <dhb@...>
To: <dxlab@...>
Sent: Friday, December 21, 2001 10:57 PM
Subject: [dxlab] SpotCollector 1.1.5


> This release properly aligns spot notes in the spot database window. It
will
> also inform you when an error log has been generated, which previous
> versions failed to do.
>
> Previous releases of SpotCollector were designed to retain spot notes of
up
> to 29 characters. During my testing of this release, it became apparent
that
> spot notes can contain up to 30 characters; full-length spot notes were
> stored absent the 30th character. I know its possible to expand the
> field-size of an existing database -- I can do this using Microsoft
Access,
> for example -- but have so far been unable to do make SpotCollector do
this.
> What I have done is modify SpotCollector so that any new spot database
it
> creates will be capable of storing 30-character spot notes. So you have
the
> following choices:
>
> 1. decide that you can continue to live without seeing the 30th
character
of
> 30-character spot notes -- e.g. do nothing
>
> 2. realize that the 30th character of a spot note could well contain
> life-or-death information about when or where a valid P5 will next
appear --
> e.g. force SpotCollector to create a new spot database by shutting down
> SpotCollector, deleting the old spot database, and restarting
SpotCollector.
>
> If you choose the second alternative, you'll find the spot database in
the
> Databases folder within your SpotCollector folder; the spot database
file
is
> named Spots.mdb . When you restart SpotCollector, the spot database it
> creates will handle 30-character spot notes. This new spot database will
> start out empty -- so what ever you'd previously "recorded" will be
gone.
>
> If you have a spot database containing vital information (like the P5's
> listening pattern) that you can't lose, then don't delete it -- let me
know
> and I'll explain how to preserve access to it.
>
> To upgrade, see http://www.qsl.net/spotcollector/development.htm --
you'll
> be downloading
http://www.qsl.net/spotcollector/SpotCollector115Update.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/
>
>
>
>


Yahoo! Groups Sponsor



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: SpotCollector 1.1.5

tim holmes <kc8pea@...>
 

Dave:

Hi, 2 questions for you

1. what database are you using for spotcollector?

and

2. What language is it programmed in?

TIM
KC8PEA

----- Original Message -----
From: "Dave, AA6YQ" <dhb@...>
To: <dxlab@...>
Sent: Friday, December 21, 2001 10:57 PM
Subject: [dxlab] SpotCollector 1.1.5


This release properly aligns spot notes in the spot database window. It
will
also inform you when an error log has been generated, which previous
versions failed to do.

Previous releases of SpotCollector were designed to retain spot notes of
up
to 29 characters. During my testing of this release, it became apparent
that
spot notes can contain up to 30 characters; full-length spot notes were
stored absent the 30th character. I know its possible to expand the
field-size of an existing database -- I can do this using Microsoft
Access,
for example -- but have so far been unable to do make SpotCollector do
this.
What I have done is modify SpotCollector so that any new spot database it
creates will be capable of storing 30-character spot notes. So you have
the
following choices:

1. decide that you can continue to live without seeing the 30th character
of
30-character spot notes -- e.g. do nothing

2. realize that the 30th character of a spot note could well contain
life-or-death information about when or where a valid P5 will next
appear --
e.g. force SpotCollector to create a new spot database by shutting down
SpotCollector, deleting the old spot database, and restarting
SpotCollector.

If you choose the second alternative, you'll find the spot database in the
Databases folder within your SpotCollector folder; the spot database file
is
named Spots.mdb . When you restart SpotCollector, the spot database it
creates will handle 30-character spot notes. This new spot database will
start out empty -- so what ever you'd previously "recorded" will be gone.

If you have a spot database containing vital information (like the P5's
listening pattern) that you can't lose, then don't delete it -- let me
know
and I'll explain how to preserve access to it.

To upgrade, see http://www.qsl.net/spotcollector/development.htm -- you'll
be downloading http://www.qsl.net/spotcollector/SpotCollector115Update.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/




SpotCollector 1.1.5

Dave, AA6YQ <dhb@...>
 

This release properly aligns spot notes in the spot database window. It will
also inform you when an error log has been generated, which previous
versions failed to do.

Previous releases of SpotCollector were designed to retain spot notes of up
to 29 characters. During my testing of this release, it became apparent that
spot notes can contain up to 30 characters; full-length spot notes were
stored absent the 30th character. I know its possible to expand the
field-size of an existing database -- I can do this using Microsoft Access,
for example -- but have so far been unable to do make SpotCollector do this.
What I have done is modify SpotCollector so that any new spot database it
creates will be capable of storing 30-character spot notes. So you have the
following choices:

1. decide that you can continue to live without seeing the 30th character of
30-character spot notes -- e.g. do nothing

2. realize that the 30th character of a spot note could well contain
life-or-death information about when or where a valid P5 will next appear --
e.g. force SpotCollector to create a new spot database by shutting down
SpotCollector, deleting the old spot database, and restarting SpotCollector.

If you choose the second alternative, you'll find the spot database in the
Databases folder within your SpotCollector folder; the spot database file is
named Spots.mdb . When you restart SpotCollector, the spot database it
creates will handle 30-character spot notes. This new spot database will
start out empty -- so what ever you'd previously "recorded" will be gone.

If you have a spot database containing vital information (like the P5's
listening pattern) that you can't lose, then don't delete it -- let me know
and I'll explain how to preserve access to it.

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

73,

Dave, AA6YQ


Re: WinWarbler 2.1.8 doesn't echo transmitted characters in panes 1 or 2

Richard B Drake
 

Restoring of the sound level is a great idea. One thing I have noticed Dave
is that there is a difference in sound level output between using PSK and
RTTY. For some reason the RTTY level is lower than PSK and requires
readjustment of the mic gain to obtain proper drive level. I'm not sure if
you have control of this or if it's something that's buried within
pskcore.dll and MMTTY. Another thing is that rigs do not always perform the
same on different bands. For example, both my Omni VI+ and FT-817 require
more drive on 10 meters than on the other bands. Perhaps your preset levels
could take care of this, but keep in mind that it may require remembering
settings for each band and digital mode.

73, Rich - W3ZJ

-----Original Message-----
From: Dave, AA6YQ [mailto:dhb@...]
Sent: Tuesday, December 18, 2001 10:34 PM
To: dxlab@...
Subject: RE: [dxlab] WinWarbler 2.1.8 doesn't echo transmitted
characters in panes 1 or 2


Sounds like a good starting point; I'll try working it in over
the holidays.

The very first release of WinWarbler had a button that activated
the Windows
multimedia mixer -- and it caused some machines to crash. I have
the ability
to programmaticly manage the mixer and thus should be able to do this
directly -- this would mean that WinWarbler could automatically
restore the
appropriate level settings as part of its initialization (for those of you
who find it necessary to change levels between soundcard
applications). This
item has been languishing on the enhancements list for months; perhaps it
too will finally get some attention.

73,

Dave, AA6YQ

-----Original Message-----
From: andy [mailto:music@...]
Sent: Tuesday, December 18, 2001 15:02 PM
To: dxlab@...
Subject: Re: [dxlab] WinWarbler 2.1.8 doesn't echo transmitted
characters in panes 1 or 2


From: "Dave, AA6YQ" <dhb@...>
Oh, the old disapearing text problem; forgot about that one. I'd once
thought about displaying a warning if a display font and a background
color
were identical -- but "identical" wouldn't be good enough most of the
time:
a very dark blue font against a black background, for example, would
also be
invisible. Anyone know an algorithm for determining whether a pair of
RGB
colors are too "close" to be distinguised by the (normal) human eye?
Just off the top of my head, you could require that at least one of R,G
or B in the font colour is at least 30% of full scale (or whatever
works best at all brightnesses) away from the corresponding value in the
background colour.

HTH

Thanks for your wonderful software by the way, and for the impressive
support.

Suggestion:
How about a button to pop up the Windows mixer?

Cheers.

Andy.



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/



making telnet cluster N3RA compatible with SpotCollector

Dave, AA6YQ <dhb@...>
 

Fab IK4VYX (author of DXTelnet) reports that N3RA uses AR cluster software.
You can direct AR cluster to disable the non-standard prefix info with the
command

set/nodxsqth

Evidentally, there several other cluster variants that do not conform to the
"standard" spot format - dxspider, wincluster, and possibly dxnet. Like AR
cluster, some of these may have commands that force "standard" spot format.
If you have an experience like Tim's, where spots appear in the telnet
cluster window but not in the database, this could easily be the problem.

73,

Dave, AA6YQ


Re: WinWarbler 2.1.8 doesn't echo transmitted characters in panes 1 or 2

Dave, AA6YQ <dhb@...>
 

Agreed. I was planning to raise a warning dialog that could be dismissed by
clicking an OK button, but permit the user to continue operation with the
selected font and background colors.

I hadn't thought about using the desktop color scheme. It might be a good
source of default values, specifying how things should look when the program
is running for the very first time. But you're right, there's definitely not
enough information there to suggest, for example, which three colors to use
for received text in each of the three channels.

73,

Dave, AA6YQ

-----Original Message-----
From: muck@... [mailto:muck@...]
Sent: Tuesday, December 18, 2001 15:46 PM
To: dxlab@...
Subject: Re: [dxlab] WinWarbler 2.1.8 doesn't echo transmitted characters
in panes 1 or 2


On Dec 18, 8:02pm, "andy" wrote:
}
} > From: "Dave, AA6YQ" <dhb@...>
}
} > Oh, the old disapearing text problem; . . .
} > . . . Anyone know an algorithm for determining
} > whether a pair of RGB colors are too "close" to
} > be distinguised by the (normal) human eye?
}
} Just off the top of my head, you could require that at
} least one of R,G or B in the font colour is at least 30%
} of full scale (or whatever works best at all brightnesses)
} away from the corresponding value in the background colour.


I don't have a solution, but I do have a caveat. Some of us
have varying degrees of color blindness. So, solutions that
may work for some may not work for others. Trying to display a
"warning" is a good idea, but let those of us with weird problems
ignore the warning and forge ahead.

For example, I often encounter cyan/blue and red/black color
schemes that seem to work for most people, but are bad for me.
The red/black combo is practically invisible. On the otherhand,
I've found that the green/red color that I use is extremely
hard for others to read.

You might consider somehow tying your system into the user's
desktop color scheme. Presumably, they already have that set up
appropriately; which should make the rest easy. That's assuming
that there are enough differing variations in the desktop
theme to cover all the stuff you're doing in the program.
I'm not sure there is.

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: WinWarbler 2.1.8 doesn't echo transmitted characters in panes 1 or 2

Dave, AA6YQ <dhb@...>
 

Sounds like a good starting point; I'll try working it in over the holidays.

The very first release of WinWarbler had a button that activated the Windows
multimedia mixer -- and it caused some machines to crash. I have the ability
to programmaticly manage the mixer and thus should be able to do this
directly -- this would mean that WinWarbler could automatically restore the
appropriate level settings as part of its initialization (for those of you
who find it necessary to change levels between soundcard applications). This
item has been languishing on the enhancements list for months; perhaps it
too will finally get some attention.

73,

Dave, AA6YQ

-----Original Message-----
From: andy [mailto:music@...]
Sent: Tuesday, December 18, 2001 15:02 PM
To: dxlab@...
Subject: Re: [dxlab] WinWarbler 2.1.8 doesn't echo transmitted
characters in panes 1 or 2


From: "Dave, AA6YQ" <dhb@...>
Oh, the old disapearing text problem; forgot about that one. I'd once
thought about displaying a warning if a display font and a background
color
were identical -- but "identical" wouldn't be good enough most of the
time:
a very dark blue font against a black background, for example, would
also be
invisible. Anyone know an algorithm for determining whether a pair of
RGB
colors are too "close" to be distinguised by the (normal) human eye?
Just off the top of my head, you could require that at least one of R,G
or B in the font colour is at least 30% of full scale (or whatever
works best at all brightnesses) away from the corresponding value in the
background colour.

HTH

Thanks for your wonderful software by the way, and for the impressive
support.

Suggestion:
How about a button to pop up the Windows mixer?

Cheers.

Andy.



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 2.1.8 doesn't echo transmitted characters in panes 1 or 2

muck@...
 

On Dec 18, 8:02pm, "andy" wrote:
}
} > From: "Dave, AA6YQ" <dhb@...>
}
} > Oh, the old disapearing text problem; . . .
} > . . . Anyone know an algorithm for determining
} > whether a pair of RGB colors are too "close" to
} > be distinguised by the (normal) human eye?
}
} Just off the top of my head, you could require that at
} least one of R,G or B in the font colour is at least 30%
} of full scale (or whatever works best at all brightnesses)
} away from the corresponding value in the background colour.


I don't have a solution, but I do have a caveat. Some of us
have varying degrees of color blindness. So, solutions that
may work for some may not work for others. Trying to display a
"warning" is a good idea, but let those of us with weird problems
ignore the warning and forge ahead.

For example, I often encounter cyan/blue and red/black color
schemes that seem to work for most people, but are bad for me.
The red/black combo is practically invisible. On the otherhand,
I've found that the green/red color that I use is extremely
hard for others to read.

You might consider somehow tying your system into the user's
desktop color scheme. Presumably, they already have that set up
appropriately; which should make the rest easy. That's assuming
that there are enough differing variations in the desktop
theme to cover all the stuff you're doing in the program.
I'm not sure there is.


Re: WinWarbler 2.1.8 doesn't echo transmitted characters in panes 1 or 2

andy <music@...>
 

From: "Dave, AA6YQ" <dhb@...>
Oh, the old disapearing text problem; forgot about that one. I'd once
thought about displaying a warning if a display font and a background
color
were identical -- but "identical" wouldn't be good enough most of the
time:
a very dark blue font against a black background, for example, would
also be
invisible. Anyone know an algorithm for determining whether a pair of
RGB
colors are too "close" to be distinguised by the (normal) human eye?
Just off the top of my head, you could require that at least one of R,G
or B in the font colour is at least 30% of full scale (or whatever
works best at all brightnesses) away from the corresponding value in the
background colour.

HTH

Thanks for your wonderful software by the way, and for the impressive
support.

Suggestion:
How about a button to pop up the Windows mixer?

Cheers.

Andy.


Telnet Cluster N3RA doesn't work with SpotCollector

Dave, AA6YQ <dhb@...>
 

Tim reported that DX spots were appearing in his Telnet Cluster window, but
few were appearing in the Spot Database. We conducted a real-time debugging
session using a private #CQDX link. Turns out he was using a cluster that
adds additional information (DXCC prefixes for both the DX and the spotting
station) to each spot -- Spot Collector is unable to parse these spots, so
they don't appear in the database.

Its not obvious how to reliably detect this new format, and I am reluctant
to add code that checks for specific cluster names (because they eventually
will change) or requires the user to check a "innovative spot format #1" box
(there are already too many configuration settings in this application).
Fortunately, there are plenty of clusters out there that use the standard
format, so I won't consider this a pressing problem unless someone presents
logic to the contrary.

Thanks for reporting the problem and taking the time to help me track it
down, Tim!

73,

Dave, AA6YQ


Re: Spot Collector Question

tim holmes <kc8pea@...>
 

Dave:

I can see the original 27, but not the new incomming spots

TIM

----- Original Message -----
From: "Dave, AA6YQ" <dhb@...>
To: <dxlab@...>
Sent: Monday, December 17, 2001 11:17 PM
Subject: RE: [dxlab] Spot Collector Question


OK, there are 27 entries in your spot database but you see no entries in
the
Spot Database window. The Filter is set to "All", so that's not the
problem.
Did you by chance adjust font colors on the Config window's Display Fonts
tab? Click the Spot Database sub-tab and verify that none of the colors
are
"white" (which would make them hard to see against a white backgroun).

73,

Dave, AA6YQ
-----Original Message-----
From: tim holmes [mailto:kc8pea@...]
Sent: Monday, December 17, 2001 22:58 PM
To: dxlab@...
Subject: Re: [dxlab] Spot Collector Question


Dave:

> Tim, take a look at the Filter panel along the bottom of the Spot
Database
> window. Is the caption "Filter: All" ?

YES

If not, click the X button in the
> panel - this will set the filter so that you see everything in the
spot
> database.
>
> If that's not it, click the Config button and select the Spot Database
tab.
> There's a panel in the middle of the right side of the window whose
name
is
> Size Limit -- its followed by the size of the Spot Database. What is
the
> current Spot Database size?

27 Entries

> If the Spot Database Size is 0, the examine the Controls panel in the
upper
> left corner of the window. The Maximum age of valid incoming spots
should
be
> set to a reasonable number of minutes -- say 15.
>
> Let me know if any of the above helps; if not we'll take it from
there.
>
> 73,
>
> Dave, AA6YQ
>



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: Spot Collector Question

Dave, AA6YQ <dhb@...>
 

OK, there are 27 entries in your spot database but you see no entries in the
Spot Database window. The Filter is set to "All", so that's not the problem.
Did you by chance adjust font colors on the Config window's Display Fonts
tab? Click the Spot Database sub-tab and verify that none of the colors are
"white" (which would make them hard to see against a white backgroun).

73,

Dave, AA6YQ

-----Original Message-----
From: tim holmes [mailto:kc8pea@...]
Sent: Monday, December 17, 2001 22:58 PM
To: dxlab@...
Subject: Re: [dxlab] Spot Collector Question


Dave:

> Tim, take a look at the Filter panel along the bottom of the Spot
Database
> window. Is the caption "Filter: All" ?

YES

If not, click the X button in the
> panel - this will set the filter so that you see everything in the spot
> database.
>
> If that's not it, click the Config button and select the Spot Database
tab.
> There's a panel in the middle of the right side of the window whose name
is
> Size Limit -- its followed by the size of the Spot Database. What is the
> current Spot Database size?

27 Entries

> If the Spot Database Size is 0, the examine the Controls panel in the
upper
> left corner of the window. The Maximum age of valid incoming spots
should
be
> set to a reasonable number of minutes -- say 15.
>
> Let me know if any of the above helps; if not we'll take it from there.
>
> 73,
>
> Dave, AA6YQ
>



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: Spot Collector Question

tim holmes <kc8pea@...>
 

Dave:

Tim, take a look at the Filter panel along the bottom of the Spot Database
window. Is the caption "Filter: All" ?
YES

If not, click the X button in the
panel - this will set the filter so that you see everything in the spot
database.

If that's not it, click the Config button and select the Spot Database
tab.
There's a panel in the middle of the right side of the window whose name
is
Size Limit -- its followed by the size of the Spot Database. What is the
current Spot Database size?
27 Entries

If the Spot Database Size is 0, the examine the Controls panel in the
upper
left corner of the window. The Maximum age of valid incoming spots should
be
set to a reasonable number of minutes -- say 15.

Let me know if any of the above helps; if not we'll take it from there.

73,

Dave, AA6YQ


Re: Spot Collector Question

Dave, AA6YQ <dhb@...>
 

Tim, take a look at the Filter panel along the bottom of the Spot Database
window. Is the caption "Filter: All" ? If not, click the X button in the
panel - this will set the filter so that you see everything in the spot
database.

If that's not it, click the Config button and select the Spot Database tab.
There's a panel in the middle of the right side of the window whose name is
Size Limit -- its followed by the size of the Spot Database. What is the
current Spot Database size?

If the Spot Database Size is 0, the examine the Controls panel in the upper
left corner of the window. The Maximum age of valid incoming spots should be
set to a reasonable number of minutes -- say 15.

Let me know if any of the above helps; if not we'll take it from there.

73,

Dave, AA6YQ

-----Original Message-----
From: tim holmes [mailto:kc8pea@...]
Sent: Monday, December 17, 2001 22:37 PM
To: dxlab@...
Subject: [dxlab] Spot Collector Question


Hi:

I am using spotcollector 1.0.6, and I have it successfully set up and
receiving spots in the cluster window, but for some reason they are not
showing up in the database. I am not sure what I am doing wrong, but I
could sure use some help

TIM HOLMES
KC8PEA


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.


Spot Collector Question

tim holmes <kc8pea@...>
 

Hi:

I am using spotcollector 1.0.6, and I have it successfully set up and
receiving spots in the cluster window, but for some reason they are not
showing up in the database. I am not sure what I am doing wrong, but I
could sure use some help

TIM HOLMES
KC8PEA


Re: [psk31] FT101EE Frequncy Offset

Dave, AA6YQ <dhb@...>
 

WinWarbler provides just such an offset, located in the Transmitter panel on
the Configuration window's Soundcard PSK tab. If your transmitter's
frequency is 100 hz lower than your receiver's, set the offset to -100. This
value is retained between WinWarbler sessions. Please let me know how it
goes...

73,

Dave, AA6YQ

-----Original Message-----
From: psk31-admin@...
[mailto:psk31-admin@...]On Behalf Of Tom and Joanna
Sent: Monday, December 17, 2001 18:30 PM
To: psk31@...
Subject: [psk31] FT101EE Frequncy Offset


I managed to make a few contacts on PSK-31 with tthe FT101EE over the
weekend,
what an interesting mode. The FT101EE seemed plenty stable as far as drift
goes, however one problem is that there is a frequncy offset between tx and
rx, the tx is approximately 100 hertz lower than the rx. I have Hamscope,
Winwarbler, and Winpskse. Is there a way to permanatly set an offset in the
software to correct this? I used the Winwarbler the most and really like it,
however I loaded the Winpskse later and it looks promising also. Any
thoughts
on this would be appreciated.
Tom N7BYD
_______________________________________________
Keep in mind that only registered email addresses can post in the list.
Psk31 WWW Site at http://aintel.bi.ehu.es/psk31.html
Psk31 list info at: http://aintel.bi.ehu.es/mailman/listinfo/psk31


Re: SpotCollector 1.1.4 is available

Dave, AA6YQ <dhb@...>
 

1.1.4 is a development release, as described in
http://www.qsl.net/spotcollector/development.htm . At the moment, there is
one open defect; see http://www.qsl.net/spotcollector/defects.htm for
details. SpotCollector, like all DXLab applications, is freeware. In the
sense that there is no "for sale" version with more functionality, 1.1.4 is
"fully functional"; on the other hand, I'll be adding functionality to
SpotCollector for quite awhile.

73,

Dave, AA6YQ

-----Original Message-----
From: tim holmes [mailto:kc8pea@...]
Sent: Monday, December 17, 2001 18:17 PM
To: dxlab@...
Subject: Re: [dxlab] SpotCollector 1.1.4 is available


HI, Is this a "beta" release, a "Release Candidate" or a full up
functional
release

TIM
----- Original Message -----
From: "Dave, AA6YQ" <dhb@...>
To: <dxlab@...>
Sent: Monday, December 17, 2001 12:25 AM
Subject: [dxlab] SpotCollector 1.1.4 is available


> This release does a more compete job of correcting the "delimiters are
> stripped from spot notes" defect than 1.1.3 -- hopefully I've got all
the
> cases covered now.
>
> To upgrade, see http://www.qsl.net/spotcollector/development.htm --
you'll
> be downloading
http://www.qsl.net/spotcollector/SpotCollector114Update.exe
.
>
> 73,
>
> Dave, AA6YQ
>
>
> -----Original Message-----
> From: Richard B. Drake [mailto:rich@...]
> Sent: Saturday, December 15, 2001 18:10 PM
> To: dxlab@...
> Subject: RE: [dxlab] SpotCollector 1.1.3 is available
>
>
> 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/
> >
> >
> >
>
>
>
> 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/
>
>
>
>


Yahoo! Groups Sponsor



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: SpotCollector 1.1.4 is available

tim holmes <kc8pea@...>
 

HI, Is this a "beta" release, a "Release Candidate" or a full up functional
release

TIM

----- Original Message -----
From: "Dave, AA6YQ" <dhb@...>
To: <dxlab@...>
Sent: Monday, December 17, 2001 12:25 AM
Subject: [dxlab] SpotCollector 1.1.4 is available


This release does a more compete job of correcting the "delimiters are
stripped from spot notes" defect than 1.1.3 -- hopefully I've got all the
cases covered now.

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

73,

Dave, AA6YQ


-----Original Message-----
From: Richard B. Drake [mailto:rich@...]
Sent: Saturday, December 15, 2001 18:10 PM
To: dxlab@...
Subject: RE: [dxlab] SpotCollector 1.1.3 is available


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/
>
>
>



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/