I also encountered the problem that the database pluto_main was not created, in it's place was pluto_local but this was empty.
Where was a problem in our postinstall scripts. (instead of pluto_local and pluto_system should be pluto_main).
The orbiter ran without complaints about missing Dll's so that's fixed.
220.127.116.11 version will have release version of our applications, so the user won't need mfc's debug dlls.
When I changed the hostname on the orbiter to localhost the orbiter shutdown and restarted but the changes were not applied.
Yes, we are aware of this bug. It's fixed in 18.104.22.168 version.
When I run the DCERouter it gives warnings that the database cannot be found so I used the command line parameters "-h localhost -u xxxx -p yyyy -D pluto_local" and it found the database but could not identify it's device ID automatically.
When I specify the -d parameter it crashed and windows asked if I wanted to report an error.
DCERouter needs pluto_main which wasn't created because of postinstall scripts issue. However, we'll need another postinstall script to insert the informations about current installation and its devices.
The hostname 'dcerouter' could still not be resolved.
If you are using the same computer to run dcerouter, the hosts file should have an entry like this "127.0.0.1 dcerouter". The installer doesn't do this yet. Use localhost for now.
Should I have any more paths set up besides C:\pluto\bin, C:\pluto\libs that settings are saved into?