How is the 126 Character Limit supported in ImgBurn if the Microsoft API itself does not support the maximum?

[AlbertEinstein]

ImgBurn is, at the moment, the only software package on the Windows platform that I am aware of that supports the maximum character limit of 126 characters for an optical media label using the UDF file system. However, it is fully supported, again AFAIK, on almost every Linux operating system. I keep pushing everyone I can for the adoption of software developers, including Microsoft, to fix this shortcoming in their software packages. But one question I have is, how ImgBurn supports this feature when the Windows Operating System itself, does not? I would be very interested to know so that we could at least offer this solution to other developers interested in supporting the UDF file system properly.

Edited December 25, 2023 by AlbertEinstein

[LIGHTNING UK!]

It's just a descriptor in the file system. There's no 'Microsoft API' involved where ImgBurn is concerned as I'm creating the descriptor from scratch at Byte level.

If programs / OSs support reading from it, it'll work as intended.

 

[AlbertEinstein]

Thank You very much for the help on this. I'll pass your comments on to the developers applications that fall short of this feature!