November 2003 - Wine-Devel - list.winehq.org

Re: copy protection - was: Re: Is it time for playing games on WINE?
by Ivan Leo Murray-Smith Nov. 4, 2003

Nov. 4, 2003

>but this brings fort the legal issues. If the re-implemented driver only allows the user to play the game, and not to make a perfect copy of the CD, there is no legal issue.

6 5

Re: copy protection - was: Re: Is it time for playing games on WINE?
by Ivan Leo Murray-Smith Nov. 4, 2003

Nov. 4, 2003

> When you play > using an incorrect crack the game will slowly become unplayable. Like this we can be sure that the reimplemented driver is perfect or a bit buggy. Also, some people may prefer the idea of a open source safe disc driver more that the idea of loading the proprietary one.

1 0

Wine lecture slides
by Shachar Shemesh Nov. 4, 2003

Nov. 4, 2003

Hi all, I have placed on my site the slides for a presentation I gave at a local LUG about Wine. The slides are in English, in PDF format. You can get them at http://shemesh.biz/lectures.html The lecture was given several months ago, but I'm going to repeat it in about a month. If you have any comments, please send them over for inclusion for next time. Shachar -- Shachar Shemesh Open Source integration consultant Home page & resume - http://www.shemesh.biz/

9 16

Re: Various CompareString fixes
by Alexandre Julliard Nov. 4, 2003

Nov. 4, 2003

Dmitry Timoshkov <dmitry(a)baikal.ru> writes: > Changelog: > Dmitry Timoshkov <dmitry(a)codeweavers.com> > Move CompareString implementation to libwine_unicode, > add a bunch of CompareString tests. This causes a lot of breakage in the shlwapi string tests. Some of these may well be because the shlwapi implementation depends on a broken CompareString, but others look suspicious. For instance the StrChrA test fails because CompareString says "-" and "'" are equal, that doesn't sound right at all. -- Alexandre Julliard julliard(a)winehq.com

2 1

wine/wine/dlls/ntdll.dll.so: undefined symbol: GetCurrentProcessId
by Karl Vogel Nov. 3, 2003

Nov. 3, 2003

Had to apply the following patch to be able to run the 20031016 cvs. Without this patch I always got the following error: wine: failed to initialize: wine/wine/dlls/ntdll.dll.so: undefined symbol: GetCurrentProcessId Am running on an NPTL platform (Fedora Core Beta3 v0.95) Index: dlls/ntdll/thread.c =================================================================== RCS file: /home/wine/wine/dlls/ntdll/thread.c,v retrieving revision 1.8 diff -u -r1.8 thread.c --- dlls/ntdll/thread.c 31 Oct 2003 00:16:20 -0000 1.8 +++ dlls/ntdll/thread.c 3 Nov 2003 20:08:09 -0000 @@ -27,6 +27,7 @@ #include "wine/library.h" #include "wine/server.h" #include "wine/debug.h" +#include "ntdll_misc.h" WINE_DEFAULT_DEBUG_CHANNEL(thread);

1 0

UI porting issues with odd shapped window
by Rob Nov. 3, 2003

Nov. 3, 2003

Second posting - original post somehow got attached to an existing unrelated thread, apologies... Hello All Again, We have found a work around for all our existing issues porting X-Lite so long as Jerry Jenkins's unincorporated WINE patch listed below is applied to Wine. I don't know why it's not incorporated yet, but without it our application has horrible issues (as do similar styled applications). We have spent time creating another test application with source to demonstrate UI issues that fail under Wine with unusual shaped windows, so you all can have a test application to work against to fix these issues at your leisure. We have worked around all of these issues in our application (with the unincorporated JJ patch) by using alternative APIs or use the APIs in a different manner. What are the chance's JJ's patch can be put into the main Wine CVS tree? Does anyone know what issues it breaks? All I can see is improvement (even though it's not a complete solution yet to all issues), hence my curiosity. This application demonstrates the issues we are having which will allow X-Lite to run under WINE. Find the demo application at: http://www.xten.com/files/winetest2.zip Some of the bugs are fixed by this *unincorporated* WINE patch by Jerry Jenkins: http://www.winehq.org/hypermail/wine-patches/2003/09/0268.html (hereafter called "the unincorporated JJ patch") - B1. Critical, but fixed by the unincorporated JJ patch. Focus does not appear to be on the application at startup. We do not receive keyboard messages, though we do receive many other messages, such as as mouse-clicks. Clicking on the square labelled "focus:" fixes the problem, by bringing up a message box -- when the message box is dismissed, the application has focus. This appears to be the same problem as that discussed here: http://bugs.winehq.org/show_bug.cgi?id=292 - B2. Critical, but fixed by the unincorporated JJ patch. No task bar item. - B3. Critical, but fixed by the unincorporated JJ patch. "System" commands do not appear to be working. Examples: - we do not receive WM_CLOSE when the user presses Alt+F4 - Alt+Space does not bring up the System menu - B4. Critical, but fixed by the unincorporated JJ patch. We are always on top, until a screen-saver kicks in. (Also can be fixed by simply removing WS_POPUP.) This appears to be the same problem as that discussed here: http://bugs.winehq.org/show_bug.cgi?id=1288 - B5. Not critical, as we have a work-around. The application window is supposed to have a non-rectangular shape. The shape is made by setting a "region" from a mask bitmap, and calling SetWindowRgn. The problem under Wine happens when converting the 2-bit color mask to a 24-bit color mask. The black 2-bit pixels are properly converted to black 24-bit pixels, but the white 2-bit pixels are converted to a near-black, rather than white. The sample app demonstrates 2 ways of working around the problem: method 1: fixes the problem by using a 16-color (4 bit per color) mask instead of a 2-color mask. This gets around the bug in a reasonable way. method 2: fixes the problem by using near-black (instead of white) for the "transparent" color. This exploits the bug and causes a bad (but correct) appearance on Windows. - B6. Fixed by latest CVS WINE release. Copy to the clipboard doesn't work (though pasting from the clipboard does work). - B7. Not critical, as we have a work-around. Attempting to bring up the right-click context menu causes the app to hang. - B8. Not critical, as we have a work-around. Unwanted caption. If an application without a caption shows itself, and *then* gives itself a funky shape by calling SetWindowRgn, the application will have a caption. If, however, the application calls setWindowRgn *before* showing itself, it will correctly not have a caption. The sample app demonstrates this, as well as demonstrating a fix for the problem. min. fix view: clicking on this square hides the window and then shows it again, which gets rid of the caption max. fix view: clicking on this square also fixes B5 (using method 1) and then hides and shows the window - B9. Not critical, as we have a work-around. Handling WM_NCHITTEST to move an app without a caption. Another example of such an app was the clock that shipped with older versions of Windows. (You've got to first turn off the caption and menu by pressing Esc, or with Settings->NoTitle in the menu.) There's a copy here: http://www.user.dccnet.com/jroe/wakeup/winclock.zip This app shows another Wine bug -- turning off the caption bar and menu ony half works -- the caption bar remains. Another example of an application which turns off the caption bar and menu (and which only half works under Wine): http://www.user.dccnet.com/jroe/wakeup/wakeup.zip - B10. Not critical, as we have a work-around. Apart from the WM_NCHITTEST method (see B9), the sample app demonstrates 2 algorithms for moving a window. I'll call the algorithms the 'mouse move argument' algorithm and the 'cursor pos' algorithm. Either algorithm works fine under Windows, and either algorithm works fine under Wine *if* the window has a caption bar. but if the window does not have a caption bar, the mouse move argument algorithm produces some very undesirable results -- if you move the mouse fast, WM_MOUSEMOVE appears to send some very confused LPARMS, and the window gets moved to unpredictable positions. Clicking on the "toggle bug B10" toggles between the 2 algorithms. (Remember to turn off the caption bar first -- see B8). - B11. Not critical, as we have a work around. RTF control. This one is not actually demonstraded by the sample app. The problem can commonly be seen when running installer progams -- the EULA is often displayed in a rich edit control, and is unreadable under wine. An example of such an installer: ** http://www.innosetup.com/ -Rob

1 0

Re: PATCH: uncripple winword 2000
by Andreas Mohr Nov. 3, 2003

Nov. 3, 2003

Hi, On Sat, Oct 25, 2003 at 02:23:17PM +0200, Marcus Meissner wrote: > Hi, > > Make Winword 2000 work again. > > I do not know, why it does outb $al,0x70, inb 0x71, $al ... > > And I am _afraid_ to ask. Why, that's perfectly ok... Just imagine your feeling if it also did: outb $al,0x70, outb al, 0x71 ;-)) That only goes to show what a crappy piece of !@#$@$% Winword 2000 is... > + if (INSTR_EmulateInstruction( epointers->ExceptionRecord, epointers->ContextRecord) == ExceptionContinueExecution) > + return EXCEPTION_CONTINUE_EXECUTION; BTW: Thanks!! This will most certainly fix my JTAG parallel port flashing tool (I already reported it, but nobody fixed it, and the result of "time * need" was too low...). -- Wir kommen alle als Original zur Welt, aber die meisten von uns sterben als Kopien (Autor unbekannt)

6 5

Wiki
by Mike Hearn Nov. 3, 2003

Nov. 3, 2003

Hi, Is there a Wine wiki anywhere? If not, I think there should be, I'm always coming across random useful bits of info that it makes sense to note down somewhere, but writing and submitting a patch against the Wine Docbook sources is too much effort (or it doesn't fit neatly into a category). Would it be possible to run one on WineHQ? Jeremy? thanks -mike

4 4

Re: Wiki
by Brian Vincent (C) Nov. 3, 2003

Nov. 3, 2003

> Well, a Wiki isn't an FAQ-o-matic (which I agree was not great). I was > thinking more of a random scratch pad developers can use to note down > useful tips, win32 oddities that don't fit better elsewhere, quick notes > on bugs and so on.... This really sounds like something that won't be maintained or contain enough information to be useful. Lots of folks spent a lot of time over the past year consolidating docs and cleaning everything up. Lots of developers don't even take the time to write up an email on this stuff, I can't imagine putting a web interface on it would change that. -brian

2 1

Re: Partially implement advapi.ReportEvent
by Mike Hearn Nov. 3, 2003

Nov. 3, 2003

Hi Alexandre, What was wrong with this patch? I guess you want it in a separate debug channel, yes? On Sun, 2003-10-19 at 12:58, Mike Hearn wrote: > This implementation is obviously not complete, but it prints out the > event log strings using MESSAGE, which is good enough for now. This is > handy because MSI uses this API when it gets into trouble, so we can now > see what it thinks is going on.

5 6