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

Noteworthy Composer under WineDbg
by Andrew Neil Ramage March 12, 2005

March 12, 2005

I have been unable to find the reason Wine MIDI Mapper does not open properly. The trace below shows the output from winedbg with WINDEBUG set to +all. I hope someone can tell me what is going on. Andrew [andrew(a)zeus Default]$ set WINEDEBUG=+all [andrew(a)zeus Default]$ winedbg ~/.wine/drive_c/"Program Files"/"NoteWorthy Composer"/NWC32.EXE WineDbg starting on pid 0xa In 32 bit mode. 0x404d7dbf start_process+0xcf [/home/andrew/Download/Software/wine-20050211/dlls/kernel/../../include/winternl.h:1356] in kernel32: jmp 0x404d7db5 start_process+0xc5 [/home/andrew/Download/Software/wine-20050211/dlls/kernel/process.c:1046] in kernel32 1356 static inline void WINAPI DbgBreakPoint(void) { __asm__ __volatile__("int3"); } Wine-dbg>next 1046 ExitProcess( entry( peb ) ); Wine-dbg>next err:thunk:_loadthunk (NWMID95B.DLT, thunkobj_ThunkData16, NWMID95B.DLL): Unable to load 'NWMID95B.DLT', error 2 fixme:commdlg:PRINTDLG_OpenDefaultPrinter Could not open printer EPSONStylusC42?! fixme:mmtime:timeBeginPeriod Stub; we set our timer resolution at minimum fixme:mmtime:timeEndPeriod Stub; we set our timer resolution at minimum Invalid address (0x404d7db8) for breakpoint 0, disabling it Process of pid=0x0000000a has terminated Wine-dbg>quit WineDbg terminated on pid 0xa [andrew(a)zeus Default]$ -- Andrew [hackcoughsniffle] Internal Virus Database corrupt

2 2

wine 20050310
by Kevin DeKorte March 12, 2005

March 12, 2005

The latest wine still has issues with Notes 6.51 that started in the 20050111 release. Basically if you open Notes and click on one of the bookmarks on the bookmark bar on the left, wine will consume all the CPU. Killing wineserver and wine-preload returns the machine to normal. Wine 20041201 works fine. Kevin

4 3

Response from NoteWorthy
by Andrew Neil Ramage March 12, 2005

March 12, 2005

I wrote NoteWorthy support about the problem of opening the MIDI mapper. Here is their response. Hi: >My question is how do you detect the MIDI mappers ? The MIDI Mapper actually has a hard coded device ID on Windows. There is no need to detect it. Any other device listed in Tools, Options, Midi, "Available play devices" are detected using the multi-media subsystem. Regards, Eric, http://noteworthysoftware.com -- Andrew [hackcoughsniffle] Internal Virus Database corrupt

1 0

Re: Wine release 20050310 (2/2) and (1/2)
by Brian March 12, 2005

March 12, 2005

Hi Julliard, Your last two emails, Wine release 20050310 (1/2) and Wine release 20050310 (2/2), were received with no text and only an attachment with no file extension. Regards, Brian Alexandre Julliard wrote: -- OpenOffice Suite 1.1.4 : Firefox Browser 1.0.1 : Thunderbird Email 1.0

1 0

Fw: wine 20050310
by Paul R Streitman March 12, 2005

March 12, 2005

Seconded. No remarkable messages, etc. winedbg does not show anything unusual either - Notes just 'hangs' consuming the CPU. I would be happy to run any kind of test/trace to help debug this problem. The failure will also happen if you do not click one of the bookmarks on the left, it just takes longer before it happens. Paul z/OS core components development Internet: prs(a)us.ibm.com ----- Forwarded by Paul R Streitman/Poughkeepsie/IBM on 03/11/2005 07:46 PM ----- Kevin DeKorte <kdekorte(a)yahoo.c om> To Sent by: "wine-devel(a)winehq.com" wine-devel-admin@ <wine-devel(a)winehq.com> winehq.org cc Subject 03/11/2005 05:49 wine 20050310 PM The latest wine still has issues with Notes 6.51 that started in the 20050111 release. Basically if you open Notes and click on one of the bookmarks on the bookmark bar on the left, wine will consume all the CPU. Killing wineserver and wine-preload returns the machine to normal. Wine 20041201 works fine. Kevin (See attached file: attg49w2.dat)

1 0

Re: New uninstaller
by Dmitry Timoshkov March 12, 2005

March 12, 2005

"Jonathan Ernst" <Jonathan(a)ErnstFamily.ch> wrote: > With some help I'll be able to improve it (more unicodification, etc.) > when I'll come back. You can't really convert to unicode partially, you have to do it in one go. That not only will simplify things a lot, but also will save you a lot of time. > + for (i=0; i < numentries; i++) > + { > + len = WideCharToMultiByte(CP_UNIXCP, 0, entries[i].descr, -1, NULL, 0, NULL, NULL); > + descr = HeapAlloc(GetProcessHeap(), 0, len * sizeof(WCHAR)); > + WideCharToMultiByte(CP_UNIXCP, 0, entries[i].descr, -1, descr, len, NULL, NULL); > + printf("%s|||%s\n", entries[i].key, descr); There is no need to allocate len * sizeof(WCHAR) bytes, len works just fine. > +int wmain(int argc, char *argv[]) wmain takes 'WCHAR *argv[]' list. All remaining problems are caused by the fact that now argv[] array is passed in unicode but you still handle argv[] strings as ASCII and pass them around to internal functions which accept 'char *' not 'WCHAR *' strings. -- Dmitry.

5 15

Re: cabinet.dll FDI Conformance Test
by Dimitrie O. Paun March 11, 2005

March 11, 2005

On Fri, Mar 11, 2005 at 12:13:18AM -0800, Rizwan Kassim wrote: > Wine cabinet.dll FDI Conformance Test Patch A few comments: -- the patches uses Windows line ends, please fix that -- the preprocessor is abused. There's no need to have #ifdef VERBOSE #endif all over the code, please pull that into the trace() function -- the STANDALONE business should also go, there's no need for it in Wine. -- Dimi.

1 0

Re: add version info to the reg
by Vincent Béron March 11, 2005

March 11, 2005

Le jeu 10/03/2005 à 17:50, Ivan Leo Puoti a écrit : > lamest patch I've ever sent, but it wasn't my idea. > > ChangeLog: > Add hardcoded version info to the registry. > > Ivan. > ---- > > --- wine/tools/wine.inf 2005-01-08 09:32:29.000000000 +0100 > +++ new/tools/wine.inf 2005-03-10 23:19:01.589998042 +0100 > @@ -108,6 +108,8 @@ > HKLM,%CurrentVersion%,"ProgramFilesDir",,"%16422%" > HKLM,%CurrentVersion%,"RegisteredOrganization",,"Change preferred organization in ~/.wine/system.reg" > HKLM,%CurrentVersion%,"RegisteredOwner",,"Change preferred owner in ~/.wine/system.reg" > +HKLM,%CurrentVersion%,"CSDVersion",,"Service Pack 4" > +HKLM,%CurrentVersion%,"CurrentVersion",,"5.0" > HKLM,%CurrentVersion%\Setup,"BootDir",,"%30%" > HKLM,%CurrentVersion%\Setup,"SharedDir",,"%25%" > HKLM,Software\Microsoft\Windows NT\CurrentVersion\Fonts,,,"" This doesn't look like the right place to put it, especially since Wine can be set to something else than Win2k. That doesn't mean I know where to put it... Vincent

3 2

Re: Make running tests on a visible desktop a mandatory requirement
by Paul Vriens March 11, 2005

March 11, 2005

On Thu, 2005-03-10 at 17:06, Dmitry Timoshkov wrote: > "Paul Vriens" <Paul.Vriens(a)xs4all.nl> wrote: > > > Apart from the fact whether winrash should be 'fixed' or not, this patch > > doesn't seem to do what it is supposed to do. Put in other words the > > running_on_visible_desktop is not correct (enough). > > Apparently that's because desktop window is completely covered by the Progman > window and SysListView32. I'm very sorry for the breakage. > > Here is a patch that hopefully should finally work for all systems. It's based > on the article pointed out by Robert Shearman. > > Changelog: > Dmitry Timoshkov <dmitry(a)codeweavers.com> > Implement a test for the desktop visibility based on the MSDN article > pointed out by Robert Shearman. Hi, someting is wrong with pulling the latest winetest (with winrash) but that's another issue. When running the latest winetest from Paul' page, I get on my win98 box: C:\WINDOWS\Desktop>C:\WINDOWS\DESKTOP\WINETE~1.EXE Assertion failed: pGetUserObjectInformationA(wstation, UOI_FLAGS, &uoflags, size of(uoflags), &len), file /home/paul/Production/wine-cross-source/programs/winete st/main.c, line 82 abnormal program termination This doesn't seem right ;-) Paul.

1 0

Re: Wine & Valgrind 2.2.0
by Oliver Stieber March 11, 2005

March 11, 2005

--- Lars Segerlund <lars.segerlund(a)comsys.se> wrote: > > Hi, > > Has anybody given prospect & oprofile a spin ? > > My machine is a bit to slow for a build of the > latest wine, but I figured it could be a nice way to > check systemusage in conjunction with wine. > > Opinions ? I've oprofiled the DirectX 9 work, but it's not so usefull their since most of the dogs work is performed in the openGL driver. No problems profiling though, there's a WWN artical about it. http://www.winehq.org/?issue=249#oprofile & Wine > > / regards, Lars Segerlund. > > > On Fri, 11 Mar 2005 17:40:25 +0200 (EET) > Saulius Krasuckas <saulius2(a)ar.fi.lt> wrote: > > > On Fri, 11 Mar 2005, James Hawkins wrote: > > > On Fri, 11 Mar 2005 17:12:35 +0200 (EET), > Saulius Krasuckas <saulius2(a)ar.fi.lt> wrote: > > > > On Wed, 9 Mar 2005, Robert Shearman wrote: > > > > > I find the --tool=memcheck option the most > useful, which can be used for > > > > > finding the source of memory corruption. > > > > > > > > Fine, but can you help me to fight an error > saying "SEGMENT MAPS NOT OK" ? > > > > I try running 'wine Diablo.exe' and get > something like that: > > > > > > > > | INV 2 FAILED: seg 0x1C490000-0x1C492000 > crosses boundaries of mapping 0x1C490000-0x1C491000 > > > > | INV 1 FAILED: seg -0x1C490000 does not end > at mapping 0x1C492000-0x1C490000 end > > > > | INV 1 FAILED: mapping 0x1C491000-0x1C492000 > (prot=rwx file=/usr/local/lib/wine/ole32.dll.so) is > before 0x1C492000-0x1C498000 > > ... > > > > And then valgrind terminates. Where is the > problem? Something is wrong > > > > with the ole32.dll.so file? > > > > > > Try running valgrind with wine-pthread or > wine-kthread instead of > > > wine, because valgrind doesn't run child > processes in it's vm. > > > > Yes, I already am running that way (wine-pthread). > W/o wine-pthread name > > or w/o --trace-children=yes option supplied I > capture nothing usefull. > > > > And BTW, wine under valgrind runs slowly now. > AFAICS, a lot more slowly > > than the stable v2.2.0. > > > > > > Send instant messages to your online friends http://uk.messenger.yahoo.com

1 0