dream wrote:Ok, I did this:
- deleted these two files, EAR_HALLS.AUT and EAR_HALLS.SER;
- run the Server;
- run EAR;
- loaded a HALL preset;
- got the INIT preset.
No SER file is generated.
EDIT: if I run NebulaPro instead, the EAR_HALL.SER is generated once again.
So, where's the problem?
EDIT2: if I run the Server and I check the DISK page, I can see "CUSTOMER", so I guess Nebula is properly authorized.
Let's go to the details.
1. Nebula Server is an stand alone app. Seems that your are talking about Nebula3 Server. Nebula3 Server without Nebula Server (local or LAN) is called Nebula3 Server Client mode
2. Nebula can not generate AITB EAR .SER files due you don't have administration rights and you can not write in the Nebula folder. Please use wikigooglegood to find a solution, Windows 8 and Windows 8.1 must to do it too running CMD and enabling admin account.
3. There is not a problem but Nebula3 FREE, Pro and Server use the same path so depend the rights to write in that folder. If Nebula3 Pro create your EAR .SER file use it, Nebula3 Server (Client mode) should generate the same file/value.
4. Nebula will show CUSTOMER under REGISTERED if you have a valid key, and numbers from your .SER file if you have DEMO key, but if .SER file and Nebula key does not match Nebula will still show you CUSTOMER. This could happen if you copy files from other OSX computer or from other HDD in OSX and Windows. The best way to check that is to install an setup that will overwrite your custom key with demo one, then generate .SER file again and check number inside with old one .SER file.