[WT-support] Can't use "?" on ONE computer in callsigns

[Bob Wilson, N6TV]

In addition to DEFINEKEYS, which should be double-checked to ensure that "?"
and "Shift-?" doesn't appear anywhere, is it possible you assigned a LUA
script to the "?" key at one point.  Type SCRIPTS [Enter] to check for
script assignment.

If you type Alt-N, to create a note, does the question mark key work?  If
not, I'd suspect a keyboard problem.  Another program like AutoHotkey can
also remap the "?" key.

Finally, there's no point in using "only a Radio 2."  Just change it to
Radio 1, keep the same COM port, change the COM port from "Radio 2" to
"Radio 1", and make sure the serial port settings are the same, and let us
know if that makes any difference.

73,
Bob, N6TV

On Sat, Mar 26, 2011 at 10:34 PM, <kd4d at comcast.net> wrote:

> I was thinking more about this...that computer has ONLY a RADIO 2.  (Radio
> 1
> was disconnected).  The other three computers (where the "?" works great)
> are
> on Radio 1.  Could that have something to do with it?
>
> 73,
>
> Mark
>
> ----- Original Message -----
> From: kd4d at comcast.net
> To: support at win-test.com
> Sent: Sunday, March 27, 2011 5:13:14 AM
> Subject: Can't use "?" on ONE computer in callsigns
>
> Good day, everyone:
>
> I have five computers set up with WinTest for a M/2 in WPX.  On four of
> them,
> I can enter a partial callsign with question marks and look for a match in
> the supercheck partial window.
>
> On the fifth computer, the "?" character doesn't show up on the logging
> line.
> There was some stuff in the Redefine Keyboard Keys on that computer so I
> removed
> all of the entries.  That didn't change anything.
>
> Any suggestions?  This is our FIRST time to use WinTest so be gentle... :-)
>
> 73,
>
> Mark, KD4D
> _______________________________________________
> Support mailing list
> Support at f5mzn.org
> http://lists.f5mzn.org/cgi-bin/mailman/listinfo/support
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.f5mzn.org/pipermail/support/attachments/20110326/e113468c/attachment.html>