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

Re: what happened wineboot?

by Steven Edwards

Ask the codeweavers guys and look at the crossover stuff. Andi wrote wineboot and discussed it at wineconf but it has never been commited to the winehq cvs. It is in the list archive somewhere also...... Steven --- Matthew Davison <m.davison(a)virgin.net> wrote: > 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> > > __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com

Dec. 4, 2002

Re: Dll separation question

by Rolf Kalbermatter

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

Dec. 4, 2002

Re: Registering DLL's

by Dimitrie O. Paun

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.

Dec. 4, 2002

what happened wineboot?

by Matthew Davison

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>

Dec. 4, 2002

Re: Dll separation question

by Alexandre Julliard

Martin Wilck <Martin.Wilck(a)fujitsu-siemens.com> writes: > 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? The rules are that you can only call exported functions, and that you can't add dll imports that would create a circular dependency. You can find the list of existing dependencies near the end of dlls/Makefile.in. > 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 ? netapi32 already imports advapi32, so you can freely use the registry functions from there. -- Alexandre Julliard julliard(a)winehq.com

Dec. 4, 2002

Re: Painting message order?

by Robert North

Paul Millar paulm-at-astro.gla.ac.uk |Wine Mailing Lists| wrote: >On 3 Dec 2002, Mike Hearn wrote: > > >>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. >> >> > >Well, speaking in ignorance (I freely admit to it ;) it *could* have >something to do with problem 2 of: > > http://www.winehq.com/hypermail/wine-devel/2002/11/0803.html > >corruption when dialogue boxes are moved around. I tried it again today >(with cvs a few days old) and the problem still exists. > >---- >Paul Millar > Don't know if it helps, but I see similar corruption to Word on Painter 5. I don't know if it would help either of you guys, but I could get some traces/debug output, if someone gives me hints at to what to trace/break on. -Rob. > >

Dec. 4, 2002

Registering DLL's

by Jeff Smith

I was looking at entry C.5 of the 0.9 Todo list: "Make Wine's DLLs register themselves to avoid manual merging of the winedefault.reg [TODO]" Upon first glance I figured the approach is to (not necissarily in this order): add regsvr32.exe calls in the installation scripts, fill in the DllRegisterServer (and DllUnregisterServer) sections of the appropriate libraries, and remove those entries from winedefault.reg. About a dozen dll files have their names in winedefault.reg. So I checked the native versions of these files, and only half of them have a DllRegisterServer function. I did some further research and found that perhaps DllInstall was what I needed. Well, that only adds one library, and two have *both* functions. 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. -- Jeff S _________________________________________________________________ Add photos to your e-mail with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail

Dec. 4, 2002

Re: Fix winsock conformance test on Windows NT

by Francois Gouget

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

Dec. 4, 2002

Re: Use COMSPEC command interpreter to run .bat files.

by Alexandre Julliard

Sylvain Petreolle <spetreolle(a)yahoo.fr> writes: > COMSPEC is set find it in windows/system => we should change it in > files/directory.c to point to windows/system32 instead. COMSPEC is set in directory.c to point to the windows system directory, this is correct and should not be changed. The bug is that wineinstall puts stuff in windows/system32 but specifies windows/system as system dir in the config file. -- Alexandre Julliard julliard(a)winehq.com

Dec. 4, 2002

Re: Use COMSPEC command interpreter to run .bat files.

by Alexandre Julliard

Uwe Bonnes <bon(a)elektron.ikp.physik.tu-darmstadt.de> writes: > It's tools/wineinstall that does rename wcmd.exe to cmd.exe when installing. > I don't think this is right. Other opinions? Actually it could be argued that this is the right thing to do, since wcmd is supposed to be a replacement for cmd.exe. But then of course we should rename it consistently everywhere, not just in wineinstall. -- Alexandre Julliard julliard(a)winehq.com

Dec. 4, 2002

Re: Use COMSPEC command interpreter to run .bat files.

by davep

On Wednesday 04 Dec 2002 09:48, Sylvain Petreolle wrote: > Here is what I get in wcmd : > C>dir cygwin.bat > Volume in drive C is > Volume Serial Number is 1234-5678 > > Directory of C:\cygwin\ > > 01/03/2002 05:05:16 55 cygwin.bat > 1 file 55 bytes > 0 directories 2,218,336,256 bytes free > > C>wcmd /c cygwin.bat > File not found > > C> For that to work wcmd needs to be able to find itself (ie it must be in one of the places Win32 searches for executables). wcmd has no special knowledge of its own name or how to invoke itself. However even if wcmd is able to start another version of itself there is another problem. wcmd started in this way does not inherit the current directory from its parent, so unless you included the full path to cygwin.bat the child wcmd would not find it. Dave .

Dec. 4, 2002

Re: Use COMSPEC command interpreter to run .bat files.

by Dimitrie O. Paun

On December 4, 2002 12:26 pm, davep wrote: > wcmd started in this way does not inherit the current > directory from its parent And isn't this a problem? -- Dimi.

Dec. 4, 2002

Vstserver v0.2.0

by Kjetil S. Matheussen

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. --

Dec. 4, 2002

Re: The conformance tests need you!

by Dimitrie O. Paun

On December 4, 2002 04:35 am, Martin Wilck wrote: > I guess for newbies it will be pretty much impossible to figure this > out. Or is there a really simple way that I just missed? This is why I think we need someone to build the tests, and make them available for people to run on Windows. Even if we simplify the process (which we should do!), it's still too much trouble if we want to have them tests on many different Windows versions at regular intervals. -- Dimi.

Dec. 4, 2002

Re: Use COMSPEC command interpreter to run .bat files.

by Uwe Bonnes

>>>>> "Sylvain" == Sylvain Petreolle <spetreolle(a)yahoo.fr> writes: Sylvain> I found why we have a 'not found', the problem is that wcmd Sylvain> isn't installed by default in c:\windows\system32, it installed Sylvain> as "cmd". should we add it to wineinstall or what ? Sylvain> for the false COMSPEC problem, I found it too. it is in Sylvain> files/directory.c:107/180. it assigns wcmd as interpreter. Sylvain> to give a summary: wineinstall installs cmd.exe in Sylvain> windows/system32. COMSPEC is set to search wcmd.exe => we need Sylvain> to add it in wineinstall. COMSPEC is set find it in Sylvain> windows/system => we should change it in files/directory.c to Sylvain> point to windows/system32 instead. It's tools/wineinstall that does rename wcmd.exe to cmd.exe when installing. I don't think this is right. Other opinions? Bye -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------

Dec. 4, 2002

Re: Use COMSPEC command interpreter to run .bat files.

by Sylvain Petreolle

I found why we have a 'not found', the problem is that wcmd isn't installed by default in c:\windows\system32, it installed as "cmd". should we add it to wineinstall or what ? for the false COMSPEC problem, I found it too. it is in files/directory.c:107/180. it assigns wcmd as interpreter. to give a summary: wineinstall installs cmd.exe in windows/system32. COMSPEC is set to search wcmd.exe => we need to add it in wineinstall. COMSPEC is set find it in windows/system => we should change it in files/directory.c to point to windows/system32 instead. Comments ? > To parse inside wcmd > > c> wcmd /c cygwin.bat > > we need to have a look at wcmd itself. Probably it doesn't know > itself :-) > ===== Sylvain Petreolle spetreolle(a)users.sourceforge.net Fight against Spam ! http://www.euro.cauce.org/en/index.html ICQ #170597259 "Don't think you are. Know you are." Morpheus in Matrix, chapter 15. ___________________________________________________________ Soyez solidaire soutenez laction du Téléthon avec Yahoo! France. http://www1.telethon.fr/030-Espace-Relais-Dons/webtirelire1.asp?hebergeur_i…

Dec. 4, 2002

Dll separation question

by Martin Wilck

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

Dec. 4, 2002

Re: Fix winsock conformance test on Windows NT

by Martin Wilck

Am Mit, 2002-12-04 um 10.21 schrieb Francois Gouget: > > With the following fixes, the winsock test runs fine (0 errors) on Win > > NT (and Wine!). > > I applied the patch but the test still fails and gets stuck on NT4: Strange - on my Win2k box it runs perfectly. Error 10022 is WSAEINVAL - I have no idea how this could happen, unless I did something wrong with the TLS stuff. However it runs on W2k, it runs on Wine, and AFAICT it's programmed to the specs. What now? 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

Dec. 4, 2002

Re: Midi, was Re: Direct3D8 regression/bug

by Justin

----- Original Message ----- From: "Sylvain Petreolle" <spetreolle(a)yahoo.fr> To: "Justin" <justintyme(a)accesswave.ca>; "Greg Turner" <gmturner007(a)ameritech.net> Cc: "wined" <wine-devel(a)winehq.com> Sent: Wednesday, December 04, 2002 5:55 AM Subject: Midi, was Re: Direct3D8 regression/bug > > > You wrote exactly what I wanted to avoid when I put "mplayer.exe" > > > It isn't mplayer from mplayerhq.hu, but windows mplayer.exe from > > > Windows ME. > > > I need it to test midi with winealsa.drv. > > > Now I didn't succeed because of Registry glitch: couldn't find midi > > out > > > (%s)\n > > > > I get a similiar Registry glitch error with a game I run ( The Realm) > > using wineoss.drv I think. > > > > Kevin > > > I get the same with es1371 module, this is why I tried to switch to > alsa. > When I use wineoss.drv with alsa (in order to use OSS emulation), > I get > fixme:mcimidi:MIDI_mciPlay NIY: MIDI port=0, track=1 > fixme:mcimidi:MIDI_mciPlay NIY: MIDI port=0, track=2 > fixme:mcimidi:MIDI_mciPlay NIY: MIDI port=0, track=3 > using kde + arts and wineoss.drv (I also tried with alsa installed but never was sure if I had it set up correctly, although wave, midi, mp3 all seemed to play ok) [kevin(a)localhost realm]$ wine --debugmsg +mcimidi,+midi,+msacm,+dsound,+wave wlaunch.exe trace:msacm:DllMain 0x410b0000 0x1 (nil) trace:msacm:MSACM_RegisterDriver ('MSACM.msg711', 'msg711.acm', (nil)) trace:msacm:MSACM_RegisterDriver ('msacm.vivog723', 'vivog723.acm', (nil)) trace:msacm:MSACM_RegisterDriver ('msacm.lhacm', 'lhacm.acm', (nil)) trace:msacm:MSACM_RegisterDriver ('msacm.iac2', 'C:\WINDOWS\SYSTEM\IAC25_32.AX', (nil)) trace:msacm:MSACM_RegisterDriver ('msacm.sl_anet', 'sl_anet.acm', (nil)) trace:msacm:MSACM_RegisterDriver ('MSACM.imaadpcm', 'imaadp32.acm', (nil)) trace:msacm:MSACM_RegisterDriver ('MSACM.msadpcm', 'msadp32.acm', (nil)) trace:msacm:MSACM_RegisterDriver ('MSACM.msgsm610', 'msgsm32.acm', (nil)) trace:msacm:MSACM_RegisterDriver ('MSACM.trspch', 'tssoft32.acm', (nil)) trace:msacm:MSACM_RegisterDriver ('msacm.imc', 'C:\WINDOWS\SYSTEM\imc32.acm', (nil)) trace:msacm:MSACM_RegisterDriver ('msacm.voxacm160', 'vct3216.acm', (nil)) trace:msacm:MSACM_RegisterDriver ('msacm.msnaudio', 'msnaudio.acm', (nil)) trace:msacm:MSACM_RegisterDriver ('msacm32.dll', 'msacm32.dll', (nil)) trace:msacm:WAVEMAP_DriverProc (00000000, 0x40393a78, 00000001, 00000000, 00000000) trace:msacm:WAVEMAP_DriverProc (00000000, 0x40393a78, 00000002, 00000000, 00000000) trace:msacm:WAVEMAP_DriverProc (00000000, 0x40393a78, 00000003, 00000000, 00000000) trace:msacm:WAVEMAP_widMessage (0, 0064, 00000000, 00000000, 00000000); trace:msacm:WAVEMAP_widMessage (0, 0032, 00000000, 00000000, 00000000); trace:msacm:WAVEMAP_wodMessage (0, 0064, 00000000, 00000000, 00000000); trace:msacm:WAVEMAP_wodMessage (0, 0003, 00000000, 00000000, 00000000); trace:msacm:MIDIMAP_modMessage (0, 0064, 00000000, 00000000, 00000000); trace:msacm:MIDIMAP_modMessage (0, 0001, 00000000, 00000000, 00000000); fixme:system:ChangeDisplaySettingsA (0x530364,0x00000002), stub flags=TEST, fixme:system:ChangeDisplaySettingsA (Putting X in this mode beforehand might help) fixme:ntdll:NtQuerySystemInformation (0x00000008,0x406b1d94,0x00000030,0x406b1dfc) stub trace:msacm:DllMain 0x410b0000 0x2 (nil) trace:msacm:DllMain 0x410b0000 0x2 (nil) trace:msacm:MIDIMAP_modMessage (65535, 0003, 406B297C, 403EC594, 00000000); trace:msacm:modOpen (0x406b297c 0x403ec594 00000000) err:msacm:MIDIMAP_LoadSettingsDefault Registry glitch: couldn't find midi out (SB PCI128 MIDI Out) trace:msacm:DllMain 0x410b0000 0x2 (nil) fixme:hook:NotifyWinEvent (32768,0x20030,-4,1)-stub! fixme:hook:NotifyWinEvent (32768,0x20030,-4,2)-stub! fixme:hook:NotifyWinEvent (32768,0x20030,-4,3)-stub! fixme:hook:NotifyWinEvent (32768,0x20032,-4,1)-stub! fixme:hook:NotifyWinEvent (32768,0x20032,-4,2)-stub! trace:msacm:DllMain 0x410b0000 0x3 (nil) trace:msacm:MIDIMAP_modMessage (0, 0065, 00000000, 00000000, 00000000); trace:msacm:WAVEMAP_widMessage (0, 0065, 00000000, 00000000, 00000000); trace:msacm:WAVEMAP_wodMessage (0, 0065, 00000000, 00000000, 00000000); trace:msacm:WAVEMAP_DriverProc (00000001, 0x40393a78, 00000004, 00000000, 00000000) trace:msacm:WAVEMAP_DriverProc (00000000, 0x40393a78, 00000005, 00000000, 00000000) trace:msacm:WAVEMAP_DriverProc (00000000, 0x40393a78, 00000006, 00000000, 00000000) trace:msacm:DllMain 0x410b0000 0x0 0x1 This is were I leave the game. Sound should be playing at this point. Hmm, I don't see a dsound error which I had before. I have to run, but I'll try again later today. Kevin > > > ===== > Sylvain Petreolle > spetreolle(a)users.sourceforge.net > Fight against Spam ! http://www.euro.cauce.org/en/index.html > ICQ #170597259 > > "Don't think you are. Know you are." Morpheus in Matrix, chapter 15. > > ___________________________________________________________ > Soyez solidaire soutenez l'action du Téléthon avec Yahoo! France. > http://www1.telethon.fr/030-Espace-Relais-Dons/webtirelire1.asp?hebergeur_id =1309 >

Dec. 4, 2002

Re: Use COMSPEC command interpreter to run .bat files.

by Uwe Bonnes

>>>>> "Sylvain" == Sylvain Petreolle <spetreolle(a)yahoo.fr> writes: Sylvain> I known it works directly, but it should work with wcmd... >> From inside wcmd you can run the batch directly. In this case, th >> epatch isn't involed neither. >> >> Try C> cygwin.bat To parse inside wcmd c> wcmd /c cygwin.bat we need to have a look at wcmd itself. Probably it doesn't know itself :-) Bye -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------

Dec. 4, 2002

Re: Use COMSPEC command interpreter to run .bat files.

by Sylvain Petreolle

I known it works directly, but it should work with wcmd... > From inside wcmd you can run the batch directly. In this case, th > epatch > isn't involed neither. > > Try > C> cygwin.bat > ===== Sylvain Petreolle spetreolle(a)users.sourceforge.net Fight against Spam ! http://www.euro.cauce.org/en/index.html ICQ #170597259 "Don't think you are. Know you are." Morpheus in Matrix, chapter 15. ___________________________________________________________ Soyez solidaire soutenez laction du Téléthon avec Yahoo! France. http://www1.telethon.fr/030-Espace-Relais-Dons/webtirelire1.asp?hebergeur_i…

Dec. 4, 2002

Midi, was Re: Direct3D8 regression/bug

by Sylvain Petreolle

> > You wrote exactly what I wanted to avoid when I put "mplayer.exe" > > It isn't mplayer from mplayerhq.hu, but windows mplayer.exe from > > Windows ME. > > I need it to test midi with winealsa.drv. > > Now I didn't succeed because of Registry glitch: couldn't find midi > out > > (%s)\n > > I get a similiar Registry glitch error with a game I run ( The Realm) > using wineoss.drv I think. > > Kevin > I get the same with es1371 module, this is why I tried to switch to alsa. When I use wineoss.drv with alsa (in order to use OSS emulation), I get fixme:mcimidi:MIDI_mciPlay NIY: MIDI port=0, track=1 fixme:mcimidi:MIDI_mciPlay NIY: MIDI port=0, track=2 fixme:mcimidi:MIDI_mciPlay NIY: MIDI port=0, track=3 ===== Sylvain Petreolle spetreolle(a)users.sourceforge.net Fight against Spam ! http://www.euro.cauce.org/en/index.html ICQ #170597259 "Don't think you are. Know you are." Morpheus in Matrix, chapter 15. ___________________________________________________________ Soyez solidaire soutenez laction du Téléthon avec Yahoo! France. http://www1.telethon.fr/030-Espace-Relais-Dons/webtirelire1.asp?hebergeur_i…

Dec. 4, 2002

Re: Use COMSPEC command interpreter to run .bat files.

by Uwe Bonnes

>>>>> "Sylvain" == Sylvain Petreolle <spetreolle(a)yahoo.fr> writes: Sylvain> Here is what I get in wcmd : C> dir cygwin.bat Sylvain> Volume in drive C is Volume Serial Number is 1234-5678 Sylvain> Directory of C:\cygwin\ Sylvain> 01/03/2002 05:05:16 55 cygwin.bat 1 file 55 bytes 0 directories Sylvain> 2,218,336,256 bytes free C> wcmd /c cygwin.bat Sylvain> File not found >From inside wcmd you can run the batch directly. In this case, th epatch isn't involed neither. Try C> cygwin.bat Bye -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------

Dec. 4, 2002

Re: Use COMSPEC command interpreter to run .bat files.

by Sylvain Petreolle

Here is what I get in wcmd : C>dir cygwin.bat Volume in drive C is Volume Serial Number is 1234-5678 Directory of C:\cygwin\ 01/03/2002 05:05:16 55 cygwin.bat 1 file 55 bytes 0 directories 2,218,336,256 bytes free C>wcmd /c cygwin.bat File not found C> > If you run "wine --debugmsg +process -- wcmd /c cygwin.bat", my patch > shouldn't be involved. Is in your case a 'CreateProcess (...,"....bat > ...")' somehow involved? Only then my patch should change anything. > Wcmd should be found somehow magically, either in ../wine/programs or > by the > COMSPEC variable. > link_app wcmd "$CROOT/windows/system32/cmd.exe As shown in the above line fom wineinstall, its put in C:\windows\system32, with some other built-in .exe. > Where does the wine install process put WCMD? As I always run wine in > my > build tree, I can't check... ===== Sylvain Petreolle spetreolle(a)users.sourceforge.net Fight against Spam ! http://www.euro.cauce.org/en/index.html ICQ #170597259 "Don't think you are. Know you are." Morpheus in Matrix, chapter 15. ___________________________________________________________ Soyez solidaire soutenez laction du Téléthon avec Yahoo! France. http://www1.telethon.fr/030-Espace-Relais-Dons/webtirelire1.asp?hebergeur_i…

Dec. 4, 2002

Cygwin/wine : partial success

by Sylvain Petreolle

Making only one tweak to /etc/profile, cygwin manages to launch partially. If you comment the line USER="`id -un`", bash -l -i displays : (I placed "I'm here!" at the end of .bahrc) C>bash -l -i I'm here! syl(a)snoop ~ $ logout C> The next step will be identify the reason why it just logs out. I tried zsh but it says zsh: error on TTY read: permission denied and then I have no keyboard in wcmd. mc begin to display itself,then makes disappear the wcmd window, the program doesn't terminate. (??) ===== Sylvain Petreolle spetreolle(a)users.sourceforge.net Fight against Spam ! http://www.euro.cauce.org/en/index.html ICQ #170597259 "Don't think you are. Know you are." Morpheus in Matrix, chapter 15. ___________________________________________________________ Soyez solidaire soutenez laction du Téléthon avec Yahoo! France. http://www1.telethon.fr/030-Espace-Relais-Dons/webtirelire1.asp?hebergeur_i…

Dec. 4, 2002

Re: Direct3D8 regression/bug

by Justin

----- Original Message ----- From: "Sylvain Petreolle" <spetreolle(a)yahoo.fr> To: "Greg Turner" <gmturner007(a)ameritech.net> Cc: "wined" <wine-devel(a)winehq.com> Sent: Tuesday, December 03, 2002 7:30 PM Subject: Re: Direct3D8 regression/bug > --- Greg Turner <gmturner007(a)ameritech.net> a écrit : > On Tuesday 03 > December 2002 02:34 pm, Sylvain Petreolle wrote: > > > NVidia and its bugged binary shit... > > > > yuck. doesn't xfree or drm-kernel project provide a decent driver > > for > > you guys? > the nv driver provided with Xfree is way too slow to use it on Wine. > and I don't want to have to compile Xfree myself. > > You wrote exactly what I wanted to avoid when I put "mplayer.exe" > It isn't mplayer from mplayerhq.hu, but windows mplayer.exe from > Windows ME. > I need it to test midi with winealsa.drv. > Now I didn't succeed because of Registry glitch: couldn't find midi out > (%s)\n I get a similiar Registry glitch error with a game I run ( The Realm) using wineoss.drv I think. Kevin > > > Note : it crashes even with mplayer.exe !! > > > > mplayer is very, very agressive and takes wierd liberties with > > compiler > > flags. compile it yourself, disable stuff you don't want, and pay > > attention to the compiler flags you get. when all is said and done > > ... > > > ===== > Sylvain Petreolle > spetreolle(a)users.sourceforge.net > Fight against Spam ! http://www.euro.cauce.org/en/index.html > ICQ #170597259 > > "Don't think you are. Know you are." Morpheus in Matrix, chapter 15. > > ___________________________________________________________ > Soyez solidaire soutenez l'action du Téléthon avec Yahoo! France. > http://www1.telethon.fr/030-Espace-Relais-Dons/webtirelire1.asp?hebergeur_id =1309 >

Dec. 4, 2002

Re: The conformance tests need you!

by Martin Wilck

Hi Francois, You may have seen that Alexandre applied my patch, so the winsock test issue appears to be fixed. I inserted an #ifdef _WIN32 clause at the top to adjust includes to run with VC++. I wonder if this should be done for all test programs to avoid the editing hassle. The "Running tests on Windows" section in the Wine docs _definitely needs correction_. It currently doesn't talk about running tests on Windows at all - it covers running tests in Wine!! Besides, it is largely out of date, talking about perl tests and such. With the current docs, my level of wine experience, and a fair amount of googling, it took me about 2 hours to find out how to get the tests running on Windows (1 - do "make test" in wine, 2 - copy .c files and wine/test.h to Windows, 3 - import everything into a VC++ project, 4 - adjust #include directives with trial and error, 5 - go for it). I guess for newbies it will be pretty much impossible to figure this out. Or is there a really simple way that I just missed? 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

Dec. 4, 2002

Re: Fix winsock conformance test on Windows NT

by Francois Gouget

On 3 Dec 2002, Martin Wilck wrote: > > With the following fixes, the winsock test runs fine (0 errors) on Win > NT (and Wine!). I applied the patch but the test still fails and gets stuck on NT4: sock.c:694: **** STARTING TEST 0 **** sock.c:332:simple_server (d3) starting sock.c:341:simple_server (d3) ready sock.c:346:simple_server (d3): waiting for client sock.c:391:simple_client (dd): starting sock.c:394:simple_client (dd): server ready sock.c:391:simple_client (b9): starting sock.c:394:simple_client (b9): server ready sock.c:406:simple_client (dd) connected sock.c:346:simple_server (d3): waiting for client sock.c:427:simple_client (dd) exiting sock.c:406:simple_client (b9) connected sock.c:374:simple_server (d3) exiting sock.c:427:simple_client (b9) exiting sock.c:696: **** TEST 0 COMPLETE **** sock.c:694: **** STARTING TEST 1 **** sock.c:332:simple_server (ec) starting sock.c:341:simple_server (ec) ready sock.c:346:simple_server (ec): waiting for client sock.c:445:event_client (ea): starting sock.c:445:event_client (e3): starting sock.c:447:event_client (ea): server ready sock.c:456: Test failed: event_client (ea): connect error: 10022 sock.c:447:event_client (e3): server ready sock.c:456: Test failed: event_client (e3): connect error: 10022 It stays there for a long time and then prints: sock.c:456: Test failed: event_client (e3): connect error: 10022 sock.c:614: Test failed: some threads have not completed: 102 sock.c:621:terminating thread 000000ec sock.c:621:terminating thread 000000ea sock.c:621:terminating thread 000000e3 sock.c:696: **** TEST 1 COMPLETE **** But then the process does not terminate... -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ Hiroshima '45 - Czernobyl '86 - Windows '95

Dec. 4, 2002

Re: Use COMSPEC command interpreter to run .bat files.

by Uwe Bonnes

>>>>> "Sylvain" == Sylvain Petreolle <spetreolle(a)yahoo.fr> writes: Sylvain> Thanks, this works. But it seems another problem is coming. I Sylvain> checked the COMSPEC value under wcmd. It currently answers Sylvain> COMSPEC=C:\WINDOWS\SYSTEM\wcmd.exe. Sylvain> This cannot be found - wineinstall sets links into system32. Sylvain> link_app wcmd "$CROOT/windows/system32/cmd.exe" Is wcmd setting Sylvain> comspec ? If so, this setting must be changed. >> you can't run "wine cygwin.bat --debugmsg +process". Only >> "CreateProcess(...,"...bat") is supported? And the fix for GOTO in >> batch files needs still to be applied. >> >> Is "wine cygwin.bat --debugmsg +process" really something valid? >> "wine --debugmsg +process -- wcmd /c cygwin.bat" Should work. If you run "wine --debugmsg +process -- wcmd /c cygwin.bat", my patch shouldn't be involved. Is in your case a 'CreateProcess (...,"....bat ...")' somehow involved? Only then my patch should change anything. Wcmd should be found somehow magically, either in ../wine/programs or by the COMSPEC variable. Where does the wine install process put WCMD? As I always run wine in my build tree, I can't check... Bye -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------

Dec. 4, 2002

Re: Use COMSPEC command interpreter to run .bat files.

by Sylvain Petreolle

Thanks, this works. But it seems another problem is coming. I checked the COMSPEC value under wcmd. It currently answers COMSPEC=C:\WINDOWS\SYSTEM\wcmd.exe. This cannot be found - wineinstall sets links into system32. link_app wcmd "$CROOT/windows/system32/cmd.exe" Is wcmd setting comspec ? If so, this setting must be changed. > you can't run "wine cygwin.bat --debugmsg +process". Only > "CreateProcess(...,"...bat") is supported? And the fix for GOTO in > batch > files needs still to be applied. > > Is "wine cygwin.bat --debugmsg +process" really something valid? > "wine > --debugmsg +process -- wcmd /c cygwin.bat" Should work. ===== Sylvain Petreolle spetreolle(a)users.sourceforge.net Fight against Spam ! http://www.euro.cauce.org/en/index.html ICQ #170597259 "Don't think you are. Know you are." Morpheus in Matrix, chapter 15. ___________________________________________________________ Soyez solidaire soutenez laction du Téléthon avec Yahoo! France. http://www1.telethon.fr/030-Espace-Relais-Dons/webtirelire1.asp?hebergeur_i…

Dec. 4, 2002

Re: Painting message order?

by Mike Hearn

Hmmm, dunno. I don't think it is, because otherwise when I forced a refresh (by covering up and uncovering it, or switching desktops) it would render correctly. This isn't the case here - it simply does not render until something inside the plugin causes a refresh: an animation for instance, or toggling the antialiasing. I really need a Windows painting guru to explain to me exactly what WM_ERASEBKGND does, MSDN didn't clear things up for me at all thanks -mike On Tue, 2002-12-03 at 16:25, Paul Millar wrote: > On 3 Dec 2002, Mike Hearn wrote: > > 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. > > Well, speaking in ignorance (I freely admit to it ;) it *could* have > something to do with problem 2 of: > > http://www.winehq.com/hypermail/wine-devel/2002/11/0803.html > > corruption when dialogue boxes are moved around. I tried it again today > (with cvs a few days old) and the problem still exists. > > ---- > Paul Millar > -- Mike Hearn <m.hearn(a)signal.qinetiq.com> QinetiQ - Malvern Technology Center

Dec. 4, 2002

Re: Use COMSPEC command interpreter to run .bat files.

by Uwe Bonnes

>>>>> "Sylvain" == Sylvain Petreolle <spetreolle(a)yahoo.fr> writes: Sylvain> Is your patch allowing the run of .bat files by wine itself, or Sylvain> only a W-process ? When I try it on command line I have this : Sylvain> [syl(a)snoop cygwin]$ wine cygwin.bat --debugmsg +process Sylvain> trace:process:PROCESS_InitWine starting process name="" Sylvain> file=(nil) argv[0]="cygwin.bat" trace:process:find_exe_file Sylvain> looking for "cygwin.bat" trace:process:find_exe_file Trying Sylvain> built-in exe "C:\\cygwin\\cygwin.bat" Sylvain> trace:process:find_exe_file Trying native exe Sylvain> "C:\\cygwin\\cygwin.bat" wine: cannot determine executable type Sylvain> for 'C:\cygwin\cygwin.bat' [syl(a)snoop cygwin]$ cat cygwin.bat Sylvain> @echo off you can't run "wine cygwin.bat --debugmsg +process". Only "CreateProcess(...,"...bat") is supported? And the fix for GOTO in batch files needs still to be applied. Is "wine cygwin.bat --debugmsg +process" really something valid? "wine --debugmsg +process -- wcmd /c cygwin.bat" Should work. Bye -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------

Dec. 4, 2002

Re: Direct3D8 regression/bug

by Jeff Smith

>From: Greg Turner <gmturner007(a)ameritech.net> > > > I need it to test midi with winealsa.drv. > > Now I didn't succeed because of Registry glitch: couldn't find midi > > out (%s)\n > >gotcha. I run winealsa too... but I've never tried midi. My buddy owns >cakewalk, I should give it a whorl sometime, and see what happens. >From what I can see in the source, winealsa only supports wave out at this time. I just recently started running ALSA (because its MIDI implementation is much better for my card than OSS), but am using OSS emulation + wineoss for midi from wine. It worked beautifully for me (after I made a couple of fixes, now in CVS). -- Jeff S _________________________________________________________________ The new MSN 8: advanced junk mail protection and 2 months FREE* http://join.msn.com/?page=features/junkmail

Dec. 4, 2002

Re: rpc_J_PL4

by Greg Turner

On Wednesday 04 December 2002 01:41 am, Francois Gouget wrote: > + /* Must be Win9x (no Unicode support), skip the tests */ I actually did not run the test myself, but I guess I had some mistaken recollection that there was crashing involved :) 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. -- gmt

Dec. 4, 2002

Re: rpc_J_PL4

by Francois Gouget

On Tue, 3 Dec 2002, Greg Turner wrote: > License: X11-MIT > > Changelog: > > * programs/rpcss/tests: rpc.c: > Greg Turner <gmturner007(a)ameritech.net> > - W9x doesn't support widechar uuids (crashes on test) That surprises me. I ran these tests on Win95 and Win98 and they failed but did not crash. Thus I think it would be better to apply this patch instead: Index: dlls/rpcrt4/tests/rpc.c =================================================================== RCS file: /home/wine/wine/dlls/rpcrt4/tests/rpc.c,v retrieving revision 1.1 diff -u -r1.1 rpc.c --- dlls/rpcrt4/tests/rpc.c 7 Oct 2002 21:54:07 -0000 1.1 +++ dlls/rpcrt4/tests/rpc.c 4 Dec 2002 07:29:22 -0000 @@ -101,7 +101,12 @@ /* Uuid to String to Uuid (wchar) */ for (i1 = 0; i1 < 10; i1++) { Uuid1 = Uuid_Table[i1]; - ok( (UuidToStringW(&Uuid1, &wstr) == RPC_S_OK), "Simple UUID->WString copy" ); + rslt=UuidToStringW(&Uuid1, &wstr); + if (rslt==RPC_S_CANNOT_SUPPORT) { + /* Must be Win9x (no Unicode support), skip the tests */ + break; + } + ok( (rslt == RPC_S_OK), "Simple UUID->WString copy" ); ok( (UuidFromStringW(wstr, &Uuid2) == RPC_S_OK), "Simple WString->UUID copy from generated UUID String" ); ok( UuidEqual(&Uuid1, &Uuid2, &rslt), "Uuid -> WString -> Uuid transform" ); /* invalid uuid tests -- size of valid UUID string=36 */ With this patch, all tests are run on NT and Wine platforms, and on Win9x platforms, all tests are skipped after the first first Unicode call. -- 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.

Dec. 4, 2002

Re: spec file definitions

by Marcus Meissner

On Wed, Dec 04, 2002 at 12:21:55AM +0100, Rolf Kalbermatter wrote: > I have seen some definitions of functions in a spec file where a string was > defined as str or wstr. I do remember that there was an issue with this depending > if the string parameter was input only (eg. const) or an input/output parameter. This is only for string parameters which are valid during input. Ciao, Marcus

Dec. 4, 2002

Wine Janitorial Projects

by Dimitrie O. Paun

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.

Dec. 4, 2002

Re: Installing Internet Explorer without windows

by Greg Turner

On Tuesday 03 December 2002 03:58 am, Alberto Massari wrote: > Software\Microsoft\Windows NT\Current Version\Hotfix\Q246009 > "Installed"="1" cool. I did it with just vanilla wine, nt40, your registry key, urlmon=n and uh.. cabinet=n. Well at least I have a test case now... Perhaps we should put this in winedefault.reg? Index: winedefault.reg =================================================================== RCS file: /home/wine/wine/winedefault.reg,v retrieving revision 1.60 diff -u -r1.60 winedefault.reg --- winedefault.reg 13 Nov 2002 21:25:34 -0000 1.60 +++ winedefault.reg 4 Dec 2002 05:12:39 -0000 @@ -93,6 +93,9 @@ # to 0 if a message box has to be presented before running the debugger "Auto"="1" +[HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Hotfix\Q246009] +"Installed"="1" + # # This identifies the files for available code pages # -- gmt

Dec. 3, 2002

Re: HTML Help and IWebBrowser status

by Greg Turner

On Tuesday 03 December 2002 06:59 am, Mike Hearn wrote: > Hi Roderick, > > This was discussed about a month ago, so see the archives for more > info. Basically there was a Gecko vs KHTML debate, with Ender (who is > writing the code) eventually settling on KHTML for the following > reasons: This is true, but I think that does not mean that the KHTML IWebBrowser implementors wouldn't welcome some competition....? As long as we're planning ahead, I for one, wouldn't mind both capabilities ;) -- gmt

Dec. 3, 2002

Use COMSPEC command interpreter to run .bat files.

by Sylvain Petreolle

Is your patch allowing the run of .bat files by wine itself, or only a W-process ? When I try it on command line I have this : [syl(a)snoop cygwin]$ wine cygwin.bat --debugmsg +process trace:process:PROCESS_InitWine starting process name="" file=(nil) argv[0]="cygwin.bat" trace:process:find_exe_file looking for "cygwin.bat" trace:process:find_exe_file Trying built-in exe "C:\\cygwin\\cygwin.bat" trace:process:find_exe_file Trying native exe "C:\\cygwin\\cygwin.bat" wine: cannot determine executable type for 'C:\cygwin\cygwin.bat' [syl(a)snoop cygwin]$ cat cygwin.bat @echo off C: chdir \cygwin\bin bash --login -i ===== Sylvain Petreolle spetreolle(a)users.sourceforge.net Fight against Spam ! http://www.euro.cauce.org/en/index.html ICQ #170597259 "Don't think you are. Know you are." Morpheus in Matrix, chapter 15. ___________________________________________________________ Soyez solidaire soutenez laction du Téléthon avec Yahoo! France. http://www1.telethon.fr/030-Espace-Relais-Dons/webtirelire1.asp?hebergeur_i…

Dec. 3, 2002

Re: Reducing the header maze (warning: long, unsuitable for children)

by Greg Turner

On Tuesday 03 December 2002 04:07 pm, Alexandre Julliard wrote: > Greg Turner <gmturner007(a)ameritech.net> writes: > > This should ensure that each header can actually be run through the > > compiler all by itself -- that is, that it #include's any headers > > it relies on to compile. > > We don't want that, it's not what Windows does. But yes, the whole > obj_*.h stuff is a mess, that's why we should get rid of it all, and > use the exact same include names and dependencies as Windows. > Anything else is a nightmare to maintain. thanks for all the responses... this makes me think it would be really cool to try and visualize the header dependencies in the platform sdk, and compare the resulting graph to that of wine.... which is not to say that I will bother, unless it falls into my lap... hmm, I wonder if ctags or wine's "make depend" could help there... well, I guess I'll spare you all any more ramblings.... but I'll be sure to get back to you all if any other random things cross my mind :P -- gmt

Dec. 3, 2002

Re: Fwd: Re: [putty]Winelib support + patch

by Alexandre Julliard

"Dimitrie O. Paun" <dpaun(a)rogers.com> writes: > Yes, having a PE-aware ld.so would allow us to bypass our import > mechanism. But I guess the question was: given that we don't have > such a ld.so, can we handle import of variables through our current > import mechanism? I don't see how. The compiler will generate references into the ELF GOT so you need to do the fixups there, which is basically what an ELF loader does. What we do for functions is to make the ELF loader link to our version of the function, and then jump to the real one; but of course this cannot work with variables. -- Alexandre Julliard julliard(a)winehq.com

Dec. 3, 2002

Re: Direct3D8 regression/bug

by Greg Turner

On Tuesday 03 December 2002 05:30 pm, Sylvain Petreolle wrote: > --- Greg Turner <gmturner007(a)ameritech.net> a écrit : > On Tuesday > the nv driver provided with Xfree is way too slow to use it on Wine. > and I don't want to have to compile Xfree myself. Wow, that sounds really bad... unless our experinces differ, I don't find wine to be /too/ much hungrier (a bit) than the equivalent native X application (i.e.: ms word vs. openoffice writer). This is going a bit off-topic but.... you can compile just the Xserver and or drm kernel module from xfree cvs and even use some ./configure flags to turn off the various drivers you don't need IIRC (I always just suffer through the whole compile personally). It's still probably a pretty big compile, but much less. If you "xmkmf /path/to/xc" and "make depend," you can "make" the subdirectories just like wine, without getting sucked into the notorious "make World" invisible progress bar. > You wrote exactly what I wanted to avoid when I put "mplayer.exe" > It isn't mplayer from mplayerhq.hu, but windows mplayer.exe from > Windows ME. haha, I should have paid more attention! the ".exe" was a dead giveaway... > I need it to test midi with winealsa.drv. > Now I didn't succeed because of Registry glitch: couldn't find midi > out (%s)\n gotcha. I run winealsa too... but I've never tried midi. My buddy owns cakewalk, I should give it a whorl sometime, and see what happens. -- gmt

Dec. 3, 2002

Re: Janitorial Projects

by Dimitrie O. Paun

On December 2, 2002 03:38 pm, Francois Gouget wrote: > You should be able to unzip the tests anywhere. Sure that means you will > have a lot of choice and may have to make hard decisions<g>. :P No, it's that I have to unzip them anywhere that bothers me <g> > Besides, I'm not sure one can compile all the tests in just one > executable or that it would be wise. There would be quite a high risk of > naming conflicts between the tests, and that executable would have to > link with tons of libraries for instance. Indeed. I still think would be nice to have a shell exe (sort of like the one provided by JUnit), that contains the little exes, extracts them in a temp dir one by one, runs them, and displays a nice progress bar, and a list with the messages. Essentially the main window should be a dialog that contains: -- a progress bar at the top that tracks the number of executed tests -- a listview in LVS_REPORT mode below, that displays the messages -- a "Cancel" button (that changes to "Close" when tests are done) -- a "Report..." button that brings up the "Save As..." dialog Not hard to write, and quite cool to play with. Maybe I should add it to the Fun Projects page. ;) Any takers? :) -- Dimi.

Dec. 3, 2002

Re: Fwd: Re: [putty]Winelib support + patch

by Dimitrie O. Paun

On December 2, 2002 02:03 pm, Alexandre Julliard wrote: > Yes, it would be possible to resolve imports directly through the ELF > tables and avoid our own separate import mechanism; basically this > would be a PE-aware ld.so. It's quite a bit of work though, and > portability is an issue. Yes, having a PE-aware ld.so would allow us to bypass our import mechanism. But I guess the question was: given that we don't have such a ld.so, can we handle import of variables through our current import mechanism? Since you mentioned portability, I would like to add that while worrying about compatibility makes sense, holding back features for long periods for the hope of finding the perfect portable solution probably hurts everyone. Past experience has shown that having a working version for the dominant OS (Linux for us), is the way to go. The other systems will find a way of emulating the behavior faster (and better!) than we can figure out a good portable solution. We had the same debate about threading long ago, and at that time I was advocating using clone(2), but due to portability reasons threading support was delayed substantially. In the end, we ended up using clone, and it showed that (1) the hard part was to do the locking, and that was shared by all systems anyway, so progress on that front, even if only on Linux initially, helped _all_ systems, and (2) the *BSD folks come up with a solution in no time. I know, it sounds selfish, but I think the best approach for everybody is to go ahead and implement it only on Linux if there isn't an obvious portable solution. The other systems will follow sooner rather than later. In the end, everybody wins. -- Dimi.

Dec. 3, 2002

Re: Fwd: Re: [putty]Winelib support + patch

by David Laight

> > http://chiharu.haun.org/peace/ > > As far as I can tell, this is only a PE loader, so you need to > cross-compile everything as PE dlls. What we would want for Wine is an > ELF loader that can also load PE and seamlessly link binaries of both > types together. I've not read the URL above, but have looked at the netbsd ld.elf_so, making it do something subtly different with other object formats shouldn't be too hard - it of only boring (system) code. You might want to make the wine binary use a non-standard ELF interpreter, the name of the program used to do all the library loading and symbol fixupnis a property of the program being run, not of the system. Do if you need a pe_open (cf dlopen) it shouldn't be too hard to sort out. Although the different OS will have different requirements on the ELF interpreter, it is the ELF object format that requires it. In particular the rules for looking up symbols are easily changed. David -- David Laight: david(a)l8s.co.uk

Dec. 3, 2002

Re: Direct3D8 regression/bug

by Sylvain Petreolle

--- Greg Turner <gmturner007(a)ameritech.net> a écrit : > On Tuesday 03 December 2002 02:34 pm, Sylvain Petreolle wrote: > > NVidia and its bugged binary shit... > > yuck. doesn't xfree or drm-kernel project provide a decent driver > for > you guys? the nv driver provided with Xfree is way too slow to use it on Wine. and I don't want to have to compile Xfree myself. You wrote exactly what I wanted to avoid when I put "mplayer.exe" It isn't mplayer from mplayerhq.hu, but windows mplayer.exe from Windows ME. I need it to test midi with winealsa.drv. Now I didn't succeed because of Registry glitch: couldn't find midi out (%s)\n > > Note : it crashes even with mplayer.exe !! > > mplayer is very, very agressive and takes wierd liberties with > compiler > flags. compile it yourself, disable stuff you don't want, and pay > attention to the compiler flags you get. when all is said and done > ... ===== Sylvain Petreolle spetreolle(a)users.sourceforge.net Fight against Spam ! http://www.euro.cauce.org/en/index.html ICQ #170597259 "Don't think you are. Know you are." Morpheus in Matrix, chapter 15. ___________________________________________________________ Soyez solidaire soutenez laction du Téléthon avec Yahoo! France. http://www1.telethon.fr/030-Espace-Relais-Dons/webtirelire1.asp?hebergeur_i…

Dec. 3, 2002

spec file definitions

by Rolf Kalbermatter

I have seen some definitions of functions in a spec file where a string was defined as str or wstr. I do remember that there was an issue with this depending if the string parameter was input only (eg. const) or an input/output parameter. Is this still valid and if yes how are the rules? Rolf Kalbermatter

Dec. 3, 2002

Re: Reducing the header maze (warning: long, unsuitable for children)

by Francois Gouget

On Tue, 3 Dec 2002, Greg Turner wrote: [...] > Anyhow, this project has served to remind me just how deep, and how > confusing, the maze of wine headers can really be. It's clear to me > that lots of header inclusions are just historical remnants, that no > longer serve any purpose, and, conversely, that many implicit header > dependencies exist that happen to be hidden, and missing (i.e., X.h > needs Y.h, but all references to X.h happen to occur after Y.h was > already included, so there's no compile failure). A third kind of > unnecessary (but arguably correct, in many cases) dependency is created > when an include file is pulled in that is already pulled in by some > prior include... Many Windows programs expect that they will get the definitions of y.h when then include x.h because x.h happens to include y.h anyway. So preserving such includes is important if you do not want to break Winelib. So as long as your automatic scripts preserve such dependencies I'm ok with it. IOW, it's probably not feasible. -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ Any sufficiently advanced bug is indistinguishable from a feature. -- from some indian guy

Dec. 3, 2002

RE: Compiling out the debug messages

by Medland, Bill

> -----Original Message----- > From: Jeff Smith [mailto:whydoubt(a)hotmail.com] > Sent: Tuesday, December 03, 2002 2:13 PM > To: Bill.Medland(a)accpac.com; wine-devel(a)winehq.com > Subject: Re: Compiling out the debug messages > > > Bill, > > Unless I missed the whole point, you gave the answer before asking the > question. > > ./configure > > should have been > > ./configure --disable-debug You are correct; I made a right fist of writing the email. I did actually remember the --disable-debug. > > -- Jeff S > > _________________________________________________________________ > MSN 8 with e-mail virus protection service: 2 months FREE* > http://join.msn.com/?page=features/virus >

Dec. 3, 2002