[openbeosstorage] Re: ISO9660/cdrom progress
- From: "Ingo Weinhold" <bonefish@xxxxxxxxxxxxxxx>
- To: openbeosstorage@xxxxxxxxxxxxx
- Date: Tue, 25 Feb 2003 19:20:17 +0100 CET
Tyler Dauwalder <tyler@xxxxxxxxxxxxx> wrote:
>
> > > Looking at the root directory record, the location of the
> > > directory's
> > > extent (an LBN) is always specified with an absolute block
> > > number.
> > > One
> > > could debate that the sequence # of 1, which is also always
> > > specified,
> > > refers to the volume space of the first session, which begins at
> > > zero
> > > (even for the first data session immediately following an audio
> > > session
> > > on an "Enhanced Audio CD", interestingly). And while that's true,
> > > addresses outside the first volume's volume space are still
> > > specified
> > > this way. Further, every volume on the CD is always given the
> > > sequence
> > > # of 1.
> >
> > Ouch!
>
> The "production quality", pressed-not-burned CD that came with my
> lovely new Pocket PC actually references a volume sequence # of 0 in
> its addresses...
You should claim your money back -- keeping the hardware, of course. ;-
)
[...]
> > > I, OTOH, have been approaching it as "There is no standard
> > > followed
> > > by
> > > current burners (or Nero, at least; I guess others should be
> > > checked
> > > too :-)
> >
> > Oh, yes, please do that. :-) I can't, for I don't use Windows for
> > religious reasons. ;-)
>
> Ah, I see how it is. :-) Well, might you be able to check any of the
> burners available in Linux then=3F I don't have the patience to figure
> out how to get something as terribly complex as CD burning software
> to
> work. :-P :-)
Actually, I've never burned a CD under Linux. In fact, the only CD
burner I possess lives in a BeOS-only machine that has been terribly
unstable for quite some time. :-(
Maybe I could try the Knoppix CD I got recently. I don't know whether
there's a CD burner app on it that supports burning multisession
ISO9660 CD, though. Oh, I've got a better idea, I could ask stippi to
burn some CDs for me under FreeBSD. :-)
> Also, I recently inherited an iMac, so if I ever manage to get OS X
> installed (ironically, Linux installed with only the expected handful
> of hang-ups) and it turns out the thing has a CD-RW drive (I'm not
> sure
> if it does, and Linux isn't convinced yet that the drive even exists,
> despite being installed off of it...), I'll check out some Mac
> burners
> too.
Cool. :-)
Hint for the Linux user: Try a newer distribution, or build your own
kernel. ;-))
[...]
> > > Yes, though I see no evidence of any sort of restriction on where
> > > files
> > > can be referred from. It looks to me like any volume can refer to
> > > anywhere on the disc it pleases (not according to the standard,
> > > but
> > > according to actual CDs and their root directory records).
> >
> > Sadly. Maybe one should notify the application creators of these
> > standard deviations.
>
> Yeah, I might do that. Maybe they'll counter with something along the
> lines of "you're using an old standard, go look at XYZ". :-) I'm not
> getting my hopes up, though.
If there indeed exists a newer standard, it would be nice to learn
about it. :-P
> [rumblings of disk=5Fscanner interface and kernel migration changes]
> > > I, too, am thinking about this, but this reply has taken me long
> > > enough
> > > to get sent off already, so it can wait till next time.
> >
> > :-)
> > No hurry. I haven't thought much about the matter yet. I first want
> > to
> > get the userland GUI add-ons done, with partitioning support,
> > before
> > actively reconsidering the registrar->kernel migration and the
> > required
> > /useful changes.
>
> How is the GUI add-on stuff going, btw=3F
It's progressing slowly. After some painful attempts to build a GUI
with the plain Interface Kit, I decided to write some classes for a
generic layout management. Don't worry, I don't intend to hold myself
off too long with that. It will be relatively simple, and by accident I
have this very powerful, `almost complete' layout library of mine
discontinued some four years ago, from which I can borrow some ideas
and code.
> I still haven't gotten around
> to nosing around in what's been checked in. :-(
>
> As to the thinking...well, it's not quite done yet. :-)
:-)
CU, Ingo
- Follow-Ups:
- [openbeosstorage] Re: ISO9660/cdrom progress
- From: Axel =?iso-8859-1?q?D=F6rfler
- References:
- [openbeosstorage] Re: ISO9660/cdrom progress
- From: Tyler Dauwalder
Other related posts:
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- [openbeosstorage] Re: ISO9660/cdrom progress
- From: Axel =?iso-8859-1?q?D=F6rfler
- [openbeosstorage] Re: ISO9660/cdrom progress
- From: Tyler Dauwalder