Sent: 02/06/2005
From: mark
Message:Suspected that and tried google, but the support for Phar Lap is not good, to
put it mildly!
Many thanks
Mark
"Colin Barnhorst" wrote:
Show quoted text
> This is not a VPC error. It would not be presented from within the guest.
> You are correct that it is the DOS extender. Google on "Phar Lap" to get an
> idea of how it works.
>
> --
> Colin Barnhorst [MVP Windows - Virtual Machine]
> (Reply to the group only unless otherwise requested)
> "mark" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
> > Error message is:
> >
> > Phar Lap fatal err 10049: Ran out of stack buffers
> >
> > Happens (as always) on my sister's computer when running an APL program
> > under virtual PC. She has to run APL in a traditional DOS enviroment to
> > get
> > the full memory allocation
> >
> > This might be an error on the dos extender she is using - think it is Phar
> > Lap or it might be virtual PC. Having little or no knowledge of either
> > program (or APL!) but able to use the internet I'm just acting as a
> > conduit
> > for my sister.
> >
> > Thanks
> >
> > Mark
>
>
>
Sent: 02/06/2005
From: "Colin Barnhorst" <colinbarharst(nojunk)@msn.com>
Message:This is not a VPC error. It would not be presented from within the guest.
You are correct that it is the DOS extender. Google on "Phar Lap" to get an
idea of how it works.
--
Colin Barnhorst [MVP Windows - Virtual Machine]
(Reply to the group only unless otherwise requested)
"mark" <(email address - cut out)> wrote in message
news:(email address - cut out)...
Show quoted text
> Error message is:
>
> Phar Lap fatal err 10049: Ran out of stack buffers
>
> Happens (as always) on my sister's computer when running an APL program
> under virtual PC. She has to run APL in a traditional DOS enviroment to
> get
> the full memory allocation
>
> This might be an error on the dos extender she is using - think it is Phar
> Lap or it might be virtual PC. Having little or no knowledge of either
> program (or APL!) but able to use the internet I'm just acting as a
> conduit
> for my sister.
>
> Thanks
>
> Mark
Sent: 02/06/2005
From: "Colin Barnhorst" <colinbarharst(nojunk)@msn.com>
Message:Sorry about that. There are a couple of dos newgroups you could try.
Someone may be savvy. I doubt it ever shows up in XP.
--
Colin Barnhorst [MVP Windows - Virtual Machine]
(Reply to the group only unless otherwise requested)
"mark" <(email address - cut out)> wrote in message
news:(email address - cut out)...
Show quoted text
> Suspected that and tried google, but the support for Phar Lap is not good,
> to
> put it mildly!
>
> Many thanks
>
> Mark
>
> "Colin Barnhorst" wrote:
>
>> This is not a VPC error. It would not be presented from within the
>> guest.
>> You are correct that it is the DOS extender. Google on "Phar Lap" to get
>> an
>> idea of how it works.
>>
>> --
>> Colin Barnhorst [MVP Windows - Virtual Machine]
>> (Reply to the group only unless otherwise requested)
>> "mark" <(email address - cut out)> wrote in message
>> news:(email address - cut out)...
>> > Error message is:
>> >
>> > Phar Lap fatal err 10049: Ran out of stack buffers
>> >
>> > Happens (as always) on my sister's computer when running an APL program
>> > under virtual PC. She has to run APL in a traditional DOS enviroment to
>> > get
>> > the full memory allocation
>> >
>> > This might be an error on the dos extender she is using - think it is
>> > Phar
>> > Lap or it might be virtual PC. Having little or no knowledge of either
>> > program (or APL!) but able to use the internet I'm just acting as a
>> > conduit
>> > for my sister.
>> >
>> > Thanks
>> >
>> > Mark
>>
>>
>>
Sent: 02/07/2005
From: "GaryM" <Gary(No.Canned.Meat)(email address - cut out)>
Message:Hi Mark,
Before we completely dismiss this as a memory extender error, I'm reminded
of the conflict that used to exist between EMM386 and VPC's DOS folder
sharing addition (pre-SP1). Something in the DOS Additions might be causing
this conflict, so you might try uninstalling them (assuming they're
installed), and then reboot the Guest and run your sister's program again.
If you get the same results, then just make sure the config.sys file has the
same "STACKS=" setting that she used on a physical computer running her
program. Maybe that setting was lost or changed in the migration. Good
luck. Much of Phar Lap tech support was written in the days of chisels and
stone tablets ;-)
--Gary
"Colin Barnhorst" <colinbarharst(nojunk)@msn.com> wrote in message
news:eW$$(email address - cut out)...
Show quoted text
> Sorry about that. There are a couple of dos newgroups you could try.
> Someone may be savvy. I doubt it ever shows up in XP.
>
> --
> Colin Barnhorst [MVP Windows - Virtual Machine]
> (Reply to the group only unless otherwise requested)
> "mark" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
>> Suspected that and tried google, but the support for Phar Lap is not
>> good, to
>> put it mildly!
>>
>> Many thanks
>>
>> Mark
>>
>> "Colin Barnhorst" wrote:
>>
>>> This is not a VPC error. It would not be presented from within the
>>> guest.
>>> You are correct that it is the DOS extender. Google on "Phar Lap" to
>>> get an
>>> idea of how it works.
>>>
>>> --
>>> Colin Barnhorst [MVP Windows - Virtual Machine]
>>> (Reply to the group only unless otherwise requested)
>>> "mark" <(email address - cut out)> wrote in message
>>> news:(email address - cut out)...
>>> > Error message is:
>>> >
>>> > Phar Lap fatal err 10049: Ran out of stack buffers
>>> >
>>> > Happens (as always) on my sister's computer when running an APL
>>> > program
>>> > under virtual PC. She has to run APL in a traditional DOS enviroment
>>> > to
>>> > get
>>> > the full memory allocation
>>> >
>>> > This might be an error on the dos extender she is using - think it is
>>> > Phar
>>> > Lap or it might be virtual PC. Having little or no knowledge of either
>>> > program (or APL!) but able to use the internet I'm just acting as a
>>> > conduit
>>> > for my sister.
>>> >
>>> > Thanks
>>> >
>>> > Mark
>>>
>>>
>>>
>
>
Wiki