May 2005 - Wine-Devel - list.winehq.org

Bug 469 - Application can not read from serial port
by Dustin Navea May 25, 2005

May 25, 2005

Hey guys, this one was (obviously) reported a while back, and the offending patch was found a while back as well, but it appears that mike (at codeweavers dot com) never was able to get around to it.. Basically it is an issue that a solar panel reading application cant retrieve information via the serial port. I have requested that someone test it (the demo of the app is attached to the bug) on a recent wine build. So hopefully it is working now, and if not, maybe it will be trivial? Either way, the name of the program looks to be SunGoXL, and perhaps there is a more recent version of the program that allows it to run in wine, if the older one doesn't work. The changelog for the patch is: cvs log files/file.c Mike McCormack <mike_mccormack(a)start.com.au> Read data immediately in overlapped ReadFile if possible. From the most recent traces we have that show the problem, it looks as though the GetOverlappedResult function is waiting on something (probably the solar equipment) to be returned, but it never does, so maybe at the time (if not still now) wine was unable to use the serial port for whatever reason? Other people could test the program, but if it is something to do with serial communication with solar equipment, it wouldn't make any sense, unless that someone else has the same equipment and issue... Maybe the reporter still checks that email, and can test it out... If theres no activity on the bug in 1 month, I will resolve it abandoned.. Dustin

3 2

Bug 2977 - Homeworld 2 wont launch
by Dustin Navea May 25, 2005

May 25, 2005

Hey guys, this bug was reported, but recently (without updating wine from what I can tell), the reporter updated the kernel with yum.. After doing so, the game launches perfectly (except for the copy protection getting in the way).. Any comments on why this might happen? The reporter should be subscribing shortly, so he can probably post info about it. Dustin

1 0

Re: [dbghelp] dwarf2 support progress step 5
by Alexandre Julliard May 24, 2005

May 24, 2005

Raphael <fenix(a)club-internet.fr> writes: > Hi, > > This times symt model construction seems good :) > > But for debug lines, i don't really understand the sm/regs concept :( > > Changelog: > - implement dwarf2_find_symt_by_ref and dwarf2_add_symt_ref using hashtables > - some debug lines defines > - handle forwards references (ie dwarf2_find_symt_by_ref returns NULL) using > ref hashtable > - better traces It doesn't compile, you probably forgot part of the diff: elf_module.c: In function `elf_load_debug_info_from_map': elf_module.c:901: too few arguments to function `dwarf2_parse' make: *** [elf_module.o] Error 1 -- Alexandre Julliard julliard(a)winehq.org

2 1

Help with winelib and development
by Afkhampour, Cyrus May 24, 2005

May 24, 2005

Hi I am trying to learn how to use winelib/wine as I am trying to port a piece of code from windows to Linux and was told that wine might be the tool to use. I have downloaded wine and begna the winelib tutorial but now I can not find the winemaker file to save my life. Can someone explain what I am missing?

2 1

Compiling with winelib
by antonio.fernandez.moreno＠dmr-consulting.com May 24, 2005

May 24, 2005

Hello, Im trying to compile with winelib the notepad following the steps in the user guide. When I run the make command, the compiler gives me errors with the .rc files. Then I try to compile without these files and the compiler gives me the next error: bash-2.03$ make gcc -c -I. -I/usr/local/include/wine/windows -g -O2 -fPIC -D_REENTRANT -o dialog.o dialog.c LD_LIBRARY_PATH=":$LD_LIBRARY_PATH" /usr/local/bin/winebuild -fPIC -o notepad2.exe.spec.c --exe notepad2.exe -mgui License_En.o dialog.o license.o main.o notepad.exe.dbg.o -L/usr/local/lib -L/usr/local/lib/wine -ladvapi32 -lcomdlg32 -lgdi32 -lkernel32 -lodbc32 -lole32 -loleaut32 -lshell32 -luser32 -lwinspool gcc -c -I. -I/usr/local/include/wine/windows -g -O2 -fPIC -D_REENTRANT -o notepad2.exe.spec.o notepad2.exe.spec.c gcc -shared -Wl,-Bsymbolic -o notepad2.exe.so License_En.o dialog.o license.o main.o notepad.exe.dbg.o notepad2.exe.spec.o -lwine -lwine_unicode -lwine_uuid -lsocket -lw -lm dialog.o: In function `DIALOG_FilePrint': /opt/cfw/wine/programs/notepad2/dialog.c:380: undefined reference to `strcpy' /opt/cfw/wine/programs/notepad2/dialog.c:381: undefined reference to `strlen' dialog.o: In function `DIALOG_SelectFont': /opt/cfw/wine/programs/notepad2/dialog.c:675: undefined reference to `memcpy' /opt/cfw/wine/programs/notepad2/dialog.c:688: undefined reference to `memcpy' dialog.o: In function `DIALOG_Search': /opt/cfw/wine/programs/notepad2/dialog.c:697: undefined reference to `memset' main.o: In function `NOTEPAD_InitData': /opt/cfw/wine/programs/notepad2/main.c:100: undefined reference to `strlen' /opt/cfw/wine/programs/notepad2/main.c:102: undefined reference to `strlen' /opt/cfw/wine/programs/notepad2/main.c:104: undefined reference to `strlen' /opt/cfw/wine/programs/notepad2/main.c:106: undefined reference to `strlen' main.o: In function `HandleCommandLine': /opt/cfw/wine/programs/notepad2/main.c:205: undefined reference to `printf' /opt/cfw/wine/programs/notepad2/main.c:221: undefined reference to `strlen' /opt/cfw/wine/programs/notepad2/main.c:231: undefined reference to `strlen' /opt/cfw/wine/programs/notepad2/main.c:231: undefined reference to `strcmp' /opt/cfw/wine/programs/notepad2/main.c:238: undefined reference to `strncpy' /opt/cfw/wine/programs/notepad2/main.c:239: undefined reference to `strcat' main.o: In function `WinMain': /opt/cfw/wine/programs/notepad2/main.c:276: undefined reference to `memset' test -f notepad2 || install wineapploader notepad2 find: no es posible abrir notepad2: No existe tal archivo o directorio find: no es posible seguir enlace simbólico /etc/wtmpx: No existe tal archivo o directorio install: wineapploader was not found anywhere! make: *** [notepad2.exe.so] Error 2 This error appears because I have not the include <string.h> line. Wont winelib must link with this file when I compile? Im using this version of Wine: Wine-20030618.tar.gz in a Solaris 8 (SPARC) How can I know if winelib is correctly installed? Thank you. Antonio Fernández.

2 1

Bugzilla wiki
by Dustin Navea May 24, 2005

May 24, 2005

Hey everyone, I've just finished the bugzilla wiki.. If anyone has any comments or changes, go ahead and post them. Alexandre, Jeremy, is there any chance that a link to the bugzilla wiki could be put into the sidebars for the winehq main page and the bugzilla main page? That way people can read that, as it has some preferred guidelines on posting (including initial bug reports). If we can get a link there, or at least in the docs, it should cut down on some of the dupes I have been getting, and also make it easier to diagnose bugs. Todo: * find out _every_ valid flag that can be passed to wine via the WINEDEBUG= variable * post them into a separate wiki * post a link from the bugzilla wiki to that new wiki If anyone wants to start emailing me flags and what they do or can be useful for tracing, feel free, and I will get the wiki page started either tonight or tomorrow. Dustin

2 1

Re: ITSS Conformance Test Patch
by Dimi Paun May 24, 2005

May 24, 2005

From: "Chris Watmore" <chris.watmore(a)gmail.com> > This patch adds tests for the itss dll. Please no Perl or Shell scripts -- they will not run on Windows, where we ship tests via winetest. Just code them in C, it shouldn't be too hard. -- Dimi Paun <dimi(a)lattica.com> Lattica, Inc.

2 1

question about standalone tests
by Kees Cook May 24, 2005

May 24, 2005

Hi! My crypt32 protectdata tests were just added to CVS (thanks!) but they were added without the #ifndef STANDALONE stuff that exists in the recommended example from the lzexpand test code. The steps here: http://www.winehq.com/site/docs/wine-devel/testing-windows don't have a method for doing the build with the free-of-charge windows CLI compiler (which the "STANDALONE" stuff works fine with). Is there some new way to build standalone tests, or should I send a patch for re-including the #ifndef STANDALONE stuff for the tests? -- Kees Cook @outflux.net

3 3

PowerPaint not working
by Andrew Neil Ramage May 24, 2005

May 24, 2005

I installed PowerPaint (free on thw Net, somewhere) OK, but when I try to run it I get a message box telling me the installation is corrupt, and the following output from Wine. andrew(a)zeus:~/.wine/drive_c/Program Files/FLISoft/PowerPaint> wine PowerPaint.exe fixme:shell:SHGetFileInfoW set icon to shell size, stub fixme:ole:CoRegisterMessageFilter stub fixme:ole:CoCreateInstance no classfactory created for CLSID {47ad7e45-ba98-47e4-887f-9ab7a07f7d4d}, hres is 0x80040150 fixme:ole:CoRegisterMessageFilter stub I am using the latest CVS of Wine. -- Andrew You can be the captain I will draw the chart Sailing into destiny Closer to the heart Closer to the Heart by Rush (A Farewell to Kings, 1977) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

1 0

qcap/avicap and driver models
by Maarten Lankhorst May 24, 2005

May 24, 2005

Hi Alexandre, I implemented a driver model in qcap now, but avicap32 still uses my old #ifdef LINUX_VIDEODEV_H, since some people might be interested in writing capcreatecapturewindow, I think we should move out the drivers from qcap to our own vfwwine dll/driver, windows uses a similar model for it, as rolf kalbermatter pointed out in http://www.winehq.com/?issue=274#Video%20Capture%20in%20Windows For the qcap drivers, I used some kind of COM model typedef struct capturefunctions { ... Video_SetMediaType SetFormat; ... void *pMine; } Capture; First, it tries to initialise, and lets the constructor function fill this struct, then if something is needed, it just calls Capture->SetFormat(Capture->pMine, parameters..), this is the qcap implementation, but I'm sure that if I write some parts of it so it will be DirectShow indepent, it can be used by avicap and qcap, I'm not really interested in avicap, but in the very least capgetdriverdescription should use the same code as qcap, because writing the same twice would mean a huge overhead. So basically, I'm just wondering what to do, should I go ahead with the seperate driver dll or should I do something else? Maarten

3 2