Patches and discussion for Ensoniq VFX family

Hi there,
A couple of years ago or so I bought from Route 66 a couple of eprom chips for version 2.3 ROM chips for the basic Ensoniq VFX.

Recently I had the VFX serviced and had the keyboard calibration problem fixed on it.  I took the two eProms along with me to the specialist who sorted out the keyboard but he tells me that the code on one of the chips is corrupted - so the keyboard would not boot on version 2.3.

What I need are the two binary files so that the two chips  Hi and Lo
can be rewritten with an eProm reader.

Is there anyone out there on this list who has the files for version 2.3 on the VFX??  This is not the SD keyboard it is the basic VFX.

Have already emailed Route 66 in the US to see what they can do on this

Thanks in hopes
Simon
Milton Keynes UK

> Is there anyone out there on this list who has the files for version 2.3
> on the VFX?? This is not the SD keyboard it is the basic VFX.

Not that I'm exactly promising this, but I could probably look into 
dumping these from my VFX if the chips are of some standard type (like 
27c256 on the cartridges).

It's not just the harddrive backups that come handy every now and then ;)

.Arto.
-- 
http://amazingdiy.wordpress.com/
http://littlebitchard.com/

I guess it would depend how you dump the data.  The files that I would need would probably have a *.bin extension on them.  My understanding is that an eProm reader /burner is the standard way to extract these files from ic chips once they have been withdrawn from the keyboard itself.  But you may well know something I don't about this anyway - so if you have time please have a go if the chips are 2.3 version.  I don't think the resulting binary files are terribly large anyway.  Route 66 who sold me the chips in the first place must surely have these files.

Thanks very much for your interest and help anyway
Simon
Milton Keynes
UK




________________________________

 From: Arto <r2.koivisto@...>
To: Ensoniq-VFX-SD@yahoogroups.com 
Sent: Monday, 21 January 2013, 19:29
Subject: Re: [Ensoniq-VFX-SD] Ensoniq VFX eProm binary files version 2.3
 

  
> Is there anyone out there on this list who has the files for version 2.3
> on the VFX?? This is not the SD keyboard it is the basic VFX.

Not that I'm exactly promising this, but I could probably look into 
dumping these from my VFX if the chips are of some standard type (like 
27c256 on the cartridges).

It's not just the harddrive backups that come handy every now and then ;)

.Arto.
-- 
http://amazingdiy.wordpress.com/
http://littlebitchard.com/

> But you may well know something I don't about this anyway - so if you
> have time please have a go if the chips are 2.3 version.  I don't think

Yeah it's more about opening the synth and taking the roms to a place 
with the tools. Something I can't promise a "next day delivery" at the 
moment :)

.Arto.
-- 
http://amazingdiy.wordpress.com/
http://littlebitchard.com/

>> But you may well know something I don't about this anyway - so if you
>> have time please have a go if the chips are 2.3 version.  I don't think

Turned out my VFX had version 2.00 firmware, but I dumped it nonetheless:

http://dl.dropbox.com/u/3753457/diyblog/vfx-rom-200.zip

..and Rainer seems to have V2.10b available on his website, check "other 
ensoniq stuff" from the following page:

http://www.buchty.net/ensoniq/index.html

Anyone up for dumping and sharing V2.3? Is there some sort of a firmware 
changelog available somewhere, like what bugs have been fixed in the 
various versions?

If anyone has sound cartridge dumps, point them my way :)

--
.Arto.
http://amazingdiy.wordpress.com/
http://littlebitchard.com/

Where did this end up - chasing down 2.30? - I can read/write with equipment here and have searched to no end for 2.30 on the WWW. Only place seems to be R66 but no response there. Would collaborate with anyone who has 2.3 to read them. - Mail em, visit me (NW Indiana), etc.

These are 27C512 in the VFX.

My concern: eproms in general, certainly of the 72-90 vintage, are projected to have 20-30 year data retention. Just one bit changes in the code and something is no longer correct. So my VFX at it's tender age, is at risk. In reality, I dumped the chips and compared them to WWW sourced 2.10 code = perfect match. Whew, so have good code confirmed. But still, sure would like to update to the 2.30, for what it is worth even if I don't really gain function that I would actually use - more of an "anal" thing to get "up to date".

I have too many other irons in the fire to worry about going commercial on this, just want mine on 2.30 but will be glad to share in the process if we can just get this in hand. 

...ArtQ

--- In Ensoniq-VFX-SD@yahoogroups.com, "jammie" <jammie.emma@...> wrote:

>
> try syntaur they also do chips
> 
> route 66 dont answer emails much
> 
> but is the moderator of this site as he is the owner of it
> 
> richard if you read this message can you cantact the list
> 
> so simon can talk with you orpm him
> 
> i know that richard has had very bad health
> 
> but his wife also answers his emails
>   ----- Original Message ----- 
>   From: simon_ensoniq 
>   To: Ensoniq-VFX-SD@yahoogroups.com 
>   Sent: Sunday, January 20, 2013 6:52 PM
>   Subject: [Ensoniq-VFX-SD] Ensoniq VFX eProm binary files version 2.3
> 
> 
>     
>   Hi there,
>   A couple of years ago or so I bought from Route 66 a couple of eprom chips for version 2.3 ROM chips for the basic Ensoniq VFX.
> 
>   Recently I had the VFX serviced and had the keyboard calibration problem fixed on it. I took the two eProms along with me to the specialist who sorted out the keyboard but he tells me that the code on one of the chips is corrupted - so the keyboard would not boot on version 2.3.
> 
>   What I need are the two binary files so that the two chips Hi and Lo
>   can be rewritten with an eProm reader.
> 
>   Is there anyone out there on this list who has the files for version 2.3 on the VFX?? This is not the SD keyboard it is the basic VFX.
> 
>   Have already emailed Route 66 in the US to see what they can do on this
> 
>   Thanks in hopes
>   Simon
>   Milton Keynes UK
>