Process Explorer

**Snee** · 04-02-2005, 07:47 PM

Machine Debug manager.

Usually it's a pretty useless drain on resources, unless you are a developer of some sort, but apparently this needs it for something.

It's for script-debugging.

**100%** · 04-02-2005, 07:50 PM

Originally Posted by zapjb

Hey Ariel_001 where is the "%systemroot%\system32 folder" in XP? Probably should know myself. lol. Thanks.

C:\WINDOWS\system32
then look for taskmgr.exe

**peat moss** · 04-02-2005, 08:08 PM

Originally Posted by 15%

C:\WINDOWS\system32
then look for taskmgr.exe

First thing I looked for . Thought I'm "NOT" fucking with that !

But will try whats the worst thing that can happen ? Format big deal .

**zapjb** · 04-03-2005, 02:07 AM

Thanks folks.

**uNz[i]** · 04-03-2005, 02:52 AM

Environment variables - These are wildcard values that can be entered into Windows explorer on NT based systems.
They will always lead to the named directories, regardless of the drive letter Windows was installed to.

C: is used in the following examples, but the letter for the system drive could be R or even X - and it would work just the same.

%Type in this variable% = Displays this drive/directory

%SystemDrive% = C:
%SystemRoot% = C:\WINDOWS
%WinDir% = C:\WINDOWS
%Temp% or %Tmp% = C:\DOCUME~1\[user]\LOCALS~1\Temp from C:\Documents and Settings\[user]\Local Settings\Temp
%HOMEDRIVE% = C: The drive letter associated with the user's home directory
%HOMEPATH% = The path to the user's home directory (excluding drive):\Documents and Settings\[user]

There are other variables for NT and Win2000 systems too..
Google 'windows environment variables' for more info.