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

How to determine if an application is running in Wine environment?
by Raghavan Gurumurthy June 11, 2004

June 11, 2004

BlankIf i want to do some special handling inside my Windows executable when running in Wine environment, what is the best way to do this? Thanks, -- Raghavan Gurumurthy Gupta Technologies

4 4

[D3D8] Fix Ati set_tex_op
by Raphael June 11, 2004

June 11, 2004

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Changelog: - fix version string - some fixes to ATI specific paths of set_tex_op (Christian need to complete it) - fix use of GL_SUPPORT(NV_TEXGEN_REFLECTION). I have used the wrong define, i'll get a brown paper bag :( Now Unreal(s) (UT2003,UT2004,U2) are more beautifulls :) Regards, Raphael -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAyP9+p7NA3AmQTU4RAiFyAJ0TqFMtteoA2A7NIMQ1tZqnEnuiIACeLKL7 6zh71LxsAFX1KhX6W1Q0EP4= =93Dw -----END PGP SIGNATURE-----

1 0

Zombie processes
by Shachar Shemesh June 9, 2004

June 9, 2004

Hi all, Mike M told me on IRC that this matter has come up before, but I have not been able to find it in the archives. It seems Wine has been generating lots of zombie processes when it's not 100% cleanly killed. I have also seen the system hold a socket created from a wine process in "ESTABLISHED" state, when no process is registered as the socket's owner. According to Alexandre according to Mike, this is a kernel bug. Well, it most certainly is. Theoretically, there is nothing a user space process can do to cause zombies to stay around after their parent has exit, or keep sockets open after their controlling process has quit. As wine is a user space only process, this must be a kernel bug. No way around it. However, it happened to me both on RedHat 9 with 2.4.something (NPTL back ported), with both RH9's original kernel, and their most up to date one. It also happened on Debian Sid's almost-vanilla kernel 2.6.6. It happened with LD_ASSUME_KERNEL=2.4.1 making wine choose the standard threading mode, as well as without, choosing nptl. The zombies are sometimes called wine-pthread/wine-kthread, and sometimes wine-preloader. In short, I think this is a long standing Linux kernel bug, and Linus helps those who help themselves. I will also not be surprised if it was triggered by a wine bug. So the question is this. Is there anyone on this list who knows how to submit this as a question to lkml? The only time I tried to do anything remotely like it, I was seriously ridiculed. I understand from friends that live there that this is not an exceptional thing, so I'm a bit hesitant to go back there. If no one else does, however, I will. It will require me to untaint my kernel, so someone please save me from the slow armagatron I get when I'm not running nvidia, and report this :-) Will someone take this task on himself? Shachar -- Shachar Shemesh Lingnu Open Source Consulting http://www.lingnu.com/

7 6

[winemenubuilder] shell:SHELL32_DllCanUnloadNow (void): stub, WinMain failed
by Luca Capello June 9, 2004

June 9, 2004

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I'm not 100% sure this is the good mailing-list, but I think so. I was trying to use the 'winemenubuilder' with CVS-20040605, but I got an error: ===== luca(a)gismo:~/cvs/wine$ ./wine winemenubuilder \ /home/luca/.wine/fake_windows/TreeView.lnk fixme:shell:SHELL32_DllCanUnloadNow (void): stub err:menubuilder:WinMain failed to build menu item for \ /home/luca/.wine/fake_windows/TreeView.lnk luca(a)gismo:~/cvs/wine$ ===== Now, to let you know my 'wine' environment, my 'fake_windows' came from the 'WineTools' [1] and then I installed: 1) DCOM98 (via WineTools) 2) Windows Installer (via WineTools) 3) Adobe Illustrator 10 4) Adobe Photoshop 7.0 5) BioEdit && TreeView && pDRAW32 (biological programs) In ~/.wine/config, I've: ===== luca(a)gismo:~/cvs/wine$ grep shell /home/luca/.wine/config "ShellLinker" = "wineshelllink" "shell32" = "builtin, native" luca(a)gismo:~/cvs/wine$ ===== Is this a 'wine' bug or a problem with my configuration? Thx, bye, Gismo / Luca [1] http://franksworld.net/winetools.html -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using GnuPG with Debian - http://enigmail.mozdev.org iD8DBQFAwdyCVAp7Xm10JmkRAiKVAJ0Sf/n7T1HZHP5DnkTmJB7d69AFIwCfSWMc mnMY9xdr2OODWBPWZknkoWc= =W0wV -----END PGP SIGNATURE-----

3 11

Wine on FreeBSD current
by John Birrell June 9, 2004

June 9, 2004

Are there any people subscribed to this list who use Wine on FreeBSD current? I'm just wondering if it is supposed to work as well as FreeBSD stable. -- John Birrell

2 1

Linux links in Windows
by Fabian Cenedese June 9, 2004

June 9, 2004

Hi I have a question about the standard drive/directory. I think there were some changes recently so I don't know the current state. I'm still on 20040408 as we needed to freeze and test the source. I have a process which changes the current dir and then starts a new program with CreateThread. But this one is back in the old dir again. Shouldn't it inherit the current dir of the starting process? Is this already in the current wine? Thanks bye Fabi

1 1

Re: winmm GetDevCaps better pointer check patch
by Robert Shearman June 8, 2004

June 8, 2004

On Sun, 2004-06-06 at 19:26, Robert Reif wrote: > Not a real program but Microsoft's API checking programs do > try non NULL bad pointers and expect an error return rather > than a program crash. > > Are you saying checking a good pointer can cause problems? No, checking a bad pointer can cause problems. See: http://blogs.msdn.com/LarryOsterman/archive/2004/05/18/134471.aspx Rob

4 4

Re: (Still) problem on AMD64 with wine CVS
by Maurizio Monge June 8, 2004

June 8, 2004

> Maurizio, > Ignore what it says in the source, in dlls/ntdlls/virtual.c you can change > the value in ADDRESS_SPACE_LIMIT to suit yourself. Many applications (I > venture to say most ) work fine and my solaris distro has been compiled > like this for two years with few (Actually no) complaints. > > Just don't tell Aleandre, the comment in there about not being able to > change it was directed squarely at me as a result of me doing it ! Stil, it > made wine work, while without changing the define Wine definitely would NOT > > Bob mh, i have set ADDRESS_SPACE_LIMIT to 0xffffffff and i am getting the same error... :-( Does anyone have an idea of why the mmap at the and of the "strace" i posted some time ago fails? Thx Maurizio please CC to monge(at)sns(dot)it

1 0

RE: Incoming Msg
by Twickline June 8, 2004

June 8, 2004

1 0

wine problem
by mguyard June 8, 2004

June 8, 2004

Hello I do that Before starting to work on a big project you may want to try to port a small application. The winemine application from the Wine source tree suits well for testing purposes. It can be found in the programs subdirectory. winemine is a simple application, but has a few C, header and resource files. Run make clean in the winemine source directory if it contains results of previous builds. Create a separate directory with name winemine2, so it won't conflict with the Wine copy of the application. Copy the sources of winemine (files *.c, *.h, *.rc) to this directory. Now run the commands, mentioned above from the winemine2 directory: $ winemaker --lower-uppercase . without any problem and after i go at wine directory and do ./configure and after i type make and i have a lot of errors: dialog.c:64: « p_board » non déclaré (première utilisation dans cette fonction) dialog.c:64: erreur d'analyse syntaxique avant le jeton « ) » dialog.c:65: « hDlg » non déclaré (première utilisation dans cette fonction) dialog.c:67: « TRUE » non déclaré (première utilisation dans cette fonction) dialog.c:69: « WM_COMMAND » non déclaré (première utilisation dans cette fonction) dialog.c:70: « wParam » non déclaré (première utilisation dans cette fonction) dialog.c:71: « IDOK » non déclaré (première utilisation dans cette fonction) dialog.c:78: « IDCANCEL » non déclaré (première utilisation dans cette fonction) dialog.c:84: « FALSE » non déclaré (première utilisation dans cette fonction) dialog.c: Au niveau supérieur: dialog.c:87: erreur d'analyse syntaxique avant « CALLBACK » dialog.c:87: erreur d'analyse syntaxique avant « hDlg » dialog.c: Dans la fonction « TimesDlgProc »: dialog.c:89: erreur de syntaxes avant le jeton « * » dialog.c:92: « uMsg » non déclaré (première utilisation dans cette fonction) dialog.c:93: « WM_INITDIALOG » non déclaré (première utilisation dans cette fonction) dialog.c:94: « p_board » non déclaré (première utilisation dans cette fonction) dialog.c:94: erreur d'analyse syntaxique avant le jeton « ) » dialog.c:98: « hDlg » non déclaré (première utilisation dans cette fonction) dialog.c:102: « FALSE » non déclaré (première utilisation dans cette fonction) dialog.c:103: « TRUE » non déclaré (première utilisation dans cette fonction) dialog.c:105: « WM_COMMAND » non déclaré (première utilisation dans cette fonction) dialog.c:106: « wParam » non déclaré (première utilisation dans cette fonction) dialog.c:107: « IDOK » non déclaré (première utilisation dans cette fonction) dialog.c:108: « IDCANCEL » non déclaré (première utilisation dans cette fonction) dialog.c: Au niveau supérieur: dialog.c:117: erreur d'analyse syntaxique avant « CALLBACK » dialog.c:117: erreur d'analyse syntaxique avant « hDlg » dialog.c: Dans la fonction « AboutDlgProc »: dialog.c:119: « uMsg » non déclaré (première utilisation dans cette fonction) dialog.c:120: « WM_INITDIALOG » non déclaré (première utilisation dans cette fonction) dialog.c:121: « TRUE » non déclaré (première utilisation dans cette fonction) dialog.c:123: « WM_COMMAND » non déclaré (première utilisation dans cette fonction) dialog.c:124: « wParam » non déclaré (première utilisation dans cette fonction) dialog.c:125: « IDOK » non déclaré (première utilisation dans cette fonction) dialog.c:126: « IDCANCEL » non déclaré (première utilisation dans cette fonction) dialog.c:127: « hDlg » non déclaré (première utilisation dans cette fonction) dialog.c:132: « FALSE » non déclaré (première utilisation dans cette fonction) something is not declared so i follow the operation procedure: You are done! Now you can start the application as ./winemine2. If you come across problems preparing and building this application this probably means that winemaker utility is broken by some changes in Wine. Try asking for help on <wine-devel(a)winehq.org> so i try to ask the question at your business. Please help me regards Mickael GUYARD INTA engineer Paris Accédez au courrier électronique de La Poste : www.laposte.net ; 3615 LAPOSTENET (0,34/mn) ; tél : 08 92 68 13 50 (0,34/mn)

1 0