wine-devel

wine-devel@winehq.org

10 participants
84459 discussions

Cooperation between Odin & Wine
by Sander van Leeuwen 26 Dec '01

26 Dec '01

Hi, As some of you might remember I'm the lead developer of the Odin project. (project for OS/2 with the same goals as Wine). Odin is partly based on Wine code. The core dlls (gdi32, user32, kernel32) + some special dlls (winmm, directx, winsock) use some Wine code, but is basically incompatible with Wine for obvious reasons. Most of the remaining dlls are based entirely on Wine code. The last few years there has been little cooperation between both projects for several reasons. One of them is that we have far fewer active developers and cooperation sometimes proved to be difficult. Some source files of the two project had grown apart since changes were never merged back into Wine. Now, I'm trying to change this situation, but am wondering how to proceed. I can post bug fixes to this list, but it will be difficult for me to actually test these changes in Wine itself. (too time consuming) Posting diff files is not always possible due to the major differences between source files. Merging changes from Wine into our source tree is no problem. We can do that ourselves. However, it would be nice if compiler incompatibilites (we use IBM VisualAge C++, not GCC) could be resolved. There aren't many, but the IBM compiler is not always as flexible as GCC and of course doesn't understand any GCC extensions. It would be a big help if incompatible code could be changed. Switching compilers is not an option for us. I can post a (small) list of changes we had to make. The license of our project is not compatible with Wine, but the dlls that are largely based on Wine (such as comctl32, shell32, ole) are an exception to the project license. The sources of those dlls are released under the Wine license. In case there is ever interest in the other sources, then you can just ask me. I'd be happy to 'donate' them to Wine. For more information about Odin you can visit http://odin.netlabs.org (some information is outdated though). There you can find out where to download the sources (cvs). The next post from me will contains some patches for bugs in Wine that I've recently found. Sander

2 2

CVS server
by Dimitrie O. Paun 26 Dec '01

26 Dec '01

It looks like we're running an old version of CVS on the server, as it complains it does not understand #cvs up -C is it possible to upgrade it? That would be a good idea irrespective of the -C problem, as the new versions fixed quite a few (nasty) bugs. -- Dimi.

2 1

Re: Wine Tasklist (UNC)
by Mike McCormack 26 Dec '01

26 Dec '01

Hi Francois, I think the best way to handle UNC pathes is to do it properly; Wine should talk SMB/NBT directly to other machines on the network, not through Linux's VFS layer. This approach would give high level of flexability to Wine. We could: * support NetDDE and DCOM with a common code base * use Windows file permissions and security properly * support unicode share names properly * support named pipes, etc across the network * eliminate SMB<->VFS<->SMB problems eg. parsing /etc/fstab There's three options: 1) write our own SMB code (wineserver talks NetBIOS/SMB) i have a short snippet of code to resolve NetBIOS names in CreateFile, but that is only the beginning of the effort. 2) link with a LGPL'ed CIFS implementation. http://www.ubiqx.org/libcifs/ (very incomplete, but maybe possible later, may still have threading issues) 3) get Samba to provide us with a Unix domain socket to talk with. (SambaTNG looks like the best bet there.) i have experimented with linking Wine to samba's libsmbclient and use it to open files. That works (i have a test patch), has threading and licensing issues (it's GPL). This would be alot of work, but i think it's the only way to do it properly. Mike > * UNC path handling > - for drives '\\.\e:', devices > - for network paths > - there's been a patch related to this recently but I believe it does > not cover all cases > - integrate with Samba to handle network UNC paths > - provide a way to mount/unmount drives at runtime, especially > network drives. One should be able to disable this in the config > file (for security reasons). > - Support for 'persistent' mounts... will require modifying the way w > specify which drives are mounted where. > - provide an applet to mount/unmount drives while Wine is running. ------------------------------------------ mailto:Mike_McCormack@start.com.au ph +82 16 430 0425 __________________________________________________________________ Get your free Australian email account at http://www.Looksmart.com.au

2 1

Re: Bulletproof the debugger.
by Michael Stefaniuc 26 Dec '01

26 Dec '01

On Fri, Dec 21, 2001 at 01:52:12PM -0800, Medland, Bill wrote: > Bill Medland (medbi01(a)accpac.com) > Don't ask me why but on my setup vsnprintf returned a value greater than This is the new and correct behavior according to the C99 standard. All snprintf function should return in error case the number of characters that would have been written to the buffer if the size of buffer would have been big enough. This change while usefull will brake a lot of things. IMO the glibc is still using the old behavior. bye michael > the size of the buffer (much bigger), resulting in the debugger tripping > a segment violation. > Considering the location of this code I see no problem with using belts and > braces; it isn't going to be executed much but when it is we want it to work > (despite braindead operating systems) -- Michael Stefaniuc Tel.: +49-711-96437-199 System Administration Fax.: +49-711-96437-111 Red Hat GmbH Email: mstefani(a)redhat.de Hauptstaetterstr. 58 http://www.redhat.de/ D-70178 Stuttgart

2 3

Patches for several bugs
by Sander van Leeuwen 26 Dec '01

26 Dec '01

Hi, Here are the bug fixes I promised. There are more, but I can post those at a later time. - controls\button.c CB_Paint, line 806 hBrush = SendMessageW( GetParent(hwnd), WM_CTLCOLORSTATIC, hDC, (LPARAM)hwnd ); if (!hBrush) /* did the app forget to call defwindowproc ? */ hBrush = DefWindowProcW( GetParent(hwnd), WM_CTLCOLORSTATIC, hDC, (LPARAM)hwnd ); -> (Auto)Check, (Auto)Radio & (Auto)3State buttons send WM_CTLCOLORSTATIC instead of WM_CTLCOLORBTN (verified in NT4) (fixes opening dialog buttons in Opera 6 (choose interface)) - dll\user32\text.c TEXT_GrayString, line 499 if(!hdc) { DeleteDC(memdc); return FALSE; } -> DC leak - COMCTL32: Comboex, rebar, tooltips, toolbar: NEVER delete the font object received by WM_SETFONT -> See attached diff files for comboex, rebar & toolbar. Our tooltips has too many differences for diff to produce usable output, but the changes are similar to the other three. - COMCTL32: Tooltips: wrong COMCTL32_Free calls -> 4 calls with wrong pointer: COMCTL32_Free(&lpttsi); should be COMCTL32_Free(lpttsi); - user32: frame tracking * - Only draw changed track frame instead of clearing the old one and * drawing the new one (less flickering) * - Send WM_MOVING when moving a window * - Send WM_SIZING only when sizing a window * - Fixed handling of rectangles changed by WM_SIZING/MOVING -> Can't easily produce diff file. Too many changes. (check src\user32\wintrack.cpp in our CVS tree) - USER32: groupbox redrawing fixes -> I am not 100% sure the same happens in Wine, but it looks like that. When an application changes the font or the text of a groupbox (smaller font or fewer characters), then the old text has to be erase properly or else you'll still see part of it. If I remember correctly, that could be seen in Opera 5.12 (property dialogs) -> Again, too many changes to produce a diff file. (check src\user32\button.cpp, BUTTON_SetText & BUTTON_SetFont) - USER32: static control -> our version supports more styles (SS_CENTERIMAGE, SS_REALSIZEIMAGE) and features (SS_ENHMETAFILE) (src\user32\static.cpp) Sander

1 0

Re: DOS packing patch (fix)
by Lionel Ulmer 25 Dec '01

25 Dec '01

Hi all, I am a bit worried by this patch : I looked at how "pshpack1.h" works, and it uses the '#pragma pack(1)' method when compiling with GCC. > +/* WARNING: one byte packed structs from here !! (i.e. not DWORD aligned) */ > +#include "pshpack1.h" > + And I wonder if this really works as with the latest versions of GCC (2.95.3 onwards AFAIK), '#pragma pack(1)' is ignored (at least on my self-compiled GCC :-) ) and you need to use the '__attribute((__packed__))' construction after each structure. But well, I may say completely stupid things as otherwise a lot of bugs would exist in Wine... Lionel PS: Merry Christmas all :-) -- Lionel Ulmer - http://www.bbrox.org/

1 0

16 bit comm issue
by Mike McCormack 24 Dec '01

24 Dec '01

Hi, There's a problem with the current 16bit comm architecture which i'm not sure how to solve correctly. If a 16bit Windows programs uses EnableCommNotification to receive WM_COMMNOTIFY messages then sits in a message loop waiting for them, it will never receive them because there is no chance for APC that sends the message (COMM16_ReadComplete) to run. I have a patch for this problem which puts an alertable wait in GetMessage(16), which i posted in October. What is the problem with this method, and is there a better solution to the problem? Mike ------------------------------------------ mailto:Mike_McCormack@start.com.au ph +82 16 430 0425 __________________________________________________________________ Get your free Australian email account at http://www.Looksmart.com.au

2 1

DOS stuff pretty much broken [Re: wine/ dlls/kernel/kernel_main.c dlls/kernel/wp ...]
by Andreas Mohr 24 Dec '01

24 Dec '01

On Tue, Dec 04, 2001 at 02:54:50PM -0500, Alexandre Julliard wrote: > ChangeSet ID: 1007495689308334133587778 > CVSROOT: /opt/cvs-commit > Module name: wine > Changes by: julliard@wine2. 01/12/04 14:54:50 > > Modified files: > dlls/kernel : kernel_main.c wprocs.spec > dlls/ntdll : Makefile.in ntdll.spec > dlls/winedos : Makefile.in dosvm.c int09.c module.c > winedos.spec > graphics : dispdib.c > include : callback.h miscemu.h > miscemu : main.c > msdos : Makefile.in dosmem.c dpmi.c int20.c int21.c > int2f.c interrupts.c ioports.c > Added files: > dlls/winedos : devices.c dosaspi.c dosexe.h int10.c int16.c > int17.c int19.c int20.c int21.c int29.c int31.c > int33.c ioports.c vga.c vga.h xms.c > Removed files: > include : dosexe.h vga.h > msdos : devices.c dosaspi.c int10.c int16.c int17.c > int19.c int29.c int33.c vga.c xms.c > > Log message: > Moved most of the real-mode stuff to dlls/winedos. > > Patch: http://cvs.winehq.com/patch.py?id=1007495689308334133587778 This one probably breaks a whole heap of older Win3.x apps. When I started the Win98 setup.exe for fun, it choked on int 0x21 "list of lists" (DOS_LOLSeg not initialized). Trouble is that we initialize DOS variables in case of DOS programs *only*. This is rather fatal IMHO, especially in the case of List Of Lists, which is a pretty important structure with lots of information that some Win 3.x programs might rely on. Thus DOS stuff should be reorganized somehow. Any suggestions ? IMHO probably winedos should get loaded as soon as DOS3Call() gets called even once. -- Andreas Mohr Stauferstr. 6, D-71272 Renningen, Germany Tel. +49 7159 800604 http://home.nexgo.de/andi.mohr/

2 1

fixme:dialog:MSGBOX_OnInit task modal msgbox ! Not modal yet.
by Laurent Pinchart 24 Dec '01

24 Dec '01

When trying to install The Longest Journey (an adventure game), I ran into a problem with modal message boxes. The installer displays at some point a task modal message box, but for some reason the box disapears almost instantly, and I'm stuck with a focused installshield screen on which I can't do anything as the task modal msgbox is invisible and unfocused. I'd like to implement the modal message boxes to fix my problem, but I don't know where to start. Could someone give me a few indication about what would be required to achieve a proper behaviour or modal message boxes ? Thanks. Laurent Pinchart

4 8

Terrible bug: WinExec16, DOS programs
by Andreas Mohr 24 Dec '01

24 Dec '01

Hi all, I just found out that WinExec16 doesn't even support starting DOS programs. Whereas LoadModule16 doesn't seem to support loading DOS programs (error 22, which is not documented for LoadModule16), WinExec16 definitely does launch command.com on Win98SE. Not so when using Wine. What to do about that ? More specifically, which functions to change how exactly to support this ? (the whole interoperation between WinExec, WinExec16, LoadModule*, LoadLibrary*,CreateProcess etc. is highly problematic). This thing makes me get slightly worried about our Win16/DOS compatibility as a whole... :-\ -- Andreas Mohr Stauferstr. 6, D-71272 Renningen, Germany Tel. +49 7159 800604 http://home.nexgo.de/andi.mohr/

1 0

Windows screensaver.
by gleb＠nbase.co.il 24 Dec '01

24 Dec '01

Hello all, Perhaps this was asked before, but I didn't find the answer. Is it possible to run windows screensaver in linux using wine? If not, how hard it will be to write support for this? Thanks, -- Gleb.

2 2

Re: License debate conclusion
by James Tabor 23 Dec '01

23 Dec '01

Dan Kegel wrote: > > Roger Fujii wrote: > > I'm sad. The LGPL seems like the clearest hope we have of protecting > Wine against companies that want to take it and never contribute code > back. Its protection might not be airtight -- but it would clearly > communicate the spirit. And my impresson was that the majority of > Wine developers agree. > > > - Dan Hum????????? Like the ODIN Project! James

1 0

Re: License debate conclusion
by Dan Kegel 23 Dec '01

23 Dec '01

James wrote: > > Dan Kegel wrote: > > I'm sad. The LGPL seems like the clearest hope we have of protecting > > Wine against companies that want to take it and never contribute code > > back. Its protection might not be airtight -- but it would clearly > > communicate the spirit. And my impresson was that the majority of > > Wine developers agree. > > Like the ODIN Project! Good point. The ODIN project's license is at http://odin.netlabs.org/License.phtml There was some talk of sharing code between Wine and Odin in 1999; see http://www.winehq.com/News/1999-50.html#0 We might want to update http://www.winehq.com/others.html to reflect the current status and license of the Odin project. I'm not quite sure whether the Odin license is compatible with the LGPL. It looks fairly GPL compatible, but I didn't look hard. - Dan

1 0

Re: License debate conclusion
by Roger Fujii 23 Dec '01

23 Dec '01

Alexandre Julliard <julliard(a)winehq.com> wrote: > > My conclusion is that there clearly isn't enough support in the > developers community to justify changing the license. So I'm not going > to proceed with any change, either now or in the foreseeable future. hurrah. before this is concluded, I will add one thing just for the sake of archival (in case this comes up again). If ALL of wine were strictly LGPLed, basically, *all* propriatary extensions could no longer be included. Why? Because the output of winebuild will be LGPLed, thus no propriatary programs could use its output in creating a shared library. winebuild is like bison in this case, and the output of bison has a special exemption so that you can use it in something other than *GPLed programs. This inadvertant problem is precisely why *GPLed stuff has to be scrutinized carefully if you care about commercial relationships (most *GPL projects don't care) and is why commerical interests are wary of projects with a *GPL license. -r

6 6

[Fwd: Re: License debate conclusion]
by lee 23 Dec '01

23 Dec '01

> I think it's clear that Wine cares, and should be careful not to alienate > companies like Codeweaver and Transgaming. One way to deal with Transgaming > might be to start a campaign to get people to buy Transgaming subscriptions, > or perhaps try to rummage up enough of a one-time payment to get Transgaming > to contribute their current changes back. I suspect that there's some > such arrangement they'd be happy with. I tried to do just that and got rejected ( error after submitting and didn't want to try 'again' until they contact me ) by the online payment system for some odd reason....I wonder how many others have experineced this ( I checked my input twice and had all *'s filled out )........granted it could be isolated in that I made some minor goof on form..-we'll see. just a fyi in case it wasnt' me.. lee -===

1 0

Re: [PATCH] forward tab notification to the parent
by Andreas Mohr 23 Dec '01

23 Dec '01

On Sat, Dec 22, 2001 at 02:31:56PM +0000, Gerard Patel wrote: > The following patch : > ChangeSet ID: 1008622332606314052827656 > CVSROOT: /opt/cvs-commit > Module name: wine > Changes by: julliard@wine2. 01/12/17 15:52:12 > > Modified files: > dlls/comctl32 : tab.c > > Pass on all unhandeled messages to the owner. > > leads to bad regressions with some apps. > > The attached patch has the same positive effect on hh.exe > but without the regressions. Confirmed: That patch had horrible effects on desk.cpl. Applying your patch fixed it. -- Andreas Mohr Stauferstr. 6, D-71272 Renningen, Germany Tel. +49 7159 800604 http://home.nexgo.de/andi.mohr/

1 0

fixme:win32:DeviceIoControl Unimplemented control 256 for VxD
by Matts Kivik 23 Dec '01

23 Dec '01

[root@localhost Visual Pinball]# wine Vpinball.exe +relay +snoop +vxd x11drv: Warning: $DISPLAY variable ignored, using ':0.0' specified in config file fixme:dsound:IDirectSoundImpl_SetCooperativeLevel (0x403b4be8,00010022,2):stub fixme:ddraw:Main_DirectDraw_SetCooperativeLevel (0x403b50c4)->(00000000,00001008) fixme:commdlg:GetFileName95 Flags 0x00000002 not yet implemented fixme:win32:DeviceIoControl Unimplemented control 256 for VxD device VNETBIOS fixme:win32:DeviceIoControl Unimplemented control 256 for VxD device VNETBIOS fixme:win32:DeviceIoControl Unimplemented control 256 for VxD device VNETBIOS fixme:win32:DeviceIoControl Unimplemented control 256 for VxD device VNETBIOS fixme:win32:DeviceIoControl Unimplemented control 256 for VxD device VNETBIOS fixme:win32:DeviceIoControl Unimplemented control 256 for VxD device VNETBIOS fixme:win32:DeviceIoControl Unimplemented control 256 for VxD device VNETBIOS fixme:win32:DeviceIoControl Unimplemented control 256 for VxD device VNETBIOS fixme:win32:DeviceIoControl Unimplemented control 256 for VxD device NWLINK wine: Unhandled exception, starting debugger... I get the following errors when trying to run a windows program called Visual Pinball. Wine release 20011108. In addition to the crash, the toolbars are not drawn. Some tools in the toolbars are drawn when I "hoover" over them with the mouse. I another thread I have read that the VNETBIOS call is to check the MAC adress, but what is the NWLINK doing ? _____________________________________________________________ Want a new web-based email account ? ---> http://www.firstlinux.net

1 0

Re: CVS regression.
by Gerard Patel 23 Dec '01

23 Dec '01

At 02:30 PM 22/12/2001 -0800, you wrote: >I'm in the processess of doing a cvs regression to find out what broke >half-life in the main wine. The first problem appears in the "2001-11-8 >EDT" cvs, but it's not the same promlem as I was having with the current >cvs. That one occured between the "2001-11-15 EDT" cvs and the "2001-11-13 >EDT". > >But unless anyone has any ideas I though I'd start working on what patch >did it, and I was wondering if "2001-11-13 EDT" was the cvs at the >begining or end of the day (before or after that days pathces were >applied). And if the dates in the wine.cvs newsgroup are accurate. > >I'm rather new at this so any advice would be welcome. Did you read documentation/cvs-regression ? I updated some weeks ago to add precisely that you can use times up to the second so that it's possible to apply each patch separately. I use http://www.winehq.com/hypermail/wine-cvs/ to find exact patches times. > >P.S. The error i'm looking for is a timeout of a CriticalSelection when >you try to join a mulitplayer game. The one I found in the "2001-11-8 EDT" >cvs is an unhandeled exception when it first goes to the "Loading..." >screen. > Unfortunately, it is not impossible that a first breakage is completed by another a few days after. The more important breakage to find is the first (unless the second breakage is an attempt to fix the first) Another possibility is that the 2 problems are only different manifestations of a single problem; you can have a thread crash nicely, triggering the debugger, or in different circumstances nastily, without much messages. In the latter case, it can happen that another thread is blocked by the crashed thread and displays a critical section wait timeout. It will not be possible for me to help you more until next year, I'll not have internet access until then. Good luck. Gerard

1 0

CVS regression.
by Daniel Sabo 22 Dec '01

22 Dec '01

I'm in the processess of doing a cvs regression to find out what broke half-life in the main wine. The first problem appears in the "2001-11-8 EDT" cvs, but it's not the same promlem as I was having with the current cvs. That one occured between the "2001-11-15 EDT" cvs and the "2001-11-13 EDT". But unless anyone has any ideas I though I'd start working on what patch did it, and I was wondering if "2001-11-13 EDT" was the cvs at the begining or end of the day (before or after that days pathces were applied). And if the dates in the wine.cvs newsgroup are accurate. I'm rather new at this so any advice would be welcome. P.S. The error i'm looking for is a timeout of a CriticalSelection when you try to join a mulitplayer game. The one I found in the "2001-11-8 EDT" cvs is an unhandeled exception when it first goes to the "Loading..." screen.

1 0

For review... CD interfaces in wine
by eric pouech 22 Dec '01

22 Dec '01

not ready yet for cvs inclusion (yet), this patch implements two things: - it replaces the wine internal & proprietary cdrom interface (used in MCICDA and MSCDEX/int2F) with the proper win32 ioctl:s calls - it allows opening any device with CreateFile (using the name "\\.\E:") (this is still very hackish, but not worse than what already existed) patch posted for review/comments/enhancements... (before I go on vacation, in case someone would work on something equivalent) A+ -- --------------- Eric Pouech (http://perso.wanadoo.fr/eric.pouech/) "The future will be better tomorrow", Vice President Dan Quayle

2 1

RE: Installshield 6 (inter-proc) patches
by Patrik Stridvall 22 Dec '01

22 Dec '01

> On Fri, 21 Dec 2001, Patrik Stridvall wrote: > [...] > > > > However, just because it doesn't combine to something normal > > > > doesn't mean that is doesn't combine. > > > > > > And how does it combine exactly? Both the book and the > critic are > > > available independently. > > > > > > You can still read the book independently from the critic so > > > they are obviously two separate pieces of work, not a single one. > > > > > > Or how do you define 'combine'? > > > > I do not define combine in any general way. It depend on > what my intent > > is and on the circumstances. I do not expect others to > nessarily define > > combine in the same way either. > > I would say that piece of work 1 combines with piece of > work 2 if it > alters piece of work 1 and results in an entity that a user would > consider to be a single piece of work of the same type. > > Now I believe this is a more restrictive and reasonable > definition of > 'combine' and should match general expectations better than your > 'everything combines with everything if I decide so' definition. What a user would consider a single piece of work depends on the user so it is very vague and unsuitable definition in a court of law. > [...] > > > So you agree that gratis, open-source and commercial > works are all > > > entitled to the same copyright protection. The last two > paragraphs of > > > your email seemed to imply differently to me. > > > > Yes, it is entitled to the _same_ copyright protection. > > Good. We agree on something! :-) > > > > However since you give away your work gratis to the end user by > > your free choice, you have the right to stop doing this(1), > > if anything I sell to the end user bothers you. > > Yes, or as the copyright owner I have another alternative: choose a > license that restricts what you can do with my work. I can even choose > to use multiple licenses and tell you to which one you must abide by > depending on how much money you give me. And no matter how much or how > little you pay me, you must abide by this license, this at least we > agree on, so that's good. > And if I say that you must not redistribute work based on mine then > you must comply. And basically saying 'take his work and then apply my > modifications' still has the same effect: the user magically > gets a copy > of your work which is clearly based on mine. So the end > result is still > that you are redistributing a work based on mine which is > precisely was > forbidden by the license agreement. No, the license is not a contract, and even if it was it can't override the original contract that you implicitly made with society to get any copy protection at all. The license can only be about the rights granted to you by society to your work and while you certainly can deny me, as normal commercial licenses do, that right do redistribute, you can only deny me the right to do derived works to the extent copyright law defines a derived work.

1 0

License debate conclusion
by Alexandre Julliard 21 Dec '01

21 Dec '01

OK folks, I think we are way past the end of the useful part of this discussion, and it's time to come to a conclusion. I'll ask people who want to continue arguing the fine points of the LGPL to please do it by private mail. My conclusion is that there clearly isn't enough support in the developers community to justify changing the license. So I'm not going to proceed with any change, either now or in the foreseeable future. Thanks to everybody who participated to the discussion, and now let's go back to writing code... -- Alexandre Julliard julliard(a)winehq.com

1 0

Latest OSS changes and Pajam Sam, again
by Ori Pessach 21 Dec '01

21 Dec '01

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi again, For what it's worth, I've been testing those troublesome games from Humongous with newer versions of Wine. Up until Nov. 9th, they worked fine. Afterwards, they started failing with a difficult to diagnose error message on startup, saying that the sound card was not detected. I tested this with OSS and ALSA sound drivers. The latest version fails after playing a sound on startup. I get two error dialogs - the first says: "The sound card driver is refusing to accept our sample", the second says "The sound card driver will not unprepare our sample header". I'm also still getting "err:wave:OSS_AddRingMessage buffer overflow !? " messages. I have the feeling that these messages should give someone who's familiar with the code a bit more to go on. waveOutUnprepareHeader() seems like a good place to start, and I'll look at it myself when I have the time for it (not soon), unless somebody else figures it out first. Bye, Ori Pessach -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: http://www.oripessach.com iD8DBQE8Ip0kzA/uWWyw6uQRAgeUAJ9K2NvscRvz0ciAvvsWqVF/3M1qBACfe8QA k8KtoVC5TIP2cYhONTWbLlk= =17aJ -----END PGP SIGNATURE----- _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com

2 1

RE: Installshield 6 (inter-proc) patches
by Patrik Stridvall 21 Dec '01

21 Dec '01

> On Fri, 21 Dec 2001, Patrik Stridvall wrote: > [...] > > > - a critic's book about the original is not a derived piece > > > of work. It > > > is clearly specific to the original book but does not > modify it and > > > clearly does not combine with it to form a single piece of work. > > > (no real equivalent to this one, closest thing would be an > > > application/script that uses another, like a script that > calls 'ls') > > > > This is not all clear IMHO. What a single piece of work is not > > well defined. Sure a combined work will not be a book since a book > > normally is something that can be read in linear order and combining > > with the critisism will not likely form a normal linear book. > > > > However, just because it doesn't combine to something normal > > doesn't mean that is doesn't combine. > > And how does it combine exactly? Both the book and the critic are > available independently. > > You can still read the book > independently from > the critic so they are obviously two separate pieces of work, not a > single one. > > Or how do you define 'combine'? I do not define combine in any general way. It depend on what my intent is and on the circumstances. I do not expect others to nessarily define combine in the same way either. However, the problem is that you (or rather the law) must define what combine means for your: "Can't legally distribute, is derived work" to have any meaning. > [...] > > > > > > From my point of view open-source is not any different from any > > > commercial work. Obviously there are legal means to obtain > > > the original > > > work in both cases (whether you have to pay for it is irrelevant). > > > Otherwise the point is moot. > > > > > > But saying that open-source is different would mean that > > > because you > > > are not making a direct profit from this work, you are > not entitled to > > > any protection under copyright law. You can't mean that, can you? > > > > But you _have_ protection from copyright, everybody that > _distribute_ your > > work must fullfill the license otherwise you can sue them. > > So you agree that gratis, open-source and commercial works are all > entitled to the same copyright protection. The last two paragraphs of > your email seemed to imply differently to me. Yes, it is entitled to the _same_ copyright protection. However since you give away your work gratis to the end user by your free choice, you have the right to stop doing this(1), if anything I sell to the end user bothers you. (1) Of course you, by your free choice, choose to give the end user the right to redistribute as well so, he can legally give it to his "friends" all other the world, but that is not my problem either. Note that I not saying that your choice was wrong, but you shouldn't complain that rights that you gave up by _free_ choice have been used against you.

2 1

Re: Visual FoxPro 5 apps
by Rick Romero 21 Dec '01

21 Dec '01

I just noticed that my Foxpro 5 post is on WWN, so I thought I'd share the thread from the wine-users list... Rick On 5 Dec 2001 at 13:34, Rick Romero wrote: > On Wed, 2001-12-05 at 13:22, gerard patel wrote: > > On 05 Dec 2001 11:55:10 -0600, Rick Romero <rick(a)valeoinc.com> wrote: > > > > <snip window problems> > > > > >Now I've tried a few different distro's, and quite a few different > > >releases of wine (been compiling from cvs for the last couple months), > > >so I don't think it's just me... BUT. > > > > Try with Wine from 01 june 2001. > > Huge changes have caused several severe regressions > > after this date and they are mostly unfixed. > > Well, I downloaded Wine-20010510, and the MDI windows work PERFECTLY. > They're highlighted blue when active > The scrollbars work > The mouse click is released. > > Although overall, it doesn't work near as well.. > > > > > If your app has the same glitches with Wine as of 01 june > > 2001, its problems are not related to the general regression. > > In this case try to do this, I'll take a look. > > In the other case, it's unnecessary as I'm already aware of > > these problems. > > If I'm not imposing too much, could you point me in the right direction? > > I don't know if I could come up with anything of 'acceptable patch > quality', but I'd like to try. > > Is the problem in mdi.c? > If it was only a simple bug, I'll have it killed since a long time. I'm mostly in the dark, but I think it's more the progressive passage to a whole new design that has caused a string of regressions. Gerard ----- Valeo, Inc. will be closed for the Holiday season starting on December 20, 2001 through January 1, 2002 resuming business on January 2, 2002. We wish you a Happy Holiday Season! -- Rick Romero IT Manager Valeo, Inc. ph 262.695.4841 fax 262.695.4850 rick(a)valeoinc.com

1 0

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