Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site wlbr.UUCP
Path: utzoo!watmath!clyde!cbosgd!ihnp4!nsc!voder!wlbr!steve
From: steve@wlbr.UUCP (Steve Childress)
Newsgroups: net.micro.68k
Subject: Re: Re: Re: Info on OS9 Operating System
Message-ID: <379@wlbr.UUCP>
Date: Thu, 17-Oct-85 19:21:12 EDT
Article-I.D.: wlbr.379
Posted: Thu Oct 17 19:21:12 1985
Date-Received: Sat, 19-Oct-85 06:10:25 EDT
References: <347@wlbr.UUCP> <9500001@datacube.UUCP> <126@mcrware.UUCP> <837@lsuc.UUCP>
Organization: Eaton IMS, Westlake Village, CA
Lines: 21
Summary: OS9's CRC Scheme

I too did not like Microware's Module CRC scheme (in level I, I assume
that level II is likewise encumbered). The idea was to validate that
ROMs and EPROMs existed at boot-time. I believe that the CRC was intended
to detect ROMd modules (Mot's "Silcon Software" crusade), and
not to catch memory or I/O errors. But someone got carried away
and used the CRC scheme for modules and programs fetched from disk.

I say it was a mistake because disk files themselves have error checking.

When I NOP'd the call to CRC check LOAD'ed modules I noted a large speed-up
in hard disk systems. I sent the patches for the APPLE, CoCo, and SS50
OS9 level I's to '68 Micro Journal (magazine) to publish for the users
but they never printed..

		Regards,
			Steve Childress
			Eaton IMS    R&D Group MS 43 
			31717 La Tienda Drive
			Westlake Village,  CA    91360
			{trwrb, scgvaxd, ihnp4, voder, vortex} !wlbr!steve
		        or	 		        ...wlbr!wlbreng1!steve