Re: standard file extensions for exported apple dos files ?

[Eric Rucker <bhtooefr@gmail.com>]

On Jan 24, 8:08 am, Jonno Downes <jonno...@gmail.com> wrote:
> On Jan 24, 11:37 pm, Alex Freed <alex_n...@mirrow.com> wrote:
>
>
>
>
>
> > The only cross-platform place for storing file metadata is in the file
> > > extension, but there doesn't seem to be any convention or standard
> > > file extension used for this purpose - BIN and BAS are too generic.
>
> > > I am considering using .?33, where the first char is the DOS 3.3 file
> > > type (i.e. a binary file will get saved with extension .B33, an
> > > Applesoft file will get .A33 etc).
>
> > > But is anyone aware of unique extensions already being used for this
> > > purpose?
>
> > Yes. CiderPress saves the type and loading address (for binary type) as
> > a part of the name. If you have a modern file system as opposed to
> > say MSDOS, the "extension" doesn't have to be a CP/M standard 3 letters.
> > Even FAT understands long file names these days.
>
> Interesting apprach, but unfortunately the file type and load address
> are in the main file name, not the extension, so you can't set up a
> program to run when you double click an exported file. To be
> completely accurate, you CAN get ciderpress to add a file extension,
> but it will be .BAS or .BIN, which is not unique to Apple DOS 3.3.
> files. For example, exporting "HELLO" from a DOS 3.3 disk with both
> "add file attribute information" and "add file extension" selected
> resulted in the file being saved as "HELLO#fc0801.BAS"
>
> One of the things I'd like to be able to do is run an individually
> exported binary or Applesoft file in AppleWin just by double clicking
> it (doing this properly would require an extension to AppleWin - I
> plan to kludge it by having as the handler assigned to whatever is the
> unique file extension a ruby script that takes the file that's been
> double clicked, puts it into an otherwise blank DOS 3.3 dsk image,
> along with a HELLO that runs the file in question, and then pass
> AppleWin  the filepath for the newly minted dsk ).

If you're taking advantage of the Windows association handler, you'll
want as few extensions as possible.

I'll suggest something like HELLO.A.D33. Use D33 for everything, that
way you've only got one association to deal with. Put the load address
in after the filetype for binary files.