February 2006 - Wine-Devel - list.winehq.org

Re: Implement DVD_ReadStructure
by Detlef Riekenberg Feb. 9, 2006

Feb. 9, 2006

Am Sonntag, den 05.02.2006, 22:01 +1100 schrieb Troy Rollo: > ChangeLog: > Implement DVD_ReadStructure > --- /dev/null 2006-02-03 18:20:42.451563144 +1100 > +++ wine-git/include/ntddcdvd.h 2006-02-05 21:50:39.000000000 +1100 Please use "include/ddk/" -- By By ... ... Detlef

7 11

wine on Intel Xeon Processor
by Ananth M Feb. 9, 2006

Feb. 9, 2006

Hi I have a windows application that calls a function ( approximately 10000 times) exported by a third party DLL. I have two machines ( one with Intel pentium 4 processor and other with Intel Xeon processor ) with RHEL 4.0 installed on both of these machine. If I execute the windows application on the first machine (one with Intel pentium 4 processor ) using WINE, the execution time is almost equal to the execution time in windows machine. But, if I execute the same application on the second machine (Intel Xeon processor ), the execution time is almost 6 times to the first machine. I am using WINE-0.9.2 and wine is installed by downloading the wine source code from winehq.org Is it a known issue (or ) Do I need to do any additional configuration setting to work with Intel Xeon processor ? Any suggestions please Thank you Ajay

1 0

Directx 8 and wined3d
by Christian Gmeiner Feb. 9, 2006

Feb. 9, 2006

Hi all. I have here a directx 8 game - first splinter cell - and i get this fixme: fixme:d3d_surface:IDirect3DSurface8Impl_UnlockRect Unsupported Format 22 in locking func So i looked at wine source and found out that format 22 (WINED3DFMT_X8R8G8B8) is supported in wined3d. Will directx8 converted to use wined3d or is it a good idea to write a patch for it? Thanks, Chiristian -- Christian Gmeiner - student of computer science http://dxr3plugin.sf.net http://itb04.ath.cx

2 3

dx9 and shaders
by Coleman Kane Feb. 9, 2006

Feb. 9, 2006

Hi, What is the status on Shader support for DX9 in the latest WINE cvs, and the future projections of support in this area? I am working on a transition project, and am curious how far off support for this is in the WINE project, and perhaps where work needs to be done. Are there any people organizing this effort here? -- Coleman Kane

8 15

[wined3d] support for WINED3DFMT_A8B8G8R8
by Christoph Frick Feb. 9, 2006

Feb. 9, 2006

attempt #3: this patch fixes several texture bugs with the demos of OGRE. License: LGPL ChangeLog: 2006-02-08 Christoph Frick <rid(a)zefix.tv> - dlls/wined3d/utils.c support for WINED3DFMT_A8B8G8R8 -- cu Index: dlls/wined3d/utils.c =================================================================== RCS file: /home/wine/wine/dlls/wined3d/utils.c,v retrieving revision 1.18 diff -u -r1.18 utils.c --- dlls/wined3d/utils.c 23 Nov 2005 19:29:20 -0000 1.18 +++ dlls/wined3d/utils.c 8 Feb 2006 12:23:00 -0000 @@ -35,6 +35,7 @@ FMT_TO_STR(WINED3DFMT_UNKNOWN); FMT_TO_STR(WINED3DFMT_R8G8B8); FMT_TO_STR(WINED3DFMT_A8R8G8B8); + FMT_TO_STR(WINED3DFMT_A8B8G8R8); FMT_TO_STR(WINED3DFMT_X8R8G8B8); FMT_TO_STR(WINED3DFMT_R5G6B5); FMT_TO_STR(WINED3DFMT_X1R5G5B5); @@ -1611,6 +1612,7 @@ case WINED3DFMT_A4R4G4B4: retVal = GL_RGBA4; break; case WINED3DFMT_X4R4G4B4: retVal = GL_RGB4; break; case WINED3DFMT_A8R8G8B8: retVal = GL_RGBA8; break; + case WINED3DFMT_A8B8G8R8: retVal = GL_RGBA8; break; case WINED3DFMT_A2R10G10B10: retVal = GL_RGBA8; break; case WINED3DFMT_X8R8G8B8: retVal = GL_RGB; break; /* to see */ @@ -1676,6 +1678,7 @@ case WINED3DFMT_A4R4G4B4: retVal = GL_BGRA; break; case WINED3DFMT_X4R4G4B4: retVal = GL_BGRA; break; case WINED3DFMT_A8R8G8B8: retVal = GL_BGRA; break; + case WINED3DFMT_A8B8G8R8: retVal = GL_RGBA; break; case WINED3DFMT_A2R10G10B10: retVal = GL_BGRA; break; case WINED3DFMT_X8R8G8B8: retVal = GL_BGRA; break; /* to see */ @@ -1738,6 +1741,7 @@ case WINED3DFMT_A4R4G4B4: retVal = GL_UNSIGNED_SHORT_4_4_4_4_REV; break; case WINED3DFMT_X4R4G4B4: retVal = GL_UNSIGNED_SHORT_4_4_4_4_REV; break; case WINED3DFMT_A8R8G8B8: retVal = GL_UNSIGNED_INT_8_8_8_8_REV; break; + case WINED3DFMT_A8B8G8R8: retVal = GL_UNSIGNED_INT_8_8_8_8_REV; break; case WINED3DFMT_A2R10G10B10: retVal = GL_UNSIGNED_INT_2_10_10_10_REV; break; case WINED3DFMT_X8R8G8B8: retVal = GL_UNSIGNED_INT_8_8_8_8_REV; break; /* to see */ @@ -1781,6 +1785,7 @@ case WINED3DFMT_A4R4G4B4: retVal = 2; break; case WINED3DFMT_X4R4G4B4: retVal = 2; break; case WINED3DFMT_A8R8G8B8: retVal = 4; break; + case WINED3DFMT_A8B8G8R8: retVal = 4; break; case WINED3DFMT_A2R10G10B10: retVal = 4; break; case WINED3DFMT_X8R8G8B8: retVal = 4; break; /* Paletted */

3 3

Fwd: game "Knights and Merchants" deadlocks
by James Trotter Feb. 9, 2006

Feb. 9, 2006

On 2/4/06, Joris Huizer <jorishuizer(a)planet.nl> wrote: > > Hello, > > I have this question: I have a game called "Knights and Merchants" which > I sometimes play; I find it deadlocks each time after playing for an > hour or so > it seems it isn't a complete deadlock, sometimes some of sound comes > through between intervals of minutes or so; harddisk activity seems > extreme - the light is burning constantly. > I then usually decide to kill the program; as it opens fullscreen I > can't get to the xterm that launched it, so I try to get to a console; > The system is so slow that it takes some time to get to a console > <ctrl-alt-f1>, and login in may time out a few times before finaly > getting in (the cure to that one is simple: login before starting the > game...) - then it takes another minute or so to run ps and kill the > wine process > > is there a way to find what is causing the deadlock? I can log the > output wine gives using `script`, but as deadlocks only occur after a > lot of time running the game with lots of logging active would be a pain > > will log the output at least next time I play; for now, has somebody > ideas how to log without getting major slowdown (otherwise there's no > playing in it)? > > thanks, > > Joris > > > This really sounds like a memory leak to me. Usually I'd use valgrind ( http://valgrind.org/) to find memory leaks and such. Valgrind 3.1.0 works with wine, but it produces alot of output you'd have to look through and the program will run insanely slow. It might be worth a try.

3 6

Re: Wine and Intel Macs
by Steven Edwards Feb. 9, 2006

Feb. 9, 2006

Hi, On 2/8/06, Eric W. Triplett <ewt(a)ufl.edu> wrote: > Does Wine work with the new Macs that contain Intel processors? If > so, which distribution should I download and install? It should compile out of the box. Beware you may need a few patches from the darwine mailing list to get some win32 apps running. -- Steven Edwards "There is one thing stronger than all the armies in the world, and that is an idea whose time has come." - Victor Hugo

1 0

Somewhat disappointing experiences with Winelib and WTL
by Claus Fischer Feb. 8, 2006

Feb. 8, 2006

Hi Wine developers and users! Over the last few days, I have been trying to find out whether the combination of WTL and Winelib could be a promising inter-platform GUI solution. While I have made some progress and got some new knowledge, I believe I have now come to a dead end where I'll have to give up that attempt. In case you are interested, here's my summary report. It might be useful to others. Regards, Claus *********************************************************** The Goal: ********* WTL on Windows gives me: - compact executables: small and fast - easy-to-install executables: no DLLs needed - programs easy to maintain and deploy - mature GUI The goal is to combine WTL/ATL (no COM) with Winelib to create a Linux-application with the same look and feel and roughly the same qualities: no DLL's, shared libraries, C++ ABI hassles, etc. Just one binary linked to libc. 1. ATL/WTL ********** ATL 3.0 (from my MSVC 6 compiler) and WTL 7.5 (from sourceforge) can be made to work. Issues are: - GCC 4 is very picky with templates and would need lots of template prototypes; I have used GCC 3.3.5 - Some template prototypes are still needed - Some MSVC-specific pragmas etc. need to be ifdef'd - A few pack pragmas need to be replaced by Wine's pack headers - Everything related to _get_uuid(class) I've commented out; I need no COM stuff - Some GCC warnings need to be turned off, or alternatively code changes need to be made - Various small changes - As more parts of WTL get used (i.e. instantiated), more changes will be required Basically, ATL+WTL can reach a state where they compile with GCC 3 and the changes are still mostly cosmetic. Some of the changes might even be incorporated in the official WTL, now that it's free. I have read the mails of Boaz Harrosh' previous changes; apparently he has had to invest much more work because of COM. With the modified ATL/WTL, I was able to compile the wizard-created sample SDI application on Linux. 2. Winelib "as is" ****************** After some digging through the Web, I've been able to link the sample SDI application against Winelib. It took somewhat longer than it should have due to (a) WTL's habit of just ATLASSERT()ing things and (b) the rather elaborate work of finding those places with wine-dbg and/or ATLTRACE()s plus WINEDEBUG=+relay. Since I'm not familiar with the Wine debugger, it would have been very helpful to be able to use gdb on the resulting executable. However, gdb reported that it didn't know the file format. ==> Wishlist to Wine: - Make gdb work on Winelib programs - Document Winelib and the build process better (the documentation is outdated, though the tools are good). All in all a reasonably successful endeavour, and the application runs stable and looks fine except for the font (that probably can be configured better). BUT: ... BIG SHOCK: That's not a single ELF executable, it's a weird mixture of PE and ELF and a .so file and a wrapper program that apparently starts wine in the background ... That doesn't fulfill my goals of building a native Linux exe with no dependencies except libc. It's also quite slow when loading. 3. Winelib statically linked **************************** Apparently Wine has made a decision a few years ago: that support for native Windows apps with all the infrastructure they need (Wine server, registry, resources, multithreading, etc.) is more important than support for porting applications to native Linux apps. That decision is obviously correct, given the large number of Windows applications that are only available as binaries and require much infrastructure. I'm aware of that, but I've still decided to give my dream of a native Linux app a try. I tried the following method: (a) Get and compile Wine 0.9.7 (b) Add rules to Makedll.rules to pack the objects into .a libraries (c) Attempt to link my program's objects against those static libs (d) Make changes and corrections and repeat I first made a reduced WTL application that does not use a resource file. I don't know if this was a good decision. The following changes were necessary to Wine: - Comment out a lot of DLLMain functions - Comment out some 16-bit functions that have name collisions - Turn on debug mode (-O0 -g) - Write a startup function main() (Wine's libwinecrt0.a didn't work for me) That might be the reason for more trouble - Link to all of libs/unicode - Link to some objects in libs/wine (I didn't link to loader, don't know if that's good) This is where the heavy trouble started: - Replace the assembly stuff in critical sections (due to the debug mode) ... my app is single-threaded - Somehow set up code pages for ansi/Unix (LocaleInit() failed, see below) - Comment out some calls to the registry where the run-time environment is registered What eventually caused me to stop is: - Somehow fake Wine Server or do the equivalent stuff or just jump over (Basically Register Class as atoms) - Somehow fake a lot of initial resources (E.g. GetSystemCursor etc.) - Overall too many modifications in interacting systems - Altogether not a "robust" feeling This is where I stopped. I don't know whether I'm "so close" or miles away, but my random code editing seemed to get out of hand. 4. What is needed ***************** What would be needed to support static linking against Winelib (if that's decided to be a supportworthy goal): - Infrastructure to build static libs - separate out DllMain - separate out some 16 bit functions - Possibility to provide heap based allocation through straight malloc() - Infrastructure to fake loading resources (for those resources that come from Winelib/system) - Infrastructure for proper initialization of modules e.g. through one setup function for each DLL and one common setup function that calls the others in some natural order The overall initialization function should be configurable so that programs that need only a few DLL's (user, gdi, crtdll, kernel, ntdll) don't need to link everything - Infrastructure to allow faking registry calls for those calls initiated by Winelib internal stuff (and possibly also ATL/WTL internal stuff) - Infrastructure to handle Window class registration etc. (i.e. reduced Wine server support in the app) What I specifically don't need/want through Winelib: - networking - filesystem access - loading of external DLL's or other libraries - C++ runtime library support *********************************************************** This is, in keywords, my experience with WTL and static Winelib linking. I'll be apreciative of any responses. Please CC: my mail address. Also, if anyone is interested in hosting patches to ATL/WTL or even just looking at them, I'll gladly provide them. Regards, Claus -- Claus Fischer <claus.fischer(a)clausfischer.com> http://www.clausfischer.com/

6 10

Wine and Intel Macs
by Eric W. Triplett Feb. 8, 2006

Feb. 8, 2006

Does Wine work with the new Macs that contain Intel processors? If so, which distribution should I download and install? Thanks, Eric -- ___________________________________________ Professor Eric W. Triplett, Chair Department of Microbiology and Cell Science Institute of Food and Agricultural Sciences University of Florida P.O. Box 110700 Gainesville, FL 32611-0700 1-352-392-5430 (phone) 1-352-392-5922 (fax) ewt(a)ufl.edu ___________________________________________

1 0

gethostbyname call with 0 length arg
by Phil Goss Feb. 8, 2006

Feb. 8, 2006

Hi, Is it a bug in the WINE gethostbyname (WS_gethostbyname) implementation, where if the arg name is of string length 0, then it returns unsuccessful. I have experience this issue with a Windows program (Onkyo Nettune) where the hostname passed to gethostbyname is of length 0. (This seems to be a bug in the program itself). However, the program works okay in native Windows. There seems to be a check in the gethostbyname for a NULL arg name ... if(!name) ... But no check for ... if(!strlen(name)) .... I have tested the strlen check and it seems to work and satisfies the Windows program. Does the above make sense, as I am not a programmer? Not sure if this s bug in wine even though it implementation should be matching Windows native. Thanks, Phil -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

4 9