[WriteLog] CW direct keying

[Kostas SV1DPI]

Unfortunately you will find that writelog does not work while almost any 
other piece of software I have tried, works (dx4win, logger, n1mm). 
Writelog needs to improve this but Wayne told abt it in the past that he 
does not want to try to improve cw and we must go and buy winkey because 
is cheap. Of course behaviour like this, has led writelog to be in the 
4th place between contesting software. I have learned to use writelog, I 
like it, I have learned to reset the winkey (guess winkey has also 
problems!!), I have bought and use the latest version but I am not 
pleasant with writelog because of problems like this and finally I would 
like to see the software I use in 1st place. Unfortunately the right 
persons has not asked for this until now. So don't try more because you 
loose time from your dxpedition. Enjoy the dxpedition.

73 Kostas SV1DPI

Στις 9/7/2014 10:51 μμ, ο/η Darren Collins (G0TSM) έγραψε:
> I re-hooked up the direct keying interface and tried changing the 
> priority in the Windows task manager, but it made no difference, same 
> issue kept cropping up, even with anti-virus disabled on the 
> near-vannilla Win7 32bit installation. Incidentally it is the same for 
> RTTY but is harder to hear the problem when TXing, the rtty QSOs were 
> taking longer due to callers repeating their exchanges as I was 
> sending un-decodable replies.
> As a test I tried Logger32 directly keying the same interface in CW 
> and RTTY (it's a dual rtty/cw direct keying interface) and that ran 
> smoothly so i'll need to do some more investigating.
>
> 73 Darren G0TSM
>
>
>
> On 06/07/2014 21:59, Darren Collins (G0TSM) wrote:
>> Wayne,
>> Thanks for replying... Luckily the Winkey unit has sprung back into 
>> life after being disconnected for 24hrs, but i'll try your suggestion 
>> on direct keying tomorrow.
>>
>> 73 Darren (SV5/)G0TSM
>>
>> On 06/07/2014 18:30, Wayne, W5XD wrote:
>>>> my Winkey compatible interface has failed, luckily
>>>> I have a spare directkeying interface which is just an
>>>> opto-isolater type. It works fine but everynow and then
>>>> it will just go crazy and it sounds like rig is being
>>>> keyed very fast with rough choppy CW.
>>> This is a tough one. The reason WinKey exists is exactly the situation
>>> you're in. Its not COM port settings that are your problem. Your 
>>> problem is
>>> tasks that Windows thinks are higher priority than WriteLog and its CW
>>> timers. It might be possible to track them down, but its not easy. I 
>>> would
>>> start with virus checkers--turn them all off. (Why? they tend to 
>>> install
>>> themselves as being higher priority than anything else on the machine.)
>>>
>>> I would at least have a look at the Processes tab of the Windows Task
>>> Manager (right click in your Start Menu bar, and choose Task 
>>> manager) and
>>> sort by "CPU". See if something is running that you recognize and 
>>> see if you
>>> an figure out how to turn it off.
>>>
>>> You might even try sorting that same panel by Image Name, find 
>>> WriteL32.exe,
>>> right click on it, and raise its priority. I have never tried that. 
>>> But I
>>> don't think it can hurt anything.
>>>
>>> Wayne, W5XD
>>>
>>> _______________________________________________
>>> WriteLog mailing list
>>> WriteLog at contesting.com
>>> http://lists.contesting.com/mailman/listinfo/writelog
>>> WriteLog on the web: http://www.writelog.com/
>>
>> _______________________________________________
>> WriteLog mailing list
>> WriteLog at contesting.com
>> http://lists.contesting.com/mailman/listinfo/writelog
>> WriteLog on the web: http://www.writelog.com/
>
> _______________________________________________
> WriteLog mailing list
> WriteLog at contesting.com
> http://lists.contesting.com/mailman/listinfo/writelog
> WriteLog on the web: http://www.writelog.com/
>
>