Tested with Build 20230430-D02

ACER ASpire 5920 VESA + 'noacpi' does not work, black screen

Samsung R730 VESA + 'noacpi' Guru shown above !

I will now try a test with the new Build '20241209-D04'

Test Hardware Build 20241209

- Netbook ACER Aspire One ZG5 Intel GMA Mobile 945SE
Native = Works Fine
VESA = Works Fine

- Netbook Dell Inspiron Mini 910 Mobile IntelGMA 945GSE
Native = Works Fine
VESA = Works Fine

- Laptop ACER ASpire 5920 NVIDIA GeForce 8600M GS
Native = Black screen, white flashing dot
VESA = Black screen
VESA + noacpi = Black screen
Safe Mode = Error Mount (see screenshot)
Safe Mode + noacpi = Works Fine

- Laptop Samsung R730 Intel HD Graphics
Native = GURU
VESA = GURU
Safe Mode = Guru

New build:

https://axrt.org/development/AROS-20241213-D08-pc-i386-boot-iso.zip

Functionality-wise it's the same as D04, however source code patches have been cleaned up and re-integrated which might have caused some additional regression. At this point most of the source code re-integration has been done and following builds should have only very specific changes.

This problem was also present on Build '20221221-D01', so the new AROS One 2.7 ready for distribution will not run on ACER Aspire One ZG5 Netbooks

Have you released AROS One 2.7 based on a test build? But why?

No it is the latest stable version released ABIv0 20220318-1-U2!

Excluding the ACER Aspire One ZG5 Netbooks problem, the system is very stable!

That's good Sorry, I misunderstood

deadwood, I have encountered a conflict between 20241213-D08 and AROS One

Basically if I integrate 20241213-D08 on AROS One I get an error in the Grub, if I restore just the "Grub" folder of AROS One the Grub works.

This never happened with the other Core integrations!

What should I delete from the old Core to make it compatible?

What kind of error are you getting?

I re-did the integration and this time everything went well, I don't think this could have happened, now AROS One with '20241213-D08' integrated works very well.

I also created volume icons for InstallAROS and improved the visibility of gadgets, see screenshot!

Glad to hear that. Keep in mind that there is a number of bugs in InstallAROS that make installation problematic. I should release fixed version soon.

Thanks, I'm just testing at the moment!

Hi All,

Since the release in Q1 next year will be a joint release of 32-bit and 64-bit versions, from now I will be providing updates to both of them. Below you will find links to ISO. The naming template has been changed slightly. Instead of D09, we now how 32D09, which defined a version of 32-bit AROS and 64D09 which defines a version of 64-bit AROS. When reporting errors, please make sure you use the full version to avoid confusion whethere you are talking about 32-bit or 64-bit version.

For 32D09:
- The only change compared to D08 is InstallAROS which fixes several installation issues.
ISO: https://axrt.org/development/AROS-20241216-32D09-pc-i386-boot-iso.zip

For 64D09:
- if you are looking for 64-bit contrib, it can be downloaded from: https://axrt.org/downloads-aros-64bit
ISO: https://axrt.org/development/AROS-20241216-64D09-pc-x86_64-boot-iso.zip

Happy testing!

deadwood I encountered a small problem on 'D08' and 'D9', it is no longer possible to Dismount a share on Windows, in practice the 'SMB2' share remains in use!

Dismount or Restart is necessary on shares on Windows PCs, because by default if they are not in use they are automatically deactivated after about 15 minutes.

Basically, to reactivate the share now you have to restart the system or create a new DosDrivers with a different Unit.

How do you dismount a share?

To unmount a Share on AROS One I use 2 commands, both of which must be executed otherwise it will not unmount completely:

Assign Dismount SMB2:
UnMount SMB2:

UnMount does not exist on AROS but I have compiled it, if you want I can attach it to you

See attached video to see how to Mount, Dismont and Restart SMB2

Ok, thanks for the video. Please share the sources for UnMount command.

Also, why are they disconnected after 15 minutes? Did you conctact the author of SMB2? Shouldn't the filesystem itself detect disconnection and reconnect back without user action?

It does not depend on SMB2 but on Windows systems:

Windows has a idle timeout for network drive connections; by default it's 15 minutes. So after 15 minutes of not using the share it will disconnect

https://learn.mic...share-lost

Regarding an UnMount, the source was originally Amiga (Aminet), and Mazze corrected it:

https://ae.aroswo...2#msg16052

At first it seemed not to work, then I discovered that with the 2 commands the dismount works.

deadwood, D09 includes all files included in previous Builds D01, D02, D04, so there is no need to integrate all Builds on the distribution each time !

I ask this to avoid copying all the files with each new test!

You should at minimum integrate D08 fully - everything before D08 is considered by me "broken". From D08, next builds should only contain changes to specific components (like 32D09 only contains change to InstallAROS).