October 2007 - Wine-Devel - list.winehq.org

Re: Wine at Systems in Munich

by David M. Gümbel

On Donnerstag, 11. Oktober 2007, Dan Kegel wrote: > It would be great to have a booth there, hope somebody can go. > > It's kind of hard to do a good booth on short notice, though. > Let's remember that this is coming up next year, and plan > for it. Can you send me contact info for the organizers? Well, the person who contacted me was Peter Gietz from OpenLDAP, but I guess he would not be exactly whom you are looking for ;) Peter, do you have that bit of information and could pass it along? Thanks! Cheers, David

Oct. 14, 2007

Re: Wine crashes while trying to use Lexmark Network Scanback utility

by L. Rahyen

On Sunday October 14 2007 03:19, King InuYasha wrote: > Ehh, well, I was trying to use the Lexmark Scanback Utility to operate my > Lexmark OptraImage 322 and it crashed after clicking the button to setup a > new profile.... Installed original MFC42.DLL in the Scanback program > folder... > > Crash log: > > [InuTaisho(a)PIIMMX-GTWE4200 ScanBack]$ wine scanwiz.exe > wine: Call from 0x40ee68 to unimplemented function MFC42.DLL.6905, aborting > wine: Unimplemented function MFC42.DLL.6905 called at address 0x40ee68 > (thread 0038), starting debugger... > Unhandled exception: unimplemented function MFC42.DLL.6905 called in 32-bit > code (0x602e4d4c). Most likely you have wrong (probably too old) version of MFC42.DLL. You should try newer version of this DLL. BTW, if your Lexmark OptraImage 322 is non-ttyUSB USB device (you don't see it as ttyUSB in /dev/ directory) then don't even waste your time - it will not work with Windows programs on WINE. In this case you want try Virtual Box, QEmu or VMWare instead. WINE currently only support ttyUSB USB devices and all other kinds of tty devices (for example bluetooth/IRDA phones).

Oct. 14, 2007

Re: Wine crashes while trying to use Lexmark Network Scanback utility

by Juan Lang

King, On 10/13/07, King InuYasha <ngompa13(a)gmail.com> wrote: > Ehh, well, I was trying to use the Lexmark Scanback Utility to operate my > Lexmark OptraImage 322 and it crashed after clicking the button to setup a > new profile.... Installed original MFC42.DLL in the Scanback program > folder... Wrong forum. Use wine-users for this. > wine: Call from 0x40ee68 to unimplemented function MFC42.DLL.6905, aborting And this means you don't have the right version of mfc42.dll. Wine doesn't provide its own, so we can't help you with that. The application was supposed to have installed it, but many don't. --Juan

Oct. 14, 2007

Re: RICHED20: EM_SETTEXTEX must support RTF strings too

by Dmitry Timoshkov

<a_villacis(a)palosanto.com> wrote: > Changelog: > * EM_SETTEXTEX should also support RTF strings, just like WM_SETTEXT It would be helpful to have a test case for this, as well as a unicode version of WM_SETTEXT/EM_SETTEXTEX. -- Dmitry.

Oct. 14, 2007

Wine crashes while trying to use Lexmark Network Scanback utility

by King InuYasha

Ehh, well, I was trying to use the Lexmark Scanback Utility to operate my Lexmark OptraImage 322 and it crashed after clicking the button to setup a new profile.... Installed original MFC42.DLL in the Scanback program folder... Crash log: [InuTaisho(a)PIIMMX-GTWE4200 ScanBack]$ wine scanwiz.exe wine: Call from 0x40ee68 to unimplemented function MFC42.DLL.6905, aborting wine: Unimplemented function MFC42.DLL.6905 called at address 0x40ee68 (thread 0038), starting debugger... Unhandled exception: unimplemented function MFC42.DLL.6905 called in 32-bit code (0x602e4d4c). Register dump: CS:0073 SS:007b DS:007b ES:007b FS:0033 GS:003b EIP:602e4d4c ESP:0034dbd4 EBP:0034dc38 EFLAGS:00000206( - 00 - -IP1) EAX:00001af9 EBX:6032fa78 ECX:0034e938 EDX:00030068 ESI:0034dbe0 EDI:0003006c Stack dump: 0x0034dbd4: 00000038 00030068 0100101b 80000100 0x0034dbe4: 00000001 00000000 0040ee68 00000002 0x0034dbf4: 0041cca6 00001af9 0034dc3c 6062e98e 0x0034dc04: 5f422d22 00030068 00000000 00000038 0x0034dc14: 00030068 00001036 00000000 00000020 0x0034dc24: 00000000 00000000 00000000 0034e8d8 Backtrace: =>1 0x602e4d4c in ntdll (+0x24d4c) (0x0034dc38) 2 0x0040ee68 in scanwiz (+0xee68) (0x0034e938) 3 0x00000001 (0x00419bc8) 4 0x0040fed0 in scanwiz (+0xfed0) (0x0041524c) 5 0x25ff0041 (0x837c25ff) 6 0x00000000 (0x00000000) 0x602e4d4c: subl $4,%esp Modules: Module Address Debug info Name (67 modules) PE 400000- 420000 Export scanwiz PE 10000000-10035000 Deferred scanwizg ELF 41d2d000-41d4a000 Deferred ld-linux.so.2 ELF 41d4c000-41d60000 Deferred libresolv.so.2 ELF 426fe000-42852000 Deferred libc.so.6 ELF 42854000-4287d000 Deferred libm.so.6 ELF 4287f000-42884000 Deferred libdl.so.2 ELF 4289b000-428b3000 Deferred libpthread.so.0 ELF 428b5000-428b8000 Deferred libxau.so.6 ELF 428ba000-428c0000 Deferred libxdmcp.so.6 ELF 428c2000-429c4000 Deferred libx11.so.6 ELF 429c6000-429d6000 Deferred libxext.so.6 ELF 429d8000-42a62000 Deferred libfreetype.so.6 ELF 42a64000-42a85000 Deferred libexpat.so.0 ELF 42aaf000-42ade000 Deferred libfontconfig.so.1 ELF 42ae0000-42ae9000 Deferred libxrender.so.1 ELF 42af5000-42aff000 Deferred libxcursor.so.1 ELF 42b01000-42b08000 Deferred libxrandr.so.2 ELF 42b0a000-42b0d000 Deferred libxinerama.so.1 ELF 42b0f000-42b14000 Deferred libxfixes.so.3 ELF 42bc5000-42bce000 Deferred libsm.so.6 ELF 42bd0000-42bea000 Deferred libice.so.6 ELF 4347a000-43485000 Deferred libdrm.so.2 ELF 43487000-434f7000 Deferred libgl.so.1 ELF 43fcb000-43fd0000 Deferred libxxf86vm.so.1 PE 5f400000-5f4ed000 Deferred mfc42 ELF 6001d000-60132000 Deferred libwine.so.1 ELF 602a3000-6034b000 Export ntdll<elf> \-PE 602c0000-6034b000 \ ntdll ELF 60374000-60380000 Deferred libnss_files.so.2 ELF 60380000-604b5000 Deferred kernel32<elf> \-PE 603a0000-604b5000 \ kernel32 ELF 604b5000-604cf000 Deferred version<elf> \-PE 604c0000-604cf000 \ version ELF 604cf000-604e3000 Deferred lz32<elf> \-PE 604e0000-604e3000 \ lz32 ELF 604e3000-6054f000 Deferred msvcrt<elf> \-PE 604f0000-6054f000 \ msvcrt ELF 6054f000-6059c000 Deferred advapi32<elf> \-PE 60560000-6059c000 \ advapi32 ELF 6059c000-606ea000 Deferred user32<elf> \-PE 605c0000-606ea000 \ user32 ELF 606ea000-607f6000 Deferred shell32<elf> \-PE 60700000-607f6000 \ shell32 ELF 607f6000-60853000 Deferred shlwapi<elf> \-PE 60800000-60853000 \ shlwapi ELF 60853000-6091a000 Deferred comctl32<elf> \-PE 60860000-6091a000 \ comctl32 ELF 6091a000-60978000 Deferred rpcrt4<elf> \-PE 60930000-60978000 \ rpcrt4 ELF 60978000-60997000 Deferred iphlpapi<elf> \-PE 60980000-60997000 \ iphlpapi ELF 609ab000-609d8000 Deferred ws2_32<elf> \-PE 609b0000-609d8000 \ ws2_32 ELF 60a28000-60abd000 Deferred winex11<elf> \-PE 60a40000-60abd000 \ winex11 ELF 60c8e000-60cac000 Deferred imm32<elf> \-PE 60ca0000-60cac000 \ imm32 ELF 60cbb000-60cef000 Deferred uxtheme<elf> \-PE 60cc0000-60cef000 \ uxtheme ELF 627d4000-62878000 Deferred gdi32<elf> \-PE 627f0000-62878000 \ gdi32 ELF 63167000-63213000 Deferred ole32<elf> \-PE 63180000-63213000 \ ole32 ELF 6875e000-68778000 Deferred wsock32<elf> \-PE 68760000-68778000 \ wsock32 ELF 7bf00000-7bf03000 Deferred <wine-loader> Threads: process tid prio (all id:s are in hex) 00000037 (D) C:\Program Files\Lexmark\ScanBack\scanwiz.exe 00000038 0 <== 00000013 00000015 0 00000014 0 0000000f 00000016 0 00000010 0 0000000a 0000000c 0 0000000b 0 wine: Call from 0x40ee68 to unimplemented function MFC42.DLL.6905, aborting wine: Call from 0x40ee68 to unimplemented function MFC42.DLL.6905, aborting

Oct. 14, 2007

Re: Support GCOV for Wine 1.0?

by Detlef Riekenberg

On Fr, 2007-10-12 at 09:47 -0700, Dan Kegel wrote: > > It would be nice, when we can support gcov in current Wine > > "out of the box". > > That would help us a lot, when we write more tests for the > > suggested Wine 1.0 Applications. > > That project had a doc patch accepted: > http://www.winehq.org/pipermail/wine-patches/2005-April/017067.html > This created > http://www.winehq.org/site/docs/winedev-guide/x1374 > Does that suffice? I was thinking about: "./configure --enable-gcov" or "./configure --with-gcov" With the suggested flags, wine does not compile: gcc -c -I../../../src/dlls/activeds -I. -I../../../src/include -I../../include -D__WINESRC__ -D_REENTRANT -fPIC -Wall -pipe -fno-strict-aliasing -Wdeclaration-after-statement -Wwrite-strings -Wpointer-arith -fprofile-arcs -ftest-coverage -o activeds_main.o ../../../src/dlls/activeds/activeds_main.c ../../tools/winegcc/winegcc -B../../tools/winebuild -shared ../../../src/dlls/activeds/activeds.spec activeds_main.o -o activeds.dll.so -lkernel32 ../../libs/port/libwine_port.a activeds_main.o: In function `global constructors keyed to 0_DllMain':activeds_main.c:(.text+0x6da): undefined reference to `__gcov_init' activeds_main.o:(.data.rel+0x24): undefined reference to `__gcov_merge_add' ../../dlls/winecrt0/libwinecrt0.a(stub.o): In function `global constructors keyed to 0___wine_spec_unimplemented_stub':stub.c:(.text +0x81): undefined reference to `__gcov_init' ../../dlls/winecrt0/libwinecrt0.a(stub.o):(.data.rel+0x24): undefined reference to `__gcov_merge_add' collect2: ld gab 1 als Ende-Status zurück winegcc: gcc failed. make[2]: *** [activeds.dll.so] Fehler 2 make[1]: *** [activeds] Fehler 2 make: *** [dlls] Fehler 2 -------- I tried also: export CFLAGS="-fprofile-arcs -ftest-coverage" ./configure that breaks wine already in tools/* -- By by ... Detlef

Oct. 13, 2007

Re: Translating the Wiki

by Dimi Paun

On Sat, 2007-10-13 at 19:02 +0200, Francois Gouget wrote: > I have also added a FrenchDict page as described in the above help, in > an attempt to have users who open the FAQ page sent to the > FoireAuxQuestions page if their locale is French. However this does > not seem to work. Do you know what I got wrong? I'm afraid not, I've never used the feature. I guess you can ask the MoinMoin guys, they are usually responsive. > Another issue I have is: after some time, how do I know which parts of > the translation are up to date and which are not? The above page does > not touch on this issue. I don't think they have anything builtin, but you can always ask. At the very least, one can store the version of the translated page in a comment at the top of the page, and keep track of differences that way... -- Dimi Paun <dimi(a)lattica.com> Lattica, Inc.

Oct. 13, 2007

Re: CSS changes to the Wiki

by Jan Zerebecki

On Sat, Oct 06, 2007 at 01:32:32PM -0500, Alex Waite wrote: > Awhile ago I sent a few patches in to cleanup some HTML and CSS on > WineHQ. I didn't continue with writing more patches since it seemed > like we didn't have a clear idea of what direction we wanted to pursue. > I am more than happy to help with a rewrite or update of the site, but > as long as we have an plan of what we want to accomplish and how to go > about it. You likely need to come up with the plan yourself and if you want to make sure the other people working on the website stuff agree you might need to address them personally (in mail with cc-ing them or on IRC). > With the release of Wine 1.0 coming... sometime... in the future, it > would make sense if we had an updated website to accompany that release. > From my point of view, the following are some big problems with the > current site: > * Not pretty: while not awful, there are better color schemes and > layouts in the world. We can also look at some usability improvements. > If people are partial to it, we can still use the winish-red color, but > I think we can use it in a more attractive way than we do now. We probably want to retain some winish-red color. (The content and the rest listed here is probably more important than a better layout / color scheme. But if you come up and implement something better that most like, your work is welcome anyway.) > * Table-hell: This is where I tout the joys of <div>'s and CSS. Tables > are a pain to deal with and bloat the code quite a bit. Not to mention > that they make pages pretty inaccessible. Yes. > * Accessibility: Tables are the big culprit here, but there's also > simple things like making the code valid. There's also some fairly > straightforward ways of writing code which help a lot (precede lists > with headers, nest headers correctly, etc). While accessibility doesn't > have to be perfect, I think it promotes well written code and makes > pages more accessible to more people. Yes. > * Valid code: This is a principal to me. I think if code is to be > written, it should be written correctly. Wine is known for not > accepting hacks or improper fixes; I think our website should reflect > that, especially since the spec is not hard to conform to. Yes. In-Reply-To: <47102381.4060307(a)uiuc.edu> On Fri, Oct 12, 2007 at 08:46:41PM -0500, Alexander Q. Waite wrote: > I've offered a few times to help work on the website, provided we had > a plan and worked together to achieve it. I hope I didn't come across > as whining, because that was never my intention. I just feel there are > a number of improvements which can be made to the website/wiki/appdb and > it would likely be a better outcome if the efforts were coordinated. > In my previous posts I attempted to identify what I felt were > potential problem areas, to encourage others to provide their input and > hopefully get some dialog. I think the Wine pages need a bit of a face > lift, and the HTML could use some improvement too when it comes to > conforming to the spec and accessibility. If others agree or disagree, > I'd like to hear about it, so that we can - together - identify what we > feel are and aren't problem areas. Then we can determine if the tasks > at hand are large enough to warrant coordination or are better left to > singular efforts. > I look forward to hearing other people's thoughts. No reply is usually an indicator for agreement on wine-devel. As I said above you can find out the main workers / responsible people in that area and ask them directly. For the appdb there is some coordination done already, but for the rest of the website stuff besides that there is not that much work done there is thus also not much coordination going on. So you likely need to do the coordination and/or leading yourself. Work on this is welcome. Jan

Oct. 13, 2007

Translating the Wiki

by Francois Gouget

On Sat, 13 Oct 2007, Dimi Paun wrote: > On Sat, 2007-10-13 at 10:32 +0200, Francois Gouget wrote: > > > > d) there's no way to translate it > > http://moinmoin.wikiwikiweb.de/HelpOnLanguages > > More is on the way I believe. Ok. So I have added a FoireAuxQuestions page with the start of a translation for the FAQ. http://wiki.winehq.org/FoireAuxQuestions I have also added a FrenchDict page as described in the above help, in an attempt to have users who open the FAQ page sent to the FoireAuxQuestions page if their locale is French. However this does not seem to work. Do you know what I got wrong? Another issue I have is: after some time, how do I know which parts of the translation are up to date and which are not? The above page does not touch on this issue. -- Francois Gouget <fgouget(a)free.fr> http://fgouget.free.fr/ It really galls me that most of the computer power in the world is wasted on screen savers. Chris Caldwell from the GIMPS project http://www.mersenne.org/prime.htm

Oct. 13, 2007

Wiki looks much better

by Juan Lang

Hi Dimi, I just checked out the Wiki after your most recent checkin. It does, indeed, look much better. Thanks for taking the time to look at it. And, after reviewing the change, I have to agree: it would be hard to predict that the browsers would do what they did based on the old CSS. :-/ --Juan

Oct. 13, 2007