- Wine-Devel - list.winehq.org

dreamweaver 4
by tom Aug. 21, 2002

Aug. 21, 2002

Hello, I installed Dreamweaver 4 today and I get this message in my log start log -------- Wed Aug 21 01:14:58 2002, starting [/home/tom/cxoffice/bin/wine --] C:/Program Files/Macromedia/Dreamweaver 4/Dreamweaver.exe Use of uninitialized value in pattern match (m//) at /home/tom/cxoffice/bin/wine line 890. fixme:xrender:X11DRV_XRender_Finalize Free cached glyphsets stop log ------------ So does anyone here know what I need to do to fix this ? Or a work around ? It looks as if it needs a hack on line 890 ??? Tom -- 'extraordinary claims require extraordinary evidence' -Carl Sagan."

1 0

pdb symbols
by Fabian Cenedese Aug. 20, 2002

Aug. 20, 2002

Hi I try to debug my MSVC-application, consisting of an exe and several dlls. When I start it in WineDBG it tells my that it can't find symbol information for my files. I tried having debug info in .pdb files as well as included in the linked files but nothing worked. How can I give WineDBG the symbol information? When it stops on an exception it prints me the stack trace, sometimes even with function names but I strongly suspect that the shown info is wrong now. I'm using Wine 20020605. Thanks Fabi

2 1

Another font question
by Spanke, Alexander Aug. 20, 2002

Aug. 20, 2002

Hi again, In which file, what option is to set the used Font ? I play with the config-file, the system.reg but nothing changed, in the application i define no special font, so i want it change over the configuration. But how ? I will kick this machine to the moon ! Or the programmer of the Application. Thnx / regards Alex

1 0

Unmanaged window focus problem
by Brad Campbell Aug. 20, 2002

Aug. 20, 2002

G'day all, I have been battling with this for a while and would appreciate the guidance of someone who knows the x11 driver better.. At http://www.wasp.net.au/~brad/test3.tgz there is a simple program that will demonstrate the error on wine with managed set to N in the config file. File is compiled with Borland Delphi 4 and includes full source for the paranoid/interested. The problem seems to be the same as most dialog box problems I encounter in managed or unmanaged mode. The program opens a small form, then after 1 second it opens a second form in modal format. The second form is focused above the first form as it should be. After another second the second form closes and the first form is again focused correctly. A third form opens and is given focus, but the first form remains the top form where the third form should be on top. In normal applications, particularly full screen ones, this means the dialog box that gets opened and focused is underneath the main window and can't be accessed. If I'm in unmanaged mode, usually I have to kill wine from a console to get control back. I have looked at a +x11drv,+timer,+message trace and found that when the third form opens, it focuses correctly however something causes the original form to then stack on top of the third form. If I only use two forms, and open/close the second one twice this does not occur. It only seems to happen when at least three diffenent windows are present. A good example. You go to quit a program and it pops up a dialog asking you if you want to save your work. When you click yes, the question dialog closes and a save file selector opens. The save file selector is focused but stacked underneath the main window and you can't get to it. In managed mode I can get to it by windowshading the main window, but in unmanaged mode I'm stuck. I have been poking around in dlls/x11drv/winpos.c but I'm having a bit of trouble following things. Unfortunately C is not my native language and so it's taking me a while to get a grasp. Thanks for any pointers.. -- Brad.... /"\ Save the Forests \ / ASCII RIBBON CAMPAIGN Burn a Greenie. X AGAINST HTML MAIL / \

1 0

Wine and the fonts
by Spanke, Alexander Aug. 19, 2002

Aug. 19, 2002

Hi, Ii try to start an application with wine, but the fonts used by the application are terrible. So i changed the default - entry in the config - file to change the font. Nothing changed :( I don't want any special font, only a simple mono font, how can i get it ? Reagrds Alex

1 0

[breakage] Set the correct permissions on the PE image sections.
by Uwe Bonnes Aug. 18, 2002

Aug. 18, 2002

Hallo, the patch http://cvs.winehq.com/patch.py?id=1027987166850574216879071 "Set the correct permissions on the PE image sections" breaks the propsheet handling on the xilinx webpack suite. When a propsheet should be opened, appended backtrace appears. PROPSHEET_CreatePage writes to ppshpage->u.pResource when PSP_DLGINDIRECT is set. MSDN also tells that applications will break if pResource is not writable. It seems that above patch maps the resource section write protected. Info segments doesn't tell about a range including 0x00467390, info maps tells about VirtualQueryEx Unsupported . Bye -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ---------- First chance exception: page fault on write access to 0x00467390 in 32-bit code (0x408c888c). Register dump: CS:0023 SS:002b DS:002b ES:002b FS:008f GS:0000 EIP:408c888c ESP:405c6080 EBP:405c60c4 EFLAGS:00010202( R- 00 I - - 1 ) EAX:40000440 EBX:409203dc ECX:00000000 EDX:4092021d ESI:00467390 EDI:41552098 Stack dump: 0x405c6080 (_end+0x117800): 409203dc 00000000 00000000 00010056 0x405c6090 (_end+0x117810): 405c60c4 00000000 00010056 0000130c 0x405c60a0 (_end+0x117820): 00000000 41552070 00000000 ffffffff 0x405c60b0 (_end+0x117830): 405c60c0 409203dc 4092021d 00000000 0x405c60c0 (_end+0x117840): 00000000 405c6108 408c9587 00020051 0x405c60d0 (_end+0x117850): 00000000 40400788 41552098 409203dc 0x405c60e0 (_end+0x117860): 0011: sel=008f base=4010f1c0 limit=00000fff 32-bit rw- Backtrace: =>0 0x408c888c (PROPSHEET_CreatePage+0xec(hwndParent=0x20051, index=0x0, psInfo=0x40400788, ppshpage=0x41552098) [propsheet.c:1239] in comctl32.dll.so) (ebp=405c60c4) 1 0x408c9587 (PROPSHEET_SetCurSel+0x127(hwndDlg=0x20051, index=0x0, skipdir=0x1, hpage=0x41552098) [propsheet.c:1773] in comctl32.dll.so) (ebp=405c6108) 2 0x408cabc0 (PROPSHEET_DialogProc+0x320(hwnd=0x20051, uMsg=0x110, wParam=0x10052, lParam=0x40400788) [propsheet.c:2591] in comctl32.dll.so) (ebp=405c6330) 3 0x40755cfb (WINPROC_wrapper+0x17 in user32.dll.so) (ebp=405c6354) 4 0x40755d9f (WINPROC_CallWndProc+0x8f(proc=0x408ca8a0, hwnd=0x20051, msg=0x110, wParam=0x10052, lParam=0x40400788) [winproc.c:183] in user32.dll.so) (ebp=405c6384) 5 0x4075c3b7 (CallWindowProcW+0xa7(func=0x414012f8, hwnd=0x20051, msg=0x110, wParam=0x10052, lParam=0x40400788) [winproc.c:2836] in user32.dll.so) (ebp=405c63ac) 6 0x4072ce71 (DefDlgProcW+0x51(hwnd=0x20051, msg=0x110, wParam=0x10052, lParam=0x40400788, hwnd=0x20051) [defdlg.c:405] in user32.dll.so) (ebp=405c63d8) 7 0x40755cfb (WINPROC_wrapper+0x17 in user32.dll.so) (ebp=405c63fc) 8 0x40755d9f (WINPROC_CallWndProc+0x8f(proc=0x4072ce20, hwnd=0x20051, msg=0x110, wParam=0x10052, lParam=0x40400788) [winproc.c:183] in user32.dll.so) (ebp=405c642c) 9 0x4075bd26 (WINPROC_CallProc32ATo32W+0xc6(func=0x4072ce20, hwnd=0x20051, msg=0x110, wParam=0x10052, lParam=0x40400788) [winproc.c:2592] in user32.dll.so) (ebp=405c6458) 10 0x4075c2d7 (CallWindowProcA+0xa7(func=0x414001f6, hwnd=0x20051, msg=0x110, wParam=0x10052, lParam=0x40400788) [winproc.c:2800] in user32.dll.so) (ebp=405c6480) 11 0x5f446f6b (MFC42.DLL.?DefWindowProcA(a)CWnd@@MAEJIIJ(a)Z+0x42 in I:\XILINX\MFC\MFC42.DLL) (ebp=405c64a0) 12 0x5f446603 (MFC42.DLL.?Default(a)CWnd@@IAEJXZ+0x25 in I:\XILINX\MFC\MFC42.DLL) (ebp=405c64f4) 13 0x0042b8ef (_pn.exe.??4RticStore@@QAEAAV0(a)ABV0@@Z+0xa8af in I:\xilinx\bin\nt\_pn.exe) (ebp=405c6594) 14 0x5f447664 (MFC42.DLL.?WindowProc(a)CWnd@@MAEJIIJ(a)Z+0x45 in I:\XILINX\MFC\MFC42.DLL) (ebp=405c65bc) 15 0x5f446546 (MFC42.DLL.?AfxCallWndProc@@YGJPAVCWnd@@PAUHWND__@@IIJ(a)Z+0x90 in I:\XILINX\MFC\MFC42.DLL) (ebp=405c661c) 16 0x5f446749 (MFC42.DLL.?AfxWndProc@@YGJPAUHWND__@@IIJ(a)Z+0x2b in I:\XILINX\MFC\MFC42.DLL) (ebp=405c6638) 17 0x5f46f12b (MFC42.DLL.?AfxWndProcBase@@YGJPAUHWND__@@IIJ(a)Z+0x39 in I:\XILINX\MFC\MFC42.DLL) (ebp=405c6664) 18 0x40755cfb (WINPROC_wrapper+0x17 in user32.dll.so) (ebp=405c6688) 19 0x40755d9f (WINPROC_CallWndProc+0x8f(proc=0x5f46f0f2, hwnd=0x20051, msg=0x110, wParam=0x10052, lParam=0x40400788) [winproc.c:183] in user32.dll.so) (ebp=405c66b8) 20 0x4075c26b (CallWindowProcA+0x3b(func=0x5f46f0f2, hwnd=0x20051, msg=0x110, wParam=0x10052, lParam=0x40400788) [winproc.c:2781] in user32.dll.so) (ebp=405c66e0) 21 0x4076bd00 (call_window_proc+0x100(hwnd=0x20051, msg=0x110, wparam=0x10052, lparam=0x40400788, unicode=0x0) [message.c:1372] in user32.dll.so) (ebp=405c6730) 22 0x4076c9d9 (SendMessageTimeoutA+0xe9(hwnd=0x20051, msg=0x110, wparam=0x10052, lparam=0x40400788, flags=0x0, timeout=0xffffffff, res_ptr=0x405c67b8, hwnd=0x20051) [message.c:1784] in user32.dll.so) (ebp=405c6788) 23 0x4076cb59 (SendMessageA+0x39(hwnd=0x20051, msg=0x110, wparam=0x10052, lparam=0x40400788) [message.c:1829] in user32.dll.so) (ebp=405c67bc) 24 0x40730695 (DIALOG_CreateIndirect+0x525(hInst=0x0, dlgTemplate=0x41552244, owner=0x20025, dlgProc=0x408ca8a0, param=0x40400788, procType=0x3, modal=0x0, hwnd=0x20025) [dialog.c:860] in user32.dll.so) (ebp=405c683c) 25 0x40730a6f (CreateDialogIndirectParamW+0x2f(hInst=0x0, dlgTemplate=0x415521e8, owner=0x20025, dlgProc=0x408ca8a0, param=0x40400788) [dialog.c:1011] in user32.dll.so) (ebp=405c686c) 26 0x408c7adc (PROPSHEET_CreateDialog+0xfc(psInfo=0x40400788) [propsheet.c:581] in comctl32.dll.so) (ebp=405c6898) 27 0x408ca21c (PropertySheetA+0x11c(lppsh=0x4113d250) [propsheet.c:2245] in comctl32.dll.so) (ebp=405c68bc) 28 0x5f4661eb (MFC42.DLL.?DoModal(a)CPropertySheet@@UAEHXZ+0xbc in I:\XILINX\MFC\MFC42.DLL) (ebp=00000000)

3 5

Re: AutoCAD2000 again and CreateFiber
by Matts Aug. 18, 2002

Aug. 18, 2002

Hi! Does this mean that AutoCad 2000 works good in wine, if I set window version to win95 (which I dont see a problem with right now)? Regards Matts >Well, after the patch-hack-or whatever on VirtualQuery, AutoCAD2000 >began >coming alive ! Some problems yet, but one wonders me in particular : >setting window version as win98 or winnt40, app shows an exception >stating >that CreateFiber function is not implemented; setting as win95 the apps >starts quite well. >Any idea ? Is there some plan to implement xxxxxFiber functions, or >it's too >difficult ? >BTW, looking for help on the net, i haven't really understood the >difference >between a regular thread and a fiber (only caught that use of fibers >instead >of threads is somehow discouraged...) >Regards >Max _____________________________________________________________ Want a new web-based email account ? ---> http://www.firstlinux.net _____________________________________________________________ Promote your group and strengthen ties to your members with email(a)yourgroup.org by Everyone.net http://www.everyone.net/?btn=tag

3 2

gdbproxy
by Robert Lunnon Aug. 18, 2002

Aug. 18, 2002

On solaris gdbproxy doesn't compile because S_un is not defined, S_un is only defined on SOlaris for XPG 4 applications. The header file however exposed _S_un so should this be _S_un or do I have to invent a new test for these features. Grabbed these comments off the net POSIX Applications that are intended to be conforming POSIX.1 applications must define the feature test macros specified by the standard before including any headers. For the stan- dards listed below, applications must define the feature test macros listed. Application writers must check the corresponding standards for other macros that can be queried to determine if desired options are supported by the imple- mentation. POSIX Standard Feature Test Macros POSIX.1-1990 _POSIX_SOURCE POSIX.1-1990 and _POSIX_SOURCE and POSIX.2-1992 C-Language _POSIX_C_SOURCE=2 Bindings Option POSIX.1b-1993 _POSIX_C_SOURCE=199309L POSIX.1c-1996 _POSIX_C_SOURCE=199506L X/Open CAE To build or compile an application that conforms to one of the X/Open CAE specifications, use the following guidelines. Applications need not set the POSIX feature test macros if they require both CAE and POSIX functionality. XPG3 The application must define _XOPEN_SOURCE with a value other than 500 (preferably 1). XPG4 The application must define _XOPEN_SOURCE with a value other than 500 (preferably 1) and set _XOPEN_VERSION=4. SUS (XPG4v2) The application must define _XOPEN_SOURCE with a value other than 500 (preferably 1) and set _XOPEN_SOURCE_EXTENDED=1. SUSv2 The application must define _XOPEN_SOURCE=500.

1 1

WINE fork and Win32api implementation
by Steven Edwards Aug. 18, 2002

Aug. 18, 2002

Hola Everyone, I'm CC'ing this to wine-devel so all of the WINE devs know whats going on as they have been very nice and supporting of my work so far. As everyone knows I've been doing a lot of work with Casper, James and Jurgan on the WINE fork to windows. I've had a lot of luck and been learning alot along the way but I dont think I can contribute much more the WINE porting work at this point from the ReactOS side. As David, Eugene and Jason are makeing lots of progress on the Windowing are just a few days/weeks(?) away from having Winhello working with the new Region code, I think someone needs to take over merging and maintaining the WINE dlls. I talked to Jason about it today and we thought that Robert might want to take over for a while if he is interested because he seems to like doing a lot of the Win32 side of things. If he is not interested does anyone else want to do it? IMHO the "right" way to fork the WINE code to best suite both projects is going to have to work like this: 1. We make a set policy of when to merge. I know Jason was wanting to change the release cycle times so the merging should be cordinated with that. Mabey like 2 weeks before a new release? 2. Whoever wants to try and maintain the fork is going to need to work with Capser on keeping the w32api headers up to date. I have submitted a few minor patches but I dont have the time to do the work that is really needed. This has been one of the biggest problems so far. Having 3 sets of headers is just a pain and all of the projects seem interested in moving to one common include system. I did a little bit of work trying to get some of the WINE dlls to compile with only the mingw headers but I didnt have the time to do to much with it. 3. Keep from forking/redunancy as much as possible. It bothers me when as small as our projects are we have already manged to have so much forking in WINE, mingw and ReactOS. How many registry editors do we need? How many filemanamgers? Once again the header thing bothers me. Sorry I'm ranting. Anyways, as things move along it should get better as we will be able to share the headers, programs, and librarys with WINE and Mingw. As of right now though I dont know how much more I can do with my limited skill. So who wants to do it? In another few weeks/month we are going to need to to try and get WINEmine, notepad and win/winefile working and import shell32, comctl32 and comdlg32. I'm going to keep submitting patches to the winehq.com tree as I find fun and interesting stuff. I still want to work toward having a drop in replacement with the "bleeding edge". My hope is that ReactOS will one day work off of the stable wine 1.0 if it is ever released =) and people that want the cutting edge can build wine 1.x dlls/programs for a ReactOS system. Most of my work from now on though is going to focus documentation, testing and spreeding the word about OpenSource, ReactOS, Wine and Mingw. Thanks Steven __________________________________________________ Do You Yahoo!? HotJobs - Search Thousands of New Jobs http://www.hotjobs.com

1 0

Compilation errors when using CFLAGS=-g
by Shachar Shemesh Aug. 17, 2002

Aug. 17, 2002

I did the following: make dist-clean CFLAGS=-g ./configure make depend make For some strange reason, I get the following errors: make[2]: Entering directory `/home/sun/sources/wine/wine/programs/winhelp' gcc -o hlp2sgml hlp2sgml.o hlpfile.o hlpfile.o: In function `HLPFILE_ReadHlpFile': /home/sun/sources/wine/wine/programs/winhelp/hlpfile.c:205: undefined reference to `GetProcessHeap' /home/sun/sources/wine/wine/programs/winhelp/hlpfile.c:238: undefined reference to `GetProcessHeap' /home/sun/sources/wine/wine/programs/winhelp/hlpfile.c:239: undefined reference to `GetProcessHeap' /home/sun/sources/wine/wine/programs/winhelp/hlpfile.c:240: undefined reference to `GetProcessHeap' /home/sun/sources/wine/wine/programs/winhelp/hlpfile.c:241: undefined reference to `GetProcessHeap' hlpfile.o:/home/sun/sources/wine/wine/programs/winhelp/hlpfile.c:337: more undefined references to `GetProcessHeap' follow collect2: ld returned 1 exit status make[2]: *** [hlp2sgml] Error 1 make[2]: Leaving directory `/home/sun/sources/wine/wine/programs/winhelp' make[1]: *** [winhelp] Error 2 make[1]: Leaving directory `/home/sun/sources/wine/wine/programs' make: *** [programs] Error 2 The exact same line of code failing in this file works without a problem in a hundred other places throughout the code, and when not overriding the flags (that is, if I understand correctly, when -g -O2 is used), everything is fine. Now, I don't need this file for my tests, so I just skip compiling it, but the problem is .... wierd. Anyone has any insight into it? sun(a)sun:~/sources/wine/wine/programs/winhelp$ cvs stat hlpfile.c =================================================================== File: hlpfile.c Status: Up-to-date Working revision: 1.9 Tue Jul 16 01:46:29 2002 Repository revision: 1.9 /home/sun/sources/wine/cvs/wine/programs/winhelp/hlpfile.c,v Sticky Tag: (none) Sticky Date: (none) Sticky Options: (none)

1 0