I am trying to write a patch to an existing application. The existing application
required extensive customization by the end user (several hours). Now I want to
update a few of the longer scripts using a patch, so that the users don't need to go
through the excruciating setup again. I have writte
Scott Rossi wrote:
> If I was going to create my own Windows file installer (say, launched from a
> CD), how would I go about tracking the volume of data copied to the user's
> drive? Is it only possible to poll the number of files or is there some way
> to track the actual K or bytes?
>
> Has
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 the
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 circu
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 stuf