It may be possible to do the same by setting a button command in Dopus4. When a user highlights a file then presses the "Convert" button it sends the filename to the converter/editor. Also, Magellan has "Open With..." that can be used in a similar way.

AMIGASYSTEM, That is correct. In the MultiView Icon Tooltypes you can set editors for EDITPIC=, EDITSND=, EDITTXT=. EXPORT= is the Tooltype for the media converter. The text string for your chosen application follows the '=' in each case. Yes. If we had an "FFMedia" Converter (FFMpeg GUI Frontend based on WinFF) we could set that as "EXPORT=AROS:Utilities/FFMedia %s" then when the user selects Project->Export the current filename is sent to open the media converter. That's how it works. It's really easy. Once I adjust the Zoom functions which need to be updated then I can submit the changes for MultiView. In a future update a few more options can be added such as Picture->Centered on Screen to open each new picture in the center of the screen rather than at the 0,0 origin in the far top, left corner. The Save Settings will save the m settings to a text file. At that point you won't need to save settings in tooltypes. Use mvsettings.txt instead. Since we don't have a way to save settings currently it doesn't make sense to include Centered on Screen. Also planned is multi image support such as opening icon files or tiff files or other image containers (mng, ico, icns, etc) then use arrow keys to toggle image display (prev/next). But that's for next time. :-)

The addition of ‘Edit File’ to Multiview is brilliant news; this means that all text files and images can now be edited, thanks In future, when music editors become available, it will also be possible to edit the sounds supported by Multiview Basically, you’ll be able to use ‘Edit With…’

In order to continue updating and testing Datatypes I had to update MultiView. I added "Save As" on the Project Menu and "Edit File" on the Edit Menu. These will work for all Datatypes not just picture Datatypes. Save As will save a "new" copy of the file using the datatype save function. So if I open a wav file in MultiView and chose Save As it should save a wav file to a new filename. And if I open a picture and Save As it uses the datatype save function to save it. That's how I have been testing load and save functions of the Datatypes. The other feature that I added is Edit File. The Tooltypes are set in the MultiView Icon as far as the editor of choice. EDITPIC=AROS:Tools/Zune view %s will send the current picture filename to open Zune view when the user chooses Edit->Edit File. So many times I've opened files in MultiView such as text files or pictures then I wanted to edit them. Rather than open the editor then navigate to the file to open the Edit File method is so much easier.

With the Intel Pro 3945ABG 802.11a/g/n card, Wi-Fi does not work on either the AROS 32-bit or 64-bit

With the Intel High Definition Audio card, the audio does not work on either AROS 32-bit or 64-bit

Success!! I updated the version of MultiView in the sources from 1.7 to 1.8 by adding "Save As" and "Edit File". This version doesn't use strings.h instead it uses MultiView catalogs. So it was really easy to update it. Since EXPORT and EDIT options are set in the MultiView Icon Tooltypes we can assign FFMedia or DTConvert or whichever converter. Later I'll add the Zoom functions then it will be complete and ready to commit to the code repository. See screenshots...

So it looks like I will need to update the current MultiView. At a minimum I may need to add Project->Save As, Edit, and Zoom functions which have been updated. DTConvert is used with the Export function. Edit uses MultiView Icon Tooltypes to open your editor of choice. These will be some nice additions to MultiView. Some of the OM_NEW return types had to be edited for several Datatypes to get them to work properly with DTConvert. DTConvert should be rewritten as MUI/Zune. Sometimes I feel like there are so many projects but time is limited.

The conversion didn't take long. I first made a complete backup of my native installation to an SD card. After attaching the SD card in Virtual Box the first thing to setup was Magellan. Then I mostly copied the appearance items, backgrounds, icons, Themes and Theme Manager. I call my "distro" AeROS Desktop. It's a Light Installation of AROS with the look and feel of Icaros Desktop. :-) But I have a couple of issues. Theme Manager is an AmiLUA script but the program needs to be re-compiled for ABIv0. However, I can't find sources for AmiLUA. Also, the version of MultiView in the U3 stable version doesn't have Project->Save As that I need for datatype testing. So I have to compile my MultiView version 1.8 or I could just update the version 1.7 in the repository then compile it. :-) Setting up AbIv11 testing environment will be similar to this procedure. That's the next step. And refreshing my AROS sources. :-)

Here are some screenshots of my new 32bit test environment in VirtualBox. The native version is faster and more responsive. But Virtual Box is easier for testing. It's based on the U3 stable version for ABIv0 which has the latest system files. It works with the latest ABIv0 Build System for compiling. As is the tradition we have the before and after the customizing. The full screen picture is the native AROS on real hardware. The two windowed ones are before & after in a Virtual Box virtual machine.

Hollywood currently only supports 32-bit, but it is possible to run many Hollywood applications on AROS 64-bit using the built-in ‘EmuV0’ emulator https://www.forums.hollywood-mal.com/viewtopic.php?p=22426#p22426 The attached thread lists the various Hollywood app compatibilities with AROS 64-bit; if you like, we can test your Hollywood GU! https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=1763&rowstart=0&highlight=emuv0&pid=10678#post_10678

First and foremost, developers creating their own software within the Hollywood application should start putting more pressure on Hollywood’s developer to finally release a 64-bit version...

What is the status regarding AROS64 BTw? do I assume right Hollywood only supports AROS32? (I have a Hollywood GUI - done by a Betatester, I never used Hollywood - for Dungeonkeeper here).

The x86 stable system build ISO installed quickly but it will need some customization. So I'm installing AROS One x86 in the meantime. It's more complete. :-)

AMIGASYSTEM That is good to know about updating the stable builds. The one I'm using for x86 is the U3 version of ABIv0. Also, it's good to have test systems setup in virtual machines for quickly testing new software. But I have a couple Native Installations of AROS One x86. I'm very pleased with them.

With the new version of the Hollywood language released a while ago, there have also been changes to the binary files, where, in my opinion, something doesn’t quite add up. In practice, the new development version of Hollywood significantly streamlines the binaries by removing libraries that are now required externally. Well, or rather badly: previously, some applications ‘that didn’t include the library internally’ would look for it in the programme folder or in the system’s Libs/Hollywood folder. Now, however, all required libraries, “and there are quite a few”, must be located in the programme folder. In practice, this means the system will end up with dozens and dozens of duplicate libraries. If we then add that some older Hollywood applications refuse to use new libraries and instead require a specific older version, the confusion only increases. The Amiga philosophy dictates that all libraries, as is the case with other operating systems, must be located in a single system folder: ‘Libs’ for AROS and Amiga. This ensures there is only one copy, making updates straightforward; otherwise, they would all need to be updated as applications are updated.

But please note that Stable versions do not include the numerous updates and improvements that might cause conflicts or regressions. I recommend updating the Stable builds before using them. For example, ABIv11 updated to U3 via Grub supports native displays on VMware, VirtualBox and QEMU.

For my testing environment I was going to use AROS One but I've decided that I only need a minimal system that is easy to update. So I'm downloading the AROS AVIv0 stable build ISO to test the latest version. I'm in the process of updating my ABIv0 and ABIv11 Build Systems.

AI text ... dunno if its correct https://github.com/JJDSNT/bellatrix/blob/main/AI_context/consolidated/issue_cdrom_boot.md i will try: Option B — Inject 'CD01' into FSR via DiagArea: Our DiagArea ROM (already present for serial debug) runs at expansion init time Add code to allocate a FileSysEntry with fse_DosType = 'CD01' and a minimal fse_SegList pointing to a stub handler Add it to FileSystem.resource lide.device will find it; cdBoot = true; ScanCDROM runs find_filesystem inside ScanCDROM also needs 'CD01' present — same mechanism covers it Option B is lower overhead and stays within the current 64 KB window. if someone has a better approach lemme know. Regards,

Ok, i am using https://github.com/LIV2/lide.device But yet no success ... :/ [SERIAL] ROMInfo: 1MiB ROM detected [SERIAL] ROMInfo: ROM region(s).. [SERIAL] ROMInfo: 0x00e00000 - 0x00e7ffff [SERIAL] ROMInfo: 0x00f80000 - 0x00ffffff [SERIAL] [EXEC] InitCode: calling InitResident (110 02 "expansion.library") [SERIAL] Found board 00e80000: mfg=5194 prod=7 size=00010000 serial=00000001 diag=00000004 [SERIAL] Configuring board: cd=00002688 mfg=5194 prod=7 size=00010000 type=d1 [Z2] board 'lide.cdrom' assigned base=00e90000 size=00010000 [Z2] all boards configured [SERIAL] -> configured, 00e90000 - 00e9ffff [SERIAL] [EXEC] InitCode: calling InitResident (105 82 "debug.library") [SERIAL] [EXEC] InitCode: leave InitCode(0x02, 0) [SERIAL] [EXEC] InitCode: enter InitCode(0x01, 0) [SERIAL] [EXEC] InitCode: kickmemptr=0x00000000 kicktagptr=0x00000000 kickchecksum=0x00000000 [SERIAL] [EXEC] InitCode: calling InitResident (120 01 "exec.library") [SERIAL] [EXEC] InitCode: calling InitResident (105 01 "diag init") [SERIAL] callroms [SERIAL] Read boot ROM base=00e90000 cd=00002688 type=d1 [SERIAL] da_Config=10 [SERIAL] Size=03e8 DiagPoint=000e BootPoint=0050 Name=01c8 [SERIAL] Name='Chainloader' [SERIAL] Call boot rom @0001bf46 board 00e90000 diag 0001bf38 configdev 00002688 [SERIAL] ->success [SERIAL] callroms done [SERIAL] 00000400: 00000400 - 00100000 00001703 -10 'chip memory' [SERIAL] 00001550: 00f80000 - 01000000 00000400 -128 'Kickstart ROM' [SERIAL] 00001570: 00e00000 - 00e80000 00000400 -128 'Kickstart ROM' [SERIAL] [EXEC] InitCode: calling InitResident (103 81 "utility.library") [SERIAL] [EXEC] InitCode: calling InitResident (101 81 "aros.library") [SERIAL] [EXEC] InitCode: calling InitResident (100 01 "mmu") [SERIAL] [EXEC] InitCode: calling InitResident (100 01 "task.resource") [SERIAL] [EXEC] InitCode: calling InitResident (100 81 "potgo.resource") [SERIAL] [EXEC] InitCode: calling InitResident (100 01 "bootloader.resource") [SERIAL] [EXEC] InitCode: calling InitResident (99 01 "processor.resource") [SERIAL] [EXEC] InitCode: calling InitResident (94 81 "oop.library") [SERIAL] [EXEC] InitCode: calling InitResident (92 81 "hiddclass.hidd") [SERIAL] [EXEC] InitCode: calling InitResident (91 81 "system.hidd") [SERIAL] [EXEC] InitCode: calling InitResident (90 81 "bus.hidd") [SERIAL] [EXEC] InitCode: calling InitResident (89 81 "storage.hidd") [SERIAL] [EXEC] InitCode: calling InitResident (80 01 "cia.resource") [SERIAL] [EXEC] InitCode: calling InitResident (80 01 "FileSystem.resource") [SERIAL] [EXEC] InitCode: calling InitResident (70 81 "battclock.resource") [SERIAL] [EXEC] InitCode: calling InitResident (66 81 "gfx.hidd") [SERIAL] [EXEC] InitCode: calling InitResident (65 81 "graphics.library") [SERIAL] [EXEC] InitCode: calling InitResident (64 81 "layers.library") [SERIAL] [EXEC] InitCode: calling InitResident (50 81 "timer.device") [SERIAL] [EXEC] InitCode: calling InitResident (48 81 "card.resource") [SERIAL] [EXEC] InitCode: calling InitResident (45 81 "keyboard.hidd") [SERIAL] [EXEC] InitCode: calling InitResident (45 81 "mouse.hidd") [SERIAL] [EXEC] InitCode: calling InitResident (45 01 "misc.resource") [SERIAL] [EXEC] InitCode: calling InitResident (44 81 "keyboard.device") [SERIAL] [EXEC] InitCode: calling InitResident (44 81 "gameport.device") [SERIAL] [EXEC] InitCode: calling InitResident (40 81 "partition.library") [SERIAL] [EXEC] InitCode: calling InitResident (40 81 "amigakbd.hidd") [SERIAL] [EXEC] InitCode: calling InitResident (40 81 "amigamouse.hidd") [SERIAL] [EXEC] InitCode: calling InitResident (40 81 "keymap.library") [SERIAL] [EXEC] InitCode: calling InitResident (39 81 "disk.resource") [SERIAL] [EXEC] InitCode: calling InitResident (35 81 "trackdisk.device") [SERIAL] [EXEC] InitCode: calling InitResident (30 81 "input.device") [SERIAL] [EXEC] InitCode: calling InitResident (15 81 "intuition.library") [SERIAL] [EXEC] InitCode: calling InitResident (9 81 "amigavideo.hidd") [SERIAL] [EXEC] InitCode: calling InitResident (5 81 "cd.device") [SERIAL] [EXEC] InitCode: calling InitResident (4 81 "console.device") [SERIAL] [EXEC] InitCode: calling InitResident (4 81 "ata.device") [SERIAL] [EXEC] InitCode: calling InitResident (3 81 "ata_gayle.hidd") [SERIAL] [EXEC] InitCode: calling InitResident (0 81 "gadtools.library") [SERIAL] [EXEC] InitCode: calling InitResident (0 81 "mathieeesingbas.library") [SERIAL] [EXEC] InitCode: calling InitResident (0 81 "freeanim.library") [SERIAL] [EXEC] InitCode: calling InitResident (0 81 "lowlevel.library") [SERIAL] [EXEC] InitCode: calling InitResident (-1 01 "afs-handler") [SERIAL] [EXEC] InitCode: calling InitResident (-1 01 "cdrom-handler") [SERIAL] [EXEC] InitCode: calling InitResident (-9 01 "romboot") [SERIAL] romtaginit [SERIAL] Diag board 00e90000 InitResident 0001bf9e (V=1 P=0 F=01 'Chainloader' 'Chainloader') [ATA-IDE] cmd ec [ATA-IDE] cmd 08 [ATA-IDE] cmd a1 [ATA-IDE] read16 pos=0/512 word=c085 (lo=c0 hi=85) [ATA-IDE] read16 pos=2/512 word=0000 (lo=00 hi=00) [ATA-IDE] read16 pos=4/512 word=37c8 (lo=37 hi=c8) [ATA-IDE] read16 pos=6/512 word=0000 (lo=00 hi=00) [ATA-IDE] read16 pos=508/512 word=0000 (lo=00 hi=00) [ATA-IDE] read16 pos=510/512 word=0000 (lo=00 hi=00) [ATA-IDE] cmd a0 [ATA-IDE] pkt_write[0] value=0000 -> bytes 00 00 [ATA-IDE] pkt_write[2] value=0000 -> bytes 00 00 [ATA-IDE] pkt_write[4] value=0000 -> bytes 00 00 [ATA-IDE] pkt_write[6] value=0000 -> bytes 00 00 [ATA-IDE] pkt_write[8] value=0000 -> bytes 00 00 [ATA-IDE] pkt_write[10] value=0000 -> bytes 00 00 [ATA-IDE] ATAPI pkt: 00 00 00 00 00 00 00 00 00 00 00 00 [ATAPI] cmd 00 media=1 [ATA-IDE] atapi_exec rc=0 data_len=0 [ATA-IDE] cmd a0 [ATA-IDE] pkt_write[0] value=2500 -> bytes 25 00 [ATA-IDE] pkt_write[2] value=0000 -> bytes 00 00 [ATA-IDE] pkt_write[4] value=0000 -> bytes 00 00 [ATA-IDE] pkt_write[6] value=0000 -> bytes 00 00 [ATA-IDE] pkt_write[8] value=0000 -> bytes 00 00 [ATA-IDE] pkt_write[10] value=0000 -> bytes 00 00 [ATA-IDE] ATAPI pkt: 25 00 00 00 00 00 00 00 00 00 00 00 [ATAPI] cmd 25 media=1 [ATA-IDE] atapi_exec rc=0 data_len=8 [ATA-IDE] read16 pos=0/8 word=0200 (lo=02 hi=00) [ATA-IDE] read16 pos=2/8 word=679e (lo=67 hi=9e) [ATA-IDE] read16 pos=4/8 word=0000 (lo=00 hi=00) [ATA-IDE] read16 pos=6/8 word=0008 (lo=00 hi=08) [ATA-IDE] cmd ec [ATA-IDE] cmd 08 [ATA-IDE] cmd a1 [ATA-IDE] read16 pos=0/512 word=c085 (lo=c0 hi=85) [ATA-IDE] read16 pos=2/512 word=0000 (lo=00 hi=00) [ATA-IDE] read16 pos=4/512 word=37c8 (lo=37 hi=c8) [ATA-IDE] read16 pos=6/512 word=0000 (lo=00 hi=00) [ATA-IDE] read16 pos=508/512 word=0000 (lo=00 hi=00) [ATA-IDE] read16 pos=510/512 word=0000 (lo=00 hi=00) [ATA-IDE] cmd a0 [ATA-IDE] pkt_write[0] value=0000 -> bytes 00 00 [ATA-IDE] pkt_write[2] value=0000 -> bytes 00 00 [ATA-IDE] pkt_write[4] value=0000 -> bytes 00 00 [ATA-IDE] pkt_write[6] value=0000 -> bytes 00 00 [ATA-IDE] pkt_write[8] value=0000 -> bytes 00 00 [ATA-IDE] pkt_write[10] value=0000 -> bytes 00 00 [ATA-IDE] ATAPI pkt: 00 00 00 00 00 00 00 00 00 00 00 00 [ATAPI] cmd 00 media=1 [ATA-IDE] atapi_exec rc=0 data_len=0 [ATA-IDE] cmd a0 [ATA-IDE] pkt_write[0] value=2500 -> bytes 25 00 [ATA-IDE] pkt_write[2] value=0000 -> bytes 00 00 [ATA-IDE] pkt_write[4] value=0000 -> bytes 00 00 [ATA-IDE] pkt_write[6] value=0000 -> bytes 00 00 [ATA-IDE] pkt_write[8] value=0000 -> bytes 00 00 [ATA-IDE] pkt_write[10] value=0000 -> bytes 00 00 [ATA-IDE] ATAPI pkt: 25 00 00 00 00 00 00 00 00 00 00 00 [ATAPI] cmd 25 media=1 [ATA-IDE] atapi_exec rc=0 data_len=8 [ATA-IDE] read16 pos=0/8 word=0200 (lo=02 hi=00) [ATA-IDE] read16 pos=2/8 word=679e (lo=67 hi=9e) [ATA-IDE] read16 pos=4/8 word=0000 (lo=00 hi=00) [ATA-IDE] read16 pos=6/8 word=0008 (lo=00 hi=08) [SERIAL] romtaginit done [SERIAL] [EXEC] InitCode: calling InitResident (-10 81 "p96gfx.hidd") [SERIAL] [EXEC] InitCode: calling InitResident (-45 01 "alert.hook [SERIAL] ") [SERIAL] [EXEC] InitCode: calling InitResident (-49 01 "ATA boot wait") [SERIAL] [EXEC] InitCode: calling InitResident (-50 01 "dosboot.resource") [ATA-IDE] cmd a0 [ATA-IDE] pkt_write[0] value=0000 -> bytes 00 00 [ATA-IDE] pkt_write[2] value=0000 -> bytes 00 00 [ATA-IDE] pkt_write[4] value=0000 -> bytes 00 00 [ATA-IDE] pkt_write[6] value=0000 -> bytes 00 00 [ATA-IDE] pkt_write[8] value=0000 -> bytes 00 00 [ATA-IDE] pkt_write[10] value=0000 -> bytes 00 00 [ATA-IDE] ATAPI pkt: 00 00 00 00 00 00 00 00 00 00 00 00 [ATAPI] cmd 00 media=1 [ATA-IDE] atapi_exec rc=0 data_len=0 [ATA-IDE] cmd a0 [ATA-IDE] pkt_write[0] value=0000 -> bytes 00 00 [ATA-IDE] pkt_write[2] value=0000 -> bytes 00 00 [ATA-IDE] pkt_write[4] value=0000 -> bytes 00 00 [ATA-IDE] pkt_write[6] value=0000 -> bytes 00 00 [ATA-IDE] pkt_write[8] value=0000 -> bytes 00 00 [ATA-IDE] pkt_write[10] value=0000 -> bytes 00 00 [ATA-IDE] ATAPI pkt: 00 00 00 00 00 00 00 00 00 00 00 00 [ATAPI] cmd 00 media=1 [ATA-IDE] atapi_exec rc=0 data_len=0 [ATA-IDE] cmd a0 [ATA-IDE] pkt_write[0] value=0000 -> bytes 00 00 [ATA-IDE] pkt_write[2] value=0000 -> bytes 00 00 [ATA-IDE] pkt_write[4] value=0000 -> bytes 00 00 [ATA-IDE] pkt_write[6] value=0000 -> bytes 00 00 [ATA-IDE] pkt_write[8] value=0000 -> bytes 00 00 [ATA-IDE] pkt_write[10] value=0000 -> bytes 00 00 [ATA-IDE] ATAPI pkt: 00 00 00 00 00 00 00 00 00 00 00 00 [ATAPI] cmd 00 media=1 [ATA-IDE] atapi_exec rc=0 data_len=0