Comment by JetSetIlly | Hacker News Reader

Comment by JetSetIlly | Hacker News Reader

> Farting around with Amigas in 2026 means actively choosing to make things harder for the sake of making things harder. Making that choice and still outsourcing the bulk of the craft and creative process is like claiming to be a passionate hobby cook while serving professionally catered dinners and pretending they're your own concoctions.

People wanting to explore the use of generative AI for vintage computers is happening not just for graphics but for code too.

I think in the case of code though, it's still interesting because I don't believe there's been any success yet. I hear of people having success with Claude in contemporary settings but it seems to fare less well when working for older computing platforms. There's a reason for that of course and it's worth exploring.

However, it will cease to be interesting as soon as the first person manages to create something substantial. At the point, the scene should probably shun it for the reasons stated in the quote.

There's definitely been success in using generative AI for vintage Computers. Just the other day I got it to produce a bootable floppy for my Amiga 1200. It loads the network driver, uses BOOTP to get an ip address, connects to a server and then downloads code via UDP that it will then execute. I doubt you'll get it doing amazing graphical scenes like you see in the demo scene though.

I really meant in the coding realm, but it's interesting that it created a bootable floppy. That wouldn't be trivial.

Questions: 1) Which AI platform did you use? 2) Did it create a binary image of the floppy disk (an ADF perhaps)? If not, what form did it take?

I used cursor with a mix of Gemini 3.1 and opus 4.6.

It referenced the Amiga ROM Kernel Reference Manual, appendix C to create a boot block in assembly. It's a raw sector-mapped image, the build process creates a blank adf, which then writes everything at it's fixed offsets and we go back with another tool to patch the bootblock with the right checksum so the kernel accepts it.

I copied that adf to the A1200 so I can then write it to a real floppy.

> That wouldn't be trivial.

INSTALL DF0:

Just type that and your disk is bootable.

What I find mind-boggling is the handwave over the rest. "Loads the network driver" - ok, which one? There's no standard network driver, only a specification for writing drivers (SANA-II). Was it a driver for SLIP/PPP over the serial port, or a PCMCIA Ethernet adaptor, or something else? Was it a copy of a driver someone's already written?

Also, it would be madness to try doing this in a bootblock, or insinuating that the bootblock did it. Demo bootblocks take over the hardware and start using their loading routines, eschewing the main AmigaOS, and that's the implication of saying something was done in the bootblock (you have under 1KB of space so the first thing you need is your own loader).

What's much more mundane and normal is a standard bootblock which returns control to AmigaDOS and lets it run the startup-sequence, whereupon you can use normal files, libraries, devices, including a full suite of other people's networking software, including BOOTP (AmiTCP comes with a client) and TFTP (see Olaf Barthel's tftpclient: https://github.com/obarthel/amiga-sana-ii-tftpclient). But it stopped being the "bootblock" that did it as soon as it started AmigaDOS.

Reply on news.ycombinator.com