wine-devel May 2004

wine-devel@winehq.org

124 participants
249 discussions

Getting the API's for Windows Applications
by Jacobus Erasmus 18 May '04

18 May '04

Is it possible to workout or read the API's that a specific Windows application use ? The theory is that it would be possible to estimate the amount of work needed to get a Windows app to work on Wine by calculating the number of API's that is not working or only half working and estimating the time it would take to correct these API's. By running wine-debug it is possible to get the API's used by an application. I'm hoping that there is some simpler way (although I'm not holding my breath) to read the API's used by an application directly from the .exe or .dll. I'm working on a utility that would collect this information and estimate the number of man hours it would take to get an application running on Wine. Also I'm hoping to build a utility that can collect stats on the API's being used in an application as well. The idea is to build a web page with these statistics for the applications that people want to run on a wine installation. If we can get some participation on the work and completeness of an API. It should be able to build a pretty accurate picture of the amount of work that needs to be done to get an app running under Wine. There is some other interesting side effects that I will not elaborate on until I have something in place (this is very simple but time does not permit. Somebody feels better equip to do this please say so) If not I will probably get arround to doing something this weekend. Cu jacobus(a)kewlconcepts.co.za

3 2

Re: Incoming Message
by Julliard 18 May '04

18 May '04

1 0

RE: Protected message
by Dmitry 18 May '04

18 May '04

1 0

Re: Re: Empty (Stubs in spec only) d3drm
by fenix＠club-internet.fr 18 May '04

18 May '04

>On Tue, May 18, 2004 at 12:59:57AM +0200, Ivan Leo Murray-Smith wrote: >> This dll is needed by a game, bug report number 1202. With this empty dll, the >> game crashes at the same point where it crashes when used with the native copy, >> mainly because it crashes before any function in the dll is called. But at least >> it doesn't crash with a dll not found error. You'll have to run the autofoo >> stuff after applying this patch. > >Ivan, > >As far as I know, you did not submit also a patch to the default >configuration file to add this DLL with 'native' as default (which is a good >thing as all the people having a Windows box have this DLL - it could even >be installed if someone manages to install DirectX under Wine). > > Lionel > Hi Lionel, This dll should be easy to implement (almost geometries utilities functions as d3dx8/d3dx9 for d3d8/d3d9). It can be a begin for people who want to begin patches for wine (as for d3dx8/d3dx9) :) Regards, Raphael PS: d3dx8/d3dx9 have difficults parts on some textures and geometry loading (stream/unstream) and shaders utilities.

3 3

VirtualProtect bug?
by Robert Reif 18 May '04

18 May '04

I'm trying to write a test that checks for data overruns using VirtualAlloc and VirtualProtect and I think I may have found a bug. Here is the problem: DWORD dwPageSize; BYTE * twoPages, temp; DWORD flOldProtect; twoPages = VirtualAlloc(NULL, 2 * dwPageSize, MEM_RESERVE | MEM_COMMIT, PAGE_READWRITE); res = VirtualProtect(twoPages + dwPageSize, dwPageSize, PAGE_NOACCESS, &flOldProtect); temp = twoPages[dwPageSize + 1]; // should cause exception but doesn't in wine twoPages[dwPageSize + 1] = 0; // does cause exception I would like to write a test to check the exception handling but I don't know how to do a __try and __except in C. Any ideas?

2 2

RE: Message Notify
by Julliard 18 May '04

18 May '04

1 0

Re: [MSI] Added version info to MSI dll
by Filip Navara 18 May '04

18 May '04

Christian Costa wrote: >+#define WINE_FILENAME_STR "amstream.dll" > This should be '#define WINE_FILENAME_STR "msi.dll"'. - Filip

2 1

Path too deep???
by Clare 18 May '04

18 May '04

Hello groups, I would like to use Wine to run a Windows compiler "cc" to complie a c file "test.c" on Linux, but I have the problem. <try1> cd /a1/a2 wine -- /usr/local/bin/cc -c /b1/b2/b3/b4/b5/b6/test.c -o test.o Catastrophic error: could not open source file \b1\b2\b3\b4\b5\b6\test.c I try this in another way like this: <try2> cd /a1 wine -- /usr/local/bin/cc -c /b1/b2/b3/b4/b5/b6/test.c -o test.o This works well. Could you give me some informations why <try1> has the error? Thank you. Best Regards, Clare

2 1

RE: Text message
by Dmitry 18 May '04

18 May '04

1 0

Re: Document
by Julliard 18 May '04

18 May '04

1 0

← Newer
1
...
8
9
10
11
12
13
14
...
25
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 May 2004