Recent content by Thom Cherryhomes

because one of the main features is literally to boot and load software over the Internet. we also wanted to utilize the floppy port's faster access speeds. This device makes sense, the more resource constrained a machine is, so it will give a 128k Mac, features that otherwise would not be...

Yeah. I know there's a hard limit as to what hardware will be able to support this, but we're trying anyway. :) Next few weeks are going to be very interesting seeing how many different ways I can abuse the IWM...

Yes. Everything we release is GPL v. 3. We want this to always be free.

Yup indeed, this is a possibility. :) -Thom

Completely understandable, my only counter is that everything we do is open source, and freely available, now and forever. We want people to use our stuff; without reservation. Firmware: https://github.com/FujiNetWIFI/fujinet-platformio Hardware: https://github.com/FujiNetWIFI/fujinet-hardware...

Host slots, are TNFS hosts where you can mount disk images into drive slots. So, e.g. in that picture, there's a copy of System 6.0.8.img being mounted from host slot 2 (which is fujinet.online). There is a special host name, 'SD' that you can assign to a host slot, to read/write stuff off the...

The Mac FujiNet needs to be able to interact with the IWM directly, so that we can send our own messages to handle control and networking functions. Is it safe to twiddle the IWM registers directly? Long term will most likely be a new DRVR, but I'm trying to get us bootstrapped. I know I am...

Still sculpting on it, but here's a pic. Here's the corresponding FujiNet on Superbenk's desk:

Yes, intent is for additional commands to be added to support it, and a device driver on the Mac side to expose it. And yes, this is explicitly meant to support even the 128K Mac, so we have to go floppy. -Thom

Because it natively supports booting disks directly, and we can extend DCD to provide access to the other subdevices with new device drivers (even the virtual printer).

Yup, it sure looks like it. Thanks guys. The reason I am using Retro68 here, is literally because this program needs to become part of our whole stack, and be able to be built e.g. from a pipeline. But this is doable, if a wee...bit....awkward. :) -Thom

Has anyone managed to make a usable DRVR using Retro68? I need to prototype not only a desk accessory (for the FujiNet Configuration UI), but also a device driver that will talk to the FujiNet via the floppy port. -Thom