September 2008 - Wine-Devel

Re: Recent msi/package tests failures

by James Hawkins

On Mon, Sep 1, 2008 at 10:18 AM, James Mckenzie <jjmckenzie51(a)earthlink.net> wrote: > 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. > Why would you be grep'ing windows msi log files? -- James Hawkins

Sept. 1, 2008

Re: Adding Flawfinder to Patchwatcher

by Hans Petter Selasky

Hi, I've received +50 copies of this e-mail now with full attachments flooding my inbox. Is there a bug at my ISP or is there a bug in the mailman software ? Thanks, --HPS

Sept. 1, 2008

Re: Recent msi/package tests failures

by James Mckenzie

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

Sept. 1, 2008

Re: Recent msi/package tests failures

by Nicolas Le Cam

Same thing here with a 2k box running on VirtualBox. 2008/8/31 Paul Vriens <paul.vriens.wine(a)gmail.com> > 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. > > -- > Cheers, > > Paul. > > >

Sept. 1, 2008

Re: Adding Flawfinder to Patchwatcher

by Wesley Parish

One thing you might do is check your email settings. I received at least twenty coppies of this email - twenty * 3.1 MB. Not nice. Wesley Parish On Friday 29 August 2008 08:59, Austin English wrote: > I had a discussion with Dan about adding Flawfinder to the > patchwatcher. Currently, it's got some pretty generic errors, but it > seems able to test only patches, so we wouldn't be flooded with old > nonbugs (or we could set up a blacklist of safe errors). For > reference, I've run it on today's git. I'm attaching the full log, as > well as a condensed version of the most common errors (1 per error > type). Looks like a lot of chances for buffer overflows.. > > Thoughts? > > -Austin -- Clinersterton beademung, with all of love - RIP James Blish ----- Gaul is quartered into three halves. Things which are impossible are equal to each other. Guerrilla warfare means up to their monkey tricks. Extracts from "Schoolboy Howlers" - the collective wisdom of the foolish. ----- Mau e ki, he aha te mea nui? You ask, what is the most important thing? Maku e ki, he tangata, he tangata, he tangata. I reply, it is people, it is people, it is people.

Sept. 1, 2008

RE: Fix for rendering issues when calling GetDepthStencilSurface

by Stefan Dösinger

> This is a better patch which shows the source of the problem and > implements the correct behaviour of GetDepthStencilSurface. But there > is a problem in function IWineD3DDeviceImpl_GetDepthStencilSurface. > This couldn't return the value which we need (see test cases). So > anyone a suggestion? Reset sets a flag when it fails. In this state, the device is essentially broken, and all you can do is release objects and attempt to call reset again(or destroy the device altogether). We currently implement a few Reset failure conditions and set a flag if Reset fails. I think this is done in d3d9 only right now, but a flag could be set in wined3d too, or d3d9's GetDepthStencilSurface could check the flag and return a different error value.

Sept. 1, 2008

git still down...

by Dan Kegel

$ git pull source.winehq.org[0: 209.46.25.134]: errno=Connection refused :-(

Sept. 1, 2008

Re: Problems Running Windows app

by Vijay Kiran Kamuju

Hi, Please post this a bug in bugzilla. Also please post the detailed logs in the bug description. Please also provide a link and name of the software you are trying to run. Also try testing with the latest wine 1.1.3 Thanks, Vijay Fran Lebowitz - "Life is something to do when you can't get to sleep." On Fri, Aug 29, 2008 at 3:10 AM, Chris Vermeulen <chris.vermeulen(a)itecgroup.co.za> wrote: > 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. > ##################################################################################### > > >

Sept. 1, 2008