Trying hex-editing to fix the date-time data in file which was generated while the computer system clock was wrong. Some tutorial will be helpful appreciated after my attempts so far.

[screen shot attached-- WRONG DATE-- surrounded in bold-red box]

Screenshot of incorrect dates in Hex Editor

My attempts:

  • Changing the text by typing in the right characters:-- doesn't work, date turns into "not available" when file is opened with the OEM software.

  • Deleting all boxed text and typing in the right date:-- file won't open at all using the OEM software.

  • NOTE: for the editing by simply typing in new characters (replacing the old), the applied edits correctly shows in the OEM software only if the new date-time is at a future point relative to the existing "Dec 30, 2015 03:23:10" – qrst Jan 4 '16 at 5:08
  • 3
    I see this is from the program Sciex Analyst. What does the function call-stack look like when FMWIFFCompDocNTDriver.dll!GetFieldC_csChecksumTimeStamp is called? – Jason Geffner Jan 4 '16 at 15:30
  • is there some sort of CRC in the file that makes the file invalid when opened with the OEM software? – grepNstepN May 20 '16 at 16:18

Surfing the net about WIFF file formats, I found two software that convert WIFF file to others formats:

You can check if there are bytes used to check the data in addition to the chunk that you have already tried to patch (d5a0 -> d640).

Your Answer

 

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.