 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
Mac Forum / General / Hardware / November 2006OS X 10.4.8 - CD Burning
I recently purchased a new Macbook Pro and I'm noticing something odd in my CD burning. As far as I can tell, the native burning implementation in the Finder does the job just fine (all I burn are data CDs/DVDs), but there seems to be a disc size issue with CDs. When I try to burn something that I know will just barely fit, OS X tells me that it won't fit and can't be burned onto the CD. However, if I take the disc over to my Linux box and burn it with K3B, the data fits onto the CD. For example, this recently happened with a file that is exactly 735,631,360 bytes in size. Can anyone think of what might be the case here? Is it a physical limitation of the drive in the Macbook Pro? A software setting that can be changed somewhere? Any help would be much appreciated, thank you. Regards, David 7 Computers <47computers@gmail.com> wrote: > When I try to burn something that I know will just barely fit, OS X > tells me that it won't fit and can't be burned onto the CD. However, if > I take the disc over to my Linux box and burn it with K3B, the data fits > onto the CD. I've had Toast fit data on an MP3 disc than iTunes would.  Signature<http://designsbymike.biz/macconsultshop.shtml> Mac-themed T-shirts <http://designsbymike.biz/musings.shtml> Mostly muckraking T-shirts <http://designsbymike.biz/prius.shtml> Prius shirts & bumper stickers <http://cafepress.com/comedancing> Ballroom dance-themed shirts & gift > I've had Toast fit data on an MP3 disc than iTunes would. Make that: I've had Toast fit more data on an MP3 disc than iTunes would. Signature<http://designsbymike.biz/macconsultshop.shtml> Mac-themed T-shirts <http://designsbymike.biz/musings.shtml> Mostly muckraking T-shirts <http://designsbymike.biz/prius.shtml> Prius shirts & bumper stickers <http://cafepress.com/comedancing> Ballroom dance-themed shirts & gift > I recently purchased a new Macbook Pro and I'm noticing something odd in > my CD burning. As far as I can tell, the native burning implementation [quoted text clipped - 10 lines] > limitation of the drive in the Macbook Pro? A software setting that can > be changed somewhere? Any help would be much appreciated, thank you. One possible explanation that occurs to me is that the Mac may be consuming more space by providing more file systems than the Linux box does. The Mac, I believe, does both Joliet and HFS+ (and Joliet IIRC is kind of an ancillary set of structures presupposing an ISO 9660 directory). Not familiar with K3b, but it may not be doing all 3 of those and thus may not go over the limit when your data barely fits. SignatureThe best intentions in the world don't make a flawed argument magically valid. > One possible explanation that occurs to me is that the Mac may be > consuming more space by providing more file systems than the Linux box > does. The Mac, I believe, does both Joliet and HFS+ (and Joliet IIRC is > kind of an ancillary set of structures presupposing an ISO 9660 > directory). Not familiar with K3b, but it may not be doing all 3 of > those and thus may not go over the limit when your data barely fits. I hadn't thought of that, but you may be onto something there. Not being much of an expert on filesystems and the technical details of CD-specific filesystems, I'm not sure what information is entirely relevant. However, the various options I have set up in K3B are as follows: 1) No multisession (maybe the Mac is initiating a multisession disc by default and that eats up some space?) 2) Generate Rock Ridge extensions (no idea what this means) 3) Generate Joliet extensions (ditto) 4) Allow 103 character Joliet filenames (I would imagine this affects the filesystem used by K3B, no?) 5) ISO Level 2 (this was the default, I don't know the difference) My Googling on the subject hasn't turned up anything meaningful yet. But at the moment I'm mostly interested in that multisession idea. Thoughts? Regards, David >> One possible explanation that occurs to me is that the Mac may be >> consuming more space by providing more file systems than the Linux box [quoted text clipped - 12 lines] > default and that eats up some space?) > 2) Generate Rock Ridge extensions (no idea what this means) Check Wikipedia. POSIX file semantics to ISO 9660. This is a Good Thing. |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2009 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.