What arguments to use to call winemenubuilder by hand?

[Uwe Bonnes]

Hallo,

the error
> err:menubuilder:extract_icon32 LoadLibraryExW\
> (L"C:\\altera\\quartus60\\win\\quartus.exe") failed, error 126
> with varying file targets seems to be a common one. The one above happened
> with the current 0.9.12 and Altera's quartusii_60_web_edition.exe, running
> with XP-native ole32,oleaut32 and rpcrt4. Without these native dlls,
> installation hangs at an early stage.

"Error 126" is
> include/winerror.h:#define ERROR_MOD_NOT_FOUND 126
> so I guess that winemenubuilder is invoked in an too early stage where the
> executables are not already deployed.

I tried to decipher, what is calling winemenubuilder and when, but did't succeed.
Google also wasn't a big help.

Can anyone give a short explanation?

Bye
-- 
Uwe Bonnes                bon(a)elektron.ikp.physik.tu-darmstadt.de

Institut fuer Kernphysik  Schlossgartenstrasse 9  64289 Darmstadt
--------- Tel. [phone] -------- Fax. [phone] ----------

[Vitaliy Margolen]

Tuesday, May 9, 2006, 7:12:29 AM, Uwe Bonnes wrote:
> Hallo,
> the error
> > err:menubuilder:extract_icon32 LoadLibraryExW\
> > (L"C:\\altera\\quartus60\\win\\quartus.exe") failed, error 126
> > with varying file targets seems to be a common one. The one above happened
> > with the current 0.9.12 and Altera's quartusii_60_web_edition.exe, running
> > with XP-native ole32,oleaut32 and rpcrt4. Without these native dlls,
> > installation hangs at an early stage.
> "Error 126" is
> > include/winerror.h:#define ERROR_MOD_NOT_FOUND 126
> > so I guess that winemenubuilder is invoked in an too early stage where the
> > executables are not already deployed.

It's misleading. It first tries to extract icon from file as PE. Then it
tries that file as an .ico file. If that fails, it queues itself into
RunOnce to be started by wineboot.

But it looks like something really broke that part. We now trying to
create links to "c:\"c:\Program Files\Prog\App.exe"". Which wasn't the
case before.

That's on top of lots of other problems that are still exists in
winemenubuilder and still not fixed.


Vitaliy.

[Tom Spear]

On 5/9/06, Vitaliy Margolen <wine-devel(a)kievinfo.com> wrote:
> Tuesday, May 9, 2006, 7:12:29 AM, Uwe Bonnes wrote:
> > Hallo,
> > the error
> > > err:menubuilder:extract_icon32 LoadLibraryExW\
> > > (L"C:\\altera\\quartus60\\win\\quartus.exe") failed, error 126
> > > with varying file targets seems to be a common one. The one above
> > > happened
> > > with the current 0.9.12 and Altera's quartusii_60_web_edition.exe,
> > > running
> > > with XP-native ole32,oleaut32 and rpcrt4. Without these native dlls,
> > > installation hangs at an early stage.
> > "Error 126" is
> > > include/winerror.h:#define ERROR_MOD_NOT_FOUND 126
> > > so I guess that winemenubuilder is invoked in an too early stage where
> > > the
> > > executables are not already deployed.
>
> It's misleading. It first tries to extract icon from file as PE. Then it
> tries that file as an .ico file. If that fails, it queues itself into
> RunOnce to be started by wineboot.
>
> But it looks like something really broke that part. We now trying to
> create links to "c:\"c:\Program Files\Prog\App.exe"". Which wasn't the
> case before.
>
> That's on top of lots of other problems that are still exists in
> winemenubuilder and still not fixed.
>
> Vitaliy.

I recall seeing this problem with the deprecated wineshelllink script,
although it didn't give this error, as that was not a part of the script.
What happens (although not in this case, because of what Vitality explained
with the double "C:\") is that under windows, an installer can create a link
before the executable, dll, or ico is actually properly extracted.  This
works because of the way that windows lnk files work.  Under wine, since we
are actually trying to extract the icon, the executable has to be there, and
when it isn't we fall back to running it on the next invocation of wine by
the user, by putting it in runonce.  As for the "C:\" being doubled, I
dunno, but it def wont work at all that way.