@smarkusg

thanks for the hint. For the moment I downloaded the d version as the c is not available and then I have to recover it from my real Sam but atm I'm not at home.
Providing I get the right files, how did you managed to have then working under the emulation?

thanks

@walkero,

Windows defender does not allow me to download kyvos 1.7 claiming there is a virus.
Could be due to the ending of support for W10 I'm still using?

Trojan:Script/Wacatac.B!ml

Great news thanks

@walkero

One suggest.

Concerning Sam460 OS4 (probably Mos too) emulation, setting the USB media, the whole command is translated as "-drive if=none,id=ufat,format=raw,file=fat:rw:myshreddir -device usb-storage,drive=ufat". As known and as stated in the Balton Qemu support webpage, this does not work hanging the boot. To avoid this, only the first half of the command should be reported in the qemu string while the second half should be activated via console. Sure to teaching anything new, it is just to clarify the context.
I think this exception should be handled by kyvos by including the first half of the command (if Usb media is set) and adding a messagebox before running qemu to remember to activate the console and then imputing the second half of the command to activate the usb sharing. Even better I do not know if there is a way to run a sort of batch under OS4 or Qemu consol to do that semiautomatically.

At the moment to do this I copied the qemu string generated by kyvos to a batch and modifying it according above description. This is quite boring not having the possibility to run the emulation directly from kyvos unless I remove the Usb media.

Thank for your great work.

@walkero

Yes I used the advanced method having the img disks already created and configured.
I suggest to add a statement in the manual to avoid using a single directory as I did, or you could rename the config file to VMname&_config.json so it remain unique.

@Walkero,

probably I have found the root cause of the issue.
There is a file config.json. Because all my disk images and in general amiga emulation stuffs are in the same directory, this config file seems to be the cause being always there for any VM path. Because the os4 VM has a different set up for the VM path and this file is there is not affected.
That means that I have to create a different directory for any OS/VM?

UPDATE
Ok that was the issue. I split the data on 4 different directories, reinstalled kyvos from scratch, recreated the VM and now everything works fine.

@Walkero,

I just created a new VM for Aros64 and it runs fine, but in the meantime I got corrupted the MOS installation having the network set to pcnet user and aros64 that is the latest set for aros64 and also the primary disk is set the same as for aros64 and the memory that I increased for aros 64 is increased too in mos configuration.

Previous aros64 VM that was corrupted now works fine because the corruption was from/for the same type of VM

Aros32 VM got the same modifications while OS4 (that is the last in the list) remained untouched.

Forgot to mention I'm using Windows10

After some other tests I can confirm that modifying any of the above mentioned data, after saving, the data it spread on all other VM's EXCLUDING THE LAST ONE IN THE LIST

@walkero

I got a serious issue using different VM'.
Switching between the different VM for my tests the configurations remain corrupted. I mean the latest network setup remain in all subsequently opened VM invalidating the possibility to run them.
Also some other setup, such as the memory size, are suffering the same issue. I have to regenerate the the VM to be able to run them, but after few switching they get corrupted.
Not sure but it seems that the last in the list is the one not having issue, for me is OS4.

Where the data are saved?

Another issue is that I can't donwnload smb2fs53.6 I tried with netsurf,Odissey and IBrowse. I need it to have some shared disk with the host.

@walkero

thanks for your reply.
Concerning the VM path it is a not relevant need, simply I created all my emulations using a certain path, when created the OS4 one I forgot to change it so it remained kyvos. I wanted to uniform this set up with the others. I can regenerate a new VM correctly.

Another issue I got is that on my real Sam I have two hd one for os4 and the second for mos, I can see the mos hd from os4 and vice versa. Here I tried to load the mos hd img under os4 emulation using the 2nd hd or third hd but they are not mounted

@walkero

a couple of suggests (may be are already there)
1. would be useful, if possible to set, to have a button with the boot priority. I better explain, if I add a bootable CD in the media it automatically want to have the boot from it while in certain cases would be necessary to boot from the HD and have the CD just mounted.
2. the path of the VM is showed but can't be changed.

@walkero
my first use impressions/suggest.
It has been quite straightfull to generate a Sam460 emulation, very easy.
I did not have time to test other systems so far.
It would be welcome an additional tab with a textbox for the output string with the possibility to copy it on the clipboard.
I miss, or at least I have not understand how to use, an option to handle file sharing such as o common directory in the host. Coding on Hollywood this is my main need for testing my programs.

Finally why the application version is 1.3.1 and the manual is 1.5?

Ok thanks it worked, even if, I'm quite sure, before, this view content button was not present.

@Walkero
Sorry,I'm a bit dumb, but I registered to your site then I did a donation to get Kyvos, but I don't find where to download it

But Os4 has the possibilty to resize the icons trough the preferences so bigger they are Better It is

I'm using DOpus time to time. Also on Icoaros I switched to Wanderer.
The main reason is the number of buttons available for which I do not know the behavior. Then before doing irreversible actions I don't use them.

Would be great to have a tool tip bobble message. Would be too difficult to implement this?

What happened with this project? Was it released?

WOW I was dreaming a basic language for OS4 since ever.

This was a spark in the sunshine.

congratulation I will test it on my sam asap

Then we now know that for AmigaOS 4.2 issue OWB will not work any more!

Thanks a lot for the hint
As soon as I arrive home I will have a try

Very quickly solved

Taking the opportunity to ask for help

On the upcoming version of VMT I'm planning to add the possibility to add reminders to AOrganiser, but I have a couple of problems. I already asked directly help to Broadblues but, despite his advises I did not solved my problems.

First of all I never used Arex, so probably I'm missing some relevant fact.
Secondly I'm using the latest free version of AOrganiser (sorry broadblues). 1.4
For what I understood from Aorganiser manual and Arex, to add an entry I generate and run a small arex program structured as follow:

/*VMT add entry to AOrganiser*/
ADDRESS DIARY
' Add DATESTRING/31-12-18, TITLE/Promemoria aggiunto da V.M.T., NOTE/Promemoria aggiunto da V.M.T.**Fiat 500L Targa AA000AA**Scadenza Collaudo'

It obviously does not work and I'm getting an arex error that actually can't remember as I'm not at home.

For sure in this example is wrong the date format. The manual states that should be an extended format according to the nationality catalog. This is giving me a first problem as I should have on all the catalogs with the translation for the months (at least in Hollywood I do not know how to retrieve it from the system). I would ask Broadblues to consider to give the possibility to use a data in short format as per mine erroneous example. (it would be great to have it on the 1.4 version as well).

Should AOrganiser up and running when I run the arex script or not?

If someone could try to copy and execute above example and show me where it is wrong it would be really appreciated. Actually I'm stuck on this problem for releasing the updated version of my program.

thanks in advance