September 2005 - Wine-devel

Problem in a installation on IBM zSeries s/390
by Ricardo Azzolini 22 Sep '05

22 Sep '05

IŽm having intallation problems with WINE ( when interlocked.c is compiled the following message appears: "error you must implement the interlocked* functions for your CPU"). I've been working with Linux SUSE Enterprise Server 9 for s/390 zSeries, and WINE-20050830. Have you ever seen this error before? Do you have any suggestions ? Thanks, Ricardo Azzolini

2 1

Newbie Wine question... Borland C++ Builder and Firebird via FIBplus
by Esko Woudenberg 22 Sep '05

22 Sep '05

I have a Borland C++ Application (with full source code) that I am trying to get to run under Wine 20050830. (I plan on switching to CVS builds once I see some progress) I keep getting "segmentation fault" when running the app. I found info on WINEDEBUG and am currently running it set to +relay This results in 300+ Megabyte debug file. (Ran system out of memory trying to loot at it with Konq) I have then been using "tail" to grab just the last few thousand lines of it... It always ends with hundreds/thousands of calls to ntdll.RtlEnterCriticalSection and ntdll.RtsLeaveCriticalSection followed by err:seh:setup_exception stack overflow ### bytes in thread #### eip ###### esp ###### stack 0x##### - 0x#### I am planning on using the HKLM\Software\Wine\Wine existence to let the app know it is running on wine... The app itself also has a "debug mode" that logs events to a file while running - is there a way to send these messages to the same log as WINEDEBUG? That way I would be able to see what method or function of the app resulted in the thousands of calls into the WIN32 API... I am trying to figure out how to: A> Turn the above errors into useful bug reports B> Be able to resolve limitations or errors in wine as I came across them... I do NOT speak for the U.S.Army Corps of Engineers. I am a contractor supporting one of their projects... The recent developments in Mass re Open Formats motivated me to try to get this app working under wine so that running Windows (only platform currently supported by this software) would not be a requirement in order to work on large USACE contracts... __________________________________ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com

3 4

Running Wine from source tree
by James Liggett 22 Sep '05

22 Sep '05

Hi, I'm doing a lot of testing, and I was wondering if I can run Wine from within its source tree without having to reinstall it after every build. If it can be done without conflicting with an existing installation of Wine, how do I do it? Thanks, James

5 4

Re: IDE disk geometry
by Michael Ost 22 Sep '05

22 Sep '05

On Tue, 2005-09-20 at 18:22, Vitaliy Margolen wrote: > Tuesday, September 20, 2005, 6:11:49 PM, Michael Ost wrote: > > Should I put my code in CDROM_DeviceIoControl? Or handle it in > > NtDeviceIoControlFile? Should I pass all other IoControlCodes except > > IOCTL_DISK_DRIVE_GET_GEOMETRY for a verifiable IDE drive on to the > > CDROM_... function? > I don't it make any sense to create the whole new file to parse just one IOCTL. > So you might just add it to the cdrom.c I think that might get accepted. I don't think it was clear that the device in question is not a CDROM, but a hard disk. Are IDE hard disks supposed to be lumped in with CDROMs in the code? > But before you go too far, pleas look at kernel/oldconfig.c. It does some > parsing of /proc already. So all you need to do is to find where this > information is stored on windows (it has to be somewhere in registry) and add to > that. Then you don't need to parse /proc all the time but just read info from > the registry. One possible option would be to use IOCTL_SCSI_GET_INQUIRY_DATA to OK. That's a good idea, except that in the Wine version my company is using there is no oldconfig.c. So for our version I guess I would patch dlls/ntdll/cdrom.c by reading out of proc directly. But I would submit a version that stores disk geometry in the registry. I'll look in to that. Thanks for the feedback... mo

2 2

Re: ntdll: Add few tests for object manager
by Alexandre Julliard 22 Sep '05

22 Sep '05

Vitaliy Margolen <wine-patch(a)kievinfo.com> writes: > All of them are to-do. Thanks to Robert Shearman for examples. ;-) > Can't really test nothing more since most of the om functions are stubs. Come on, you can test a lot more than that. Even if you only test create and open functions, if you test the various case combinations, with or without the CASE_INSENSITIVE flag, for mutexes, events, semaphores, pipes, mappings, files, etc. you should be able to easily come up with a few hundred tests. -- Alexandre Julliard julliard(a)winehq.org

2 1

Dragon ns8 problem
by Jean Magnan de Bornier 22 Sep '05

22 Sep '05

Hello all, My machine: Linux-gentoo, wine 20050725 I'm quite new to wine, just installed it in order to use dns8, of which I have the french version. I looked at recent threads on this list and have been more or less hopeful, but right now I have had no success; here is the log of my last attempt with the command "wine setup.exe": === Début de l'écriture dans le journal : 22/08/2005 14:18:02 === Début de l'action 14:18:02 : INSTALL. Début de l'action 14:18:02 : ISMsiServerStartup. Fin de l'action 14:18:03 : ISMsiServerStartup. Valeur renvoyée : 1. 1: The InstallScript engine version currently installed on this machine is adequate. Début de l'action 14:18:03 : ISStartup. 1: Event 'E183186' is created 1: GetInstallDriver, Can not find InstallDriver in ROT table, Return Code = 0x800401e3 1: {DDDD0C4B-57F7-4A85-ACF0-DB3FC8F1DBB4} 1: ISMsiServerStartup Failure. Unknown Exception. Fin de l'action 14:18:03 : ISMsiServerStartup. Valeur renvoyée : 1603. 1: ISStartUp Failure. OpenEvent, Error = 0x2 Fin de l'action 14:18:03 : ISStartup. Valeur renvoyée : 3. Début de l'action 14:18:03 : SetupCompleteError. Informations 2898. Tahoma8, Tahoma, 0 Informations 2898. TahomaBold10, Tahoma, 0 Début de l'action 14:18:06 : ISCleanUpFatalExit. Fin de l'action 14:18:06 : ISCleanUpFatalExit. Valeur renvoyée : 3. DEBUG: Error 2896: Executing action ISCleanUpFatalExit failed. Erreur interne 2896. ISCleanUpFatalExit Fin de l'action 14:18:06 : SetupCompleteError. Valeur renvoyée : 3. Fin de l'action 14:18:06 : INSTALL. Valeur renvoyée : 3. === Fin de l'écriture dans le journal : 22/08/2005 14:18:06 === MSI (c) (0C:0E): Produit : Dragon NaturallySpeaking 8 -- L'installation a échoué. The eighth line of this seems to be tne interesting one; what would this InstallDriver and this ROT table be? Can I find them somewhere? Any hope still? TIA, -- Jean Magnan de Bornier | Cours Victor Hugo e-mots: jean at bornier.net | 13980 Alleins France T 08 70 39 34 03 | P 06 09 17 35 87

6 38

Re: DDRAW: Fix reference counting
by Robert Shearman 21 Sep '05

21 Sep '05

Stefan Dösinger wrote: >Hello, >This patch increases the reference count of a DirectDraw object when a Surface >is created, like Windows does. It also adds a test which tests this >functionality. > >Stefan Dösinger > > >------------------------------------------------------------------------ > >Index: dlls/ddraw/ddraw_main.c >=================================================================== >RCS file: /home/wine/wine/dlls/ddraw/ddraw_main.c,v >retrieving revision 1.9 >diff -u -r1.9 ddraw_main.c >--- dlls/ddraw/ddraw_main.c 12 Sep 2005 14:12:47 -0000 1.9 >+++ dlls/ddraw/ddraw_main.c 18 Sep 2005 19:56:12 -0000 >@@ -697,8 +697,10 @@ > } > else if (pDDSD->ddsCaps.dwCaps & DDSCAPS_TEXTURE) > { >- /* create texture */ >+ /* create texture. This increases the DD refcount by 2 */ > > Why do you increase the refcount by 2? Since you add and release them in the same functions, it is not really necessary and just adds complexity to the code. > hr = create_texture(This, pDDSD, ppSurf, pUnkOuter); >+ if(!FAILED(hr)) >+ IDirectDraw7_AddRef(iface); /* Plus the increase at the end of the function */ > > if (!FAILED(hr)) -> if (SUCCEEDED(hr)) -- Rob Shearman

4 4

Re: listview: infoPtr might be invalid after WM_NOTIFY
by Dimi Paun 21 Sep '05

21 Sep '05

> Dimi, if you think this is ugly, or if you are working on a better solution, > please do protest. Well, in part it's a matter of style, and IMO this will clutter the code. Moreover, the patch as it is now works by accident. For example: /* send NM_RELEASEDCAPTURE notification */ - notify(infoPtr, NM_RELEASEDCAPTURE); + notify(infoPtr->hwndSelf, NM_RELEASEDCAPTURE); if (!infoPtr->bFocus) SetFocus(infoPtr->hwndSelf); See, after the notify() the infoPtr may be invalid. This means that if we assume the control can be deleted at any point we send out a notification, we have to reget and recheck infoPtr after every function call. There's got to be a better way. I personally think an exception-based solution would be better. This is what exceptions where invented. I know they look alien in C, but I use them every day in Java for good effect. It's true, we have to be careful to release resources along the way, but we have only 6 such allocations that need protecting, and they are localized. And there we already have a try/catch simulated with goto's. Another approach may be to ref count the structure pointed to by infoPtr, and release it at exit from WinProc when the count is 0. Sort of a poor man's garbage collection. I'm cool with this too, and in fact it may be cleaner then the exception-based solution. -- Dimi Paun <dimi(a)lattica.com> Lattica, Inc.

2 3

Re: Wine FAQ update #2
by Dimi Paun 21 Sep '05

21 Sep '05

From: "Tom Wickline" <twickline(a)gmail.com> >I forgot a </para> and put a trademark tag in for Bricscad, also fixed >the Bricscad url. Can you please re-diff to the lastest and resend? -- Dimi Paun <dimi(a)lattica.com> Lattica, Inc.

2 1

Googletalk unable to connect
by Vijay Kiran Kamuju 21 Sep '05

21 Sep '05

Hi, I think i might have found one missing link why one cannot connect using gmal. When i was looking through symbols in googletalk.exe, i have found that there are strings like WinHttp* These are functions in winhttp.dll, defined in winhttp.h I will send you details if i find any other thing. bye, Vijay

1 0