Hi-
 
I'm running X3e x64 "for real" under Win 8.1, but I need Win7 x64 for some other things and would like to install SONAR there as well so I don't have to reboot just for trivial things. If I install X3e under Win7, I'll be able to bypass all the plugins and content, etc. that I already have installed, correct?
 
Thanks-
 
-Susan

Not necessarily, a lot of info for plugins are stored in the registry.
 

gustabo
Not necessarily, a lot of info for plugins are stored in the registry.
 

Hi gustabo-

But if I elect not to install as many plugins as possible and some still insist on being registered during the X3 install, can I at least not duplicate the content? I can't remember which, if any, allowed me to specify a content directory.
 
Thanks-
 
-Susan

If it re-installs the content on the Win 7 install - just delete it.
You should get a choice though - what to install and what not to...

Sorry, misunderstood you, thought you meant installing Sonar and using your existing vstplugins directory for the plugs.
 

jbraner
If it re-installs the content on the Win 7 install - just delete it.
You should get a choice though - what to install and what not to...

Hi John-
 
IME, deleting the content in one install can mess up the content location in another, but I guess I'll go ahead and try it.
 
Thanks-
 
-Susan

Just make sure you install it *somewhere different* in the second install ;-)
Or don't install it at all (if possible)

The two Windows installations will be entirely seperate and the configuration of one will not affect the other (apart from the boot manager, obviously). Software installed in one will generally not be usable in the other without a seperate install. I've riun Sonar under Windows dual boot, but I've never tried to have two installations, one in each Windows install, with shared anything. My setup was a "general" installation and a "DAW only" installatoin.
 
You might get away with only installing the Sonar content once and pointing both installations at it, but any changes to it made by one installation might confuse the other. As for plugins, again you might get away with pointing both installations at the same VST directories and having the second one scan it without re-installing the plugins in the second Windows install. However I wouldn't bet on it working and certainly not bet on such a setup being trouble free. If the plugin installation routine writes anything to the registry or there are files the plugin uses (i.e. it's not a stand-alone dll) then expect a mess unless you do seperate installs for each Windows installation. If plugins have licensers (e.g. Waves) then that will need a seperate install for each OS.
 
A further problem might be permissions, as Windows 1 might be unwilling to write to directories in Windows 2 and vice versa because the file permissions indicate it shouldn't. This is particularly likely in the Program Files directories or Windows directory itself.

tlw
The two Windows installations will be entirely seperate and the configuration of one will not affect the other (apart from the boot manager, obviously). Software installed in one will generally not be usable in the other without a seperate install. I've riun Sonar under Windows dual boot, but I've never tried to have two installations, one in each Windows install, with shared anything. My setup was a "general" installation and a "DAW only" installatoin.
 
You might get away with only installing the Sonar content once and pointing both installations at it, but any changes to it made by one installation might confuse the other. As for plugins, again you might get away with pointing both installations at the same VST directories and having the second one scan it without re-installing the plugins in the second Windows install. However I wouldn't bet on it working and certainly not bet on such a setup being trouble free. If the plugin installation routine writes anything to the registry or there are files the plugin uses (i.e. it's not a stand-alone dll) then expect a mess unless you do seperate installs for each Windows installation. If plugins have licensers (e.g. Waves) then that will need a seperate install for each OS.
 
A further problem might be permissions, as Windows 1 might be unwilling to write to directories in Windows 2 and vice versa because the file permissions indicate it shouldn't. This is particularly likely in the Program Files directories or Windows directory itself.

Hi tlw-
 
Well, I think what I'll do, then, is just not bother! It's not worth it to me just for the convenience of not having to reboot in order to try something out.
 
Thanks-
 
-Susan