Yes, with 20220318, old and new driver are working as expected.

Ok, so let me understand correctly: When you use 20220318-1 release, the old ahci driver partitions and installs AROS, but partition is limited to 8GB (as expected). When you use 20220318-1 release, the new ahci driver partitions and installs AROS, and partition is not limited to 8GB. Is this correct understanding?

Both tests failed with old driver. During testing, I was using Aros One 2.4, which seems to be a specific issue of the distro. When I switched to Aros 32-bit version 20220318, the driver was running on the device. I am very sorry for this great missalert.

It's quite weird that old driver fails on newly partitioned drive :/ Can you do two tests: 1) repartition (Wipe option) the disk using ata.device and check if old ahci.device allows installing correctly 2) repartition the disk using ahci.device and check if installing 3-4 times work every time If in both cases installing using old ahci.device works, I will prepare for you a few versions of new ahci.device to try to pin point where is the problem. Can you also share vendor id and product id of your AHCI chipset?

Hi all, Thank you ppl, Just a quick update, AHI implemented , updeted version on Aros-Archives Uploads... Simple_PlayMusic added to examples (mp3/flac/wav) tested and plays fine.. usage Simple_PlayMusic test.mp3 or other formats...

maybe there is hope of bringing some other software:)

adrive.com is accessible with OWB for cloud storage

1.) Yes, the driver return the error pretty early. It starting something after fourth folder has been copied. 2.) "AHCI=slowstart" not fixing the error.

Alexander 'Selco' is still working on WCS will add improvements but the work will take a long time in the meantime we can use the current version which is new for us

Thanks for explanation. Additional question: What do you mean by "for first bits"? Does it mean that when you partition with new driver, reboot to old driver, start InstallAROS then it starts writing some files but process still crashes at some point and does not finish? Please test the new driver with AHCI=slowstart grub kernel parameter. Does it solve the "-6" problem?

1.) Yes, I getting issues when rebooting after partition has been created by installer. 2.) It happening every time I trying to installing on the harddisk. 3.) On the recommended hardware I have not tested yet (related to missing equipment), but well working device, where AHCI has worked before with old driver. 4.) Missed to add aditional informations. The correction is: "... harddisk with old AHCI-driver running on the partition, which has been made with the new AHCI-driver, working fine for first bits ..."

So if I understand correctly, with new ahci.device (version 0.9) you were able to partition the disk to have more than 8GB partition, but then when installing after reboot, you got the error? Does it happen every time you try to install? Is this happening on one of the recommended hardware? Does you added comment mean that on this hardware also installing using old ahci.device gives errors?

I was trying to installing AROS on native AHCI-device and got returned an access-error with code "-6". Same issue when manually copying folders or files into AHCI-device. The creation of an partition on AHCI was successful. Also the capacity of the harddisk was read correctly. Accessing the harddisk with old AHCI-driver working fine for first bits until some seconds after installing process started.

Thank you for your efforts to improve AROS.

Many Thanks

Hi All, Here is ahci.device for tests: https://axrt.org/development/ahci.device-0.9.i386-aros.zip When you open HDToolbox you should now see full disk capacity. Existing partitions won't be "extended", but if you "wipe" and InstallAROS, the partition should be created to cover whole disk or 127GB if the disk is bigger than 127GB. Let me know if it works for you.

yahoo mail works only opera 12 recongnitions, well delete windowsB)

many thanks deadwood

Hi, First visual effects of the emulator. A simplest hello-world program compiled under ABIv0 is now loaded, executed and unloaded under 64-bit AROS. See screenshot. It's good progress considering the short amount of time. Next objective is to start loading and using 32-bit libraries - any software more complex that this example needs to be able to use libraries. For anyone interested, here is the code of minimal program: [code] #include <proto/exec.h> #include <proto/dos.h> struct DosLibrary *DOSBase; __startup AROS_PROCH(Start, argstr, argsize, SysBase) { AROS_PROCFUNC_INIT DOSBase = (struct DosLibrary *)OpenLibrary("dos.library", 0L); PutStr("Hello from ABIv0!!n"); CloseLibrary((struct Library *)DOSBase); AROS_PROCFUNC_EXIT } [/code]

After some hours compilation went good, Thank you. Now i can try to port something.:)