On Sat, May 29, 2004 at 09:22:02AM +0200, Ferenc Wagner wrote:
> What's missing, what should be easier?
Now that you're asking: in the reports, I don't quite like
that a single report for Win95 is listed as OSR2 in the
main summary, but then it switches to Win95(n) when we have
more than one. Simi
Jon Griffiths <[EMAIL PROTECTED]> writes:
> @@ -2557,8 +2562,10 @@
> infoPtr->items[iItem].iImage = pti->iImage;
>
>if (pti->mask & TCIF_PARAM)
> -infoPtr->items[iItem].lParam = pti->lParam;
> -
> +memcpy(&infoPtr->items[iItem].lParam, &pti->lParam, infoPtr->cbInfo);
> + else
>
On Tue, Jun 01, 2004 at 08:40:09AM +0530, Rajeev Bansal wrote:
> thanks for reply
>
> i used wineg++ also but result was the same as wineg++ is link to winegcc
> lrwxrwxrwx1 root root7 May 25 17:34 wineg++ -> winegcc
Can you please come up with a short test case?
--
Dimi.
Eric Pouech wrote:
Shachar Shemesh a écrit :
While I agree in principle, in practice symbol lookups *appear* to
work when winedbg is invoking the application directly.
silly me. when run with gdb, the PE symbol lookup doesn't work, gdb
doesn't know anything about PE. You need to use winedbg witho
Shachar Shemesh a écrit :
Eric Pouech wrote:
While I'm doing ok at working like that, the client really prefers
working with a GUI. When I try to run the program using the --gdb
switch (with or without --no-start), debug symbols for the PE part
are not shown. I get all the symbols for the ELF dl
Rajeev
On June 1, 2004 09:39 pm, Rajeev Bansal wrote:
> Hi
> Dimi,
> I was trying to understand why any wine shared dll (like msvcrt.dll.so)
> crashed at the _fini call. This does not happen if I use my own created
> shared libraries. I was seeking help to find out why the crash occurs only
> with
Eric Pouech wrote:
While I'm doing ok at working like that, the client really prefers
working with a GUI. When I try to run the program using the --gdb
switch (with or without --no-start), debug symbols for the PE part
are not shown. I get all the symbols for the ELF dlls (wine's DLLs),
but not
On Wed, 02 Jun 2004 15:36:56 -0400, Paul R Streitman wrote:
> That was the problem! In Mandrake you need a separate static devel
> package. Its curious that I was able to compile kernels, x.org, older
> levels of wine, etc. without it...
Static libc is only used rarely. We use it in Wine because
I have an odd focus problem to report. This problem is a regression, some
time since 4/26 (which does not exhibit the problem). I have not had time
to pull interative CVS levels to find out exactly when it appeared, but it
was definitely failing last week (at first, I thought that it might be
That was the problem! In Mandrake you need a separate static devel
package. Its curious that I was able to compile kernels, x.org, older
levels of wine, etc. without it...
I am appending from Notes 6.5.1 running under today's CVS. I have another
problem, but I will report that separately.
Ewert, Mark a écrit :
Hi All,
I have a simulation tool that runs under windows NT/2K directly from the
DOS command shell. When running it on a Windows machine I get 200
cycle/s. When running it on Linux via Wine I get ~10 cycle/s. I didn't
realize Wine would have such a negative performance impa
Second problem is probably independant.
it is
> I figured that going through the
process of getting the program compiled as winelib was unnecessary, so I
am still compiling it on Windows using Visual Studio. This, naturally,
means that it's a PE. After resolving the font problems, I can finally
On Wed, 02 Jun 2004 12:28:46 -0400, Paul R Streitman wrote:
> This is on Mandrake cooker, gcc 3.3.2.
Do you have the static libc installed? It's called libc.a and should be a
part of the developer packages.
thanks -mike
On Wed, 02 Jun 2004 14:19:07 +0200, Rein Klazes wrote:
> Mike's solution seems certain to work. Disadvantage is that it may break
> another program (that /needs/ the presence of this stub).
That's unlikely at this point. The activation context APIs are
XP/Server2003 only, very very few apps (if a
"Dimitrie O. Paun" <[EMAIL PROTECTED]> writes:
>> When compiling with STLPort I saw a method that can eliminate the need
>> for the MSVCRT macro and yet produce MSVCRT_xxx for those who need it
>> and an xxx for those how don't.
>> Basically you have your Regular cleanroom headers-set for wine
On Wed, 02 Jun 2004 20:15:30 +0300, Shachar Shemesh wrote:
> 3. Any way to force wine to start wine-kthread?
I suppose you need to figure out why you're getting such wierd symptoms,
starting the wrong wine-[pk]thread version will cause even wierder stuff
(like libc not being thread safe). The NPTL
On Wed, Jun 02, 2004 at 02:07:16PM +0200, Ahmed Abdel Aal wrote:
> Hi,
> I installed new version of wine -20040505 but when I tried
> to use winemaker to gnerate configuration file.
> it is not generated and generate Makefile direct.
> is it and error in winemaker or updates in new version.
>
Shachar Shemesh <[EMAIL PROTECTED]> writes:
> Three questions, then:
> 1. Any idea why it starts the wrong executeable?
It doesn't, you do that when you start wine-kthread directly on a
platform that requires wine-pthread.
> 2. Is using wine-pthread when LD_ASSUME_KERNEL=2.4.1 considered "the
>
Alexandre Julliard wrote:
Shachar Shemesh <[EMAIL PROTECTED]> writes:
So, the question <---
Will running wine-kthread directly work? Or is there something crucial
done by the "wine" executable?
These days it launches the preloader too, so you probably shouldn't
bypass that. But
Shachar Shemesh <[EMAIL PROTECTED]> writes:
> So, the question <---
>
> Will running wine-kthread directly work? Or is there something crucial
> done by the "wine" executable?
These days it launches the preloader too, so you probably shouldn't
bypass that. But in any case it's unlikel
Luca Capello <[EMAIL PROTECTED]> writes:
> So, it seems that there's only Mike's solution, if someone has no other
> ideas...
If simply returning an error doesn't work, you need to improve the
stub to provide enough functionality for the app to be happy.
--
Alexandre Julliard
[EMAIL PROTECTED]
When compiling CVS, I get:
...
gcc -c -I. -I. -I../include -I../include-Wall -pipe
-mpreferred-stack-boundary=2 -fno-strict-aliasing -gstabs+ -Wpointer-arith
-g -O2 -o pthread.o pthread.c
gcc -o wine-pthread -Wl,--export-dynamic
-Wl,--section-start,.interp=0x77f00400 pthread.o main.o -L../
Hi
Dimi,
I was trying to understand why any wine shared dll (like msvcrt.dll.so)
crashed at the _fini call. This does not happen if I use my own created
shared libraries. I was seeking help to find out why the crash occurs only
with wine shared library. I had to port my windows code even on MacOS,
Hi,
I installed new version of wine
-20040505 but when I tried
to use winemaker to gnerate configuration
file.
it is not generated and generate Makefile
direct.
is it and error in winemaker or updates in new
version.
thanks
aallabs
Eric Pouech wrote:
The next time the app calls read, wine sets off a new (now making it
two) FILE_AsyncReadService, but clears the buffer first, so all the
characters received from the previous FILE_AsyncReadService get lost.
it seems the event to be signaled when something is done in the first
On Wed, 02 Jun 2004 15:52:41 +0200, you wrote:
>
> So, it seems that there's only Mike's solution, if someone has no other
> ideas...
Yes, thanks for trying.
Rein.
--
Rein Klazes
[EMAIL PROTECTED]
Hi all,
As mentioned in a previous thread, I'm trying to get a client to migrate
their product to Linux using Wine. So far, the results have been so so,
with mightily strange results (sockets in "Established" state with no
controlling process, zomby processes who's parent is init that are not
b
> When compiling with STLPort I saw a method that can eliminate the need
> for the MSVCRT macro and yet produce MSVCRT_xxx for those who need it
> and an xxx for those how don't.
> Basically you have your Regular cleanroom headers-set for wine-lib and
> external dlls. And you have another set
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
on 06/02/04 14:19, Rein Klazes wrote:
> It is a small function, hard to do it wrong there. Just put it before
> the line with return .
I'm so stupid, I didn't think that I should see in the other files
modified by the patch. Thank you for the e
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
on 06/02/04 13:35, Mike Hearn wrote:
> Normally you would post the patch to wine-patches for review. Could you do
> that please? We don't use bugzilla for patch tracking.
sure, done [1]. Sorry for my confusion.
Thx, bye,
Gismo / Luca
[1] http
On Wed, 02 Jun 2004 13:31:41 +0200, you wrote:
> > with a number of specific activation context error codes in the
> > 12000-14999 region.
> simple problem: I'm not a good programmer (some BASH, C, Perl and php
> knowledge), so where should I insert the above line?
It is a small function, hard to
On Wed, 02 Jun 2004 13:08:16 +0200, Luca Capello wrote:
> patch posted on bug #2017 [1]. Direct link to the patch [2].
Normally you would post the patch to wine-patches for review. Could you do
that please? We don't use bugzilla for patch tracking.
thanks -mike
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
on 06/02/04 10:55, Rein Klazes wrote:
> Here are the details of the QueryActCtxW call:
>
> |0009:Ret advapi32.RegCloseKey() retval= ret=00be869f
> |0009:Call
kernel32.QueryActCtxW(8010,0116283c,,0001,406aebc0,0008,0
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
on 06/01/04 20:10, Mike Hearn wrote:
> OK, could you submit a patch to comment that line out? These functions are
> just stubs anyway. When they are more complete it's trivial to renable
> them.
patch posted on bug #2017 [1]. Direct link to the
On Wed, 2004-06-02 at 01:36, Raphael wrote:
> With latest rsabase (i'll send the last today) and ntdll patches
> we go a lot further. But we seems to crash with File Access (sharing) problem.
> Who can understand this log ?
> The traces like fixme:ntdll:NtCreateFile L"\\??\\E:\\4996.rra" => (0, 1)
On Wed, 2004-06-02 at 01:39, Raphael wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Wednesday 02 June 2004 00:51, Robert Shearman wrote:
> > On Tue, 2004-06-01 at 22:53, Robert Shearman wrote:
> > > Hi,
> > >
> > > The second registry key added by this patch is needed for rsabase
Dimitrie O. Paun wrote:
On Tue, Jun 01, 2004 at 11:16:06AM -0700, Alexandre Julliard wrote:
No I don't think we want that. The headers are not that stable, we are
still making changes to them. We also need the MSVCRT definitions in
multiple dlls so there would be a lot of duplication.
Yes,
On Tue, 01 Jun 2004 18:42:34 +0200, you wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hello,
>
> on 06/01/04 18:28, Rein Klazes wrote:
> > That is one possibility. You can also attach it in bugs.winehq.org to
> > the bug report that you mentioned before.
> I'm so stupid I didn't t
38 matches
Mail list logo
