Hi Dennis,

I am having a problem with the latest update, version 9.1.3. Instead of connecting the Logic Telnet form directly to a DX spotting cluster, I connect Logic Telnet to the program: CC User. It is the CC User program that connects to the cluster.

To connect Logic Telnet to CC User, I use the URL: 127.0.0.1 :7300. Both programs are the same Windows 10 computer. When I enter this URL into Logic Telnet, with Logic version 9.1.3 installed, I get a message that the URL was not found. The CC User developer provides this information: “If the logging program is running in the same machine, use the local telnet loopback port (127.0.0.1 :7300)”.

I reinstalled the previous Logic version, 9.1.2. That version works well with the above URL.

73,
John

I am having issues as well with Telnet. When it connects no issues but when it doesn't I get numerous error messages.

Hi Dennis,

I posted my telnet issues here:

http://www.hosenose.com/..._postst1921_Telnet.aspx

Thanks,
Vin

Hi Dennis,

Amazing, eliminating the space and making it 127.0.0.1:7300 fixed the problem. I can now log into CC User.

I reverted back to version 9.1.2 to test this. With this version installed, it does not make a difference whether there is a space: 27.0.0.1 :7300 or no space: 127.0.0.1:7300.

I tried a number of things before I wrote to you. I never played around with the spacing!

If you would like to try CC User, it is found here:

http://www.bcdxc.org/ve7cc/

You have to scroll down about 2/3 to find the installation instructions. It is a free program. In part, I can define each band as a different color. Thus, each spot row is shown in a different color for different bands. It works well with LoGIC.

Thanks for your help.

73,
John

Thanks, but the main reason we replaced Telnet was stability problems under Win 10 here lately.

1. I tried sleep and waking it up, and no problem. Maybe I need to let it sleep longer or something. It could be that a data flood on waking causes it to fail. I will experiment further. I don't use sleep, but do use hibernate. I haven't had a problem with that either -- I have probably hibernated with LOGic/Telnet going, but not positive. I will test that too.

2. Haven't seen this. Hopefully it is tied into 1.

3. The Windows event viewer may give more info. I am preparing a video on how to do this and will post it Mon or Tues.

Tnx & 73,

DH WN4AZY

Dennis, V14 has the same problem--OLE code 0 "a device attached to the system is not functioning." Hit ignore and telnet is disconnected.

I am also getting random crashes. Here are the files from one, as stored by WIN7.

Bob, N7IP

The random crashes are not related to sleep/awake. They have been random.

In the case of the telnet-related crashes, Telnet was running when the PC went to sleep. It was disconnected when logic woke up. Then, after starting telnet, it crashes.

Today, after several days of the experience above, Logic starts fine if telnet is disconnected. But withing 10-20 seconds of starting telnet, Logic crashes. In other words, I can't use Logic now. Here is the dump from one of those crashes.

Bob, N7IP