I've successfully built LOS from source!: https://lisalist2.com/index.php/topic,644.0.html
Quote from: berskyboy on October 29, 2026, 09:22:28 AMI tried the Piggyback method still getting
00000186 0000 8000 0000 0000 0000 0000 0000 0000
Quote from: stepleton on October 30, 2026, 01:20:19 PMThis 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?
Quote from: berskyboy on October 29, 2026, 04:11:50 PMI'm assuming I need to replace these two ROMS...
Quote from: sigma7 on October 28, 2026, 01:55:27 PM
- A Lisa CPU Board Video PROM which has an Apple part number of 371-0072
Quote from: AlexTheCat123 on October 06, 2026, 03:42:16 PMYou're getting low-high-high beeps though, which means that you have a RAM error. One of the memory chips on one of the two RAM boards probably went bad, or a board could also just be making a bad connection with its slot. First try reseating both boards, but if that doesn't fix the problem, then you'll need to go into Service Mode and follow the instructions at this link to figure out which chip is bad. But obviously you can't do that until the video board is fixed!
https://lisafaq.sunder.net/single.html#lisafaq-hw-mem_error
To test the keyboard, try pressing Apple-S (which enters Service Mode) after the error beeps. You should see the screen change rather significantly. If you haven't replaced the foam and foil pads inside your keyboard yet, then it is very unlikely to work until you do that.