I won't say the ship has sailed, but it's certainly pulled out of the port. I'm all for embedding metadata, if a place can be found. At least, it's a fun thought experiment. I once thought about putting metadata in Block Zero, but I suppose that's used more often than Track 18, Sector 18. Overwriting the BAM with a Magic Word, for example. (After all, rebuilding the BAM is just one validate away.) And I *do* like the possibilities made by the X64, unlikely tho they are to be ever exercised. On Mon, Jan 27, 2014 at 9:29 PM, Jim Brain <email@example.com> wrote: > On 1/27/2014 4:59 PM, Rob Eaglestone wrote: > >> re: container format. Hasn't this been done already, i.e. the X64? And, >> it's rather moribund (although I think there are fun things one can do with >> a container). But yes, tradition tends to be a handy bond. >> >> And, regarding the thought of a five-character extension: sure, but I >> think that way lies madness; you'll suggest a modest and reasonable but new >> way, and before you know it I'll have lost my self-restraint and will >> suggest a real-like 256-byte header appended to those new formats, and then >> I'll be suggesting a .D1541 image that includes that header, and that the >> directory should be located at the front of the image, and......well it's >> just madness, I tell you!! >> > > I agree containers and different extensions are on a ship that has sailed. > > However, I am wondering if there is a way to "embed" the metadata into the > existing format. > > Yes, I know there are issues... > > Still, giving people the option of using the last sector of track 18, for > example, which is hardly ever used, or tacking a block onto the end of the > image and putting data into that block would sure help matters. > > Jim > > > > Message was sent through the cbm-hackers mailing list > Message was sent through the cbm-hackers mailing listReceived on 2014-01-28 06:00:06
Archive generated by hypermail 2.2.0.