--- Francois Gouget <[EMAIL PROTECTED]> wrote:
>Yes and no. They need a C library (badly).
>Frankly I've never used 'crtdll.dll' and don't
> know it very well. All
> I know is that it seems very similar to a C library
> except I'm not sure
> who is supposed to use it. All the windows progr
> However doing so it looks like:
>
>
> 0x405cdf46 (CreateWindowExA+0x46 [win.c:1118])
> 1118 FIXME("BON:Setting up SysHeader32\n");
> Wine-dbg>bt
> Backtrace:
> =>0 0x405cdf46 (CreateWindowExA+0x46(exStyle=0x0, className=0x5f4a5444,
>windowName=0x0, style=0x4042, x=0x5f403903, y=
robert w hall <[EMAIL PROTECTED]> writes:
> well the mods are in include/asm/segment.h I think
>
> and the double whammy is that people loading stock win4lin kernels DON'T
> get that updated . So even if they build WINE from source (but not their
> kernel) they're scuppered.
No, Wine gets the v
In message <[EMAIL PROTECTED]>, David Elliott
<[EMAIL PROTECTED]> writes
>Jeremy White wrote:
>Ah, so that explains why I haven't seen this problem then, because I always
>build from source.
likewise
> Hmm, come to think of it, that'd make it kind of hard
>for me to make a wine package usable by
Forwarding this to Wine-devel since I originally sent it to wine-patches
because I just hit "Reply-All" and didn't bother to check.
I agree with Francois, I really shouldn't get up before like 5 or so, 4 is
too early ;-) (pm that is)
-Dave
Francois Gouget wrote:
> David Elliott wrote:
> >
>
Jeremy White wrote:
> Actually, it's a fascinating problem - I've been bit by it, badly.
>
> Wine works fine with a Win4lin kernel, so long as you build
> it from source. If you try to take a binary built on a non
> Win4lin kernel, you get an unhandled exception when your
> app starts to run, wi
Hello.
For quite some time I've been having problems attaching winedbg to a running
process, for instance in the case of automatic invokation due to a crash.
Direct invokation causes no problems and I also believe that my registry
entries are all ok. My kernel is a standard 2.0.34 which otherwis
Damn, I sent it to the wrong list! I shouldn't get up so early!
David Elliott wrote:
>
> Francois Gouget wrote:
>
> >Hi,
> >
> > David Elliott wrote:
> > [...]
> > > Are Winelib programs also supposed to use the wine CRTDLL?
> >
> >Yes and no. They need a C library (badly).
> >
Hallo,
I am trying to debug some missfunction in a programm (avrstudio.exe)
that uses MFC. The missfunction are senseless top/left/width/height
values to CreateWindowExA and that CreateWindowExA is called from the
MFC library. As VC++ comes with PDB files and source for the MFC
library, I though
Actually, it's a fascinating problem - I've been bit by it, badly.
Wine works fine with a Win4lin kernel, so long as you build
it from source. If you try to take a binary built on a non
Win4lin kernel, you get an unhandled exception when your
app starts to run, with a problem in the ThunkConnect
robert w hall <[EMAIL PROTECTED]> writes:
> I keep seeing occasional reports that 'wine does not run... on a
> win4lin-enabled kernel'. Though this is contrary to my experience and
> sounds like finger-trouble, I wonder if anyone has any better/hard
> info?.
I think the problem is that they chan
[EMAIL PROTECTED] writes:
> Good day!
>
> I am trying to make a winelib rundll32, but I can not get GetProcAddress
> to return anything but (nil). I must be doing something even stupider
> than the stupid errors I have already fixed, but I can't see it. Maybe
Hallo,
in my understanding, winel
Francois Gouget wrote:
>Hi,
>
> David Elliott wrote:
> [...]
> > Are Winelib programs also supposed to use the wine CRTDLL?
>
>Yes and no. They need a C library (badly).
>Frankly I've never used 'crtdll.dll' and don't know it very well. All
> I know is that it seems very similar to a
I keep seeing occasional reports that 'wine does not run... on a
win4lin-enabled kernel'. Though this is contrary to my experience and
sounds like finger-trouble, I wonder if anyone has any better/hard
info?.
The one possibility for serious interaction would appear to be the
dosmod/vm86 area? (wh
In message <[EMAIL PROTECTED]>, Andreas Mohr
<[EMAIL PROTECTED]> writes
>If you're an end-user, you might want to stick with normal releases.
Why?
>But even for end-users CVS is not too bad ;)
>
>Andreas Mohr
I thought Alexandre's present policy was that there was no real
difference between a dat
Hi,
David Elliott wrote:
[...]
> Are Winelib programs also supposed to use the wine CRTDLL?
Yes and no. They need a C library (badly).
Frankly I've never used 'crtdll.dll' and don't know it very well. All
I know is that it seems very similar to a C library except I'm not sure
who is s
16 matches
Mail list logo
