July 2005 - Wine-Devel - list.winehq.org

Re: LoadString problems

by James Hawkins

On 7/30/05, Hans Leidekker <hans(a)it.vu.nl> wrote: > On Saturday 30 July 2005 09:06, James Hawkins wrote: > > > LoadStringA(NULL, IDS_CONTENTS, text, MAX_PATH); > > MSDN documents the use of GetModuleHandle(NULL) as the first > argument to LoadString to get resource strings from the current > module. Maybe passing NULL is an undocumented synonym for it that > Wine doesn't implement? yet? > Actuall wine implements that feature, but it doesn't help because calling LoadString(GetModuleHandle(NULL)...) doesn't work either. What I'll end up doing is saving a global hhctrl hinstance in DllMain and using that, though it confuses me why GetModuleHandle(NULL) doesn't work. Maybe that only returns the hinstance of the process calling the module, and not the hinstance of the module itself. -- James Hawkins

July 30, 2005

Re: Benchmark's on the Wiki

by Mitchell Mebane

Tom Wickline wrote: >On 7/30/05, Felix Nawothnig <felix.nawothnig(a)t-online.de> wrote: > > >>Tom Wickline wrote: >> >> >>>I'm not finished, but I thought I would ask if this going in the right >>>direction? >>>http://wiki.winehq.org/BenchMark >>> >>> >>Much better, although Windows should really be on the left side. >> >> > >Why? its Wine against XP ... not XP against Wine. >But ill change it if others think it would be best :-) > >Tom > > > >>Felix >> >> >> > > > >. > > > Yes, in this case XP is the reference platform, so it should be on the left. Also, you could change the title of the comparison column to "Wine Difference" or some such. --Mitchell -- I find that a great part of the information I have was acquired by looking up something and finding something else on the way. -- Franklin P. Adams

July 30, 2005

Re: Benchmark's on the Wiki

by Felix Nawothnig

Tom Wickline wrote: >>>I'm not finished, but I thought I would ask if this going in the right >>>direction? >>>http://wiki.winehq.org/BenchMark >>Much better, although Windows should really be on the left side. > Why? its Wine against XP ... not XP against Wine. Maybe it's just me (no it's not, someone else in this thread also suggested it ;) but when I looked at it I really expected XP being on the left side. This is probably caused by the third column - a green +42% looks like the expected increase when switching from Windows to Wine for me. Another explanation would be that we are reimplementing the Windows API - first there was Windows, then Wine was written. I'd also like to note that this (Windows, Wine) is the same order as used on test.winehq.com: 95,98,ME => NT3,NT4,2K,XP,2K3 => Wine (consider that this chronology is in terms of popularity with the families grouped afterwards). It also implies that Wine will take over the world one day. :-) Felix

July 30, 2005

Re: Benchmark's on the Wiki

by Tom Wickline

On 7/30/05, Felix Nawothnig <felix.nawothnig(a)t-online.de> wrote: > Tom Wickline wrote: > > I'm not finished, but I thought I would ask if this going in the right > > direction? > > http://wiki.winehq.org/BenchMark > > Much better, although Windows should really be on the left side. Why? its Wine against XP ... not XP against Wine. But ill change it if others think it would be best :-) Tom > > Felix >

July 30, 2005

Re: Benchmark's on the Wiki

by Felix Nawothnig

Tom Wickline wrote: > I'm not finished, but I thought I would ask if this going in the right > direction? > http://wiki.winehq.org/BenchMark Much better, although Windows should really be on the left side. Felix

July 30, 2005

Re: wine/dlls/ntdll loadorder.c

by Rein Klazes

On 28 Jul 2005 11:46:46 +0200, you wrote: > Rein Klazes <wijn(a)wanadoo.nl> writes: > > > | trace:module:load_dll looking for L"comm.dll" in L"E:\\bin\\gt3\\GTWin;.;d:\\win98\\system;d:\\WIN98;d:\\windows;d:\\windows\\system;h:\\shared;r:\\x86\\Setup" > > | trace:module:MODULE_GetLoadOrderW looking for L"E:\\bin\\gt3\\GTWin\\comm.dll" > > | trace:module:open_app_key searching L"E:\\bin\\gt3\\GTWin\\comm" in L"Software\\Wine\\AppDefaults\\girotel.exe\\DllOverrides" > > | trace:module:MODULE_GetLoadOrderW got hardcoded default "b,n" for L"E:\\bin\\gt3\\GTWin\\comm.dll" > > | trace:module:load_dll Trying built-in L"E:\\bin\\gt3\\GTWin\\comm.dll" > > | warn:module:load_dll Failed to load module L"comm.dll"; status=c000007b > > Are you sure you don't have an old symlink lying around? comm.drv > used to be named comm.dll, but it was renamed about 2 years ago. You are absolutely right, comm.dll.so was still existing in the local/lib/wine dir. From the date probably created during some regression testing recently. Rein.

July 30, 2005

Re: LoadString problems

by Frank Richter

On 30.07.2005 09:06, James Hawkins wrote: > TCITEMA tie; > char text[MAX_PATH]; > > LoadStringA(NULL, IDS_CONTENTS, text, MAX_PATH); > /* text should be '&Contents', but we get a GetLastError() */ Hm, wouldn't it be better use wide strings? -f.r.

July 30, 2005

Re: Benchmark's on the Wiki

by Tom Wickline

On 7/28/05, Dimi Paun <dimi(a)lattica.com> wrote: > > Wine XP Wine vs. Win > 3DMark Result (marks): 14,606 13,332 +10% > CPU Speed (CPU Marks): 786 650 +21% > ... > > I personally like the last one the best. I'm not finished, but I thought I would ask if this going in the right direction? http://wiki.winehq.org/BenchMark Tom > > -- > Dimi Paun <dimi(a)lattica.com> > Lattica, Inc. >

July 30, 2005

Re: LoadString problems

by Hans Leidekker

On Saturday 30 July 2005 09:06, James Hawkins wrote: > LoadStringA(NULL, IDS_CONTENTS, text, MAX_PATH); MSDN documents the use of GetModuleHandle(NULL) as the first argument to LoadString to get resource strings from the current module. Maybe passing NULL is an undocumented synonym for it that Wine doesn't implement? yet? -Hans

July 30, 2005

LoadString problems

by James Hawkins

Hey, I'm trying to load strings from the hhctrl.ocx resource file to use as the text for tabs and toolbar buttons, but I can't get it to work. I've tried to get LoadString to work a couple ways, but it just won't work for me. I've attached the resource files and Makefile.in. Maybe something is wrong with the way those are set up. The following code is one of the (failing) places where I call LoadString: TCITEMA tie; char text[MAX_PATH]; LoadStringA(NULL, IDS_CONTENTS, text, MAX_PATH); /* text should be '&Contents', but we get a GetLastError() */ tie.mask = TCIF_TEXT; tie.pszText = text; TabCtrl_InsertItemA(hwndTabCtrl, dwIndex, &tie); I should note that the code works when compiled with Visual Studio and run on Windows. -- James Hawkins

July 30, 2005