filesystems - If I burn a dvd with files on mac, is it going to be readable on another systems?

06
2013-08
  • Somebody still uses you MS-DOS

    I don't want to burn a DVD with files that is only going to be read by newer Windows versions, and not by a Linux box.

    Can I trust on Mac's bultin DVD recorder in Finder in creating fully compatible DVD-Rs like all recorders in the planet in a Windows system do, or am I going to have a 'hybrid' Mac proprietary format and would make a CD-R useless when trying to use for example in my car system with some MP3?

  • Answers
  • Huw

    I don't know what the Finder does, so I don't trust it... However, a good piece of software is Burn:

    http://burn-osx.sourceforge.net/Pages/English/home.html

    It's straight forward and free.

  • Hydaral

    Make sure you use the UDF format when burning your disc (v1.02 for compatibility), this can be read by all Mac and Windows OSes released in about the last 5 years, maybe more. If you have the option, use Joliet and ISO 9660 too, this will ensure compatibility with all OSes for about the last 15-20 years.

    From a quick search, it appears that Finder burns a hybrid ISO 9660/HFS filesystem, this should be able to be read on Windows machines but ISO 9660 is very old and restrictive, I suggest finding some better burning software. Burn, as Huw suggested, is free, so you might want to try that.


  • Related Question

    windows 7 - Double Layer DVD+R burning problem - I/O Error
  • Questioner

    I have a modern PC (Quad Core CPU, 4 GB RAM, Win7 Home Premium 64-bit) but I have a problem with burning .dvd images to Double Layer (8.5 GB) DVDs. I wasted too many DVD+R DL discs but to no avail. Here is a short explanation of what I did:

    I'm using ImgBurn v2.5.0.0 (latest version). I'm trying to burn an image file (.dvd) which is together with the related .iso file in the same folder. In ImgBurn, I select the file with .dvd extension, and set writing speed to 2.4x. Burning process starts normally, but around 7% of the process, it gives a I/O Write Error, which is as follows:

    enter image description here

    I wasted 3 discs (Magic, Made in Taiwan, DVD+R DL, 8.5 GB) trying the same thing. My DVD writer is LG GH22NP20 with IDE connection type. I updated its firmware from 1.04 to 2.00 but no success in burning again. Then my cousin brought his LG (an older model) which, he claims, was successful in writing DL discs with the same brand (Magic). I plugged off my LG and plugged the older one in, and tried to burn the image again. It also gave an I/O Error even without standing till 7%. I tried another burning program (CloneCD), but failed again.

    Then I bought other brands (TDK and VERBATIM) and tried to burn the image. Burning process started successfully, but around 14% (for Verbatim) and 25% (for TDK) failed again. Here is a screeny from ImgBurn:

    enter image description here

    I've burned lots of 4.7 GB DVD+Rs and DVD-Rs successfully, even without a single error, with this LG DVD writer, but this case is very bothering for me. What should I do? Should I buy a new DVD writer other than LG? Could this be related to Windows or my hardware configuration? Thanks for your help.

    Edit: My burner works on my cousin's machine. So the problem must be related to my system. What could be the reason?

    Latest news: I borrowed an external USB DVD writer from a friend, which is PHILIPS SPD3000CC (an old model). Guess what! It's burning DVD+R DLs successfully! How come an internal DVD writer of a brand new computer system cannot burn DL DVDs? Now I'm considering buying a new internal DVD writer with not IDE, but SATA connection...

    Bottom Line: I've sold this PC and probably never gonna learn the answer to my question.


  • Related Answers
  • Joshua Nurczyk

    It could be an issue with the drive controller it is plugged into, or it could be an issue with Windows. Did your cousin use Windows 7 to burn DL discs? Also, have you tried your burner in your cousin's computer?

    Reinstalling Windows may help, but there is no way to know until you try.