🚀 go-pugleaf

In article <1043@oakhill.UUCP>, jmvm@oakhill.UUCP (John VanMunster) writes:

	<following up to messages, listing the version numbers of the latest
	 release version of the files System, Finder, MultiFinder>

> >please "graduate" the version of the System File such that both Finder and
> >System have the same version number?  There is already a lot of confusion
> >around because the two files have had the same and similar numbering.

> >Just Think:

> >	System 6.1
> >	Finder 6.1   ... and I know I'm pushing it...
> >	Multifinder 6.1

> >Just say *yes*
 
>   Y E S !   Y E S ! and  Y E S ! Please, its driving everyone crazy. Now,
> instead of alleviating the problem, its WORSE (System Software 5.0/System
> file 6.0 - yeecch)! Can't you just use ONE version number across ALL system
> stuff that comes on a specific release?

please, remember, that there are a couple of other files which have version
numbers, such as LaserWriter and LaserPrep, ScrapBook, FindFile-DA, etc ...

would you really like the version-numbers of all files to change for each
release, even when they don't change?  Somehow, when I think back to System
versions 3.0, 3.1, 3.1.1, I can see where that would drive me crazy also...

What I would like to see is something completely transparent to the user,
some code which gets executed as part of the boot process, which checks that
all the system files are compatible and warns the user of problems.
How the situation could be handled where you switch the Finder/System when
executing a file on a disks with it's own complete System or when you do a
OPTION-CLOVER-double-click on another Finder, I'll leave that to Apple
who should be the one writing this particular bit of code .....

BTW, it is probably necessary that DA's such as ControlPanel, Chooser, etc
do their own checking, because they might be run "out of the SuitCase"  ((-:
and not be available at boot ....

How the heck you check that the fonts are up-to-date beats me ....

otherwise, YES, YES, YES ....

-- 
kraut@ngp.utexas.edu