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

Re: New win api docs

by tom

Dmitry Timoshkov wrote: >"Michael Stefaniuc" <mstefani(a)redhat.de> wrote: > > > >>here is the documentation for the API's that m$ had to disclose after >>the settlement: >>http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnapiover/… >> >> > >And nothing regarding undocumented comctl32 interfaces... > >Almost all disclosed APIs are already known or useless. > > > Yea here is a nice link : http://www.theregister.co.uk/content/4/26803.html It tell's the real story about the API documentation ;-) Tom

Aug. 28, 2002

Re: Wine Status

by Jas Sandys-Lumsdaine

I'm completely new to the Wine project mailing list - but I noticed on the status page mentioned below there's a section for "CPU Emulation" which has "No serious efforts yet". Is there some plan to integrate bochs (or some other) x86 emulator into WINE so WINE can be run on non-x86 platforms. I realise this is very non-critical to 1.0 release! Just interested. Jas. >The Wine Status page located here : >http://www.winehq.com/about/index.php?status >Has gone for about one year now with out updates and I

Aug. 28, 2002

BreakOnDllLoad crashes Wine

by Fabian Cenedese

Hi I set the registry setting BreakOnDllLoad to 1 to find a problem in the DllMain function of my dll. Like that WineDbg stops first while loading NTDll.dll. After continuing with c it stops again at Kernel32.dll. If I try now to continue with c I get an "illegal instruction in 32-bit code" and I can't continue. Without the registry setting it starts up without a problem. Has anyone else had this problem? (WinNT4, Wine-20020804, all dlls builtin) WineDbg starting on pid 81433c8 Loaded debug information from ELF 'wine' (0x00000000) Breakpoint 2 at 0x4000c714 (_end+0x37fbefec) Loaded debug information from ELF '/usr/local/lib/libntdll.dll.so' (0x4002b000) Loaded debug information from ELF '/usr/local/lib/libwine.so' (0x40125000) Loaded debug information from ELF '/usr/local/lib/libwine_unicode.so' (0x4013d000) No debug information in ELF '/lib/libm.so.6' (0x40207000) No debug information in ELF '/lib/libc.so.6' (0x4022b000) No debug information in ELF '/lib/libdl.so.2' (0x40353000) No debug information in ELF '/lib/ld-linux.so.2' (0x40000000) Loaded debug information from 32bit DLL 'C:\imd\Bin\ImdD.exe' (0x18000000) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\NTDLL.DLL' (0x40063000) Stopping on DLL C:\WINDOWS\SYSTEM\NTDLL.DLL loading at 40063000 Wine-dbg>c No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\KERNEL32.DLL' (0x4084b000) Stopping on DLL C:\WINDOWS\SYSTEM\KERNEL32.DLL loading at 4084b000 Wine-dbg>c First chance exception: illegal instruction in 32-bit code (0xbffff3d6). In 32-bit mode. Register dump: CS:0023 SS:002b DS:002b ES:002b FS:008f GS:0000 EIP:bffff3d6 ESP:405c65d0 EBP:bffff3c4 EFLAGS:00010243( R- 00 I Z- - 1C) EAX:4001600c EBX:40015a60 ECX:bffff3c4 EDX:4001600c ESI:40016004 EDI:4001600c Stack dump: 0x405c65d0 (NTDLL.DLL.sscanf+0x33dd10): 4034db98 00000008 080501b8 40000660 0x405c65e0 (NTDLL.DLL.sscanf+0x33dd20): 405c6668 4000bcd0 00000003 bffff3c4 0x405c65f0 (NTDLL.DLL.sscanf+0x33dd30): 00000003 080501b8 405c6668 4032b6b1 0x405c6600 (NTDLL.DLL.sscanf+0x33dd40): bffff3d4 08050354 00000000 00000000 0x405c6610 (NTDLL.DLL.sscanf+0x33dd50): 40015a60 00000000 08050108 00009052 0x405c6620 (NTDLL.DLL.sscanf+0x33dd60): 4022a000 00000000 00000000 00000000 0x405c6630 (NTDLL.DLL.sscanf+0x33dd70): 0011: sel=008f base=401225c0 limit=00000fff 32-bit rw- Backtrace: =>0 0xbffff3d6 (KERNEL32.DLL.TryEnterCriticalSection+0x7f77005a) (ebp=bffff3c4) 1 0xbffff58f (KERNEL32.DLL.TryEnterCriticalSection+0x7f770213) (ebp=bffff57b) 2 0x636f6c2f (KERNEL32.DLL.TryEnterCriticalSection+0x22e678b3) (ebp=7273752f) 0xbffff3d6 (KERNEL32.DLL.TryEnterCriticalSection+0x7f77005a): Wine-dbg>c Unhandled exception: illegal instruction in 32-bit code (0xbffff3d6). Register dump: CS:0023 SS:002b DS:002b ES:002b FS:008f GS:0000 EIP:bffff3d6 ESP:405c65d0 EBP:bffff3c4 EFLAGS:00010243( R- 00 I Z- - 1C) EAX:4001600c EBX:40015a60 ECX:bffff3c4 EDX:4001600c ESI:40016004 EDI:4001600c Stack dump: 0x405c65d0 (NTDLL.DLL.sscanf+0x33dd10): 4034db98 00000008 080501b8 40000660 0x405c65e0 (NTDLL.DLL.sscanf+0x33dd20): 405c6668 4000bcd0 00000003 bffff3c4 0x405c65f0 (NTDLL.DLL.sscanf+0x33dd30): 00000003 080501b8 405c6668 4032b6b1 0x405c6600 (NTDLL.DLL.sscanf+0x33dd40): bffff3d4 08050354 00000000 00000000 0x405c6610 (NTDLL.DLL.sscanf+0x33dd50): 40015a60 00000000 08050108 00009052 0x405c6620 (NTDLL.DLL.sscanf+0x33dd60): 4022a000 00000000 00000000 00000000 0x405c6630 (NTDLL.DLL.sscanf+0x33dd70): 0011: sel=008f base=401225c0 limit=00000fff 32-bit rw- Backtrace: =>0 0xbffff3d6 (KERNEL32.DLL.TryEnterCriticalSection+0x7f77005a) (ebp=bffff3c4) 1 0xbffff58f (KERNEL32.DLL.TryEnterCriticalSection+0x7f770213) (ebp=bffff57b) 2 0x636f6c2f (KERNEL32.DLL.TryEnterCriticalSection+0x22e678b3) (ebp=7273752f) 0xbffff3d6 (KERNEL32.DLL.TryEnterCriticalSection+0x7f77005a): Wine-dbg>c Invalid address for breakpoint 1, disabling it Invalid address for breakpoint 2, disabling it Process of pid=081433c8 has terminated Thanks Fabi

Aug. 28, 2002

Re: New win api docs

by Dmitry Timoshkov

"Michael Stefaniuc" <mstefani(a)redhat.de> wrote: > here is the documentation for the API's that m$ had to disclose after > the settlement: > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnapiover/… And nothing regarding undocumented comctl32 interfaces... Almost all disclosed APIs are already known or useless. -- Dmitry.

Aug. 28, 2002

New win api docs

by Michael Stefaniuc

Hello, here is the documentation for the API's that m$ had to disclose after the settlement: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnapiover/… bye michael -- Michael Stefaniuc Tel.: +49-711-96437-199 System Administration Fax.: +49-711-96437-111 Red Hat GmbH Email: mstefani(a)redhat.com Hauptstaetterstr. 58 http://www.redhat.de/ D-70178 Stuttgart

Aug. 28, 2002

Re: [Help] Handwriting input?

by leanne

When I found that it got: switch (event->type) { case SelectionNotify: /* all of these should be caught by XCheckTypedWindowEvent() */ FIXME("Got SelectionNotify - must not happen!\n"); Handwriting is through clipboard, where I could get more information about clipboard mechanism of X and WINE? Very thanks. leanne wrote: > Dear all, > > Does WINE support hand-writing input? > I got a software and use mouse for input, here is my error: > > > err:clipping:CLIPPING_UpdateGCRegion DC is dirty. Please report this. > err:clipping:CLIPPING_UpdateGCRegion DC is dirty. Please report this. > > Any idea? > > Thanks in advance. > Leanne > > >

Aug. 28, 2002

Re: RFC: 'test' bugzilla keyword

by Francois Gouget

On Tue, 27 Aug 2002, Paul Millar wrote: [...] > > Maybe 'conformance' would work? > > Personally, I prefer "regression" to "conformance", although both are > applicable names. The problem is we already have a 'regression' keyword with a reasonable meaning: 'bugs relating to programs that were working at one time but stoped working for some reason'. But this does not specifically cover the 'conformance test suite'. If a conformance test used to work and no longer does, then I think it would be reasonable to tag it as 'conformance, regression'. But I have also found that some tests do not pass on Windows. IIRC, there's a test having to do with TEMP that fails if it is set to 'c:\Windows\Temp' rather than 'c:\'. I would like to be able to make a bug report and tag it with a keyword to indicate it is related to the 'conformance test suite' (or whatever we want to call it). Similarly, there would be reports to be made about the conformance tests as run on FreeBSD and Solaris. And note that none of these are regressions. -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ 1 + e ^ ( i * pi ) = 0

Aug. 28, 2002

Re: Patch to restore iconified window

by Alexandre Julliard

Duane Clark <dclark(a)akamail.com> writes: > Unlike most other apps, when iconified fpga_editor triggers > X11DRV_ShowWindow() with a cmd==SW_HIDE, to hide the window. When > X11DRV_MapNotify() was subsequently called, it did nothing because > WS_VISIBLE was not set. This patch fixes that. > > I've been using this patch with everything I run for about 5 months now. > > Log message: > Fix restoring of windows that were iconified with SW_HIDE. Well, SW_HIDE is supposed to hide the window, not iconify it, so we are not supposed to get a MapNotify at this point. What is probably missing is proper handling for hiding an iconified window. -- Alexandre Julliard julliard(a)winehq.com

Aug. 27, 2002

Re: RFC: 'test' bugzilla keyword

by Paul Millar

Hi everyone, A few thoughts ... although the bits about winelib should be taken with a pinch of salt: I've never used winelib in anger. Personally, I don't like the keyword "test". Its far too ambiguous. On Tue, 27 Aug 2002, Francois Gouget wrote: > Maybe 'conformance' would work? Personally, I prefer "regression" to "conformance", although both are applicable names. Yes, the tests are checking that wine _conforms_ to what we've specified (via the tests) as correct windows behaviour, but equally if a test fails then wine has _regressed_ to a more primitive (and therefore less useful) state. I think most people would think of "regression testing" as an automated process: a suite of many (usually short) tests all of which which must pass. This is just "make testclean && make test || echo Regression found" :) The problem (in terms of nomenclature) is that wine (as opposed to winelib) runs applications. So a regression is also when an application doesn't behave as well as it did. (This is in the docs as what we mean by "regression".) But, from another point-of-view, running an application is just another test. Its a test that checks _lots_ of different aspects of wine. Perhaps another possibility worth considering is winelib: whether test applications continue to build correctly. If something were to interfere with winelib (perhaps subtle enough not to affect wine running of native applications), then a different type of regression has been introduced. So I'd say we have possibility of regressions in: 1. core Windows functionality - currently tested by many "little" tests: an automated process. 2. running native applications - tested by people using wine and complaining when something breaks. 3. winelib infrastructure - tested by building tools? People complaining? If we cannot sub-categorise "regression" in bugzilla, how about implicitly subgrouping. For example, calling them something like: regression-automated regression-application regression-winelib Alternatively, we could have the "regression" keyword and also the "application", "winelib", "automated" keywords. The bug-reporter adds whatever s/he feels best describes their bug. Cheers, Paul. ---- Paul Millar

Aug. 27, 2002

Re: Wine Ma os X port

by Francois Gouget

On Tue, 27 Aug 2002, Fausto Saporito wrote: > Hello, > > i'm completely a newbie, but should be possible merge bochs code in > order to emulate an x86 cpu in wine? > The MacOS port of Bochs is quite operative. Trying to run an x86 Windows application inside a non-x86 Wine(lib) environment is going to be a nightmare. If you want to run Wine (i.e. the binary emulator) on non-x86 architectures, the best approach is to run the Windows application and Wine-x86 in an x86 emulator. If your emulator is fast enough to run the Windows application with a reasonable performance, then it should be fast enough to run Wine-x86 too. -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ Good judgment comes from experience, and experience comes from bad judgment -- Barry LePatner

Aug. 27, 2002