Date: prev next · Thread: first prev next last
2014 Archives by date, by thread · List index


Gary Collins wrote
   Hi, I've tried installing the secfix version of LO to run in parallel
with the version I generally use (on Windows 7). The instructions in the
link were unclear (or just plain wrong), but I did finally manage to get
the installer to complete, apparently successfully, i.e. the installer
"wizard" reported that install was OK and the files appear to be
there, but when I try to start  it up it crashes with the error
    "Application Error: The application was unable to start correctly
(0xc000007b)"
Does anyone have the explanation (and hopefully also the remedy) for
this?Thanks,/Gary

Gary,

I do hundreds of these installs, and at the moment in addition to current
4.3.3.2 build, I have 16 parallel builds of prior release and TB daily
builds available to use on Windows.  So, doing this is second nature to me. 

I just reviewed the "in parallel" instructions for Windows builds (Version
3.5.x and newer) on the Wiki:

https://wiki.documentfoundation.org/Installing_in_parallel

Two key points for in parallel loads that should help you sort things:

On Windows builds we use the Microsoft Installer mechanism to perform an
"Administrative" installation of the package with the /A flag.  Lots of
general support online for what happens with Administrative installations of
.msi packages.  But the important part is that the typical installation does
not actually install anything--it just fully extracts it to the system.  And
the step to specify the target directory  with TARGETDIR= is very necessary
to do things consistently into a location other than the Download folder.
Personally  I set it to a folder named for the build on the C: drive, e.g.
TARGETDIR="C:\LO42363_20140904"

The other aspect, in the User Configuration section of the Wiki, is that the
default extraction sets the program to use  an internal LibreOffice variable
$SYSUSERCONFIG that on launch points to your Windows %APPDATA%
directory--and would interfere with content of your actual installation.  To
run installs in parallel, in the program directory the bootstrap.ini file is
edited to change the variable to $ORIGIN (i.e. where program is being
launched from) and giving it a relative path "/../Data/settings" to keep
everything on execution within the "parallel" installation.

If you get those to facets correct, things should run well for you.  If not,
it is possible that the downloaded .msi installer was corrupt.  You can
check that for the release builds by reviewing either the hash values, or
PGP signature of the file you download.  The released builds are here:
http://downloadarchive.documentfoundation.org/libreoffice/old/  and drill
down to the Windows folder where hash and signatures are on the "details"
links. Verify your download.

Hope that was clear for you, but post back if still stuck.

Stuart



--
View this message in context: 
http://nabble.documentfoundation.org/Help-with-Conditional-Macro-Please-tp4126933p4127315.html
Sent from the Users mailing list archive at Nabble.com.

-- 
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.