August 2003 - Wine-devel - list.winehq.org

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