Script tasklist fails

Start a cmd.
Type "tasklist /?".
Note the syntax for writing filters such as IMAGENAME.
Write simple line of code to see if the internet browser is running: tasklist /FI "IMAGENAME eq iexplore.exe"
Get error message: "The search filter cannot be recognized."
Scour the net for why this is happening.
Discover lots of people it works just fine for.
Consult documentation at Microsoft.com.
Read the example: tasklist /fi "USERNAME ne NT AUTHORITY\SYSTEM" /fi "STATUS eq running"
Type the exact example.
Get the error message: "Microsoft users can't even check what processes are running from a simple prompt - have a free dildo."

Do I have to get XP Professional for this to work, or something?

>>9
What seems to be lacking in general, is DOS documentation for XP Home editions, which means that Microsoft figured you'd have to be a PROFESSIONAL in order to abandon the Windows GUI and want to open a DOS prompt.
The undocumented crippling of basic commands will of course also severly limit third party scripts in unexpected ways, but why would any Home user need to install or run any "PROFESSIONAL" scripts? *sarcasm*
The next time I buy a Windows edition, I'll dress up in a suit, and serve the staff my business card, stating "Professional DOS programmer at private business company".