December 2001 - Wine-Devel - list.winehq.org

Windows screensaver.
by gleb＠nbase.co.il Dec. 24, 2001

Dec. 24, 2001

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 Dec. 23, 2001

Dec. 23, 2001

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 Dec. 23, 2001

Dec. 23, 2001

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 Dec. 23, 2001

Dec. 23, 2001

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 Dec. 23, 2001

Dec. 23, 2001

> 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 Dec. 23, 2001

Dec. 23, 2001

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(a)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 Dec. 23, 2001

Dec. 23, 2001

[root(a)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 Dec. 23, 2001

Dec. 23, 2001

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 Dec. 22, 2001

Dec. 22, 2001

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 Dec. 22, 2001

Dec. 22, 2001

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 Dec. 22, 2001

Dec. 22, 2001

> 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 Dec. 21, 2001

Dec. 21, 2001

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 Dec. 21, 2001

Dec. 21, 2001

-----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 Dec. 21, 2001

Dec. 21, 2001

> 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 Dec. 21, 2001

Dec. 21, 2001

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

RE: Installshield 6 (inter-proc) patches
by Patrik Stridvall Dec. 21, 2001

Dec. 21, 2001

> On Fri, 21 Dec 2001, Patrik Stridvall wrote: > > > There are many thing that are important in the world not just one, > > so it was just a reaction of your persistance that the spirit of > > something is the only thing that matters. > > I focused on the spirit to put some sense in the discussion, > go get to the > point where we agree to disagree, but you don't seem to want that. > > In computers we have interfaces and implementations. It's healthy to > separate the two. Yes, but this doesn't mean that this is always possible. > In our case, the interface is the spirit of > the LGPL, > while the implementation is the LGPL itself. > > If there are 'Gapping Holes' anywhere, they are in your > arguments. You say > you agree with the interface, but you disagree violently with the > implementation. On the other hand, when I ask you for a different > implementation, you can't it can not be done. I say that it can't be done without having a copyright law that will be unacceptable in other ways. > Patrik, you > can not agree > with an unimplementable interface, for crying out loud!!! You > have to make > up your mind and choose! I would very much like to have "Peace on earth", but I don't think it every will be "Peace on earth". You can call that illogical if you wish. It is up to you.

1 0

license discussions
by Marcus Meissner Dec. 21, 2001

Dec. 21, 2001

Hi, Could we please create a new mailing list wine-license, where all the people who care about licenses can discuss them? Ciao, Marcus

2 1

RE: Installshield 6 (inter-proc) patches
by Patrik Stridvall Dec. 21, 2001

Dec. 21, 2001

> On Thu, 20 Dec 2001, Patrik Stridvall wrote: > > > Does it nessararily follow that you wish to accept any means to > > achieve this? Including, say, to be really extreme: > > "Nuke the middle east, then it will be peace there" > > and after enough nukes it probably WILL be peace, > > so it would be entire in line with peace on earth. Right? > > Patrik, if you think licensing software under the LGPL is > equivalent to > nuking the middle east out of existence, you need to take a _deep_ > breath, drink some cold water, and stay away from those pills. > > Since we're here, this is the type of attitude that really > destroys the > credibility of much of your arguments. It was purposely extreme to illustrate that you can fullfill the spirit of something good with very bad results. There are many thing that are important in the world not just one, so it was just a reaction of your persistance that the spirit of something is the only thing that matters. > I mean, exagerations > of the form: > 'LGPL gives you nothing, it's a pile of crap' despite the > enormous effort > put in it by various lawyers and law professors from reputable > universities, will not buy you many friends. Do you really > think that the > entire law establishment in the US has all gone mad and can't see the > 'Gapping Hole' in the LGPL, and you were the chosen one to see it? I'm sure they all have worked very hard, however as in the extreme example above, all means to achieve something is not nessarily good, if seen as a whole. The meant this time is the doctrine of derived work, which since it is one of the few means they got it was naturely the choice. However, a to strong doctrine of derived work, is not good from other points of views so it will be entirely possibly that the courts will not rule in their favour.

2 1

RE: Installshield 6 (inter-proc) patches
by Patrik Stridvall Dec. 21, 2001

Dec. 21, 2001

> On Thu, 20 Dec 2001, Patrik Stridvall wrote: > > > No, its not irrelevant because it will effect the advise the company > > lawyers give their clients. > > But know you are inconsistent with yourself. You've been > claiming that it > is the very spirit of the LGPL that would scare companies > away, and I can > see some merit to that idea. No, I have been say that the _means_ to implement the spirit of LGPL might scare away companies. > You've also been claiming that > the LGPL may > not be enforceable, thus in mathematical terms, > the expected value of the LGPL < the intended meaning of the LGPL > it follow directly, that the more you are right, the less negative the > advise of the lawyers. Only if lawyers have certain mathematical properties, which they certainly do not have. Actual most functions don't have such properties either. > So, if you 100% right, the LGPL would become BSD, and the > lawyers would > give the same advise, as for the BSD. If you are 100% wrong, > then we do > get the full protection of the LGPL, and we're happy. > Anything in between > is a linear combination of the two. In any case, there really > is no point > about bitching the doctrine of derived work. QED. LGPL can only be BSD if the doctrine of derived work is very weak, so it does have something to do with that. > In fact, choosing the LGPL is a very nice way of hedging our > bets agains > future changes in copyright law. And this is so because of > the negative > feedback loop that the LGPL introduces agains the copyright > law. Brilliant. Now you are contradicting your self. You said earlier IIRC something about that you shouldn't believe that the license Wine chooses effect copyright law.

2 1

RE: Installshield 6 (inter-proc) patches
by Patrik Stridvall Dec. 21, 2001

Dec. 21, 2001

> On Thu, 20 Dec 2001, Patrik Stridvall wrote: > > > Sure it is true that what people (read: companies) believe > is true is > > more important than what really is true. > > So, in fact, you indirctly agree that arguing about the doctrine of > derived work as part of this discussion is irrelevant. No, its not irrelevant because it will effect the advise the company lawyers give their clients. You seem to wish to use ignorance (or uncertainty) as weapon to protect Wine, but know this: Ignorance (or uncertainty) cuts both ways. Gav has said that Transgaming or for that matter Corel would have use Wine if it had been LGPL:ed. Perhaps this was because of ignorance, perhaps not. Anyway even if you would be able to convince Gav that he was/is wrong, you must realize that Gav IIRC have researched legallity issues extensively so it is entirely likely that somebody else spending similar resources would come to the same, in your opinion wrong, conclusion. In short: Ignorance (or uncertainty) is a dangerous weapon. > All you seem to be saying is that you think that the _spirit_ > of the LGPL > would be detrimental to Wine since it will drive companies away. > > Right? No. I have been trying to explain just because to are for the spirit of something it is not nessarily so that you support all possible means to acheive something and sometimes any acceptable means to acheive something might not exists. Do you support the spirit of: "Peace on earth!" Does it nessararily follow that you wish to accept any means to achieve this? Including, say, to be really extreme: "Nuke the middle east, then it will be peace there" and after enough nukes it probably WILL be peace, so it would be entire in line with peace on earth. Right?

2 2

RE: Installshield 6 (inter-proc) patches
by Patrik Stridvall Dec. 21, 2001

Dec. 21, 2001

> Patrik Stridvall <ps(a)leissner.se> writes: > > > But why should I do that? > > I can for example write a script that download Wine for the > end user user > > and apply the patch automatically. > > The patch would be considered a derivative work, so distributing it > would also violate the LGPL. That again is dependent of the doctrine of derived work have any meaning since the patch is written by me and only contains my work. Just because you build upon somebody else work doesn't mean it is a derivation. Anyway since it denies my right to speech it must be constitional within the context of the first amendment which is IMHO very unlikely that a strong doctrine of derived work is. The copyright clause exception only reserves only gives congress the right to give exclusive rights to _their_ work not to the work of others (read: me). Note by patch I do not nessarily mean a patch like (diff -u) that contains the (LGPL:ed) context of the patch. An "ed-script" or whatever similar will do. Anyway the LGPL:ed context of a (diff -u) patch might very well be consider fair use so that might not be relevant.

4 4

Re: CryptoAPI (no, this has nothing to do with licensing! YAY!)
by David Elliott Dec. 21, 2001

Dec. 21, 2001

On 2001.12.20 11:52 Travis Michielsen wrote: [BIG SNIP] > Actually I too, have been hacking away at the CryptoAPI (advapi32.dll) > and > was going to submit a full patch for it at the end of the week. My > patch, > however, has almost a completely different approach to the problem! > Attached is my version (not quite complete or clean). > > These are the main differences and issues I see between our patches: > > 1) I can successfully acquire/release a context (tested with MSDN sample > code). I have not experienced any problems with <loading> a CSP. Umm, yes, I can successfully acquire and release when testing with the MSDN sample as well, but not with RSAENH.DLL that IE wants. > 2) Currently the ms CSPs can perform but all launch pstores.exe - the > protected stores service. This is fine except that it eventually crashes > > with an unhandled exception c0000005 and then becomes unwilling to start > again. Pardon my ignorance, but I didn't realize that that was what pstores did. > 3) Dependancy functions of pstores and M$ providers not implemented: > (advapi:RevertToSelf, ntdll:NtOpenProcessToken, advapi:SetThreadToken, > mpr:WNetGetCachedPassword, etc.) Yup, if pstores is necessary, we'll need pstores working, so that's something to add to the task list. > 4) I do not create any list of providers. This should not be required as > the > registry is supposed to contain the list of available providers. Once a > handle is acquired then we can gain access to the provider by this > handle. > Note: Key and hash objects need to link to the provider handle, when they > are > created. As for the key and hash: Yes, I am well aware of this, there is a blatant FIXME in the code since I haven't gotten there yet. And I don't know where you get that I am making a list of all CSPs. What I am doing is making a list of any CSPs which are in use and storing the appropriate function pointers in that object. I could simply do a loadlibrary each time the CSP is loaded and store all of that information for every context. But I thought it would be better to do it the way I did so that if multiple contexts are acquired from the same provider we don't have duplicate information in memory. > 5) I have not yet considered thread or process safing/locking. Nor have I > > done any reference counting. Well, I am not so sure about my thread safety but I think theoretically it is okay. I wrote the thread safety in from the beginning. > 6) Seting and getting Key/Hash/Prov Params doesn't consider flags not > used by > the CSP and have meaning in advapi32.dll. Haven't even really gotten that far yet. > 7) I currently do not allow a CSP to drop any of the stardard functions. > > This only affects a few functions, however, as MSDN states these > functions > are *required* for the CSP to have. If they are not implemented they > must > set the last error as ERROR_CALL_NOT_IMPLEMENTED. Well, CSP.DLL from the CSPDK does not provide a couple things. Originally I required every function to be provided but when I found that CSP.DLL did not provide one of them I decided to err the other way and only require the bare essentiallys like Acquire/ReleaseContext. > 8) You seem to make not use > ?????????? > Anyway I think the correct thing to do right now is to co-ordinate our > work > to make a single patch and implementation. > YES, definitely. Sorry to be stepping on your toes here. Most of the CryptAcquireContext function, specifically the parts that look up which CSP we need to load, I implemented rather quickly months ago. I didn't have time to do anything until a few days ago when I wrote everything else and posted it on wine-devel. > I am currently testing this code against windows 98. > Well, I have Win95osr2 running under Win4Lin and I use that as my C: drive in Wine as well. It works a lot better having everything stored on an ext2 drive than on vfat. I have not yet taken a look at your code but will do so as soon as I finish reading the rest of today's wine-devel. -Dave

1 0

Re: timed-out non-overlapped ReadFile
by Mike McCormack Dec. 21, 2001

Dec. 21, 2001

Hey Lawson, Cool. i just wanted to get apps like yours back to their working state. Ideally i need to add a bit more code for the case (ReadIntervalTimeout = -1) that waits until at least some data is received before returning.... more trouble :-) The timeouts for non overlapped ReadFile should help alot of the recent problems reported on wine-users... hopefully. Mike Original message from: lawson_whitney(a)juno.com .. >Sorry if that sounded like faint praise. The app works as well with >both patches as it did before with neither, and probably there is some >other app that needs non-overlapped ReadFile to time out. > >Thanks! > >Lawson ------------------------------------------ mailto:Mike_McCormack(a)start.com.au ph +82 16 430 0425 __________________________________________________________________ Get your free Australian email account at http://www.Looksmart.com.au

1 0

Re: timed-out non-overlapped ReadFile
by lawson_whitney＠juno.com Dec. 21, 2001

Dec. 21, 2001

On Fri, 21 Dec 2001, Mike McCormack wrote: > > This patch handles the special case where > ReadIntervalTimeout=MAXDWORD, ReadTotalTimeoutConstant=0 and > ReadTotalTimeoutMultiplier=0 a little better. We should just wait > until we get some data, then read it and return in that case. > > Mike > > ChangeLog: > * handle ReadIntervalTimeout=MAXDWORD special case a bit better > Sorry if that sounded like faint praise. The app works as well with both patches as it did before with neither, and probably there is some other app that needs non-overlapped ReadFile to time out. Thanks! Lawson Slowly but with considerable uncertainty.

1 0

RE: Installshield 6 (inter-proc) patches
by Patrik Stridvall Dec. 21, 2001

Dec. 21, 2001

> > You forgot that the end user still need to legally get hold of > > the work somehow. For normal commercial stuff this involves > > paying for it and the author will get payed just like he did in > > the old non-digital world for _each_ copy. > > I did not forget that. Good because this is _very_ important. > But I still do not think a book author would > allow you to publish a patch that would modify the last chapter to > provide a different ending. Why, if people like the alternative ending and recomend it to other he might get increase sales because presumeable they want to read the begining. Anyway, we a talking about what is legal and what is not, so that doesn't matter. > The point is that whatever way you use to distribute your > modifications, they are specific to the original work, alter it and > combines with it to provide a single new work. And these are the > criteria I would use to define a 'derived piece of work'. > > And since > derived pieces of work reuse the original work it seems only fair that > they can only do so if they respect the license of the original work. I might sound good from a open source perspective but it nearly isn't as attrative applied to normal commercial works. > Let's take a couple of common sense examples and assume that the > original work is a book. > - a bottle of black ink is not a derived piece of work. Obviously you > can alter the book quite a bit by dropping its content on it > and the ink > will definitely merge with the book. But just as obviously the ink is > not specific to your book. > (computer science equivalent: a file compression utility) First of all since we have a physical object we defintively in addition have the doctrine of first sale so inkstaining your book and reselling it is specifically allowed by law. By selling it the author lost control over that copy. > - 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. > - as long as you have the right to sell the original book, you should > have the right to sell it bundled with other books. The reason is that > this does not alter the original book and that it does not form a > combined piece of work. > (linux distributions) Again, you seem to miss that just because thing does not combine in normal ways it doesn't mean that they don't combine. > - but leaflet that replaces the last chapter of the book to provide a > different ending is a derived piece of work. The reason is that it is > specific to the original book, alters the story (the original work of > which the physical book is nothing but a printed > representation) told by > the book, and combines with it to form a new work (a new story with a > different ending). Thus you can only distribute it with permission of > the original author, even if you do not distribute the original book > with your leaflet. > (that's your patch example) Here it combines in a linear readable way. In short: Everything combines with everything else is some way, so unless you define some exact criteria on where the legal border talking about what can combine is rather pointless. The only trend, in your examples, I can see is that you wish to give work that combine in linear readble way more protection, for some, not mentioned, reason. Can you please explain why? > > No particular problem, > > except that some companies might be greedy and want more, > > but hey, do you really wish to give them more? > > I did not express any wishes and in any case they are irrelevant: I > do not have the power to give companies more or less. Now, when I'm > world-dictator for life... :-) :-) > > Open source is more problematic since the end user legally can > > get hold of the work for free and thus any distribution > > restrictions is meaningless since the end user doesn't distribute. > > 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.

2 1