Mike Petersen wrote:
I am in the process of creating a "Network Install Script" for
OpenOffice.org 2.0 and I just finished capturing all of the settings a new
install makes to a Windows Machine. There are a *lot* of registry entries
created by the installer, however, OOo 2.0 Beta2 works just fine if I
simply copy the files to another computer and create new launchers.
So, is there any advantage of using CLSIDs in the Windows Registry which
OOo2 does by default ? Or, to put it another way - If I recreate my own
registry entries by not using CLSIDs and simply link file extensions to the
actual program path, what features/benefits do I loose ??
Granted, I know I won't be able to use the "QuickLaunch" feature, but I do
not want to anyway since OOo Beta 2 launches so fast (also want to avoid
that for remote upgrades anyway.)
Thanks, and if you want to check out any of my other "Network Install
Scripts" go to http://www.pcc-services.com/kixtart/scripts.html
I've had *incredible* problems with OOo not cleaning up the registry and
updating stale links when upgrading. If you have some way of overriding
what OOo wants to do and replacing it with something sane, then firstly
tell me about it, and secondly, maybe post details of what you're doing at:
http://www.openoffice.org/issues/show_bug.cgi?id=45477
--
Daniel Kasak
IT Developer
NUS Consulting Group
Level 5, 77 Pacific Highway
North Sydney, NSW, Australia 2060
T: (+61) 2 9922-7676 / F: (+61) 2 9922 7989
email: [EMAIL PROTECTED]
website: http://www.nusconsulting.com.au
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
