Support Questions
Q: I have a problem. How do I get support?
A: Support is provided through the user community through the support forum. Generally
a question can be answered by reading through the previous postings or by an expert
user. Shortwave Log is free. And the price for that is simply that there is no formal
support.
Installation
Q: What are the recommended system requirements?
A:
- Windows 7 (highly prefered)
- Windows Vista
- Windows XP (not recommended)
- 1 GHz or faster processor
- 512 MB or more of RAM
- Approximately 1GB of available hard-disk space
Q: Does SWLog run under the 64-bit version of Windows 7 or Windows Vista?
A: Yes. Nothing special is necessary. And under a 64-bit operating system, the installation
package will install the 64-bit version of SQL Server.
Q: Does SWLog run on a Netbook?
A: Absolutely! As with all applications on a netbook, performance is better with
Windows 7 and 2GB of RAM. Windows XP or Windows Vista is not recommended for netbooks.
Q: Does anything else need to be downloaded?
A: All installation tasks are handled by the installation package. Any items that
are not already installed on the computer will automatically be downloaded. Note
that any software that may be automatically downloaded comes from Microsoft or a
Microsoft partner (e.g. the Crystal Reports runtime from Business Objects). No spyware
or other malicious software would ever be downloaded. Please feel free to put the
installation package through as many A/V and malware scanners as you desire.
N.B. In some cases, especially under Windows XP, the installation package cannot
install Microsoft SQL Server Express due to the computer missing key prequesite
components. This typically manifests itself with an "Error 26" message. If this
occurs, a plethora of resources are available on the web to ensure that the required
components (most often Windows Installer 4.5 and XP SP3) are installed.
Q: What version of .NET does Shortwave Log use?
A: .NET 3.5 SP1. SWLog will move to .NET 4.0 in the April/May 2010 timeframe soon
after the release of Visual Studio 2010.
The Logbook
Q: What is this blinking icon? How do I get rid of it?
A: The blinking icon denotes an error in the field. The source of this error is
most likely an empty field or malformed data, such as entering a letter in the kHz/MHz
field. The error condition must be cleared to proceed.
Q: Why do I have to enter data top-down? Why can't I add information the way I want
to and have the program magically interpret my intentions?
A: Shortwave Log is designed to auto-populate frequency, station, transmitter, and
power information from EIBI, HFCC, PTSW, AOKI, ADDX, other databases, and your personal
frequency databases. It expects this information to be added in a specific order,
and that order that is top-down. For example, entering the transmission start and
stop times is crucial to obtain accurate matches and recommendations for transmissions
during that particular time frame.
Q: Why is a particular field required? Why can't I leave it blank?
A: This is a bit of an oversimplification, but still valid: a log entry could be
added to the database, but if certain fields are blank, none of the reports would
"see" the entry, effectively sending the log entry to the database equivalent of
Bermuda Triangle. Some fields (e.g. Mode, Transmission Type) can be blank, but Shortwave
will convert the blanks to "Unknown" when the record is added to the database.
Q: When the program searches for matches, I get several results from [Logbook] that
do not match the date/time. Why is this?
A: When searching, all logbook entries for a frequency regardless of time
are returned. Say that a broadcast occurs from 0000 to 0100 GMT. You have previously
logged this station from 0010 to 0015 GMT and 0022 to 0035 GMT. For your third log
of this station, the time frame is 0040 to 0050 GMT. If time were included in the
search, the entry would not be listed as an option. Thus all [Logbook] entries are
matches for the frequency, regardless of time. Note that there is a System Settings
option to limit the number of logbook entries that are searched. This can limit
the search to only recent logs, e.g. those within three months, and will prevent
old logs, like the BBC on 6175 or 9590 kHz (remember when the BBC actually transmitted
on shortwave?), from showing as possible matches. (What? You don't have all your
old paper logs from the 1970s and 1980s entered yet? Well, you have some work to
do!)
Q: Why are political boundaries used for countries? Why can't I use the fake, made-up
radio countries like the ARRL, DXCC, or the NASWA Country List?
A: Alaska and Hawaii are not countries! They are part of the United States of America!
The notion of a radio country is a vane and misguided concept. Shortwave Log does
not support the folly of fake radio countries at least for shortwave and mediumwave
logs. Sadly, in order to support integration with eQSL.cc for electronic amateur
radio QSLs, the idiotic DXCC list had to be integrated into the amateur
radio log module as eQSL.cc codes each QSL with a DXCC country code. But this intgration
is, and will be, limited to the amateur radio side of the program. The shortwave
side will continue to use the political list that is published by the United States
Department of State and that is also used by the CIA World Fact Book. The DXCC country
list is used for Amateur logs.
Q: Why can't I use my own names for countries? For example, why do I have to use
United Kingdom instead of Great Britain?
A: Shortwave Log supports many different types of external databases. Some databases
call the U.K. the United Kingdom, some Great Britain, and some England (even if
the transmitter is in Wales, Scotland, or Northern Ireland). In order to make all
these databases coexist, Shortwave Log maps all these various permutations to a
master country list, which is based upon the spellings in the CIA World Factbook,
which in turn is based upon the official United States Department of State spellings
for each country. Shortwave Log does a lot of behind the scenes magic to make HFCC,
ILGRadio, Fineware, Prime Time Shortwave, NIMA, FCC AM, FCC HF, FCC Amateur, and
Canadian Amateur to work as a single, unified database. In order to make everything
work, a master country list is required.
That being said, it is quite simple to write a SQL command to update all of the
various databases where the country name is used. That command would need to be
executed after each import of an external database. Doing so would also likely cause
problems with uploading logs to the Community.
Reports
Q: Why do the reports show up in kHz even though I've selected MHz?
A: All frequencies are stored and manipulated in the database as kHz. The MHz option
is merely a cosmetic setting that divides by 1,000 when a frequency needs to be
displayed on the screen. The reporting engine (Crystal Reports) is a separate product
and pretty much acts as a black box: the report is written with a wizard and any
post-wizard configuration is quite difficult. At present, the reports merely display
the frequencies in the manner they're stored in the database: in kHz. See the Programmer's
Reference page for links to third-party report writers. Any ODBC- or OLEDB-compliant
reporting tool can be used to generate reports. What comes with the application
is only a starting point.
Q: Why do the reports appear in English instead of my chosen language?
A: At this time only the user interface has been made multi-lingual. Changing the
reports is much more involved. As with the above answer, you can use pretty much
any reporting tool to create your own reports.
Propagation, Sunrise/Sunset, & TerraServer-USA Utilities
Q: Why are some of these locations wrong? For example, why are Delano, California
and Greenville, North Carolina listed as being in Greece?
A: Garbage in = garbage out. Shortwave Log merely reports on the data that was entered
or imported into it. For example, the now-defunct ILGRadio database was notorious
for listing the home country name of the broadcaster instead of the country where
the transmitter or relay station was located. This would result in items like Sackville,
U.K.; Limasol, U.K., Delano, U.K., Singapore, U.K., etc. This happens from time
to time with the current frequency lists as well. All of the transmitter sites should
be regarded as recommendations, for they are only as good as the underlying data.
QSL Functions
Q: What is the recommended resolution at which to scan QSL cards?
A: Scans at 300 dpi result in images between 300k and 700k in size. If the purpose
is to view QSL cards on the screen and not to print, then a resolution or 72 dpi
will suffice.
Q: What is eQSL.cc? Is it required?
A: eQSL.cc is a great on-line QSL service for amateur radio. While Shortwave Log
integrates with eQSL.cc, membership in the service is not required to use the QSL
functions of the program.
Q: How do I use eQSL.cc? How do I synchronize my logbook with eQSL.cc?
A: Integration is quite easy.
Step 1: Options / eQSL.cc / Upload. This will create an ADIF file (extension
.ADI) of any logs that have not yet been uploaded to eQSL.cc. The first time that
this command is run, the entire amateur radio logbook will be processed. On subsequent
runs, only new logs will be processed.
Step 2: Login to eQSL.cc and upload the ADIF file.
Step 3: Options / eQSL.cc / Download (Import). A hyperlink will appear. Click
the hyperlink to automatically generate an ADIF file from eQSL.cc that contains
a listing of all eQSLs in their system. eQSL.cc allows for this file to be downloaded
with either and .ADI or .TXT extension. Either is fine. Download the file and save
it to the hard drive. Then import its contents into SWLog.
Step 4: Options / eQSL.cc / Manage QSLs. This is the tedious part and is
targeted to improve with later versions. With the Manage QSLs form open, also open
Internet Explorer (Firefox generates an error in this step). Using IE, view your
inbox on eQSL.cc. This will display all eQSL cards that have not yet been viewed.
As you view each eQSL card, select the matching logbook entry in the form, then
drag-n-drop the picture into the window in the Manage QSLs form. (This is what only
works with IE.) An automatic download is targeted for a future release.
Miscellaneous
Q: Why does the clock pause for several seconds then start again?
A: The clock is coded to run only when the program is idle. If Shortwave Log is
processing data, importing, printing, etc., the clock will not be updated until
the program becomes idle again.
Q: Is Shortwave Log available in any other languages than English?
A: Yes - Norwegian, Italian, Spanish, Russian, German, Portuguese (Iberian and Brazilian
variants), Swedish, and French; however, none of the documentation (like this FAQ)
has been translated.
Backup & Restore
Q: How do I backup my logs?
A: Search the web for "backup SQL Server Express".
Q: How do I restore my logs?
A: Search the web for "restore SQL Server database".
Q: My computer has crashed and/or I wish to move my logs to another computer. How
do I do this?
A: The answer is pretty much the same as above, but in reverse. Neither this FAQ
nor this program is meant to be a primer on SQL Server. There is ample information
about this on the Internet.
Radio Control Server (RCS)
Q: Why doesn't the Radio Control Server support all the functions of my receiver?
A: Radio Control Server differs from traditional radio control software in that
it has two primary functions:
1. Integrate with Shortwave Log, thereby aiding the logging process.
2. Support control over TCP/IP, thereby allowing remote control over your home network,
the Internet, or the web via the RCSweb application.
It is not a goal of the program to support every single function for every single
receiver. The goal is to support a basic subset of commands to allow for general
tuning. If you need a specific feature that is not available in the Radio Control
Server program, use the software that came with your receiver. It should be noted
that in the years that Radio Control Server has been available, the policy of providing
a basic level of functionality -- but with SWLog and Network/Web integration --
has proved to be quite positive. Radio Control Server will never be the best software
available for your particular radio, but it is the best with respect to integrating
into Shortwave Log!
Q: While Radio Control Server does not support my receiver, Ham Radio Deluxe (HRD)
does. Can I use HRD with Shortwave Log?
A: Yes. Choose Ham Radio Deluxe as the receiver type in the Settings form in the
Radio Control Server. Choose the appropriate instance of HRD. If you are trying
to connect to the first running copy of HRD, choose HRD_RADIO_000. If you happen
to have ten receivers and ten copies of HRD running at the same time and you wish
to connect to the tenth instance of HRD, choose HRD_RADIO_009. Although it's a pretty
safe assumption that almost everyone will be connecting th HRD_RADIO_000 or HRD_RADIO_001.
Note that HRD only provides for a very limited feature set. Only mode and frequency
can be set. HRD does not provide for filters, passband, volume, squelch, or anything
else to be set remotely. To set those features, you must use HRD itself. Nonetheless,
the integration is sufficient to allow features such as What's Playing Now to automatically
tune the receiver via HRD, to have the SINPO value and frequency automatically populated
when adding a new log, and it also allows any receiver supported by HRD to be published
on the Internet via RCSweb.
Q: Can I use a USB-to-serial port adapter?
A: Absolutely, although some brands work better than others. The TrippLite (formerly Keyspan) USA-19HS adapter is by far
the best adapter and is highly recommended by the author. Another good choice is
the IOGear GUC232A. Another advantage with both of these adapters
is that they work perfectly under 64-bit Windows.
Q: Why can't I read or write the memories in my receiver?
A: Because the Radio Control Server supports so many different types of receivers,
a software-based memory model is used. 1000 memories are available to every recevier,
regardless of whether a particular receiver can support that many memories in hardware
or not. (The theoretical limit on the number of memories is approximately 2 million;
however, no one has yet expressed a need for more than 1000.) Another advantage
of using software-based memories is that they can span receivers. Memories can be
manipulated on the AOR 7030 and 7030+ receivers.
Q: My receiver is either not listed or is listed as "as-is". Why is that the case?
A: Only those receivers that I has personally tested are listed as official, supported
receivers. If you would like to loan me your receiver for a couple of weeks, I could
test it and then declare it offically supported. No one has yet offered to do this,
so these receivers remain "as-is".
Q: My receiver is either not listed or is listed as "as-is" and is not working. How
do I my receiver added or fixed?
A: The only option is to loan your friendly author your receiver for a couple of
weeks. No more receivers will be added without having physical access. It's just
too hard and time consuming.
Q: I am unable to get the radio control module to tune the radio when I go into the
What's Playing Now function. What's going on?
A: You most likely have a personal fireall installed. The radio control module listens
for connections on TCP port 21687. You will need to open this port on your PC. Try
using the RCS.EXE command-line application to test. Issue a query (RCS /Q). If you
cannot get a simple query to work, then there is definately a communication problem
over TCP port 21687.
Q: Radio Control Server hangs. What do I do?
A: The Radio Control Server can hang for a variety of reasons: wrong port, wrong
baud, wrong radio type, forcing CTS/RTS, not forcing CTS/RTS, etc. 1. Use Task Manager
to kill the RadioControl.exe process. 2. Open a command prompt and change to C:\SWLOG
3. Start RadioControl.exe with a paramater --> "radiocontrol x" Any parameter
will do. The program will then reset itself to demonstration mode and let you pick
a radio and COM port.
Q: Why does Radio Control Server hang? If there is an error, why is it not trapped?
A: It is a limitation of the technology. The .NET Framework has no support for serial
communication. Thus all serial port communication is accomplished via P/Invoke calls
to the Win32API. Calling unmanaged code is fraught with peril in that if an error
occurs, the program may hang. In short, if there's a problem with the COM port,
the program will hang.
Q: Why is the Windows Media Encoder used?
A: The Microsoft encoder is free and very simple to set up. Thus it is used in the
examples and documentation. Any streaming audio encoder that can stream WMA or MP3
audio can be used.
Q: What ports are necessary to get my recevier to work with SWLog Online?
A:
- 943 - Silverlight Policy Server
- 4502 - Data Exchange
- 21687 - Legacy .NET Remoting port, still used to communicate between SWLog and RCS
- 21688 - Audio stream