wine-devel January 2005

wine-devel@winehq.org

149 participants
343 discussions

Re: Setupapi - (Take 2) implement MyFree, MyMalloc and MyRealloc
by Huw D M Davies 24 Jan '05

24 Jan '05

On Sun, Jan 23, 2005 at 08:42:52PM -0800, Steven Edwards wrote: > Changelog: > Eric Kohl <eric.kohl(a)t-online.de> > Implement MyFree, MyMalloc and MyRealloc ... > --- /dev/null 2005-01-23 12:40:28.000000000 -0500 > +++ misc.c 2005-01-23 18:50:33.000000000 -0500 > +LPVOID WINAPI MyMalloc(DWORD dwSize) > +{ > + return HeapAlloc(GetProcessHeap(), HEAP_ZERO_MEMORY, dwSize); > +} > + ... > +LPVOID WINAPI MyRealloc(LPVOID lpSrc, DWORD dwSize) > +{ > + if (lpSrc == NULL) > + return HeapAlloc(GetProcessHeap(), 0, dwSize); > + > + return HeapReAlloc(GetProcessHeap(), 0, lpSrc, dwSize); > +} So MyAlloc zeros the memory while MyRealloc doesn't - is this really correct? If so I think a comment, at the very least, is in order. Huw. -- Huw Davies huw(a)codeweavers.com

1 0

Re: MSI: indentation and style cleanup
by Rolf Kalbermatter 24 Jan '05

24 Jan '05

On Sat, Jan 22, 2005 at 05:16:45PM +0000, Mike Hearn wrote: > Given that it can be quite complex and introduce new bugs, and given that > it's really quite a useless feature IMHO as modern Linux boxes will hang > themselves in swap hell before returning NULL from malloc I don't think > this should be a janitorial project. While I agree this may be not an easy thing to do without looking at the whole code very throughly I think saying that it doesn't help at all because on Linux you will never get this problem is a little shortsighted. Wine doesn't only compile for Linux and there might be other systems with a very straightforward swapping system which will run out of memory before the disk dies from overactivity. Also who says that the next version of Linux or some sort of stress test extension, a security hardened kernel, or a memory quota system on user basis or whatever, will not add an easy to get into out of memory situation. Couldn't Solaris for instance limit the memory available to users on a user base eventhough there are loads and loads of physical memory still available? Rolf Kalbermatter

2 1

Re: [LOSTWAGES] Update howto and downloads page (Second try)
by Tom 24 Jan '05

24 Jan '05

Scott Ritchie wrote: > I removed the conflict in this version. I hate CVS. > > This is a rewrite of the howto to make it short and sweet and remove > some of the duplicitous information to link to the User Guide instead. > Once I finish the rewrite of the User Guide, things should look pretty > smooth and easy from a new user's perspective. > > Changelog: > +Rewrite howto to link to user's guide and mention Winetools > +Add special instruction for Debian users to howto > +Make Winetools appear further up on the download's page It looks as if you added Franks Corner back in and removed http://www.von-thadden.de/Joachim/WineTools Frank is no longer the maintainer of winetools so Joachim von Thadden should be left as the maintainer. Tom

2 1

Re: wined3d updates
by Jesse Allen 24 Jan '05

24 Jan '05

On Thu, 20 Jan 2005 01:40:00 +0000 (GMT), Oliver Stieber <oliver_stieber(a)yahoo.co.uk> wrote: > --- Oliver Stieber <oliver_stieber(a)yahoo.co.uk> > opps, it helps if I actually attach them > wrote: > > Hi, > > The attached patches: > > > > Bring d3d9.h upto date with MSDN. > > Implement DepthStencils in wined3d. > > Create STUB object for d3d9 functionality not yet > > implemented. > > Start to implement stateblocks in WineD3D. > > Implements point sprites. > > Implements ColorFill. > > Almost fix reference counting. > > And implement some very basic memory management. > > > > > > I'm sorry the patch is so big, it's taken a couple > > of > > days to merge with Jasons changes and perform > > regression testing. > > Hi Oliver, I tried your patches against CVS as of 2004-01-21. I don't believe they have been applied yet. There was one rejection, so I hacked it back in where I could see it. I could have done it wrong, as I only have a crash when loading Pirates -- it follows. So maybe you ought to take a look at rediffing your patch. Thanks for your help, and I'll keep at testing. Jesse fixme:system:SystemParametersInfoW Unimplemented action: 55 (SPI_SETMOUSEKEYS) fixme:system:SystemParametersInfoW Unimplemented action: 59 (SPI_SETSTICKYKEYS) fixme:d3d:IWineD3DImpl_GetDeviceCaps Caps support for directx9 is non-existent at the moment! fixme:d3d:IWineD3DImpl_GetDeviceCaps Caps support for directx9 is non-existent at the moment! fixme:d3d:IWineD3DImpl_GetDeviceCaps Caps support for directx9 is non-existent at the moment! wine: Unhandled exception (thread 0009), starting debugger... WineDbg starting on pid 0x8 Unhandled exception: page fault on write access to 0x4a18bd19 in 32-bit code (0x4a18e98a). In 32 bit mode. Register dump: CS:0073 SS:007b DS:007b ES:007b FS:0033 GS:0000 EIP:4a18e98a ESP:4068fa94 EBP:4068f9c0 EFLAGS:00210246( - 00 -RIZP1) EAX:4a1b2e68 EBX:4a1b2314 ECX:000000ad EDX:4a181131 ESI:42800000 EDI:403ec130 Stack dump: 0x4068fa94: 00000000 00000000 00000000 00000000 0x4068faa4: 00000000 00000000 00000000 00000000 0x4068fab4: 00000000 00000000 00000000 00000000 0x4068fac4: 00000000 00000000 00000020 00000320 0x4068fad4: 00000258 00000000 00000000 00000000 0x4068fae4: 00000000 00000000 00000000 00000000 Backtrace: =>1 0x4a18e98a IWineD3DStateBlockImpl_InitStartupStateBlock+0x5ba(iface=0x4a181131) [stateblock.c:171] in wined3d (0x4068f9c0) 2 0x4a181131 IWineD3DDeviceImpl_SetTextureStageState+0x11(iface=0xffffd4b3, Stage=0x806f6ff, Type=0xf147d8b, Value=0x1ac685) [/home/jesse/wine/dlls/wined3d/device.c:3011] in wined3d (0x4a181131) 0x4a18e98a IWineD3DStateBlockImpl_InitStartupStateBlock+0x5ba [stateblock.c:171] in wined3d: movl $0x0,0xabe8(%edx) Unable to open file stateblock.c Wine-dbg>

1 0

Re: setupapi: implement MyFree, MyMalloc and MyRealloc
by Jonathan Wilson 24 Jan '05

24 Jan '05

Looks like the new misc.c is missing from the patch...

1 0

Re: [Resend] wineloader: call wineprefixcreate with explicit WINEPREFIX
by Alexandre Julliard 23 Jan '05

23 Jan '05

Crestez Leonard <cleonard(a)go.ro> writes: > This allows you do "export WINEPREFIX=~/.wine-zzz; ./wine regedit", > and automatically generate ~/.wine-zzz. You used to have to call > wineprefixcreate yourself, with correct parameters. Actually this is a feature ;-) The rationale is that if you make a typo in your WINEPREFIX it's better to get an error message than to silently create a new hierarchy and having things fail in mysterious ways. So you have to run wineprefixcreate to confirm that you really meant to use a non-existent WINEPREFIX. -- Alexandre Julliard julliard(a)winehq.org

2 1

Wine Knowledge Base
by Mike Hearn 23 Jan '05

23 Jan '05

Hi, I was going to wait a while (until it had a bit more content) before announcing this here, but as it seems people are setting up Wikis etc already here is my 2 cents: http://navi.cx/svn/misc/trunk/winekb/index.xml ** THIS IS NOT A WIKI ** Instead, it's a mini website that uses a simple dialect of XML suitable for embedding code and random text into. It's designed to be: - Easy to improve - Visually appealing - Controlled What do I mean by these things? Firstly, easy to improve: if you want to add some content to a page, save or wget the file to disk, edit it in your favourite text editor, and then send me the diff (or the full file and I'll diff it for you). You don't need any web design skill, as you can see if you do a "View Source" in the page. Secondly, visually appealing: I dislike the way Wikis look most of the time. XSL:T is a nice language for doing tree transformations so I used it. The page code looks like this: <kbpage title="Index"> <section title="Users"> * Installing <l>NativeMSI</l> and <l>NativeDCOM</l> * The <l>ConfigFile</l> * <a href="http://bylands.dur.ac.uk/~mh/wine-faq.html">#winehq channel faq</a> - read this when you have an issue </section> <section title="Developers"> * <l>AddingStuff</l> to this site * <l>InterestingPatches</l> * <l>WinelibAsBinaries</l> </section> </kbpage> See? It's easy. Yet the resulting pages looks quite nice IMHO and are uniform in style. There's a new page template here: http://navi.cx/svn/misc/trunk/winekb/template.xml Thirdly, controlled: one of the objections Newman always had to a Wiki was that it'd fill up with crap or become another appdb, and then he'd have to maintain it. You can contribute to the knowledge base by sending patches to me or to wine-devel (if you think others would find the text useful), same as any other project. I won't be adding anything there that duplicates the appdb except maybe for extremely popular programs and libraries like MSI and DCOM. You can hack on it in other ways: the code for the site is managed using Subversion/SVK, so you can check out a copy of it like so: $ svn co http://navi.cx/svn/misc/trunk/winekb If you want to do a lot of work on it, use SVK which will let you branch changes and commit locally so you can keep your patches separated nicely. Right now there isn't much content. There's some stuff for users, like how to set up a basic config file, how to install native DCOM etc, and there is stuff for developers like a list of interesting-yet-bounced patches and some notes on the "Winelib programs as binaries" work me and Vincent did. It's designed for content that doesn't really fit the main WineHQ website. If I think something makes more sense in the developer guide I'll ask you to send the content there. In other words, the KB is designed to be half-way between the structured and professional WineHQ website and a Wiki. Hope that helps! thanks -mike

2 3

New dcom95 mirror
by Ivan Leo Puoti 23 Jan '05

23 Jan '05

Hello, as Jeremy Newman wanted mirrors for dcom95, here's a new link http://www003.portalis.it/115/download/dcom95.zip Note that because of the Microsoft licencing conditions, you are licenced to download this file only if you are going to use it with wine. Ivan.

1 0

Simple web based presentation system useful for WineConf
by Mike Hearn 23 Jan '05

23 Jan '05

Hi, With the spring comes WineConf 2005, and perhaps some interesting presentations by people. Last time I went to WineConf I was asked to write a mini presentation to show newbies what Wine hacking was all about. In the end, there weren't many non-Wine developers there (which is what you'd expect, really) so we just had a discussion about how to reduce the learning curve instead. In retrospect that was far more interesting and useful than any presentation I could have done. Nonetheless, that presentation was there and when I wrote it, I also wrote a little XSL transform for slide shows. That's because I don't like PowerPoint that much, especially I don't like how sucky its web export is and slideshows are good to put on the web. So here is the presentation itself: http://bylands.dur.ac.uk/~mh/wineconf2004/presentation.xml Just load it into a web browser like Mozilla or even IE6 (konq doesn't support xslt, sorry). As you can see it's nicely Wine themed :) Here is the transform if you want to use the same presentation system yourself: http://navi.cx/~mike/xslt-slides/gen.xsl Just look at the source code of presentation.xml to see how to use it. I'm hoping we'll have a similar mix for this years Wineconf as last year - Lionels OpenGL/games presentation in particular was interesting, but I think the mix of discussion and presentations was good. One problem with presentations is that they tend to be in quite specialist areas, eg a DCOM presentation wouldn't be all that useful because there aren't many people working on it. So I think a bias more towards discussion of process and project organisation, things like that, would be more useful. That's just my humble opinion of course ;) thanks -mike

2 2

Nagging on Wineconf
by Jeremy White 23 Jan '05

23 Jan '05

Hi all, Okay, we've got 19 rsvp's for Wineconf. And that's missing me and a lot of other people that I know will be there, so shame on me and shame on you. So get over to www.winehq.org/wineconf and rsvp (including fellow folks from CodeWeavers; if you're reading this, you better plan on being there <grin>). In all seriousness, we really need an accurate head count so we can plan properly; if there really only will be 25-30 people, that makes things a good bit different than 75 people. While you're there, join the wine-conf mailing list; I think that's the most appropriate place for us to start the discussions of the agenda and to start fine tuning the details. So if you don't subscribe to wine-conf, but you're planning to go, you're going to start missing out on everything but the nag messages <grin>. Cheers, Jer

1 0

← Newer
1
...
8
9
10
11
12
13
14
...
35
Older →

Jump to page:

2025

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 January 2005