Ok Tom,

I really think we can get these 2  seperate issues solved.  Fixing the 
N3FJP thing should be  fairly easy (I hope)?

Again, what software are you using for packet?

Although you know I'm not a big CW guy, I do plan to play  this weekend. 
  Last year, I only worked 160 meters in this contest and worked 30 
countries and 5 new ones on the band.  Things probably won't be so good 
on 160 this year, but it will be worth a look.

Let me know how all this stuff works out.

73, Steve KW3A




On 2/14/2012 6:40 AM, Tom Behler wrote:
>      Steve:
>
> Excellent idea!
>
> I never thought of that!
>
> That's why it's so good to have you around!  (grin)
>
> Will try it tonight after work if I get the chance!
>
> Will keep you posted.
>
> P.S.  Are you going to play at all this week-end in the ARRL International
> DX CW contest?
>
> I won't have all 48 hours available, but will certainly play a little, just
> to see what I can do.
>
> 73 from Tom Behler: KB8TYJ
>
> ----- Original Message -----
> From: "Steve Forst"<[log in to unmask]>
> To:<[log in to unmask]>
> Sent: Monday, February 13, 2012 9:49 PM
> Subject: Re: Using USB Signalink Device With Windows 7
>
>
>> Tom,
>>
>> On the N3FJP thing:  Since Scott N3FJP told you a few months ago that
>> his software can only use the default sound card and it can't be
>> changed, you may have to attack this from another angle.   If you hear
>> the relay in the signal link click and it goes into transmitt when
>> moving between fields, try turning the vox delay knob all the way  clock
>> wise.   That may delay the vox to the point that it doesn't trip and so
>> won't transmitt.
>>
>> You should probably go into sound devices in windows and make the
>> realtek the default sound card.  In it's infinite wisdom, windows will
>> make the usb card the default whenever you plug it in, and this is what
>> N3FJP is  accessing.   Killing the vox may be a quick fix just to see
>> what happens,
>>
>> 73, Steve KW3A
>
>
>