The only times I've seen anything like this was; one time I had installed just the program files, not the vectors (duh), and when after an update often times the scanboot and Nebula temp files need to be deleted and rebuilt.
Are you reinstalling windows from a saved image or from the install disc. You shouldn't need to reinstall an OS just to make Nebula work. Let me ask a few other Neb gurus out there and see if we can clear this up. It's odd......
dizzib wrote:I think I'm getting the same problem.
I installed Nebula3 Pro x64 1.3.492, upgraded to 1.3.504, sent in the SER and ran in the license. On launching, Nebula takes a few seconds to initialise as expected, with no libraries.
I then installed library NL_Plt#4. Launching Nebula then seems to skip the initialise phase, again showing no libraries!?
I've never had a problem with licensing before, and I'm fairly sure I'm doing everything right.
No emulation preset at all? = Wrong path in MAST page .XML file.
So am I right in assuming from your response that you do have to get a new autho file every time you want to reinstall windows or nebula?
i think what enrique is saying there, is that maybe your n2ps are in the wrong place. if you look at the .xml file that should be in the same spot as your actual nebula.dll (the vst plugin file itself), it is like an initialization file. you can look at that xml in a txt editor, and add extra paths, places on your hd where n2ps can go. i think that's all enrique is asking, is to check and make sure your n2ps are in the right spot.
my personal feelings are that i agree with whoever said you shouldn't have had to reinstall windows to get it working. the main area to focus on would be possibly re-installing nebula itself, and also making sure to delete the xmls in the 'temp' folder inside the 'nebulatemprepository' folder.
those xmls in the 'temp' folder, they are re-generated by nebula every time you open (if they are missing), so it's ok to delete them. and if you ever make any dramatic change with your nebula stuff, it's a good idea to clean that folder out. if that doesn't help (and i actually don't expect it to in this case), maybe an uninstall/reinstall of nebula.