For those coming internationally, just hope that Microsoft isn't waiting
at the airport with a bunch of DCMA lawyers to arrest you :)
Mind you, M$ wouldn't do that because they don't like to admit that Linux,
Wine, or anything else actually exists.
Regards,| It's always bad news in
I received this today... it seems Lindows seem to want to host a Wine
conference. I noticed that they misspelled Alexandre's name and email
address, though they claim to work with him.
Well, I'm not suprised. I'm not 100% sure how his last name is spelled.
I usually cut and paste or more
For those coming internationally, just hope that Microsoft
isn't waiting
at the airport with a bunch of DCMA lawyers to arrest you :)
Mind you, M$ wouldn't do that because they don't like to
admit that Linux,
Wine, or anything else actually exists.
I don't think Wine does anything DMCA
On Wednesday 06 February 2002 11:40 am, Patrik Stridvall wrote:
I received this today... it seems Lindows seem to want to host a Wine
conference. I noticed that they misspelled Alexandre's name and email
address, though they claim to work with him.
Well, I'm not suprised. I'm not 100%
PS. Does anybody know if a VISA to the US is required for citizens of the
European Union countries (like Sweden)?
Nope.
Check out:
http://www.ins.usdoj.gov/graphics/lawenfor/bmgmt/inspect/vwpp.htm
Most importantly:
What Countries Are in the VWP?
The following countries are currently in the
On Tue, 5 Feb 2002, Patrik Stridvall wrote:
I have finally tried to compile Wine with MSVC.
Eventhough I had to do some hack on the whole
it compiled quite well.
Great. On a slightly related note, is it possible that we compile Wine
with the MS headers? What would it take to do that? If we
On Wed, 6 Feb 2002, Patrik Stridvall wrote:
Anybody else interested?
I might, provided of course some other people show up... :)
--
Dimi.
First the huge Office 2000 patch from Codeweavers, now the wineconf
invitation from lindows. So we might call it official that lindows is
using wine and they DO give back their patches?
ciao
Jörg
--
Joerg Mayer [EMAIL PROTECTED]
I found out that
On Wed, 6 Feb 2002, Patrik Stridvall wrote:
Anybody else interested?
People from Macadamian might be going, it all depends
on our various schedules. (Right now it is looking
like a go, but won't know for sure for a few days)
-James
--
James Hatheway
[EMAIL PROTECTED] ~
On Tue, 5 Feb 2002, Patrik Stridvall wrote:
I have finally tried to compile Wine with MSVC.
Eventhough I had to do some hack on the whole
it compiled quite well.
Great. On a slightly related note, is it possible that we compile Wine
with the MS headers? What would it take to do that?
If i got a paid trip, i'll come anytime... But I can see why I'm not invited
:(
The working SetupAPI dlls is on it's way, it's taiking some time as i'm
currently heavily overworked, most of the functionality is there however.
/Stefan
I received this today... it seems Lindows seem to want
Hmm,
If so, wouldn't they be recruiting wine developers? Or have they?
Best REgards,
Stefan
Joerg Mayer wrote:
First the huge Office 2000 patch from Codeweavers, now the wineconf
invitation from lindows. So we might call it official that lindows is
using wine and they DO give back their
On Wed, 6 Feb 2002, Patrik Stridvall wrote:
Well. If you do as I did and just add just create
a Visual Studio Project (.dsp) for each DLL using the
MS headers is the default. I had to add ..\..\include
to the include path to get it to use the Wine header.
Sorry Patrik if my questions are
I'm working with someone involved in the Microsoft trial,
and they are looking for some information from the
Wine team.
Specifically, they need clear examples of Windows APIs
that are not documented, or cases where the actual
working of an API is substantially different from the
documented
Platform Compilers BinFmt Headers
- -- ---
Linux gccELF Wine
*BSD MSVC PE MS
Solaris BorlandReactOS(?)
Cygwin
There are very little changes needed for the ReactOS port and only one
or 2 ReactOS specific
On Wed, 6 Feb 2002, Patrik Stridvall wrote:
Well. If you do as I did and just add just create
a Visual Studio Project (.dsp) for each DLL using the
MS headers is the default. I had to add ..\..\include
to the include path to get it to use the Wine header.
Sorry Patrik if my
On Wed, 6 Feb 2002, Patrik Stridvall wrote:
[...]
I also so got some other strange error with PCONTEXT
in winnt.h which in didn't understand.
You must define _X86_ before including 'winnt.h'. Otherwise it won't
known on which architecture it's being compile and it won't define
CONTEXT.
On Wed, 6 Feb 2002, Patrik Stridvall wrote:
[...]
I also so got some other strange error with PCONTEXT
in winnt.h which in didn't understand.
You must define _X86_ before including 'winnt.h'.
Otherwise it won't
known on which architecture it's being compile and it won't define
Is it possible to compile/linkedit .obj, not the source, with wine libs?
not directly... you'd need a linker that understands both .o and .obj
formats
tweaking binutils with windows support enable might do it, but it may
be painfull
A+
--
---
Eric Pouech
Personally I think that the ultimate solution would be to
automatically generate the .dsp files from Makefile.in or otherwise.
May not be easy but you are pretty good with perl so if anyone can
pull it off it's you :-)
I don't think it is that difficult even for somebody less
Speaking of conferences, is anyone planning on going to FOSDEM (16th
17th Feb, Brussels) ?
--
Keith Matthews
Frequentous Consultants - Linux Services,
Oracle development database administration
Hmm. Well, I gave the MS headers one more try and discovered
a few not so nice things.
If you have a Wine specific include like below in a file:
#include heap.h
and this file heap.h in turn has a
#include winbase.h
it will include the Wine version of the file instead of the
MS version.
Alexandre Julliard wrote:
David Laight [EMAIL PROTECTED] writes:
This is the standard behaviour for C includes. It is actually usually
best to use not for all header files - unless you explicitely want
the file included from the current directory.
The problem is our makedep uses
On Wed, 6 Feb 2002, Steven Edwards wrote:
There are very little changes needed for the ReactOS port and only one
or 2 ReactOS specific headers. ReactOS only has private headers for the
kernel. Everything else we use is either in the mingw win32api or wine.
Nice. In that case replace ReactOS
On Wed, 6 Feb 2002, James wrote:
I don't know about Sweden, but you definitely DON'T need a visa if you're a
UK citizen; there's a list of countries eligible for the visa waiver
program, under which you just sign a declaration that you are not a Nazi war
criminal, terrorist or drug
Speaking of conferences, is anyone planning on going to FOSDEM (16th
17th Feb, Brussels) ?
I'll go (easy, I live in Belgium :-).
Laurent Pinchart
On Wed, 6 Feb 2002, Eric Pouech wrote:
what still remains to be fixed is adding support for console handles
based on unix consoles (today, it's still a bit hacky), and implement
a (n)curse (or xterm as Marcus once did) back end for wineconsole
A+
I didn't mean to criticize the debugger.
I would like to know if/how it is possible to set a watchpoint from
inside, say, a Winelib program (without any UI involved until the
watchpoint trips), but don't waste a lot of your time on it if it's not.
normally yes. start your program from the debugger, then set your
watchpoint:
watch *
Folks,
Some recent events have occurred that have made me change my opinion
about a Wine license change.
During my involvement in the Wine project, I have always striven to
make sure that I, and my company, did what was best for the Wine
project. I believe Wine's success will help to make the
On Wed, Feb 06, 2002 at 04:54:05PM -0600, Jeremy White wrote:
Some recent events have occurred that have made me change my opinion
about a Wine license change.
...
However, with some recent events I cannot disclose, it is clear to me
that the opportunity for Wine to be used in a proprietary
Bonjour,
Je rencontre un problème persistant avec wineconsole.
Dès qu'il est chargé le système ralentit et wine
grandit en mémoire jusqu'à saturation de la mémoire
swap.(256M ram physique + 208M swap)
Le message fixme:bitmap:CreateCompatibleBitmap got
bad width 1939840 or height 2457900 me fait
On Wed, 6 Feb 2002, Joerg Mayer wrote:
OK, when the last discussion was going on, I started out with the opinion
that the change would be good and changed it to not so good, because if
proprietary stuff that *is* part of the windows kernel (or drivers) needs
to be implemented, this can't be
On Wed, Feb 06, 2002 at 07:51:04PM -0500, Dimitrie O. Paun wrote:
Yeah, that could work. But I still don't understand your objections about
the proprietary drivers: LGPL would work just fine with that. What's your
concern?
Look at the copy protection stuff that transgaming have added to their
Hello, I´m running a windows aplication made on Builder C, and when I execute
de program with Wine, I receive an error message, reference to the date format,
I get the year correctly, but the rest of date content is =0, for example
01 January 2002 at 13:20:15 is= 17/20/02 00:00:00
can you
Joerg wrote:
OK, when the last discussion was going on, I started out with the
opinion
that the change would be good and changed it to not so good, because
if
proprietary stuff that *is* part of the windows kernel (or drivers)
needs
to be implemented, this can't be done with an LGPLed wine.
Jeremy White wrote:
Specifically, they need clear examples of Windows APIs
that are not documented, or cases where the actual
working of an API is substantially different from the
documented behavior.
I know of a bunch of functions in the rpcrt4.dll. Most of them starting
with Ndrxxx. many
Hi Jeremy et al,
Well, for my 2c worth (or about 1c in US currency :)) I suspect most
people who don't look at the license would assume that Wine is xGPL
anyway, as so many Linux-type things are... so from a typical user's
point of view they'd probably not notice the difference. The occasional
Jeremy White wrote:
Should the Wine project switch to a license which has as
its goal to attempt to secure some form of Copyleft
protection for Wine while still permitting proprietary
software to link and bind with Wine?
Since I like the (L)GPL licenses, I have no problem
This little offtopic butWhat ever happend to
TWINE? Is there anything of TWIN left that would be
used moves to LGPL?
Steven
__
Do You Yahoo!?
Send FREE Valentine eCards with Yahoo! Greetings!
http://greetings.yahoo.com
Jeremy White wrote:
Folks,
Some recent events have occurred that have made me change my opinion
about a Wine license change.
However, with some recent events I cannot disclose, it is clear to me
that the opportunity for Wine to be used in a proprietary product is
too tempting and has
So lets get this straight, if no one wants to change to the LGPL you'll
fork the code? I don't have anything necessarily against the LGPL, but
your email sounds all wrong.
I dont see how there can be a problem here. The current license allows
anyone to do whatever they please with the code. You
Steven Edwards wrote:
So lets get this straight, if no one wants to change to the LGPL you'll
fork the code? I don't have anything necessarily against the LGPL, but
your email sounds all wrong.
I don?t see how there can be a problem here. The current license allows
anyone to do whatever
As someone with absolutely no connection to anyone at Codeweavers, I
think Codeweavers' actions over the past two years or so more than
sufficiently establishes the fact that they deserve to be given the
benefit of the doubt in regards to statements like these. You can
agree
or disagree with
On Wed, Feb 06, 2002 at 08:17:39PM -0800, Daniel Walker wrote:
I don't think anything in Jeremy's message suggested that conversation was
a requirement. He's looking for feedback to get an idea of how members of
the Wine community feel. But if you're open to being persuaded that the
Jeremy White wrote:
...
However, with some recent events I cannot disclose, it is clear to me
that the opportunity for Wine to be used in a proprietary product is
too tempting and has caused some harm to the Wine project. Based on
experience, I feel strongly that the potential for harm is
45 matches
Mail list logo
