With ahci.device originally included on 20220318-1, same thing happens, same error shown with new ahci.device

I attach 2 screenshots !

- The first one shows what you requested where I select the option Wipe Disk

- The second again using "20220318-1" with ahci.device orinary, you can see5e that a strange thing happens, basically on the Workbench the icon of a (CD1) appears "momentarily", then the icon seems to disappear.

On the PC in questine, there is no CD in the CD drive, with AROS One it seems not to happen.

Hmm, appearing of CD1.. that is very strange...

Is the AHCI/SATA autoselected when you start InstallAROS or do you select that manually?

Please also attach listing of devices from PCITool.

What is the capacity of the SATA drive you are trying to partition just to make sure it's not a disk size issue. I find that if the SATA drive is over 128GB then partitioning will likely fail to work.

No miker, the partition dedicated to AROS is 97.6 GB,

FYI, for testing I used a 230GB SATA SSD and I was able to partition it - AROS just creates a 128GB partition and leaves rest of disk space unasigned.

On my PCs I always create a DualBoot, with the Windows installer I create a partition for Win7/Win10, and then leave a "RAW" partition that AROS will use as its Hardisk.

Done this many times on many PCs and never had problems, maybe I will have an unsupported SSD ?

I don't understand this. When you use WIPE option you will delete your Windows partition so why are you refering to dual boot?

Also the screen shot from HDToolBox shows that partition table is not recognized, suggesting this is empty. Was this really an empty disk?

No Wipe Disk, if it finds a virgin "RAW" partition, it will ignore the partitions initialized by Windows, and will install only on that partition and will create the DualBoot, it is a safe operation done dozens of times and never was Windows deleted !

I can make you a video showing what I write !

Window is destroyed if the partition dedicated to AROS is initialized by Windows (FAT32/NTFS), in which case WipeDisk will destroy the Windows partition

In post #45 you said that you use use Wipe option.

Yes, it's better if you make a video showing all actions you are doing. Please make the video using 0.9b ahci.device.

I attach video created directly on AROS One, as you can see the partitions dedicated to Win10 will not be touched/deleted by "Wipe Disk"

I use this procedure also when I install a new version of AROS One, in this case I format from Wanderer the AROS volume and then from InstallAROS I choose "Use existing AROS Partitions ..."

The video is not quality because the VESA Video Card is too slow to record a quality video !

Ok, thanks for the video.

First, please provide me with the export of PCITool of your current hardware (before making any changes)

Then please confirm that Wipe option works correctly when you switch SATA to IDE compatibility mode.

If I disable "ahci" from the Bios of the PC under discussion, Win10 generates error and will not boot, possibly I can do this test on a PC where DualBoot AROS/Windows is installed in IDE mode.

In any case if important I still do the Test on that PC, maybe to use Windows each time I will have to change the Bios.

As soon as I get home I will send you the PCITool data.

I attach PCITool Log.

Done quelche tests on the PC in question, from the BIOS it is only possible to disable "ahci" (see screeshot BIOS), but it does not provide IDE enablement, although I think it should have been obvious.

If from the Bios I Disable "ahci", as mentioned Win10 (installed in "ahci" mode) will not boot generating errors on the operating system.

If with "ahci" Disabled, I try to start the Live Pendrive with AROS One which includes the new "ahci.device 0.9b", AROS One starts, but without the wallpaper and applications do not work.

On the other hand, if still with "ahci" Disabled, I try to start the Live Pendrive with AROS One that includes the old/original build "ahci.device", AROS One "won't start", it remains black screen !

Ok, if I understand you correctly you have two PCs;

First one is where you have AROS installed over IDE (ata.device) and dual boot with Windows

Second, the one which BIOS screen shot you've shown and where installation over ahci.device does not work.

Is this correct understaning?
If yes, have you ever had AROS installed on the Second PC?

Yes they are 2 different PCs, on both there is DualBoot, I also have other PCs in DualBoot AROS/Win7 and AROS/Win10

On the PC under discussion (Samsung R730), I never installed AROS, before on this PC there was a normal Sata Hardisk, now I mounted the new SSD and wanted to do DualBoot here too, encountering the problems mentioned.

Ok, thanks for explanation.

On Samsung R730 it's too bad we didn't test AROS with normal SATA harddisk. Then we would know if the problem is related to drive or to motherboard. There is a development of MSI (message signalled interrupts) that will come with next base system update. Maybe this will help on this PC.

Ok if I find a SATA HD available I will see to do the test with a Sata HD !

About Wipe Disk there are still doubts "that does not destroy the Windows partition" !

As said this does not happen if AROS finds and identifies a partition in any location as long as it is a "virgin" partition i.e. never initialized by any Filesystem !

I don't understand what doubts you are refering too?

The purpose of Wipe is to complete erase disk. If InstallAROS detects existing partition structure, it will default to option of "Use free space". In your case AROS is not detecting correct partition structure as seen by your screenshot of HDToolBox. Something needs to be updated in ahci.device to work with your hardware.

One thing was spotted on your BIOS photo.

You have Large Disk Access Mode set to DOS. See if changing this to Other will make ahci.device work with your disk drive.

@Studenteer

The problem is not the installation, but the "Wipe Disk" initialization which does not work "only" on this PC, on other PCs there is no problem installing AROS One either in DualBoot or alone.

The software you mentioned has nothing to do with "Wipe Disk" functions, which is used to initialize the partition (Write RDB, similar to MBR on Windows)