Last days i wanted to give the 64Bit Version of Haiku a try. Therefore i burned a anyboot-CD and tried to boot for install.
No success -> landing in the KDL. For further testing i then used the 32bit hybrid anyboot-CD (hrev51366) and tried it on all my systems (2 Desktops, 2 Notebooks) all with the same negativ (see subject) result.
The latest offered live-CD with hrev47380 boots all my 4 systems and on all was Haiku successfully installed bevor in that way. I must say, the all are older machines with normal msdos-partitioning with a mbr. The bootmanager was GAG 4.10 and all installed linux distributions were forced to install grub in the root/install partition and not the mbr. It seems to me that the bootloader code of the anyboot-CD works somewhat different to that of the live-CDs?
I then tested a little bit more to found out that difference. That are the steps i’ve done:
I deleted the haiku partition with a gparted live-CD => no success
I uninstalled GAG 4.10 with his own bootcd and made one linux partion activ and bootable. The system then boots that system correct. The Haiku anyboot-cd fails with the same PANIC than before.
I created a grub-install in the mbr with a bootcd called Rescatux and the linux systems are all bootable from that menu. Haiku still fails.
In the end, i first had success in deleting all on the disk with gparted by creating a new partition-table. Then the anyboot-CD boots as normal. But that is not really a solution - i think:slight_smile:
IMHO from the viewpoint of a potential unexperienced new user of Haiku would it not be better to offer a live-CD (instead/additional of the raw-image) as in hrev47380? raw-images are very limited for end users: Lack of space on the created mini-partiton and a not expandable bfs filesystem.
That should not be a critique but only a appeal.
Has anybody an idea, what lets anyboot-CD fail on all my systems?