wine-devel

wine-devel@winehq.org

15 participants
84452 discussions

quartz.dll
by Hidenori Takeshima 31 Aug '02

31 Aug '02

I'm original developer of quartz. I don't want my quartz code to be restored. There seems to be many patented algorythms. Many codecs like MPEG-1/2/4 are patented. The ffmpeg library seems to use many patented codes. And the legal state of quartz interfaces is unclear for me. I can't accept any liability. Please add all codes in CVS explicitly: The code has been removed since the original author requests 'please remove my quartz codes' explicitly. The original author don't accept any liability. __________________________________________________ Do You Yahoo!? Yahoo! Finance - Get real-time stock quotes http://finance.yahoo.com

2 2

Re: PATCH: rename WIN_Handle{16,32} to HWND_{16,32}
by Alexandre Julliard 31 Aug '02

31 Aug '02

Michael Stefaniuc <mstefani(a)redhat.de> writes: > - rename WIN_Handle{16,32} to HWND_{16,32} to make it consistent > with the other handle <--> handle16 macros I think you should keep WIN_Handle32 as it is, to make it clear that it does more that simply cast the handle to the right type. Especially since we will need an HWND_32 macro in other dlls that does what its name suggests. Otherwise it's going to be very confusing to have HWND_32 be sometimes a simple macro and sometimes a complex function. -- Alexandre Julliard julliard(a)winehq.com

1 0

MYOB 3.5.2 autorun
by Anand Kumria 31 Aug '02

31 Aug '02

I just tried out MYOB (a popular financial program used widely in Australia). The autorun program on the CD attempts to start programs using WinExec as WinExec("whatnews\\whatnews.exe") Unfortunately the FILE_contains_pathW function belueves that is a full path which causes (in files/directory.c): if (FILE_contains_pathW(name)) { ret = DOSFS_GetFullName( name, TRUE, full_name ); goto done; } to fail and return an error to WinExec and subsequently not do anything. The below patch fixes this problem (for me) and lets me install a number of ancillory programs. Unfortunately MYOB install uses InstallShield6 as its installer, so I've had no success with the actual program. Is there a better way to do this patch? Thanks, Anand -- `` We are shaped by our thoughts, we become what we think. When the mind is pure, joy follows like a shadow that never leaves. '' -- Buddha, The Dhammapada --- files/directory.c Sun Sep 1 01:27:00 2002 +++ files/directory.c Sun Sep 1 01:26:02 2002 @@ -821,12 +821,11 @@ } /* If the name contains an explicit path, everything's easy */ + /* But only jump if we successfully found it */ - if (FILE_contains_pathW(name)) - { - ret = DOSFS_GetFullName( name, TRUE, full_name ); + if ( FILE_contains_pathW(name) && + DOSFS_GetFullName(name, TRUE, full_name) ) goto done; - } /* Search in the specified path */

1 0

Re: seg fault compiling wine
by Sebastian 'yath' Schmidt 31 Aug '02

31 Aug '02

On Tue, May 07, 2002 at 08:40:20PM -0500, Mason Kidd wrote: > Hi everyone, Hi, > I'm getting a segmentation fault compiling wine. This is the error > message: > [...] I got the same error. > wine-20020411 release of wine and got the same error. I am assuming > that > there is something wrong with my setup, because I compiled the CVS > source about 2 weeks ago without problems, which was after the > wine-20020411 release. Any ideas? It seems the configure-script is broken; it detects mmap64(), but there isn't mmap64(). So size_t gets 32 bits and off_t 64 bits. fstat() returns a structure with a member of type off_t, which is handed over to mmap(), which wants a size_t. mmap() gets 0 as size, returns a NULL-pointer, and in check_header(), where get_dword() the program receives a segmentation fault. Fix: change the "#define _FILE_OFFSET_BITS 64" in config.h to "#undef _FILE_OFFSET_BITS" and recompile. Sebastian -- pub 1024D/5A13B048 2001-08-28 Sebastian Schmidt (yath) <yathen(a)web.de> Key fingerprint = 8D25 C96B 3DE0 C7D0 AE01 6824 BC15 6273 5A13 B048 VI VI VI The editor of the beast.

1 0

Re: Wine Ma os X port
by Francois Gouget 30 Aug '02

30 Aug '02

On Wed, 28 Aug 2002, Lionel Ulmer wrote: [...] > Anyway, if you do that, you would need to simulate also a full Linux kernel > on this emulator (as otherwise, on what system would emulated Wine run). Not necessarily. What you propose to do for Wine can be done for the C and X11 libraries. Then you get an emulator that lets you run x86 Linux applications on a PPC machine... including Wine. It is similar, though more complex, to FreeBSD's Linux emulation mode. -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ $live{free} || die "";

2 3

Re: Check accelerator descriptions in CreateAcceleratorTableA
by Vincent Béron 30 Aug '02

30 Aug '02

Le mar 13/08/2002 à 09:52, Steven K. a écrit : > Was looking for something to get me started with Wine, > and a message kept coming up that accelerator > descriptions should be checked in > CreateAcceleratorTableA, this is a patch to hopefully > do that. Like I say this is my first, so please be > gentle with me ;) > > Changelog: > Check accelerator descriptions are valid in > CreateAcceleratorTableA. > Please use the -u option for diff (normal diff or cvs diff). It's much easier to merge should somebody else had also changed the file, and it's the only format that Alexandre will accept anyway :) If you use cvs diff, you can add it to your .cvsrc as "diff -u". Vincent

2 1

trying to draw off-screen
by Bill Medland 30 Aug '02

30 Aug '02

Does anyone know who constrains a window to be on the screen? Our application, in order to minimise flicker, does the hard work with a container application deliberately positioned well off-screen (enormous negative coordinates I think). This works under Windows. However under WINE the initial window appears in the top right corner of my screen (I think I've seen it appear in other corners too on other computers). It then resizes , keeping the same top left corner (with parts of the window off-screen) before correctly repositioning itself into the middle of the screen. Does anyone know which code is doing the initial positioning in the top right corner? Is this deliberate? Bill

2 2

wine regression - win16 file read problem!?
by Rizsanyi Zsolt 30 Aug '02

30 Aug '02

Hi! I have recently upgraded wine cvs and done a recompile and install. But now one of the programs I'm using does not work. My last cvs update was about 2 weeks ago. Its an old dictionary program (win16). It starts up ok, but when it tries to open the dictionary data, it says, that it is not found, and I should specify a location. I have looked at the +file debug channel output, and it does not even contain the location I have specified. Does that mean, that it does not even tries to open the file? Does somebody has some ideas where the problem could come from? Or which debug channel should I turn on to get some info about the problem? I just would like to ask for ideas before I start more serious debugging... Thanks Zsolt

1 0

Re: Wine Status
by Andriy Palamarchuk 30 Aug '02

30 Aug '02

[skipped] > I am new to the Wine Project and I am in need of some > assistance to make > sure all changes are corrct and accurate. > Over the next week or so I plan to read over the change > log's for the > last year > so I will have a feel of the changes that have been > made. A couple of good sources of information about changes in Wine: 1) Wine Weekly News articles http://www.winehq.com 2) Notes in the release ANNOUNCE file http://cvs.winehq.com/cvsweb/wine/ANNOUNCE Good luck, Andriy Boston, MA, USA __________________________________________________ Do You Yahoo!? Yahoo! Finance - Get real-time stock quotes http://finance.yahoo.com

3 2

Re: DOSFS_FindUnixName and "unix" filesystem (was: Re: (HELP) ...)
by Duane Clark 30 Aug '02

30 Aug '02

Martin Wilck wrote: > > In any case this is relatively minor and we can live without. If we > don't patch, we need to be prepared that other people stumble into the > problem I had, though. I am still feeling dumb - my wine development was > practically stuck for 2 months because of that "wine" file. Since I also was stumbled for a long period on a similar problem, due to specifying a "unix" filesystem, perhaps it would be appropriate in the documentation to put some large warnings on that option.

3 3

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