Command Prompt oddities

[InvaderPar]

So I've got this Autohotkey script that I use to replace explorer.exe. I'm trying to get a command line working (instead of the standard Win+R), however I'm running into some odd problems.

I'm an admin user, and if I run cmd from Win+R, I don't have any problems. I can run every command I can think of that exists in the System32 folder. For example, I can run 'sndvol' and 'soundrecorder' without problems.



However, whenever I run a command from Autohotkey (which is running as admin), or even run a command from the command prompt that was initiated from Autohotkey, some things don't seem to be recognized. For example, I can run 'sndvol' no problem, but I can't run 'soundrecorder'.




I did notice something though, when I run Autohotkey as admin, the command prompt inherits that and it gets "Administrator:" at the beginning of the window title. However, this isn't making a difference, because running Autohotkey not as admin produces the same results.

So basically, the question is, what can cause the command prompt to not recognize certain commands? Is it a privilege issue? Is it an issue with those commands? What can I try?

Very odd problem... I would greatly appreciate help.

 

[richc46]

When CMD is run, certain commands will be followed, regardless of the soruce. Other commands, you must right click and run as administrator.
Any command that affects the OS, must be run as administrator.

 

[InvaderPar]

It is running as admin. The title of the command prompt says "Administrator:"

I even turned off UAC and that didn't help. (Autohotkey is already running as admin)

 

[richc46]

Well lets find out
Test it from this account
http://www.sevenforums.com/tutorials/507-built-administrator-account-enable-disable.html?filter[2]=User Accounts

 

[InvaderPar]

Nope. Same results.

 

[InvaderPar]

I guess nobody's ever run into this issue before... If anyone could at least reference me to somewhere where I can learn about command prompt permissions (or anything that might be related to this issue), I'd most appreciate it.

 

[cluberti]

No, sounds like a path issue - run echo %path% in a regular cmd prompt, and then again in the autohotkey cmd prompt and compare the differences. I'll bet the autohotkey's path is different - you may need to pass the full path when calling .exes under a cmd prompt run as a different user (as "run as administrator" does).