Xref: utzoo comp.misc:7376 sci.electronics:8640
Path: utzoo!attcan!utgpu!watmath!iuvax!rutgers!att!cbnewsj!ncas
From: ncas@cbnewsj.ATT.COM (clifford.a.stevens..jr)
Newsgroups: comp.misc,sci.electronics
Subject: Re: Non-volatile Memory--EEPROM
Summary: Exactly!
Message-ID: <2335@cbnewsj.ATT.COM>
Date: 16 Nov 89 01:39:09 GMT
References: <1308@rodan.acs.syr.edu> <65243@psuecl.bitnet> <1230@corpane.UUCP>
Organization: AT&T Bell Laboratories
Lines: 23

In article <1230@corpane.UUCP>, sparks@corpane.UUCP (John Sparks) writes:
> In article <65243@psuecl.bitnet> peg@psuecl.bitnet writes:
> >In article <1308@rodan.acs.syr.edu>, pwasilko@rodan.acs.syr.edu (Wasilko)
> writes:
>  >>   Query: What is the current state of the art in non-volatile solid
>  >> state memory technology?
> 
>  >I don't know if you would consider it "state of the art" but EEPROM seems
>  >to be pretty well-liked right now.  I have databooks from SEEQ and
> 
> Don't EEPROMS also have a problem with a limited number of writes?
> That is, after so many writes to the chip, it begins to degrade?
> 
> are great for storing data that needs to be changed and non-volitile (such
> as modems use to save parameters) but probably not so good for use in RAM
> replacement where there is a constant read-write situation.
Exactly!  We use a EEPROM in our *MODEMS* to hold options and other such info,
but they do have a write limitation.  They are fairly slow on writes and
have a limited number of writes, but operate at the speed of the bus, forever
(As forever as any RAM!) on reads!
------------
Who, me worry?!?
	Cliff Stevens	MT1E228  att!cbnewsj!ncas  (201)957-3902