HD image load as content.

[voodatari]

The regular Hatari core accepts .VHD files (they are just .img hd images renamed) and they boot perfectly fine, but I couldn't make the same with hatariB. Could it be possible to add that functionality?

Thanks a lot!

[bbbradsmith]

I left a response at the Atari-Forum thread, so I think it's better to continue discussion there.

[bbbradsmith]

Leaving myself some notes here about potential implementation:

• M3U seems to use the need_fullpath override to allow direct access to the content file, can probably use this?
• When loading content, if the extension matches an HD one use it for HD instead of floppy. (AHD, IDE, VHD?)
• I think we can only allow changing hard drive if added before first boot, but maybe M3U images could create a floppy + HD combo.
• Can we avoid placing an unusuable disk image in the disk list when HD is loaded instead of floppy? If not maybe we can decorate the name and prevent insertion. Make sure the floppy drives don't attempt to load it at startup either.
• VFS access to content folder might be read-only. I think we might have a read-only fallback for hard drives already, but make sure one exists. Followup: yes the fallback already exists: ACSI, IDE

This should probably also satisfy one of the desires expressed in #12 about wanting to launch an HD image from the command line. During that discussion it was discovered impossible to override core options via the command line.

[bbbradsmith]

I thought there was a second comment from @voodatari, did I accidentally delete this?

[bbbradsmith]

Now supported in: https://github.com/bbbradsmith/hatariB/commit/78d4faec3cc7c8a0d6d27d9ca04466120456aa87