- Wine-Devel - list.winehq.org

Video capturing under Wine, some overview
by Rolf Kalbermatter May 14, 2005

May 14, 2005

Prompted by the recent work by Maarten Lankhorst on getting his video cam to work in Wine, I did some in depth investigations on how Windows actually does this stuff. This is a summary of what I found and some thoughts about it. I would like some comments on how to progress. Basically applications have two obvious ways to use video capture services in Windows. One is avicap32.dll which is basically the Video for Windows way of doing this and the other one is ActiveMovie/DirectShow, soon to be obsoleted by Microsoft as well, as it seems. Avicap32 implements two functions, one is for the enumeration of the VfW devices registered in the system. For this it does enumerate all entries in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\MediaResources\msvid eo and for compatibilty reasons with 16bit Windows also in the Drivers32 section in system.ini. I have an untested version of this code already. The enumeration function does not try to detect any devices other than what it finds in above mentioned places. I assume that a webcam driver installation would have to do that. The second function in Avicap32.dll creates a (hidden) window which handles the actual interaction with the video device as well as being an optional user interface for the video data. The communication with the video device is always by so called installable drivers, like wineoss, etc. is used for audio devices. The interface to these installable video drivers is for the video device specific parts declared in a header file msviddrv.h which is really part of the DDK. (How would we add that to the Wine headers?) In modern Windows systems there is one MS provided installable driver vfwwdm32.dll, which is basically a translation layer between the installable interface and modern WDM stream based video drivers. Devenum uses the avicap enumeration function to find all registered VfW video sources and provide them to an application. Presumably there are other possible video source objects which would provide a direct interface to WDM stream class devices somehow and could be enumerated by devenum as well. DirectShow seems to be somwhat complicated. Video sources can be provided from VfW again, which is provided by the "VfW Capture Filter" class in qcap.dll. This is basically a DirectShow filter wrapper around the same installable driver interface as is used in avicap32.dll (and through above mentioned vfwwdm32.dll driver an application can also access WDM stream class video capture sources indirectly. How the direct interface to WDM stream class devices is provide I haven't found out yet but according to MSDN it should be possible somehow. For Wine purposes the VfW path seems the most interesting one. Separating the Video4Linux interface into an installable multimedia driver such as winev4l would cleanly separate platform specific code from the rest of the Wine DirectShow and Avicap implementation. Trying to emulate direct access to WDM based drivers would not be possible anyhow, as that would seem to require kernel driver support, which is mostly absent in Wine. I could probably hack an experimental winev4l driver together based on the work already done by Maarten Lankhorst, but would first want to make sure that this is considered the way to go, before investing more time into this. While the current implementation by Maarten is not as clean and nice because of the direct V4L dependency in standard Wine DLLs, it is something which already works somehow and could be integrated into Wine in quite a short time. What are the thoughts about this? Rolf Kalbermatter

5 4

sonicstage
by wino＠piments.com May 14, 2005

May 14, 2005

Hi , I have just bought a NH900 and wanted to try to get it to communicate with linux, I did a quick search before buying and found a ref to someone who reckoned to have got this working. I believe sonicstage2 under wine. Seem to have lost the link and google is not helping today. Anyone got any info on this ? TIA

1 0

Re: [WINEDOCS] Add French translation for Wine's FAQ
by Dimi Paun May 14, 2005

May 14, 2005

On Thu, 2005-05-12 at 16:49 +0200, Francois Gouget wrote: > This patch adds the framework for translating Wine's documentation and > adds a translation of the FAQ to French as a demonstration. No compressed patches, please. Also, the patch is big, and some things are cleaner than others. Let's break it down a bit. > Here is what the framework does: > > * first it moves most of en/Makefile.in to Make.rules.in so that this > code can be shared across the various translations. Well, the reason I didn't do that is for cases like incomplete translations. We can move to Make.rules.in: -- DB2* defines -- the targets (docs, pdf, etc) -- the tar rules The rest we can keep local, see how things evolve. We can always refactor it up. > * the actual translation is stored in a po file, one per documentation > document. So for French we currently have fr/wine-faq.po and later we > will also have wineusr-guide.po and winelib-guide.po. I'm not too hot about it to be honest. SGML is hard on the eye, this .po stuff seems to be even worse. But maybe it's easier to work with due to the various tools. If it makes it easier for you to maintain the translation, I'm cool with it. However, I'm not sure this will be the preferred way for all translators out there, so we shouldn't force it on everybody. > * Using po files lets us track exactly which translation paragraphs > are up to date and which are not. It also lets us leverage the tools > that have been developed around that format such as KBabel and maybe > even make it possible for contributors to translate the documentation > online using tools like Pootle (http://pootle.wordforge.org/) Kartouche > (http://i18n.kde.org/tools/kartouche/) or Rosetta > (https://launchpad.ubuntu.com/rosetta) This is great, but I doubt such tools can tell you *what* changed when something did change (the *what* here is "how did paragraph change") > * The link between the SGML files and the PO files and back is handled > by PO4A (http://po4a.alioth.debian.org/) I'm a bit worried about this one. It's new, debian specific, etc. There's no .rpm for it, and that makes me nervous. Tools like this must be easily available. Even if we go for it, maybe we'll have to keep the generated .sgml in CVS (just like configure). > * So configure.ac checks for the po4a tools. If they are missing then > the translated documentation cannot be built. I also added a > Makepo.rules.in that should be used by Makefiles building translated > documentation. What it does is just include the main Make.rules.in file > and add a couple of rules for generating SGML using PO files, and > extending the 'clean' target. This last bit cannot be put in the > top-level Make.rules.in because it does '$(RM) $(ALLBOOKS:%=%.sgml)' > which would be unfortunate in the en directory. The $(RM)... can remain local, and the rules can go in Make.rules.in. It would be confusing to have too many rule files. > sed -e 's/^<$article .*$ lang="en">$/<\1 lang="fr">/' -e > 's/^<$book .*$ lang="en">$/<\1 lang="fr">/' wine-faq.posgml > >wine-faq.sgml || (rm -f wine-faq.sgml && false) Nasty. BTW, the 'lang="en"' part of the patch can go in separately too. -- Dimi Paun <dimi(a)lattica.com> Lattica, Inc.

3 5

winefile
by Martin Fuchs May 14, 2005

May 14, 2005

Hi, I want to merge some Robert Dickenson's version of winfile (derived from the old winefile code in 2002) in the next time into winefile. At the same time I want to keep the code it in sync between the ReactOS code base and Wine. What do you think about splitting the source file into several smaller modules? winefile.c is quite large with its 4223 lines. Martin

3 4

Winelib's role in converting Windows applications
by Ira Krakow May 14, 2005

May 14, 2005

As many of you know, Brian and I are writing a book on Wine and Winelib for Prentice Hall. Brian's doing the Wine part; I'm doing the Winelib part. At Wineconf, I had a number of conversations about Winelib's role in converting Windows apps. The consensus seems to be that the most efficient conversion path is for much of the Windows app to stay in Visual C++ (or whatever) and that only the modules that specifically require native Linux calls should be recompiled, via MinGW/Dev-C++ on the Windows side, and Winemaker on the Linux side, into Winelib objects. For example, if the application requires PAM authentication, or a Linux-based help system, these modules would be separated out and encapsulated as Winelib objects. I was thinking of using PAM authentication as a good example, since it works for any authentication scheme that the application requires. This is the approach I plan to take. I welcome all feedback. Thanks. Ira

6 5

Re: Assertion fails in riched20; relay debug segfaults
by Adrian Harvey May 14, 2005

May 14, 2005

> On Wed, 11 May 2005 23:01:17 +1200, Adrian Harvey wrote: > > Well, I got some output at least! Never used strace before, but it > > looks kinda like a +relay trace for the kernel :-) > > Yep, that's exactly what it is :) > > > I also happened to be tailing the syslog (I was looking at something > > completely different) and I noticed that the following was written: > > > > May 11 22:50:55 orac kernel: strace[7749] trap stack segment rip:410c86 rsp:800000007b20 error:0 > > May 11 22:50:55 orac kernel: wine-preloader[7750]: segfault at 000000005575b624 rip 000000005575b624 rsp 00000000ffffc824 error 15 > > > > I doubt it's much use, but I thought any information might help here.... > > Somehow you managed to compile Wine as 64-bits, which isn't going to work. > I think you need to remove your current Wine installation and > install/compile it as 32 bits. > > thanks -mike OK, I've removed that install of wine form my system, updated to the latest CVS, re-run configure, make depend, make and make install, and still I get the same problem. I piped all the make output to a file, and the all the gcc commands have the -m32 flag after them (the winegcc ones don't, but these seem to all be linking rather than compiling.) I have run file over the binaries, and they all say ELF 32-bit LSB executable (or shared object, for the libraries). Out of interest, how did you know it had been compiled as 64 bit? Any ideas how I can track down which bit is being mis-compiled as 64 bit, so I can tidy up the build for that part? And is anyone else seeing the same symptoms (ie: WINEDEBUG="+relay" wine crashing)? I've got a pretty vanilla Fedora install, apart from being AMD64, so I shouldn't be unique.... thanks, Adrian

1 0

Re: Firefox 1.0.4 Installation
by Juan Lang May 13, 2005

May 13, 2005

Andrew wrote: > Firefox appeared to install correctly, but it won't start. Trying to > install under winedbg with WINDEBUG=+trace winedbg to terminate the > application after I typed "next": Hmm, works for me here. I assume you mean WINEDEBUG=, not WINDEBUG=. And, do you mean WINEDEBUG=trace or WINEDEBUG=trace+all? I think +trace will have no effect, as trace isn't the name of a debug channel. --Juan __________________________________ Yahoo! Mail Mobile Take Yahoo! Mail with you! Check email on your mobile phone. http://mobile.yahoo.com/learn/mail

1 0

Firefox 1.0.4 Installation
by Andrew Neil Ramage May 13, 2005

May 13, 2005

When I tried to install Firefox 1.0.4 for Windows, I got the following output in the shell window I started wine from. andrew(a)zeus:~/Download/Software> wine Firefox\ Setup\ 1.0.4.exe fixme:win:SetWindowTextW cannot set text L"Extracting" of other process window 0x7002e err:static:STATIC_SetIcon huh? hicon!=0, but info=0??? err:static:STATIC_SetIcon huh? hicon!=0, but info=0??? err:ntdll:NtQueryInformationToken Unhandled Token Information class! fixme:shell:Stream_WriteLocationInfo writing empty location info fixme:shell:Stream_WriteLocationInfo writing empty location info fixme:shell:Stream_WriteLocationInfo writing empty location info fixme:shell:Stream_WriteLocationInfo writing empty location info fixme:shell:Stream_WriteLocationInfo writing empty location info fixme:exec:ShellExecuteExW32 flags ignored: 0x00000340 andrew(a)zeus:~/Download/Software> err:ntdll:NtQueryInformationToken Unhandled Token Information class! fixme:ole:CoCreateInstance no classfactory created for CLSID {4955dd33-b159-11d0-8fcf-00aa006bcc59}, hres is 0x80040154 andrew(a)zeus:~/Download/Software> Firefox appeared to install correctly, but it won't start. Trying to install under winedbg with WINDEBUG=+trace winedbg to terminate the application after I typed "next": andrew(a)zeus:~/Download/Software> winedbg Firefox\ Setup\ 1.0.4.exe fixme:console:SetConsoleCtrlHandler (0x405ef3e0,1) - no error checking or testing yet WineDbg starting on pid 0x15 In 32 bit mode. Wine-dbg>next Process of pid=0x00000015 has terminated Wine-dbg> Does anyone know what is going wrong ? -- 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

Re: Extending File Dialog to include unix file paths [4/4]
by Steven Edwards May 13, 2005

May 13, 2005

Hi, --- Francois Gouget <fgouget(a)free.fr> wrote: > No, that should not happen. If an application links with a library that > exports funcA() and funcB() but it only calls funcA(), then it will only > import funcA() and it will work on a system where that library only > exports funcA(). OK maybe I am thinking of a bug in binutils or something. There were a few of them caused problems when building on mingw which result in me having to hack Winebuild a bit. Thanks Steven Yahoo! Mail Stay connected, organized, and protected. Take the tour: http://tour.mail.yahoo.com/mailtour.html

1 0

Re: winefile temporary allocations
by Francois Gouget May 13, 2005

May 13, 2005

On Fri, 13 May 2005, Martin Fuchs wrote: > Changelog > use macros for platform dependent temporary allocations [...] > +#define TMP_ALLOC(s) HeapAlloc(GetProcessHeap(), 0, s) > +#define TMP_FREE(p) HeapFree(GetProcessHeap(), 0, p) > +#else > +#define TMP_ALLOC(s) alloca(s) > +#define TMP_FREE(p) > #endif Why is this needed? Doesn't HeapAlloc work on any 'Win32' platform? -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ Before you criticize someone, walk a mile in his shoes. That way, if he gets angry, he'll be a mile away - and barefoot.

3 2