On Wed, 3 Mar 2004 16:20, Alexandre Julliard wrote:
> Actually we don't run on the main stack, so allocating the space above
> 0x8000 would definitely be possible, the stack doesn't need to
> grow there.
In that case I could move the changes to start_process and incorporate the
address space
Troy Rollo <[EMAIL PROTECTED]> writes:
> + * The problem with emulating this is that on Linux the top of the stack is at
> + * 0xbfff and below, so reserving even the balance of this range would
> + * artificially limit stack growth. We could move the stack, but it's too late
> +
[EMAIL PROTECTED] writes:
> Alexandre, is there any reason that this patch isn't applied?
Well, it has a lot of suspicious sizeof() calls on W buffers, and I
haven't yet found the time to go through every one of them to make
sure they are correct.
--
Alexandre Julliard
[EMAIL PROTECTED]
Alexandre, is there any reason that this patch isn't applied?
http://www.winehq.org/hypermail/wine-patches/2004/02/0332.html
--
Tony Lambregts
Hi,
I have noticed that when you load up Warcraft III, and then quit the game, that
it will pop up with a messagebox error message complaining about a memory
location, 0xdeadbeef. I have also noticed this message:
err:win32:PE_fixup_imports No implementation for
imm32.dll.2(ImmAssociateContextE
What is the plan for combining these audio drivers? One thing that is common to each
driver are the functions that handle the wave headers, adding, removing etc.
I'm also weary of any kind of combination that includes OSS as OSS is depreciated and
has been replaced by Alsa.
I'm also concerned
On Tue, 2 Mar 2004, Dimitrie O. Paun wrote:
> On Tue, 2 Mar 2004, Francois Gouget wrote:
[...]
> >We must specify '-lmsvcrt' if using the msvcrt.
>
> Please don't, it's not needed. If you want to use msvcrt, please
> pass the -mno-cygwin switch. if that doesn' work, it's a bug
> in winegcc.
A
Dan Kegel <[EMAIL PROTECTED]> writes:
> Running Office was another matter. I only tested it a bit, but
> there's a display problem: text is displayed invisible
> in the main document pane on the same line you're editing.
> If you refresh, everything's there.
> Not terribly usable.
That's a bug t
James Gregory a écrit :
On Thu, 2004-02-26 at 08:59, Alexandre Julliard wrote:
Robert Reif <[EMAIL PROTECTED]> writes:
I think it might be worthwhile considering restructuring the audio
drivers into hardware independent wave, direct sound, midi
and mixer sections and a hardware dependent low
Alexandre Julliard a écrit :
Yorick Hardy <[EMAIL PROTECTED]> writes:
The idea is that eventually winenbsd and wineoss only have the drv.h
and the spec file. drv.h will define all driver specific names/functions.
I must stress that I am only concerned with the OSS and NetBSD drivers
at the moment
Hans Leidekker <[EMAIL PROTECTED]> writes:
> Would it be an idea to rename vxd directories like ifsmgr.vxd
> to ifsmgr? Or do you foresee conflicts? After all, .acm, .ocx
> and .drv exist besides .dll without the subdirectories bearing
> a corresponding suffix.
There will be conflicts, yes. And
Yorick Hardy <[EMAIL PROTECTED]> writes:
> The idea is that eventually winenbsd and wineoss only have the drv.h
> and the spec file. drv.h will define all driver specific names/functions.
> I must stress that I am only concerned with the OSS and NetBSD drivers
> at the moment.
Any such solution n
"Dimitrie O. Paun" <[EMAIL PROTECTED]> writes:
>> 6. winegcc is not rebuilt if the '--prefix' changes.
>
> Maybe AJ can fix the Makefile. I think winegcc.o should depend on
> the Makefile.
Nothing gets rebuilt if the prefix changes, you have to do a make
clean.
--
Alexandre Julliard
[EMAIL PROT
I started now with the integration of the OSS and NetBSD audio drivers.
Before I get too far, I would like to hear suggestions/criticisms.
1) I created the directory dlls/winmm/drvcommon
(perhaps there is a better name ?)
2) moved dlls/winmm/wineoss/oss.c and dlls/winmm/winenbsd/nbsd.c
to th
On Tue, 2 Mar 2004, Francois Gouget wrote:
> winemaker is pretty broken since it has been patched to call winegcc. I
> suspect it was not tested.
Hey, I can't do everything! :))) I just wanted to get the ball rolling.
>We must specify '-lmsvcrt' if using the msvcrt.
Please don't, it's not
On March 2, 2004 2:19 am, Kirill Smelkov wrote:
> I think that from this point of view it is desirable to add the options to
> generated Makefiles, or at least do some checking for them
> (this was done originally).
Yes. I just wanted to know where is the proper place for them.
If MinGW have them
> ifsmgr.vxd$(DLLEXT): ifsmgr.vxd/ifsmgr.vxd$(DLLEXT)
>$(RM) $@ && $(LN_S) ifsmgr.vxd/ifsmgr.vxd$(DLLEXT) $@
>
> because, if $(DLLEXT) is empty, it will try to create a link
> with a name that's already there as a directory.
Would it be an idea to rename vxd directories like ifsmgr.vxd
to if
On Monday 01 March 2004 18:55, Juan Lang wrote:
> > additionally
> > link to ws2_32 it builds on MinGW as well as Wine.
>
> You have to link to ws2_32? That's interesting, I
> didn't. I submitted a patch, minus that bit.
Yes you need to, I have tested this. You don't need it on
Wine because t
Dan Kegel wrote:
Sigh. I guess I'll dig up the copy of Crossover I bought for testing
a while ago. Wonder if that even works with such an old Linux, though...
- Dan
Once you run Crossover and create a dir REG and other stuff, you can
than use that fake_windows with your up-to-date wine.
Just
19 matches
Mail list logo
