I can control that to an extent, and I set all the quality settings to the max figuring it would deliver the best clarity because earlier attempts had some of the text in the shell blurring together because of the screen's glow. I'll see about making it a more reasonable size next time.
Well, i am currently bound to full-hd but tbh 320x200 or something to that extend should be enough
But on a more serious note, the glaring is still there because the rates of recording and monitor are not in sync and there is not much that can be done about that (unless you happen to have a high-speed camera or an output capturing device).
The ABIv0 build from last Monday.
Oke, thanks for the info.
There is no secure boot option, unless I set to boot mode for UEFI. And, I have changed the BIOS to allow USB legacy support, set boot mode to legacy support, set boot priority to legacy first, and changed the OS optimized defaults to Other OS. But, the problem is that I cannot find a way to actually change the SATA hard drive's mode to AHCI or IDE.
I understand. Sorry for the mantra but it happens on occasion that instructions are not always followed. I had to work with stills and therefor was not sure which way your BIOS implemented it (seems to be the other way around as i thought).
That should be ok, except for the fact that you seem unable to change SATA mode. Usually that can be solved with the grub option(s) as mentioned in the caveats and workaround threads.
Didn't know that I can do that. I'll see about giving it a whirl.
afaik you have two options there, either native boot from cd/dvd and install directly onto SD or use your virtual machine.
Do note though that when going the raw device way in case your host machine has an sd-card reader/writer that you can only do that when you mount the sd-card as raw device to your VBox (please read the VBOX manual thoroughly on that subject). That is a bit risky because it allows you to mount the wrong device (such as your internal HD or a pendrive that happens to be inserted). Numbers are everything there so make sure you check and double-check or are able to revert in case something goes wrong.
I know that the premade Icaros Grub options allows for the user to enter early boot without having to use any keyboard shortcuts. Would that still work? Never mind.
I still answer in case someone else is reading this thread:
Yes, that should still work although i don't know the grub option from memory so i would have to check in the source-tree of AROS. The mouse-button-press should be able to do the trick though (unless your USB hardware is entirely unsupported by AROS).
So, try to keep everything restricted to ABIv0. Okay.
Well, you can of course do as you wish
It is just that i'm unable to provide any help that is accurate enough. I stopped experimenting with v1 when things changed about every other day and i was unable to keep up with the changes.
EDIT: Actually, now I'm wondering something. Just to make sure that the problem isn't a complete OS lock-out (And just a problem with AROS), should I try to see if I can install a different OS, something light like FreeDOS or TempleOS (Something I can easily remove)?
Yes, i was already thinking to suggest that but the first thing that popped into mind was a linux distro as that is usually the easiest to install but afaik that supports secureboot in this day and age (unless locked entirely) ? But indeed you can try that in order to verify.
On another note that also happens to be mentioned in that same thread as methanoid posted, nikos seem to have experienced something unusual with regards to the device numbering depending on enabling ahci or not but your HD-toolbox from successfull v1 boot seems to report it correctly. Ah well, you probably have digged yourself through many of the threads already....
