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

Tip: Run a free scan for common Windows errors ad

re: CONFIG/AUTOEXEC.NT not run by command window Sunday, November 1, 2009 at 3:26 pm Posted by normanw (1284 messages posted) 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 [Reply or follow-up to this message] re: CONFIG/AUTOEXEC.NT not run by command window Monday, November 2, 2009 at 4:16 am 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 [Reply or follow-up to this message] re: CONFIG/AUTOEXEC.NT not run by command window Monday, November 2, 2009 at 4:56 pm Posted by Ricer46 (23825 messages posted) Well ,you're supposed to use CMD.exe and not command.exe On Monday, November 2, 2009 at 4:16 am, Kevin Carmody wrote: >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 [Reply or follow-up to this message] Tip: Use one of the [Reply or follow-up to this message] links above to add a message to this thread Search this forum Start a new thread on a different subject Report abuse of the forum Return to the Windows XP Discussion Forum