- Wine-Devel - list.winehq.org

What is the proper value for ACM_DRIVERADDF_NAME?
by Alex Villacís Lasso Jan. 2, 2006

Jan. 2, 2006

I am working on a set of patches for msacm, and I want to add support for ACM_DRIVERADDF_NAME. The problem is that Wine does not have a definition for this value, which is supposed to be used in acmDriverAdd[AW]. It does not appear in any header of MSVC either. I searched MSDN and Google, and it does not appear either. MSDN mentions its use, but does not mention its specific value. Has anybody seen the value for this definition, and if so, can you please forward it to me? Thanks in advance. BTW, what happened to the two MSACM patches sent in December 28? Alex Villacís Lasso

2 2

Re: There is no point to specify both MEM_RESERVE and MEM_COMMIT for VirtualAlloc
by Vitaliy Margolen Jan. 2, 2006

Jan. 2, 2006

Monday, January 2, 2006, 1:23:22 AM, Dmitry Timoshkov wrote: > Changelog: > Dmitry Timoshkov <dmitry(a)codeweavers.com> > There is no point to specify both MEM_RESERVE and MEM_COMMIT for > VirtualAlloc. According to MSDN: "To reserve and commit pages in one step, call VirtualAlloc with MEM_COMMIT | MEM_RESERVED. The function fails if you attempt to commit a page that has not been reserved. The resulting error code is ERROR_INVALID_ADDRESS." Why do you want to do something that _should_ fail? Vitaliy Margolen

2 1

Self-extracting zips do not extract themselves
by Ivan Gyurdiev Jan. 2, 2006

Jan. 2, 2006

> err:virtual:map_image Image was mapped at 0x49910000: standard load address for a Win32 program (0x00400000) not available > err:virtual:map_image Do you have exec-shield or prelink active? > wine: could not load L"H:\\nfsmw\\nfsmwdemo.exe" as Win32 binary Yes I do, is that bad? Should I file a bugzilla (or do something else to help resolve this issue)?

1 0

D3DX9 SDK releases, DLL support (CIV4)
by Andrei Barbu Jan. 2, 2006

Jan. 2, 2006

Hi, I've been playing with getting CIV4 to run on wine. http://appdb.winehq.org/appview.php?versionId=3632&iTestingId=125 I'm left with just one issue. D3DX9_26.DLL is missing. This is a D3D9 SDK release (they put one out every month or so from what I've seen, with a new DLL that has the number incremented). It's mostly like the original with some minor changes. How would I support this in wine? I don't know the wine build system enough to extend it to do this. Is there a nice way to generate these DLLs and to include the d3dx9 dll so I just have to add in/fix missing calls? This may not be an issue now, but as more and more games get released more will depend on these dlls. Thanks, Andrei

5 5

Running GUI test automation tools with Wine?
by Dan Kegel Jan. 2, 2006

Jan. 2, 2006

Do any Windows GUI test automation tools run under Wine yet? I've tried two from the list at http://tejasconsulting.com/open-testware/feature/gui-test-driver-survey.html so far, but they both had issues: http://bugs.winehq.org/show_bug.cgi?id=4209 (tester 3 can't record) http://bugs.winehq.org/show_bug.cgi?id=4211 (autoit3 can't play back) It's kind of demanding to expect this kind of application to work properly, since it really gets under the hood of Windows, but Wine has progressed to the point where maybe it's not unrealistic. And I can think of no better way to help ISVs get their apps running on Wine than to get their regression test runner working on Wine! <insert obligatory monkeyboy reference here> - Dan -- Wine for Windows ISVs: http://kegel.com/wine/isv

1 1

Question about X11DRV_ChoosePixelFormat glXChooseFBConfig returns NULL (glError: 0)
by L. Lenders Jan. 2, 2006

Jan. 2, 2006

Just for the info: after some digging i found a quick hack to get rid of the error: comment line 208 in dlls/x11drv/opengl.c: //TEST_AND_ADD1(ppfd->dwFlags & PFD_STEREO, GLX_STEREO); Somehow setting the PFD_STEREO flag makes doom3 crash and triggers the error mentioned in the subject. After commenting line 208 doom3 starts up just fine. Digging further..... :) (any help appreciated) Louis ___________________________________________________________ To help you stay safe and secure online, we've developed the all new Yahoo! Security Centre. http://uk.security.yahoo.com

5 6

Registry entries for serial ports not created
by Pavel Troller Jan. 2, 2006

Jan. 2, 2006

Hi! I was trying to utilize a program for updating mobile phone's firmware (for Siemens/Benq mobiles, just an original app with encapsulated firmware image). This program immediately told that there are no serial ports present in my machine and terminated. After a bit of seeking in my own memory and wine list mail archive I remembered that there should be some registry entries which a program can examine and get some basic info about the ports. In an old mail I found something, which I converted to the following registry entry and put to system.reg file: [Hardware\\Devicemap\\Serialcomm] 1015709345 "Serial0"="COM1" "Serial1"="COM2" "Serial2"="COM3" "Serial3"="COM4" I think this should go to the standard system.reg by default, maybe in the reduced form with just the first two ports. Together with correct links in .wine/dosdevices, it makes that the program can really find the port. And at the end: How to create such a registry entry by wine's regedit ? I've spent about 15 minutes trying to do so but I've failed and then edited the file manually. Any attempt to create a "folder" called Serialcomm in Hardware\\Devicemap was unsuccessfull; I didn't find how to create a "folder" for keys, and using "Add key" menu entry I always got an error dialog saying "A subkey must be volatile". What does it mean ? With regards, Pavel Troller

2 2

MSVC compilation of DLLs
by Rolf Kalbermatter Jan. 1, 2006

Jan. 1, 2006

I was just looking to get some of the Wine DLLs compiled under Visual C and run into a number of problems. First msvcmaker seems to only create a wine.dsp file in the loader directory but rather should do that in the libs/wine directory instead it would seem to me. Second it also should create a wine_unicode.dsp project in libs/unicode which it doesn't do at all. I created my own wine.dsp file to create a wine.lib file but run into new problems. First the DECLSPEC_NORETURN position in following declaration does not work with Visual C. It does want the DECLSPEC_NORETURN before the entire function declaration and not before the function pointer name. This: struct wine_pthread_functions { void (*init_process)( const struct wine_pthread_callbacks *callbacks, size_t size ); void (*init_thread)( struct wine_pthread_thread_info *info ); int (*create_thread)( struct wine_pthread_thread_info *info ); void (*init_current_teb)( struct wine_pthread_thread_info *info ); void * (*get_current_teb)(void); void (* DECLSPEC_NORETURN exit_thread)( struct wine_pthread_thread_info *info ); void (* DECLSPEC_NORETURN abort_thread)( long status ); }; should get: struct wine_pthread_functions { void (*init_process)( const struct wine_pthread_callbacks *callbacks, size_t size ); void (*init_thread)( struct wine_pthread_thread_info *info ); int (*create_thread)( struct wine_pthread_thread_info *info ); void (*init_current_teb)( struct wine_pthread_thread_info *info ); void * (*get_current_teb)(void); DECLSPEC_NORETURN void (* exit_thread)( struct wine_pthread_thread_info *info ); DECLSPEC_NORETURN void (* abort_thread)( long status ); }; to compile, but probably won't work for the GNU_C declaration of this macro, or does it? The next problem are the use of BINDIR and DLLDIR in config.c and loader.c respectively. What are those and do they have any function under a Windows compile of these files? Should those parts of the files simply be excluded for such a compile, or are they not necessary at all? Rolf Kalbermatter

1 0

Compiling test application (Notepad) with winelib - executeable segfaults
by Richard Wild Jan. 1, 2006

Jan. 1, 2006

Hi all, I was trying to compile the test application (Notepad) with winelib to get a feel for how to use it. I followed the instructions in your docs, but ended up with a target file notepad2.exe.so. The instructions imply that I should end up with an executable called notepad2, since they tell me to run it. If I run the .so file it segfaults, so I assume it really is a shared library and not just an executable with a funny name. I want to understand what I've done wrong here, because if I can't get this right I certainly won't be able to port anything complicated. I'm sorry if this has been asked often before, but I couldn't find an easy way of searching the mailing list. I am using WINE-0.9.4 built by Adam Schreiber for Slackware 10.2. Regards, Rich. P.S. Here is my output (so you can see exactly what I did): rich(a)radhagovinda:/usr/local/src/wine-0.9.4/programs/notepad2$ winemaker --lower-uppercase . Winemaker 0.6.0 Copyright 2000 Francois Gouget <fgouget(a)codeweavers.com> for CodeWeavers Scanning the source directories... Fixing the source files... License_En.c dialog.c license.c main.c Bg.rc Cs.rc Da.rc De.rc En.rc Es.rc Fi.rc Fr.rc Hu.rc It.rc Ja.rc Ko.rc Nl.rc No.rc Pl.rc Pt.rc Ru.rc Si.rc Sk.rc Sw.rc Th.rc Wa.rc Zh.rc rsrc.rc dialog.h license.h main.h notepad_res.h Generating project files... . rich(a)radhagovinda:/usr/local/src/wine-0.9.4/programs/notepad2$ make winegcc -c -mno-cygwin -I. -o License_En.o License_En.c winegcc -c -mno-cygwin -I. -o dialog.o dialog.c winegcc -c -mno-cygwin -I. -o license.o license.c winegcc -c -mno-cygwin -I. -o main.o main.c wrc -I. -foBg.res Bg.rc Bg.rc:21:24: Error: parse error make: *** [Bg.res] Error 1 rich(a)radhagovinda:/usr/local/src/wine-0.9.4/programs/notepad2$ vi Makefile reading Makefile wrote Makefile, 110 lines, 2368 chars rich(a)radhagovinda:/usr/local/src/wine-0.9.4/programs/notepad2$ make wrc -I. -forsrc.res rsrc.rc winegcc -mwindows -mno-cygwin -o notepad2.exe.so License_En.o dialog.o license.o main.o rsrc.res -lodbc32 -lole32 -loleaut32 -lwinspool -luuid rich(a)radhagovinda:/usr/local/src/wine-0.9.4/programs/notepad2$ ll total 520 -rw-r--r-- 1 rich users 5303 2006-01-01 21:02 Bg.rc -rw-r--r-- 1 rich users 5257 2006-01-01 21:02 Cs.rc -rw-r--r-- 1 rich users 5228 2006-01-01 21:02 Da.rc -rw-r--r-- 1 rich users 5495 2006-01-01 21:02 De.rc -rw-r--r-- 1 rich users 5282 2006-01-01 21:02 En.rc -rw-r--r-- 1 rich users 5625 2006-01-01 21:02 Es.rc -rw-r--r-- 1 rich users 4693 2006-01-01 21:02 Fi.rc -rw-r--r-- 1 rich users 5369 2006-01-01 21:02 Fr.rc -rw-r--r-- 1 rich users 5388 2006-01-01 21:02 Hu.rc -rw-r--r-- 1 rich users 5513 2006-01-01 21:02 It.rc -rw-r--r-- 1 rich users 5431 2006-01-01 21:02 Ja.rc -rw-r--r-- 1 rich users 5396 2006-01-01 21:02 Ko.rc -rw-r--r-- 1 rich users 1331 2006-01-01 21:02 License_En.c -rw-r--r-- 1 rich users 2040 2006-01-01 21:02 License_En.o -rw-r--r-- 1 rich users 2368 2006-01-01 21:03 Makefile -rw-r--r-- 1 rich users 5268 2006-01-01 21:02 Nl.rc -rw-r--r-- 1 rich users 5170 2006-01-01 21:02 No.rc -rw-r--r-- 1 rich users 5398 2006-01-01 21:02 Pl.rc -rw-r--r-- 1 rich users 7642 2006-01-01 21:02 Pt.rc -rw-r--r-- 1 rich users 5288 2006-01-01 21:02 Ru.rc -rw-r--r-- 1 rich users 5230 2006-01-01 21:02 Si.rc -rw-r--r-- 1 rich users 4676 2006-01-01 21:02 Sk.rc -rw-r--r-- 1 rich users 5251 2006-01-01 21:02 Sw.rc -rw-r--r-- 1 rich users 4517 2006-01-01 21:02 Th.rc -rw-r--r-- 1 rich users 5256 2006-01-01 21:02 Wa.rc -rw-r--r-- 1 rich users 5179 2006-01-01 21:02 Zh.rc -rw-r--r-- 1 rich users 22737 2006-01-01 21:02 dialog.c -rw-r--r-- 1 rich users 1754 2006-01-01 21:02 dialog.h -rw-r--r-- 1 rich users 14472 2006-01-01 21:02 dialog.o -rw-r--r-- 1 rich users 1321 2006-01-01 21:02 license.c -rw-r--r-- 1 rich users 1528 2006-01-01 21:02 license.h -rw-r--r-- 1 rich users 984 2006-01-01 21:02 license.o -rw-r--r-- 1 rich users 12222 2006-01-01 21:02 main.c -rw-r--r-- 1 rich users 1722 2006-01-01 21:02 main.h -rw-r--r-- 1 rich users 9388 2006-01-01 21:02 main.o -rwxr-xr-x 1 rich users 165396 2006-01-01 21:03 notepad2.exe.so -rw-r--r-- 1 rich users 2629 2006-01-01 21:02 notepad_res.h -rw-r--r-- 1 rich users 1813 2006-01-01 21:02 rsrc.rc -rw-r--r-- 1 rich users 65612 2006-01-01 21:03 rsrc.res rich(a)radhagovinda:/usr/local/src/wine-0.9.4/programs/notepad2$ ./notepad2.exe.so Segmentation fault

2 2

SPARC assembly won't compile, problems with NT headers
by Troy Rollo Jan. 1, 2006

Jan. 1, 2006

winegcc from the current WineHQ produces assembly output for SPARC systems that cannot be processed by the assembler. 1. "operation combines symbols in different segments" error. This problem arises because the imports code attempts to generate a relocation involving symbols in different segments (one in the text segment and one in the data segment). SPARC assemblers (including gas on a SPARC) cannot deal with relocations involving symbols in different segments. This only affects position independent code and can be avoided by changing the assembly code output in imports.c to something simpler. 2. "can't resolve `_end' {*UND* section} - `.L__wine_spec_rva_base' {.data section}" This problem is more sinister. It arises from the same limitation as the first problem, but is not susceptible to being worked around. The offending code is the code that attempts to generate the NT header of the executable - specifically the SizeOfImage element. I can't see any way at this point to provide for this calculation to be done until after the linker output is generated. I suspect the solution to this problem is to just output a zero in this location and have winegcc modify the executable image to insert the correct values after the linker has created it. Does anybody have any objections to this solution or another approach to suggest? -- Troy Rollo - wine(a)troy.rollo.name

7 13