Steve:

I really don't need to set up the ports that often, so it typically is a
"set it and forget it" sort of thing.  This is actually why I don't usually
worry about the problem too much.

The only time I seem to run into a problem is if I am setting up an updated
version of a program, or when I'm switching from the TS590 to the TS480 for
some reason.  Switching rigs while my TS590 was out at Kenwood Service
Center East was when I ran into the issue again.

As you suggest, maybe routing the Winkeyer to another port might be at least
a partial solution, and I may try that.  Usually, I set the winkeyer on port
6, and rig interface on port 5.  Sometimes, out at the RV, for reasons I
don't quite understand, I have to re-route rig interface to port 3, but the
winkeyer always seems to be happy on port 6, no matter which rig I am using.

Will also wait to see if Scott has anything further to offer.

Tom Behler: KB8TYJ




-----Original Message-----
From: For blind ham radio operators [mailto:[log in to unmask]]
On Behalf Of Steve Forst
Sent: Saturday, November 15, 2014 6:09 PM
To: [log in to unmask]
Subject: Re: FW: N3FJP software Port Locking Issue

Tom,

How often do you need to set up the ports in this software?   I would 
have expected that it would be  a set it and forget it kind of thing, unless
you make a change of some sort.


I'll assume that no other programs are running and taking control of the 
ports.

I think you are running a Winkeyer  USB for CW that sets up the USB 
connection as a comm port.  Maybe changing that port assignment to 
another comm port number in windows device manager  could avoid a 
conflict on that port.

Just a thought, Steve KW3A

On 11/15/2014 5:06 PM, Tom Behler wrote:
> Hi, all.
>
> =20
>
> Here is the initial response I received from Scott regarding my port =
> locking issue.
>
> =20
>
> Obviously, this was not terribly helpful, so I have tried to clarify =
> further.
>
> =20
>
> Will keep everyone posted.
>
> =20
>
> Tom Behler: KB8TYJ
>
> =20
>
> =20
>
> From: Scott & Kimberly Davis [mailto:[log in to unmask]]=20
> Sent: Saturday, November 15, 2014 3:37 PM
> To: [log in to unmask]
> Subject: Re: N3FJP software Port Locking Issue
>
> =20
>
> Hi Tom,=20
>
> =20
>
> Thanks for your e-mail.  If you make the proper port selections so that =
> you don't try to access the same port with multiple functions or =
> programs, you will no longer see the warning message.=20
>
> =20
>
> More details are here:
>
> =20
>
>   <http://www.n3fjp.com/faq.html#q40> Why do I get a com port sharing =
> error message?
>
> =20
>
> 73, Scott
>
> N3FJP
>
> http://www.n3fjp.com
>
> =20
>
> Serving the Amateur Radio community with contesting and general logging =
> software since 1997.
>
> =20
>
> 1 Peter 3 vs 15: Always be prepared to give an answer to everyone who =
> asks you to give the reason for the hope that you have =
> <http://www.n3fjp.com/Faith.htm> . But do this with gentleness and =
> respect...
>
> =20
>
> =20
>
> =20
>
> -----Original Message-----
> From: Tom Behler <[log in to unmask]>
> To: 'Scott & Kimberly Davis' <[log in to unmask]>
> Sent: Sat, Nov 15, 2014 3:19 pm
> Subject: N3FJP software Port Locking Issue
>
> Hi, Scott.
>
> =20
>
> Tom Behler: KB8TYJ here.
>
> =20
>
> I have been  experienceing a rather frustrating situation with your =
> logging software locking up when I accidentally choose an incorrect port =
> for a given application such as cw setup or rig interface.  In other =
> words, I get a port selection error message, and if I hit ok to get out =
> of the message, the computer keyboard remains locked up so that I =
> can=E2=80=99t do anything else.
>
> =20
>
> I have tried to correct the situation by completely shutting down the =
> computer, and then re-booting, but that does not help.  I=E2=80=99ve =
> also tried alt control delete followed by invoking the end task option =
> for whatever program I=E2=80=99m using, but still have had no success.
>
> =20
>
> The only way I can get out of the situation is to have my sighted XYL =
> use the mouse and click a number of times to a check box which =
> apparently unfreezes things.  We are trying to figure out a consistent =
> number of mouse clicks so that I can correct the problem independently, =
> but it seems like there should be a better way to address the issue =
> using the keyboard.
>
> =20
>
> I have found this problem to occur both with A C log, and several of =
> your other contest logging programs.
>
> =20
>
> Just for the record, I=E2=80=99m using windows XP on a Dell Lattitude =
> 600 laptop as my logging computer.
>
> =20
>
> Do you have any suggestions for me to try?
>
> =20
>
> Tom Behler: KB8TYJ, Big Rapids, MI
>
> =20
>
>
>