Yahoo Groups archive

Vintage Synth Repair

Index last updated: 2026-04-28 23:41 UTC

Message

RE: [vintagesynthrepair] Casio VZ and Atari ST/TT/Falcon questions

2005-03-25 by Ricardo Verschut @ Jura Music Production

Hi,

I know of an editor for the VZ1pro that works fine on TOS 1.4. I'm not sure 
if it will be compatible with the Falcon's OS. Neither do I know if it will 
work for other machines than the VZ1pro. I'll look it up over the Easter 
weekend and see if I can send you a copy by e-mail.

Cheers,
RVe



_____________________________________________________________
Als je wilt weten hoe het met Luke gaat;
de laatste nieuwe foto's vind je op:
http://groups.msn.com/GeorgeLucasVerschut/shoebox.msnw
_____________________________________________________________




>From: "Larry T." <larry@...>
>Reply-To: vintagesynthrepair@yahoogroups.com
>To: vintagesynthrepair@yahoogroups.com
>Subject: [vintagesynthrepair] Casio VZ and Atari ST/TT/Falcon questions
>Date: Thu, 24 Mar 2005 03:53:55 -0000
>
>
>Hello All
>
>Is anyone aware of a patch editor/librarian for the Casio VZ
>synths that runs on the Atari ST/TT/Falcon systems?
>
>Also, I have just received an "Atari TT Fast Ram board, 32Mb" that I
>aquired on eBay.  There is no documentation however and there is a
>four position dip switch.  On the front the board has "(C) Catch
>Computer, 12.01.93, Rev 1.4" and on the back is "CC-MegTT".  The board
>has a connector to plug into the TT's expansion bus, and 8 simm
>sockets.  Does anyone have any documentation regarding this board?  Is
>there any special software necessary to use it or will the TT
>automatically recognize the memory?  What size/speed simm's does it
>need?  And what are the dip switch settings?
>
>Any assistance is appreciated.
>
>Larry T.
>
>
>

_________________________________________________________________
MSN Search, for accurate results! http://search.msn.nl

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.