Originally posted here by paulie walnuts


Perhaps I will. I'm still wondering why the **** they got greens in the first place for them.




No one can disagree with that. Comment, question, suggest, and then let the person responsible for the tutorial make the necessary corrections. That should do the trick, unless the information provided was intentionally misleading. I doubt that is the case here.

`pw

The whole tutorial was crap. Most of it was nothing more than loose facts, and unneeded option with absolutly NO cohesion whatsoever. It didn't makes sense, it didn't provide accurate or correct information, etc, etc.

- I see the term "32bit, 16bit" tossed around dozens of times, yet no explination about what it is. (just as an example)

- Calling an API "a big scary word" is laughable. Unless you're a software developer, you probably don't know, want to know, or even give a **** what an API is. It means nothing to your average userbase. Not to mention his description is fatally flawed. Anyone who needs to know what an API is, or does, already knows what it is, and in most cases how it's used. (as another example)

- windows 3.x and 95 offering no security ... LOL, they don't offer any services. It's a workstation. Turn off FPNW and you have one of the most secure workstations MS has ever put out. Especially since 3.x didn't bundle WSH and VBS active scripting to it. Which means no lamer script virii. And in most cases no Mass Mailer worms either, as they cannot use a scripted SMTP engine. (yawn)