wine-devel

wine-devel@winehq.org

10 participants
84459 discussions

Direct3D8 - OpenGL header problem
by Thomas Brix Larsen 11 Jan '04

11 Jan '04

Hi list, just upgraded to 2.6.0 and the NVIDIA driver from minion.de and now I get this error when compiling wine: directx.c: In function `IDirect3D8Impl_GetDeviceCaps': directx.c:639: `GL_MAX_VERTEX_UNITS_ARB' undeclared (first use in this function) My X11/include/GL/ headers date, 2001-2002. Greetings, --Thomas _________________ My worst enemy gave me a copy of Windows...

3 2

Re: shell32 patches to be usable by ReactOS Explorer
by Martin Fuchs 11 Jan '04

11 Jan '04

Sorry, I forgot to include the new file "shlcpanel.c" into the shell32 patch mail. Changelog: - Implementation of control panel folder in shgell namespace -- Martin Fuchs martin-fuchs(a)gmx.net

1 0

Build fails for current CVS update
by Sami Aario 11 Jan '04

11 Jan '04

Hi, Building with tools/wineinstall fails with the latest CVS update on my system with the following: gcc -c -I. -I. -I../../include -I../../include -I/usr/X11R6/include -D__WINE SRC__ -D_REENTRANT -fPIC -Wall -pipe -mpreferred-stack-boundary=2 -fno-stri ct-aliasing -gstabs+ -Wpointer-arith -g -O2 -o ddraw.spec.o ddraw.spec.c {standard input}: Assembler messages: {standard input}:654: Error: no such instruction: `yes "ddraw.dll"' {standard input}:655: Error: no such instruction: `yes "DDHAL32_VidMemAlloc"' {standard input}:656: Error: no such instruction: `yes "DDHAL32_VidMemFree"' {standard input}:657: Error: no such instruction: `yes "DDInternalLock"' and so on, lots more of the same. Anyone else getting these?

3 4

Re: bogus patch to bind() dlls/winsock/socket.c (request removal)
by Mike Hearn 11 Jan '04

11 Jan '04

That looks familiar. In fact, the TRACE was originally a FIXME but it caused so much spew with so many apps I changed it. I couldn't see exactly what needed to be fixed given the contents of the message - it seems to be simply informing us of progress, but it's a possibility somebody knew this wasn't correct. On Sat, 10 Jan 2004 17:09:52 -0600, Jeremy White wrote: > Index: dlls/winsock/socket.c > =================================================================== > RCS file: /home/wine/wine/dlls/winsock/socket.c,v > retrieving revision 1.144 > diff -u -r1.144 socket.c > --- dlls/winsock/socket.c 2 Jan 2004 20:12:00 -0000 1.144 > +++ dlls/winsock/socket.c 10 Jan 2004 22:56:57 -0000 > @@ -1302,10 +1302,6 @@ > else > { > int on = 1; > - /* The game GrandPrixLegends binds more than one time, > but does > - * not do a SO_REUSEADDR - Stevens says this is ok */ > - TRACE( "Setting WS_SO_REUSEADDR on socket before we > bind it\n"); > - WS_setsockopt( s, WS_SOL_SOCKET, WS_SO_REUSEADDR, > (char*)&on, sizeof(on) ); > > if (bind(fd, uaddr, uaddrlen) < 0) > {

2 1

bogus patch to bind() dlls/winsock/socket.c (request removal)
by Jeremy Shaw 10 Jan '04

10 Jan '04

As a result of this patch (which is currently applied in cvs head): http://www.winehq.com/hypermail/wine-patches/2002/12/0009.html WS_bind() currently does this before every call to bind(): WS_setsockopt( s, WS_SOL_SOCKET, WS_SO_REUSEADDR, (char*)&on, sizeof(on) ); Basically, it sets SO_REUSEADDR for every call to WS_bind(). I can't imagine this is the correct thing to do. According to MSDN, bind() should fail unless the program has explicitly set SO_REUSEADDR. See Error code WSAEADDRINUSE at: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/winsock/wi… I found that this patch causes major problems with the xten sipphone client. The xten client does not explicitly set SO_REUSEADDR and depends on bind() failing if it tries to bind to the same local address/port twice. When the sipphone client needs a socket, it starts at port 8000, and calls bind() on successive ports until bind() returns success. So normally, if the program is already using port 8000, then bind() will fail and will try port 8001. However, with the above patch in place, bind() always works. So then the sipphone client will be using port 8000 twice, which the program is not designed to handle. If I remove the call to WS_setsockopt(), the xten sipphone client works correctly. I am proposing that the portion of the patch applied to WS_bind() be removed unless someone has a convincing arguement that the patch is actually valid. Jeremy Shaw.

2 1

WWN broken
by Brian Vincent (C) 10 Jan '04

10 Jan '04

> We scan the XMl with tidy before posting. What is odd is that tidy > reports the XML is valid, but yet PHP's XML parser barfs on it. Whatever > the case, I just patched it, so it should be fixed online soon. Whoops. Sorry about that. I was running out the door when I put it up. I did run it through tidy, but tidy kind of sucks. The only way to really catch things is to run it through xmllint. But xmllint has a terrible interface for finding malformed problems.. hence tidy. Thanks for fixing that. Also, if anyone is bored and wants to do something easy, it might be nice to change all references in the WWN issues from winehq.com to winehq.org. I've just recently switched over to trying to be consistent on the .org thing. There's about 200 issues that could be run through sed. --------------- Brian Vincent Copper Mountain Telecom vincentb(a)coppercolorado.com

2 1

Re: dsound global variable use reduction
by Eric Pouech 10 Jan '04

10 Jan '04

Robert Reif a écrit : > Reduce the use of the dsound global variable by > passing address to functions. This is in preparation > of supporting multiple DirectSound devices. We can't > remove all uses because an mmtimer callback can be > called even after the timer is killed. Windows has an > mmtimer flag that prevents this but wine doesn't > implement it. Could you be more specific on this one ? timeKillEvent is not 100% thread safe (I'll send a patch later on), but timeKillEvent in Wine is always synchronous (ie the killer is killed when timeKillEvent returns).

2 3

Re: shell shortcuts
by Martin Fuchs 10 Jan '04

10 Jan '04

Hello again, I just had a look at some WIN98 shortcut files. They are also in ANSI format, not 16 bit Unicode: 00000000: 4C 00 00 00-01 14 02 00-00 00 00 00-C0 00 00 00 L ☺¶☻ └ 00000010: 00 00 00 46-1B 00 00 00-00 00 00 00-00 3E EA 22 F← >Û" 00000020: 0F 7D BD 01-00 98 32 60-C0 14 C2 01-00 3E EA 22 ☼}¢☺ ÿ2`└¶┬☺ >Û" 00000030: 0F 7D BD 01-00 D0 00 00-00 00 00 00-01 00 00 00 ☼}¢☺ ð ☺ 00000040: 00 00 00 00-00 00 00 00-00 00 00 00-61 00 14 00 a ¶ 00000050: 1F 0F E0 4F-D0 20 EA 3A-69 10 A2 D8-08 00 2B 30 ▼☼ÓOð Û:i►óÏ◘ +0 00000060: 30 9D 19 00-23 43 3A 5C-00 00 00 00-00 00 00 00 0Ø↓ #C:\ 00000070: 00 00 00 00-00 00 00 00-00 51 4D 17-00 31 00 00 QM↨ 1 00000080: 00 00 00 CF-2C 4C 27 10-00 57 49 4E-44 4F 57 53 ¤,L'► WINDOWS 00000090: 00 00 1B 00-32 00 00 D0-00 00 AB 24-20 98 00 00 ← 2 ð ½$ ÿ 000000A0: 4E 4F 54 45-50 41 44 2E-45 58 45 00-00 00 00 67 NOTEPAD.EXE g 000000B0: 00 00 00 1C-00 00 00 03-00 00 00 1C-00 00 00 32 ∟ ♥ ∟ 2 000000C0: 00 00 00 36-00 00 00 53-00 00 00 16-00 00 00 03 6 S ▬ ♥ 000000D0: 00 00 00 07-0D 2B 3E 10-00 00 00 57-49 4E 39 38 •♪+>► WIN98 000000E0: 00 43 3A 5C-00 1D 00 00-00 02 00 00-00 14 00 00 C:\ ↔ ☻ ¶ 000000F0: 00 00 00 00-00 00 00 02-00 5C 5C 4D-56 39 38 5C ☻ \\MV98\ 00000100: 43 00 57 49-4E 44 4F 57-53 5C 4E 4F-54 45 50 41 C WINDOWS\NOTEPA 00000110: 44 2E 45 58-45 00 0E 00-2E 2E 5C 4E-4F 54 45 50 D.EXE ♫ ..\NOTEP 00000120: 41 44 2E 45-58 45 0A 00-43 3A 5C 57-49 4E 44 4F AD.EXE◙ C:\WINDO 00000130: 57 53 00 00-00 00 - - WS -- Martin Fuchs martin-fuchs(a)gmx.net

1 0

Re: shell shorcuts
by Martin Fuchs 10 Jan '04

10 Jan '04

> Hmm..., I KNOW 'SCF_UNICODE' is NOT 0x1000 in the first place, but why do > you say it's 0x80 ? > > Going by the copyrights, Marcus Meissner and Juergen Schmied did the initial > job, and perhaps one of them put this value. > I don't know about Juergen, but I have tremendous faith in Marcus (I use > SuSE you see ;) ), and there MUST have been some reason why 'SCF_UNICODE' > got the value 0x1000, although it seems to be wrong ! I looked into the CVS history logs and found, when SCF_UNC (rev. 1.21) and SCF_UNICODE (rev. 1.54) have been introduced: ---------------------------- revision 1.21 date: 1999/08/15 14:31:36; author: julliard; state: Exp; lines: +23 -15 Juergen Schmied <juergen.schmied(a)metronet.de> More use of rc files for strings and menus, fixes. First internal icons. ---------------------------- revision 1.54 date: 2003/05/21 18:50:53; author: julliard; state: Exp; lines: +701 -846 Mike McCormack <mike(a)codeweavers.com> Remove code that starts wineshelllink, instead create a windows compatible shortcut (*.lnk) file. After creating that file, start a link processor (winemenubuilder) on it, which reads it back then calls wineshelllink. Rework CreateStreamFromFile to create an IStream object that is writeable. ---------------------------- Perhaps we should ask Juergen Schmied and Mike McCormack where they got their defintions from. But I think SCF_UNC = 0x80 is the right one. > Hence, please consolidate your assigning it 0x80 with some examples/hexedits > so that I can answer when I get grilled ;) OK, you want to see some hex dumps. Here ist one for notepad.exe on WIN95: (sorry for the likely unreadable formating) 00000000: 4C 00 00 00-01 14 02 00-00 00 00 00-C0 00 00 00 L ?¶? ? 00000010: 00 00 00 46-0B 00 00 00-20 00 00 00-00 92 6A 89 F? Æjë 00000020: 12 9B BB 01-00 58 E5 4E-04 D7 C3 01-00 92 6A 89 ?ø?? XÕN?Î?? Æjë 00000030: 12 9B BB 01-00 8A 00 00-00 00 00 00-01 00 00 00 ?ø?? è ? 00000040: 00 00 00 00-00 00 00 00-00 00 00 00-5F 00 14 00 _ ¶ 00000050: 1F 00 E0 4F-D0 20 EA 3A-69 10 A2 D8-08 00 2B 30 ? ÓOð Û:i?óÏ? +0 00000060: 30 9D 19 00-23 43 3A 5C-00 00 00 00-00 00 00 00 0Ø? #C:\ 00000070: 00 00 00 00-00 00 00 00-00 F1 8A 15-00 31 00 00 ±è§ 1 00000080: 00 00 00 2A-30 9D 64 10-80 57 69 6E-39 35 00 00 *0Ød?ÇWin95 00000090: 1B 00 32 00-00 8A 00 00-25 21 60 59-20 80 4E 6F ? 2 è %!`Y ÇNo 000000A0: 74 65 70 61-64 2E 65 78-65 00 00 00-00 48 00 00 tepad.exe H 000000B0: 00 1C 00 00-00 01 00 00-00 1C 00 00-00 32 00 00 ? ? ? 2 000000C0: 00 00 00 00-31 47 00 00-00 16 00 00-00 03 00 00 1G ? ? 000000D0: 00 04 13 5F-37 10 00 00-00 57 49 4E-39 35 00 43 ??_7? WIN95 C 000000E0: 3A 5C 57 49-4E 39 35 5C-4E 4F 54 45-50 41 44 2E :\WIN95\NOTEPAD. 000000F0: 45 58 45 00-00 0E 00 2E-2E 5C 4E 4F-54 45 50 41 EXE ? ..\NOTEPA 00000100: 44 2E 45 58-45 - - D.EXE Here is the dump of a XP shourtcut file: 00000000: 4C 00 00 00-01 14 02 00-00 00 00 00-C0 00 00 00 L ?¶? ? 00000010: 00 00 00 46-9B 02 00 00-80 00 00 00-A0 A6 B2 00 Fø? Ç áª? 00000020: 9B C8 C3 01-76 98 AB AD-7D D7 C3 01-00 C8 2F B0 ø???vÿ½¡}Î?? ?/? 00000030: E5 27 C1 01-00 02 01 00-00 00 00 00-01 00 00 00 Õ'?? ?? ? 00000040: 00 00 00 00-00 00 00 00-00 00 00 00-F3 00 14 00 ¾ ¶ 00000050: 1F 50 E0 4F-D0 20 EA 3A-69 10 A2 D8-08 00 2B 30 ?PÓOð Û:i?óÏ? +0 00000060: 30 9D 19 00-2F 45 3A 5C-00 00 00 00-00 00 00 00 0Ø? /E:\ 00000070: 00 00 00 00-00 00 00 00-00 00 00 3C-00 31 00 00 < 1 00000080: 00 00 00 21-30 DC 73 10-00 57 49 4E-44 4F 57 53 !0?s? WINDOWS 00000090: 00 26 00 03-00 04 00 EF-BE 3C 2D 98-18 2A 30 11 & ? ? ´¥<-ÿ?*0? 000000A0: 6A 14 00 00-00 57 00 49-00 4E 00 44-00 4F 00 57 j¶ W I N D O W 000000B0: 00 53 00 00-00 16 00 40-00 31 00 00-00 00 00 25 S ? @ 1 % 000000C0: 30 47 BE 10-00 73 79 73-74 65 6D 33-32 00 00 28 0G¥? system32 ( 000000D0: 00 03 00 04-00 EF BE 3C-2D 98 18 2A-30 11 6A 14 ? ? ´¥<-ÿ?*0?j¶ 000000E0: 00 00 00 73-00 79 00 73-00 74 00 65-00 6D 00 33 s y s t e m 3 000000F0: 00 32 00 00-00 18 00 48-00 32 00 00-02 01 00 12 2 ? H 2 ?? ? 00000100: 2B 00 68 80-00 6E 6F 74-65 70 61 64-2E 65 78 65 + hÇ notepad.exe 00000110: 00 2E 00 03-00 04 00 EF-BE 96 2F 5C-76 2A 30 99 . ? ? ´¥û/\v*0Ö 00000120: 6B 14 00 00-00 6E 00 6F-00 74 00 65-00 70 00 61 k¶ n o t e p a 00000130: 00 64 00 2E-00 65 00 78-00 65 00 00-00 1A 00 00 d . e x e ? 00000140: 00 54 00 00-00 1C 00 00-00 01 00 00-00 1C 00 00 T ? ? ? 00000150: 00 33 00 00-00 00 00 00-00 53 00 00-00 17 00 00 3 S ? 00000160: 00 03 00 00-00 04 5D C9-28 10 00 00-00 53 79 73 ? ?]?(? Sys ... (snipped here) Look at the dword from 0x0014 to 0x0017. It is 0xB ("0B 00 00 00") for WIN95 and 0x29B ("9B 02 00 00") for XP. Please don't ask me for the meanging of this 0x200 - I just don't know it. But believe me - this bit with value 0x80 has been zero in any WIN95 created .lnk file I saw. And it has been set in all .lnk files of XP. As you know, WIN95 uses ANSI strings and XP uses UTF16 strings. Bit "0x1000" was never set in any OS's shortcut files. If you double-click a WIN95-link on XP it also works. You can even edit its properties. When saving it using XP, it get overwritten with the new format. The bit in question is now set! However Windows itself seems to ignore the bit when reading shortcut files. It can successfully read them regardless of me having changed the bit before. This is some kind of "file recovery" if you ask me. > However, I think that we should ALL handle strings as Unicode internally, > and convert to ANSI when required, and NOT the other way round. > Hence, we will be compatible with Win98/ME/2K/XP, as that's what M$ does... > If you see my code carefully, you will notice that EVERYTHING is handled as > Unicode internally. Of course. Shell link objects in memory should store the strings in Unicode format. > The flag 'SCF_UNICODE' is used to test the bit mask and determine if the > .lnk is serialized in Unicode or not... > I am pretty sure that Windows >95 handle EVERYTHING in Unicode, and thus a > wrong value of 'SCF_UNICODE' will ONLY mess up Win95 .lnk files ! > > If you can consolidate your defining 'SCF_UNICODE' as 0x80, I will ONLY be > too happy to incorporate that, else those still using Win95 (?) may suffer, > as Win95 handles strings as ANSI and not Unicode... Regards, Martin

1 0

Key signing party at wineconf
by Shachar Shemesh 09 Jan '04

09 Jan '04

Hi all, I'm organizing a key signing party at wineconf. Anyone who wishes to participate, please email me the following details: Your full, real, name. It is not possible to participate in a key signing party using a nickname or a virtual identity. Sorry. Your key's fingerprint. Your actual key. Again, the key must have your real name on it (I am talking public key, of course. You should never send your private key to anyone). I am going to compile the list of names into a keyring and post it to a public key server. If, for any reason, you wish your key to remain unpublished (highly unrecommended), please note so in your mail. For more info about GPG key signing parties, check out the howto at http://www.cryptnet.net/fdp/crypto/gpg-party.html Shachar -- Shachar Shemesh Lingnu Open Systems Consulting http://www.lingnu.com/

1 0

Compilation broken in CVS
by Paul Millar 09 Jan '04

09 Jan '04

Hi everyone, Looks like one of the patches broke compiling last night: http://www.astro.gla.ac.uk/users/paulm/WRT/buildinfo.php?id=472 I get error messages like: gcc -shared -Wl,-Bsymbolic,-z,defs,-init,__wine_spec_init,-fini,__wine_spec_fini winearts.drv.spec.o arts.o audio.o winearts.drv.dbg.o -o winearts.drv.so -L../../../libs/wine -lwine -L/usr/lib -ldl -lartsc -lpthread -L../../../libs/uuid -lwine_uuid -L../../../libs/port -lwine_port -lm -lc audio.o: In function `wodPlayer_WriteMaxFrags': /scratch/lilith1/paulm/wine/dlls/winmm/winearts/audio.c:722: undefined reference to `HeapRealloc' collect2: ld returned 1 exit status make[2]: *** [winearts.drv.so] Error 1 Anyone else get this? Cheers, Paul. ---- Paul Millar

3 4

Fwd: Re: [Discuss] Crossover Office with Microsoft Publish '97
by Jesse Hammons 09 Jan '04

09 Jan '04

Does anybody know the basic problem with Microsoft Publisher '97 not working with wine? I'm willing to debug it a bit, but I want to find out how big of a project it is first. Or maybe somebody else is working on this already? Publisher '97 loads files and seems to almost complete functionality on my system. Unfortunately I can't click on any UI elements and keyboard events aren't processed. Someone seems to have even gotton Publisher 2000 to work (there is a workaround posted in the application database). However this fix doesn't work on Publisher '97. I would like to patch this, especially if it is relatively straightforward to do so. What kind of logging can I turn on to find out what is happening to the mouse/keyboard events, etc. Thanks, -Jesse --- Jeremy White <jwhite(a)codeweavers.com> wrote: > Subject: Re: [Discuss] Crossover Office with Microsoft Publish '97 > From: Jeremy White <jwhite(a)codeweavers.com> > To: discuss(a)crossover.codeweavers.com > Date: 09 Jan 2004 08:58:30 -0600 > > Hi Jesse, > > This is a great question, and the answer is to a Wine hacker -- > we'd love to have your help! > > The full set of resources for hacking on Wine are at www.winehq.org; > I know that's intimidating, but there are friendly folks > on irc at #winehq. If you show that you're willing to do > the elbow grease (and are a bit patient), I think you'll find > that folks will jump to help you. > > Finally, it's fairly straightforward to configure CrossOver to > use Wine from CVS; look in the config file in the cxoffice/etc > directory. > > Good hunting, and welcome! > > Cheers, > > Jeremy > > > On Thu, 2004-01-08 at 15:32, Jesse Hammons wrote: > > > > I have downloaded and installed the Crossover Office trial version > on > > my debian GNU/linux system (sarge, kernel version 2.4.20). I used > the > > Crossover setup program to install MS Publisher from the Office '97 > CD. > > > > Setup installs MS publisher with no errors. Publisher starts up, > and > > displays the initial dialog (where you can choose a template or > open an > > existing file). After cancelling this initial dialog, publisher is > > aware of the mouse location (it updates the rulers when you move > the > > mouse) but no mouse clicks or keyboard presses are processed. > > Something wrong with window modality? > > > > Is there anything I can tweak to try to get MS pub to work? How > about > > a way to log the translation of X events to windows events, so I > can > > try to trace where they are going? > > > > PS This behavior in crossover is the same behavior as when I tried > with > > wine-030618. > > > > Thanks, > > -Jesse > > > > __________________________________ > > Do you Yahoo!? > > Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes > > http://hotjobs.sweepstakes.yahoo.com/signingbonus > > _______________________________________________ > > discuss mailing list > > discuss(a)crossover.codeweavers.com > > http://crossover.codeweavers.com/mailman/listinfo/discuss > > > _______________________________________________ > discuss mailing list > discuss(a)crossover.codeweavers.com > http://crossover.codeweavers.com/mailman/listinfo/discuss __________________________________ Do you Yahoo!? Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes http://hotjobs.sweepstakes.yahoo.com/signingbonus

1 0

Re: #6 - Add delay loading to rundll32
by Dmitry Timoshkov 09 Jan '04

09 Jan '04

"Steven Edwards" <steven_ed4153(a)yahoo.com> wrote: > I hope my formatting is right. I use EditPlus to do my development and > it tends to not agree with Wine sources sometimes so I have to go back > to notepad to clean it up. With this patch I can compile rundll32 on > Mingw now. > > Changelog: > Delay load Wine16 APIs for Win16 dlls. Your patch is not only formatted badly, but it also does things not allowed in plain C - places variables in the middle of the function body. Please fix. -- Dmitry.

2 1

WWN broken
by Mike Hearn 09 Jan '04

09 Jan '04

XML error: not well-formed (invalid token) at line 104 Looks like it contains a typo. I thought only 1 item was a bit strange :)

2 1

Re: #6 - Add delay loading to rundll32
by Andreas Mohr 09 Jan '04

09 Jan '04

On Fri, Jan 09, 2004 at 07:14:07AM -0800, Steven Edwards wrote: > Hello, > I hope my formatting is right. I use EditPlus to do my development and As soon as you have to resort to phrases like "I hope...", you already know that you're in troubled and boiling water. ;-) - HeapFree( GetProcessHeap(), 0, dllA );^M - return ret;^M Andreas Mohr

1 0

Re: shell shorcuts
by Subhobroto Sinha 09 Jan '04

09 Jan '04

One day thus spake Martin Fuchs: >I am working on the ReactOS Explorer, which uses Wine's shell32 implementation. >We already have made many bugfixes and estensions to the shell link and other >shell32 code. One of those extensions is the implementation of control panel in >shell namespace I am already aware of that (thanks to Steve), and I would appreciate if someone could send me the changes/patches to shell32 by the ReactOS team (even if the source does not compile) so I can have a look.. Perhaps you can send me a zip of the ReactOS shell32 directory (keep the makefiles and .defs out - send just the real source :) ) ? That will be nice >Well, I think it's because it has been defined wrong. I am currently using this >definition: >#define SCF_UNICODE 0x80 (instead of 0x1000) >This is at least compatible to links of WIN95 (ANSI strings) and WIN XP (UTF16 strings). >I did not yet test any other operating system versions. With this corrected >defintion and a few more extensions Stream_LoadString() works pretty well >on ReactOS. Hmm..., I KNOW 'SCF_UNICODE' is NOT 0x1000 in the first place, but why do you say it's 0x80 ? Going by the copyrights, Marcus Meissner and Juergen Schmied did the initial job, and perhaps one of them put this value. I don't know about Juergen, but I have tremendous faith in Marcus (I use SuSE you see ;) ), and there MUST have been some reason why 'SCF_UNICODE' got the value 0x1000, although it seems to be wrong ! Hence, please consolidate your assigning it 0x80 with some examples/hexedits so that I can answer when I get grilled ;) However, I think that we should ALL handle strings as Unicode internally, and convert to ANSI when required, and NOT the other way round. Hence, we will be compatible with Win98/ME/2K/XP, as that's what M$ does... If you see my code carefully, you will notice that EVERYTHING is handled as Unicode internally. The flag 'SCF_UNICODE' is used to test the bit mask and determine if the .lnk is serialized in Unicode or not... I am pretty sure that Windows >95 handle EVERYTHING in Unicode, and thus a wrong value of 'SCF_UNICODE' will ONLY mess up Win95 .lnk files ! If you can consolidate your defining 'SCF_UNICODE' as 0x80, I will ONLY be too happy to incorporate that, else those still using Win95 (?) may suffer, as Win95 handles strings as ANSI and not Unicode... Will send Alexandre my patch within the next few days as no one has objected to it being messy, so take the last chance ;) BTW Martin, great work with ROSExplorer, keep at it, and one day WINE will have a complete Desktop with shell namespaces ! Regards Subhobroto Sinha

2 1

reading relay log
by Ferenc Wagner 09 Jan '04

09 Jan '04

Hi, I feel rather stupid, but need help understanding this. I managed to screw up winetest so that it runs into trouble. The relay trace goes like (indented by examine-relay) -------------------------------------------------------------------- 000a:Call comctl32.InitCommonControls() ret=40593c29 000a:Ret comctl32.InitCommonControls() retval=40def6d4 ret=40593c29 000a:Call kernel32.GetModuleHandleA(00000000) ret=40593c3c 000a:Ret kernel32.GetModuleHandleA() retval=40540000 ret=40593c3c 000a:Call user32.CreateDialogParamA(40540000,00000064,00000000,40593b4c,00000000) ret=40593c42 000a:Call kernel32.FindResourceA(40540000,00000064,00000005) ret=407aa47f 000a:Ret kernel32.FindResourceA() retval=405954f8 ret=407aa47f 000a:Call kernel32.LoadResource(40540000,405954f8) ret=407aa48a 000a:Ret kernel32.LoadResource() retval=40590d20 ret=407aa48a 000a:Call kernel32._EnterSysLevel(40810b00) ret=407c21b8 000a:Ret kernel32._EnterSysLevel() retval=00000008 ret=407c21b8 000a:Call kernel32._LeaveSysLevel(40810b00) ret=407c21dc 000a:Ret kernel32._LeaveSysLevel() retval=00000000 ret=407c21dc 000a:Call kernel32._EnterSysLevel(40810b00) ret=407c21b8 000a:Ret kernel32._EnterSysLevel() retval=00000008 ret=407c21b8 000a:Call kernel32._EnterSysLevel(40810b00) ret=407c21b8 000a:Ret kernel32._EnterSysLevel() retval=00000008 ret=407c21b8 000a:Call kernel32._LeaveSysLevel(40810b00) ret=407c21dc 000a:Ret kernel32._LeaveSysLevel() retval=00000000 ret=407c21dc 000a:Call ntdll.RtlAllocateHeap(40300000,00000000,0000001c) ret=407a6047 000a:Ret ntdll.RtlAllocateHeap() retval=40347998 ret=407a6047 000a:Call gdi32.CreateDCA(407f0e04 "DISPLAY",00000000,00000000,00000000) ret=407a6066 000a:Call ntdll.RtlCreateUnicodeStringFromAsciiz(40def3e8,407f0e04 "DISPLAY") ret=408994dd 000a:Ret ntdll.RtlCreateUnicodeStringFromAsciiz() retval=00000001 ret=408994dd 000a:Call kernel32._CheckNotSysLevel(408cf320) ret=408a56e8 000a:Ret kernel32._CheckNotSysLevel() retval=0000000a ret=408a56e8 000a:Call ntdll.RtlEnterCriticalSection(408cf400) ret=408ae109 000a:Ret ntdll.RtlEnterCriticalSection() retval=00000000 ret=408ae109 000a:Call ntdll.RtlLeaveCriticalSection(408cf400) ret=408ae1d9 000a:Ret ntdll.RtlLeaveCriticalSection() retval=00000000 ret=408ae1d9 000a:Call kernel32._EnterSysLevel(408cf320) ret=408a50cf 000a:Ret kernel32._EnterSysLevel() retval=0000000c ret=408a50cf 000a:Call ntdll.RtlAllocateHeap(40300000,00000000,00000138) ret=408a5215 000a:Ret ntdll.RtlAllocateHeap() retval=403479c0 ret=408a5215 000a:Call x11drv.CreateDC(403479c0,403479d8,40def15c L"DISPLAY",00000000,00000000,00000000) ret=40899405 000a:Call ntdll.RtlAllocateHeap(40300000,00000008,0000008c) ret=409ee0de 000a:Ret ntdll.RtlAllocateHeap() retval=40347b00 ret=409ee0de 000a:Call gdi32.GetObjectType(0000007c) ret=409ee125 000a:Call kernel32._EnterSysLevel(408cf320) ret=408a5527 000a:Ret kernel32._EnterSysLevel() retval=0000000c ret=408a5527 000a:Call kernel32._LeaveSysLevel(408cf320) ret=408a56c3 000a:Ret kernel32._LeaveSysLevel() retval=00000000 ret=408a56c3 000a:Ret gdi32.GetObjectType() retval=00000003 ret=409ee125 000a:Call ntdll.RtlEnterCriticalSection(40a20700) ret=409fe8b0 000a:Ret ntdll.RtlEnterCriticalSection() retval=00000000 ret=409fe8b0 err:ntdll:RtlpWaitForCriticalSection section 0x40334040 "?" wait timed out in thread 000a, blocked by 0009, retrying (60 sec) -------------------------------------------------------------------- which I don't understand given the definition -------------------------------------------------------------------- HWND WINAPI CreateDialogParamA( HINSTANCE hInst, LPCSTR name, HWND owner, DLGPROC dlgProc, LPARAM param ) { HRSRC hrsrc; LPCDLGTEMPLATEA ptr; if (!(hrsrc = FindResourceA( hInst, name, (LPSTR)RT_DIALOG ))) return 0; if (!(ptr = (LPCDLGTEMPLATEA)LoadResource(hInst, hrsrc))) return 0; return CreateDialogIndirectParamA( hInst, ptr, owner, dlgProc, param ); } -------------------------------------------------------------------- After LoadResource returns, I would expect a call to CreateDialogIndirectParamA instead of the SysLevels etc. Could somebody explain this, please? Thanks a lot, Feri.

7 19

uxtheme and unicode INI files
by Kevin Koltzau 09 Jan '04

09 Jan '04

I've submitted this patch once with no luck, but I've got a question that may affect my need to use this patch (or one similar) Msstyles store a few INI files within the style that define various properties of the theme. Windows duplicates all the .ini file processing within uxtheme.dll, I would prefer to not do this (hence this patch) however, what are the feelings of temp files being generated from resources in a style while its being loaded (which would be needed to use the GetPrivateProfile* family of functions)? Or would it be preferable that I stick with the way windows does it (by duplicating the ini file loading within uxtheme) and do all the processing in memory?

2 1

Re: Allow runtime control of the number of X11 fonts
by Alexandre Julliard 09 Jan '04

09 Jan '04

Bill Medland <billmedland(a)mercuryspeed.com> writes: > Bill Medland (billmedland(a)mercuryspeed.com) > Allow runtime increase in the maximum number of fonts processed. Do we really need a config parameter for that? Actually, do we really need a limit at all? -- Alexandre Julliard julliard(a)winehq.com

2 2

Re: Broken Mandrake packages
by Ivan Leo Murray-Smith 08 Jan '04

08 Jan '04

> Hmm, OK. I don't know which this person was using. Why is /usr/lib/wine > even added to ld.so.conf though, surely that isn't necessary? Only > libwine needs to be in the linker path. libs are in /usr/lib/wine and dlls are in /usr/lib/wine/dlls, not adding /usr/lib/wine to ld.so.conf causes wine to fail, as it doesn't find ntdll.dll.so. There are alternative solutions, but this looks good to me, keeps dirs tidy and has always worked. Ivan.

4 6

dll name length (was: Windows dll replacement with Linux library)
by Dan Timis 08 Jan '04

08 Jan '04

I finally figured out what my problem was. If the name of the library is "USBUtils" it works, if it is "USBDeviceUtils" it doesn't. Actually the max length I can use is 11 characters. That is probably 15 characters including ".dll" In my config file all filesystems are "win95" The version is "nt40" Is there any way to configure wine to support longer names? Thanks, Dan Timis Sounds Just Right, Inc. > From: Dan Timis <timis(a)museresearch.com> > > On Saturday, January 3, 2004, at 01:07 AM, Dimitrie O. Paun wrote: > >>> I'm new to this so please bear with me. >>> >>> First I edited the Makefile and replaced gcc with winegcc. When I >>> run >>> "make" I get this error when it tries to link: >>> >>> could not open .def file for kernel32 >>> Error: /usr/bin/winebuild failed. >>> Error: /usr/bin/winewrap failed. >> >> Can you please send me the command that generates this? Just to make >> sure that we're on the same page, use winegcc (for now) just for >> building >> the test application, not the DLL. >> >>> Then, I ran ./configure --help and it says that you can use the "CC" >>> var to specify the compiler. I started from scratch, set "export >>> CC=winegcc", then ran configure again. The output looks like this: >>> >>> checking whether make sets {$MAKE}... yes >>> checking for gcc... winegcc >>> checking for C compiler default output... configure: error: C >>> compiler >>> cannot create executables >> >> This is very odd. winegcc should be configure friendly (it does work >> for >> wxWindows BTW). Hey, what version of Wine are you using? I do hope >> it's >> the latest CVS... > > I am using an older version 20030618. It's hard to change, other > people depend on this particular version and I would have to upgrade > several machines. I could try on one machine, but... > > A colleague who dealt with similar problems in the past helped me. He > added this to Makefile.in > > # generate a .def "import library" file from the spec file > $(usbutils_dll_DEF): $(usbutils_dll_SPEC_SRCS) Makefile.in > $(WINEBUILD) --def $(usbutils_dll_SPEC_SRCS) > $(usbutils_dll_DEF) > > Both the .dll.so and the .def go in /usr/lib/wine/wine. Earlier I > noticed that there was no .def file. That was our clue. > > For the test we added the library to the list of wine dlls in > Makefile.in. > > It's working. > > I'm still a little confused, but I understand much more than a week > ago. Thanks. > > Dan Timis > Muse Research, Inc. >

3 3

Re: Broken Mandrake packages
by Ivan Leo Murray-Smith 08 Jan '04

08 Jan '04

> These are all libraries that belong to /usr/lib. > All others (<dllname>.dll.so dlls must go to /usr/lib/wine/). > > libwine.so will look and find them in /usr/lib/wine/ by default when trying to load them. > > There is NO need to add /usr/lib/wine to ld.so.conf! OK, I'll change this in this months build. Ivan.

1 0

Re: Broken Mandrake packages
by Ivan Leo Murray-Smith 08 Jan '04

08 Jan '04

> Could whoever is responsible for these packages please double check the > specfiles? Never heard of such a problem, all RPMs are tested on both mdk 9.2 and 9.1, on 2 different computers, and I've never noticed any lib problem. /usr/lib/wine is added to ld.so.conf during post, and after that ldconfig is run. I am NOT responsible for the RPMS shipped by Mandrakesoft. Ivan.

2 1

Wine troubles on Diskless workstations.....
by Alex Stewart 08 Jan '04

08 Jan '04

Hi, Below is a thread I started in the wine-users list but so far no seems to know the answer. I've tried their suggestions but they dont work. I think its a simple question (maybe not I dont really know thats why I have the question) How does wine store the path to its libraries? Simply put I changed the prefix var in the wineinstall script to point to a different "root" path for a diskless client system. The path is the root folder that gets made into a compressed tar.gz for the ram disk. Anyway as you would think/probobly guessed when I run wine on the client the path to the libs are not correct, they still point to the path on the server instead of the true root (/lib/wine)..... Thanx a bunch in advance! -Alex PS- If I didnt explain to well above the drawn out thread of what Im doing and why is below....Thanx for your time! > Then perhaps you should build wine with the prefix that the clients > will > be using. You may need to create a chroot'ed environment that emulates > what the clients will be using. The problem with that is the Diskless clients are "Thin" ie they have a minimal system and thus no rpm management or a compiler (no gcc). > This is, of course, the problem you're actually having. You're pointing > the install directory to a directory that doesn't exist for the > clients. > Right. If I did point it to the correct path it would install on the server's local lib folder which the clients have no access to. If I rebuild wine (now that it has installed in the client root system) with the correct path would all I need to do is snag the new binaries from the bin folder of the server and put them in the bin of the client root? Sorry I keep asking this but WHERE is this path stored? Because its not in ./wine/config I cant seem to find it anywhere. I ask because if I do rebuild and its not hardcoded in the binary and it aint in ./wine/config then the problem will persist because I dont know where to change it back! On Jan 7, 2004, at 11:21 PM, Rob Hughes wrote: > On Wed, 2004-01-07 at 20:18, Alex Stewart wrote: > >> it looks for its libs at : >> /opt/pxes-0.7/stock/dist/lib/wine/ntdll.dll.so Which makes since. >> The >> directory "dist" >> is the distribution level of the root fs. So when it gets compressed >> the nodes think dist is root ie the libraries >> are in the file system there just not in >> opt/pxes-0.7/stock/dist/lib/wine/ntdll.dll.so they are in fact in >> /lib >> at the root of the ramdisk.......So my question is where is this path > > > Then perhaps you should build wine with the prefix that the clients > will > be using. You may need to create a chroot'ed environment that emulates > what the clients will be using. > > This is, of course, the problem you're actually having. You're pointing > the install directory to a directory that doesn't exist for the > clients. > > _______________________________________________ > wine-users mailing list > wine-users(a)winehq.com > http://www.winehq.com/mailman/listinfo/wine-users >

3 2

Wineconf update, RFC re remote participation
by Jeremy White 08 Jan '04

08 Jan '04

Hi folks, Okay, I've updated the Wineconf page: http://www.winehq.org/wineconf/ One thing I would like to do is to stream audio from the conference out to the web and also work very hard to include folks from #winehq (or maybe #wineconf) in some of the sessions. The sessions I thought made particular sense were the ones around Wine 1.0 as well as on OLE and Games. Does anyone recall being remote to the last Wineconf? Did it work at all? Is there anything we could/should do to enable others to join us, if only virtually? (Please feel free to tell me that it didn't work worth beans and we should just drop it, btw <g>). Other thoughts or comments? Thanks, Jer

4 6

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