@zwangseinweisung If anyone tries to do a similar project with Amiga-related system software today that doesn't involve AROS and Cloanto or Hyperion finds out about it, you're sued into oblivion.
Speaking as an Amiga enthusiast, this is why I find the Atari community more mature, more friendly, and will out-last the corresponding Amiga community.
Congratulations on the effort! It makes me very happy to see EmuTOS development continue.
@vertigo @zwangseinweisung This is part of why I'm playing with the Atari ST for my 16bit computer itch. With the Atari I can look at the source code to see what an OS from that period did (relatively speaking). I can't do that with the Amiga ROMS (or really AROS either, since AROS feels more like an Amiga-inspired OS than an actual Amiga-based OS).
Much thanks to Caldera and the EmuTOS team for making this all open and GPLed.
@craigmaloney @zwangseinweisung AROS isn't (well, *wasn't* when I last looked at it) too far from actual AmigaOS. The exec.library wasn't very sophisticated, and I basically replicated its core functionality back in the early 2000s in assembly language.
If it'll help, I recommend studying the architecture of Tripos (Cintpos will work as a modern-day version). That'll tell you a lot of how AmigaOS worked under the hood.
@craigmaloney @zwangseinweisung I think the problem with AROS is that they have this obnoxious build environment, which seems entirely overkill for what they're trying to achieve, and I think it obscures a lot of details.
Also, now-a-days, they depend so heavily upon Zune (their MUI replacement, not the MS music player) that applications are all quite complicated now.
@vertigo @zwangseinweisung Thanks. I'm still at a pretty basic level with GEM. The plus side with that is I have access to however low I want to go with it, and it's non-multitasking. It's pretty nice and flat from what I've seen.
Eventually I'll take a look at Tripos, but even the Amiga CLI is just a daunting mess with the c, t, u, p, s, and whatever other single-level directories are in there. And I thought UNIX had the prize for brevity.
Note this confusion though: AmigaOS != AmigaDOS != Tripos. AmigaOS is literally everything *except* dos.library. So intuition.library, exec.library, and so forth are all part of AmigaOS.
AmigaDOS is dos.library plus the shell and its commands. This is a *port* of Tripos to AmigaOS, but there are some minor differences from raw Tripos. E.g., the use of exec.library to pass messages.
@craigmaloney @zwangseinweisung And then there's Tripos, which is a self-standing OS unto itself. Its kernel has something like 30ish system calls, and has a lot of similarities to AmigaOS, hence why AmigaDOS was so easily ported to it. A lot of Tripos system calls are actually "standard library" calls in AmigaDOS applications, implemented as macros which just invoke AmigaOS equivalents.
@craigmaloney @zwangseinweisung This confusion all comes from the Commodore engineer's inability to deliver CAOS (Commodore-Amiga OS, appropriately named) on time. So CBM rushed to get an OS implemented via a 3rd party (Metacomco, IIRC). Since Commodore had already written much of the core OS already, Metacomco just ported over the bits of the OS which were missing.
Fun fact: if CAOS had been completed on-time, it would have been a Unix-alike, similar to OS-9.
It also supported "assignments" (similar to VMS's "logical volumes", but as of AmigaDOS 2.0, closer to Plan 9's union-capable mount points). C: would map to SYS:C, and SYS: would map to the boot volume, etc. LIBS: and L: are both libraries; LIBS: for AmigaOS, L: for AmigaDOS.
@mmu_man @clarjon1 thanks. Maybe a Copy/Paste Error :( https://sourceforge.net/projects/emutos/files/emutos/1.0/
@zwangseinweisung wie haben denn die rechner überhaupt solange durchgehalten????? meine beiden 1040stm waren schon seit '98 tote bretter...
@jayrope in kurzform: Pflege und Benutzung. Außerdem haben die nicht wie alte Apple oder Amigas eine Batterie auf der Platine. Das was ich hier an Atari Hardware habe (ist nicht wenig) läuft alles noch
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!