I use vdisk.device to build a large RAD volume. I have a working set up and VD0 mounted on A2000 machine + TekMagic 060 + OS 3.9: RAD volume survives a reboot and can boot an OS. However, the same mechanism applied to a second A2000 + pistorm2K + Pi 3A + Emu68 1.0 + kickstart ROM 3.1 / 3.9 / 3.2 + OS 3.9 / OS 3.2 allows survival of the RAD volume but ...
VD0 never appears in Early Startup
... while trackdisk.device, brcm-sdhc.device and buddha.device are detected.
Although vdisk.device has never been considered as a valuable tool in the past, a large RAD volume makes sense inside Emu68: entire OS 3.9 fits easily in it, can be transferred from SD card in 12 s at first boot, and can be executed in a disk 200 times faster than what Zorro II speed allows. This is the way I am using the A2000 now with the possibility to play FLAC file without specific decoding hardware.
Why vdisk.device is not presented to Early Startup ? How to solve this issue ?
Hello,
I use vdisk.device to build a large RAD volume. I have a working set up and VD0 mounted on A2000 machine + TekMagic 060 + OS 3.9: RAD volume survives a reboot and can boot an OS. However, the same mechanism applied to a second A2000 + pistorm2K + Pi 3A + Emu68 1.0 + kickstart ROM 3.1 / 3.9 / 3.2 + OS 3.9 / OS 3.2 allows survival of the RAD volume but ...
VD0 never appears in Early Startup
... while trackdisk.device, brcm-sdhc.device and buddha.device are detected.
Although vdisk.device has never been considered as a valuable tool in the past, a large RAD volume makes sense inside Emu68: entire OS 3.9 fits easily in it, can be transferred from SD card in 12 s at first boot, and can be executed in a disk 200 times faster than what Zorro II speed allows. This is the way I am using the A2000 now with the possibility to play FLAC file without specific decoding hardware.
Why vdisk.device is not presented to Early Startup ? How to solve this issue ?
Many thanks.