Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: Notesfiles $Revision: 1.7.0.8 $; site trsvax
Path: utzoo!watmath!clyde!cbosgd!ihnp4!inuxc!pur-ee!uiucdcs!convex!trsvax!gm
From: gm@trsvax
Newsgroups: net.micro
Subject: Microsoft Access trashes disk
Message-ID: <53400078@trsvax>
Date: Tue, 24-Sep-85 18:20:00 EDT
Article-I.D.: trsvax.53400078
Posted: Tue Sep 24 18:20:00 1985
Date-Received: Sat, 28-Sep-85 04:55:09 EDT
Lines: 28
Nf-ID: #N:trsvax:53400078:000:1427
Nf-From: trsvax!gm    Sep 24 17:20:00 1985


This was an article which appeared in this week's (Sep 24) "PC Week". I 
thought it was kind of funny. Reproduced without permission, of course.
---------------------------------------------------------------------------

     What do you do when your program summarily announces that it is "Trashing
Program Disk"? It happened to us while we were reviewing Microsoft Access--a 
new telecommunication program. We had diligently performed the hard-disk
installation and had successfully run the program a dozen or more times.
Suddenly we were assaulted with an error message that struck fear into our
hearts:

			Internal Security Violation
		    The tree of evil bears bitter fruit
			     Crime does not pay
			      The Shadow knows

     And finally the punchline: "Trashing Program Disk." Since the "program
disk" was our system's hard disk, this was no laughing matter. Luckily,
Access didn't really destroy all our work--it merely deepened our animosity
toward copy protection.
     Microsoft's response was unsatisfactory. "Don't worry about it," a
spokesman said, "It really doesn't do any damage."
     That's debatable. Clearly, Microsoft's snide message is intended to be
displayed when copy protection is circumvented. When sloppy programming
allows such foolishness to frighten and insult a legitimate user, however,
that's unforgivable.
---------------------------------------------------------------------------