wine-devel

wine-devel@winehq.org

2 participants
84470 discussions

Re: Janitorial: Get rid of W->A calls for shlexec [RESEND]
by Marcelo Duarte 15 Jan '04

15 Jan '04

Why my patch was not applied? If it will be because it conflicts with the patches of the ROS, can leave that in the next weekend I intend to make this, thus diminishes the work of them. But necessary to know if my patch it goes to be accepted, if I do not go to be losing my time. Thank you. Em Sáb 10 Jan 2004 04:51, Marcelo Duarte escreveu: > Updated with the lastest cvs. > > Changelog: > Marcelo Duarte <wine-devel(a)bol.com.br> > -Janitorial: Get rid of W->A calls for shlexec > -Implementation of FindExecutableW -- Marcelo Duarte

1 0

Re: Solaris specific configuration
by Alexandre Julliard 15 Jan '04

15 Jan '04

Robert Lunnon <bobl(a)optushome.com.au> writes: > Changelog > Autodetection of XFREE86 as required for Solaris. This should be done in configure, assuming it is really necessary. Why can't we use the standard Xlib? -- Alexandre Julliard julliard(a)winehq.com

2 1

Re: ifenum.c mtu acquisition - Solaris
by Dimitrie O. Paun 15 Jan '04

15 Jan '04

On January 13, 2004 09:46 pm, Robert Lunnon wrote: > +#if !defined sun > *mtu = ifr.ifr_mtu; > +#else > + *mtu=ifr.ifr_metric; > + #endif The #endif is not properly indented, any special reason? -- Dimi.

2 1

comctl32/imagelist -> ImageList_Remove problem
by hatky 15 Jan '04

15 Jan '04

I run a free program call The All-seeing Eye, available for free at: http://www.udpsoft.com/eye2/index.html And run into a few errors like this: err:imagelist:ImageList_Remove index out of range! 0 ImageList_Remove gets( HIMAGELIST himl, int i) line 2040 of imagelist.c says: if ((i < -1) || (i >= himl->cCurImage)) { ERR("index out of range! %d\n", i); return FALSE; } But since "When an image is removed, the indexes of the remaining images are adjusted so that the ...." I assume most call do not include an index but only the handle as the case with this program from the trace I checked it sends 0 as the i and a true handle in himl and it makes since, since it first calls ImageList_Create to add images and ImageList_Create returns "Handle to the created image list" and not the place (remember the place changes anyway....) So..... I assume that in the case of the i = 0 the procedure should locate the i itself from the handle, am I right? getting close to his first patch :), Hatky. __________________________________ Do you Yahoo!? Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes http://hotjobs.sweepstakes.yahoo.com/signingbonus

2 1

Will function advapi32.dll.RegOpenUserClassesRoot will be implemented?
by MediaHost (TM) 14 Jan '04

14 Jan '04

Hi, Is there a chance, that function advapi32.dll.RegOpenUserClassesRoot will be implemented? As I can see, most up 2 date software of Micro$oft (Explorer etc.) is using this function and can not run on a W2K environment. Any suggestions? Regards Signer: Eddy Nigg Company: StartCom Group at http://www.startcom.org MediaHostT at http://www.mediahost.org --- StartCom Ltd. http://www.startcom.org Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.560 / Virus Database: 352 - Release Date: 1/10/2004

3 3

strange warning message when buildint current cvs
by Ivan Leo Murray-Smith 14 Jan '04

14 Jan '04

With current cvs, I get this strange warning message make[2]: Entering directory `/home/ivan/Development/Wine/CVS/wine/programs/winetest' cp ../../dlls/advapi32/tests/advapi32_test.exe.so advapi32_test.exe.so && strip -s advapi32_test.exe.so cp ../../dlls/gdi/tests/gdi32_test.exe.so gdi32_test.exe.so && strip -s gdi32_test.exe.so cp ../../dlls/kernel/tests/kernel32_test.exe.so kernel32_test.exe.so && strip -s kernel32_test.exe.so cp ../../dlls/ntdll/tests/ntdll_test.exe.so ntdll_test.exe.so && strip -s ntdll_test.exe.so cp ../../dlls/user/tests/user32_test.exe.so user32_test.exe.so && strip -s user32_test.exe.so cp ../../dlls/winmm/tests/winmm_test.exe.so winmm_test.exe.so && strip -s winmm_test.exe.so cp ../../dlls/winspool/tests/winspool.drv_test.exe.so winspool.drv_test.exe.so && strip -s winspool.drv_test.exe.so LD_LIBRARY_PATH="../../libs/unicode:$LD_LIBRARY_PATH" ../../tools/wrc/wrc --nostdinc -I. -I. -I../../include -I../../include -fowinetest.res winetest.rc ../../tools/winebuild/winebuild -D_REENTRANT -fPIC -o winetest.exe.spec.c --exe winetest.exe --exe-mode gui winetest.res main.o send.o util.o winetest.exe.dbg.o -L../../dlls -luser32 -lwsock32 gcc -c -I. -I. -I../../include -I../../include -D_REENTRANT -fPIC -Wall -pipe -mpreferred-stack-boundary=2 -fno-strict-aliasing -gstabs+ -Wpointer-arith -g -O2 -o winetest.exe.spec.o winetest.exe.spec.c {standard input}: Assembler messages: {standard input}:856275: Warning: .stabs: description field '1a385' too big, try a different debug format {standard input}:856278: Warning: .stabs: description field '1a38c' too big, try a different debug format {standard input}:856281: Warning: .stabn: description field '1a38c' too big, try a different debug format {standard input}:856287: Warning: .stabn: description field '1a38f' too big, try a different debug format {standard input}:856291: Warning: .stabn: description field '1a38c' too big, try a different debug format {standard input}:856299: Warning: .stabn: description field '1a38e' too big, try a different debug format {standard input}:856302: Warning: .stabn: description field '1a38f' too big, try a different debug format {standard input}:856305: Warning: .stabn: description field '1a38e' too big, try a different debug format {standard input}:856308: Warning: .stabn: description field '1a390' too big, try a different debug format {standard input}:856316: Warning: .stabn: description field '1a393' too big, try a different debug format {standard input}:856321: Warning: .stabn: description field '1a397' too big, try a different debug format {standard input}:856324: Warning: .stabn: description field '1a398' too big, try a different debug format {standard input}:856331: Warning: .stabn: description field '1a391' too big, try a different debug format {standard input}:856344: Warning: .stabn: description field '1a392' too big, try a different debug format {standard input}:856349: Warning: .stabn: description field '1a398' too big, try a different debug format {standard input}:856357: Warning: .stabn: description field '1a39a' too big, try a different debug format {standard input}:856378: Warning: .stabn: description field '1a39b' too big, try a different debug format {standard input}:856383: Warning: .stabn: description field '1a39c' too big, try a different debug format {standard input}:856389: Warning: .stabn: description field '1a39d' too big, try a different debug format {standard input}:856401: Warning: .stabn: description field '1a39e' too big, try a different debug format {standard input}:856413: Warning: .stabn: description field '1a39f' too big, try a different debug format {standard input}:856416: Warning: .stabn: description field '1a3a0' too big, try a different debug format {standard input}:856420: Warning: .stabn: description field '1a3a1' too big, try a different debug format {standard input}:856428: Warning: .stabn: description field '1a394' too big, try a different debug format {standard input}:856442: Warning: .stabs: description field '1a38d' too big, try a different debug format {standard input}:856443: Warning: .stabs: description field '1a38e' too big, try a different debug format {standard input}:856444: Warning: .stabs: description field '1a38f' too big, try a different debug format {standard input}:856445: Warning: .stabs: description field '1a38f' too big, try a different debug format {standard input}:856446: Warning: .stabs: description field '1a38f' too big, try a different debug format {standard input}:856509: Warning: .stabs: description field '1a3f3' too big, try a different debug format {standard input}:856513: Warning: .stabn: description field '1a3f3' too big, try a different debug format {standard input}:856522: Warning: .stabn: description field '1a3f5' too big, try a different debug format {standard input}:856530: Warning: .stabn: description field '1a3f6' too big, try a different debug format {standard input}:856548: Warning: .stabs: description field '1168a' too big, try a different debug format {standard input}:856549: Warning: .stabs: description field '12078' too big, try a different debug format {standard input}:856550: Warning: .stabs: description field '12fff' too big, try a different debug format {standard input}:856551: Warning: .stabs: description field '13f10' too big, try a different debug format {standard input}:856552: Warning: .stabs: description field '148d9' too big, try a different debug format {standard input}:856553: Warning: .stabs: description field '17277' too big, try a different debug format {standard input}:856554: Warning: .stabs: description field '181cf' too big, try a different debug format {standard input}:856555: Warning: .stabs: description field '18d39' too big, try a different debug format {standard input}:856556: Warning: .stabs: description field '19709' too big, try a different debug format {standard input}:856557: Warning: .stabs: description field '1a290' too big, try a different debug format {standard input}:856558: Warning: .stabs: description field '1a2a8' too big, try a different debug format {standard input}:856559: Warning: .stabs: description field '1a2f2' too big, try a different debug format {standard input}:856560: Warning: .stabs: description field '1a3cf' too big, try a different debug format gcc -shared -Wl,-Bsymbolic,-z,defs,-init,__wine_spec_init,-fini,__wine_spec_fini winetest.exe.spec.o main.o send.o util.o winetest.exe.dbg.o -o winetest.exe.so -L../../libs/wine -lwine -L../../libs/port -lwine_port -lm -lc make[2]: Leaving directory `/home/ivan/Development/Wine/CVS/wine/programs/winetest' make[2]: Entering directory `/home/ivan/Development/Wine/CVS/wine/programs/winevdm' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/home/ivan/Development/Wine/CVS/wine/programs/winevdm' make[2]: Entering directory `/home/ivan/Development/Wine/CVS/wine/programs/winhelp' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/home/ivan/Development/Wine/CVS/wine/programs/winhelp' make[2]: Entering directory `/home/ivan/Development/Wine/CVS/wine/programs/winver' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/home/ivan/Development/Wine/CVS/wine/programs/winver' make[1]: Leaving directory `/home/ivan/Development/Wine/CVS/wine/programs' make[1]: Entering directory `/home/ivan/Development/Wine/CVS/wine/server' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/home/ivan/Development/Wine/CVS/wine/server' Wine build complete. I've tried make distclean and I still get it. I'm using gcc 3.3.1-2mdk, does this classify as something that should be fixed? Ivan.

2 1

Re: PATCH: Port Tim Ferguson's ICCVID codec to Wine
by Dmitry Timoshkov 14 Jan '04

14 Jan '04

"Mike McCormack" <mike(a)codeweavers.com> wrote: > ChangeLog: > Tim Ferguson <Tim.Ferguson(a)infotech.monash.edu.au> > Mike McCormack <mike(a)codeweavers.com> > * Port Tim Ferguson's ICCVID codec to Wine Mike, could you put the iccvid sources at the same place as msrle32 (dlls/msvideo) and resend the patch? -- Dmitry.

4 4

Shell32 Patch 1.1
by Steven Edwards 14 Jan '04

14 Jan '04

This patch replaces the prior patch. The ReactOS changelog wasnt very good and Martin pointed out that I missed the spec file. Changelog: "Martin Fuchs" <martin-fuchs(a)gmx.net> Implement RestartDialog and RestartDialogEx __________________________________ Do you Yahoo!? Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes http://hotjobs.sweepstakes.yahoo.com/signingbonus

1 0

Re: More Vacation backlog
by Hans Leidekker 14 Jan '04

14 Jan '04

On Tuesday 13 January 2004 23:57, Uwe Bonnes wrote: > +HANDLE DEVICE_Open( LPCWSTR filenameW, DWORD access, DWORD attributes, LPSECURITY_ATTRIBUTES sa ) > { > const struct VxDInfo *info; > char filename[MAX_PATH]; > @@ -283,7 +283,7 @@ > > for (info = VxDList; info->name; info++) > if (!strncasecmp( info->name, filename, strlen(info->name) )) > - return FILE_CreateDevice( info->id | 0x10000, access, sa ); > + return FILE_CreateDevice( info->id | 0x10000, access, access, sa ); ^^^^^^ I think you want to pass 'attributes' here, right? -Hans

1 0

listview and LVS_OWNERDATA problems update
by Dan Kegel 14 Jan '04

14 Jan '04

I just revisited http://bugs.winehq.org/show_bug.cgi?id=1268 and found that things are improved, but not fully working; there is corruption to the left of column 1 in the demo app. I have not yet rechecked http://bugs.winehq.org/show_bug.cgi?id=1404 to see how well that demo app is doing. - Dan

1 0

wwn #110 ??
by Tom 14 Jan '04

14 Jan '04

If I look at WWN #110 on winehq.org I get this http://www.winehq.org/?issue=110 If I look at 110 at : http://kt.zork.net/wine/wn20011212_110.html it is almost toatly different!! Do I need to start reading both sites each week? And I guess ill send a patch to fix this as there is alot of good crap here to read! :) Tom

1 0

Oleaut32 tests fail
by Sylvain Petreolle 14 Jan '04

14 Jan '04

Running the oleaut32 tests shows that vartype and vartest are failing. The 25 tests that fail are returning DISP_E_TYPEMISMATCH (0x80020005) Has someone an idea about these ? vartest.c:2653:======== Testing different VARTYPES ======== fixme:ole:VarParseNumFromStr dwInFlags & NUMPRS_HEX_OCT not yet implemented! vartest.c:2680: Test failed: 14: vt 83, return value 80020005, expected was 0 ===== Sylvain Petreolle (spetreolle_at_users_dot_sourceforge_dot_net) ICQ #170597259 Say NO to software patents Dites NON aux brevets logiciels "What if tomorrow the War could be over ?" Morpheus, in "Reloaded". _________________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com

1 0

Re: Re: slight trouble running winetests under windows
by chmorgan＠charter.net 14 Jan '04

14 Jan '04

Ahh yes, this appears to be the issue. If I go to "project settings->link->object/library modules" and add "uuid.lib" to the list then the test compiles without many other issues. Shouldn't the script be adding this to the .dsp/.dsw? I'm having great troubles compiling the test against vs6 header files as well, should I upgrade to the latest platform sdk? The wine headers work pretty well except for errors from the compiler about not being able to convert __uint64 to double. Chris > > From: Hans Leidekker <hans(a)it.vu.nl> > Date: 2004/01/13 Tue AM 05:20:29 EST > To: wine-devel <wine-devel(a)winehq.com> > CC: Chris Morgan <cmorgan(a)alum.WPI.EDU> > Subject: Re: slight trouble running winetests under windows > > On Tuesday 13 January 2004 05:47, Chris Morgan wrote: > > > I'm trying to get some of the wine tests compiling and running under > > windows, oleaut32 test specifically. I've got the project file built and > > everything opens fine under visual studio 6. The only issue is that during > > linking of the oleaut32 tests _IID_IFont is undefined. Oddly enough if I > > I get these linking errors too when compiling with MinGW. I solve > these by manually adding -luuid. The dsound test needs -luuid and > -ldxguid to link. There has been some discussion in the past as to > how to solve this. I proposed a number of changes to Wine's build > system to fix this but they were rejected. > > Let's see if I can sum up the issues. In Wine uuids are put in > a lib called libwine_uuid. It's called like that because a > libuuid already exists. Second thing is that in MinGW and MSVC > there are two separate libraries with uuids, uuid and dxguid, > whereas in Wine they're all in one. > > -Hans > >

3 2

Re: Implement LockWindowUpdate [take 2]
by Alexandre Julliard 14 Jan '04

14 Jan '04

Mike Hearn <mike(a)theoretic.com> writes: > The other reason it might have bounced is if we're not allowed to extend > WND, though as it's purely internal and not accessible from the APIs that > should be OK? I'm not sure how to do this otherwise without exporting the > currently locked window variable from USER to X11DRV which probably breaks > dll separation. Either that, or adding a new driver procedure. Extending the WND structure is OK (though it doesn't seem necessary in that case), but accessing it from x11drv is a violation of dll separation. We still do that in a number of places but they will have to be fixed, so we probably shouldn't add new ones. -- Alexandre Julliard julliard(a)winehq.com

2 2

Cdrom driver
by Robert Lunnon 13 Jan '04

13 Jan '04

I have just finished embelishing the cdrom driver to support solaris but I have nothing to test it against. Can anyone recommend a good test program for excercising CDROM ioctls ? Thanks Bob

2 1

Re: Solaris compile time fixes for CVS wine
by Dimitrie O. Paun 13 Jan '04

13 Jan '04

On January 8, 2004 01:22 am, Robert Lunnon wrote: > Here are a buch of Solais compatibility patches for wine (Some but not all > of them). Within the enclosed tarball the diffs are structured according to > the wine cvs tree. There is a readme file accompanying each diff to explain > what the change is. Please break the archive into one patch per message, not compressed (preferably inlined). Here are a few pointers on how to send patches: http://www.winehq.org/site/sending_patches BTW, what's the status of building Wine under Solaris? What architecture (i386, etc) are you using? -- Dimi.

4 3

Re: [Bug 521] WINE removes trailing backslash in GetFullPathNameA/W in dos_fs.c.
by Eric Pouech 13 Jan '04

13 Jan '04

Mike McCormack a écrit : > > This closes bug 521, and removes a couple of wine_todos from the > regression test for pathes. The test for setting "lastpart" in both > GetFullPathNameA/W was wrong (would always pass). for the record, I also sent a patch regarding (among other things) this issue, which also has never been applied. I don't know Alexandre's state on this. A+

2 3

WWN Links are busted
by Tom 13 Jan '04

13 Jan '04

Hi, If you try to go to a WWN article from the status page's they don't work. example : Wine's fundamental architecture #154 = http://www.winehq.com/site/status_wine?issue=154#Kernel%20Module%20/%20Shar… the current link is: <a href="?issue=154#Kernel%20Module%20/%20Shared%20Memory%20Revisited">#154</a></td> when I think it should be: <a href="{$root}/site/?issue=154#Kernel%20Module%20/%20Shared%20Memory%20Revisited">#154</a></td> Jeremey N is this correct? If so I can fix all the links in the next day or so.. Tom

2 1

Re: WWN Links are busted
by Brian Vincent (C) 13 Jan '04

13 Jan '04

> the current link is: > <a > href="?issue=154#Kernel%20Module%20/%20Shared%20Memory%20Revisited">#154</a> </td> I think it should be: href="/?issue=154#Kernel%20Module%20/%20Shared%20Memory%20Revisited" sed -e "s/href=\"\?/href=\"\/\?/g" --------------- Brian Vincent Copper Mountain Telecom vincentb(a)coppercolorado.com

1 0

Re: shell32 patches to be usable by ReactOS Explorer
by Alexandre Julliard 13 Jan '04

13 Jan '04

"Martin Fuchs" <martin-fuchs(a)gmx.net> writes: > This was no joke. If you say, you would accept such as reformating patch, > I can easyly create one that eliminates all tab-characters, and generates > nice and uniform indented code. > This will make it a bit easier to create the small self-contained patches > you want to see instead of the big one. As additional bonus you will get > a very better formated shell32 code base. There's no reason to reformat all of shell32. If a given function is messed up you can fix it (in a separate patch), but otherwise it doesn't really matter if all functions don't use the exact same style. -- Alexandre Julliard julliard(a)winehq.com

2 1

stray file
by Hans Leidekker 13 Jan '04

13 Jan '04

Hi, There's a stray file, dlls/checklink.c, in Wine CVS with these contents: int main(void) { return 0; } It must be a leftover from a configure run. I suspected my own tree but but it came back after I removed it and did a cvs update. -Hans

4 4

Re: uxtheme: lots of infrastructure
by Alexandre Julliard 13 Jan '04

13 Jan '04

Kevin Koltzau <kevin(a)plop.org> writes: > This is a ton of infrastructure for my future patches, and a full > implementation of GetThemeDocumentationProperty which I primarilly > used to test my INI file processing, and its now possible to set the > current theme through the API..not that its much use to do that yet The part about storing the string maps as resources seems unnecessarily complicated and inefficient. Why can't you store an array directly in the code? -- Alexandre Julliard julliard(a)winehq.com

2 4

[Janitorial] Remove CopyMetaFileW->A call
by Vincent Béron 13 Jan '04

13 Jan '04

Indentation in CopyMetaFileW is a bit inconsistent (there are some tabs which I left since I didn't touch those lines). Should I redo my patch to get rid of them (adds some noise to the patch), keep them in a separate patch (limited to this very function) or leave it as is? Also, should I change MF_CreateMetaHeaderDisk to accept a LPCWSTR, even though it then needs to convert it back to Ascii, or is the proposed way sufficient? Changelog: Removed a W->A cross-call (CopyMetaFileW->CopyMetaFileA). Vincent

1 0

Re: Implemention of LockWindowUpdate
by Mike Hearn 13 Jan '04

13 Jan '04

On Tue, 13 Jan 2004 00:10:20 +0000, Mike Hearn wrote: > This patch makes the halflife menu screen look a bit better, with less > flashing. Unfortunately it also makes it feel a bit slower, but I think > that's just an optical illusion caused by less screen activity. The > bottleneck is elsewhere. Just had a hunch, and yes, switching off XRender and antialiasing speeds things up nicely. I guess I should yell at keithp or something.... :)

1 0

Re: wine/ windows/scroll.c include/user.h dlls/x11 ...
by Dimitrie O. Paun 12 Jan '04

12 Jan '04

On Mon, 12 Jan 2004, Alexandre Julliard wrote: > Log message: > ScrollDC doesn't need to be in the graphics driver. Yay! (I submitted a similar patch some time ago, but you didn't like the {Start,End}GraphicsExposures functions. I still think they are decent GUI abstractions :)): http://www.winehq.com/hypermail/wine-patches/2002/09/0196.html Speaking of these things, I also don't think the driver should know about the caret. I see no need for the USER driver to know anything about the caret, we can just always implement it ourselves, no? http://www.winehq.com/hypermail/wine-patches/2002/09/0174.html I think there is a bug in the above patch (IIRC, I used to get some freezing in certain situations), but the idea still stands. -- Dimi.

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-devel