SEWALL@UCONNVM.BITNET (Murph Sewall) (07/06/88)
> Sorry but it does mater. Kermit when it initializes itself sets things up >depending upon the machine type. So when you do your bsave then the machine >is locked in. The bsave from ez install doesnt have that problem since kermit >has never been executed. Sigh! AHA! Now I understand how people can get Kermit disks in the mail and complain that they crash (disk made on enhanced //e and sent to unenhanced //e owners or vice-versa). In future, I will make sure the BIN files I mail to people have been created from the EZ Install and not BSAVE'd after being BRUN. I installed the patch you sent after the EZ Install and now have a patched version that runs on both my unenhanced //e and my //c. I gather that if the BIN file is going to be changed for someone (as in EXEC KER3xx.INSTALL) the program should be placed in memory with BLOAD KER3xx (so that the version in memory is one that hasn't been altered by execution). That should allow changes to be installed without making the program unuseable by a different Apple 2 shouldn't it? Murph Sewall Sewall@UCONNVM.BITNET Business School sewall%uconnvm.bitnet@mitvma.mit.edu [INTERNET] U of Connecticut {rutgers psuvax1 ucbvax & in Europe - mcvax} !UCONNVM.BITNET!SEWALL [UUCP] -+- My employer isn't responsible for my mistakes AND vice-versa! (subject to change without notice; void where prohibited) "It might help if we ran the MBA's out of Washington." - Adm Grace Hopper