Re: Warcraft 3 Copy Protection (regression?)

Warcraft 3 will not run without a crack after the following commit: http://www.winehq.org/hypermail/wine-cvs/2004/03/0093.html If no one wants to tackle this immediately I'd like to fix it. Any ideas? Brian G. > > I don't know whether the difference was something about the version of WC3, or >

Re: CreateFile GENERIC_WRITE on a directory

Opened a bugzilla:

Re: RFC re winmm/time.c

In terms of other optimization, you can remove the call to TIME_MMTimeStart in most of the places, except for a timer creation. The other places rely on it to get WINMM_SysTimeMS updated, but since you killed it... Good point. I'd mainly like to get rid of the poor anti-race scheme that's imple

CreateFile GENERIC_WRITE on a directory

Not sure if this should be in -users, but I'm trying to get the Tribes: Vengeance dedicated server going (1st person shooter) and it stops with a messagebox that it can't write to its own directory. Tracing the program with +relay reveals this: 000b:Call kernel32.CreateFileW(10415fc0 L"Z:\\home

Re: Revised Wine User Guide Introduction

On Sun, 2004-10-10 at 09:34 -0400, Dimitrie O. Paun wrote: > On Sat, Oct 09, 2004 at 06:30:19PM -0700, Scott Ritchie wrote: > > The version 0.9 todo list (bug 85) specifies the need for a rewritten > > intro to the Wine User Guide. > > > > This patch is that rewritten intro. It rewords things to

RE: wine-devel digest, Vol 1 #3011 - 15 msgs

Vitaliy Margolen wrote: > Well, I tried to shuffle the order of creation of these > files. The results I got was as follows: > - On windows I was getting "sorted by name" order. > - On Linux I was getting creation order. Funny thing is I work on Suse Linux 9.0 with current wine CVS and IEnumIDLi