Neil: The problem with spaces in names are also present with ABI v.0 This is using yesterdays night build. I can not get into a directory where there are space in directory name.

edwberger: Thx for the clearification. I think this is all good. We will have a even better 68k version of AROS and being able to port 68k stuff more easy to AROS i386 or other cpus is a good thing.

When ABI v.1 is in good shape, it could be time for a next gen.. AROS version with mem.. protection etc. This version of AROS should not focus on being compatible with old stuff since ABI v.1 would be the AROS version for that. For a start maybe the next gen.. AROS version should be able to emulate ABI v.1 stuff feeling almost like native. Sure it should be no reason why this next gen.. AROS version could not happen quite soon. I guess the only problem with it is how attractive it would be for AROS developers to do it. I'm at least quite sure it would gain quite some interest from outside AROS would. The big problem is to get it started.

@OlafS3

There's no schedule for when the ABI_V1 transition will take place. It will be ready when its ready. There's no pretenses that it will offer any features you mentioned. 32-bit AROS (i386, ppc, m68k) will remain 32bit, and incompatible with 64bit unless someone does additional work. Memory protection progress took a backseat to the developers day job. Noone has said they're actively working on multi-core changes for exec. That work is all outside the scope of ABI_V1.

The primary goals of ABI_V1 were to fix up various binary compatibility issues in the system which affected source code compatibility with AmigaOS 3.x. It moved to DOS packet devices to be similar again to Amiga OS. Various system library work is under way as Staf has time. When he thinks its ready to freeze, then it will be ready.

Neil: ok, thx for testing it. This was using night build from yesterday. I installed to usb storage device. One other strange thing I noticed was that in my device list I had DU0 (normal) but also (can not rem.. 100% how it was) but something like DU0.1
Same goes for DU1, DU1.1

Olaf: Good questions. I have a feeling not even the developers are 100% of the path of ABI v.1
It would be nice to see some kind of plan.

sorry for be offtopic

I have a general question. When will be the change to ABI v.1? And what features are planned? It would be great to become 64bit and have multicore-support. And Memory protection (at least partly) would be great too.

I only had time so far to test the problem with spaces in a directory name, but I can't reproduce it. What exact nightly date are you using?

I have some problems with ABI v.1 that I like to report.

First wi-fi is working, but it is little strange how it behaves.

If I like to get online I have to set everything up in network.prefs then save.
After I done that I'm online and everything seams good.

If I try to tick the "start networking during system boot" I'm getting into trouble. After reboot I get an error requester. I have not written down what it says, but can for sure do that if of any interest.

What is also strange is that even if I have not ticked to start networking during system boot and try to start the network from shell with "startnet" nothing happens.

Now to next problem.

If I create a directory with space I can not get into it using shell. Lets say I made a dir called "aros rocks" in DU0:

If I try to go into that dir with aro(pressing TAB) I will see "aros rocks

Sure pressing enter after "aros rocks will bring me nowhere.

Writing "aros rocks" without using TAB will net get me anywhere either.

Last is that in DOpus First letter of drives seams to be cut of.

DOpus tell me all the time to insert "ROS" in any drive.