take a huge capital and time investment, but the
payoff would likely be worth it.
I've scaned the other mails on the list, but am not quite sure if this point
was brought to attention already: I guess what would most aid Wine
development from a legal perspective would be legal certainty
On 11/21/05, Michael Jung [EMAIL PROTECTED] wrote:
I think it's kind of ironic that the finding of facts states that it's not
possible for technical or economical reasons to clone the Windows API, a
statment which in my opinion Wine clearly proves wrong, while not mentioning
the legal
On Fri, 18 Nov 2005 13:11:30 +0100, Mike Hearn [EMAIL PROTECTED] wrote:
Most of the time, the code itself is the best documentation, and it'd
take a government with steel balls to force Microsoft to open source
Windows. That'd almost guarantee its bankruptcy.
I thought the current crew
On Fri, 2005-11-18 at 15:19 -0800, Daniel Kegel wrote:
Here are a few things a judge could order Microsoft to do that would help
Wine:
* order them to break up into two companies, one for operating systems and
.net, one for everything else
* donate gobs of cash to Wine
* offer a perpetual,
Folks, here is another question:
The following excerpt is from the Microsoft antitrust trial's finding
of facts. Some of what has been said in this thread hints at the
extreme position this finding takes. That said, I can't believe that
members of this community believe the task is impossible,
Jeremy,
I am sorry if my remarks troubled you. Perhaps my meaning didn't come
across as intended? I didn't mean to imply that WINE is not currently
useful or has an impossible task. I believe just the opposite - that
WINE is useful and it can, one day, achieve 100% Windows
compatibility.
On Sat, 19 Nov 2005 21:54:39 +0100, Susheel Daswani
[EMAIL PROTECTED] wrote:
Jeremy,
I am sorry if my remarks troubled you. Perhaps my meaning didn't come
across as intended? I didn't mean to imply that WINE is not currently
useful or has an impossible task. I believe just the opposite -
Susheel Daswani wrote:
My belief (which opposes the 'fact' stated above) is that if there was
virtually complete documentation of what exists, and full disclosure
of additions and modifications, a cloning could be achieved. Of
course it would take a huge capital and time investment, but the
[EMAIL PROTECTED] wrote:
The only real barrier that remains is for sufficient number of
businesses and administrations to adopt a strategy where it is no
longer acceptable to publish and transmit documents in a format that
forces the recipient to have the lastest version of M$ office to
Juan Lang wrote:
The Windows API is of course public, so my guess is that isn't
a huge bar to creating WINE.
Unfortunately, you guess incorrectly. While the API may legally be public
(the interface can't be protected, as far as we know,) it isn't always
documented. MS uses undocumented APIs
Hi,
On Fri, Nov 18, 2005 at 10:00:22AM +, Aneurin Price wrote:
And on that note: does anybody know of any documentation anywhere for
msvcrt sopen? Particularly, what the different pmode flags mean (I'm
getting 0x01b6)...
I've got an old grey folder with MSVCRT API documentation at home
Susheel Daswani wrote:
In terms of what a court could order, I think remedying the
documentation and scope problems wouldn't be overly difficult.
Actually I think it'd be very hard. It's not like Microsoft is just
ULTRA-EVIL here, they often face the same problems we do with
application
Susheel Daswani wrote:
For my 'Antitrust IP' course this semester I am writing a brief
about why I think the remedy in the Microsoft antitrust case was
inadequate.
Back in the day, I wrote an essay about this; it's online at
http://kegel.com/remedy/
in particular,
The Windows API is of course public, so my guess is that isn't
a huge bar to creating WINE.
Unfortunately, you guess incorrectly. While the API may legally be public
(the interface can't be protected, as far as we know,) it isn't always
documented. MS uses undocumented APIs very, very
Susheel Daswani [EMAIL PROTECTED] wrote:
So my question for the WINE developers is What materials from
Microsoft would most aid the development of WINE? The Windows API is
of course public, so my guess is that isn't a huge bar to creating
WINE. So what are the bars? Is it simply the scope
On 11/17/05, Susheel Daswani [EMAIL PROTECTED] wrote:
I plan to use your answers for no other purpose than educating my
professor on what, alas, *could* have been done to help restore
competition to the personal desktop OS market.
Hello,
The only real remedy to the Microsoft Monopoly would
16 matches
Mail list logo
