August 2002 - Wine-Devel - list.winehq.org

Re: Wine Hides On-board RAM

by Francois Gouget

On Mon, 26 Aug 2002, Ian D. Stewart wrote: [...] > > To differentiate from Windows, nobody's suggesting you remove and > > reinstall > > Linux, here :-) > > Unless I misunderstood Andreas' e-mail, that i pretty much what he is > recomending. Not quite. You can compile and run a new Linux kernel without reinstalling your system. Furthermore, you can switch back and forth between the old kernel and the new one at each reboot. Andreas was recommending a blind upgrade with a prayer that the bug be fixed, but you can also view this as a way to diagnose the problem, pretty much like one would do a binary search on Wine's CVS sources to find when a bug appeared. In your case, either the bug is still present in the latest kernel which then means you are not wasting your time trying to fix a bug that has already been fixed, or it is no longer present and then analyzing the differences between the two kernels may help you find what was wrong. Note: I'm running Wine a lot on my system and have never seen MemTotal change (with 2.4.17 and older kernels). -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ Any sufficiently advanced bug is indistinguishable from a feature. -- from some indian guy

Aug. 27, 2002

Re: RFC: 'test' bugzilla keyword

by Francois Gouget

On Sat, 24 Aug 2002, Tony Lambregts wrote: [...] > I would suggest that "apifailure" would be better (and longer..) but > It would be great to have this. The problem with apifailure (and api*) is that it may be the test that is wrong, not the API implementation. Also I would like something that reminds people this is about the conformance tests (previously known as regression tests). Maybe 'conformance' would work? -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ Linux, WinNT, MS-DOS - also known as the Good, the Bad and the Ugly.

Aug. 27, 2002

Re: Wine Ma os X port

by Andriy Palamarchuk

--- Fausto Saporito <fausto.saporito(a)virgilio.it> wrote: > Hello, > > i'm completely a newbie, but should be possible > merge bochs code in > order to emulate an x86 cpu in wine? > The MacOS port of Bochs is quite operative. Such idea was descussed before many times. Run search on Google with keywords Wine bochs for more information. Andriy __________________________________________________ Do You Yahoo!? Yahoo! Finance - Get real-time stock quotes http://finance.yahoo.com

Aug. 27, 2002

Re: Need to know some macro values

by Andriy Palamarchuk

Fabian, thank you for help. --- Fabian Cenedese <Cenedese(a)indel.ch> wrote: > > >I'm going to add some define's to our headers, but > >can't find their values online. > >Can somebody who has Microsoft headers compile and > run > >the test application and send me the output? > > I tried but I failed. I don't know where you have > these definitions from, I'm working on implementing a function LsaNtStatusToWinError, which maps NT status codes to Windows error codes, according to: http://support.microsoft.com/default.aspx?scid=KB;EN-US;q113996& > but they aren't anywhere in the normal MSVC6 Studio. > Also MSDN > doesn't know anything. Maybe in some SDK... I just got response from Dmitry. You are right, he found almost all of them in XP/Win2000 development kits headers. Thank you, Andriy __________________________________________________ Do You Yahoo!? Yahoo! Finance - Get real-time stock quotes http://finance.yahoo.com

Aug. 27, 2002

Re: Need to know some macro values

by Fabian Cenedese

>I'm going to add some define's to our headers, but >can't find their values online. >Can somebody who has Microsoft headers compile and run >the test application and send me the output? I tried but I failed. I don't know where you have these definitions from, but they aren't anywhere in the normal MSVC6 Studio. Also MSDN doesn't know anything. Maybe in some SDK... Sorry Fabi

Aug. 27, 2002

Re: Wine Ma os X port

by Fausto Saporito

Hello, i'm completely a newbie, but should be possible merge bochs code in order to emulate an x86 cpu in wine? The MacOS port of Bochs is quite operative. regards, fausto Lunedì, Agosto 26, 2002, alle 09:27 PM, Lionel Ulmer ha scritto: >> b) Wine includes an x86 emulator and gets nearly re-written. > > Well, the 'nearly gets re-written' is maybe a little bit exagerated.... > Winelib already works on PPC (or at least Marcus is trying to get it to > work). That is already a first step :-) After, there are a lot of tricky > stuff to do, but no big rewrite (well, except in the core DLLs like > Kernel > and the server). > > I wonder if anybody ever started a 'bug' or 'task' on Bugzilla to write > down > everything that would be needed to support Wine + emulation. > > Lionel > > -- > Lionel Ulmer - http://www.bbrox.org/ >

Aug. 27, 2002

Re: wine/ dlls/kernel/wowthunk.c dlls/ntdll/file.c ...

by Dmitry Timoshkov

"Marcus Meissner" <meissner(a)suse.de> wrote: > > Convert most of the file APIs to Unicode. > > Is it just me or did this patch and several more not go over wine-patches? It's a usual merge from Crossover Office which Alexandre does every time when new version of cxoffice is released. -- Dmitry.

Aug. 27, 2002

Re: wine/ dlls/kernel/wowthunk.c dlls/ntdll/file.c ...

by Marcus Meissner

On Mon, Aug 26, 2002 at 08:14:00PM -0500, Alexandre Julliard wrote: > ChangeSet ID: 1030410840440784468854876 > CVSROOT: /opt/cvs-commit > Module name: wine > Changes by: julliard(a)wine.codeweavers.com 02/08/26 20:14:00 > > Modified files: > dlls/kernel : wowthunk.c > dlls/ntdll : file.c > dlls/winedos : int21.c > files : directory.c dos_fs.c drive.c file.c profile.c > smb.c smb.h > include : drive.h file.h > loader : task.c > memory : registry.c > misc : registry.c > msdos : dosconf.c int11.c int21.c ioports.c > scheduler : process.c > > Log message: > Dmitry Timoshkov <dmitry(a)codeweavers.com> > Convert most of the file APIs to Unicode. Is it just me or did this patch and several more not go over wine-patches? Ciao, Marcus

Aug. 27, 2002

Re: Wine Hides On-board RAM

by Ian D. Stewart

On 2002.08.25 07:38 Andreas Mohr wrote: > On Sun, Aug 25, 2002 at 08:17:09AM -0400, Ian D. Stewart wrote: > > On 2002.08.18 12:21 Andreas Mohr wrote: > > > On Sun, Aug 18, 2002 at 11:32:54AM -0400, Ian D. Stewart wrote: > > > > After running Wine for awhile, /proc/meminfo reports MemTotal as > > > 32680 > > > > kb. The system performs as if it only had 32 MB of RAM. A > reboot > > > of > > > > the system resets total memory to the proper value. > > > > > > > > My question is: > > > > > > > > 1) Has anybody else encountered this? > > > > 2) Does anyone know what causes this, or better yet how to avoid > it? > > > > 3) Is there anyway to recover the lost RAM short of a reboot? > > > > > > Huh ? This is very, very, VERY strange ! > > > Something like this should never happen. > > > Are you sure it's caused by Wine only, or maybe it is due to > faulty > > > memory > > > instead ? (and thus the board/Linux notices that only 32MB are > useable > > > and resorts to accessing 32MB only). > > > > Well I can't say with absolute certainty that it's caused by Wine, > but > > the system runs without any problems for extended periods of time so > > > long as I don't run Wine, and consistently 'loses' memory when I > *do* > > run wine. > > > > I don't know exactly what's going on. I do know that there appears > to > > be some sort of threshold that is reached at which point the memory > > hiding occurs (e.g., the same issue arises whether I run Wine for 5 > > hours at one shot or for 30 minutes a day for 10 days) and the > > threshold isn't 'reset' until I reboot. > > > > > > > > Again, I'm utterly puzzled when hearing such a story. > > > Or maybe Wine accesses some Linux memory management function in > some > > > way > > > that causes Linux to tamper with the value for some reason ? > > > This wouldn't be the first time that Wine is the only program to > > > reveal > > > some severe bug in Linux memory management... > > > > > > Definitely try upgrading your kernel, too. > > > > I have no problem with upgrading, but I would like to know *why* I > am > > upgrading (i.e., what bug is causing the problem, and how does the > new > > kernel address the bug). To do otherwise strikes me as being > > equivelant to the tendency in the Windows community whenever > something > > odd happens. > *sigh* > You're definitely not of the easy kind of people, are you ? ;-) > A lot of people would just upgrade and be happy in case the bug is > fixed, > but you... :) Guilty as charged ;) > > Well, if you're so eager to learn what the problem is, then I'd > suggest > to get your hands pitch black dirty immediately ;-) > > Find out where /proc/meminfo gets fed with values, then find out which > part messes with the MemTotal value in any way. > > Hmm, arch/i386/mm/init.c/si_meminfo() sounds like a sure winner. > I'd suggest looking for the totalram_pages variable (add logging > whenever > that one gets modified in some way). > OTOH I don't see any place where there is a direct assignment of that > variable. Hmm, where does that variable even get initialized then ??? > (well, probably declaration auto initialization then) > > Oh well, good luck ! ;) Thanks. I'll report back once I know more. Ian

Aug. 27, 2002

Re: Wine Hides On-board RAM

by Ian D. Stewart

On 2002.08.26 09:03 Derek Broughton wrote: > From: "Ian D. Stewart" <idstewart(a)compuvative.com> > > > I have no problem with upgrading, but I would like to know *why* I > am > > upgrading (i.e., what bug is causing the problem, and how does the > new > > kernel address the bug). To do otherwise strikes me as being > > equivelant to the tendency in the Windows community whenever > something > > odd happens. > > Not at all. Wine has always been distributed as 'alpha' software, and > thus > we can expect that a lot of things are continuously getting fixed. > Nobody's > going to try fixing something that's only reported in an old version > of the > software. So you upgrade, test again, and if it's still a problem > report > the bug. I thonk you misunderstood my e-mail. The problem apparently does not lie with Wine per se (I have no problem with upgrading Wine, especially considering its alpha status and active development, and have on several occasions IOT track down regression bugs), but rather with the memory management aspects of the Linux kernel. > > To differentiate from Windows, nobody's suggesting you remove and > reinstall > Linux, here :-) Unless I misunderstood Andreas' e-mail, that i pretty much what he is recomending. Ian

Aug. 27, 2002