BLIND-HAMS Archives

For blind ham radio operators

BLIND-HAMS@LISTSERV.ICORS.ORG

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Tom Behler <[log in to unmask]>
Reply To:
For blind ham radio operators <[log in to unmask]>
Date:
Sat, 15 Nov 2014 11:02:16 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (64 lines)
Dave:

I've done the alt control delete, and the task manager thing, and tried
ending the N3fJP task, but to no avail.

The laptop I use for ham radio logging is an older Windows XP machine, and
I'm using Jaws 14 with it.

I'm almost tempted to go back to an earlier version of Jaws on that machine
to see if the problem still occurs, but I hate to go through all that
trouble if it isn't necessary.

Tom Behler: KB8TYJ


-----Original Message-----
From: For blind ham radio operators [mailto:[log in to unmask]]
On Behalf Of Dave Basden
Sent: Saturday, November 15, 2014 12:25 AM
To: [log in to unmask]
Subject: Re: N3FJP software port locking issue

Hi Tom,

I've experienced the same problem at times.  One sure solution is to use
Control-Alt-Del to bring up the logout screen and then arrow down to task
manager.  Use it to close the N3FJP program.  I think Scott needs to address
the problem.

73,

Dave, W7OQ

At 07:34 PM 11/14/2014, you wrote:
>Hi, all.
>
>
>
>Every once in a while, I experience a rather frustrating situation with 
>the N3FJP 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't do anything else.  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.
>
>
>
>Has anyone else on the list experienced this problem, and if so, were 
>you able to figure out a way to solve it independently via the keyboard?
>
>
>
>Thanks and 73 from Tom Behler: KB8TYJ
>
>

ATOM RSS1 RSS2