deadwood, regarding bug #140, when using the Relabel command to rename a volume, you don't need to reboot the system to see the new name (as in the bug report), actually just do a "Refresh" on Wanderer, you get the same result by using the Backdrop comado "Menu Wanderer", just turn Backdrop activate/deactivate This procedure also works when changing the icon to a Volume or folder, after "Refresh" from wanderer, the new icon will be visible.

Voted for #116

voted:)

deadwood, about Dopus4, the 64Bit version did not work well, I hope the 32Bit version will work !

Hello, This month's IBOTM marks half a year of running this activity! To celebrate this, this time [b]not one, but two[/b] bugs will be selected. First bug will be selected using regular rules via the poll above. Second bug, will be selected to award people who have been consistent on voting on things they find important but didn't have enough luck each time. The second bug will be selected by highest number of total votes in last 5 polls and combined with this poll. The current total scoring is as follows: #125 -> 7 #116 -> 6 #105 -> 8 In case both method end up selecting the same bug, the bug with second most total points will be selected. As usual, you can read descriptions of bugs here: [b][url]https://github.com/deadwood2/AROS/labels/IBOTM[/url][/b] Have fun and vote!

[quote name=AMIGASYSTEM post=4736]@AMIGASYSTEM - Great work deadwood, will the 32Bit software in emulation keep its speed, or will it be slower ?[/quote] It will keep it's speed.

Thank you:)

Great work deadwood, will the 32Bit software in emulation keep its speed, or will it be slower ?

[quote name=deadwood post=4733]@deadwood - Hi, Looking at available information, C++ 17 was available in GCC since version 7/8. We are now at 6.5.0 so upgrading the compiler is the first requirement. Timewise, unless someone else steps in the does the work, I don't see upgrading the compiler before end of this year and probably also before end of next year (but planning for next year is not really clear at this point in time).[/quote] Many thanks, and I ceratinly appreciate there are far more important things going on with AROS right now; I just thought I'd check in the (unlikely) event the Hollywood authors had missed something, Cheers, Nigel.

Hi All, The emulator reached today first major milestone. All 32-bit libraries needed to run ABIv0 Calculator are loaded and Calculator is now able to open it's window directly under 64-bit AROS. This is a native 64-bit AROS window so there should be full interaction between windows of programs running under emulation and native 64-bit programs. A user should not notice he is running a 32-bit program. Some technical notes: Loading libraries was problematic at first, but after adding some needed structure, they started loading mostly on their own, which was very positive as it means less work for me. The part that I'm focusing now turned out however to be more complex and harder than I expected. The objective is now to implement "proxy" graphics.library and intuition.library that will take 32-bit programs calls and "forward" them to native 64-bit libraries, so that 32-bit programs render graphics and gadgets in integrated way.

Hi, Looking at available information, C++ 17 was available in GCC since version 7/8. We are now at 6.5.0 so upgrading the compiler is the first requirement. Timewise, unless someone else steps in the does the work, I don't see upgrading the compiler before end of this year and probably also before end of next year (but planning for next year is not really clear at this point in time).

A new Hollywood plugin 'Pangomonium' has just been realeased which gives much better control of text (e.g. adding superscripts/subscripts and being able to change font type or size within a text object). Unfortunatley there isn't a verion for AROS. I asked about this and the reply was: "It's not possible on AROS with their current SDK. It's the same reason why Polybios and the XLSX plugin aren't available on AROS: All those plugins need a compiler capable of creating LoadSeg()able binaries which use C++17 code and exception handling." So I was just wondered if the required additions were in the development plan for any point? Many thanks, Nigel.

@deadwood About "Wipe Disk" was not referring to my Hardware, it was a kind of "warning" for all those who would like to do a DualBoot, to be careful not to destroy Windows or other OS installed on the same Disk. Regarding Bios I changed from DOS to Other, but nothing changed ! I encountered the same problem.

@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)

@Amigasystem , please try following: 1.) Make fresh installed USB-Stick of your latest AROS One with deadwood's AHCI-driver. 2.) Boot USB-Stick and remove following files in Live-enviroment: C/p2t C/flite C/flite_time C/PlayNoSound System/AROS One/Install Icons Apps System/AROS One/Install Icons Drawer System/AmiTranslate/NotoSansJP-Regular.ttf Tools/PasteQuick/Pastequick Tools/MPlayer/mencoder Tools/MPlayer/MPlayer Tools/MUIInspector/MUIInspector Tools/DirList/DirList Tools/FryingPan/Libs/mui.interface.dbg Tools/FryingPan/Libs/Optical.dbg 3.) Do regular install, but just core-system and grub (important!) 4.) Trying to boot up and check, if system working as installed on computer. If everything working fine, I maybe found the issue.

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.

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.

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 !

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.

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.