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

Re: problem building tests with msvc6

by Dan Kegel

Francois Gouget wrote: > On Mon, 13 Jan 2003, Dan Kegel wrote: > [...] > >>Also, *what tests* are you running on those versions >>of ms-windows? AFAIK, all our tests are win32... > > > That also had me confused for a while. In fact none of the tests are > running on Windows. They are all running on Wine and Wine is told to > emulate Win95, Win98, etc. *oh*. Your page should say that clearly, then, and should also mention what real operating system you're running on. Could your scripts be used to automate building or running the wine tests under real Windows (perhaps with the help of cygwin and msvc6)? - Dan -- Dan Kegel http://www.kegel.com http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045

Jan. 14, 2003

Re: Add filesytem type NTFS to config

by Andreas Mohr

On Mon, Jan 13, 2003 at 09:06:28PM -0700, Tony Lambregts wrote: > Some program (VirtualDub) checks the fsname returned by > GetVolumeInformation, to find the name of the file system, when it needs > to write files that are larger than 2GB. It refuses to create the file > when we return FAT but will successfully write the file when NTSF is > returned. > > Change Log: add configuration option to report NTFS as the file system > type for a drive. Hmm, I'm not sure whether we should increase the preexisting Filesystem type mess by doing that. I've hated the "win95", "vfat" etc. syntax almost from the beginning (well, to be fair, I think I'm not too innocent when it comes to its implementation, but at some time I just came to the conclusion that it sucked) After all we're running on *Unix* file systems in many cases, so "win95" does have no place here at all ! (neither does "vfat") Not to mention that "win95" awfully collides with the "win95" winver... And adding yet another "incorrect" "ntfs" setting makes my head want to go bonkey ;-) So I guess that it might be a good idea to think about how to solve this configuration issue in a nicer way (and of course keep the old config capabilities for about 2 years in order to have backward compatibility). We might even want to think of introducing "nameless" filesystem type settings (instead of having "broken" conflicting and "wrong" FS type names). And of course it seems as if we also need a separate FS *name* setting in order to have Wine return "NTFS" instead of "FAT" in your case... So could we start a discussion about that perhaps ? > Files changed: documentation/samples/config > documnetation/configuring.sgml > files/drive.c Finally a beautifully implemented patch ! I hate having to clean up the docu "after the fact". > -;; DON'T use "unix" unless you intend to port programs using Winelib ! > +;; - "ntfs" for ext2fs (some program need this to write files > 2GB) ^^^^^^^^ urks ! a significant portion of unix FS users don't even use ext2fs... > +;; - "unix" DO NOT USE unless you intend to port programs using Winelib ! Somehow that setting is also quite some pain... Andreas Mohr

Jan. 14, 2003

Re: Restarting winedbg

by Eric POUECH

> Hallo (Eric), > > is there another way of restarting a debugged process than to quit winedbg > and restart the whole thing? All the dll need to get reparsed, all > breakpoint need to get set up again. it depends what you want to achieve (or avoid) : - as of today, loading of DLLs (and info parsing) is mandatory, and I don't see ways of removing it. One area of improvment would be to implement a quicker parsing engine (or delay some information loading until it's needed). gcc for example implements such a scheme: first it just parses for the name of symbols ; if needed, it then parses the full information to get the extra bits (type definition, function lines information...). that would need some extra work on winedbg to get this running. using gdb and the winedbg proxying stuff could help here. - from the "environment" point of view, what you can do is store all the needed commands to re-create your environment in a text file (setting breakpoints, setting displays..), and use the source command to reload this. we could rather easily automate the creation of such a file if needed. from another perspective, winedbg does currently a lousy job at unloading DLL information when : - the process stops - and even worse, when a DLL gets unloaded (in other words, debug information is not attached internally to the module definition (as it should be), nor the process, but are global variables) unless this gets fixed, I'd recommend exiting and reentering the debugger for not running into the here above mentionned problems. A+

Jan. 14, 2003

Restarting winedbg

by Uwe Bonnes

Hallo (Eric), is there another way of restarting a debugged process than to quit winedbg and restart the whole thing? All the dll need to get reparsed, all breakpoint need to get set up again. Bye -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------

Jan. 14, 2003

Re: Add filesytem type NTFS to config

by Mike Hearn

Just curious tony, but if that's the case why doesn't Wine return NTFS all the time? Are there some apps that actually won't run if it returns NTFS at all? On Tue, 2003-01-14 at 04:06, Tony Lambregts wrote: > Some program (VirtualDub) checks the fsname returned by > GetVolumeInformation, to find the name of the file system, when it needs > to write files that are larger than 2GB. It refuses to create the file > when we return FAT but will successfully write the file when NTSF is > returned. > > Change Log: add configuration option to report NTFS as the file system > type for a drive. > > Files changed: documentation/samples/config > documnetation/configuring.sgml > files/drive.c -- Mike Hearn <m.hearn(a)signal.qinetiq.com> QinetiQ - Malvern Technology Center

Jan. 14, 2003

Re: patch for "GetFileTitleW: illegal call to GetFileTitleA" 2ed

by liu spider

--- "Dimitrie O. Paun" <dpaun(a)rogers.com> wrote: > If no one complained, it's probably OK until > Alexandre > gets around to it. He can't reply in real time, wait > for > a few days. If you see commits going in (subscribe > to, > or check the mail archives for wine-cvs(a)winehq.org > to > monitor the checkins) and yours is not applied, > email > and ask him what's up. > I have already subscribed wine-cvs and have been monitoring it all the time. Thanks for your clues. liuspider __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com

Jan. 14, 2003

Re: [D3D status] Page update...

by Sylvain Petreolle

Could you update the Revolt Demo page ? The links present on the page you give on your site are old. To avoid the annoying registration page, the demo can be donwloaded at http://www.re-volt.com/thankyou.html or direct link : http://www.re-volt.com/images/revoltdemo.zip --- Lionel Ulmer <lionel.ulmer(a)free.fr> a écrit : > Hi all, > > I updated the D3D status page (http://www.bbrox.org/d3d_status.html) > with > some new screenshots and some new demos. Nothing revolutionnary > though :-) > > Thanks to Christian for the 3D Mark 2000 paragraph. > > Lionel > > -- > Lionel Ulmer - http://www.bbrox.org/ > ===== Sylvain Petreolle spetreolle(a)users.sourceforge.net Fight against Spam ! http://www.euro.cauce.org/en/index.html ICQ #170597259 "Don't think you are. Know you are." Morpheus, in "Matrix". ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com

Jan. 14, 2003

Re: problem building tests with msvc6

by Francois Gouget

On Mon, 13 Jan 2003, Dan Kegel wrote: [...] > Also, *what tests* are you running on those versions > of ms-windows? AFAIK, all our tests are win32... That also had me confused for a while. In fact none of the tests are running on Windows. They are all running on Wine and Wine is told to emulate Win95, Win98, etc. It's not that it not useful, it is. It's just that at first I hoped it was running the tests on the real thing and reported the results. But I guess that was a bit unrealistic. If I am off-track here then there is something wrong since apparently none of the tests fails and many are still known to fail on Windows... -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ RFC 2549: ftp://ftp.isi.edu/in-notes/rfc2549.txt IP over Avian Carriers with Quality of Service

Jan. 14, 2003

Re: problem building tests with msvc6

by Dan Kegel

Paul Millar wrote: > On Thu, 9 Jan 2003, Dan Kegel wrote: > >>Paul Millar wrote: >> >>>[1] - http://www.astro.gla.ac.uk/users/paulm/WRT/wrt.php >> >>Wow. Does it really make sense to test against windows 2.0 >>or 3.0 anymore? I recall Windows itself was pretty much a joke >>and terribly unstable until windows 3.1... > > > Probably not, but I thought: what the hell :^) Also, *what tests* are you running on those versions of ms-windows? AFAIK, all our tests are win32... >>Are the WRT sources in CVS? > > > Well, they're in _a_ cvs (here in Glasgow) but not _the_ winehq cvs. > They're currently an embarrassing hackage of bash scripts with some > customised code to do the bits sed/awk/... couldn't easily do. Oh, and > some PHP to act as a front end. > > But, if anyone wants to have a look and/or help out, I'll try and figure > out how to get the code out on the web, or something. Please do... that way others can run their own copies of your wine tinderbox, which will give us some assurance one will always be around! - Dan -- Dan Kegel http://www.kegel.com http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045

Jan. 14, 2003

Re: new to wine and would like to be actively involved.

by Tom Wickline

Dan Kegel wrote: > By the way, > http://www.dssd.ca/wine/Wine-Contrib-0.7.html#conf_tests > still says > "Either C or perl skills" > but perhaps this should just say > "C programming skills" > as the Perl tests were removed. > - Dan > Thanks Ill note to do that in 0.8 Tom

Jan. 14, 2003