Re: KERNEL: honor additional DLL search paths under HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\App Paths

[Mike McCormack]

Alex Villací­s Lasso wrote:
> Changelog:
> - Check under HKLM\Software\Microsoft\Windows\CurrentVersion\App
>
> Paths\EXENAME.EXE for
>  additional directory locations to search for DLLs. Fixes Dreamweaver MX 
> 6.0.

This change is incorrect.  The App Pathes key is checked by 
ShellExecute, not by CreateProcess.

Try running "wine start exename.exe"

Mike

KERNEL: honor additional DLL search paths under HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\App Paths

[Alex Villací­s Lasso]

Mike McCormack escribió:
> Alex Villací­s Lasso wrote:
> > Changelog:
> > - Check under HKLM\Software\Microsoft\Windows\CurrentVersion\App
> >
> > Paths\EXENAME.EXE for
> >  additional directory locations to search for DLLs. Fixes Dreamweaver 
> > MX 6.0.
>
> This change is incorrect.  The App Pathes key is checked by 
> ShellExecute, not by CreateProcess.
>
> Try running "wine start exename.exe"
>
> Mike

[alex@srv64 Dreamweaver MX]$ wine start Dreamweaver.exe
fixme:exec:SHELL_execute flags ignored: 0x00000500
[alex@srv64 Dreamweaver MX]$ fixme:ole:CoRegisterMessageFilter message 
filter has been registered, but will not be used
fixme:system:SystemParametersInfoW Unimplemented action: 65 
(SPI_SETSOUNDSENTRY)fixme:shell:SHGetFileInfoW set icon to shell size, stub
fixme:shell:SHGetFileInfoW set icon to shell size, stub
err:x11drv:X11DRV_CreateWindow invalid window height -2
err:x11drv:X11DRV_CreateWindow invalid window height -4
err:x11drv:X11DRV_CreateWindow invalid window height -2
err:x11drv:X11DRV_CreateWindow invalid window height -2
fixme:imm:ImmReleaseContext (0x101cc, 0x159978): stub
fixme:imm:ImmReleaseContext (0x101cc, 0x159978): stub
fixme:imm:ImmReleaseContext (0x101cc, 0x159978): stub
fixme:imm:ImmReleaseContext (0x101cc, 0x159978): stub
fixme:imm:ImmReleaseContext (0x101cc, 0x159978): stub
err:module:import_dll Library Gemstone.dll (which is needed by 
L"C:\Archivos de programa\Macromedia\Dreamweaver 
MX\Configuration\JSExtensions\DWEMLaunch.dll") not found
fixme:imm:ImmReleaseContext (0x101cc, 0x159978): stub
fixme:imm:ImmReleaseContext (0x101cc, 0x159978): stub
fixme:imm:ImmReleaseContext (0x101cc, 0x159978): stub
fixme:imm:ImmReleaseContext (0x101cc, 0x159978): stub

Dreamweaver still can't find the DLL without my patch, even with the 
"start" command, as demonstrated in the previous trace. Did you mean 
that my patch *should* have placed the check in ShellExecute? Does 
cmd.exe from Windows XP use CreateProcess or ShellExecute? I plan to 
install DreamWeaver MX 6 inside a virtual machine, to check actual 
behavior. If cmd.exe uses CreateProcess and your statement is correct, 
then the error message should also appear when Dreamweaver.exe is 
executed from the command line.

KERNEL: honor additional DLL search paths under HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\App Paths

[Vitaliy Margolen]

Alex Villací­s Lasso wrote:
> Mike McCormack escribió:
> > Alex Villací­s Lasso wrote:
> > > Changelog:
> > > - Check under HKLM\Software\Microsoft\Windows\CurrentVersion\App
> > >
> > > Paths\EXENAME.EXE for
> > >  additional directory locations to search for DLLs. Fixes Dreamweaver
> > > MX 6.0.
> >
> > This change is incorrect.  The App Pathes key is checked by
> > ShellExecute, not by CreateProcess.
> >
> > Try running "wine start exename.exe"
> >
> > Mike
>
> [alex@srv64 Dreamweaver MX]$ wine start Dreamweaver.exe
> L"C:\Archivos de programa\Macromedia\Dreamweaver
> MX\Configuration\JSExtensions\DWEMLaunch.dll") not found
>
> Dreamweaver still can't find the DLL without my patch, even with the
> "start" command, as demonstrated in the previous trace. Did you mean
> that my patch *should* have placed the check in ShellExecute? Does
> cmd.exe from Windows XP use CreateProcess or ShellExecute? I plan to
> install DreamWeaver MX 6 inside a virtual machine, to check actual
> behavior. If cmd.exe uses CreateProcess and your statement is correct,
> then the error message should also appear when Dreamweaver.exe is
> executed from the command line.

You have to run it from other directory. Actually from _any_ directory
but the one that exe is in. Don't ask me - ask m$ why they came up with
this sort of .... stuff.

Btw it will fail on win exactly the same way.

Vitaliy

KERNEL: honor additional DLL search paths under HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\App Paths

[Alex Villací­s Lasso]

Vitaliy Margolen escribió:
> Alex Villací­s Lasso wrote:
> > Mike McCormack escribió:
> > > Alex Villací­s Lasso wrote:
> > > > Changelog:
> > > > - Check under HKLM\Software\Microsoft\Windows\CurrentVersion\App
> > > >
> > > > Paths\EXENAME.EXE for
> > > >  additional directory locations to search for DLLs. Fixes Dreamweaver
> > > > MX 6.0.
> > >
> > > This change is incorrect.  The App Pathes key is checked by
> > > ShellExecute, not by CreateProcess.
> > >
> > > Try running "wine start exename.exe"
> > >
> > > Mike
> >
> > [alex@srv64 Dreamweaver MX]$ wine start Dreamweaver.exe
> > L"C:\Archivos de programa\Macromedia\Dreamweaver
> > MX\Configuration\JSExtensions\DWEMLaunch.dll") not found
> >
> > Dreamweaver still can't find the DLL without my patch, even with the
> > "start" command, as demonstrated in the previous trace. Did you mean
> > that my patch *should* have placed the check in ShellExecute? Does
> > cmd.exe from Windows XP use CreateProcess or ShellExecute? I plan to
> > install DreamWeaver MX 6 inside a virtual machine, to check actual
> > behavior. If cmd.exe uses CreateProcess and your statement is correct,
> > then the error message should also appear when Dreamweaver.exe is
> > executed from the command line.
>
> You have to run it from other directory. Actually from _any_ directory
> but the one that exe is in. Don't ask me - ask m$ why they came up with
> this sort of .... stuff.
>
> Btw it will fail on win exactly the same way.
>
> Vitaliy

[alex@srv64 ~]$ pwd
/home/alex
[alex@srv64 ~]$ wine start "C:\Archivos de 
programa\Macromedia\Dreamweaver MX\Dreamweaver.exe"
fixme:exec:SHELL_execute flags ignored: 0x00000500
[alex@srv64 ~]$ fixme:ole:CoRegisterMessageFilter message filter has 
been registered, but will not be used
fixme:system:SystemParametersInfoW Unimplemented action: 65 
(SPI_SETSOUNDSENTRY)fixme:shell:SHGetFileInfoW set icon to shell size, stub
fixme:shell:SHGetFileInfoW set icon to shell size, stub
err:x11drv:X11DRV_CreateWindow invalid window height -2
err:x11drv:X11DRV_CreateWindow invalid window height -4
err:x11drv:X11DRV_CreateWindow invalid window height -2
err:x11drv:X11DRV_CreateWindow invalid window height -2
fixme:imm:ImmReleaseContext (0x101cc, 0x159a10): stub
err:module:import_dll Library Gemstone.dll (which is needed by 
L"C:\Archivos de programa\Macromedia\Dreamweaver 
MX\Configuration\JSExtensions\DWEMLaunch.dll") not found

If my home directory is not considered being outside the Dreamweaver 
directory, I don't know what is.

So, I should assume ShellExecute has code that duplicates the 
functionality I tried to add with my patch? Then I need to see why it is 
not working.

Alex Villacís Lasso

KERNEL: honor additional DLL search paths under HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\App Paths

[Vitaliy Margolen]

Alex Villací­s Lasso wrote:
> Vitaliy Margolen escribió:
> > Alex Villací­s Lasso wrote:
> > > Mike McCormack escribió:
> > > > Alex Villací­s Lasso wrote:
> > > > > Changelog:
> > > > > - Check under HKLM\Software\Microsoft\Windows\CurrentVersion\App
> > > > >
> > > > > Paths\EXENAME.EXE for
> > > > >  additional directory locations to search for DLLs. Fixes Dreamweaver
> > > > > MX 6.0.
> > > >
> > > > This change is incorrect.  The App Pathes key is checked by
> > > > ShellExecute, not by CreateProcess.
> > > >
> > > > Try running "wine start exename.exe"
> > > >
> > > > Mike
> > >
> > > [alex@srv64 Dreamweaver MX]$ wine start Dreamweaver.exe
> > > L"C:\Archivos de programa\Macromedia\Dreamweaver
> > > MX\Configuration\JSExtensions\DWEMLaunch.dll") not found
> > >
> > > Dreamweaver still can't find the DLL without my patch, even with the
> > > "start" command, as demonstrated in the previous trace. Did you mean
> > > that my patch *should* have placed the check in ShellExecute? Does
> > > cmd.exe from Windows XP use CreateProcess or ShellExecute? I plan to
> > > install DreamWeaver MX 6 inside a virtual machine, to check actual
> > > behavior. If cmd.exe uses CreateProcess and your statement is correct,
> > > then the error message should also appear when Dreamweaver.exe is
> > > executed from the command line.
> >
> > You have to run it from other directory. Actually from _any_ directory
> > but the one that exe is in. Don't ask me - ask m$ why they came up with
> > this sort of .... stuff.
> >
> > Btw it will fail on win exactly the same way.
> >
> > Vitaliy
>
> [alex@srv64 ~]$ pwd
> /home/alex
> [alex@srv64 ~]$ wine start "C:\Archivos de
> programa\Macromedia\Dreamweaver MX\Dreamweaver.exe"

This is not correct. You need _literally_ run :
wine start Dreamweaver.exe

And you can not be in the directory with that program.

Vitaliy

KERNEL: honor additional DLL search paths under HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\App Paths

[Mike McCormack]

Alex Villací­s Lasso wrote:
> Dreamweaver still can't find the DLL without my patch, even with the 
> "start" command, as demonstrated in the previous trace. Did you mean 
> that my patch *should* have placed the check in ShellExecute? Does 
> cmd.exe from Windows XP use CreateProcess or ShellExecute?

cmd.exe uses CreateProcess by default, and ShellExecute if you use 
"start".  The ShellExecute code isn't perfect, so if you're going to fix 
something, start looking there.

Mike