At this moment please report only results of my ISO builds to avoid any confusion.

With VESA tests two scenarions:

1) add noacpi; if that does not work
2) add noacpi, change ATA=32bit to ATA=nodma

Done some tests with D09, D10 and D10+P05, the test results are idendic for both Acer and Samsung

With D09, D10, the screen remains black with both "noacpi" and "ATA=nodma" + "noacpi".

With D10+P05, with "noacpi" and with "ATA=nodma" + "noacpi" I get instead a Guru on "IntelGMA" see screnshoot 002

With standard GRUB sometimes an error appears after the black screen see screenshot 001.

surely your hardware is incompatible it can happen

No, they were supported PCs before! in safe mode they work

ok understand

Which option were you selecting in grub when testing? Option 1) native or option 5) VESA 1024x768?

The "IntelGMA" error visible on screenshot1 actually proves that VESA is working for you - seeing this would not be possible without VESA - so this is good news.

Please take 64D10+P05 ISO, select option 5) VESA 1024x768 then add "noacpi", don't change ATA and let me know what happens. If that does not work, repated the same process with option 2) true color VESA graphics.

All the tests I mentioned I did with VESA 1024x768, tested the VESA true colour mode and got the same 'IntelGMA' error

That is very strange o.O.

Can you edit the 64D10+P05 ISO and move IntelGMA + IntelGMA.info from Devs/Monitors to Storage/Monitors and they try again with VESA 1024x768 and noacpi switch?

OK it worked on both ACER and SAMSUNG, but I also had to move WMware and WMvare.info, otherwise I had an error on 'WMware', the remaining Monitor files do not give any problems!

Ok, glad it worked!

Can you check that your VESA 1024x768 command line has 'nomonitors' switch? Intel and VMWare you should be giving you issues when this switch is there.

Also, did you have to use 'noacpi' to get it to work eventually?

I did not understand what you mean by "command line has 'nomonitors' switch?" can you attach a screenshot

However in the Grub I used 'noacpi' without the parameter "'nomonitors'".

Without 'noacpi' I get a black screen and then after a long time that request errorre shown before comes up (AFFS error)

Ok, here is how the command line should look like, with both nomonitors and noacpi switches, see attached.

OK. "'nomonitors'" + "noacpi", works fine, Bootmenu also works fine

I've noticed that in VESA mode on native PC, both on Samung and Acer, some applications go into Guru, for example "Reboot", "Shutdown" (on WMware they work fine), while "protrekkr-2.7.6" on VESA PC goes into Guru as on WMware.

Even BoingIconBar goes into Guru sometimes on VESA mode PCs as on WMware!

Ok, my question was if you had "nomonitors" in the command line before moving files from Devs/Monitors to Devs/Storage. Having "nomonitors" should stop the IntelGMA from loading so you should not get the crash in first place.

protrekkr has crash also on VBox, so for now I assume there is a problem with program itself. BoingIconBar I have on my TODO list.

Protrekkr on my HP Z400 works on the laptop no it's a compaq 6720s I connect with the phone it's the only way to use the network for the rest everything works except when I reboot or turn off I attach image

Ok deadwood, File Monitor in DEVS + "'nomonitors'" + "noacpi", works fine

I installed V11 in DualBoot with Win10 (old AROS One was inistalled in DualBoot on the ACER PC), Windows appeared in the Grub Menu of V11, but Win10 does not start error "Win7 NTLDR is missing".

AROS side Windows Partitions are intact and all files are present, I have to do some tests installing AROS One 2.7 x86 on this PC to check if the problem is not caused by V11, I'll let you know

EDIT

Installed AROS One 2.7 x86 on the same PC, Win10 now works fine in DualBoot, probably with V11 it doesn't finish the DualBoot properly

Ok, this then means new 32-bit build also most like has this problem.

Yes if you are referring to hardware compatibility, in fact now on ACER which previously did not work the new builds with "'nomonitors'" + "noacpi", now also the latest build including AROS One 2.7 works fine

Finally I can now test 32Bit Buid on all my PCs! the DualBot- works fine with 32Bit

On VirtualBox on v11 i noticed a strange thing, if I add the BootMenu in the Grub the menu is cut off, it shows only 4 lines.

The same ISO on native PC and WMware the GRUB Menu is complete and works fine, strangely VirualBox with 32Bit ISOs does not have this problem ... I have to investigate.

@AMIGASYTEM

Just for references, which versions of VMWare and VirtualBox are you using?

VMware Player 12 (Faster version for Win7 64Bit)
VirtualBox 7.0.22 r16 (Latest version supported by Win7 Bit)

On the fixed PC where I work, I still use Win7 64Bit for convenience