From melamy@earthlink.net Thu Aug 12 06:11:18 2004 From: melamy@earthlink.net To: test-drb@ccmp.vtda.org Subject: archive file format exmaple Date: Thu, 12 Aug 2004 06:11:18 +0000 Message-ID: <20568369.1092309078565.JavaMail.root@grover.psp.pas.earthlink.net> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1960588231844295697==" --===============1960588231844295697== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable here is a "crude" example of what I was talking about.=20 try: a place to put whatever relevant information is needed about the format or= achive or your favorite poem or joke Tandy Model 100 Ian Blindly 5.25" floppy

MFM? RLL? something ... 35 1 18 8

... 456789ABCDEF... 1234567890A... 890ABCDEF01245... 456789ABCDEF... 456789ABCDEF... 1234567890A... 890ABCDEF01245... 456789ABCDEF... 456789ABCDEF... 1234567890A... 890ABCDEF01245... 456789ABCDEF... please don't get hung up on names, etc, The basic structure is what I have be= en=20 talking about. A utility can go into the archive file, find a , know what it is and extract it without having to know anything about the OS. = Another utility can read the media, datamap, and datablocks to re-create tracks in me= mory to then write out to disk. There was earlier talk about years from now being = able to still re-create disks. I think that is a fine ambition, but that still req= uires all the hardware and intimate OS knowledge to still be around. My idea was to= at least be able to extract the data without having to have ANY knowledge of the= OS. best regards, Steve Thatcher --===============1960588231844295697==--