On Thu, 8 Jun 2000, Andreas Mohr wrote:
Hi,
as there are already going on some prolonged discussions about this matter,
what about WINSPOOL.DeviceCapabilities(/A/W) ?
I guess it's the same here...
(an app I have needs DeviceCapabilities)
Reminded that this was not answered to
On Fri, 16 Jun 2000, Uwe Bonnes wrote:
Hallo,
running with --synchronous should give you a backtrace now.
The backtrace might be helpfull.
Bye
Uwe Bonnes[EMAIL PROTECTED]
Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt
- Tel. 06151 162516
During `make install` with BSD make (instead of GNU make) I get the
following error:
cd `dirname tools/__install__` make install
cd `dirname cvdump/__install__` make install
make: don't know how to make install. Stop
*** Error code 2
What's the correct fix here?
a) Remove cvdump
This weekend I will be updating the HOWTO-winelib documentation. This week is
DLL week and it seems we need this documentation yesterday.
Lumin Software's local Windows guru has written a small sample program with a
DLL. I plan to add this to the wine project on Monday. I will show the original
On Thu, Jun 15, 2000 at 11:56:14PM -0700, Francois Gouget wrote:
On Thu, 8 Jun 2000, Andreas Mohr wrote:
what about WINSPOOL.DeviceCapabilities(/A/W) ?
Yes. I think it's the same thing except that:
* DeviceCapabilities is correctly declared in winspool.h
* DeviceCapabilities is
Hi,
Here's what I normally do when approaching problem at the X level (X error
...)
First, this message is caused by a wrong call made to X API or a bug in X.
In both cases you should start looking for which X call is causing the
problem. All calls to X are in one directory: tsx11/*.c. Adding
On Fri, 16 Jun 2000, Stephane Lussier wrote:
Hi,
Here's what I normally do when approaching problem at the X level (X
error
...)
Thanks. Every little bit helps.
Lawson
---cut here
YOU'RE PAYING TOO MUCH FOR THE
Unfortunately it also locks up on a release build with no debugging information (apart
from wine). Maybe I'll just have to debug the
debugger...
Dave Hawkes
- Original Message -
From: "James Hatheway" [EMAIL PROTECTED]
To: "Dave Hawkes" [EMAIL PROTECTED]
Cc: "WineHQ Devel" [EMAIL
As discussed earlier, it's a problem when users (or rpms) install their
.so files into a directory like /usr/lib/wine that's not in their
ld.so.conf files, only in the EXTRA_LD_LIBRARY_PATH option, because of
those ELF loader dependencies.
Elfdlls should solve it once and for all eventually, but
On Fri, 16 Jun 2000, Uwe Bonnes wrote:
Hallo,
running with --synchronous should give you a backtrace now.
The backtrace might be helpfull.
Bye
Uwe Bonnes[EMAIL PROTECTED]
Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt
- Tel. 06151 162516
On Fri, 16 Jun 2000, FT Rathore wrote:
Hi
Sorry if I sound stupid and it has been announced in WWN. I am tring to
get opengl32 tested with utah-glx and had problems with Heretic 2, now
I
am trying to test with Half-Life. It requires extra args to be passed
to
windows to disable splash and
Hi.
I think I might have ran into an bug in the way Wine
imports/handles Windows registry keys.
When I installed Windows (before I installed Linux
or even knew about Linux) I didn't specify a
user/password combo. As I understand it this results
in all users being 'the same' and all reg
12 matches
Mail list logo