David states that the 2 releases of os2ahci.add v1.32 are identical apart from the bldlevel info
Personally, I believe David.
If I ever knew what motherboard, and processor, that Pete has the problem with, I have forgotten (I see it was posted, after I wrote this). I have also not heard of another user with a problem (or I have forgotten). I use AHCI on multiple AMD processors, and multiple Intel processors, with no problems (with and without UEFI). The most likely source of the problem would be an early BIOS implementation, that was never fixed by the manufacturer (but that doesn't explain the difference that is seen between AHCI 1.32 in eCS b2, and AHCI 1.32, from the AN package). In that case, it would probably be a good idea to switch to IDE mode, and avoid using AHCI.
That's totally wrong. VirtualBox is quite slow and less acurate compared to other solutions. There is also no integration for OS/2. The guest driver misses all advanced features. The mouse driver integration can only be used in 1 PM session - better not try fullscreen OS/2 or DOS sessions including Win-OS/2-fullscreen.
I did a lot of ArcaOS testing in VBOX under win 10 on my Lenovo ThinkPad T510, using various settings. It works quite well, and performance is only a little slower than in a real machine (in fact, it may be faster in some ways). Not sure what you mean by "less accurate". It either works, or it doesn't. The guest driver doesn't handle shared folders, but network folders work fine. What else is missing? FWIW, I probably didn't try DOS/WIN16 in VBOX.
I do have a problem with VBOX under win 10 on my Lenovo ThinkPad L530, but I am convinced that it is caused by a bad BIOS update. It suddenly broke both ArcaOS and eCS, under VBOX, after the last BIOS update (which I haven't tried to fix, yet).
VBOX under OS/2 has problems, but the new 5.0.6 version works about the same as the old 1.6.1 version, with a winXP guest. Neither one is considered to be more than Alpha code anyway.