Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!uunet!munnari.oz.au!uniwa!andreww
From: andreww@uniwa.uwa.oz (Andrew John Williams)
Newsgroups: comp.sys.m68k
Subject: Re: Programming Roms/Eproms/Pla/etc
Message-ID: <1991Apr29.010431.12127@uniwa.uwa.oz>
Date: 29 Apr 91 01:04:31 GMT
References: <91107.091241SCP100@psuvm.psu.edu> <1991Apr27.060346.25929@netcom.COM>
Organization: University of Western Australia
Lines: 15

mcmahan@netcom.COM (Dave Mc Mahan) writes:

>the appropriate alogorithm.  I don't know why Data I/O doesn't do this
>automatically, but they don't.  It KNOWS the proper ROM ID code for the 
>chip in the socket, why don't they just use the right algorithm?  I guess
>it could be difficult to even select the proper socket (the Data I/O 29B
>programmer has 6 or 8 sockets, all different sizes) and read the ID code
>without risking damage to the chip, but it would be nice if they could.

Could it have anything to do with not knowing where A9 is (or even if
the chip has a signature mode) until you know what the chip is? I've
seen A9 move around quite a lot.

John West (stealing Andrew's account)
Why is a fish?