October 2012 - Wine-Devel - list.winehq.org

Re: [PATCH 1/3] vbscript: Added Trim() implementation

by Marvin

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at http://testbot.winehq.org/JobDetails.pl?Key=21942 Your paranoid android. === WNT4WSSP6 (32 bit) === No test summary line found === W2KPROSP4 (32 bit) === No test summary line found === WXPPROSP3 (32 bit) === No test summary line found === W2K3R2SESP2 (32 bit) === No test summary line found === WVISTAADM (32 bit) === No test summary line found === W2K8SE (32 bit) === No test summary line found === W7PRO (32 bit) === No test summary line found === W7PROX64 (32 bit) === No test summary line found === TEST64_W7SP1 (32 bit) === No test summary line found === W7PROX64 (64 bit) === No test summary line found === TEST64_W7SP1 (64 bit) === No test summary line found

Oct. 2, 2012

Re: wininet(2/2): Fail to commit a url cache entry when the original URL is specified and no local filename is given

by Piotr Caban

On 10/02/12 03:31, Juan Lang wrote: @@ -3084,6 +3084,11 @@ static BOOL CommitUrlCacheEntryInternal( SetLastError(ERROR_INVALID_PARAMETER); return FALSE; } + if (lpszOriginalUrl && !lpszLocalFileName) + { + SetLastError(ERROR_INVALID_PARAMETER); + return FALSE; + } if (lpszOriginalUrl) WARN(": lpszOriginalUrl ignored\n"); The function should succeed if lpszOriginalUrl is specified and it operates on history container. Probably the check for lpszLocalFileName with STICKY_CACHE_ENTRY is also redundant. I guess that the lpszLocalFileName should be validated in following way: if(pContainer->default_entry_type==NORAML_CACHE_ENTRY && !lpszLocalFileName) { SetLastError(ERROR_INVALID_PARAMETER); return FALSE; } I haven't check what happens for cookies containers. Cheers, Piotr

Oct. 2, 2012

Re: [PATCH] scsiport.sys: Add stub implementaton of scsiport.sys.

by Christian Costa

Le 02/10/2012 00:26, André Hentschel a écrit : > Am 02.10.2012 00:10, schrieb Christian Costa: >> This is needed by prosync1.sys (StarForce protection) used in Obscure. >> --- >> configure | 284 +++++++++++++++++------------------ >> configure.ac | 1 >> dlls/scsiport.sys/Makefile.in | 9 + >> dlls/scsiport.sys/scsiport.c | 39 +++++ >> dlls/scsiport.sys/scsiport.sys.spec | 48 ++++++ >> 5 files changed, 238 insertions(+), 143 deletions(-) >> create mode 100644 dlls/scsiport.sys/Makefile.in >> create mode 100644 dlls/scsiport.sys/scsiport.c >> create mode 100644 dlls/scsiport.sys/scsiport.sys.spec >> >> diff --git a/configure b/configure >> index 54675b4..801dcf8 100755 >> --- a/configure >> +++ b/configure >> @@ -1,11 +1,13 @@ >> #! /bin/sh >> # Guess values for system-dependent variables and create Makefiles. >> -# Generated by GNU Autoconf 2.69 for Wine 1.5.14. >> +# Generated by GNU Autoconf 2.68 for Wine 1.5.14. > You should not include configure changes > > > It's a mistake. Thanks.

Oct. 2, 2012

Re: [PATCH] scsiport.sys: Add stub implementaton of scsiport.sys.

by André Hentschel

Am 02.10.2012 00:10, schrieb Christian Costa: > This is needed by prosync1.sys (StarForce protection) used in Obscure. > --- > configure | 284 +++++++++++++++++------------------ > configure.ac | 1 > dlls/scsiport.sys/Makefile.in | 9 + > dlls/scsiport.sys/scsiport.c | 39 +++++ > dlls/scsiport.sys/scsiport.sys.spec | 48 ++++++ > 5 files changed, 238 insertions(+), 143 deletions(-) > create mode 100644 dlls/scsiport.sys/Makefile.in > create mode 100644 dlls/scsiport.sys/scsiport.c > create mode 100644 dlls/scsiport.sys/scsiport.sys.spec > > diff --git a/configure b/configure > index 54675b4..801dcf8 100755 > --- a/configure > +++ b/configure > @@ -1,11 +1,13 @@ > #! /bin/sh > # Guess values for system-dependent variables and create Makefiles. > -# Generated by GNU Autoconf 2.69 for Wine 1.5.14. > +# Generated by GNU Autoconf 2.68 for Wine 1.5.14. You should not include configure changes

Oct. 1, 2012

Wine Mono 0.0.8 Release

by Vincent Povirk

Since I messed up the 0.0.6 release, here's another one, almost identical. The source tarball is at http://sourceforge.net/projects/wine/files/Wine%20Mono/0.0.8/wine-mono-0.0.… The binary is at http://sourceforge.net/projects/wine/files/Wine%20Mono/0.0.8/wine-mono-0.0.… For developers, the source repository is at https://github.com/madewokherd/wine-mono Changes since 0.0.4: * Updated the visual basic class libraries from upstream. * Updated mono from 2.11.1 to 2.11.4. Unfortunately, there wasn't a nice changelog like 2.11.1 had. Here are some highlights: * Beginnings of support for hosting ActiveX controls inside winforms. (Alistair Leslie-Hughes) * Various HttpClient-related fixes. (Martin Baulig) * "Intermediate" state check boxes now rendered in winforms. (Steven Boswell II) * ACL support on Windows. (James Bellinger) * One can now specify WINE_MONO_TRACE=wrapper to log all transitions between native and managed code, which is sort of the Mono equivalent of a relay log. * RVA fields can now be accessed properly via the ldsfld[a] instruction. This should help with Managed C++ support. * Fix for winehq bug 30947 - Mono would cause a hang when a dll is loaded after Mono is loaded but before it is used to run any .NET code. * Because of a problem with the build system, MonoPosixHelper.dll was not present, and this prevented some builtin methods in Mono from working correctly. This has been resolved. * Added hashes for all included files in the msi package, which is needed for msi to replace the files on upgrade. * Added 64-bit registry entries to the msi package. * Build process now fails immediately if wine or gmcs is missing, instead of waiting until they're used. (Austin English)

Oct. 1, 2012

Re: ws2_32: Fix TRACE format in WS_getsockname (try 2)

by Bruno Jesus

On Mon, Oct 1, 2012 at 12:37 AM, Dmitry Timoshkov <dmitry(a)baikal.ru> wrote: > Bruno Jesus <00cpxxx(a)gmail.com> wrote: > >> - TRACE("socket: %04lx, ptr %p, len %8x\n", s, name, *namelen); >> + TRACE("socket: %04lx, ptr %p, len %08x\n", s, name, namelen?*namelen:0); > > Adding some spaces to make this slightly more readable wouldn't hurt IMHO. I just copied the same solution from the other function. I will look for all constructions like that and fix all of them a in next patch. > Dmitry. Best wishes, Bruno

Oct. 1, 2012

Re: [PATCH 6/6] wininet/tests: Remove all temporary files

by Marvin

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at http://testbot.winehq.org/JobDetails.pl?Key=21929 Your paranoid android. === WINEBUILD (build) === Patch failed to apply

Oct. 1, 2012

Re: [PATCH 5/6] wininet: Set entry type based on container type

by Marvin

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at http://testbot.winehq.org/JobDetails.pl?Key=21928 Your paranoid android. === WINEBUILD (build) === Patch failed to apply

Oct. 1, 2012

Re: [PATCH 4/6] wininet: Added support for cache entries overwritting

by Marvin

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at http://testbot.winehq.org/JobDetails.pl?Key=21927 Your paranoid android. === WINEBUILD (build) === Patch failed to apply

Oct. 1, 2012

Re: [1/4] Assorted spelling fixes.

by Piotr Caban

Hi, On 10/01/12 13:07, Julian Rüger wrote: > Hi Francois, > >> - * size [I] How much percent of cache space should be free. >> + * size [I] How many percents of the cache should be free. > > Maybe something like "Precentage of cache that should be free" would > sound more natural. However I'm not sure of the intended meaning here, > it could be "freed". The intended meaning is: Percentage of maximal cache size that should be free when the function succeeds. The function doesn't guarantee that it will clean any files, this parameter is only a clue. When there's already enough free space in the cache the function may exit without freeing any files. Cheers, Piotr

Oct. 1, 2012