Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!uwvax!uwmacc!rick
From: rick@uwmacc.UUCP (the absurdist)
Newsgroups: comp.sys.mac
Subject: Re: Should 64K ROMs be supported? (Two example cases)
Message-ID: <758@uwmacc.UUCP>
Date: Mon, 22-Dec-86 11:05:11 EST
Article-I.D.: uwmacc.758
Posted: Mon Dec 22 11:05:11 1986
Date-Received: Mon, 5-Jan-87 22:08:31 EST
References: <476@runx.OZ> <1490@hoptoad.uucp> <907@ur-tut.UUCP>
Reply-To: rick@unix.macc.wisc.edu.UUCP (Rick Keir)
Organization: UW-Madison Academic Computer Center
Lines: 55

[ should the 64K Line Eater Bug be supported ? ]

A few concrete examples:

Example case 1:

I'm writing a data collection program;  one aspect of it would be
aided by the ListManager routines.  This program will run on a
small # of Macs;  it will be cost effective for the University to
simply restrict the program to only work on the new ROMs, so I am
not going to try and replace the ListManager stuff with equivalent
functionality.  On start up, it tests for the new ROM, and if it is
running on the old ROMs it will disable those routines and substitute
a crufty TTY style interface instead: see a list of your choices and 
type your response.  This is provided for the day when every lab Mac
is in the shop for repairs, and someone pulls out their personal 
machine instead.  Many functions will still work (printing,
data analysis, etc.) and even those parts which use list
manager routines *can* be made to work, although less conveniently
than usual. This seems to be a reasonable compromise position.
I can't justify making their lab pay for program code that *they*
don't need for their site, in the name of compatibility with older
machines.

Example Case 2:

On the other hand, I'm writing a program for my personal use also;
I am avoiding all 128K rom calls in it because I don't know what
machine I'll be using it on, and at least some of the ones around
here will not have updates.  Programming costs aren't important here;
this is hobbyist work.

Supporting the 64K roms requires asking these questions:

(1)  Just how much do I gain by excluding the 64K ROMs?  In case 1,
above, I save a lot of programming time, and don't exclude any
workstation that I know of in the lab I'm writing for;  but in case
2 the added functionality would be minimal compared to the restriction
of places I could use the program.

(2)  Can I provide a program that works partially on the 64K machine?
It's easy to test for;  in case 1 above there are specific features
that won't work, but the program as a whole will still run.

(3)  How much do I lose if I can't provide any support for 64K ROMs?
In case 2,  the loss is in my freedom to use my program: I'd rather
spend the programming time and be able to use it anywhere;  in a
commercial sense I'd look at the time cost vs. the loss of potential
market.

-- 
"I'll do it -- I've got the GUTS.  I'm the PRESIDENT."
"Maybe we should take that box away from him."  "Why bother?"
Rick Keir -- one floor up from the Oyster Tank -- UWisc - Madison
{allegra, ihnp4, seismo}!uwvax!uwmacc!rick