wine-devel

wine-devel@winehq.org

2 participants
84471 discussions

err:ntdll:RtlpWaitForCriticalSection section 0xXXXXXXX "?" wait timed out, retrying (60sec) fs = XXXX
by Sylvain Petreolle 30 Jan '02

30 Jan '02

Hi, Like many users now, I have this message when I launch some programs : err:ntdll:RtlpWaitForCriticalSection section 0xXXXXXXX "?" wait timed out, retrying (60sec) fs = XXXX To clear the situtation : What does this message means and what could be done to make it disappear ? Some users have made post with these and have got no response... ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.fr

2 4

New to wine
by Rolf Kalbermatter 30 Jan '02

30 Jan '02

Hello I happened to find wine when researching some undocumented stuff in shell32.dll for my own shell extensions I had written. It was interesting to see how things may be done in windows. I also identified some parts in the wine shell32 which need more attention and plan to submit some patches concerning that after I have familiarized myself a little more with wine. Since I had no Linux system at my hands I tried to use the Visual C 5 compiler on my windows system to compile the shell32 dll and found some problems with that. Separate from some wine specific project definitions which need to be made for Visual C to process the wine headers Iand which I probably haven't done all properly) there was one problem with function pointer definitions. All wine headers seem to declare function pointers like <return value> WINAPI (*<function pointer name)(<parameter list>) Visual C 5 does not like the WINAPI (eg __stdcall) outside of the brackets and requires: <return value> (WINAPI *<function pointer name>)(<parameter list>) I could also not find any comprehensible ANSI C description which would care to explain what would be the correct way of function pointer declarations with a calling convention identifier. I tried to figure out how this could be solved. Declaring WINAPI to be empty and telling Visual C to use __stdcall as default gives other problems with internal wine functions without explicit calling convention declaration and with a variable argument list, which requires __cdecl. The only way I could find was to adjust the function pointer definitions in the affected headers. Of course this goes quite far and might cause problems with other compilers. As I will soon have a new development machine on which I will install Linux alongside of Windows I can fairly easily check if this would cause problems with gcc, but wine seems to care for more compilers than that and I have no idea if such a change would cause problems (it probably would anyhow :-| ). Maybe there is someone on this list which can give me an direct answer to this. Rolf Kalbermatter

2 1

Prob with freetype...
by Meths 30 Jan '02

30 Jan '02

Hiya, Didn't see anyone mention this so... When compiling CVS tonight... gcc -c -I. -I. -I../../include -I../../include -I/usr/include/freetype2 -g -O2 -Wall -mpreferred-stack-boundary=2 -fPIC -D__WINE__ -D_REENTRANT -I/usr/X11R6/include -o freetype.o freetype.c freetype.c: In function `WineEngGetGlyphOutline': freetype.c:947: `FT_Angle' undeclared (first use in this function) freetype.c:947: (Each undeclared identifier is reported only once freetype.c:947: for each function it appears in.) freetype.c:947: parse error before `angle' freetype.c:993: `angle' undeclared (first use in this function) freetype.c:1003: warning: implicit declaration of function `FT_Vector_Rotate' freetype.c:1059: warning: implicit declaration of function `FT_Cos' freetype.c:1060: warning: implicit declaration of function `FT_Sin' make[2]: *** [freetype.o] Error 1 make[2]: Leaving directory `/root/cvs_root/wine/dlls/gdi' make[1]: *** [gdi/libgdi32.so] Error 2 make[1]: Leaving directory `/root/cvs_root/wine/dlls' make: *** [dlls] Error 2 Compilation failed, aborting install. Meths

2 1

Re: SetEndOfFile fix
by Guy L. Albertelli 30 Jan '02

30 Jan '02

----- Original Message ----- From: <lawson_whitney(a)juno.com> To: <rklazes(a)xs4all.nl>; <galberte(a)neo.lrun.com> Cc: <wine-patches(a)winehq.com> Sent: Sunday, January 27, 2002 4:30 PM Subject: Re: SetEndOfFile fix > On Sun, 27 Jan 2002, Rein Klazes wrote: > > > You still need ftruncate in case the file has to shrink. To do that > > without ftruncate takes a lot more work then an lseek and a write. > > > > Rein. > > > Right. I meant sort of like this. Unfortunately I haven't an app that > does this, to be sure I have it right. > > Changelog > server : file.c > Lawson Whitney <lawson_whitney(a)juno.com> > Rein Klazes <rklazes(a)xs4all.nl> > Guy Albertelli <galberte(a)neo.lrun.com> > Do not rely on ftruncate to grow a file. It may refuse or fail > to do so. (eg with vfat filesystem under Linux) > > Outlook Express 5.0 is happy (relatively). Lets commit this. Guy

1 0

RE: Sooo quiet...
by Patrik Stridvall 29 Jan '02

29 Jan '02

> ... I feel like starting a flamewar, just to get some > traffic on this list :) Yes!!! Flamewar!!! No retreat!!! No surrender!!! > Speaking of which, I figured I should rattle Alexandre's cage :) Well, I guess he will have fun with all the outstanding patches. I think he has never had so many. :-) > So here I go: > > Wine's been around for 8 (_eight_) years (how time flies)! It is my > understanding that we're approaching the 1.0 status. I say, > let's change > the versioning scheme, just to give the outside world a feeling of > progress. Really, I think the current scheme kindda hurts us on a PR > level. > > We can start with something like 0.90.0. This should give us plenty > numbers to the upcoming 1.0, don't you think? Unfortunetely there won't be any flamewar as far as I'm concerned since don't care very much either way. :-) But if anybody is intrested in my opinion anyway here goes: I'm slightly against changing the versioning scheme before 1.0. After 1.0 we probably want to have so sort of different versioning especially since we might release different versions of the DLL:s independently of each other. However I don't think there is much use of having that pre 1.0.

8 10

Re: A new SDL back-end we've been toying with
by Steven Edwards 29 Jan '02

29 Jan '02

> > You might want to take a look at microwindows if > you > > want GDI/framebuffer > > However, keep in mind that Microwindows can be had > at > either MPL and GPL licenses. True, but you might be able to get them relicense certain parts for wine. __________________________________________________ Do You Yahoo!? Great stuff seeking new owners in Yahoo! Auctions! http://auctions.yahoo.com

1 0

FW: Prob with freetype...
by Medland, Bill 29 Jan '02

29 Jan '02

-----Original Message----- From: Medland, Bill Sent: Tuesday, January 29, 2002 2:22 PM To: 'Meths' Subject: RE: Prob with freetype... Mentioned it this morning (sort of). Michael Stefaniuc upgraded to freetype 2.0.3 and that worked. I just cheated; I inserted the following lines into freetype.c to get it compiled; Index: wine/dlls/gdi/freetype.c =================================================================== RCS file: /home/wine/wine/dlls/gdi/freetype.c,v retrieving revision 1.4 diff -u -r1.4 freetype.c --- wine/dlls/gdi/freetype.c 2002/01/29 03:02:51 1.4 +++ wine/dlls/gdi/freetype.c 2002/01/29 20:29:42 @@ -56,6 +56,12 @@ #endif #ifdef HAVE_FREETYPE_FTTRIGON_H #include <freetype/fttrigon.h> +#else +/* Just a hack to get it to compile without upgrading my freetype */ +typedef FT_Fixed FT_Angle; +inline FT_Fixed FT_Sin(FT_Angle a) {return 0;} +inline FT_Fixed FT_Cos(FT_Angle a) {return 65536;} +inline FT_Vector_Rotate(FT_Vector *v, FT_Angle a) {return;} #endif static FT_Library library = 0; Bill > -----Original Message----- > From: Meths [mailto:meths@btinternet.com] > Sent: Tuesday, January 29, 2002 1:27 PM > To: wine-devel(a)winehq.com > Subject: Prob with freetype... > > > Hiya, > > Didn't see anyone mention this so... > > When compiling CVS tonight... > > gcc -c -I. -I. -I../../include -I../../include > -I/usr/include/freetype2 > -g -O2 -Wall -mpreferred-stack-boundary=2 -fPIC -D__WINE__ > -D_REENTRANT > -I/usr/X11R6/include -o freetype.o freetype.c > freetype.c: In function `WineEngGetGlyphOutline': > freetype.c:947: `FT_Angle' undeclared (first use in this function) > freetype.c:947: (Each undeclared identifier is reported only once > freetype.c:947: for each function it appears in.) > freetype.c:947: parse error before `angle' > freetype.c:993: `angle' undeclared (first use in this function) > freetype.c:1003: warning: implicit declaration of function > `FT_Vector_Rotate' > freetype.c:1059: warning: implicit declaration of function `FT_Cos' > freetype.c:1060: warning: implicit declaration of function `FT_Sin' > make[2]: *** [freetype.o] Error 1 > make[2]: Leaving directory `/root/cvs_root/wine/dlls/gdi' > make[1]: *** [gdi/libgdi32.so] Error 2 > make[1]: Leaving directory `/root/cvs_root/wine/dlls' > make: *** [dlls] Error 2 > > Compilation failed, aborting install. > > Meths > > >

1 0

GetNearestColor Fix
by Dave Hawkes 29 Jan '02

29 Jan '02

Fix for GetNearestColor so it returns the true color rather than the system palette if the device does not support a palette (ie > 256 colors). This not quite what the Windows SDK docs say, but it's what happens in practice... Dave Hawkes

1 0

DOSfs - further work ?
by Keith Matthews 29 Jan '02

29 Jan '02

While this is not critical, or even a large amount of work, I noticed when playing around with the floppy media problem that wine does not attempt to mount either a floppy or CD to display the contents. Was this intentional does anyone remember ? If not does anyone have reservations about trying to enable it? -- Keith Matthews Frequentous Consultants - Linux Services, Oracle development & database administration

1 0

Patch that broke SetFileAttributes
by Jukka Heinonen 29 Jan '02

29 Jan '02

Fallout II requires that a certain file is located on a CDROM drive. For some reason it checks this using SetFileAttributes, which is supposed to fail on readonly drives. This used to work until the following patch broke this behaviour (message continues after the patch): Index: file.c =================================================================== RCS file: /home/wine/wine/win32/file.c,v retrieving revision 1.26 retrieving revision 1.27 diff -u -r1.26 -r1.27 --- file.c 2001/05/14 20:09:39 1.26 +++ file.c 2001/05/18 23:18:25 1.27 @@ -104,7 +104,7 @@ { FILE_SetDosError(); MESSAGE("Wine ERROR: Couldn't set file attributes for existing file \"%s\". Check permissions or set VFAT \"quiet\" flag !\n", full_name.long_name); - return FALSE; + return TRUE; } return TRUE; } The above patch obviously breaks Windows compatibility (and likely has a bug related to FILE_SetDosError). I would like to suggest that this patch is either removed or replaced with a patch that includes a C comment that properly documents reasons for this deliberate incompatibility and that either only affects non-CDROM drives or drives configured using some magic flag in Wine configuration file. -- Jukka Heinonen <http://www.iki.fi/jhei/>

4 8

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-devel