Progress Update (plus 13 days)

So… I haven’t actually focused on this project for more than a couple of hours at a time. I ended up essentially going wildly asynchronous and setting up the Research Assistant to work on relatively small pieces of work while I did other things like having a job and living a life.

That being said, we did get quite a few major things done:

New ROM

The latest we’ve got in a ROM for the Osborne 1 is the OZROM 1E. It’s got a bunch of interesting features, but it’s missing a couple of things that we’re going to need. The biggest barrier to writing an update to the ROM is definitely the “cycling through the compile, write, install, boot, debug routine” and we don’t have that particular restriction. The MAME apparatus keeps proving the usefulness of being able to emulate the environment you’re expecting to work in. The point is carefully made in computer science that a less powerful computer can emulate a more powerful computer - just slowly. The reverse is so painfully true too. I’m doing most of the development on my Mac Studio and it has subsystem processors that are orders of magnitude more powerful than the Z80, when you combine that with --no-throttle, you get a whole different level of capability. The Research Assistant writes the test in .lua and then watches the memory map as the test executes. Basically “The Matrix” – the code that is running and creating the fabric of reality is under our control and from the inside of the Z80, it just looks like an office cubicle in 1983.

Adding features to the ROM is mostly about me being a whiny old man… I want the hard drive that I never had. Those drives were expensive - 10MB cost basically twice what the machine did and that’s the “slow” interface version. But taking the cue from so many other projects in the vintage computing community, we’re just going to bludgeon that one to death with a $10 part. More on that in a moment!

Side Quest - Drive C

On the way to hard drive, we took advantage of the availability of software drivers and reverse engineered the hardware side of the Drive C RAM disk. It’s interesting and would’ve been astonishingly fast for the time - just a brick of memory chips with a power supply and an IEEE-488 interface. They needed to draw power from the video shunt because that’s the only real power source available from the computer. There is technically a 12v line in the modem jack and with a jumper you can send 12v down the keyboard cable however that source is limited by a resistor to about 100mA and that’s not enough to do much. The hardware design is relatively complete and in emulation works well. The actual hardware would be the same RP2354B that we’re using for the Interposer just with a different electrical interface. The major downside of the Drive C in 1983 was that you either had to supply it with battery power or carefully load and unload it every time you hard powered the machine (it would survive a reset). Since we’re just storing the 384KB memory blob as a file on disk, we can stick it in a cheap 16MB flash chip and just provide a custom program (MOUNT.COM) that will let you change which of the stored images is currently “inserted”. In this way, it’s basically a double-sized floppy drive - and fast - but still not what you might actually want. The plan is currently to offer this as a hardware device for someone who wants to expand their Osborne 1 without opening it up. It will work with both the beige and blue models. I’ve been toying with just how small it could be made and it might be possible to lose it in a very small adapter but it really should go in the right floppy pocket.

Hard Drive(s)

Ok, great, we’ve got double sized floppy disks but we still need to boot from drive A or B and then run the driver to get to C. That’s cool but it’s not what we’ve come to expect over the last 45 years.

There were basically two implementations of a hard drive interface for the Osborne 1. The “easiest” was to use the IEEE-488 port. This was how some computers of the day (HP 85, CBM) did it. And there are a few projects that implement these disks. In theory, we could just pick up one of those projects and write a new CP/M driver for it. The other method for connection was with an Interposer card - basically tapping the 40 pins of the Z80 socket to exert our own will on the world. Most of the manufacturers followed the pattern that Corvus set up and did it this way. Because the hardware is completely fungible, I took the approach of looking at the drivers we had available and working backwards from there. The most complete driver set was the MD-10. There are a set of three diskettes available on Archive.org that complete the software picture. Mega-byte / Media Distributing produced the MD-10 and MD-20 drives using the ubiquitous Adaptec ACB-4000 SCSI<->MFM controller. By a cheerful happenstance, the OEM manual for the ACB-4000 is available and provides all of the details of the hardware and how to implement it. The software was relatively easy to puzzle out and not for the first or last time, Lee’s decision to memory map all of the peripherals made this work far easier than it should’ve been. The Adaptec card runs a pile of code on a processor of its own so the interfacing is relatively high level and allows for a small footprint on the Osborne side.

With a little bit of magic (and watching memory while executing), it was possible to sort out what the real hard limits were. And because I’m “that way”, we implemented right to the limit. CP/M is limited to just shy of 8MB per partition, drive tables take up a certain amount of memory space, and the ACB-4000 can handle two attached drives. Realistically the maximum number of partitions is 11. So it’s almost an 88MB drive array. In 1983, that would’ve been unthinkably expensive… buy a really nice car or a starter house kind of money.

You boot with the MD-10 floppy in Drive A and then transfer control to the CP/M installed on the hard drive. This pushes your floppy disk drives to the back of the list and inserts whatever partitions you have in front of the physical drives.

Yes, it’s still emulation (we haven’t built the hardware yet) but I can not only go to A: and B:, but also… C: D: E: F: G: H: I: J: K: and L: M: – that’s enough room to hold basically all of the available software for the Osborne 1 in a single 88MB file on a microSD card. There’s a script that you can use to load up the disk - it currently absorbs the original shipping diskettes, and then tacks on a selection from the FOG library. You’re going to really miss not having sub-directories though!

An Embarrassment of Riches

Never content, and with those tantalizing orginal source files for ROM 1.44… I went for broke. How much space can we realistically find in the ROM to do cool stuff. It turns out that there’s quite a bit of space available in the memory map… in fact, it’s trivial to have an 8KB ROM in a stock Osborne 1 if you bodge in a single wire for A12.

But wait! I’m sure you’ve all done the thing where instead of hitting to boot from drive A, you hit <"> to boot from drive B... did you know that a stock 1.44 ROM has a THIRD boot key? Yes it does... and that goes exactly no where. But we've now got what we need to have it go somewhere and do something. We can increase the size of the ROM and jam enough code in there to get the interface with the MD-10 up and read in the beginning of the CP/M stored there.

Yes, we can boot from ROM straight to hard disk.

IBM would end up doing this in the same 1983-ish time frame to add the ability to boot directly from hard disk to the original IBM 5150 Personal Computer.

There’s still a few more bytes available in there to get some of the OZROM functionality included.

Interposer Octopus and Looking Cool

We’re going to need to replace the Character ROM to be able to implement the SCREEN PAC personality on the interposer and we can also add an adapter that goes in the main ROM socket as well. The interposer ends up with four cables - power, ROM 1 and ROM 2, in addition to the user interface elements that will somehow be grafted onto the front panel (probably in the left floppy slot). That also allows the trapping of the address signal and passthrough of the original ROM chips if you want an “interposer-less” boot for some reason.

Since we’ve got this ragingly cool new ROM, we need the boot screen that goes with it. There’s not much room in that part of the ROM and I do not want to start moving CBIOS around to make more room. After experimentation, we decided to cheat the system on making a cool boot screen. The interposer is going to watch memory while the machine boots and when it sees the “fall back” boot screen, it’s going to do a little bus mastering DMA magic and write successive pages to the top 4k of RAM and forcibly paint animation there. Is it cheating? Probably. Do I care? HELL NO. It’s going to look COOL. Especially if you’re booting into 80 or 104 column mode.

That’s ROM 2.0 :: genuine new functionality.

But we’re not done!

It took a long time to get that ROM situation sorted out and I needed a break from software. It was time for some hardware work. The really big hardware work is coming soon enough, but let’s get some fundamentals out of the way to get our practice in. Starting simply… the Floppy Adapter. Richard Loxley did a fantastic job of putting a GoTek into the right-side floppy pocket and doing the careful job of chopping up the signal wiring to allow him to switch between the physical floppy drive and the floppy emulator. This is a great idea but just needs a little smoothing around the edges. So we planned out a little adapter that sits on top of either the mainboard or the dual density board (if you have one) and essentially throws a Y in the cable with the drive select line and both power and ground switched. Either work out a hacked up cable to fit through the vent slots and make no cosmetic changes to your machine or just chop out a vent slot so that you can feed a standard 34pin floppy cable and the switch lead through and you’ll have the “up = physical floppy, down = emulated floppy” switch that you’ve always wanted.

And since I was on a roll, why not tackle what I think might be the most popular piece to come out of this project… the WiFi COMM PAC! It’s a combination of hardware and software but it’s going to be sooo awesome! Start with the hardware side - using the left floppy pocket as the installation spot and linking to the same 9pin modem connector used by the original 300 baud COMM PAC. This is going to be so easy because I have the 12vdc there and I’m only running a power sipping ESP32 and some blinky lights… piece of cake right? Nope. That 12vdc is really heavily limited and isn’t going to do much more than about 100mA so… I need power from somewhere else… Back to how the Drive C got it, straight off the CRT supply. Should be good. Will look a little wonky but it is what it is. Alright, hardware spec done. But we don’t want to rebuild anything we don’t have to… how about Zimodem? Sure - it doesn’t do the blinky lights or the modem torture screams I want but it does everything else, time to fork Zimodem and see what we can get done. Turns out quite a lot actually but there’s really no way to do the testing.

Enter “crazy ideas for $100 Alex”. MAME probably has a serial port virtualized, or we can go ahead with writing a monitor that watches the ACIA registers and “fakes” being a serial port right? Yes we can - there’s a virtual serial port right there that can be connected to a PTY on the underlying host operating system. So… what if we added a “super duper” serial adapter in there in the form of a second ESP32 TX-RX wired to the Zimodem test board…

MAME’s ACIA -> pty -> relay -> super-serial-port -> UART1 -> modem -> wifi -> TELNET BBS

So from my emulated ROM 2.0 Osborne (with SCREEN PAC) that boots directly to an 88MB hard drive, I can run MDM740.COM and just type ATDT hostname port and be on a BBS? Yes I can.

The modem schematic is done, just a matter of knocking out the floorplan and wiring it up. Then order the boards (probably assembled) and I’ll be able to call that part done.

Along the way some more emulation

To make sure that all of the firmware we’re going to be running on that RP2354B is actually able to run on it, we set up picoem and found a few bugs to fix but have the beginnings of the software that runs on the interposer board – a complete round trip hard disk transaction from MAME to picoem and back again. It doesn’t emulate quite everything so we’re still going to be in hardware hell for this one. until we can be sure that we’ve wired up everything we’re going to need. The first version of the interposer is going to have a lot of test points brought out as header pins so I can remap things without a lot of rework.

Confidence Increasing!

What started out as a “maybe” attempt to get the Co-Power-88 board that I have running has turned into me working on literally everything but that. We did some decompilation and document writing at the beginning that shows how to do it but nothing actually completed. Oh, we did do a cleanup round on the documentation. There’s a lot of documentation. The Research Assistant is very good at reading and also very good at structuring what it learned and writing it all down again. It’s well over 300 pages long at this point.

I’m pretty confident that we’re going to have not just real hardware and software to show for this but a whole new world of what can be done with the Osborne 1.

But AI is involved!

Is all of this just “AI Slop”? There’s a certain amount of “yes and no” in the answer. It’s certainly got elements of “wow… you said something simple in the most complex way possible” but it has also been very much a case of the tooling needing a ton of creative insight and guidance to get to where it is possible to have the outcomes that people might expect. I’ve kept all of the history of how this was created - 160 issues and over 200 pull requests as of today. You can just walk through them and see how we ended up here together. It was not a simple or seamless process. I’d argue that without the architectural insight and memory of being a user of the system, we never would’ve made it this far. Like I’ve said before, this is augmentation, not just replacing the developer/architect but doing the hard parts in the human brain and the mechanical parts in the non-human side. I’d go with ‘slop adjacent’ but also… come on… this is pretty cool and would’ve taken a large team months to accomplish what we’ve been able to pull together in less than a month.