To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=71342


User hro changed the following:

                What    |Old value                 |New value
================================================================================
                Priority|P2                        |P3
--------------------------------------------------------------------------------
        Target milestone|OOo 2.4                   |OOo 2.x
--------------------------------------------------------------------------------




------- Additional comments from [EMAIL PROTECTED] Mon Jan 14 16:12:18 +0000 
2008 -------
The problem does occur only, when the update is installed into the same
directory as the old Version. On default (without custom installation) this is
only true for a micro update (f.e. 2.3 -> 2.3.1).

On Win9x/ME the system does not allow DLLs to be renamed or deleted that are
mapped into a process. The stlport_vc7145.dll is mapped into the EXPLOER.EXE
process because OOo shell extensions are running in explorers process context.
Therefor the microsoft installer is not able to delete the old file or copy the
new file to the same location. On Win9x/ME it uses the wininit.ini mechanism to
simulate MoveFileEx( ..., DELAY_UNTIL_REBOOT ) but the wininit.ini only supports
8.3 filenames.

The problem is that the Microsoft Installer Engine first writes entries for
deleting the old files and after that the entries for copying the new ones. It
does not merge the entries so that the wininit.ini looks like this:

[rename]
NULL=C:\PROGRA~1\OPENOF~1\PROGRAM\STLPOR~1.DLL
C:\PROGRA~1\OPENOF~1\PROGRAM\STLPOR~1.DLL=C:\TEMP\1234.TMP

Because MSI does not detect that the second line would be sufficient the
deletion of the short file name also destroys the long file name whereas a
simple move instruction to the short file name would preserve the long one.

So this is a bug in MSI Engine (because it would be avoidable) or just "don't
use long file names on W9x".

A fix is possible but a little bit tricky: A custom action that scans the
wininit.ini for entries relating the affected OOo installations that could be
merged into one move instruction.

Workaround: First uninstall the old version, reboot, install the new version
(Also just one reboot ;-))

Changing to 2.x, P3



---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to