January 2004 - Wine-Devel - list.winehq.org

comctl32/imagelist -> ImageList_Remove problem
by hatky Jan. 15, 2004

Jan. 15, 2004

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) Jan. 14, 2004

Jan. 14, 2004

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 Jan. 14, 2004

Jan. 14, 2004

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 Jan. 14, 2004

Jan. 14, 2004

"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 Jan. 14, 2004

Jan. 14, 2004

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 Jan. 14, 2004

Jan. 14, 2004

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 Jan. 14, 2004

Jan. 14, 2004

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 Jan. 14, 2004

Jan. 14, 2004

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 Jan. 14, 2004

Jan. 14, 2004

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 Jan. 14, 2004

Jan. 14, 2004

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