Re: Fix snprintfW Return Value

Rob Shearman <[EMAIL PROTECTED]> writes: > On Fri, 2004-07-09 at 19:55, Alexandre Julliard wrote: >> Actually, something does depend on it: it is used to implement >> _vsnwprintf in ntdll, so you can't change it. > > How about this updated patch then? No, vsnprintfW is used directly in ntdll.spec

strange problem on mdk10

on my laptop wine just starts and doesn't do anything. In addition to this, ps -A, ctrl+c, ctrl+z, the kde system guard and all tools that popup a box to ask for root password all stop working. Attached is a relay log. Any ideas? log.txt.bz2 Description: BZip2 compressed data

Re: Debugger bugs

Mike Hearn a écrit : Hi guys, I've got a few problems with various debuggers. Can anybody help? 1) gdb doesn't seem to catch signals to sent to Wine. In a crash, winedbg is invoked without gdb ever being aware of it. run the winedbg in gdb proxy mode, this should work fine. 2) winedbg can't locate

Re: PATCH: tests/vartype gcc fix

Marcus Meissner <[EMAIL PROTECTED]> writes: > Illegal lvalue casts in tests/vartype.c spotted by new compiler. Also > the format strings were wrong for long longs. Long long format strings are not portable, they shouldn't be used. -- Alexandre Julliard [EMAIL PROTECTED]

Re: added API documentation to advapi32/crypt.c

Wow, go truiken! This sort of stuff is really handy, it's so much easier to document wierd stuff in the Wine API docs than rely on MSDN and peoples memories. Good work! On Mon, 2004-07-12 at 02:44 -0500, [EMAIL PROTECTED] wrote: > Changelog >* Added API documentation to most crypt.c functions

Re: Status of MSI

On Saturday 10 July 2004 20:15, Mike McCormack wrote: > Consider adding "msi" = "native, builtin" to your Wine configuration > files, and not installing the MSI redistributables straight away when > you encounter an installer that uses msi.dll :) Let us know what bugs > that turns up. When I

Re: Status of MSI

On Sat, 10 Jul 2004 13:15:16 -0500, Mike McCormack wrote: > Consider adding "msi" = "native, builtin" to your Wine configuration > files, and not installing the MSI redistributables straight away when > you encounter an installer that uses msi.dll :) Let us know what bugs > that turns up. Rand

Re: Stack blowout in _w95_dump_dke

Hi, On Mon, Jul 12, 2004 at 07:53:33AM +1000, by way of Troy Rollo <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > _w95_dump_dke has code in it that processes sibling keys in the registry > recursively. This results in a stack blowout for large registries (in my