Just unpacking

[Mysha]

All these people who have problems with programs: I don't have those. I've downloaded <AROS-20240229-linux-x86_64-system.tar.bz2>, I think from 29 February, and now that I've gotten it to the right computer, it tells me that the file is not a bzip file.

Any known problems, or should I just try anew with a more recent archive?

[AMIGASYSTEM]

What OS do you use, and what program do you use to unpack?

[Mysha]

What OS do you use, and what program do you use to unpack?

OK, that suggests it's not a problem throughout. Let me see: I run Ubuntu Mate (let me check for that computer) - here I am again - 22.04. Engrampa is doing to unpacking; curiously, it's doing the unpacking of the contribs (I think) fine, while I'm typing t his. This looks like it's going to be a redownload.

[AMIGASYSTEM]

I have no problem with Windows, I unzip quietly with WinRAR or 7-Zip
Make sure the archive you downloaded is not corrupt !

[Mysha]

I have no problem with Windows, I unzip quietly with WinRAR or 7-Zip
Make sure the archive you downloaded is not corrupt !

Thanks. The archive I downloaded is OK, but the copy I had on my memstick I'm a bit in doubt about.

BTW, when I unpack AROS on a memstick, would that be a CD or a harddisk with floppy? I never do that, but I noticed that only a harddisk version has a floppy with it.

[AMIGASYSTEM]

I don't use Linux, but I think you can build a CD ISO, to make it Bootable you should have the knowledge !you cannot create a Live Pendrive, you can create it later using InstallAROS

My AROS One x86 Distribution, you can download it as an ISO or as a USB image that you can burn to a Pendrive or External USB Hardisk.

[Mysha]

I have no problem with Windows, I unzip quietly with WinRAR or 7-Zip
Make sure the archive you downloaded is not corrupt !

Thanks. The archive I downloaded is OK, but the copy I had on my memstick I'm a bit in doubt about.

Sent it over by sneaker-mail again. (I always wonder if we could write out an actual sneaker-mail protocol.) This time everything went fine. Thanks for reassuring me that it worked for you.


So, this is now a non-topic. Is there a way to get rid of it, now that it's no longer relevant?

[AMIGASYSTEM]

Can serve for other users !

[magorium]

All these people who have problems with programs: I don't have those. I've downloaded <AROS-20240229-linux-x86_64-system.tar.bz2>, I think from 29 February, and now that I've gotten it to the right computer, it tells me that the file is not a bzip file.

Any known problems, or should I just try anew with a more recent archive?

The automatic builds rotate every night when there was a succesful build so i can't check/verify with the exact same archive that you downloaded.

Simply replace the numbers of the date to match the current date, and in case the link fails check on the www.aros.org download-page
which was the latest date that had a succesful build (and change the numbers accordingly).

Download the archive:

Code: (bash) [Select]

$ cd temp
$ wget https://sourceforge.net/projects/aros/files/nightly2/20240301/Binaries/AROS-20240301-linux-x86_64-system.tar.bz2

Check type of file:

Code: (bash) [Select]

$ file AROS-20240301-linux-x86_64-system.tar.bz2
AROS-20240301-linux-x86_64-system.tar.bz2: bzip2 compressed data, block size = 900k

download and verify MD5 checksum:

Code: (bash) [Select]

$ wget https://sourceforge.net/projects/aros/files/nightly2/20240301/Binaries/AROS-20240301-linux-x86_64-system.tar.bz2.md5
$ md5sum -c AROS-20240301-linux-x86_64-system.tar.bz2.md5
AROS-20240301-linux-x86_64-system.tar.bz2: OK

unarchive:

Code: (bash) [Select]

$ tar -xf AROS-20240301-linux-x86_64-system.tar.bz2

Start AROS:

Code: (bash) [Select]

$ cd AROS-20240301-linux-x86_64-system
$ boot/linux/AROSBootstrap
... and AROS should be showing its face.

Note that, in case nothing changed all this time, that the archived build that you downloaded is not compatible with deadwood's work (which is a fork and is using ABIv11 for 64-bit).

[magorium]

BTW, when I unpack AROS on a memstick, would that be a CD or a harddisk with floppy? I never do that, but I noticed that only a harddisk version has a floppy with it.

With regards to the specific archive you downloaded ? Neither.

You need the native version in case you want to natively boot AROS. So for a 64 bit machine that would be the archive that is listed on the download page as: pc-x86_64-boot-iso

The imo easiest way to get that to work is to boot that iso from a virtual machine, attach a thumbdrive to your VM and use the AROS installer to install AROS to that thumbdrive. Once done you can use that thumbdrive to try and boot AROS natively on your hardware.

As noted by AMIGASYSTEM, both AROS one and icaros also provide a (raw) thumbdrive image that you can directly write to a thumbdrive to safe you the hassle of preparing it yourself.

Please do not bother writing ISO's to a physical CD-Rom (it more often goes wrong than that it actually works) and none of the available tools that allow you to boot (Linux/windows) ISO files is able to boot AROS.

Do note that not every hardware is supported by AROS and that it requires older hardware that is compatible with AROS in order for this to work. It is finicky.

My rule of thumb: if the hardware is too new to be able to boot AROS then the hardware is usually fast enough to be able to enjoyable run AROS hosted (on your main OS) or running it inside a VM

[Mysha]

Thanks for the description. It has no direct equivalent to what I actually do, but it's a nice overview to work off of.

The one thing I am not sure about is the closing bit about AB1.*, though it can well be that that's my confusion.
I have 86*64 machines; I usually run Linux, though admittedly the one I now loaded AROS to, could be made to run AROS natively. The last time I paid attention to the OS versions, I believe AROS had a restructured version as its target, that the 64 machines were moving towards, while your 32-bit (ah, it'll come back to me) distribution was a bit more conservative.

Is this all still the case, or have the goal posts moved?

[magorium]

Is this all still the case, or have the goal posts moved?

It is complicated but I'll try to give it a spin.

As natural progression the 64-bit version of AROS came into play. A long story short, that resulted in the 64-bit version of AROS taking some other approaches than the 32-bit version did.

Because 64-bit AROS never came to full frutation as the 32-bit version did (distro's available, people porting software) deadwood made the decision to make a spin-off of the 64-bit version of AROS with the aim to make the experience as close as possible to the 32-bit version, also backporting new features from the original 64-bit version into AROS 32-bit (development of AROS 32-bit practically came (or was) to an hold at that time).

So, now we have 32-bit and 64-bit versions of AROS that are almost up to par with the original AROS implementation and deadwood came with another idea, named axrt (aros executable runtime environment). This allows for AROS compiled software to run natively on your Linux machine. This in the hopes to increase interest for porting 32-bit software to 64-bit and perhaps also attract some more souls as development can be done natively on Linux and for missing functionality you can fallback using Linux API, so be able to gradually port software).

I am sure i forgot to mention some tings here and there or perhaps there are other goals but you would have to ask one of the AROS developers about further details.

Point being that afaik none of the original AROS developers hang around here anymore (they reside on slack) and here we mostly focus on work done by deadwood's forks. Do note that things are ported back'n'forth between the different repositories of AROS that do exist, though afaik original developers completely seized 32-bit development of AROS.

Does that help you in having a better understanding ?

[Mysha]

Oof - Legendary member talking to a Newbie (Though "Legendary" would suggest you are no longer part of the project, and "Newbie" would suggest I'm completely new to it.)
Ok, so thanks for the story, but the short is: (The developers, who are no longer at the mailing lists, have gone where I can't take part, and) The version for me to get, would be for 86 - Nightly ABI1, to catch the problems, and Nightly ABI0 to be usable.

That would brings us to the icon manager tool, that can be run without doing more harm than HELP. Any progress?
And obviously, this would suggest a tool to make a disk bootable, that'll work on memsticks. Is it there yet, or will I have to move things over from memstick do harddisk each time?

[magorium]

Ok, so thanks for the story, but the short is: (The developers, who are no longer at the mailing lists, have gone where I can't take part, and) The version for me to get, would be for 86 - Nightly ABI1, to catch the problems, and Nightly ABI0 to be usable.

uhm, no. Not exactly 

@deadwood: in case I got something wrong here then please add your (valuable) input.

The people that make distributions (AROS one for instance) and develop software (miker for instance) use the new ABIv0 created by deadwood. It leave things incompatible to older distributions such as Icaros Desktop and AspireOS. www.aros.org also does not support that old(er) ABIv0 anymore.

Deadwood backports new features from 64-bit ABIv1 back to his (alternate) version of AROS ABIv0 and can be found here and on his github here.

The date mentioned in the downloadable archive names is the date that signifies the changes (up to that date) that were made in AROS 64-bit (ABIv1) that can originally be found at www.aros.org and https://github.com/aros-development-team/AROS.

That was the information concerning the (32-bit) ABIv0.

Then we have 64-bit (ABIv1 at www.aros.org) which is forked by deadwood as ABIv11 and is entirely focused on 64-bit AROS. ABIv11 and ABv1 are incompatible with each other.

That would brings us to the icon manager tool, that can be run without doing more harm than HELP. Any progress?

I am not entirely sure what you meant with icon manager tool but am assuming you are referring to the work that user Miker is doing on his icon tools ?

And obviously, this would suggest a tool to make a disk bootable, that'll work on memsticks. Is it there yet, or will I have to move things over from memstick do harddisk each time?

The only way to install AROS is either by physical booting a CD-rom and use the installer or boot AROS from a memory stick and use the installer.

Those are currently the only two options that are available to make it possible to try AROS to run native on hardware.

Actually there is a third, namely using a raw HD in a VM, boot AROS from ISO or memory stick in the VM and install AROS to the raw attached HD. Afterwards, move the HD physcially from your VM machine to the final hardware where you want to have AROS run, but that is tiresome, not for the fainthearted and thus not for everyone.

[magorium]

@deadwood:
Writing the above actually made me realize if it would be an idea to make a (humble) request/issue to try and explore if it would be possible for AROS to be used with something like ventoy and what would be required (if any) to accomplish such task.

I am aware that such request was made in the past and was denied for obvious reasons (each solution booting ISO's requires its own solution) but looking at how a more mature tool like ventoy approaches this it might perhaps be something that makes it worthwhile ?

Oh, and I am aware that hosted with USB enabled should be able to do the trick as well but I can't seem to get that to work (last time I checked it was not enabled by default but that might have its reason(s))