Hi Ariel, > don't know others, but I always left the desktop integration for the > "stable" version I'm working with at that moment (if not, just click on > any OOo doc will open them on a version not meant for *production* , and > this is not very safe)
Yes, desktop integration is rarely needed. Don't know when I last time installed one with system integration ... Which reminds me of what I should have mentioned in my previous mail: Try msiexec /a openofficedev.msi This does a so-called administrative installation, which effectively means the .cab files (I'm talking about Windows only here, there are similar solutions for other platforms) are simply extracted. Be sure to, before you run OOo the first time, adjust the "UserInstallation" key in program/bootstrap.ini. For me, it always looks like UserInstallation=$ORIGIN/.. Since $ORIGIN expands to the program directory, this means you get a folder "user" besides the "program" folder, where "user" will take all your user data. (Which implies if you use the same installation from multiple Windows accounts, they will all share the user data - which is unlike a "normal" installation.) This procedure IMO is unbeatable when it comes to running multiple OOo versions in parallel. Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Base http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
