MZ is back!HEAD main

author: Mark Zbikowski 2024-04-25 21:24:10 +0100
committer: Microsoft Open Source 2024-04-25 22:32:27 +0000
commit: 2d04cacc5322951f187bb17e017c12920ac8ebe2 (patch)
tree: 80ee017efa878dfd5344b44249e6a241f2a7f6e2 /v4.0-ozzie/bin/DISK1
parent: Merge pull request #430 from jpbaltazar/typoptbr (diff)
download: ms-dos-main.tar.gz
ms-dos-main.tar.xz
ms-dos-main.zip
27 files changed, 489 insertions, 0 deletions
diff --git a/v4.0-ozzie/bin/DISK1/AUTOEXEC.BAT b/v4.0-ozzie/bin/DISK1/AUTOEXEC.BAT
new file mode 100644
index 0000000..7842e98
--- /dev/null
+++ b/v4.0-ozzie/bin/DISK1/AUTOEXEC.BAT
@@ -0,0 +1,5 @@
+date
+time
+prompt $p$g
+path a:\bin;a:\
+\ No newline at end of file
diff --git a/v4.0-ozzie/bin/DISK1/BIN/ARENA.EXE b/v4.0-ozzie/bin/DISK1/BIN/ARENA.EXE
new file mode 100644
index 0000000..0bf52f1
--- /dev/null
+++ b/v4.0-ozzie/bin/DISK1/BIN/ARENA.EXE
Binary files differ
diff --git a/v4.0-ozzie/bin/DISK1/BIN/BBSET.EXE b/v4.0-ozzie/bin/DISK1/BIN/BBSET.EXE
new file mode 100644
index 0000000..1414161
--- /dev/null
+++ b/v4.0-ozzie/bin/DISK1/BIN/BBSET.EXE
Binary files differ
diff --git a/v4.0-ozzie/bin/DISK1/BIN/CHKDSK.EXE b/v4.0-ozzie/bin/DISK1/BIN/CHKDSK.EXE
new file mode 100644
index 0000000..3a6dded
--- /dev/null
+++ b/v4.0-ozzie/bin/DISK1/BIN/CHKDSK.EXE
Binary files differ
diff --git a/v4.0-ozzie/bin/DISK1/BIN/COUNTDOW.EXE b/v4.0-ozzie/bin/DISK1/BIN/COUNTDOW.EXE
new file mode 100644
index 0000000..148ce1c
--- /dev/null
+++ b/v4.0-ozzie/bin/DISK1/BIN/COUNTDOW.EXE
Binary files differ
diff --git a/v4.0-ozzie/bin/DISK1/BIN/DEMO1.BAT b/v4.0-ozzie/bin/DISK1/BIN/DEMO1.BAT
new file mode 100644
index 0000000..c4f8563
--- /dev/null
+++ b/v4.0-ozzie/bin/DISK1/BIN/DEMO1.BAT
@@ -0,0 +1,3 @@
+cd bin
+pound 290 a:bbset.exe a:sm.exe
+\ No newline at end of file
diff --git a/v4.0-ozzie/bin/DISK1/BIN/DEMO2.BAT b/v4.0-ozzie/bin/DISK1/BIN/DEMO2.BAT
new file mode 100644
index 0000000..49fe3d6
--- /dev/null
+++ b/v4.0-ozzie/bin/DISK1/BIN/DEMO2.BAT
@@ -0,0 +1,4 @@
+c:
+cd \bin
+pound 800 bbset.exe sm.exe
+\ No newline at end of file
diff --git a/v4.0-ozzie/bin/DISK1/BIN/DEMO3.BAT b/v4.0-ozzie/bin/DISK1/BIN/DEMO3.BAT
new file mode 100644
index 0000000..eb99c7b
--- /dev/null
+++ b/v4.0-ozzie/bin/DISK1/BIN/DEMO3.BAT
@@ -0,0 +1,7 @@
+c:
+cd \bin
+cd a:\bin
+detach pound 800 bbset.exe sm.exe
+detach pound 290 a:bbset.exe a:sm.exe
+basica a:prime
+\ No newline at end of file
diff --git a/v4.0-ozzie/bin/DISK1/BIN/DETACH.EXE b/v4.0-ozzie/bin/DISK1/BIN/DETACH.EXE
new file mode 100644
index 0000000..dc75d46
--- /dev/null
+++ b/v4.0-ozzie/bin/DISK1/BIN/DETACH.EXE
Binary files differ
diff --git a/v4.0-ozzie/bin/DISK1/BIN/HE_DAEM.EXE b/v4.0-ozzie/bin/DISK1/BIN/HE_DAEM.EXE
new file mode 100644
index 0000000..3cf823b
--- /dev/null
+++ b/v4.0-ozzie/bin/DISK1/BIN/HE_DAEM.EXE
Binary files differ
diff --git a/v4.0-ozzie/bin/DISK1/BIN/KILL.EXE b/v4.0-ozzie/bin/DISK1/BIN/KILL.EXE
new file mode 100644
index 0000000..ef240b6
--- /dev/null
+++ b/v4.0-ozzie/bin/DISK1/BIN/KILL.EXE
Binary files differ
diff --git a/v4.0-ozzie/bin/DISK1/BIN/POUND.EXE b/v4.0-ozzie/bin/DISK1/BIN/POUND.EXE
new file mode 100644
index 0000000..1ed27f1
--- /dev/null
+++ b/v4.0-ozzie/bin/DISK1/BIN/POUND.EXE
Binary files differ
diff --git a/v4.0-ozzie/bin/DISK1/BIN/PRIME.BAS b/v4.0-ozzie/bin/DISK1/BIN/PRIME.BAS
new file mode 100644
index 0000000..a088c0c
--- /dev/null
+++ b/v4.0-ozzie/bin/DISK1/BIN/PRIME.BAS
Binary files differ
diff --git a/v4.0-ozzie/bin/DISK1/BIN/SLEEP.EXE b/v4.0-ozzie/bin/DISK1/BIN/SLEEP.EXE
new file mode 100644
index 0000000..fdeaa14
--- /dev/null
+++ b/v4.0-ozzie/bin/DISK1/BIN/SLEEP.EXE
Binary files differ
diff --git a/v4.0-ozzie/bin/DISK1/BIN/SM.EXE b/v4.0-ozzie/bin/DISK1/BIN/SM.EXE
new file mode 100644
index 0000000..15da78c
--- /dev/null
+++ b/v4.0-ozzie/bin/DISK1/BIN/SM.EXE
Binary files differ
diff --git a/v4.0-ozzie/bin/DISK1/BIN/TEXT.EXE b/v4.0-ozzie/bin/DISK1/BIN/TEXT.EXE
new file mode 100644
index 0000000..edcc27f
--- /dev/null
+++ b/v4.0-ozzie/bin/DISK1/BIN/TEXT.EXE
Binary files differ
diff --git a/v4.0-ozzie/bin/DISK1/COMMAND.COM b/v4.0-ozzie/bin/DISK1/COMMAND.COM
new file mode 100644
index 0000000..3546cbd
--- /dev/null
+++ b/v4.0-ozzie/bin/DISK1/COMMAND.COM
Binary files differ
diff --git a/v4.0-ozzie/bin/DISK1/COMMANDS.DOC b/v4.0-ozzie/bin/DISK1/COMMANDS.DOC
new file mode 100644
index 0000000..0fcfed7
--- /dev/null
+++ b/v4.0-ozzie/bin/DISK1/COMMANDS.DOC
@@ -0,0 +1,199 @@
+                                Multi-Tasking MS-DOS
+                               Beta Test Release 1.00
+                                   Command Guide
+            ARENA.EXE - Prints out arena assignments
+                 arena
+                      The system's  memory arena  is printed  out.   The
+                      number listed  under the owner field is the PID of
+                      the process which owns the memory.
+            BBSET.EXE - Set and report on behavior bits
+                 bbset [-o] [ {+|-}bitname ... ] fname ...
+                      BBSET sets or clears behavior bits in an .EXE file
+                      header.   Multi-Tasking MS-DOS  uses the  behavior
+                      bits   to   determine   the   level   of   special
+                      compatibility   support    needed   to   run   the
+                      application.
+                      BBSET will  set  (if  +bitname)  or  clear  (if  -
+                      bitname)  the   named  behavior  bit(s)  from  the
+                      specified files.   If  the -o switch is specified,
+                      BBSET writes  a report  on the  current setting of
+                      all the  defined behavior  bits  to  stdout  after
+                      making the requested changes.
+                      For a  list of  behavior  bits  that  BBSET  knows
+                      about, type BBSET without any arguments.
+            COUNTDOW.EXE - Count down a CPU loop
+                 countdown number
+                      Its argument  is a  number; it  counts the  number
+                      down to 0, at about a 1hz rate.     It  prints out
+                      the countdown.   Another  CPU  loop  program  like
+                      TEXT, but  this  one  terminates  when  the  count
+                      reaches 0
+            DETACH.EXE - Detaches a child process
+                 detach command [argument ...]
+                      The command  given is run as a background process.
+                      Detach prints  out the  Command Subgroup ID (CSID)
+                      which may  be used  as  an  argument  to  KILL  to
+                      terminate the process.
+     Multi-Tasking MS-DOS Command Guide - Page: 2
+            HE_DAEM.EXE - Hard error catcher
+                 detach he_daem
+                      Intercepts hard  errors, reports them and requests
+                      user action.   This  should always  be run  in the
+                      background for now.  Put the above command line in
+                      your AUTOEXEC.BAT  file if you're not going to use
+                      the Session Manager (SM).
+            KILL.EXE - send a signal to a process
+                 kill [-nn] [sig=nn] [disp=mm] pid ...
+                      Sends signal  nn with  disposition mm to processes
+                      mentioned in pid.  Defaults to SIGTERM and process
+                      tree disposition.
+            POUND.EXE - Exercise disk I/O system
+                 pound [t]count filea fileb
+                      Pound reads  sequencially through filea and fileb,
+                      reading 512  bytes at  a time  alternating between
+                      the files  on each  read.  When the end of file is
+                      read the  following read  for that  file begins at
+                      the  beginning  of  the  file.    If  a  count  is
+                      specified without  the preceeding  "t" then  pound
+                      reads 512  bytes, count  number of times from each
+                      file  before  the  program  terminates.    If  "t"
+                      preceeds the  count value  then the files are read
+                      for count  number of  seconds before  the  program
+                      terminates.
+            SLEEP.EXE - Sleep for a while
+                 sleep sec[.millisec]
+                      Sleep will  execute a  sleep system  call for  the
+                      number  of  seconds  and  milliseconds  specified.
+                      This might  be useful  in batch files to pause for
+                      an interval  as opposed  to  waiting  for  a  user
+                      response.
+            SM.EXE - Session manager
+                 sm
+                      Manages multiple  processes running  on  different
+                      screens.   Uses initialization  file SM.INI.  This
+     Multi-Tasking MS-DOS Command Guide - Page: 3
+                      program includes  the hard error catcher, so don't
+                      run HE_DAEM  if you're going to use this.  See the
+                      file SM.DOC for more information.
+            TEXT.EXE - Loop and print text
+                 text argument
+                      CPU loops  and prints  its argument  every  2  CPU
+                      seconds or so
+\ No newline at end of file
diff --git a/v4.0-ozzie/bin/DISK1/CONFIG.SYS b/v4.0-ozzie/bin/DISK1/CONFIG.SYS
new file mode 100644
index 0000000..3d6d514
--- /dev/null
+++ b/v4.0-ozzie/bin/DISK1/CONFIG.SYS
@@ -0,0 +1,3 @@
+buffers = 40
+files = 20
+break=on
diff --git a/v4.0-ozzie/bin/DISK1/DOS33/FDISK.COM b/v4.0-ozzie/bin/DISK1/DOS33/FDISK.COM
new file mode 100644
index 0000000..b4e3af1
--- /dev/null
+++ b/v4.0-ozzie/bin/DISK1/DOS33/FDISK.COM
Binary files differ
diff --git a/v4.0-ozzie/bin/DISK1/DOS33/FORMAT.COM b/v4.0-ozzie/bin/DISK1/DOS33/FORMAT.COM
new file mode 100644
index 0000000..306fc49
--- /dev/null
+++ b/v4.0-ozzie/bin/DISK1/DOS33/FORMAT.COM
Binary files differ
diff --git a/v4.0-ozzie/bin/DISK1/DOS33/SYS.COM b/v4.0-ozzie/bin/DISK1/DOS33/SYS.COM
new file mode 100644
index 0000000..d26e982
--- /dev/null
+++ b/v4.0-ozzie/bin/DISK1/DOS33/SYS.COM
Binary files differ
diff --git a/v4.0-ozzie/bin/DISK1/IBMBIO.COM b/v4.0-ozzie/bin/DISK1/IBMBIO.COM
new file mode 100644
index 0000000..280a2ef
--- /dev/null
+++ b/v4.0-ozzie/bin/DISK1/IBMBIO.COM
Binary files differ
diff --git a/v4.0-ozzie/bin/DISK1/IBMDOS.COM b/v4.0-ozzie/bin/DISK1/IBMDOS.COM
new file mode 100644
index 0000000..a859665
--- /dev/null
+++ b/v4.0-ozzie/bin/DISK1/IBMDOS.COM
Binary files differ
diff --git a/v4.0-ozzie/bin/DISK1/README b/v4.0-ozzie/bin/DISK1/README
new file mode 100644
index 0000000..4163d4f
--- /dev/null
+++ b/v4.0-ozzie/bin/DISK1/README
@@ -0,0 +1,67 @@
+                                Multi-Taking MS-DOS
+                               Beta Test Release 1.00
+                                   Release Notes
+                 Enclosed you  will find  Microsoft's first beta release
+            of Multi-tasking  MS-DOS.  This version is based upon MS-DOS
+            Version 2  sources, we  will be  reimplementing  the  multi-
+            tasking enhancements on top of Version 3 sources shortly.
+                 Although we  have distributed  a bootable  disk for the
+            IBM PC,  this package  can be adapted to any MS-DOS machine.
+            Those manufacturers  who are  designing IBM compatible ROMs,
+            would be  wise to keep multi-tasking in mind.  Specifically,
+            this IBM  PC implementation  has had  to hook out the entire
+            disk (both  floppy and  hard disk) ROM code because after he
+            IBM code  set's up  the DMA  transfer it simply loops in ROM
+            waiting for the interrupt to occur (routine WAIT_INT).
+            Problems you may wish to avoid within future ROMs are:
+                 1)   loading ES  with the  physical video  RAM location
+                      (label M3)
+                 2)   Looping in ROM on Cntrl-NumLock (label K40)
+                 3)   No  way  to  add  special  detecting  special  key
+                      strokes which  a jump  out into  RAM after reading
+                      the keystroke at KB_INT would avoid
+                 4)   Not being  able to hook the loading of DS to point
+                      to DATA (EQU 40H) in numerous routines.
+            Other than  these deficiencies the ROM code developed should
+            be very usable.
+                 By implementing the above suggestions, the size of your
+            BIOS can  be reduced  since it  will  not  be  necessary  to
+            duplicate functionality in RAM.
+                 More  detailed  specifications  of  the  device  driver
+            formats will  be forth  coming.  For the time being you will
+            have to  make use  of the sample source code for the IBM PC.
+            If you  have further  questions please contact Microsoft OEM
+            customer support through Technical Assist Requests (TAR).
+               * * *  WARNING  * * *  WARNING  * * *  WARNING  * * *
+                 Each copy  of this  software distribution has been
+                 individually serialized  to facilitate  tracing of
+                 unauthorized duplication.
+               * * *  WARNING  * * *  WARNING  * * *  WARNING  * * *
+\ No newline at end of file
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 @@
+                                Multi-Tasking MS-DOS
+                               Beta Test Release 1.00
+                                  Session Manager
+                                    User's Guide
+            Introduction
+                 The  Session  Manager(SM)    for  Multi-Tasking  MS-DOS
+            allows you  to run up to six programs at one time and switch
+            between them  with a  couple of  keystrokes.  Each program's
+            screen is  preserved so  that it  can be  restored when  you
+            switch back  to it.  SM also contains the system-wide, Int24
+            Handler.
+            Initialization
+                 The first  thing SM does when it is started is look for
+            any program  initialization information  you may  have.   SM
+            looks for  the initialization  information in  a file  named
+            SM.INI in  the current  directory.  Although recommended, no
+            initialization information is needed.
+            There are two types of initialization lines:
+                 1)   define <program key> <program name> [program args]
+                      <working directory>
+                 2)   start  <program key>
+                 "program key"  - a printable ascii character, a control
+                           character (^A thru ^^), or a function key (F1
+                           - F10).
+                 "working directory"  - a well formed path; i.e., begins
+                           with drive letter (d:\).
+                 Each define  line will  associate a key with a program.
+            If there  is more  than one  define line using the same key,
+            only the information in the last one is used.
+                 A start  line is  optional.  If one exists, the program
+            associated with  the key on the start line is run as soon as
+            SM finishes  initializing.   If more  than one start line is
+            given, the last one is used.
+            This is what a sample initialization file might look like:
+                      define f1 a:\command.com c:\bin\src
+                      define ^z z.exe foo.c a:\foo\bar
+                      start f1
+            Running the Session Manager
+                 To run  Session Manager,  just type  SM.   It does  not
+            require any  arguments.   If there  was a  start line in the
+     Session Manager User's Guide - Page: 2
+            initialization file,  the program  associated with the start
+            key will be run.  Otherwise, the SM screen will be displayed
+            and you will be prompted for input.
+                 The SM  screen contains  a chart  that  describes  each
+            defined  program's   key,  status,  arguments,  and  working
+            directory.  There are 3 types of program status:
+                      1)   New - the program has never been run.
+                      2)   Active - the program has been started.
+                      3)   Dead - the program has terminated.
+                 The input  choices at  this point  are to either type a
+            program key  or hit  the <ESC> button to enter command mode.
+            If you  hit a  program key,  the screen associated with that
+            program   will   be   displayed   and   the   program   will
+            start/continue executing.   If  this is  the first  time the
+            program has  been run,  a chdir  to  the  program's  working
+            directory is  made before it is started.  If SM cannot start
+            the program you desired, the SM screen will reappear.
+                 If the  program you  chose to  run has died, its screen
+            will still  be displayed  so that  you can check its output.
+            That is  all you  can do  while in  a dead  programs  screen
+            except switch back to SM.
+                 To  switch  back  to  SM,  hit  Alt-F10.    Alt-F10  is
+            currently the  program key  for SM and will be recognized no
+            matter what  other programs  are running.   This is the only
+            program key  that works  this way.   All  of the others will
+            only be  recognized if  SM is  running and  the SM screen is
+            being displayed.
+                 Whenever any  of SM's  children die,  their  status  is
+            changed to  dead.   You will  see the status change the next
+            time the  SM screen  is displayed.  If the program using the
+            current screen dies, you will go back into SM.
+            Command Mode
+            When you  enter SM's  command mode the prompt "SM command or
+            HELP>" is displayed.  The valid SM commands are:
+                 1)   INIT <program key>
+                      Initialize the program associated with key so that
+                      it can  be run  again.   The program's  status  is
+                      changed to  "New" and  its screen memory is freed.
+                      If the   program is active, it is killed before it
+                      is initialized.
+                 2)   DEFINE <program key> <program name> [program args]
+                      <working directory>
+                      Define and  run a  new program  using the supplied
+                      information.   If the  key was previously defined,
+                      redefine it.
+     Session Manager User's Guide - Page: 3
+                 3)   RUN <program key>
+                      Run the program associated with key.
+                 4)   RESTART <program key>
+                      Restart the  program associated  with key.    This
+                      like issuing an INIT and a RUN command.
+                 5)   KILL <program key>
+                      Kill the  program associated with key.  Its status
+                      is changed to dead.
+                 6) HELP
+                      Display a help screen.
+                 7)   EXIT
+                      Kill all of SM's children and exit SM.
+                 In all  of the  above commands,  "key" is the printable
+            ascii representation of a programs key.  If a command fails,
+            you will either be asked to enter a new command or placed in
+            SM's top level.
+            Session Manager's Int24 Handler
+                 Whenever an Int24 occurs, SM's Int24 handler is called.
+            No matter  what program  is using  the screen  and no matter
+            which program  caused the error, SM's Int24 screen is always
+            displayed.  This screen will contain information on the type
+            of Int24  that happened, and the name and pid of the program
+            that caused the error.  You will then be prompted for one of
+            the valid  actions for this type of error.  After the action
+            typed in  has been taken, you are returned to the screen you
+            were using before the Int24.
+\ No newline at end of file
diff --git a/v4.0-ozzie/bin/DISK1/SM.INI b/v4.0-ozzie/bin/DISK1/SM.INI
new file mode 100644
index 0000000..bf7dfc8
--- /dev/null
+++ b/v4.0-ozzie/bin/DISK1/SM.INI
@@ -0,0 +1,2 @@
+define F7 a:\command.com a:\
+define F8 a:\command.com c:\
author	Mark Zbikowski	2024-04-25 21:24:10 +0100
committer	Microsoft Open Source	2024-04-25 22:32:27 +0000
commit	2d04cacc5322951f187bb17e017c12920ac8ebe2 (patch)
tree	80ee017efa878dfd5344b44249e6a241f2a7f6e2 /v4.0-ozzie/bin/DISK1
parent	Merge pull request #430 from jpbaltazar/typoptbr (diff)
download	ms-dos-main.tar.gz ms-dos-main.tar.xz ms-dos-main.zip

diff --git a/v4.0-ozzie/bin/DISK1/AUTOEXEC.BAT b/v4.0-ozzie/bin/DISK1/AUTOEXEC.BAT new file mode 100644 index 0000000..7842e98 --- /dev/null +++ b/v4.0-ozzie/bin/DISK1/AUTOEXEC.BAT
@@ -0,0 +1,5 @@
	1	date
	2	time
	3	prompt $p$g
	4	path a:\bin;a:\
	5	\ No newline at end of file


diff --git a/v4.0-ozzie/bin/DISK1/BIN/ARENA.EXE b/v4.0-ozzie/bin/DISK1/BIN/ARENA.EXE new file mode 100644 index 0000000..0bf52f1 --- /dev/null +++ b/v4.0-ozzie/bin/DISK1/BIN/ARENA.EXE
Binary files differ


diff --git a/v4.0-ozzie/bin/DISK1/BIN/BBSET.EXE b/v4.0-ozzie/bin/DISK1/BIN/BBSET.EXE new file mode 100644 index 0000000..1414161 --- /dev/null +++ b/v4.0-ozzie/bin/DISK1/BIN/BBSET.EXE
Binary files differ


diff --git a/v4.0-ozzie/bin/DISK1/BIN/CHKDSK.EXE b/v4.0-ozzie/bin/DISK1/BIN/CHKDSK.EXE new file mode 100644 index 0000000..3a6dded --- /dev/null +++ b/v4.0-ozzie/bin/DISK1/BIN/CHKDSK.EXE
Binary files differ


diff --git a/v4.0-ozzie/bin/DISK1/BIN/COUNTDOW.EXE b/v4.0-ozzie/bin/DISK1/BIN/COUNTDOW.EXE new file mode 100644 index 0000000..148ce1c --- /dev/null +++ b/v4.0-ozzie/bin/DISK1/BIN/COUNTDOW.EXE
Binary files differ


diff --git a/v4.0-ozzie/bin/DISK1/BIN/DEMO1.BAT b/v4.0-ozzie/bin/DISK1/BIN/DEMO1.BAT new file mode 100644 index 0000000..c4f8563 --- /dev/null +++ b/v4.0-ozzie/bin/DISK1/BIN/DEMO1.BAT
@@ -0,0 +1,3 @@
	1	cd bin
	2	pound 290 a:bbset.exe a:sm.exe
	3	\ No newline at end of file


diff --git a/v4.0-ozzie/bin/DISK1/BIN/DEMO2.BAT b/v4.0-ozzie/bin/DISK1/BIN/DEMO2.BAT new file mode 100644 index 0000000..49fe3d6 --- /dev/null +++ b/v4.0-ozzie/bin/DISK1/BIN/DEMO2.BAT
@@ -0,0 +1,4 @@
	1	c:
	2	cd \bin
	3	pound 800 bbset.exe sm.exe
	4	\ No newline at end of file


diff --git a/v4.0-ozzie/bin/DISK1/BIN/DEMO3.BAT b/v4.0-ozzie/bin/DISK1/BIN/DEMO3.BAT new file mode 100644 index 0000000..eb99c7b --- /dev/null +++ b/v4.0-ozzie/bin/DISK1/BIN/DEMO3.BAT
@@ -0,0 +1,7 @@
	1	c:
	2	cd \bin
	3	cd a:\bin
	4	detach pound 800 bbset.exe sm.exe
	5	detach pound 290 a:bbset.exe a:sm.exe
	6	basica a:prime
	7	\ No newline at end of file


diff --git a/v4.0-ozzie/bin/DISK1/BIN/DETACH.EXE b/v4.0-ozzie/bin/DISK1/BIN/DETACH.EXE new file mode 100644 index 0000000..dc75d46 --- /dev/null +++ b/v4.0-ozzie/bin/DISK1/BIN/DETACH.EXE
Binary files differ


diff --git a/v4.0-ozzie/bin/DISK1/BIN/HE_DAEM.EXE b/v4.0-ozzie/bin/DISK1/BIN/HE_DAEM.EXE new file mode 100644 index 0000000..3cf823b --- /dev/null +++ b/v4.0-ozzie/bin/DISK1/BIN/HE_DAEM.EXE
Binary files differ


diff --git a/v4.0-ozzie/bin/DISK1/BIN/KILL.EXE b/v4.0-ozzie/bin/DISK1/BIN/KILL.EXE new file mode 100644 index 0000000..ef240b6 --- /dev/null +++ b/v4.0-ozzie/bin/DISK1/BIN/KILL.EXE
Binary files differ


diff --git a/v4.0-ozzie/bin/DISK1/BIN/POUND.EXE b/v4.0-ozzie/bin/DISK1/BIN/POUND.EXE new file mode 100644 index 0000000..1ed27f1 --- /dev/null +++ b/v4.0-ozzie/bin/DISK1/BIN/POUND.EXE
Binary files differ


diff --git a/v4.0-ozzie/bin/DISK1/BIN/PRIME.BAS b/v4.0-ozzie/bin/DISK1/BIN/PRIME.BAS new file mode 100644 index 0000000..a088c0c --- /dev/null +++ b/v4.0-ozzie/bin/DISK1/BIN/PRIME.BAS
Binary files differ


diff --git a/v4.0-ozzie/bin/DISK1/BIN/SLEEP.EXE b/v4.0-ozzie/bin/DISK1/BIN/SLEEP.EXE new file mode 100644 index 0000000..fdeaa14 --- /dev/null +++ b/v4.0-ozzie/bin/DISK1/BIN/SLEEP.EXE
Binary files differ


diff --git a/v4.0-ozzie/bin/DISK1/BIN/SM.EXE b/v4.0-ozzie/bin/DISK1/BIN/SM.EXE new file mode 100644 index 0000000..15da78c --- /dev/null +++ b/v4.0-ozzie/bin/DISK1/BIN/SM.EXE
Binary files differ


diff --git a/v4.0-ozzie/bin/DISK1/BIN/TEXT.EXE b/v4.0-ozzie/bin/DISK1/BIN/TEXT.EXE new file mode 100644 index 0000000..edcc27f --- /dev/null +++ b/v4.0-ozzie/bin/DISK1/BIN/TEXT.EXE
Binary files differ


diff --git a/v4.0-ozzie/bin/DISK1/COMMAND.COM b/v4.0-ozzie/bin/DISK1/COMMAND.COM new file mode 100644 index 0000000..3546cbd --- /dev/null +++ b/v4.0-ozzie/bin/DISK1/COMMAND.COM
Binary files differ


diff --git a/v4.0-ozzie/bin/DISK1/COMMANDS.DOC b/v4.0-ozzie/bin/DISK1/COMMANDS.DOC new file mode 100644 index 0000000..0fcfed7 --- /dev/null +++ b/v4.0-ozzie/bin/DISK1/COMMANDS.DOC
@@ -0,0 +1,199 @@
	1
	2
	3
	4
	5
	6
	7	Multi-Tasking MS-DOS
	8	Beta Test Release 1.00
	9
	10	Command Guide
	11
	12
	13	ARENA.EXE - Prints out arena assignments
	14
	15	arena
	16
	17	The system's memory arena is printed out. The
	18	number listed under the owner field is the PID of
	19	the process which owns the memory.
	20
	21
	22	BBSET.EXE - Set and report on behavior bits
	23
	24	bbset [-o] [ {+\|-}bitname ... ] fname ...
	25
	26	BBSET sets or clears behavior bits in an .EXE file
	27	header. Multi-Tasking MS-DOS uses the behavior
	28	bits to determine the level of special
	29	compatibility support needed to run the
	30	application.
	31
	32	BBSET will set (if +bitname) or clear (if -
	33	bitname) the named behavior bit(s) from the
	34	specified files. If the -o switch is specified,
	35	BBSET writes a report on the current setting of
	36	all the defined behavior bits to stdout after
	37	making the requested changes.
	38
	39	For a list of behavior bits that BBSET knows
	40	about, type BBSET without any arguments.
	41
	42
	43	COUNTDOW.EXE - Count down a CPU loop
	44
	45	countdown number
	46
	47	Its argument is a number; it counts the number
	48	down to 0, at about a 1hz rate. It prints out
	49	the countdown. Another CPU loop program like
	50	TEXT, but this one terminates when the count
	51	reaches 0
	52
	53
	54	DETACH.EXE - Detaches a child process
	55
	56	detach command [argument ...]
	57
	58	The command given is run as a background process.
	59	Detach prints out the Command Subgroup ID (CSID)
	60	which may be used as an argument to KILL to
	61	terminate the process.
	62
	63
	64
	65
	66
	67
	68
	69
	70
	71	Multi-Tasking MS-DOS Command Guide - Page: 2
	72
	73	HE_DAEM.EXE - Hard error catcher
	74
	75	detach he_daem
	76
	77	Intercepts hard errors, reports them and requests
	78	user action. This should always be run in the
	79	background for now. Put the above command line in
	80	your AUTOEXEC.BAT file if you're not going to use
	81	the Session Manager (SM).
	82
	83
	84	KILL.EXE - send a signal to a process
	85
	86	kill [-nn] [sig=nn] [disp=mm] pid ...
	87
	88	Sends signal nn with disposition mm to processes
	89	mentioned in pid. Defaults to SIGTERM and process
	90	tree disposition.
	91
	92
	93	POUND.EXE - Exercise disk I/O system
	94
	95	pound [t]count filea fileb
	96
	97	Pound reads sequencially through filea and fileb,
	98	reading 512 bytes at a time alternating between
	99	the files on each read. When the end of file is
	100	read the following read for that file begins at
	101	the beginning of the file. If a count is
	102	specified without the preceeding "t" then pound
	103	reads 512 bytes, count number of times from each
	104	file before the program terminates. If "t"
	105	preceeds the count value then the files are read
	106	for count number of seconds before the program
	107	terminates.
	108
	109
	110	SLEEP.EXE - Sleep for a while
	111
	112	sleep sec[.millisec]
	113
	114	Sleep will execute a sleep system call for the
	115	number of seconds and milliseconds specified.
	116	This might be useful in batch files to pause for
	117	an interval as opposed to waiting for a user
	118	response.
	119
	120
	121	SM.EXE - Session manager
	122
	123	sm
	124
	125	Manages multiple processes running on different
	126	screens. Uses initialization file SM.INI. This
	127
	128
	129
	130
	131
	132
	133
	134
	135
	136
	137	Multi-Tasking MS-DOS Command Guide - Page: 3
	138
	139	program includes the hard error catcher, so don't
	140	run HE_DAEM if you're going to use this. See the
	141	file SM.DOC for more information.
	142
	143
	144	TEXT.EXE - Loop and print text
	145
	146	text argument
	147
	148	CPU loops and prints its argument every 2 CPU
	149	seconds or so
	150
	151
	152
	153
	154
	155
	156
	157
	158
	159
	160
	161
	162
	163
	164
	165
	166
	167
	168
	169
	170
	171
	172
	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


diff --git a/v4.0-ozzie/bin/DISK1/CONFIG.SYS b/v4.0-ozzie/bin/DISK1/CONFIG.SYS new file mode 100644 index 0000000..3d6d514 --- /dev/null +++ b/v4.0-ozzie/bin/DISK1/CONFIG.SYS
@@ -0,0 +1,3 @@
	1	buffers = 40
	2	files = 20
	3	break=on


diff --git a/v4.0-ozzie/bin/DISK1/DOS33/FDISK.COM b/v4.0-ozzie/bin/DISK1/DOS33/FDISK.COM new file mode 100644 index 0000000..b4e3af1 --- /dev/null +++ b/v4.0-ozzie/bin/DISK1/DOS33/FDISK.COM
Binary files differ


diff --git a/v4.0-ozzie/bin/DISK1/DOS33/FORMAT.COM b/v4.0-ozzie/bin/DISK1/DOS33/FORMAT.COM new file mode 100644 index 0000000..306fc49 --- /dev/null +++ b/v4.0-ozzie/bin/DISK1/DOS33/FORMAT.COM
Binary files differ


diff --git a/v4.0-ozzie/bin/DISK1/DOS33/SYS.COM b/v4.0-ozzie/bin/DISK1/DOS33/SYS.COM new file mode 100644 index 0000000..d26e982 --- /dev/null +++ b/v4.0-ozzie/bin/DISK1/DOS33/SYS.COM
Binary files differ


diff --git a/v4.0-ozzie/bin/DISK1/IBMBIO.COM b/v4.0-ozzie/bin/DISK1/IBMBIO.COM new file mode 100644 index 0000000..280a2ef --- /dev/null +++ b/v4.0-ozzie/bin/DISK1/IBMBIO.COM
Binary files differ


diff --git a/v4.0-ozzie/bin/DISK1/IBMDOS.COM b/v4.0-ozzie/bin/DISK1/IBMDOS.COM new file mode 100644 index 0000000..a859665 --- /dev/null +++ b/v4.0-ozzie/bin/DISK1/IBMDOS.COM
Binary files differ


diff --git a/v4.0-ozzie/bin/DISK1/README b/v4.0-ozzie/bin/DISK1/README new file mode 100644 index 0000000..4163d4f --- /dev/null +++ b/v4.0-ozzie/bin/DISK1/README
@@ -0,0 +1,67 @@
	1
	2
	3
	4
	5
	6
	7	Multi-Taking MS-DOS
	8	Beta Test Release 1.00
	9
	10	Release Notes
	11
	12
	13	Enclosed you will find Microsoft's first beta release
	14	of Multi-tasking MS-DOS. This version is based upon MS-DOS
	15	Version 2 sources, we will be reimplementing the multi-
	16	tasking enhancements on top of Version 3 sources shortly.
	17
	18	Although we have distributed a bootable disk for the
	19	IBM PC, this package can be adapted to any MS-DOS machine.
	20	Those manufacturers who are designing IBM compatible ROMs,
	21	would be wise to keep multi-tasking in mind. Specifically,
	22	this IBM PC implementation has had to hook out the entire
	23	disk (both floppy and hard disk) ROM code because after he
	24	IBM code set's up the DMA transfer it simply loops in ROM
	25	waiting for the interrupt to occur (routine WAIT_INT).
	26
	27	Problems you may wish to avoid within future ROMs are:
	28	1) loading ES with the physical video RAM location
	29	(label M3)
	30	2) Looping in ROM on Cntrl-NumLock (label K40)
	31	3) No way to add special detecting special key
	32	strokes which a jump out into RAM after reading
	33	the keystroke at KB_INT would avoid
	34	4) Not being able to hook the loading of DS to point
	35	to DATA (EQU 40H) in numerous routines.
	36	Other than these deficiencies the ROM code developed should
	37	be very usable.
	38
	39	By implementing the above suggestions, the size of your
	40	BIOS can be reduced since it will not be necessary to
	41	duplicate functionality in RAM.
	42
	43	More detailed specifications of the device driver
	44	formats will be forth coming. For the time being you will
	45	have to make use of the sample source code for the IBM PC.
	46	If you have further questions please contact Microsoft OEM
	47	customer support through Technical Assist Requests (TAR).
	48
	49
	50	* * * WARNING * * * WARNING * * * WARNING * * *
	51
	52	Each copy of this software distribution has been
	53	individually serialized to facilitate tracing of
	54	unauthorized duplication.
	55
	56	* * * WARNING * * * WARNING * * * WARNING * * *
	57
	58
	59
	60
	61
	62
	63
	64
	65
	66
	67	\ No newline at end of file


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


diff --git a/v4.0-ozzie/bin/DISK1/SM.INI b/v4.0-ozzie/bin/DISK1/SM.INI new file mode 100644 index 0000000..bf7dfc8 --- /dev/null +++ b/v4.0-ozzie/bin/DISK1/SM.INI
@@ -0,0 +1,2 @@
	1	define F7 a:\command.com a:\
	2	define F8 a:\command.com c:\