Apologies, here is the link [url]https://sourceforge.net/projects/afilemanager/[/url]

Link SourceForge not Work

I do intend to support x86_64 once the foundation is stable, and ARM is also interesting to me — especially for small, low-cost systems such as Raspberry Pi-class hardware. I would rather stabilise the AROSA architecture on one target first than spread the work across several architectures too early. Out of interest, which platform do you think would be the most useful target for future AROS development and support? For this first AROSA/AFileManager preview I chose i386 because that is the environment where my current FPC toolchain and integrated components are tested and stable. Longer term I am interested in other platforms, but I would be very interested to hear which architecture the AROS maintainers and users think makes the most sense to prioritise next.

i386? seriously?

Version 0.4 of distro piAROS ready to download: [url]https://archive.org/download/piAROS[/url]

[b][size=20]AFileManager Public Preview Release[/size][/b] I am pleased to announce the first public preview of [b]AFileManager[/b], built on the emerging [b]AROSA[/b] application platform for [b]AROS[/b]. This release should be considered a [b]technology preview and architectural demonstrator[/b], rather than a finished application. AFileManager is my attempt to explore a more modern direction for AROS application development while retaining the efficiency, responsiveness and distinctive character of the Amiga architecture. More importantly, it is the first substantial public demonstration of the wider AROSA architecture in a real application. [size=16][b]Download[/b][/size] The AFileManager / AROSA Public Preview can be downloaded from SourceForge: [b]SourceForge:[/b] [url]https://sourceforge.net/projects/afilemanager/[/url] The main release package is: [b]AFileManager-AROSA-Preview-0.8.6.8.0.2-i386-AROS.zip[/b] An optional CD / ISO distribution image is also available: [b]AFileManager-AROSA-Preview-0.8.6.8.0.2-i386-AROS-Media.iso[/b] The ISO is intended as installation media for an existing AROS pc-i386 system. It is not a complete bootable AROS distribution. Documentation is included with the release and is also available separately: - AROSA-AFileManager-Quick-Start.pdf - AFileManager-User-Guide.pdf If you do not already have a compatible AROS installation, a current AROS pc-i386 build can be obtained from: [URL]https://www.aros.org/download.html[/URL] [size=16][b]What is AFileManager?[/b][/size] AFileManager is a completely new file manager developed specifically for AROS and AROSA. It does [b]not[/b] depend on MUI, Zune or another desktop application framework. Its interface is built directly on [b]Intuition and the native AROS/Amiga graphics system[/b], together with a growing set of AROSA graphical controls and reusable services. The current preview already provides a substantial set of file-management and desktop-oriented features, including: - Dual-pane file management - Multiple file-manager tabs - List, Details, Icon and Workbench-style views - Editable path navigation and breadcrumb controls - Standard keyboard and text-editing operations - Copy, paste, delete and drag-and-drop functionality - Context menus and configurable toolbars - File preview and metadata handling - Image preview, including common bitmap and IFF-related formats - Archive inspection and compression support - AmigaGuide viewing through the AROSA presentation system - Limited HTML and CSS rendering - Basic sound-file support - Modern window-management features, including window snapping - Integrated help, information and configuration interfaces Some areas are intentionally incomplete. The HTML and CSS implementation currently focuses on establishing the foundations of a lightweight document and presentation engine rather than attempting to provide a complete modern web browser. Multimedia support is still limited, and animation support has not yet been implemented. Behind the visible interface, AFileManager also exercises AROSA's messaging architecture using [b]native AROS tasks, message passing and message queues[/b], allowing applications and services to cooperate without becoming one large monolithic program. [size=16][b]What is AROSA?[/b][/size] AFileManager is also a demonstrator for something considerably larger. [b]AROSA is intended to become a modern application platform for AROS[/b], providing reusable infrastructure that applications should not need to implement independently. Current work includes, or is laying the foundation for: - Reusable graphical controls and UI infrastructure - Application and resource invocation - Presentation and document services - File-format handling - HTML and CSS presentation - Font and text rendering - Application configuration - Logging and diagnostics - Message-based services - Registry and persistent data services - Common dialogs and reusable components - Application descriptors and capability descriptions - Structured application startup and environment management - User-defined workspaces based on the Amiga screen architecture The objective is to provide a consistent application layer so that future AROSA applications can share common infrastructure instead of each implementing its own incompatible version of the same functionality. [size=16][b]Workspaces and the Amiga Screen Model[/b][/size] One of the ideas I am particularly interested in developing within AROSA is [b]user-defined workspaces[/b]. The Amiga introduced a powerful multi-screen architecture decades ago. Rather than replacing that concept with conventional virtual desktops, AROSA can build upon it. A workspace can represent a dedicated working environment for a particular activity, for example: - Development - File Management - Communications - Graphics - Documentation - Media - Administration Each workspace can maintain its own applications, window layouts and working environment while still using the native Amiga screen model underneath. The aim is not simply to copy virtual desktops from other operating systems, but to evolve the Amiga's original multi-screen concept into a more structured system of persistent, purpose-driven working areas. AFileManager is already being designed with this model in mind and is one of the first applications being used to explore how such workspace management can operate in practice. [size=16][b]Native AROS Development[/b][/size] This is not an attempt to recreate Linux, Windows or another operating system on top of AROS. I believe AROS should continue to build on the ideas that made the Amiga architecture unusual and interesting: - Lightweight operation - Native tasks - Message passing - Multiple screens - Responsive graphical applications - Small and efficient programs At the same time, computing environments and user expectations have changed enormously since the original Amiga was introduced. My goal is therefore not simply to preserve the past, but to explore what a [b]modern Amiga-inspired computing platform[/b] could become today. [size=16][b]Compatibility[/b][/size] There is one important compatibility limitation with this preview. The current AFileManager and AROSA builds target the [b]current AROS development branch and its newer application-launch environment[/b]. They are therefore [b]not compatible with older AROS installations, including existing AROS One installations, unless the required newer AROS components are present[/b]. This preview depends on functionality that is not available in older environments, and maintaining full backward compatibility at this stage would significantly restrict the architectural work being explored. [size=16][b]Included Technologies[/b][/size] The preview contains or integrates several technologies that are also becoming reusable AROSA platform components, including: - ZIP and UnZIP support - NanoSVG - SQLite - Supporting compression and file-format libraries The intention is for these capabilities to become reusable across AROSA applications rather than existing only inside AFileManager. The [b]ATransfer[/b] transport and web-service framework is [b]not included[/b] in this release. ATransfer remains a separate project and still requires completion of its Linux and Windows service components before I consider it ready for public release. [size=16][b]This Really Is a Preview[/b][/size] There will be bugs. Some functionality remains incomplete. Some user-interface behaviour still requires refinement. Performance and rendering still need improvement in a number of areas. This release marks the point where I feel the project is mature enough to put in front of the community for testing, discussion and criticism. [size=16][b]Why Release It Now?[/b][/size] Developing AROSA is a substantial undertaking. AFileManager was never intended to be just another file manager. I started with it because I needed a real application large enough to exercise the graphical controls, services, messaging, presentation system, resource handling and architectural ideas that AROSA depends upon. In that sense, AFileManager is the proving ground for the platform itself. With this preview, I would like to understand whether there is genuine interest in this direction and whether the community believes these ideas are worth developing further. [size=16][b]Feedback Welcome[/b][/size] I would particularly welcome: - Testing on real AROS systems - Bug reports - User-interface feedback - Feature suggestions for AFileManager - Ideas for additional AROSA services - Architectural discussion and criticism - Developers interested in experimenting with or contributing to the platform Positive feedback is appreciated, but constructive criticism is equally valuable. At this stage, understanding what works, what does not work and what people would like to see next is very useful. [size=16][b]Looking Forward[/b][/size] [b]AFileManager is the application you can see today. AROSA is the platform being built underneath it.[/b] The long-term goal is not simply to preserve what the Amiga gave us, but to explore how those ideas could have evolved if the platform had continued moving forward. My ambition is for AROSA to help bring Amiga-inspired computing into the 21st century while remaining recognisably rooted in the architecture and principles that made the platform interesting in the first place. [b]This preview is the first public step in that direction.[/b]

Very nice! I love that iconset

I decided to switch to an M.2 NVMe drive. Small 16GB drives have low power consumption, which the USB port should be able to handle. I ordered an Intel Optane M10; I'll let you know how it performs when it arrives. Amelinium 1.3.6 released :)

Indeed, when I booted from RAM, it updated without errors. I thought I had a good microSD card (Sandisk), but I got an unpleasant surprise. The question is whether it's the file system or the card. Overall, it's bad news :(

Hi, Nothing different so far, loads sites as normal and youtube works. I do run the browser out of RAM: as I do not trust sd cards yet

I have a question for Raspberry Pi users. Does the latest Amelinium 1.3.5 build work for you?

Still some work to do, but... [img]https://i.imgur.com/Ov5zAvf.png[/img]

I've run some tests, but there are still issues. I tested it with both an English keyboard and an Italian keyboard. Keyboard English: Keys Not Working Underscore > < ù Shift +ù Shift + > Shift + @ Shift +; Shift +. Shift +Underscore Shift + > Shift + 8 Tabulator Numeric keypad Numpad Minus Numpad * --------------------------- Keyboard Italiano: Keys Not Working > < Shift + : Shift + > Shift + * Shift + ? Shift + 7 forward slash Numpad * Numpad slash ------------------------

@bsek Thank you so much!!! My bootloader version was from May 2015, updating to the latest version resolved it. I had no idea a bootloader fix for this existed. Wifi works also, this will be so much fun!

I've modified the system Time (Prefs) to update the time from the internet. The offset to UTC is pre-populated from the time zone settings. All that remains is to account for daylight saving time changes (summer/winter time).

@jimaz is the 500 you own old? Can you post your bootloader version (or might even try to update it)? The easiest way to find it is to boot linux on your pi, it should be printed at the top of the bootscreen.

Have you tried a different microSD card? Or reformat it and re-burn the files. Also, try the latest nightly build.

[quote name=bsek post=15069]@bsek - @jimaz Try the other hdmi port, only hdmi 0 is supported at the moment on the pi 5/500/500+[/quote] Thanks for the suggestion @bsek - however, I used hdmi 0, switching to hdmi 1 also just shows the mouse pointer.

[quote name=AMIGASYSTEM post=14772]@AMIGASYSTEM - Right now, some of the Shift, Alt, Caps Lock, Caret, and asterisk combinations aren't working, but I've noticed that the Windows PC version has the same issues. What keyboard layout is GrafX set to internally?[/quote] In this AROS build, text input follows your active system keymap. I found a bug in our revision 4 keyboard conversion. On the Italian layout, Shift+ì failed to produce `^`, Shift+`+` produced `+` instead of `*`, and AltGr+ò failed to produce `@`. Accented characters were also lost. [b]Revision 5 fixes this[/b], verified against the AROS Shell with the Italian keymap. It is available [url]https://github.com/tomaszstaniak/aros-grafx2/releases/tag/v2.9-r5[/url], or through `apkg update` followed by `apkg upgrade grafx2`. Keyboard shortcuts are handled separately and were unchanged by this fix. Dead-key composition remains unsupported. This was a bug in my AROS patch. This doesn't explain the Windows issue; please provide the exact failing combinations and the field or command where they fail.

@jimaz Try the other hdmi port, only hdmi 0 is supported at the moment on the pi 5/500/500+