Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!columbia!rutgers!sri-spam!nike!ucbcad!ucbvax!decwrl!exodus.dec.com!harrow
From: harrow@exodus.dec.com (Jeff Harrow, NCSE LKG1-3/F16 DTN=226-7445)
Newsgroups: net.micro.mac
Subject: Mods to the Mac-Plus Write-Thru Cache?
Message-ID: <6009@decwrl.DEC.COM>
Date: Fri, 17-Oct-86 14:20:53 EDT
Article-I.D.: decwrl.6009
Posted: Fri Oct 17 14:20:53 1986
Date-Received: Sat, 18-Oct-86 00:39:39 EDT
Sender: daemon@decwrl.DEC.COM
Organization: Digital Equipment Corporation
Lines: 16

I believe that we have finally put to rest the confusion about the
Mac-Plus Control Panel Cache:  It is **NOT** write-thru.  Hence you **DO**
risk that in a crash situation, files which you THOUGHT were safe (you
SAVEd them) can really be left in an un-updated, or even corrupt state.

I still don't understand why Apple would choose this dangerous type oc
cache when the Mac usually defaults to the safest mode (yes, non-write thru
IS faster, but so is not asking a user if he wants to save a modified
document when he quits the application...).

Now for my question:  Since Apple didn't even offer the OPTION of choosing
safety over speed (a radio button to show a DEFAULT of write-thru, with
the OPTION of non-write-thru), has anyone figured out a SAFE patch to the
cache code to make this non-write-thru cache into a write-thru one?

Jeff Harrow