Analogue-sequencer

Hi Colin,
    On my Production P3 with MemX added, I've just started to experience 
a peculiar issue. 
I've been running an older version of the P3 v4.0 beta, I think it's 
beta 22. I've been getting
ready for a live set this Saturday, so haven't wanted to upgrade until 
after I've done the show.

But this Weekend, when I went down to the Studio to practice with the 
others, my P3 was
showing some weird behavior.   On certain Banks, such as Bank 2 and Bank 
15, on
parts 2 & 4 or something like that (some important songs for us!), we 
weren't hearing
any sound. So I went in and edited the patterns and it just showed the 
first step with a
solid green repeating over and over.  So I then check, and see that it's 
got all the
steps set to "skip".  It was working fine, we turned it off and came 
back the next day,
and turned it on and it was like this.  So I try to turn off the "skip" 
and I can't turn
off the skip at all for these tracks. 

I had initialized the bank after my initial upgrade to beta 22, and it's 
been running fine
with no issues since that initial upgrade quite a few months back.   I 
went ahead
and did 2 sysex backups of the files and initialized the memory again 
and uploaded
the sysex files again and it was still doing the same thing.  So I went 
ahead
and re-initialized the memory again (F1 + 7 on startup) and uploaded a 
sysex file
from August, that I know worked fine and I had re-uploaded into the P3 
after the initial
dump and all was fine, but even with this known backup being used, the 
same Banks
and Parts do the same thing, Show all 16 steps in Skip and I can't 
remove the skip.

I'm guessing this might be a hardware issue, since a known backup is now 
showing the
same issues.  I was wondering if you can give any pointers on trying to 
see what's wrong?

Should I reset my MemX?  Could that be a possible explaination?
I have another MemX card for my DIY P3 that I'm hoping to still build.  
Should I try that,
in case it's an issue with the MemX card that I am currently using?

Should I try re-loading the OS?   

Any other pointers?   Hoping to somehow get this fixed before Saturday 
night :)



Thanks,
Dave