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

Re: critical section blocking

by Duane Clark

Aric Stewart wrote: > > Working with QuickTime5 I found a situation where mouse messages could > lockup wine. This leaving and entering the critical section resolves > that bug. > > -aric > > ------------------------------------------------------------------------ > Index: windows/message.c > =================================================================== > RCS file: /home/wine/wine/windows/message.c,v With this patch, Myst locks up solid as soon as the mouse is moved into the Myst window. Without it, Myst works fine. Duane

May 25, 2001

Re: Small fixes in controls/menu.c

by kenon＠go2.pl

On Wed, May 23, 2001 at 12:11:28AM +0200, gerard patel wrote: > > Btw, I have downloaded several of the availables app on your web site > and I don't see anything wrong with menus; IIRC I have tried 7.5 for > Win3.11, and trial versions 8 and 9 (32 bits). Is it with the main menu > that you see this problem ? > I downloaded ftp://ftp.supermemo.com/ftp/sm8zip.exe and managed to reproduce the bug. (WINE version 20010510) The way: 1) Using mouse chose File>SuperMemo 2) When app changes its mode click at capition of window "Contents: E:\SM8\SYSTEMS\SUPERMEMO" And now main menu is inaccesible (using mouse) When you force wine to repaint all windows (eg. switch to linux console and back to X-Window ) you can see menu is drawn up 10-20 pixels than it should. --

May 25, 2001

Re: Unused OPTIONS variable in configure.in

by Alexandre Julliard

Fran=E7ois Gouget <fgouget(a)codeweavers.com> writes: > I noticed that OPTIONS is not used anymore in 'configure.in'. I > believe it may have been used to store the --enable-* stuff at one ti= me > but AFAIU this is now stored in 'config.h'. So I propose to remove it > altogether. Or is it set as a side effect of some standard autoconf > macro on some exotic system? It's here so that you can specify extra flags that configure doesn't know about, by doing OPTIONS=3D-Dfoo ./configure. This can be useful in some cases. --=20 Alexandre Julliard julliard(a)winehq.com

May 25, 2001

Re: AFM files no longer required

by Alexandre Julliard

Ian Pilcher <ian.pilcher(a)home.com> writes: > I decided to put all of the data into dlls/wineps/agl.c, since changing > the glyph list data without regenerating the font metrics data would > cause things to break in extremely bizarre ways. (Well, it will once I > actually use the glyph names.) You should really split it into separate files, a 40,000 lines file is a bit too much. Also all this data must be constant and in a read-only section, it's eating 400k of data space right now. I'm guessing that you have a script to generate all this; could you please consider submitting it? This way other people can make changes too. -- Alexandre Julliard julliard(a)winehq.com

May 25, 2001

Re: Strange Wine Problems

by r.maurizzi＠gvs.it

That's the same kernel problem that plagues Lotus Notes (If I've understood correctly the message in German ;-) Lotus Notes will die with the same problem if you use a SuSE 7.0 with SuSE kernel 2.2.18 (Mandrake kernels have the same problem, according to other people here) If you compile the kernel yourself starting from ftp.kernel.org's sources, all is well (at least for Notes). I didn't try SuSE Kernels 2.2.19 / 2.4.2 however. Ciao, Roberto.

May 25, 2001

Re: PATCH: mirc dcc send

by Dmitry Timoshkov

"Marcus Meissner" <marcus(a)jet.franken.de> wrote: > + /* This might be a DOS device we do not handle yet ... */ > + FIXME("(%) not detected as DOS device!\n",devname); ^^^ Seems a typo to me.

May 25, 2001

Strange Wine Problems

by Josef.Wegner＠t-online.de

Hi, I have some strange errors with wine the last few weeks. Everytime I try to start an application (mainly Ultima Online and Baldur's Gate) wine crashes (stops) with this errors: >wine client.exe For language 'german' several language ids were found: de_DE - 0407; de_CH - 0807; de_LU - 1007; de_LI - 1407; Instead of using first in the list, suggest to define your LANG environment variable like this: LANG=de_DE Protocol error:0x8071580: read : Die Ressource ist zur Zeit nicht verfügbar fixme:dsound:IDirectSoundImpl_SetCooperativeLevel (0x403938fc,00000138,3):stub fixme:pthread_kill_other_threads_np For language 'german' several language ids were found: de_DE - 0407; de_CH - 0807; de_LU - 1007; de_LI - 1407; Instead of using first in the list, suggest to define your LANG environment variable like this: LANG=de_DE Protocol error:0x8067660: read : Die Ressource ist zur Zeit nicht verfügbar Beendet Protocol error:0x8075258: read : Die Ressource ist zur Zeit nicht verfügbar I don't know what the problem is. My first thought was that I have problems with my sound drivers (Alsa 0.5.11) , so I tried the kernel emu10k1 driver and after that I loaded no sound module. All with the same result. The only other thing I did with my linux installation was upgrading to a 2.2.18 kernel. My system specs: Latest wine cvs SuSE Linux 7.0 All updates from Suse.com (new glibc 2.1.3) Kernel 2.2.18 (SMP) Alsa 0.5.11 KDE 2.1.1 Xfree86 4.0.3 (Ximera on) Dual PIII 500Mhz 384 MB Ram Adaptec AIC-7880 Ultra SCSI host adapter Matrox G400 Max Dualhead SoundBlaster Live! Value Regards -Josef Wegner

May 25, 2001

Q: anybody using Exceed on NT4 as X server for wine?

by Heiko Nardmann

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Is there anybody out there who uses Exceed on NT4 as the X server to display wine applications (like winemine from examples) which have been started on Linux? If yes are did you try 20010510 snapshot (or CVS) to run your applications? If yes could you provide me with your configuration files? I am still not able to start winemine since snapshot 20010418 (20010326 works fine). - -- Heiko Nardmann (Dipl.-Ing.), h.nardmann(a)secunet.de, Software Development secunet Security Networks AG - Sicherheit in Netzwerken (www.secunet.de) Weidenauer Str. 223-225, D-57076 Siegen Tel. : +49 271 48950-13, Fax : +49 271 48950-50 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7DgpMpm53PRScYygRAn6cAKDaQl3Tm4l/sIe9cQoRbdwo7vf7bwCg8gm5 38OwXBWHUxJVc1ZV91iywRY= =CjPM -----END PGP SIGNATURE-----

May 25, 2001

Re: More wine beginner questions

by Alexandre Julliard

Francois Gouget <fgouget(a)free.fr> writes: > So according to the dll separation rules we must not make msvcrt > depend on an API not exported by a regular windows dll. But in the case > of ntdll I'm not sure. Can we use native ntdll in Wine? I don't think so > since it also exports things like 'wine_dbgstr_[aw]n?'. So maybe we can > bend the rules a little and export _vsnwprintf anyway. A better solution would be to put the *wprintf functions inside libwine_unicode. -- Alexandre Julliard julliard(a)winehq.com

May 23, 2001

Re: More wine beginner questions

by Francois Gouget

On Wed, 23 May 2001, Mike Bond wrote: > I was just perusing through msvcrt and noticed that in wcs.c there is > an implementation of _vsnwprintf, which also exists, verbatim, in it's > entirety, in ntdll/wcstring.c. Unless I am misunderstanding the .spec > files there appears to be a method of "forward"ing a symbol to an > external implementation, such as: > > @ forward -noimport wcslen ntdll.wcslen > > Is there any particular reason this was not done for _vsnwprintf as well? The problem is that _vsnwprintf is not exported by ntdll. On Win9x I don't see any *printf function in ntdll. But on Win2000 there is: _snprintf, _snwprintf, _vsnprintf, sprintf, swprintf and vsprintf. But no _vsnwprintf. So according to the dll separation rules we must not make msvcrt depend on an API not exported by a regular windows dll. But in the case of ntdll I'm not sure. Can we use native ntdll in Wine? I don't think so since it also exports things like 'wine_dbgstr_[aw]n?'. So maybe we can bend the rules a little and export _vsnwprintf anyway. Better ask Alexandre... [...] > Also, on perhaps a style note, I've noticed some implementations are > prefixed by the dll name in all caps, such as MSVCRT_vfprintf, and some > are not, such as _wmkdir. Is this just personal style or is there more > to these differences? There's more to it. Here are the MSVCRT conventions: * any function name which may conflict with a regular C function is prefixed with 'MSVCRT_'. In particular this includes all functions that don't start with '_'. Example: vfprintf -> MSVCRT_vfprintf _errno -> MSVCRT__errno (exception) * Any function name that will not conflict with a regular C function name is not prefixed. This includes most functions starting with a single '_'. Example: _access -> _access _wchmod -> _wchmod * Internal functions are prefixed by 'msvcrt_', but I'm not sure I renamed strictly all of them (so there might still be internal functions prefixed with 'MSVCRT_'). (I say function but it's really any symbol) -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ We are Pentium of Borg. You will be approximated. Division is futile.

May 23, 2001