Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!mordor!sri-spam!sri-unix!ctnews!pyramid!prls!philabs!sbcs!root
From: root@sbcs.sunysb.edu (SBCS Systems Staff)
Newsgroups: comp.sys.amiga
Subject: Re: Autoconfig for expansions
Message-ID: <985@sbcs.sunysb.edu>
Date: 23 Feb 88 17:59:27 GMT
References: <1408@sugar.UUCP> <507@xicom.UUCP> <2507@tekig4.TEK.COM>
Organization: State University of New York at Stony Brook
Lines: 14
Keywords: autoconfig hobby
Summary: EEPROM (actually stable storage) autoconfig

In article <2507@tekig4.TEK.COM>, brianr@tekig4.TEK.COM (Brian Rhodefer) writes:
> peripherals".  This wonder would include (or perhaps consist of)
> a battery-backed CMOS RAM or EEPROM to hold autoconfig code

	I had proposed this same idea to folks out at Los Gatos - they
	didn't like it too much.  At Ameristar, we wanted to use the idea
	to provide a user configurable network boot for the Amiga.  I 
	personally feel that the idea has a lot of merit - perhaps enough
	that CA should provide a largish EEPROM on the next cut machine.
	This way, each vendor that wants autoboot, etc would provide an
	EEPROM'able driver that could be loaded at user discretion into
	the machine.  8K EEPROM's are pretty cheap in volume these days..

						Rick Spanbauer
						SUNY/Stony Brook (& Ameristar)