Re: New SCSI Driver for Mac OS X

2010-04-27 Thread Charles Davis
On 4/27/10 8:54 PM, C.W. Betts wrote: > Excuse me, but why is this needed again? What IOCTL is missing in Mac OS X's > native implementation? Do I have to explain everything?! All right. Here goes. Way back in October of last year, I started a discussion on this list about SCSI on Mac OS X: htt

Re: New SCSI Driver for Mac OS X

2010-04-27 Thread C.W. Betts
Excuse me, but why is this needed again? What IOCTL is missing in Mac OS X's native implementation? On Apr 27, 2010, at 2:10 PM, Charles Davis wrote: > Hi, > > A while ago on this list, I was talking about implementing SCSI support > on Mac OS X in Wine, and we all agreed the best way to do that

RE: user32: Fix some tests on 2K8R2 and win7

2010-04-27 Thread Greg Geldorp
> From: André Hentschel > > Yepp, the bot doesnt compare results with an unpatched state... Actually, it does. It compares the results of patch jobs against the most recent winetest.exe job for the same VM, which in this case would be https://testbot.winehq.org/JobDetails.pl?Key=1749. That job d

Re: user32: Fix some tests on 2K8R2 and win7

2010-04-27 Thread André Hentschel
Am 27.04.2010 20:55, schrieb (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.win

Re: user32: Fix some tests on 2K8R2 and win7

2010-04-27 Thread testbot
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=1768 Your paranoid android.

Re: Slackware download description line updated to latest package binary format

2010-04-27 Thread Jeremy Newman
This patch does not apply against the current git tree. Please always submit patches using "git format-patch". Also, it helps if you prefix the subject with [website] so I can tell which patches are meant for the website without scanning the body. -Newman Ing. Simone. Giustetti wrote: Hi al

Re: [3/5] msi/tests: Use a unique product code when testing MsiConfigureFeature parameter validation.

2010-04-27 Thread testbot
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=1761 Your paranoid android.

Re: [1/5] msi/tests: Return INVALID_FILE_SIZE from get_pf_file_size if the file can't be opened.

2010-04-27 Thread testbot
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=1760 Your paranoid android.

RE: gdi32: "StretchDIBits" with value of zero for "xSrc" and "ySrc"

2010-04-27 Thread Greg Geldorp
> From: Wolfram Sang > > > === W98SE (32 bit dib) === > > dib.c:159: Test failed: Bitmap data not matching. > [...] > > === WNT4WSSP6 (32 bit dib) === > > dib.c:159: Test failed: Bitmap data not matching. > Probably 16-bit display depth again? Yes. smime.p7s Description: S/MIME cryptographic s

Re: [7/9] msi: Implement the UnregisterMIMEInfo standard action.

2010-04-27 Thread Hans Leidekker
On Tue, 2010-04-27 at 08:55 +0200, Vincent Pelletier wrote: > Backtrace: > =>0 0x7ecf3750 ACTION_UnregisterMIMEInfo+0x260(package=0x131f00) > [/home/vincent/git/wine/dlls/msi/classes.c:1516] in msi (0x0033f998) > 1 0x7ecda25e ACTION_HandleStandardAction+0x1dd(package=, > action="UnregisterMIME

Re: [PATCH] Remove variable dbgtext which is not really used frommake_number.

2010-04-27 Thread Dmitry Timoshkov
James McKenzie wrote: > Could you help us who are trying to match up what has changed by putting > the module name in braces like this: > > [riched20] > > somewhere in the title? Better to follow a commonly used patch naming convention instead: http://wiki.winehq.org/SubmittingPatches -- Dm