wine-devel November 2002

wine-devel@winehq.org

152 participants
501 discussions

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

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

07 Nov '02

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.

1 0

Re: Interrupts / Move most of int31 to winedos
by Jukka Heinonen 06 Nov '02

06 Nov '02

Andreas Mohr wrote: > On Tue, Nov 05, 2002 at 06:47:35PM +0200, Jukka Heinonen wrote: > > After this patch winedos contains almost complete int31 > > emulation. What has not been moved to winedos is mostly > > functions that require either W32S_WINE2APP or W32S_APP2WINE. > > This makes me wonder whether Wine still needs to support WIN32S... > Well, of course it does. > Wine is supposed to run *all* reasonably new (i.e.: not "standard mode") > Windows programs, and that does include Win32s IMHO. Sure, I know that (I'm working on DPMI32 which isn't for standard mode Windows programs), I was probably being a bit unclear about what I was wondering about. It is quite difficult to find any information about Win32s nowadays and everything I have found was suggesting that Win32s was for running Win32 applications on Win16. Since Wine does run Win32 applications directly it just made me wonder whether Win32s support is something that was once needed when Wine only had Win16 support. But, since I know very little about Win32s, I can only wonder. It all depends on how Win32s applications differ from Win32 and Win16 applications. The existence of Win32s dlls seems to suggest that Win32s applications are not regular Win32 applications as well as the text in "msdos/vxd.c" which talks about some strange pointer mangling required with Win32s applications. This mangling is probably something that is only required if Wine supports official Win32s dlls. Which makes me wonder if Win32s dlls provided by Wine actually do work because they don't seem to do any pointer mangling. Well, it could be that Win32s applications do this pointer mangling internally. Anyway, I seem to have answered myself. If Wine is going to support Win32s applications using both builtin and official Win32s dlls, it needs pointer mangling. I just have to figure out how the required offset can be accessed from multiple dlls because I would really like to have all the interrupt handlers in one place. I still think that all the tricks required in order to support official Win32s dlls are quite ugly: all the routines that use linear addresses and are called directly by Win32s applications need to do pointer mangling and msdos/vxd.c actually modifies the official dlls in order to work around some problems. But since this most likely works already, I don't think I want to change anything. -- Jukka Heinonen <http://www.iki.fi/jhei/>

8 14

← Newer
1
...
35
36
37
38
39
40
41
...
51
Older →

Jump to page:

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 November 2002