My experience in using powergrep

If you use Windows2003, you will find that the system's search tool cannot search files by text. do not believe you can according to the following post to make an experimental http://www.cnblogs.com/cowbird/archive/2004/06/04/13374.aspx, because there is no text search, so to change something, it is difficult to locate in which file.

I happened to read the blog "musicland" post a few days ago, is to introduce the document search tool grep, http://blog.joycode.com/musicland/posts/14203.aspx I saw a little heart.

According to the muiscland post, I have made some practices. If you are also using the grep tool, this post may be of reference value.
The musicland post explains two methods (I personally understand ). first, get an authentic grep command. run cygwin to get a compilation environment, so that it can be used in cmd (but I can't install cygwin anywhere ). as a result, I used the second method based on the Windows grep tool. In the wingrep and powergrep tools, I chose powergrep because the powergrep version is newer (version 2.3.1, released on July 15, June this year ).

I am using powergrep2.2. After using it, I feel that powergrep is much faster than Windows's own search speed.

Some experiences with powergrep:
A's search results may contain garbled Chinese characters and the output font needs to be modified. (The locations are preferences-> results and files-> results font and text file font. Select a Chinese font)
B. It sets up a tool called editpad to edit the text, which needs to be downloaded again. I personally use ultraedit and can add it in the editors option.
C. I am using the trial version 2.2. You may want to crack it. I can find the crack.ProgramCurrently, only version 2.2 is available. the results of the cracking were not perfect. I found that the editors option cannot be configured after the cracking. depressing... (However, If you configure it before cracking, You can retain the previous configuration)

These are some of my experiences.