[Patch] dlls/oleaut32/typelib.c - Via a CVS search, reverseregression to get Kazza working

2003-06-26 Thread Stefan Jones
On upgrading to Wine 20030618 I found that kazaa lite will no longer work and gave me the following error: No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\SHDOCVW.DLL' (0x7100) Unhandled exception: page fault on read access to 0x0004 in 32-bit code (0x411ed9c9). In 32-bit mode. 0x411e

Re: Wine Status Changelog

2003-06-26 Thread Tom
Robert North wrote: Is this in the CVS tree? Can't see it on the cvsweb page or in the repository. I would like to apologize for any misunderstandings about my post on the Wine Status changelog. To clarify the Changelog that i'm working on is the Wine Status Page Changelog and it can be f

Re: Doom Legacy / Problems with DOS & and winedbg

2003-06-26 Thread Eric Pouech
Sylvain Petreolle wrote: you shouldn't need to change the mode, why do you want to switch to mode 32 ? since it complains in vm86 mode, I tried something different (all the others :)) since the pc has changed between the two exceptions, I assume several int 21 take place in a row. yes, this is a

Re: Doom Legacy / Problems with DOS & and winedbg

2003-06-26 Thread Sylvain Petreolle
> you shouldn't need to change the mode, why do you want to switch to > mode > 32 ? since it complains in vm86 mode, I tried something different (all the others :)) > since the pc has changed between the two exceptions, I assume several > int 21 take place in a row. yes, this is a dos prog... wic

Re: Wine Status Changelog

2003-06-26 Thread Robert North
Robert North 7ownq0k402-at-sneakemail.com |Wine Mailing Lists| wrote: Sylvain Petreolle spetreolle-at-yahoo.fr |Wine Mailing Lists| wrote: Of course, its already in the tree... see the CVS : http://cvs.winehq.org/cvsweb/wine/dlls/wintab32/ Oh, sorry, I'll clarify: The CVS currently has stubs (I

Re: Doom Legacy / Problems with DOS & and winedbg

2003-06-26 Thread Eric Pouech
Sylvain Petreolle wrote: Unfortunately, winedbg complains on the first int21 call : First chance exception: interrupt 21 in vm86 mode in vm86 code (00d4:045e). How can this be avoided ? do you get the winedbg prompt or not ? if so, 'pass' should do. This works, thanks. But the same error appears on

Re: Doom Legacy / Problems with DOS & and winedbg

2003-06-26 Thread Sylvain Petreolle
> > Unfortunately, winedbg complains on the first int21 call : > > First chance exception: interrupt 21 in vm86 mode in vm86 code > > (00d4:045e). > > > > How can this be avoided ? > > do you get the winedbg prompt or not ? if so, 'pass' should do. This works, thanks. But the same error appears

Re: Doom Legacy / Problems with DOS & and winedbg

2003-06-26 Thread Eric Pouech
Sylvain Petreolle wrote: Trying to debug a problem into INT21_CreateDirectory, I want to run doom3.exe into winedbg. (DL tries to create the directory in %HOME%, set to /home/something... LOL) Unfortunately, winedbg complains on the first int21 call : First chance exception: interrupt 21 in vm86 mo

Re: WaitForMultipleObjects loops forever if passed an array of size zero

2003-06-26 Thread Troy Rollo
On Thu, 26 Jun 2003 15:59, Troy Rollo wrote: > With the condition as (count > MAXIMUM_WAIT_OBJECTS || (count <= 0 && > !timeout)), wine's behaviour mirrors that of Win2k, at least for the > WaitForMultipleObjectsEx(0, 0, INFINITE, QS_ALLEVENTS, 0) case. While I somehow got MsgWaitForMultipleObject

Re: WaitForMultipleObjects loops forever if passed an array of size zero

2003-06-26 Thread Troy Rollo
On Thu, 26 Jun 2003 10:16, Alexandre Julliard wrote: > Troy Rollo <[EMAIL PROTECTED]> writes: > > @@ -412,7 +412,7 @@ > > { > > int ret, cookie; > > > > -if (count > MAXIMUM_WAIT_OBJECTS) return STATUS_INVALID_PARAMETER_1; > > +if (count > MAXIMUM_WAIT_OBJECTS || count <= 0) return >

Doom Legacy / Problems with DOS & and winedbg

2003-06-26 Thread Sylvain Petreolle
Trying to debug a problem into INT21_CreateDirectory, I want to run doom3.exe into winedbg. (DL tries to create the directory in %HOME%, set to /home/something... LOL) Unfortunately, winedbg complains on the first int21 call : First chance exception: interrupt 21 in vm86 mode in vm86 code (00d4:04

Re: Wintab: Update on debugging & demo patch.

2003-06-26 Thread Robert North
Aric Stewart aric-at-codeweavers.com |Wine Mailing Lists| wrote: I chatted with Alexandre yesterday and he expressed a number of concerns with how my patch works. He and I are going to work on make that patch suitable for winehq. Then i will get that applied. It should not change any of the func

Re: Wine Status Changelog

2003-06-26 Thread Robert North
Sylvain Petreolle spetreolle-at-yahoo.fr |Wine Mailing Lists| wrote: Of course, its already in the tree... see the CVS : http://cvs.winehq.org/cvsweb/wine/dlls/wintab32/ Oh, sorry, I'll clarify: The CVS currently has stubs (I think contributed by Patrick Stridvall). They were contributed in late 2

Re: Wine Status Changelog

2003-06-26 Thread Sylvain Petreolle
Of course, its already in the tree... see the CVS : http://cvs.winehq.org/cvsweb/wine/dlls/wintab32/ > > Is this in the CVS tree? > > Can't see it on the cvsweb page > > or in the repository. > > Nope, not in CVS yet. Once Tom sends me a patch at wine-patches, I > will > commit them to th

Re: Wintab: Update on debugging & demo patch.

2003-06-26 Thread Aric Stewart
I chatted with Alexandre yesterday and he expressed a number of concerns with how my patch works. He and I are going to work on make that patch suitable for winehq. Then i will get that applied. It should not change any of the functionality. Just trying to preserve DLL separation. Then i will w

Re: Wine Status Changelog

2003-06-26 Thread Robert North
Jeremy Newman jnewman-at-codeweavers.com |Wine Mailing Lists| wrote: On Thu, 2003-06-26 at 07:39, Robert North wrote: Is this in the CVS tree? Can't see it on the cvsweb page or in the repository. Nope, not in CVS yet. Once Tom sends me a patch at wine-patches, I will commit them

Wintab: Update on debugging & demo patch.

2003-06-26 Thread Robert North
Ok, Firstly, I'm including a patch that demonstrates fixes to the crashing in Painter, and the recursion in Photoshop. The patch assumes that you have already applied Aric's patch from April 23rd. I'd like feedback on wether the patch is OK, as it was generated on from my local subversion reposit

Re: Wine Status Changelog

2003-06-26 Thread Jeremy Newman
On Thu, 2003-06-26 at 07:39, Robert North wrote: > Is this in the CVS tree? > Can't see it on the cvsweb page > or in the repository. Nope, not in CVS yet. Once Tom sends me a patch at wine-patches, I will commit them to the site. -- Jeremy Newman <[EMAIL PROTECTED]> CodeWeavers, Inc

Re: Wine Status DLL's #2

2003-06-26 Thread Robert North
Tom twickline-at-skybest.com |Wine Mailing Lists| wrote: Here is #2 any one have any comments ? Tom > wintab32.dll 80% Didn't see that one come in! Nice to see it up on the list of dlls. What I'm concerned about is seeing marked as 80% done. (Aric, don't get me wrong, you've done a great job, bu

Re: Wine Status Changelog

2003-06-26 Thread Robert North
Tom twickline-at-skybest.com |Wine Mailing Lists| wrote: Hello, Here is what I have for the Changelog thus far. There is 49 entries so far and I could have over looked something. If anything is out of place, incorrect just let me know and ill fix it. Tom -

Re: Mac OS X Support : Asm syntax support

2003-06-26 Thread Pierre d'Herbemont
On Thursday, June 26, 2003, at 11:41 AM, Marcus Meissner wrote: On Wed, Jun 25, 2003 at 02:32:29PM +0200, Pierre d'Herbemont wrote: Hi, Here is a patch which should add support for Mac OS X ppc asm syntax, and some Mach-O quirk (like text section). This needs 2 places fixed: +# define LD_SECTI

Re: Mac OS X Support : Asm syntax support

2003-06-26 Thread Marcus Meissner
On Wed, Jun 25, 2003 at 02:32:29PM +0200, Pierre d'Herbemont wrote: > Hi, > > Here is a patch which should add support for Mac OS X ppc asm syntax, > and some Mach-O quirk (like text section). > I hope it will be ok. It mainly relay on Macro which are stored in > build.h (any better place?). >