32 comments

[ 2.7 ms ] story [ 84.7 ms ] thread
I never would have guessed that the Kickstart 1.x graphic was vector, but it’s so clear in retrospect. It’s not hard to spot the nodes of the pre-Bézier shape paths once you’re looking for them!
What’s even more impressive is a basically identical graphic was in the 8KB A1000 boot ROM, to ask for a Kickstart disk
There is a youtube video in the comments with a recreation of the vector image from the original graphics:

https://www.youtube.com/watch?v=gXhxE4j6dm0

Using AMOS Basic nontheless
Yes, a powerful language paired with an incredibly fast interpreter/compiler even on low end Amigas; not a BASIC fan here, but have to admit it was really great. It's also Open Source [0], although it's entirely written in M68K assembly language (hence the high speed) which would likely turn any porting effort into a nightmare.

[0] https://web.archive.org/web/20151031001644/http://www.pianet...

It also has an odd mix of anti-aliased text and non-anti-aliased. Additionally, I don't like the aspect ratio of the floppy disk.
> Additionally, I don't like the aspect ratio of the floppy disk.

The Amiga used a standard 320x200 pixel mode [1] for it's boot screen. On a normal 4:3 CRT this mean the pixels are non-square. Since CRTs are analog, it doesn't really matter to the monitor, but if you just look at the digital bits without stretching them it looks a little flat.

[1] https://en.wikipedia.org/wiki/Mode_13h

Root cause: The Amiga didn't have curves in its graphic primitives.

Just this week i read an article in a 1986 Byte magazine which included a comparison of the Amiga and Macintosh graphic privatives. The Amiga had color routines, but the Mac had circles, curves, rounded rectangles, and a few other desirable shapes that the Amiga lacked.

Except for the text, the Kickstart image is not a bitmap, it's the output of a vector drawing program using the built-in ROM routines. No curves, and that's what you get.

Edit: September, 1986, page 251.

For me mostly the aspect ratio looks too wide. Not sure if it also looked like that on an Amiga monitor, did it have square pixels?
Most TV output and home computer monitors in the 1980's did not have square pixels.

Source: lived through those times...

I thought it was just the Amiga. Like, Macs had square pixels, to my recollection, both 512x342 and 640x480. I had forgotten that VGA was 320x200 not 320x240, but PCs also had 640x480, so it seems like square or not square depended on the mode.

Strictly speaking, I don't think square pixels were a characteristic of the monitor. If you looked closely there were little dots on a shadow mask monitor considerably smaller than the average pixel, or horizontal gaps between the wires on a trinitron.

(comment deleted)
And just to throw a wrench into things, EGA had modes like 640x350.
Bad? What about iconically good? Instantly recognisable definitive Amiga ... that's good isn't it?
Yes, it's pretty great by the standard of the time!
In the mid-late 80s, I didn't think anything about the Amiga was as polished and nice looking as the Mac, but the insert floppy graphic didn't stand out to me as below the standards of the rest of the interface.
If you want to see what the image would look like at high resolution -- I couldn't resist making a small JS implementation: http://ianhenderson.org/kickstart-vector.html
Now imagine your boss coming back a week later.... panic, I showed it to the client and they love it. Can you quickly change it to hold the floppy between the index finger and thumb - at an angle? It's probably easy to do.
Nice. Might be interesting to try ctx.scale(0.9,1) or whatever ratio approximates the pixel shape on the Amiga in that video mode...would square up the shape of the floppy.
Added to mine. Experimentally, it looks like a 4:3 ratio makes the floppy come out square, which lines up with expectations.
(comment deleted)
An unfinished, but "sorta working" attempt to recreate that vector drawing data onto an html canvas.

https://jsfiddle.net/kw4b95gv/4/

I didn't do the color flood fill, and something isn't quite right, but it's recognizable.

I tried to debug it by assigning a different color to each path:

https://jsfiddle.net/s2L3ydrx/15/

but it just gets the color of the final path, and I don't know why.

I fixed the errant lines bug and updated the link.
Tossing my JS implementation onto the pile as well, I guess. Missing the flood fill command; picked the wrong graphics library for this and it was too late by the time I'd realized it. ;) Easy enough to change over to something else, but it's time to move on.

https://codepen.io/Fortyseven/pen/rNWZpJb