

                        Plug and Play Kit


This release of the Plug and Play Kit includes:

 - Plug and Play Configuration Manager

   This device driver provides other device drivers and 
   application programs access to Plug and Play configuration 
   information.  It also detects and configures any Plug and Play 
   Industry Standard Architecture (ISA) devices that were not 
   configured during your PC's power-on self test.

 - Plug and Play ISA Configuration Utility (ICU)

   This utility provides a way to assign system resources to 
   add-in cards before the card is installed in your PC.  This 
   avoids resource conflicts and keeps track of system resources 
   so that Plug and Play cards do not conflict with non-Plug and 
   Play cards.  A full description of ICU features is available 
   in the ISA Configuration Utility (ICU) on-line help file.

 - Configuration Assistance Utility

   For Plug and Play cards to operate in an ISA system without a 
   Plug and Play BIOS, the Configuration Assistance Utility, 
   CASSIST.EXE, is provided.  This utility determines your 
   system's resource allocation and initializes the ESCD.RF file.

 - Configuration Files

   Configuration files contain information about non-Plug and 
   Play add-in cards.  Over 260 files are provided.  The ICU uses 
   these files to automatically assign system resources.


Installation Notes
------------------

1) On systems with MS-DOS version 6.0 or later that use a 
   multipath CONFIG.SYS file, the MS-DOS installation procedure 
   might corrupt the CONFIG.SYS file by duplicating sections of 
   the file and corrupting the duplicate sections.  If you have 
   this type of CONFIG.SYS file, verify its integrity before 
   rebooting your system.  If you see this problem, perform the 
   following steps:

   a) Replace the CONFIG.SYS file with the backup file made by 
      the installation, CONFIG.BAK.  

   b) Edit the CONFIG.SYS file and add a line to load the CM 
      driver to the beginning of the file.  Here is an example 
      line that assumes the default installation:

      DEVICE=C:\PLUPGPLAY\DRIVERS\DOS\DWCFGMG.SYS

2) The installation assumes that C: is the boot drive of the 
   system.  For example, the procedure puts the ESCD.RF file into 
   C:\, and creates or modifies the CONFIG.SYS file in C:\.  

   On systems without the Plug and Play BIOS, if the boot drive 
   is not C:, but some other drive, you must move the ESCD.RF 
   file to the root directory of the boot drive.  Also, you must 
   add the line that loads the CM driver (DWCFGMG.SYS) to the 
   CONFIG.SYS file in the root directory of the boot drive. 

   Some utilities, for example, the Stacker disk compression 
   utility, can change the boot drive from C: to another drive.  
   Such drive changes are not always obvious.

3) If you have already installed one version (MS-DOS or Windows) 
   of this kit, install the other version in the same directory 
   as you installed the first version.  By default, both versions 
   of the installation use the same directory: C:\PLUGPLAY.  

   If you use a different directory, the system configuration 
   information displayed when you invoke the Windows ICU might 
   look different than that displayed when you invoke the MS-DOS 
   ICU.

4) If you have already installed the one version (MS-DOS or 
   Windows) of the kit, when the second installation procedure 
   asks if you want to replace an existing ESCD.RF file, answer 
   No.  If you answer Yes, you will lose any system configuration 
   changes you made with the first installed version of the ICU.  

   If you inadvertently answer Yes to this question, you can 
   recover the previous version of the ESCD.RF file by copying 
   the C:\ESCD.BAK file to C:\ESCD.RF.  This recovery is not 
   necessary if you made no system configuration changes with the 
   MS-DOS ICU.

                              NOTE
       The ESCD.RF file is not used on systems with the 
       Plug and Play BIOS.
	

MS-DOS Installations
--------------------

1) To install and run the Plug and Play Kit for MS-DOS, your 
   system must have a minimum of 488 KBytes of free conventional 
   memory. 

2) Run the MS-DOS installations for the kit components from 
   MS-DOS, not from an MS-DOS window under Windows.

3) The MS-DOS install program is incompatible with the expanded 
   memory manager (emm386).  Before installing the Plug and Play 
   kit for MS-DOS, disable your expanded memory manager. After 
   you have finished the installation, you can enable the 
   expanded memory manager again.

4) The MS-DOS installation fails during an overinstall of a 
   previous version of the Kit if you changed the file 
   permissions of the previously installed version to read-only.

5) During MS-DOS installations, you are offered the opportunity 
   to select from one or more choices. The highlighted choice 
   (that is, the choice selected when you press the Enter key) is 
   lighter than the other choices.  On many, but not all, 
   displays, the highlighted choice flashes.

    
Plug and Play Configuration Manager (CM)
----------------------------------------

Advanced users should be aware this release of the Plug and Play 
Configuration Manager has the following limitations:

- By default the functionality provided by the CM_LockConfig and 
  CM_UnlockConfig functions is available to applications running 
  in real-mode MS-DOS environment.  The CM lock functionality is 
  always available under Windows, including the Windows V86 DOS. 

  If this functionality is not needed, add the /NOLOCK parameter 
  in the line in config.sys that invokes the CM driver 
  (DWCFGMG.SYS).

                              NOTE

         The CM_LockConfig and CM_UnlockConfig functions 
         are unrelated to the locking options available 
         with ECU or ICU utilities.

- In the absence of the Intel Plug and Play BIOS extensions, Plug 
  and Play boot devices are not reconfigured by the Configuration 
  Manager.

- Calls to the Configuration Manager do not work during 
  sys_critical_init.



ISA Configuration Utility (ICU)
-------------------------------

The ISA Configuration Utility provides a way to assign system 
resources to add-in cards before the card is installed.  This 
assignment avoids resource conflicts and keeps track of system 
resources so that Plug and Play cards do not conflict with 
non-Plug and Play cards in a system.

                              NOTE

     The ISA Configuration Utility is for ISA systems 
     only.  Do not run it on EISA systems.  To configure
     EISA systems, use an EISA Configuration Utility.


Configuration Assistance Utility (CASSIST)
------------------------------------------

On systems without the Plug and Play BIOS, the Configuration 
Assistance Utility (CASSIST) determines the resources used by 
system (motherboard) devices.

                              NOTE

       The cassist utility is not needed on systems
       with the Plug and Play BIOS.


Plug and Play Kit Notes and Limitations
---------------------------------------

This release of the Plug and Play Kit for MS-DOS has the 
following limitations:

- The CM and ICU do not support more than one PCI bus.

- EMM386 Versions Prior to 4.49:

  You may experience a hang and/or reset when using any version
  of EMM386 prior to version 4.49.  The problem occurs only on 
  systems with a Plug and Play BIOS, Plug and Play software (ICU 
  and Configuration Manager) and EMM386 versions prior to 4.49.  
  If you have such an earlier version, contact the place you 
  purchased your PC or Microsoft for information on obtaining an 
  updated EMM386 program.

- Memmaker Program:

  Using the MS-DOS 6.21 or 6.22 Memmaker program with a Plug and 
  Play system may cause your system to reboot.  Selecting the 
  Memmaker program's "Aggressive" memory scanning option will 
  cause Memmaker to specify HIGHSCAN as an option parameter to 
  EMM386 in the CONFIG.SYS file.  Do not select the "Aggressive" 
  memory scan option in Memmaker.

  The HIGHSCAN option may cause EMM386 to map memory into the 
  F000:0 memory area used by the system BIOS.  In this instance, 
  EMM386 does not recognize that the BIOS may be using the entire 
  memory range from F000:0 to F000:FFFF.  Typically, the system 
  will reboot when the Plug and Play Configuration Manager begins 
  initialization.  The behavior may vary from system to system 
  depending upon the BIOS.

- Excluding or Including an EMM386 Memory Range:

  Some Plug and Play BIOS systems map ESCD storage somewhere in 
  the E000:0 block of memory.  While current implementations of 
  ESCD contain a BIOS signature (0x55AA) that signals EMM386 to 
  avoid the area, older implementations may not have this 
  signature.  Without a signature, EMM386 does not recognize the 
  ESCD and can map memory on top of it.  This can result in ESCD 
  data becoming corrupt.

  You should contact the maker of your PC.  You may have to 
  exclude the E000:0 memory range on your EMM386 command line in 
  your CONFIG.SYS file.  Also, you should never explicitly 
  include the memory range E000:0 on your EMM386 command line.

- In the absence of the Intel Plug and Play BIOS extensions, Plug 
  and Play boot devices are not reconfigured by the Configuration 
  Manager.

- Software exists that is incompatible with proper Configuration 
  Manager operation.  The interaction between this software and 
  the CM might cause unusual system behavior or system delays 
  when both the CM and the software are running on the system.

  If you suspect such interaction is causing problems on your 
  system, try adding the /STATIC and/or the /NOVCPI options to 
  the DWCFGMG.SYS driver line in the CONFIG.SYS file.  Either or 
  both options might remedy the problem.

- The VCAD Windows driver provides protected-mode EISA 
  interfaces.  when the /PMEISA CM option is specified. Since not 
  all EISA systems provide this level of BIOS functionality, 
  these functions might not work correctly on all EISA systems.  

- If you use the /FILE option of the Configuration Manager on a 
  system with the ACFG BIOS, and your ESCD.RF file doesn't 
  provide motherboard information for your system, the ICU cannot 
  run.  This option is normally needed only for testing on EISA 
  systems.


ISA Configuration Utility Notes and Limitations
-----------------------------------------------

- Using the ICU, when you save an image file (Save Image File or 
  Save Image File As.. on the Advanced menu), the ICU.NDX index 
  file is not updated.  So, if the configuration you saved 
  contained one or more unlisted cards, when you load the image 
  file you saved, the card resources for these unlisted cards are 
  in the loaded configuration image.  However, cards of this type 
  might be listed as "Unknown Card," instead of by the name you 
  assigned when you added it.  You can avoid this behavior by 
  choosing the Save item on the File menu before you save the 
  image file.  In addition, if you copy the image file to another 
  system, you must also copy the ICU.NDX index file to avoid this 
  behavior.

- Pressing the F1 key invokes the ICU help facility from the ISA 
  Configuration Utility window (the main window) only.

- When you are modifying a function of a Plug and Play card in 
  preparation for locking it, you might see a conflict message 
  that indicates the card is conflicting with itself.  Try 
  reconfiguring the card functions in a different order.

- If a function has two or more resource types that must be 
  configured together, the ICU might not be able to configure 
  that function, even though there might be a valid configuration 
  available.  If you encounter this problem, see the discussion 
  on resolving conflicts in the Troubleshooting section of the 
  ICU User's Guide for ways to successfully configure functions 
  in this category.

- When you pick a resource for a new card that is currently used 
  by an existing card, the ICU reconfigures the Plug and Play ISA 
  cards first, then the PCI cards.  However, PCI cards are 
  restricted to specific interrupts.  Sometimes, the 
  configuration fails because the ICU assigns Plug and Play cards 
  to all the valid PCI card interrupts.  Then, The ICU cannot 
  configure the PCI cards.  Use the ICU to reconfigure the Plug 
  and Play cards to different interrupts, then try again to 
  configure your new card.

- If a boot function on a Plug and Play card causes a conflict 
  error on a system without the Plug and Play BIOS, one of two 
  messages appears after you Modify the card and change the 
  function:  

   "This card will be configured when the system is rebooted."
      
  This may not be true. If this message appears, there is a 
  configuration that works.  However, systems without the Plug 
  and Play BIOS lack the ability to configure boot functions of 
  Plug and Play cards, and cannot find the working configuration 
  for you.  

  Find the working configuration and configure the Plug and Play 
  card using jumpers, switches, or a software configuration 
  utility provided by the card manufacturer.  Inspect the 
  resources currently used in the system to determine a working 
  configuration.

   "A conflict has been detected with <conflicting_card>.  The 
    conflicting resource is <resource_and_value>."

  This message might be inaccurate. It might not inform you of 
  the conflict keeping the card from being configured.

  Inspect the resources currently used in the system and use the 
  conflict resolution techniques described in the Chapter 5 of 
  the ICU User's Guide to discover and correct the conflict.  If 
  in the course of resolving a conflict reported by this message 
  you see the message discussed previously, use the techniques 
  described to continue.

- Because of ISA architecture limitations, ISA cards cannot use 
  Interrupt 2, but must use Interrupt 9 instead.  The ICU takes 
  this limitation into account and only allows users to choose 
  Interrupt 9 when Interrupt 2 is listed as a valid resource 
  value in a configuration file.  When this substitution occurs, 
  the interrupt value is offered as "Interrupt 9(2)."

- When you are configuring an unlisted card, if the card 
  manufacturer's documentation lists Interrupt 2 as a valid 
  resource value, you must instead choose Interrupt 9.

- A set of reserved resources is standard on ISA systems.  
  However, the ICU mistakenly allows these resources to be 
  allocated by the user.  Please do not allocate the following 
  resources:

	I/O Ports       279h, A79h

- You can increase the size of the Smartdrv buffer to make the 
  ICU faster.


MS-DOS ICU Limitations
----------------------

- The MS-DOS ICU installation might fail if some Terminate and 
  Stay Resident (TSR) programs or drivers are resident in memory.  
  If this happens, remove all TSRs from memory and restart the 
  install process. Some example TSRs and drivers are Borland Side 
  Kick and network drivers that are not loaded from CONFIG.SYS.

- You might see this message:

            "N100: Not enough memory to run the ICU."

  In a few cases, 488 KBytes of free memory is insufficient.  In 
  these cases, ICU operation ceases suddenly and you see an 
  MS-DOS "Out of Memory" error.  In this situation, use the 
  Windows version of the ICU if it is available.  If the Windows 
  ICU is not available, use the Save item on the File menu after 
  each card operation to avoid losing too much work.  

- You might see this message:

         "N110: Please run the ICU from its directory."

  You must invoke the ICU from the directory that contains the DB 
  directory (default placement C:\PLUGPLAY\ICU).    

- You must execute the MS-DOS ICU from MS-DOS only, not from an 
  MS-DOS window.  

- If you rearrange the ICU dialog boxes on the screen, you might 
  see spurious lines, characters, or buttons.  Do not click the 
  mouse on these spurious entities.  Clicking the mouse here 
  causes the system to hang.

- The scroll box (the square slider inside the scrollbar) 
  occasionally does not work.  Use the arrow keys.

- If you initiate an action such as Add Card when the System 
  Resource Usage dialog box is visible, the dialog box might 
  close.


Configuration Assistance Utility Notes and Limitations
------------------------------------------------------

- CASSIST operation is incompatible with network operation.  
  Disable network drivers on your system before running CASSIST.  
  Enable the network drivers after you have run CASSIST.

- CASSIST creates the ESCD.RF file in the root directory of the 
  current drive (that is, the drive on which the CASSIST utility 
  is run).  On systems without the Plug and Play BIOS, if the 
  current drive is not the boot drive, you must move this ESCD.RF 
  file manually to the root directory of the boot drive.

- CASSIST does not detect interrupt resources used by ISA video 
  cards.


MS-DOS is a registered trademark, and Windows is a trademark of 
Microsoft Corporation.

The program used for MS-DOS installation of components of the 
Plug and Play Kit for MS-DOS and Windows, INSTALL, is licensed 
software provided by Knowledge Dynamics Corp., P.O. Box 780068, 
San Antonio, Texas 78278 (U.S.A.). INSTALL is Copyright (c) 
1987-1993 by Knowledge Dynamics Corp., which reserves all 
copyright protection worldwide. INSTALL is provided to you for 
the exclusive purpose of installing the MS-DOS components of the 
Plug and Play Kit for MS-DOS and Windows.  Motorola is 
exclusively responsible for the support of the Plug and Play Kit 
for MS-DOS, including support during the installation phase.  In 
no event will Knowledge Dynamics Corp.  provide any technical 
support for the Plug and Play Kit for MS-DOS.

Other names and trademarks are the property of their respective 
companies.

