J
Jacques Schett
I have two Windows XP Pro systems on a domain that the command shell
does not work properly.
We use scripts to handle user rights on some poorly written apps
(security wise, poorly written...like QUickBooks) The script starts by
granting the user of this instance local admin rights. Then it
launches the app, then it resets the admin accounts and removes the
current user.
This works well on all but these two machines. What I get is scripts
that fail to work because the paths are implicit (i.e. I don't say
"C:\Windows\System32\Net.exe ..." instead I use "Net ..."
The PATH statement shows %SystemRoot%; %SystemRoot%\System32;... but
NOTHING works properly in the cmd shell.
How can I fix this short of reinstalling XP? Would SFC /ScanNow work?
I just hate to have to reinstall all the files since SP2 released (our
XP cd is slipstreamed with SP2 so at least I won't have to ins. the
SP.
Any thoughts are appreciated!
does not work properly.
We use scripts to handle user rights on some poorly written apps
(security wise, poorly written...like QUickBooks) The script starts by
granting the user of this instance local admin rights. Then it
launches the app, then it resets the admin accounts and removes the
current user.
This works well on all but these two machines. What I get is scripts
that fail to work because the paths are implicit (i.e. I don't say
"C:\Windows\System32\Net.exe ..." instead I use "Net ..."
The PATH statement shows %SystemRoot%; %SystemRoot%\System32;... but
NOTHING works properly in the cmd shell.
How can I fix this short of reinstalling XP? Would SFC /ScanNow work?
I just hate to have to reinstall all the files since SP2 released (our
XP cd is slipstreamed with SP2 so at least I won't have to ins. the
SP.
Any thoughts are appreciated!