re: CONFIG/AUTOEXEC.NT not run by command window
Monday, November 2, 2009 at 4:16 am
Windows XP Annoyances Discussion Forum
Posted by Kevin Carmody
(2 messages posted)
Normanw,
Thanks for your reply, but after some more experimentation I did not find that changing
permissions had any effect on the problem. (Besides, I can't see why it would be
desirable to allow users to run a command shell without initializing it.) All users
have read and execute permissions for CONFIG.NT and AUTOEXEC.NT, and even giving
them full control makes no difference.
What does make a difference is using COMMAND.COM instead of CMD.EXE. In my CONFIG.NT
is a SHELL command that uses COMMAND.COM, and then the users were running CMD.EXE.
If they run COMMAND.COM instead, then AUTOEXEC.NT is run.
Kevin
> That is precisely what is supposed to happen. Only an administrator
> account has the necessary priviliges to execute those files.
> ‘There’s always tomorrow. At least, there always has been, so far.’ – Keith Waterhouse
> On Sunday, November 1, 2009 at 1:08 pm, Kevin Carmody wrote:
>>Hello everyone,
>>
>>I have a new XP system on which I have 3 accounts, 1 admin account, and 2 limited
>>accounts. When I start a command window under the admin account, CONFIG.NT and
AUTOEXEC.NT
>>are executed, but when I do the same under either of the limited accounts, CONFIG
>>and AUTOEXEC are not executed.
>>
>>CONFIG.NT and AUTOEXEC.NT are in %SystemRoot%\system32\. I am launching CMD.EXE
>>from a link, not a PIF. HKEY_LOCAL_MACHINE\Software\Microsoft\Command Processor\AutoRun
>>is empty and HKEY_CURRENT_USER\Software\Microsoft\Command Processor\AutoRun is
not
>>present for any user.
>>
>>Any ideas? TIA for your help.
>>
>>Kevin
|
All messages in this thread [show all]
 | |  | re: CONFIG/AUTOEXEC.NT not run by command window (Kevin Carmody: Mon, Nov 2, 2009, 4:16 am) |
|
