🚀 go-pugleaf

In article <7162@prls.UUCP> gardner@prls.UUCP (Robert Gardner) writes:
>
>looking at "computer illiterate users".) I'm hoping the THINK will fix
>the problem before the Mac II market (for my products) becomes big
>enough to worry about. (Actually, most of my stuff runs on the Mac II,
>you just have to be careful with low-level file io calls.)

	LightspeedC version 2.11 (posted to sumex-aim, comp.binaries.mac,
Delphi, Genie, and CompuServe, and from there to most of the civilized
world.

	LSC 2.11 fixes the problems with cache violation and direct handle
attribute maipulation.

	The problem with HGetState and HSetState is one that has been flamed
about very much on this net, but there's really nothing that's going to
be done; certainly, the startup code could be modified to check every
possible machine/ROM/System file combination, but this is not going to be done.

	The simple fact is that running System 2.0 on a machine with the
128K (or later) ROM set will not work. This is what Apple says, and this
is the way it is. If you want to test your software on old ROMs or with
an old System, use System 3.2. If you must test with System 2.0, you'll
have to get an old 512K machine to try it. 

	The reason you get crashes using HGetState and HSetState with System
2.0 on a Mac Plus is because the trap dispatch table is different under 
System 2.0, and these two calls (among others) get mapped out.

>LSC v3.x had better NOT have this problem!!!!!
	LSC 2.11 doesn't have it, LSC 3.x won't either.

		--Rich





**The opinions stated herein are my own opinions and do not necessarily
represent the policies or opinions of my employer (THINK Technologies, Inc).

* Richard M. Siegel | {decvax, ucbvax, sun}!harvard!endor!singer    *
* Customer Support  | singer@endor.harvard.edu			    *
* Symantec, THINK Technologies Division.  (No snappy quote)         *