readme.2nd

MMURTL(tm) Computer Operating System Ver x0.8, source code.

ReadMe.2nd

This file lists problems, bugs, changes,
differences, inadequacies, and hassles,
dealing specifically with MMURTL
version x0.8.
It may even have a suggestion or two
concerning the cause and resolution.

   **********  WARNINGS **********

DON'T run MMURTL if you are using data compression
on your hard disks.  "MMURTL don't play that."

DON'T attempt to access disk partitions other than
MS-DOS FAT compatible (e.g. FAT16, FAT12), even if
they show up on MMURTL Boot up.

This version was not tested extensively.
Backup your disk if you intend to experiment
with the file system (writing files).

   **********  WHATS NOT DONE **********
   (not an all inclusive list for sure)

Loader:
  DLLs are not done in this version.
  Device Drivers can not be loaded dyamically.

File System:
  Remove and Create Directory
  Redirection (SysIn and SysOut)
  Reset of Floppy drives on error

Kernel:
  Preemptive Prioritized task switching
  Request Forwarding

Job Management:
  DeInstallation of System Services
  Setting Job Names

Monitor:
  Job Display

Debugger:
  Set & Clear breakpoints

Comms - Serial & Parallel
  The serial comms driver in this
  version is not really too
  efficient (we've run it at 38,400
  baud and it works...)
  The parallel driver was not done for
  this version at all... we tried
  a retrofit, but there was no time.


CM32 (Compiler):

1) Argument passing to "main" in stdlib in the
DOS version of CM32 is not done.  Whe are now
concentrating on the MMURTL version of instead.

2) Structures don't work correctly as local
vaiables.

DASM (Assembler):

Library Search (.SEARCH command) in DASM isn't
functioning in the DOS version.  As you will
see in the sample code, you simply include
the .ASM files that match the header you have
included.

CLI.run:
  No pattern matching is done in the CLI for
  wildcards. The copy command is not implemented
  in this CLI.

  External command searching was also not
  implemented (use "RUN filename" instead).

There are no "real" applications.
We're working on the OS and we only have
indepth test programs completed.  The CLI
and the little editor included are simple
qickies (treat them as such).
They were the first things ever done when
MMURTL was completed to the point of being
able to load something...


   **********  BUGS & PROBLEMS **********

1) PROBLEMS LOADING AND RUNNING THE DOS MMURTL IMAGE

If you are running the MS-DOS EMM386 device driver
this may prevent MMURTL from loading.  The symptom
is that your machine simply reboots when you run MMURTL.
Comment out EMM386, reboot DOS, and run MMURTL again.


2) STATISTICS DON'T SHOW CORRECT AMOUNT OF MEMORY

MMURTL depends on the address line A20 being active
so all memory can be accessed. This is controlled via
the keyboard serial controller (8042) as documented in the
IBM-PC AT technical reference manual. Most ISA PCs support
this method but a few don't.  If you only show 1 Meg of
RAM and you have more, this is no doubt the culprit.
Some support chip sets (such as C&T) provide
an alternate method which you can investigate.
(We're investigating right now)

3)  I CAN'T SEE MMURTL ON MY SCREEN

If you hear two beeps (a short low tone, then a
longer high tone) MMURTL has initalized at least part
of the way.  If you can't see anything on your screen
it means that your video text base address is not
where MMURTL expects it.  You can change this in the
code (VGATextBase in VIDDATA.INC) if you know where
yours is located.  This is a 32 bit linear address.
In fact, I guess you can rewrite the entire video code
if you need to... (but wait for V1.0 if your that
serious)

4) FILE SYSTEM ERRORS ON BOOT UP

This version of MMURTL is a little picky about
timing on some IDE drives.  This may cause problems
for a small number of users.  This version was
only tested on about 14 major brands and clones
(IDE based).

5)  MS-DOS OUT OF MEMORY WHILE BUILDING MMURTL 0.8X

You will need just above 600K to build MMURTL
version 0.8x.  TASM requires this.  Start hacking
at your DOS Config.sys and Autoexec.bat file...

6) FLOPPY DRIVES ALWAYS RETURN ERRORS

We weren't really concentrating on floppies
at that time (0.8x).  The FDD driver works,
we just didn't have code in the file system to
reset them on change-line or error indications.
If there's a floppy in the drive when you boot
it will be recognized.  Only High Density
3.5 and 5.25 work (1.44 * 1.2M).
We have the additional code in the FDD driver
to recognize the lower density, but we didn't do
anything with it.

--------------- End of file ------------