Strings v2.40By Mark RussinovichPublished: April 24, 2007 IntroductionWorking on NT and Win2K means that executables and object files will many times have embedded UNICODE strings that you cannot easily see with a standard ASCII strings or grep programs. So we decided to roll our own. Strings just scans the file you pass it for UNICODE (or ASCII) strings of a default length of 3 or more UNICODE (or ASCII) characters. Note that it works under Windows 95 as well. Using StringsUsage: strings.exe [-a] [-b bytes] [-n length] [-o] [-q] [-s] [-u] <file or directory> Strings takes wild-card expressions for file names, and additional command line parameters are defined as follows: | -s | Recurse subdirectories. | | -o | Print offset in file string is located. | | -a | Scan for ASCII only. | | -u | Scan for UNICODE only. | | -b bytes | Bytes of file to scan. | | -n X | Strings must be a minimum of X characters in length. |
To search one or more files for the presence of a particular string using strings use a command like this: strings * | findstr /i TextToSearchFor .gif) Download Strings (41 KB)
|