Hello RJKinsman,
yeah - another hostie with a Pre :-)
You are talking about an S0C4 on mainframe... great, I also think here we have a similar problem. But on Mainframe to solve such an error we don't need as long as motionapps :-( Sometime it must be solved or to work around within a few hours!
And yes, after 1.3.1 I also get those annoying messages about 'no classic certification' instead the message 'there is an update available'(which rises once during start) under 1.1.3 (in Europe).
I think there is a single function inside classic that destroys the memory itself. I tried with a hard reseted classic and the problems also appears from time to time.
But meanwhile I don't try it longer - its the job of motionapps.
If they don't come out with a stable release soon, they'll lose a lot of customer!
Regards Klaus
|