The user-startup, as on AmigaOS, is located in the S folder.

When starting up, AROS One installs Amistart by default, but you can change this and install BoingIconBar. To install BoingIconBar, go to the System/BoingIconBar folder and run Install-BoingIconBar from its icon.

In practice, Install-BoingIconBar and Install-AmiStart are simple scripts that replace the user-startup.

To disable BoingIconBar or AmiStart, you can also do so manually by modifying the user startup.

N.B. = on AROS One v2.8, Install-AmiStart is no longer present due to a copying error on my part.

Try AROS One and you will discover many advantages, as well as its great similarity to Amiga OS.

AROS One is inspired by my old AfA One Amiga OS 3.9 bb4 AfA OS distribution, see attached video.

https://youtu.be/lXyV1PvkNvo

[quote name=AMIGASYSTEM post=10356]@AMIGASYSTEM - [quote name=Build-0-Matic post=10352]@Build-0-Matic
Or maybe it would be just better to use ArosONE (which does support BIOS) and remove what I don't want on it (like amistart)[/quote]
As recommended by terminills, try adding noacpi to grub.cfg.

Regarding AROS One, Amistart can be replaced by BoingIconbar. Just go to SYS:System and click on Install-BoingIconbar. After clicking, AROS One will restart with BoingIconbar installed.

Before installing BoingIconbar, you must edit the ‘Iconbar.prefs’ file located in ‘Env-Archive’. Unfortunately, I forgot to delete an entry that affects SMB2, which is not present in the ISO.
If you do not edit ‘Iconbar.prefs’, you will not see BoingIconbar in the bar.

If, on the other hand, you do not want Amistrat and do not want to install BoingIconbar, edit User-Startup and delete the line concerning the start-up of Amistart.[/quote]

Funny because when I installed Aros One, for some reason I have no Amistart and no Boingbar running at startup!
Not that I miss them any as they just clutter-up that small screen.
I went looking just for fun and I couldn't find the user-startup file (or folder) anywhere

Me too
I'm now going to sorta get the Amiga I wanted back in the day.

Glad you made it working

Fantastic news Deadwood!
I have the ABIv1 version running flawlessly on my Acer Aspire One ZG5 (1.5gb ram, 160gb mechanical IDE drive).
I have no issues with the mouse. Now to download some demos and apps to load it up and test the sound.

(BTW, this thing boots FAST! I've never seen this netbook so speedy)

[quote name=deadwood post=10369]@deadwood - AROSOne has made a special USB-image that works with Rufus. That's something that the standard nightly build or release ISO's don't have.[/quote]

OK, so that explains it!

Thanks.

I'm going to soldier on with the Virtualbox solution.

AROSOne has made a special USB-image that works with Rufus. That's something that the standard nightly build or release ISO's don't have.

[quote name=deadwood post=10359]@deadwood - [quote post=10352]@Build-0-Matic - I've been playing with it (ABIv0) and discovered that they dropped BIOS boot support.
I'm now wondering what would be the best way to put it on my venerable netbook...
Or maybe it would be just better to use ArosONE (which does support BIOS) and remove what I don't want on it (like amistart) ?[/quote]

Actually ABIv0 ONLY support BIOS-enabled machines right now, not UEFI. Could you let us know what ISO exactly are you trying to boot (please provide the link) and whether you are trying to boot from CD or from USB-stick. When using USB-stick you need to follow this process to prepare the USB-stick (AROS ISOs are not writable to USB-stick like Linux ISOs are):

[url]https://arosnews.github.io/how-to-prepare-usb-flash-drive-aros/[/url]

Note: this tutorial speaks about 64-bit version of AROS but the same applies to 32-bit version.[/quote]

Here is the link to the one I have that will not boot. But I am using Rufus which is wrong I just discovered
https://sourceforge.net/projects/aros/files/snapshots/20250313/Binaries/AROS-20250313-pc-i386-boot-iso.zip/download

I find it odd that Rufus works with ArosOne but not this one.

[quote name=AMIGASYSTEM post=10357]@AMIGASYSTEM - @Build-0-Matic

Question: What did you burn onto the USB stick with Rufus, an ISO or a USB image?
[/quote]
Sorry for taking so long to reply.
I'm using the nightly ISO for ABIv1
As for the snapshot of ABIv0, it only works on UEFI. To me that is a strange decision since pretty much all 32 bit machines are BIOS only.

As for Aros One, it works just fine out of the box.

[quote name=Build-0-Matic post=10336]@Build-0-Matic - Here is where I got it
http://www.aros.org/nightly1.html

pc-i386-boot-iso

The native version for i386-based PC AT computers and compatibles. This is the bootable CD-ROM ISO image, which contains all core AROS system files.

And this is the link to the direct file
https://sourceforge.net/projects/aros/files/nightly2/20251218/Binaries/AROS-20251218-pc-i386-boot-iso.zip/download

Since it's a nightly build, the date will be different.[/quote]

I just tested todays nightly and the boot problem is fixed.

[quote post=10352]@Build-0-Matic - I've been playing with it (ABIv0) and discovered that they dropped BIOS boot support.
I'm now wondering what would be the best way to put it on my venerable netbook...
Or maybe it would be just better to use ArosONE (which does support BIOS) and remove what I don't want on it (like amistart) ?[/quote]

Actually ABIv0 ONLY support BIOS-enabled machines right now, not UEFI. Could you let us know what ISO exactly are you trying to boot (please provide the link) and whether you are trying to boot from CD or from USB-stick. When using USB-stick you need to follow this process to prepare the USB-stick (AROS ISOs are not writable to USB-stick like Linux ISOs are):

[url]https://arosnews.github.io/how-to-prepare-usb-flash-drive-aros/[/url]

Note: this tutorial speaks about 64-bit version of AROS but the same applies to 32-bit version.

@Build-0-Matic

Question: What did you burn onto the USB stick with Rufus, an ISO or a USB image?

Are you burning a Night or Arosone?

Which version of Rufus are you using?

[quote name=Build-0-Matic post=10352]@Build-0-Matic
Or maybe it would be just better to use ArosONE (which does support BIOS) and remove what I don't want on it (like amistart)[/quote]
As recommended by terminills, try adding noacpi to grub.cfg.

Regarding AROS One, Amistart can be replaced by BoingIconbar. Just go to SYS:System and click on Install-BoingIconbar. After clicking, AROS One will restart with BoingIconbar installed.

Before installing BoingIconbar, you must edit the ‘Iconbar.prefs’ file located in ‘Env-Archive’. Unfortunately, I forgot to delete an entry that affects SMB2, which is not present in the ISO.
If you do not edit ‘Iconbar.prefs’, you will not see BoingIconbar in the bar.

If, on the other hand, you do not want Amistrat and do not want to install BoingIconbar, edit User-Startup and delete the line concerning the start-up of Amistart.

that's actually a kernel panic ... I let kalamatee know about it yesterday. but you can always add sysdebug=all and you'll see the kernel output.

When I boot with it, it just gives me a black screen with a blinking cursor.
So, the noacpi command is pretty useless in that case.
On Rufus, the target system is locked on UEFI no CSM when I make the USB stick, so this is a no-go.
I could hop on my linux box and try and fix the grub install, but since Aros uses a modified version of grub, I'm not too confident that it would fix it.

You can try arosone ... but you can also try added noacpi to the grub line to see if that helps... but afaik the latest AROS does have Bios and EFI support... but iirc kalamatee fixed the build issue on ABIv1 so tonight or tomorrows build should have the fix.

I've been playing with it (ABIv0) and discovered that they dropped BIOS boot support.
I'm now wondering what would be the best way to put it on my venerable netbook...
Or maybe it would be just better to use ArosONE (which does support BIOS) and remove what I don't want on it (like amistart) ?

Unfortunately that's what happened with AROS. We can argue about if it was the right decision all day long. However the outcome is a mainline which became a playground more than the future because without testers bugs go unnoticed. When bugs go unnoticed you have stability and incompatibility issues and when that happens no one will port software to it for basically one user. But if it's to ever fully stabilize it needs testers I'm not saying everyone needs to download a copy every day and test ... but the Distro maintainers actively steering people away from it causes a lot of harm imho.

I must admit that it's the first time I hear of people backporting parts of an OS to an older version of said OS...

Usually, when backwards compatibility is required, people create an abstraction layer for the old software. But that slows things down.

This somehow reminds me of the C64 vs C128 thing. Almost nobody produced software for the C128 because it was backwards compatible with the C64 which had a much wider user base.

[quote name=Build-0-Matic post=10345]@Build-0-Matic - I just downloaded the ABIv0 image and this one works.

Now, I wonder why the ABIv1 team never checked to see if their fork worked in the first place?
With people disliking Windows more and more, hardware prices going up and up, and the excess of perfectly good hardware floating around, I see it as a great opportunity for AROS to become an interesting alternative for the oldest gear.[/quote]

ABIv1 isn't a fork it's the mainline branch. Much of the work has been focusing on 64 Bit that's where the main drive was/is. Add to that it's an open source platform so it relies on users to report bugs. Unfortunately that is where the contention comes in from my side. ABIv0 was the Original ABI, ABIv1 was designed to fix mistakes they made when ABIv0 was being developed. Unfortunately most applications at the time were ABIv0 so the Distro maintainers stuck with what was available. ABIv0 stagnated until Deadwood started back porting parts of ABIv1 to it which one could argue was good for the users but the flip side is ABIv1 lost in the end due to lack of users and no one will port software to a platform with no users so here we are in a chicken and the egg situation.