As Joachim mentioned, the article is quite out of date.
If you're running on Windows 2000, yes, you might need to do this, find an old version of Sysinternals Process Explorer (12 does still work, and has both Image Path and Command Line options), or use
wmic /node:"server" process
from a more current machine (using an domain permissioned account, or using wmic flags to use a local account and password with sufficient permissions), which gives image path, command line, and processid.
Windows 2003 R2, same as the above, but wmic will run locally as well.
Windows 2008 is probably like 2008 R2.
Windows 2008 R2, in Task Manager, select View, Select Columns, and pick either or both of Image Path Name, Command Line.
Windows 2012 is also probably like 2008 R2.
In no case should trolling through multiple SQL Server log files be required or efficient.