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

Re: fixme:win32:PeekNamedPipe

by Michael Cardenas

Michael Riedel wrote: > Thanks for the hint, and yes it is a kernel32 function. ok, then there's some work to do. > fixme:win32:PeekNamedPipe (00000080, (nil), 00000000, (nil), > 0x406a2194, (nil)): stub > > this means that at least a valid handle was created so that there is > already some code for CreateNamedPipe or CreatePipe? This means there's a stub. So, there's a placeholder with no code in it. > Is there anybody knowing more before I am going to try looking into > the sources? I'm not more knowing about this function per se, I'm sure whoever else wrote the rest of the named pipe implementation will know. But I do know that you can do this to find the stub, and possibly the file that has the other named pipe functions: find (winesrcdir) -name *.c | xargs grep PeekNamedPipe -- michael cardenas lead windows compatibility engineer www.lindows.com "Be the change you want to see in the world." -Mahatma Gandhi

April 16, 2002

Re: Urgent need for advice: POLLHUP and sockets

by Michael Cardenas

> My first reaction to this was to comment out the above call to > set_select_events() and continue listening to events from the socket. > However, due to the semantics of poll(), this will cause a POLLHUP event > on this socket for each and every iteration of the wineserver's main select > loop, putting the server basically into a busy-wait state. well, can you just ignore the POLLHUP events in the server for that socket after the first one is received?

April 16, 2002

Re: fixme:win32:PeekNamedPipe

by Michael Riedel

Thanks for the hint, and yes it is a kernel32 function. BOOL PeekNamedPipe( HANDLE hNamedPipe, // handle to pipe LPVOID lpBuffer, // data buffer DWORD nBufferSize, // size of data buffer LPDWORD lpBytesRead, // number of bytes read LPDWORD lpTotalBytesAvail, // number of bytes available LPDWORD lpBytesLeftThisMessage // unread bytes ); Since I get fixme:win32:PeekNamedPipe (00000080, (nil), 00000000, (nil), 0x406a2194, (nil)): stub this means that at least a valid handle was created so that there is already some code for CreateNamedPipe or CreatePipe? Is there anybody knowing more before I am going to try looking into the sources? Thanks, Michael --

April 16, 2002

Re: fixme:win32:PeekNamedPipe

by Michael Cardenas

Try searching for PeekNamedPipe on msdn.microsoft.com and at the bottom it will tell you what dll the function is in. unfortunately, if it's in the kernel, you won't be able to use a native dll. On Tuesday 16 April 2002 03:40 am, Michael Riedel wrote: > First of all I want to thank the community for the efforts spent in > developing wine. It's simple a cool "tool" (sorry, it's more, I know). > > Now my problem: I installed wine-20020411 without having a native > windows installation. I installed successfully a simulator software > which obviously uses a tcl/tk-GUI to invoke other program moduls > (compiler, library manager, simulator core) re-directing their > stdin/stdout to the console window via pipes. It does not work for me > and I get the message (infinitivly repeated): > > fixme:win32:PeekNamedPipe (00000080, (nil), 00000000, (nil), 0x406a2194, > (nil)): stub > > Searchin the web I got no hit. > > Questions: > > (1) Can I avoid this by using a native windows-dll? If yes, which dll I > have to install (but I assume it is a kernel-dll function and so it is > not possible)? > > (2) I have no Windows programming background, but what do you think: > Should I dare to implement this function or was it left open because of > a tricky windows-API-Linux mapping problem? > > (3) Any other ideas? > > Thanks, > Michael

April 16, 2002

a problem using /tools/wineinstall

by davide madrisan

I had a problem using the wine installer script from wine-20020411. This is the brute change I've made to be able to end successfully the installation procedure. echo "Installing default Wine registry entries..." echo ## DEBUG : TMPREG == "/tmp/wineinstall.reg" ## DEBUG : REGAPI == "programs/regapi/regapi" # if ! $REGAPI setValue < $TMPREG > /dev/null <-- here is the problem # then { # rm -f $TMPREG # echo "Registry install failed." # conf_reset_question regapi_error # conf_question high regapi_error # exit 1 # } # else { # if we are converting from a .winerc file, running regapi once # will ONLY convert .winerc -> ~/.wine/config, it will not import the # registry data. so if we are converting we need to run regapi twice if [ "$CONVCONF" = 'yes' ] then if ! $REGAPI setValue < $TMPREG > /dev/null then rm -f $TMPREG echo "Registry install failed." conf_reset_question regapi_error conf_question high regapi_error exit 1 else echo echo "Registry entries successfully installed." fi else echo echo "Registry entries successfully installed." fi # } # fi I've choosen a wine-only installation, so no windows partition. If you need more informations, please let me know. Thanks. Saluti. -- Davide Madrisan GPG/PGP keys: <http://pgp.mit.edu/>

April 16, 2002

fixme:win32:PeekNamedPipe

by Michael Riedel

First of all I want to thank the community for the efforts spent in developing wine. It's simple a cool "tool" (sorry, it's more, I know). Now my problem: I installed wine-20020411 without having a native windows installation. I installed successfully a simulator software which obviously uses a tcl/tk-GUI to invoke other program moduls (compiler, library manager, simulator core) re-directing their stdin/stdout to the console window via pipes. It does not work for me and I get the message (infinitivly repeated): fixme:win32:PeekNamedPipe (00000080, (nil), 00000000, (nil), 0x406a2194, (nil)): stub Searchin the web I got no hit. Questions: (1) Can I avoid this by using a native windows-dll? If yes, which dll I have to install (but I assume it is a kernel-dll function and so it is not possible)? (2) I have no Windows programming background, but what do you think: Should I dare to implement this function or was it left open because of a tricky windows-API-Linux mapping problem? (3) Any other ideas? Thanks, Michael --

April 16, 2002

Re: building documentation failed

by Stefan Leichter

Michael Stefaniuc wrote: > > On Sat, Apr 13, 2002 at 01:36:37PM +0200, Stefan Leichter wrote: > > when i run make inside the ~wine/documentation directory i get an error when > > the pdf is created. The fix is easy for me, just an additional parameter (-s) > > for the command db2pdf. > > > > But before i send the attached patch to wine-patches i like to know if anyone > > can run make successful in the documentation directory. In this case we may > > have to add a check in the configure script. > > > > If someone is able to build the documentation successful please post the > > output of "db2pdf -v". > Yes, it works without the "-s" for me. > camus:~/work/wine/documentation$ db2pdf -v > DocBook-utils version 0.6.9 (jw version 1.1) > Hello, does the documentation build with '-s' too? Tschüß Stefan

April 16, 2002

Re: wine/ misc/options.c scheduler/process.c

by Dimitrie O. Paun

On April 15, 2002 10:14 am, Michael Cardenas wrote: > When was this patch applied? I don't see it on the wine-patches list. Maybe you should look in the wine-cvs list? :-) -- Dimi.

April 15, 2002

*update*: fixed tools/wineconf and tools/wineinstall

by Speeddymon

ok guys, I know some of you are going to flame me for my post to wine-patches, but I can explain...I did rtfm (the patch submitting archive) for the format of submitting a patch, but I have no internet at home my college's computers are all windows-only, so please, forgive me for sending the whole files and not just 2 patch files... __________________________________________________ Do You Yahoo!? Yahoo! Tax Center - online filing with TurboTax http://taxes.yahoo.com/

April 15, 2002

Re: PATCH: accept-deferred.diff (5 in series)

by Dimitrie O. Paun

On April 15, 2002 09:38 am, Martin Wilck wrote: > On Fri, 12 Apr 2002, Dimitrie O. Paun wrote: > > > + if ( lpCallerData || lpCalleeData || lpSQOS || lpGQOS ) > > > + WARN ("unsupported parameters!"); > > > > ^^^^ > > Shouldn't this be a FIXME instead? > > I don't think so - there is little to fix on the part of wine. > AFAICS the Linux network stack simply doesn't support passing of > additional parameters along with a connection request. But this is irrelevant. Wine is supposed to implement the Win32 API, whether we know how to do it or not (on some platforms) is another matter. But we should be vocal (i.e. FIXME :)) when we can not implement all the features, this way people will implement them in the future, even if this requires modifications to the kernel. There are only few cases where WARN is the right answer. Most messages are either ERR, FIXME or TRACE. -- Dimi.

April 15, 2002