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

warning to "wine on cygwin" experimenters
by Anonymous Jan. 23, 2004

Jan. 23, 2004

I got cygwin to compile wine to the point where wine-install tried to run regedit on winedefault.reg. I should have been paying closer attention. The good news is that the wine regedit.exe works like a charm. The bad news is that it overwrote my actual windows registry with the bunk values in winedefault.reg. Not gonna be very easy to roll back. So... WATCH OUT! That last step's a doozy.

2 1

Re: WWN#206
by Rein Klazes Jan. 23, 2004

Jan. 23, 2004

Hi, > Mike wondered why the end of 1998 seemed so productive. > Rein felt two factors might have had a hand it: in October > CVS mistakenly reported the same commit more than once, > however at time Corel was actively working on Wine and > there geniunely were a lot of commits. > > Note - this graph does not reflect the size of the Wine > source code. It's only the commits. Anyone want to produce > a graph of how much has been added? I think it would be > interesting to see the trend. You can find it here: http://home.wanadoo.nl/~wijn/wine/cvssize.png Notes: - All files in the cvs wine tree are included, not just the sources. - I excluded the (libs/)unicode directory. That is almost 5 MByte of mostly generated source files creating an ugly step in an otherwise smooth curve. - The trend quite accurately represents the growth in the first 3 years. The last 2 years the rate of growth is clearly increasing. - The number of cvs commits in October '98 was corrected to 258 commits. Rein. -- Rein Klazes rklazes(a)xs4all.nl

1 0

RE: shlwapi prototype fixes
by Ge van Geldorp Jan. 23, 2004

Jan. 23, 2004

> From: Robert Shearman > > > MLLoadLibrary was recently documented by Microsoft. > > My changes makes it conform to the now-documented prototype > > so I don't see what's wrong with it? > > Either it is different on Windows XP (my system is Windows > 2000 SP4 with IE6 SP1), or they just got it wrong. The fact > remains that I have seen an application working perfectly > well on Wine whilst using this function as it stands. Yes, you're right. Ordinals 377 and 378 (MLLoadLibraryA/MLLoadLibraryW) in both the Win2k and WinXP shlwapi.dll pop 12 bytes from the stack on return. I'll resubmit my patch for the other prototypes. Gé van Geldorp.

1 0

RE: comctl32 resources / shlwapi prototype fixes
by Robert Shearman Jan. 23, 2004

Jan. 23, 2004

> Changelog: > Sync with ReactOS 0.2 > Fix various function prototypes to conform to PSDK > > Index: dlls/shlwapi/ordinal.c > =================================================================== > RCS file: /home/wine/wine/dlls/shlwapi/ordinal.c,v > retrieving revision 1.75 > diff -u -r1.75 ordinal.c > --- dlls/shlwapi/ordinal.c 1 Oct 2003 03:10:42 -0000 1.75 > +++ dlls/shlwapi/ordinal.c 22 Jan 2004 23:41:41 -0000 > @@ -3414,7 +3414,8 @@ > * Success: A handle to the loaded module > * Failure: A NULL handle. > */ > -HMODULE WINAPI MLLoadLibraryA(LPCSTR new_mod, HMODULE inst_hwnd, > DWORD dwFlags) > +HMODULE WINAPI MLLoadLibraryA(LPCSTR new_mod, HANDLE inst_hwnd, > DWORD dwFlags, > + LPCSTR component, BOOL cross_code_page) This is wrong. Please resubmit without this change until we can discover why the prototype has 5 parameters, yet on my system the implementation only takes 3. > { > /* FIXME: Native appears to do DPA_Create and a DPA_InsertPtr for > * each call here. > @@ -3453,7 +3454,8 @@ > * > * Unicode version of MLLoadLibraryA. > */ > -HMODULE WINAPI MLLoadLibraryW(LPCWSTR new_mod, HMODULE > inst_hwnd, DWORD dwFlags) > +HMODULE WINAPI MLLoadLibraryW(LPCWSTR new_mod, HANDLE inst_hwnd, > DWORD dwFlags, > + LPCWSTR component, BOOL cross_code_page) Same again > { > WCHAR mod_path[2*MAX_PATH]; > LPWSTR ptr;

1 0

RFC on our new initiative
by Jeremy Newman Jan. 23, 2004

Jan. 23, 2004

>From the desk of Jeremy White (who is at LinuxWorld ATM). Hey folks, We've just launched a major new initiative, the CodeWeavers CrossOver Compatibility Center. You can check it out at http://www.codeweavers.com/site/compatibility/ but I think it's fair to describe it as the appdb on steroids. I wanted to announce it here to give folks a sense of what we're up to, and to apologize a bit in advance for stepping on the toes of folks that have been doing good work within the appdb. However, the #1 problem we have had over the past year or so is how to handle all the many, many requests we get for applications not on our 'supported' list. We've basically ended up sending people away, which has been pretty unsatisfying. Further, we haven't had any good way of determining what our priorities should be; we follow major paying clients, but beyond that, we mostly just follow our gut hunches in establishing priorities. We hope to end that; this new center lets our customers vote for apps, and lets non customers make pledges. We can hopefully follow those pledges to get apps running (and we'd probably be open to having wine hackers committing to support apps in exchange for a piece of the pledges, but we haven't gotten there yet). We've also, we hope, set the stage for a major new Wine related initiative - we hope to encourage lots of ISVs to certify their apps against Wine. The rationale for this is pretty simple - apps won't run on Wine as well as they do on Windows until developers start testing against Wine. They've got to start somewhere - we're trying to give them that beginning. We're obviously also hoping that this will help us to continue funding the work we've been able to do on Wine so far. As much of a struggle as it's been at times, we really feel lucky that we've been able to do so much. We hope that these initiatives will give us an extra little boost so we can help push Wine over the hump. I sincerely believe that the day when we can honestly tell people "It will most likely work nicely on Wine" is not long off. I also believe in the tooth fairy and Santa Claus, so make what you will of that <grin>. At any rate, this is a brand new initiative for us; call it an 0.1.7 release. We're very open to comments and thoughts and suggestions, so I would greatly appreciate any public or private comments you have to make. Cheers, Jeremy -- Jeremy Newman <jnewman(a)codeweavers.com> CodeWeavers, Inc.

9 18

Re: Add support for MDICREATESTRUCT conversion for 16-bit windows
by Alexandre Julliard Jan. 23, 2004

Jan. 23, 2004

Dmitry Timoshkov <dmitry(a)baikal.ru> writes: > I've got a bug report that after my MDI rewrite some 16-bit MDI app > stopped to work. That's not a surprise at all. The surprise is that > STRUCT32_xxx conversion helpers didn't cope correctly with 16-bit > hInstance and actually that caused a 16-bit app to misbehave in > the first place. I had to use GetExePtr() because MapHModuleSL checks > for NE_FFLAGS_WIN32 (why?) and bails out. Using GetExePtr is going to return the wrong instance once we get back to 16-bit code. The instance handles are actually not supposed to be converted at all, we just expand the 16-bit ones to 32-bit. What was the problem with your 16-bit app? -- Alexandre Julliard julliard(a)winehq.com

2 1

Re: Implement binary relocatability
by Alexandre Julliard Jan. 23, 2004

Jan. 23, 2004

Mike Hearn <mike(a)theoretic.com> writes: > Before Wine would not be able to find libwine nor ntdll.so, now it can. > > I hope this patch is OK, as I think this is a useful feature that far more > free software should support. The list of use cases is big. As dicussed a couple of weeks ago, this needs to be optional; you don't necessarily always want that behavior, and it conflicts with the --prefix option. -- Alexandre Julliard julliard(a)winehq.com

1 0

Re: GetCommandLine issue with Dungeon Keeper
by Frank.Schruefer＠t-online.de Jan. 23, 2004

Jan. 23, 2004

( REPOST, again: I was told that my massages need long time to appear because I'm not subscribed as frank.schruefer(a)t-online.de, ok, but my postings as wine(a)man-made.de (which I'm subscribed as) never come through. Maybe that is because mozilla only allows configuration for one outgoing mailserver which is the t-online one? Anything I could do about the situation? ) > > I'll soon come up with a win98 winnt comparison for the functions in > question. > I just have some trouble setting up *real* windows, believe it or not, > asrock > with SIS is nothing (old) windows' like! > Setting up wine is much easier LOL! > Hy, Ok, I made a simple test programm reading argv, GetCommandLineA and GetModuleFileNameA. I failed with NtCurrentTeb, even after installing microsoft sdk ... it didn't get linked. Well, I actually have very little experience if it comes to the C language but the test results I already have answer most of our questions already I think. I'd say the bottom line of the test results below is that wine almost perfectly simulates win32s behaviour but has no support for win9x be- haviour (regarding GetCommandLine* and argv). Changing the 'Windows' config parameter of wine in the [Version] sec- tion didn't make any difference to the test results from wine. That's what needs to be changed. Some of you suggested to always deliver full path but as some others said I also think that might break more programs than it'll make work so I'd oppose that idea. I think the solution is something like: if(GetVersion() & 0x80000000) /* not win32s */ { behave_as_win9x_and_modify_actual_command_line(); } else { behave_as_now(); } Basically: make the 'Windows' param in [Version] affect whether the command line is altered or not. So in my eyes it should come down to this: if(keeper_started_with_full_path() || wine_behaves_as_win9x_set_in_config()) { keeper_working = TRUE; } // woohoo! That I call programming ;-) To introduce a totally new config param to set wines behaviour here is neither necessary nor desireable. I see only one question remaining: at which place in wine should the commandline be modified if_win9x is 'set'? In GetCommandLineA? Guess no. Somewhere before CreateProces I think. But as I already menitioned c is not my mother tongue so I hope somebody else here might come up with the final solution ... Appendet here you'll find the source of a little test prog, a batch and the output the prog produced on: Windows 98, Windows NT 4.0 and Wine (on SuSE Linux 9.0). As I read it simulation of win9x behaviour needs to replace slashs by backslashs (which win32s has no probles with but 9x does) and relative paths by full paths and also the return of GetModuleFileNameA should be made to all uppercase - just to be on the safe side. ===================== TEST PROGRAM ==================== #include <windows.h> #include <stdio.h> #include <stdlib.h> int main(int argc, char** argv) { int i; char buffer[1024]; printf("+++ GetCommandLineA +++\n"); printf("%s\n", GetCommandLineA()); printf("+++ GetModuleFileNameA +++\n"); GetModuleFileNameA(0, buffer, sizeof(buffer)); printf("mfna: %s\n", buffer); printf("+++ argc & argv +++\n"); printf("argc: %i\n", argc); for(i = 0; i<argc; i++) printf("argv #%i: %s\n", i, argv[i]); getch(); } ======================================================= ===================== TEST BATCH ====================== echo %0 cmdline ======================================================= ================= WIN98: FROM EXPLORER ================ +++ GetCommandLineA +++ "C:\Eigene Dateien\WineCommandLine\CMDLINE.exe" +++ GetModuleFileNameA +++ mfna: C:\EIGENE DATEIEN\WINECOMMANDLINE\CMDLINE.EXE +++ argc & argv +++ argc: 1 argv #0: C:\Eigene Dateien\WineCommandLine\CMDLINE.exe ======================================================= ================= WINE: FROM EXPLORER ================= (not applicable) ======================================================= =============== WINNT4.0: FROM EXPLORER =============== +++ GetCommandLineA +++ "C:\Eigene Dateien\WineCommandLine\CMDLINE.exe" +++ GetModuleFileNameA +++ mfna: C:\Eigene Dateien\WineCommandLine\CMDLINE.exe +++ argc & argv +++ argc: 1 argv #0: C:\Eigene Dateien\WineCommandLine\CMDLINE.exe ======================================================= ============ WIN98: FROM SHELL, IN .exe DIR =========== C:\Eigene Dateien\WineCommandLine>cmdline +++ GetCommandLineA +++ C:\EIGENE~1\WINECO~1\CMDLINE.EXE +++ GetModuleFileNameA +++ mfna: C:\EIGENE DATEIEN\WINECOMMANDLINE\CMDLINE.EXE +++ argc & argv +++ argc: 1 argv #0: C:\EIGENE~1\WINECO~1\CMDLINE.EXE ======================================================= ============ WINE: FROM SHELL, IN .exe DIR ============ merlin(a)Merlin:~/.wine/fake_windows/Eigene Dateien/WineCommandLine> wine cmdline +++ GetCommandLineA +++ cmdline +++ GetModuleFileNameA +++ mfna: C:\Eigene Dateien\WineCommandLine\CMDLINE.exe +++ argc & argv +++ argc: 1 argv #0: cmdline ======================================================= ========== WINNT4.0: FROM SHELL, IN .exe DIR ========== C:\Eigene Dateien\WineCommandLine>cmdline +++ GetCommandLineA +++ cmdline +++ GetModuleFileNameA +++ mfna: C:\Eigene Dateien\WineCommandLine\CMDLINE.exe +++ argc & argv +++ argc: 1 argv #0: cmdline ======================================================= ========== WIN98: FROM SHELL, NOT IN .exe DIR ========= C:\Eigene Dateien>winecommandline\cmdline +++ GetCommandLineA +++ C:\EIGENE~1\WINECO~1\CMDLINE.EXE +++ GetModuleFileNameA +++ mfna: C:\EIGENE DATEIEN\WINECOMMANDLINE\CMDLINE.EXE +++ argc & argv +++ argc: 1 argv #0: C:\EIGENE~1\WINECO~1\CMDLINE.EXE ======================================================= =========== WINE: FROM SHELL, NOT IN .exe DIR ========= merlin(a)Merlin:~/.wine/fake_windows/Eigene Dateien> wine winecommandline/cmdline +++ GetCommandLineA +++ winecommandline/cmdline +++ GetModuleFileNameA +++ mfna: C:\Eigene Dateien\WineCommandLine\CMDLINE.exe +++ argc & argv +++ argc: 1 argv #0: winecommandline/cmdline ======================================================= ========= WINNT4.0: FROM SHELL, NOT IN .exe DIR ======= C:\Eigene Dateien>winecommandline\cmdline +++ GetCommandLineA +++ winecommandline\cmdline +++ GetModuleFileNameA +++ mfna: C:\Eigene Dateien\winecommandline\CMDLINE.exe +++ argc & argv +++ argc: 1 argv #0: winecommandline\cmdline ======================================================= ============= WIN98: FROM SHELL, FULL PATH ============ C:\Eigene Dateien>"c:\eigene dateien\winecommandline\cmdline" +++ GetCommandLineA +++ C:\EIGENE~1\WINECO~1\CMDLINE.EXE +++ GetModuleFileNameA +++ mfna: C:\EIGENE DATEIEN\WINECOMMANDLINE\CMDLINE.EXE +++ argc & argv +++ argc: 1 argv #0: C:\EIGENE~1\WINECO~1\CMDLINE.EXE C:\Eigene Dateien>"c:/eigene dateien/winecommandline/cmdline" Befehl oder Dateiname nicht gefunden C:\Eigene Dateien> ======================================================= ============== WINE: FROM SHELL, FULL PATH ============ merlin(a)Merlin:~/.wine/fake_windows/Eigene Dateien> wine "c:\\eigene dateien\\winecommandline\\cmdline" +++ GetCommandLineA +++ "c:\eigene dateien\winecommandline\cmdline" +++ GetModuleFileNameA +++ mfna: C:\Eigene Dateien\WineCommandLine\CMDLINE.exe +++ argc & argv +++ argc: 1 argv #0: c:\eigene dateien\winecommandline\cmdline merlin(a)Merlin:~/.wine/fake_windows/Eigene Dateien/WineCommandLine> wine "c:/eigene dateien/winecommandline/cmdline" +++ GetCommandLineA +++ "c:/eigene dateien/winecommandline/cmdline" +++ GetModuleFileNameA +++ mfna: C:\Eigene Dateien\WineCommandLine\CMDLINE.exe +++ argc & argv +++ argc: 1 argv #0: c:/eigene dateien/winecommandline/cmdline ======================================================= ============ WINNT4.0: FROM SHELL, FULL PATH ========== C:\Eigene Dateien>"c:\eigene dateien\winecommandline\cmdline" +++ GetCommandLineA +++ "c:\eigene dateien\winecommandline\cmdline" +++ GetModuleFileNameA +++ mfna: c:\eigene dateien\winecommandline\CMDLINE.exe +++ argc & argv +++ argc: 1 argv #0: c:\eigene dateien\winecommandline\cmdline C:\Eigene Dateien>"c:/eigene dateien/winecommandline/cmdline" +++ GetCommandLineA +++ "c:/eigene dateien/winecommandline/cmdline" +++ GetModuleFileNameA +++ mfna: c:\eigene dateien\winecommandline\CMDLINE.exe +++ argc & argv +++ argc: 1 argv #0: c:/eigene dateien/winecommandline/cmdline ======================================================= ============ WIN98: FROM BATCH, IN .exe DIR =========== C:\Eigene Dateien\WineCommandLine>batch C:\Eigene Dateien\WineCommandLine>echo batch batch C:\Eigene Dateien\WineCommandLine>cmdline +++ GetCommandLineA +++ C:\EIGENE~1\WINECO~1\CMDLINE.EXE +++ GetModuleFileNameA +++ mfna: C:\EIGENE DATEIEN\WINECOMMANDLINE\CMDLINE.EXE +++ argc & argv +++ argc: 1 argv #0: C:\EIGENE~1\WINECO~1\CMDLINE.EXE ======================================================= ============= WINE: FROM BATCH, IN .exe DIR =========== merlin(a)Merlin:~/.wine/fake_windows/Eigene Dateien/WineCommandLine> wine batch wine: cannot find 'batch' merlin(a)Merlin:~/.wine/fake_windows/Eigene Dateien/WineCommandLine> wine batch.bat wine: cannot determine executable type for L"C:\\Eigene Dateien\\WineCommandLine\\batch.bat" ======================================================= =========== WINNT4.0: FROM BATCH, IN .exe DIR ========= C:\Eigene Dateien\WineCommandLine>batch C:\Eigene Dateien\WineCommandLine>echo batch batch C:\Eigene Dateien\WineCommandLine>cmdline +++ GetCommandLineA +++ cmdline +++ GetModuleFileNameA +++ mfna: C:\Eigene Dateien\WineCommandLine\CMDLINE.exe +++ argc & argv +++ argc: 1 argv #0: cmdline ======================================================= ========== WIN98: FROM BATCH, NOT IN .exe DIR ========= C:\Eigene Dateien>winecommandline\batch C:\Eigene Dateien>echo winecommandline\batch winecommandline\batch C:\Eigene Dateien>cmdline Befehl oder Dateiname nicht gefunden. ======================================================= =========== WINE: FROM BATCH, NOT IN .exe DIR ========= merlin(a)Merlin:~/.wine/fake_windows/Eigene Dateien> wine WineCommandLine/batch wine: cannot find 'WineCommandLine/batch' merlin(a)Merlin:~/.wine/fake_windows/Eigene Dateien> wine winecommandline/batch.bat wine: cannot determine executable type for L"C:\\Eigene Dateien\\WineCommandLine\\batch.bat" ======================================================= ========= WINNT4.0: FROM BATCH, NOT IN .exe DIR ======= C:\Eigene Dateien>winecommandline\batch C:\Eigene Dateien>echo winecommandline\batch winecommandline\batch C:\Eigene Dateien>cmdline Der Befehl ist entweder falsch geschrieben oder konnte nicht gefunden werden. Bitte überprüfen Sie die Schreibweise und die Umgebungsvariable 'PATH'. ======================================================= ============ WIN98: FROM BATCH, BY EXPLORER =========== C:\Eigene Dateien\WineCommandLine>echo C:\EIGENE~1\WINECO~1\BATCH.BAT C:\EIGENE~1\WINECO~1\BATCH.BAT C:\Eigene Dateien\WineCommandLine>cmdline +++ GetCommandLineA +++ C:\EIGENE~1\WINECO~1\CMDLINE.EXE +++ GetModuleFileNameA +++ mfna: C:\EIGENE DATEIEN\WINECOMMANDLINE\CMDLINE.EXE +++ argc & argv +++ argc: 1 argv #0: C:\EIGENE~1\WINECO~1\CMDLINE.EXE ======================================================= ============= WINE: FROM BATCH, BY EXPLORER =========== (not applicable) ======================================================= =========== WINNT4.0: FROM BATCH, BY EXPLORER ========= C:\Eigene Dateien\WineCommandLine>echo "C:\Eigene Dateien\WineCommandLine\batch. bat" "C:\Eigene Dateien\WineCommandLine\batch.bat" C:\Eigene Dateien\WineCommandLine>cmdline +++ GetCommandLineA +++ cmdline +++ GetModuleFileNameA +++ mfna: C:\Eigene Dateien\WineCommandLine\CMDLINE.exe +++ argc & argv +++ argc: 1 argv #0: cmdline =======================================================

2 3

Re: PATCH: install more programs
by Alexandre Julliard Jan. 23, 2004

Jan. 23, 2004

Marcus Meissner <meissner(a)suse.de> writes: > I think we can install those safely. > > Ciao, Marcus > > Changelog: > Install rundll32,winemenubuilder and winevdm into the system. Why do you need these? They are not really supposed to be started directly by the user. -- Alexandre Julliard julliard(a)winehq.com

1 0

Re: Wine release 20040121
by Boaz Harrosh Jan. 23, 2004

Jan. 23, 2004

Alexandre Julliard wrote: > - Better support for constructors in C++ Winelib apps. > > I follow the wine mailing list every work day. I even went back on these messages I did not read. I cannot find that patch. Alexandre Please? Elaborate a little about that fix. What do we do now? Just remove the wrapper and run? nothing to do in the Makefiles? Please also explain in a few words the technology behind it. (GCC that is). Free Life Boaz

3 3