[whumphrey]

Originally Posted by midiwall

I understand this side and I agree with it as well. But... As an example, someone asked if the next step in the process after verifying on a VM was to recreate for the target hardware - you jumped him pretty hard and that spun into the spoon-feeding rant. The guy asked a straight question, he was basically asking if the XPe image had to be re-genned; it was clear to me that he didn't understand the core process and needed one small line connected.

Well if he had done one simple google he would have had his answer and not needed to ask the question! Thats the reason he got a slating, because it was the first thing i did, just to check if someone had already covered that! If he had done any research on XPe he would have known the answer.....

Originally Posted by midiwall

Well, it depends on what you were looking to accomplish with the docs. Is it a tutorial, an overview, a conceptual bullet list, etc?

If you look at my post Windows XP Embedded - HOWTO
it states :

I quickly whipped up my yesterdays findings on using Windows XP Embedded and VMware.

I would like to keep this one and the XPe and Centrafuse tuts separate as they not really the same thing. One is how to use XPe and the other would be how to get CF to work with XPe.

Originally Posted by midiwall

If it's a tutorial then it really should be step-by-step through the process explaining the WHY along the way - "WHY are you using a VM?" "WHY XPe?", along with a good dose of WHERE - "WHERE do I get the tools?", "WHERE do I get the core XPe image?", and finally HOW - "HOW do I determine what drivers I need for _MY_ hardware?".

Well, if no one gives me feedback in that forum or in PM how am I meant to know?

Originally Posted by midiwall

As it stands now, the document spends more time explaining how to create a VM than anything else.

Thats all that the document is meant to do, hence the title "How to use Windows XP Embedded using Vmware Workstation 6.pdf"

Originally Posted by midiwall

If you don't mean for this to be a tutorial, then declare it as just a high-level overview - in the document itself - and clearly state that it's only meant to be a starting point, _and_ state that you don't really have the time/patience to answer questions. It's okay if you take that line, but as it is now, no one here knows that about you.

I do have the time and patience to answer any questions as long as the person asking them is asking relevant questions that are not already been answered.

I always used to say to people that came to me with "I need to ask you a stupid question" that there is no such thing as a stupid question, over the past years I have noticed the M$ community asking stupid questions..... I now do be leave people ask pathetic idiotic questions as its there right in front of them!!! When i lived in a third world country and not everyone had access to the net or limited access I could understand. But asking a question on a forum because you to bloody lazy to research it is no excuse. You asking on a forum so you have internet access, you just to bloody lazy to research your ****.......

Originally Posted by midiwall

The overall effect right now is that you've tossed folks a large bone, asked them to come feed off of it, and are then kicking them in the face when they show you how hungry they are.

Originally Posted by midiwall

Thanks for being open to talking about this side of your efforts.

Who said i was open for talking? Just kidding, yea if i was such a prick as most people make out I guess i would not be open about it.... My main thing is people don't spend anytime before asking questions is what gets my beef.......

--me
P.S. One just to stir things up