1.

Solve : MS DOS can not identify pipeline charactor?

Answer»

Hello all,

I am using Windows 7.

My Dos prompt is unable to identify the | character.
The following error occurs.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Anuradha\Desktop>time /t
04:24 PM

C:\UsersAnuradha\Desktop>echo |time
The system cannot find the path specified.


Can somebody kindly help me to resolve the issue?
Thanks in advance.

Anuradha
.check for an
echo.bat
echo.com
echo.exe
or a file just called echo
somewhere in the current directory or the path

Then try this to see if it also complains.

CODE: [Select]time /t|sortMicrosoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Anuradha>time /t|sort
The system cannot find the path specified.

C:\Users\Anuradha>time /t
09:35 AM

C:\Users\Anuradha>time /t sort
09:35 AM

C:\Users\Anuradha>time /t|sort
The system cannot find the path specified.
\

It also complains and as I feel the error is generated from the "|" pipeline charactor

Thanks.
Anuradha
Does it also complain when you type this?

Code: [Select]ver|sort
Yes.
The results attached for your referernce.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Anuradha>ver

Microsoft Windows [Version 6.1.7601]

C:\Users\Anuradha>ver |sort
The system cannot find the path specified.

C:\Users\Anuradha>


Thank you.
Anuradha
can you try these commands, in case there is an issue with your temp folder?

echo "%temp%"
cd /d "%temp%"Hi,
It seems to be there is no error with the temp folder.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\bgf478>echo "%temp%"
"C:\Users\bgf478\AppData\Local\Temp"

C:\Users\bgf478>cd /d "%temp%"

C:\Users\bgf478\AppData\Local\Temp>

It's an odd error.

Run this command (assuming your windows drive is c:) and let it run on reboot.

Code: [Select]chkdsk c: /f
See if that makes any difference.

Also try deleting files from temp, in case some process has created millions of files.

Code: [Select]del "%temp%\*.*" /s /qI suggested the %temp% issue but a pipe doesn't create temp files like it used to in Win9x etc. It uses the registry.

Maybe there is an issue with your registry being corrupted in some way. I tried to GOOGLE for the error but with no luck.
If chkdsk and freeing up temp files doesn't help then maybe a repair install is what I would try next.

EDIT: Check your %path% statement for illegal syntax or charactersHi,

Thanks for your suggestions.
Both chkdsk and deleting temp files did not resolve the issue.
Yes, it can be a registry issue.
Because my machine used to work properly earlier and the malfunctioning was observed from about four weeks time.

Yes. There is the option of formatting the machine which would be painful.
I WANTED to avoid that.

Here is the %path% variable content

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\bgf478>set %path%
Environment variable C:\Program Files\Common Files\Microsoft Shared\Microsoft On
line Services;
C:\Program Files (x86)\Common Files\Microsoft Shared\Microsoft Online Services;
C:\Program Files (x86)\IBM\RationalSDLC\common;
C:\Windows\system32;C:\Windows;
C:\Windows\System32\Wbem;
C:\Windows\System32\WindowsPowerShell\v1.0\;
C:\Program Files (x86)\IBM\RationalSDLC\ClearCase\bin;
c:\Program Files (x86)\Microsoft SQL Server\90\Tools\binn\;
C:\Program Files (x86)\IDM COMPUTER Solutions\UltraEdit\ not defined


Regards,
AnuradhaTry this:
Code: [Select]Type "ver" (without quotes) then press "ALT+0124" (without quotes) then type "sort" (without quotes) and press enter.Hi,

Thanks for suggestion.
But it too behaves same as earlier.


C:\AnuProjects\MPA3p0\CETK\CETK SRC\SensorMicroTest\Util\CETKUtil


Thanks.
AnuradhaVerify that the file "sort.exe" exists in C:\Windows\System32
You can use SFC.EXE to scan the system files after you open an admin elevated cmd prompt

Code: [Select]sfc /SCANNOW
I suspect that cmd.exe itself might be corrupt.


But if that fails you can try a system restore to a point four or five weeks ago.



Discussion

No Comment Found