[WT-support] wtDX Telenet status update?

[Peter]

Olivier

As said before at PI4CC we have similar problems with DXtelnet.

This evening I installed  a fresh win-test 3.5.0 at home on a second 
computer with xp-prof and wtdxtelnet 2.0
On that computer I have loaded the cqwwssb contest with 1902 qso's
Make the connection with the  dx-cluster and see spots coming in

Run down to the livingroom and update the win-test 3.3 version to 3.5.0
Start wintest and try to reach the cluster via win-test and its get spots
Then I mark out disable log sychronization I got the full log from the 
other PC

Got the 1902 qso's and guess..... no commands can't send anymore to the 
cluster.
Spots still roling in.

When back to the pc with wtdxtelnet and via alt-t there in NO commands 
sening out. A command direct into wtdxtelnet  gives an output.

So just  (un)lucky?
I will no touch the system and for ready to make some test on request.

Peter
PC2A

Olivier F5MZN schreef:
> Tim Duffy K3LR wrote:
>> I was curious if there has been any resolution to the problem with 
>> out going DX
>> spots (ALT-F3) and other out-going communications as reported by several
>> stations during CQWW Phone?
>>
>> Hoping for a solid fix for CQWW CW.
>
> Hi -
>
> I was just thinking to post a message to the mailing list on this topic!
>
> In spite of many hours spend here, I still cannot repeat the problem. 
> So that I am not able to confirm that it is related to wtDxTelnet 
> itself, to the wtCom.DLL library, to Win-Test or to anything else.
>
> It is even harder to engage a corrective measure, because the few 
> people who suffered from this problem submitted different reports:
>
> - some reported that it was just needed to stop/restart wtDxTelnet to 
> temporary cure, other told that it was necessary to close the Windows 
> session and start with a new one (or reboot the computer);
>
> - some reported that sending datas from wtDxTelnet itself wasn't 
> working, other told that it was.
>
> It is quite hard to fix something I cannot repeat, but it is 
> absolutely impossible to fix anything if the reports are so different.
>
> For now, the status of this problem is: "I cannot repeat, waiting for 
> additional informations".
>
> I am thinking to add a debug option in wtDxTelnet which will trace in 
> a file the network traffic. That way we will perhaps be able to go up 
> to the problem.
>
> 73,