Damage NTFS

Will the following command work on an NTFS system?http://support.microsoft.com/default...kb;en-us;74038
Will it cause any damage to any files?

No, it won't hurt anything. Won't work either though because it's hardcoded to look for FIND and MORE in a C:\DOS directory (folder).

The following command will do pretty much the same:

for %x in (*.*) do type %x|find "whatever"

(Change that whatever to whatever string of characters you're searching for).

Thanks a lot...
Have you tried this (your) command yourself on an NTFS system?
Are you sure it can not change any type of files?

Quote:

---

Originally Posted by Robert M

Thanks a lot...

---

You're welcome. :)

Quote:

---

Originally Posted by Robert M

Have you tried this (your) command yourself on an NTFS system?

---

Yes, on XP PRO. (Also tested it on XP Home).

Quote:

---

Originally Posted by Robert M

Are you sure it can not change any type of files?

---

Yes, I'm sure. The TYPE command simply sends reads the specified file and sends the output to the screen, (usually*). No write/re-write operations are done to the original file.

The pipe ("|") through the FIND command simply takes what was sent to the screen (*by the TYPE command) and searches for the string specified.

Again, no alterations are done to the original file.

The only thing that is altered, is a a temporary file or two (in your %temp% directory) which are subsequently deleted when the command is done.

(Note that piping the output of the TYPE through FIND goes w-a-y, w-a-y back, to the very early DOS days. And it still works the same on XP as it did then).

Thanks,
My curiosity about where the message talked about in the following link originated is why I ask. I wonder if falcon2000 could locate the file which produced his error message about output destination ...seen or created
in the following old virtual doctor link.
http://discussions.virtualdr.com/sho...d.php?t=159976

I just spent about 10 minutes running through that 4-page thread and didn't see any mention of a related issue, (i.e., a problem redirecting TYPE output through FIND). Maybe I missed it?

No, you didn't miss it.

I think falcon2000 could at least locate the file that is issuing the message.