forked from emutos/emutos
-
Notifications
You must be signed in to change notification settings - Fork 1
/
startup.txt
80 lines (63 loc) · 3.38 KB
/
startup.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
A few notes on the EmuTOS startup sequence
==========================================
The EmuTOS startup sequence is similar to that of Atari TOS. The
following keys affect startup:
Alt: set floppy A: as boot device instead of first disk partition
Esc: run an early console
Ctrl: start up as a 'bare' system:
do not use any Nova/ET4000 card present
do not run AUTO folder programs
do not load user-defined mouse cursors
do not load desk accessories
do not run an autorun program
do not load desktop icons
do not use the EMUDESK.INF file for desktop setup
Details
-------
Note: in the following, all files referenced must be in the root
directory of the boot device.
1. After some basic system initialisation, if a diagnostic cartridge
is present, it is run.
2. ST RAM is initialised, then the BIOS and the rest of the hardware
is initialised.
An optional cold boot delay (1-255 seconds) can be configured by the
user by changing a value in the extended OS header (OSXH) in the ROM
image. EmuTOS then waits the configured amount of time before
accessing any block devices (floppy disks, hard disks, etc.).
See doc/version.txt for details.
3. On ROMs other than 192K, the code checks for the presence of a
Nova/ET4000 video board. If detected, the video output is directed
to it (this may be skipped by pressing the Ctrl key during startup).
4. If a cartridge is present, any type 3 cartridge applications are
run (under Hatari, this is where GEMDOS emulation is set up).
5. On a cold boot only, the EmuTOS welcome screen is displayed.
While the screen is displayed, the keys Alt, Ctrl, and Esc may be
pressed to alter subsequent processing (see below).
6. If the user pressed the Alt key in step 4 above, the boot device
is set to the first floppy (drive A:). Otherwise it is set to
the first partition of the first device found. Devices are scanned
in the following sequence: IDE, SCSI, ACSI, SD/MMC.
7. If the user pressed the Esc key in step 4 above, the Emucon2 console
is displayed (on exit, the startup will continue as below).
8. All PRG programs in the AUTO folder are run, in directory sequence.
This is skipped if the Ctrl key was pressed in step 4 above.
9. The AES is started. If an EMUDESK.INF file is present, it is
checked for a video setting (a #E line). If a setting is specified,
and it differs from the current setting, the current display mode
is changed.
10. The AES is initialised. If an EMUCURS.RSC file is present, user-
defined mouse cursors are loaded from it. This is skipped if the
Ctrl key was pressed in step 4 above.
11. Desk accessories are loaded, if present. This is skipped if the
Ctrl key was pressed in step 4 above.
12. If an EMUDESK.INF file is present, it is checked for an autorun
program setting (a #Z line). If an autorun program exists, it is
run. This is skipped if the Ctrl key was pressed in step 4 above.
13. The desktop is started. If an EMUICON.RSC file is present, user
desktop icons are loaded from it. This is skipped if the Ctrl key
was pressed in step 4 above.
14. If an EMUDESK.INF file is present, it is used to set up the
desktop display. This is skipped if the Ctrl key was pressed in
step 4 above, and a default display is set up instead.
At this point, desktop initialisation is complete, and EmuDesk waits
for user input.