hyperyoda Posted April 25, 2012 Posted April 25, 2012 (edited) I'm not sure when this behavior started but I'd say I noticed it after either the last update or the one before that. Before if I had a filename "TEST ONE TWO THREE" (or a directory name) it would be burned to disc with that same name. Now it is burned to disc as "TEST_ONE_TWO_THREE". I don't like this and in the case of game backups I must manually rename everything to get the game working again once I decide to copy it back over from disc! It seems whatever used to default to OFF with regards to this setting is now defaulting to ON. Any idea how I can fix this? BTW no matter what filesystem I choose it still burns the disc with this same unwanted behavior. I'm using ImgBurn 2.5.7.0 on Windows 7 Ultimate (x64). Thanks. Edited April 25, 2012 by hyperyoda
LIGHTNING UK! Posted April 25, 2012 Posted April 25, 2012 That sounds normal for an ISO9660 filesystem. What are you trying to use the disc in that only supports ISO9660 rather than Joliet or UDF (which do allow spaces) ?
hyperyoda Posted April 25, 2012 Author Posted April 25, 2012 That sounds normal for an ISO9660 filesystem. What are you trying to use the disc in that only supports ISO9660 rather than Joliet or UDF (which do allow spaces) ? The File System ImgBurn is using is "ISO9660 + UDF". So if it is using UDF why isn't it preserving the spaces? Here is what I did: Burn disc of data (which consists of various games), load newly created disc, explore disc and see that all filenames and directories with spaces have been converted to conform with ISO9660. I changed nothing in how I make discs, the only thing that changed is I upgraded ImgBurn. What I need to know is what default seting can I set so that I don't have a problem with this again?
LIGHTNING UK! Posted April 25, 2012 Posted April 25, 2012 Please look at that disc using IsoBuster. It'll show you the two file systems on the disc and show you the names recorded in each one. I'd like to think you'll see that the UDF side of things is correct and has spaces in the names where they were originally. So then what we need to figure out is why Windows is only loading the ISO9660 file system and not the 'better' UDF one. There is no setting in ImgBurn that can make it convert spaces to underscores for all file systems. It only ever does it for the ISO9660 one - as per the specs.
Recommended Posts