HP 770k (LA), 740n (US), 792.se DLA Engine Installation, Shared Components Installation, Registry

●MSVCP60.DLL – A shared file required by MFC due to our UI.

●MSVCRT.DLL – A shared file required by MFC for the C run time library routines needed by the UI.

●OLEAUT32.DLL – A shared file that is required due to some of the UI functions we use in MFC.

●OLEPRO32.DLL – A shared file that is required due to some of the UI functions we use in MFC.

●PICTUREBTN.OCX – A shared file that contains some of the buttons used in the main user interface.

●PNPWPROP.DLL - This is a Windows 9x Plug-n-play resource file used by PAPI to generate the PNP dialog.

●PNPWR???.DLL - A shared Windows 9X file that contains translated resources for the PNP dialog

●VXBLOCK.DLL – This is a helper DLL shared between many products that allows us to stop running conflicting applications. It provides the support for running MyCD and DLA simultaneously.

●VXDMDBTN4.OCX – This is a shared file that contains some of the buttons used in the main user interface.

Files installed to “[Windows Directory]\HELP”:

●PNPWH???.HLP – A shared Windows 9X help file for our plug and play drivers.

●DRVMCDB.INF – A shared Windows 2000 installation file for DRVMCDB.SYS.

DLA Engine Installation

The DLA engine attempts to update all DLA engine drivers to be the same. These drivers are the file system engine drivers and have nothing to do with the actual device drivers from the shared components team. There are two complex issues with this. The first is to be certain that all of the engine drivers are the new versions. The second is to make certain that all of the PCONFIG data gets combined into one file.

Each installation has a PCONFIG file. This file indicates what devices are supported for DLA. However, as a new version of DLA is installed, new devices may be supported and this needs to be updated. As a version of DLA is uninstalled, some devices may disappear from the support list while others remain from another installation.

All of this is handled by DLAUNIN.EXE. The normal installer calls “DLAUNIN.EXE –Q–I –D:<INSTALL>” where –Q means quiet mode, -I means install, and –D indicates the directory to install from where <INSTALL> is the directory. Only 1 version of DLA can be installed on a machine. This is a new feature of the MSI installer

Files installed to “[Windows Directory]\SYSTEM32\DRIVERS”:

●DRVMCDB.SYS – Our shared optical device driver for Windows 2000 only.

●DRVNCDB.SYS – Our shared optical device driver for Windows NT 4.0 only.

●DRVNDDM.SYS – Our shared DDM driver file for Windows NT (4.0 or 2000) only.

Files installed to “[Windows Directory]\INF”:

●DRVMCDB.INF – A shared Windows 2000 installation file for DRVMCDB.SYS.

●DRVNCDB.INF – A shared Windows NT 4.0 installation file for DRVNCDB.SYS.

●DRVNDDM.INF – A shared Windows NT (4.0 and 2000) installation file for

DRVNDDM.SYS.

●PNPWIDE.INF – A shared Windows 9X installation file for our IDE plug and play drivers.

●PNPWTAPE.INF – A shared Windows 9X installation file for our tape plug and play drivers.

Shared Components Installation

The shared components (drivers used by all products including backup) are handled by the basic installer. Each component is updated to make certain that only the newest version is installed. A helper file (PNPWTAPE.EXE for Win9X or PNPNINST.EXE for NT) handles the plug and play driver installation. This installation is the same basic installation we use on all products.

Registry

DLA install settings are stored in the registry in MyComputer\HKEY_LOCAL_MACHINE\Software\VERITAS\Direct Access\CurrentVersion\All

DLA driver settings are stored in the registry in

MyComputer\HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\* (* = name of DLA driver e.g. tfsnifs)

NOTE: These settings should not be altered by the user.