not actually to establish a blogging point where individuals can enrich their learns on facilitating and leveraging .NET-related activities most effectively
Holy cow, I wrote a book!
Yes, you can write a whereis program in 90 bytes but Windows Server 2003 and Windows Vista both come with a version of WHERE.EXE, so you don't even need the batch file any more.
WHERE.EXE
Neat, but still *far* from my infinitely-profitable program!
http://www.peetm.com/blog/?p=55
It seems that <i>where</i> was written on the cheap too:
C:\> where
ERROR: The operation completed successfully
And now, thanks to our friend the copy command, so does my XP machine :)
@David
Is that Vista? On Server 2003 I get:
C:\>where
ERROR: Invalid syntax
Type "WHERE /?" for usage help.
Vista SP1:
>where
ERROR: The operation completed successfully.
Now try
C:\>where where
for enlightenment.
Perhaps it can answer this age old question that comes up every time someone produces a batch file like the one referred to?
WHERE *secret_batchfile_advanced_syntax_guide*
So WHY does all Vista EXEs if run under XP give the "is not a valid Win32 application" error? What is the reason for the behavior? I don't wish to know the technical reason, I want to know did MS design it on purpose so people may not "get" and "use" Vista binaries in XP? Like how one can use msconfig from XP under 2000, did MS deliberately limit such use under XP?
> I don't wish to know the technical reason
Why not? Because that's the explanation (manifests) - not the conspiracy theory you obviously prefer.
[offtopic]
So WHY does all Linux EXEcutables if run under XP give the "*****" error? What is the reason for the behavior? I don't wish to know the technical reason, I want to know did Ubuntu, Redhat, etc. design it on purpose so people may not "get" and "use" Nix binaries in XP? ... did Linux community deliberately limit such use under XP?
[/offtopic]
@Paul Coddington
The syntax for Raymond's batchfile is actually included for a bit. If you run 'for /?' you get a lot of inromation about it :)
