- Wine-Devel - list.winehq.org

Wine Janitorial Projects
by Dimitrie O. Paun Dec. 4, 2002

Dec. 4, 2002

Hi folks, The Wine Janitorial Project section has grown to the point where a separate page is warranted. It's been *greatly* enhanced, hopefully making the tasks a lot more explicit, easier to understand, and track. The first release of this page is available at: http://www.dssd.ca/wine/Wine-Janitorial-0.1.html As you are probably used to by now, the working version can be found here: http://www.dssd.ca/wine/Wine-Janitorial.html Please feel free to suggest new projects for the list. There are many things to cleanup in the tree, and having them available on an easy to read page increase the changes of (1) someone picking them up, and (2) us not forgeting them. So let me know if you come across anything that you feel should be on the list. Also, if you're working on something big, I can mark your name there so we can avoid duplicated work. Last but not least, there are a lot of small, self contained, and easy to get into tasks listed there. If you feel like getting your feet a bit wet in Wine development, this is an ideal opportunity to start, and get to know the project a little better. Just ask for help if you are new, and would like some help to get you started. -- Dimi.

2 2

Re: rpc_J_PL4
by Greg Turner Dec. 4, 2002

Dec. 4, 2002

On Wednesday 04 December 2002 02:31 am, Francois Gouget wrote: > On Wed, 4 Dec 2002, Greg Turner wrote: > [...] > > > Anyhoo, yes, I like something like what you are doing better, it > > seems that if anything might just break out of the blue, it would > > be the unicode version, right? So I should have done more like > > that and that way wine doesn't lose the test. knowing there's no > > crash involved makes the difference, I guess. > > Submitting for inclusion then :-) well, if it doesn't crash, I say we'd might as well run the tests but show traces instead of "ok"'s on failure.... I really wish there was a "whatever" macro that took the same syntax as "ok" but didn't constitute failure (or is there? perhaps I should make one?) Anyhow, until I make my mind up or whatever, Francois' patch is fine by me, considered rpc_J_PL4-r0 if it's OK to call it X11. -gmt

2 1

Re: Registering DLL's
by Jeff Smith Dec. 4, 2002

Dec. 4, 2002

>From: "Dimitrie O. Paun" <dpaun(a)rogers.com> > >On December 4, 2002 01:36 pm, Jeff Smith wrote: > > Does anyone have any better ideas on what the "Right Way" to tackle > > this item is? I am sure that adding external functions that do not > > exist in native versions is *not* the way. > >This was Alexandre's idea. Alexandre, a more detailed brain dump on >the configuration stuff would be useful. For example: > >C.1 Merge configuration into the registry > >Any gochas? What would it take? > >C.5 Make Wine's DLLs register themselves to avoid manual merging of the >winedefault.reg > >How should this be implemented? See Jeff's questions. > >C.6 Write wine.inf script to setup a new Wine installation > >Do we have the code that executes .inf scripts? Is this one >just a matter of writing the scripts? > >-- >Dimi. For those interested, here are a couple of links relating to the INF file format (1), and the SetupAPI (2). I don't know how complete our implementation is, but it can be found under wine/dlls/setupapi. 1.) http://msdn.microsoft.com/library/en-us/install/hh/install/create-inf_4l47.… 2.) http://msdn.microsoft.com/library/en-us/install/hh/install/setupapi_2faf.asp -- Jeff S _________________________________________________________________ Add photos to your messages with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail

1 0

what happened wineboot?
by Matthew Davison Dec. 4, 2002

Dec. 4, 2002

I have been trying to get programs installed which place entries in RunOnce. I read a while ago about a wineboot program which automates these jobs, thus simulating a reboot, similar to what crossover does. Does anyone have such a program, as I have been looking for it and cant find it. -- Matthew Davison <m.davison(a)virgin.net>

2 1

Re: Dll separation question
by Rolf Kalbermatter Dec. 4, 2002

Dec. 4, 2002

Martin Wilck <Martin.Wilck(a)fujitsu-siemens.com> wrote: >I am sorry to say that I still don't quite understand this issue, but - >can anybody point me to a resource saying what exactly I may or may not >do when writing code for a wine DLL? In particular, when writing code >for DLL X, which functions from other DLLs may I call? This interests me as well! >Example: When writing netapi32 code, can I call advai32 Registry >functions to obtain config options, or do I need to use the (IMO rather >awkward) ntdll interface ? I was under the impression that the main issue was that no DLL calls not officially exported functions in any other DLL, with officially exported meaning any function which is not wine specific eg. is also exported by the according MS Windows DLL. I have gotten the impression that all Wine specific exports start with the uppercase name of the DLL which implements them followed by an underscore and then the actual name and the main and final target is to get rid of any and all exports of such functions. So in general I would think that usage of the Reg.. functions from ADVAPI32 should be ok, but I'm not familiar with NETAPI32 at all and how it relates to the rest of Win. Maybe it is more considered part of the actual Win kernel and therefore should maybe call the Nt... functions in NTDLL. But the Reg... functions are really just a convinience wrapper around the according Nt... functions and ADVAPI32 is certainly a well known standard DLL. >Btw: Dll separation is a really complex issues and I think I'm not the >only one who feels he doesn't quite understand what it means. IMO winehq >needs a very clear description of that somewhere where it's easy to find. Some documentation or a link to them would certainly help. Rolf Kalbermatter

1 0

Dll separation question
by Martin Wilck Dec. 4, 2002

Dec. 4, 2002

I am sorry to say that I still don't quite understand this issue, but - can anybody point me to a resource saying what exactly I may or may not do when writing code for a wine DLL? In particular, when writing code for DLL X, which functions from other DLLs may I call? Example: When writing netapi32 code, can I call advai32 Registry functions to obtain config options, or do I need to use the (IMO rather awkward) ntdll interface ? Btw: Dll separation is a really complex issues and I think I'm not the only one who feels he doesn't quite understand what it means. IMO winehq needs a very clear description of that somewhere where it's easy to find. 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

2 1

Painting message order?
by Mike Hearn Dec. 4, 2002

Dec. 4, 2002

Hi all, My beloved SVG plugin broke again :( For some reason it's not repainting properly, in fact, the only way I can force it to repaint when running in wine desktop, internet explorer kiosk mode (ie it fills a window) is by toggling high quality/low quality which controls antialiasing. trace:message:SPY_EnterMessage (0x10041) L"{ATL:5303EA68}" message [000f] WM_PAINT dispatched wp=00000000 lp=00000000 trace:message:SPY_EnterMessage (0x10041) L"{ATL:5303EA68}" message [0085] WM_NCPAINT sent from self wp=00000001 lp=00000000 trace:message:SPY_EnterMessage (0x10041) DefWindowProc32: WM_NCPAINT [0085] wp=00000001 lp=00000000 trace:message:SPY_ExitMessage (0x10041) DefWindowProc32: WM_NCPAINT [0085] returned 00000000 trace:message:SPY_ExitMessage (0x10041) L"{ATL:5303EA68}" message [0085] WM_NCPAINT returned 00000000 trace:message:SPY_EnterMessage (0x10041) L"{ATL:5303EA68}" message [0014] WM_ERASEBKGND sent from self wp=000008a8 lp=00000000 trace:message:SPY_ExitMessage (0x10041) L"{ATL:5303EA68}" message [0014] WM_ERASEBKGND returned 00000001 trace:message:SPY_ExitMessage (0x10041) L"{ATL:5303EA68}" message [000f] WM_PAINT returned 00000000 That's a message trace of the paint cycle (when I make it paint by minimizing the wine window for instance. It sends WM_PAINT, the does the NCPAINT thing which seems to be do do with window borders, and then some ERASEBKGND messages come from somewhere. I have a sneaking suspicion that the background gets erased after it's painted and not before, but that's a total shot in the dark and the absence of flicker kind of makes my theory look not so strong. I did some traces with +gdi as well, but it wasn't very helpful. There were lots of GetObjPtr and locking methods called, but I didn't see any actual obviously drawing related calls. There was 1 warning: GetObjPtr was called at one point with nil. What does this mean? I can't find any documentation about GetObjPtr on google. I'll look at the sources later to see if I can figure out what's wrong. Anyway, my final question is : is there a way to alter the colour with which the background is erased? Even if it screws up rendering elsewhere just for debugging i'd like to see if I can make it display as anything *except* offwhite. If so then it confirms my theory. Or are those messages processed by the plugin itself? thanks -mike -- Mike Hearn <m.hearn(a)signal.qinetiq.com> QinetiQ - Malvern Technology Center

3 3

Re: Fix winsock conformance test on Windows NT
by Francois Gouget Dec. 4, 2002

Dec. 4, 2002

On 4 Dec 2002, Martin Wilck wrote: > Am Mit, 2002-12-04 um 10.21 schrieb Francois Gouget: > > > sock.c:456: Test failed: event_client (ea): connect error: 10022 > > I could reproduce that on NT4. [...] > But setting the socket to overlapped mode helps. So with the > following one-liner we should be fine. Yep, that works. Thanks :-) -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ A particle is an irreducible representation of the Poincaré Group - Eugene Wigner

1 0

Vstserver v0.2.0
by Kjetil S. Matheussen Dec. 4, 2002

Dec. 4, 2002

http://www.notam02.no/arkiv/src/ VSTServer V0.2.0. ----------------- GRM tools 1 runs with the 25.11.2002 release of wine. ABOUT Vstserver is a program that must be running when using programs using vstlib. Vstlib is a library that can be used by programs to run windows vst audio plugins under linux/freebsd/i386solaris/etc. RUNNING First you should set the "VST_PATH" environment variable pointing to the directory where your VST dll files are placed. Then to run the vstserver program, you have to cd into the directory where the "vstservant.so" file is placed (and thats most probably the directory where this README file is placed), and then run the "vstserver" program. DEVELOPMENT Vstserver is released under the GPL, and vstlib under LGPL. If there comes many source-contributions, I will probably make it a sourceforge project. To use vstlib in a program, look at the tests/exampleclient program, and various vst plug-in documentation. The interface to the vstlib consists only of two functions (new/delete), the rest is like you would do when programming for windows, macos(X), beos, irix, etc. You do currently not have access to the audioMaster callback function from a client. If you need access to it, please contact me, and I'll extend the library and the vstservant program. CURRENT STATUS Vstserver seems to be very stable. Very few vst plug-ins and instruments wont run, and I am not able to hear any latency. And plug-ins does not seem to cause more cpu-power than under windows. BUGS 1. When loading a lot of plugins simultaniously, the X server crashes (!). I manage to do that when running the ladspa "listplugins" program _many_ times in a row like this: "listplugins &". I dont know the cause of it. (running redhat 7.2, with latest XFree rpm updates installed) 2. Shared memory handlig might be faulty. I suspect that it doesnt free resources because clients sometime complains about not getting shared memory. (see server/shmhandler.c) 3. The graphics code to support gui is just hacked together by looking at the winemine source-code included with the wine distribution. I have no windows programming experience or documentation about the windows API, so if someone that have windows programming experience would have a look at the code and check that its fine/not fine, that would be, eh, fine. (The code I'm unsure about is server/win/winwin.c and server/win/main.c, about 200 lines of code.) NOT WORKING DLLS - "SimSynth VSTi demo.dll" - The standalone version wont even run under wine, so theres currently not much hope for this one. Please send me dlls that wont work. FUTURE -Make a DX-plugin server. (would be fun running pi-warp under linux). -Add gui to the plugins not providing gui themselves. (help wanted, windows programming) HISTORY 0.1.1 -> 0.2.0: -When upgrading my wine installation from the 31.10.2002 version to the 25.11.2002 version, the "err:local:LOCAL_GetBlock not enough space in GDI heap 01f7 for 24 bytes" problem got much worse. So I changed the vstserver program to be a normal unix program that starts a winelib program called "vstservant.so" for each new request it gets. This seems to have solved the GDI heap problem totally. -Extended the audioMaster function yet more by copying a lot of opcode handlings from the vst~ pd external by Mark Williamson. I didn't ask before doing this, but according to the pdf file, he used some code from the plugin~ external, which then should automaticly make vst~ GPL. The positive result is that more plugins works. The negative result is that you now need to patch the steinberg "vst/aeffectx.h" file before compiling, as there are some strange things in it. -Some smaller fixes here and there. 0.1.0 -> 0.1.1: -Replaced the old audioMaster function in the server with the one coming from the plugin~ source by Jarno Seppänen. Result is that GRM tools 2 now works. (I thought there were a different reason it didnt work before, without going into further detail...) Seems like vst instruments works better now too. The mousedrag problem seems to have dissapeared. -Removed some debug printings. 0.0.2 -> 0.1.0: -Added graphics support to the plug-ins. (effEditOpen/effEditClose dispatch opcodes works.) -Fixed the makefile a bit. 0.0.1 -> 0.0.2: -Fixed the process function in vstlib. -Fixed the problem with processreplace could fail if sampleframes was to high. -Added processreplace simulation to vstlib, in case plugin doesnt implement processreplace itself. CREDITS vstserver and vstlib are made by Kjetil S. Matheussen / Notam. k.s.matheussen(a)notam02.no Some programming hints is gathered by looking at the pd vst-object plugin~ source and the jack soundserver source. --

1 0

Re: The conformance tests need you!
by Martin Wilck Dec. 4, 2002

Dec. 4, 2002

Am Mon, 2002-12-02 um 19.12 schrieb Francois Gouget: > > Am Sam, 2002-11-30 um 04.02 schrieb Francois Gouget: > > > > > > Come on people, we can do better. > > > Send fixes to wine-patches, and send me emails to so that I update this > > > table. > > > > I'll have a look at the winsock stuff. > > Thanks :-) I am currently having trouble with running stuff natively on Windows. Can anybody run the winsock test with verbose output (trace enabled) on Windows NT and send me the result ? 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

3 3