November 2002 - Wine-devel - list.winehq.org

Wine 0.9 TODO v0.3
by Dimitrie O. Paun 07 Nov '02

07 Nov '02

Lots of updates on this one: http://www.dssd.ca/Wine-0.9-TODO-0.3.html The actual TODO included below as text, for your commenting convenience. A. WineHQ work Website redesign [IN PROGRESS] worker: Jeremy Newman status: backend is getting finalized updated: Nov 7, 2002 Reorganize the navigational menu [DONE] worker: Francois Gouget & al. status: merged into new site updated: Nov 5, 2002 Create some really sexy screenshots [IN PROGRESS] worker: ? status: just starting updated: Nov 7, 2002 criteria: one app per screenshot, avoid cluttered desktop Rework the FAQ interface [IN PROGRESS] workers: Dimitrie O. Paun, Keith Matthews, Thomas Wickline status: close to first public release updated: Nov 7, 2002 Enlist some 'official' distribution maintainers [DONE] RedHat: Vincent Béron SUSE: Marcus Meissner Mandrake: Kye Lewis Debian: Ove Kaaven FreeBSD: Gerald Pfeifer status: completed updated: Nov 7, 2002 Create nice page with apps that run virtually flawless [IN PROGRESS] workers: Carlos Lozano, Dustin Navea status: 20% updated: Nov 7, 2002 criteria: not MS dlls required, no tricks, etc. B. Documentation work We need to first figure what is out of date. [IN PROGRESS] worker: Dustin Navea status: just started updated: Nov 7, 2002 Move CVS docu from User Guide to Devel Guide [IN PROGRESS] worker: Bill Medland status: just started updated: Nov 7, 2002 C. Wine configuration Merge configuration into the registry [TODO] Write control panel applets for editing it [TODO] Have decent defaults so we can start control panel without prior configuration [TODO] Have wizard like app to autoconfigure wine [TODO] proposal: WineSetupTk by Jeremy White Make Wine's DLLs register themselves to avoid manual merging of the winedefault.reg [TODO] Write wine.inf script to setup a new Wine installation [TODO] Have a wineboot script for RunOnce stuff [IN PROGRESS] workers: Andreas Mohr, Shachar Shemesh status: 50% updated: Nov 7, 2002 D. Stabilize utilities Get rid of the init directive from .spec files [DONE] worker: Alexandre Julliard status: implemented by this updated: Nov 7, 2002 Make sure the .spec file format is fairly stable [IN PROGRESS] worker: Dimitrie O. Paun status: investigating updated: Nov 7, 2002 what: can we get rid of the rsrc directive? Ensure the various utilities' options are stable [IN PROGRESS] status: Alexandre fixed winebuild options updated: Nov 7, 2002 what: audit the other utilites Get rid of the Perl testing framework [TODO] worker: Dimitrie O. Paun status: started looking at it updated: Nov 7, 2002 E. Important fixes Window management rewrite, so we can install apps in managed mode. [TODO] worker: Alexandre Julliard status: not started Finish DLL separation Phase 1 [IN PROGRESS] worker: ? status: ntdll, and kernel not done updated: Nov 7, 2002 criteria: DLLs should use only functions exported through .spec file. Detect printing system at runtime [TODO] worker: Huw Davies status: Yup, I'm going to do this in the near future. updated: Nov 7, 2002 Detect OpenGL system at runtime [TODO] worker: Lionel Ulmer status: Real Soon Now (TM) updated: Nov 7, 2002 -- Dimi.

2 1

Re: debugging a lockup in Planescape Torment
by Eric Pouech 07 Nov '02

07 Nov '02

> RFE: > Actually I am not interested in debug msgs after the debugger started. > Could there be an option that an debugger start turns off debug msgs. set - all > When the debugger starts I often get the msg > wine: hash.c:392: DEBUG_GetSymbolValue: Assertion 'strlen(name) < > sizeof(buffer) - 2' failed. which results in an unhandled exception in the > debugger. Whats up with that? fixed size for internal buffers... however a 512 characters identifier seems a bit big to me (even in C++) would you mind printing out the name of the symbol, just to check I'll send a work around for that A+

2 4

user.reg and winedbg
by steve.lustbader＠philips.com 07 Nov '02

07 Nov '02

They key in user.reg that controls whether winedbg pops up in its own window or in the shell in which wine was started seems to be getting ignored. When I set "UseXTerm"=dword:00000000, and run my app, it crashes and brings up winedbg in a separate window. When I look at user.reg again, UseXTerm has been set back to 1. The reason I need this is because when my app crashes, the backtrace is so long (~40 frames) that I can only see the bottom (mostly useless half). Is there a way to increase the size of the winedbg window, pause bt's output (like piping to more in a shell), or display only part of a back trace? -Steve

5 4

Re: FreeBSD configure fix
by Andreas Mohr 07 Nov '02

07 Nov '02

On Thu, Nov 07, 2002 at 06:21:14PM +0100, Patrik Stridvall wrote: > Gerald Pfeifer configure change broke FreeBSD 4.7 > This should fix it. ROTFL !! The "man who is constantly annoyed about having to fix stupid Linux breakage on *BSD" manages to break *BSD :-)) -- Andreas Mohr Stauferstr. 6, D-71272 Renningen, Germany Tel. +49 7159 800604 http://mohr.de.tt

1 0

Re: ComputerName
by Dimitrie O. Paun 07 Nov '02

07 Nov '02

On November 6, 2002 10:27 am, Martin Wilck wrote: > - Keep old behavior as default, using new config option to change. Can you also please update the documentation as well (man pages, etc.)? -- Dimi.

5 14

RE: Wine 0.9 TODO v0.2
by Medland, Bill 07 Nov '02

07 Nov '02

> -----Original Message----- > From: wine-devel-admin(a)winehq.com > [mailto:wine-devel-admin(a)winehq.com]On > Behalf Of Dimitrie O. Paun > Sent: Wednesday, November 06, 2002 11:21 PM > To: Wine Devel > Subject: Wine 0.9 TODO v0.2 > > > Folks, > > This time in HTML & Technicolor, at: > > http://www.dssd.ca/Wine-0.9-TODO.html > > Please take a look, and let me know if you think > anything needs to change. If you are listed there > on a task, a status update would be more than > appreciated. If you feel like working on something, > I would like to know to add you in there. > > NOTE: most tasks don't require coding, so don't be > shy, and step up to the challenge. ;) > > -- > Dimi. > Dimi (et al) I guess I could do B.2; Move CVS Docu from User Guide to Devel guide. Before doing so, though, I just want to check what that means. I presume that this means moving the "Getting Wine Source code from CVS" section. I wonder if that is exactly what we want. Are we trying to avoid scaring beginners and non-programmers? If we basically mean that the user Guide will not talk about getting the source and compiling it on your own machine then we might as well also move "Getting Wine Source Code from the FTP archive" and "Upgrading Wine with a patch" If we basically mean that we suggest that the user be able to build from source but only from the FTP archive versions then do we really need the "Upgrading Wine with a patch" If we support the user being able to build from source but don't want to scare them then all we need to do is drop the talk about changing the code and diffing (and maybe adding a little more hand-holding to the cvs section a la dummies guide). Also if we go towards the "build from source" we are going to have to address little issues like the tendency not to install the compiler these days. My suggestion is that, since we are talking about fairly stable releases, we ought to move all the sections concerned with building from source. Guidance please. Bill

3 2

RE: Wine 0.9 TODO v0.2
by Medland, Bill 07 Nov '02

07 Nov '02

> -----Original Message----- > From: Dimitrie O. Paun [mailto:dpaun(a)rogers.com] > Sent: Thursday, November 07, 2002 9:42 AM > To: Medland, Bill; Wine Devel > Subject: Re: Wine 0.9 TODO v0.2 > > > On November 7, 2002 12:37 pm, Medland, Bill wrote: > > My suggestion is that, since we are talking about fairly > stable releases, > > we ought to move all the sections concerned with building > from source. > > I think so. User Guide should all about how you use Wine, not how you > develop it, build it, etc. We should just add a small note to the > User Guide pointing people to the other guide, if interested in > building from source. > > You're on. That was quick!! Catch them while you can, Eh? I'll wait a couple of days to allow any discussion on the list. > > -- > Dimi. > Bill

1 0

Re: Wine FAQ - call for a volunteer
by Ulf Dambacher 07 Nov '02

07 Nov '02

Just one tip: Why not use a wiki-Engine to creaate/maintain a faq, like e.g. www.squirrelmail.net does? I recommend phpwiki (http://phpwiki.sourceforge.net/) This way users can maintain the faq and it is most up to date! Greetings Ulf

3 2

Pls help me.
by yf 07 Nov '02

07 Nov '02

When I using wine start a winapp, it first download some data and then save it to the disk. But when save the data, it always says "Disk full while accessing C:\south\Base.map. What's the matter with it? How could I resolve it? Pls give me some hints? Best regards. /yf

2 1

Re: [PATCHLET] DeleteFile With Empty Paths
by Marcus Meissner 07 Nov '02

07 Nov '02

On Thu, Nov 07, 2002 at 02:18:20AM -0800, Ryan Cumming wrote: > Hi, > > KaZaA Lite 2.0 calls DeleteFile with an empty path at shutdown, which triggers > ERR("Empty path passed\n"). It seems a bit silly to call that an error, so > this patch changes the message to a warning. It also does a > SetLastError(ERROR_FILE_NOT_FOUND) in that case, which is consistant with > Windows XP. Can you also create a testcase for this problem? Ciao, Marcus

1 0