Questions concering an application I maintain

[Jacob Alberty]

I'm aware of the WINEDEBUG stuff, just wanted to use something that gives me
uniform results, the data it outputs is the same on wine as windows, to
speed up comparison I've been going through a WINEDEBUG=+all and have found
some points of interest,  I just need data to compare that to on a real
windows machine (which I am currently setting up in a vm) This project is
ultimately going to be moved to lazarus so that I can have a native
solution, however wine is damned close to perfect with the corefonts
package, a little config tweaking and riched20.dll from the nativemsi
installer (which by the way the instructions at
http://wiki.winehq.org/NativeMsi) have been failing for me as of wine
0.9.27(tested on
0.9.28 and 0.9.29 still didnt work) fails when i run instmsia.exe with
"wine: Unimplemented function mscoree.dll.GetCORSystemDirectory called at
address 0x60368820 (thread 0013), starting debugger...
Unhandled exception: unimplemented function
mscoree.dll.GetCORSystemDirectory called in 32-bit code (0x603688a2).
"
I have been extracting riched20.dll with cabextract for use.

On 1/20/07, Andreas Mohr <andi at rhlx01.fht-esslingen.de> wrote:
>
> Hi,
>
> On Fri, Jan 19, 2007 at 02:12:49PM -0800, Duane Clark wrote:
> > Jacob Alberty wrote:
> > >What method is best to watch the api interaction going on in my
> > >application so I can see if wine is returning any weirdness that
> > >it shouldnt (do normal windows api spy programs work under wine?).
> >
> > SPY++, at least older versions, work fine under Wine.
>
> He most likely isn't talking about a message spy (i.e. SPY++),
> but about API tracers.
> apispy32 (IIRC) was one of the better API tracers on Windows.
> On Wine you just use WINEDEBUG=+relay and be done with it
> (unless you need further channels for specific Windows subsystems).
>
> Andreas Mohr
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.winehq.org/pipermail/wine-devel/attachments/20070120/dec2b4a5/attachment.htm