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

Re: SafeDisc FAQs

by Tels

-----BEGIN PGP SIGNED MESSAGE----- Moin, On 30-Apr-02 Tels carved into stone: > And even if it did, what could non-americans care about that? http://www.theregister.co.uk/content/4/25088.html Ouch! Seems we Europeans are in for much worse things :-( Cheers, Te"I wanna move - to the Mars"ls - -- "Why do you go so slowly? Do you think this is some kind of game?" PGP key available on http://bloodgate.com/tels.asc or via email. perl -MDev::Bollocks -e'print Dev::Bollocks->rand(),"\n"' confidentially deliver eligible mindshares -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: When cryptography is outlawed, bayl bhgynjf jvyy unir cevinpl. iQEVAwUBPM8lO3cLPEOTuEwVAQEPZAf+O4FH8K6alJQRo3HYwWktedcZ7j+co6as RlN1AH3f94c2mVRZ33gzNKZlXnCgpmNYXlxPI69dgiKuxTLs/zwUj13lIPviR79H PLzp/jJde6Rb1TSkoCbLTwx2OXJClFNyb6ElhpxKDMgNKK8m22RFfuFDjoz64q4e kPJrl5lBEPDggo0ppGpn5iN0QswhP1F5XmNv6l+qlq3mnYGk4w7K9xYFxSvEVaiE iAxP89rzuE7pODsNhK0JwMyorxea7dzHrVtqYc9ryWVuva7Ab3yVwMDoIYJhri7L DQqM6Q/NIQsmdcVXRMkxljfaNBoKVhCVn1pZoE5NT5nwoYdvmcVz5Q== =AadL -----END PGP SIGNATURE-----

April 30, 2002

Re: Bugzilla: A Call to Arms

by Dustin Navea

--- Andriy Palamarchuk <apa3a(a)yahoo.com> wrote: > > --- Tony Lambregts <tony_lambregts(a)telusplanet.net> > wrote: > > Of course, the responsibility is voluntary (as the > whole project BTW :-). > > Suggested list (so far): > * Guy L. Albertelli - GUI > * Alexandre Julliard - wineserver, kernel > * Marcus Meissner - printing > * Andreas Mohr - documentation > * Andriy Palamarchuk - winelib applications under > "programs" directory (agreed). > * Dimitrie O. Paun - GUI > * Laurent Pinchart - copy protection > * Eric Pouech - sound > * Hidenori TAKESHIMA - quartz, DirectShow (is the > scope too narrow?) > * Dmitry Timoshkov - internationalization, Unicode, > keyboard i/o > * Martin Wick - sockets > Do we need following directions, who are good > owners: > * DOS support > * common controls > * command-line handling > * wine tools > > This list is *very* subjective. I went through the > last month archives of wine-patches. Please, let me > know if you agree or not, know other better owner > for > the subsystem, want to suggest new subsystem, any > other comments are welcome. > Update: * wine tools: Dustin Navea IOW: I will help out with wine tools (bash/perl stuff) and when i can i will try to work on some actual wine bugs... knowing only enough c to bugfix can always be helpful... ;) -Dustin __________________________________________________ Do You Yahoo!? Yahoo! Health - your guide to health and wellness http://health.yahoo.com

April 30, 2002

MAX_PATH mess fix

by Steven Edwards

It seems mingw tries to include stdlib.h after windef.h in the build process and that was the result of the warnings/error. By making this change I don't have to change any of the other headers That depend on MAX_PATH (winnls,wingdi) by adding stdlib.h in them. I don't know if its right by the wine project standards but now I can compile 90% of the wine dll sources without warrnings/errors from stupid MAX_PATH. If someone has a better way please cvs diff -u me =) Thanks Steven Changelog: Fix the MAX_PATH mess under Mingw. (for real this time) cvs diff -u windef.h Index: windef.h =================================================================== RCS file: /home/wine/wine/include/windef.h,v retrieving revision 1.62 diff -u -r1.62 windef.h --- windef.h 10 Mar 2002 00:02:34 -0000 1.62 +++ windef.h 30 Apr 2002 21:41:42 -0000 @@ -149,6 +149,10 @@ #endif #endif /* NOMINMAX */ +#ifdef __MINGW__ +#include <stdlib.h> +#else + #ifndef _MAX_PATH /* FIXME: These are supposed to be in stdlib.h only */ #define _MAX_DRIVE 3 @@ -156,9 +160,13 @@ #define _MAX_DIR _MAX_FNAME #define _MAX_EXT _MAX_FNAME #define _MAX_PATH 260 -#endif +#endif /* _MAX_PATH */ + +#ifndef MAX_PATH #define MAX_PATH _MAX_PATH +#endif /* MAX_PATH */ +#endif /* __MINGW__ */ #define HFILE_ERROR ((HFILE)-1)

April 30, 2002

Re: wine/win32 editline.c

by Eric Pouech

Alexandre Julliard a écrit : > Modified files: > win32 : editline.c > > Log message: > Jason Edmeades <us(a)the-edmeades.demon.co.uk> > - Added f8 (history retrieval from partial command) support > - Delete key deletes current character > - Ctrl + end deletes to end of line > - Ctrl + right stopped before the word itself <patch excerpt> static KeyEntry EmacsKeyMapCtrl[] = { { CTRL('@'), WCEL_SetMark }, @@ -617,6 +664,7 @@ {/*VK_END*/ 0x23, WCEL_MoveToEnd }, {/*VK_UP*/ 0x26, WCEL_MoveToPrevHist }, {/*VK_DOWN*/ 0x28, WCEL_MoveToNextHist }, + {/*VK_DEL*/ 0x2e, WCEL_FindPrevInHist /*L_DeleteCurrChar*/ }, { 0, NULL } }; </patch excerpt> there's a typo in the patch. the VK_DEL entry should point to WCEL_DeleteCurrChar and not to WCEL_FindPrevInHist A+

April 30, 2002

wineconsole (Eric?) problem

by Ann and Jason Edmeades

Hi again, Another bug I have spotted can be demonstrated clearly by dir /s /w on wcmd on a small set of directories a couple of times (once my patch for /w is on). The first time it writes to the screen without scrolling and all is ok, the second time as it scrolls, it misses off 'Total files listed' and 'bytes free' two lines near the bottom. Basically the wineconsole is not being updated 100% correctly and skips some lines. Looking closely at the wineconsole code (by dumping out the screen at each event) I have worked out what is going on, but am not 100% sure about the 'proper' way to fix it. The problem is the console routines generally generate a sequence of events (assume an n line screen) v-scroll(x) (Make the xth line of the buffer the top line) update(x+n, x+n) (Write to the new bottom line of the screen) In the failing case I see v-scroll(x) (Make the xth line of the buffer the top line) update(x+n, x+n) (Write to the new bottom line of the screen) update(x+n+2, x+n+3) (Write beyond the bottom line of the screen) Although the data is retrieved correctly, it never gets displayed (An invalidaterect appears to happen) A simple way of avoiding this is to update wineconsole as follows: case CONSOLE_RENDERER_UPDATE_EVENT: Trace(1, " update(%d,%d)", evts[i].u.update.top, evts[i].u.update.bottom); /* test fix - Force updates to occur on visible screen */ if ((data->curcfg.win_pos.Y+data->curcfg.win_height) < evts[i].u.update.bottom) { Trace(1, " Forced vscroll \n"); data->fnScroll(data, evts[i].u.update.bottom - data->curcfg.win_height, FALSE); data->fnPosCursor(data); } else if (data->curcfg.win_pos.Y > evts[i].u.update.top) { Trace(1, " Forced vscroll2 \n"); data->fnScroll(data, evts[i].u.update.top, FALSE); data->fnPosCursor(data); } WINECON_FetchCells(data, evts[i].u.update.top, evts[i].u.update.bottom); The question is, is this correct, or is the server generating incorrect events, is the refresh not occurring properly etc? Thoughts please? Regards, Jason jason @ the-edmeades.demon.co.uk

April 30, 2002

Re: patch for cups printers

by Joerg Mayer

Just a very late addition to this discussion: I'm using cups 1.1.12 from Suse 8.0 and "cat file | lpr -Pprintername" works fine. ciao Jörg > - if (!strncmp("LPR:",pszOutput,4)) > + if (!strncmp("CUPS:",pszOutput,5)) > + sprintf(psCmd,"|lp -d%s",pszOutput+5); > + else if (!strncmp("LPR:",pszOutput,4)) > sprintf(psCmd,"|lpr -P%s",pszOutput+4); > else -- Joerg Mayer <jmayer(a)loplof.de> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.

April 30, 2002

Re: Bugzilla: A Call to Arms

by Tony Lambregts

Andriy Palamarchuk wrote: >--- Tony Lambregts <tony_lambregts(a)telusplanet.net> >wrote: > > >>Andriy Palamarchuk wrote: >> >> >[snip] > [snip] >Of course, the responsibility is voluntary (as the >whole project BTW :-). > >Suggested list (so far): >* Guy L. Albertelli - GUI >* Alexandre Julliard - wineserver, kernel >* Marcus Meissner - printing >* Andreas Mohr - documentation >* Andriy Palamarchuk - winelib applications under >"programs" directory (agreed). >* Dimitrie O. Paun - GUI >* Laurent Pinchart - copy protection >* Eric Pouech - sound >* Hidenori TAKESHIMA - quartz, DirectShow (is the >scope too narrow?) >* Dmitry Timoshkov - internationalization, Unicode, >keyboard i/o >* Martin Wick - sockets >Do we need following directions, who are good owners: >* DOS support >* common controls >* command-line handling >* wine tools > * Dustin Navea - wine tools (scripts?) * Duane Clark - toolbar > >This list is *very* subjective. I went through the >last month archives of wine-patches. Please, let me >know if you agree or not, know other better owner for >the subsystem, want to suggest new subsystem, any >other comments are welcome. > Could we can get some help to make this list somewhat complete, Please? [snip] >>>issues do not present challenge to them. >>>BTW, I do not see a field "Priority" in the bugs >>>entries. >>> >>> >>> >>The Severity field is for this and yes we should >>use it. >> >> > >Not exactly. "Severity" is an importance for the end >user - e.g. crash is the highest level of severity. >"Priority" is an importance of the issue for us. >E.g. crash of an application due to Wine not >supporting vxd is severity "Critical" for the user, >but priority is "Minor" for the Wine developers >because we are not going to support vxd anyways. > To most users that encounter a bug the severity is "critical". It is up to the bug owners and triage to decide what is important. Mozzilla has a resolution "WON'T FIX" for some bugs. I think vxd is "WONT FIX". As a long term tester of Mozilla I can say with confidence that severity is a flag for triage and development not for bug reporters. [blocker] is the highest priority: for example something prevents wine from compiling. Anyway the way that mozilla uses bugzilla is not the only way to use it. We have the source code if we really want to change it. I just don't see that it is nesessary. > >[... skipped ...] > > >>If there are no objections can we change the >>official documentation to >>say that bugzilla is the place to report bugs. I >>noticed that when the >>wineinstall script had a bug in it that it told the >>users to report it >>to wine-devel when it should point them to >>bugzilla. One other comment >>about this is that bugzilla's address is >>http://wine.codeweavers.com/bugs/ and I think it >>scares people away from >>using it. I have nothing against CodeWeavers but I >>think If bugzilla's >>address was http://www.winehq.com/bugzilla users >>would be certain it is >>the place for wine bugs >> >> > >Agree. Now enter bugs to bugzilla for these changes >;-) > > > I entered bugs for the first two, and the third seems to be resolved already. <grin> Tony Lambregts

April 30, 2002

Re: word can't open documents...

by Michael Cardenas

Here's some more info on this major regression in microsoft word, with my own trace messages added. This feature works correctly in crossover office, by the way. The crash occurs after create_whole_window and create_client_window are called, when we try to do a TSXSync. ---------------------------------------------------------------------- trace:win:WIN_CreateWindowEx (null) "_WwG" ex=00000000 style=46000000 0,0 1022x673 parent=2003f menu=0000 inst=30000000 params=(nil)trace:win:dump_window_styles style: WS_CHILD WS_CLIPSIBLINGS WS_CLIPCHILDREN trace:win:dump_window_styles exstyle: trace:win:WIN_CreateWindowEx winproc type is 2 (WIN_PROC_32A) trace:win:WIN_SetWindowLong 20040 -12 0 3 trace:x11drv:X11DRV_CreateWindow in trace:win:WIN_SetRectangles win 20040 window (0,0)-(1022,673) client (0,0)-(1022,673) trace:x11drv:X11DRV_CreateWindow before create_whole_window trace:x11drv:X11DRV_CreateWindow before create_client_window trace:x11drv:X11DRV_CreateWindow after create_client_window trace:x11drv:X11DRV_CreateWindow after TSXSync trace:x11drv:X11DRV_CreateWindow after SetPropA whole_window_atom trace:x11drv:X11DRV_CreateWindow after SetPropA client_window_atom trace:x11drv:X11DRV_CreateWindow before WM_GETMINMAXINFO trace:x11drv:X11DRV_CreateWindow before WM_NCCREATE trace:x11drv:X11DRV_CreateWindow hwnd 20040 cs 0,0 1022x673 trace:win:WIN_SetRectangles win 20040 window (0,0)-(1022,673) client (0,0)-(1022,673) trace:x11drv:X11DRV_CreateWindow win 20040 window 0,0,1022,673 client 0,0,1022,673 whole 0,0,1022,673 X client 0,0,1022,673 xwin 28000ff/2800100 trace:win:WIN_SetWindowLong 20040 0 41e903ec 2 trace:x11drv:X11DRV_CreateWindow returning... trace:win:WIN_CreateWindowEx created window 20040 trace:win:WIN_CreateWindowEx (null) "SCROLLBAR" ex=00000000 style=54000001 0,1079331068 1065353216x0 parent=2003f menu=0000 inst=30000000 params=(nil) trace:win:dump_window_styles style: WS_CHILD WS_VISIBLE WS_CLIPSIBLINGS 00000001 trace:win:dump_window_styles exstyle: trace:win:WIN_CreateWindowEx winproc type is 2 (WIN_PROC_32A) trace:win:WIN_SetWindowLong 2003c -12 0 3 trace:x11drv:X11DRV_CreateWindow in trace:win:WIN_SetRectangles win 2003c window (0,1079331068)-(1065353216,1079331068) client (0,1079331068)-(1065353216,1079331068) trace:x11drv:X11DRV_CreateWindow before create_whole_window trace:x11drv:X11DRV_CreateWindow before create_client_window trace:x11drv:X11DRV_CreateWindow after create_client_window X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 1 (X_CreateWindow) Value in failed request: 0x0 Serial number of failed request: 2275 Current serial number in output stream: 2278 -- michael cardenas lead windows compatibility engineer lindows.com "Be the change you want to see in the world" -Mahatma Gandhi

April 30, 2002

File not found after cvs update

by Marcelo Welter

Hello friends after cvs update a make ./configure config.status: error: cannot find input file: dlls/snmpapi/Makefile.in what happen with this file...? Marcelo

April 30, 2002

Re: SafeDisc FAQs

by Tels

-----BEGIN PGP SIGNED MESSAGE----- Moin, On 29-Apr-02 Laurent Pinchart carved into stone: > >> Aren't you actually violating the DMCA? since you're practically reverse >> engineering and making wine work with copy protection based games.. > > Most of my work was implementing missing features. No problem there. > > The only problem could be the implementation of secdrv.sys, but IMHO it > doesn't violate the DMCA, And even if it did, what could non-americans care about that? Cheers, Te"Glad I am an European for now;)"ls - -- "Why do you go so slowly? Do you think this is some kind of game?" PGP key available on http://bloodgate.com/tels.asc or via email. perl -MDev::Bollocks -e'print Dev::Bollocks->rand(),"\n"' evangelistically foster third-generation patterns -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: When cryptography is outlawed, bayl bhgynjf jvyy unir cevinpl. iQEVAwUBPM7NB3cLPEOTuEwVAQG3Twf9HQBdiauLsQNSjcNub2YG3NzrCY1ZwS/X fLgPfy+u+jvNFgejV/mziYTb2Ffxo4XHtJaaV2Ee/HzEVygdY0JFUexLoza8cNaQ NxnjSkuCe2nMUEFu16SM9DIsTOa6uKGPD/D4IXFfBHjIrpd1WJ62DcRE+AwMSOjp 8nWTvxzT2x5Ldr7GwuePd8XPaZctclwsslwS7iygGgXRS2yJVN0ZKczP0l34mvXu 1ihnzpOHkDZuk1G/oUAJkhh3PRJUNLZNi8MvId2xyoy+qEHiIaheWxcdnyPoB6np WexHFzpaaRGKDTN8TeJ0V8kV5OtzIlozZYz254cfKIGW9lJJJG1Ecw== =F5Zg -----END PGP SIGNATURE-----

April 30, 2002

Re: patch for cups printers

by Michael Cardenas

Yes, Duane Clark pointed this out already. Apparently, the lpr that shpis with lindowsOS is incomplete for some reason. We're looking into fixing it. I just submitted the patch because I think it is more correct, and there is a possibility that other systems that have cups might not have complete lpr implementations. On Tue, Apr 30, 2002 at 09:42:07PM +0200, Joerg Mayer wrote: > Just a very late addition to this discussion: I'm using cups 1.1.12 from > Suse 8.0 and "cat file | lpr -Pprintername" works fine. > > ciao > J?rg > > > - if (!strncmp("LPR:",pszOutput,4)) > > + if (!strncmp("CUPS:",pszOutput,5)) > > + sprintf(psCmd,"|lp -d%s",pszOutput+5); > > + else if (!strncmp("LPR:",pszOutput,4)) > > sprintf(psCmd,"|lpr -P%s",pszOutput+4); > > else > > > -- > Joerg Mayer <jmayer(a)loplof.de> > I found out that "pro" means "instead of" (as in proconsul). Now I know > what proactive means. > > > > -- michael cardenas lead windows compatibility engineer lindows.com "Be the change you want to see in the world" -Mahatma Gandhi

April 30, 2002

Re: Chinese text input into Notes R6 Mail field

by Daniel Schwarz

> Actually Aric and Ulrich helped a lot and they provided us the patch you > Codeweavers did for your clients and Aric has > gained permission to open the source. Since he needs to clean up the > code, he suggested to let him post the patch when it's > done. > > I used it to try for Chinese Input on Notes Client r6. Unfortunately, > it only works on some controls. > When I want to type Chinese/Japanese on the mail content area ( do not > know what kind of widget it is), > it doesn't show properly. I think it's a bug. Could you kindly help? > Which segment of code I should trace on? I have not used Notes R6 extensively but based on my understanding of the Notes R4 - R5 code, the mail content area is a Notes Rich Text field, which is implemented internally to Notes. It's not a Windows control therefore will not be responsive to code that hooks into Windows controls. Notes is localized for many countries,including, I think, Chinese, although the Notes R6 Beta is probably US-English only. I suggest you experiment with a copy of Notes R5 with Chinese localization. If you need technical details on how localized versions of Notes handle alternate keyboard input methods, let me know and I'll see what I can dig up. Regards, Dan Schwarz http://www.winecentric.com/wiki The Wine Wiki

April 30, 2002

Re: Bugzilla: A Call to Arms

by Andriy Palamarchuk

--- Tony Lambregts <tony_lambregts(a)telusplanet.net> wrote: > Andriy Palamarchuk wrote: [... skipped ...] > >Developers, please let me know your areas of > >expertese. > >I can overview Wine applications. > > > Let me see if I have this right you want an > inventory of who has what > area of experise right. For example if a bug report > seems to point to a > problem with sockets you could in theory assign it > to Martin Wick, or if > the problem was with copy protection It could be > assigned to Laurent > Pinchart. Of course that assumes that both of them > are ok with this. Of course, the responsibility is voluntary (as the whole project BTW :-). Suggested list (so far): * Guy L. Albertelli - GUI * Alexandre Julliard - wineserver, kernel * Marcus Meissner - printing * Andreas Mohr - documentation * Andriy Palamarchuk - winelib applications under "programs" directory (agreed). * Dimitrie O. Paun - GUI * Laurent Pinchart - copy protection * Eric Pouech - sound * Hidenori TAKESHIMA - quartz, DirectShow (is the scope too narrow?) * Dmitry Timoshkov - internationalization, Unicode, keyboard i/o * Martin Wick - sockets Do we need following directions, who are good owners: * DOS support * common controls * command-line handling * wine tools This list is *very* subjective. I went through the last month archives of wine-patches. Please, let me know if you agree or not, know other better owner for the subsystem, want to suggest new subsystem, any other comments are welcome. > What exactly do you mean by overview applications? > I'm guessing you mean > the wine lib applications currently under /programs > right? Correct, see above > >2) more formally define process of bugs handling > and > >use this process. [... skipped ...] > >I see that Tony Lambregts, Michael Cardenas, others > do > >a great work with the Bugzilla database. > >I'm also going to contribute some time for this. > > > > > Think if we can get a few more people to to help > with this it would be > better Completely agree with you. This is why I invited the companies testers for this work ;-) I'm sure we'll get more volunteers from Wine users as soon as we will be more responsive in Bugzilla. Anyway, the first priority is to start to actually move bugs throgh their lifecycle to the RESOLVED status and now the bottleneck is on status NEW. > >3) Prioritize bugs. This is, probably, part of (2). > >Some bugs, while relatively easy to fix provide > very > >big value for the end user. Often developers do not > >choose such issues to work on, exactly because > these > >issues do not present challenge to them. > >BTW, I do not see a field "Priority" in the bugs > >entries. > > > > The Severity field is for this and yes we should > use it. Not exactly. "Severity" is an importance for the end user - e.g. crash is the highest level of severity. "Priority" is an importance of the issue for us. E.g. crash of an application due to Wine not supporting vxd is severity "Critical" for the user, but priority is "Minor" for the Wine developers because we are not going to support vxd anyways. [... skipped ...] > If there are no objections can we change the > official documentation to > say that bugzilla is the place to report bugs. I > noticed that when the > wineinstall script had a bug in it that it told the > users to report it > to wine-devel when it should point them to > bugzilla. One other comment > about this is that bugzilla's address is > http://wine.codeweavers.com/bugs/ and I think it > scares people away from > using it. I have nothing against CodeWeavers but I > think If bugzilla's > address was http://www.winehq.com/bugzilla users > would be certain it is > the place for wine bugs Agree. Now enter bugs to bugzilla for these changes ;-) Andriy __________________________________________________ Do You Yahoo!? Yahoo! Health - your guide to health and wellness http://health.yahoo.com

April 30, 2002

Re: cups support apparently broken

by Michael Stefaniuc

On Mon, Apr 29, 2002 at 02:53:32PM -0400, Michael Cardenas wrote: > On Mon, Apr 29, 2002 at 10:09:19PM +0200, Marcus Meissner wrote: > > > trying to do an > > > > > > echo "print" | lpr -Peng > > > > Actually WINE assumes that a CUPS printer can be sent jobs using > > lpr -P<printername> on stdin. > > > > If this is not the case, you will have to change dlls/gdi/printdrv.c > > and dlls/winspool/info.c. > > Apparently, the correct command for cups is lp and -P needs to be > replaced with -d I don't know how the cups package is build on debian, but cups provides both commands lpr and lp. And both commands work. bye michael > > so by changing > > if (!strncmp("LPR:",pszOutput,4)) > sprintf(psCmd,"|lpr -P%s",pszOutput+4); > > to > > if (!strncmp("LPR:",pszOutput,4)) > sprintf(psCmd,"|lp -d%s",pszOutput+4); > > in > > wine/dlls/gdi/printdrv.c > > it now works, but only for CUPS printers. > > I'll send a patch that checks the registry for a description with CUPS > in it and uses lp -d if appropriate. > > thanks for the help. > > -- 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

April 30, 2002

Re: Bugzilla: A Call to Arms

by Jeremy Newman

I'm not going to even debate this one <g> http://bugs.winehq.com http://bugs.winehq.org http://bugs.codeweavers.com Are now all the same website. Use whatever Url makes you fell all warm and fuzzy. On Tue, 2002-04-30 at 10:18, Jeremy White wrote: > > to wine-devel when it should point them to bugzilla. One other comment > > about this is that bugzilla's address is > > http://wine.codeweavers.com/bugs/ and I think it scares people away from > > using it. I have nothing against CodeWeavers but I think If bugzilla's > > address was http://www.winehq.com/bugzilla users would be certain it is > > the place for wine bugs > > Wouldn't > http://bugs.winehq.com > be even better? > > We can make that switch fairly readily, and we're cheerful > to do so. (Okay, I'm cheerful to do so, Jeremy is going to > kill me for adding to his workload <grin>). > > Cheers, > > Jer > > > -- __ _WebGeek/NetAdmin CodeWeavers -= http://www.codeweavers.com | \| |_____ __ ___ __ __ _ _ _ -= http://www.dracowulf.com | .` / -_) | | / ' \/ _` | ' \ -= mailto:jnewman(a)codeweavers.com |_|\_\___|\_/\_/|_|_|_\__,_|_||_| -= ICQ: 1842980 Yahoo: laxdragon

April 30, 2002

Re: default windows version

by Andreas Mohr

On Tue, Apr 30, 2002 at 08:39:05AM -0300, Insyde wrote: > >There's no such thing as a default version ;-) > >Wine figures it out from the DLLs the program uses if no version is forced. > > So why I get an error msg if I start with no parameters and all DLL from > win2k? Hell, is that code so difficult ? VERSION_GetSystemDLLVersion clearly only has NT351 or NT4 results in case of NT DLLs. (and yes, you could call this sort of buggy ;) Hmm, I guess we should actually update the whole version code to take newer Windows versions into account... I'll have a look at that. -- Andreas Mohr Stauferstr. 6, D-71272 Renningen, Germany Tel. +49 7159 800604 http://home.arcor.de/andi.mohr/

April 30, 2002

Re: Bugzilla: A Call to Arms

by Jeremy White

> to wine-devel when it should point them to bugzilla. One other comment > about this is that bugzilla's address is > http://wine.codeweavers.com/bugs/ and I think it scares people away from > using it. I have nothing against CodeWeavers but I think If bugzilla's > address was http://www.winehq.com/bugzilla users would be certain it is > the place for wine bugs Wouldn't http://bugs.winehq.com be even better? We can make that switch fairly readily, and we're cheerful to do so. (Okay, I'm cheerful to do so, Jeremy is going to kill me for adding to his workload <grin>). Cheers, Jer

April 30, 2002

Re: default windows version

by Sylvain Petreolle

try this : set an alias for wine such as : alias wine='wine --winver win2k' --- Insyde <insyde(a)insyde.com.br> a écrit : > >There's no such thing as a default version ;-) > >Wine figures it out from the DLLs the program uses > if no version is forced. > > So why I get an error msg if I start with no > parameters and all DLL from > win2k? > this is the error I got when I start with out > parameters (which is the same > I have > when the child program is called): > > err:ntdll:RtlpWaitForCriticalSection section > 0x400f164c "module.c: > loader_section" wait timed out, retrying (60 sec) > fs=021f > > > >Hmm, come to think of it: > >Unless we actually pass all wine cmdline parameters > (--winver, --managed > etc.) > >on to the wine child process (not sure about that > right now, I think we > do), > >the new process won't use the same forced winver > value as the > >parent process uses. > >Is this a problem ? Should this info be passed to > the wineserver to > >globalize it ? > > Yes, if this happen it should be a problem. I think > most people will never > face > it because their programs have only one executable. > If you have a lot of > child > programs and need the version to be the chosen one > then we need to send the > parameter to wineserver to start with that winver. > > >Oh, BTW: I'll rename defaultWinVersion to > cmdlineWinVersion. > >Much better name. > Yes, it really is. > > Ricardo. > > ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com

April 30, 2002

Re: word can't open documents...

by Michael Cardenas

Here's a little more info on this. I ran wine with trace+x11drv and got this: trace:x11drv:X11DRV_CreateWindow hwnd 1004a cs 0,0 1022x673 trace:x11drv:X11DRV_CreateWindow win 1004a window 0,0,1022,673 client 0,0,1022,673 whole 0,0,1022,673 X client 0,0,1022,673 xwin 240013f/2400140 X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 1 (X_CreateWindow) Value in failed request: 0x0 Serial number of failed request: 3077 Current serial number in output stream: 3080 does anyone know what has changed lately with X11DRV_CreateWindow? On Wed, Apr 24, 2002 at 04:33:11PM -0400, Michael Cardenas wrote: > With yesterday's cvs, opening a document causes it to crash with this output > on the console: > X Error of failed request: BadValue (integer parameter out of range for > operation) > Major opcode of failed request: 1 (X_CreateWindow) > Value in failed request: 0x0 > Serial number of failed request: 30392 > Current serial number in output stream: 30395 -- michael cardenas lead windows compatibility engineer lindows.com "Be the change you want to see in the world" -Mahatma Gandhi

April 30, 2002

Re: default windows version

by Insyde

Ok, it worked!! Wine is NOT passing the --winver parameter to the child process. So what I did (I know that's not right, but I needed this working): Edit misc/version.c and changed line (193 of wine-20020411) static BOOL versionForced = FALSE; to static BOOL versionForced = TRUE; and line (194 of wine-20020411) WINDOWS_VERSION = WIN31; to WINDOWS_VERSION = NT2K; As I'm using NT2K DLLs, on a non-windows wine instalation, I didn't copy any of the DLLs wine implements, maybe wine can't guess what Windows version to use (no clue), just the DLLs needed by the program to run. Why don't use something inside .wine/config or wine.conf like winver = "win98" to set the environment we want to use? If the user wants to override this he would use the command line so force a different one. If someone can help me, I would be happy to try to do it. Ricardo. ps.: but please be patient, I'm not very skilled with C. :)

April 30, 2002

Re: patch for cups printers

by Michael Cardenas

Attached is a correction for yesterday's lame printing patch. This corrects the string length errors and the LPR else case. On Tue, Apr 30, 2002 at 06:43:11AM +0200, Marcus Meissner wrote: > > --- winehq/dlls/gdi/printdrv.c Thu Mar 28 17:22:05 2002 > > +++ wine/dlls/gdi/printdrv.c Mon Apr 29 15:29:42 2002 > > @@ -482,6 +482,8 @@ > > > > if (!strncmp("LPR:",pszOutput,4)) > > sprintf(psCmd,"|lpr -P%s",pszOutput+4); > > + if (!strncmp("CUPS:",pszOutput,4)) > > + sprintf(psCmd,"|lp -d%s",pszOutput+4); > > else > > { > > HKEY hkey; > > > This is wrong, the else { } is handled in the LPR: case too so you break > /etc/printcap based printing. > > Ciao, Marcus > > > -- michael cardenas lead windows compatibility engineer lindows.com "Be the change you want to see in the world" -Mahatma Gandhi

April 30, 2002

Re: File not found after cvs update

by Michael Cardenas

snmpapi is a new dll, update won't get new files for you. you need to cvs update -RdP which you can read about if you do a cvs -H update On Tue, Apr 30, 2002 at 02:18:53PM -0300, Marcelo Welter wrote: > > Hello friends > > after cvs update a make > ./configure > config.status: error: cannot find input file: dlls/snmpapi/Makefile.in > > > what happen with this file...? > > > Marcelo > > > -- michael cardenas lead windows compatibility engineer lindows.com "Be the change you want to see in the world" -Mahatma Gandhi

April 30, 2002

Re: default windows version

by Insyde

>There's no such thing as a default version ;-) >Wine figures it out from the DLLs the program uses if no version is forced. So why I get an error msg if I start with no parameters and all DLL from win2k? this is the error I got when I start with out parameters (which is the same I have when the child program is called): err:ntdll:RtlpWaitForCriticalSection section 0x400f164c "module.c: loader_section" wait timed out, retrying (60 sec) fs=021f >Hmm, come to think of it: >Unless we actually pass all wine cmdline parameters (--winver, --managed etc.) >on to the wine child process (not sure about that right now, I think we do), >the new process won't use the same forced winver value as the >parent process uses. >Is this a problem ? Should this info be passed to the wineserver to >globalize it ? Yes, if this happen it should be a problem. I think most people will never face it because their programs have only one executable. If you have a lot of child programs and need the version to be the chosen one then we need to send the parameter to wineserver to start with that winver. >Oh, BTW: I'll rename defaultWinVersion to cmdlineWinVersion. >Much better name. Yes, it really is. Ricardo.

April 30, 2002

Re: patch for cups printers

by Marcus Meissner

> --- winehq/dlls/gdi/printdrv.c Thu Mar 28 17:22:05 2002 > +++ wine/dlls/gdi/printdrv.c Mon Apr 29 15:29:42 2002 > @@ -482,6 +482,8 @@ > > if (!strncmp("LPR:",pszOutput,4)) > sprintf(psCmd,"|lpr -P%s",pszOutput+4); > + if (!strncmp("CUPS:",pszOutput,4)) > + sprintf(psCmd,"|lp -d%s",pszOutput+4); > else > { > HKEY hkey; This is wrong, the else { } is handled in the LPR: case too so you break /etc/printcap based printing. Ciao, Marcus

April 30, 2002

Re: [Help]: Notes Client on WINE with XIM (Chinese/Japanese Input)

by leanne

Mike McCormack wrote: > > Hi Leanne, > > Which notepad.exe are you using? As far as I understand, Wine has no > support for X Input contexts at all, so I don't understand how you can > enter Chinese text into Notes... perhaps Notes has it's own input > method or you using an Xlib modified for multibyte support? Is your > Wine-20020422 tree unmodified? Hello, Mike! Actually Aric and Ulrich helped a lot and they provided us the patch you Codeweavers did for your clients and Aric has gained permission to open the source. Since he needs to clean up the code, he suggested to let him post the patch when it's done. I used it to try for Chinese Input on Notes Client r6. Unfortunately, it only works on some controls. When I want to type Chinese/Japanese on the mail content area ( do not know what kind of widget it is), it doesn't show properly. I think it's a bug. Could you kindly help? Which segment of code I should trace on? Very thanks. > > > Could you please explain your setup in a bit more detail, for example, > which X input method you are using, the XMODIFIERS, LANG, LC_ALL > settings, etc. I'm very curious as to how this is working... > > thanks, > > Mike > > > leanne wrote: > >> Dear all, >> >> We are trying to use WINE (22/4/2002 version) to run Notes Client r6 >> with Chinese/Japanese Input. >> XIM is started successfully, but in some widgets we could not input >> Chinese/Japanese. >> >> Please find the screenshot here >> (http://www.thizlinux.com/~leanne/notes.png) >> >> We are forwarding a mail (with Chinese) in Notes Client. Chinese can >> be displayed but NOT input in >> the mail content area (After "Subject" line). What type of widget it >> is so that we could fix it? >> >> We can type Chinese on "Address" line (listbox). >> >> p.s. We can display and input Chinese/Japanese in Notepad.exe without >> any problems. >> >> Yours, >> Leanne >> >> > > > >

April 30, 2002

Re: Bugzilla: A Call to Arms

by Tony Lambregts

Andriy Palamarchuk wrote: >We already had discussion on wine-devel about >importance of polishing Wine, making a set of >applications to work very well. > >Cruicial in this process is prioritizing of the >issues, work distribution between developers. The >companies already have internal testing and bug fixing >process. > >Of course, each company has their own product-specific >work, but most of the problems are general for Wine. >I suggest to share this work more actively using >Bugzilla. > >Recently there was some work done in cleaning the >issues database and it is in pretty much usable >condition. > >To start using bugzilla more actively I suggest >following steps: >1) define subsystem/direction owners. The owners will >get their system-specific bugs. They won't necessary >fix the bugs themselfs, but will have complete picture >about all the issues in their subsystems and >coordinate the bug fixing. > >Developers, please let me know your areas of >expertese. >I can overview Wine applications. > Let me see if I have this right you want an inventory of who has what area of experise right. For example if a bug report seems to point to a problem with sockets you could in theory assign it to Martin Wick, or if the problem was with copy protection It could be assigned to Laurent Pinchart. Of course that assumes that both of them are ok with this. What exactly do you mean by overview applications? I'm guessing you mean the wine lib applications currently under /programs right? Anyway this would be very usefull to the people who want to triage bugzilla. > >2) more formally define process of bugs handling and >use this process. There is no high qualification >needed to filter out bad bug reports, duplicates, >request users for more information, attach relay trace >to the bug, etc, etc. >Result - developers will have to spend less time on >discussion trivial bugs with users, will have better >bug reports to work on, users will be more involved >with more active feedback. Some users are very >cooperative and some bug reports are really excellent! >I see that Tony Lambregts, Michael Cardenas, others do >a great work with the Bugzilla database. >I'm also going to contribute some time for this. > > Think if we can get a few more people to to help with this it would be better >3) Prioritize bugs. This is, probably, part of (2). >Some bugs, while relatively easy to fix provide very >big value for the end user. Often developers do not >choose such issues to work on, exactly because these >issues do not present challenge to them. >BTW, I do not see a field "Priority" in the bugs >entries. > The Severity field is for this and yes we should use it. > >4) Ask users to submit there problems in Bugzilla. >Submitting Bugzilla report allows us to involve users >more actively, persist their bug reports. > >Bugzilla is a more scalable approach than using >mailing list only. Of course we still will discuss >bugs on the mailing lists, bug big part of >communication will be unloaded. > > If there are no objections can we change the official documentation to say that bugzilla is the place to report bugs. I noticed that when the wineinstall script had a bug in it that it told the users to report it to wine-devel when it should point them to bugzilla. One other comment about this is that bugzilla's address is http://wine.codeweavers.com/bugs/ and I think it scares people away from using it. I have nothing against CodeWeavers but I think If bugzilla's address was http://www.winehq.com/bugzilla users would be certain it is the place for wine bugs >There is a lot to do and discuss. >For me the goal is to have this process not worse than >in Mozilla project. This is impressive: >http://webtools.mozilla.org/miscstats/ >http://mothra.mozilla.org/webtools/miscstats/ > >I also like their bug report form: >http://www.mozilla.org/quality/help/bugzilla-helper.html > >And this is for 1 application only! I'm sure Wine can >generate much bigger volume of bug reports ;-) > >Look forward for your comments. >Andriy > >__________________________________________________ >Do You Yahoo!? >Yahoo! Health - your guide to health and wellness >http://health.yahoo.com > > > >

April 30, 2002

Re: [Help]: Notes Client on WINE with XIM (Chinese/Japanese Input)

by Mike McCormack

Hi Leanne, Which notepad.exe are you using? As far as I understand, Wine has no support for X Input contexts at all, so I don't understand how you can enter Chinese text into Notes... perhaps Notes has it's own input method or you using an Xlib modified for multibyte support? Is your Wine-20020422 tree unmodified? Could you please explain your setup in a bit more detail, for example, which X input method you are using, the XMODIFIERS, LANG, LC_ALL settings, etc. I'm very curious as to how this is working... thanks, Mike leanne wrote: > Dear all, > > We are trying to use WINE (22/4/2002 version) to run Notes Client r6 > with Chinese/Japanese Input. > XIM is started successfully, but in some widgets we could not input > Chinese/Japanese. > > Please find the screenshot here > (http://www.thizlinux.com/~leanne/notes.png) > > We are forwarding a mail (with Chinese) in Notes Client. Chinese can be > displayed but NOT input in > the mail content area (After "Subject" line). What type of widget it is > so that we could fix it? > > We can type Chinese on "Address" line (listbox). > > p.s. We can display and input Chinese/Japanese in Notepad.exe without > any problems. > > Yours, > Leanne > >

April 30, 2002

[Help]: Notes Client on WINE with XIM (Chinese/Japanese Input)

by leanne

Dear all, We are trying to use WINE (22/4/2002 version) to run Notes Client r6 with Chinese/Japanese Input. XIM is started successfully, but in some widgets we could not input Chinese/Japanese. Please find the screenshot here (http://www.thizlinux.com/~leanne/notes.png) We are forwarding a mail (with Chinese) in Notes Client. Chinese can be displayed but NOT input in the mail content area (After "Subject" line). What type of widget it is so that we could fix it? We can type Chinese on "Address" line (listbox). p.s. We can display and input Chinese/Japanese in Notepad.exe without any problems. Yours, Leanne

April 30, 2002

Re: patch for cups printers

by Dmitry Timoshkov

"Michael Cardenas" <michael.cardenas(a)lindows.com> wrote: > --- winehq/dlls/gdi/printdrv.c Thu Mar 28 17:22:05 2002 > +++ wine/dlls/gdi/printdrv.c Mon Apr 29 15:29:42 2002 > @@ -482,6 +482,8 @@ > if (!strncmp("LPR:",pszOutput,4)) > sprintf(psCmd,"|lpr -P%s",pszOutput+4); > + if (!strncmp("CUPS:",pszOutput,4)) > + sprintf(psCmd,"|lp -d%s",pszOutput+4); Something tells me that two '4's above should be replaced by '5's ... -- Dmitry.

April 29, 2002

Re: patch for cups printers

by Huw D M Davies

On Mon, Apr 29, 2002 at 03:39:46PM -0400, Michael Cardenas wrote: > Changelog: > This patch fixes printing on cups systems that don't have complete lpr > implementations. It won't affect non cups systems. > > It changes the device listed in the registry for cups printers to CUPS: > instead of LPR: and uses "lp -d" for a cups printer instead of "lpr -P". > > + if (!strncmp("CUPS:",pszOutput,4)) > + sprintf(psCmd,"|lp -d%s",pszOutput+4); s/4/5/ ? By the way the cups user manual seems to imply that it supplies both lp and lpr commands. Of course we should probably send jobs to cups via the cupsPrintFile() api but I guess that can wait. Huw.

April 29, 2002

Re: debugging focus problem

by degs

On Monday 29 April 2002 23:06, Andreas Mohr wrote: > On Mon, Apr 29, 2002 at 10:33:04PM +0100, degs wrote: > > Hi, > > > > Can anyone suggest what debug channels would be useful for locating the > > cause of focus or mouse input routing problems? > > --debugmsg +relay,+win,+msg,+sendmsg,+message,+event,+x11,+x11drv,+cursor > Mainly relay, event, msg, x11drv, I think. > > Then have a look at search.microsoft.com to locate some docu about one or > another thing, and that's it. Thanks. It looks like mouse messages are going to the window's parent rather than the window itself. I'm not very familiar with win32 so I don't know if this is usual or not but it seems a bit odd. Anyway - at least I have an idea what's going on now. -- degs

April 29, 2002

Re: default windows version

by Andreas Mohr

On Mon, Apr 29, 2002 at 07:07:13PM -0300, rootzz(a)ig.com.br wrote: > Em 29 Apr 2002, andi(a)rhlx01.fht-esslingen.de escreveu: > > >On Mon, Apr 29, 2002 at 04:58:16PM -0300, Insyde wrote: > >> Hi, > >> I had a problem loading a second program under wine. > >> I called the first program with: > >> wine --winver win2000 pgm1 > >> I input a password and it wirtes a data file, unloads itself > >> and loads a second program. But there was an error every > >> time the second program was to start that send me to the > >> debug screen. > >> So I found misc/version.c line 196 that the default value to > >> wine load a program was WIN31, so I changed it to NT2K. > >> > >> Is there any problem doing this? If not, why is the default still > >> WIN31? > >No, it's *not*. > > > >If you examine the code more closely, then you'll notice that > >defaultWinVersion only gets used in case versionForced is TRUE, > >which is only the case once defaultWinVersion gets set to an actually > >specified value. > > > >I know, the code is sort of confusing if you don't examine it closely, > >so feel free to comment on how to improve the situation with regards > >to defaultWinVersion initialization (I'd like to not initialize it at all, > >since it isn't being used unless there's a user setting, > >but that's not very clean of course ;-) > > So it's only used if I force a version? I forced a version as: > wine --winver win2000 pgm1 > when pgm1 stops and start pgm2 which version is used? The one that Wine figures out for the new program. > what is the default version though? There's no such thing as a default version ;-) Wine figures it out from the DLLs the program uses if no version is forced. Hmm, come to think of it: Unless we actually pass all wine cmdline parameters (--winver, --managed etc.) on to the wine child process (not sure about that right now, I think we do), the new process won't use the same forced winver value as the parent process uses. Is this a problem ? Should this info be passed to the wineserver to globalize it ? Oh, BTW: I'll rename defaultWinVersion to cmdlineWinVersion. Much better name. -- Andreas Mohr Stauferstr. 6, D-71272 Renningen, Germany Tel. +49 7159 800604 http://home.arcor.de/andi.mohr/

April 29, 2002

Re: debugging focus problem

by degs

On Monday 29 April 2002 22:50, Mike McCormack wrote: > You'll get most of the information you want from: > > --debugmsg +x11drv,+win,+message > Thanks - that looks like it its going to be useful. > The problem is you'll get too much. Sometimes you can pipe the output > through egrep... Its getting stuck pretty early on so there's not *that* much to wade through... > > Mike > > degs wrote: > > Hi, > > > > Can anyone suggest what debug channels would be useful for locating the > > cause of focus or mouse input routing problems? > > > > thanks > > -- degs

April 29, 2002

Re: debugging focus problem

by Andreas Mohr

On Mon, Apr 29, 2002 at 10:33:04PM +0100, degs wrote: > Hi, > > Can anyone suggest what debug channels would be useful for locating the cause > of focus or mouse input routing problems? --debugmsg +relay,+win,+msg,+sendmsg,+message,+event,+x11,+x11drv,+cursor Mainly relay, event, msg, x11drv, I think. Then have a look at search.microsoft.com to locate some docu about one or another thing, and that's it. -- Andreas Mohr Stauferstr. 6, D-71272 Renningen, Germany Tel. +49 7159 800604 http://home.arcor.de/andi.mohr/

April 29, 2002

Re: debugging focus problem

by Mike McCormack

You'll get most of the information you want from: --debugmsg +x11drv,+win,+message The problem is you'll get too much. Sometimes you can pipe the output through egrep... Mike degs wrote: > Hi, > > Can anyone suggest what debug channels would be useful for locating the cause > of focus or mouse input routing problems? > > thanks > -- degs

April 29, 2002

debugging focus problem

by degs

Hi, Can anyone suggest what debug channels would be useful for locating the cause of focus or mouse input routing problems? thanks -- degs

April 29, 2002

Re: SafeDisc FAQs

by Laurent Pinchart

> I don't think he is. Reverse engineering for the purpose of enabling > interoperability is permitted, and he doesn't know, and therefore > doesn't (and can't) disclose, how to circumvent the copy protection. > > Granted, somebody could take that information and use it to figure out > how to make copies of SafeDisc protected software. The same is true of > debuggers, disassemblers, or In Circuit Emulators, which are all > legitimate engineering tools. That's just a symptom of the DMCA's > biggest problem, which is that it criminalizes perfectly legitimate > activities. The information that I disclosed (which is all the information that I have) wouldn't even help someone trying to make copies of SafeDisc protected games. I implemented a few methods of debugger detection. Some others, already implemented, are used by SafeDisc. Even after weeks of work, I haven't been able to run the executable in winedbg! Laurent Pinchart

April 29, 2002

Re: SafeDisc FAQs

by Laurent Pinchart

> Aren't you actually violating the DMCA? since you're practically reverse > engineering and making wine work with copy protection based games.. Most of my work was implementing missing features. No problem there. The only problem could be the implementation of secdrv.sys, but IMHO it doesn't violate the DMCA, as secdrv.sys doesn't protect the game againt copying, and as my implementation of SafeDisc support doesn't allow the user to play the game with a copied disc. Laurent Pinchart

April 29, 2002

Re: default windows version

by Andreas Mohr

On Mon, Apr 29, 2002 at 04:58:16PM -0300, Insyde wrote: > Hi, > I had a problem loading a second program under wine. > I called the first program with: > wine --winver win2000 pgm1 > I input a password and it wirtes a data file, unloads itself > and loads a second program. But there was an error every > time the second program was to start that send me to the > debug screen. > So I found misc/version.c line 196 that the default value to > wine load a program was WIN31, so I changed it to NT2K. > > Is there any problem doing this? If not, why is the default still > WIN31? No, it's *not*. If you examine the code more closely, then you'll notice that defaultWinVersion only gets used in case versionForced is TRUE, which is only the case once defaultWinVersion gets set to an actually specified value. I know, the code is sort of confusing if you don't examine it closely, so feel free to comment on how to improve the situation with regards to defaultWinVersion initialization (I'd like to not initialize it at all, since it isn't being used unless there's a user setting, but that's not very clean of course ;-) -- Andreas Mohr Stauferstr. 6, D-71272 Renningen, Germany Tel. +49 7159 800604 http://home.arcor.de/andi.mohr/

April 29, 2002

Re: SafeDisc FAQs

by Ori Pessach

I don't think he is. Reverse engineering for the purpose of enabling interoperability is permitted, and he doesn't know, and therefore doesn't (and can't) disclose, how to circumvent the copy protection. Granted, somebody could take that information and use it to figure out how to make copies of SafeDisc protected software. The same is true of debuggers, disassemblers, or In Circuit Emulators, which are all legitimate engineering tools. That's just a symptom of the DMCA's biggest problem, which is that it criminalizes perfectly legitimate activities. -Ori Pessach Hetz Ben Hamo wrote: > And thats in wine cvs? > > Aren't you actually violating the DMCA? since you're practically reverse > engineering and making wine work with copy protection based games.. > > Thanks, > Hetz > > On Monday 29 April 2002 22:32, Laurent Pinchart wrote: > >>Hi, >> >>For those interrested, here's a FAQs about my SafeDisc support >>implementation. >> >>Feel free to comment. >> >>Laurent Pinchart >> > >

April 29, 2002

Re: cups support apparently broken

by Huw D M Davies

On Mon, Apr 29, 2002 at 09:51:00AM -0400, Michael Cardenas wrote: > On Sat, Apr 27, 2002 at 10:53:20PM +0200, Marcus Meissner wrote: > > Actually I just did a full recompile and I am still able to print. > > (Tested using standard 32bit notepad.exe.) > > I apologize for the erroneous bug report. I didn't have libcupsys2-dev > on my machine. Now that I have that and I did a full recompile, I can > get a print dialog from word with the correct printer description, but > when I click the print button, it doesn't print. > > Printing from notepad doesn't work either, it seems to do something, and > gives me an hourglass that goes away once you move the mouse. I've > attached the output of +psdrv to this email. > > > Are you still using the same test application? Did you compile in CUPS support? > > (ldd winspooldrv.so shoud show libcups.so referenced). > > I usually use word as my test application. > > Crossover office can actually print from word, excel, outlook and ie, > but not notepad. You might want to run with +print,+winspool to check that the job is being piped to the right command. Huw.

April 29, 2002

Re: cups support apparently broken

by Marcus Meissner

On Mon, Apr 29, 2002 at 01:56:51PM -0400, Michael Cardenas wrote: > Hmmm... > > thanks huw! apparently, wine is getting the wrong print command. > > Printing from kwrite, I see this on the console: > > cmd1 = /bin/apsprint -P'eng' --format=application/postscript > --attrmultiple-document-handling=separate-documents-uncollated-copies > > whereas using +print in wine I get this message: > > trace:print:OpenJob16 'LPR:eng' 'Untitled - Notepad' 0b50 > trace:print:CreateSpoolFile Got printerSpoolCommand '|lpr -Peng' for > output device 'LPR:eng' > > trying to do an > > echo "print" | lpr -Peng > > doesn't create any output from the printer. Actually WINE assumes that a CUPS printer can be sent jobs using lpr -P<printername> on stdin. If this is not the case, you will have to change dlls/gdi/printdrv.c and dlls/winspool/info.c. Ciao, Marcus

April 29, 2002

Bugzilla: A Call to Arms

by Andriy Palamarchuk

We already had discussion on wine-devel about importance of polishing Wine, making a set of applications to work very well. Cruicial in this process is prioritizing of the issues, work distribution between developers. The companies already have internal testing and bug fixing process. Of course, each company has their own product-specific work, but most of the problems are general for Wine. I suggest to share this work more actively using Bugzilla. Recently there was some work done in cleaning the issues database and it is in pretty much usable condition. To start using bugzilla more actively I suggest following steps: 1) define subsystem/direction owners. The owners will get their system-specific bugs. They won't necessary fix the bugs themselfs, but will have complete picture about all the issues in their subsystems and coordinate the bug fixing. Developers, please let me know your areas of expertese. I can overview Wine applications. 2) more formally define process of bugs handling and use this process. There is no high qualification needed to filter out bad bug reports, duplicates, request users for more information, attach relay trace to the bug, etc, etc. Result - developers will have to spend less time on discussion trivial bugs with users, will have better bug reports to work on, users will be more involved with more active feedback. Some users are very cooperative and some bug reports are really excellent! I see that Tony Lambregts, Michael Cardenas, others do a great work with the Bugzilla database. I'm also going to contribute some time for this. 3) Prioritize bugs. This is, probably, part of (2). Some bugs, while relatively easy to fix provide very big value for the end user. Often developers do not choose such issues to work on, exactly because these issues do not present challenge to them. BTW, I do not see a field "Priority" in the bugs entries. 4) Ask users to submit there problems in Bugzilla. Submitting Bugzilla report allows us to involve users more actively, persist their bug reports. Bugzilla is a more scalable approach than using mailing list only. Of course we still will discuss bugs on the mailing lists, bug big part of communication will be unloaded. There is a lot to do and discuss. For me the goal is to have this process not worse than in Mozilla project. This is impressive: http://webtools.mozilla.org/miscstats/ http://mothra.mozilla.org/webtools/miscstats/ I also like their bug report form: http://www.mozilla.org/quality/help/bugzilla-helper.html And this is for 1 application only! I'm sure Wine can generate much bigger volume of bug reports ;-) Look forward for your comments. Andriy __________________________________________________ Do You Yahoo!? Yahoo! Health - your guide to health and wellness http://health.yahoo.com

April 29, 2002

default windows version

by Insyde

Hi, I had a problem loading a second program under wine. I called the first program with: wine --winver win2000 pgm1 I input a password and it wirtes a data file, unloads itself and loads a second program. But there was an error every time the second program was to start that send me to the debug screen. So I found misc/version.c line 196 that the default value to wine load a program was WIN31, so I changed it to NT2K. Is there any problem doing this? If not, why is the default still WIN31? Thanks, Ricardo.

April 29, 2002

Re: SafeDisc FAQs

by Hetz Ben Hamo

And thats in wine cvs? Aren't you actually violating the DMCA? since you're practically reverse engineering and making wine work with copy protection based games.. Thanks, Hetz On Monday 29 April 2002 22:32, Laurent Pinchart wrote: > Hi, > > For those interrested, here's a FAQs about my SafeDisc support > implementation. > > Feel free to comment. > > Laurent Pinchart

April 29, 2002

Re: default windows version

by Michael Cardenas

The command line options are passed. That's how the debug options get to newly created processes. On Tue, Apr 30, 2002 at 12:19:12AM +0200, Andreas Mohr wrote: > > >On Mon, Apr 29, 2002 at 04:58:16PM -0300, Insyde wrote: > > >> Hi, > > >> I had a problem loading a second program under wine. > > >> I called the first program with: > > >> wine --winver win2000 pgm1 > > >> I input a password and it wirtes a data file, unloads itself > > >> and loads a second program. But there was an error every > > >> time the second program was to start that send me to the > > >> debug screen. ... > Unless we actually pass all wine cmdline parameters (--winver, --managed etc.) > on to the wine child process (not sure about that right now, I think we do), > the new process won't use the same forced winver value as the > parent process uses. > Is this a problem ? Should this info be passed to the wineserver to globalize > it ? > > Oh, BTW: I'll rename defaultWinVersion to cmdlineWinVersion. > Much better name. > > -- > Andreas Mohr Stauferstr. 6, D-71272 Renningen, Germany > Tel. +49 7159 800604 http://home.arcor.de/andi.mohr/ > > > -- michael cardenas lead windows compatibility engineer lindows.com "Be the change you want to see in the world" -Mahatma Gandhi

April 29, 2002

SafeDisc FAQs

by Laurent Pinchart

Hi, For those interrested, here's a FAQs about my SafeDisc support implementation. Feel free to comment. Laurent Pinchart

April 29, 2002

Re: Wineconsole using all memory

by Sylvain Petreolle

> did you try to erase all registry entries and start > from > scratch ? > A+ I tried this today. result is the same and no values are saved in the registry. is this the normal behaviour ? I suggest this : if there is no HKCR\Console key, we could call WINECON_RegSave to ensure all default values are saved. ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com

April 29, 2002

Re: cups support apparently broken

by Michael Cardenas

On Mon, Apr 29, 2002 at 10:09:19PM +0200, Marcus Meissner wrote: > > trying to do an > > > > echo "print" | lpr -Peng > > Actually WINE assumes that a CUPS printer can be sent jobs using > lpr -P<printername> on stdin. > > If this is not the case, you will have to change dlls/gdi/printdrv.c > and dlls/winspool/info.c. Apparently, the correct command for cups is lp and -P needs to be replaced with -d so by changing if (!strncmp("LPR:",pszOutput,4)) sprintf(psCmd,"|lpr -P%s",pszOutput+4); to if (!strncmp("LPR:",pszOutput,4)) sprintf(psCmd,"|lp -d%s",pszOutput+4); in wine/dlls/gdi/printdrv.c it now works, but only for CUPS printers. I'll send a patch that checks the registry for a description with CUPS in it and uses lp -d if appropriate. thanks for the help. -- michael cardenas lead windows compatibility engineer lindows.com "Be the change you want to see in the world" -Mahatma Gandhi

April 29, 2002

Re: PATCH: make twain compile again

by Sylvain Petreolle

Thanks ! --- Marcus Meissner <marcus(a)jet.franken.de> a écrit : > On Mon, Apr 29, 2002 at 01:27:28AM +0200, Sylvain > Petreolle wrote: > > Hi, > > > > Following patch make wine not compile for me : > > (have last sane cvs code) > > > > gcc -c -I. -I. -I../../include -I../../include > > -I/usr/local/include -g -O2 -Wall > > -mpreferred-stack-boundary=2 -fPIC -D__WINE__ > > -D_REENTRANT -I/usr/X11R6/include -o dsm_ctrl.o > > dsm_ctrl.c > > dsm_ctrl.c: In function `TWAIN_IdentityGetFirst': > > dsm_ctrl.c:134: warning: `pSourceIdentity' might > be > > used uninitialized in this function > > dsm_ctrl.c: In function `TWAIN_OpenDSM': > > dsm_ctrl.c:367: warning: dereferencing `void *' > > pointer > > dsm_ctrl.c:367: void value not ignored as it ought > to > > be > > make[2]: *** [dsm_ctrl.o] Erreur 1 > > make[2]: Quitte le répertoire > `/home/wine/dlls/twain' > > make[1]: *** [twain/twain_32.dll.so] Erreur 2 > > make[1]: Quitte le répertoire `/home/wine/dlls' > > make: *** [dlls] Erreur 2 > > The patch is not yet applied. If you apply it, it > will compile again. > > (It got broken by something else.) > > Ciao, Marcus ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com

April 29, 2002