Re: Re: Nominating Issue 116439 and accepting Issue 116318 and Issue 116371
Thorsten Ziehm <[email protected]> Fri, 14 Jan 2011 10:54:11 +0100
| Newsgroups | gmane.comp.openoffice.releases |
|---|---|
| Message-ID | <[email protected]> |
Hi Volker and Olaf, Am 14.01.2011 10:29, schrieb Olaf Felka: > Hi Volker, > > On 01/14/11 10:22, Volker Merschmann wrote: >> Hi, >> >> 2011/1/14 Olaf Felka<[email protected]>: >>> On 01/14/11 09:48, Thorsten Ziehm wrote: >>>> as I heard and what I could read in the issue it isn't a general >>>> problem >>>> with installing OOo 3.3 RCx on Windows 2000. So it isn't needed to >>>> change the system requirements. Because it couldn't reproduced on every >>>> Windows 2000 system. >>>> >>>> If you have the same problem as Volker, please help to identify the >>>> rout cause of the error. >>>> >>>> On the other hand please take also a look in the Windows Knowledge >>>> database or google about the problem (search for "Windows 2000 >>>> MSVCR90.DLL missing"). You will see, it isn't a OOo-Problem only. >>>> A lot of software have such problem with this operation system. >>>> >>> >>> this is not a general problem in OOo. It seems that the problem is >>> caused by >>> the vcredist.exe and the Microsoft Installer (MSI). >>> OOo requires MSI version 2.x. Vcredist requires MSI version 3.x. As >>> you can >>> read in issue 116035 Volkers system provides MSI 2.x. >>> >>> Updating the Microsoft Installer on e.g. >>> http://www.microsoft.com/downloads/en/details.aspx?displaylang=en&FamilyID=889482fc-5f56-4a38-b838-de776fd4138c >>> >>> will solve the problem. >>> >> I will continue to help with the investigation. >> Please have an in mind that I used a relatively fresh system for the >> test which has been set up in a VM just for testing the builds. So >> anyone could stumble into this. You can't count in that other >> installation have brought the missing/updated system parts before. > > I don't think that a fresh installed system is a common use case of a > ten year old operating system. I second this. If a company use Win2000 as work environment, they are stubled or will stumble over this problem with other software also. So they have to fix this problem anyway. Thorsten