September 2008 - Wine-devel

Re: Recent msi/package tests failures
by James Mckenzie 01 Sep '08

01 Sep '08

Paul/James: Paul Vriens wrote: >James Hawkins wrote: >> On Sat, Aug 30, 2008 at 3:17 PM, Paul Vriens <paul.vriens.wine(a)gmail.com> wrote: >>> Hi, >>> >>> I just sent a few patches that fix the problem with the timeout on my >>> machines. >>> >>> Do you think it's still worthwhile to disable logging by using >>> MsiEnableLogA? When I now look in my temp folder I have a few hundred MSI >>> log files. We could either disable logging or create 1 file ourselves and >>> append everything to there (removing it afterwards maybe). >>> >> >> Logging to one file takes just as long as any other type of logging. >> No logging should be happening. No I don't think it's worth using >> MsiEnableLog to disable loggin. Logging is not enabled by default, >> and to enable it you have to change some registry entries, which I >> doubt anyone is doing. >> >The reason for the 1 file was not to speed up things but to limit the number of >logfiles in the temp directory (and maybe the ability to remove this file as we >know the one we created ourselves). > >On all of my boxes (95/98/NT/W2K/ 2 times XP/W2K3/Vista) I end up with 200 or so >logfiles in the temp directory after running the install tests. On none of these >boxes did I do anything to tinker with the msi logging settings. > >It would be nice if other could tell if they have a huge number of these >logfiles in their temp directory after running the tests. > +1 to one log file. I hate having to look through piles of log files to find errors. Yes, I know that I could grep them, but that is an added step that should not be needed. -- James McKenzie

2 1

Recent msi/package tests failures
by Paul Vriens 01 Sep '08

01 Sep '08

Hi, I was looking into the recent test failures for the msi/package tests on my WinXP box. The reason for most of them was a stray MSITEST package that couldn't be removed via the 'Add/Remove Programs' (had to remove stuff from the registry). Any one else seeing this? (Adam Petaccia's XP box has the same issue I guess). -- Cheers, Paul.

5 12

RE: Fix for rendering issues when calling GetDepthStencilSurface
by Stefan Dösinger 01 Sep '08

01 Sep '08

> When IWineD3DDevice_GetDepthStencilSurface returns WINED3DERR_NOTFOUND > it was setting ppZStencilSurface to null. This was the cause of > rendering issues with the 3d models in spore. Can you write a test for this? I think we have some depth stencil tests in dlls/d3d9/tests/device.c which you could use to test this. I think you are right with this patch - I vaguely remember writing a test for a different getter function, but it is better to be sure

3 4

Problems Running Windows app
by Chris Vermeulen 01 Sep '08

01 Sep '08

Hi Please help me I'm currently running ubuntu 8.04, with wine 1.0 I've got a program that I use to program Telephone systems. It uses a SQL database with a web interface. but I can't get this to work on wine, if I want to install it gives me the following and just closes. Usage: Install a product: msiexec {package|productcode} [property] msiexec /i {package|productcode} [property] msiexec /a package [property] Repair an installation: msiexec /f[p|o|e|d|c|a|u|m|s|v] {package|productcode} Uninstall a product: msiexec /x {package|productcode} [property] Advertise a product: msiexec /j[u|m] package [/t transform] [/g languageid] msiexec {u|m} package [/t transform] [/g languageid] Apply a patch: msiexec /p patchpackage [property] msiexec /p patchpackage /a package [property] Modifiers for above operations: msiexec /l[*][i|w|e|a|r|u|c|m|o|p|v|][+|!] logfile msiexec /q{|n|b|r|f|n+|b+|b-} Register a module: msiexec /y module Unregister a module: msiexec /z module Display usage and copyright: msiexec {/h|/?} NOTE: Product code on commandline unimplemented as of yet Copyright 2004 Vincent B�ron Please help I'm hate this dual booting into windows. If I can get this working It'll be like a huge Christmas gift. If you need the program let me know and I'll get it to you Thanks Chris Vermeulen ##################################################################################### Notice This e-mail message and/or attachments may contain information that is confidential to ITEC and/or any of its affiliated companies. If you are not the intended recipient you cannot use, distribute or copy the message and/or attachments. In such a case, please notify the sender by return e-mail immediately and erase all copies of the message and/or attachments. Opinions, conclusions and other information in this message and/or attachments that do not relate to the official business of ITEC or any of its affiliated companies are neither given nor endorsed by it. ITEC and its affiliated companies accept no liability or responsibility of whatever nature for any failure or loss arising from the use of email as a form of communication. #####################################################################################

2 1