After you copy the correct DLL, try "regsvr32 rpcrt4.dll". The DLL may have different functionality and the DLL "registers" this functionality during installation if you do this. Maybe another progra
I've installed WriteLog on a different computer and can't seem to get = the beam headings to work right. I've entered my lat/long (roughly 47 122) in the "Great Circle" window, = then I saved the con
I found if I use the second tab of Great Circle to set the relative order of the bearing, long path bearing, distance, sunrise and sunset that things started to work. I had them all at 0. But I still
Ahh, found it in the registry. The mystery is over. K6KR -- Original Message -- From: "Peter" <pb0aiu@pi4cc.nl> To: "Dick Dievendorff" <dieven@msn.com> Cc: <writelog@contesting.com> Sent: Saturday, M
This is a multi-part message in MIME format. --=_NextPart_000_000E_01C1647F.90F31B00 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I'm trying to use a W5X
This is a multi-part message in MIME format. --=_NextPart_000_0007_01C16481.53582950 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Well, part of the probl
Well I found that my Multi-Keyer works in single-radio mode as long as I hook up the rig as the Right radio. Maybe something's wrong with the software; maybe something's wrong with the left part of m
But I'm worried that if/when I eventually go to two-radio contesting that the thing won't key both rigs. So I have to figure this out very soon. Maybe it's the software. Maybe the firmware in the box
This is a multi-part message in MIME format. --=_NextPart_000_005B_01C16534.A1216670 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I was frequently called
I didn't think I was flaming anyone. I'm not upset or trying to upset other people, I'm trying to understand why my hardware/software doesn't work as I expected it to. I'm troubleshooting, and I'm as
Thanks, Jerry! I didn't realize I had to deal with a two-radio situation. The keyer worked initially when connected as the left, but the first time I pressed "ESC" or "Alt-F10" to change speeds, appa
I would be very surprised if the current WriteLog offers LPT1 for a device driver that it doesn't expect. I'd expect that Writelog would figure out that it's on Windows 2000 (or NT, or XP) and grey o
This is a multi-part message in MIME format. --=_NextPart_000_0131_01C12D84.62A1FA00 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I'm re-installing all m
Thanks. Writelog has something to do with this, as I can control my ICOM rig with a RocketPort card with DxBase, but I switch to WriteLog and it doesn't work. I guess I'll just go with COM1 for this
I have used a Heil Proset with my ICOM 761 with just the Heil "blue" ICOM AD-1 adapter, see http://www.heilsound.com/ad-1.htm. It's the little widget that has an 8-pin plug on one end and a 1/4 inch
The conventional wisdom is to log what you recieved, and then append a note for the log checkers. Presumably the Canadian station sent "NL" to other stations as well. You wouldn't want your QSO to be
I didn't come to the conclusion you did. The PW-1 manual says that all CI-V devices have to be set to the same SPEED, but I saw nothing to lead me to the conclusion that they should be the same addre
Do you have any printers installed? Maybe the Windows print spooler wants to own the LPT port. I'm not sure that this is the problem, I'm just guessing. Dick, K6KR Hello, After too many crashes with