Currently I use ssd_extract.py from https://github.com/tom-seddon/beeb/ - that, or use the disk image tools to write to an actual floppy disk and run things from there.
And that's fine and all that, but... BeebLink could do better.
Some thoughts:
Manual extract - e.g., *VOL with a file, possibly from a PC folder, causes it to extract the .ssd somewhere (where?) then do *VOL on that folder. Then also manual creation of .ssd file from volume - obviously you have to have respected the DFS limitations...
have in-built mini Beeb emulator that runs DFS to access the .ssd directly. Pretend there's a copro attached and handle the data transfer that way. Bit of a pain to get working (to say the least), but in theory it'd be easy to support stuff like Watford DFS (62 files, DDFS) and Opus (720 KB) without having to disassemble the ROM
write code to manipulate the ssd file directly. This doesn't sound terribly appealing, but it'd probably be straightforward enough. Might require a bit of surgery on the code
Currently I use
ssd_extract.py
from https://github.com/tom-seddon/beeb/ - that, or use the disk image tools to write to an actual floppy disk and run things from there.And that's fine and all that, but... BeebLink could do better.
Some thoughts:
*VOL
with a file, possibly from a PC folder, causes it to extract the .ssd somewhere (where?) then do*VOL
on that folder. Then also manual creation of .ssd file from volume - obviously you have to have respected the DFS limitations...Any more?
Should at least do the extract case of option 1.