: Problem with writing a patch stack
Date: Sat, 16 Sep 2000 14:16:43 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
In-Reply-To: [EMAIL PROTECTED]
On 16/9/00 8:59 am, Andy Bailey [EMAIL PROTECTED] wrote:
My home stack is licensed,
on 9/16/00 12:59 AM, Andy Bailey at [EMAIL PROTECTED] wrote:
I am trying to write a patch to an existing application.
and on 9/17/2000 5:10 AM, Geoff Canyon [EMAIL PROTECTED]
suggested:
Two other possible solutions, which may or may not violate your license,
would be:
1. Instead of
One other thought about patching stacks...
Remember that MC's stackfile format changed at certain version
releases. That may have an effect on your success, depending on
the version of the engine that runs thing you're patching, and
what kinds of objects are included in or affected by the patch.
Sounds like you might be opening the stack to patch the environment? You
need to open the patch stack from within the environment, as if he licenced
home stack is not the first thing to open the script limits are set to the
Starter kit.
This may not be the problem, but if it is have a look at
On 16/9/00 8:59 am, Andy Bailey [EMAIL PROTECTED] wrote:
My home stack is licensed, so I don't see the problem. Also, does this mean
that
others who just have bigearl.mc, mc, and mctools.mc can't use the patch
because of
the script limit? If this is indeed the case, how does one circumvent
on 9/16/00 12:59 AM, Andy Bailey at [EMAIL PROTECTED] wrote:
I am trying to write a patch to an existing application.
Two other possible solutions, which may or may not violate your license,
would be:
1. Instead of trying to copy the new stuff into the old stack, copy the
user-customized
