4LIVE is a scratchpad for keeping notes while you're working on your Apple II under DOS 3.3. The current version ("revision 03") allows you to keep up to 99 separate screens of freeform text, accessible at any time that DOS is in memory.
- Apple II+ or later
- 64K memory
- DOS 3.3 or compatible third-party DOS (tested with Pronto-DOS, Diversi-DOS, and Diversi-DOS 64K)
When you first run 4LIVE, it will load only a small code stub in low memory, at $0232. This stub will load the rest of 4LIVE directly into LC RAM bank 1. Thereafter, 4LIVE uses $0309-$03CF in main memory and $D000-$DFFF in LC RAM bank 1. 4LIVE never uses LC RAM bank 2, auxiliary memory, or any other region in main memory.
Install 4LIVE by typing
BRUN _4LIVE from the BASIC prompt, or by executing it in your
10 PRINT CHR$(4);"BRUN _4LIVE"
Now you can press
<Ctrl+@> at any time to enter the 4LIVE editor. This works from the BASIC prompt or the monitor -- even in the middle of typing a command -- as long as DOS is in memory and connected. (If you can do a
CATALOG, DOS is connected.)
Keyboard commands within the 4LIVE editor:
<Esc>exits the 4LIVE editor.
- Arrows move freely up, down, left, and right. On an Apple II+, you can use
<Ctrl+J>in place of up and down arrows.
<Return>moves the cursor to the beginning of the next line. It does not erase any text on the current line. It will wrap around from the bottom of the screen to the top.
<Ctrl+B>toggles highlighting of the current line.
<Ctrl+T>creates a new 4LIVE screen and switches to it.
<Ctrl+R>switches to the previous 4LIVE screen.
<Ctrl+Y>switches to the next 4LIVE screen.
<Ctrl+C>clears the current 4LIVE screen.
<Ctrl+^>imports the "real" text screen you were looking at before you entered the 4LIVE editor (like taking a text screenshot).
4LIVE will automatically save the contents of your screen whenever you switch screens or exit the 4LIVE editor. It saves everything to the file
_4LIVE DATA. You will see this file in the disk catalog.
4LIVE is written in 100% 6502 assembly language, but it is developed on modern PCs (not in a "classic" IDE like Merlin-8). The source code is stored and managed in text files. These text files are assembled to executable code with ACME, then transferred to a disk image (
.dsk file) with AppleCommander. You can mount this disk image in any Apple II emulator.
If you are on Mac OS X and have the Virtual II emulator, you can use the included Applescript to mount the
.dsk file and reboot the emulator automatically. The included
Makefile does this by default (after running ACME and AppleCommander).
Thus, during development, my testing cycle goes like this:
.asource code file in any modern text editor
- Test in Virtual II
- GOTO 1
Thanks to Peter Ferrie, a.k.a. qkumba for his many contributions to this project.