Mouse Key

[OC71]

I am still working at making a usable paddle out of a mouse. It works, but the problem is latency.

 

[G4HAA]

I am still working at making a usable paddle out of a mouse. It works, but the problem is latency.

Is this the mouse itself causing the latency, or the software it's feeding in to/using I wonder?

73, Mark...

 

[OC71]

It's the software. It's xcwcp from the unixcw suite:

http://unixcw.sourceforge.net/

which, like most of ham software, is almost abandonware.

I am thinking of setting up a partition with ReactOS and try some Windows software but I'm not holding my breath.

 

[G4HAA]

I use an old Samsung laptop for work (while on my breaks), I found that Lint Mint and the like ran too slowly on it. After some digging around I found Q4OS which runs much faster and seems to works quite well.

I was thinking, could you not use CW-Comm? For sending practice it will decode what you send, and for receiving practice you could just past text files straight in to it and get it to send them.

If you paste the text in to CW-Comm it will send it as text but there will be no CW audio. What you do is open CW-Comm twice on your machine and give each instance a different 'call sign'. Then tick the "translate TEXT ONLY messages to Morse" option.

Then when you paste some text in to one screen  CW-Comm will send the text, and the second screen/instance of CW-Comm will convert it to CW.

The only down side is that you do need to be online for this to work as each 'screen' will be 'talking' to the other via the virtual ionosphere.

73, Mark...

 

[OC71]

CWCom is Windows-only and, for the reasons we already went through in the past, I don't and can't use Wine. However, I might try and see of this works on ReactOS.

 

[G4HAA]

Yes, it is Windows only, but I run it here on both Linux Mint (laptop at home), and Q4OS (Linux laptop at work), both using WINE.

I found it performs exactly the same on a Windows 10 laptop, with all the same (occasional) glitches.

Neither of the Linux machine are particularly high spec, in fact the one at work is maybe ten or more years old now, just a cheap net-book style unit.

Anyway, it was just a suggestion...

 

[OC71]

In the meantime, I have just realised that ReactOS is crap and it's no way to go.

With regards to Linux, see my other thread about morse over ip. One day, I'll have to go and dig a way to make it work for me. At this moment, I have some personal issues that prevent me from doing that but it's in my TODO, however long it's going to take.

 

[OC71]

Sorry for going off topic. I've found a way to boot Reactos. I'll try to install CWCOM and I'll create  e new thread.

 

[G4HAA]

I've split this 'project' away from the original post (makes more sense as a separate thread).

I was reading about React-OS. I was surprised to find that...

ReactOS has been in development since 1996. As of October 2020, it is still considered feature-incomplete alpha software, and is therefore recommended by the developers only for evaluation and testing purposes.

73, Mark...

 

[OC71]

Yes, it's like a butchered version of Windows  Nt4 Windows Server 2003. DHCP doesn't work and networking is finicky, but I could sideload some Windows applications that I have already downloaded. It's 100% Open Source, though. It's built on top of Wine, with the difference that Wine can emulate Windows 10 and ReactOS can't. Some screenshots attached.