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

Wine Definitions take #2
by Tom Wickline Feb. 4, 2003

Feb. 4, 2003

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.

5 6

Re: How to remount CDROM during program execution
by Roger Young Feb. 4, 2003

Feb. 4, 2003

Tony Lambregts suggested that I check whether the problem (qv) was with Wine or WineX. It turned out to be a WineX problem. Remounting during program install works perfectly with Wine. Roger Young

1 0

Code Duplication
by Matthew Davison Feb. 4, 2003

Feb. 4, 2003

During my work to clean up the Unicode -> ascii cross-calls I have noticed some A:W pairs where both are implemented in essentially the same way. Would it be sensible in these case to make the A function into a call to the W one, to reduce code size, or would I be wasting my time . -- Matthew Davison <m.davison(a)virgin.net>

2 1

Re: PATCH: glibc 2.3.x and errno
by lucho Feb. 4, 2003

Feb. 4, 2003

Just an idea that could be of use. Since the __errno_location cannot be replaced anymore in glibc 2.3, isn't it possible to replace the %gs segment instead - Wine could create it's own %gs segments for it's threads, containing the errno's address where glibc is ecpecting it to be. Lucho

1 0

Paypal and website
by Joerg Mayer Feb. 4, 2003

Feb. 4, 2003

Can you please add alt, height and width statements to the paypal button? It's completely invisible with konqueror otherwise (yes, I do have image loading diabled :-). The same is true for most pictures on the winehq pages. On a related topic: When will the new web pages be moved to winehq? Ciao Jörg -- Joerg Mayer <jmayer(a)loplof.de> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.

2 1

Re: Packagers Guide Update #5
by Tony Lambregts Feb. 4, 2003

Feb. 4, 2003

Tom Wickline wrote: > Tony Lambregts wrote: > >> I don't think it is nessasary for a configure or shell script for >> this. I think we can just include it. Declaring it as an entity and >> wraping it in <programlisting> _should_ work. Tom: you can try this >> your self or if you want/need some help with this I'll see what I can >> do. >> > Declaring the sample config as an entity is as easy as the following patch. Index: wine-pkg.sgml =================================================================== RCS file: /home/wine/wine/documentation/wine-pkg.sgml,v retrieving revision 1.1 diff -u -r1.1 wine-pkg.sgml --- wine-pkg.sgml 19 Jan 2001 20:58:37 -0000 1.1 +++ wine-pkg.sgml 26 Jan 2003 18:02:24 -0000 @@ -5,8 +5,8 @@ %authors; <!entity packaging SYSTEM "packaging.sgml"> +<!entity config SYSTEM "samples/config"> ]> <book id="index"> ----- After making that change you can include the config file anywhere you like by using the directive &config; Getting around the <wineconf> problem is another problem however. It looks to me that this wineconf could just as easily been surrounded by stars or braces or whatever since getting rid of the lines does not seem to have affected any of my programs. If this is the case then getting rid of <> and replacing them with something else is the (easiest) solution. If we cannot replace the <> around wineconf the burning question for me is what is the directive to tell the make process ignore <wineconfig> Does anyone have an idea? Vincent...? -- Tony Lambregts

5 7

GDI question
by Hetz Ben Hamo Feb. 4, 2003

Feb. 4, 2003

Hi, I'm testing some apps installation with either the free WineHQ, WineX, Crossover Office, and many times I see buttons and other GUI related stuff in the wrong size or place, and I understand it's a GDI related issue, so here's 3 questions.. 1. Is the GDI implementation is so bad that it needs hacking per app to make it look ok? 2. Is there a way to take GDI parts from native WIndows and use it in Wine? 3. Funding - can any company (transgaming, CodeWeavers, others) can estimate the cost of rewriting a better (and faster - the speed of Wine graphics today is something in magnitude of 486 PC!) GDI? Thanks, Hetz

7 9

Re: LISTVIEW_SetItemCount take 4
by Duane Clark Feb. 4, 2003

Feb. 4, 2003

Duane Clark wrote: > Sigh.. I guess I really should have compiled that previous version > before sending it in. Sorry for the excessive traffic. So here it is > fixing compiler warnings, with the missing return added in, and with the > changelog. Hopefully this will be the last time. > Dimi, Dan and I have been looking into this further. This is not the right fix, so please do not apply.

1 0

Windows API database / map
by Dave Miller Feb. 4, 2003

Feb. 4, 2003

I've begun cross referencing the windows dlls in a 'map' format as Dan Kegel suggested. I'm not finished yet because it seems when I sort alphabetically I am sorting the entire path. Sample output is here: http://home.ptd.net/~compsol/winxp_sample_map.html Be aware though this HTML is around 900K. If anyone has comments or suggestions on how to improve it or the next logical step please let me know.

5 6

Re: Using the real Windows kernel
by Mike Hearn Feb. 4, 2003

Feb. 4, 2003

I suggest you read the GNU manifesto. The point of Wine and Linux is that it's a philosophically free replacement for the current status quo - simply using Microsoft code changes nothing except the way the windows look, which isn't really the point. thanks -mike On Mon, 2003-02-03 at 21:04, David Filskov wrote: > I'm not a programmer and I know this is not your goal... but: > > Woulden't it help if Windows users just copied the kernel from their Windows installation and used this for an alternative desktop/system? - I mean the Windows NT kernel seems to work alright, but all the things Microsoft put on top of it slows it down and locks people away from settings and confuses them etc... if you had people use the real kernel instead (without offering it online of course) Windows users could use YOUR desktop/GUI implementation but still use all the existing drivers and apps... and have faster and more configurable computer using your alternative desktop. > > I know a lot of Windows users who would want such an alternative... just a thought... > > --David Filskov > Denmark > -- Mike Hearn <m.hearn(a)signal.qinetiq.com> QinetiQ - Malvern Technology Center

1 0