> Well, I just experienced it too. Some report the problem > spontaneously going away. It only happens when grepping binary files, > and only -7 and not -5. This is on an ultra5. That is my experience. I've gotten it with ascii files, too, on an ultra1. -5 works flawlessly. I didn't see any problems when grep was reading from stdin, only when filenames were specified on the command line did it result in an error. Eric