1st_read.bin File Checker 1.3 will not correctly identify these apps' binaries:

256byte (impossible?),
dcload (impossible?),
linuxdc,
luftvarg (impossible?),
rotozoomer (impossible?)

What happens is, it will say it's scrambled when it's really an unscrambled bin.  This is
happening because my program identifies an unscrambled bin by scanning for a certian
string, and if the string is found, it will say it's an unscrambled bin.  If the string
isn't found, it will say it's a scrambled bin.  The bins above with "(impossible?)" are
too small, and don't have any strings to be found.  Making it also impossible to manually
hexedit the bin to see if the file is scrambled or unscrambled.

In addition, Katana (DreamSpec, warez) and WinCE (Gypplay, warez) programs will not work.

If you notice any other bin that does not get correctly identified, please email me ASAP.

Sweater Fish Deluxe has found a new way to identify if a bin is scrambled or unscrambled, 
but is not as reliable as the way I have this program set up.  Although I did look at
DCLoad knowing about this new string, and you can correctly identify if the file was 
scrambled or unscrambled.

For more information on this new string, check out this thread:
http://consolevision.com/forums/YaBB.cgi?board=DC_Discussion;action=display;num=1056221943