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:
Harry Brown <[log in to unmask]>
Reply To:
For blind ham radio operators <[log in to unmask]>
Date:
Mon, 27 Feb 2012 21:57:36 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (88 lines)
Hi Gary and all,
Well folks, if any of you have the NVDA screen reader, try all the n3fjp software with that, and let us know how it works with that!
73,
Trippy, ac8s
  ----- Original Message ----- 
  From: Gary Smith 
  To: [log in to unmask] 
  Sent: Sunday, February 26, 2012 9:22 PM
  Subject: Re: MS QSO Party


  Tom,
  My girlfriend, who is also a ham and is not sight impaired, also
  participated in the QSO Party and used the same logging program.  She didn't
  have any problems.  So it has to be some type of conflict with JAWS and
  N3FJP State logging software.  I have no problems like that when I use
  N3FJP's AC Log.     

  73, Gary

  -----Original Message-----
  From: For blind ham radio operators [mailto:[log in to unmask]]
  On Behalf Of Tom Behler
  Sent: Sunday, February 26, 2012 7:09 PM
  To: [log in to unmask]
  Subject: Re: MS QSO Party

      Gary:

  First of all, congrats on a great effort in the Mississippi QSO Party!

  Your score in six hours of operating time is truly something to be proud of!

  Regarding the N3FJP software, I have experienced both of the problems you 
  mention here.  I have experienced them both with my older Windows XP laptop,

  and with my new Windows 7 laptop.

  Someone on the list was trying to develop a solution to the problem of the 
  first letter not being entered when typing into the various data fields, but

  I don't know how that effort has progressed.

  Regarding the second problem of the contact info not always being logged 
  when hitting the "enter" key, my solution has always been to hit the enter 
  key again, after which time, the new entry usually is accepted.  In other 
  words, you should not have to go back and re-enter the contact info.

  These appear to be minor glitches with the N3FJP software.  Scott Davis 
  (N3FJP) himself is aware of them, although he seems unable to suggest a 
  truly workable fix.  Sometimes, I wonder if these glitches are being caused 
  by some sort of a Jaws conflict.

  Anyway, you are not alone here, and I think it's terrific that you got the 
  great score that you did, despite those nuissance-type problems.

  73 from Tom Behler: KB8TYJ


  ----- Original Message ----- 
  From: "Gary Smith" <[log in to unmask]>
  To: <[log in to unmask]>
  Sent: Sunday, February 26, 2012 7:27 PM
  Subject: MS QSO Party


  > Thanks to everyone who worked me during the Mississippi QSO Party contest.
  > I worked a little over six hours and made 333 contacts which seven of them
  > were DX.  I'm not sure how good that is since this was my first time to do
  > the QSO Party contest.  What I do know is that it was a lot of fun.
  > I was using the N3FJP logging software and had a few problems.  It seems
  > like this was discussed some time back and I was wondering if there were 
  > any
  > solutions?  The first field, where you type the callsign in, sometimes it
  > wouldn't type the first letter and the same thing would happen in the 
  > field
  > where you type the state or country.  The second problem was when after 
  > you
  > would put everything in and press enter sometimes the info wouldn't enter
  > into the log and I would have to delete the call out and retype it back 
  > in.
  > Then when you press enter it would go in.  Has anyone else had this 
  > problem
  > and if so did you find a solution?
  >
  > 73, Gary, N5GD
  >

ATOM RSS1 RSS2