Search hex string doesn't find some input byte values

[j7n]

I am trying to search for file contents, and click the "It's a hex string", mode:normal, type:binary.

If the input string contains a certain byte value, it is not found.

For example: a 3254 byte file contains multiple occurrences of "96 01 21 7F" near the end. The program does not find it. But it is able to find "01 21 7F".

If I search for "96" in a set of random 6818 files (web cache), it returns only 1501 files. In reality 5394 files contain a byte equal to 0x96. Furthermore, if I search for either of these values 80,82,84,85,86,87,89,8B,8D,8E,8F I also get only approximately 1500 files, give or take a few. 81, 88, 8A, 8C return the correct number. But this pattern doesn't hold when searching for 2 consecutive bytes. The number of files returned is somewhat less if one of the bytes is 8X, or maybe any greater than 80.

Version: 22.80
OS: Server 2003 SP2

Last version known to work: 16.10 (must select binary mode)

[admin]

Interesting. Can you send me such a file for testing?

[j7n]

I can. But it is not a unique example of a file that is skipped from the results.

sj.package: 96 01 21 7F > not found
test81.bin: 7881BC > found
test87.bin: 7887BC > not found

sj.zip

[admin]

When I set Type to "Binary" it seems to work. Can you confirm that?

[j7n]

No. I can't find these search strings in 22.80 at all.

Here is how it looks.

https://i.imgur.com/u1d3QgC.png
https://i.imgur.com/2jAXmG3.png
https://i.imgur.com/fgVFRfU.png
https://i.imgur.com/LQuXFpF.png

I wouldn't be surprised if it's a regional setting on my computer. Previously I had a VisualBasic program stop working after I changed the decimal separator. lol. Maybe there is an unintentional conversion between code pages, which would affect the higher byte values only? I use windows-1257 and cp775.

[admin]

Attach images in the forum:

[admin]

Should be fixed in the next beta. Thanks, good bug!