On the Qemu side, you need to use the ‘-vga vmware’ option, while in the operating system you need to update ‘vmwaresvga.hidd’, path: SYS\Devs\Drivers.

@walkero

Starting with the next release of AROS One 64Bit, the VMware “Native Video Driver” will also be available for QEmu. See screenshot link.

https://www.arosworld.org/infusions/fo ... ments/qemu-screenmode.jpg



You can test VMware video drivers for Qemu in the Test-Demo Build available at this link:

https://www.arosworld.org/infusions/fo ... =180&pid=10167#post_10167

Even the most modern browsers still do this. Firefox allows you to delete all temporary files on exit via an option, while Chrome requires you to do it manually!

@hotrod
In response to your statement, ‘deadwood’, the developer of OWB 3.0 for AROS 64Bit, replied:

"Finally it is quite possible that Wayfarer has a smarter way to manage caches when memory consumpion reaches hardware limit. There is nothing stopping this from being implemented in Odyssey, because Odyssey 3.0 is using the public part of Waywarer 3.0 codebase already."

@hotrod

Quote:

Perhaps my English translated online is not understandable!

I didn't say that you need 6GB to use OWB, I said that if you have more than 4GB you have more speed, you can open more tabs and have a better experience.

Even on Windows with 2GB, Firefox works well, but if you have 8GB, it's even better, don't you think?

Furthermore, on a 64-bit system, it is not recommended to use 2GB, at least on AROS, because any software bugs are not detected.

Finally, MOS and OS4, being 32-bit systems (at least I think so), have a limit of 3.5GB; beyond this size, they cannot use it.

@joerg

AROS 68k is not compatible with OS 3.9, AROS 68k is based on OS 3.1.

OWB 3.0 is a modern, fast browser compatible with many websites, but for optimal performance it is best to have 4GB of RAM or more.

OWB 3.0 can be used on AROS x86 32-bit, but due to the RAM restrictions of 32-bit, it cannot be as fast as it is on AROS 64-bit, where you can take advantage of all the RAM of the PC hardware.

@LiveForIt

FireFox works very well on my Windows 7 64-bit system and is fast even on my old DualCore 4GB RAM.

Of course, it depends on how you use it. With a little care, deleting all temporary files lightens the load. It is also important to have a powerful video card.

NetSurf not only has slow updates, the latest version being 2023, but it also does not work on my Windows 7 64-bit. The previous version did not support many sites and no multimedia. NetSurf is not a suitable browser for a growing OS.

OWB 3.0 is the best, offering browsing similar to Firefox. The problem is having adequate RAM and CPU. As mentioned, it works very well on AROS 64-bit, and YouTube videos are very smooth.

@LiveForIt

Quote:

This version of OWB 3.0 is based on the AROS 64-bit version of Deadwood. In fact, to get the most out of OWB 3.0, you would need to have much more RAM.

On AROS 64-bit, we use a minimum of 4/6 GB of RAM to watch YouTube videos as fast as on a Windows PC. AROS 64Bit has no RAM limits.

https://youtu.be/0OeMbB2rGXc

Kyvos, for the problems mentioned, the mystery has been solved as to why CDs, DVDs and HD images are not detected from other paths.

Basically, on Windows, if an ISO or HD image is located in ‘Program Files’ or another directory with a split name (with a space), Kyvos cannot find the file.

I tried adding the path in quotation marks, but it doesn't work!

Hello walkero, I would like to share some suggestions that I believe are important.

-The ability to use different paths for CDs and hard disks, which would allow the same hard disks and CDs/DVDs to be used for multiple applications that use them.

-ISO name and CD-DVD name, this is also important. For example, the name of the default AROS DVD does not exist, and AROS distributions have different names. It would be useful to be able to choose the path and name of the ISO as desired.

A less experienced user would certainly have problems installing an AROS distribution. Furthermore, AROS 64-bit should have 6GB of RAM by default, but inexperienced users will ignore this very important setting for 64-bit (errors/Guru not shown in case of poorly compiled software).

Another request, if possible, is to be able to install the OS on or use a RAW format hard disk. To use my AROS/OS4.1 hard files Created with my Qemu GUI, I had to modify the config.json.

@NinjaCyborg

The archives ‘afa_os_zune_1.0’ and ‘afa_os_zune1.0beta4’ contain amiblitzsource files for ‘zune_promoter’.

The archives up to version ‘AfA_OS_3.94.1’ contain ‘arossource’ source files, but later versions do not contain any source files.

Quote:

I have saved a number of files downloaded from that site. See the list, but I don't have the file you are looking for, ‘HOWTO_Compile_AfA.pdf’.

These are the files I have saved:

afa_os_zune_1.0.lha
afa_os_zune1.0beta4.lha
AfA_OS_3.92.1.lha
AfA_OS_3.92.lha
AfA_OS_3.93.1.lha
AfA_OS_3.93.2.lha
AfA_OS_3.93.lha
AfA_OS_3.93_beta1.lha
AfA_OS_3.94.1.lha
AfA_OS_3.94.lha
AfA_OS_V4.4.lha
AfA_OS_V4.5.lha
AfA_OS_V4.6.lha
AfA_OS_V4_7.lha

You can access that link via web.archive, If it doesn't work, press ‘Enter’ on the browser address bar.

ttps://web.archive.org/web/2012020605 ... ga-world.de/afaupload.php

@NinjaCyborg

AROS 68k binaries are of the ‘ELF’ type and therefore incompatible with Amiga OS.

On the contrary, OS 3.1 binaries are compatible with AROS 68k.

AROS 68k is based on Amiga OS3.1 and therefore does not support Amiga OS 3.2/3.9.

Regarding Zune, there is a native Amiga OS 3.9 version of ZUNE, which you can find installed on the AfA OS extension.

I am attaching an old screenshot of mine where you can see the difference in the ModExplorer GUI on OS3.9 AfA OS, first running with MUI and then with ZUNE.

https://www.amiganews.it/forum/downloa ... 3489a4bdb27&mode=view.jpg


AROS 68k is a system that requires a powerful machine.
If you run AROS 68k on a real Amiga, it will be too slow to use.

@walkero

If you're interested, yesterday I released the new version of AROS One 64Bit. If you wish, you can add it to Kyvos.

Here you will find information and download links for AROS One 1.2 64Bit.

https://www.arosworld.org/infusions/fo ... d=1418&pid=9724#post_9724

Okay, never mind, in any case, I solved it by deleting that string, now all operating systems are working fine! Windows shares on the network are also working fine, as is mounting a USB stick as a ‘Windows volume’.

How can I monitor the error? I use Qemu 6.2.0, the latest version supported by Win7 64Bit, but in any case, all operating systems work fine with my scripts.

Today I tried reinstalling AROS One 64Bit, and even Aros 64 Bit no longer starts up. It may be that the new version of kyvos-1.3.1 is causing these problems.

As mentioned, the creation of the VM works fine without errors.
I should download the previous versions to check.


EDIT:

AROS One 64 and OS 4.1 problem solved!

To make it work, I removed the string ‘-display sdl,gl=off,show-cursor=off,full-screen=off’.

Could this be an incompatibility issue only for my old PC?

@walkero

The Sam 460ex configuration on Windows 7 does not seem to work. The VM creation proceeds and is saved without errors, but when I run it, I get an error in the configuration!

My personal script works fine with the same ISO.

OK, thank you. If you need to monitor Guru, on AROS One, in the System/Debug folder, there are ‘Sashimi’ and ‘Snoopy’.

Snoopy (System:System/Snoopy) patches some library functions in such a way that their arguments and result are print to the debugging console.

Sashimi (System:Developer/Debug/sashimi) shows all debugging output in a Wanderer window. This is useful when you want to see debug output of AROS when it's build without debug support or you can't read the serial output.

Hello walkero, have you run any tests with kyvos to check the AuraFly Guru on AROS x86 32Bit? Thank you.