[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Volume Number support for .dsk images



Rubywand <rubywand@swbell.net> wrote in message news:<3E282CDF.8920D890@swbell.net>...
> Like emu writers don't have enough to do, here's another wish list item:
> 
> Why not add support for Volume Numbering of .dsk images?
> 
> 
>      Sure, we can use .nib images when volume number has to be preserved; but,
> .nib images take up a lot more space and are not nearly as easy to use when you
> want to transfer between machines and/or go from image to diskette.
> 
>      At present, we are dealing with piles of .nib images mostly because it's
> the only way to preserve volume number.
> 
> 
>      One way to retain VN info without any changes to .dsk format would be to
> make it a filename option-- i.e. an extension which tells the emulator the
> volume number.
> 
>      For instance, suppose you know that the volume number for Robot Muncher's
> boot disk needs to be 29. Instead of going through the bother of making a .nib
> image, you make a .dsk image and name it "RobotMuncher1_V029.dsk".
> 
>      An emu which supports VN recognition sees the "_V029" near the end of the
> file name and sets that as the default VN for that drive so long as the image
> is there.
> 
> 
> Rubywand

What about Dapple, which doesn't support LFNs?  (Dapple ][ will
possibly support LFNs in an LFN-aware environment.  I, however, don't
have one.)

My suggestion is to use the format "rbmunch1.$1C" (volume number in
hex) and have the emulator recognize *.$?? as .dsk files.

-uso.