Here is the list of Wine Static and Shareable Files after some updates. Same as before if you see something that's wrong could you let me know. Tom ----------- -- = files that are listed in this Doc but are not installed on my system. * = files are in this Doc and on my system @ = files that are on my system but not in the Doc # = files that are not in the Doc or on my System ( wineboot ) will be in future releases ? -- dosmod : Deleted as of Jan 2001. -- fnt2bdf : Discussed on Wine-Devel ( practically obsolete ) @ notepad : The windows Notepad replacement @ progman : Program Manager for WINE. @ regedit : A tool to edit your regestory or for exporting a windows registory to Wine. @ regsvr32 : A program to register .DLL's and .OCX files. @ uninstaller: A Winelib program to uninstall installed Windows programs. @ wcmd : Wine's command line interpreter @ widl : Wine IDL compiler * wine : The main Wine executable. This program will load a Windows binary and run it, relying upon the Wine shared object libraries. # wineboot : A Winelib application that's executed by Wine on startup of the first wine process of a particular user. wineboot won't automatically run when needed. Currently you have to manually run it after you install something. A list of what it currently does. * wininit.ini processing * registry RenameFiles entries * RunServices* / RunOnce* / Run registry keys -- winebootup : Now wineboot...... * winebuild : Winebuild is a tool used for Winelib applications (and by Wine itself) to allow a developer to compile a .spec file into a .spec.c file. * wineclipserv : The Wine Clipboard Server is a standalone XLib application whose purpose is to manage the X selection when Wine exits. @ wineconsole : a console program for wine, For running CUI executables (Windows console programs), use wineconsole instead of wine run). Not using wineconsole for CUI programs will only provide very limited console support, and your program might not function properly. * winedbg : Winedbg is the Wine built in debugger. @ winedump : A NE and PE file dumper @ winefile : A clone of the win3x filemanager @ winegcc/wineg++: Wrappers for gcc/g++ respectively, to make them behave as MinGW's gcc. Used for porting app's over to winelib. * winelauncher : A wine wrapper shell script that intelligently handles wine invocation by informing the user about what's going on, among other things. To be found in tools/ directory. Use of this wrapper script instead of directly using wine is strongly encouraged, as it not only improves the user interface, but also adds important functionality to wine, such as session bootup/startup actions. If you intend to use this script, then you might want to rename the wine executable to e.g. wine.bin and winelauncher to wine. the WINECONFDIR/config file. winemaker : Winemaker is a perl script which is designed to help you bootstrap the conversion of your Windows projects to Winelib. In order to do thisit will go analyze your code, fixing the issues listed above and generate autoconf-based Makefiles. @ winemine : A clone of "Windows Minesweeper" @ winepath : Specifies the path(s) in which to search for builtin dlls and Winelib applications. * wineserver : The Wine server is critical to Wine; it is the process that coordinates all shared Windows resources. -- winesetup : This is a Tcl/Tk based front end that provides a user friendly tool to edit and configure the WINECONFDIR/config file. * wineshelllink : This shell script can be called by Wine in order to propagate Desktop icon and menu creation requests out to a GNOME or KDE (or other Window Managers). @ winewrap : Takes care of linking winelib applications. Linking with winelib is a complex process, winewrap makes it simple. @ winhelp : For viewing windows help files * wmc : Wine Message Compiler it allows Windows message files to be compiled into a format usable by Wine. * wrc : Wine Resource Compiler. It allows Winelib programmers (and Wine itself) to compile Windows style resource files into a form usable by Wine.
I would like to thank everyone who has helped so far on this. If you see something out of pace please comment on it. If everything looks good ill send a patch to alexandre in a couple days after everyone has had time to look this over. Tom --------------------------- 2003/02/03 -- = files that are listed in this Doc but are not installed on my system. * = files are in this Doc and on my system @ = files that are on my system but not in the Doc # = files that are not in the Doc or on my System ( wineboot ) will be in future releases ? -- dosmod : Deleted as of Jan 2001. -- fnt2bdf : Discussed on Wine-Devel ( practically obsolete ) @ notepad : The windows Notepad replacement @ progman : A program Manager for WINE. @ regedit : A command-line tool to edit your registry or for important a windows registry to Wine. @ regsvr32 : A program to register/unregister .DLL's and .OCX files. Only works on those dlls that can self-register. @ uninstaller: A program to uninstall installed Windows programs. Like the Add/Remove Program in the windows control panel. @ wcmd : Wine's command line interpreter a cmd.exe replacement. @ widl : Wine IDL compiler compiles (MS-RPC and DCOM) Interface Definition Language files (into something useful for compiling Wine and Winelib apps, similar to wmc and wrc). Should also be able to generate typelibs (someday). * wine : The main Wine executable. This program will load a Windows binary and run it, relying upon the Wine shared object libraries. # wineboot : This program is executed on startup of the first wine process of a particular user. wineboot won't automatically run when needed. Currently you have to manually run it after you install something. A list of what it currently does. * wininit.ini processing * registry RenameFiles entries * RunServices* / RunOnce* / Run registry keys -- winebootup : Now wineboot...... * winebuild : Winebuild is a tool used for building Winelib applications (and by Wine itself) to allow a developer to compile a .spec file into a .spec.c file. * wineclipserv : The Wine Clipboard Server is a standalone XLib application whose purpose is to manage the X selection when Wine exits. @ wineconsole : The purpose of wineconsole is to render the output of CUI programs it does so either thru a window (called the USER32 backend) or by using an existing unix shell (called the curses backend) the first backend is triggered when the app programmatically opens a console (AllocConsole) the second one is triggered on startup by using wineconsole myapp.exe instead of wine myapp.exe on the command line * winedbg : A application making use of the debugging API to allow debugging of Wine or Winelib applications as well as Wine itself (kernel and all DLLs). @ winedump : Dumps the imports and exports of NE and PE (Portable Executable) files. DLL (included in wine tree). @ winefile : A clone of the win3x filemanager. @ winegcc/wineg++: Wrappers for gcc/g++ respectively, to make them behave as MinGW's gcc. Used for porting apps over to winelib. * winelauncher : A wine wrapper shell script that intelligently handles wine invocation by informing the user about what's going on, among other things. To be found in tools/ directory. Use of this wrapper script instead of directly using wine is strongly encouraged, as it not only improves the user interface, but also adds important functionality to wine, such as session bootup/startup actions. If you intend to use this script, then you might want to rename the wine executable to e.g. wine.bin and winelauncher to wine. the WINECONFDIR/config file. @ winemaker : Winemaker is a perl script which is designed to help you bootstrap the conversion of your Windows projects to Winelib. In order to do thisit will go analyze your code, fixing the issues listed above and generate autoconf-based Makefiles. @ winemine : A clone of "Windows Minesweeper" a demo WineLib app. @ winepath : A tool for converting between Windows paths and Unix paths (useful for shell scripts ans such). * wineserver : The Wine server is the process that manages resources, coordinates threads, and provides synchronization and interprocess communication primitives to Wine processes. -- winesetup : This is a Tcl/Tk based front end that provides a user friendly tool to edit and configure the WINECONFDIR/config file. * wineshelllink : This shell script can be called by Wine in order to propagate Desktop icon and menu creation requests out to a GNOME or KDE (or other Window Managers). @ winewrap : Takes care of linking winelib applications. Linking with winelib is a complex process, winewrap makes it simple. @ winhelp : When Windows (at least 3.0, but it may well have appeared in 2.0) was launched, a help system was designed. Help information is stored in .hlp files, and was viewed with winhelp.exe (16 bit application). When Windows 95 was launched, the same help system still existed (even it grew in complexity), and help was viewed by a 32 bit application (winhlp32.exe). Those help files (.hlp) are in fact generated by a specific build system, starting from RTF files, with some very styles to define the specific portions (pages, links...). When an application requires a specific help page to be displayed, it calls an API (WinHelp), specifying the name of the help file, and a information about what needs to be displayed (hence the context sensitive help). When the Internet wave was clear to the MS folks, they moved the help system architecture to HTML files (replacing the RTF sources). That are the .CHM files (basically, compressed HTML files and their embedded information - images, metafiles...), which are normally displayed by an OCX (which basically decompress the right files and ask IWebBrowser to display them).hh.exe (which is now the .CHM viewer) is just a wrapper to that OCX. * wmc : Wine Message Compiler it allows Windows message files to be compiled into a format usable by Wine. * wrc : Wine Resource Compiler. It allows Winelib programmers (and Wine itself) to compile Windows style resource files into a form usable by Wine.
On February 3, 2003 05:25 am, Tom Wickline wrote:
-- dosmod : Deleted as of Jan 2001.
-- fnt2bdf : Discussed on Wine-Devel ( practically obsolete )
Are you deleting these from the guide?
@ progman : A program Manager for WINE.
Why not: A Program Manager replacement.
@ regedit : A command-line tool to edit your registry or for important a windows registry to Wine.
What about: A Registry Editor replacement.
@ regsvr32 : A program to register/unregister .DLL's and .OCX files. Only works on those dlls that can self-register.
I'd just delete the second sentence. It does not matter for the purpose of the guide.
@ uninstaller: A program to uninstall installed Windows programs. Like the Add/Remove Program in the windows control panel.
@ wcmd : Wine's command line interpreter a cmd.exe replacement.
Maybe a comma is needed after interpreter.
@ widl : Wine IDL compiler compiles (MS-RPC and DCOM) Interface Definition Language files (into something useful for compiling Wine and Winelib apps, similar to wmc and wrc). Should also be able to generate typelibs (someday).
I'd keep just the first part, up to the (into something...
* wine : The main Wine executable. This program will load a Windows binary and run it, relying upon the Wine shared object libraries.
# wineboot : This program is executed on startup of the first wine process of a particular user. wineboot won't automatically run when needed. Currently you have to manually run it after you install something. A list of what it currently does.
* wininit.ini processing * registry RenameFiles entries * RunServices* / RunOnce* / Run registry keys
Get rid of A list of ....
-- winebootup : Now wineboot......
I hope this goes away.
@ wineconsole : The purpose of wineconsole is to render the output of CUI programs it does so either thru a window (called the USER32 backend) or by using an existing unix shell (called the curses backend) the first backend is triggered when the app programmatically opens a console (AllocConsole) the second one is triggered on startup by using wineconsole myapp.exe instead of wine myapp.exe on the command line
This is far too long for the packager's guide. Just say: A console replacement. It is used to render the output of CUI programs.
@ winedump : Dumps the imports and exports of NE and PE (Portable Executable) files. DLL (included in wine tree).
I'd get rid of "DLL (included in wine tree)."
* winelauncher : A wine wrapper shell script that intelligently handles wine invocation by informing the user about what's going on, among other things. To be found in tools/ directory. Use of this wrapper script instead of directly using wine is strongly encouraged, as it not only improves the user interface, but also adds important functionality to wine, such as session bootup/startup actions. If you intend to use this script, then you might want to rename the wine executable to e.g. wine.bin and winelauncher to wine. the WINECONFDIR/config file.
Way too long of a description, compared to all others. Besides, this script will go away soon (I hope). Maybe we shouldn't even document it.
@ winemaker : Winemaker is a perl script which is designed to help you bootstrap the conversion of your Windows projects to Winelib. In order to do thisit will go analyze your code, fixing the issues listed above and generate autoconf-based Makefiles.
thisit == this, it
@ winepath : A tool for converting between Windows paths and Unix paths (useful for shell scripts ans such).
ans = and
-- winesetup : This is a Tcl/Tk based front end that provides a user friendly tool to edit and configure the WINECONFDIR/config file.
Is this going away?
@ winhelp : When Windows (at least 3.0, but it may well have appeared in 2.0) was launched, a help system was designed. Help information is stored in .hlp files, and was viewed with winhelp.exe (16 bit application). When Windows 95 was launched, the same help system still existed (even it grew in complexity), and help was viewed by a 32 bit application (winhlp32.exe). Those help files (.hlp) are in fact generated by a specific build system, starting from RTF files, with some very styles to define the specific portions (pages, links...). When an application requires a specific help page to be displayed, it calls an API (WinHelp), specifying the name of the help file, and a information about what needs to be displayed (hence the context sensitive help). When the Internet wave was clear to the MS folks, they moved the help system architecture to HTML files (replacing the RTF sources). That are the .CHM files (basically, compressed HTML files and their embedded information - images, metafiles...), which are normally displayed by an OCX (which basically decompress the right files and ask IWebBrowser to display them).hh.exe (which is now the .CHM viewer) is just a wrapper to that OCX.
Why soooo long? Why not: A Windows Help replacement. Just like progman, winemine, etc. -- Dimi.
Okay how does this look ? Tom ---------------- notepad : The windows Notepad replacement. progman : A Program Manager replacement. regedit : A command-line tool to edit your registry or for important a windows registry to Wine. regsvr32 : A program to register/unregister .DLL's and .OCX files. Only works on those dlls that can self-register. uninstaller: A program to uninstall installed Windows programs. Like the Add/Remove Program in the windows control panel. wcmd : Wine's command line interpreter, a cmd.exe replacement. widl : Wine IDL compiler compiles (MS-RPC and DCOM) Interface Definition Language files. wine : The main Wine executable. This program will load a Windows binary and run it, relying upon the Wine shared object libraries. wineboot : This program is executed on startup of the first wine process of a particular user.wineboot won't automatically run when needed. Currently you have to manually run it after you install something. winebuild : Winebuild is a tool used for building Winelib applications (and by Wine itself) to allow a developer to compile a .spec file into a .spec.c file. wineclipserv : The Wine Clipboard Server is a standalone XLib application whose purpose is to manage the X selection when Wine exits. wineconsole : The purpose of wineconsole is to render the output of CUI programs. winedbg : A application making use of the debugging API to allow debugging of Wine or Winelib applications as well as Wine itself (kernel and all DLLs). winedump : Dumps the imports and exports of NE and PE (Portable Executable) files. winefile : A clone of the win3x filemanager. winegcc/wineg++: Wrappers for gcc/g++ respectively, to make them behave as MinGW's gcc. Used for porting apps over to winelib. winemaker : Winemaker is a perl script which is designed to help you bootstrap the conversion of your Windows projects to Winelib. In order to do this it will go analyze your code, fixing the issues listed above and generate autoconf-based Makefiles. winemine : A clone of "Windows Minesweeper" a demo WineLib app. winepath : A tool for converting between Windows paths and Unix paths (useful for shell scripts and such). wineserver : The Wine server is the process that manages resources, coordinates threads, and provides synchronization and interprocess communication primitives to Wine processes. wineshelllink : This shell script can be called by Wine in order to propagate Desktop icon and menu creation requests out to a GNOME or KDE (or other Window Managers). winewrap : Takes care of linking winelib applications. Linking with winelib is a complex process, winewrap makes it simple. winhelp : A Windows Help replacement. wmc : Wine Message Compiler it allows Windows message files to be compiled into a format usable by Wine. wrc : Wine Resource Compiler. It allows Winelib programmers (and Wine itself) to compile Windows style resource files into a form usable by Wine.
On Tue, 4 Feb 2003, Tom Wickline wrote:
Okay how does this look ?
I propose the following changes, nothing really major: --- descs.txt.orig 2003-02-04 13:02:08.000000000 -0800 +++ descs.txt 2003-02-04 13:15:02.000000000 -0800 @@ -4,18 +4,21 @@ ---------------- -notepad : The windows Notepad replacement. +notepad : The Windows Notepad replacement. progman : A Program Manager replacement. -regedit : A command-line tool to edit your registry or for important a -windows registry to Wine. - -regsvr32 : A program to register/unregister .DLL's and .OCX files. Only -works on those dlls that can self-register. - -uninstaller: A program to uninstall installed Windows programs. Like the -Add/Remove Program in the windows control panel. +regedit : A command-line compatible replacement for the Windows +regedit tool. Wine's regedit tool does not have a graphical +interface but makes it possible for applications to manipulate +the registry and to import .reg files. + +regsvr32 : The Windows regsvr32 replacement. This lets applications +register/unregister self-registering dlls and ocx files. + +uninstaller: A program to uninstall installed Windows programs. Its +functionality is similar to the Add/Remove Program in the Windows +control panel. wcmd : Wine's command line interpreter, a cmd.exe replacement. @@ -25,8 +28,8 @@ wine : The main Wine executable. This program will load a Windows binary and run it, relying upon the Wine shared object libraries. -wineboot : This program is executed on startup of the first wine process -of a particular user.wineboot won't automatically run when needed. +wineboot : This program is executed on startup of the first Wine process +of a particular user. wineboot won't automatically run when needed. Currently you have to manually run it after you install something. winebuild : Winebuild is a tool used for building Winelib applications @@ -46,15 +49,15 @@ winedump : Dumps the imports and exports of NE and PE (Portable Executable) files. -winefile : A clone of the win3x filemanager. +winefile : A clone of the win3x file manager. winegcc/wineg++: Wrappers for gcc/g++ respectively, to make them behave -as MinGW's gcc. Used for porting apps over to winelib. +as MinGW's gcc. Used for porting apps over to Winelib. -winemaker : Winemaker is a perl script which is designed to help you +winemaker : Winemaker is a perl script designed to help you bootstrap the conversion of your Windows projects to Winelib. In order -to do this it will go analyze your code, fixing the issues listed above -and generate autoconf-based Makefiles. +to do this it will analyze your code, fix the issues it finds +and generate autoconf-based makefiles. winemine : A clone of "Windows Minesweeper" a demo WineLib app. @@ -65,16 +68,16 @@ coordinates threads, and provides synchronization and interprocess communication primitives to Wine processes. -wineshelllink : This shell script can be called by Wine in order to -propagate Desktop icon and menu creation requests out to a GNOME or KDE -(or other Window Managers). +wineshelllink : This shell script is called by Wine in order to +propagate desktop icon and menu creation requests to the native +desktop environment such as Gnome, KDE or other window managers. -winewrap : Takes care of linking winelib applications. Linking with -winelib is a complex process, winewrap makes it simple. +winewrap : Takes care of linking Winelib applications. Linking with +Winelib is a complex process, winewrap makes it simple. winhelp : A Windows Help replacement. -wmc : Wine Message Compiler it allows Windows message files to be +wmc : Wine Message Compiler. It allows Windows message files to be compiled into a format usable by Wine. wrc : Wine Resource Compiler. It allows Winelib programmers (and Wine -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ Advice is what we ask for when we already know the answer but wish we didn't -- Eric Jong
Also maybe add something like # explorer : A clone of the Windows interface, needed for certain applications and testing of the common controls. --- Tom Wickline <twickline2(a)triad.rr.com> wrote:
I would like to thank everyone who has helped so far on this. If you see something out of pace please comment on it. If everything looks good ill send a patch to alexandre in a couple days after everyone has had time to look this over.
Tom
--------------------------- 2003/02/03
-- = files that are listed in this Doc but are not installed on my system. * = files are in this Doc and on my system @ = files that are on my system but not in the Doc # = files that are not in the Doc or on my System ( wineboot ) will be in future releases ?
-- dosmod : Deleted as of Jan 2001.
-- fnt2bdf : Discussed on Wine-Devel ( practically obsolete )
@ notepad : The windows Notepad replacement
@ progman : A program Manager for WINE.
@ regedit : A command-line tool to edit your registry or for important a windows registry to Wine.
@ regsvr32 : A program to register/unregister .DLL's and .OCX files. Only works on those dlls that can self-register.
@ uninstaller: A program to uninstall installed Windows programs. Like the Add/Remove Program in the windows control panel.
@ wcmd : Wine's command line interpreter a cmd.exe replacement.
@ widl : Wine IDL compiler compiles (MS-RPC and DCOM) Interface Definition Language files (into something useful for compiling Wine and Winelib apps, similar to wmc and wrc). Should also be able to generate typelibs (someday).
* wine : The main Wine executable. This program will load a Windows binary and run it, relying upon the Wine shared object libraries.
# wineboot : This program is executed on startup of the first wine process of a particular user. wineboot won't automatically run when needed. Currently you have to manually run it after you install something. A list of what it currently does.
* wininit.ini processing * registry RenameFiles entries * RunServices* / RunOnce* / Run registry keys
-- winebootup : Now wineboot......
* winebuild : Winebuild is a tool used for building Winelib applications (and by Wine itself) to allow a developer to compile a .spec file into a .spec.c file.
* wineclipserv : The Wine Clipboard Server is a standalone XLib application whose purpose is to manage the X selection when Wine exits.
@ wineconsole : The purpose of wineconsole is to render the output of CUI programs it does so either thru a window (called the USER32 backend) or by using an existing unix shell (called the curses backend) the first backend is triggered when the app programmatically opens a console (AllocConsole) the second one is triggered on startup by using wineconsole myapp.exe instead of wine myapp.exe on the command line
* winedbg : A application making use of the debugging API to allow debugging of Wine or Winelib applications as well as Wine itself (kernel and all DLLs).
@ winedump : Dumps the imports and exports of NE and PE (Portable Executable) files. DLL (included in wine tree).
@ winefile : A clone of the win3x filemanager.
@ winegcc/wineg++: Wrappers for gcc/g++ respectively, to make them behave as MinGW's gcc. Used for porting apps over to winelib.
* winelauncher : A wine wrapper shell script that intelligently handles wine invocation by informing the user about what's going on, among other things. To be found in tools/ directory. Use of this wrapper script instead of directly using wine is strongly encouraged, as it not only improves the user interface, but also adds important functionality to wine, such as session bootup/startup actions. If you intend to use this script, then you might want to rename the wine executable to e.g. wine.bin and winelauncher to wine. the WINECONFDIR/config file.
@ winemaker : Winemaker is a perl script which is designed to help you bootstrap the conversion of your Windows projects to Winelib. In order to do thisit will go analyze your code, fixing the issues listed above and generate autoconf-based Makefiles.
@ winemine : A clone of "Windows Minesweeper" a demo WineLib app.
@ winepath : A tool for converting between Windows paths and Unix paths (useful for shell scripts ans such).
* wineserver : The Wine server is the process that manages resources, coordinates threads, and provides synchronization and interprocess communication primitives to Wine processes.
-- winesetup : This is a Tcl/Tk based front end that provides a user friendly tool to edit and configure the WINECONFDIR/config file.
* wineshelllink : This shell script can be called by Wine in order to propagate Desktop icon and menu creation requests out to a GNOME or KDE (or other Window Managers).
@ winewrap : Takes care of linking winelib applications. Linking with winelib is a complex process, winewrap makes it simple.
@ winhelp : When Windows (at least 3.0, but it may well have appeared in 2.0) was launched, a help system was designed. Help information is stored in .hlp files, and was viewed with winhelp.exe (16 bit application). When Windows 95 was launched, the same help system still existed (even it grew in complexity), and help was viewed by a 32 bit application (winhlp32.exe). Those help files (.hlp) are in fact generated by a specific build system, starting from RTF files, with some very styles to define the specific portions (pages, links...). When an application requires a specific help page to be displayed, it calls an API (WinHelp), specifying the name of the help file, and a information about what needs to be displayed (hence the context sensitive help). When the Internet wave was clear to the MS folks, they moved the help system architecture to HTML files (replacing the RTF sources). That are the .CHM files (basically, compressed HTML files and their embedded information - images, metafiles...), which are normally displayed by an OCX (which basically decompress the right files and ask IWebBrowser to display them).hh.exe (which is now the .CHM viewer) is just a wrapper to that OCX.
* wmc : Wine Message Compiler it allows Windows message files to be compiled into a format usable by Wine.
* wrc : Wine Resource Compiler. It allows Winelib programmers (and Wine itself) to compile Windows style resource files into a form usable by Wine.
__________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com
couldnt it be used as appwiz.cpl replacement ?
@ uninstaller: A program to uninstall installed Windows programs. Like the Add/Remove Program in the windows control panel.
===== Sylvain Petreolle spetreolle(a)users.sourceforge.net Fight against Spam ! http://www.euro.cauce.org/en/index.html ICQ #170597259 "Don't think you are. Know you are." Morpheus, in "Matrix". ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com
participants (5)
-
Dimitrie O. Paun -
Francois Gouget -
Steven Edwards -
Sylvain Petreolle -
Tom Wickline