[net.micro.mac] MacPascal question

bill@utastro.UUCP (William H. Jefferys) (06/29/85)

I have two simple questions about MacPascal and the new Finder.
I would like to use it under the new Finder, but fear 
ruining my disk if I were to update it with System Update.
As is common knowledge, Think Technologies chose to use a
fearsome copy protection scheme on MacPascal, complete with
worms and other nasties (fie on you, Think Technologies!)  
Unless one of the newer bit copy programs has overcome these
"worms", one is forced to run off the master diskette.  The
questions are:

(1) Is it safe to use System Update to install the new Finder  (4.1)
    on the master MacPascal disk?  Has anyone tried it?  Does someone at
    Apple *know* the answer to this question?

(2) A related question is the following.  I use a Mac XL at work.
    After quitting MacPascal, one returns to the desktop with MacPascal
    selected as the startup disk.  This takes forever, since I have
    quite a few files on the hard disk, and it's the old finder.
    Then I have to launch the finder on the hard disk which also takes time.
    This is a pain.  Is there an easy way to prevent this from happening,
    again, without destroying the MacPascal disk?  Any information
    is welcome, but an Authoritative (read: Official Apple) reply
    would be best!

-- 
"Men never do evil so cheerfully and so completely as when they do so from
	religious conviction."  -- Blaise Pascal

	Bill Jefferys  8-%
	Astronomy Dept, University of Texas, Austin TX 78712   (USnail)
	{allegra,ihnp4}!{ut-sally,noao}!utastro!bill	(uucp)
	bill%utastro.UTEXAS@ut-sally.ARPA		(ARPANET)

jwp@utah-cs.UUCP (John W Peterson) (06/30/85)

By going in with Fedit and turning off some "invisible" bits, you can 
indentify the four files MacPascal needs to run (The application, and
three files called "IPAux", "IPInit" and "IPabout" if I recall).  Then
you can copy these three files to a RAM/Hard/floppy disk, and start up
MacPascal with whatever system you like.

However, the original MacPascal "master" must be in one of the floppy drives
when you start up Mac Pascal, and when you save or open any files (best
just leave it in the drive all the time, to avoid getting bitten).

Sometimes the first startup of MacPascal on the RamDisk just returns to the
finder.  However, starting it again on the RamDisk seems to work fine.

bill@utastro.UUCP (William H. Jefferys) (06/30/85)

> By going in with Fedit and turning off some "invisible" bits, you can 
> indentify the four files MacPascal needs to run (The application, and
> three files called "IPAux", "IPInit" and "IPabout" if I recall).  Then
> you can copy these three files to a RAM/Hard/floppy disk, and start up
> MacPascal with whatever system you like.
> 
> However, the original MacPascal "master" must be in one of the floppy drives
> when you start up Mac Pascal, and when you save or open any files (best
> just leave it in the drive all the time, to avoid getting bitten).

Yes, I know about this.  There is a problem, however.  With the new
finder (and maybe with the old one too) MacPascal does something (to the
system heap?) that breaks the "copy one disk to another by dragging the
icon of one disc onto the other" operation.  You get a "Disk contains
locked items" message, even if neither disk has them.  Since I leave
my machine on for several days during the week and only turn it off on
the weekends (as has been recommended) I have to live with this until
the next time I start up the machine.  Can this be circumvented?

BTW, the MacPascal "master" has to remain in the drive at all times, not
only on the occasions you mention.  Otherwise the "one hundred clicks in
the editor window" worm will get you (MacPascal quits and all your work
goes down the toilet).

-- 
"Men never do evil so cheerfully and so completely as when they do so from
	religious conviction."  -- Blaise Pascal

	Bill Jefferys  8-%
	Astronomy Dept, University of Texas, Austin TX 78712   (USnail)
	{allegra,ihnp4}!{ut-sally,noao}!utastro!bill	(uucp)
	bill%utastro.UTEXAS@ut-sally.ARPA		(ARPANET)

bill@utastro.UUCP (William H. Jefferys) (06/30/85)

Addendum to the last message.  What I am really wondering is if one can
remove the finder altogether from the MacPascal master disk so that
when I return to the desktop the version of the finder on the hard
disk is still in control.

-- 
"Men never do evil so cheerfully and so completely as when they do so from
	religious conviction."  -- Blaise Pascal

	Bill Jefferys  8-%
	Astronomy Dept, University of Texas, Austin TX 78712   (USnail)
	{allegra,ihnp4}!{ut-sally,noao}!utastro!bill	(uucp)
	bill%utastro.UTEXAS@ut-sally.ARPA		(ARPANET)

cmk@amdahl.UUCP (Carol Kent) (07/01/85)

> By going in with Fedit and turning off some "invisible" bits, you can 
> identify the four files MacPascal needs to run (The application, and
> three files called "IPAux", "IPInit" and "IPabout" if I recall).  Then
> you can copy these three files to a RAM/Hard/floppy disk, and start up
> MacPascal with whatever system you like.
> 
> However, the original MacPascal "master" must be in one of the floppy drives
> when you start up Mac Pascal, and when you save or open any files (best
> just leave it in the drive all the time, to avoid getting bitten).


I've copied all the above files to a disk (made the "ip*" files invisible
again), and tried to run the program.  Executes just fine, but I've got a
problem which others have encountered as well, I think:  after X number
of mouse clicks, the application quits itself and goes back to the Finder.

Not friendly....

Is there a fix available for this?
I don't want to spin my original disks and one day find they don't work
anymore; I paid too much for them to let that happen!

I post a summary of replies to the net.  Thanks for any help.

m55al@brahms.BERKELEY.EDU (Deepak Munjal) (03/21/86)

I've got MacPascal and I'm trying to make a key command
that halts the program when its running.  I've tried
Hertzfeld's Menu Editor, but it doesn't seem to work
with MacPascal.  But even if it did, I wouldn't be able
to make a key command for halt because the menu that has 
the halt command only appears when the program is running.
Any ideas to remedy this situation would be greatly 
appreciated.