June 2006 - Wine-Devel - list.winehq.org

[ntdll patch] Patch dropped?
by Andrew Talbot June 21, 2006

June 21, 2006

I saw a patch I posted yesterday (ntdll: server.c, write-strings fix) appear on the wine-cvs page for a while :), and now it has disappeared :(. Did it fall, or was it pushed? ;) -- Andy.

1 1

Re: Resend: WineD3D: pixel format cleanup
by Stefan Dösinger June 21, 2006

June 21, 2006

> It doesn't (last I checked)... neither does CreateVolume(). > This also requires a test to see what Windows does. > > Checking if a format is supported before > > > returning the gl config doesn't really make sense. If the format isn't > > supported and we ask gl for a compressed texture we will get an error > > returned and broken graphics(because we ignore gl errors generally). If > > we pass 0 instead for the gl format and internal format we will have > > broken graphics too but I don't think gl returns an error then(although > > I'd have to > > check the man page for that) > > I agree, but I thought the patch was a no-op :) Oh well, not a 100% no op then. But that is hard to nop with a constant table :-) Well, almost all cards support that extension, so it's a de-facto no-op

1 0

Re: Resend: WineD3D: pixel format cleanup
by Ivan Gyurdiev June 21, 2006

June 21, 2006

On 6/21/06, Stefan Dösinger <stefan(a)codeweavers.com> wrote: > > This is a resend of the patch from a few days ago with some modifications > requested by Alexandre: > > *getFormatDescEntry returns a pointer to a format structure, not an index > in > the array > > * Removed the format counter Stefan, can you clarify what happened to the GL_SUPPORT check for compressed formats?

2 1

ntoskrnl status
by Mario Demontis June 21, 2006

June 21, 2006

Hello It's my first post here... Any news about ntoskrnl.exe support? As far as I can understand it's not yet integrated... Are there any new patches? Thanks in advance Mario -- Email.it, the professional e-mail, gratis per te: http://www.email.it/f Sponsor: Grande Offerta di Benvenuto Cassine di Pietra: * 36 bottiglie di ottimo vino veneto direttamente a casa tua! * Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=3923&d=15-6

9 14

Re: [Bug 5463] ie6 installs now, but doesn't work...
by Peter Åstrand June 21, 2006

June 21, 2006

On Mon, 19 Jun 2006, Wine Bugs wrote: > vitaliy(a)kievinfo.com changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Status|RESOLVED |CLOSED > > > ------- Additional Comments From vitaliy(a)kievinfo.com 2006-19-06 14:11 ------- > Again this is not a bug. There is nothing to fix because there is nothing that > broke. I disagree. If IE doesn't run, it's a bug. I would actually say that it's a major bug - IE is one the those core applications that users expects to work. You are incorrect about "there is nothing to fix": Perhaps the source code is fine, but the documentation is certainly not. http://appdb.winehq.org/appview.php?versionId=469 even says: "(to be continued because then it still doesn\'t run because of ole errors)" > Anyone is welcome to write up instructions on what to override and place them in > appDB. Bugzilla is not the right place for that. Why do you think Bugzilla cannot be used for tracking documentation bugs? There is a "wine-documentation" component and a "WineHQ Apps Database" component, if you think that wine-misc is totally wrong. I would very much prefer is this bug could be left open until someone has managed to figure out what needs to be overridden to actually *run* IE. Regards, -- Peter Åstrand ThinLinc Chief Developer Cendio http://www.cendio.se Teknikringen 3 583 30 Linköping Phone: +46-13-21 46 00

7 7

Re: wined3d: Bind correct # of samplers for GLSL shaders
by Ivan Gyurdiev June 21, 2006

June 21, 2006

On 6/20/06, Jason Green <jave27(a)gmail.com> wrote: > > - We are only checking against GL_MAX_TEXTURES when binding samplers, > when we should be checking against the maximum number of samplers that > the card supports. Spotted by H. Verbeet. Yes, I'm aware of that...it was done on purpose. This limit is in a lot of other places - stateblock code, drawprim code. Have you checked that it will all interact properly using this higher limit? Specifically, have you tested a sampler > 4 with SetTexture()? I think this problem should be solved by a single patch that updates all the necessary places to use the higher texture units value, as opposed to the legacy one (there's some caps code to write for this).

2 1

solution: IE6 setup says "The download location information is damaged"
by James Hawkins June 21, 2006

June 21, 2006

Hey, If you're still having this problem, please make sure you are not on a remote or network-mounted drive. IE6 setup checks if the drive is remote, and will not install if it is, complaining with the completely non-related error that "The download location information is damaged." If you're not sure whether you're on a remote drive or not, and the IE6 setup is still not working, please post back and attach a +volume trace. I was frustrated that the setup was not working on my work machine, while it was on my home machine. Reading through a +all log showed that GetDriveTypeW was returning 4 for my work machine, which is DRIVE_REMOTE, and then it would fail with the message box. Hacking GetDriveTypeW to always return DRIVE_FIXED let me install onto my remote drive. Thanks, James Hawkins

2 3

wined3d:add an "\n" to a fixme to fix an overflow
by Louis. Lenders June 21, 2006

June 21, 2006

Hi, i get this crash in an application (ftp://ftp.avault.com/demos/puzzleblastsetup.exe) : wine_dbg_vprintf: debugstr buffer overflow (contents: 'fixme:d3d_surface:IWineGDISurfaceImpl_Blt Unsupported flags: 00000010 Unsupported flags: 00000010 Unsupported flags: 00000010 Unsupported flags: 00000010 etcetera This simple patch fixes it. Changelog:add an "\n" to a fixme to fix an overflow --------------------------------- All New Yahoo! Mail Tired of Vi(a)gr@! come-ons? Let our SpamGuard protect you.

1 0

Very large fonts cause loss of connection to X server
by Troy Rollo June 21, 2006

June 21, 2006

Rendering text to a screen DC with a font height on the order of 17,000 pixels results in glyphs being uploaded to the X server that are on the order of 30MB in size (or more for some wide characters). The next attempt to make a request of the server results in a SIGPIPE. This is possible if an app has the ability to zoom in on a document containing text and allows the user to specify the scaling factor without limiting it. Very large screen fonts can also arise when some WYSIWYG display strategies are used, although this would not ordinarily get to the 17,000 pixel range. Windows deals with such behaviour without problems. I'm not sure there's anything that can be done about this other than imposing an arbitrary sanity check on the size of the screen font prior to uploading the glyph - if the font is much larger than the screen, for instance, then perhaps the best thing is just not to upload the glyph but mark it internally as having been uploaded. Presumably that will prevent the loss of connection without breaking WYSIWYG display strategies that involve calculating positions using large fonts in a screen DC. -- Troy Rollo - wine(a)troy.rollo.name

1 0

Re: [AppDB] - make variables more consistent, fix indenting
by Tony Lambregts June 21, 2006

June 21, 2006

Chris Morgan wrote: > Make the code more consistent by using the appdb coding standards. > > Change $result = query_appdb(...) to $hResult = ... etc. > > Also fix some odd indenting due to spaces vs. tabs. > > There are still a ton of variables that are integers or strings that should be > prefixed with 'i' or 's' if anyone is interested in cleaning some of that up. > > Chris I am not opposed to doing this but I think that the patch is way too big. At the momment we still have issues with the last "big patch" that are not cleared up [1]. On the whole unless we cannot avoid it I really do not think that we should be making such large changes in one go like this. Please break up the patch into smaller patches. That way it is easier to find and fix any issues that arise. [1] New versions end up as orphans with current setup. -- Tony Lambregts

2 4