is it possible to add an physical USB floppy drive to have Amibian load automatically?
Basically so I don't have to load anything by hand and have it going?
Thanks.
Cheers,
Boy
1 comment
Like
1 Comment
Phalkon13
Mar 22, 2018
As far as I understood, current physical USB floppy drives were not compatible with Amiga disks at all, as they could not read the 880k disks properly (the ADF files usually are ripped from Floppy drives connected directly to a motherboard via the IDE connection on PCs, which is not really an option with newer PCs sadly.) Also, I believe any USB storage device will load via the /media/
If you're trying to get Amibian to boot automatically into a specific build of your AmigaOS, you can always create your configuration (build of Amiga, mount your floppy, etc...), and save it with the primary name "autostart" (name, not description: you can put anything in the description, but the name has to be "autostart"),. making sure in the Misc tab to uncheck "Show GUI on startup before you save the config".
Just make sure you have a good-working build, as from experience I screwed up my AmigaOS build and had to plug the SD card into another RPi os build so that I could navigate to the config files to delete the autostart config.
UPDATE:
I cannot verify if an 880k Amiga-native disk will work, but if you're using a standard 1.44MB, you can mount the /media/usb directory (it might be /media/usb1 or usb2 as well is you have multiple USB storage devices mounted). I also made sure to set the Device name as "FD0" instead of "HD0" I had my virtual floppy disabled so I do not know if it causes issues if enabled. I verified by copying the files from my Workbench 2.04 ADF file to a floppy disk. I did run into some issues trying to copy from the Amibian CLI or MC due to Amibian mounting the disk as read-only (regardless of the tab), but I copied the files to the floppy via Windows 10.
In Amibian, when set to autoboot with GUI disabled from the floppy drive directory, it boots into the Floppy disk and first asks to copy files from the "Extras" dosk. If I select 0 to not copy, it then boots right into Workbench 2.04. So it does work, just in a round-about way.
As far as I understood, current physical USB floppy drives were not compatible with Amiga disks at all, as they could not read the 880k disks properly (the ADF files usually are ripped from Floppy drives connected directly to a motherboard via the IDE connection on PCs, which is not really an option with newer PCs sadly.) Also, I believe any USB storage device will load via the /media/
If you're trying to get Amibian to boot automatically into a specific build of your AmigaOS, you can always create your configuration (build of Amiga, mount your floppy, etc...), and save it with the primary name "autostart" (name, not description: you can put anything in the description, but the name has to be "autostart"),. making sure in the Misc tab to uncheck "Show GUI on startup before you save the config".
Just make sure you have a good-working build, as from experience I screwed up my AmigaOS build and had to plug the SD card into another RPi os build so that I could navigate to the config files to delete the autostart config.
UPDATE:
I cannot verify if an 880k Amiga-native disk will work, but if you're using a standard 1.44MB, you can mount the /media/usb directory (it might be /media/usb1 or usb2 as well is you have multiple USB storage devices mounted). I also made sure to set the Device name as "FD0" instead of "HD0" I had my virtual floppy disabled so I do not know if it causes issues if enabled. I verified by copying the files from my Workbench 2.04 ADF file to a floppy disk. I did run into some issues trying to copy from the Amibian CLI or MC due to Amibian mounting the disk as read-only (regardless of the tab), but I copied the files to the floppy via Windows 10.
In Amibian, when set to autoboot with GUI disabled from the floppy drive directory, it boots into the Floppy disk and first asks to copy files from the "Extras" dosk. If I select 0 to not copy, it then boots right into Workbench 2.04. So it does work, just in a round-about way.