Welcome!

By registering with us, you'll be able to discuss, share and private message with other members of our community.

SignUp Now!

Corruption from FFIND?

May
12,930
170
I issue:
Code:
ffind /e"." /m /s c:\windows\system32\*.log

The first few files returned are OK.
1523750617116.png


But then it finds
1523750669790.png

That's a rather odd file, being a mixture of binary, ASCII, and Unicode. The one (?) line printed goes on for, apparently, a little more that 4096 characters.

The next file found has this name:
1523750129782.png


The rest of the files found have similarly corrupted named. When I get back to the prompt, the prompt itself is corrupted, as well as much other output.
1523750523474.png
 
This is probably the same thing you've reported before - you've got an ANSI sequence in one of your binary files.
I can understand that corrupting my prompt. But how would it corrupt other output, like that (last pic above) of SET and WHICH?
 
Probably because you're changing the character set (ESC N or ESC O). See your numerous previous messages on the same subject.

Indeed! After things are fouled up, I can set it straight again with
Code:
echo ^e(B
Thanks.
 
Ah HA!

Something similar happened to me a few weeks back, but I didn't remember the details of what I had done so I couldn't reproduce it. It didn't happen again, so, while mystifying, it fell "off my radar."

Mystery solved!
 

Similar threads

Back
Top