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

Re: How to Calling PE Dlls on linux??

by Roderick Colenbrander

> I have a PE Dll named Arithmetic.dll which exports a function, > it's prototype is: > void sort(unsigned int*, int num) > The easiest way would be to use LoadLibrary/GetProcAddress to load the function from the library. That way you avoid linking to it which makes things more complicated. In order to be able to use wine functions you need to (re)compile parts of your program using Winelib (e.g. winegcc/wineg++). Your program will depend on Wine but you will be able to use the win32 dll. Regards, Roderick Colenbrander

Aug. 20, 2007

How to Calling PE Dlls on linux??

by trulyliu

hi: I am sorry to disturb you with a question about calling PE Dll on linux. This is really an old question. I found the sameness issues in mail list. http://www.winehq.org/pipermail/wine-devel/2003-December/thread.html http://www.winehq.org/pipermail/wine-devel/2005-November/thread.html#41917 http://www.winehq.org/pipermail/wine-users/2004-August/014685.html http://www.winehq.org/pipermail/wine-devel/2006-August/050619.html I have tried the ways discussed in these threads。 But it's not clear enough how to do this. So I send this mail to you for some help. I have a PE Dll named Arithmetic.dll which exports a function, it's prototype is: void sort(unsigned int*, int num) I want to call the function in my Linux App. I used winedump to generate a spec file winedump spec Arithmetic.dll This comand generated three files: Arithmetic_dll.h Arithmetic_main.c and Arithmeticspec. What's the next exactly step I should do? What's the usage of the three files? And wow could I use them? I made reference to mplayer's implementation, It's code is a little clutter， and I don't have experience on MS D-Show. Could you give me some simple sample codes ?? Best Regards. -- trulyliu(a)gmail.com

Aug. 20, 2007

Re: winmm: Change default driver order to be alsa,coreaudio,oss - try2

by Vitaliy Margolen

Maarten Lankhorst wrote: > Vitaliy Margolen schreef: >> Maarten Lankhorst wrote: >>> Vitaliy Margolen schreef: >>>> That didn't work all that well: >>>> >>>> err:wave:DSDB_MapBuffer Please run winecfg, open "Audio" page and set >>>> "Hardware Acceleration" to "Emulation". >>>> wine: Unhandled page fault on read access to 0x00000030 at address >>>> 0x7edf2cf8 (thread 0011), starting debugger... >>>> >>>> This is with OSS and full acceleration. >>> Just sent-in patch to dsound fixes that, even then it is no reason not >>> to accept this patch as it would have happened already with the current >>> code. >>> >> Doesn't help: > To fix it I need a more usable backtrace then that, one that has all > dsound calls too. > Attached to the bug http://bugs.winehq.org/show_bug.cgi?id=9381 Vitaliy.

Aug. 20, 2007

Re: [Winetest RFI] What do you want out of the test suite?

by Wagner Ferenc

Paul Vriens <paul.vriens.wine(a)gmail.com> writes: > Wagner Ferenc wrote: >> Paul Vriens <paul.vriens.wine(a)gmail.com> writes: >> >>> http://www.xs4all.nl/~pvriens/200708181000_with_todo_yellow_border_and_grou… >>> is the same but also shows that are are todo's for a group in the >>> summary. >> >> Yeah, that's what I experimented with, thanks for presenting it so >> quickly! I'd add a title (tooltip) for the decorated group results, >> stating the number of todos (next to the best number, or alone). >> Skips could receive the same treatment, too. > > Do you really think there's a need to have the left border also in the > group results? I think that it suffices to have them in the main > summary. They have more to do with the test and not so much with the > report. Yes, you are right. They are more important in the main summary, as they are a property of the tests, not the individual reports. Still, I'd keep them everywhere, just for the shake of consistency. But if they clutter the screen too much, let them go. One more thing to vote on. > If we need them in the group results we have the strange thing again > that some are mentioned (the ones that don't differ and have 0 > failures) in the main results but not in the group. This of course > can be overcome again by adding them ...... I'm not sure this would warrant adding these otherwise uninteresting lines. One can't easily see the dissected results this way, but todos aren't really represented in the output anyway. -- Cheers, Feri.

Aug. 20, 2007

Re: [Winetest RFI] What do you want out of the test suite?

by Paul Vriens

Wagner Ferenc wrote: > Paul Vriens <paul.vriens.wine(a)gmail.com> writes: > >> http://www.xs4all.nl/~pvriens/200708181000_with_todo_yellow_border_and_grou… >> is the same but also shows that are are todo's for a group in the >> summary. > > Yeah, that's what I experimented with, thanks for presenting it so > quickly! I'd add a title (tooltip) for the decorated group results, > stating the number of todos (next to the best number, or alone). > Skips could receive the same treatment, too. > >> (The yellow border will clash with the mixed results). > > We are running out of colors... :) What about something like 50ffff > or ff50e0? I'm still experimenting with the color. Not sure yet what to do/pick. Do you really think there's a need to have the left border also in the group results? I think that it suffices to have them in the main summary. They have more to do with the test and not so much with the report. If we need them in the group results we have the strange thing again that some are mentioned (the ones that don't differ and have 0 failures) in the main results but not in the group. This of course can be overcome again by adding them ...... Cheers, Paul.

Aug. 20, 2007

Re: setupapi: if needed create directories for fake dlls

by Alexandre Julliard

"Mikolaj Zalewski" <mikolajz(a)google.com> writes: > @@ -302,9 +302,28 @@ BOOL create_fake_dll( const WCHAR *name, > else > { > h = CreateFileW( name, GENERIC_WRITE, 0, NULL, CREATE_NEW, 0, NULL ); > + > + if (h == INVALID_HANDLE_VALUE && GetLastError() == ERROR_PATH_NOT_FOUND) > + { > + WCHAR *pathel; > + > + /* create the directory/directories */ > + pathel = strchrW(name, '\\'); > + while (pathel != NULL) > + { > + *pathel = 0; You shouldn't write to the name, it's a const pointer, even if strchrW hides the warning. -- Alexandre Julliard julliard(a)winehq.org

Aug. 20, 2007

Re: [PATCH] handle builtin regedit.exe.so

by Alexandre Julliard

Marcus Meissner <marcus(a)jet.franken.de> writes: > On my system it tries to load /usr/lib/wine/regedit.exe.so > (via symlink) and this fails. We stopped using symlinks a long time ago, it sounds like your .wine dir is out of date. -- Alexandre Julliard julliard(a)winehq.org

Aug. 20, 2007

Re: [Winetest RFI] What do you want out of the test suite?

by Wagner Ferenc

Paul Vriens <paul.vriens.wine(a)gmail.com> writes: > http://www.xs4all.nl/~pvriens/200708181000_with_todo_yellow_border_and_grou… > is the same but also shows that are are todo's for a group in the > summary. Yeah, that's what I experimented with, thanks for presenting it so quickly! I'd add a title (tooltip) for the decorated group results, stating the number of todos (next to the best number, or alone). Skips could receive the same treatment, too. > (The yellow border will clash with the mixed results). We are running out of colors... :) What about something like 50ffff or ff50e0? -- Cheers, Feri.

Aug. 20, 2007

Re: comdlg32: printdlg: Fix number display in PrintDlgW()

by Alexandre Julliard

Alexander Nicolaysen Sørnes <alex(a)thehandofagony.com> writes: > vsprintfW and friends do not support float numbers, so we have to format an > initial string with printf() and then print it to a wide string with > vsprintfW()'s %hs format. For a simply conversion to Unicode MultiByteToWideChar is a better choice. -- Alexandre Julliard julliard(a)winehq.org

Aug. 20, 2007

Re: Fixing wrong prototypes in a header

by Francois Gouget

On Wed, 15 Aug 2007, Juan Lang wrote: [...] > Should I leave the prototypes incorrect in wintrust.h to match the > PSDK, or should I fix them to make them more convenient for me to use? I think that's a case where we could diverge from the PSDK (with a comment explaining why). Otherwise the header is completely useless: we could not even make sure its prototypes match those of our implementation. Btw, did you check this against the very latest PSDK? Could you provide the name of one of these functions? -- Francois Gouget <fgouget(a)free.fr> http://fgouget.free.fr/ tcA thgirypoC muinelliM latigiD eht detaloiv tsuj evah uoY

Aug. 20, 2007