attrib command in XP?

  • Thread starter Thread starter Jim Carlock
  • Start date Start date
J

Jim Carlock

I can't seem to find the old DOS prompt attrib command in XP.

Am I missing an SDK thing?
 
Never mind, I found it. For some reason my path is messed up
and I'm not getting system32 in the path.

--
Jim Carlock
http://www.microcosmotalk.com/
Post replies to the newsgroup.


I can't seem to find the old DOS prompt attrib command in XP.

Am I missing an SDK thing?
 
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;

is the normal syntax for the first three entries of the System level
path env var.
 
Yes, they were there, but for some reason, the DOS prompt
was confused and didn't want to go through the paths. I checked
the path with the DOS prompt SET command, and the path was
listed, but for some reason it wasn't being processed. I started up
another DOS prompt and it worked in the new DOS prompt.

I thought my Attrib command walked away. I probably won't ever
see this error again. Definitely has me puzzled.

--
Jim Carlock
http://www.microcosmotalk.com/
Post replies to the newsgroup.


%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;

is the normal syntax for the first three entries of the System level
path env var.
 
: I can't seem to find the old DOS prompt attrib command in XP.
:
: Am I missing an SDK thing?
:
:

Just for curiosity, you should edit winnt\system32\config.nt and see
if the line

# NTCMDPROMPT

is #commented out or not

I think you definitely want to be running cmd.exe rather than
command.com

NTCMDPROMPT is commented out in Win2K by default. I don't know if
that has anything to do with your problem or not but it may.
 
Wow, I thought XP and Win2K went away from reading Config
and autoexec files.

The only active lines in the Config.nt file are:
dos=high, umb
device=%SystemRoot%\system32\himem.sys
files=40

That is weird. In the past for DOS, I used to set files to 100.
Haven't messed with that in ages upon ages.

Somewhere around 2000 when I moved from Win98 to Win2K.

Is the # a REM command ? All the other lines are all REMmed
out. Where have I seen # used as a comment character?

As a list of comment characters:

; <= assembly
// and /* */ <= c, c++, java, javascript
<!-- --> <= html
' <= VB
REM <= config.sys and autoexec.bat
::: <= This might have worked in config.sys files at one
time.
I have an old config.sys from 1994 lying in a
backup
folder.

My shortcuts are set up to cmd.exe. I didn't know command.com
was still around. Learn something new everyday. Thanks!

--
Jim Carlock
http://www.microcosmotalk.com/
Post replies to the newsgroup.


: I can't seem to find the old DOS prompt attrib command in XP.
:
: Am I missing an SDK thing?
:
:

Just for curiosity, you should edit winnt\system32\config.nt and see
if the line

# NTCMDPROMPT

is #commented out or not

I think you definitely want to be running cmd.exe rather than
command.com

NTCMDPROMPT is commented out in Win2K by default. I don't know if
that has anything to do with your problem or not but it may.
 
Yes, it went away from it for running the Windows OS ... but for the
environment used when calling the command prompt boxes, it uses these files.

Hope this is useful to you. Let us know.

rms
 
I knew I saw # as a comment indicator in a file somewhere!

Found it in the hosts file! Been a long time since I've looked
at one of those as well, but not quite as long as the config.nt.

--
Jim Carlock
http://www.microcosmotalk.com/
Post replies to the newsgroup.


: I can't seem to find the old DOS prompt attrib command in XP.
:
: Am I missing an SDK thing?
:
:

Just for curiosity, you should edit winnt\system32\config.nt and see
if the line

# NTCMDPROMPT

is #commented out or not

I think you definitely want to be running cmd.exe rather than
command.com

NTCMDPROMPT is commented out in Win2K by default. I don't know if
that has anything to do with your problem or not but it may.
 
Back
Top