WriteLog
[Top] [All Lists]

Re: [WriteLog] WriteLog Digest, Vol 113, Issue 17

To: "Gary AL9A" <al9a@mtaonline.net>, <writelog@contesting.com>
Subject: Re: [WriteLog] WriteLog Digest, Vol 113, Issue 17
From: "DickT-W0RAA" <dickt@w0raa.com>
Date: Tue, 22 May 2012 21:06:45 -0600
List-post: <writelog@contesting.com">mailto:writelog@contesting.com>
Thanks, Gary.  I'll give that a try and see what happens.  Will get back to 
you tomorrow.

Dick
W0RAA


----- Original Message ----- 
From: "Gary AL9A" <al9a@mtaonline.net>
To: "DICK THOMPSON" <DICKT@W0RAA.COM>; <writelog@contesting.com>
Sent: Tuesday, May 22, 2012 8:02 PM
Subject: Re: [WriteLog] WriteLog Digest, Vol 113, Issue 17


> Dick,
>
> I too use VE7CC's CCuser interface.  On the CCuser Settings tab look at 
> the left most box called "Technical Stuff".  There is a line there that 
> states "Listening on Port 7300".  When I open a Telnet connection in WL my 
> settings show Telnet 127.0.0.1 and Port 7300.  If you are using Port 23 
> that may be the problem.  Try changing it to Port 7300 and see what 
> happens.
>
> 73,
> Gary AL9A
>
>
>
> ----- Original Message ----- 
> From: "DICK THOMPSON" <DICKT@W0RAA.COM>
> To: <writelog@contesting.com>; <al9a@mtaonline.net>
> Sent: May 22, 2012 11:34 AM
> Subject: Re: [WriteLog] WriteLog Digest, Vol 113, Issue 17
>
>
>> Hi Gary (and others)...
>>
>> Yes, I used to get spots in the bandmap without a problem.
>>
>> I have normally used w0mu.net / port 23 which had worked fine.  I am 
>> using telnet and it says w0mu.net Port 23 (as above).  I have tried ve7cc 
>> and it's the same.  Outside of Writelog I am getting spots.  Using 
>> WriteLog I don't.  I can't figure out why, which is the frustrating part. 
>> I use w0mu.net and ve7cc in my logging program (Win-EQF*) and the spots 
>> show up OK.  Everything else works in WL (CW/RTTY, SSB) with the 
>> exception of the spots.  I have even tried the command SET/NOFILTERS, and 
>> that doesn't help.
>>
>> I am using XP Home/SP3/Quad Core Processor and 3 gig of RAM.
>>
>> Hope that helps, Gary.  I appreciate the response from you.  HOPE TO SEE 
>> YOU IN THIS WEEKENDS WW WPX CW TEST.  I won't be able to spend a lot of 
>> time as we have to spend most of Saturday at a granddaughters high school 
>> graduation party.  So, it'll be a limited effort at this end.
>>
>> 73,
>>
>> Dick-W0RAA
>> Sent from my iPad 2
>>
>> PS:  The spots are appearing in the Incoming Only Packet Window in 
>> W0MU.net and VE7CC.  They are just not transferring to Writelog's Bandmap 
>> window.  I can furnish a screen shot of my layout if you think that would 
>> help any.
>> __________________________________________________________
>>
>> On May 22, 2012, at 1:00 PM, writelog-request@contesting.com wrote:
>>
>>> Date: Mon, 21 May 2012 21:13:43 -0800
>>> From: "Gary AL9A" <al9a@mtaonline.net>
>>> Subject: Re: [WriteLog] Band Map Problems
>>> To: "Writelog Reflector" <writelog@contesting.com>
>>> Message-ID: <8360E277474D4C268492CCDCE9EF33A4@AL9APC>
>>> Content-Type: text/plain; format=flowed; charset="iso-8859-1";
>>>    reply-type=original
>>>
>>> Dick,
>>>
>>> When you say everything has been running pretty good, does that mean you
>>> used to get stuff in the band map or not?  You don't mention a DX 
>>> cluster in
>>> your note.  Which cluster are you connecting to?  Are you using telnet?
>>> When you open the Incoming-only Packet window what does it say for a 
>>> Telnet
>>> address and a Port number?  Need more info to figure out where the 
>>> problem
>>> is.  Running V11.04A here and the Incoming-only Packet works FB - it 
>>> should
>>> on your V11.02B too.
>>>
>>> 73,
>>> Gary AL9A
>> _______________________________________________
>> WriteLog mailing list
>> WriteLog@contesting.com
>> http://lists.contesting.com/mailman/listinfo/writelog
>> WriteLog on the web:  http://www.writelog.com/
>
> 

_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web:  http://www.writelog.com/

<Prev in Thread] Current Thread [Next in Thread>