BTW, the header files and libraries used would be licenced under something
like BSD/X11
And the code thats shared between ReactOS and WINE would be LGPL or
something similar.
Currently, we have 3 different projects that are working towards windows
"compatibility".
We have ReactOS
We have WINE
and We have MingW-Runtime and w32Api (refered to as just MingW from now on)
The 3 projects have different goals but the same target. Microsoft Windows
and the Microsoft SDK, DDK
On Friday 17 October 2003 21:55, you wrote:
> If someone wants to come up with a few lines of awk that take
> something like this input:
>
>
>
> and convert it to this:
>
Test these lines
BEGIN { FS = "\"" }
{ A+=$2 }
{ B+=$4 }
END { print "" }
mvh Acke
Does everybody's kernel32 named pipes test pass (in wine)? Named pipes are
acting very wierd here, lots of segfaults and other wierdness... the test
seems to freeze attempting to create the alarmThread in test_NamedPipe_2
(test 3 of 4). The wineserver holds up OK, but the client side looks a m
Title: Re: WWN: wn20031017_192.xml
> There's still something wrong with the sorting:
Nope. The problem is with you :)
Since you post from two different email accounts that means the
script I run generates two different lines for you every week.
Then I go in and manually adjust it. (Con
On Fri, 17 Oct 2003 18:58:42 +0200, Lionel Ulmer <[EMAIL PROTECTED]> wrote:
>The big question is when the card does not support it and we need to do the
>decompression in software and send it back to the card In this case, do
>we violate it or not ?
Is it a patent for a hrdware solution, or f
Robert Reif wrote:
This patch fixes a crash when doing a DRV_QUERYDEVNODE
from 16 bit code but I'm not sure this is the best
way to fix this problem.
if you have some apps doing DRV_QUERYDEVNODE from 16 bit interface, then
the patch is correct.
A+
--
Eric Pouech
On Fri, 2003-10-17 at 17:36, Geoff Thorpe wrote:
> On October 17, 2003 11:56 am, Mike Hearn wrote:
> > In future please do not raise patents on this list. What we don't know,
> > can't hurt us (as much).
>
> IANAL, but I beg to differ.
I'm not either, but the advice I gave is based on similar dis
On Fri, Oct 17, 2003 at 11:47:04AM -0400, Vincent Béron wrote:
> Le ven 17/10/2003 à 11:24, Jonathan Wilson a écrit :
> > What specificly does this patent cover and what parts of WINE would it affect?
> > (i.e. which bits of windows, if implemented in WINE, would fall under the
> > patent?)
>
> P
On Fri, 17 Oct 2003, Brian Vincent wrote:
>
> wn20031017_192.xml
There's still something wrong with the sorting:
The sorting looks odd:
--
Dimi.
On October 17, 2003 11:56 am, Mike Hearn wrote:
> In future please do not raise patents on this list. What we don't know,
> can't hurt us (as much).
IANAL, but I beg to differ.
First, Wine should be reasonably well protected against patent
infringement, because (and I mean this in the nicest way
In future please do not raise patents on this list. What we don't know,
can't hurt us (as much).
On Fri, 2003-10-17 at 16:24, Jonathan Wilson wrote:
> What specificly does this patent cover and what parts of WINE would it affect?
> (i.e. which bits of windows, if implemented in WINE, would fall un
Le ven 17/10/2003 à 11:24, Jonathan Wilson a écrit :
> What specificly does this patent cover and what parts of WINE would it affect?
> (i.e. which bits of windows, if implemented in WINE, would fall under the
> patent?)
Probably not much, since (IANAL) it'd be the GL driver doing the actual
work
The only thing I miss from MurkySlop, after years of freedom
from it, is the GPS/road/topo map programs from Garmin (primarily),
DeLorme, et al. I keep wine in each new release of RedHat and YellowDog
just in the hope of that. Any guesses when it might be up to them?
--
RR 'Beartooth
What specificly does this patent cover and what parts of WINE would it affect?
(i.e. which bits of windows, if implemented in WINE, would fall under the
patent?)
15 matches
Mail list logo
