[Elecraft] FTDI to serial adapter for K3 with Windows 7 change. Why?

[Ken G Kopp]

Slight correction to my post ...

"first push the TEST side of the MODE button..."

73!

Ken - K0PP
-------------------------------------------------------------------

On Thu, Nov 12, 2015 at 10:35 AM, Art Hejduk <valvetbone at gmail.com> wrote:

> I just make sure I have the K3 connected to a dummy load.
>
> 73,
> Art  WB8ENE
>
> On Thu, Nov 12, 2015 at 12:24 PM, Ken G Kopp <kengkopp at gmail.com> wrote:
>
>> John,
>>
>> My Windows 7 Pro has always operated this way.  Dunno if it's evidence of
>> a
>> "problem" or not.  The "fix" ... for me ... is to first push TX disable on
>> the K3 when turning the computer on.
>>
>> 73
>>
>> Ken - K0PP
>> On Nov 12, 2015 10:16 AM, "John Lawrence via Elecraft" <
>> elecraft at mailman.qth.net> wrote:
>>
>> >
>> >  I have recently had to reform my C drive and reload Windows 7 Pro
>> >
>> > After doing the process of reinstalling the K3 utilities off the
>> Elecraft
>> > site
>> > it has given me an outcome not meeting the prior results.  It down
>> loaded
>> > fine
>> > but now I get PTT pulses on boot or sleep turn on.
>> >
>> >
>> >  Never before with the same OS did the same DELL give me this.
>> Exactly, I
>> > get a series
>> > of PTT key up pulses in a series of, " - - -   - -   - - " each dash
>> > representing the short PTT keyup
>> > pulses on the K3 and it's always the seme series of PTT key ups.
>> >  Something has changed but it isn't the FTDI driver. The command is
>> coming
>> > from the Win 7 OS generating it with the FTDI driver.  Is there
>> something
>> > in the BIOS that has changed?  This is the Elecraft FTDI chip set cable.
>> >
>> > Any Windows 7 gurus who can help me?
>> >
>> > Thanks
>> >
>> >
>> >
>> > John, W1QS
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>