Jump to content


  • Content Count

  • Joined

  • Last visited

About Jinx

  • Rank
  1. Was I too verbose/descriptive? Is anyone else interested in archival options? Is there perhaps a way to use an external program with the compilation (".dxp") files to perform some of the tasks mentioned automatically? Does anyone have any alternative suggestions for archival that would accomplish those tasks?
  2. Currently the "Disc Information" shows rather limited information and seems to also be limited to the active write-capable drive. It would be great if the Disc Information dialog could show more information. Examples could include: (1) ISO Volume Labels (perhaps including those beyond the 3 mentioned in the "set volume labels" dialog); (2) Media identification information (similar to that provided by the "Read" or "Discovery" modes in ImgBurn--particularly the physical "Disc ID"); (3) Presence of a bridged/hybrid filesystem (e.g. to help identify issues related to the current lack of bridged filesystem support) Finally, please enable a drop-down box to allow the user to select from which drive to report information. Edit: Also added a uservoice suggestion thread.
  3. Any chance the burning library has implemented 8-bit support yet? I'm still hoping to be allowed to burn lengthy filenames again one day.
  4. This would indeed be a great feature to have. It amazes me that even with recent versions of UDF, one still cannot get filename lengths as long as FAT32. Apparently this is due to UDF requiring Unicode (which essentially doubles the byte count), and Floele has indicated for some reason that... ( Source ) However, at least as of recently, CDBurnerXP will now prompt us to truncate such lengthy filenames. Not a great solution for archiving, but it's better than nothing. Perhaps there will be a way to export the filenames into a meta-file (such as a BAT) that can automatically rename the entire disc if ever extracted to a writeable medium. That would indeed be convenient. P.S. I'm still confused at "file names may be as long as 255 bytes (that is, 254 8-bit or 127 16-bit Unicode characters)" on this page. Is there any way to tell CDBurnerXP to use "8-bit" characters (assuming they are such in the first place)?
  5. Forgive my lack of comprehension, but why are audio discs not verifiable? If the data was known once to write, shouldn't it be known again to read? Even if the hardware performs some sort of algorithm on it, couldn't that be emulated/reversed? I also would appreciate as much verification as possible.
  6. I share this user's exact issue. It took me ages (and about 8 bad discs) to figure out that it was a filesystem issue--because both the current (nonworking) discs and all my previous (working) discs still reported "UDF"! I may also revert for now. See also: http://cdburnerxp.uservoice.com/forums/165656-feature-requests/suggestions/3492608-allow-creating-data-disk-with-iso9660-joliet-udf-f
  7. For years now, I have been using optical media as a method of archival. However, while burning the files is fairly painless, keeping track of them requires a good deal of extra time and effort. I have a few ideas for utilities that would make archival much less painful. While these are surely possible to do as standalone applications (and I am open to hearing about alternative suggestions), I'm not sure any alternative would replace the convenience of integration with the burning software. (1) Backup File Lists: This is perhaps the easiest of my suggestions, as the current save file format (XML) could probably be converted to CSV or even plaintext (tab-delimited) to provide a good record of everything that is on a disc.However, some information would need to be added, such as the filesize and preferably a few choice hash algorithms. The main purpose of this suggestion is to help to know what is on a disc without having to locate/load it. (2) Placeholder Files: Similarly, one may wish to keep a hierarchy of placeholder files on the local drive, and use that to reference an indexed disc. It would be very convenient if the burning application could automatically create small placeholder files indicating both the disc ID of the file as well as some other file details (size, date, hash, etc.). To prevent all files from receiving placeholders, a minimum size "threshold" could be enabled. The purpose of this suggestion is to help easily locate a file via a search and/or hierarchy, while keeping the contents of the file on an optical disc. (3) Directory Hybrid: There may also be a way to merge these two ideas by leaving one placeholder file per directory, which contains all the file details. So, for example, if a directory was burned to one disc at one point in time, it would receive a "{DISCID}.ext" placeholder file. However, later that same directory could be burned again and receive a new placeholder file. (4) Plugins / Extensions Finally, if all of this tickles your "bloat" bone, then perhaps an interface could be made to enable a plugin/extension model to accomplish these tasks. If anyone has other archival-related suggestions, I'd love to see them on this thread. I truly look forward to the day when I can drag some files over to the CDBurnerXP window, hit burn, and let it do the rest--never again having to worry about whether or not I'll be able to find/verify those files again in the future.
  8. http://cdburnerxp.se...ices/filesystem Please restore this feature. It was silently removed and as a result I could not figure out what was causing my recent MP3CDs to fail, since both the working ones I burned last Fall and the non-working ones I burned recently both reported a "UDF" filesystem! Perhaps also the "Disc Information" could do a check to see if there is a bridged mode involved, and if so report it. Thank you. See also: http://cdburnerxp.us...60-joliet-udf-f
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.