Microsoft KB Archive/84795

-

{| The information in this article applies to:
 * width="100%"|
 * Microsoft Windows operating system versions 3.1, 3.11

SUMMARY
When you run Microsoft Windows, incorrect or outdated dynamic link library (.DLL) files can cause the following error message:

Call to Undefined Dynalink This article discusses several software products and files that can cause this error message with outdated files, including:
 * Access Pack for Microsoft Windows
 * Ace File Database
 * Artisoft LANtastic for Windows
 * LaserTools PCPanel
 * Microsoft Bookshelf
 * Microsoft Dr. Watson
 * Microsoft LAN Manager
 * Microsoft printer drivers
 * Microsoft SHELL.DLL file (Program Item Properties dialog)
 * Powersoft PowerBuilder
 * Novell NetWare utilities
 * Microsoft Bookshelf for Windows 1994, 1995, 1996-97

Access Pack for Microsoft Windows
After you install Access Pack for Microsoft Windows (available on the Windows Driver Library [WDL]), you may receive the &quot;Call To Undefined Dynalink&quot; error message when you try to run one of the Access Pack utilities.

The error occurs because one or more of the following conditions exist:


 * The MOUSE.DRV= entry in the [BOOT] section of the SYSTEM.INI file points to the wrong mouse driver.
 * The KEYBOARD.DRV= entry in the [BOOT] section of the SYSTEM.INI file points the wrong keyboard driver.
 * The Access Pack mouse driver (AP-MOU.DRV) in your Windows SYSTEM subdirectory is not the current version.
 * The Access Pack keyboard driver (typically AP-KBD.DRV, AP-KBDHP.DRV, or AP-KBDOL.DRV) in your Windows SYSTEM subdirectory is not the current version.

If the MOUSE.DRV= entry in the [BOOT] section of the SYSTEM.INI file points to anything other than AP-MOU.DRV, change it to read MOUSE.DRV=AP-MOU.DRV, and then copy the AP-MOU.DRV file from the WDL disk to your Windows SYSTEM subdirectory. For example, if Windows is installed in the C:\WINDOWS directory and your WDL disk is in drive A, type the following at the MS-DOS command prompt and then press ENTER: copy a:\ap-mou.drv c:\windows\system If the KEYBOARD.DRV= entry in the [BOOT] section of the SYSTEM.INI file points to KEYBOARD.DRV, KBDHP.DRV, or KBOLI,DRV, change it to point to the appropriate Access Pack keyboard driver (AP-KBD.DRV, AP-KBDHP.DRV, or AP- KBDOL.DRV), and then copy the corresponding file from the WDL disk to your Windows SYSTEM subdirectory. For example, if Windows is installed in the C:\WINDOWS directory, your WDL disk is in drive A, and you change your KEYBOARD.DRV= entry from KEYBOARD.DRV to AP-KBD.DRV, type the following at the MS-DOS command prompt and then press ENTER: copy a:\ap-kbd.drv c:\windows\system NOTE: If your current keyboard driver is not AP-KBD.DRV, AP-KBDHP.DRV, or AP-KBDOL.DRV, contact your mouse vendor to determine if it is compatible with the Microsoft Mouse driver. If it is not, your mouse vendor may provide Access Pack-compatible drivers. If the MOUSE.DRV= entry in the [BOOT] section of the SYSTEM.INI file points to the Access Pack mouse driver (AP-MOU.DRV), replace the file with the correct mouse driver from the WDL disk. For example, if Windows is installed in the C:\WINDOWS directory and your WDL disk is in drive A, type &quot;copy a:\ap-mou.drv c:\windows\system&quot; (without the quotation marks) at the MS-DOS command prompt and then press ENTER.

If the KEYBOARD.DRV= entry in the [BOOT] section of the SYSTEM.INI file points to AP-KBD.DRV, AP-KBDHP.DRV, or AP-KBDOL.DRV, replace the file with the correct keyboard driver from the WDL disk. For example, if Windows is installed in the C:\WINDOWS directory, your WDL disk is in drive A, any you are using AP-KBD.DRV, type &quot;copy a:\ap-kbd.drv c:\windows\system&quot; (without the quotation marks) at the MS-DOS command prompt and then press ENTER.

NOTE: If the Access Pack keyboard drivers are installed properly, most Access Pack features work correctly even if an improper mouse driver is installed. However, the MouseKeys and SerialKeys features are disabled, and you cannot run the Access Utility to customize the settings or view Help.

For more information about how to run Access Pack for Microsoft Windows with unsupported hardware, query on the following words in the Microsoft Knowledge Base:

using and access pack and unsupported hardware For more information, query on the following words in the Microsoft Knowledge Base: access.wri and wdl

Ace File
The database program Ace File version 1.0 for Windows may cause a &quot;Call to Undefined Dynalink&quot; error message when you choose Open from the File menu and select Database. Ace Software can be contacted at (408) 451-0100.

There is currently no solution to this problem. Contact Ace Software for an upgrade.

Artisoft LANtastic for Windows
You may receive a &quot;Call to Undefined Dynalink&quot; error message or &quot;FatalExit code=0x0404&quot; if you are running an earlier version of the LANtastic version 3.0 install program WINSTALL.EXE.

These error messages occur if the date of the WINSTALL.EXE file is earlier than 10/23/91. They do not occur if you use Windows 3.1 to update an existing version of Windows 3.0 that was already configured for the network.

To correct this problem, obtain an updated version of the WINSTALL.EXE file by contacting LANtastic technical support.

Lasertools PCPanel
When running under Windows 3.1, the LaserTools utility Printer Control Panel (PCPanel) may cause a &quot;Call to Undefined Dynalink&quot; error message.

PCPanel is produced by LaserTools and ships with some NEC printers, the Texas Instruments MicroLaser, and Okidata Lasers.

PCPanel looks for HPPCL or PostScript data being sent to the printer and then modifies the data being sent. This function may not work correctly with Windows 3.1 and may cause error messages and/or printing problems.

This problem has been corrected in version 2.3 of PCPanel, and is available from LaserTools.

To Obtain Version 2.3:

Current owners of PCPanel can receive a new copy by calling LaserTools at (800) 995-6487. NEC Silentwriter owners who purchased their printer after January 1, 1992 receive this upgrade free of charge. Silentwriter owners who purchased their printers before January 1, 1992 are charged a $15.00 handling and shipping fee. The software upgrade center accepts popular credit cards or a check by mail. The mailing address is:

NEC Redemption Center P.O. Box 3503, Wallingford, CT 06494 The upgrade package includes installation instructions, and also revised .WPD files for Silentwriter Model 95 usage with Windows 3.1. This 800 number is for SOFTWARE UPGRADES only, and is not a technical support center. NEC Bulletin Board System (BBS): (508) 635-4706

Temporary Workaround:

Until you receive the updated version of PCPanel, you can work around the problem by removing PCPanel. The following paragraph is taken from the &quot;Printer Control Panel Owner's Manual&quot;:

If you install Printer Control Panel for Windows 3.0, certain information is added to your Windows 3.0 files. If you wish to  remove that information from your working copy of Windows 3.0, you must use the Re-INSTALL program to do so. Simply choose the Remove PCPANEL From Windows selection from the Windows 3.0 menu in INSTALL. You'll want to remove Printer Control Panel as an  application in Windows 3.0 also. Refer to Appendix A.

NOTE: Appendix A shows how to delete the PCPanel icon. According to LaserTools technical support, you can remove the Printer Control Panel with the following steps:   In the PCPrinter or LaserTools directory, type: install /u  Select &quot;Skip this step without modifying the AUTOEXEC.BAT.&quot; Choose Remove Printer Control Panel For Windows.

NOTE: The MS-DOS-based TSR can remain in place.

Microsoft Dr. Watson
If you have an earlier version of TOOLHELP.DLL (dated before 3-10-92) in your Windows directory, you will receive a &quot;Call to Undefined Dynalink&quot; error message. When earlier versions of Dr. Watson were installed under Windows 3.0, DRWATSON.EXE and TOOLHELP.DLL were installed into the Windows directory. When Dr. Watson version 0.80 is installed during the installation of Windows 3.1, DRWATSON.EXE is installed into the Windows directory, and TOOLHELP.DLL is installed into the Windows\SYSTEM directory. To correct this problem, delete the TOOLHELP.DLL file from the Windows directory.

NOTE: This problem can also occur with an earlier version of SHELL.DLL (see below), OLECLI.DLL, OLESVR.DLL, and COMMDLG.DLL. All these files should be located in the Windows\SYSTEM directory and should be dated 3/10/92 or later.

Microsoft LAN Manager
If you receive a &quot;Call to Undefined Dynalink&quot; error message when starting Windows 3.1 with Microsoft LAN Manager loaded, you most likely have outdated versions of LAN Manager network dynamic link libraries (DLLs). Using the proper versions of the DLLs corrects the problem.

Normally, the original DLLs, NETAPI.DLL and PMSPL.DLL, are in the NETPROG subdirectory of the LAN Manager directory and they are updated in place. The original DLLs are backed up to NETAPI.BAK and PMSPL.BAK. To prevent the destruction of the original files when multiple installations or updates take place, the files are not updated if the .BAK files are already present.

The problem can result from a variety of causes:


 * If the backup files are present but the DLLs are out of date, then the files are not updates and the out-of-date DLLs are used.
 * If the LAN Manager directory isn't found during setup, but the out-of-date DLLs are in the path, they are used.
 * If Windows was set up for a different network, and you changed to LAN Manager 2.0 from Windows Setup in maintenance mode, the drivers aren't copied correctly. MS-DOS maintenance mode Setup copies the files correctly.

The LAN Manager 2.0 files are called NETAPI20.DLL and PMSPL20.DLL on the Windows disks. They may be present in the system directory in some cases. If the files are not, they can be expanded from the Windows disks using the EXPAND utility. These files should be copied to the NETPROG subdirectory of the LAN Manager directory and renamed to NETAPI.DLL and PMSPL.DLL. Note that these LAN Manager 2.0 DLLs should NOT be used with LAN Manager 2.1. The DLLs and drivers provided with LAN Manager 2.1 should be used. If the error message results on a LAN Manager 2.1 configuration, NETAPI.DLL and PMSPL.DLL may have been overwritten by LAN Manager 2.0 libraries and should be expanded from the LAN Manager 2.1 disks. This can occur if you specified LAN Manager 2.0 as your network when installing Windows 3.1 and then changed to LAN Manager 2.1. This will happen most likely when using batch mode installations on dissimilar machines. If the .BAK files are larger than the .DLL files, then this has probably occurred.

Microsoft SHELL.DLL File (Program Item Properties Dialog)
Choosing the Change Icon button in the Program Item Properties dialog box in Windows 3.1 may cause the &quot;Call to Undefined Dynalink&quot; error message if the SHELL.DLL file is dated earlier than 3-10-92:

To update the SHELL.DLL file:

  Expand the SHELL.DLL file from the original Windows 3.1 disks (Disk 4 of the 1.44-MB 3.5-inch disk set, or Disk 5 of the 1.2- MB 5.25-inch disk set) to the Windows\SYSTEM directory. To do this, at the MS-DOS command prompt, type the following expand [drive1]:\shell.dl_ [drive2]:\windows\system\shell.dll where &quot;drive1&quot; is the drive designating the location of the Windows 3.1 disk, and &quot;drive2&quot; is the drive on which Windows 3.1 is installed.  Remove any SHELL.DLL files that may exist in the Windows directory.

Microsoft Printer Drivers
The &quot;Call to Undefined Dynalink&quot; error message may occur if Windows version 3.1 attempts to use a Windows version 3.0 printer driver. You must remove the Windows version 3.0 printer driver and install the Windows version 3.1 printer driver to correct the problem.

NOTE: You must remove duplicate printer driver entries from the Installed Printers list or you will be unable to install a new Windows version 3.1 printer driver from the Windows disks.

Be sure to search all drives and directories for outdated printer drivers. This is especially important if you are running on a network, where printer drivers may be stored in multiple directories.

Novell NetWare Utilities
When you start Windows for Workgroups, the wallpaper appears, the &quot;Call to Undefined Dynalink&quot; error message flashes on the screen, and you return to an MS-DOS prompt.

If you have the Novell NetWare Tools for Windows installed and their files are dated earlier than 1992 you need to update the utilities.

Powersoft Powerbuilder
Using Powersoft PowerBuilder 1.0a with Windows 3.1 may result in a &quot;Call to Undefined Dynalink&quot; error message. PowerBuilder uses a custom version of TOOLHELP.DLL. This design is not compatible with the TOOLHELP.DLL file shipped with Windows 3.1.

To run PowerBuilder successfully with Windows 3.1, please contact Powersoft for a PowerBuilder update.

Microsoft Bookshelf for Windows 1994, 1995, 1996-97
For information pertaining to this error message with the versions of Bookshelf listed above, please see the following article in the Microsoft Knowledge Base.

ARTICLE-ID: Q96336 TITLE    : &quot;Call to Undefined Dynalink&quot; Errors The third-party products discussed in this article are manufactured by vendors independent of Microsoft; we make no warranty, implied or otherwise, regarding these products' performance or reliability.
 * }

-

Last reviewed: September 18, 1997

© 1998 Microsoft Corporation. All rights reserved. Terms of Use.