1
0
mirror of synced 2026-01-15 00:12:24 +00:00
Interlisp.medley/docs/internal/DAYBREAKS.TEDIT

3 lines
4.5 KiB
Plaintext
Raw Blame History

This file contains invisible Unicode characters

This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

Daybreak Software Installation and Operation
This document is preliminary. It probably won't really be the way things work when the product is released.
The power switch and reset button are located on the front of the daybreak. There is no "ALT-B" button to specify alternate booting choices. Instead, the blank function keys along the top of the keyboard are used to specify the boot device.
When the daybreak is first turned on, the screen will be filled with a gray pattern with a solid white cursor in the upper left corner. Press one of the function keys according to the following table:
F1: Disk boot (Lisp)
F2: Floppy boot (doesn't work)
F3: Ethernet boot
F4: Alternate ether boot
F5: Diagnostic Disk boot
F6: Diagnostic Floppy boot
F7: Diagnostic Ether boot
F8: Reserved
Getting into Othello:
To get into othello, boot the machine then do an Alternate Etherboot-6 by pressing F4 followed by the number 6 (not F6 and not the keypad's 6). Sometime later, the cursor will change to 0900 and Othello will come up.
Installing Lisp:
The physical volume is partitioned into at least 3 volumes for Lisp.
uCode: This is where the Lisp microcode lives (about 150 pages)
Lisp: Where the sysout lives.
LispFiles: For those who want to use the local file system.
Lisp booting on the daybreak is similar to Mesa, so the microcode is stored as "Pilot Microcode" and there is a dummy "germ" file which is there just so the microcode can load something for the germ.
To bring up a new lisp on a fresh volume, do the following:
> Initial Microcode Fetch
Drive Name: RD0
File Name: <LispCore>Dove>DiskInitialDove.db
> Germ Fetch
Logical Volume Name: uCode
File Name: <LispCore>Dove>Dummy.Germ
> Lisp Microcode Fetch
Logical Volume Name: uCode
File Name: <LispCore>Dove>LispDove.db
Finally, fetching the Lisp sysout is more or less normal:
> Lisp Sysout Fetch
Logical Volume Name: Lisp
File Name: <LispCore>Next>Full.sysout
Shall I expand this lisp to fill the volume? Yes
Shall I make this the default? Yes
To boot Lisp:
Press the reset button and then press F1
Lisp caveats:
If you need the local file system, do:
(DEFINEQ (MACHINETYPE ()(QUOTE DOVE)))
then DIR {DSK} or (CREATEDSKDIRECTORY 'LISPFILES)
MACHINETYPE will return DOVE later, but the file system's eventfn crashes on daybreaks and I'm afraid to touch the file system code to disable it any other way.
LOGOUT doesn't work right. If you want to save work and resume it later, do a SAVEVM. However, if you want to resume a frozen sysout, it must be expanded and the file system must be disabled (redefine MACHINETYPE to return DAYBREAK).
If the ethernet seems to go away, use (RESTART.ETHER) to start it up again.
Lots of programs like LAFITE create their status windows off the screen.
I'm not sure what will happen if you SYSOUT from a daybreak and load into a DLion/dorado.
&<01>&<01>&MODERN
MODERN?1(DEFAULTFONT 1 (GACHA 10) (GACHA 8) (TERMINAL 8))
-m<00><00>
<00>EA =<00><-
%&:&1#)''2<00><00>LIZ ?<00>z<EFBFBD>