View Single Post
  #7  
Old March 8th 19, 09:49 PM posted to alt.windows7.general
Paul[_32_]
external usenet poster
 
Posts: 11,873
Default Is "C:\Windows\System32\NUL)" a good file?

Zaidy036 wrote:
I have Googled but cannot find an answer:

Windows 7 Home SP-1 64bit and I see a file named
"C:\Windows\System32\NUL)".

Since it has a ")" at the end of its name I am wondering if it is a
"good" file.


So you malformed a command line expression that
was attempting to redirect output to /dev/null, like this.

NUL


In Windows, NUL is the equivalent of Linux /dev/null.
You can redirect stderr or stdout to NUL, to make
an application "quiet".

So the closing parenthesis was likely some sort of attempted
"pipe" and "redirection" which didn't get quoted properly. The
person doing this, was running an administrator command prompt
at the time.

If the attempt had pointed at NUL instead of NUL)
then there would have been no output file generated.
As "NUL" is the bit-bucket.

As far as I can tell, that malformed filename is valid. The ")"
is not reserved. So yes, it's a good file, and likely contains
text from the failed command formulation. Rename the file
and load into Notepad.

https://docs.microsoft.com/en-us/win.../naming-a-file

"The following reserved characters..."

Paul
Ads