> causes Windows to Crash even more and Microsoft get the blame

I'm sorry, but the phrase above makes it sound as if Microsoft had no part whatsoever in creating BSODs... I'm an NT Workstation user, and while I'll admit that it is 100 times more stable than 95/98, I can't help but think that this is because I'm typing on a VMS with a new shell. Even with this relative stability I just mentioned, there is no one but Microsoft to blame when Excel or Access crash on me. There's no excuse (except for hardware failure) for a program to crash, IMHO.

I have seen some good products come out of Microsoft. I think IIS is anoying as hell, and I personaly wouldn't use it, but I can't help admitting that I think its a good webserver. The same applies to the Proxy suite. Sure version 1 was sucky, but they made ammends with version 2.0. That's a pretty good product. All they really need is to get their act together with the OSs and applications.

You wanna know what MS products I love? Keyboards and Mice! That Intellimouse with the wheel kicks ass when changing weapons in Q3A. :o)

#!/home/bbq/bin/perl
# Trust no1!

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.