January 2011 - Wine-devel - list.winehq.org

/ is writable on mac... leading to lots of awkward msi droppings?
by Dan Kegel 05 Jan '11

05 Jan '11

Quentin Paris informs me that the root directory is user-writable on MacOSX (shudder), which means our beloved z: mapping leads to lots of garbage directories named e.g. /fd91216cc2ce81eb2ce16a058619 after running msi installers. Is this something Wine's msi could avoid doing?

4 4

WyldBot
by wylda＠volny.cz 05 Jan '11

05 Jan '11

Hi, i take the chance to make this info publicaly aware, so adding wine-devel > Hi, > your WyldBot has some Audio/Video issues in it's > XP machines no other machines have, in which VM do > they run? WyldBOT1 and WyldBOT2 are not VM, but true physical older-machines made only for wine-testing. WyldBOT1 has more OS so little explanation here: * WyldBOT1-ie6 was cleanlly installed, patched and never run wine-test (to avoid broken registry thing by wine-testsuite sometime ago), than made image of that partition * for WyldBOT1-ie7, i restored image of WyldBOT1-ie6 and installed IE7 on top of it * for WyldBOT1-ie8, i restored image of WyldBOT1-ie6 and installed IE8 on top of it * for WyldBOT1 64bit edition i did exactly same installation steps like in 32bit * for WyldBOT2 i did exactly same installation steps like in WyldBOT1-ie6, but runs on different HW box (it's not the same image like WyldBOT1-ie6, only same installation steps) So things works that way, that when i power up that machine and boot into WyldBOT-recovery and then * recovery takes the first image from second HDD * changes boot.ini sequence * reboots and then boots into WyldBOT1-ie6 * WyldBOT1-ie6 waits 120sec to finish all services startup and not disturb winetest * downloads the wine test suite from FTP + some testing video file etc. * it does the winetesting * changes boot.ini and to boot into Wylbot recovery * Wylbot recovery takes another image * and so on and after last image the machine si turned off This Chrismas time (after 8months) Wylbot was restored just for windows update and updated images were store again. Once on wine-devel, i noticed some speculation, that it uses old drivers, so nvidia drivers got updated too on all WyldBOT1. I used to run WylBOT 3x per week, but there were no changes or effort to fix things, so i reduced the WylBOT run to once a week (i do my best not to miss friday's release, but sometime i run it on saturday/sunday. Maybe when the relese would be around 17h UTC, i could make it friday-regular ;) As WyldBOT2 was unlucky and did not get those fresh updates as his brother WyldBOT1, i didn't turn it on recently. WyldBOT1's HW: MB: Asus P5K-E WiFi AP Bios rev. 1305 Intel Core 2 Quad Processor Q9550 sSpec Number: SLB8V CPU SPeed: 2.83GHz Bus speed: 1333MH z L2 Cache size: 12MB Package Type: LGA775 Technology: 45nm 8GB RAM Kingston HyperX DDR2 2x KHX8500D2T1K2/4G (DDR800), CAS: 5-5-5-18 Nvidia 8600GT latest driver 260.99, latest DirectX June2010 redist v9.29.1962 (2010-06-07) Soundcard Asus's onboard (i guess it uses "SoundMAX ADI Audio Driver") Some printers Wheel wingman formula force gp2 Wheel Microsoft (thurstmaster??) If interested in details let me know, i can look closer at home. > Btw: you can use the winetest option "-i" to add a > description of the machine... That's a pity, that i didn't have this info one week back, when i did the image jobs. But maybe it's stored on the FTP in control file, so won't be a hard job - don't know now. > > Best Regards, André Hentschel PS1: On Monday i noticed, that other machines have D3Dcompiler_43 installed, but mine's not even if i cleanly installed June's 2010 DirectX. Do you guys use for testing those messy free-dll downloads??? PS2: Wylbot2 has Intel Graphic Card and used to have completely different 2D/3D?? testing-pictures (those red, greens,... flashing shapes). But i didn't find a time to report the differences.

1 0

Re: d3dcompiler_43/tests: fixed nonconformant C string literals in HLSL test suite
by Henri Verbeet 05 Jan '11

05 Jan '11

On 4 January 2011 22:25, Travis Athougies <iammisc(a)gmail.com> wrote: > + "float4 test(float x: TEXCOORD0): COLOR" > + "{" > + " const float pi2 = 6.2831853;" > + " float calcd_sin = (sin(x * pi2) + 1)/2;" > + " float calcd_cos = (cos(x * pi2) + 1)/2;" > + " return float4(calcd_sin, calcd_cos, 0, 0);" > + "}"; Some newlines probably wouldn't hurt.

1 0

Re: kernel32/tests: Don't test function directly when reporting GetLastError()
by Marvin 04 Jan '11

04 Jan '11

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=8130 Your paranoid android. === WNT4WSSP6 (32 bit pipe) === pipe.c:878: Test failed: WriteFile to not-yet-connected pipe pipe.c:880: Test failed: ReadFile from not-yet-connected pipe pipe.c:897: Test failed: WriteFile to disconnected pipe pipe.c:899: Test failed: ReadFile from disconnected pipe with bytes waiting === W2KPROSP4 (32 bit pipe) === pipe.c:878: Test failed: WriteFile to not-yet-connected pipe pipe.c:880: Test failed: ReadFile from not-yet-connected pipe pipe.c:897: Test failed: WriteFile to disconnected pipe pipe.c:899: Test failed: ReadFile from disconnected pipe with bytes waiting === WXPPROSP3 (32 bit pipe) === pipe.c:878: Test failed: WriteFile to not-yet-connected pipe pipe.c:880: Test failed: ReadFile from not-yet-connected pipe pipe.c:897: Test failed: WriteFile to disconnected pipe pipe.c:899: Test failed: ReadFile from disconnected pipe with bytes waiting === W2K3R2SESP2 (32 bit pipe) === pipe.c:878: Test failed: WriteFile to not-yet-connected pipe pipe.c:880: Test failed: ReadFile from not-yet-connected pipe pipe.c:897: Test failed: WriteFile to disconnected pipe pipe.c:899: Test failed: ReadFile from disconnected pipe with bytes waiting === WVISTAADM (32 bit pipe) === pipe.c:878: Test failed: WriteFile to not-yet-connected pipe pipe.c:880: Test failed: ReadFile from not-yet-connected pipe pipe.c:897: Test failed: WriteFile to disconnected pipe pipe.c:899: Test failed: ReadFile from disconnected pipe with bytes waiting === W2K8SE (32 bit pipe) === pipe.c:878: Test failed: WriteFile to not-yet-connected pipe pipe.c:880: Test failed: ReadFile from not-yet-connected pipe pipe.c:897: Test failed: WriteFile to disconnected pipe pipe.c:899: Test failed: ReadFile from disconnected pipe with bytes waiting === W7PRO (32 bit pipe) === pipe.c:878: Test failed: WriteFile to not-yet-connected pipe pipe.c:880: Test failed: ReadFile from not-yet-connected pipe pipe.c:897: Test failed: WriteFile to disconnected pipe pipe.c:899: Test failed: ReadFile from disconnected pipe with bytes waiting === W7PROX64 (32 bit pipe) === pipe.c:878: Test failed: WriteFile to not-yet-connected pipe pipe.c:880: Test failed: ReadFile from not-yet-connected pipe pipe.c:897: Test failed: WriteFile to disconnected pipe pipe.c:899: Test failed: ReadFile from disconnected pipe with bytes waiting === W7PROX64 (64 bit pipe) === pipe.c:878: Test failed: WriteFile to not-yet-connected pipe pipe.c:880: Test failed: ReadFile from not-yet-connected pipe pipe.c:897: Test failed: WriteFile to disconnected pipe pipe.c:899: Test failed: ReadFile from disconnected pipe with bytes waiting

1 0

Re: user32/tests: Don't test function directly when reporting GetLastError()
by Marvin 04 Jan '11

04 Jan '11

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=8127 Your paranoid android. === WVISTAADM (32 bit clipboard) === Failure running script in VM: The specified guest user must be logged in interactively to perform this operation

1 0

re: include: Add ONCE macro for making debug output less noisy
by Dan Kegel 04 Jan '11

04 Jan '11

Alexandre wrote: >> +#define WINE_ONCE(do_once) ... > > I don't think that buys anything over spelling it out explicitly. It makes it easier to grep for, which might be useful if you want to find all the places it's used to throttle messages that shouldn't be happening in the first place.

1 0

Re: include: Add ONCE macro for making debug output less noisy
by Alexandre Julliard 04 Jan '11

04 Jan '11

Sven Baars <sven.wine(a)gmail.com> writes: > @@ -250,6 +250,12 @@ static inline const char *wine_dbgstr_longlong( ULONGLONG ll ) > #define WINE_DPRINTF wine_dbg_printf > #define WINE_MESSAGE wine_dbg_printf > > +#define WINE_ONCE(do_once) \ > + do{ static int wine_once_var; \ > + if (!wine_once_var) { \ > + wine_once_var = 1; \ > + do_once; } } while(0) I don't think that buys anything over spelling it out explicitly. -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: winemaker: Add def file support
by Alexandre Julliard 04 Jan '11

04 Jan '11

André Hentschel <nerv(a)dawncrow.de> writes: > @@ -2480,7 +2498,9 @@ sub generate_project_files($) > my $canon=canonize("@$target[$T_NAME]"); > $canon =~ s/_so$//; > > - if (@$target[$T_TYPE] == $TT_DLL) { > + if (@$target[$T_TYPE] == $TT_DLL && (@$project_settings[$T_FLAGS] & $TF_HASDEF)) { > + print FILEO "\$(${canon}_MODULE).so: \$(${canon}_OBJS) \$(${canon}_MODULE:%.dll=lib%.def)\n"; > + } elsif (@$target[$T_TYPE] == $TT_DLL) { There's no reason to add a lib prefix. -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: advapi32: Parital Implement InitiateSystemShutdown(Ex) (try 2)
by Alexandre Julliard 04 Jan '11

04 Jan '11

André Hentschel <nerv(a)dawncrow.de> writes: > @@ -232,6 +233,10 @@ BOOL WINAPI InitiateSystemShutdownExA( LPSTR lpMachineName, LPSTR lpMessage, > DWORD dwTimeout, BOOL bForceAppsClosed, BOOL bRebootAfterShutdown, > DWORD dwReason) > { > + if (!lpMachineName && !lpMessage && !dwTimeout) > + ExitWindowsEx(bRebootAfterShutdown ? EWX_REBOOT : 0 | > + bForceAppsClosed ? EWX_FORCE : 0, > + dwReason); > FIXME("%s %s %d %d %d %d\n", debugstr_a(lpMachineName), > debugstr_a(lpMessage), dwTimeout, bForceAppsClosed, > bRebootAfterShutdown, dwReason); I don't think you want to call user32 functions here. -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: wined3d: Revert vertex blend capabilities patch
by Stefan Dösinger 04 Jan '11

04 Jan '11

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Yep, the patch(f41fdb22...) should be reverted. As I explained on IRC, the correct approach is to implement a replacement shader for the vertex pipeline and implement vertex blending in it. Henri has a rebased version of my ARBvp experiments from 2008. Am 04.01.2011 um 05:42 schrieb Jeremy Chin: > My previous patch was accepted as f41fdb225cf1e1df494237664ce92e51179f3725, though Henri Verbeet pointed out it was incorrect. stefan on IRC warned that announcing blend capabilities without supporting them may cause issues, hence the revert.<0002-Revert-wined3d-Update-detection-of-vertex-blend-ca.txt> -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.16 (Darwin) iQIcBAEBAgAGBQJNIxBHAAoJEN0/YqbEcdMw8boQAIy4oDcaDv90bSyxMZJ4HwZy q/bKznK807Rt6UmL8p4OplFLdAOF+mMnqDmNT9vZxr5k7rWC3GDtW+5nohKwyl74 rpQI71lSTo1lixjPP0t+t2bASl9mQ/Gb2AfPqiFsG0dZmKxwP7aa/25h01ZucHTc c39j234nXxQ1po5j00PoaA0Ya5yeCQ3edFdBMSPorPTdYLVGuHWSA4qdVQdf6mq4 /luSIkMp/MUygqEMCvT9/elaRjCG1dJ9RE4JBXOCtK5CgkCxN+MdnVrTguGeWTtc UV2rwNTZA+4KZouegDQPeHb2qKoQRuNWLdM07/yvCE5rVDJBiAem+MYOjJ3LHsP2 nB3Vfff2zmC6mp+544aQIKFtu0RC2IVU+AbcdmRV6yDwbNK3/wZb3ZV1LcOZ5Z1h 9m5uINreq1R54FnjA1xaYPmWMutN8jVYn2SBPfLA11dKh0sFwsjS4PkUPH1fbAOi nmjwtd7r1z6AyoaP12XIrXGkTNSx8bMHQ9twfWq4D8IqbefMYtrkh896F/wfTIQI nT0FGeDL3gCafpW+wkGQT78tVMZXCAIx2rb+C3sZd/KcQzVCMcgbfFY6R5LnrYVf k+M6CsM0ZyAfIyMpkEFwruMAV0zYQ6NAMhFL4muiyRjY4UA2YvtLhPrNjOp5LAi0 EfbvhcGcDQeh4W45ljuv =HOqP -----END PGP SIGNATURE-----

1 0