The heather.cfg file has a com port setting (/1u) and a /rxa (receiver auto-detect) command line option setting which gets processed before the settings on the command line.

Try editing heather.cfg file and change the /1u command to /0

connected to another PC, but what I got was an error message saying :

Error exit 10002: Can't GetCommState()

Mark
I am trying to use Heather with a z3801. I have tried numbers of
combinations of what should set the system to the Z receiver. But none seem
to work. It immediately brings up the help screen and I assume that says
the command is bad.
I have no problem making the TBolt work.
Wonder if you could please clarify the receiver command.
Other bad note. My lucky day I have a LT1180 bad rcvr drvr chip in the
z3801.
Its receiving but not transmitting. Yahoo fun time.
Regards
Paul
WB8TSL

On Sat, Dec 10, 2016 at 7:25 PM, Mark Sims holrum@hotmail.com wrote:

Version 5.00 is working well with my 58503A, but I did find one annoying behavior. If LH is the active application, as in it has keyboard focus, I find my screen saver will not activate.

Jim WN1X
On 12/11/2016 11:45:10 AM, paul swed paulswedb@gmail.com wrote:
Mark
I am trying to use Heather with a z3801. I have tried numbers of
combinations of what should set the system to the Z receiver. But none seem
to work. It immediately brings up the help screen and I assume that says
the command is bad.
I have no problem making the TBolt work.
Wonder if you could please clarify the receiver command.
Other bad note. My lucky day I have a LT1180 bad rcvr drvr chip in the
z3801.
Its receiving but not transmitting. Yahoo fun time.
Regards
Paul
WB8TSL

On Sat, Dec 10, 2016 at 7:25 PM, Mark Sims wrote:

time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.

Hello Mark,

many thanks for your immense and invaluable work!

I am using the trimble thunderbold together with LH version 3 all the
last years with success, I like your program very much.
I downloaded and installed today the version 5, but I have some problems
because it looks like my windows 7 does
not get access to the heather.cfg file, what do I wrong? Anybody has an
idea how to do it right?

Many thanks

Arnold, DK2WT

Am 11.12.2016 um 01:25 schrieb Mark Sims:

Arnold:

It seems during the install at least on Windows 10 that it does not give the full permissions to the files. I just gave the folder the correct permissions after the isntall. If you go to help, at the bottom of the screen  it tells you where during the install another copy of the heather.cfg was installed. You should be able to read/write this copy. At least that was my experience during installing.

-=Bryan=-

From: time-nuts time-nuts-bounces@febo.com on behalf of Arnold Tibus arnold.tibus@gmx.de
Sent: December 11, 2016 10:39 AM
To: time-nuts@febo.com
Subject: Re: [time-nuts] Lady Heather Version 5 is now available

Hello Mark,

many thanks for your immense and invaluable work!

I am using the trimble thunderbold together with LH version 3 all the
last years with success, I like your program very much.
I downloaded and installed today the version 5, but I have some problems
because it looks like my windows 7 does
not get access to the heather.cfg file, what do I wrong? Anybody has an
idea how to do it right?

Many thanks

Arnold, DK2WT

Am 11.12.2016 um 01:25 schrieb Mark Sims:

time-nuts Info Page - American Febo Enterpriseshttps://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
www.febo.com
time-nuts is a low volume, high SNR list for the discussion of precise time and frequency measurement and related topics. To see the collection of prior postings to ...

time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
time-nuts Info Page - American Febo Enterpriseshttps://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
www.febo.com
time-nuts is a low volume, high SNR list for the discussion of precise time and frequency measurement and related topics. To see the collection of prior postings to ...

and follow the instructions there.

I'm not sure what might be going on here, but one thing that tripped me up personally was that some options I was using in both my old heather.cfg file and my command-line shortcut were changed between V3 (which is what I was running before) and V5.  If you somehow get into a situation where LH V5 is trying to load an older config file, you may need to track down that file and modify or delete it.

In general, make sure you run the LH setup program while logged in as the same user that will run the app.  Currently the installer always writes heather.cfg to the current user's documents folder (e.g., c:\Users\johnm\Documents).  If you have a separate admin user on your system and you launch the installer under that account, heather.cfg may end up in a different directory.  That, in turn, may leave an older copy of heather.cfg  lying around for the program to find.

Still another thing to watch out for, now that heather.cfg is an officially-installed file, is that subsequent reinstallations of LH will overwrite any changes you've made to heather.cfg.  So you may want to make a backup if you need to reinstall for any reason after making extensive changes to heather.cfg.

Future builds will solve both of these problems by having the program itself create heather.cfg the first time it's run, if the file isn't already present in {userdocs}.  That's really the only right way to install .cfg/.ini files in Windows-land, but neither of us got around to implementing that for the initial V5.00 release.

-- john, KE5FX
Miles Design LLC

Many thanks Brian!

I found it!
In Windows 7 (10?) this file must be copied into the system32 directory
of windows in order to be read and enable the instructions to be executed.

73
Arnold DK2WT

Am 11.12.2016 um 21:51 schrieb Bryan _:

Hmm, that doesn't make any sense at all.  Nothing should be written to \windows\system32 by the installer under any conditions.

-- john, KE5FX
Miles Design LLC

On 12/11/2016 1:25 AM, Mark Sims wrote:

Problem fixed. The reason for the misbehaving was that the installer did not set the "Start In" field of
the Properties panel.

Look at this screen capture :

https://dl.dropboxusercontent.com/u/15089947/lh.gif

When properly set, the error disappeared. My suggestion would be to modify the installer so that
also that field is correctly set.

73  Alberto  I2PHD