Test performed on VMware with Build 20251110-021008 (I will subsequently perform the test on a native PC)

- Boot -> Works well
- Mouse -> PS2 and USB work well
- Restart Computer -> OK, restarts from Grub
- Restart AROSr -> OK, restarts from Grub
- ahci/nvme disk -> Used IDE on VMware and works fine
- VMware video driver -> Works fine as before

- NTFS-Handler -> Does not work as well as in the previous build

I don't know if it's just my impression, but I noticed better device management with InstallAROS when multiple peripherals are connected.

With Build 20251110-021008 Pendrive Live, I ran a test on my Samsung PC R730 laptop with Win10 installed:

- Boot SSD SATA AHCI Enable -> Works well (‘add noacpi’)
- Boot SSD SATA AHCI Disable -> Works well (‘add noacpi’)
- Mouse -> USB works well
- Restart Computer -> OK, restarts from Grub
- Restart AROS -> Restarts with black screen

* With this Build on my Samsung PC R730, the TouchPad now works (it never worked before)

Thanks for the tests. It looks like "Restart AROS" in both VMWARE and native hardware test is not doing what it supposed to. How is "Restart AROS" behaving on those machines with previous build?

Nothing has changed compared to previous builds. For ‘Restart AROS’

However, the behaviour of ‘Restart AROS’ on VMware is different from that on a native PC.

On VMware, ‘Restart AROS’ restarts from Grub, while on native it stops at a black screen.

I think I will test the new builds next month because I want to get a laptop with nvme

Firstly, many apologies for dropping out from testing over the last few weeks - between home-life and work-life I've been kept very busy.

I've just installed the latest nightly as linked to on page 9 to my i5 laptop. Looks to be working well (posting from it now). One little bump in the road was I tired to copy across the prefeneces I'd set from the previous install but then there was some odd behaviour - the machine froze when trying to drag-and-drop a file in Wanderer and wirelessmanager locked the machine part way through connecting to the wifi. Anyway, with env-archive reset to that in the release these problemas have gone.

I shall continue testing the release and then finally try the emulation layer.

Cheers,
Nigel.

Glad to see you back @ntromans. Looking forward to you testing of EmuV0.

I tried RNOSuite; there's the problem of the text not being aligned on the GUI, but everything else works.

Just to say Wanderer prefs are still an issue (at least on native) unless Wanderer's global.prefs included in the nightly is deleted. I changed Wanderer prefs without deleting global.prefs and then found the machine locked up when copying an icon e.g. to ram:. Once global.prefs was been deleted there seems to be no ongoing issue with changing Wanderer prefs.

Cheers,
Nigel.

@ntromans

A few questions:
1) is it happening from LiveCD or from installation (LiveUSB or disk)
2) what changes are you making in Prefs/Wanderer
3) does the lock up happen when copying to RAM: or to any disk at all

There is a new Nightly build which I would like to ask you to re-test.

[url]https://build.axrt.org/download/builds/AROS-ABIv11/pc-x86_64-20251125-014634.tar.gz[/url]

Please read this post [url]https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=1707#post_9254[/url] before proceeding.

History:
- improvements to vmwaresvga.hidd

Areas to test:
- it should now be possible to use vmware driver with QEMU (via option '-vga vmware'
- wmwave driver on VMWare and VirtualBox should work the same way as in previous build

Regarding the issue reported by ntromans, I tested Build 20251110-021008 on a native PC both from a Live USB stick and from an installed hard disk. After saving with Wanderer, I found no problems copying files to RAM.

Now I'm going to try the new Build 20251125-014634 on WmWare!

I quickly tested the new Build 20251125-014634, and on Qemu I also tried the new “wmwave driver” on AROs One, and it worked perfectly, see screenshot.

I will continue to test this new Build more thoroughly! Are there any other new features to test in this new Build?

Thanks for testing and no - the only notable change in this build compared to the previous is vmwaresvga.hidd.

It's almost time to test NVMe; next month I'm getting the computer.

[quote name=deadwood post=10155]@deadwood - @ntromans

A few questions:
1) is it happening from LiveCD or from installation (LiveUSB or disk)
2) what changes are you making in Prefs/Wanderer
3) does the lock up happen when copying to RAM: or to any disk at all[/quote]

1) Installed to hard drive.

2) Didn't actually need to make any changes - just opening an then saving Wanderer prefs caused the problem.

3) Happened between any partitions.

As mentioned, this was just with the prefs as set in the iso; once deleted and started again from scratch everthing seems to be fine.

Cheers,
Nigel

I tested four machines with the latest build and they all booted. I didn't do much further testing.

[quote name=ntromans post=10175]@ntromans

1) Installed to hard drive.

2) Didn't actually need to make any changes - just opening an then saving Wanderer prefs caused the problem.

3) Happened between any partitions.

As mentioned, this was just with the prefs as set in the iso; once deleted and started again from scratch everthing seems to be fine.
[/quote]

I can't replicate this issue. What I did:

Took 20251125 NB ISO and 2GB disk image into VBox. Booted default grub option. Went through default instalation process (Proceed (...) -> reboot -> Proceed ( ) -> Install -> Remove cd from driver -> Reboot).

Then I opened Prefs/Wanderer, clicked Save. Then I tried copying Demos drawer from SYS: to RAM: by drag & drop. Copying worked, no freeze.

EDIT: Can you try repeating this freeze in some VM? Maybe it's somehow related to specific hardware.

No VM I'm afraid. If I get some time I'll try some further test runs, but as you mentioned maye it's just something particular to my i5. Anyway, with a clean start everything seems OK now.

Cheers,
Nigel.

ntromans, I tested two native PCs, VMware and QEmu, and did not encounter your problem. It may be your hardware or some corruption global.prefs file. Have you tried replacing global.prefs installed on the hard disk with the one from the ISO or another ISO?