autocommit for file dated 1999-12-02 03:35:32

diff --git a/problems.txt b/problems.txt
new file mode 100644 (file)
index 0000000..954f56f
--- /dev/null
+++ b/problems.txt
@@ -0,0 +1,133 @@
+This file relates to version 1.0 of the MMURTL\r
+computer operating system that accompanies the\r
+book:\r
+\r
+   MMURTL-V1.0\r
+\r
+This discusses known problems trying to run MMURTL, as well\r
+as bugs, and portions of the code that are incomplete\r
+\r
+1) LOADING AND RUNNING MMURTL\r
+\r
+       If MMURTL will not run on your system, you may have to\r
+       remove EMM386 from your Autoexec.BAT or Config.sys file.\r
+       EMM386 doesn't take kindly to hostile memory take-overs.\r
+\r
+       If you receive an error during file system initialization or\r
+       hard disk device driver installation:\r
+\r
+    a) Your disk controller may not be supported.\r
+    MMURTL has some problems with some of the newer 32 bit\r
+    disk controllers that move data directly between the \r
+    drive and memory.\r
+    All ISA driven controllers seem to work fine (I have\r
+    tested more than 12 different ISA IDE controllers).\r
+    I have also tested many PCI based controllers and they\r
+    seem to work ok too.  I have no problems running MMURTL\r
+    on my 233 Mhz Pentium MMX with a PCI controller so it\r
+    can be done!  I have no idea what effect the UDMA\r
+    33 and 66 PCI controllers will have.\r
+\r
+    b) SCSI disks and other SCSI devices are not supported.\r
+    (no SCSI driver)\r
+\r
+    c) Your data may be compressed by MS-DOS or another product\r
+    such as Stacker. MMURTL does not support disk data compression.\r
+\r
+    d) If you are running OS/2 V2.x or Warp (V3.x or V4.x), \r
+    MMURTL doesn't recognize the multiboot partition correctly.\r
+    You can copy the MMSYS directory to a floppy and run it\r
+    from there to test it.\r
+\r
+2) WHAT'S NOT DONE??\r
+\r
+       FILESYSTEM:\r
+\r
+       a) The file system call to remove a directory is not completed\r
+       so I didn't include it. Use MS-DOS to get rid of directories if\r
+       needed.\r
+\r
+       DLLs:\r
+\r
+       a) DLLs are not supported. AND NEVER WILL BE - I hate them...\r
+\r
+       LOADING DEVICE DRIVERS:\r
+\r
+       a) Device drivers can't be loaded dynamically. If you need to add\r
+       a driver you will have to build it into the OS (sounds like Unix...)\r
+        That's actually        quite easy to do, so I didn't strain myself \r
+        getting it done.\r
+\r
+       DASM LIBARARY SEARCH FUNCTION\r
+\r
+       a) The search function (.SEARCH command) is not fully implimented.\r
+       The work around is quite easy, and really there is not much\r
+       library code to search through at this point in time.\r
+       Simply include the ASM modules in the ATF file. All of the sample\r
+       programs and the operating system are built this way right now.\r
+       They should provide you with good examples.\r
+\r
+       COMMAND LINE INTERPRETER\r
+\r
+       a) There is no wildcard feature in the file system or any\r
+       template matching code in a library. This means *.* has no\r
+       effect. The copy, rename, and delete functions all take single\r
+       filenames.\r
+\r
+3)  BUGS\r
+\r
+       OPERATING SYSTEM\r
+\r
+       a) On occasion, when a program is beating the filesystem to death\r
+       and you attempt to load and run another CLI, the system crashes.\r
+       It doesn't even make it into the debugger. It is apparently a\r
+       processor double fault. Still looking for this one....\r
+\r
+       b) The CTRL-ALT-DELETE function is a rather nasty way to shut down\r
+       an application. It was a late addition, but was necessary. On\r
+       occasion is causes some problems. The system still functions and\r
+       tasks appear to be running fine - but every once in a while when\r
+       you use it, you can't switch to the other applications. This IS\r
+       a problem I'm still looking for.\r
+\r
+       CM32 C Compiler\r
+\r
+       a) Occasionally when you have accidentally "nested" a function\r
+       (which is not allowed in C) the compiler goes into a loop...\r
+       It's churning away somehwere. I just haven't found out where\r
+       that is yet.\r
+\r
+4) An updated Filesystem is included for download but not incorporated\r
+ - you have to do it by replacing the file. I did not want to\r
+mess with the code so it folloows the book exactly. Otherwise I\r
+would have create a confusing mess!  \r
+\r
+This is STILL version 1.0. You WILL find many other problems.\r
+Let me know if you get the time. Send E-Mail to rburgess@aol.com.\r
+(Please, bugs only - and yes, the AOL email address is still mine\r
+after 6 years.)\r
+\r
+Quite obviously, neither myself nor the publisher has time to really\r
+support a product of this complexity. You're on your own. BUT at least\r
+you DO have the source code.\r
+\r
+Thanks, and I hope you get something out of all this!\r
+\r
+Richard Burgess\r
+Alexandria, VA.\r
+1995-1999\r
+\r
+P.S. Most of this text is 6 years old but still applies.\r
+HOWEVER, with a publisher like Sensory willing to keep a BBS\r
+up and running for user exchange and support - maybe MMURTL\r
+will take off like I wanted it to in the first place...\r
+I'm not sure how much time I'll have to help, but it is tempting\r
+and MMURTL really is a sweet OS.  I've never run it on a PII\r
+or PIII - let's hear it out there.... whoa... who's got the guts?\r
+But it does run on my IBM Aptiva 233Mhz MMX... Hmmm. \r
+Not bad for 5 years later. It does cough on the bigger disk\r
+quite often though.  \r
+\r
+\r
+\r
+\r