Multia Service Pack V3.2-SP1/x86 - Release Notes Mar-1997  
  
  

Multia Service Pack V3.2-SP1/x86 is a maintenance release of Multia Software which fixes problems encountered in
Multia Software versions 3.2 and 3.2A for x86. This is a Service Pack kit and requires that Multia Software V3.2 or
V3.2A to be installed prior to installation. It is installed from the CD-ROM using either Software Update This Desktop
from the Multia Application Manager or by scheduling an Update using the Multia Configuration Manager. Once
successfully installed the Multia Version Number can be verified from the Application Manager in Help About as
V032-SP1. 

Below is a list of problems resolved since the release of Multia Software V3.2 and V3.2A for x86: 

Multia Desktop Management System : 

    The Multia Desktop Server would sometimes generate error messages because of problems with RPC locator. 

    Enabling DHCP for a desktop, would sometimes hang the Multia desktop server on that desktop and
    consequently the configuration manager could not reach that desktop to perform any customizations. 

    When a Multia administrator configured a target desktop to be DHCP ENABLED AND join a Domain
    simultaneously, the desktop management system failed to complete the transaction. Now it completes
    succesfully. Note: If you have encountered any problems related to Joining a Domain or enabling DHCP, we
    strongly recommend the following steps: 
        Disable DHCP and joining a Domain(set to default workgroup), using the configuration manager. 
        Reboot the managed desktops (use the Configuration manager if possible). 
        Software update all desktops to V3.2-SP1. 
        Re-enable DHCP and Joining a Domain. 
    Software Upgrade now works properly even when no user is logged on the target desktop. 
    In International settings, Multia did not support the space character as a separator. 

Xserver : 

     An X application or X session would sometimes fail to display if the X server was not already running. 

    The local Motif Window Manager (MWM.EXE) would not start automatically when LAT was the only active
    network protocol. 

    The X server would crash when connecting to systems running the Common Desktop Environment (CDE). 

    When logging out or shutting down the desktop, the X server would prompt twice to confirm that existing clients
    would be closed. 

    The "slow dashed lines" problem has been fixed. Dashed lines are now drawn very fast!!! 

    Xserver crash related to non-cacheable fonts (for example the "esfonts") has been fixed. 

Other :  

    When a non-U.S. keyboard was selected for Windows NT the corresponding keyboard number for use with
    MS-DOS applications was not set. 

    When the MOP server was configured to start automatically an error message saying that a service had failed to
    start was displayed. 

     "Netherlands" has been added to the "Country" list and "Dutch" has been added to the "Language" list in the
    international settings of the Multia control panel. 

    The LAT configuration problem (node name being changed to the NT computer name, when a workgroup level
    property is applied to the desktop) has been fixed. 
    Any application that had been set to "autostart", sometimes failed to start because the network transport
    protocols had not started yet. Now,  Appmanager waits until the network transports start and then launches the
    "autostart" applications.