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
On Friday 18 November 2005 02:05, Juan Lang wrote:
Someone proposed a hack where the loader would know that these DLLs are
dummies based on a wine-specific flag in the header.
Why a dummy? Why not ship a full PE DLL with a flag saying it's a built-in?
That way file existence checks, PE header
On Thu, 17 Nov 2005 23:56:40 +0100, Peter Beutner [EMAIL PROTECTED]
wrote:
Hi
There is yet another issue preventing SeriousSam from working.
It fails to load opengl32.dll because before loading the dll it makes
sure it can find it
via SearchPath().The problem is that SearchPath doesn't
Title: wine command is not working in crontab
Hi all,
I'm not able to use wine command in crontab it giving following error
Error opening terminal: unknown
I'm using wine 0.9, i have added following command in crontab
20 10 * * * /home/Maven/test.sh
In the test.sh file has the
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
On Thu, 2005-11-17 at 17:05 -0800, Juan Lang wrote:
2) place dummy files for all builtin dlls in c:\windows\system32
I believe this is the correct approach. I know of at least one
InstallShield installer (that uses MSI) that searches for IE by looking
for the file shdocvw.dll and checking
Is it possible, via Wine, to link against a Windows DLL in a C++ program compiled under Linux? My specific situation: I would like to interface a piece of hardware over a serial port. The manufacturer
refuses to provide a serial comms specification for the device because it's proprietary, but
Hi Charles,
OK, so what I suspect is happening is crontab has no DISPLAY variable set, so
wine is defaulting to using the ttydriver. Unfortunately, crontab
environment isn't attached to any tty, so that fails too with the error
message you see.
What you really want is the nulldriver (which I
Am Freitag, den 18.11.2005, 02:51 +0200 schrieb Saulius Krasuckas:
strange enough is the fact, that some win98s don't crash. [2] maybe that
are those which runs under Qemu emulator? (w98.ie50.dx61 and w98.ie6.dx81)
qemu is correct.
--
By By ...
... Detlef
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,
Jim Morash wrote:
Is it possible, via Wine, to link against a Windows DLL in a C++
program compiled under Linux? My specific situation: I would like to
interface a piece of hardware over a serial port. The manufacturer
refuses to provide a serial comms specification for the device because
it's
Hi Jim,
You might actually do best turning the problem upside down.
That is, it's quite easy to write a .exe or winelib
application that links to a Windows DLL and connects
to a Linux binary or library.
It's hard to call Wine as a library, because Wine has
to have quite a lot initialized
Paul Millar [EMAIL PROTECTED] writes:
What you really want is the nulldriver (which I think Alexandre mentioned
once
a while back) but that doesn't exist yet.
It very much exists. Running without a display should work just fine
with 0.9.1.
--
Alexandre Julliard
[EMAIL PROTECTED]
Just wondering, I'm going through all of the different apps that I have
to see what sorts of problems I am running into, and in several of them,
the programs run fine, but there are some graphic glitches (nothing
major).. Should I report those here, to bugzilla, or both? They all
see to be
Hans Leidekker schrieb:
On Friday 18 November 2005 02:05, Juan Lang wrote:
Someone proposed a hack where the loader would know that these DLLs are
dummies based on a wine-specific flag in the header.
Why a dummy? Why not ship a full PE DLL with a flag saying it's a built-in?
That way file
16 matches
Mail list logo
