I'll see if I can get v53.8 smb-handler working correctly. Reconnecting is a safer approach as it doesn't "restart" the filesystem. Dismounting will not work if you have any files opened and using any software "on" that share can leave unclosed files.

Hi
I want to try the latest Aros 64bit image (aros-20250206-64D11-pc-x86_64.iso) with VirtualBox (i have VB version 7.0.14 r161095) but don't works, it's booting fine but on Grub if i select any config (apart from Safe mode) i have only a black screen and nothing seems to go ahead.

If i select "Safe mode" i have :
Your processor is not x86-64 compatible
CPUID: EAX 0x00500f20, EDX 0x0bc3fb3f
failed to run the kickstart
******* SYSTEM PANIC!!! *****
There are some other option to try that i don't know? or maybe it's not yet working with VBox.

My PC have:
AMD E-350D APU with Radeon(tm) HD Graphics × 2
Linux Mint 19.3 Tricia 64-bit
Kernel Linux 5.4.0-150-generic x86_64

Thanks

I think the problem is configuration of VirtualBox. You create your VM based on template Other/Unknown(64-bit). Right now AROS things your CPU is 32-bit only.

My settings:
typether
version: other/unknown(64bit)

Motherboard:
base memory: 1792MB
chipsetIIX3
TPM:no
Mouse PS/2
disabled I/O APIC
disabled UTC
disabled EFI
CPU page:
nr CPU:1
Execution Cap:100%
disabled PAE/NX
enabled VT-x/AMD-V nested
accelleration page:
interface:default
Hardware virtualization: enabled

Video mem: 64MB
Video card:VBoxVGA
no extended functionality(3D)

Yes Reconnecting is undoubtedly more correct and I'm glad it was done, but with all previous AROS x86/68k builds Dismounting worked very well, even if an application was open and in use, Dismounting worked perfectly, applications stayed open and you could reuse them after Remounting.

Thanks for the fix smb-handler v53.8, SMB2 is very useful especially if you use WMware, it avoids using external peripherals every time you need to copy something

Uhmm sorry you are right...i have started again and now it works..thanks

@Farox

I'm glad it worked. BTW change the video card to VMSVGA (but don't enable 3D acceleration) and you will be able to use native video driver and change resolution.

20250313-32D10-P01:

Changes:
- formatting SFS disk should no longer leave "ghost" icon on the desktop
- pluging in and out an SFS formatted pendrive should no longer leave "ghost" icon on the desktop

https://axrt.org/development/20250313-32D10-P01.zip

Topics I want to look at before release:
- working smb2-handler v53.8
- warm reboot working in VBox and WMware with native driver
- https://github.com/deadwood2/AROS/issues/123
- an update package to update installations based on 20220318-1 release

@AMIGASYSTEM

Can you make me a screenshot of crash you are getting with smb2-handler v53.8 (with More.. button clicked to see the whole call stack).

In fact no error message or Guru appears, practically everything remains frozen, menu and Wanderer Icons locked and you can't click them.

I attach a screenshot of Sashimi where it shows that the latest upload is filesysbox.library!

I also tested the new version of filesysbox.library v54.5, but nothing changes !

https://github.co.../tag/V54.5

Ok, got it. Could you also attach the smb2 file you are clicking on that screenshot?

I enclose the SMB2 DOSDrivers !

Startup = "smb://Win7-PC/Share VOLUME=Shared NOPASSWORDREQ".

Win7-PC= Computer Name
Share= Shared Name
Shared= Volume Name shown on Wanderer

Disabled the Windows-side Password prompt, created a Network Drive named Share and gave all necessary permissions.

In the archive, in addition to DOSDivers "SMB2" I have also attached the file "SMB2-Start" to be copied into WBStatup for automatic mounting.

The DOSDRiver "Smb2" with its icon should be copied into Storage/DOSDrivers which will facilitate manual mounting from the icon. but also a more secure automatic mounting that works.

https://axrt.org/development/tmp/smb2-handler.i386.zip

Please try this version. I located the problem which hang the system, but I can't test it beyond connection attempt as I have no Window machine.

Your smb2-handler now works perfectly, I suppose it can also work with a Linux share!

Can you kindly compile smb2-handler also for v11 64Bit so that I can test it, thank you

Ok, thanks for confirmation. I will compile it for 64-bit once I switch back to working on 64-bit AROS release.

After these updates AROS 32Bit seems to have improved considerably, the "Relabel" problem with a Volume of Name "DH0" still doesn't work, with other types of Name it is possible to rename without problems !

The problem exists from both DOS and Wanderer, I can only rename if I mount the hard disk on another system as a data disk.

I will look into this problem when working on 64-bit release.

Hello,

Below you can find release candidates for next 32-bit ABIv0 release:

https://axrt.org/development/tmp/AROS-20250313-RC1-linux-i386-system.tar.bz2
https://axrt.org/development/tmp/AROS-20250313-RC1-pc-i386-boot-iso.zip

Unless major issues are found, these builds will become final releases next week.

Here is also an update from 32D10 to RC1:

https://axrt.org/development/tmp/20250313-32D10-P02.zip

New in P02:
- fix #123
- reset handler added to vmwaresvga.hidd

Still TODO:
- prepare update package from 20220318-1 to 20250313-1

I have to change computers for aros x86_64 even though I have an old laptop where it works for me

And here is last part of release, an update package that will change 20220318-1 into 20250313-1

https://axrt.org/development/tmp/AROS-20220318-1-U3-any-i386-update.zip

If you run into issues applying this update, let me know.

If no major issues are found, the release will be made offical by end of this week.