I'm completing a DVD project with a small web site in the ROM section of the disc. The write to tape was w/o problems. But the compare failed at the very end with the following message in the log:
File name .DS_Store Offset 0000017c
0000: 0000 0001 4275 6431 0000 1000 0000 0800 0000 1000 0000 0108 0000 0000 0000 0000 ....Bud1........................
0160: ffff ffff ffff 0000 0000 0004 0073 0069 0074 0065 6473 636c 626f 6f6c 0000 0000 .............s.i.t.edsclbool....
0160: ffff ffff ffff 0000 0000 0004 0073 0069 0074 0065 6473 636c 626f 6f6c 0100 0000 .............s.i.t.edsclbool....
Format copy error detected in function Run at line 180 of file CInputComparatorThread.cp Note: Data compare error
3: 1729781 670002 1729801 20 Start/Stop 01 00 00 00 00
I'm using DVDAE 3.0.3 with "Include Mac ROM Data" checked in my preferences and "Create Joliet Directory" unchecked.
In the mastering dialog "Include Mac ROM Data" is checked and Joliet is set to "None"
If I write out a disc image file and then mount it, the ROM data is present, including the .DS_Store file.
If I compare the project to the saved disc image, the compare succeeds.
Should I ignore this? ;->
Michael
Hi Michael, That sounds
Hi Michael,
That sounds possible - as you know, the .DS_Store file holds all the info about icon layout and window size etc. used by OS-X when opening a folder. So, certainly the "last accessed" info would probably be updated, if nothing else. And this would be enough to make the compare fail, I'm sure. If you accidentally moved one of the icons a pixel or two, or moved the window on the desktop, or resized it slightly, those would all do it too.
Ian
Re-wrote tape, compare failure gone; a theory...
So I re-wrote the tape and then performed the compare, which succeeded this time.
My theory is that after I wrote the tape the first time, I may have done something that caused the attributes of .DS_Store file to change. Specifically, I opened the web site with a browser. Maybe that caused a modification time to be re-set. I don't know.
Could this be the reason for the initial compare failure?
Michael
Post new comment