You likely have WIRELESS INTERNET ability in your LISA right now!

[bmwcyclist]

If your Lisa boots from an ESProFile (Alex Anderson-McLeod's ESP32 ProFile emulator), it can now reach the internet with no other hardware.

Alex has approved of this being published, but he does not support the ESPFuji firmware in any way: ESPFuji questions and bugs go to the repository's Issues, never to Alex. The ESProFile boards and the stock firmware remain his.

ESPFuji is a firmware for the ESProFile that leaves the ProFile emulation exactly as it is and adds a network task on the ESP32's second core: a Lisa Office System program writes a request into a file on the ProFile volume, the drive fetches the page over Wi-Fi, and the program reads the reply back from the same file. Nothing on Serial B.

What it does: HTTP and HTTPS pages up to 32 KB, and the time of day from SNTP, in your own time zone. LisaFuji 1.2 (news, Wikipedia, the space station map, the weather, the clock) and LisaCheckers find the drive by themselves and use it instead of a serial FujiNet; the first complete checkers game through an ESProFile was played on 29 October.

What 1.0 rests on: one Lisa 2/10 and two ESProFile boards, a month of work, an 8-hour idle soak, 1,500-fetch overnight runs and a day-long soak of the release code with a fetch and a clock check every 15 minutes, nothing lost. Flashing is one Python command from Windows, macOS or Linux; the script backs up your original firmware first and puts it back with one command, and the SD card is not touched. The repository: https://github.com/GyroPilot/ESPFuji (not the official ESProFile repository, which is github.com/alexthecat123/ESProFile).

Release, README and the test tool floppy: https://github.com/GyroPilot/ESPFuji/releases/tag/v1.0

I will be posting an informational presentation later today if the internet at this campground holds!

I will attach the software images although it seems most people download from GlobalTalk or GitHub. I think LIsaList2 is a good archive.

If you are using LisaFuji software (Checkers, Salvo, LisaBrowser etc.) you will need an update to use this.

[stepleton]

This is another considerable capability enhancement, but I have to say that the method that this approach uses is a fairly strange one in my opinion. It requires the ESProFile to have some rudimentary understanding of the Lisa OS filesystem, or at least it must detect read and write patterns characteristic of Lisa OS file I/O. Different OSs would not readily be able to use this approach. It does have the advantage of not requiring the Lisa to have any special driver software. That said, changing the contents of a file without the OS's knowledge feels kinda weird...

...It works, there's not likely to be a fundamental reason it wouldn't continue working (unless there are radical community updates to the Office System, which these days who knows), but to this longtime programmer, it just feels kinda... cursed I guess... (It is Halloween, I suppose!) It's not the kind of thing you would ordinarily do, just because it kinda violates assumptions that other programmers and programs make when they code for a computer platform. What if someone else is writing an email app and chooses to store emails in a file with a perfectly ordinary name like MAILBOX.DATA? There would be trouble! (And while using a more obfuscated name like ~~00MBOX~~.DATA would reduce the odds of collision, it still feels like a bit of an untidy workaround to a risky method; there'd be something 95-era Microsoft about it.)

The ESProFile has other ways of exposing special functionality that goes beyond what a regular ProFile does. The Selector takes advantage of this functionality to list disk images and make changes to them. It's modular and extensible; you can add to it. There's documentation all about it here:

https://codeberg.org/stepleton/cameo/src/branch/master/aphid/selector/PROTOCOL.md

To take advantage of this capability, you would just say on a forum like this one, "I'm reserving another one of these 'magic blocks' for myself" (or more than one if you wanted, there are tens of thousands) and then have direct reads or writes to your magic blocks engage the FujiNet functionality. This would no longer rely on having an operating system that writes to files in the way the Lisa OS does. The downside is that you would need to make and install a driver on the Lisa OS. But Claude appears to be quite good at making drivers, the Lisa OS has a very sophisticated and capable driver system, and we have already seen projects ship custom drivers for various things. Other OSs like MacWorks and the Unixes would need drivers too, but it would probably be a good amount easier to make those than to make them do something that looks like the Lisa OS writing to a file.

So I guess I'm excited by the idea (have been interested to try out FujiNet for a while), but I'd hope for a different execution of it. I hope this criticism is welcome and that it seems constructive. I am sure it would be well within the grasp of the tools to do it in this way. What do you think?

[bmwcyclist]

Lisa FujiNet tools, 30 October 2026 update (Lisa_FujiNet_Tools_2026-10-30_pack.zip)

Every tool in the set now works three ways:

through an RS-232 FujiNet on a serial port,
on a LisaFPGA through LisaNet, Michael Wottle's ESP32 add-on on the FPGA's GPIO header,
or through an ESPFuji ESProFile, the drive your Lisa already boots from, with no serial adapter. Put the tool on the drive's own volume and it finds the network by itself.

What's in the zip:

LisaFuji 1.2: news, Wikipedia, the space station and crew, the weather, and the Lisa's clock from the network
LisaFuji Browser 1.2 beta: a text web browser
LisaTwinClock 1.3: sets the Lisa's clock from the network
LisaCheckers 1.2: checkers against the Lisa or people on other machines
LisaSalvo 1.2: Battleship on the FujiNet Battleship server
ESPFuji test tool 0.2: checks an ESPFuji drive and sets up its mailbox

Six Disk Copy 4.2 floppy images with a read-me each, for a Floppy Emu, BlueSCSI or LisaEm. Lisa Office System 3.1. Free and open (MIT); sources at github.com/GyroPilot. Thanks to Michael for LisaNet, and to Alex Anderson-McLeod for the ESProFile.

[bmwcyclist]

This is another considerable capability enhancement, but I have to say that the method that this approach uses is a fairly strange one in my opinion. It requires the ESProFile to have some rudimentary understanding of the Lisa OS filesystem, or at least it must detect read and write patterns characteristic of Lisa OS file I/O. Different OSs would not readily be able to use this approach. It does have the advantage of not requiring the Lisa to have any special driver software. That said, changing the contents of a file without the OS's knowledge feels kinda weird...

...It works, there's not likely to be a fundamental reason it wouldn't continue working (unless there are radical community updates to the Office System, which these days who knows), but to this longtime programmer, it just feels kinda... cursed I guess... (It is Halloween, I suppose!) It's not the kind of thing you would ordinarily do, just because it kinda violates assumptions that other programmers and programs make when they code for a computer platform. What if someone else is writing an email app and chooses to store emails in a file with a perfectly ordinary name like MAILBOX.DATA? There would be trouble! (And while using a more obfuscated name like ~~00MBOX~~.DATA would reduce the odds of collision, it still feels like a bit of an untidy workaround to a risky method; there'd be something 95-era Microsoft about it.)

The ESProFile has other ways of exposing special functionality that goes beyond what a regular ProFile does. The Selector takes advantage of this functionality to list disk images and make changes to them. It's modular and extensible; you can add to it. There's documentation all about it here:

https://codeberg.org/stepleton/cameo/src/branch/master/aphid/selector/PROTOCOL.md

To take advantage of this capability, you would just say on a forum like this one, "I'm reserving another one of these 'magic blocks' for myself" (or more than one if you wanted, there are tens of thousands) and then have direct reads or writes to your magic blocks engage the FujiNet functionality. This would no longer rely on having an operating system that writes to files in the way the Lisa OS does. The downside is that you would need to make and install a driver on the Lisa OS. But Claude appears to be quite good at making drivers, the Lisa OS has a very sophisticated and capable driver system, and we have already seen projects ship custom drivers for various things. Other OSs like MacWorks and the Unixes would need drivers too, but it would probably be a good amount easier to make those than to make them do something that looks like the Lisa OS writing to a file.

So I guess I'm excited by the idea (have been interested to try out FujiNet for a while), but I'd hope for a different execution of it. I hope this criticism is welcome and that it seems constructive. I am sure it would be well within the grasp of the tools to do it in this way. What do you think?

Thank you!

Great point about the filename, I did not think of that at all.

There are now 4 ways to connect the Lisa LOS to Fujinet; ESprofile is just one, but it does have an advantage in speed, and lots of people already own one.

I will make a filename change in the next version.

Writing a driver is more than I want to take on right now but... maybe someday.

If someone else is up for it, I would be more than happy to collaborate!

All constructive feedback is VERY welcome!