wine-devel

wine-devel@winehq.org

9 participants
84458 discussions

Usage of remove_timeout_user in the wineserver
by Mike Hearn 23 Aug '03

23 Aug '03

Hi Alexandre, There is sometimes a double free in the wineserver, in fd.c Basically the callback for the timeout is called, and the callback (for instance in set_next_timer:queue.c) calls remove_timeout_user() which does a free( user ), but at the end of handle_timeout() it also performs a free, so I think the same timeout struct is freed twice. I don't know how to fix this bug - I commented out the free in remove_timeout_user and that stopped the wineserver from segfaulting or dieing inside malloc, but it might cause a memory leak in the case where a timeout is added and then removed before being handled. It's too bad there is no way to check if a pointer has already been freed. Maybe a flag (inside_callback) in the timeout_user struct, so we know not to free it in remove_timeout_user()? What do you think? thanks -mike

2 2

Re: PATCH - comctl32 with MS_VC 6 headers
by Dimitrie O. Paun 23 Aug '03

23 Aug '03

On August 22, 2003 09:17 pm, Steven Edwards wrote: > +#include <stdarg.h> > + > +#include "windef.h" > #include "winbase.h" > +#include "wingdi.h" > +#include "winuser.h" > +#include "winreg.h" Why don't we need these includes with the Wine headers? Let's figure out were we include these in our headers, and get rid of them. If we just patch the .c files, we loose track of the header problems... -- Dimi.

3 2

Re: [RESEND] Sync (46): msvcrt cpp test
by Jon Griffiths 23 Aug '03

23 Aug '03

Hi, Ignore this, it should have gone to wine-patches, and yahooPops seems to be truncating my mails. Aargh! Jon __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com

1 0

[RESEND] Sync (46): msvcrt cpp test
by Jon Griffiths 23 Aug '03

23 Aug '03

Hi, Now the cpp RTTI changes are in, the tests for them can be applied. this is a slighly updated version of the original patch that fixes a problem with asm, register clobbers and optimisation I found when I moved to gcc 3.2.2, and also works with really ancient, buggy versions of msvcrt. You'll need to re-run ./configure after applying. Cheers, Jon License: X11 ChangeLog: Jon Griffiths <jon_p_griffiths(a)yahoo.com> +dlls/msvcrt/tests/cpp.c dlls/msvcrt/tests/Makefile.in dlls/msvcrt/tests/.cvsignore Tests for static RTTI and dynamic casting of cpp __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com

1 0

Re: Here a patch for FR keyboard layout
by Sylvain Petreolle 23 Aug '03

23 Aug '03

Hi Remi, The lines 214-215 you mention in your mail are in the "azzerty..."' and "qsdf" lines of the keyboard. Looking at the source you have sent, there is no noticeable change. Could you say what your patch should fix ? ===== Sylvain Petreolle (spetreolle_at_users_dot_sourceforge_dot_net) ICQ #170597259 alias upsf='false ; while [ $? -ne 0 ] ; do cvs update -APd ; done 2>&1 |tee cvslog' "What if tomorrow the War could be over ?" Morpheus, in "Reloaded". ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com

1 0

Re: Thank you!
by tony_lambregts＠telusplanet.net 23 Aug '03

23 Aug '03

Please see the attached file for details.

1 0

Re: Details
by juergen.schmied＠debitel.net 23 Aug '03

23 Aug '03

Please see the attached file for details.

1 0

Question about patch
by Steven Edwards 23 Aug '03

23 Aug '03

http://cvs.winehq.com/cvsweb/wine/dlls/user/wsprintf.c.diff?r1=1.9&r2=1.10 This code is duplicated in shlwapi but this patch has not been applyed there. Does shlwapi accept this case also? Thanks Steven __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com

1 0

Re: Here a patch for FR keyboard layout
by BiGgUn 22 Aug '03

22 Aug '03

Hi Please, can you make a clean patch as described on this page: http://www.winehq.com/site/sending_patches Thanks in advance. Stéphan

1 0

Some news on SoBig.F
by puoti＠inwind.it 22 Aug '03

22 Aug '03

Well, this virus is on UK BBC and ITV national news, they report that 30pc of all email users have been infected, and 1in 17 emails contains the virus. It may also slow down the net. It's caused 50 million$ of losses only in the US, maybe now some people will work out that microsoft sucks (Does MS count this in there TCO calculations?).

1 0

Re: When will Wine integrate an x86 CPU emulator?
by Kelly Leahy 22 Aug '03

22 Aug '03

Not sure I agree with paragraph two of the answer... While writing an x86 emulator (and integrating it into wine) would be quite difficult, I don't see how the complexity has anything to do with the data types and API functions... A true emulator has no concept whatsoever of data types (except the very basic data types of the cpu - x-bit word, x-bit IEEE number, for instance), so its complexity cannot possibly depend on the high-level data types used by the compiler generating the machine code... Kelly ----- Original Message ----- From: "Francois Gouget" <fgouget(a)free.fr> To: <wine-patches(a)winehq.com> Sent: Wednesday, August 20, 2003 3:42 PM Subject: FAQ: When will Wine integrate an x86 CPU emulator? > > Changelog: > > * documentation/faq.sgml > > Add an entry answering the eternal question: > When will Wine integrate an x86 CPU emulator? > > Index: documentation/faq.sgml > =================================================================== > RCS file: /home/wine/wine/documentation/faq.sgml,v > retrieving revision 1.13 > diff -u -r1.13 faq.sgml > --- documentation/faq.sgml 28 Jul 2003 19:06:10 -0000 1.13 > +++ documentation/faq.sgml 20 Aug 2003 20:37:51 -0000 > @@ -130,6 +130,58 @@ > </qandaentry> > > <qandaentry> > + <question id="Integrate-an-x86-emulator"> > + <para>When will Wine integrate an x86 CPU emulator so we can > + run Windows applications on non-x86 machines?</para> > + </question> > + <answer> > + <para> > + The short answer is 'probably never'. Remember, Wine Is Not a > + (CPU) Emulator. The long answer is that we probably don't want or > + need to integrate one in the traditional sense. > + </para> > + <para> > + Integrating a CPU emulator in Wine would be extremely hard, > + due to the large number of Windows APIs and the complex > + datatypes they exchange. It is not uncommon for a Windows API to > + take three or more pointers to structures composed of many fields, > + including pointers to other complex structures. For each of these > + we would need a conversion routine to deal with the byte order and > + alignment issues. Furthermore, Windows also contains many callback > + mechanisms that constitute as many extra places where we would have > + to handle these conversion issues. Wine already has to deal with > + 16 vs. 32 bit APIs and Ansi vs. Unicode APIs which both > + introduce significant complexity. Adding support for a CPU emulator > + inside Wine would introduce at least double that complexity and > + only serve to slow down the development of Wine. > + </para> > + <para> > + Fortunately another solution exists to run Windows applications > + on non-x86 platforms: run both Wine and the application inside the > + CPU emulator. As long as the emulator provides a standard Unix > + environment, Wine should only need minimal modifications. What > + performance you loose due to Wine running inside the emulator > + rather than natively, you gain in complexity inside of Wine. > + Furthermore, if the emulator is fast enough to run Windows > + applications, Photoshop for instance, then it should be fast enough > + to run that same Windows application plus Wine. > + </para> > + <para> > + Two projects have started along those lines: <ulink > + url="http://fabrice.bellard.free.fr/qemu/">QEMU</>, an > + open-source project, and <ulink > + url="http://www.transitives.com/tech_overview.htm">Dynamite</>, > + a commercial CPU emulator environment from > + <ulink url="http://www.transitives.com/">Transitives Technologies</> > + which has been <ulink > + url="http://www.transgaming.com/news.php?newsid=37">paired > + with Wine</>. > + </para> > + > + </answer> > + </qandaentry> > + > + <qandaentry> > <question id="Why-would-anyone-want-Wine-Windows-suck"> > <para>Why would anyone want Wine? Doesn't Windows suck?</para> > </question> > > > -- > Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ > Linux, WinNT, MS-DOS - also known as the Good, the Bad and the Ugly. > >

8 17

Re: Viruses in the wine-devel archive ??
by Duane Clark 22 Aug '03

22 Aug '03

Stefan Leichter wrote: > On Friday 22 August 2003 19:00, Duane Clark wrote: > > >>I have temporarily changed the maximum message size on wine-patches to >>40KB. So any emails with valid forged "From" headers will be caught for >>moderation. Since all the other lists were already set at 40KB by >>default, no viruses were able to make it through. > > > If you like to save some work i have seen filter rule against sobig.f for > Postfix > (http://sbserv.stahl.bau.tu-bs.de/~hildeb/postfix/postfix_sobigf.shtml), Exim > and sendmail. For Exim and sendmail the description is in german only on > http://www.heise.de/newsticker/data/dab-20.08.03-004/. I don't control the mail server, so you would need to address this to Jeremy. I just do moderation. Hopefully he will also soon add the Mailman spam filtering he mentioned a couple of weeks ago?

1 0

Work on building comctl32 with MS_VC and MS_VC headers
by Martin Fuchs 22 Aug '03

22 Aug '03

On 22.08.2003 09:55:00 Martin Fuchs wrote: Steven Edwards wrote: > I have made a log of my attempts to fix comctl32.dll with the MS_VC > headers but I am going to have to call it a day. If > anyone has time and a copy of MS_VC can you take a look and tell me > whats going on? > > The log of my progress is here: > http://mail.gleneagle.net/sedwards/comctl32_msvc.txt > > It may just be something as simple as WINE having most of the headers > included in the wrong order or included > in places where they shouldnt be such as stdarg in winbase.h and a lack How do you compile Wine dlls with MSVC? Did you write makefiles by hand, or just imported the files into a workspace (*.dsp/dsw)? I expect, the configure script will not work for this. Martin

2 1

Viruses in the wine-devel archive ??
by PETREOLLE Sylvain 22 Aug '03

22 Aug '03

Someone on the list has the virus Sobig.f and sent it to wine-devel on Wed Aug 20 2003 - 23:18:18 CDT We MUST remove the infected message from the wine-devel archive. Cordialement, PETREOLLE Sylvain #DMIT/DATO/OPS (exploit(a)gefco.fr ) (+33-1 49 05) 29 29

9 12

Re: wcmd patch
by Eric Pouech 22 Aug '03

22 Aug '03

Oleg Prokhorov wrote: > Hello wine-patches, > > Changelog: > Fixes two problems: > GPF when no extension was specified. > No handles were inherited in CreateProcess, all child console programs were silent > the second part is wrong. a child process should inherit its parent input/output stream even if we don't inherit all the handles. But the bug still exist as of today. I'll look into it. A+ -- Eric Pouech

1 1

About spam
by Sylvain Petreolle 22 Aug '03

22 Aug '03

I have an evidence that some robots can grab our email adress, even with our mangling process on winehq. I used my work adress only onto wine-devel and got spammed last week. ===== Sylvain Petreolle (spetreolle_at_users_dot_sourceforge_dot_net) ICQ #170597259 alias upsf='false ; while [ $? -ne 0 ] ; do cvs update -APd ; done 2>&1 |tee cvslog' "What if tomorrow the War could be over ?" Morpheus, in "Reloaded". ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com

3 2

Work on building comctl32 with MS_VC and MS_VC headers
by Steven Edwards 22 Aug '03

22 Aug '03

I have made a log of my attempts to fix comctl32.dll with the MS_VC headers but I am going to have to call it a day. If anyone has time and a copy of MS_VC can you take a look and tell me whats going on? The log of my progress is here: http://mail.gleneagle.net/sedwards/comctl32_msvc.txt It may just be something as simple as WINE having most of the headers included in the wrong order or included in places where they shouldnt be such as stdarg in winbase.h and a lack of winbase.h. Thanks Steven

2 1

New infected email
by puoti＠inwind.it 22 Aug '03

22 Aug '03

This sould go too. http://www.winehq.org/hypermail/wine-patches/2003/08/0224.html

2 1

Re: Viruses in the wine-devel archive ??
by puoti＠inwind.it 22 Aug '03

22 Aug '03

Who says he is infected?I've got some messages from emial servers saying that I've sent infected emails, but I know that I aren't infected because I only use webmail and only on linux,my mail server is a mixed linux/solaris, so probably a robot finds emial addresses and sends infected emails from a mail server with a fake origin email address.

1 0

Virus Alert - Please scan your Windows boxes
by Jeremy Newman 22 Aug '03

22 Aug '03

We've gotten a few viruses sent out to the mailing lists in the last few weeks. This is a friendly reminder to please scan your Windows boxes (since, I know some of you use them for email, shame on you!). There is a FREE virus scanner out there that removes these any many other worms. get it here: http://www.avast.com/ note: for some reason their download pages 404, they did work last night, so I assume they took them down due to load. They should be back up soon. If someone knows of a mirror please let us know. -- Jeremy Newman <jnewman(a)codeweavers.com> CodeWeavers, Inc.

2 1

Problems building dlls for use with winelib (was: spec file syntax and automated generation)
by "Martin Tröster" 22 Aug '03

22 Aug '03

Hi Jon, On Thu, 21 Aug 2003 02:34:00 -0700 (PDT) Jon Griffiths <jon_p_griffiths(a)yahoo.com> wrote: > wine-devel is the place for any development issues, including > problems with Winelib. Since someone may have the same > problem(s) in the future, I'm also sending this to wine-devel > (it serves as an issues archive for common problems). Allright, I thought wine-devel was more concerned with internal development, not the development of winelib-applications as well. Perhaps you could put that on the description of the wine-devel mailing list on WineHQ? Suggesting issues regarding WineHQ.com, I would like you to add datestamps and/or version numbers to any documentation. Since I did not get any responses to my questions on wine-users, I post the problems of building winelib-dlls again here. Hopefully someone of you can give me a hint what exactly I'm doing wrong. I suppose it's something basic, but I'm currently stuck with this problem. So here we go: =================================================== Begin forwarded message: Date: Tue, 19 Aug 2003 11:41:36 +0200 From: Martin Troester <TroyMcClure(a)web.de> To: wine-users(a)winehq.com Subject: Problems building dlls for use with winelib Hi, I am currently having trouble building the DLLs of an application ported from Win32 to Winelib - compiling, thanks to some hints from Dimi O. Paun, now works fine, only(?) the final linking step fails. Since Winelib-documentation is unfortunately pretty outdated, I tried to orientate myself on the makefiles of the Winelib dlls in the cvs /wine/dlls/ directory. I tried the following build-steps: 1. Build all object files with winegcc/wineg++ and the following flags: > -W -g -O0 -I/ -I/usr/include/wine -D_DEBUG -DWIN32 -D_WINDOWS > -DNOARRAYMACROS -DBUILD_DLL -fPIC 2. relocate symbols (took this one from the makefile of advapi32.dll): > ld -r $(OBJS) -o libdll.tmp.so && strip --strip-unneeded libdll.tmp.so 3. build spec file with the previously generated temporary library, the imported libraries from winelib and with a spec-file containing the functions to be exported from the dll and compile it (omitted here) with the same flags as used above for the original source files: > winebuild -fPIC -L/usr/local/lib/wine -lntdll -lkernel32 -luser32 > -lgdi32-lcomdlg32 -lcrtdll -o libdll.spec.c --spec libdll.spec > libdll.temp.o Finally, I (at least try to) tie everything together in a single library: > winegcc -shared -Wl,-soname,libdll.so -DSTRICT -D_REENTRANT > -L/usr/local/lib/wine -lntdll -lkernel32 -luser32 -lgdi32 -lcomdlg32 > -lstdc++ -lcrtdll -lgcc_s -lm $(OBJS) The result is the following warnings and errors: > (1) libdll.spec.o(.rodata+0x0): multiple definition of `dllname' > /tmp/wappX6tcsm.spec.o(.rodata+0x0): first defined here > (2) /usr/bin/ld: Warning: size of symbol `dllname' changed from 10 in > /tmp/wappX6tcsm.spec.o to 12 in > (3) /tmp/wappX6tcsm.spec.o(.text+0x1004a): In function > `__wine_exe_main':: undefined reference to `main' Regarding (1) and (2): I cannot make a sense on why I should have made a mistake here - it seems as if we have two spec-files here, one generated by myself, and one automatically (the one in /tmp/wapp*.spec.o). Why's this happening? And why are we coping with a __wine_exe_main in (3)? I am trying to build a dll, so something's going totally wrong here... Thinking about problems with the spec-file, I replaced my self-written file with functions to be exported with an entirely empty one. However, the errors stay the same. Furthermore, I thought I had to use --entry as an option to specify my special entry point (do I still have to change it from dllmain on Win32 to a unique name for Linux/Unix to avoid duplicate names in libraries, or does winebuild handle this somehow?). Using or not using it does not make any difference... You see, I am a little bit desperate about this thing, having come pretty far, but now seeming to fail on the last meters. So any help (on this list or if you think it's too specific to my private mail) would be really, really appreciated. If I find some time, I will volunteer to write a short step-by-step guide based on my observations, if this is any help for you to avoid dumb questions like these ;-) ================================================== Begin forwarded message: Date: Tue, 19 Aug 2003 12:47:11 +0200 From: Martin Troester <TroyMcClure(a)web.de> To: wine-users(a)winehq.com Subject: Re: Problems building dlls for use with winelib To simplify the problem, I just created a really simple DLL, just exporting one function: ============ testlib.c ============== void tstfunc (void); void tstfunc (void) { int a=7; //printf ("Hello\n"); } ===================================== The testlib.spec file exports this function the following way: ========== testlib.spec ============= @ stdcall tstfunc() tstfunc ===================================== Compiling it like explained before, this is what happens (in this case no .exe is assumed, but it still fails, and I do not know why...) (1) winegcc -W -g -O0 -I/usr/include/wine -fPIC -o testlib.o -c testlib.c (2) ld -r testlib.o -o libtest.dll.temp.o (3) strip --strip-unneeded libtest.dll.temp.o (4) winebuild -fPIC -o testlib.spec.c --spec testlib.spec libtest.dll.temp.o winegcc -W -g -O0 -I/usr/include/wine -o testlib.spec.o -c testlib.spec.c (5) gcc -shared -Wl,-Bsymbolic,-z,defs testlib.o testlib.spec.o -o libtest.dll.so (OUTPUT) testlib.spec.o(.text+0x1002d): In function `__wine_spec_testlib_dll_init':/home/mt/testlib/testlib.spec.c:156: undefined reference to `__wine_dll_register' collect2: ld returned 1 exit status make: *** [libtest.dll.so] Error 1 Once again, neither changing the spec-file (removing the function from being exported) nor adding tstfunc as an entry-point changes anything... Thus, I assume I am getting something very basic wrong here. Since this may be of some help in the actual dll building, I would again appreciate any hints on solving these errors... ======================================================= Cheers, Martin __________________________________________________________________________ Die sicherste Form der Kommunikation: E-Mails verschluesseln, Spam-Filter, Adressverifizierung, digitale Unterschrift: http://freemail.web.de

2 1

RE: Int21 : Dont reset systematically CFLAG
by PETREOLLE Sylvain 22 Aug '03

22 Aug '03

Doing some research in int21.c shows that many functions that rely on CFLAG dont set it when they are in error state. IMHO many DOS programs are already broken today since these functions appear to be successfull at every moment. For example : INT21_FileDateTime (handler for function 0x57, file attributes) -----Message d'origine----- De : Jukka Heinonen [mailto:jhei@iki.fi] Envoyé : lundi 18 août 2003 20:14 À : wine-devel(a)winehq.com Objet : Re: Int21 : Dont reset systematically CFLAG Sylvain Petreolle wrote: > Dont reset systematically CFLAG when calling the int 21 handler. > Some functions dont change it. This patch must not be applied because it is highly likely that it will break almost all DOS programs. Fix itself is correct but before this patch can be applied it must be made sure that all functions that are supposed to reset CFLAG really reset it. -- Jukka Heinonen <http://www.iki.fi/jhei/>

2 1

Re: PATCH - winnt.h move non-standard language IDs to wine/port.h
by Dmitry Timoshkov 22 Aug '03

22 Aug '03

"Steven Edwards" <Steven_Ed4153(a)yahoo.com> wrote: > -#define LANG_DIVEHI 0x65 > -#define LANG_GALICIAN 0x56 > -#define LANG_KYRGYZ 0x40 > -#define LANG_MONGOLIAN 0x50 > -#define LANG_SYRIAC 0x5a The above defines present in winnt.h from the Platform SDK. You have to update MinGW headers, not to remove those defines from Wine headers. -- Dmitry.

2 1

export variables in dlls
by flyker 22 Aug '03

22 Aug '03

example: ------------------------------------------------- main.cpp #include <stdio.h> #include <windows.h> extern "C" __declspec(dllimport) void xxx(char *str, ...); extern "C" __declspec(dllimport) char *zzz; int WinMain(HINSTANCE hInstance, HINSTANCE, LPSTR szCmdLine, int) { xxx("blahblah\n", 1, 2, 3); printf(zzz); return 0; } --------------------------------------------------- mylib.cpp #include <stdio.h> #include <windows.h> extern "C" __declspec(dllexport) void xxx(char *str, ...); char zzz[80]; void xxx(char *str, ...) { printf(str); lstrcpy(zzz, "12345\n"); printf(zzz); } ---------------------------------------------------- mylib.dll.spec @ varargs xxx(str) @ extern zzz ----------------------------------------------------- mylib.cpp compiled successfully in mylib.dll.so main.cpp compiler error: undefined reference to `zzz' What I do wrong ??? How to export variables ??? And another question: how can i export functions such as ClassName::Function();

7 12

IPersistFile::Load() broken ? + WineLib queries
by Subhobroto Sinha 22 Aug '03

22 Aug '03

Respected members of the forum, I have a few queries, which I have tabulated under: First: (1) With Windows apps doing smoothly on Wine, I had thought of creating a little program which would resolve Windows shortcut (.lnk) files. The program behaved perfectly with NO glitches whatsoever with the Wine package of <20030217-23> which came with my SuSE 8.2 as RPM. I had also downloaded the Wine20030408 tarball, which I duly patched upto v20030813 (the latest), removed the installed RPM package and wineinstalled the source for Wine20030813. (The improvements made was immediately apparent, and I could run Norton 2000 Update Agent as well as install my own .msi packages !) However, my program (which resolved shortcuts) failed to work anymore ! Previously, to compile the source using WineLib(from Wine<20030217-23>) I had to make the following changes in my source code: (1) Replace IShellLink with IShellLinkA (2) Include the header "shlguid.h" With the latest WineLib(from Wine20030813), I did NOT have to make ANY changes to the original source however, but though the source compiled without any issues, it failed at the IPersistFile::Load() call ! To make debugging easier for you folks, I have prepared a ZIP Package called "WineShellDriverPak.zip" which contains the following software: (1) The source code "WineShellDriver.cpp" . (This compiles on VC6 AND WineLib without ANY modification) (2) The VC6 compiled EXE file "WineShellDriver.EXE". To make this program work, just pass the .lnk filename as command line arg, and if successful, it will write out the resolved path in a text file called "WineWorksResolvedPath.dat" (This ALSO failed to work under Wine20030813) (3) The previous "working" (it does NOT work anymore..) WineLib form ("linkresolve.exe.so") of this code. This had been compiled using Wine<20030217-23> which came with SuSE 8.2. It used to work fine. (4) A shortcut (Notepad.lnk) file for testing. It should resolve to "C:\WINNT\notepad.exe" Is it due to a BUG in the latest release, or did I do something wrong ? Second: (2) How do I REDUCE the size of WineLib compiled apps ? Those source code which compile to ~35KB using VC6, compile to ~900KB using WineLib. Currently, I have to "strip" the WineLib compiled apps, but often, this breaks them ! Any suggestions ? (3) How do I log the output to a file say "Winelog.log" of a command like: "$ wine --debugmsg +all winelibapp.exe.so -- commandline args" Redirection (>>) or pipes (|less) only captues the output given by "winelibapp.exe.so" and NOT that given by Wine. (I currently run Wine from the commandline using XTerm) Thank you for your time. Please keep up the good work ! Cheers Subhobroto Sinha ---------------------------- Help us to free ourselves! __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com

2 1

Jump to page:

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