[WT-support] Fresh Install Wintest Fails

Bob Wilson, N6TV n6tv at arrl.net
Thu Oct 20 02:55:35 CEST 2016 

Stewart,

If you don't mind, I'd really like to get to the bottom of this.  Are you
using a KEYSPAN USA-19HS (https://www.tripplite.com/
keyspan-high-speed-usb-to-serial-adapter~USA19HS/) or something else?  That
device uses a TI chipset.

I really need to know if the KEYSPAN adapter is supported on Windows 10
64-bit.  The Keyspan web site says yes, but I see no specific device
drivers for Windows 10, which means the support is supposed to be built-in
to Windows 10, and no  driver installation should be required.  Did you
install a driver or did Windows find one?  Have you ever connected *any*
other type of USB-to-Serial adapter (FTDI or Prolific) to this PC?  If so,
those drivers could be interfering with the Keyspan driver due to a
conflict.  Multiple drivers could be trying to use the same COM port number
even when those devices are not connected.  I've fixed problems like this
in the past by removing all traces of Prolific USB-to-Serial device drivers.

Please do the following to remove unnecessary device drivers, it won't take
long:


   1. Connect the USB-to-Serial adapter to the PC (you can leave the K3 OFF)
   2. Set the Windows environment variable *devmgr_show_nonpresent_devices*
   to *1*.  Here's how:
      1. From a Windows command prompt, run *sysdm.cpl* (a shortcut to
      System Properties)
      2. Click the *Advanced *tab
      3. Click  *Environment Variables*
      4. Under *System Variables* click *New...*
      5. Set Variable name to: *devmgr_show_nonpresent_devices*
      6. Set Variable value to:  *1*
      7. Click *OK* twice to close the dialogs
      8. Click *Apply* and *OK*
   3. Run *devmgmt.msc* (a shorcut to the Windows Device Manager)
   4. From the Device Manager menu, select *View | Show hidden devices*
   5. Expand the *Ports* section
   6. You may see some grayed-out devices that you are no longer using,
   perhaps some using the same serial port as the KEYSPAN
   7. Right click on unused devices and click Uninstall.  Leave the KEYSPAN
   as is, unless it is the only serial port listed, in which case you should
   delete it too.
   8. If you're about to remove the last device of a particular type
   (Prolific, FTDI, etc.) that shares a driver, you may also check the
box *Delete
   the driver software for this device*, especially for Prolific
   9. Click *OK*
   10. Repeat for all unused serial ports, especially those using the same
   COM port number as the KeySpan USB Serial Port
   11. Shutdown and Restart the Windows computer (cold boot), and the
   USB-to-Serial adapter should talk to the K3 just fine.  If not, the device
   driver is probably to blame, not Win-Test, and you should get a different
   type of USB-to-Serial adapter such as the GearMo, FTDI, or Edgeport.

73,
Bob, N6TV

On Oct 19, 2016 1:04 PM, <stewart at gm4aff.net> wrote:

> Thanks Bob, and everyone else who helped. The reason I was reluctant to
> issue a cry for help was because I have my desktop PC in front of me
> connected to the K3, and everything works. The laptop is configured exactly
> the same way - the ports baud rate, etc. are all easy to see and check that
> they are correct. It shouldn't be rocket science. I worked my way through
> all the help received, including re-installing the application as Admin,
> and running it as Admin. Nothing has made any difference. It's weird, but I
> can't be bothered chasing it. Life's too short!
>
> I bought the TrippLite adapter based on advice received which (at the
> time) said FTDI was unreliable. I can find references to FTDI as both good
> and bad on this reflector!
>
> I will revert to using my trusty old XP laptop for CQ WW and put this
> 64-bit piece of junk back in the sun lounge for my wife to use.
>
> So please work PZ5K next weekend - I expect we will be able to log the QSO!
>
> 73
> Stewart
> GM4AFF
>
>
>
> On Tue, Oct 18, 2016, at 11:15 PM, Bob Wilson, N6TV wrote:
>
> In this case, I recommend uninstall first, then reinstall the full version
> 4.22, not the "update."
>
> It probably won't resolve all the problems you reported, so continue down
> the list.
>
> 73,
> Bob, N6TV
>
> On Tue, Oct 18, 2016 at 10:45 PM, Stewart GM4AFF <stewart at gm4aff.net>
> wrote:
>
> Bob,
> Wonderful reply! Thanks. No, I didn't run the install as Admin. Can this
> be simply rectified by reinstalling?
> 73
> Stewart
>
> Sent from my iPhone
>
> On 18 Oct 2016, at 23:59, Bob Wilson, N6TV <n6tv at arrl.net> wrote:
>
> I assume you're not using the new KIO3B module in your K3 (the one with
> the RJ-45-style connector and a serial adapter).
>
> Did you remember to right click and select *Run as an Administrator* when
> you ran the Win-Test installer?
>
> After installation completed, did you remember to change the *Properties*
> of the Win-Test shortcut, under the *Compatibilty* tab, to *Run as an
> Administrator*?
>
> Did you remember that the Win-Test SOUND command (CW sidetone via PC
> speakers) is not supported on Windows 7?  It only works on Windows XP now.
>
> Did you remember to set the baud rate of the radio's COM port to match the
> baud rate of the radio?
>
> Did you remember to open a CW log and program the CW messages?
>
> If Advanced SO2R Mode is enabled, did you select a blank scenario?
>
> Are any scripts assigned to the function keys (see Win-Test Scripts
> Manager).
>
> In the K3, did you set CONFIG:PTT-KEY to RTS-DTR and set DTR = CW, RTS =
> PTT in Win-Test for the radio's COM port?
>
> Is VOX enabled on the K3?
>
> Did you install the latest Tripp-Lite device driver?  I've heard from
> others that had trouble getting it to work on 64-bit Windows (blue screen
> crash), but that was some time ago.  I'd recommend an FTDI or Edgeport
> USB-to-Serial adapter.  Here's an inexpensive one for single port purposes.
>
> http://www.digikey.com/product-detail/en/ftdi-future-technol
> ogy-devices-international-ltd/CHIPI-X10/768-1138-ND/3103022
>
> If you cannot figure it out, send me your WT.INI file, your log file, your
> Advanced_SO2R.ini file, and a screen shot of the Ports section of your
> Window Device Manager (run devmgmt.msc).  Use File | Explore /cfg directory
> and File | Explore /log directory to locate these files.
>
> 73,
> Bob, N6TV
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.f5mzn.org/pipermail/support/attachments/20161019/112211d2/attachment-0001.html>

More information about the Support mailing list