On Thu, 2 Mar 2000 03:11:43 +0100 (CET), you wrote:
On Wed, 1 Mar 2000, Ian Schmidt wrote:
Whatever happened to the much more complete trackbar fix from the Odin
project? I tried the patch at the time it was posted and it made trackbars
*perfect*, but apparently there was some
On Thu, 2 Mar 2000, Andreas Mohr wrote:
So you mean setting it in a config script ?
Yes, that is possible, but I don't know whether we want to do so.
The problem is that in Wine, you have a well-defined and fixed API to
access the registry to set up any initial values needed.
You can always use
Well, if you really need a setup program, we can always write a
programs/winesetup program. So there is no need for a -init switch. Just run
winesetup -- it will have access to all Windows API. But for this particular
function GetComputerName, we can always code it like this:
val = get val from
Hi all,
just another case of completely mad wndproc management, I guess.
LabView 4.01 16 bit does this:
Call GDI.70: ENUMFONTS(0x0e8c,0x #,0x026f32aa,0x0001) ret=026f:09c5
ds=0277
CallTo16(func=026f:32aa,ds=0277,0x009f,0x05dc,0x009f,0x058c,0x0001,0x,0x0001)
ss:sp=0277:4938
Hi,
I just compiled the last two releases and I'm getting a
compile failure in server/context_i386.c relating to the
use of PTRACE_PEEKUSER and PTRACE_POKEUSER for ptrace calls.
Looking in my system (libc5) I have PTRACE_PEEKUSR and
PTRACE_POKEUSR (note the lack of E in USR). This seems to
