MICEpack/SLD 1.1

Host System Requirements:

The following host computer requirements and recommendations apply:
 1. An Intel 386DX, Intel 486, or Intel Pentium(tm)-based PC or 100%
    compatible system.
 2. At least 6 Megabytes of RAM.
 3. 4.4 Megabytes of available disk space.
 4. VGA or Super VGA graphics card and color monitor (A graphics
    accelerator card will boost performance, and a monitor capable
    of at least 800x600 operation is highly recommended).
 5. Mouse.
 6. MS-PCE card for connection to emulator.
 7. MSDOS 3.3, 5.0, or 6.x.
 8. Windows 3.1 running in 386-enhanced mode.
 9. 4 Megabytes or greater swap file (permanent swap file recommended).
10. Minimum: Files=30  Buffers=30


MICEpack/SLD Configuration Guidelines:

  * Use a disk cache such as smartdrive for improved Windows performance.

  * Be sure you have a swap file of at least 4 Megabytes (a permanent
    swap file is recommended).

  * MICEpack/SLD requires a minimum of 5 Megabytes of free memory after
    Windows is loaded.  More memory is better, especially if you run
    other applications at the same time.  If memory is low, close other
    applications to regain memory.

  * While the emulator runs, status messages are sent from the chassis to
    the host PC.  If you are running a DOS shell at the same time, give it
    a low priority via the .PIF file settings, or stop the emulator.

  * One GP fault that showed up in MICEpack/SLD was traced to a
    faulty video device driver of the Diamond Stealth ISA 1M VRAM card
    (version 2.31) in 1024 X 768 mode.  The problem went away by
    reducing the resolution to 800 X 600.  Another problem exists with
    the Genoa 256-color small font driver.  The symptom is the load-progress
    indicator is not updated completely at the completion of a load.
    If you encounter a fault in a driver file (*.DRV), try installing a 
    more current device driver.

Known limitations in version 1.1:

  * Extremely long or looping include files can generate an "Out of Object
    Pointers" error message and MICEpack/SLD will exit. 

  * Modules with multiple code segments are not supported.

  * Floating point variables are not supported.
  
  * Variable inspection (double clicking on a variable in the source
    window) does not work in Mixed mode, only in Source mode. (9778)

  * Bitfield support is not working properly. (9891)

  * The shell command AddressOf does not support #module#staticVar lookup
    if #module is not the current execution context.  (9626,9896)

  * The Variable window does not display UNIONs correctly. (9909)

  * When the source window is displaying in assembly mode, the window
    elevator is pulled to the bottom, and the down arrow clicked, then
    the address jumps to a random location. (9945)

  * No warning is given if a source file is newer than the OMF. (9953)

Notes:

  * Supported toolchains

    MICEpack/SLD supports OMF86 file format.  Testing has confirmed, 
    however, that there are numerous interpretations of the OMF file 
    specifications.  MICEpack/SLD 1.1 has been tested with these toolchains:

      Microsoft C v7 & SSI Link&Locate-86, v7.2f
      Microsoft C v7 & PharLap Asm/LinkLoc v4.0

  * MICEpack/SLD does not currently support C++.
  
  * Initialization Script

    MICEpack/SLD can be set up the communication port and its port address
    in "Comm" and "Microtekparallel" sections of MP186.INI file.
    For example:
       [Comm]
       type=microtekparallel

       [MicrotekParallel]
       basePort=0x200
 
    MICEpack/SLD can be set up the emulated target CPU in "SystemInfo"
    section of MP186.INI file. For example:
       [SystemInfo]
       MICEpack=80C186XL

    MICEpack/SLD-186 supports 80C186/188 XL, 80C186/188 EA, 80C186/188 EB,
    and 80C186/188 EC.
 
    MICEpack/SLD can be set up to run an auto-initialization script.  The
    script sets up the emulator to your requirements each time you
    run MICEpack/SLD.  The product is shipped with an include file that
    describes how to do this.  The file is named "include.me".  To create
    your own script file, create a file with the commands you want for
    initialization.  BE SURE TO END EACH COMMAND WITH A SEMICOLON.
    Edit the MP186.INI file (in your windows directory), and change
    the "script=include.me" line, replacing "include.me" with your
    initialization file.  Be sure to include the full path, including
    drive letter if necessary.  For example:

           script=c:\mp186\reset.inc

    You can also run the same initialization file in the Shell window.
    For example:

           include "c:\mp186\reset.inc";

  * Shell command history

    You can access the Shell command history with Ctrl-uparrow
    and Ctrl-downarrow keys.


Diagnosing Fatal MICEpack/SLD Errors

  * GP Faults

    If you have received a GP fault, our ability to find and fix it is
    increased if you run the Dr. Watson recorder, which captures
    information at the point of the GP fault.  The Dr. Watson program
    is shipped with Windows and is located in your windows directory.

    To start Windows with Dr. Watson enabled, use the File Manager to
    drag and drop the drwatson.exe icon (in your windows directory) into
    the Windows StartUp Group.  Another way to do this is to add the path
    and filename to the load= line of your win.ini file.  Example:

          load=c:\windows\drwatson.exe

    After a GP fault, the drwatson.log file in your Windows directory
    holds the information.  Fax or e-mail this file, along with any other
    information that led up to the GP fault, to Microtek International.  

         Fax: 1-503-629-8460.         E-mail: csupport@microtekintl.com

  * PV.DMP

    Under some conditions, an error can occur which produces a message box
    indicating that information about a problem has been placed in the file
    pv.dmp in your MICEpack/SLD directory.  This file gets written over each
    time an error occurs, so we recommend that you rename the file, then
    fax or e-mail it to Microtek International.