Re: [Info-mtools] What does it take to support FAT12 dialects?

[Alexander Huemer]

On Mon, Jun 07, 2021 at 12:39:11PM +0200, Alain Knaff wrote:
> Hi Alex,
> 
> On 07/06/2021 11:35, Alexander Huemer wrote:
> [...]
> > 
> > Many thanks for this!
> > 
> > I did some testing, this seems to work as intended.
> > E.g.
> 
> Glad to hear this!
> 
> > 
> >> ~/src/_readonly/mtools/mtools-4.0.28/minfo -i 
> >> /tmp/24.img\|data_map=1s,zero31s,28s,skip1s
> > 
> >> ~/src/_readonly/mtools/mtools-4.0.28/mdir -i 
> >> /tmp/24.img\|data_map=1s,zero31s,28s,skip1s -a ::
> > 
> >> ~/src/_readonly/mtools/mtools-4.0.28/mcopy -i 
> >> /tmp/24.img\|data_map=1s,zero31s,28s,skip1s -a :: .
> > 
> > The parameters of the command below were suggested by `minfo`.
> > 
> >> ~/src/_readonly/mtools/mtools-4.0.28/mformat -C -T 4800 -h 2 -s 30 -H 
> >> 1710948352 -i "/tmp/foo.img|data_map=1s,zero31s,28s,skip1s" ::
> > 
> > What I did not yet figure out is how I can write all files in a local 
> > directory (e.g. from a previous `mcopy` call from an images file to the 
> > disk) into an image file. This probably has little to do with the 
> > data.map but is simple lack of understanding on my end.
> > 
> > I tried this:
> > 
> >> ~/src/_readonly/mtools/mtools-4.0.28/mcopy -i :: * 
> >> /tmp/foo.img\|data_map=1s,zero31s,28s,skip1s
> 
> Hmmm, weird. For some reason the command line looks all jumbled up 
> (parameters in random order). I am not sure whether this was executed  
> this way, or whether it happened while pasting into the mail.
> 
> In case it was indeed executed in this order, could you try whether it 
> works better in order:
> 
> ~/src/_readonly/mtools/mtools-4.0.28/mcopy -i 
> /tmp/foo.img\|data_map=1s,zero31s,28s,skip1s * ::

My attempt was probably foolish...

Though, I don't have success with your suggestion either.

$ ~/src/_readonly/mtools/mtools-4.0.28/mcopy -i 
/tmp/foo.img\|data_map=1s,zero31s,28s,skip1s * ::
Cannot initialize '::'
Bad target ::

-Alex