mathias wrote:my understanding is, when the server application is not running, the nebula server dll is acting like a nebula pro sort of.
Incorrect. Nebula3 Server will try to find a Local or LAN Server (Remote Server) if IP and PORT tags are in MAST page in boot. If can't find a server or no IP and PORT tags, will run in a mode called local client, with RAM sharing feature that Nebula3 Pro hasn't. Here we have Nebula3 Pro + Nebula3 Server + Nebula3 FREE in order to test but we only use Nebula3 Server. Can can use Nebula3 Pro if you want backward compatibility with old project, but Nebula3 Server should be able to load any project done with Nebula3 Pro.
Running both version is not something I do regularly or I want to, also because it wouldn't be possible in my workflow. Most of the time I use just the Server version, but AITB libraries don't load (of course in my system, no idea about others, just trying to find a workaround that works for me).
So, if the project is still small I can start with Nebula Pro, load AITB (interested mostly on EAR) and then run the server. The new instances, after that point, will run under the Server, and what was loaded before still runs under Nebula Pro.
Lately "my" solution is (when I need EAR): - deactivate all Nebula instances; - close the server; - open EAR with NebulaPro (which will load this time); - print; - delete the EAR instance; - open the Server; - activate again all other Nebula instances.
Therefore sometimes it happens that I use both, but once the printing has be done Id like to use just the server. In my system (10.8.5, mostly 32 bit) I would prefer Nebula Pro because the Server, always in my system, is a little slower-ish than Pro, but the Server allow me more instances.
Wait for AITB library update. We are beta testing Nebula and AITB libraries in OSX. You should version upgrade to something higher than 1.3.668 for sure but there is not any public beta available but should work in both, Nebula3 Pro and Nebula3 Server. I always suggest to product upgrade to Nebula3 Server due RAM sharing feature.