To explain further:
The Simulator connection has been available in JMRI for along time and has rarely caused user confusion.
The Internal connection type is needed for some non-connection type features.
At some stage the Internal connection type was made visible but rarely caused user confusion.
Some people liked the idea of an automatic fallback to Internal if a connection wasn't working properly, with normal operation being restored next time. Effectively a "lazy Simulator mode". This was introduced in V4.10 (not without dissent). Unfortunately there were many circumstances in which the Internal switchover occurred and in many cases the Internal setting was unwittingly saved into Preferences (became permanent and needed manual correction).
We put a lot of effort into remedying the situation with V4.12 but it didn't prevent all possible permanent switchover problems.
With V4.14 we have removed the automatic switchover and prevented the user manually selecting Internal if an alternative is available.
But no matter what version you have, in many cases you will have to fix the problem manually. Reverting to an older version than V4.14 just increases the risk of the problem recurring in the future.
toggle quoted message
Show quoted text
On 14 Jan 2019, at 5:05 PM, gwi8251315 via Groups.Io <gwi8251315@...> wrote:
Dave
I memo'd a Massoth problem a few minutes ago 1/13/18.
What IF I re-install 4.10 then 4.14 around 4.11/ 4.12/ 4.13 OR run 4.10 until the issue is resolved/
Reinstalling older versions will not fix your problem. The problem was caused by an issue in V4.12, but reinstalling v4.10 will never fix it. It will now be there in V4.10!!!
You must install V4.14 or later (over the top of whatever you currently have) and manually fix the problem as Bob and I have explained.
Trying to remove JMRI manually and reinstall will not fix the problem and could cause you to lose all your data (Roster entries, Panels, etc. - anything you have created).
--
Dave in Australia
