Re: dir | more command is killing the command window

From: Olaf Engelke [MVP Windows Server] (oenews01_at_mvps.org)
Date: 11/15/05

  • Next message: Haim Beyhan: "Windows 2000 local accounts" 
    Date: Tue, 15 Nov 2005 09:21:55 +0100

    Hi again,
    pdabak@yahoo.com wrote:
    > When you do "dir | more" from command shell (cmd.exe) on a working
    > system, filemon generates write/read events on
    > \\.\Pipe\Win32Pipes.xxxxxxxx.00000001 from cmd.exe and more.com where
    > xxxxxxxx is the hex representation of process id of cmd.exe. On a
    > failing system, it generates only two events from cmd.exe on
    > \\.\Pipe\Win32Pipes.xxxxxxxx.000000001 i.e. Open and Close.
    >
    On
    http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/redirection.mspx
    it reads
    "The pipe operator (|) takes the output (by default, STDOUT) of one command
    and directs it into the input (by default, STDIN) of another command. "
    I am not sure, if it is possible to change the behavior of the pipe to get
    its input from something else than stdout. So if for example the output of
    these systems would be something different than stdout this could be a
    reason.
    But since I am not a programmer, I have no real clue, where to start the
    tracing without such a failing system in my hands.
    What is the output of the command SET?
    Are there any Access Denied errors in filemon?

    Best greetings from Germany
    Olaf

  • Next message: Haim Beyhan: "Windows 2000 local accounts"
    • Quantcast