<div>hopefully nobody flames me but i just tied all these bugs together thru bug 5350.. they block it now.. maybe i should just make them all dupes instead?</div>
<div> </div>
<div>plz dont flame me im just trying to help</div>
<div> </div>
<div>Tom<br><br> </div>
<div><span class="gmail_quote">On 6/3/06, <b class="gmail_sendername">EA Durbin</b> <<a href="mailto:ead1234@hotmail.com">ead1234@hotmail.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">I have compiled a list of applications that are affected by the bug in which<br>the query in ready_media_for_file() in MSI returns the wrong results, it
<br>returns LastSequence less than the file->Sequence being passed.<br><br>Here is a detailed analysis of the multiple types of errors this bugs<br>causes.<br><br>Common debug outputs of this bug are:<br><br>Error #1:
<br><br>err:msi:ACTION_InstallFiles compressed file wasn't extracted<br><br>This error is usually caused by the results of the query returning a<br>LastSequence number of Less than that of the working install media and the
<br>installer is trying to extract the file from the wrong install medium.<br><br>Error #2:<br><br>err:msi:extract_cabinet_file FDICopy failed<br>err:msi:ACTION_InstallFiles Unable to ready media<br><br>There is a zero in LastSequence Value of the Media table and the query in
<br>ready_media_for_file() returns it. For some reason the msi file has a zero<br>in the LastSequence but its really a dummy cabinet file and doesn't exist.<br>The file sequence being passed for the first file is most likely 1, and the
<br>query of >= 1 is returning 0 falsely causing this error.<br><br><br><br>This problem in MSI spans a multitude of bugs.<br><br><br>America's Army - bug #5139<br>J2SE - bug # 4280<br>Half Life 2 - bug # 5004, 4533<br>
Dawn of War Demo - bug # 3749<br>E-Sword 6.5 - bug # 4251<br>Rush for Berlin demo - bug #5187<br>ATI demo(Rendering With Natural Light ) - bug # 4712?<br><br>There are probably other bugs resulting from this, but the log doesn't
<br>detail it well enough, alot of them just have the debug dump at the end and<br>not the pertainent msi err lines. I only included applications where it was<br>obvious from the log, or I tested personally.<br><br>>From: Mike McCormack <
<a href="mailto:mike@codeweavers.com">mike@codeweavers.com</a>><br>>To: EA Durbin <<a href="mailto:ead1234@hotmail.com">ead1234@hotmail.com</a>><br>>Subject: Re: FW: RE: My 1.0 wish list<br>>Date: Sun, 04 Jun 2006 00:30:41 +0900
<br>><br>><br>>You can send me as many mails as you like, but I'm not doing anything until<br>>there's a test case showing the problem.<br>><br>>Mike<br><br>I wrote a test showing the results of the query in the wine installer and
<br>included the source code and resulting logs which clearly displays the<br>problem. That's the best I can do. I'm not up to snuff on my C programming,<br>nor am I familiary with how the official test case for wine is supposed to
<br>be layed out. If someone else wants to work on it then thats fine, but I<br>layed out the problem, and debugged it, and I've proven this with code and<br>resulting logs. This problem affects a multitude of applications in wine. If
<br>your not willing to work on it then either someone else can, or it can<br>remain broken.<br><br><br><br><br></blockquote></div><br>