Read is adding four bytes at 01B8

Bug #1770038 reported by Eric Durfee on 2018-05-08
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Image Writer
Medium
Tobin Davis

Bug Description

Been using version 1.0 for a year. When I switched computers a few months ago from Win7 to Win10 Home, I started getting verify errors after writing a file to a 128MB PC Card (various name brands) through a Digigear USB reader. I thought it was an OS glitch or something. The reader gets assigned three different drive letters. Today I read back the image into a new file and compared it to the original. I'm finding four consecutive bytes changed in the read back file starting at 01B8. They were originally 00's. This particular file has FB E9 42 7D. I checked some others and they all had changed values from 00's at this spot. Another file had 86 BD 03 71. Other files had different characters.

Tobin Davis (gruemaster) wrote :

This is good info. I wonder if Windows 10 is adding either a filesystem access timestamp or a filesystem checksum? Will require more research.

Changed in win32-image-writer:
importance: Undecided → Medium
status: New → Triaged
assignee: nobody → Tobin Davis (gruemaster)
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers