Alpha 0.3.2 is here!
Most likely this is the LAST alpha release
There is mandatory switch to 0.3.2. Nodes running 0.3.x won't communicate with 0.2.x
Not updating will result in staying on a fork.
There are MANY changes in this release, we've tried our best to get rid of bugs, but because of the amount of changes, there will obviously be some…
There is already one known issue, when starting Client can claim that:
"NIS info is not avaiable yet. Trying to retrieve NIS info…"
The message will most likely stay there indefinitely, but nem-monitor should tell you if node has booted or not.
If node is booted, everything should work ok.
Changes (it might not seem so, but they are actually HUGE):
[li]Most visible: changes in settings dialog, there is possibility to use remote node (in this case you don't have to run local NIS - but it's highly appreciated as you're backing up the network!), you can try it by using san.nem.ninja as a remote[/li]
[li]new languages added or fixed, some messages might be missing, we're working on "translation portal", which hopefully will make it easier for everyone to make translations, also you can now select pirate lang in settings ;)[/li]
[li](beta feature) NTP protocol - after testing it in 0.2.18, it is now turned ON,[/li]
[li](beta feature) partial implementation of Remote Harvesting - currently invisible to users[/li]
You can start NCC and NIS with the following link:
Standalone version: http://bob.nem.ninja/
Usual Troubleshooting Guide:
[li]standalone - shouldn't have issues with this release[/li]
[li]kill any running jawa/jawaws processes[/li]
[li]Go to java control panel, and hit "View…" (can be run with javaws -viewer)
[li]from "applications" remove both NCC and NIS[/li]
[li]to be sure check resources and clean them all (this will cause redownload of everything, which might take a bit, but should help with most of the problms)[/li]
[li]If you end up on a fork, go to c:\users<i><username>, and delete NEM\NIS subdirectory[/li]