Hey Thomas,
Thanks for taking the time to go back and clarify your post.
I guess I should have explained a bit more - I agree with your statement "why does navx display them at all?" At first it seemed weird that it was reporting them and yet also reporting that the files are clean. The navx command should only report back the files it believes are infected, unless you give it the option to report back all files scanned (if you type in navx by itself on the command line, you can see the usage and all of the options/switches, -c is to scan compressed archives).
I'm sorry that I didn't first catch up on your conversation with Mike about your issues. I'm trying to encourage him to try to use this forums more, for reasons like this - we are trying to have more than 1 set of eyes on these forums in cases someone goes AWOL. If conversations happen too much off the boards, then it kind of shuts the rest of us out - not to mention other people who have the same problem and might get a good solution.
It's our fault for not having the right arm talk to the left arm on this - I apologize.
We are a small team, and I can guarantee you that it annoys all of us to have bugs out in the field. It's sometimes tough to prioritize what we work on and when we work on it, but we do care about customer issues. It's also very helpful to get feedback from (understandibly) upset/frustrated customers. We take it seriously.
It looks like it's definitely a false positive - and we are able to reproduce the issue using pjp's suggestion of the SlingboxPlayer.app.
It's interesting because it seems to only occur when you are scanning inside of Archives - we use a Library that is created and maintained outside of our team. We are going to ping those guys with the files that produce the FP and, hopefully, we'll be able to get this resolved ASAP.
Thanks again for all your help and continued patience.
Nick Uchida
Manager, SQA Engineering
Macintosh Products
