Jeremy Newman wrote:
On Tue, 2003-03-25 at 22:02, Dimitrie O. Paun wrote:
On March 25, 2003 11:48 pm, Dan Kegel wrote:
It would be nice if the site recognized normal URLs without
the ?page= prefix. That ought to be easy to hack up.
The extra verbiage makes links posted in news articles
Sylvain Petreolle wrote:
It does, see the nice(1), renice (8) commands and get/setpriority(2).
would work. But Linux doesn't allow a non-root process to increase
its scheduling priority (and of course people shouldn't run Wine as
root), so it mostly seemed to just be an exercise in
Tony Lambregts wrote:
David Fraser wrote:
Tony Lambregts wrote:
Wine does not have these defined anywhere. Does anyone know what
they should be and where they should be defined?
Not sure about REG_FORCE_RESTORE, but MinGW has the following in winnt.h
#define REG_WHOLE_HIVE_VOLATILE 1
#define
Tony Lambregts wrote:
Following Dan's advice I thought I would try my hand at putting
together a regression test for RegSaveKey(A/W). Well I kind of run
into a snag with that, actualy a couple of them. The first is that the
counterpart for RegSaveKey is a stub. Oh well thats OK. I can still
Mike Hearn wrote:
I should spam the list less :)
http://msi2xml.sourceforge.net/
Easy way to write a Wine version of MSI? Hardly important at the moment,
but might be in future.
H ... I might be talking nonsense warning in advance:
I had a look at this a few months back, tried to port it
Serenity wrote:
Hi,
Right, I've been Googling this one up, and I've found some information, but
it's a few years old so I'm not sure if it's current...
Has anybody had any success compiling and executing Wine on Win32? I know,
it seems a bizzare concept, but I have legitament reasons to want to
Serenity wrote:
snip
You can compile it successfully on cygwin but not run it yet. If you're
really interested,
search the list archives and read them. If you have a specific question
or a goal, say what it is,
otherwise I'm not sure what to say...
Well, put short, my goal is to be able
I found a patch which I think was from them, and applied it to the cvs
to try it out, it compiled OK but failed on startup and I haven't
investigated it.
David
Mike Hearn wrote:
I don't think anybody has a fix yet. The work TransGaming contributed
was prototype code for using pthreads on
Jaco Greeff wrote:
On Saturday 22 February 2003 07:08 pm, Mike Hearn scribbled on a piece of
papyrus:
Last time I talked to Jaco, he was busy finding work. Hopefully he'll
resurface soon, maybe he has a nice surprise for us :).
Yeah, Jaco, are you there? :)
Alive and kicking. Way
Johan Gill wrote:
Mike Hearn wrote:
And I have it in my tree :) It should be ready for submission in a
few months from now.
Hvae you checked that it wouldn't be easier to merge in the TransGaming
implementation? It seems daft to duplicate work if that's the case...
It is their work, but
Mike Hearn wrote:
What stage is the implementation currently at? According to the
TransGaming docs, there are still a number of functions to fill in...
I would be interested in seeing a patch no matter how much/little is
implemented ... because my main aim in getting rid of the fault handler
David Hammerton wrote:
On Tue, 25 Feb 2003 01:49, David Fraser wrote:
snip
Seems to make sense except that I still have one question: the MSDN docs
seem to indicate that you need to call GDIFlush() before performing any
drawing operations to the bitmap yourself (at least for Windows NT).
Would
Dan Kegel wrote:
Dimitrie O. Paun wrote:
On February 24, 2003 12:46 am, Dan Kegel wrote:
So I wonder if Wine shouldn't be mean, and not try
so hard to understand Unix paths.
What about reversing the order: first try the DOS
path, if that fails, try the Unix one...
Hmm, that's a good idea.
Hi
I was wanting to do some work on x11drv dll separation.
The last remaining dll separation between x11drv and ntdll is
VIRTUAL_SetFaultHandler.
This is called from X11DRV_DIB_CreateDIBSection, where it tries to set
the fault handler to X11DRV_DIB_FaultHandler, with addr=dm.dmBits and
Dan Kegel wrote:
I wrote a humble beginning of a conformance test for
named pipes, in hopes of preventing regressions like the one which
is currently breaking Installshield installs (or was last I checked).
Later it's going to verify that named pipes like
the ones Wine uses internally (e.g. in
Dan Kegel wrote:
A couple questions:
1. Is anyone working on NamedPipe conformance tests?
If not, I'd be happy to try. (Might be a challenge
to scare up a Server version of Windows, so initially
I'd just write the tests on Wine, and make sure they
compiled with winelib and with vc++.)
2.
Dan Kegel wrote:
David Fraser wrote:
Dan Kegel wrote:
However, it's not clear to me that's required
for developing winethreads-over-pthreads. People
could probably get started on that with their
current Linux, even though it's not 100% posix-compliant,
and has odd quirks like using
Dan Kegel wrote:
However, it's not clear to me that's required
for developing winethreads-over-pthreads. People
could probably get started on that with their
current Linux, even though it's not 100% posix-compliant,
and has odd quirks like using a special management thread, etc.
Exactly.
David Fraser wrote:
Dimitrie O. Paun wrote:
On February 1, 2003 02:10 am, David Fraser wrote:
Could we go straight down to the underlying win32 api and do a
GetThreadContext there? Is that cheating?
I don't know the Cygwin threading model, but calling the real
[GS]etThreadContext
Dimitrie O. Paun wrote:
On February 5, 2003 03:36 am, David Fraser wrote:
Under cygwin, there is no clone call as far as I can make out ... there is
pthreads support and there is hackish support for fork.
Do threads in Cygwin's pthreads map one-to-one to Windows threads?
Just looked
Dimitrie O. Paun wrote:
On February 1, 2003 02:10 am, David Fraser wrote:
Could we go straight down to the underlying win32 api and do a
GetThreadContext there? Is that cheating?
I don't know the Cygwin threading model, but calling the real
[GS]etThreadContext is a good first order
Steven Edwards wrote:
well I made it serial.c before I had to run to work. I'm having good luck getting alot of the
objects to compile so far I've only had to kill file.c, ptrace.c, request.c and select.c. Getting
this to build and run on Windows is going to be a bitch =) gettimeofday, fork and
Francois Gouget wrote:
On Tue, 7 Jan 2003, Dimitrie O. Paun wrote:
On January 7, 2003 02:25 pm, Francois Gouget wrote:
* winemaker
The assumption is that you have a Windows application (complete with
CR/LF), most likely based on Visual C++ and thus with no suitable
makefiles. So
Steven Edwards wrote:
I will be lending those guys a hand with the port. Mostly the
work seems to be done, they just need a gentle nudge to get it
in the tree (I hope :)).
As always, your comments and suggestions are highly appreciated.
when/if I ever get more time I will try to help. I
Dimitrie O. Paun wrote:
On January 2, 2003 12:30 pm, Alexandre Julliard wrote:
It doesn't really matter, just pick the one you prefer.
I know, but I was hoping people had better suggestions :)
I like __WINESRC__ the best (but that doesn't mean much g),
so unless people have a better
Dimitrie O. Paun wrote:
Hi folks,
For those of you who follow my Winelib quest, one of the most
ambitious projects is compiling Mozilla under Wine. Needless
to say, this would be quite something to accomplish, and would
provide Wine with a formidable test for it's headers, and it's
tools
Dimitrie O. Paun wrote:
Folks,
Last night I managed to compile, link, and successfully run
all(1) samples that come with wxWindows.
In all honesty I am overjoyed! Let me explain why:
Excellent news!
-- wxWindows is a large piece of software that touches on
most (if not all) Wine
Dimitrie O. Paun wrote:
On December 19, 2002 09:26 am, Waldek Hebisch wrote:
If we are going to seriously support mingw then we need mingw headers.
I am not sure if true mingw headres are different enuugh from normal
wine and msvcrt headers to warrant extra subdirectory, but logically
they
Francois Gouget wrote:
On Wed, 18 Dec 2002, Dimitrie O. Paun wrote:
On December 18, 2002 03:36 pm, Francois Gouget wrote:
[...]
winegcc
Why not wgcc?
I had the impression that we were going away from just using 'w' as the
prefix and more towards using 'wine'. So I'm
Uwe Bonnes wrote:
It's not wine that needs msiexec, it's some application with it's
installer. So this application has to care for msiexec.
If things change and msiexec get's part of the ms core distribution, we can
reconsider...
Bye
Actually it is included with Windows 2000, XP and Me etc:
Hi
Just ran the same tests, reported results where different.
Maybe this will help debugging...
David
Kye Lewis wrote:
advapi32_test
registry: 56 tests executed, 0 marked as todo, 0 failures.
kernel32_test
alloc: 58 tests executed, 0 marked as todo, 0 failures.
atom:
Shachar Shemesh wrote:
Benchmark will follow soon. In the mean time, think about the fact
that, compared to linear copying of the strings in, these are the
overheads (neglecting function call overhead, which is not neglectible
but is fair):
n - number of strings in the final string
m(i) -
Hi all
This is a brief indicator on what parts of wine compile successfully
under cygwin and what give errors. Almost all the source code compiles
successfully, but lots of things have linking problems. Note that I
haven't yet tested the resulting parts that did link successfully.
The
Martin Wilck wrote:
Am Don, 2002-11-28 um 07.35 schrieb Dimitrie O. Paun:
-CC=gcc
+CC=wcc
-RC=windres
+RC=wrc
I can't follow you here. You seem to have been porting Applications
using Unix-Style Makefiles. I'd guess the vast majority of Applications
comes with Windows VC++ project
David Fraser wrote:
The significant compilation problem is in server/context_i386.c: You
must implement get/set_thread_context for your platform.
Basically there's some code that does the threading stuff which is
platform-specific. There are Linux and BSD and Sun variants, none of
which work
Dimitrie O. Paun wrote:
On November 28, 2002 09:51 am, David Fraser wrote:
So part of the question is, in order to get Wine to function properly on
Cygwin, what is the right
threading approach to take? Am I right in thinking that the current code
wouldn't work on Cygwin?
I say, let's
Brian Vincent wrote:
First, take a look at:
http://www.theshell.com/~vinn/ss
Quite a few folks have sent stuff in. Now, after looking at so
many screenshots and trying to evaluate them for content I've
realized a few things..
1) We're absolutely going to have to insist on 800x600 resolution.
Greg Turner wrote:
On Tuesday 19 November 2002 07:18 pm, Sylvain Petreolle wrote:
Cygwin bash currently fails to execute due to OpenProcessToken.
Looking in source, I see that advapi32.OpenProcessToken calls
ntdll.NtOpenProcessToken.
This functions is a stub that returns always false today.
Dimitrie O. Paun wrote:
On November 19, 2002 09:46 am, Dimitrie O. Paun wrote:
[dimi@dimi wine]$ gcc -nostdinc -fshort-wchar -I /home/dimi/dev/wine/wine.src/include/msvcrt -I /home/dimi/dev/wine/wine.src/include test.c
Hm, maybe we need the standard headers after all.
Even though this
Martin Wilck wrote:
I am thinking about some netapi32 improvements where I'd need to call
the functions of the getpw/getgr family: getpwnam(), getpwent(),
getgrent(), etc.
Configure checks for the pwd.h header and getpwuid(). Must I add more
checks for all the functions I use, or is it ok to
Dimitrie O. Paun wrote:
Hehe,
It's hard to keep these things 'secret' :)))
http://developers.slashdot.org/developers/02/11/17/1648220.shtml?tid=125
Yup, a nice surprise to see that this morning. Hope your site's
surviving :-)
Seeing as we're getting such coverage, maybe you should move
Fredrick P. Lackey wrote:
Where I am at the moment is a crossroads. I own a company focused on
rapid development on a Microsoft platform (essentially, we build
components to simplify complex tasks for developers working on a M$
system). Unfortunately, I'm getting pretty sick of the OS and M$
Dimitrie O. Paun wrote:
I had to use the following hack to allow this
bit to go through my g++ compiler.
I'm using RedHat 8.0, so this gives me:
[dimi@dimi wine.src]$ g++ --version
g++ (GCC) 3.2 20020903 (Red Hat Linux 8.0 3.2-7)
Copyright (C) 2002 Free Software Foundation, Inc.
This is free
Michael Riedel wrote:
Hello,
is it possible to use wine in a telnet session to start a (command
line) windows application? I get the error that x11drv can't connect
to a display (which is correct). I'm also not very sure that the
windows program itself does not perform some graphic related
Dimitrie O. Paun wrote:
Folks,
The second release (much expanded) of the Fun Project
page has been released, in all it's glory, at:
http://www.dssd.ca/wine/Wine-Fun-0.2.html
The working version of the above is at:
http://www.dssd.ca/wine/Wine-Fun.html
By now, you should know that comments,
Dustin Navea wrote:
- Original Message -
From: David Fraser [EMAIL PROTECTED]
To: Michael Riedel [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Friday, November 15, 2002 7:30 AM
Subject: Re: Wine without any X11 environment
Michael Riedel wrote:
Hello,
is it possible to use
Greg Turner wrote:
Doesn't work between Linux and a Windows machine
(Linuz client sends
messages locally, client on Windows machine returns exception)
Not sure if this is what you've encountered, but there is a shortcoming
of the current implementation: the client-side API's report
Greg Turner wrote:
This patch doesn't implement the resolve_rpc_endpoint server message
yet, although my final (ya right) submission will include an untested
implementation (I don't think the interop sample uses this API (or does
it?) and that's the only known working test case right now).
Sylvain Petreolle wrote:
--- Dimitrie O. Paun [EMAIL PROTECTED] a écrit : On November 9,
2002 09:28 am, Sylvain Petreolle wrote:
Using the cygwin under is difficult for the moment, as bash and sh
both refuse to run today.
What's the problem with them?
--
Dimi.
They die when
Sylvain Petreolle wrote:
This is what I did.
the gcc included in dev-c++ is a statically linked that doesn't need
the cygwin1.dll to run.
But that I looked particularily at compiling cygwin under wine.
Using the cygwin under is difficult for the moment, as bash and sh
both refuse to run today.
Dimitrie O. Paun wrote:
Folks,
It's Friday, I'm out of my meetings, weather is superb here
in Toronto (so I'm gonna go for a ride on my bike); this
calls for some lighter, more entertaining stuff.
So, if someone feels like doing something fun, here is a list of
interesting Wine-related
Dimitrie O. Paun wrote:
On October 31, 2002 06:02 pm, Alexandre Julliard wrote:
Dimitrie O. Paun [EMAIL PROTECTED] writes:
What is NOT in 0.8:
-- stable server protocol: no binary compatibility
-- DLL separation: ditto
IMO the goals for 0.9 will be reached before the ones for
Hi
Have had trouble getting through to [EMAIL PROTECTED], so reposting
this to see...
Funny, nothing's bounced...
David
Original Message
Subject: x11drv WND separation
Date: Mon, 04 Nov 2002 15:27:27 +0200
From: David Fraser [EMAIL PROTECTED]
To: [EMAIL PROTECTED], [EMAIL
Geoff Thorpe wrote:
On Thursday 31 Oct 2002 10:00 am, Greg Turner wrote:
On Thursday 31 October 2002 08:10 am, Raul Dias wrote:
My $0.02,
A way to make it more secure is to catch key API calls and decide if
the application is allowed to run it or not.
not a bad idea.
Wine
if this configure is autogenerated or if this patch is
applicable, but
thought others trying the same thing might find this helpful...
David Fraser
Steven Edwards wrote:
David Fraser wrote:
I've been trying to build ntdll and various other dlls (I'm actually
interested in gdi
and x11drv) for cygwin as well.
I tried building ntdll with the latest CVS which includes Alexandre's
patch from below.
However I still get lots of errors
lots
of the code doing
something someone else has done? Or am I missing the point?
David Fraser
Alexandre Julliard wrote:
Steven Edwards [EMAIL PROTECTED] writes:
we get much futher now when building ntdll on cygwin. when linking I
am getting the following error
ntdll.exp(.edata+0xe4c):fake
I have been trying to compile the wine gdi dll under cygwin. I am using
the 20020804 snapshot
This is part of an attempt to get native Windows applications to display
themselves
in cygwin's X Windows.
I have seen several posts from Steven Edwards and others about compiling
wine under cygwin
So
58 matches
Mail list logo
