Date:	Wed, 20 Jan 1999 10:55:09 +0100 (CET)
Message-Id:	<199901200955.KAA29286@login-2.eunet.no>
From:	"Gisle Vanem" <gvanem AT eunet DOT no>
To:	djgpp AT delorie DOT com
Subject:	Re: Dosx & FoxPro (Phar Lab) & DJGPP
X-Mailer:	Watt/POP
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com

Eli Zaretskii said:

> >
> > "Phar Lab fatal err 10049: Ran out of stack buffers"
>
> Could you please explain in more detail what this message means?  I
> doubt anybody here knows enough about FoxPro and Phar Lap to guess
> this information.  Without understanding what are those ``stack
> buffers'' that Phar Lap runs out of, it is almost impossible to guess
> what exactly goes wrong here.

Message 10049 means the number of "real-to-protected mode switches" has
exceeded the number of allocated interrupt stacks (default is 6). Pharlap
allocates a locked stack of 1kByte (default) in preparation for each
hardware interrupt originating in real-mode. Or when performing a real-
protected mode-switch. 

Looks like someone (Foxpro) is enabling interrupts too early so that
nested interrupts occur and overflows the stack pool. Or that the IF
bit (Interrupt Flag) is not virtualised correctly.

> > When I write in autoexec: SET DOSX=-ni 20 -is 2, I can run good my DJGPP
> > program from FoxPro 18 time.
>
> Again, please explain what do these parameters mean, and how do they
> affect the ``stack buffers''.

This simply mean; allocate 20 interrupt stacks of 2kbyte each.

The original poster may add more debug to the DOSX variable:

SET DOSX=-debug xxxxh

where each bit in xxxx enables specific trace messages. He might try
SET DOSX=-debug 1003h


> 2. When I run FoxPro form DOS, and when I run DJGPP program, this
> situation not exist too.

This means you could solve the problem easily by running from the
DJGPP port of Bash, for example.

> > I thing that there is problem between dosx, FoxPro(PharLab) and DJGPP
> > program.
> > I can modify only DJGPP program, but I do not know how.
> >
> > I'd appreciate any advice you could give me.
>
> More information is needed to advise.  It would also help if somebody
> who knows about Phar Lap and can describe the meaning of these
> failures (does Phar Lap provide on-line support?) would join this
> discussion.

I've always got good help at "tech-support AT pharlap DOT com".


Gisle V.

- Raw text -