summaryrefslogtreecommitdiff
path: root/v4.0-ozzie/bin/DISK1/SM.DOC
diff options
context:
space:
mode:
Diffstat (limited to 'v4.0-ozzie/bin/DISK1/SM.DOC')
-rw-r--r--v4.0-ozzie/bin/DISK1/SM.DOC199
1 files changed, 199 insertions, 0 deletions
diff --git a/v4.0-ozzie/bin/DISK1/SM.DOC b/v4.0-ozzie/bin/DISK1/SM.DOC
new file mode 100644
index 0000000..ebbe220
--- /dev/null
+++ b/v4.0-ozzie/bin/DISK1/SM.DOC
@@ -0,0 +1,199 @@
1
2
3
4
5
6
7 Multi-Tasking MS-DOS
8 Beta Test Release 1.00
9
10 Session Manager
11 User's Guide
12
13
14 Introduction
15
16 The Session Manager(SM) for Multi-Tasking MS-DOS
17 allows you to run up to six programs at one time and switch
18 between them with a couple of keystrokes. Each program's
19 screen is preserved so that it can be restored when you
20 switch back to it. SM also contains the system-wide, Int24
21 Handler.
22
23
24 Initialization
25
26 The first thing SM does when it is started is look for
27 any program initialization information you may have. SM
28 looks for the initialization information in a file named
29 SM.INI in the current directory. Although recommended, no
30 initialization information is needed.
31
32 There are two types of initialization lines:
33 1) define <program key> <program name> [program args]
34 <working directory>
35 2) start <program key>
36
37 "program key" - a printable ascii character, a control
38 character (^A thru ^^), or a function key (F1
39 - F10).
40 "working directory" - a well formed path; i.e., begins
41 with drive letter (d:\).
42
43 Each define line will associate a key with a program.
44 If there is more than one define line using the same key,
45 only the information in the last one is used.
46
47 A start line is optional. If one exists, the program
48 associated with the key on the start line is run as soon as
49 SM finishes initializing. If more than one start line is
50 given, the last one is used.
51
52 This is what a sample initialization file might look like:
53
54 define f1 a:\command.com c:\bin\src
55 define ^z z.exe foo.c a:\foo\bar
56 start f1
57
58
59 Running the Session Manager
60
61 To run Session Manager, just type SM. It does not
62 require any arguments. If there was a start line in the
63
64
65
66
67
68
69
70
71 Session Manager User's Guide - Page: 2
72
73 initialization file, the program associated with the start
74 key will be run. Otherwise, the SM screen will be displayed
75 and you will be prompted for input.
76
77 The SM screen contains a chart that describes each
78 defined program's key, status, arguments, and working
79 directory. There are 3 types of program status:
80
81 1) New - the program has never been run.
82 2) Active - the program has been started.
83 3) Dead - the program has terminated.
84
85 The input choices at this point are to either type a
86 program key or hit the <ESC> button to enter command mode.
87 If you hit a program key, the screen associated with that
88 program will be displayed and the program will
89 start/continue executing. If this is the first time the
90 program has been run, a chdir to the program's working
91 directory is made before it is started. If SM cannot start
92 the program you desired, the SM screen will reappear.
93
94 If the program you chose to run has died, its screen
95 will still be displayed so that you can check its output.
96 That is all you can do while in a dead programs screen
97 except switch back to SM.
98
99 To switch back to SM, hit Alt-F10. Alt-F10 is
100 currently the program key for SM and will be recognized no
101 matter what other programs are running. This is the only
102 program key that works this way. All of the others will
103 only be recognized if SM is running and the SM screen is
104 being displayed.
105
106 Whenever any of SM's children die, their status is
107 changed to dead. You will see the status change the next
108 time the SM screen is displayed. If the program using the
109 current screen dies, you will go back into SM.
110
111
112 Command Mode
113
114 When you enter SM's command mode the prompt "SM command or
115 HELP>" is displayed. The valid SM commands are:
116
117 1) INIT <program key>
118 Initialize the program associated with key so that
119 it can be run again. The program's status is
120 changed to "New" and its screen memory is freed.
121 If the program is active, it is killed before it
122 is initialized.
123
124 2) DEFINE <program key> <program name> [program args]
125 <working directory>
126 Define and run a new program using the supplied
127 information. If the key was previously defined,
128 redefine it.
129
130
131
132
133
134
135
136
137 Session Manager User's Guide - Page: 3
138
139 3) RUN <program key>
140 Run the program associated with key.
141
142 4) RESTART <program key>
143 Restart the program associated with key. This
144 like issuing an INIT and a RUN command.
145
146 5) KILL <program key>
147 Kill the program associated with key. Its status
148 is changed to dead.
149
150 6) HELP
151 Display a help screen.
152
153 7) EXIT
154 Kill all of SM's children and exit SM.
155
156 In all of the above commands, "key" is the printable
157 ascii representation of a programs key. If a command fails,
158 you will either be asked to enter a new command or placed in
159 SM's top level.
160
161
162 Session Manager's Int24 Handler
163
164 Whenever an Int24 occurs, SM's Int24 handler is called.
165 No matter what program is using the screen and no matter
166 which program caused the error, SM's Int24 screen is always
167 displayed. This screen will contain information on the type
168 of Int24 that happened, and the name and pid of the program
169 that caused the error. You will then be prompted for one of
170 the valid actions for this type of error. After the action
171 typed in has been taken, you are returned to the screen you
172 were using before the Int24.
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199 \ No newline at end of file
HIC SVNT DRACONES