Software Bisque Knowledge Base Article – 280

RESOLUTION

Launching a Software Bisque Windows application immediately displays the error message “A required .DLL file, (filename), was not found.” Clicking OK to this message causes the application to terminate.The operating system cannot locate the specified dynamic-link library (DLL).  This means the Software Bisque application was not installed correctly for one or more of thefollowing reasons:

• The DLL was incorrectly moved or deleted after installation.

• An anti-virus application, or Microsoft Vista's User Account Control (UAC) is prohibiting the software from being installed correctly. 

• Another application (such as Norton WinDoctor) has erroneously modified the Windows Registry and causes this error message to appear.

• The account installing the application does not have administrative privileges (Windows NT and Windows 2000 OS only).  

• A virus (such as the SIRCAM virus) on your computer may be causing this behavior.

BACKGROUND

When Windows launches any application, the operating system must load files that are “dynamically linked” to the executable file.  The operating system attempts to locate these dynamic-link library files (also called “shared files”) in the following order:

• The folders located in the PATH system environment variable are searched for the dynamic-link library file. If not located in the folders located in the Path variable, 

• The Path value in the App Paths key of the Windows Registry is used by the operating system to determine the location of shared files for the particular executable. The Path value for any Windows application can be viewed using the following procedure:

1. Click Start | Run.

2. In the Run dialog box, type Regedit in the Open text box and then click OK.

3. From the Windows Registry, navigate to the following key:

HKEY_LOCAL_MACHINE/Software/Microsoft/Windows/CurrentVersion/App Paths/Application Name.exe (such as Sky.exe)

For a properly installed application, the Path value must have the string Data similar to the following: 

C:/Program Files/Software Bisque/;C:/Program Files/Common Files/System

Where the first path is the location of the executable on the hard drive and the second path (after the semi-colon () is the location of the Windows Common Files Folder.  The location of the Common Files folder is specified by the Windows operating system and the setup program determines this folder when the software is installed. 

According to the Windows Logo Program guidelines, applications that use dynamic-link libraries must place them in the System folder of the Common Files folder. Software Bisque follows these guidelines for all its Windows-based applications.

1. Update your virus signatures and scan your computer for potential infection. Once the virus is removed, the application should run normally. If the same behavior persists, continue to step 2.

2. Verify that the dynamic link library is present on the computer.  Click Start | Find | Files or Folders (Start | Search | Files or Folders under Windows 2000), enter the name of the DLL file that cannot be found and then click Find.  The file should reside in the folder C:/Program Files/Common Files/System.

In order for an application to locate its shared files, the proper Registry entries must be present as described above.  The Registry entries for Software Bisque applications are added when the software is installed.  If another application (such as Norton WinDoctor) incorrectly removes these entries after the Software Bisque application is installed, the entries must be added to the Registry again in order for the application to run.   

Uninstalling and reinstalling the affected application (provided that all anti virus applications and Norton WinDoctor are disabled) will resolve this problem. 

Adding to the System Path

A second solution is to add “c:/Program Files/Common Files/System folder to the computer's PATH environment variable.   

Windows 95/98/Me

To add the common files folder to the PATH environment variable under Windows 95/98/Me, do the following:

Click Start | Programs | Accessories | Notepad

From Notepad, click File | Open and then enter C:/AUTOEXEC.BAT. 

Add the following text to the last line in this file (or to the end of the PATH statement, if it already exists in this file): 

PATH=”C:/PROGRAM FILES/COMMON FILES/SYSTEM”

 

or, for example, if the PATH already exists:

 

PATH=C:/WINDOWS;C:/WINDOWS/COMMAND;”C:/PROGRAM FILES/COMMON FILES/SYSTEM”

Make sure to include the quotes at each end of the common files path, otherwise, the PATH command will fail. 

1. Click File | Save. 

2. Restart the computer.

3. Verify that the path statement now includes the common files folder by clicking Start | Programs | MS DOS Prompt. 

4. From the MS DOS Prompt, type the word PATH and then press ENTER.

The PATH= statement should now include the C:/Program Files/Common Files/System folder.

Windows NT/2000/XP

To modify the Path environment variable under Windows NT or Windows 2000 or XP, click Start | Settings | Control Panel | System,  Advanced tab.  Select the Environment Variable option (the exact location of this option varies with the operating system, consult the operating system's help file for details).  Edit the existing PATH environment variable to add the following path: 

C:/Program Files/Common Files/System

to the Systme PATH environment variable.  Note that each folder in the PATH variable must be separated by a semi-colon (.  Most operating systems require that the computer be restarted before this change takes affect.

The affected Software Bisque application will now be able to located its shared files regardless of the Registry Entries. 

Windows Vista

Microsoft's Vista (32-bit and 64-bit Editions) includes an application called “User Account Control” (UAC) that is designed to prevent installation of malicious software. It can also prevent successful installation of software like Software Bisque's CCDSoft.

Before installing CCDSoft (or other software), temporarily disable UAC (search Windows Help for “UAC” or “User Account Control”). Don't forget to enable UAC afterwards.

More Information

Symantec's technical support has confirmed that Norton WinDoctor incorrectly modifies the Windows Registry.  This bug in WinDoctor affects all Software Bisque applications that use shared files. Software Bisque recommends disabling Norton WinDoctor.