Pedro, *, Short of uninstalling and installing cleanly each time, these buildbot nightly versions do not clean up after themselves.
Using Microsoft's package installer -- msiexec.exe offers a reasonable work around of the /A Administrative, aka Server install, and running multiple versions in parallel. So with the nightly build downloaded, you can use any unzip program to extract the whole package into a folder. And then run the Microsoft installer in /A administrative mode. But, this does not "register" the the program as an application in the Windows registry. And, unless changed, the default user profile will conflict. So, instead you can do a bit more tweaking of the /A installation, to be able to isolate each instance of it. That is done by installing to a unique location with at TARGETDIR flag, and then editing the bootstrap.ini to make the user profile relative to the installation. E.g. the steps to install: 1.) Download a current nightly build, Apache_OpenOffice_4.2.0_Win_x86_install_en-US_1601656.exe 2.) unzip the package (rather than running it) into a folder--the name is not important, but good practice to not include spaces. 3.) open a command window (cmd.exe) and cd into the folder 4.) issue the command "msiexec.exe /A openoffice420.msi /L*v AOO420_r1601656.log TARGETDIR="C:\AOO_420_r1601656" -- note the quotes after the TARGETDIR= 5.) the Microsoft installer will perform the /A administrative install, writing a verbose log in the current folder, and creating a new directory C:\AOO_420_r1601656 -- you can review the log should there be any issues 6.) change directory into that new folder 7.) and from there change to the C:\AOO_420_r1601656\program folder 8.) make a backup of the bootstrap.ini file, and then edit the original 9.) locate the line that reads: UserInstallation=$SYSUSERCONFIG/OpenOffice/4 10.) delete the "$SYSUSERCONFIG" and replace it with "$ORIGIN/.." this moves the user configuration to a path relative to this installation, and other than the $SYSUSERCONFIG the OpenOffice/4 can be changed or left as is--personally I go with the suggested $ORIGIN/../Data/settings. Removing the SYSUSERCONFIG removes any conflict between versions. 11.) in the same C:\AOO_420_r1601656\program folder, any of the component launchers can be sent to the desktop to create a shortcut--but I usually only make one for the soffice.exe, and then from the desktop rename the shortcut to match the version -- AOO_420_r1601656 so I can keep track of it. 12.) launch the shortcut, the user profile and any registrymodifications.xcu configuration will be local to this /A install. When the next nightly build you'd like to work with is posted, simply repeat the process placing the install into a folder of its own. Stuart ________________________________________ From: Pedro Lino <[email protected]> Sent: Thursday, June 12, 2014 2:08 PM To: [email protected] Subject: Re: Using dailies under Windows Hi Ouchka msiexec / a openoffice400.msi. > This is essentially what I needed ;) I still think it would be nice if the installer detected that the build is newer and allowed to install without any "tricks". This would be more user friendly ;) Merci bien! Kind regards, Pedro --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
