LISA File Transporter tool moves files from modern computers to the Workshop

[bmwcyclist]

I have found that FloppyEMU disk images on MicroSD cards often get corrupted. There are various reasons such as incomplete shutdowns etc. These tools will help check and verify LOS 3.x disk images.

AFAIK, corruption of FloppyEMU disk images is not a common complaint - please correct me if I'm wrong.

So I wonder if the image corruption you've experienced is a result of experiments in editing them, or if your particular FEMU has a technical problem. Did you experience corruption before the editing experiments?

The issue seems to be from the FPGA since it keeps power to the EMU after the "lisa" is shut down. Too hasty a card removal can cause issues, apparently.

[bmwcyclist]

Is the serial port configuration kept in a file or is it kept in some sort of parameter ram?

It defaults to 9600 baud at startup; one can reconfigure it using the startup exec script feature, eg: Portconfig Exec Script

For "voting on the best method" purposes, I'd select "all of the above" as different situations benefit from different methods.

Perhaps when (if) there is a workshop + LOS tool that does binary and multiple files rapidly, then that will win out.

The portconfig.obj tool is giving me errors on both A and B. "invalid device name"

.
So it is writing to a file or ram?

[AlexTheCat123]

The issue seems to be from the FPGA since it keeps power to the EMU after the "lisa" is shut down. Too hasty a card removal can cause issues, apparently.

I'm not quite sure how that could cause a problem, and I haven't observed anything like that myself, but it definitely needs to be fixed if it's truly an issue! Can you elaborate on what you think could be causing a problem when power is sustained after the Lisa is off?

[bmwcyclist]

The issue seems to be from the FPGA since it keeps power to the EMU after the "lisa" is shut down. Too hasty a card removal can cause issues, apparently.

I'm not quite sure how that could cause a problem, and I haven't observed anything like that myself, but it definitely needs to be fixed if it's truly an issue! Can you elaborate on what you think could be causing a problem when power is sustained after the Lisa is off?

I'm trying to reproduce the issue. I can almost guarantee you. It's end user error and not a problem with either the 210 or the FPGA.

[Eschaton]

Sadly, with AI's, there's no real way to figure out what they're doing, which is a big problem in my field, which is information Security. You can have them give you a list of sources, but it's not always accurate.

Just to clear something up: When you ask an LLM to explain itself after the fact, it's never accurate to what the LLM was actually doing, because they are not minds with that kind of introspection ability. All the LLM is going to do is incorporate the existing transcript of your interactions and produce a stream of next-most-likely tokens that happen to look like the explanation you asked for, regardless of what was actually going on under the hood.

That doesn't mean it might not be useful to you, since after all it may point you to references and give reasonable explanations of what someone asked to solve that problem might do, which you can learn from. But its relationship to what the model already did is arms' length at best.

[Eschaton]

Another source of information for the Lisa filesystems would be my lisafs, which is extract-only at the moment but if someone did the work could be used to put content into disk images. (I didn't feel like writing the B-tree insert code that filesystem v3 would require, and I don't use or allow LLMs in any of my projects.)

[bmwcyclist]

Another source of information for the Lisa filesystems would be my lisafs, which is extract-only at the moment but if someone did the work could be used to put content into disk images. (I didn't feel like writing the B-tree insert code that filesystem v3 would require, and I don't use or allow LLMs in any of my projects.)

Thank you!

[bmwcyclist]

Newist version:

A native Apple Lisa Office System application for moving files between a Lisa and a modern computer over a serial cable. Open it from a desktop icon, choose Receive or Send, and watch the blocks tick by in its own window — no Workshop session, no floppy shuttling.

Runs on Lisa OS 3.x. Serial B, XMODEM checksum, 1200 through 38400 baud — and yes, 38400 works on real hardware, well past Apple's documented 19200 ceiling, confirmed on two Lisa 2/10s.

Working now: receive · send · browse the disk and pick a file by number · adjustable speed · progress and block counts as it goes · any key stops a transfer.

Planned:

• Terminal mode, so you can drive a real modem and dial out
• CRC-16 in addition to checksum
• YMODEM batch — send a whole folder in one go, filenames and all
• Background transfers, so the desktop stays fully interactive
• A proper file-picker dialog
• File listing on machines whose boot volume isn't a 2/10's internal disk

Beta testers welcome — bug reports and feature ideas to LisaList2.

Built with the generous help of two people's published work: Alex Anderson-McLeod's heavily commented LOS Minesweeper, which is a teaching course in Office System app structure, and Tom Stepleton's lisabbs and format documentation. See less