From jackoverfull@gmail.com Mon Feb 27 14:51:00 2012
Subject:Re: VB3 Main Stage Emergency parachute
Il giorno 27/feb/2012, alle ore 22.29, Gary Brumm ha scritto:
>
> OK non - virtual hardware....whatever either way the original diagnosis applies.
>
I see. So your information about Apple hardware was at least 7 years old…
add a few more years, go back to the year 1999 or so and your previous posts about freezes and your lack of knowledge about the existence of kernel panics finally start to make sense.
> >guilty of what ...not listening to options....
>
WHAT options?
> like I said throw your Widows away and use your iPod...it is apparently too complicated for you and you don't want to learn anything about it.
>
Your obstinate referrals to my presumed lack of mental skills and your constant use of stereotypes is only good at showing how do you think.
> > Gee, I don't know, maybe your drivers are corrupted, or your hardware is incompatible with what you are trying to do....
> >
> Again. You keep repeating the same thing...
>
> Maybe because it might be true...you apparently wouldn't know one way or the other...
>
Right. Indeed. Apart from the fact it doesn't make any sense whatsoever.
> > Do a fresh reload of the machine and see if you can track down the issue.
> >
> A reboot? Well, that's the only option after a BSOD... A reinstall? That's not possible on the Mojo, it ships with is no recovery disk of any sort, recreating the OS configuration from scratch would be a nightmare.
> And, anyway, the system can't become corrupted over time: the ssd is usually read-only, you need to enable write access to do modifications.
>
> I have seen firmware become corrupted....ROMS go bad so your point it?
>
Could happen, right. that's exactly what happened on most windows machines around, if you put it in those terms.
> Who saud anything about recreating the OS from scratch.
>
You used the word "reload"…Tell me what a "reload" should be when speaking about computers! I had to guess: you could have either meant a reboot (obvious choice) or a reinstall (good solution to postpone the problem in spite of a big loss of times, but not in this situation).
> As far as the MOJO goes you
> should be working with the manufacturer on that......and good luck with that,
>
should be working with microsoft, probably…there isn't a thing that crumar can do. Just take back my hardware if I really insisted.
But that's not what I wan't to do: as written before, I was well aware this kind of problems would occur from time to time, as they do on every windows based machine. But yours, of course.
> I was referring to a workstation scenario.
>
Who ever mentioned workstation, by the way?
>
> This thread is done as far as I am concerned,
>
You keep repeating yourself again! Is it done? That's OK for me.
> sorry I tried to help and it was a waste of time.
>
"Tried to help". Yeah. Right. In your dreams.
> If your Mojo doesn't work get something else that does. If you want to blame someone blame the manufacturer
> and not Microsoft...that is just ridiculous.
>
My Mojo works exactly as expected. I now have a lot more functionality than before (2 keyboards, presets, 2 sets of drawbars) and a lot of less thing that can go wrong while gigging (because 2 crashes in 7 months are still less than the VB3 crashes I had before…without even mentioning the fact that I now have less things to worry around: no midi cables, no external midi interface, no computer that can be walked over by the guitar player…). It is perfect? No. Very few things are perfect. Is it good? In my opinion yes, other may think otherwise. Is this what I expected? Exactly, nothing less and nothing more.
[Non-text portions of this message have been removed]