April 2002 - Wine-Devel - list.winehq.org

WINE XIM Patch

by Aric Stewart

Hello everyone, Myself, Mike McCormack and Ulrich Czekalla have been working like mad to get XIM into Wine. We have a very early and unclean patch for people to try and help improve. This patch applies to the winehq tip as of today and probably changed a bunch of things it does not need to. If you use XIM input and can work with this please give it a try. I know it works with Japanese input with kinput2 on my redhat 7.2 machine. Since i do japanese that is what i have been testing but i have not idea for any other input methods or languages. Some known issues. * The xim box does not appear in the right place, and i cannot see what i type as i type it in. * the input does not always go to the correct edit window. * Presently it probably only works for edit controls... Hope this helps people! -aric

April 25, 2002

Re: cups support apparently broken

by Michael Cardenas

Is there a better place to send this type of thing so that it will get some kind of attention? Is everybody regularly checking bugzilla, for example? On Wednesday 24 April 2002 04:42 pm, Michael Cardenas wrote: > Hello all. > > Apparently wine's cups support is broken. > > With our old version of wine, wine would correctly detect the current cups > printer, but it couldn't actually print to it. So, you would see the print > dialog, but when you hit the print button nothing happened. > > Now, I have cups installed and a build of yesterday's cvs and when I try to > print wine tells me that there are no printers installed and I should > "point to settings on the windows start menu, click printers" and add a > printer. > > Anyone have any ideas on how this broke? > > thank you > michael -- michael cardenas lead windows compatibility engineer lindows.com "Be the change you want to see in the world" -Mahatma Gandhi

April 25, 2002

Memori and Swap Full after some hours

by Marcelo Welter

I have a windows application run in a very old machine Pentium 133Mhz 32 Mb RAM (believes this still exist) The application running fine, but after some hours (3 or 4) the memory and swap are full and the machine run very slowly. I Close the wine and all back to normal I dont know what are happen with system, but is a very hard trouble to me. Anybody have any idea to apply in this case Thanks Marcelo Welter

April 25, 2002

Re: wine and aol7 [was: Re: New Winsock2 patch series - now tested]

by Michael Cardenas

thanks. On Thursday 25 April 2002 03:30 pm, you wrote: > Nothing was attached... > > On Thu, 25 Apr 2002 10:16:38 -0400, Michael Cardenas > > <michael.cardenas(a)lindows.com> wrote: > >Now, on to the work at hand. > > > >Attached is the output of running aol7 with +winsock, +file, with your > > latest series of winsock patches. Aol is still unable to handshake > > properly with it's web proxy and so you can't see any web content in aol > > or the buddy list. > > > >If anyone wants to work on aol or just to see it working, I can provide a > > deb package or a tarball that lets you install aol, so you don't have to > > worry about the aol installer working. I submitted some patches a few > > weeks ago that allow aol7 to launch. -- michael cardenas lead windows compatibility engineer lindows.com "Be the change you want to see in the world" -Mahatma Gandhi

April 25, 2002

Re: overlapped read problem.

by Martin Wilck

On Thu, 25 Apr 2002, Rein Klazes wrote: > Here is the same +comm,+file now with added +server: > > | trace:file:FILE_ReadFileEx file 232 to buf 0x405953f0 num 8 0x409032e4 func (nil) > | 0806cfe8: get_handle_fd( handle=232, access=80000000 ) > | 0806cfe8: get_handle_fd() = 0 { fd=18, type=1, flags=1 } > | 0806cfe8: register_async( handle=232, type=1, overlapped=0x41d615b0, count=8, status=00000103 ) > | 0806cfe8: register_async() = 0 => async request successfully registered > | trace:file:GetOverlappedResult (232 0x409032e4 0x405953a4 0) > | trace:file:GetOverlappedResult waiting on 0x409032e4 > | 0806cfe8: select( flags=14, cookie=0x405951bc, sec=1019746522, usec=250830, handles={236} ) > | 0806cfe8: select() = TIMEOUT => async has not been served yet - TIMEOUT. The reason is that the file descriptot for serial port had not been polled in the meantime. OK, I know what to do about that. When register_async is called with a new request, we must immediately look for pending events, as we do with sockets. Thanks for spotting this, expect a patch soon. Martin -- Martin Wilck Phone: +49 5251 8 15113 Fujitsu Siemens Computers Fax: +49 5251 8 20409 Heinz-Nixdorf-Ring 1 mailto:Martin.Wilck(a)Fujitsu-Siemens.com D-33106 Paderborn http://www.fujitsu-siemens.com/primergy

April 25, 2002

RE: Question about Warning when building wine under Cygwin/Mingw/MSYS

by Steven Edwards

Thanks I will have a look at that. > > With "typedef long long __int64;" being the problem on line 47. > Could it be that mingw32 simply doesn't understand "long > long" ? (probably the second "long" confuses it into an > "empty declaration"). > > If so, either find the real type name of "long long" that > mingw32 uses (if it exists), or simply #ifdef it out completely. >

April 25, 2002

Port.h issue with mingw

by Steven Edwards

I need help with fixing this too. ../include/wine/port.h:175: parse error before `pread' ../include/wine/port.h:175: warning: type defaults to `int' in declaration of `p read' ../include/wine/port.h:175: warning: data definition has no type or storage clas s ../include/wine/port.h:179: parse error before `pwrite' ../include/wine/port.h:179: warning: type defaults to `int' in declaration of `p write' ../include/wine/port.h:179: warning: data definition has no type or storage clas S Thanks Steven "Every revolution was once a thought in one man's mind" - Ralph Waldo Emerson

April 25, 2002

Unexpected calls of MODULE_LoadLibraryExA

by Sylvain Petreolle

Hi, Running the installer of the latest beta version of Povray gives these error when copying a file : MODULE_LoadLibraryExA fails because it is called with plain text files (for example pov sources). Function returns as it should, 193 (ERROR_BAD_EXE_FORMAT) err:module:MODULE_LoadLibraryExA Loading of native DLL C:\Program Files\POV-Ray for Windows v3.5\renderer\slow.ini failed (error 193), check this file. err:module:MODULE_LoadLibraryExA Loading of native DLL C:\Program Files\POV-Ray for Windows v3.5\renderer\tgaflc.ini failed (error 193), check this file. err:module:MODULE_LoadLibraryExA Loading of native DLL C:\Program Files\POV-Ray for Windows v3.5\renderer\tgafli.ini failed (error 193), check this file. ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com

April 25, 2002

Separating Process and Debugger Debugmsg Output

by Uwe Bonnes

Hallo, if one starts a program via wine with e.g. relay debug messages enabled, and the program crashes, these debugmessages get also enabled for the winedbg process and this clutters the relay log to get nearly unreadable. Until Alexandre's restructuring of the Command Line handling, I had "---debugmsg -all" as additional argument to the winedbg command line in system.reg, aedebug section. No wine spits on this argument. How do you solve this problem? Bye -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------

April 25, 2002

Re: Question about Warning when building wine under Cygwin/Mingw/MSYS

by Andreas Mohr

On Thu, Apr 25, 2002 at 12:53:01PM -0400, Steven Edwards wrote: > Anyone have any idea what to do about this? > > mingw32-gcc -c -I. -I. -I../../include -I../../include -D__MINGW__ > -D_WINDOWS - > DWINE_NOWINSOCK -Wall -mpreferred-stack-boundary=2 -DSTRICT > -DNONAMELESSUNION -D > NONAMELESSSTRUCT -D_REENTRANT -o regedit.o regedit.c > In file included from ../../include/winnt.h:24, > from ../../include/windef.h:30, > from ../../include/windows.h:32, > from regedit.c:23: > ../../include/basetsd.h:47: warning: useless keyword or type name in > empty decla > ration > ../../include/basetsd.h:47: warning: empty declaration > > > Basetsd.h has > > #ifndef _MSC_VER > typedef char __int8; > typedef short __int16; > typedef int __int32; > typedef long long __int64; > #endif /* !defined(_MSC_VER) */ > > With "typedef long long __int64;" being the problem on line 47. Could it be that mingw32 simply doesn't understand "long long" ? (probably the second "long" confuses it into an "empty declaration"). If so, either find the real type name of "long long" that mingw32 uses (if it exists), or simply #ifdef it out completely. -- Andreas Mohr Stauferstr. 6, D-71272 Renningen, Germany Tel. +49 7159 800604 http://home.arcor.de/andi.mohr/

April 25, 2002