You senior engineer/programmers (who rarely burn roms)
	probably have not run into this problem, but the less
	fortunate staff who are blessed with using the DIO (every-
	ones favorite machine) are familiar with this scenario. 

	 DIO claims that the roms are non-blank, you know that you've
	erased them and wonder what's wrong?  Try going out of the
	COMPUTER-CONTROL mode (using up/down keys on DIO) and do a
	BLANK-CHECK, you'll be happy to confirm that your roms are 
	indeed blank.  Now if you resume RS232/COMPUTER-CONTROL mode
	and try to program those parts it'll be a happy camper and
	so will you.

	 Why does the DIO work this way?  Any ideas?

	Farrokh