- Wine-Devel - list.winehq.org

winetest.exe on wine fails
by Robert Reif June 5, 2004

June 5, 2004

When I try to run winetest.exe on wine, it fails with an error dialog: "Can't redirect stdout." and prints: fixme:msvcrt:_dup2 (od=3, nd=1): stub to the screen. Shouldn't we be able to run wintest.exe on wine?

1 0

Microsoft Visio 2000
by James Courtier-Dutton June 5, 2004

June 5, 2004

Has anyone managed to get Microsoft Visio 2000 working on a native wine install. I.E. No Pre installed Windows partition. If so, how? If not, I will open a bug and post the details of where the install fails. Cheers James

1 0

Re: [tests] disable winspool tests if we don't have a default printer
by Dimitrie O. Paun June 5, 2004

June 5, 2004

On Fri, Jun 04, 2004 at 08:26:49AM +0200, Andreas Mohr wrote: > Why not be more verbose about that? Because those people will not see the warning anyway I'm afraid. Most run in non-interactive mode through winrash, others through winetest. The most we can do is leave the error in, and bug people into fixing their setup, but I'm not sure this is practical. Maybe we need a special sort of failure more for these sort of things, so we can separate them in the HTML output. -- Dimi.

2 2

segfault at startup -- race condition
by terra＠gnome.org June 5, 2004

June 5, 2004

Recall that "./wine" usually, but not always, segfaults for me. I have tracked my race condition down to SHELL_LoadRegistry where the successful runs exit via the first return ("someone else already loaded the registry") whereas the segfaulting runs go on. Ideas? Morten

1 0

Re: Tab control TCM_SETITEMEXTRA (bugzilla #1046)
by Alexandre Julliard June 4, 2004

June 4, 2004

Jon Griffiths <jon_p_griffiths(a)yahoo.com> writes: > @@ -2557,8 +2562,10 @@ > infoPtr->items[iItem].iImage = pti->iImage; > > if (pti->mask & TCIF_PARAM) > - infoPtr->items[iItem].lParam = pti->lParam; > - > + memcpy(&infoPtr->items[iItem].lParam, &pti->lParam, infoPtr->cbInfo); > + else > + memset(&infoPtr->items[iItem].lParam, 0, infoPtr->cbInfo); That doesn't look right at all, lParam is not at the end of the structure. And the variable-size info should really be a byte array or something similar, not an LPARAM. -- Alexandre Julliard julliard(a)winehq.org

3 4

segfault at startup
by terra＠gnome.org June 4, 2004

June 4, 2004

It looks like it is blowing the stack. Ideas? Morten gdb loader/wine-pthread ...] (gdb) where #0 0x4010afdc in _int_malloc () from /lib/libc.so.6 #1 0x4010a18c in malloc () from /lib/libc.so.6 #2 0x404adb72 in _xmalloc (size=25) at ../../misc/registry.c:95 #3 0x404aeb24 in _w95_dump_dke (key_name=0x4055470c "", creg=0x405c0000, rgkn=0x405c0020, dke=0x406444d4, f=0x77f04f60, level=0) at ../../misc/registry.c:717 #4 0x404aeba7 in _w95_dump_dke (key_name=0x4055470c "", creg=0x405c0000, rgkn=0x405c0020, dke=0x4064449c, f=0x77f04f60, level=0) at ../../misc/registry.c:725 #5 0x404aeba7 in _w95_dump_dke (key_name=0x4055470c "", creg=0x405c0000, rgkn=0x405c0020, dke=0x40644464, f=0x77f04f60, level=0) at ../../misc/registry.c:725 #6 0x404aeba7 in _w95_dump_dke (key_name=0x4055470c "", creg=0x405c0000, rgkn=0x405c0020, dke=0x4064442c, f=0x77f04f60, level=0) at ../../misc/registry.c:725 [...] (gdb) p *dkh $1 = {nextkeyoff = 86, nrLS = 188, nrMS = 75, bytesused = 86, keynamelen = 23, values = 1, xx1 = 0, name = "I"} (gdb) p *dke $2 = {x1 = 0, hash = 0, x3 = 0, prevlvl = 0, nextsub = 1, next = 0, nrLS = 0, nrMS = 0} Note dke->next==0.

3 3

Re: Listview ignores the user specified image state index
by Dimitrie O. Paun June 4, 2004

June 4, 2004

On Thu, Jun 03, 2004 at 02:12:49PM -0700, Krishna Murthy wrote: > While inserting the item in ListView control in wine( in function > ISTVIEW_InsertItemT() ), the state image index is overwritten with zeros. > After copying the LVITEM structure to newly created item in > LISTVIEW_InsertItemT(), a statement is unnecessarily masking the state with > LVIS_STATEIMAGEMASK by using ~ operator (item.state &= ~LVIS_STATEIMAGEMASK; > ). This statement is making the bits 12 through 15 overwrite with 0's by > replacing original state image index. Odd, I've added that, but I can not understand why. If anything, it might be a typo, as I can't see why I would want to nuke the state image, but I also can not remember what I wanted to remove. So the patch is OK, I'll think some more tonight what, if anything, I wanted to remove from the state. -- Dimi.

1 1

Re: Don't send messages when doing a ShowWindow(SW_HIDE) on aninvisible window
by Dmitry Timoshkov June 4, 2004

June 4, 2004

"Mike Hearn" <mh(a)codeweavers.com> wrote: > OK, I sent a fixed patch to wine-patches. I thought ShowWindow/SWP might > do extra things we didn't want to skip, but if the Windows Internals > book says this is what Windows does then we can do that too. On Windows > it returns FALSE if you do that anyway, so it's probably right. FALSE returned by ShowWindow doesn't mean a failure. ShowWindow returns previous visibility status, and FALSE means that a window was invisible. > By the way how much is "Windows Internals"? Is it still sold? I should > look into getting a copy. I bought russian translation of the book in 1995. Original book was published in 1993 by Addison-Wesley, ISBN 0-201-62217-3. -- Dmitry.

1 0

Request for winetesting volunteers
by Chris Morgan June 3, 2004

June 3, 2004

Thanks to Brian Vincent, Paul Millar, Dimi Paun, Ferenc Wagner and Kevin Koltzau the automated winetest suite is ready for more widespread testing. Kevin and Paul build winetests each night if there were cvs commits since the last time the tests were built. The winetests are published to a script on winehq that Brian and Dimi wrote. The winrash service that I wrote sends its current state to the service and receives a script to process that may direct it to check in later, download a winetest and run it or upgrade itself. Thanks to Ferenc the winetest results are sent back to winehq and can be accessed via http://test.winehq.org/data/ Pretty formatting of the results is coming soon ;-) We need volunteers that are willing to particpate in the winetesting process by running the winrash service on their computers. The winrash installer can be downloaded from: http://prdownloads.sourceforge.net/winrash/winrash-0007-chris-msvc.exe?down… You can find out more about winrash at http://winrash.sf.net The installer will install winrash as a service and run Wine tests as required. It is IMPORTANT that you set the client id correctly. Please use your first and last name WITHOUT spaces, like JohnSmith. Using the default client id will cause your winetest results to be ignored. The service is smart enough to autoupgrade as new versions are released. To uninstall just go to the Add/Remove programs and click 'remove' as you do for many windows programs. There is the ability to restrict the times when winrash runs winetests but this requires manually adding some keys to the registry. I haven't finished testing this feature but if someone wants it I can see about getting it polished up and in a release early this coming week. We currently need testers for the whole range of windows versions, win95/98/me, nt3/4, win2k, xp and 2003. Please reply if you want to help out so that we know what kind of coverage we can expect. The more the merrier, so please sign up even if others have done so for your version of Windows. Chris

3 5

Re: Re: Request for winetesting volunteers
by chmorgan＠charter.net June 3, 2004

June 3, 2004

I think we should switch the winrash id field from the users first and last name to an email address we can contact the user at. There are a few odd errors that I'd like to get more information about but its difficult to contact people via their first and last name. Any objections to this? Winetest able to handle an email address as the username field? Chris > > From: "Dimitrie O. Paun" <dpaun(a)rogers.com> > Date: 2004/06/03 Thu AM 01:30:05 EDT > To: Ferenc Wagner <wferi(a)afavant.elte.hu> > CC: wine-devel(a)winehq.org > Subject: Re: Request for winetesting volunteers > > On Sat, May 29, 2004 at 09:22:02AM +0200, Ferenc Wagner wrote: > > What's missing, what should be easier? > > Now that you're asking: in the reports, I don't quite like > that a single report for Win95 is listed as OSR2 in the > main summary, but then it switches to Win95(n) when we have > more than one. Similarly for Win98. This is very confusing. > > For example, after the first submitted tests, the main > summary header read: > > OSR2 SE ME .... > > I wasn't even sure what SE was. Anyway, I think the header > should remain immutable: > > Win95 Win98 ME NT3 NT4 2000 XP 2003 > > -- > Dimi. > > >

3 3