Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ooo-dev@incubator.apache.org
Date: Sun, 16 Sep 2012 09:15:33 -0300
From: Ariel Constenla-Haile <arielch@apache.org>
To: ooo-dev@incubator.apache.org
Subject: Re: Missing Visual C++ Libraries in all recent versions of Open
 Office installer
Message-ID: <20120916121533.GA28176@localhost>
References: 
 <1347705790.3282.140661128236713.0BCA63AD@webmail.messagingengine.com>
 <20120915140303.GB26530@localhost>
 <5054AAE9.3070508@apache.org>
 <1347792376.31419.140661128530545.7F2EB927@webmail.messagingengine.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="MGYHOYXEY6WxJCY8"
Content-Disposition: inline
In-Reply-To: 
 <1347792376.31419.140661128530545.7F2EB927@webmail.messagingengine.com>
User-Agent: Mutt/1.5.21 (2010-09-15)

--MGYHOYXEY6WxJCY8
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sun, Sep 16, 2012 at 03:46:16AM -0700, jsmith321@fastmail.fm wrote:
> Being on a 64 bit system I removed the msvcr100.dll from my SysWOW64
> directory and confirmed that Base will not work, it reports that Java is
> corrupt. Copying the msvcr100.dll to the "C:\Program Files
> (x86)\OpenOffice.org 3\program" directory restored functionality to Base
> and wizards.=20
>=20
> I'm sure that including msvcr100.dll in the program's main directory
> (where msvcr71.dll and msvcr80.dll are already included) would be a good
> enough solution, unless there is something in the Microsoft licensing
> agreement that says you can't split the files up like that.=20
>=20
> Even if it is not the fault of Open Office Developers that it is broken,
> pointing fingers (even in the correct direction) does nothing to gain
> new users.=20


It's funny how people get dramatic. I wasn't pointing fingers, I was
simply describing my interpretation of the "facts"; the fact is that
there is a bug, that has to be closed as wontfix or left open depending
on a *new* one: install the MSVCRedist (which IMO is no defect, but
a request for enhancement).

I quote again the link in my previous mail:
http://www.duckware.com/tech/java6msvcr71.html it has a dramatic and
hilarious tone, with its bold, italic, and red: "Sun's fix is to copy
msvcr71.dll next to the EXE. But in the future, when Sun moves on to
another msvcr##.dll version, your EXE will still work, right? NO. Your
'fixed' app works just fine now, but when Java 7 ships and requires
msvcr100.dll, your application will once again break. Sun has learned
nothing from this experience because they are recommending a course of
action where they know that EXE's will once again break in the future
when a new Java VM is shipped."

> I hope my comments on this issue are welcomed

Yes, they are :) In fact, you solved the mystery of this bug that
no developer could reproduce (no one can fix something she/he cannot
reproduce).


Regards
--=20
Ariel Constenla-Haile
La Plata, Argentina

--MGYHOYXEY6WxJCY8
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJQVcLlAAoJEMjP1bm45QNW9FsP/2U+CsZqQQtcWna65Mh7D0zn
g38YYVPiPtIuya+8DV0L86jmYmFNp1jv+tdCGyiYSWVny3lESsO7hkSdY1F2QblW
I+putM1BlaEQY9/PdLGF/ZO0AQGHLwL7pD+fc3CcpX8D+KJgj4TNNXh/5U0ydEz7
QV3UR4zAsetBGetdbJhDAPWx6Kk3Jn0OIX/iDPUsthk/hyGFzlmphjhgKBxmyI0r
c5iXkUXRGkPDpQu1kDFe/Vku8ZKRvUve7Fv+WsxZgWWanrwbU2ivmvsMN1ro6edE
67dts3wmK669A8h+H+OYaKG1LXLgfqmF8g765wjpzGGsDGlvBFWTtOUZpl35Nmq6
KNvvjo/LdvLghLdXfnlE8W2ZTx7zWl0CDA0oSz47xXCUhzwFLzpydbFEsj9Y83S/
45bivfUVjvqmGIuHx413zKEyRRDmpUqKyg5LGoSa1mgDoi9yFNqWD0su88boJ5Qw
5g6RqvxWBQuRWzZEtCvMOnZsq9q1RlJKJvEgxqj/TVkia/ICC3+MRlIZDpO1M8az
2lFzDphRym9ZxRjkncVHxC9u7+ux6OtDgKb4AwY0SriSWnon7Eo8AgiMudaKkbNG
iC0PsjT5SceDtzsljQPT5kSDMm+mdrsTKbqtChYaIT4Eu5ghJJppDyHGyUlyQ6zW
ARI8kpF6I0eF+aQuGIK4
=8ddZ
-----END PGP SIGNATURE-----

--MGYHOYXEY6WxJCY8--