After much sound, fury, hair pulling, and bad language, the results are in.
Programs that recognize the W7 app data path variable, keep their data outside the program file tree, and work when installed to the default directory (Program Files (x86)):
FLdigi (Note 1)
JVComm32
TrueTTY
Programs that should probably be installed in a different folder you create yourself (I called mine "Radio"):
DSCdecoder (Note 2)
MultiPSK (3)
PC-ALE (4)
PC-HFDL (5)
POSFIX
Spectran
1) Created files under "Users," not in program folder.
2) ITU lookup won't work installed under Program Files (x86).
3) Some confusion over whether or not to run INSTAL.exe after unzipping.
4) Do not leave "create desktop icon" checked. Create shortcut manually in program's home directory, and drag to desktop. In fact, do this for all these programs.
5) Go into ground station file, change "AUCKLAND - NEW ZEALAND" to "AUCKLAND - NZ" due to a bug unrelated to platform.
As always, your results will be different. That's what worked here.
Showing posts with label windows. Show all posts
Showing posts with label windows. Show all posts
Monday, January 16, 2012
Saturday, January 14, 2012
Ham Radio Software Meets Windows 7 #3: Debugging PC-ALE
After uninstalling MARS-ALE and removing various droppings still found throughout my computer, I bravely set out to see what PC-ALE would do in a home directory outside the Program Files (x86) or the virtual machine ("XP Mode"). Others had reported success when installed in this manner.
The version I'd been using is in the 1.07x cycle. I had the installers on backups. The files are not on HFLINK, but can be found elsewhere. You install the FI version, then drop the unzipped UD .exe file over the original .exe in your installation. Then you copy in your .qrg files. You DID back up your .qrg, right?
Scanning will have to wait until a compatible USB-serial adapter is obtained. Right now I'm only parking on frequencies.
Here are some issues:
#1: Do not check the "Create Desktop Icon" box in the installer. This creates an incorrect path, which causes PC-ALE to write the files it needs for proper operation to the desktop instead of its home folder. It is then unable to find them there.
Instead, go to the home directory and right-click ALE.exe. Drop down and hit "Create Shortcut," then move the resulting new shortcut icon to the desktop. This solves the problem. The files are created in the right place.
#2. The problem encountered with the input being pure noise seems to have fixed itself with the install to my custom directory. PC-ALE is finding the right input now. "First light" here was J14, 003, and D08 sounding on 15867. BER and S/N were well above minimums for high confidence decode.
#3: For some inexplicable reason, PC-ALE likes to set the gain of Line In to zero at startup and shutdown. This causes the bars/sync to vanish altogether, because there's no signal. Do W7's silly sound driver and turn it back up. The bars/sync should appear, and you should be decoding ALE. This issue fixes itself after running the program a couple of times. Presumably, the default level finally gets set to the figure in your 141A config screen.
#4: It is said that MARS-ALE is actually better for receive-only than PC-ALE. This could be the case. MultiPSK, however, is better than both of them for receive, though equally user-inscrutable. It will scan after you do the developer's weird payment procedure and get a license.
#5: ALL MILEAGE WILL VARY!!!!! We are dealing with computers, after all. If you get a total bomb job, try asking the experts on the HFLINK group at Yahoo.
The version I'd been using is in the 1.07x cycle. I had the installers on backups. The files are not on HFLINK, but can be found elsewhere. You install the FI version, then drop the unzipped UD .exe file over the original .exe in your installation. Then you copy in your .qrg files. You DID back up your .qrg, right?
Scanning will have to wait until a compatible USB-serial adapter is obtained. Right now I'm only parking on frequencies.
Here are some issues:
#1: Do not check the "Create Desktop Icon" box in the installer. This creates an incorrect path, which causes PC-ALE to write the files it needs for proper operation to the desktop instead of its home folder. It is then unable to find them there.
Instead, go to the home directory and right-click ALE.exe. Drop down and hit "Create Shortcut," then move the resulting new shortcut icon to the desktop. This solves the problem. The files are created in the right place.
#2. The problem encountered with the input being pure noise seems to have fixed itself with the install to my custom directory. PC-ALE is finding the right input now. "First light" here was J14, 003, and D08 sounding on 15867. BER and S/N were well above minimums for high confidence decode.
#3: For some inexplicable reason, PC-ALE likes to set the gain of Line In to zero at startup and shutdown. This causes the bars/sync to vanish altogether, because there's no signal. Do W7's silly sound driver and turn it back up. The bars/sync should appear, and you should be decoding ALE. This issue fixes itself after running the program a couple of times. Presumably, the default level finally gets set to the figure in your 141A config screen.
#4: It is said that MARS-ALE is actually better for receive-only than PC-ALE. This could be the case. MultiPSK, however, is better than both of them for receive, though equally user-inscrutable. It will scan after you do the developer's weird payment procedure and get a license.
#5: ALL MILEAGE WILL VARY!!!!! We are dealing with computers, after all. If you get a total bomb job, try asking the experts on the HFLINK group at Yahoo.
Ham Radio Software Meets Windows 7 #2: DSCdecoder FIXED!
OK. Thanks to the informative forum at HF-ALE, I have the intelligence that Windows 7 security prevents programs from modifying certain files in their own home folders and subdirectories therein. Variable data is supposed to be stored in User Data, App Data, or someplace like that. These old ham programs don't do that.
The advice was given to create a folder OUTSIDE Program Files (x86) for old radio software that won't work any other way, and install these old programs there. While they were talking about PC-ALE, this worked for DSCdecoder. The ITU lookup is now working and the program is as far as I'm concerned now operating properly. The display screen changes, and the data is written to the daily log and shipid.txt.
While I was at it, I moved the logging folder to My Documents, since I look at it a lot. This is done with Options > Directories > Log File.
I wouldn't recommend this installation procedure for every single new program, since it does defeat a security feature built into W7. This is for the care and feeding of these old radio sharewares. Make sure you trust the software.
The advice was given to create a folder OUTSIDE Program Files (x86) for old radio software that won't work any other way, and install these old programs there. While they were talking about PC-ALE, this worked for DSCdecoder. The ITU lookup is now working and the program is as far as I'm concerned now operating properly. The display screen changes, and the data is written to the daily log and shipid.txt.
While I was at it, I moved the logging folder to My Documents, since I look at it a lot. This is done with Options > Directories > Log File.
I wouldn't recommend this installation procedure for every single new program, since it does defeat a security feature built into W7. This is for the care and feeding of these old radio sharewares. Make sure you trust the software.
Friday, January 13, 2012
Ham Radio Software Meets Windows 7
Despite knowing the perils of attempting to use ham radio software with anything newer than XP, I continued in my resolve to enter the modern age with an operating system that has some hope of support after next year. Since SDRs tend to like all the processor and memory you can throw at them, I loaded up on plenty of both, requiring the dreaded 64-bit operating system.
Dreaded because most ham shareware never heard of it.
After two weeks, results have emerged. Here we go:
Programs that work with 64 bit Windows 7 (your mileage WILL vary):
FLdigi - No problems so far.
JVComm32 - Works fine; it's going right now. Complains bitterly about my font sizes, but since I'm using a 1950x1200 graphic arts monitor, it'll just have to understand show biz.
MultiPSK - so far no problems except the need to personally communicate with the programmer to give him his well deserved money. (And that issue is platform-independent :-) . ) It stopped complaining about the font size when I went to Properties > Compatibility and checked the part about "Disable display settings on high DPI."
PC-HFDL - No problems AT ALL.
Posfix - No problems AT ALL.
Spectran: So far, works perfectly, despite Windows declaring it incompatible. There was some strange issue with its installer, which is really more like an unpacker. No matter how bitterly Windows complains, it can be unpacked to anywhere, and moved by hand to an appropriate folder you create under Programs (x86). There are no registry issues. The program barely even wastes time on MickeySoft's new sound drivers (more on that later).
TrueTTY/SeaTTY - so far no problems.
Programs that do not work (at least here):
PC-ALE & MARS-ALE - the UI functions properly but it can't seem to find the right sound input. Only noise displays in the box on the upper left. Using the virtual machine and "XP mode" does not seem to help. Also, scanning on many rigs requires a USB to serial adapter, and the older ones don't work on 64 bit W7, which has no driver for them.
Spectrum Lab - it's too bad that this state of the art package was never updated to post-Vista operating systems. It's fine to declare yourself an XP holdout, and even brag about how much better it is, and in the case of ham radio you are undoubtedly right. Back in the real world, it's important to keep up with technology.
Programs that work with some fiddling:
DSCdecoder - I think I finally have this one as happy as it's ever going to get. It's running in compatibility mode, and everything works except the ITU lookup. The issue with that is mysterious, and it may relate to the font sizes. Clicking the MMSI does indeed go to ITU and grab the information, as can be seen by picking through the file named ituresponse.txt that gets written to the program's directory. However, it never makes it onto the UI, or into the master lookup database file shipid.txt.
---------------
More on the W7 sound card issue:
The problem is that, from what I can find online, MickeySoft has made it harder, if not impossible, to record from streams. This is undoubtedly a concession to the music industry, which is concerned about copyright. Every sound card driver is different, but in my case, both the on-board and external sound had Stereo Mix and/or What U Hear missing.
In addition, the external sound card, a venerable Creative Live! they stopped supporting years ago, did not work well. It was prone to pops and crackles, and the sound was poor. The driver available at Creative Labs was a legacy product, and did nothing to solve the problem. I'll stay with the on-board sound, which is fine in all specs except signal to noise, until I feel like popping for a decent external card.
There is a hack to get Stereo Mix back on some of the sound drivers, at least for the Realtek driver on the Asus motherboard. This is documented all over the Internet, and it works. It involves going to a certain place in the config, finding Stereo Mix and unblocking it. However, my Stereo Mix still wouldn't do the right kind of loopback for legally recording and/or decoding audio from remote SDRs and radios.
(Psssst... Spectran, which ignores the sound board nonsense, will listen to Stereo Mix just fine on my box. AND it records. AND it's free. Don't tell RIAA.)
Happy computing......
Dreaded because most ham shareware never heard of it.
After two weeks, results have emerged. Here we go:
Programs that work with 64 bit Windows 7 (your mileage WILL vary):
FLdigi - No problems so far.
JVComm32 - Works fine; it's going right now. Complains bitterly about my font sizes, but since I'm using a 1950x1200 graphic arts monitor, it'll just have to understand show biz.
MultiPSK - so far no problems except the need to personally communicate with the programmer to give him his well deserved money. (And that issue is platform-independent :-) . ) It stopped complaining about the font size when I went to Properties > Compatibility and checked the part about "Disable display settings on high DPI."
PC-HFDL - No problems AT ALL.
Posfix - No problems AT ALL.
Spectran: So far, works perfectly, despite Windows declaring it incompatible. There was some strange issue with its installer, which is really more like an unpacker. No matter how bitterly Windows complains, it can be unpacked to anywhere, and moved by hand to an appropriate folder you create under Programs (x86). There are no registry issues. The program barely even wastes time on MickeySoft's new sound drivers (more on that later).
TrueTTY/SeaTTY - so far no problems.
Programs that do not work (at least here):
PC-ALE & MARS-ALE - the UI functions properly but it can't seem to find the right sound input. Only noise displays in the box on the upper left. Using the virtual machine and "XP mode" does not seem to help. Also, scanning on many rigs requires a USB to serial adapter, and the older ones don't work on 64 bit W7, which has no driver for them.
Spectrum Lab - it's too bad that this state of the art package was never updated to post-Vista operating systems. It's fine to declare yourself an XP holdout, and even brag about how much better it is, and in the case of ham radio you are undoubtedly right. Back in the real world, it's important to keep up with technology.
Programs that work with some fiddling:
DSCdecoder - I think I finally have this one as happy as it's ever going to get. It's running in compatibility mode, and everything works except the ITU lookup. The issue with that is mysterious, and it may relate to the font sizes. Clicking the MMSI does indeed go to ITU and grab the information, as can be seen by picking through the file named ituresponse.txt that gets written to the program's directory. However, it never makes it onto the UI, or into the master lookup database file shipid.txt.
---------------
More on the W7 sound card issue:
The problem is that, from what I can find online, MickeySoft has made it harder, if not impossible, to record from streams. This is undoubtedly a concession to the music industry, which is concerned about copyright. Every sound card driver is different, but in my case, both the on-board and external sound had Stereo Mix and/or What U Hear missing.
In addition, the external sound card, a venerable Creative Live! they stopped supporting years ago, did not work well. It was prone to pops and crackles, and the sound was poor. The driver available at Creative Labs was a legacy product, and did nothing to solve the problem. I'll stay with the on-board sound, which is fine in all specs except signal to noise, until I feel like popping for a decent external card.
There is a hack to get Stereo Mix back on some of the sound drivers, at least for the Realtek driver on the Asus motherboard. This is documented all over the Internet, and it works. It involves going to a certain place in the config, finding Stereo Mix and unblocking it. However, my Stereo Mix still wouldn't do the right kind of loopback for legally recording and/or decoding audio from remote SDRs and radios.
(Psssst... Spectran, which ignores the sound board nonsense, will listen to Stereo Mix just fine on my box. AND it records. AND it's free. Don't tell RIAA.)
Happy computing......
Monday, July 26, 2010
Digital Mode Programs That Work #2: Multipsk
Multipsk is a multimode receive/transmit program that works with the PC sound card in Windows or Linux. It's rapidly becoming the big gun in freely available ham/SWL software for these platforms.
The program is by Patrick Lindecker, F6CTE. It can be downloaded from Patrick's F6CTE web site, which is in English. A Yahoo group (also in English) for users is reachable at Multipsk (at) yahoogroups.com. I haven't looked at this group, but I keep meaning to.
Just about everyone I can think of who uses Windows or Linux for serious utility work has at least tried this program. Now that SkySweeper is no longer supported, Multipsk is the most viable PC multimode package for under $3000 US. WAY under, in fact, since a perfectly acceptable version is available free. As in $0000 US. This is not crippleware or nagware. When you pony up the $45 (last I looked), you get more features, and lose the time limits on some others.
New versions come out on a regular basis, and most add at least one new mode. The latest is 4.18. The major change from 4.17 is the addition of US weather radio SAME (Specific Area Message Encoding) decode. I've played with SAME on my scanner a bit. Its purpose is to alert local areas for bad weather.
The list of other modes is boggling:
110A (MIL-STD-188-110A/B), 1382 (1200 baud MSK), STANAG 4285, VHF ACARS, ALE, AMTOR/SITOR, ASCII, BPSK/QPSK 32/63/125/250, CHIP 64/128, Contestia, Coquelet, CW (OOK/Coherent/FSK), DGPS, Domino, DSC, DTMF, FAX, Hellschreiber (Feld/PSK/FM), JT65, MFSK8/16, MT63, Olivia, Packet/APRS, Pactor-I (used mostly for calling), PAX, PSK10/63F/220F, PSKAM, QRSS, RTTY, SELCAL, SSTV, and THROB.
Whew.
Hams will be able to take advantage of many features for logging, radio control (with 3rd-party software), and display of things like maps. For utility, the later versions have steadily added "professional" modes, such as SITOR-A, non-amateur RTTY speeds and shifts, and a SYNOP decoder (time limited w/o registration). Now, if I could only get good skip on Hamburg Meteo when the SYNOP codes are on.
The package includes another program called Clock, which decodes the data hidden in most time signals and GPS. After registration, it can set your computer clock. I've used this on several low-frequency European time signals via the WebSDR in Holland. This is close to a worst case for decode, given the Internet link's general instability. With considerable patience, though, I've managed decodes on nearly all stations at one time or another.
Anything this complicated is going to have a learning curve. Also, many people have been intimidated at first by the user interface. Now, I have come to like this. It's way faster than going through menus or trying to remember presets when you're in a hurry to grab onto some signal. The downside, though, is that there really are a lot of little buttons.
The colors have also turned some people off, though I don't mind them at all. They help group the aforementioned little buttons in a fairly logical manner.
How do the decodes stack up against other programs? Most of the time, just fine. I like SkySweeper better for FAX, but a lot of people hate it. DGPS might be better than SkySweeper, though DSCdecoder beats them both. SIGMIRA is somewhat better than either for STANAG 4285, though that mode really pushes the edge for any sound card decoder.
Where Multipsk has the general edge, for me anyway, is its use as a tool for attacking completely weird signals. This is especially true for the PSK variants.
I realize that the high-end government packages are often pretty good at this. But they aren't free/ $45. Case closed.
The program is by Patrick Lindecker, F6CTE. It can be downloaded from Patrick's F6CTE web site, which is in English. A Yahoo group (also in English) for users is reachable at Multipsk (at) yahoogroups.com. I haven't looked at this group, but I keep meaning to.
Just about everyone I can think of who uses Windows or Linux for serious utility work has at least tried this program. Now that SkySweeper is no longer supported, Multipsk is the most viable PC multimode package for under $3000 US. WAY under, in fact, since a perfectly acceptable version is available free. As in $0000 US. This is not crippleware or nagware. When you pony up the $45 (last I looked), you get more features, and lose the time limits on some others.
New versions come out on a regular basis, and most add at least one new mode. The latest is 4.18. The major change from 4.17 is the addition of US weather radio SAME (Specific Area Message Encoding) decode. I've played with SAME on my scanner a bit. Its purpose is to alert local areas for bad weather.
The list of other modes is boggling:
110A (MIL-STD-188-110A/B), 1382 (1200 baud MSK), STANAG 4285, VHF ACARS, ALE, AMTOR/SITOR, ASCII, BPSK/QPSK 32/63/125/250, CHIP 64/128, Contestia, Coquelet, CW (OOK/Coherent/FSK), DGPS, Domino, DSC, DTMF, FAX, Hellschreiber (Feld/PSK/FM), JT65, MFSK8/16, MT63, Olivia, Packet/APRS, Pactor-I (used mostly for calling), PAX, PSK10/63F/220F, PSKAM, QRSS, RTTY, SELCAL, SSTV, and THROB.
Whew.
Hams will be able to take advantage of many features for logging, radio control (with 3rd-party software), and display of things like maps. For utility, the later versions have steadily added "professional" modes, such as SITOR-A, non-amateur RTTY speeds and shifts, and a SYNOP decoder (time limited w/o registration). Now, if I could only get good skip on Hamburg Meteo when the SYNOP codes are on.
The package includes another program called Clock, which decodes the data hidden in most time signals and GPS. After registration, it can set your computer clock. I've used this on several low-frequency European time signals via the WebSDR in Holland. This is close to a worst case for decode, given the Internet link's general instability. With considerable patience, though, I've managed decodes on nearly all stations at one time or another.
Anything this complicated is going to have a learning curve. Also, many people have been intimidated at first by the user interface. Now, I have come to like this. It's way faster than going through menus or trying to remember presets when you're in a hurry to grab onto some signal. The downside, though, is that there really are a lot of little buttons.
The colors have also turned some people off, though I don't mind them at all. They help group the aforementioned little buttons in a fairly logical manner.
How do the decodes stack up against other programs? Most of the time, just fine. I like SkySweeper better for FAX, but a lot of people hate it. DGPS might be better than SkySweeper, though DSCdecoder beats them both. SIGMIRA is somewhat better than either for STANAG 4285, though that mode really pushes the edge for any sound card decoder.
Where Multipsk has the general edge, for me anyway, is its use as a tool for attacking completely weird signals. This is especially true for the PSK variants.
I realize that the high-end government packages are often pretty good at this. But they aren't free/ $45. Case closed.
Subscribe to:
Posts (Atom)