Slow DIR command

  • Thread starter Thread starter Mike
  • Start date Start date
M

Mike

I was hoping someone could help me out with this problem
I'm having with Windows XP Professional.

Basically, we have a Windows NT 4 Domain / Server. The
clients are a mix between Windows 98 / 2000 / and now XP.

A lot of the work we do requires "dir /s" commands on a
mapped drive while we are in a DOS window (the mapped
drives are mapped to the server). When I execute that
command on the Windows 98 and Windows 2000 computer, it
works fine.

When I execute that command on a Windows XP machine, it
works but the screens keep pausing... in other words it
doesn't just fly through the directories like in the other
2 operating systems. (Which is odd to me since I thought
that 2000 and XP were based off the same thing.)

I've tried this using both cmd.exe and command.com.

Any help would be appreciated.

You can respond here, or e-mail me.
Thanks in advance.
Mike
 
Mike said:
I was hoping someone could help me out with this problem
I'm having with Windows XP Professional.

Basically, we have a Windows NT 4 Domain / Server. The
clients are a mix between Windows 98 / 2000 / and now XP.

A lot of the work we do requires "dir /s" commands on a
mapped drive while we are in a DOS window (the mapped
drives are mapped to the server). When I execute that
command on the Windows 98 and Windows 2000 computer, it
works fine.

When I execute that command on a Windows XP machine, it
works but the screens keep pausing... in other words it
doesn't just fly through the directories like in the other
2 operating systems. (Which is odd to me since I thought
that 2000 and XP were based off the same thing.)

I've tried this using both cmd.exe and command.com.

Any help would be appreciated.

You can respond here, or e-mail me.
Thanks in advance.
Mike
Click to expand...

The WinXP kernel is a later version of the W2K kernel, but lots
of non-kernel stuff was changed. Don't ask for a list of what
was changed, since I'm sure that not even the NT kernelking knows
{feel free to speak up, Dave, if I'm wrong again}.

Try this in a CMD window: "Set DIRCMD=", then try "DIR /S" again.
I'm guessing that somebody did a "Set DIRCMD=BunchOfSwitches"
which disabled the subsequent /S of your "DIR /S" command.

<SemiRant>
IMHO, the DIR command is broken in W2K and in XP, in that the
Set DIRCMD=whatever does not work as advertised. Not even close.
</SemiRant>
<FullRant>
I do not believe that WinWhatever will ever become a viable
OS for an enterprise without a rich, documented, and debugged
batch capability.
DCL would be a good model, and many M$ programmers already know
about it.
</FullRant>
 
-----Original Message-----


The WinXP kernel is a later version of the W2K kernel, but lots
of non-kernel stuff was changed. Don't ask for a list of what
was changed, since I'm sure that not even the NT kernelking knows
{feel free to speak up, Dave, if I'm wrong again}.

Try this in a CMD window: "Set DIRCMD=", then try "DIR /S" again.
I'm guessing that somebody did a "Set DIRCMD=BunchOfSwitches"
which disabled the subsequent /S of your "DIR /S" command.

<SemiRant>
IMHO, the DIR command is broken in W2K and in XP, in that the
Set DIRCMD=whatever does not work as advertised. Not even close.
</SemiRant>
<FullRant>
I do not believe that WinWhatever will ever become a viable
OS for an enterprise without a rich, documented, and debugged
batch capability.
DCL would be a good model, and many M$ programmers already know
about it.
</FullRant>
Click to expand...

Thanks for the reply, but I've tried both having a DIRCMD
enviroment variable, and I've also tried it without one.

I started to think it might be network latency, but I don't
think that's it because it is working fine on 98 /2000. I
just feel like there is something I'm missing.

The network browsing was slow, but I fixed that by turning
off Web Client and the Indexing Service.

There has to be something that is causing this dir /s to
make the screen pause.

Any other suggestions?
 
-----Original Message-----


Thanks for the reply, but I've tried both having a DIRCMD
enviroment variable, and I've also tried it without one.

I started to think it might be network latency, but I don't
think that's it because it is working fine on 98 /2000. I
just feel like there is something I'm missing.

The network browsing was slow, but I fixed that by turning
off Web Client and the Indexing Service.

There has to be something that is causing this dir /s to
make the screen pause.

Any other suggestions?
.
Click to expand...

I think I finally found the solution to my problem. If
anyone else experiences this, you can try this solution here:

http://support.microsoft.com/default.aspx?scid=kb;en-us;177266
 
Back
Top