January 2003 - Wine-Devel - list.winehq.org

Re: LockFile support

by Eric POUECH

> Now, it USED to work under Wine. It no longer does. The program coughs > up an error "No access to directory", and stderr shows a bunch of > "LockFile not supported in server" errors. LockFile didn't change AFAICT. What may have changed is: - timing of some operations may have changed (and if LockFile is really used & several threads/processes are used, this changes the whole picture) - reading operations has been a bit improved (which comes back to bullet above) But, I don't think those would lead to the no access to directory error. I think it's more something in the file management code which can play in this area, not the file locking. > Are there plans to add LockFile support into Wine? they've been some talks of implementing it lately, but not lots of very conclusive so far. A+

Jan. 23, 2003

Re: App works almost perfectly, but one MDI screen won't draw

by Mike Hearn

> So then it becomes a matter of figuring out where they should > be generated. Yeah, that's the big that usually gets me :) Are they the sort of messages that should be generated by Wine or the app? What happens if the app doesn't call BeginPaint in a WM_PAINT handler. Is that an API violation, or are there reasons for it? MSDN had an explanation that seemed to suggest that in certain unusual circumstances you didn't need to call it, but I don't remember exactly what. > It is a bit of a > mystery to me why the call is bad; it is a call directly from the app. I > wonder if the wrong function is being called for some reason. But that > is something I will look into later. How common is it for apps to actually make bad API calls? QuickTime seemed to do that, is it rare or not? thanks -mike -- Mike Hearn <m.hearn(a)signal.qinetiq.com> QinetiQ - Malvern Technology Center

Jan. 23, 2003

LockFile support

by David D. Hagood

I have an old, nasty application that uses the Paradox database engine. This app attempts to lock the database files using LockFile. Now, it USED to work under Wine. It no longer does. The program coughs up an error "No access to directory", and stderr shows a bunch of "LockFile not supported in server" errors. Did the behavior of LockFile change in the past couple of months? Are there plans to add LockFile support into Wine?

Jan. 23, 2003

Re: Spanish Documentation Project

by Tom Wickline

Javier Canovas wrote: > hi, this is my first message on this mailing list... HI! > > I am a spanish user of wine, and I am going to translate the english > documentation of wine (I manage the project). I am creating the project > (cvs, bugzilla...) in Lucas (es.tldp.org) but I cant do it alone. I am > meeting people to work in this, somebody can help us? > > Thks I just want to say thanks for taking on part of the translation. I am aware that wine needs the README : http://cvs.winehq.com/cvsweb/wine/README?hideattic=0 translated to as many languages as possiable at this time. This would be a good place to start...... You might want to read over : > http://cvs.winehq.com/cvsweb/~checkout~/wine/documentation/i18n.sgml?rev=1.… as well . And im sure we could use many more volinteers in this department. Many thanks for your support !!! Tom

Jan. 23, 2003

Re: A strange problem with xmpeg

by Mike Hearn

> 1. When the splash screen desapears, so does all of my desktop. I have > to make a Refresh Desktop to get it back. Judging by the log below, I am > suspecting of something in the DirectDraw functions. Upon request I will > gladily send a (45Kb) screen shot of this. This problem also occurs with QuickTime when it's using DirectDraw. It was easier to switch it to GDI mode than debug though :) -- Mike Hearn <m.hearn(a)signal.qinetiq.com> QinetiQ - Malvern Technology Center

Jan. 23, 2003

Re: debugger detection in newbin.

by Marcus Meissner

On Thu, Jan 23, 2003 at 10:12:32AM +0100, Rein Klazes wrote: > Hi, > > The latest version of newsbin 4.1B5 refuses to run, displaying > "debugger or monitoring tool detected". > > The detection code is very simple, immedeately at the program entry > point 0x516000 it does (intel syntax): > > | Disassembly of 0x00516000 > | 0x51600D: 64A023000000 mov al,fs:[0x23] > | 0x516013: EB03 jmp 0x516018 > | ;*************************************************** > | 0x516018: 84C0 test al,al > | 0x51601A: EB03 jmp 0x51601f > | ;*************************************************** > | 0x51601F: 7567 jnz 0x516088 > > This jump is taken and leads immedeatly to the messagebox displaying the > message above. > > Any idea's and/or explanation? Well, we store the thread pid there, see thread.h: DWORD pid; /* !2- 20 Process id (win95: debug context) */ Try to move the pid somewhere else and mark this field as unused. Ciao, Marcus

Jan. 23, 2003

debugger detection in newbin.

by Rein Klazes

Hi, The latest version of newsbin 4.1B5 refuses to run, displaying "debugger or monitoring tool detected". The detection code is very simple, immedeately at the program entry point 0x516000 it does (intel syntax): | Disassembly of 0x00516000 | 0x51600D: 64A023000000 mov al,fs:[0x23] | 0x516013: EB03 jmp 0x516018 | ;*************************************************** | 0x516018: 84C0 test al,al | 0x51601A: EB03 jmp 0x51601f | ;*************************************************** | 0x51601F: 7567 jnz 0x516088 This jump is taken and leads immedeatly to the messagebox displaying the message above. Any idea's and/or explanation? Rein. -- Rein Klazes rklazes(a)xs4all.nl

Jan. 23, 2003

Re: Wine kernel acceleration module?

by Tom Wickline

Gavriel State wrote: > Another key factor in favour of the ShmServer is that we've got > a working prototype available right now that runs several real-world > apps. 8-) May I ask for a list of Apps ? Tom > > Take care > -Gav >

Jan. 23, 2003

Re: RtlpWaitForCriticalSection?

by Dan Kegel

Christian Costa wrote: >> All the static CRITICAL_SECTIONs in Wine DLLs have names. >> The only unnamed ones are those that are initialized at runtime. > > It is what I said! No? :-) I guess I missed part of what you said, sorry. >> To give these a name, we'd either have to convert them to >> static initialization, or change InitializeCriticalSection >> to somehow generate a name from the caller's program counter. > > > What about writing a new macro that initializes the name in the > CRITICAL_SECTION struct. > ................. > InitializeCriticalSection(&crit); > SET_CRITICAL_SECTION_NAME(&crit,"name"); Hmm. Seems to be the Wine DLL sources should try to avoid stuff that doesn't compile under Windows. That said, we could provide a header file that defined SET_CRITICAL_SECTION_NAME in Windows, and made it do nothing. Furthermore, we could be real sneaky, and make that header file turn InitializeCriticalSection into a macro that called the real InitializeCriticalSection, then called SET_CRITICAL_SECTION_NAME, so no source changes would be needed to get the name in there, maybe. - Dan -- Dan Kegel http://www.kegel.com http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045

Jan. 23, 2003

Re: RtlpWaitForCriticalSection?

by Christian Costa

Dan Kegel wrote: > Christian Costa wrote: > >>>> I think, It would be cool to have all locks named and thus make >>>> debugging and bug report easier. >>>> It's not a hard task but names must be meaningfull. :-) >>> >>> >>> I guess you mean all Wine locks should be named >> >> >> Yes! :-) >> >>> ... >>> Naming the Wine locks would be nice (or is it done already?). >> >> >> No, it isn't. > > > All the static CRITICAL_SECTIONs in Wine DLLs have names. > The only unnamed ones are those that are initialized at runtime. It is what I said! No? :-) > > To give these a name, we'd either have to convert them to > static initialization, or change InitializeCriticalSection > to somehow generate a name from the caller's program counter. What about writing a new macro that initializes the name in the CRITICAL_SECTION struct. So in the code, we can do : ................. InitializeCriticalSection(&crit); SET_CRITICAL_SECTION_NAME(&crit,"name"); .................. > > >>> But more >>> than meaningful names, what we would need are grep-able names :-) >>> >> What do you mean with grep-able ? > > > Ones that are easy to search for, e.g. that contain > the source filename. The filename could be added to the name with the macro I mentionned above. CRITICAL_SECTION_INIT does that (__FILE__ ": " name). Christian.

Jan. 23, 2003