PSR-8000 - is there an OS firmware update?

Started by guyfingers, December 28, 2017, 03:07:06 PM

Previous topic - Next topic

guyfingers

Hi there!
First post so be gentle!
I've actually got THREE PSR-8000s now. First one in 2001 which was my gigging workhorse for 15 years before it virtually fell to pieces with the cracks!
Got a nice 2nd hand one last year and another one this year which was too good a deal not to take.

So when I try to load my custom sounds via HDD or FDD into the new one (which work with the previous two) they're all corrupted and actually make the keyboard lock up.
Strangely, when I make new custom sounds and store them in the same keyboard, there's not a problem.

I wonder is there's an OS Update for the PSR-8000? although as I'm writing this, surely if the sounds work on my 2001 one, then they should work with this new one!!!

Any ideas on the corruption issue?  RAM/ROM?

Thanks again - any help would be appreciated.

OregonJim

Have you done a factory reset on the new one?  Try starting from ground zero to eliminate other variables.

frankmusik

The Update for PSR-8000 was a Eprom Update ... so it is not easy - or even possible - to get one in these days ...

greetings from germany
frank
Genos and Tyros /PSR Support in Germany - Europe with more than
280 keyboardscouts helping in D-AT-CH-NL at your home!
Monday 18:30 (6:30 pm german time) Live tips on youtube https://www.youtube.com/channel/UCBxOTmwqvDGu5QavFWeaQfQ

guyfingers

Quote from: OregonJim on December 28, 2017, 03:54:24 PM
Have you done a factory reset on the new one?  Try starting from ground zero to eliminate other variables.

Thanks OregonJim (and lovely to see you have an Arp Axxe - I used to have an Odyssey)
I've done the usual thing - pressing top C while switching it on to reset all data but when loading old sounds through FDD, I'm still getting corruption then lockup.

Incidentally, I did a backup to separate floppies from both PSR1 and PSR3 (PSR2 is at my gfs) and the only difference I could see was that

PSR1 showed the DISK.MNG file as  Ver0.66 Rev0.00

and

PSR3 showed the DISK.MNG   file as Ver0.61 Rev0.00

Is this something that could be changed? and how?

Finally, I just tried something which would lead me to believe that the RAM is not the problem, but the FDD is.

I quickly created a load of custom voices, stored them, then backed up to the internal HDD which I installed today. No corruption on any sounds!!
So the FDD and/or management system is causing the problem.

I forgot to mention that prior to all these shenanigans, I installed a USB/virtual floppy unit (I'm sure you've all seen them) HOWEVER in my haste and lack of good light, I accidentally connected the data ribbon cable askew (i put the top row of sockets on the bottom row of pins ie halfway down) - When it didn't work, I opened the unit up, saw my error and connected it properly.
The USB thing worked (after much research on the program needed) - well, worked playing Midifiles but not saving/loading custom sounds and backup of whole system.

As I thought it was the virtual floppy that was the culprit to the corruption, I reinstalled the old FDD and of course encountered the same problem. The only annoyance is that I never tried to load the old sounds/system via FDD BEFORE I mis-installed the USB so I don't know if it was already not working properly!  :(

SO, in conclusion;

a) Is the problem the version of the disk management file/system? If so, how can I fix this?

b) Have I knackered the disk management circuitry by installing the virtual floppy and/or installing it incorrectly?

Sorry for the long post and thanks in advance for your patience and expertise :-)

Guy


guyfingers

So after much shennanigans, it has been determined that it IS a firmware/os problem.
See details here.
https://www.psrtutorial.com/forum/index.php/topic,42329.0.html