The colorful charm of Amiga utility disks
datagubbe.se
datagubbe.se
Operating system standardization have killed this kind of creative interface, it's probably for the best, but I'm pretty sure something bold and colorful can still happen and make a difference to users.
[1] https://www.datagubbe.se/utildisks/a5003-crop-2302041155-01....
It's coming back with Electron and other frameworks for apps in the browser. Of course these must also be responsive to multiple window sizes and input styles, whereas on home computers you could always rely on a fixed-size screen and standard mouse/keyboard/gamepad as inputs.
There's a few similar "fantasy consoles" with different amounts of restraints. Oh, and there's the Playdate console, which also seems to have a pretty vibrant community - they're limited to greyscale graphics though.
Clearly there is a yearning among users — even technical users — for more creative, colorful, and interesting interfaces.
That's why we have multiple variations on sixels, dozens of libraries for drawing charts in the command line, hundreds of colors were added to terminals, and thousands of tutorials for customizing command prompts.
I still believe being able to portray an upset alien in like seven or eight pixels is true art.
For those unfamiliar with the Amiga culture, it's worth pointing out that this frequently includes shaving bytes off tools. I remember more than once disassembling some CLI utility to strip out a few bytes here and there (seeing the poor, wasteful quality output of early C compilers delayed my switch from asm to higher level languages by at least a couple of years...).
Not just for the sake of saving disk space, but because you'd either make them resident in memory or copy them to a RAM: disk so you could more easily swap floppies and still have your tools available, and when you had 512KB or 1MB of RAM, every little bit made a difference.
dos.library is a pus-filled abscess that simply does not belong anywhere near it.
It is unfortunate they were in a hurry and just tucked tripOS in there.
The ABI also makes you pass said pointers in data registers, unlike other libraries in AmigaOS, instead of address registers, because of course there'd be little point passing them in address registers when they need to be transformed for use. Horrible.
There's additional uglyness elsewhere. Like processes vs tasks, or the IPC ports. It ends up adding overhead, a layer of bad grease on top of exec.library.
> Commodore produced a great many Amiga models, but for several years the gold standard was an Amiga 500 expanded with half a meg of RAM (bringing the total to a full megabyte) and an external floppy drive (bringing the total number to two).
These memory expansion cards went into the "expansion trapdoor" at the bottom of the A500 and most of them included an RTC - without that, you had to enter the date and time at every startup (of course only if you cared for your files having correct timestamps and other such stuff). I had one of those before I got a "Power PC Board" (https://mingos-commodorepage.com/sammlung/erweiterungen_deta...) because I needed something MS-DOS-compatible. The good thing was: when the "PC" wasn't in use, it not only doubled as a 512 KB expansion + RTC, but you also had a whopping 512 KB RAM Disk where you could copy some often-used programs to reduce floppy disk swapping.
> Fred Fish's AmigaLibDisks
Of course everyone (except maybe Fred Fish himself) called them "Fish Disks"...
If you have one of these around, please remove the expansion and cut the battery off before it damages the expansion and possibly the Amiga too.
Indeed, I had that very setup, but with a little twist... I still have my very weird oddity which is an external, non-official, 5"1/4 (not 3"1/2, like most people had) floppy drive. Among our group of friends we'd all do that because, at that time and in the EU at least, 5"1/4 floppies were so much cheaper than the 3"1/2 ones that for the price of about 3 boxes of 3"1/2 floppies we could buy 3 boxes of 5"1/4 floppies and the external 5"1/4 floppy disk drive reader (which I take it were assembled by amateur/hobbyist: they didn't look anything like official drives and were very raw, bought through friends-of-friends-of-friends).
Now that Amiga Internet forums are flourishing people have accepted that this was a thing (there are even rare pictures of the thing) but in the past I've had Amiga users explain me that this didn't exist and that I was seeing things (!).
To make the matter even more confusing Commodore did sell official 5"1/4 drives for the Amiga too, but these were different.
The "bootleg" 5"1/4 were, for all matter and purpose, identical to the 3"1/2 ones and we'd install a switch on the Amiga to decide if we were booting from the 3"1/2 or 5"1/4 and the OS had zero way to tell the difference.
So we'd use them as double-sided 880 KB floppies.
Note that in a PC, the controller abstracts the tracks from the operating system. You read and write sectors, floppy controller does everything.
In an Amiga, the controller reads and writes raw data, full tracks. CPU does handle the format of the track.
The track format is described in chapter 2 of the ADF FAQ[0]. The main reason it is more efficient is that there's no gaps between sectors; only one gap after the end of the track. This is because the Amiga way is to read or write a full track, starting at any sector in the track.
One reason the PC's controller does not do this is the cost of RAM when the PC was introduced. A full raw track takes a significant amount of memory.
Commodore Amiga: a visual compendium, for example [2]
[1] https://www.bitmapbooks.com/ [2] https://www.bitmapbooks.com/collections/by-system/products/c...
It wasn't too hard. Just mount a ramdrive.device volume of enough size, mark it as bootable, copy the minimal files for it to be usable, or just icon.library, loadwb, a few commands and a startup-sequence.
The Save File dialog had a second soundtrack (played briefly at 3:45).
The composer is Paul Van Der Valk, also known for Hybris.
We keep chasing realism for the graphical frontend and its depressing.
I don't like these new modern flat themes, they look like a medical prospect from a medicine.
And then later on my Amiga 1200 with an actual hard drive. With the then excellent Amiga Workbench.
Whilst I tinkered with Basic on C64 and the 500 it was with EasyAmos on the 1200 I properly started my programming interest.
I think it was Matt Dillon's DICE C compiler. A true legend, Matt.
Once I got a second disk drive some creative tinkering with a small RAM disk allowed me to compile without switching disks. Then I could sit back and watch my custom Mandlebrot generator slowly work its magic.
For a further hit of nostalgia, check out the 1994 Impact DK demo In A World of ASCII [1] which features a lot of demo effects that pretend to look like they were done in the Amiga CLI window
The CPU (with help from Agnus's blitter in some versions of trackdisk.device) would encode/decode blocks into sectors into tracks, including MFM encoding.
But the floppy drive they bundled was DD, and to get HD you needed an HD floppy drive capable of spinning at half speed. There's few models with that feature. A4000 bundled one such drive.
The relevant chip (PAULA, which also was the interrupt controller and handled audio and serial port besides floppy) was sadly never upgraded throughout the history of the Amiga.
I do fondly remember watching my brother copy disks using X-Copy though and being mesmerized by the UI.
https://duckduckgo.com/?q=udo+lindenberg+80er+jahre&t=midori...
Note the UDO on the menu ...
For me, it's safety first... whoever it was, it's now Chuck Norris.
The demo scene was maybe a bigger group, and still going I think.