Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!cbosgd!gatech!seismo!umcp-cs!chris
From: chris@umcp-cs.UUCP (Chris Torek)
Newsgroups: net.unix-wizards
Subject: Re: Taming the UDA50
Message-ID: <3016@umcp-cs.UUCP>
Date: Sun, 2-Feb-86 14:09:25 EST
Article-I.D.: umcp-cs.3016
Posted: Sun Feb  2 14:09:25 1986
Date-Received: Mon, 3-Feb-86 06:33:40 EST
References: <2871@umcp-cs.UUCP>
Distribution: net
Organization: U of Maryland, Computer Science Dept., College Park, MD
Lines: 28

There were a few errors in my original article on UDA50/MSCP errors
(aside from the numerous typographical ggglitches, that is).

First, I should have mentioned in the `quick note' at the top that
events 0350 and 0353 are not really serious if the `flags' modifier
has bits 0x80 or 0x40 set.  I did mention these in the full
description: they are the `success' and `continuing' flags,
respectively, meaning `I fixed it' or `I think I can fix it'.
(Thanks to msdc!dan for pointing out that `event 0350' is not
necessarily cause for immediate suicide.)

Second, in the list of error codes, `hardware' and `software' write
protect are transposed.  This is also true in both C routines.
Change the table of errors, code 6, to

	  6		Write protected
		  1		via software
		  2		via hardware

and change `wrprot_msgs' to

	unknown_msg, "software", "hardware"

in udadecode.c and in uderror.
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 1415)
UUCP:	seismo!umcp-cs!chris
CSNet:	chris@umcp-cs		ARPA:	chris@mimsy.umd.edu