- wine-devel - winehq.org

Re: resend update to sgml documentation
by Dustin Navea 10 Nov '02

10 Nov '02

Hmm, wonder where the "generic steps to get output from sgml" came from??? ;) *hint hint* *wink wink* ;P -Dustin --- Tony Lambregts <tony_lambregts(a)telusplanet.net> wrote: > Since the last patch looked really screwed up I am resending with .txt > extention > > Hopfully this makes it easier for others to set up their docbook > environment and encourage more people to write documentation it is not > complete but at least it is a start. > > change log: make the instructions of how to install sgml easier to > understand . > > files changed: > documentation/documentation.sgml > documentation/authors.ent > > -- > > Tony Lambregts > > > Index: documentation.sgml > =================================================================== > RCS file: /home/wine/wine/documentation/documentation.sgml,v > retrieving revision 1.4 > diff -u -r1.4 documentation.sgml > --- documentation.sgml 2 Oct 2001 17:48:16 -0000 1.4 > +++ documentation.sgml 9 Nov 2002 04:00:59 -0000 > @@ -86,6 +86,9 @@ > <para> > Written by &name-john-sheets; <email>&email-john-sheets;</email> > </para> > + <para> > + Modified by &name-tony-lambregts; > <email>&email-tony-lambregts;</email> Nov. 2002 > + </para> > > <sect2 id="writing-docbook"> > <title>Writing Documentation with DocBook</title> > @@ -98,7 +101,123 @@ > DocBook markup looks very similar to HTML markup, although > the names of the markup tags differ. > </para> > + <sect3> > + <title>Getting Started</title> > + <note> > + <title>Why SGML?</title> > + <para> > + The simple answer to that is that SGML allows you > + to create multiple formats of a given document from a > single > + source. Currently sgml is used to create html, pdf and PS > + formats of the Users Guide, Developers Guide, Winelib Users > + Guide Packagers Guide and FAQ. > + </para> > + </note> > + > + <note> > + <title>What do I need?</title> > + <para> > + You need the sgml tools. There are various places where you > + can get them. The most generic way of geting them form > source. > + </para> > + </note> > + > + <note> > + <title>Quick instructions</title> > + <para> > + These are the generic steps to get output from sgml. > + </para> > + </note> > + > + <orderedlist> > + > + <listItem><para> > + Go to <ulink > url="http://www.sgmltools.org">http://www.sgmltools.org</ulink> > + </para></listitem> > + > + <listItem><para> > + Download all of the sgmltools packages > + </para></listitem> > + > + <listItem><para> > + Install them all and build them (./configure; make; make > install) > + </para></listitem> > + > + <listItem><para> > + Switch to your toplevel wine directory > + </para></listitem> > + > + <listItem><para> > + Run ./configure (or make distclean && ./configure) > + </para></listitem> > + > + <listItem><para> > + Switch to the documentation directory > + </para></listitem> > + > + <listItem><para> > + run make_winehq > + </para></listitem> > + > + <listItem><para> > + View wine-doc/index.html in your favorite browser > + </para></listitem> > + > + </orderedlist> > + > + </sect3> > + > + <sect3> > + <title>Getting SGML for various distributions</title> > + <para> > + Most Linux distributions have everything you need already > + bundled up in package form. Unfortunately, each > + distribution seems to handle its SGML environment > + differently, installing it into different paths, and > + naming its packages according to its own whims. > + </para> > + > + <sect4> > + <title>SGML on Redhat</title> > + <para> > + The following packages seems to be sufficient for RedHat 7.1. > You > + will want to be careful about the order in which you install > the > + rpms. > + <itemizedlist> > + <listitem><para>sgml-common-*.rpm</para></listitem> > + <listitem><para>openjade-*.rpm</para></listitem> > + <listitem><para>perl-SGMLSpm-*.rpm</para></listitem> > + <listitem><para>docbook-dtd*.rpm</para></listitem> > + <listitem><para>docbook-style-dsssl-*.rpm</para></listitem> > + <listitem><para>tetex-*.rpm</para></listitem> > + <listitem><para>jadetex-*.rpm</para></listitem> > + <listitem><para>docbook-utils-*.rpm</para></listitem> > + </itemizedlist> > + You can also use ghostscript to view the ps format output and > + Adobe Acrobat 4 to view the pdf file. > + </para> > + </sect4> > + > + <sect4> > + <title>SGML on Debian</title> > + <note> > + <title>Fix me</title> > + <para> > + List package names and install locations... > + </para> > + </note> > + </sect4> > > + <sect4> > + <title>SGML on Other Distributions</title> > + <note> > + <title>Fix me</title> > + <para> > + List package names and install locations... > + </para> > + </note> > + </sect4> > + </sect3> > <sect3> > <title>Terminology</title> > > @@ -1006,47 +1125,6 @@ > </para> > </sect3> > > - <sect3> > - <title>SGML on Redhat</title> > - <para> > - Most Linux distributions have everything you need already > - bundled up in package form. Unfortunately, each > - distribution seems to handle its SGML environment > - differently, installing it into different paths, and > - naming its packages according to its own whims. > - </para> > - <para> > - The following packages seems to be sufficient for RedHat 7.1. > You > - will want to be careful about the order in which you install > the > - rpms. > - <itemizedlist> > - <listitem><para>sgml-common-*.rpm</para></listitem> > - <listitem><para>openjade-*.rpm</para></listitem> > - <listitem><para>perl-SGMLSpm-*.rpm</para></listitem> > - <listitem><para>docbook-dtd*.rpm</para></listitem> > - <listitem><para>docbook-style-dsssl-*.rpm</para></listitem> > - <listitem><para>tetex-*.rpm</para></listitem> > - <listitem><para>jadetex-*.rpm</para></listitem> > - <listitem><para>docbook-utils-*.rpm</para></listitem> > - </itemizedlist> > - You can also use ghostscript to view the ps format output and > - Adobe Acrobat 4 to view the pdf file. > - </para> > - </sect3> > - > - <sect3> > - <title>SGML on Debian</title> > - <para> > - List package names and install locations... > - </para> > - </sect3> > - > - <sect3> > - <title>SGML on Other Distributions</title> > - <para> > - List package names and install locations... > - </para> > - </sect3> > </sect2> > > <sect2 id="emacs-psgml"> > Index: authors.ent > =================================================================== > RCS file: /home/wine/wine/documentation/authors.ent,v > retrieving revision 1.2 > diff -u -r1.2 authors.ent > --- authors.ent 24 Jul 2002 03:00:02 -0000 1.2 > +++ authors.ent 9 Nov 2002 04:01:56 -0000 > @@ -43,6 +43,9 @@ > <!entity name-alex-korobka "Alex Korobka"> > <!entity email-alex-korobka "alex(a)aikea.ams.sunysb.edu"> > > +<!entity name-tony-lambregts "Tony Lambregts"> > +<!entity email-tony-lambregts "tony_lambregts(a)telusplanet.net"> > + > <!entity name-marcus-meissner "Marcus Meissner"> >  > <!entity email-marcus-meissner "Marcus.Meissner(a)caldera.de"> > __________________________________________________ Do you Yahoo!? U2 on LAUNCH - Exclusive greatest hits videos http://launch.yahoo.com/u2

1 0

Fix for bug #688 (documentation building)
by Vincent Béron 10 Nov '02

10 Nov '02

This one I'm not sure which one is better. So I include both patches, but only one should be applied. Functionnally, both produce the exact same html files, although the fix1 creates (by the system's db2html) a directory with images (which are unused). So I'd tend to go with fix2. Please comment, and I'll post the good one to wine-patches. Vincent

4 6

RFC: rpcss skeleton prototype #2
by Greg Turner 10 Nov '02

10 Nov '02

This one implements "pseudo-fork" behavior, a main workhorse loop, pseudo-debug log emitter, and command-line interpretation. In particular I'm looking for comments/criticism/flames/etc for: o my handling of NO_NAMELESS_STRUCT... works for me, but how correct will this be, say, under MSVC with Microsoft headers? o I differentiate between "server mode" and "lazy mode"... In lazy mode I assume that I'll have at least one incoming connection (if not I time out after 20 minutes); after that, once all endpoints are unmapped (all RPC-specific code is unimplmented, but this is what RPCSS_empty() is supposed to detect) I time out after a short delay (20 sec.) In server mode, I just wait around forever until I'm told to terminate (unimplemented, will be a command-line arg in the tradition of "wineserver -k", processed via the pipe)... reasonable? o Pseudo-debug log emitter: should I be using stderr? is this basically an OK approach? What is the hex number that most real wine debug logs begin with? I'd like to look the same. o Make/autoconf BS o the pseudo-fork crud (RPCSS_spork() and the /^ cmd-line arg.) should I be worried about accidentally invoking the real rpcss.exe? is this an unacceptably stupid approach in general? thanks for your help. diff -ur -x CVS -x 'bigdif*' ../wine.test/configure.ac ./configure.ac --- ../wine.test/configure.ac 2002-11-03 11:50:15.000000000 -0600 +++ ./configure.ac 2002-11-01 18:53:32.000000000 -0600 @@ -1501,6 +1501,7 @@ programs/regedit/Makefile programs/regsvr32/Makefile programs/regtest/Makefile +programs/rpcss/Makefile programs/uninstaller/Makefile programs/view/Makefile programs/wcmd/Makefile diff -ur -x CVS -x 'bigdif*' ../wine.test/programs/Makefile.in ./programs/Makefile.in --- ../wine.test/programs/Makefile.in 2002-11-03 11:50:15.000000000 -0600 +++ ./programs/Makefile.in 2002-11-01 18:53:18.000000000 -0600 @@ -17,6 +17,7 @@ regedit \ regsvr32 \ regtest \ + rpcss \ uninstaller \ view \ wcmd \ @@ -39,6 +40,7 @@ progman \ regedit \ regsvr32 \ + rpcss \ uninstaller \ wcmd \ wineconsole \ @@ -56,6 +58,7 @@ progman \ regedit \ regsvr32 \ + rpcss \ uninstaller \ wcmd \ wineconsole \ @@ -67,6 +70,7 @@ # Symlinks to apps that we want to run from inside the source tree SYMLINKS = \ + rpcss.exe \ wineconsole.exe \ winedbg.exe @@ -115,12 +119,16 @@ # Rules for symlinks +rpcss.exe$(DLLEXT): rpcss/rpcss.exe$(DLLEXT) + $(RM) $@ && $(LN_S) rpcss/rpcss.exe$(DLLEXT) $@ + wineconsole.exe$(DLLEXT): wineconsole/wineconsole.exe$(DLLEXT) $(RM) $@ && $(LN_S) wineconsole/wineconsole.exe$(DLLEXT) $@ winedbg.exe$(DLLEXT): winedbg/winedbg.exe$(DLLEXT) $(RM) $@ && $(LN_S) winedbg/winedbg.exe$(DLLEXT) $@ +rpcss/rpcss.exe$(DLLEXT): rpcss wineconsole/wineconsole.exe$(DLLEXT): wineconsole winedbg/winedbg.exe$(DLLEXT): winedbg --- /dev/null 1969-12-31 18:00:00.000000000 -0600 +++ ./programs/rpcss/Makefile.in 2002-11-03 18:51:44.000000000 -0600 @@ -0,0 +1,15 @@ +TOPSRCDIR = @top_srcdir@ +TOPOBJDIR = ../.. +SRCDIR = @srcdir@ +VPATH = @srcdir@ +MODULE = rpcss.exe +APPMODE = cui +IMPORTS = user32 kernel32 + +C_SRCS = \ + rpcss_main.c + +@MAKE_PROG_RULES@ + +### Dependencies: + --- /dev/null 1969-12-31 18:00:00.000000000 -0600 +++ ./programs/rpcss/README 2002-11-03 18:52:12.000000000 -0600 @@ -0,0 +1,23 @@ +rpcss README + +rpcss, copyright 2002, Greg Turner +rpcss is to be distributed under the LGPL/X11-MIT licenses +See the Wine License for further information. + +Wine needs a server whose role is somewhat like that +of rpcss.exe in windows. + +Enjoy. + +KNOWN BUGS / TODO: + + o Service hooks are unimplemented (if you bother to implement + these, also implement net.exe, at least for "net start" and + "net stop" (should be pretty easy I guess, assuming the rest + of the services API infrastructure works (which net.exe should + assume, even if the API is lean or bugged))). + + o Is supposed to use RPC, not random kludges, to map endpoints. + + o Who knows? Whatever (sane) things rpcss does, we ought to at + least think about doing... but what /does/ it do? --- /dev/null 1969-12-31 18:00:00.000000000 -0600 +++ ./programs/rpcss/rpcss.h 2002-11-03 18:50:26.000000000 -0600 @@ -0,0 +1,43 @@ +/* + * Copyright 2002 Greg Turner <gmturner007(a)ameritech.net> + * + * This library is free software; you can redistribute it and/or + * modify it under the terms of the GNU Lesser General Public + * License as published by the Free Software Foundation; either + * version 2.1 of the License, or (at your option) any later version. + * + * This library is distributed in the hope that it will be useful, + * but WITHOUT ANY WARRANTY; without even the implied warranty of + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU + * Lesser General Public License for more details. + * + * You should have received a copy of the GNU Lesser General Public + * License along with this library; if not, write to the Free Software + * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA + */ + +#ifndef __WINE_RPCSS_H +#define __WINE_RPCSS_H + +#include <stdio.h> + +#include "windows.h" + +/* yet another crude debug logger substitute (just what wine needed!) */ +#define RPCSS_DEBUG(args...) \ + do { \ + if (in_debug_mode) {\ + printf("rpcss.exe.so:%s: ", __FUNCTION__); \ + printf(args); \ + } \ + } while (FALSE) + +extern BOOL in_debug_mode; + +extern BOOL RPCSS_is_server(); +extern void RPCSS_be_server(); +extern void RPCSS_server_terminate(); + +#endif /* __WINE_RPCSS_H */ + +/* end of header */ --- /dev/null 1969-12-31 18:00:00.000000000 -0600 +++ ./programs/rpcss/rpcss_main.c 2002-11-04 01:16:29.000000000 -0600 @@ -0,0 +1,308 @@ +/* + * rpcss (main.c) + * + * Copyright 2002 Greg Turner <gmturner007(a)ameritech.net> + * + * This library is free software; you can redistribute it and/or + * modify it under the terms of the GNU Lesser General Public + * License as published by the Free Software Foundation; either + * version 2.1 of the License, or (at your option) any later version. + * + * This library is distributed in the hope that it will be useful, + * but WITHOUT ANY WARRANTY; without even the implied warranty of + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU + * Lesser General Public License for more details. + * + * You should have received a copy of the GNU Lesser General Public + * License along with this library; if not, write to the Free Software + * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA + */ + +#include <assert.h> + +#include "rpcss.h" +#include "winnt.h" + +/* in seconds */ +#define RPCSS_LONG_LAZY_TIMEOUT 1200 +#define RPCSS_SHORT_LAZY_TIMEOUT 20 + +/* are we the "fork child"? */ +static BOOL secret_fork_child; + +/* do we dump debug info to the console? */ +static BOOL in_debug_mode; + +/* are we in server mode, with no timeout? */ +static BOOL in_server_mode; + +/* was server mode terminated? */ +static BOOL server_mode_was_terminated; + +/* when do we just give up and bail? (UTC) */ +static SYSTEMTIME lazy_timeout_time; + +#if defined(NONAMELESSSTRUCT) + #define FILETIME_TO_ULARGEINT(filetime, ularge) \ + ( ularge.s.LowPart = filetime.dwLowDateTime, \ + ularge.s.HighPart = filetime.dwHighDateTime, \ + ularge ) /* r-value */ + #define ULARGEINT_TO_FILETIME(ularge, filetime) \ + ( filetime.dwLowDateTime = ularge.s.LowPart, \ + filetime.dwHighDateTime = ularge.s.HighPart, \ + filetime ) /* r-value */ +#else + #define FILETIME_TO_ULARGEINT(filetime, ularge) \ + ( ularge.LowPart = filetime.dwLowDateTime, \ + ularge.HighPart = filetime.dwHighDateTime, \ + ularge ) /* r-value */ + #define ULARGEINT_TO_FILETIME(ularge, filetime) \ + ( filetime.dwLowDateTime = ularge.LowPart, \ + filetime.dwHighDateTime = ularge.HighPart, \ + filetime ) /* r-value */ +#endif /* NONAMELESSSTRUCT */ + +#define TEN_MIL 10000000LL + +/* returns time remaining in seconds */ +long RPCSS_GetLazyTimeRemaining() +{ + SYSTEMTIME st_just_now; + FILETIME ft_jn, ft_ltt; + ULARGE_INTEGER ul_jn, ul_ltt; + + assert(! in_server_mode); /* then why are you calling? */ + + GetSystemTime(&st_just_now); + SystemTimeToFileTime(&st_just_now, &ft_jn); + FILETIME_TO_ULARGEINT(ft_jn, ul_jn); + + SystemTimeToFileTime(&lazy_timeout_time, &ft_ltt); + FILETIME_TO_ULARGEINT(ft_ltt, ul_ltt); + + return (ul_ltt.QuadPart - ul_jn.QuadPart) / TEN_MIL; +} + +void RPCSS_SetLazyTimeRemaining(long seconds) +{ + SYSTEMTIME st_just_now; + FILETIME ft_jn, ft_ltt; + ULARGE_INTEGER ul_jn, ul_ltt; + + RPCSS_DEBUG("(seconds == %ld)\n", seconds); + + assert(! in_server_mode); /* then why are you calling? */ + assert(seconds >= 0); /* negatives are not allowed */ + + GetSystemTime(&st_just_now); + SystemTimeToFileTime(&st_just_now, &ft_jn); + FILETIME_TO_ULARGEINT(ft_jn, ul_jn); + + /* we want to find the time ltt, s.t. ltt = just_now + seconds */ + ul_ltt.QuadPart = ul_jn.QuadPart + seconds * TEN_MIL; + + /* great. just remember it */ + ULARGEINT_TO_FILETIME(ul_ltt, ft_ltt); + if (! FileTimeToSystemTime(&ft_ltt, &lazy_timeout_time)) + assert(FALSE); +} + +#undef FILETIME_TO_ULARGEINT +#undef ULARGEINT_TO_FILETIME +#undef TEN_MIL + +BOOL RPCSS_is_server() +{ + return in_server_mode; +} + +void RPCSS_be_server() +{ + RPCSS_DEBUG("\n"); + in_server_mode = TRUE; +} + +void RPCSS_server_terminate() +{ + assert(in_server_mode); + server_mode_was_terminated = TRUE; +} + +BOOL RPCSS_work() +{ + RPCSS_DEBUG("\n"); + Sleep(1000); + return FALSE; /* we didn't do anything */ +} + +BOOL RPCSS_empty() +{ + BOOL rslt = TRUE; + + /* FIXME */ + + RPCSS_DEBUG("%s\n", rslt ? "TRUE" : "FALSE" ); + return rslt; +} + +BOOL RPCSS_is_ready_to_die() +{ + return + ( + RPCSS_empty() && + ( + (in_server_mode && server_mode_was_terminated) || + ( + (! in_server_mode) && + (RPCSS_GetLazyTimeRemaining() <= 0) + ) + ) + ); +} + +void RPCSS_main_loop() { + BOOL did_something_new; + + RPCSS_DEBUG("\n"); + + for (;;) { + did_something_new = FALSE; + + while ( (! did_something_new) && (! RPCSS_is_ready_to_die()) ) + did_something_new = (RPCSS_work() || did_something_new); + + if ((! did_something_new) && RPCSS_is_ready_to_die()) + break; /* that's it for us */ + + if (did_something_new) { + /* if we were in server mode, but terminated, then, + because we did something new, fall back to lazy mode */ + if (in_server_mode && server_mode_was_terminated) + in_server_mode = server_mode_was_terminated = FALSE; + + /* if we aren't in server mode, set the lazy timeout */ + if (! in_server_mode) + RPCSS_SetLazyTimeRemaining(RPCSS_SHORT_LAZY_TIMEOUT); + } + } +} + +BOOL RPCSS_ProcessArgs( int argc, char **argv ) +{ + int i; + char *c; + + for (i = 1; i < argc; i++) { + c = argv[i]; + while (*c == ' ') c++; + if ((*c != '-') && (*c != '/')) + return FALSE; + c++; + switch (*c++) { + case 's': + case 'S': + in_server_mode = TRUE; + break; + case 'd': + case 'D': + in_debug_mode = TRUE; + break; + case '^': + /* "secret" hidden command-line arg means we are the "fork child" */ + secret_fork_child = TRUE; + break; + default: + return FALSE; + break; + } + while (*c == ' ') c++; + if (*c != '\0') return FALSE; + } + + return TRUE; +} + +void RPCSS_Usage() +{ + printf("\nWine RPCSS\n"); + printf("\nsyntax: rpcss [/d] [/s]\n\n"); + printf(" /d: debug mode (print debug messages to std. output)\n"); + printf(" /s: server mode (don't time out)\n\n"); +} + +void RPCSS_Spork() +{ + /* Because we are a wine app, we can't fork. This is + a trick to invoke ourselves, so we can provide a + similar effect of creating a "background" process */ + + PROCESS_INFORMATION pi; + STARTUPINFO si; + char *oldcmdline, *newcmdline; + + /* create a string to invoke ourselves */ + oldcmdline = GetCommandLineA(); + newcmdline = LocalAlloc(LPTR, strlen(oldcmdline) + 10); /* more than enough */ + assert(newcmdline); /* must succeed */ + + sprintf(newcmdline, "%s /^", oldcmdline); + + ZeroMemory(&pi, sizeof(PROCESS_INFORMATION)); + ZeroMemory(&si, sizeof(STARTUPINFO)); + si.cb = sizeof(STARTUPINFO); + + if (!CreateProcess( + NULL, // executable + newcmdline, // command line + NULL, // process security attributes + NULL, // primary thread security attributes + FALSE, // no inherit handles + 0, // creation flags + NULL, // use parent's environment + NULL, // use parent's current directory + &si, // STARTUPINFO pointer + &pi // PROCESS_INFORMATION + )) + assert(FALSE); + + LocalFree(newcmdline); +} + +int main( int argc, char **argv ) +{ + /* + * We are invoked as a standard executable; typically, we act in a + * "lazy" manner. We open up our pipe, and hang around until we have + * nothing left to do, and then silently terminate. When we're needed + * again, rpcrt4.dll.so will invoke us automatically. + */ + + if (!RPCSS_ProcessArgs(argc, argv)) { + RPCSS_Usage(); + return 1; + } + + if (! in_debug_mode) { + if (secret_fork_child) + FreeConsole(); + else { + /* pseudo-fork */ + RPCSS_Spork(); + return 0; + } + } else if (secret_fork_child) { + /* this should never happen... perhaps they typed /d /^ on cmd line */ + RPCSS_Usage(); + return 2; + } + + if (! in_server_mode) + /* we want to wait for something to happen, and then + timeout when no activity occurs... but we will be + extra patient on the first wait */ + RPCSS_SetLazyTimeRemaining(RPCSS_LONG_LAZY_TIMEOUT); + + RPCSS_main_loop(); + + return 0; +} -- gmt "The purpose of government is to rein in the rights of the people" --President Bill Clinton, MTV interview, 1993

7 15

Re: help support
by Sylvain Petreolle 10 Nov '02

10 Nov '02

CHM is a special extension of IE. The patch to make any windows compatible with CHM (except Win 3.1) is downloadable at http://www.microsoft.com/downloads/release.asp?ReleaseID=30328 To handle and generate CHM I found a french page (tools are in english). http://www.jurixt.com/informatique/hlp_compile_aide.htm Utility to decompile CHM and many many more : http://www.keyworks.net/keytools.htm Google power ! ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com

1 0

Re: int21 move a8
by Jukka Heinonen 09 Nov '02

09 Nov '02

Again, no full review, just quickly browsed through the patch. I have a feeling that I have just scratched the surface regarding this patch series and it would need a full review before it can be accepted. Function 0x40 change in winedos/int21.c breaks DOS VGA text console. Function 0x3f handling drops WIN16_hread which used to check for segment size. That check seemed to be for running buggy Win16 programs. At least I wouldn't have courage to delete this kind of checks. -- Jukka Heinonen <http://www.iki.fi/jhei/>

1 0

Re: winamp patch A0
by Vincent Béron 09 Nov '02

09 Nov '02

Le sam 09/11/2002 à 11:22, Andreas Mohr a écrit : > Hi all, > > IMHO we should now switch to Win98 SE as default Windows version. > Too many programs expect at least Win98 to be running already. > > Winamp also checks the Version registry keys, so I added them to > winedefault.reg. > > Index: winedefault.reg > =================================================================== > RCS file: /home/wine/wine/winedefault.reg,v > retrieving revision 1.58 > diff -u -r1.58 winedefault.reg > --- winedefault.reg 25 Oct 2002 19:05:19 -0000 1.58 > +++ winedefault.reg 9 Nov 2002 16:20:36 -0000 > @@ -72,6 +72,9 @@ > "ProgramFilesDir"="C:\\Program Files" > "RegisteredOrganization"="Change preferred organization in ~/.wine/system.reg" > "RegisteredOwner"="Change preferred owner in ~/.wine/system.reg" > +"SubVersionNumber"=" A " > +"Version"="Windows 98" > +"VersionNumber"="4.10.2222" This doesn't seem the place to do it, since if we specify something different (in config) then the registry keys do not match, and some other app could possibly have some problems. Would it be possible to generate automatically those keys with a call to GetVersionEx or something similar? Vincent

3 2

Re: GetCurrentObject
by steve.lustbader＠philips.com 09 Nov '02

09 Nov '02

GetCurrentObject returns 0, but as far as it knows, it is returning successfully. This is because in the line case OBJ_BITMAP: ret = dc->hBitmap; break; dc->hBitmap is 0, although dc is a valid DC. The HDC that is passed to GetCurrentObject to get dc is obtained by calling CWindow::BegingPaint(PAINTSTRUCT *) from a class derived from ATL's CWindow. I'm guessing that this is where the problem is probably coming from - the app is written in C++ with ATL. -Steve I've seen this occur when wine frees a gdi handle it shouldn't. Check that the OBJ_BITMAP handle is really valid. Also wierd stuff can occur if the app expects a HDIB but we provide it a HBITMAP... or vice versa. Mike steve.lustbader(a)philips.com wrote: > My app calls GetCurrentObject with a valid HDC and OBJ_BITMAP. > It returns 0, however, which causes my app to crash. What further > info can I provide to help debug this? > > -Steve >

2 1

Fwd: Re: So lets say we do it
by Dimitrie O. Paun 09 Nov '02

09 Nov '02

---------- Forwarded Message ---------- Subject: Re: So lets say we do it Date: Sat, 9 Nov 2002 02:51:47 -0800 From: Kenny Smith <kenny(a)blindinstinct.com> To: dpaun(a)rogers.com I don't know how to use mail lists, so i though I might mail you In responce to your ideas about reorganizing the winehq site, i think there should be a site for development, like winehq, and a site for users. most users don't want to know about listview overhauls, etc. They wnat to know if their precious Quicken will run on linux or not. I'm sure a web design would be EASILY feasible. I'm a web designer (never done anything that big), and a 6-month linux user and there are tons of people like me who i'm sure would love to help. I use wine because I am somewhat computer-savvy (A+ certified savvy). I hope this message can be passed along, if you can't maybe you can tell me how to quickly... would google-groups let me?? kenny smith (AIM:standsolid) ------------------------------------------------------- -- Dimi.

1 0

re: Wine 0.8: VB compatibility !!
by Dan Kegel 09 Nov '02

09 Nov '02

Andreas Mohr wrote: > I keep encountering people mentioning that VB stuff has > lotsa problems on Wine. > While I really can't say that I like VB, a lot of people > seem to use it for critical tasks in companies on a > daily basis, so it sounds like perfect > VB compatibility would be utterly important. > IMHO improving that should be a goal of 0.8. Make sense. How about this: let's add a visual basic regression test suite to Wine. I'm not kidding! Ought to be pretty easy to hit at least the non-gui parts... - Dan

6 6

Re: wine button
by Mike Hearn 09 Nov '02

09 Nov '02

[ps i assumed by what was written you meant for this to go to wine-devel but didn't hit reply-to-all, sorry if it was meant for me only] > There's the application, and button with a wine bottle, that says > 'works with wine'. You could come up with quite a few jokes with that. heh, true. It doesn't look good with the first letter capitalized, at least imho, and probably wouldn't alter the impression non-initiates would get. I tried putting "windows emulator" underneath, but it looks a bit out of place and kind of reduces the impact. It also makes it harder to scale down, at 50% of the size you can still read the "works with wine" text, but not the "windows emulator" underneath. It might also piss off people who say "Wine is not an emulator" :) Actually, letting people make jokes about it might be a good thing - I doubt many people would actually take it literally and assuming they do find out, if they're talking and joking about it, they're more likely to remember it too. On Fri, 2002-11-08 at 15:35, Rick Romero wrote: > > On Fri, 2002-11-08 at 08:53, Mike Hearn wrote: > > Here is my first attempt. I'm hardly an ace designer, so feel free to > > criticize, tell me to junk it etc. > I think it looks great, but if I were a Windows app owner, how would my > potential users see it? > > There's the application, and button with a wine bottle, that says > 'works with wine'. You could come up with quite a few jokes with that. > > Of course we all know what it means, should the 'W' be capitalized to > differentiate it from alcohol? > > I don't intend to start a logo flame war, but I think perceptions are > everything. > > Good thing I'm only around for another 90 minutes today :P > > Rick > > > > > > > -- > -- > Rick Romero > IT Manager > Valeo, Inc. ph: 262.695.4841 > Sussex, WI. fax: 262.695.4850 > Rick(a)valeoinc.com > >

3 2

wine button
by Mike Hearn 09 Nov '02

09 Nov '02

Here is my first attempt. I'm hardly an ace designer, so feel free to criticize, tell me to junk it etc. I did try at first to make a browser style button, but it was very hard to make the wine logo fit in a way that didn't look odd, as it's largely a vertical type of logo. Also, is the Windows logo usable? I'd assume it's trademarked or something, but i've seen the 4 colour blocks used in for instance icon overlays in KDE. If it's thought that this is too large, I can either scale it, or try and make another from scratch that is more button sized. thanks -mike

7 10

Wine 0.9 TODO v0.1
by Dimitrie O. Paun 09 Nov '02

09 Nov '02

This is based upon the Wine 0.8 TODO v0.2 send earlier to the list. It is important to get a comprehensive list of what needs to be done, in order to have a successful 0.9 release. This includes all things Wine-related, not only the code. I can not do it alone -- I need your input. Before I start, a quick reminder for the 0.9 criteria: -- Users can start using Wine -- works well for a fair number of apps -- no MS DLLs required (from real Windows) -- User facing stuff (website, docs, etc.) are in a decent state, to avoid scaring them away What is NOT in 0.9: -- stable server protocol (no binary compatibility) -- DLL separation (phase 2) Please review it, and let me know if: - I've left something out - Something is in, and it doesn't belong in here (for 0.9 that is) - I have put your name on a task you are not working on - I have NOT put your name on a task you are working on - You have a status update (if you're working on something) - You want to start working on some of these. Comments, flames, suggestions, are appreciated, as always. A. WineHQ work (Beta at: http://lostwages.winehq.org) 0. Website redesign [IN PROGRESS] - worker: Jeremy Newman <jnewman(a)codeweavers.com> 1. Reorganize the navigational menu [BETA] - wine-devel consensus merged into new site 2. Create some really sexy screenshots [IN PROGRESS] -- one app per screenshot, avoid cluttered desktop -- minimize size, if possible by using 'Positioned Color Dithering' 3. Rework the FAQ interface [IN PROGRESS] - workers: Dimitrie Paun, Keith Matthews, Thomas Wickline) 4. Enlist some 'official' distribution maintainers [TODO] (at the minimum RedHat, SUSE, Mandrake, Debian) 5. Create nice page with apps that run virtually flawless [IN PROGRESS] They should not require MS dlls, tricks, etc. to run - worker: Carlos <clozano(a)andago.com> B. Documentation work 0. We need to first figure _what_ is out of date. [TODO] 1. Convert man pages to SGML [TODO] 2. Move CVS docu from User Guide to Devel Guide [TODO] C. Wine configuration 0. Merge configuration into the registry [TODO] 1. Write control panel applets for editing it [TODO] 2. Have decent defaults so we can start control panel without prior configuration [TODO] 3. Have wizard like app to autoconfigure wine [TODO] WineSetupTk proposed by Jeremy White <jwhite(a)codeweavers.com> 4. Make Wine's DLLs register themselves to avoid manual merging of the winedefault.reg [TODO] 5. Write .inf script to setup a new Wine installation [TODO] 6. Have a wineboot script for RunOnce stuff [IN PROGRESS] - worker: Shachar Shemesh <wine-devel(a)sun.consumer.org.il> D. Stabilize utilities 0. Get rid of the init directive from .spec files [DONE] - worker: Alexandre Julliard <julliard(a)winehq.com> 1. Make sure the .spec file format is fairly stable [TODO] Any other things that may need changing here? 2. Ensure the various utilities' options are stable [IN PROGRESS] - Alexandre fixed winebuild options Anything here? E. Important fixes 0. Window management rewrite, so we can install apps in managed mode. - worker: Alexandre Julliard <julliard(a)winehq.com> 1. Finish DLL separation Phase 1 [IN PROGRESS] That is, DLLs should use only functions exported through .spec file. Phase 2 is getting rid of unwanted functions from .spec file, and this is not a target for 0.9. -- Dimi.

10 25

Re: dosconf move try 2
by Jukka Heinonen 09 Nov '02

09 Nov '02

György 'Nog' Jeney wrote: > ChangeLog: > * dlls/winedos/dosconf.c > * include/callback.h > * msdos/dmpi.c > * msdos/dosconf.c (removed) > * dlls/ntdll/Makefile.in > * dlls/winedos/winedos.spec > * dlls/winedos/Makefile.in > Move dosconf to winedos. This still won't work if Dos3Call is called directly before winedos.dll has been loaded. If this is fixed, I don't see any reason why this patch couldn't be applied. This reminds me that int21 handling is quite messy. Interrups call first DOSVM_Int21Handler and might be chained to Dos3Call. But, if you call Dos3Call directly, execution does not go through DOSVM_Int21Handler. This causes some code duplication and makes things like dosconf unnecessarily complicated. I was hoping that I could leave this stuff to its current state until I had cleaned up other interrupts. Simple solution would be to make Dos3Call load winedos.dll and call DOSVM_Int21Handler through function pointer, move all common code from old Dos3Call to DOSVM_Int21Handler and move code that is difficult to handle in winedos to INT_Int21Handler which would be chained to from DOSVM_Int21Handler when a few selected functions need to be emulated. But this requires lots of work because each int21 function must be separately evaluated in order to see how it must be emulated to properly support both Win16 and DOS; first step would probably just add check if(DOSVM_IsWin16()) to each DOSVM_Int21Handler function and chain to INT_Int21Handler if true. -- Jukka Heinonen <http://www.iki.fi/jhei/>

2 1

Fun projects
by Dimitrie O. Paun 09 Nov '02

09 Nov '02

Folks, It's Friday, I'm out of my meetings, weather is superb here in Toronto (so I'm gonna go for a ride on my bike); this calls for some lighter, more entertaining stuff. So, if someone feels like doing something fun, here is a list of interesting Wine-related projects: 1. compile & run Wine under Cygwin (in Windows) This is too cool for words, when it's going to work. It will stress the heck out of Cygwin (good test case), improve out portability 2. compile & run Cygwin under Wine (in Linux) This is also way cool, being the complement of 1. It will stress Wine a lot (another good test case), improve Cygwin portability 3. compile wxWindows/QT/Gtk+ (in Linux), under Wine All of these libraries compile under Windows. So they should compile under Wine just fine. Another superb test case for Wine. 4. make a ghostscript driver that uses Wine to print When we are going to support native Windows printer drivers, this is going to allow ghostscript to use any of the existing gazillion printer drivers out there. 5. compile OSS apps that compile under Windows under Wine This includes stuff like Mozilla, Gimp-Win32, etc. Lots of these are around, many of them hosted at http://sourceforge.net In fact, imagine if we get 3 done, and we can get all KDE/GNOME working in Wine! (I know it's not easily possible, but just the possibility is there :)) And yeah, don't ask me 'why would you want to do that?'. The answer is: Because We Can! :) Really folks, just think how cool these are! ;) Comments, suggestions, additions, are welcome. -- Dimi.

3 2

Re: StretchDIBits
by Dmitry Timoshkov 09 Nov '02

09 Nov '02

<steve.lustbader(a)philips.com> wrote: > According to my quick test on WinXP, StretchDIBits returns 0 if > lpBits or lpBitsInfo is NULL. Wine currently produces an unhandled > exception if lpBitsInfo is null. > > ChangeLog: > Prevent StretchDIBits from producing an unhandled exception if > lpBitsInfo is null. > > (See attached file: stretchdibits.diff) > --- objects/dib.c 23 Oct 2002 18:50:10 -0000 1.70 > +++ objects/dib.c 8 Nov 2002 18:49:19 -0000 > @@ -157,6 +157,9 @@ > DC *dc = DC_GetDCUpdate( hdc ); > if(!dc) return FALSE; > + if (!bits || !info) > + return 0; You have to verify parameters before DC pointer and GDI lock are grabbed, otherwise we'll get a nice dead lock. -- Dmitry.

1 0

Re: Small fix for db2html-winehq
by Jeremy White 09 Nov '02

09 Nov '02

> -if [ -f /etc/redhat_release ]; then > +if [ -f /etc/redhat-release ]; then afaik, mandrake has this file as well: [weaver@test-d weaver]$ cat /etc/redhat-release Mandrake Linux release 9.0 (dolphin) for i586 [weaver@test-d weaver]$ Jer

1 0

Cabextract offered to WINE under LGPL..
by Ender 09 Nov '02

09 Nov '02

There you go, now who wants to look into merging cabextract with WINE? [http://www.kyz.uklinux.net/cabextract.php3] It'll be useful for at least three things: - Remove external dependency in urlmon (dlls/urlmon/umon.c) - Implement advapi32:ExtractFiles and fix dlls/setupapi/queue.c - Implement cabinet.dll - Probably some other misc cabinet functions here and there - CHM viewer (in the future) I don't think it would be too hard to merge the 0.7 changes into any merging work done with 0.6, so I wouldn't think it necessary to hold out until then. The only major bug he mentions is fixed by simply changing scope of a variable, so.... :) - Ender ---------- Forwarded message ---------- Date: Wed, 06 Nov 2002 12:37:51 +0000 From: Stuart Caie <kyzer(a)4u.net> To: "J.Brown (Ender/Amigo)" <ender(a)enderboi.com> Subject: Re: cabextract licensing Hello J.Brown On 01-Nov-02, you wrote: > Quick question - would it be possible for you to release/give permission > to use the cabextract code under the LGPL? That would allow it's > integration into WINE, and make things a lot easier for WINE.. Sure, I donate to the WINE project the current cabextract 0.6 code (and next release, 0.7, when it is out) for all uses under the LGPL. Just a few technical things: - as it says in the code, cabextract is not a library. It doesn't bother freeing memory except for the 2MB LZX/QTM windows between folders. You'll have to handle memory freeing yourself :) - further, there is a real bug in 0.6: when an LZX or QTM folder follows a ZIP folder, the LZX(window) and QTM(window) pointer in the methods union will be muddied by ZIP state data and will be non-zero and therefore assumed to be valid window pointers. They're not (they're random ZIP state), so it segfaults. To fix this now, remove the "window" field from LZXstate and QTMstate, and put it in the general decomp_state, then change all references of LZX(window) and QTM(window) to CAB(window). - there are also some minor bugs that you'll see fixed in 0.7 (which is why I gifted you this one as well) If you have any other questions, feel free to ask! Regards -- Stuart Kyzer Caie -- kyzer(a)4u.net http://zap.to/kyz ICQ: 45612337 the golden rule; he who has the gold, makes the rules.

1 0

Some dead links on winehq
by Martin Wilck 08 Nov '02

08 Nov '02

A small contribution to the winehq fixes: A list of dead or non-functional links on the Development/References page. (http://www.winehq.com/development/index.php?refs) Wine Wine API - mostly useless, IMHO (is this really up-to-date? - at least it shouldn't be on top of the page). Vintage wine sources - ftpsearch.ntnu.no unfortunately out of service. Win32 Win32 API intro - dead WinDoc - only the "Local Mirror" works, the "at microsoft.com" links bring you to the main MSDN site. Unix Unix98 - needs registration LinuxThreads - why is this linked here? AFAIK not used by wine anyway. X The motif zone - dead lamentation - dead Fonts Internet Font archive - gone. X11R6 fonts - dead t1lib -dead Curvesoft - have ceased operations, a few tools still available. x86 Assembly Intel Documentation - dead Writings on software development Homesteading the Noosphere - dead Lisp... - I don't know why it's there, but I love it :-) The Open Source-revolution - dead Martin -- Martin Wilck Phone: +49 5251 8 15113 Fujitsu Siemens Computers Fax: +49 5251 8 20409 Heinz-Nixdorf-Ring 1 mailto:Martin.Wilck@Fujitsu-Siemens.com D-33106 Paderborn http://www.fujitsu-siemens.com/primergy

2 1

GetCurrentObject
by steve.lustbader＠philips.com 08 Nov '02

08 Nov '02

My app calls GetCurrentObject with a valid HDC and OBJ_BITMAP. It returns 0, however, which causes my app to crash. What further info can I provide to help debug this? -Steve

1 0

authors.ent ...
by Dustin Navea 08 Nov '02

08 Nov '02

I need everyone to look at authors.ent in their documentation directory and if you are listed in there and your email has changed, please send me a blank email off-list.. If you feel that you should be listed in there, please send me an email off-list with the reason why and i will add you in... -Dustin __________________________________________________ Do you Yahoo!? U2 on LAUNCH - Exclusive greatest hits videos http://launch.yahoo.com/u2

1 0

Re: wine button
by Scott Pickett 08 Nov '02

08 Nov '02

I think the idea of the button is great! I think you need to rework the graphic. (1) It's too big. Software publishers would view it as a small additional message about their product. As such, it should be less than half that size. (2) Put "Linux" in the message. It will make it clearer to the windows-user audience and be considered more valuable to the software publisher. "Linux/Wine Certified" or "Runs on Linux+Wine" or some such thing. (3) I'm not knocked out about the graphic, but I'm not artistic, so I don't know why. 3-D shadows, rounded corners, non-white background??? It just doesn't grab me, as is. I think the basic idea is great, however. Scott Pickett Street Wizard Mapping Software __________________________________________________ Do you Yahoo!? U2 on LAUNCH - Exclusive greatest hits videos http://launch.yahoo.com/u2

1 0

RE: Wine 0.8: VB compatibility !!
by Medland, Bill 08 Nov '02

08 Nov '02

> -----Original Message----- > From: wine-devel-admin(a)winehq.com > [mailto:wine-devel-admin@winehq.com]On > Behalf Of Andreas Mohr > Sent: Friday, November 08, 2002 12:59 AM > To: Wine Devel > Subject: Wine 0.8: VB compatibility !! > > > Hi all, > > I keep encountering people mentioning that VB stuff has lotsa problems > on Wine. > While I really can't say that I like VB, a lot of people seem > to use it > for critical tasks in companies on a daily basis, so it > sounds like perfect > VB compatibility would be utterly important. > IMHO improving that should be a goal of 0.8. > > I agree totally. Bill

1 0

Docu updates question..
by Dustin Navea 08 Nov '02

08 Nov '02

Should I email patches to Jeremy, or just update the pages myself and email those to Jeremy or Alexandre? -Dustin __________________________________________________ Do you Yahoo!? U2 on LAUNCH - Exclusive greatest hits videos http://launch.yahoo.com/u2

6 9

notepad and richedit - why?
by Shachar Shemesh 08 Nov '02

08 Nov '02

Hi, I was going over the notepad code, and it is implemented using richedit. My question is - why? There is no functionality there that is not also available through the usual Edit control. The Windows notepad is notoriously implemented via the edit control. Is there a special reason why our notepad is different here? Shachar

3 7

Re: Wine 0.8 TODO v0.2
by Gerald Pfeifer 08 Nov '02

08 Nov '02

(I'm not sure this will get through to the list, as I am not subscribed, so I am Cc:ing you.) You wrote: > 4. Enlist some 'official' distribution maintainers > (at the minimum RedHat, Suse, Mandrake, Debian) Please also include FreeBSD, and feel free to contact me for FreeBSD-related issues, especially concerning this kind of "official" distribution maintainers. Many contributors (including myself) have been providing patches to improve portability or support FreeBSD-specific features which differ from GNU/Linux and the port should be in a decent shape. Thanks, Gerald -- Gerald "Jerry" pfeifer(a)dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/

7 21

Wine 0.8: VB compatibility !!
by Andreas Mohr 08 Nov '02

08 Nov '02

Hi all, I keep encountering people mentioning that VB stuff has lotsa problems on Wine. While I really can't say that I like VB, a lot of people seem to use it for critical tasks in companies on a daily basis, so it sounds like perfect VB compatibility would be utterly important. IMHO improving that should be a goal of 0.8.

2 1

Debian Maintainer
by Dimitrie O. Paun 08 Nov '02

08 Nov '02

We're still missing one. Any takers? -- Dimi.

5 10

Huge speedup to wine ReadFile on small packets
by Hannu Kotipalo 08 Nov '02

08 Nov '02

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi! The only program I use at windows on home is wzebra, a windows based reversi game (http://www.nada.kth.se/~gunnar/othello.html). (linux version coming, but it's binary only :-() Unfortunately current wine version needs over 10 minutes time to start the program! In windows, starting time is just a few seconds. I found out that the source of the delay was a database file (opening book file), which wzebra reads in by a few byte packets. Fortunately wzebra itself measures the time needed for the readout. Since wine has a lot of overhead for opening and closing unix filesystem for every packet, the delay is understandable (but not acceptable!). Of course, buffering helps. I made a Quick-and-dirty 1k buffer for just ReadFile - routine and database readout dropped from over 800 seconds down to 12-13 seconds! (On my 200 Mhz Pentium Pro) I think this should be fixed in a more sophisticated way, so I did not yet post my patch. Also, this patch helps only on this particular problem; reading a file by small packets with ReadFile. However, I noticed that wzebra reads even bitmaps on byte by one... Don't know how usual this is, thought. In addition, I do not have too much time for playing with this. If someone is interested in continuing my work, please mail me, I can reply by sending the patch. Hannu -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE9ytdIuA3ghgc3fUsRAsrLAJ0T4ZYYmhsGx3XgsrmK/JY9jfqDbwCgqYSw rc2AIWu2A5XahdQw0AnZSmg= =0x+Q -----END PGP SIGNATURE-----

2 1

wine.texinfo
by Vincent Béron 08 Nov '02

08 Nov '02

Is it normal that I cannot find a rule to build wine.info from wine.texinfo in the Makefiles? The file seems to still be worked on (last change september 20th), but I must build it with makeinfo manually (or add it to the spec file). Vincent

2 1

Searching mailinglists
by Sam 08 Nov '02

08 Nov '02

I was wondering if it would be possible to add a search feature to the mailing list archives, while we're doing the WineHQ redesign ? I think that would be a very useful feature, for both, new and old developers. Or perhaps there is already a search available, hidden somewhere out of sight? :-) sam(a)pcuf.fi

2 1

Re: [PATCHLET] DeleteFile With Empty Paths
by Ryan Cumming 07 Nov '02

07 Nov '02

> Can you also create a testcase for this problem? Hmm, I've never written a Wine testcase before. Does the following look good? -Ryan ChangeLog: Add test for DeleteFileA with empty paths

1 0

Wine 0.9 TODO v0.3
by Dimitrie O. Paun 07 Nov '02

07 Nov '02

Lots of updates on this one: http://www.dssd.ca/Wine-0.9-TODO-0.3.html The actual TODO included below as text, for your commenting convenience. A. WineHQ work Website redesign [IN PROGRESS] worker: Jeremy Newman status: backend is getting finalized updated: Nov 7, 2002 Reorganize the navigational menu [DONE] worker: Francois Gouget & al. status: merged into new site updated: Nov 5, 2002 Create some really sexy screenshots [IN PROGRESS] worker: ? status: just starting updated: Nov 7, 2002 criteria: one app per screenshot, avoid cluttered desktop Rework the FAQ interface [IN PROGRESS] workers: Dimitrie O. Paun, Keith Matthews, Thomas Wickline status: close to first public release updated: Nov 7, 2002 Enlist some 'official' distribution maintainers [DONE] RedHat: Vincent Béron SUSE: Marcus Meissner Mandrake: Kye Lewis Debian: Ove Kaaven FreeBSD: Gerald Pfeifer status: completed updated: Nov 7, 2002 Create nice page with apps that run virtually flawless [IN PROGRESS] workers: Carlos Lozano, Dustin Navea status: 20% updated: Nov 7, 2002 criteria: not MS dlls required, no tricks, etc. B. Documentation work We need to first figure what is out of date. [IN PROGRESS] worker: Dustin Navea status: just started updated: Nov 7, 2002 Move CVS docu from User Guide to Devel Guide [IN PROGRESS] worker: Bill Medland status: just started updated: Nov 7, 2002 C. Wine configuration Merge configuration into the registry [TODO] Write control panel applets for editing it [TODO] Have decent defaults so we can start control panel without prior configuration [TODO] Have wizard like app to autoconfigure wine [TODO] proposal: WineSetupTk by Jeremy White Make Wine's DLLs register themselves to avoid manual merging of the winedefault.reg [TODO] Write wine.inf script to setup a new Wine installation [TODO] Have a wineboot script for RunOnce stuff [IN PROGRESS] workers: Andreas Mohr, Shachar Shemesh status: 50% updated: Nov 7, 2002 D. Stabilize utilities Get rid of the init directive from .spec files [DONE] worker: Alexandre Julliard status: implemented by this updated: Nov 7, 2002 Make sure the .spec file format is fairly stable [IN PROGRESS] worker: Dimitrie O. Paun status: investigating updated: Nov 7, 2002 what: can we get rid of the rsrc directive? Ensure the various utilities' options are stable [IN PROGRESS] status: Alexandre fixed winebuild options updated: Nov 7, 2002 what: audit the other utilites Get rid of the Perl testing framework [TODO] worker: Dimitrie O. Paun status: started looking at it updated: Nov 7, 2002 E. Important fixes Window management rewrite, so we can install apps in managed mode. [TODO] worker: Alexandre Julliard status: not started Finish DLL separation Phase 1 [IN PROGRESS] worker: ? status: ntdll, and kernel not done updated: Nov 7, 2002 criteria: DLLs should use only functions exported through .spec file. Detect printing system at runtime [TODO] worker: Huw Davies status: Yup, I'm going to do this in the near future. updated: Nov 7, 2002 Detect OpenGL system at runtime [TODO] worker: Lionel Ulmer status: Real Soon Now (TM) updated: Nov 7, 2002 -- Dimi.

2 1

Re: debugging a lockup in Planescape Torment
by Eric Pouech 07 Nov '02

07 Nov '02

> RFE: > Actually I am not interested in debug msgs after the debugger started. > Could there be an option that an debugger start turns off debug msgs. set - all > When the debugger starts I often get the msg > wine: hash.c:392: DEBUG_GetSymbolValue: Assertion 'strlen(name) < > sizeof(buffer) - 2' failed. which results in an unhandled exception in the > debugger. Whats up with that? fixed size for internal buffers... however a 512 characters identifier seems a bit big to me (even in C++) would you mind printing out the name of the symbol, just to check I'll send a work around for that A+

2 4

user.reg and winedbg
by steve.lustbader＠philips.com 07 Nov '02

07 Nov '02

They key in user.reg that controls whether winedbg pops up in its own window or in the shell in which wine was started seems to be getting ignored. When I set "UseXTerm"=dword:00000000, and run my app, it crashes and brings up winedbg in a separate window. When I look at user.reg again, UseXTerm has been set back to 1. The reason I need this is because when my app crashes, the backtrace is so long (~40 frames) that I can only see the bottom (mostly useless half). Is there a way to increase the size of the winedbg window, pause bt's output (like piping to more in a shell), or display only part of a back trace? -Steve

5 4

Re: FreeBSD configure fix
by Andreas Mohr 07 Nov '02

07 Nov '02

On Thu, Nov 07, 2002 at 06:21:14PM +0100, Patrik Stridvall wrote: > Gerald Pfeifer configure change broke FreeBSD 4.7 > This should fix it. ROTFL !! The "man who is constantly annoyed about having to fix stupid Linux breakage on *BSD" manages to break *BSD :-)) -- Andreas Mohr Stauferstr. 6, D-71272 Renningen, Germany Tel. +49 7159 800604 http://mohr.de.tt

1 0

Re: ComputerName
by Dimitrie O. Paun 07 Nov '02

07 Nov '02

On November 6, 2002 10:27 am, Martin Wilck wrote: > - Keep old behavior as default, using new config option to change. Can you also please update the documentation as well (man pages, etc.)? -- Dimi.

5 14

RE: Wine 0.9 TODO v0.2
by Medland, Bill 07 Nov '02

07 Nov '02

> -----Original Message----- > From: wine-devel-admin(a)winehq.com > [mailto:wine-devel-admin@winehq.com]On > Behalf Of Dimitrie O. Paun > Sent: Wednesday, November 06, 2002 11:21 PM > To: Wine Devel > Subject: Wine 0.9 TODO v0.2 > > > Folks, > > This time in HTML & Technicolor, at: > > http://www.dssd.ca/Wine-0.9-TODO.html > > Please take a look, and let me know if you think > anything needs to change. If you are listed there > on a task, a status update would be more than > appreciated. If you feel like working on something, > I would like to know to add you in there. > > NOTE: most tasks don't require coding, so don't be > shy, and step up to the challenge. ;) > > -- > Dimi. > Dimi (et al) I guess I could do B.2; Move CVS Docu from User Guide to Devel guide. Before doing so, though, I just want to check what that means. I presume that this means moving the "Getting Wine Source code from CVS" section. I wonder if that is exactly what we want. Are we trying to avoid scaring beginners and non-programmers? If we basically mean that the user Guide will not talk about getting the source and compiling it on your own machine then we might as well also move "Getting Wine Source Code from the FTP archive" and "Upgrading Wine with a patch" If we basically mean that we suggest that the user be able to build from source but only from the FTP archive versions then do we really need the "Upgrading Wine with a patch" If we support the user being able to build from source but don't want to scare them then all we need to do is drop the talk about changing the code and diffing (and maybe adding a little more hand-holding to the cvs section a la dummies guide). Also if we go towards the "build from source" we are going to have to address little issues like the tendency not to install the compiler these days. My suggestion is that, since we are talking about fairly stable releases, we ought to move all the sections concerned with building from source. Guidance please. Bill

3 2

RE: Wine 0.9 TODO v0.2
by Medland, Bill 07 Nov '02

07 Nov '02

> -----Original Message----- > From: Dimitrie O. Paun [mailto:dpaun@rogers.com] > Sent: Thursday, November 07, 2002 9:42 AM > To: Medland, Bill; Wine Devel > Subject: Re: Wine 0.9 TODO v0.2 > > > On November 7, 2002 12:37 pm, Medland, Bill wrote: > > My suggestion is that, since we are talking about fairly > stable releases, > > we ought to move all the sections concerned with building > from source. > > I think so. User Guide should all about how you use Wine, not how you > develop it, build it, etc. We should just add a small note to the > User Guide pointing people to the other guide, if interested in > building from source. > > You're on. That was quick!! Catch them while you can, Eh? I'll wait a couple of days to allow any discussion on the list. > > -- > Dimi. > Bill

1 0

Re: Wine FAQ - call for a volunteer
by Ulf Dambacher 07 Nov '02

07 Nov '02

Just one tip: Why not use a wiki-Engine to creaate/maintain a faq, like e.g. www.squirrelmail.net does? I recommend phpwiki (http://phpwiki.sourceforge.net/) This way users can maintain the faq and it is most up to date! Greetings Ulf

3 2

Pls help me.
by yf 07 Nov '02

07 Nov '02

When I using wine start a winapp, it first download some data and then save it to the disk. But when save the data, it always says "Disk full while accessing C:\south\Base.map. What's the matter with it? How could I resolve it? Pls give me some hints? Best regards. /yf

2 1

Re: [PATCHLET] DeleteFile With Empty Paths
by Marcus Meissner 07 Nov '02

07 Nov '02

On Thu, Nov 07, 2002 at 02:18:20AM -0800, Ryan Cumming wrote: > Hi, > > KaZaA Lite 2.0 calls DeleteFile with an empty path at shutdown, which triggers > ERR("Empty path passed\n"). It seems a bit silly to call that an error, so > this patch changes the message to a warning. It also does a > SetLastError(ERROR_FILE_NOT_FOUND) in that case, which is consistant with > Windows XP. Can you also create a testcase for this problem? Ciao, Marcus

1 0

Wine 0.9 TODO v0.2
by Dimitrie O. Paun 07 Nov '02

07 Nov '02

Folks, This time in HTML & Technicolor, at: http://www.dssd.ca/Wine-0.9-TODO.html Please take a look, and let me know if you think anything needs to change. If you are listed there on a task, a status update would be more than appreciated. If you feel like working on something, I would like to know to add you in there. NOTE: most tasks don't require coding, so don't be shy, and step up to the challenge. ;) -- Dimi.

1 0

Re: Interrupts / Move most of int31 to winedos
by Jukka Heinonen 06 Nov '02

06 Nov '02

Andreas Mohr wrote: > On Tue, Nov 05, 2002 at 06:47:35PM +0200, Jukka Heinonen wrote: > > After this patch winedos contains almost complete int31 > > emulation. What has not been moved to winedos is mostly > > functions that require either W32S_WINE2APP or W32S_APP2WINE. > > This makes me wonder whether Wine still needs to support WIN32S... > Well, of course it does. > Wine is supposed to run *all* reasonably new (i.e.: not "standard mode") > Windows programs, and that does include Win32s IMHO. Sure, I know that (I'm working on DPMI32 which isn't for standard mode Windows programs), I was probably being a bit unclear about what I was wondering about. It is quite difficult to find any information about Win32s nowadays and everything I have found was suggesting that Win32s was for running Win32 applications on Win16. Since Wine does run Win32 applications directly it just made me wonder whether Win32s support is something that was once needed when Wine only had Win16 support. But, since I know very little about Win32s, I can only wonder. It all depends on how Win32s applications differ from Win32 and Win16 applications. The existence of Win32s dlls seems to suggest that Win32s applications are not regular Win32 applications as well as the text in "msdos/vxd.c" which talks about some strange pointer mangling required with Win32s applications. This mangling is probably something that is only required if Wine supports official Win32s dlls. Which makes me wonder if Win32s dlls provided by Wine actually do work because they don't seem to do any pointer mangling. Well, it could be that Win32s applications do this pointer mangling internally. Anyway, I seem to have answered myself. If Wine is going to support Win32s applications using both builtin and official Win32s dlls, it needs pointer mangling. I just have to figure out how the required offset can be accessed from multiple dlls because I would really like to have all the interrupt handlers in one place. I still think that all the tricks required in order to support official Win32s dlls are quite ugly: all the routines that use linear addresses and are called directly by Win32s applications need to do pointer mangling and msdos/vxd.c actually modifies the official dlls in order to work around some problems. But since this most likely works already, I don't think I want to change anything. -- Jukka Heinonen <http://www.iki.fi/jhei/>

8 14

Re: Wine history
by Robert Amstadt 06 Nov '02

06 Nov '02

> If you live near one of these people, buy them a beer. If any of the current developers live in or around San Jose, CA, U.S., I'd be happy to buy you a beer. Thank you, Dan, for digging up that history. It is always wierd though to read my past words and realize that someone is archiving them. ----- Bob Amstadt http://www.amstadt.com/~bob bob(a)amstadt.com

1 0

Wine history
by Dan Kegel 06 Nov '02

06 Nov '02

Here are a few early posts: ============================ http://groups.google.com/groups?selm=1993Jul2.173648.3202%40amscons.com Newsgroups: comp.os.linux From: bob(a)amscons.com (Bob Amstadt) Subject: Re: Impressions of WABI/Univel vs Linux References: <C9JoGx.IMM(a)news2.cis.umn.edu> Organization: Amstadt Consulting Group Date: Fri, 2 Jul 1993 17:36:48 GMT X-Newsreader: Tin 1.1 PL4 Message-ID: <1993Jul2.173648.3202(a)amscons.com> Lines: 7 Of course, for those of you who are interested in running Windows programs there is an effort in progress to create something similar to Sun's WABI. There is an activists channel, "WABI", for discussion of this project. There is need for many volunteers to complete this project. -- Bob Amstadt bob(a)amscons.com ============================ http://groups.google.com/groups?selm=1993Aug5.153058.1530%40amscons.com Newsgroups: comp.windows.x.i386unix From: bob(a)amscons.com (Bob Amstadt) Subject: Re: WABI how good is it? References: <1993Aug4.134724.24562(a)jarvis.csri.toronto.edu> <CB96AH.2GDK(a)austin.ibm.com> Organization: Amstadt Consulting Group Date: Thu, 5 Aug 1993 15:30:58 GMT Message-ID: <1993Aug5.153058.1530(a)amscons.com> Lines: 27 In <CB96AH.2GDK(a)austin.ibm.com> guyd(a)austin.ibm.com (Guy Dawson) writes: >In article <1993Aug4.134724.24562(a)jarvis.csri.toronto.edu>, arisz(a)csri.toronto.edu (Aris Zakinthinos) writes: >> I have been reading in the local papers about WABI being able to >> translate MS Windows API calls into X calls in real time. Has anybody >> tried it? Is it any good? How about those calls that somehow made it >> into the code but not the docs (i.e. the undocumented calls). I am >> curious to here what it is like. If this realy does work then I may >> never use MS Windows again!!!! How is it being distributed? >> >It's not available yet! >It's a Windows run time enviroment for Unix boxes - Sun started it and >are going to produce it for their boxes. I don't know who else is looking >to support it... Well, those of us in the Linux camp are working on a similar project. It could be extended to run on other Unix operating systems if they would be willing to provide us with the necessary call to manipulate the LDT for the process. Perhaps someone using one of the BSD derivatives would like to get involved with our project? Questions about this project may be directed toward me. -- Bob Amstadt bob(a)amscons.com ============================ http://groups.google.com/groups?selm=1993Aug17.200321.4496%40amscons.com Newsgroups: comp.os.linux.misc From: bob(a)amscons.com (Bob Amstadt) Subject: Re: WABI/WINAPI - a Retraction References: <1993Aug17.143450.22682(a)cc.gatech.edu> Organization: Amstadt Consulting Group Date: Tue, 17 Aug 1993 20:03:21 GMT Message-ID: <1993Aug17.200321.4496(a)amscons.com> Lines: 19 In <1993Aug17.143450.22682(a)cc.gatech.edu> byron(a)cc.gatech.edu (Byron A Jeff) writes: >2) The WABI folks aren't talking. I have not seen any software yet. Well, considering the fact that we only got started in June, I think we are pretty far along. We don't have any off-the-shelf binaries running yet, but we can run binaries that contain only implemented API functions. We are always looking for more help. Only four people have provided code to the current emulator. I would gues that 80% of that code has been written by two people. If you would like to join the effort, join the linux-activists WABI channel. The name of the project is now Wine, and we have a directory under /pub/linux/ALPHA on tsx-11. Currently there is only a README file which contains information about the status of the project. -- Bob Amstadt bob(a)amscons.com ============================ http://groups.google.com/groups?selm=26ai6a%24mob%40samba.oit.unc.edu From: bob(a)amscons.com (Bob Amstadt) Newsgroups: comp.os.linux.announce Subject: Wine project status update Followup-To: comp.os.linux.misc Date: 4 Sep 1993 17:10:34 GMT Organization: Amstadt Consulting Group Lines: 84 Approved: linux-announce(a)tc.cornell.edu (Matt Welsh) Message-ID: <26ai6a$mob(a)samba.oit.unc.edu> Reply-To: bob(a)amscons.com (Bob Amstadt) NNTP-Posting-Host: calypso.oit.unc.edu Summary: You like the Wine? The Wine is good? I get you more Wine. Keywords: WABI Wine MS Windows Emulator Originator: mdw@sunSITE Numerous people have requested that the project status of Wine be posted regularly. For the benifit of those people, I am posting the latest README file that I have uploaded to tsx-11... The Wine project for linux is an attempt to write something with similar functionality to the WABI that was developed by Sun. The basic goal is to be able to take a MS-Windows binary and run it under Linux with X-Windows running. The finished product will essentiaily consist of two parts: a) A program loader, which will load the Windows binary into the virtual memory of the linux process, provide a means for adjusting the ldt of the processor so that the 16-bit segments that are typically used with Windows binaries will work correctly, and provide a means for calling the Windows binary in the first place, allowing the Windows binary to call back to the 32-bit mode program, and finally allow the 32-bit mode program to call back again to the Windows binary (i.e. Windows callbacks). In each case, the arguments being passed wil have to be pulled from the appropriate stack and loaded on to the other stack (there will be a 16 bit and a 32 bit stack). Finally some application specfic DLL libraries will have to be loaded, and dynamic linking will have to be performed. b) The second part of the finished product is an emulation library, which takes calls to Windows functions, and somehow translates these into calls to X11 in one fashion or another, so that equivalent functionality is achieved. It should be pointed out that the Windows binary will be running directly - there will be no need for machine level emulation of the instructions. Sun has reported better performance with their version of WABI than is actually achieved under MS-Windows - theoretically the same result is possible under linux. The project got started as a result of discussions on comp.os.linux in early June of 1993. A mail channel was set up for discussions, and this directory was created. At the moment, all of the files that are uploaded are in the private directory in a hidden directory. The reason for this is that the program is really only of use to developers right now. Once something is ready for public consumption, it will be uploaded to a publicly visible directory. The final product will almost certainly be under the GNU Public License (or GPL for short). If you are interested in getting involved in this project, join the linux activists' WABI channel. If you have never joined a channel before, send mail to linux-activists-request(a)niksul.hut.fi. It will reply with a help message. New releases are approximately every Tuesday. All releases are announced to the WABI channel. Also, I will do my best to answer any question mailed to me. My address is "bob(a)amscons.com". *************************************************************** Status Report - September 3, 1993 Windows Solitaire is barely playable for the first time today. Special thanks go to Alexandre Julliard, Eric Youngdale, David Metcalfe and Peter MacDonald for their work on this project. If you live near one of these people, buy them a beer. It looks like the Linux kernel modifications are nearing completion. Hopefully the next Linux kernel (0.99.13 ?) will not require patching to run Wine. The loader portion is nearing completion. Sample Windows binaries are loaded correctly into memory, dynamicly linked and so forth. The 16/32 bit call interface is fairly complete. There are still a few features that remain to be added before it can be considered "done", but it is at the point where it is actually useful. Resource loading is only partially complete. A very minimal version of the emulation library has been merged with the loader. Windows can be created, DC's may be used, bitmaps are handled, text drawing is implemented, and a preliminary implementation of menus has been created. Bugs are still present in many of the implemented functions, but things are starting to look up. -- Bob Amstadt bob(a)amscons.com -- Send submissions for comp.os.linux.announce to: linux-announce(a)tc.cornell.edu

1 0

Forgive the intrusion
by Robert Amstadt 06 Nov '02

06 Nov '02

Please don't let me distract you from your important work, but Thomas Wickline asked me to stop in and say hello to all of you. I understand that we are approaching the 10 year anniversary of Wine. That is a remarkable feat. All of you should be proud to be contributing to this effort. It is an amazing piece of software. Though many of the names I see on the WineHQ web site are new to me. I continue to see Alexandre Julliard's name on this work. I had the pleasure of meeting Alexandre many years ago and I am so glad to see that he continues the work after so many years. Alexandre, if you read this, thank you very much for all that you have done for free software. Thank you to the rest of you as well. Wine has been a team effort from the start and is so successful because it is a team effort. When I stepped down from leading this project, I knew it would continue due to the efforts of all the people that have helped along the way. It not only has continued, but it clearly thrives. I'm amazed at the number of people that know what Wine is. Congratulations to all of you Wine developers. You are amazing people. ----- Bob Amstadt http://www.amstadt.com/~bob bob(a)amstadt.com

2 1

Re: templates support to commdlg ChooseFont
by Shachar Shemesh 06 Nov '02

06 Nov '02

One more bug: FIXME still reports the CF_ENABLETEMPLATE flag as non-supported. Shachar Shemesh wrote: > ChangeLog: > Shachar Shemesh <winecode(a)sun.consumer.org.il> > > Todo: > > * Implement support for the scripts selection. > o Enum the scripts the font supports, and display the list > accordingly. > o Make the sample text use characters from the selected script > (today SOME resources included the local text, which is not > the correct behaviour). > o Implement the Unicode version of script selection properly. > > Bugs: > > * Non functional changes were only applied to the English resource. > I'm sorry, I'm sick (literally - I'm ill), and my sed skills are > not very good. I only performed the changes that were required in > order to keep the code functioning. > * The windows method is to pass stc5 not visible, and the commdlg > code created a BUTTON with the same ID at the same place. I'm not > sure why that is, probably so things will be visibily pleasing. > Our code, if passed not visible, will not display the sample text. > > > > dlls/commdlg/cdlg_En.rc > > * Changed all numeric resources in ChooseFont to labels for better > readability. > > dlls/commdlg/cdlg_*.rc > > * Changed control #1093 (sample text) to stc5 (1092) to convert to > Windows compatible numbers. > > dlls/commdlg/fontdlg.c > > * Changed all handling of stc6 (1093) to atc5 (1092) so that will be > compatible with Windows resource numbers. > * Added code to load the user's resources rather than our own if > CF_ENABLETEMPLATE is passed in "flags". > > > >

1 0

IDL/header issues
by Ove Kaaven 06 Nov '02

06 Nov '02

Now WIDL is good enough to generate a drop-in replacement for Wine's wtypes.h (attached) from a suitably crafted Wine-compatible wtypes.idl (also attached). I've included all the definitions that were already in Wine's wtypes.h (but I was too lazy to do everything that's in Microsoft's wtypes.idl yet). What do you think, is this good enough to go into Wine? Are there some desirable changes to widl or wtypes.idl? And should IDL files go into the main include dir along with the other Win32 headers? IDL-generated files would also eventually obsolete all the current wine/obj_*.h files, but those obj_* files seem to be somewhat more logically structured than MS's own IDL files, should we craft Wine's IDL files accordingly, and maybe have some top-level .idl files in include/ and some sub-.idl files under include/wine/, like it's done now in e.g. objidl.h? Note that I will work on ReWind, not directly on Wine, so I probably won't be able to submit massive "change all files to include this instead of that" patches (that apply to Wine) with any new files.

3 13

RE: Wine headers mismatch
by Patrik Stridvall 06 Nov '02

06 Nov '02

> On November 6, 2002 02:38 pm, Patrik Stridvall wrote: > > Fixed mismatches between the Wine headers and the Microsoft headers. > > Patrick, what's the status of compiling stuff on Windows? The tests compiles fine (except for ntdll if the Microsoft headers are used). Some fails on Windows when running, but I haven't had time to look at it very much. As for the normal dlls: Well some compile most don't. Quite a lot of work remains. However the compilation instructure generated by msvcmaker work quite well, so if anybody want to help they can. I have a lot of kludges in my MSVC tree so you might run into some problems though...

2 1

Re: Wine headers mismatch
by Dimitrie O. Paun 06 Nov '02

06 Nov '02

On November 6, 2002 02:38 pm, Patrik Stridvall wrote: > Fixed mismatches between the Wine headers and the Microsoft headers. Patrick, what's the status of compiling stuff on Windows? -- Dimi.

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-devel