May 2002 - Wine-devel - list.winehq.org

Re: PATCH: error message if winedefault.reg is not loaded
by Andriy Palamarchuk 16 May '02

16 May '02

--- Marcus Meissner <marcus(a)jet.franken.de> wrote: [skipped] > + MESSAGE("\nERROR: You need to merge the > 'winedefault.reg' file into your\n"); > + MESSAGE(" WINE registry by running: `regapi > setValue < winedefault.reg'!\n\n"); > + } else { Marcus, we have already regedit (based on regapi), so the old regapi application is obsolete. Regedit call in this case will be as: regedit winedefault.reg Andriy __________________________________________________ Do You Yahoo!? LAUNCH - Your Yahoo! Music Experience http://launch.yahoo.com

1 0

Migrating from winehq.com to winehq.org in files
by Vincent Béron 16 May '02

16 May '02

This patch is to replace all the instances of winehq.com by winehq.org in the various files of the Wine distribution: documentation, comments, etc. There's also one pointer to appdb.codeweavers.com changed to appdb.winehq.org. I didn't touch at the ChangeLog and ChangeLog.Old files, and to an old email from Alexandre in documentation/HOWTO-Winelib, as I don't think it's a good idea to change such things. A similar patch has also been sent to web-admin(a)winehq.org, to change the files on the website. After the application of both, the only remaining thing would be the name of the CVS module (Winehq_com). Please comment. Vincent diff -urN wine-orig/ANNOUNCE wine/ANNOUNCE --- wine-orig/ANNOUNCE Fri May 10 08:40:00 2002 +++ wine/ANNOUNCE Wed May 15 22:44:46 2002 @@ -3,7 +3,7 @@ and unimplemented features. Most applications still do not work correctly. -Patches should be submitted to "wine-patches(a)winehq.com". Please don't +Patches should be submitted to "wine-patches(a)winehq.org". Please don't forget to include a ChangeLog entry. WHAT'S NEW with Wine-20020509: (see ChangeLog for details) @@ -32,7 +32,7 @@ and wine-doc.ps.gz. You can also get the current source directly from the CVS tree. Check -http://www.winehq.com/development/ for details. +http://www.winehq.org/development/ for details. If you submitted a patch, please check to make sure it has been included in the new release. @@ -46,4 +46,4 @@ -- Alexandre Julliard -julliard(a)winehq.com +julliard(a)winehq.org diff -urN wine-orig/BUGS wine/BUGS --- wine-orig/BUGS Sun May 5 22:41:48 2002 +++ wine/BUGS Wed May 15 22:47:42 2002 @@ -8,7 +8,7 @@ If you want to help Wine project you can: - * visit Bugzilla (http://bugs.winehq.com/) for + * visit Bugzilla (http://bugs.winehq.org/) for list of existing bugs. Metabug 406 lists bugs which are reasonably simple to fix even for someone new to Wine. Have a look at it and choose subject you are insterested in. @@ -26,7 +26,7 @@ * run Windows applications, port open-source Windows applications to Wine, fix bugs you found, enter bugs you can't fix to Bugzilla. Enter information you discovered to the - Wine Application Database (http://appdb.codeweavers.com/) + Wine Application Database (http://appdb.winehq.org/) * grep for FIXME in the source files diff -urN wine-orig/README wine/README --- wine-orig/README Fri May 10 08:40:00 2002 +++ wine/README Wed May 15 22:46:22 2002 @@ -22,7 +22,7 @@ problem resolution, read the rest of this file, the Wine man page, the files in the documentation directory of the Wine source (see "DOCUMENTATION"), and especially the wealth of information -found at http://www.winehq.com. +found at http://www.winehq.org. 3. REQUIREMENTS @@ -141,7 +141,7 @@ Don't forget to add vital registry entries by applying winedefault.reg with programs/regapi/. See documentation/ directory for details. -See http://www.winehq.com/support/ for further configuration hints. +See http://www.winehq.org/support/ for further configuration hints. In case of library loading errors (e.g. "Error while loading shared libraries: libntdll.so"), make sure @@ -202,15 +202,15 @@ 8. GETTING MORE INFORMATION WWW: A great deal of information about Wine is available from WineHQ at - http://www.winehq.com/ : various Wine Guides, application database, + http://www.winehq.org/ : various Wine Guides, application database, bug tracking. This is probably the best starting point. -FAQ: The Wine FAQ is located at http://www.winehq.com/FAQ +FAQ: The Wine FAQ is located at http://www.winehq.org/FAQ Usenet: You can discuss Wine-related issues and get help on comp.emulators.ms-windows.wine. -Bugs: Report bugs to Wine Bugzilla at http://bugs.winehq.com/. +Bugs: Report bugs to Wine Bugzilla at http://bugs.winehq.org/. Please search the bugzilla database to check whether your problem is already found before posting a bug report. You can also post bug reports to comp.emulators.ms-windows.wine. @@ -223,16 +223,16 @@ IRC: Online help is available at channel #WineHQ on irc.openprojects.net. CVS: The current Wine development tree is available through CVS. - Go to http://www.winehq.com/development/ for more information. + Go to http://www.winehq.org/development/ for more information. Mailing lists: There are several mailing lists for Wine developers; see - http://www.winehq.com/development/#ml for more information. + http://www.winehq.org/development/#ml for more information. If you add something, or fix a bug, please send a patch (in 'diff -u' -format) to wine-patches(a)winehq.com list for inclusion in the next +format) to wine-patches(a)winehq.org list for inclusion in the next release. -- Alexandre Julliard -julliard(a)winehq.com +julliard(a)winehq.org diff -urN wine-orig/documentation/HOWTO-winelib wine/documentation/HOWTO-winelib --- wine-orig/documentation/HOWTO-winelib Sat Feb 2 13:03:55 2002 +++ wine/documentation/HOWTO-winelib Wed May 15 22:35:49 2002 @@ -774,7 +774,7 @@ THANKS Most of the information in this file came from postings on -<Wine-devel(a)Winehq.com> and from private e-mails. The following people +<Wine-devel(a)winehq.org> and from private e-mails. The following people contributed information for this document and I thank them for their time and effort in answering my questions. I also want to thank them for encouraging me to attack the MFC problem. diff -urN wine-orig/documentation/authors.ent wine/documentation/authors.ent --- wine-orig/documentation/authors.ent Wed Dec 13 16:52:37 2000 +++ wine/documentation/authors.ent Wed May 15 22:32:15 2002 @@ -32,7 +32,7 @@ <!entity email-james-juran "juran(a)cse.psu.edu"> <!entity name-ove-kaaven "Ove Kåven"> -<!entity email-ove-kaaven "ovek(a)winehq.com"> +<!entity email-ove-kaaven "ovek(a)winehq.org"> <!entity name-eric-kohl "Eric Kohl"> <!entity email-eric-kohl "ekohl(a)abo.rhein-zeitung.de"> @@ -73,7 +73,7 @@ <!entity email-john-richardson "jrichard(a)zko.dec.com"> <!entity name-douglas-ridgway "Douglas Ridgway"> -<!entity email-douglas-ridgway "ridgway(a)winehq.com"> +<!entity email-douglas-ridgway "ridgway(a)winehq.org"> <!entity name-adam-sacarny "Adam Sacarny"> <!entity email-adam-sacarny "magicbox(a)bestweb.net"> diff -urN wine-orig/documentation/bugs.sgml wine/documentation/bugs.sgml --- wine-orig/documentation/bugs.sgml Sun May 5 22:41:49 2002 +++ wine/documentation/bugs.sgml Wed May 15 22:32:36 2002 @@ -21,7 +21,7 @@ </para> <para> With using either approach report the found issues with relevant - <ulink url="http://bugs.winehq.com/">Wine Bugzilla</ulink>. + <ulink url="http://bugs.winehq.org/">Wine Bugzilla</ulink>. </para> <sect2> @@ -54,7 +54,7 @@ <listitem> <para> Post the bug to - <ulink url="http://bugs.winehq.com/">Wine Bugzilla</ulink>. + <ulink url="http://bugs.winehq.org/">Wine Bugzilla</ulink>. Please, search Bugzilla database to check whether your problem is already found before posting a bug report. Include your own detailed description of the problem with @@ -196,7 +196,7 @@ <listitem> <para> Post the bug to - <ulink url="http://bugs.winehq.com/">Wine Bugzilla</ulink>. + <ulink url="http://bugs.winehq.org/">Wine Bugzilla</ulink>. Please, search Bugzilla database to check whether your problem is </para> <para> @@ -215,7 +215,7 @@ If after reading this document there is something you couldn't figure out, or think could be explained better, or that should have been included, please post to - <ulink url="http://bugs.winehq.com/">Wine Bugzilla</ulink> to + <ulink url="http://bugs.winehq.org/">Wine Bugzilla</ulink> to let us know how this document can be improved. </para> </sect2> diff -urN wine-orig/documentation/configuring.sgml wine/documentation/configuring.sgml --- wine-orig/documentation/configuring.sgml Wed May 8 21:04:46 2002 +++ wine/documentation/configuring.sgml Wed May 15 22:32:57 2002 @@ -930,7 +930,7 @@ <para> There is always a chance that things will go wrong. If the unthinkable happens report the problem to - <ulink url="http://bugs.winehq.com/">Wine Bugzilla</ulink>, + <ulink url="http://bugs.winehq.org/">Wine Bugzilla</ulink>, try the newsgroup <systemitem>comp.emulators.ms-windows.wine</systemitem>, or the IRCnet channel <systemitem>#WineHQ</systemitem> found on @@ -2012,7 +2012,7 @@ <para> from your main Wine directory, then submit <filename>layout.diff</filename> to - <email>wine-patches(a)winehq.com</email> along with a brief note + <email>wine-patches(a)winehq.org</email> along with a brief note of what it is. </para> <para> diff -urN wine-orig/documentation/cvs-regression.sgml wine/documentation/cvs-regression.sgml --- wine-orig/documentation/cvs-regression.sgml Tue Oct 16 17:47:51 2001 +++ wine/documentation/cvs-regression.sgml Wed May 15 22:33:23 2002 @@ -63,7 +63,7 @@ </para> <note> <para> - If you use Cvs directly from the winehq.com server, do not + If you use Cvs directly from the winehq.org server, do not forget to add to your <filename>.cvsrc</filename> file: </para> <screen> @@ -87,7 +87,7 @@ The date format is <literal>YYYY-MM-DD HH:MM:SS</literal>. Using the EDT date format ensure that you will be able to extract patches in a way that will be compatible with the - wine-cvs archive : http://www.winehq.com/hypermail/wine-cvs + wine-cvs archive : http://www.winehq.org/hypermail/wine-cvs </para> <para> Many messages will inform you that more recent files have diff -urN wine-orig/documentation/documentation.sgml wine/documentation/documentation.sgml --- wine-orig/documentation/documentation.sgml Tue Oct 2 13:48:16 2001 +++ wine/documentation/documentation.sgml Wed May 15 22:33:41 2002 @@ -953,7 +953,7 @@ <listitem> <para> Hyperlink in URL form, e.g., <ulink - url="http://www.winehq.com">http://www.winehq.com</ulink>. + url="http://www.winehq.org">http://www.winehq.org</ulink>. </para> </listitem> </varlistentry> diff -urN wine-orig/documentation/fonts.sgml wine/documentation/fonts.sgml --- wine-orig/documentation/fonts.sgml Fri May 10 08:40:00 2002 +++ wine/documentation/fonts.sgml Wed May 15 22:33:53 2002 @@ -18,7 +18,7 @@ Wine. It can be found in the <filename>tools</filename> directory. Links to the other tools mentioned in this document can be found on wine headquarters: - <ulink url="http://www.winehq.com/development/">http://www.winehq.com/development/</ulink> + <ulink url="http://www.winehq.org/development/">http://www.winehq.org/development/</ulink> </para> </note> </para> diff -urN wine-orig/documentation/getting.sgml wine/documentation/getting.sgml --- wine-orig/documentation/getting.sgml Fri May 10 08:40:00 2002 +++ wine/documentation/getting.sgml Wed May 15 22:35:02 2002 @@ -46,7 +46,7 @@ Finally, you may someday need to know how to apply a source code patch to your version of Wine. Perhaps you've uncovered a bug in Wine, reported it to the <ulink - url="mailto:wine-devel(a)winehq.com">Wine mailing list</ulink>, + url="mailto:wine-devel(a)winehq.org">Wine mailing list</ulink>, and received a patch from a developer to hopefully fix the bug. The last section in this chapter will show you how to <link linkend="getting-upgrading">safely apply the @@ -131,7 +131,7 @@ <para> The first place you should look if your system isn't Debian or Redhat is the <ulink - url="http://www.winehq.com/download/">WineHQ Download + url="http://www.winehq.org/download/">WineHQ Download Page</ulink>. This page lists many assorted archives of binary (precompiled) Wine files. </para> @@ -160,7 +160,7 @@ <para> The safest way to grab the source is from one of the official FTP archives. An up to date listing is in the <ulink - url="http://www.winehq.com/source/ANNOUNCE">ANNOUNCE </ulink> + url="http://www.winehq.org/source/ANNOUNCE">ANNOUNCE </ulink> file in the Wine distribution (which you would have if you already downloaded it). Here is a (possibly out of date) list of FTP servers carrying Wine: @@ -212,8 +212,8 @@ <para> The official web page for Wine CVS is - <ulink url="http://www.winehq.com/development/"> - http://www.winehq.com/development/</ulink>. + <ulink url="http://www.winehq.org/development/"> + http://www.winehq.org/development/</ulink>. </para> <para> First, you need to get a copy of the latest Wine sources @@ -223,14 +223,14 @@ <command>bash</command>, it might look something like this: </para> <screen> -$ export CVSROOT=:pserver:cvs(a)cvs.winehq.com:/home/wine +$ export CVSROOT=:pserver:cvs(a)cvs.winehq.org:/home/wine $ cvs login Password: cvs $ cvs checkout wine </screen> <para> That'll pull down the entire Wine source tree from - winehq.com and place it in the current directory (actually + winehq.org and place it in the current directory (actually in the 'wine' subdirectory). CVS has a million command line parameters, so there are many ways to pull down files, from anywhere in the revision history. Later, you can grab just @@ -278,7 +278,7 @@ distribution, you have the option of applying patches to the source tree to fix bugs and add experimental features. Perhaps you've found a bug, reported it to the <ulink - url="mailto:wine-devel(a)winehq.com">Wine mailing list</ulink>, + url="mailto:wine-devel(a)winehq.org">Wine mailing list</ulink>, and received a patch file to fix the bug. You can apply the patch with the <command>patch</command> command, which takes a streamed patch from <filename>stdin</filename>: diff -urN wine-orig/documentation/installation-und-konfiguration.german wine/documentation/installation-und-konfiguration.german --- wine-orig/documentation/installation-und-konfiguration.german Fri May 10 08:40:00 2002 +++ wine/documentation/installation-und-konfiguration.german Wed May 15 22:36:14 2002 @@ -254,7 +254,7 @@ Verwendung der Bash kann dazu der folgende Befehl eingegeben werden: - export CVSROOT=:pserver:cvs(a)cvs.winehq.com:/home/wine + export CVSROOT=:pserver:cvs(a)cvs.winehq.org:/home/wine Danach kann man sich bei dem CVS-Server anmelden. Hierzu dient dieser Befehl: @@ -284,7 +284,7 @@ u.a. in der Manualseite zu cvs(1) sowie auf der CVS-Homepage, die unter http://www.sourcegear.com/CVS zu erreichen ist. Weitere wichtige Hinweise im Hinblick auf CVS und WINE sind unter der Adresse - http://www.winehq.com/development/ verfügbar. + http://www.winehq.org/development/ verfügbar. 6.0 Konfiguration und Übersetzung des Quellcodes @@ -2088,6 +2088,6 @@ Weiterführende Informationen Die zentrale Web-Adresse für Informationen zu WINE ist - http://www.winehq.com. Dort befinden sich Links zu vielen weiteren + http://www.winehq.org. Dort befinden sich Links zu vielen weiteren Dokumenten, wie einem WINE-FAQ, einem WINE-HOWTO, einer Anleitung zum Erstellen von Fehlerberichten und vieles mehr. diff -urN wine-orig/documentation/make_winehq wine/documentation/make_winehq --- wine-orig/documentation/make_winehq Tue Jan 29 12:52:29 2002 +++ wine/documentation/make_winehq Wed May 15 22:36:42 2002 @@ -3,7 +3,7 @@ ## John R. Sheets <jsheets(a)codeweavers.com> ## This is a convenience script for building the website docs for -## www.winehq.com. It creates tarballs of the HTML with special +## www.winehq.org. It creates tarballs of the HTML with special ## server-side includes and CSS settings that aren't appropriate for ## the mainline Wine tree. For this reason, and to make it easier to ## set up an automated website update system, I'm putting this in @@ -18,7 +18,7 @@ ## $ ./make_winehq ## $ rsync ... -WWWDIR=www.winehq.com +WWWDIR=www.winehq.org ## Want to put this into a sub-directory for easier maintenance if [ -d "$WWWDIR" -o -f "$WWWDIR" ]; then rm -rf "$WWWDIR.old" @@ -76,7 +76,7 @@ ## Done creating downloadable tarballs for users. Now we want to ## create a tarball of SHTML in a slightly different form, for the ## website. These versions use special server-side includes which -## aren't appropriate outside of winehq.com. +## aren't appropriate outside of winehq.org. ## ## Use the special website stylesheet export WINEDOC_STYLESHEET=../winehq.dsl diff -urN wine-orig/documentation/packaging.sgml wine/documentation/packaging.sgml --- wine-orig/documentation/packaging.sgml Tue Apr 30 20:46:05 2002 +++ wine/documentation/packaging.sgml Wed May 15 22:37:00 2002 @@ -850,7 +850,7 @@ For an excellent overview of this issue, read this - <ulink url="http://www.winehq.com/News/2000-25.html#FTR"> + <ulink url="http://www.winehq.org/News/2000-25.html#FTR"> Wine Weekly News feature.</ulink> </para> diff -urN wine-orig/documentation/wine.man.in wine/documentation/wine.man.in --- wine-orig/documentation/wine.man.in Fri May 10 08:40:00 2002 +++ wine/documentation/wine.man.in Wed May 15 22:38:32 2002 @@ -307,11 +307,11 @@ .SH BUGS .PP A status report on many applications is available from -.I http://www.winehq.com/Apps. +.I http://appdb.winehq.org/. Please add entries to this list for applications you currently run. .PP Bug reports may be posted to Wine Bugzilla -.I http://bugs.winehq.com +.I http://bugs.winehq.org If you want to post a bug report, please read the file .I documentation/bugs.sgml in the @@ -319,7 +319,7 @@ source to see what information is necessary .PP Problems and suggestions with this manpage please also report to -.I http://bugs.winehq.com +.I http://bugs.winehq.org .SH AVAILABILITY The most recent public version of .B wine @@ -333,12 +333,12 @@ The latest snapshot of the code may be obtained via CVS. For information on how to do this, please see .I -http://www.winehq.com/development/ +http://www.winehq.org/development/ .PP WineHQ, the .B wine development headquarters, is at -.I http://www.winehq.com/. +.I http://www.winehq.org/. This website contains a great deal of information about .B wine. .PP @@ -354,7 +354,7 @@ development, you might want to subscribe to the .B wine mailing lists at -.I http://www.winehq.com/development/#ml +.I http://www.winehq.org/development/#ml .SH FILES .PD 0 .TP diff -urN wine-orig/documentation/wine.texinfo wine/documentation/wine.texinfo --- wine-orig/documentation/wine.texinfo Mon Mar 18 21:10:35 2002 +++ wine/documentation/wine.texinfo Wed May 15 22:40:35 2002 @@ -340,7 +340,7 @@ The overall coordination is done by @* Alexandre Julliard @* -(a)email{julliard@@winehq.com} +(a)email{julliard@@winehq.org} @@ -405,7 +405,7 @@ The Wine USENET newsgroup @url{news:comp.emulators.ms-windows.wine} is useful for both Wine developers and Wine users. The Wine home page -is @url{http://www.winehq.com/}. +is @url{http://www.winehq.org/}. @node Wine Design, Reference Manual, Introduction, Top @chapter Wine Design @@ -1658,7 +1658,7 @@ patches}, for details. @item -Mail the patch to Alexandre Julliard, @email{julliard@@winehq.com}. +Mail the patch to the wine-devel mailing list, @email{wine-devel@@winehq.org}. @item Wait for the patch to appear in the official distribution. @@ -1731,7 +1731,7 @@ patches}, for details. @item -Mail the patch to Alexandre Julliard, @email{julliard@@winehq.com}. +Mail the patch to the wine-devel mailing list, @email{wine-devel@@winehq.org}. @item Wait for the patch to appear in the official distribution. diff -urN wine-orig/documentation/winelib-bindlls.sgml wine/documentation/winelib-bindlls.sgml --- wine-orig/documentation/winelib-bindlls.sgml Tue Oct 2 13:48:16 2001 +++ wine/documentation/winelib-bindlls.sgml Wed May 15 22:37:17 2002 @@ -85,7 +85,7 @@ # linux library libMyLinux) # # For further details of wine spec files see the Winelib documentation at -# www.winehq.com +# www.winehq.org name MyWin type win32 diff -urN wine-orig/documentation/winelib-porting.sgml wine/documentation/winelib-porting.sgml --- wine-orig/documentation/winelib-porting.sgml Fri May 18 17:01:44 2001 +++ wine/documentation/winelib-porting.sgml Wed May 15 22:37:26 2002 @@ -279,7 +279,7 @@ <para> If you come across a difference between the Windows headers and Wine's that breaks compilation, try asking for help on - <email>wine-devel(a)winehq.com</email>. + <email>wine-devel(a)winehq.org</email>. </para> </sect1> diff -urN wine-orig/programs/notepad/README wine/programs/notepad/README --- wine-orig/programs/notepad/README Wed Mar 20 17:55:46 2002 +++ wine/programs/notepad/README Wed May 15 22:51:10 2002 @@ -13,4 +13,4 @@ Please see file TODO for things to do and keep the file ChangeLog up to date. -I also try to read wine-devel(a)winehq.com frequently. +I also try to read wine-devel(a)winehq.org frequently. diff -urN wine-orig/programs/notepad/main.h wine/programs/notepad/main.h --- wine-orig/programs/notepad/main.h Wed Mar 20 17:55:46 2002 +++ wine/programs/notepad/main.h Wed May 15 22:51:22 2002 @@ -31,7 +31,7 @@ /* hide the following from winerc */ #ifndef RC_INVOKED -#define WINE_RELEASE_INFO "Wine (www.winehq.com)" +#define WINE_RELEASE_INFO "Wine (www.winehq.org)" #include "commdlg.h" diff -urN wine-orig/tools/bug_report.pl wine/tools/bug_report.pl --- wine-orig/tools/bug_report.pl Wed May 8 21:04:47 2002 +++ wine/tools/bug_report.pl Wed May 15 22:52:13 2002 @@ -75,7 +75,7 @@ the second has *all* of the debug output, which can go to thousands of lines. To (hopefully) get the bug fixed, report it to the project - bug tracking system at http://bugs.winehq.com. + bug tracking system at http://bugs.winehq.org. Attach the first file to the bug description. Also include detailed description of the problem. The developers might ask you for "the last X lines from the report". If so, just @@ -567,7 +567,7 @@ }; $var30 = qq{ Having problems with the script? -Submit a bug report to Wine bugtracking system at http://bugs.winehq.com or +Submit a bug report to Wine bugtracking system at http://bugs.winehq.org or tell the wine newsgroup (comp.emulators.ms-windows.wine). }; print do_var($var22); diff -urN wine-orig/tools/genpatch wine/tools/genpatch --- wine-orig/tools/genpatch Sat Mar 9 19:24:22 2002 +++ wine/tools/genpatch Wed May 15 22:52:33 2002 @@ -1,7 +1,7 @@ #!/usr/bin/perl # # genpatch - A utility that generates patches for submission to -# wine-patches(a)winehq.com +# wine-patches(a)winehq.org # # Copyright Steven Elliott <elliotsl(a)mindspring.com> # @@ -23,7 +23,7 @@ =head1 NAME genpatch - A utility that generates patches for submission to -wine-patches(a)winehq.com +wine-patches(a)winehq.org =head1 SYNOPSIS diff -urN wine-orig/tools/winedump/winedump.h wine/tools/winedump/winedump.h --- wine-orig/tools/winedump/winedump.h Sat Mar 9 19:24:24 2002 +++ wine/tools/winedump/winedump.h Wed May 15 22:53:10 2002 @@ -20,7 +20,7 @@ * References: * DLL symbol extraction based on file format from alib (anthonyw.cjb.net) * - * Option processing shamelessly cadged from winebuild (www.winehq.com) + * Option processing shamelessly cadged from winebuild (www.winehq.org) * * All the cool functionality (prototyping, call tracing, forwarding) * relies on Patrik Stridvall's 'function_grep.pl' script to work. diff -urN wine-orig/tools/wineinstall wine/tools/wineinstall --- wine-orig/tools/wineinstall Wed May 15 22:28:46 2002 +++ wine/tools/wineinstall Wed May 15 22:52:55 2002 @@ -363,7 +363,7 @@ echo "'$sucommand' correctly." echo "If you didn't enter an incorrect password then please report this" echo "error and any steps to possibly reproduce it to" - echo "http://bugs.winehq.com/" + echo "http://bugs.winehq.org/" echo echo "Installation failed, aborting." exit 1 diff -urN wine-orig/tools/wmc/wmc.man wine/tools/wmc/wmc.man --- wine-orig/tools/wmc/wmc.man Tue Jun 13 00:34:42 2000 +++ wine/tools/wmc/wmc.man Wed May 15 22:53:20 2002 @@ -97,7 +97,7 @@ WineHQ, the .B wine development headquarters, at -.I http://www.winehq.com/. +.I http://www.winehq.org/. .SH "SEE ALSO" .BR wine (1), .BR wrc (1) diff -urN wine-orig/tools/wrc/wrc.man wine/tools/wrc/wrc.man --- wine-orig/tools/wrc/wrc.man Fri Aug 25 17:32:18 2000 +++ wine/tools/wrc/wrc.man Wed May 15 22:53:29 2002 @@ -226,6 +226,6 @@ WineHQ, the .B wine development headquarters, at -.I http://www.winehq.com/. +.I http://www.winehq.org/. .SH "SEE ALSO" .BR wine (1),

1 0

talk-through dll
by Lonnie Cumberland 16 May '02

16 May '02

Hello All, I have been reading over the Wine documentation but have not come across this yet. I am interested in having a windows DLL that can access some functions native to Linux. For instance, possibly an application under wine that allows me to add a new user to my Linux box. My guess is that I should be able to write up a windows dll that will talk to Linux. Is this correct? If so then where in the Wine docs can I read more about the specifics of how this can be done? Thanks in advance, Lonnie

3 5

Re: wine/ ./Make.rules.in debugger/.cvsignore dlls ...
by Eric Pouech 15 May '02

15 May '02

> Added winebuild support for generating a .dbg.c file containing the > debug channels definitions. > Made win32 the default type for spec files. > Ignore C compiler in winebuild so we can simply pass it $(DEFS). > Removed type win32 and debug_channels from spec files. > Fixed winebuild to always generate correct C identifiers (reported by > Vincent Béron). > one comment about this patch: the c correct identifier isn't perfect (program name can start with a digit, whereas C ident can't) A+

2 1

Getpagesize in libwine port.c on windows target
by Steven Edwards 15 May '02

15 May '02

I have two fixes for missing getpagesize on windows. Once this is done the only thing that is stopping me from building libwine is the missing refrences to _assert and _errorno. 1. In xemacs they #define getpagesize() 4096 and it seems to work. 2. The other fix would be to use getsystem_info. I just can't make the Getsystem_info workaround to work right. Here is a example. /* getpagesize for windows */ long getpagesize (void) { static long g_pagesize = 0; if (! g_pagesize) { SYSTEM_INFO system_info; GetSystemInfo (&system_info); g_pagesize = system_info.dwPageSize; } return g_pagesize; } "Every revolution was once a thought in one man's mind" - Ralph Waldo Emerson

1 0

More GDI heap problems: How to report this as bug ?
by Gregor Hoffleit 15 May '02

15 May '02

I try to run the Brockhaus multimedial encyclopedia with Wine (Debian package 0.0.20020411-1). At a certain point (when an article is going to be displayed), the program continuously spits out these messages about the GDI heap being full: ... err:local:LOCAL_GetBlock not enough space in GDI heap 01ff for 1048 bytes err:local:LOCAL_GetBlock not enough space in GDI heap 01ff for 1048 bytes err:local:LOCAL_GetBlock not enough space in GDI heap 01ff for 1048 bytes err:local:LOCAL_GetBlock not enough space in GDI heap 01ff for 880 bytes err:local:LOCAL_GetBlock not enough space in GDI heap 01ff for 1048 bytes err:local:LOCAL_GetBlock not enough space in GDI heap 01ff for 20 bytes err:local:LOCAL_GetBlock not enough space in GDI heap 01ff for 20 bytes err:local:LOCAL_GetBlock not enough space in GDI heap 01ff for 1048 bytes err:local:LOCAL_GetBlock not enough space in GDI heap 01ff for 20 bytes err:local:LOCAL_GetBlock not enough space in GDI heap 01ff for 20 bytes err:local:LOCAL_GetBlock not enough space in GDI heap 01ff for 20 bytes err:local:LOCAL_GetBlock not enough space in GDI heap 01ff for 20 bytes err:region:CombineRgn Invalid rgn=0000 err:local:LOCAL_GetBlock not enough space in GDI heap 01ff for 1048 bytes err:local:LOCAL_GetBlock not enough space in GDI heap 01ff for 1048 bytes err:local:LOCAL_GetBlock not enough space in GDI heap 01ff for 20 bytes err:region:CombineRgn Invalid rgn=0000 err:local:LOCAL_GetBlock not enough space in GDI heap 01ff for 20 bytes err:region:CombineRgn Invalid rgn=0000 ... The application nearly comes to a hold: with much luck, portions of the display still get updated. I've seen previous reports about this problems, and appearently they are indications of leaks either in Wine's GDI objects or in some other component. How can I help tracking down these specifc leaks ? The leaks are very obvious and very good reproducable. They happen almost immediately after opening the article. I tried "--debugmsg +relay,+local", but after a few seconds, the log file filled up 100MB! I'm no Windows programmer, and I've only little experience with Wine, but if somebody could tell me how to make a proper and helpful bug report and what else could help to track down the problem, I'd be very glad. Please keep me cc'ed, since I'm not subscribed to wine-devel for the moment. Thanks, Gregor

4 5

Component owners 2
by Andriy Palamarchuk 15 May '02

15 May '02

Thanks everybody for the very active feedback. List of developers who contacted me: * Guy L. Albetelli - common controls * Robert 'Admiral' Coeyman - DOS * Huw Davies - TrueType support, printing, gdi * Francois Gouget - Winelib, Winemaker, headers, icmp * Dustin Navea - wine tools * Mike McCormack - file system, serial port, named pipes, SMB * Marcus Meissner - COM, OLE * Andreas Mohr - documentation, installers, memory handling * Andriy Palamarchuk - wine applications * Juergen Schmied - console, file open dialog Developers who has not confirmed nor declined suggestion to own a component: * Alexandre Julliard - wineserver, kernel, IPC * Laurent Pinchart - copy protection * Dmitry Timoshkov - NLS, Unicode, keyboard I/O * Martin Wick - sockets Still available components: * DDE * loader * msvcrt * x11drv * window handling Some developers are interested by areas which are not components per se. For example - Andreas Mohr worked a lot on installers issues and would like installer bugs forwarded to him. The issue will be forwarded to a person who is the most interested in an issue. Everybody else is also welcome to give me your particular areas of interest even if they do not match component boundaries. All the developers, QA engineers who is going to work with Bugzilla, please create an account and request privileges to change bugs status at bugs(a)codeweavers.com. You do not need to subscribe to wine-bugs if you are not planning to work in the first line of the bugs hanlding (handling of bugs with status UNCONFIRMED). Please, let me know if I missed anybody. Other comments are welcome too. Andriy __________________________________________________ Do You Yahoo!? LAUNCH - Your Yahoo! Music Experience http://launch.yahoo.com

5 8

Re: PlaySound and al.
by tijs＠connectux.com 15 May '02

15 May '02

Eric Pouech <eric.pouech(a)wanadoo.fr> writes: > this patch is a rewrite of the playsound functions those were a bit > buggy and proved to fail in some multi-threaded environments the > attached patch should take care of that >snip When selecting a menu-item in MSVC++ 6.0, the loop in MULTIMEDIA_PlaySound() never ends on my system (Debian unstable, no soundcard) as well as on another system (Debian unstable, soundblaster installed). Things worked fine with revision 1.51 of mmsystem.c. Unfortunately, I haven't been able to trace exactly what is going wrong. I will, of course, supply more details when I find something remarkable. Should I report bugs with respect to patches using Bugzilla, or is wine-devel sufficient? I noticed Bugzilla only allows me to select real Wine releases, i.e. 20020509, and not a CVS revision of a certain file. Regards, -- Tijs van Bakel, ConnecTUX, <tijs(a)connectux.com>

3 2

Bugzilla responsibilities (Was Component owners 2)
by Andriy Palamarchuk 15 May '02

15 May '02

I decided to define not also list of component owners, but also people, responsible for triaging and application owners. This additional information will be important for those who work with Bugzilla. I'm going to submit these lists for publishing on Wine Bugzilla pages for easy access. Owners of Components and areas of interest: * Guy L. Albetelli - common controls * Robert 'Admiral' Coeyman - DOS * Chuck Crayne - richedit * Huw Davies - TrueType support, printing, gdi, x11 gdi * Francois Gouget - Winelib, Winemaker, headers, icmp * Alexandre Julliard - wineserver, kernel, IPC, loader, x11drv * Dustin Navea - wine tools * Mike McCormack - file system, serial port, named pipes, SMB * Marcus Meissner - COM, OLE * Andreas Mohr - documentation, installers, memory handling * Andriy Palamarchuk - wine applications * Eric Pouech - multimedia, winedbg, wineconsole, DDE * Juergen Schmied - shell (shell32.dll and shlwapi.dll), file open dialog * Lionel Ulmer - OpenGL, DirectX, Direct3D * Martin Wilck - sockets People in the list below are responsible for fixes confirmation, bugs confirmation, initial research, distribution to developers, prioritization. Please, let me know if you plan to actively work in this area - I'll include you in the list. Bugs triaging: * Tony Lambregts * Andreas Mohr (SWAT team ;-) * Dustin Navea * Andriy Palamarchuk Contributors are wanted! Application owners can provide help in confirming bugs, fixes, assisting developers who do not have access to the application in bugs fixing. Application owners: * Michael Cardenas - Microsoft Office, AOL Application owners are wanted! As always I appreciate your comments. Andriy __________________________________________________ Do You Yahoo!? LAUNCH - Your Yahoo! Music Experience http://launch.yahoo.com

1 0

RE: Unhandled exception in old DOS application
by Medland, Bill 15 May '02

15 May '02

> -----Original Message----- > From: M.H.VanLeeuwen [mailto:vanl(a)megsinet.net] > Sent: Monday, May 13, 2002 7:33 PM > To: wine-devel(a)winehq.com > Subject: Unhandled exception in old DOS application > > > Hi, > > I hope this is the correct place to ask... > > Up until the 20020411 wine release my old DOS application > worked well...for the > last ~2 years. (Thanks all of you!) > With both 20020411 and 20020509 releases the wine issues an > Unhandled exception > report and starts the debugger. > > bash-2.05$ wine cardload.exe -- -a340 > -f"c:\\\winapps\\\winphone\\\cardload.hex" > Could not stat /mnt/fd0 (No such file or directory), ignoring drive A: > Warning: unprotecting the first 64KB of memory to allow > real-mode calls. > NULL pointer accesses will no longer be caught. > wine: Unhandled exception, starting debugger... > err:int:DOSVM_Loop MsgWaitForMultipleObjects returned > unexpected value. > > This application just downloads firmware (cardload.hex) to an > old ISA card. > > What can be done to fix this, where should I begin looking to > fix it, who The first thing I'd do is see which "fix" broke it. That requires getting the code out of the cvs itself. Basically I do an almost binary search between when I know it "worked" and when I know it failed and what area of code was affected. >From your post I presume you don't get the code from the cvs. Do you compile yourself or dowload rpms? Bill

2 1