I m not an expert but maybe the installer on a bought OpenOffice 3.2 CD from 
3rd party distributors is the cause for this.

I think this is a different, unrelated issue towards the exe file or the 
translation.
I am not sure if we can tweak our installer to be able to handle these cases.


Am 24. Februar 2020 05:56:13 MEZ schrieb Brian Barker 
<b.m.bar...@btinternet.com.INVALID>:
>At 14:01 23/02/2020 +0100, Peter Kovacs wrote:
>>We are discussing from time to time, that it might be worth to 
>>remove the packaging to the exe completely.
>>
>>To my knowledge in the past we did create an exe because you could 
>>not doubleclick msi files. But Microsoft had fixed this for quite 
>>some time and there is no real reason to keep the exe packaging.
>>
>>So any objections?
>
>I'm no expert, but my understanding is that the .msi file is a 
>database, required just as much during removal of any product as 
>during installation. My impression is that products such as Microsoft 
>Office quietly salt away a copy of the .msi file (or as much as is 
>needed) and Windows uses this when the product is removed. Failing 
>that, Windows remembers where the .msi file was during installation 
>and seeks it out, asking for it if necessary. And all this applies 
>when removal is effected by installing a later version, doesn't it?
>
>Now the user may have thought (or even been told) that, once the 
>product is installed, the downloaded files are no longer needed and 
>may have deleted them. This used to result in a steady stream of 
>requests to the Users list, asking how the new version can be 
>installed when the process stalls at this point. Indeed, as recently 
>as ten days ago, a user trying to install a current version reported 
>to the Users list "Every time I try I get a message to insert the 
>Open Office.org 3.2 disk". He must have installed the older version 
>from a CD - which he may well no longer have.
>
>Will distributing .msi files result in the same problem to occur 
>again? Or is OpenOffice now prepared similarly to salt away the 
>necessary parts of the installation database? If not, what was (and 
>is) the cause of the problem, please?
>
>Brian Barker  
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>For additional commands, e-mail: dev-h...@openoffice.apache.org

Reply via email to