I am have been meaning to ask you about it but I got caught in a time
crunch.

We are building more Drivers in March, so, because Production has a lot
of 27256s I changed the Driver Sound Board so it divides the Sound Wave Roms
in two banks which can be independently selected to be 27512s or 27256s. 

Bank 1 contains eight sockets and Bank 2 contains four sockets. This is
because the existing sound data takes four 27512s which will be replaced with 
eight 27256s. The Hard Drivin' upgrade kit will include additional ROMs

If we are to make a 256 version of the sound roms, then we will need to do
a formal release of these parts. I assume you have already selected the 
program part numbers for these new codes, (which is ok), what I need now is 
formal documentation and memory masters to complete the release. As an option
you can submit a CER just to add the part numbers to the AVL, for the parts
planners over in MFG and complete the release with memory masters at a later 
date. Let me know what you want to do.


                                                                 RLO

I am have been meaning to ask you about it but I got caught in a time
crunch.

We are building more Drivers in March, so, because Production has a lot
of 27256s I changed the Driver Sound Board so it divides the Sound Wave Roms
in two banks which can be independently selected to be 27512s or 27256s. 

Bank 1 contains eight sockets and Bank 2 contains four sockets. This is
because the existing sound data takes four 27512s which will be replaced with 
eight 27256s. The Hard Drivin' upgrade kit will include additional ROMs
which will be 27512s in order to be compatible with the Sound Boards in
the field as well as the new boards.

The 27256s contain the same data as the 27512s in the last Rev only split
up. I have prepared documentation which I will give you tomorrow (Friday)

The other two parts are programmed GALs. I have a lot of questions about
how programmed GALS are released and bought (because we buy them programmed).

	Do we provide them with a programmed part or a computer file?

	What if we want the security fuse blown?

	Do they test the devices with our test vectors or do they generate
	their own? (Do they test them with anybody's test vectors?)

By the way, I have programmed the part's pn in the User Signature bits.
Unfortunately the Data I/O cannot read them except as fuses in ones and
zeros.


	Jed