On Tuesday (03/22/2022 at 08:09PM -0700), Glen Slick wrote:
> On Tue, Mar 22, 2022 at 12:25 PM Chris Elmquist wrote:
> >
> > On Tuesday (03/22/2022 at 12:20PM -0700), Glen Slick wrote:
> > > On Tue, Mar 22, 2022 at 11:56 AM Chris Elmquist wrote:
> > > >
> > > > Trying not to hijack the thread too
On Wed, 23 Mar 2022, Chris Elmquist wrote:
More interesting. If the programming algorithms remained the same then I
guess it is just an issue for the programming system-- when it auto-IDs,
it should display (and allow!) 27C256A instead of 27C256.
I guess the next question is whether the progra
On 3/23/22 08:18, Christian Corti via cctalk wrote:
> On Wed, 23 Mar 2022, Chris Elmquist wrote:
>> More interesting. If the programming algorithms remained the same then I
>> guess it is just an issue for the programming system-- when it auto-IDs,
>> it should display (and allow!) 27C256A instea
On Wednesday (03/23/2022 at 04:18PM +0100), Christian Corti via cctalk wrote:
> On Wed, 23 Mar 2022, Chris Elmquist wrote:
> > More interesting. If the programming algorithms remained the same then I
> > guess it is just an issue for the programming system-- when it auto-IDs,
> > it should displa
On Wed, Mar 23, 2022 at 10:38 AM Chris Elmquist via cctalk
wrote:
>
> On Wednesday (03/23/2022 at 04:18PM +0100), Christian Corti via cctalk wrote:
> >
> > I didn't even know that primitive EPROMs have device IDs...
> > Without looking for a data book, how is the ID mechanism implemented?
>
> Inte
