- Wine-Devel - list.winehq.org

Overlapped I/O without an hEvent
by Ryan Reading Nov. 26, 2002

Nov. 26, 2002

Hi all, This is a follow-up to the message I wrote a message yesterday with the subject "Wine and IrDA via Virtual Com Port", although that wasn't a good subject for the problem. The software that I have is using Overlapped (asynchronous) I/O for communication of an IR port. The software makes WriteFile(), ReadFile(), and GetOverlappedResult() calls. However, before making any of the calls, the software does NOT initialize the hEvent member of the OVERLAPPED structure that is passed to the functions (it just zeroes the entire structure). Apparently the Win32 implementation of this is OK, but it is pretty obvious that the Wine implementation will not work with hEvent == 0. Now, I'm not saying that the Wine implementation is wrong, because based on the MSDN documentation, that value should be set to a valid event handle; however, the behavior is fundamentally different from the native Win32 environment, which in my case, leads to undesirable results. Is this something that I could feasibly fix in Wine, or would it be better to try to change the implementation of the software? Does anyone have any experience with this part of Wine? Thanks. -- Ryan 01010011 01100101 01110010 01100101 01101110 01100100 01101001 01110000 01101001 01110100 01111001 If only all life was just this simple. :)

4 5

Orlando, anyone?
by Fredrick P. Lackey Nov. 26, 2002

Nov. 26, 2002

Hey, everyone! It's the annoying Microsoft guy again. ;-) Well, I've started to make the move. Now, 1/2 of my laptop is Red Hat. Whoo hoo! Man, I love Linux! =) I am having some problems, and was wondering if anyone in your list knew anyone in or near Orlando. heck, in Florida would be close enough. I'd like to see about hooking up on the phone or in person and trying to get the few issues I'm having worked out. I know that may seem a bit odd, but I'm really pumped to get M$ outta the picture. Thanx, Fred Lackey Orlando, Florida

2 1

Found Something Really Weird here!!
by Rômulo Nov. 26, 2002

Nov. 26, 2002

I found something reeeally weird here, installing wine, on mandrake, gcc v3.2. ( [lamorack(a)WNET wine-20021031]$ gcc -v Reading specs from /usr//bin/../lib/gcc-lib/i586-mandrake-linux-gnu/3.2/specs Configured with: ../configure --prefix=/usr --libdir=/usr/lib --with-slibdir=/lib --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --enable-long-long --enable-__cxa_atexit --enable-languages=c,c++,ada,f77,objc,java --host=i586-mandrake-linux-gnu --with-system-zlib Thread model: posix gcc version 3.2 (Mandrake Linux 9.0 3.2-1mdk)) See this: (...) make[1]: Nada a ser feito para `all'. make[1]: Saindo do diretório `/home/lamorack/wine-20021031/miscemu' make[1]: Entrando no diretório `/home/lamorack/wine-20021031/programs' make[2]: Entrando no diretório `/home/lamorack/wine-20021031/programs/avitools' LD_LIBRARY_PATH="../../library:../../unicode:$LD_LIBRARY_PATH" ../../tools/winebuild/winebuild -fPIC -DSTRICT -DNONAMELESSUNION -DNONAMELESSSTRUCT -o aviplay.exe.spec.c -exe aviplay.exe -mgui aviplay.o -L../../dlls -lddraw -lkernel32 could not open .so file for ddraw.dll make[2]: ** [aviplay.exe.spec.c] Erro 1 make[2]: Saindo do diretório `/home/lamorack/wine-20021031/programs/avitools' make[1]: ** [avitools] Erro 2 make[1]: Saindo do diretório `/home/lamorack/wine-20021031/programs' make: ** [programs] Erro 2 And that's it! I really hope u have an idea... 'cause i did not. Send me any E-mail answering, please

2 1

Re: Re: About picture format.
by yf Nov. 26, 2002

Nov. 26, 2002

> On Mon, Nov 25, 2002 at 01:03:00PM +0800, yf wrote: > > > > It is a Windows application. > > you can download it on http://www.myhexin.com/tw2002/rjxz/download.asp?rjxz=exe1 > > Which program do you start? when running, it complains: fixme:ole:OLEPictureImpl_Load Unknown magic 0010 fixme:ole:OLEPictureImpl_Render type -1 not implemented fixme:ole:OLEPictureImpl_Destroy Unsupported type -1 - unable to delete fixme:ole:OLEPictureImpl_Load Could only read 136 of 1073465 bytes? > > I have a bit of a hard time following the menus, since they appear to be > in an asian language and the characters do not even display ;) I have sended the patch of how to make the Chinese character properly showed before. --- wine-20021031/graphics/x11drv/codepage.c.original 2002-11-16 13:50:31.000000000 +0800 +++ wine-20021031/graphics/x11drv/codepage.c 2002-11-04 17:44:14.000000000 +0800 @@ -279,8 +279,8 @@ { if ( IsLegalDBCSChar_cp936( *str_src, *(str_src+1) ) ) { - str2b_dst->byte1 = *str_src; - str2b_dst->byte2 = *(str_src+1); + str2b_dst->byte1 = *str_src&0x7f; + str2b_dst->byte2 = *(str_src+1)&0x7f; str_src++; } else > > Ciao, Marcus >

3 4

Re: Screwed up textures in OpenGL apps
by David D. Hagood Nov. 26, 2002

Nov. 26, 2002

Lionel Ulmer wrote: > Out of curiosity after the DoubleBuffered thread.... Does this fix your > problem too ? > > No, I was running DesktopDoubleBuffered = Y already.

1 0

Winelib Apps v0.1
by Dimitrie O. Paun Nov. 26, 2002

Nov. 26, 2002

Folks, Version 0.1 of the Winelib Applications page is available here: http://www.dssd.ca/wine/Winelib-Apps-0.1.html The current version is always available at this address http://www.dssd.ca/wine/Winelib-Apps.html Your comments, and suggestions are highly appreciated. -- Dimi.

1 1

An opengl regression
by Duane Clark Nov. 25, 2002

Nov. 25, 2002

The patch for dynamic loading of opengl, http://www.winehq.com/hypermail/wine-cvs/2002/11/0151.html has caused a (apparently minor) regression in the program earthquake http://www.navagent.com/products/earthquake/ That is a small app (250K download) with a spinning globe that shows current earthquakes; actually a pretty cool little app. The regression is that now when the oceans are turned on (via the settings dialog), the land gets flooded.

3 5

Compiling Win32 targets on Linux
by mwood＠gosympatico.ca Nov. 25, 2002

Nov. 25, 2002

I'm not sure if this is directly related to Wine, but I would like to build win32 exectuables on a Linux machine, with gcc if this is possible. I use Slackware 7.x and 8.x and was wondering what I would need to install to accomplishh this. Mikko Woodroffe

2 1

Wintab.dll technical issues.
by Robert North Nov. 25, 2002

Nov. 25, 2002

Firstly a quick note: I have opened a bug for implementation of wintab.dll (Bug No. 1160) Now the questions: 1: Writing stubs. I'll be taking up Patrik Stridvall's offer to write stubs for anyone new to wine development. One question about stubs: What's the wine policy on stub return values? Should a stub always return an error? Should/Can it return success? 2: Testing wintab.dll in Win98. wintab.dll is quite complex for what it does. Therefore the only practical way to implement it is to work on the functions and communication models that are used by the apps I want it to support. To do this, I need some tool that can log the function calls and parameters to the DLL, while wunning Win98.The logging must be able to let the programmer choose elements from data stuctures in parameters/retvals to log. Any ideas???? I've attempted to use apis32 and built a wintab.fnl file for wintab.dll. Unfortunately apis32 doen't allow the logging of the contents of data structs. I would also like to know experinces with Spy++. Wintab can send it's own custom messages, so I'm wondering how good Spy++ is at detecting custom messages? I've used it many times before, but only to examine standard windows messages. 3: Coding standards. I haven't found any coding standards associated with wine. This is particularly important, as I'll be writing new source files. Can someone point me to the standards? Hope you guys have the answers -Rob.

5 5

[RFC] pthread emulation on FreeBSD (and Linux)
by Patrik Stridvall Nov. 25, 2002

Nov. 25, 2002

With the attached patch FreeBSD compiles again even if OpenGL (which need pthreads) is used. Since it is only stubs at present OpenGL can't really work, but Wine and the normal test runs fine ("make test"). Anyway, to answer the first obvious question: Why didn't you just put it in scheduler/pthread.c? Well, the thing is it didn't work. It still generates the same link errors. However that is not very suprising since the pthread_ implementation is in ntdll.dll which is not linked with during the "-Bsymbolic -z defs" step. This begs the question: Does the Linux implementation of pthread really work anyway? The thing is Linux (or rather the GNU C library) always links in pthread suppport. However since some of the symbols are on purpose defined as weak they can be overriden. This is what scheduler/pthread.c does on Linux. Or rather tryies to do. I'm not really sure if works any longer. Note that if I apply the attach patch and compiles on Linux it seems to work with "make test" as well. Anyway be pthreads on Linux working properly as it may, the big question is how do we support pthreads on both Linux and FreeBSD. FreeBSD since it AFAICS have no default overridable implementation seems to require that we have some sort of wine_pthread library to implement pthreads from scratch like outlined in the attached patch. I'm not really very good on how runtime linking on Linux and FreeBSD. So, I would very much like comments from people more knowledgeable than I on that area. Comments? Suggestions? PS. Can somebody test if OpenGL:s pthread locking REALLY works properly on Linux?

3 2