Current cvs brokeness...

[James Pellow]

Hi List,

Just downloaded the most recent cvs, and noticed it can't run the Office 2000 
installer.  I haven't tried anything else, but it looks like a general msi 
failure.  I can't spend any time on this (shouldn't be playing with it at the 
office anyway...) but here is the output:

fixme:font:WineEngRemoveFontResourceEx :stub
fixme:font:WineEngRemoveFontResourceEx :stub
fixme:msi:MsiEnableLogA 00000516 "c:\windows\temp\Office 2000 Professional 
Setup (0002)_MsiExec.txt" 00000000
fixme:msi:MsiInstallProductW L"/I" L""
fixme:msi:MSI_OpenDatabaseW open failed r = 80004005!
Installation of /I () failed.

Is the msi system brocken right now?

I also noticed that the common file dialog seems to be returning garbage.  Try 
selecting a file in progman-file-execute-browse for example.

Just FYI...

[Mike Hearn]

> fixme:font:WineEngRemoveFontResourceEx :stub
> fixme:font:WineEngRemoveFontResourceEx :stub
> fixme:msi:MsiEnableLogA 00000516 "c:\windows\temp\Office 2000 Professional 
> Setup (0002)_MsiExec.txt" 00000000
> fixme:msi:MsiInstallProductW L"/I" L""
> fixme:msi:MSI_OpenDatabaseW open failed r = 80004005!
> Installation of /I () failed.

Hmm, I thought Vincent fixed that. No worries though, that looks like a 
very simple bug to solve (just parameter parsing in msiexec).
> Is the msi system brocken right now?

Yes, for Office 2000 it clearly is! You can install it anyway by 
installing native MSI from the Office CD or microsoft.com, or maybe by 
running the setup program with

WINEDLLOVERRIDES=msi=n wine setup.exe
> I also noticed that the common file dialog seems to be returning garbage.  Try 
> selecting a file in progman-file-execute-browse for example.

No clue.

thanks -mike

[Vincent Béron]

Le mer 15/09/2004 à 04:31, Mike Hearn a écrit :
> > fixme:font:WineEngRemoveFontResourceEx :stub
> > fixme:font:WineEngRemoveFontResourceEx :stub
> > fixme:msi:MsiEnableLogA 00000516 "c:\windows\temp\Office 2000 Professional 
> > Setup (0002)_MsiExec.txt" 00000000
> > fixme:msi:MsiInstallProductW L"/I" L""
> > fixme:msi:MSI_OpenDatabaseW open failed r = 80004005!
> > Installation of /I () failed.
>
> Hmm, I thought Vincent fixed that. No worries though, that looks like a 
> very simple bug to solve (just parameter parsing in msiexec).

msiexec is not used here, direct msi.dll functions are.
The problem which ws fixed was that msiexec /i did not like the package
name being glued to /i, it wanted two separate arguments. That has been
fixed by somebody else than me though.

Vincent

[Mike Hearn]

> > > fixme:font:WineEngRemoveFontResourceEx :stub
> > > fixme:font:WineEngRemoveFontResourceEx :stub
> > > fixme:msi:MsiEnableLogA 00000516 "c:\windows\temp\Office 2000 Professional 
> > > Setup (0002)_MsiExec.txt" 00000000
> > > fixme:msi:MsiInstallProductW L"/I" L""
> > > fixme:msi:MSI_OpenDatabaseW open failed r = 80004005!
> > > Installation of /I () failed.
> >
> > Hmm, I thought Vincent fixed that. No worries though, that looks like a 
> > very simple bug to solve (just parameter parsing in msiexec).
>
> msiexec is not used here, direct msi.dll functions are.
> The problem which ws fixed was that msiexec /i did not like the package
> name being glued to /i, it wanted two separate arguments. That has been
> fixed by somebody else than me though.

OK. What could cause this "Installation of /I () failed" message then? 
It looks an awful lot like a parameter passing screwup somewhere ....