[sebhc] Archive changes
Dwight K. Elvey
dwight.elvey at amd.com
Mon May 24 12:26:55 CDT 2004
>From: "Eric J. Rothfus" <eric at rothfus.com>
>
>Cool more disk images! However, it looks like we've landed
>on a generic (read "non-distinquishable") disk image format.
>Even the extension is generic ".disk".
>
>Far be it from me to b*tch :-), but how about a just a simple
>header with the following (as an example):
>
> H8,40,10\n
>
>This format identifies it as an H8 disk with 40 tracks and
>10 sectors. You can get rid of the header line by discarding
>everything up to the newline. Put it in binary format if you
>like.
>
>Again, the goal is simply to allow intelligent software (as
>well as historians 100 years from now) to tell that this image
>was meant to run on a Heathkit H8 and that it can be decoded
>with 40 tracks of 10 sectors. Sure, I've drawn an arbitrary
>line about how much information is necessary...but we need
>something!
>
>Hopefully, in the not too distant future, a much larger
>integrated archive of software images will assemble itself,
>and the H8/H89 images will be part of that. Fortunately,
>most other image formats have some distinguishing
>characteristics. Let's keep with that philosophy.
>
>Dave - can you live with a header on the binary file for
>the H17 part of the emulator?
>
>Eric
>
Hi
Why not put the text at a tail to the file. Those
programs that load an image size chunk will still
work while the extra bytes at the end won't make much
difference.
Dwight
--
Delivered by the SEBHC Mailing List
More information about the Sebhc
mailing list