I reported experience with my new installation yesterday - "Elyssa won't start" and that received some interesting responses.
Today I have just burned a new cd from the same downloaded iso file, after re-checking its md5sum.
It then occurred to me to view the disc contents, so I inserted it with Daryna running. Careful searching showed at /.disk/.disk_id (a plain text file) that it was built by Reconstructor 2.7, and the Reconstructor website was given, so I viewed that.
Among recent forum threads referenced on the home page were 2 referring to Busybox problems. Interesting, but above my Newby head.
Recent news was the rapid release of a version compatible with Gutsy - recent developer forum posts indicate difficulties with Hardy.
Recently also I have had several instances of the Busybox screen appearing when I start Daryna - much more frequently since installing Elyssa - now usually twice before it finally starts. It is necessary to restart each time using Ctrl+Alt+Del. Are any of the Busybox commands actually of any use in this context?
I have now also viewed the contents of my first burned disc from LinuxMint-5-r1.iso - as far as I can see it is identical to the new one, but I'll try a fresh install. Before that I'll save this post as a draft and try to boot Elyssa from Supergrub.
Returning to draft - Supergrub failed to boot Elyssa - it said it had fixed the MBR file but that didn't work, nor did Direct Boot. It reported File not found for boot/vmlinuz.
Also Daryna twice went to Busybox from Supergrub, ultimately I booted it from its own boot file. (This time). So I'll post this before trying another installation of Elyssa from the newly burned disc - at 4.7MB/s to a 52X Multispeed Fujifilm CD-R, as was the first one.