Re: DOS DPMI32, interrupt handlers in 32-bit code

[Sylvain Petreolle]

You're right, the problem seemed to be in my local repository.
I had problems with patch saying the hunks were reversed.
Today I deleted every file that should be patched, made cvs update and
it patched like a dream.

So you can apply.
 --- Jukka Heinonen <[EMAIL PROTECTED]> a écrit : > > I tried your patch on
the latest CVS.
> > This doesn't compile at the moment, complaining about FARPROC48 :
> 
> That is strange because memory/instr.c seems to include miscemu.h
> and patched miscemu.h provides type FARPROC48. I guess I have to go 
> through the patch once more and see if there is something missing.


___
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Yahoo! Mail : http://fr.mail.yahoo.com

Re: DOS DPMI32, interrupt handlers in 32-bit code

[Jukka Heinonen]

> I tried your patch on the latest CVS.
> This doesn't compile at the moment, complaining about FARPROC48 :

That is strange because memory/instr.c seems to include miscemu.h
and patched miscemu.h provides type FARPROC48. I guess I have to go 
through the patch once more and see if there is something missing.

Anyway, I guess the patch should not be applied before I have time to
see how 16-bit interrupts work in DPMI32 when user has set a custom
protected mode interrupt handler. At least the normal DPMI32 interrupt
handlers can be called using both 16 and 32 bit interrupts and
I just started to wonder if DPMI32 is supposed to provide 16->32
relays for user handlers. And DPMI documentation is really
vague on whether the user handlers should exit using iret or iretd.

So, Alexandre, please don't apply this patch to wine CVS.

-- 
Jukka Heinonen 

Re: How to add a new test dir? (Update)

[Greg Turner]

On Sunday 06 October 2002 06:25 pm, Greg Turner wrote:
> I'm trying to create a tests directory for rpcrt4.  So far I've
> done the following:
>
> o Create a dlls/rpcrt4/tests directory
>
> o Change dlls/rpcrt4/Makefile.in:
>
> o add dlls/rpcrt4/tests/Makefile.in:
>
> o add dlls/rpcrt4/tests/rpc.c:
>
> but I get no love.  configure seems to go OK;
> When I run make depend it fails:
>
> <==
> make[2]: Entering directory `/var/src/wine/dlls/rpcrt4'
> cd `dirname tests/__depend__` && make depend
> make[3]: Entering directory `/var/src/wine/dlls/rpcrt4/tests'
> make[3]: *** No rule to make target `depend'.  Stop.
> make[3]: Leaving directory `/var/src/wine/dlls/rpcrt4/tests'
> make[2]: *** [tests/__depend__] Error 2
> make[2]: Leaving directory `/var/src/wine/dlls/rpcrt4'
> make[1]: *** [rpcrt4/__depend__] Error 2
> make[1]: Leaving directory `/var/src/wine/dlls'
> make: *** [dlls/__depend__] Error 2
> ==>
>
> What am I missing?  Is this documented somewhere?
> Thanks,

I found it:

Index: configure.ac
===
RCS file: /home/wine/wine/configure.ac,v
retrieving revision 1.81
diff -u -r1.81 configure.ac
--- configure.ac2 Oct 2002 19:58:27 -   1.81
+++ configure.ac7 Oct 2002 03:09:02 -
@@ -1435,6 +1435,7 @@
 dlls/rasapi32/Makefile
 dlls/richedit/Makefile
 dlls/rpcrt4/Makefile
+dlls/rpcrt4/tests/Makefile
 dlls/serialui/Makefile
 dlls/setupapi/Makefile
 dlls/shdocvw/Makefile

Now I'm sure it'll get even more confusing ;)

--
gmt

"If ye love wealth better than liberty, the tranquility
of servitude better than the animating contest of freedom,
go home from us in peace. We ask not your counsels or your
arms. Crouch down and lick the hands, which feed you. May
your chains set lightly upon you, and may posterity forget
that ye were our countrymen."

-Samuel Adams

Re: pain and agony... a +relay,+seh trace from my cxxexcept problem case:

[Greg Turner]

On Thursday 03 October 2002 05:51 pm, Greg Turner wrote:
> OK, here is what looks to me like the relevant stuff... I'm determined to
> get this fixed, I "need" this app (ya right... I've got vmware...)
[SNIP]
> and so on.  What have we learned, except that StarTeam was probably
> written in Visual Basic?  Not sure.  I guess I need to focus on: "where are
> the NULL's passed to ThrowException coming from?"??  Or is there something
> more obvious going on here that I'm to ign'ant to grok?
>
> thanks for your help,...

Rolling around in CVS, I've discovered that StarTeam works until
this patch:

  http://www.winehq.com/hypermail/wine-cvs/2002/09/0157.html

after that, it's broken, initially in a nicer way that doesn't involve
infinite recursion in the exception handlers (XBadRequest or
something like that, and a nice clean crash).  Not sure when it
makes the transition to utter chaos in the exception handling

FYI, this is an MFC42 app, and the last thing it does before
TSHTF is to close down a dialog window in the WIZARD_97
style.  I had to use native comctl32/commctrl to use it at all,
(even when it worked otherwise, presumably because of the
WIZARD_97 business).  The patched code gets called during
the DestroyWindow processing; no failure occurs, however, until
control returns to StarTeam's "native" code.

still hoping for a magical fix from some wisened guru-type,

-- 
gmt

"If ye love wealth better than liberty, the tranquility
of servitude better than the animating contest of freedom,
go home from us in peace. We ask not your counsels or your
arms. Crouch down and lick the hands, which feed you. May
your chains set lightly upon you, and may posterity forget
that ye were our countrymen." 

-Samuel Adams

How to add a new test dir?

[Greg Turner]

I'm trying to create a tests directory for rpcrt4.  So far I've
done the following:

o Create a dlls/rpcrt4/tests directory

o Change dlls/rpcrt4/Makefile.in:

<=
--- Makefile.in.A_PL2   2002-10-04 09:26:11.0 -0500
+++ Makefile.in 2002-10-06 17:59:31.0 -0500
@@ -13,6 +13,8 @@
 rpc_binding.c \
rpcrt4_main.c

+SUBDIRS = tests
+
 @MAKE_DLL_RULES@

 ### Dependencies:
===>

o add dlls/rpcrt4/tests/Makefile.in:

<===
TOPSRCDIR = @top_srcdir@
TOPOBJDIR = ../../..
SRCDIR= @srcdir@
VPATH = @srcdir@
TESTDLL   = rpcrt4.dll
IMPORTS   = rpcrt4

CTESTS = \
rpc.c

@MAKE_TEST_RULES@

### Dependencies:
==>

o add dlls/rpcrt4/tests/rpc.c:

<
#include "wine/test.h"
#include 
#include 
#include 

START_TEST( rpc )
{
trace ( "  STARTING TEST %d  \n", 0 );
ok (1);

Exit();
}
>

but I get no love.  configure seems to go OK;
When I run make depend it fails:

<==
make[2]: Entering directory `/var/src/wine/dlls/rpcrt4'
cd `dirname tests/__depend__` && make depend
make[3]: Entering directory `/var/src/wine/dlls/rpcrt4/tests'
make[3]: *** No rule to make target `depend'.  Stop.
make[3]: Leaving directory `/var/src/wine/dlls/rpcrt4/tests'
make[2]: *** [tests/__depend__] Error 2
make[2]: Leaving directory `/var/src/wine/dlls/rpcrt4'
make[1]: *** [rpcrt4/__depend__] Error 2
make[1]: Leaving directory `/var/src/wine/dlls'
make: *** [dlls/__depend__] Error 2
==>

What am I missing?  Is this documented somewhere?
Thanks,

-- 
gmt

"If ye love wealth better than liberty, the tranquility
of servitude better than the animating contest of freedom,
go home from us in peace. We ask not your counsels or your
arms. Crouch down and lick the hands, which feed you. May
your chains set lightly upon you, and may posterity forget
that ye were our countrymen." 

-Samuel Adams

Re: msvcrt tests

[Uwe Bonnes]

> "=?iso-8859-1?Q?Gy=F6rgy" == =?iso-8859-1?Q?Gy=F6rgy 'Nog' Jeney?=  
>writes:

>>  Im trying to write regression tests for the sscanf function but ran
>> into some problems.  First, there were some conflicts with the
>> defines in the headers with my linux ones, but that was fixed simply
>> by defining USE_MSVCRT_PREFIX. Whenever I try to run the test it
>> spews out an error: undefind reference to func_sscanf.  Ofcourse
>> there is no export for func_sscanf because it was prefixed to avoid a
>> naming conflict with the unix defines.  How do I get this to work? If
>> its not prefixed, then there is a conflict but if it is then it cant
>> find the export.

=?iso-8859-1?Q?Gy=F6rgy> Sorry, this is my fault, In my test I had
=?iso-8859-1?Q?Gy=F6rgy> START_TEST(scanf) instead of
=?iso-8859-1?Q?Gy=F6rgy> START_TEST(sscanf). It works now.

Please add the msvcrt test-framework to the wine source tree. And thanks
for your findings.

Bye
-- 
Uwe Bonnes[EMAIL PROTECTED]

Institut fuer Kernphysik  Schlossgartenstrasse 9  64289 Darmstadt
- Tel. 06151 162516  Fax. 06151 164321 --

Re: some rpcrt4 stuff

[Greg Turner]

On Sunday 06 October 2002 02:47 pm, Jürgen Schmied wrote:
> Hi!
>
> Here are the old patches from Ove...
>
> Juergen
>
>
>
> ---
> [EMAIL PROTECTED]

great, these may come in handy!

-- 
gmt

"If ye love wealth better than liberty, the tranquility
of servitude better than the animating contest of freedom,
go home from us in peace. We ask not your counsels or your
arms. Crouch down and lick the hands, which feed you. May
your chains set lightly upon you, and may posterity forget
that ye were our countrymen." 

-Samuel Adams

Re: msvcrt tests

[György 'Nog' Jeney]

>
> Im trying to write regression tests for the sscanf function but ran into
> some
> problems.  First, there were some conflicts with the defines in the
> headers with my linux ones, but that was fixed simply by defining
> USE_MSVCRT_PREFIX. Whenever I try to run the test it spews out an error:
> undefind reference to func_sscanf.  Ofcourse there is no export for
> func_sscanf because it was prefixed to avoid a naming conflict with the
> unix defines.  How do I get this
> to work? If its not prefixed, then there is a conflict but if it is then
> it cant find the export.

Sorry, this is my fault, In my test I had START_TEST(scanf) instead of
START_TEST(sscanf). It works now.

nog.

msvcrt tests

[György 'Nog' Jeney]

Im trying to write regression tests for the sscanf function but ran into
some
problems.  First, there were some conflicts with the defines in the headers
with my linux ones, but that was fixed simply by defining USE_MSVCRT_PREFIX.
Whenever I try to run the test it spews out an error: undefind reference to
func_sscanf.  Ofcourse there is no export for func_sscanf because it was
prefixed to avoid a naming conflict with the unix defines.  How do I get
this
to work? If its not prefixed, then there is a conflict but if it is then it
cant find the export.

Re: DOS DPMI32, interrupt handlers in 32-bit code

[Sylvain Petreolle]

Hi Jukka,

I tried your patch on the latest CVS.
This doesn't compile at the moment, complaining about FARPROC48 :

gcc -c -I. -I. -I../../include -I../../include  -g -O2 -Wall
-mpreferred-stack-boundary=2  -fPIC -D__WINE__ -D_NTSYSTEM_ 
-DBINDIR="\"/usr/local/bin\""  -DETCDIR="\"/usr/local/etc\""
-D_REENTRANT -o ../../memory/instr.o
../../memory/instr.c../../memory/instr.c: In function
`INSTR_EmulateInstruction':
../../memory/instr.c:689: `FARPROC48' undeclared (first use in this
function)
../../memory/instr.c:689: (Each undeclared identifier is reported only
once
../../memory/instr.c:689: for each function it appears in.)
../../memory/instr.c:689: parse error before "addr"
../../memory/instr.c:697: `addr' undeclared (first use in this
function)
make[2]: *** [../../memory/instr.o] Erreur 1


___
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Yahoo! Mail : http://fr.mail.yahoo.com

Re: Wine language problem

[Armish]

Hi
$ echo $LANG
tr_TR

Yes, I am using codeweavers-wine. The new versions of
wine can fix this error, cant they?

Thanks

__
Do you Yahoo!?
Faith Hill - Exclusive Performances, Videos & More
http://faith.yahoo.com