On Monday 8 November 2004 17:11, Dan Kegel wrote:
> > What do your $TMP and $TEMP look like?
>
> In the Unix shell before I start wine, they are
> both unset.
I was asking because the path test uses GetTempPath which looks at
$TMP and $TEMP. My $TMP and $TEMP are unset as well and I don't have
a
Hans Leidekker wrote:
On Monday 8 November 2004 14:20, Dan Kegel wrote:
The path failures are all due to t: not existing; when I create
it by hand, those 397 errors go away.
It sounds very much like the startup code that creates c: and z: needs
to also create a t: drive!
What do your $TMP and $TE
On Monday 8 November 2004 14:20, Dan Kegel wrote:
> The path failures are all due to t: not existing; when I create
> it by hand, those 397 errors go away.
> It sounds very much like the startup code that creates c: and z: needs
> to also create a t: drive!
What do your $TMP and $TEMP look like?
On Monday 08 November 2004 16:47, you wrote:
> --- Michael Jung <[EMAIL PROTECTED]> wrote:
> > Yes, it is. I would even opt for removing this fixme (or changing it
> > to a
> > trace) and let the VerifyImage function always return TRUE.
> > Implementing it
> > in a sensible way would be a large eff
On Mon, Nov 08, 2004 at 04:41:59AM -0800, Dan Kegel wrote:
> Michael Jung wrote:
> >I fear that the problems with crypt.c and the crash are related to
> >rsaenh.dll, which is pretty new in wine cvs. I can't reconstruct the test
> >failures on my system. There are some entries in the initial regis
--- Michael Jung <[EMAIL PROTECTED]> wrote:
> Yes, it is. I would even opt for removing this fixme (or changing it
> to a
> trace) and let the VerifyImage function always return TRUE.
> Implementing it
> in a sensible way would be a large effort, which would not buy us any
This would be really
Dan Kegel wrote:
I pulled down sources from CVS this morning, and tried
running the regression tests. There are about 150 failures.
>$ grep "Test failed" log | sed 's/:.*//' | uniq -c | sort
> 1 filtergraph.c
> 1 rsaenh.c
> 1 shelllink.c
> 1 shreg.c
> 2 typelib.c
>
On Monday 08 November 2004 13:41, you wrote:
> Michael Jung wrote:
> > I fear that the problems with crypt.c and the crash are related to
> > rsaenh.dll, which is pretty new in wine cvs. I can't reconstruct the test
> > failures on my system. There are some entries in the initial registry,
> > whic
Michael Jung wrote:
I fear that the problems with crypt.c and the crash are related to rsaenh.dll,
which is pretty new in wine cvs. I can't reconstruct the test failures on my
system. There are some entries in the initial registry, which did change due
to rsaenh.dll. Could please retry without a
On Sunday 07 November 2004 23:19, Dan Kegel wrote:
> Hey folks,
> I pulled down sources from CVS this morning, and tried
> running the regression tests. There are about 150 failures.
> Here's a summary:
>
> $ grep "Test failed" log | sed 's/:.*//' | uniq -c | sort
>1 filtergraph.c
>
On Sun, Nov 07, 2004 at 02:19:31PM -0800, Dan Kegel wrote:
> Hey folks,
> I pulled down sources from CVS this morning, and tried
> running the regression tests. There are about 150 failures.
> Here's a summary:
>
> $ grep "Test failed" log | sed 's/:.*//' | uniq -c | sort
> 1 filtergraph.c
Hey folks,
I pulled down sources from CVS this morning, and tried
running the regression tests. There are about 150 failures.
Here's a summary:
$ grep "Test failed" log | sed 's/:.*//' | uniq -c | sort
1 filtergraph.c
1 rsaenh.c
1 shelllink.c
1 shreg.c
2 typelib.c
12 matches
Mail list logo
