Well, I would assume that if it was a problem that it would have been FIXED, and addressed (and people wouldn't need to come to the forums to find out/figure out why Fusion 2.0 is suddenly crashing, and won't boot up).
Sure, there are hundreds of posts describing various blue screen of death issues with Fusion 1.1, 1.2, and various different versions, and all seem to be unrelated to my post (various idesys files, sound driver issues, etc.).
I've seen hundreds of different solutions, to include your idea of expanding cab files, and hunting/searching Microsoft KB pages (to search for an answer), and yet Etung posted something extremely simple (that I haven't read or found anywhere else), and I was just surprised that something so simple worked.
If it was "your idea" then why did you suggest that I go check out the Microsoft KB website first, and begin expanding CAB files? When something as simple as this would solve the problem?
No disrespect, but I've found that sometimes the VMWare staff seems clueless as to why their software is crashing, or not working properly. I read about 30-40 different posts, on various blue screen of death issues, and every single one of them had several posts each (with many solutions that didn't work, as I could read from the various responses), but all I did was follow up with a quick response letting anyone else know that this was a quick and easy fix, and that etung's suggestion did work.
It was much easier than spending hours and hours hunting down KB articles and in the end after wasting hours and hours of time, I would have realized that none of those would have resolved the problem (and would have just been wasted effort).
It seems to be related only to Fusion, so it seems to be a VMWare issues (a bug that still hasn't been fixed).
+
It's not like this is some big well kept secret... +
Well I would assume that if VMWare knew about it that they would have addressed the issue and FIXED IT (not just ignored the bugs, and left them). If VMWare Fusion is causing blue screens of death, then I would think that they would take the time to actually FIX the problem (instead of leaving it up to the users to hunt and poke through the forums and various other third-party websites to try to figure out why their software is crashing or why driver's aren't loading properly, or what all the other problems/bug fixes are.
I've never had to visit a vendor's website, and hunt the forums for 3-4 major "bugs" in less than a month. So instead of complaining that I didn't do a "good enough" job reading your mind (and it shouldn't be my job to hunt through hundreds of pages of various blue screen of death problems, system crashes, stop errors, and KB articles, just to figure out that VMWare has some major bugs that they choose to ignore and I wouldn't be in this forum if these problems weren't happening).
I've never had to join a forum before, just to hunt for solutions to try and figure out why a program isn't working properly, is crashing, or is causing blue screen of deaths. If I do a simple search there was nothing I could find concerning Windows Vista x64, and Fusion 2.0 errors.
So get off your high horse, and stop whining just because etung made a simple suggestion (that worked). That's all I asked for was a simple solution, to get this fixed. Etung made a simple suggestion, and I tried it, and I was merely responding that it worked (in case anyone else every runs into this same problem with Vista and Fusion 2.0).
I would think that you would focus more energy on FIXING the "known bugs" instead of just leaving the bugs in the program (as you've admitted that they've been around for quite some time I guess). Yes, I did see hundreds of blue screen of death posts, but it's hard to say what's related and what's not related. I'm not interested in spending thousands of hours reading each and every post in this forum, and trying thousands of solutions that don't work (every post I've read has had a different solution) and this was the first time I've seen a post as simple (and as concise) as etung's suggestion.
That's all I asked for was a SIMPLE and CONCISE answer. If you can't read a question, and give a simple and concise response, instead of yelling at users and telling them they should have sifted through the thousands and thousands of pages looking for an answer on their own, then what are you here for?
If you're not interested in helping, then just ignore my post. Plain and simple. If you can't give me a simple solution, and your answer is to expand cab files, or go check Microsoft's website, well neither of those were very helpful solutions. So just ignore my posts.
All I did was post a simple response that etung's solution worked, and it was a quick and easy fix.
If you can find an exact duplicate post to this one, then just post the link. I've searched hundreds of posts on various problems with the VMWare software, and tons of blue screen of death crashes (due to sound drivers, or some ide files, or various other reasons) but all of which were Windows XP related, or Fusion 1.1 related.
I didn't find a SINGLE POST about this stop error in Windows Vista, in Fusion 2.0, that was possibly related to a recent Windows Update. So quit whining like a baby, just because I gave Etung the simple "Thank-you" and "Correct Answer" to the question.
So just because your post about telling me to go find my own solution to the problem on the Microsoft Website wasn't very helpful, so next time just ignore my post. I'm glad I ignored yours, and didn't waste a whole lot of time searching KB articles (yes I did look at a few) but realized that it wasn't a Microsoft issue, because Vista was booting up just fine in the native partition (it was only a Fusion problem).
So if it's a Fusion problem, why would I continue to waste hundreds of hours sifting through all these thousands of pages when all I needed was a simple one or two line answer?
If you seem to be so smart, then why didn't you just suggest doing it in the first place? Why give me 3 or 4 wrong answers, and then get mad just because I give Etung the points for a correct answer?
If you saw that Etung posted the correct answer (and you posted 2 wrong answers AFTER his post) then why would you even make a post? You posts certainly weren't helpful or useful, so quit crying about it.
+*
if you what to add all
the number of times Eric and several others regulars have also posted
the same advice then it's probably in the hundreds. As a mater of fact
searching for STOP 0x0000007B or BSOD 7B or STOP 7B would have yielded
the delete the Boot Camp partition Virtual Machine*+
Well then why didn't you suggest it if it was such a simple answer, and why did you go on rambling about suggesting that I go check Microsoft's KB articles instead (after Etung already posted a correct response). So apparently you didn't know the solution to the problem (or the correct response) because if you did then you wouldn't have posted a suggesting that completely contradicts what Etung suggested.
So just because I post a quick response that Etung's solution worked for me, and resolved the particular problem that I was having, why are you getting so bent out of shape and crying like a little baby just because I didn't waste my time with your ideas, and if you seemed to "already know" that Etung has posted the correct response (because you're a genius) then why are you complaining? Why would you even post AFTER Etung already posted the correct answer?
If there are hundreds of posts that all have the correct solution (as you so claim), because I didn't find a single one... then why didn't you just post a link (refering to a post with the correct solution). I haven't found a single post that has had this exact same problem on Vista Ultimate in Fusion 2.0.
As you've even said yourself, hundreds of things can cause a stop error. So why would you make an ignorant assumption that all of these hundreds of posts on one particular stop error are ALL EXACTLY THE SAME (or even related)? Why would there be hundreds of posts then? I guess everyone is a moron except for you my genius friend. So instead of crying that I'm wasting your time, trying to fix your broken software, why don't you spend more time FIXING THE BUGS in your software so I don't have to BOTHER the developers trying to find solutions to all these bugs/problems/blue screen of death, etc.
It certainly isn't a physical hardware problem, so it's something to do directly with VMWare Fusion. So instead of whining that I don't know the "ins and outs" of your software (like you do) just because I'm not a VMWare employee, or a VMWare developer, and I don't just happen to know thousands of solutions to various KNOWN BUGS and KNOWN PROBLEMS off the top of my head, all I did was post a simple question, and all I ask for was a simple answer.
It's not rocket science. Why waste my time with your silly nonsense, if you're not helping? If you are so smart and already "knew" the answer to the problem (as you so claim), then why not just post the correct answer, and then I would gladly give you credit for the post.
As far as I can tell, you have never posted a correct answer to the specific question I have asked, so just because Etung did, there is no reason to get your panties in a bunch or start whining about it.
Just because you have a shiny gold trophy next to your name (and Etung doesn't) that doesn't mean Etung's solution isn't correct. It was a simple solution, I tried it, and it worked perfectly. So quit whining.
Stop acting like a little child. This isn't some big "competition" to see who can be right or wrong.
Etung posted a correct answer, and all I did was post a response (and awarded him the credit for the correct answer). It worked, and it solved the problem. Not a big deal. Quit acting like a baby, just because someone else answered my question, and gave a simple (and correct) answer.
If you already "knew" that Etung's response was correct, then why did you post? Why did you post twice? I read your posts, but I don't think searching the Microsoft KB's was the correct answer, and I do think Etungs response WAS the correct answer.
So if you knew that was the correct answer, why are you suggesting to expand CAB files, or suggesting that I go search Microsoft's website, if you "knew" the correct answer all along? (Mr Smart Guy).
Post a correct answer, I award you the points. It's pretty simple. Etung posted the correct answer, I posted a simple reply (letting him and others know that the solution Etung suggested did work) and I awarded him the "Correct Answer" points.
No reason to get bent out of shape about it. This isn't a competition. Someone other than yourself can be right once in a while ya know. Apparently you don't know all the right answers, or you would have posted it.
+* Anyway JSYK deleting the
Boot Camp partition Virtual Machine to allow Fusion to rebuild the
meta-data does not always work with STOP 7B BSOD's and you should count
yourself lucky it worked for you this time as there are no guarantees
it will work the next time because not all STOP 7B BSOD's are caused by
the same thing*+
Wow, you are a brain. Only a real genius would have figured that out. You contradict yourself even in your own posts.
First you tell me it was an "easy solution" and there are 80-100 posts that all have the same answer (but doing a simple search yielded not a single one). Then you tell me that I got "lucky" because "not all STOP 7B BSOD's are caused by the same thing.
Wow, you're a real genius brainiac. So why do you think I didn't just follow the instructions on ALL 100 other posts (especially since none of them were related to the specific problem I was having) and wasted weeks and weeks of my time playing stupid games, and trying things that don't work, that are completely unrelated to the problem that I'm having, and unzipping CAB files, and over writing system files (just for the heck of it) because someone else had a blue screen of death on a completely different operating system, running a completely different version of Fusion, and a completely different issue with sound drivers. Really doesn't make much sense, but after your ignorant posts, I guess that's your hairbrain explanation.
In the future, just ignore my posts Woody. Thank-you. I ignore yours (as most of the solutions you have suggested haven't worked for me). So it's just habit to read what you post, and ignore it.
So far Etung has posted some very useful and valuable information (and has solved my problems in a very clear and consise manner) and that's all I'm asking for. So if he posts an answer, and it works for me, and it solves my problem, then so be it.
I'll take a minute to at least thank him for his post, let him know that his solution did fix the problem, and I'll take the time to click the "Correct Answer" button.
Just because his solution worked, and yours didn't... doesn't mean that it's the end of the world for you. No reason to be so "competitive" and get upset just because Etung's solution worked (and yours didn't), that doesn't mean you have never answered a question correctly before. I see you have a gold trophy next to your name, so apparently you've answered your fair share of correct posts or whatever, but let Etung have his day. Ok, so Etung gave a simple and easy solution, so just let him have his day.
I gave the man credit (where credit is due) and just stop complaining that he gave me the correct answer. Apparently you didn't know the correct answer, or you would have suggested it earlier (right away), and wouldn't have wasted my time.
Etung got me back up and running fairly quickly, and that my friend is what is MOST important. I didn't have to waste several days hunting and poking, and Etung posted a solution that worked for my particular problem. Just like you said, it won't work for every single blue screen of death (Duh...), but if someone did a Microsoft Update 2-3 days ago, and just happened to have the EXACT SAME PROBLEM (100% exactly the same situation, and same exact problem) then yes, it might work for them as well. It seems to be a bug, and I was just making this bug known (and looking for a quick solution).
You didn't seem to know the answer, or have a quick solution (or quick and easy fix) but you did offer many ideas (and none of them worked). So don't be upset that Etung's solution worked (and was simple and easy) and it got me back up and running within seconds.
I'd venture to say
Well you don't need to "venture to say" much of anything. Your answer was wrong, Etung's was correct. That's all you have to "venture to say". Enough said.
That doesn't mean that you are always wrong and never right, it just means on this particular post, with this particular problem... your solutions didn't work, and weren't useful to me. Etung posted the correct answer (that worked). So I gave him credit for the correct answer. Not a big deal. No reason to cry about it.
+* sometimes it does just
come down to preforming the lower level diagnostics and following the
MS KB Articles so I wouldn't discount or knock that advice because when
the time comes that your only choice is going to be try what's in the
KB or rebuild the system*+
I didn't ask for the hardest/longest solution possible, and if you really truely want to actually HELP someone, why not try the EASY and SIMPLE things first (especially if you supposedly "knew" the solution but just chose not to post the correct answer, because you were TOO SMART to post the correct answer, so you chose to post 3 or 4 wrong answers just to throw me off, right?) Your logic makes no sense at all.
If you didn't know the correct answer, then how should I have known the correct answer? Quit whining quit complaining. Etung gave a very simple solution, delete two files, and then restart Fusion. It doesn't get much simpler than that, and it worked.
Just because I didn't spend hours (or days) going back and forth with you doing some stupid crazy "low level" diagnostics and spending hours on the phone with Microsoft Technical Support (on something completetly unrelated to them) and then wasting hundreds (or even thousands of dollars) in support costs, then finally Microsoft would just tell me that it's VMWare related, and try contacting VMWare (which I did). So yes it was a VMWare Fusion problem, and yes Etung's incredibly simple solution fixed the problem. I have a hunch that it would probably fix 85% of the problems, but you would rather spend hours/days/weeks going back and forth with users (wasting their time) instead of just giving them a clear, and simple (and CORRECT) answer.
I don't need 10 or 12 posts/dialogs just to get a correct solution. If I post a question, just post an answer. It's that simple. If it's correct, and it works, then I'm gone. I'll respond with a "thank-you! It worked!" and then I'm gone.
Unfortunately you can't seem to respond with a clear, or concise, or a simple, or a correct soluton. Your answers all seem to be long complex time consuming things (and none of them worked), so I just finally tried the quick and simple (and easy) thing that Etung suggested, and it worked. So Etung gets credit for the correct answer, and he's my hero for today.
So get over it, quick crying, and just work on giving correct answers (and be clear and concise, with a detailed step by step explanation if the user asks for it).
Just remember that not all of us are Mac OS X (or Windows) pro's. (Or VMWare God's). If we were, then we wouldn't be in this forum asking for help. We're just people that need help, and every user in this forum has a different level of knowledge (and experience with VMWare).
Since I'm a VMWare novice, and I've owned a Mac for less than a month now, and I'm still pretty clueless when it comes to a Mac (and VMWare Fusion), I may need a bit more "hand holding" than you are accustomed to giving. So I suggest you go find some professionals to help, and leave the novices like me alone, because you don't seem to have the patience (or skill) to help a novice.
+* it will be less painful then having to rebuild from scratch.
*+
I hate to say this, but a VMWare novice like me, shouldn't know that your ideas have been incredibly dumb, and if Vista is working properly (natively) then there would be absolutely no reason at all to "rebuild from scratch" and if you had half a brain, you would know this.
You'd also know that if Windows Vista was functioning properly and loading up correctly (outside of VMWare Fusion) that it would be a Fusion/VMWare problem. (Basic troubleshooting 101). I guess you must have missed that class.
No reason to start banging your head against the keyboard, it's not that hard to figure out that all it would take is something as simple as a uninstall/reinstall to fix the problem (even I knew that, and I'm a complete novice). So it's ashame that such a "genius" as yourself was busy conjuring up a plan on how to rebuild a system, or expand CAB files, or do all the craziest things I've ever heard, when all it takes is something extremely simple (and easy) like what Etung suggested.
That's all I asked for, a simple way to uninstall/reinstall Fusion. Etung told me how, and that's all I needed, and it worked for me. Thank-you. If you can't give a simple answer to a simple question, (or a correct answer) then just don't respond. Etung did a fine job, and I was just giving him the credit for the correct answer. That's all. Nothing wrong with me singing Etung a little praise for giving me a correct answer, and getting me back up and running as quickly as possible (without wasting anymore of my time).
So just pat Etung on the back, and say "Good answer mate... wish I would have thought of that..." and let it all go.
Sure, you win some, you lose some. You don't need to always be 100% correct, and it's life... sometimes someone suggest something that is much easier (and almost seems TOO SIMPLE, but it works perfectly). So don't get bitter or jealous. I'm sure you'll get a correct answer someday, or get an answer to one of my posts that works, and when you do... I'll give you the proper credit for the correct answer, and I'll also give you the points for the correct answer. So just because you were wrong today, and Etung was correct, no reason to get upset (or jealous) over it.
I just thank him for getting me up and running as fast as humanly possible (and not wasting anymore of my time in the process). I don't have time to be wasting/spending reading KB articles when I should be working. So if Fusion is broken, that means I'm losing money (because I can't work). So your concern should be HOW to get me back up and running (as quickly as possible) without wasting my time asking me to hunt down CAB files, or KB articles, or send smoke signals to the man on the moon for answers.
If you know the answer thand post it, if not then quit complaining that Etung did know the answer (or at least he thought he did, because he posted a quick response to my last response) and his solution did seem work etremely well). No reason to get mad that his answer was much quicker, easier, and it WORKED (and your answers didn't).
It's all about posting a CORRECT answer. I'd rather see ONE simple correct answer, then 5 or 10 wrong answers (or a complex talk about expanding CAB files) which I would have saved for maybe a "stage 3" or "stage 4" troubleshooting (after I suggested something simple like deleting the two files and restarting Fusion). If that didn't work, then (and ONLY then) move forward with more complex testing/troubleshooting.
because when the time comes that your only choice is going to be try what's in the KB or rebuild the system you'll be happy
Well apparently it wasn't time to read the KB's or rebuild the system, and just something as simple as deleting two files and restarting Fusion fixed the problem (and I'm thankful for Etung's solution, or I'd be listening to your hairbrain idea of rebuilding a system that doesn't need to be rebuilt). So lucky for me, Etung came out with a better/faster/more correct answer.
In the future you may want to try the easiest and simple stuff first, and try to make things as easy as possible on the users/consumers of your products. Start with basic trouble shooting, and give a few quick things that a user can try first, and then (and ONLY THEN) if all else fails, then you suggest KB articles (if you are clueless and don't know the correct answer) or suggest rebuilding a system (again because you are clueless and don't know how to fix the problem).
So just because Etung knew the CORRECT answer (the one that WORKED), no reason to get upset over it. (a 10 second solution that Etung gave was by far the quickest and easiest and on top of that it was the CORRECT answer, because it worked!)
Thanks again...