General Category > Building LOS From Source

Moving the many source files to the Lisa

(1/10) > >>

sigma7:
Generously, Alex has provided a ProFile image with the Workshop and his build scripts installed via GitHub: https://github.com/alexthecat123/LisaSourceCompilation

However, since the License to download the Source files prohibits re-sharing them, posting a ProFile image that already contains the source files isn't allowed.

So, to actually build LOS from Source on a real Lisa, each individual has to move the many source files to the Lisa...

While we figure out the best way to do that, please post your ideas and progress here to minimize duplication of effort.

sigma7:
for future use... I'll put links to the top choice(s) here

sigma7:
Trying to brainstorm the possibilities, I've collected the following suggestions:


* Using the Workshop's scripting to automate multiple transfers via Serial
* Writing a specific program to transfer via Serial
* Transfer via Floppy using the MacCom function
Alex reported in his VCF presentation that floppy transfers introduced corruption; perhaps solving this problem is a possibility.

It has been suggestion that a method of packing all the necessary files into one, then unpacking on the Lisa is likely to minimize effort.

sigma7:
Additional thoughts

* Create a ProFile image with all the source files installed, over-write the contents of the source files in the image keeping the file structure otherwise intact, share the image along with some software that will repopulate using the source files on a local machine
* Remap the console to a serial port and simulate typing each of the source files
* Use the file manager to copy from a serial port to a file (same as the Transfer program but maybe easier to script?)

stepleton:
An option to consider is to do serial port automation for text file transfer by means of a custom program that runs on the Lisa. The program should listen on a designated serial port configured to use 8 bit bytes and whatever speed we think we can get away with. It begins in "idle mode", where if it receives a string like this:

~~~~~~ NEW FILE: APLW/UNITDSP.TEXT ~ LINES: 1397

then it opens the text file "APLW/UNITDSP.TEXT" and fills it with the next 1,397 lines that come over the wire. Once 1397 lines are received, it closes the text file, returns to idle mode, and awaits the next file. This continues until it receives the string ~~~~~~ THAT'S ALL FOLKS, where it quits. LIBPORT.TEXT from my old LisaBBS project might be a help, though it doesn't really have a concept of line-based I/O.

On the other end of the serial cable, a modern computer. Either it uses a modern program which scans the Lisa source code directories and sends them off one by one between the NEW FILE delimiters, or, even simpler: write a program that concatenates all of the source code files with these delimiters into one very, very large single file and send that out the serial port. These programs should both be pretty short, and probably writing it in Python would be quick work for your favourite AI, although no shade if that kind of thing doesn't appeal.

(If it doesn't bother you, here is Gemini's attempt, which looks pretty close to me: https://g.co/gemini/share/b412e38848e1 . It makes use of the pyserial library.)

...

While I was typing this, the idea you (sigma7) shared of having the modern computer just drive the console-remapped Workshop over the serial port seems mighty appealing, requiring no programming on the Lisa side, and it could make use of a lightly-modified version of the AI-made program I linked above. Is there a way on the Workshop side to write data from the console directly into a file?

[note: some edits to fix grammar etc.]

Navigation

[0] Message Index

[#] Next page