Opslog fix for binary files

When updating an existing binary file, an opslog with count of 1 instead of 0 was created