yowzer Posted August 18, 2008 Posted August 18, 2008 I have used Philips UDF Verification Software and found that when I change the volume label of a UDF image, FSD: File Set Identifier doesn't get changed. I'm using ImgBurn 2.4.2.0 old label: ====> Volume identifiers summary: PVD: Volume Identifier [32]: "[color="#FF0000"]Jumped over the[/color]" PVD: Volume Set Identifier [128]: "3912952B00000257" LVD: Logical Volume Identifier [128]: "[color="#FF0000"]Jumped over the Lazy Dog[/color]" IUVD: Logical Volume Identifier [128]: "[color="#FF0000"]Jumped over the Lazy Dog[/color]" FSD: Logical Volume Identifier [128]: "[color="#FF0000"]Jumped over the Lazy Dog[/color]" FSD: File Set Identifier [32]: "[color="#FF0000"]Jumped over the[/color]" after changing: ====> Volume identifiers summary: PVD: Volume Identifier [32]: "[color="#0000FF"]The quick brown[/color]" PVD: Volume Set Identifier [128]: "3912952B00000257" LVD: Logical Volume Identifier [128]: "[color="#0000FF"]The quick brown Foxes[/color]" IUVD: Logical Volume Identifier [128]: "[color="#0000FF"]The quick brown Foxes[/color]" FSD: Logical Volume Identifier [128]: "[color="#0000FF"]The quick brown Foxes[/color]" FSD: File Set Identifier [32]: "[color="#FF0000"]Jumped over the[/color]" <--- why doesn't this one get changed? There are a bunch of errors upon verification too. ImgBurn probably doesn't generate OSTA-compliant UDF file system structures. You can download UDF Verification Software here: http://www.ip.philips.com/ (login first) then go to: http://www.ip.philips.com/partners/registe..._udf_index.html
LIGHTNING UK! Posted August 18, 2008 Posted August 18, 2008 I've run all the images / udf versions ImgBurn can create through that tool before and they're fine. It doesn't change the FSD File Set Identifier text because it's not a 'volume identifier' - the name kinda gives that away.
Recommended Posts