Thank you for the extensive feedback Transdude1996
Let me start with saying that i've never encountered the exact same error message that you currently seem to be confronted with. From experience my suspicion is that either the boot medium is damaged or AROS tries to locate the required libraries on a device that isn't accesible at that time during the boot process (hence the suggestion to disable internal boot device). fwiw we had a time period where AROS tried to locate the system files from the internal fat/ntfs disk when the volume label met "SYS" and when the fat/ntfs driver was enabled during boot (this should not be able to happen anymore).
It didn't work. I'll try going a bootable USB drive next (Wasted enough discs).
Yes, wasting discs is another good reason to switch to pendrive. Another one is that it is much easier to travel with that pendrive and insert it into any other machine to see if AROS is able to boot from it.
I just don't care for how..."unpreservable" USBs are in their function.
They aren't. Just do not use the pendrive to work from but rather use it as installation media. I do have pendrives that i use as 'work system' but that is just because i often find myself wanting to quickly test software on particular hardware.
Which nightlies, the ABIv1 or ABIv0 builds? Tried using the 64-bit build from the former source,
Sorry, my bad.
Icaros desktop is based on ABIv0 while the more advanced is ABIv1. For better information feedback it might be advisable to test with abiV1 but if you wish to stay on par with Icaros/AspireOS then try to replicate with v0 nightly. The v0 nightly boot should be 100% similar (minus perhaps added/removed drivers in AspireOS/Icaros).
I would also suggest to stick to 32-bit for the moment (AspireOS and Icaros are as well).
and the error I encounter upon loading the desktop is:
Software Failure!
Just for the record. In either case (nightly or Icaros boot) when you say "upon loading the desktop" does that mean you already have a GUI interface or is the software failure presented to you in the console (grub) shell ?
In case your setup is presenting the errors into something that looks like a GUI, then try to do a cold boot and press the space-bar directly after grub has selected which entry to boot from (timing is important there). It alows to bypass the workbench loading script. If it is in any way related to "loading wrong drivers" then you should be able to boot into a AROS GUI shell and be able to work with boot logs (which are far more elaborating). See debug=memory in grub and biftec to copy that boot information from memory into a conole window (or disk).
Im also puzzled by the 64 bit booting error message that refers to hidd (might be similar in nature as dizzy described earlier)
So, format the hard drive to FAT before I insert the AROS disk? OH! I really should have mentioned this in the OP, I'm installing this on a fresh 500 GB hard drive that I just received in the mail. Should I try formatting the drive to FAT first and then insert the AROS disc?
No... please do not format fat32 but rather remove any partion information. That is what aros installer needs as well as it uses free space (not allocated with fat) when attempt to install from the installer script. In case AROS is unable to prepare your drive (mind the bootblock protection in BIOS when present or even worse hidden (boot) partitions that Windows is famous for) then we can try to deal with that later.
If user dizzy is the same person as dizzyofCRN from the old aros-exec forums then i would stick with his observations and try to remove the ntfs/fat32 handler. If what he writes is the case then AROS seems to indicate wanting to try loading some drivers from your internal HD (or at least tries to make an attempt). I find the context in relation to your issue a bit odd though but that might be my inexperience with (your) specifc hardware.
@paolone and/or system developer:
Has that bugger sneaked into there again (that you are aware of) ?
