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
Condense Mail Headers

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

Print Reply
Content-Type:
text/plain; charset="iso-8859-1"
Date:
Tue, 28 Feb 2012 15:58:16 -0500
Reply-To:
For blind ham radio operators <[log in to unmask]>
Subject:
MIME-Version:
1.0
Message-ID:
<502BF9DD811045CA95B016E7945D5A2B@YOUR705810B3BF>
Content-Transfer-Encoding:
quoted-printable
Sender:
For blind ham radio operators <[log in to unmask]>
From:
Harry Brown <[log in to unmask]>
Parts/Attachments:
text/plain (159 lines)
Hi Tom,
What I mean about the dupe part, is when I type a call sigg, I also type the band and mode, for example
ac8s 40 m, cw.
73,
Trippy, ac8s
  ----- Original Message ----- 
  From: Tom Behler 
  To: [log in to unmask] 
  Sent: Tuesday, February 28, 2012 6:38 AM
  Subject: Re: MS QSO Party


      Trippy:

  In your last post, you wrote:

  As far as dupes, what I will be doing is, just typing in the call sign,
  and if I get the same call sign again, somewhere in the log, it should tell 
  me."

  I am not understanding how this can  happen with a standard wordpad or MS 
  Word file.

  Perhaps I'm missing something though.

  The other disadvantage of keeping your log in wordpad or MS Word is that 
  your score is not automatically calculated for you as you go.  As we all 
  know, some of the scoring schemes in contests are quite complicated, and 
  it's sure nice to have a program like N3FJP to do all of that for you.

  Finally, if you try to submit your log for a contest to the contest sponsor, 
  I'm not sure if they would accept a wordpad or MS Word log.  They tend to 
  prefer cabrillo logs.

  If you need some help with the N3FJP logging software, I will be happy to 
  provide that, since I have used the software in various forms for the past 
  12 years.  I think others on the list have had reasonable success with it as 
  well.


  Just some thoughts here from a developing contester who admittedly has a lot 
  to learn yet.

  73 from Tom Behler: KB8TYJ




  ----- Original Message ----- 
  From: "Harry Brown" <[log in to unmask]>
  To: <[log in to unmask]>
  Sent: Monday, February 27, 2012 9:49 PM
  Subject: Re: MS QSO Party


  > Hi Gary and all,
  > I used n3fjp loging software in the past, but I just gave up on it, for =
  > those reasons and others.
  > What I will be doing in the future, is using either wordpad, or, =
  > microsoft word for my log.
  > What you can do is, when you change the band or frequency, just type it =
  > in, then, when you get a contact, just type in the information.
  > As far as dupes, what I will be doing is, just typing in the call sign, =
  > and if I get the same call sign again, somewhere in the log, it should =
  > tell me.
  > I did a write up on this, it's in my files folder.
  > I know there are xmlog, and others out there, but I haven't tryed them =
  > yet.
  > 73,
  > Trippy, ac8s
  >  ----- Original Message -----=20
  >  From: Tom Behler=20
  >  To: [log in to unmask]
  >  Sent: Sunday, February 26, 2012 8:08 PM
  >  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=20
  >  mention here.  I have experienced them both with my older Windows XP =
  > laptop,=20
  >  and with my new Windows 7 laptop.
  >
  >  Someone on the list was trying to develop a solution to the problem of =
  > the=20
  >  first letter not being entered when typing into the various data =
  > fields, but=20
  >  I don't know how that effort has progressed.
  >
  >  Regarding the second problem of the contact info not always being =
  > logged=20
  >  when hitting the "enter" key, my solution has always been to hit the =
  > enter=20
  >  key again, after which time, the new entry usually is accepted.  In =
  > other=20
  >  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=20
  >  (N3FJP) himself is aware of them, although he seems unable to suggest =
  > a=20
  >  truly workable fix.  Sometimes, I wonder if these glitches are being =
  > caused=20
  >  by some sort of a Jaws conflict.
  >
  >  Anyway, you are not alone here, and I think it's terrific that you got =
  > the=20
  >  great score that you did, despite those nuissance-type problems.
  >
  >  73 from Tom Behler: KB8TYJ
  >
  >
  >  ----- Original Message -----=20
  >  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=20
  >  > 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=20
  >  > field
  >  > where you type the state or country.  The second problem was when =
  > after=20
  >  > 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=20
  >  > in.
  >  > Then when you press enter it would go in.  Has anyone else had this=20
  >  > problem
  >  > and if so did you find a solution?
  >  >
  >  > 73, Gary, N5GD
  >  >
  >

ATOM RSS1 RSS2