August 2005 - Wine-Devel - list.winehq.org

Re: Need help debugging a memory corruption bug in shfldr_unixfs.c

by Phil Krylov

On Fri, 26 Aug 2005 22:10:16 +0200 Michael Jung <mjung(a)iss.tu-darmstadt.de> wrote: > 2) Did other people see this bug already? Yes, I confirm it. -- Ph.

Aug. 29, 2005

Re: [BUG1001]: please update comments

by Tony Lambregts

Vijay Kiran Kamuju wrote: > Hi, > > I am getting the following error, > > Not allowed You tried to change the short_desc field from Define macros > STATUS_ENDPOINT_CLOSED, STATUS_DISCONNECTED and STATUS_NONEXISTENT_NET_NAME > to Define macros STATUS_ENDPOINT_CLOSED, STATUS_DISCONNECTED, but only the > owner or submitter of the bug, or a sufficiently empowered user, may change > that field. > > and one more thing, i can only see the leave as new near the commit button. > > Thanks you, Vijay > There was cr/lf in this field (which I removed). So that's somewhat reasonable if you were in the field short_desc (Summary:) at least once before you hit the commit button (perhaps even if you were not). Since you _were_ _not_ a member of either group it gave you the error message. ( You are now..<g>) So at this point the following questions 1. Did you really try to edit this field? 2. Did you enter this field? 3. Which browser are you using? By the way... Are there any other new developers who would like the ability to edit bugs? Just give me an email and I will gladly empower you! -- Tony Lambregts

Aug. 29, 2005

Re: [BUG1001]: please update comments

by Vijay Kiran Kamuju

Hi, I am getting the following error, Not allowed You tried to change the short_desc field from Define macros STATUS_ENDPOINT_CLOSED, STATUS_DISCONNECTED and STATUS_NONEXISTENT_NET_NAME to Define macros STATUS_ENDPOINT_CLOSED, STATUS_DISCONNECTED, but only the owner or submitter of the bug, or a sufficiently empowered user, may change that field. and one more thing, i can only see the leave as new near the commit button. Thanks you, Vijay On 8/28/05, Tony Lambregts <tony.lambregts(a)gmail.com> wrote: > Vijay Kiran Kamuju wrote: > > Hi, > > > > for BUG 1001, please update the comments with the following link, > > > > http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q113996 > > > > I am unable to update via bugzilla, my id is infyquest, its giving me > > error that the short_id_desc is missing. > > > > Thanks, > > Vijay > > > I am curious why you are unable to add a comment... Or were you tying to add the link in the URL field? I looked at your account and > it seems fine, and I was able to add a comment with the link you provided. If you could you try to add a comment again and report > back I would appreciate it. > > -- > > Tony Lambregts > > > >

Aug. 28, 2005

Re: IDA Pro Regression

by James Liggett

Hi Robbert, I tried a fresh CVS copy today, and IDA works now. I guess it got fixed. That was fast... :) I wonder if your installers will work now. James On Sun, 2005-08-28 at 12:40 +0100, Robbert Xerox wrote: > Hi, same patch is causing a regression in quite a few > installers; one of them is: > > http://www.winehq.org/hypermail/wine-bugs/2005/08/0206.html > > Hopefully it can be fixed soon :) > > ------------------------------------------------------ > Hi, > A week or so ago I reported some regressions running > IDA pro on wine. > I've done some regression testing and I have found the > patches that were > causing the problems. The first problem I noticed were > the large edit > boxes in the General Registers window in IDA's > debugger. It was caused > by this edit control theming patch: > http://cvs.winehq.org/patch.py?id=19554. > > > > > > ___________________________________________________________ > Yahoo! Messenger - NEW crystal clear PC to PC calling worldwide with voicemail http://uk.messenger.yahoo.com >

Aug. 28, 2005

Re: wined3d - d3d9 regression testing 7_12_2005

by Jesse Allen

On 8/28/05, Ann & Jason Edmeades <us(a)edmeades.me.uk> wrote: > Out of interest, does reversing this patch fix the wc3 fonts - If I recall > correctly if was the glTranslate calls which originally made the wc3 fonts > look correct, and I noticed in one of the patches Oliver changed them. He's > probably right, but just in case its worth a test > > Try changing > glTranslatef(0.9 / This->stateBlock->viewport.Width, -0.9 / > This->stateBlock->viewport.Height, 0); > > to > > glTranslatef(1.0/This->stateBlock->viewport.Width, > -1.0/This->stateBlock->viewport.Height, 0); > > in drawprim.c > > Jason > > Well I tested Warcraft 3 before I got your reply and there is nothing wrong with the fonts currently, so the report may have been wrong. I did went ahead and tried Battlefield again with this change, but they are still blocks. Jesse

Aug. 28, 2005

Re: [resend] atl.DllRegisterServer

by Stefan Leichter

Am Sonntag, 28. August 2005 18:31 schrieb Alexandre Julliard: > Stefan Leichter <Stefan.Leichter(a)camLine.com> writes: > > Hi Alexandre, > > > > anything wrong with this patch ? > > Well, the resource id is 1, so loading it with 0x65 is certainly not > going to work. Were you planning to change the resource too? Hi, looks like i was confused by LoadLibraryEx. I found now that when buildin and native version of a dll are present and nothing for the load order is specified LoadLibraryEx loads the buildin version as long as LOAD_LIBRARY_AS_DATAFILE is not specified. But when LOAD_LIBRARY_AS_DATAFILE is specified it loads the native version. Can this behavoir be change to load the same dll independend of LOAD_LIBRARY_AS_DATAFILE ? Bye Stefan

Aug. 28, 2005

Re: wined3d - d3d9 regression testing 7_12_2005

by Ann & Jason Edmeades

Out of interest, does reversing this patch fix the wc3 fonts - If I recall correctly if was the glTranslate calls which originally made the wc3 fonts look correct, and I noticed in one of the patches Oliver changed them. He's probably right, but just in case its worth a test Try changing glTranslatef(0.9 / This->stateBlock->viewport.Width, -0.9 / This->stateBlock->viewport.Height, 0); to glTranslatef(1.0/This->stateBlock->viewport.Width, -1.0/This->stateBlock->viewport.Height, 0); in drawprim.c Jason

Aug. 28, 2005

Re: winspool: ERROR_INVALID_NAME in GetDefaultPrinter() ?

by Detlef Riekenberg

Am Sonntag, den 28.08.2005, 17:55 +0200 schrieb Stefan Leichter: > i thing the answer is > http://test.winehq.org/data/200406151000/2000_AshleyGordon/ > winspool.drv:info.txt Thanks for your Help. -- By By ... ... Detlef

Aug. 28, 2005

Re: wined3d - d3d9 regression testing 7_12_2005

by Stefan Dösinger

Hi, Just found the old mail, the following might be interesting: > Thanks, I've got the game running how Battlefront looked. Fonts are > messed up, and some rendering problems, but it does run for me. > Battlefront has a crashing problem I know Oliver knows how to fix. Battlefield renders really fine if you disable the vertex shaders in winecfg. The only remaining Direct3D problem are some glitches with the smoke and the explosions. The font troubles don't seem to be D3D related, as some fonts are shown correctly, for example the player names if you look at someone. >From the D3D part it looks better than in cedega: Watter effect are better, Pixel Shaders work nice, more stable(Cedega crashes my fglrx driver under certain conditions). Remaining problems are: The game works only in Desktop mode, only 800x600, the mouse tends to leave the window. The sound doesn't work, and of course the obvious font problem. And last, in the loading picture the Red and the Blue channel seem switched, which gives the pictures some modern art touch ;-) Congrats to Oliver. Stefan

Aug. 28, 2005

Re: wined3d - d3d9 regression testing 7_12_2005

by Jesse Allen

On 8/28/05, Stefan Dösinger <stefandoesinger(a)gmx.at> wrote: > Hi, > Just found the old mail, the following might be interesting: > > > Thanks, I've got the game running how Battlefront looked. Fonts are > > messed up, and some rendering problems, but it does run for me. > > Battlefront has a crashing problem I know Oliver knows how to fix. > Battlefield renders really fine if you disable the vertex shaders in winecfg. > The only remaining Direct3D problem are some glitches with the smoke and the > explosions. The font troubles don't seem to be D3D related, as some fonts are > shown correctly, for example the player names if you look at someone. > > From the D3D part it looks better than in cedega: Watter effect are better, > Pixel Shaders work nice, more stable(Cedega crashes my fglrx driver under > certain conditions). > > Remaining problems are: The game works only in Desktop mode, only 800x600, the > mouse tends to leave the window. The sound doesn't work, and of course the > obvious font problem. And last, in the loading picture the Red and the Blue > channel seem switched, which gives the pictures some modern art touch ;-) > > Congrats to Oliver. > > Stefan > Well, I do have vertex shaders on. The problem I'm having with battlefield is that the screen moves 25% of the screen off the top and left sides and cutting off 25% of the bottom and right (black) when I get to the loading screen. If I can hit the buttons to enter the game, then it does it for 25% more of all the sides, and makes the game nearly unplayable. It's been reported to me that the fonts are now messed up in Warcraft 3 in D3D as well. I don't believe this was the case before. Jesse

Aug. 28, 2005