Recent Posts

Pages: 1 ... 7 8 [9] 10
81
EchoHam / Re: EchoHam V2 - looking for beta testers
« Last post by CT1AKJ on December 24, 2015, 10:25:41 AM »
More one interested in testing the beta v2
Merry Christmas to all.
Joaquim Rodrigues
CT1AKJ
OS X El Capitan 10.11.2
82
EchoHam / Re: New version fo El Capitan?
« Last post by KM4JFM on December 18, 2015, 05:01:12 PM »
KB8ZGL, I've just joined this forum. The latest version of El Capitan is waiting to be down loaded to my MAC, so you should be seeing something pretty soon for El Capitan. I'm downloading OS X 10.10.5 right now.
Rick  KM4JFM
83
EchoHam / Re: EchoHam V2 - looking for beta testers
« Last post by DHusk on December 15, 2015, 10:20:15 PM »
Would love the chance to beta test the software. 

73

Vk6facb
84
EchoHam / Re: EchoHam V2 - looking for beta testers
« Last post by KM0S on December 15, 2015, 12:38:37 PM »
Please add my name to the "nice" list of beta testers. Thanks 73, Mike
85
EchoHam / Re: Registration difficulties with password
« Last post by support on December 13, 2015, 09:19:41 AM »
As far as I can see there is no limitation imposed on passwords on the client end.
Unfortunately there is no documentation available on the Echolink protocol, everything I know has come from studying the original EchoMac code.

In V1 of EchoHam server connection code is from the old EchoMac application, problems such as timeouts are not handled very well, V2 will have new code which addresses these issues.
86
EchoHam / Registration difficulties with password
« Last post by tnalpgge on December 12, 2015, 01:52:20 AM »
This will be more of a bug report, since I eventually achieved a successful registration and login.  Though I think it may be useful to share what I learned along the way.  I am doing this from a Mac Pro, late 2013 model, running OS X 10.9.5.  EchoHam reports its version as 1.10 (840).

My first attempts to register (I am not logged in at this point, the system does not know my password yet!) involved a 16-character password that ended in a double-quote (").  The rest of the password did contain both capital and lowercase letters, numbers, and other punctuation symbols, but no whitespace.  The login process would simply hang until the client complained that it was not able to connect.  After I removed the double-quote things appeared to work normally.

To me this suggests:
  • The double-quote character is not welcome in passwords.  Are there other unwelcome characters?
  • EchoHam does not handle 16-character passwords correctly, but shorter passwords are fine.
  • Whatever network protocol EchoLink uses for login does not properly handle passwords longer than a certain length.  This would be a server bug, not a client bug.
  • Some combination of the above.

Are there other reports of problems around password length, or specific password content?

I also discovered other authentication-related problems while attempting to debug this.  I would prefer to report them privately to a responsible party.  I can PGP encrypt if desired.
87
EchoHam / Re: EchoHam V2 - looking for beta testers
« Last post by VK2DY on December 09, 2015, 12:00:37 PM »
Hi,

I am interested in trying out the beta.

Robert

88
EchoHam / Re: New version fo El Capitan?
« Last post by support on December 09, 2015, 10:11:24 AM »
EchoHam V2 will be compatible with El Capitan.
Please see this thread for further information.
89
EchoHam / EchoHam V2 - looking for beta testers
« Last post by support on December 09, 2015, 10:07:04 AM »
Coding for EchoHam V2 is happening now.
The user interface has undergone a major revamp and the code from the old EchoMac version has been completely discarded and replaced with code written specifically for OS X.
If you are interested in beta testing V2 before it goes on the AppStore please leave a reply in this thread and click the "Notify" button to receive updates from this thread.

V2 is now ready for beta testing.
If you have registered on this forum please make sure your email address is still valid so we can email you the Beta version.

Thank You
90
Serial Tools / Unable to re-open recent config file
« Last post by jcanning on December 01, 2015, 03:24:26 AM »
I've enjoyed using SerialTools on my Mac to connect to a USB serial port.  I am able to save configuration files, but I can't re-open them from the File > Open Recent menu.  When I use Open Recent, I get the error message "Could not find file.  File may have moved or have been deleted, or of the wrong type."  I can use the File > Open menu item, navigate to the config file using the browse files dialog, and successfully open it.  I can also open a OSX Finder window, navigate to the config file, double click it, and launch SerialTools with that configuration.  SerialTools only fails to find the file when using "Open Recent".

Interestingly, if I successfully open a config file, then close that session but keep Serial Tools running another session, and then ask to create a new session using Open Recent on the previously opened file, it works.  The failure happens only after launching the SerialTools program on another config file or with no config file.  In other words, Open Recent can re-open a config file that was used by the current program, just not in previous runs of the program. The failure doesn't seem to depend on the pathname to the config file.  It happens both on pathnames that include special characters (space, asterisk, apostrophe, etc.) and on those that don't include special characters.  I am using SerialTools Version 1.3 (141) on a Mac running OS X 10.10.5.

Also to correct the English of the error message, it should say "Could not find file.  File may have moved or have been deleted, or be of the wrong type."
Pages: 1 ... 7 8 [9] 10