Re: ntdll: Fix NtQueryInformationToken(TokenGroups)

2006-05-02 Thread Robert Shearman

Dan Kegel wrote:


Rob wrote:


Fix the buffer check for NtQueryInformationToken(TokenGroups) so that it
doesn't return STATUS_BUFFER_TOO_SMALL when it shouldn't. Use the same
code for returning the required buffer and for calculating whether the
buffer is sufficient so this can't happen again.



Sadly, this doesn't seem to fix mdac installation.  I still need my
Magic Kludge:
--- a/dlls/ntdll/nt.c
+++ b/dlls/ntdll/nt.c
@@ -203,7 +203,7 @@ NTSTATUS WINAPI NtQueryInformationToken(
switch (tokeninfoclass)
{
case TokenGroups:
-len = sizeof(TOKEN_GROUPS);
+len = sizeof(TOKEN_GROUPS) + 400 /* WAG */;
break;
case TokenOwner:
len = sizeof(TOKEN_OWNER) + sizeof(SID);

Have you tested with mdac-2.7's installer?  It seems to tickle a path
you're not checking.



Hi Dan,

Sorry about this regression. Hopefully, the attached patch should fix it.

--
Rob Shearman

diff --git a/dlls/ntdll/nt.c b/dlls/ntdll/nt.c
index fb44ac3..bb5f70c 100644
--- a/dlls/ntdll/nt.c
+++ b/dlls/ntdll/nt.c
@@ -202,9 +202,6 @@ NTSTATUS WINAPI NtQueryInformationToken(
 
 switch (tokeninfoclass)
 {
-case TokenGroups:
-len = sizeof(TOKEN_GROUPS);
-break;
 case TokenOwner:
 len = sizeof(TOKEN_OWNER) + sizeof(SID);
 break;



Opera 3.21

2006-05-02 Thread Segin
when closing the list of newsgroups with the full list displayed, Opera 
crashes and gives this nice backtrace:


wine: Unhandled page fault on read access to 0x at address 
0x11df:0x29e2 (thread 0055), starting debugger...

WineDbg starting on pid 0x53
Unhandled exception: page fault on read access to 0x in 16-bit 
code (11df:29e2).

In 16 bit mode.
Register dump:
 CS:11df SS:127f DS:13e7 ES:149f FS:003b GS:0033
 IP:29e2 SP:df5a BP:df6c FLAGS:0206(   - 00  - RIP1)
 AX:6f52 BX:13e7 CX:006c DX:141f SI:1827 DI:29dc
Stack dump:
0x127f:0xdf5a:  13e7 28f7 29dc 1827 141f 127f 0160 
0x127f:0xdf6a:  127f df75 2c21 11df 006c dff4 6302 11e7
0x127f:0xdf7a:  006c 11ff  02d0 007b 02d0 a58c 7e2c
027c: sel=13e7 base=7da51108 limit=003f 16-bit rw-
0293: sel=149f base=7ccfabd8 limit=ffbf 16-bit rw-
Backtrace:
=1 0x11df:0x29e2 (0x11df:0x29e2)
  2 0x11df:0x2c21 (0x11df:0x2c21)
  3 0x6c11:0xe763 (0x6c11:0xe763)
  4 0x11ef:0xe9d7 (0x11ef:0xe9d7)
  5 0x1247:0xa1df (0x1247:0xa1df)
  6 0x11ff:0xbf14 (0x11ff:0xbf14)
  7 0x11ff:0xad75 (0x11ff:0xad75)
  8 0x11ff:0xbc9a (0x11ff:0xbc9a)
  9 0x101f:0x0468 in kernel32 (+0x643c4) (0x101f:0x0468)
  10 0x7fc636fb K32WOWCallback16Ex+0x119 in kernel32 (0x7fc636fb)
  11 0x7fa650b6 WINPROC_wrapper+0x79a in user32 (0x7fa650b6)
  12 0x7fa69c4f CallWindowProcW+0xdb in user32 (0x7fa69c4f)
  13 0x7fa40e7c in user32 (+0x50e7c) (0x7fa40e7c)
  14 0x7fa4126a SendMessageTimeoutW+0xef in user32 (0x7fa4126a)
  15 0x7fa41334 SendMessageW+0x3f in user32 (0x7fa41334)
  16 0x7fa4bf93 RedrawWindow+0x18b in user32 (0x7fa4bf93)
  17 0x7fa05a59 RedrawWindow16+0x67 in user32 (0x7fa05a59)
  18 0x7fa05c11 UpdateWindow16+0x31 in user32 (0x7fa05c11)
  19 0x7f9fa22d in user32 (+0xa22d) (0x7f9fa22d)
  20 0x7fc63fd2 in kernel32 (+0x63fd2) (0x7fc63fd2)
  21 0x11ff:0x7158 (0x11ff:0x7158)
  22 0x11ef:0xb527 (0x11ef:0xb527)
  23 0x11ef:0xbfc6 (0x11ef:0xbfc6)
  24 0x11ef:0xdcf2 (0x11ef:0xdcf2)
  25 0x1247:0xa6f8 (0x1247:0xa6f8)
  26 0x11ef:0x5562 (0x11ef:0x5562)
  27 0x124f:0x3076 (0x124f:0x3076)
  28 0x124f:0x309f (0x124f:0x309f)
  29 0x11ff:0xc967 (0x11ff:0xc967)
  30 0x11ff:0xb101 (0x11ff:0xb101)
  31 0x11ff:0xc7a4 (0x11ff:0xc7a4)
  32 0x101f:0x0468 in kernel32 (+0x643c4) (0x101f:0x0468)
  33 0x7fc636fb K32WOWCallback16Ex+0x119 in kernel32 (0x7fc636fb)
  34 0x7fa650b6 WINPROC_wrapper+0x79a in user32 (0x7fa650b6)
  35 0x7fa69c4f CallWindowProcW+0xdb in user32 (0x7fa69c4f)
  36 0x7fa40e7c in user32 (+0x50e7c) (0x7fa40e7c)
  37 0x7fa4126a SendMessageTimeoutW+0xef in user32 (0x7fa4126a)
  38 0x7fa41334 SendMessageW+0x3f in user32 (0x7fa41334)
  39 0x7fa1b3ef in user32 (+0x2b3ef) (0x7fa1b3ef)
  40 0x7fa1b79f DefWindowProcA+0x386 in user32 (0x7fa1b79f)
  41 0x7fa47563 DefWindowProc16+0x1fd in user32 (0x7fa47563)
  42 0x7fa06a62 DefMDIChildProc16+0x1ca in user32 (0x7fa06a62)
  43 0x7f9facfa in user32 (+0xacfa) (0x7f9facfa)
  44 0x7fc63fd2 in kernel32 (+0x63fd2) (0x7fc63fd2)
  45 0x11ff:0xb0aa (0x11ff:0xb0aa)
  46 0x11ff:0xc7a4 (0x11ff:0xc7a4)
  47 0x101f:0x0468 in kernel32 (+0x643c4) (0x101f:0x0468)
  48 0x7fc636fb K32WOWCallback16Ex+0x119 in kernel32 (0x7fc636fb)
  49 0x7fa650b6 WINPROC_wrapper+0x79a in user32 (0x7fa650b6)
  50 0x7fa69c4f CallWindowProcW+0xdb in user32 (0x7fa69c4f)
  51 0x7fa40e7c in user32 (+0x50e7c) (0x7fa40e7c)
  52 0x7fa4126a SendMessageTimeoutW+0xef in user32 (0x7fa4126a)
  53 0x7fa41334 SendMessageW+0x3f in user32 (0x7fa41334)
  54 0x7f80409d X11DRV_SetWindowPos+0x9f9 in winex11 (0x7f80409d)
  55 0x7fa63ef6 SetWindowPos+0xd5 in user32 (0x7fa63ef6)
  56 0x7f8046c7 X11DRV_ShowWindow+0x1c2 in winex11 (0x7f8046c7)
  57 0x7fa6395c ShowWindow+0x66 in user32 (0x7fa6395c)
  58 0x7fa36753 in user32 (+0x46753) (0x7fa36753)
  59 0x7fa37d54 in user32 (+0x47d54) (0x7fa37d54)
  60 0x7fa3860a in user32 (+0x4860a) (0x7fa3860a)
  61 0x7fa64936 WINPROC_wrapper+0x1a in user32 (0x7fa64936)
  62 0x7fa64ec1 WINPROC_wrapper+0x5a5 in user32 (0x7fa64ec1)
  63 0x7fa6a457 CallWindowProcW+0x8e3 in user32 (0x7fa6a457)
  64 0x7fa40e7c in user32 (+0x50e7c) (0x7fa40e7c)
  65 0x7fa4126a SendMessageTimeoutW+0xef in user32 (0x7fa4126a)
  66 0x7fa41334 SendMessageW+0x3f in user32 (0x7fa41334)
  67 0x7fa37183 DefMDIChildProcW+0x335 in user32 (0x7fa37183)
  68 0x7fa06964 DefMDIChildProc16+0xcc in user32 (0x7fa06964)
  69 0x7f9facfa in user32 (+0xacfa) (0x7f9facfa)
  70 0x7fc63fd2 in kernel32 (+0x63fd2) (0x7fc63fd2)
  71 0x11ff:0xb0aa (0x11ff:0xb0aa)
  72 0x11ff:0xc7a4 (0x11ff:0xc7a4)
  73 0x101f:0x0468 in kernel32 (+0x643c4) (0x101f:0x0468)
  74 0x7fc636fb K32WOWCallback16Ex+0x119 in kernel32 (0x7fc636fb)
  75 0x7fa650b6 WINPROC_wrapper+0x79a in user32 (0x7fa650b6)
  76 0x7fa698b2 in user32 (+0x798b2) (0x7fa698b2)
  77 0x7fa69a81 CallWindowProcA+0x88 in user32 (0x7fa69a81)
  78 0x7fa40e98 in user32 (+0x50e98) (0x7fa40e98)
  79 0x7fa446e7 SendMessageTimeoutA+0xef in user32 (0x7fa446e7)
  80 0x7fa44839 SendMessageA+0x3f in user32 (0x7fa44839)
  81 0x7fa4b2f7 NC_HandleSysCommand+0x17c in user32 

Re: World of Warcraft (WoW) patch/more address space layout stuff

2006-05-02 Thread Mike Hearn

Well ever since me, Mike and Alexandre did the preloader work a few
years ago Wine itself has been execshield resistant, but the apps
themselves may not be (my guess is that this is why Microsoft have not
implemented it themselves ... that and they appear to be scared of
their own dynamic linker code).

We could add the syscall to switch off execshield and get a legacy VMA
layout to Wine itself, but Alexandre doesn't like it as the ABI
personality syscall basically has no well defined behaviour at all
and is used for all kinds of things, some of which may be useful. If
there was an execshield/VMA randomization specific way to disable
things on a per-process basis that'd be best. Otherwise I guess adding
the personality syscall to the WoW patch wouldn't hurt, as it's
already custom.

thanks -mike

On 5/2/06, n0dalus [EMAIL PROTECTED] wrote:

On 5/1/06, Mike Hearn [EMAIL PROTECTED] wrote:

 Seems the WoW appdb page (apart from being a great example of what an
 appdb entry should be like!) recommends users patch their Wine to run WoW
 properly.


The patch mentioned particularly causes problems on systems like
Fedora with randomized prelinking and exec-shield.

On FC5 it took me some time to get the patched version to run and used:
setarch i386 -L wine WoW.exe -opengl

This apparently enables support for a legacy address layout. Does
anyone know how this would allow it to run?

Just curious,
n0dalus.




Re: setupapi: add case sensitivity string table tests

2006-05-02 Thread Andrew Ziem


Mike McCormack wrote:


Hi Andrew,

Andrew Ziem wrote:
These test case sensitivity in setupapi string tables, and all the 
parts I

modified pass on Microsoft's 98 and XP. As this is my first Wine patch,
comments are especially welcome.


For tests that don't pass in wine, please enclose them in todo_wine { 
}, so that the Wine test suite doesn't fail.

Everything passes in WINE, 2000, and XP. However, in 98 one test fails:

result=lstrcmpiW(string, string3);
ok(result!=0,StringID %p matches requested StringID %p\n,string,string3);




Index: stringtable.c
===
RCS file: /home/wine/wine/dlls/setupapi/tests/stringtable.c,v
retrieving revision 1.2
diff -u -r1.2 stringtable.c
--- stringtable.c 23 Sep 2005 10:09:47 - 1.2
+++ stringtable.c 1 May 2006 05:59:55 -


Please do the diff in the wine directory like this:

cvs diff dlls/setupapi/tests/stringtable


OK. Thanks for the tip.



Andrew






Re: Apps database bug #4648, IE screenshots

2006-05-02 Thread Tony Lambregts

EA Durbin wrote:
Here is the patch for bug # 4648. include/screenshot.php has a typo in 
two of its variables causing IE to render a zero pixel image.


oThumnailHeight should be oThumbnailHeight
oThumnailWidth whould be oThumbnailWidth





Good catch, thanks. One big nit... You sent a copy of the file. Patches 
are done in diff -u format. IE:


cvs diff -u include/screenshot.php  screenshot.diff






Re: Newbie question clipboard

2006-05-02 Thread leslie . polzer
On Tue, May 02, 2006 at 09:12:11AM -0700, Thomas Hehl wrote:

 1. On the line: Call user32.GetClipboardData(0001) ret=00439e26,
 what does the ret mean? Isn't the return value posted later in the
 log?
a) ret is the return address of the function.
b) the return value is posted at the end of the line (retval).

 2. I haven't found a user32.c and have found many, many hits in the
 source for GetClipboardData that I'm trying to sort through? How do I
 find the source code for that call?
The command

% find WINESRCTREE -name *user32*

  produces the directory 'dlls/user'.

 3. Since I haven't found that, I can't verify the type being passed
 it. It should be CF_TEXT, but without the source, how do I find the
 value for that constant?
The command

% grep 'define CF_TEXT' . -r
./include/winuser.h:3654:#define CF_TEXT  1

  shows it.

 4. It looks like GetClipboardData returned a handle with a value of
 796d604a, then it immediately locks this. It then turns around and
 unlocks it without doing anything, then never uses this handle again.
 Is this right?
I don't know, but I suppose there's stuff missing in between.

 5. After all that, it appears to allocate and unallocate memory and
 then re-open the clipboard. Is it doing this because the last time it
 tried it got nothing? Then, because it returned 000, it gave up
 and generated an error?
This I don't know either.

  HTH,
  
Leslie

-- 
gpg --keyserver pgp.mit.edu --recv-keys 0x52D70289
http://nic-nac-project.de/~skypher/


pgp9z4uR6oQdM.pgp
Description: PGP signature



How to get a SoC proposal immediately rejected

2006-05-02 Thread Dan Kegel

All you have to do to have your application summarily deleted is
to make it so short that it conveys no information.
Bonus points if you propose implementing something that's already
(somewhat) implemented.
For instance:
 I will add scanner support to Wine.
or
 I will implement a sentient computer program.
are both real examples that lasted all of about sixty milliseconds in the queue.
- Dan

--
Wine for Windows ISVs: http://kegel.com/wine/isv




Anyone actively working on ITypeInfo_fnInvoke and VariantChangeType?

2006-05-02 Thread Bill Medland
before I start trying to get up to speed on it.

Congratulations.  My company's program now gets somewhere with 
the builtin ole dlls (thanks to fixes in the out-of-process COM) 
so I am interested in trying to get it to work completely with 
them (especially since the native ones no longer work)

What I have just fallen over is some VB that calls a method that 
results in 
ITypeInfo_fnInvoke failed to convert param 0 to VT_VARIANT|
VT_BYREF from VT_I2.

So I changed the VB and ended up with 
ITypeInfo_fnInvoke failed to convert param 0 to VT_VARIANT|
VT_BYREF from VT_VARIANT|VT_BYREF.

Now it seems to me that it ought at least to handle the second 
case, but that probably demonstrates that I don't know what I am 
talking about.

Anyway; if someone is already working on that sort of thing then 
there is probably little point in me trying to learn it all.  
However if no-one is then I guess I will start trying to learn 
it.

Comments?
-- 
Bill Medland
mailto:[EMAIL PROTECTED]
http://webhome.idirect.com/~kbmed




Re: Anyone actively working on ITypeInfo_fnInvoke and VariantChangeType?

2006-05-02 Thread Tony Lambregts

Bill Medland wrote:

before I start trying to get up to speed on it.

Congratulations.  My company's program now gets somewhere with 
the builtin ole dlls (thanks to fixes in the out-of-process COM) 
so I am interested in trying to get it to work completely with 
them (especially since the native ones no longer work)


What I have just fallen over is some VB that calls a method that 
results in 
ITypeInfo_fnInvoke failed to convert param 0 to VT_VARIANT|

VT_BYREF from VT_I2.

So I changed the VB and ended up with 
ITypeInfo_fnInvoke failed to convert param 0 to VT_VARIANT|

VT_BYREF from VT_VARIANT|VT_BYREF.

Now it seems to me that it ought at least to handle the second 
case, but that probably demonstrates that I don't know what I am 
talking about.


Anyway; if someone is already working on that sort of thing then 
there is probably little point in me trying to learn it all.  
However if no-one is then I guess I will start trying to learn 
it.


Comments?


AFAICT I think that bug 4370 http://bugs.winehq.org/show_bug.cgi?id=4370 
is relevant to this problem. If not sorry for the noise.


--

Tony Lambregts




Re: Anyone actively working on ITypeInfo_fnInvoke and VariantChangeType?

2006-05-02 Thread Alex Villací­s Lasso

Bill Medland wrote:

before I start trying to get up to speed on it.

Congratulations.  My company's program now gets somewhere with 
the builtin ole dlls (thanks to fixes in the out-of-process COM) 
so I am interested in trying to get it to work completely with 
them (especially since the native ones no longer work)


What I have just fallen over is some VB that calls a method that 
results in 
ITypeInfo_fnInvoke failed to convert param 0 to VT_VARIANT|

VT_BYREF from VT_I2.

So I changed the VB and ended up with 
ITypeInfo_fnInvoke failed to convert param 0 to VT_VARIANT|

VT_BYREF from VT_VARIANT|VT_BYREF.

Now it seems to me that it ought at least to handle the second 
case, but that probably demonstrates that I don't know what I am 
talking about.


Anyway; if someone is already working on that sort of thing then 
there is probably little point in me trying to learn it all.  
However if no-one is then I guess I will start trying to learn 
it.


Comments?
  


You might be interested in this bug report:

http://bugs.winehq.org/show_bug.cgi?id=4370

Alex Villacís Lasso





Re: Anyone actively working on ITypeInfo_fnInvoke and VariantChangeType?

2006-05-02 Thread Robert Shearman

Bill Medland wrote:


before I start trying to get up to speed on it.

Congratulations.  My company's program now gets somewhere with 
the builtin ole dlls (thanks to fixes in the out-of-process COM) 
so I am interested in trying to get it to work completely with 
them (especially since the native ones no longer work)


What I have just fallen over is some VB that calls a method that 
results in 
ITypeInfo_fnInvoke failed to convert param 0 to VT_VARIANT|

VT_BYREF from VT_I2.

So I changed the VB and ended up with 
ITypeInfo_fnInvoke failed to convert param 0 to VT_VARIANT|

VT_BYREF from VT_VARIANT|VT_BYREF.

Now it seems to me that it ought at least to handle the second 
case, but that probably demonstrates that I don't know what I am 
talking about.


Anyway; if someone is already working on that sort of thing then 
there is probably little point in me trying to learn it all.  
However if no-one is then I guess I will start trying to learn 
it.


Comments?
 



I had hoped others would continue development on typelib stuff, picking 
up from where I left off after the rewrite to use more of 
VariantChangeType, but unfortunately this isn't the case and I don't 
have enough time to work on this area too much. Fortunately, I don't 
think there are too many issues left to fix and already the new code in 
ITypeInfo::Invoke gets some programs working that wouldn't work with the 
old code.


Does this patch fix both issues for you?

--
Rob Shearman

diff --git a/dlls/oleaut32/typelib.c b/dlls/oleaut32/typelib.c
index 43dfb73..4b88a18 100644
--- a/dlls/oleaut32/typelib.c
+++ b/dlls/oleaut32/typelib.c
@@ -5238,8 +5238,15 @@ static HRESULT WINAPI ITypeInfo_fnInvoke
 VARIANTARG *src_arg = pDispParams-rgvarg[pDispParams-cArgs - 1 - i];
 dump_Variant(src_arg);
 
-if (rgvt[i] == VT_VARIANT)
+if ((rgvt[i] == VT_VARIANT) || (rgvt[i] == V_VT(src_arg)))
 VariantCopy(rgvarg[i], src_arg);
+else if (rgvt[i] == (VT_VARIANT | VT_BYREF))
+{
+VARIANTARG *missing_arg = INVBUF_GET_MISSING_ARG_ARRAY(buffer, func_desc-cParams);
+VariantCopy(missing_arg[i], src_arg);
+V_VARIANTREF(rgvarg[i]) = missing_arg[i];
+V_VT(rgvarg[i]) = rgvt[i];
+}
 else if ((rgvt[i]  VT_BYREF)  !V_ISBYREF(src_arg))
 {
 VARIANTARG *missing_arg = INVBUF_GET_MISSING_ARG_ARRAY(buffer, func_desc-cParams);



Linuxtag06/Wiesbaden/Germany

2006-05-02 Thread Uwe Bonnes
Hallo,

Stefan Maunz, Micheal Jung and me will present Wine at
Linuxtag06/Wiesbaden/Germany.

As a project we can send out invitations. If anybody is interested to
receive an invitation, please let me know.

Bye
-- 
Uwe Bonnes[EMAIL PROTECTED]

Institut fuer Kernphysik  Schlossgartenstrasse 9  64289 Darmstadt
- Tel. 06151 162516  Fax. 06151 164321 --




Re: Newbie question clipboard

2006-05-02 Thread Mike Hearn
On Tue, 02 May 2006 09:12:11 -0700, Thomas Hehl wrote:
 Please forgive a newbie. I have extensive development background, but am
 new to wine and, though I've used VB a lot, am somewhat new to API
 programming.

Welcome! Don't worry, we all started in the same position as you did :)
 
 I have an error while running Pagemaker 7.0 and try to paste text from
 the clipboard that I put into the clipboard from another app. I tried
 running with +relay and got a bunch of stuff. I tried +msgbox to find a
 trace for the message box that's created, but that didn't seem to work
 for some reason.

It might be generated by the app itself ... if you're sure it's a win32
message box look at the relay trace for MessageBox


 1. On the line: Call user32.GetClipboardData(0001) ret=00439e26,
 what does the ret mean? Isn't the return value posted later in the log?

Return address, as already said. Can be occasionally helpful, mostly can
be ignored. It's posted twice because as you can see even for a relatively
simple API a LOT of data can be generated in between. It's just more
convenient to have it at that point.

 2. I haven't found a user32.c and have found many, many hits in the
source for GetClipboardData that I'm trying to sort through? How do I
 find the source code for that call?

The Wine source tree is a labyrinthe, mostly because it follows the layout
of Windows itself. Believe it or not, it used to be far worse. These days
nearly all the code for the APIs is under dlls/ so if you know where an
API is implemented in Windows then you can find it there.

In this case user32.GetClipboardData means it's in user32.dll, which is
implemented in dlls/user (a historical quirk, normally they map 1:1)

I navigate the tree by using etags, which plugs into emacs. If you use
emacs or vi then etags/ctags can be very handy to jump around the tree.
Run make etags or make ctags (or maybe it's make tags, I forget) in
the source root to generate the file.

 3. Since I haven't found that, I can't verify the type being passed it.
 It should be CF_TEXT, but without the source, how do I find the value
 for that constant?

CF_TEXT is, like all Windows constants, defined in a header file that can
be found in the include/ directory. Usually the best way is to use grep or
alternatively MSDN will tell you which header file it's probably in.

 4. It looks like GetClipboardData returned a handle with a value of
 796d604a, then it immediately locks this. It then turns around and
 unlocks it without doing anything, then never uses this handle again. Is
 this right?

Looks that way. Remember that a relay trace only shows calls into and out
of Wines DLLs. The +snoop channel can be used to see calls to/from native
DLLS. Also remember that programs can do a ton of work between calls that
will never register in the logs. In this case perhaps it's checking the
contents of that memory and finding it's not what it expects?

 5. After all that, it appears to allocate and unallocate memory and then
 re-open the clipboard. Is it doing this because the last time it tried
 it got nothing? Then, because it returned 000, it gave up and
 generated an error?

Could be! To find out why OpenClipboard fails check the traces for that
particular function (you can see which one it uses at the top of the
relevant source file). It might be that the app didn't CloseClipboard last
time for instance.

A word of warning ... this isn't necessarily the cause of the bug. It
could be that if GetClipboardData isn't correct that the app is pushed
onto a codepath the developers never tested and the failing OpenClipboard
call would be the same under Windows. I'm not saying this IS the case,
just that it might be.

You'll need to investigate further to find out.

thanks -mike





Re: How to get a SoC proposal immediately rejected

2006-05-02 Thread Segin

Dan Kegel wrote:

All you have to do to have your application summarily deleted is
to make it so short that it conveys no information.
Bonus points if you propose implementing something that's already
(somewhat) implemented.
For instance:
 I will add scanner support to Wine.
or
 I will implement a sentient computer program.
are both real examples that lasted all of about sixty milliseconds in 
the queue.

- Dan

--
Wine for Windows ISVs: http://kegel.com/wine/isv





You really know how to make a good joke. Kudos.

--
The real problem with C++ for kernel modules is: the language just sucks.
-- Linus Torvalds




Re: Newbie question clipboard

2006-05-02 Thread Duane Clark

Thomas Hehl wrote:


2. I haven't found a user32.c and have found many, many hits in the
source for GetClipboardData that I'm trying to sort through? How do I
find the source code for that call?



I'll just add one other simple method, since others did not mention it. In:

http://source.winehq.org/ident

You can just type in GetClipboardData, and it will find it for you.





Re: Opera 3.21

2006-05-02 Thread Tom Spear
Segin, thanks for reporting this, but just as a personal favor, would you mind including backtraces as an attachment? When I have to read my emails from the browser, gmail wraps the backtrace, which makes it difficult to read.
On 5/2/06, Segin [EMAIL PROTECTED] wrote:
when closing the list of newsgroups with the full list displayed, Operacrashes and gives this nice backtrace:wine: Unhandled page fault on read access to 0x at address0x11df:0x29e2 (thread 0055), starting debugger...
WineDbg starting on pid 0x53Unhandled exception: page fault on read access to 0x in 16-bitcode (11df:29e2).In 16 bit mode.Register dump:CS:11df SS:127f DS:13e7 ES:149f FS:003b GS:0033
IP:29e2 SP:df5a BP:df6c FLAGS:0206( - 00- RIP1)AX:6f52 BX:13e7 CX:006c DX:141f SI:1827 DI:29dcStack dump:0x127f:0xdf5a:13e7 28f7 29dc 1827 141f 127f 0160 0x127f:0xdf6a:127f df75 2c21 11df 006c dff4 6302 11e7
0x127f:0xdf7a:006c 11ff  02d0 007b 02d0 a58c 7e2c027c: sel=13e7 base=7da51108 limit=003f 16-bit rw-0293: sel=149f base=7ccfabd8 limit=ffbf 16-bit rw-Backtrace:=1 0x11df:0x29e2 (0x11df:0x29e2)
 2 0x11df:0x2c21 (0x11df:0x2c21) 3 0x6c11:0xe763 (0x6c11:0xe763) 4 0x11ef:0xe9d7 (0x11ef:0xe9d7) 5 0x1247:0xa1df (0x1247:0xa1df) 6 0x11ff:0xbf14 (0x11ff:0xbf14) 7 0x11ff:0xad75 (0x11ff:0xad75)
 8 0x11ff:0xbc9a (0x11ff:0xbc9a) 9 0x101f:0x0468 in kernel32 (+0x643c4) (0x101f:0x0468) 10 0x7fc636fb K32WOWCallback16Ex+0x119 in kernel32 (0x7fc636fb) 11 0x7fa650b6 WINPROC_wrapper+0x79a in user32 (0x7fa650b6)
 12 0x7fa69c4f CallWindowProcW+0xdb in user32 (0x7fa69c4f) 13 0x7fa40e7c in user32 (+0x50e7c) (0x7fa40e7c) 14 0x7fa4126a SendMessageTimeoutW+0xef in user32 (0x7fa4126a) 15 0x7fa41334 SendMessageW+0x3f in user32 (0x7fa41334)
 16 0x7fa4bf93 RedrawWindow+0x18b in user32 (0x7fa4bf93) 17 0x7fa05a59 RedrawWindow16+0x67 in user32 (0x7fa05a59) 18 0x7fa05c11 UpdateWindow16+0x31 in user32 (0x7fa05c11) 19 0x7f9fa22d in user32 (+0xa22d) (0x7f9fa22d)
 20 0x7fc63fd2 in kernel32 (+0x63fd2) (0x7fc63fd2) 21 0x11ff:0x7158 (0x11ff:0x7158) 22 0x11ef:0xb527 (0x11ef:0xb527) 23 0x11ef:0xbfc6 (0x11ef:0xbfc6) 24 0x11ef:0xdcf2 (0x11ef:0xdcf2) 25 0x1247:0xa6f8 (0x1247:0xa6f8)
 26 0x11ef:0x5562 (0x11ef:0x5562) 27 0x124f:0x3076 (0x124f:0x3076) 28 0x124f:0x309f (0x124f:0x309f) 29 0x11ff:0xc967 (0x11ff:0xc967) 30 0x11ff:0xb101 (0x11ff:0xb101) 31 0x11ff:0xc7a4 (0x11ff:0xc7a4)
 32 0x101f:0x0468 in kernel32 (+0x643c4) (0x101f:0x0468) 33 0x7fc636fb K32WOWCallback16Ex+0x119 in kernel32 (0x7fc636fb) 34 0x7fa650b6 WINPROC_wrapper+0x79a in user32 (0x7fa650b6) 35 0x7fa69c4f CallWindowProcW+0xdb in user32 (0x7fa69c4f)
 36 0x7fa40e7c in user32 (+0x50e7c) (0x7fa40e7c) 37 0x7fa4126a SendMessageTimeoutW+0xef in user32 (0x7fa4126a) 38 0x7fa41334 SendMessageW+0x3f in user32 (0x7fa41334) 39 0x7fa1b3ef in user32 (+0x2b3ef) (0x7fa1b3ef)
 40 0x7fa1b79f DefWindowProcA+0x386 in user32 (0x7fa1b79f) 41 0x7fa47563 DefWindowProc16+0x1fd in user32 (0x7fa47563) 42 0x7fa06a62 DefMDIChildProc16+0x1ca in user32 (0x7fa06a62) 43 0x7f9facfa in user32 (+0xacfa) (0x7f9facfa)
 44 0x7fc63fd2 in kernel32 (+0x63fd2) (0x7fc63fd2) 45 0x11ff:0xb0aa (0x11ff:0xb0aa) 46 0x11ff:0xc7a4 (0x11ff:0xc7a4) 47 0x101f:0x0468 in kernel32 (+0x643c4) (0x101f:0x0468) 48 0x7fc636fb K32WOWCallback16Ex+0x119 in kernel32 (0x7fc636fb)
 49 0x7fa650b6 WINPROC_wrapper+0x79a in user32 (0x7fa650b6) 50 0x7fa69c4f CallWindowProcW+0xdb in user32 (0x7fa69c4f) 51 0x7fa40e7c in user32 (+0x50e7c) (0x7fa40e7c) 52 0x7fa4126a SendMessageTimeoutW+0xef in user32 (0x7fa4126a)
 53 0x7fa41334 SendMessageW+0x3f in user32 (0x7fa41334) 54 0x7f80409d X11DRV_SetWindowPos+0x9f9 in winex11 (0x7f80409d) 55 0x7fa63ef6 SetWindowPos+0xd5 in user32 (0x7fa63ef6) 56 0x7f8046c7 X11DRV_ShowWindow+0x1c2 in winex11 (0x7f8046c7)
 57 0x7fa6395c ShowWindow+0x66 in user32 (0x7fa6395c) 58 0x7fa36753 in user32 (+0x46753) (0x7fa36753) 59 0x7fa37d54 in user32 (+0x47d54) (0x7fa37d54) 60 0x7fa3860a in user32 (+0x4860a) (0x7fa3860a)
 61 0x7fa64936 WINPROC_wrapper+0x1a in user32 (0x7fa64936) 62 0x7fa64ec1 WINPROC_wrapper+0x5a5 in user32 (0x7fa64ec1) 63 0x7fa6a457 CallWindowProcW+0x8e3 in user32 (0x7fa6a457) 64 0x7fa40e7c in user32 (+0x50e7c) (0x7fa40e7c)
 65 0x7fa4126a SendMessageTimeoutW+0xef in user32 (0x7fa4126a) 66 0x7fa41334 SendMessageW+0x3f in user32 (0x7fa41334) 67 0x7fa37183 DefMDIChildProcW+0x335 in user32 (0x7fa37183) 68 0x7fa06964 DefMDIChildProc16+0xcc in user32 (0x7fa06964)
 69 0x7f9facfa in user32 (+0xacfa) (0x7f9facfa) 70 0x7fc63fd2 in kernel32 (+0x63fd2) (0x7fc63fd2) 71 0x11ff:0xb0aa (0x11ff:0xb0aa) 72 0x11ff:0xc7a4 (0x11ff:0xc7a4) 73 0x101f:0x0468 in kernel32 (+0x643c4) (0x101f:0x0468)
 74 0x7fc636fb K32WOWCallback16Ex+0x119 in kernel32 (0x7fc636fb) 75 0x7fa650b6 WINPROC_wrapper+0x79a in user32 (0x7fa650b6) 76 0x7fa698b2 in user32 (+0x798b2) (0x7fa698b2) 77 0x7fa69a81 CallWindowProcA+0x88 in user32 (0x7fa69a81)
 78 0x7fa40e98 in user32 (+0x50e98) (0x7fa40e98) 79 0x7fa446e7 SendMessageTimeoutA+0xef in user32 (0x7fa446e7) 80 0x7fa44839 

Re: How to get a SoC proposal immediately rejected

2006-05-02 Thread Mike Hearn
On Tue, 02 May 2006 10:40:14 -0700, Dan Kegel wrote:
   I will implement a sentient computer program.

Michael C Hearn is interested in this proposal :)

That is, interested in how the hell they planned to implement it!





Re: Anyone actively working on ITypeInfo_fnInvoke and VariantChangeType?

2006-05-02 Thread Bill Medland
On May 2, 2006 11:44 am, Robert Shearman wrote:
 Bill Medland wrote:
 before I start trying to get up to speed on it.
 

 
 Anyway; if someone is already working on that sort of thing
  then there is probably little point in me trying to learn it
  all. However if no-one is then I guess I will start trying
  to learn it.
 
 Comments?

 I had hoped others would continue development on typelib
 stuff, picking up from where I left off after the rewrite to
 use more of VariantChangeType, but unfortunately this isn't
 the case and I don't have enough time to work on this area too
 much. Fortunately, I don't think there are too many issues
 left to fix and already the new code in ITypeInfo::Invoke gets
 some programs working that wouldn't work with the old code.

 Does this patch fix both issues for you?

Yes, thanks Rob.

Are you going to submit it?

(Now onto why it jumbs into the debugger in libkrb of all 
places!)
-- 
Bill Medland
mailto:[EMAIL PROTECTED]
http://webhome.idirect.com/~kbmed




Re: Opera 3.21

2006-05-02 Thread Segin
kk, no problem, i barely use the web interface (I just use thunderbird) 
but if it makes any difference, i'll do it. It's also easier on me cause 
i can then redirect a backtrace with a pipe to a file.


Tom Spear wrote:
Segin, thanks for reporting this, but just as a personal favor, would 
you mind including backtraces as an attachment?  When I have to read my 
emails from the browser, gmail wraps the backtrace, which makes it 
difficult to read.


On 5/2/06, *Segin* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote:

when closing the list of newsgroups with the full list displayed, Opera
crashes and gives this nice backtrace:

wine: Unhandled page fault on read access to 0x at address
0x11df:0x29e2 (thread 0055), starting debugger...
WineDbg starting on pid 0x53
Unhandled exception: page fault on read access to 0x in 16-bit
code (11df:29e2).
In 16 bit mode.
Register dump:
  CS:11df SS:127f DS:13e7 ES:149f FS:003b GS:0033
  IP:29e2 SP:df5a BP:df6c FLAGS:0206(   - 00  - RIP1)
  AX:6f52 BX:13e7 CX:006c DX:141f SI:1827 DI:29dc
Stack dump:
0x127f:0xdf5a:  13e7 28f7 29dc 1827 141f 127f 0160 
0x127f:0xdf6a:  127f df75 2c21 11df 006c dff4 6302 11e7
0x127f:0xdf7a:  006c 11ff  02d0 007b 02d0 a58c 7e2c
027c: sel=13e7 base=7da51108 limit=003f 16-bit rw-
0293: sel=149f base=7ccfabd8 limit=ffbf 16-bit rw-
Backtrace:
=1 0x11df:0x29e2 (0x11df:0x29e2)
   2 0x11df:0x2c21 (0x11df:0x2c21)
   3 0x6c11:0xe763 (0x6c11:0xe763)
   4 0x11ef:0xe9d7 (0x11ef:0xe9d7)
   5 0x1247:0xa1df (0x1247:0xa1df)
   6 0x11ff:0xbf14 (0x11ff:0xbf14)
   7 0x11ff:0xad75 (0x11ff:0xad75)
   8 0x11ff:0xbc9a (0x11ff:0xbc9a)
   9 0x101f:0x0468 in kernel32 (+0x643c4) (0x101f:0x0468)
   10 0x7fc636fb K32WOWCallback16Ex+0x119 in kernel32 (0x7fc636fb)
   11 0x7fa650b6 WINPROC_wrapper+0x79a in user32 (0x7fa650b6)
   12 0x7fa69c4f CallWindowProcW+0xdb in user32 (0x7fa69c4f)
   13 0x7fa40e7c in user32 (+0x50e7c) (0x7fa40e7c)
   14 0x7fa4126a SendMessageTimeoutW+0xef in user32 (0x7fa4126a)
   15 0x7fa41334 SendMessageW+0x3f in user32 (0x7fa41334)
   16 0x7fa4bf93 RedrawWindow+0x18b in user32 (0x7fa4bf93)
   17 0x7fa05a59 RedrawWindow16+0x67 in user32 (0x7fa05a59)
   18 0x7fa05c11 UpdateWindow16+0x31 in user32 (0x7fa05c11)
   19 0x7f9fa22d in user32 (+0xa22d) (0x7f9fa22d)
   20 0x7fc63fd2 in kernel32 (+0x63fd2) (0x7fc63fd2)
   21 0x11ff:0x7158 (0x11ff:0x7158)
   22 0x11ef:0xb527 (0x11ef:0xb527)
   23 0x11ef:0xbfc6 (0x11ef:0xbfc6)
   24 0x11ef:0xdcf2 (0x11ef:0xdcf2)
   25 0x1247:0xa6f8 (0x1247:0xa6f8)
   26 0x11ef:0x5562 (0x11ef:0x5562)
   27 0x124f:0x3076 (0x124f:0x3076)
   28 0x124f:0x309f (0x124f:0x309f)
   29 0x11ff:0xc967 (0x11ff:0xc967)
   30 0x11ff:0xb101 (0x11ff:0xb101)
   31 0x11ff:0xc7a4 (0x11ff:0xc7a4)
   32 0x101f:0x0468 in kernel32 (+0x643c4) (0x101f:0x0468)
   33 0x7fc636fb K32WOWCallback16Ex+0x119 in kernel32 (0x7fc636fb)
   34 0x7fa650b6 WINPROC_wrapper+0x79a in user32 (0x7fa650b6)
   35 0x7fa69c4f CallWindowProcW+0xdb in user32 (0x7fa69c4f)
   36 0x7fa40e7c in user32 (+0x50e7c) (0x7fa40e7c)
   37 0x7fa4126a SendMessageTimeoutW+0xef in user32 (0x7fa4126a)
   38 0x7fa41334 SendMessageW+0x3f in user32 (0x7fa41334)
   39 0x7fa1b3ef in user32 (+0x2b3ef) (0x7fa1b3ef)
   40 0x7fa1b79f DefWindowProcA+0x386 in user32 (0x7fa1b79f)
   41 0x7fa47563 DefWindowProc16+0x1fd in user32 (0x7fa47563)
   42 0x7fa06a62 DefMDIChildProc16+0x1ca in user32 (0x7fa06a62)
   43 0x7f9facfa in user32 (+0xacfa) (0x7f9facfa)
   44 0x7fc63fd2 in kernel32 (+0x63fd2) (0x7fc63fd2)
   45 0x11ff:0xb0aa (0x11ff:0xb0aa)
   46 0x11ff:0xc7a4 (0x11ff:0xc7a4)
   47 0x101f:0x0468 in kernel32 (+0x643c4) (0x101f:0x0468)
   48 0x7fc636fb K32WOWCallback16Ex+0x119 in kernel32 (0x7fc636fb)
   49 0x7fa650b6 WINPROC_wrapper+0x79a in user32 (0x7fa650b6)
   50 0x7fa69c4f CallWindowProcW+0xdb in user32 (0x7fa69c4f)
   51 0x7fa40e7c in user32 (+0x50e7c) (0x7fa40e7c)
   52 0x7fa4126a SendMessageTimeoutW+0xef in user32 (0x7fa4126a)
   53 0x7fa41334 SendMessageW+0x3f in user32 (0x7fa41334)
   54 0x7f80409d X11DRV_SetWindowPos+0x9f9 in winex11 (0x7f80409d)
   55 0x7fa63ef6 SetWindowPos+0xd5 in user32 (0x7fa63ef6)
   56 0x7f8046c7 X11DRV_ShowWindow+0x1c2 in winex11 (0x7f8046c7)
   57 0x7fa6395c ShowWindow+0x66 in user32 (0x7fa6395c)
   58 0x7fa36753 in user32 (+0x46753) (0x7fa36753)
   59 0x7fa37d54 in user32 (+0x47d54) (0x7fa37d54)
   60 0x7fa3860a in user32 (+0x4860a) (0x7fa3860a)
   61 0x7fa64936 WINPROC_wrapper+0x1a in user32 (0x7fa64936)
   62 0x7fa64ec1 WINPROC_wrapper+0x5a5 in user32 (0x7fa64ec1)
   63 0x7fa6a457 CallWindowProcW+0x8e3 in user32 (0x7fa6a457)
   64 0x7fa40e7c in user32 (+0x50e7c) (0x7fa40e7c)
   65 0x7fa4126a 

Re: Opera 3.21

2006-05-02 Thread Tom Spear
I barely ever use the web interface myself, but sometimes it is necessary (when I am at work, where they only let us use Outlook XP, blegh!)On 5/2/06, Segin
 [EMAIL PROTECTED] wrote:kk, no problem, i barely use the web interface (I just use thunderbird)
but if it makes any difference, i'll do it. It's also easier on me causei can then redirect a backtrace with a pipe to a file.Tom Spear wrote: Segin, thanks for reporting this, but just as a personal favor, would
 you mind including backtraces as an attachment?When I have to read my emails from the browser, gmail wraps the backtrace, which makes it difficult to read. On 5/2/06, *Segin* 
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: when closing the list of newsgroups with the full list displayed, Opera
 crashes and gives this nice backtrace: wine: Unhandled page fault on read access to 0x at address 0x11df:0x29e2 (thread 0055), starting debugger... WineDbg starting on pid 0x53
 Unhandled exception: page fault on read access to 0x in 16-bit code (11df:29e2). In 16 bit mode. Register dump: CS:11df SS:127f DS:13e7 ES:149f FS:003b GS:0033
 IP:29e2 SP:df5a BP:df6c FLAGS:0206( - 00- RIP1) AX:6f52 BX:13e7 CX:006c DX:141f SI:1827 DI:29dc Stack dump: 0x127f:0xdf5a:13e7 28f7 29dc 1827 141f 127f 0160 
 0x127f:0xdf6a:127f df75 2c21 11df 006c dff4 6302 11e7 0x127f:0xdf7a:006c 11ff  02d0 007b 02d0 a58c 7e2c 027c: sel=13e7 base=7da51108 limit=003f 16-bit rw- 0293: sel=149f base=7ccfabd8 limit=ffbf 16-bit rw-
 Backtrace: =1 0x11df:0x29e2 (0x11df:0x29e2)2 0x11df:0x2c21 (0x11df:0x2c21)3 0x6c11:0xe763 (0x6c11:0xe763)4 0x11ef:0xe9d7 (0x11ef:0xe9d7)5 0x1247:0xa1df (0x1247:0xa1df)
6 0x11ff:0xbf14 (0x11ff:0xbf14)7 0x11ff:0xad75 (0x11ff:0xad75)8 0x11ff:0xbc9a (0x11ff:0xbc9a)9 0x101f:0x0468 in kernel32 (+0x643c4) (0x101f:0x0468)10 0x7fc636fb K32WOWCallback16Ex+0x119 in kernel32 (0x7fc636fb)
11 0x7fa650b6 WINPROC_wrapper+0x79a in user32 (0x7fa650b6)12 0x7fa69c4f CallWindowProcW+0xdb in user32 (0x7fa69c4f)13 0x7fa40e7c in user32 (+0x50e7c) (0x7fa40e7c)14 0x7fa4126a SendMessageTimeoutW+0xef in user32 (0x7fa4126a)
15 0x7fa41334 SendMessageW+0x3f in user32 (0x7fa41334)16 0x7fa4bf93 RedrawWindow+0x18b in user32 (0x7fa4bf93)17 0x7fa05a59 RedrawWindow16+0x67 in user32 (0x7fa05a59)18 0x7fa05c11 UpdateWindow16+0x31 in user32 (0x7fa05c11)
19 0x7f9fa22d in user32 (+0xa22d) (0x7f9fa22d)20 0x7fc63fd2 in kernel32 (+0x63fd2) (0x7fc63fd2)21 0x11ff:0x7158 (0x11ff:0x7158)22 0x11ef:0xb527 (0x11ef:0xb527)
23 0x11ef:0xbfc6 (0x11ef:0xbfc6)24 0x11ef:0xdcf2 (0x11ef:0xdcf2)25 0x1247:0xa6f8 (0x1247:0xa6f8)26 0x11ef:0x5562 (0x11ef:0x5562)27 0x124f:0x3076 (0x124f:0x3076)
28 0x124f:0x309f (0x124f:0x309f)29 0x11ff:0xc967 (0x11ff:0xc967)30 0x11ff:0xb101 (0x11ff:0xb101)31 0x11ff:0xc7a4 (0x11ff:0xc7a4)32 0x101f:0x0468 in kernel32 (+0x643c4) (0x101f:0x0468)
33 0x7fc636fb K32WOWCallback16Ex+0x119 in kernel32 (0x7fc636fb)34 0x7fa650b6 WINPROC_wrapper+0x79a in user32 (0x7fa650b6)35 0x7fa69c4f CallWindowProcW+0xdb in user32 (0x7fa69c4f)
36 0x7fa40e7c in user32 (+0x50e7c) (0x7fa40e7c)37 0x7fa4126a SendMessageTimeoutW+0xef in user32 (0x7fa4126a)38 0x7fa41334 SendMessageW+0x3f in user32 (0x7fa41334)39 0x7fa1b3ef in user32 (+0x2b3ef) (0x7fa1b3ef)
40 0x7fa1b79f DefWindowProcA+0x386 in user32 (0x7fa1b79f)41 0x7fa47563 DefWindowProc16+0x1fd in user32 (0x7fa47563)42 0x7fa06a62 DefMDIChildProc16+0x1ca in user32 (0x7fa06a62)
43 0x7f9facfa in user32 (+0xacfa) (0x7f9facfa)44 0x7fc63fd2 in kernel32 (+0x63fd2) (0x7fc63fd2)45 0x11ff:0xb0aa (0x11ff:0xb0aa)46 0x11ff:0xc7a4 (0x11ff:0xc7a4)
47 0x101f:0x0468 in kernel32 (+0x643c4) (0x101f:0x0468)48 0x7fc636fb K32WOWCallback16Ex+0x119 in kernel32 (0x7fc636fb)49 0x7fa650b6 WINPROC_wrapper+0x79a in user32 (0x7fa650b6)
50 0x7fa69c4f CallWindowProcW+0xdb in user32 (0x7fa69c4f)51 0x7fa40e7c in user32 (+0x50e7c) (0x7fa40e7c)52 0x7fa4126a SendMessageTimeoutW+0xef in user32 (0x7fa4126a)53 0x7fa41334 SendMessageW+0x3f in user32 (0x7fa41334)
54 0x7f80409d X11DRV_SetWindowPos+0x9f9 in winex11 (0x7f80409d)55 0x7fa63ef6 SetWindowPos+0xd5 in user32 (0x7fa63ef6)56 0x7f8046c7 X11DRV_ShowWindow+0x1c2 in winex11 (0x7f8046c7)
57 0x7fa6395c ShowWindow+0x66 in user32 (0x7fa6395c)58 0x7fa36753 in user32 (+0x46753) (0x7fa36753)59 0x7fa37d54 in user32 (+0x47d54) (0x7fa37d54)60 0x7fa3860a in user32 (+0x4860a) (0x7fa3860a)
61 0x7fa64936 WINPROC_wrapper+0x1a in user32 (0x7fa64936)62 0x7fa64ec1 WINPROC_wrapper+0x5a5 in user32 (0x7fa64ec1)63 0x7fa6a457 CallWindowProcW+0x8e3 in user32 (0x7fa6a457)
64 0x7fa40e7c in user32 (+0x50e7c) (0x7fa40e7c)65 0x7fa4126a SendMessageTimeoutW+0xef in user32 (0x7fa4126a)66 0x7fa41334 SendMessageW+0x3f in user32 (0x7fa41334)67 0x7fa37183 DefMDIChildProcW+0x335 in user32 (0x7fa37183)
68 0x7fa06964 DefMDIChildProc16+0xcc in user32 (0x7fa06964)69 0x7f9facfa in user32 (+0xacfa) (0x7f9facfa)70 0x7fc63fd2 in kernel32 (+0x63fd2) (0x7fc63fd2)71 0x11ff:0xb0aa (0x11ff:0xb0aa)
72 0x11ff:0xc7a4 (0x11ff:0xc7a4)73 0x101f:0x0468 in kernel32 (+0x643c4) 

Re: How to get a SoC proposal immediately rejected

2006-05-02 Thread Mike McCormack


If anybody needs any advice or help with a SoC proposal, feel free to 
mail me privately...


Mike




re: Anyone actively working on ITypeInfo_fnInvoke and VariantChangeType?

2006-05-02 Thread Dan Kegel

Rob wrote:

Does this patch fix both issues for you?


Oh, man, that patch is great. It lets me start the VB6 IDE
(i.e. it fixes http://bugs.winehq.org/show_bug.cgi?id=4448 )
Please submit it.  Yum!
- Dan

--
Wine for Windows ISVs: http://kegel.com/wine/isv