Perhaps this is a dig, perhaps not, but I've got one thing to say about this issue...

This would indeed be a fine attitude for anyone who's arranger (or any software, for that matter) normally works fine. BUT.... once you KNOW that it IS going to crash, once you trumpet on a forum just how constantly it crashes, once you have made it your mission in life to lambaste the poor thing on every single thread, whether it has anything to do with Ketron or not, then it is the fool who does not pay special attention to WHAT HE WAS DOING just before it crashes (in other words, AT ALL TIMES). Let's face it... you KNEW it was going to happen. It didn't happen unexpectedly

I haven't heard word one that this is occurring to you on a gig, so you can't say that you are under any particular pressure to rush through things and play the next song, the dancefloor isn't clearing out as you struggle to hit the buttons as fast as you can, the owner isn't glaring at you because of dead air... No, sorry, but I can't help thinking that, if one KNOWS something is going to crash and has all the time in the world, only a fool would NOT try to remember what they were doing to precipitate a crash.

Sorry to come back in on this note, but I have been lurking during my ban, and have been reinstated for nearly two weeks now but found little worth commenting on. But this interminable tirade against Ketron, whilst at the same time not apparently deeming it worth lifting a finger to try to help or troubleshoot is getting tiresome. For one thing, we have at least one member on this forum with an Audya that claims that his unit is pretty bombproof. But do I see any meaningful dialog between the two of you to try and track down what is different about HIS unit from yours? No... instead we get incessant whining and sniping and backbiting.

This is nonconstructive, my friend. If this were me, before we even get to the issue of remembering one's actions before a crash, I would be hounding DonM about what his serial number is, what type and serial numbers of the internal boards were, what type of hard drive it has, how he installed his new OS and many things like that to try and find out WHY his works and yours is a lemon. You know, Troubleshooting 101... (I might, for instance, try asking Don for a 'disk image' of his HD, and try overwriting that to a clean HD in your Audya, once you have ruled out any internal hardware differences).

And, sorry to repeat it, but you were the one to bring up the 'fool' moniker, if you KNOW your machine is going to crash, NOT trying to remember each and every one of your actions (especially as you have all the time in the world) is the foolish path. Surely you can at least narrow it down to whether they occur only on certain operations, certain touchscreen pages, certain conditions, and once you have this, you can then start to investigate further..?

If you had spent a tenth of the time you have spent flaming Ketron on this forum over the last few months on actually knuckling down and trying to discover why Don's works and yours doesn't, I would be very surprised if you hadn't discovered the answer by now... But perhaps it is easier and more fun to whinge and whine about it that actually TRY something yourself..?

Starting with making an effort, now you are aware it IS going to crash, to remember what you are doing while operating it... You really got something BETTER to do?

There is another old English saying... 'You don't get aught for naught'. If playing the Audya is something you would like to enjoy doing, perhaps just a LITTLE effort at this stage will pay off in the future? If not, just sell it, take it back to the dealers, get your money back, donate it to me (I guarantee I'd have the issue tracked down lickety split!), put it in a landfill, blow it up with dynamite, we really don't care...

Just give it a rest if you can't be bothered to even TRY yourself

An OS upgrade probably isn't going to solve your problems, if Don's is working, and yours isn't. This sounds MUCH more like a hardware issue, different HD type, different HD controller, corrupted OS or an OS written for perhaps newer components. But you'll never know if you simply wait for Ketron to fix it... Unless you try to get your money back IN FULL from the dealer claiming a warranty issue (they might sit up and take notice of that!). But instead, you hang on to it anyway, don't even TRY to troubleshoot yourself AND whine about it perpetually. Sorry, but that combination sounds pretty 'foolish' in my book.

You've got time to look me up on Facebook and plant my info here, but you DON'T have time to try and see what is the matter with your Audya?? Ship it to me, then. I'd be only too happy to track down the issues... (You might not get it back, though, but it doesn't sound as if you care, anyway!)