CodeCalc

CodeCalc FAQ

The faqs are organized in following categories:


 


Installation: 

The installation of a patch/build/update begins, but after a while a message is displayed indicating an interruption regarding an MSXML file and states that the patch was not installed. What is wrong?

One cause of this problem has been traced to a problem with the Windows XML Parser. An update for this parser is available from Microsoft at http://www.microsoft.com/downloads/details.aspx?FamilyID=28494391-052b-42ff-9674-f752bdca9582&DisplayLang=en. Download the "msxml3.msi" file and run it. Then try to put the patch/build/update on again.

Additionally, review this link (http://support.microsoft.com/kb/898628) which describes a behavioral change in the Microsoft Installer, which can also cause installation problems. You should also update Microsoft Windows Installer and try the installation again.

If the above does not resolve the issue then make sure you have the latest service pack of MS Windows. Run the Windows update on your computer and try the installation again.

During the Installation an error is about missing instmsi30.exe file is encountered.

Download the latest version of Microsoft Windows installer from Microsoft website (www.microsoft.com) or from this link, http://www.installengine.com/Msiengine30/instmsi30.exe.

During the application of a patch/build/update, the InstallShield Wizard asks for the original MSI file. Where can I get this MSI file?

Windows periodically cleans up (empties) temporary folders, which is why the installation wizard may prompt for this file. The procedure for acquiring this MSI file from the original CD is as follows:

  1. Put the original CD in and start the installation. This will tell you it is going to repair the installation. Do not worry about this because you will abort before it does anything.
  2. Let the installation run until you get to the dialog titled Resuming the InstallShield Wizard for CodeCalc 2006. DO NOT CLICK [NEXT] here!
  3. In Windows Explorer, change the "View" settings to (i) show hidden files and folders, and (ii) display system folders.
  4. In Windows Explorer, browse for c:\documents and settings\administrator\local settings\temp\_is180\CodeCalc 2006.msi. (Note, the _is180 directory could be a random name generated by Windows. If the program is installed using a different account then use that account instead of the "administrator" folder)
  5. Copy this MSI file to some "safe", temporary directory. This is so you can reference it during the application of the patch.
  6. Abort the installation from the CD. Note, this will delete the _is180 directory and its contents.
  7. Start the patch file, and when it asks for the MSI file, point it to the temporary directory from step "e".

Back to Top

General Startup:

On Starting the program, ESL Errors #7 (Feature Not Found) or 31, are encountered. What is wrong?

With the version 2006 new blank HL ESL(s) were supplied. Before you can use the new ESL the license needs to be transferred from the older HASP ESL to the new HL ESL. This error indicates that the license has Not been transferred. Instruction for license transfer are located were sent with the new CD and are also located here in acrobat PDF format.

The on-line documentation does not work:

This is usually caused by the lack of the Adobe Acrobat Reader. The on-line documentation is distributed in .PDF format, which requires the Adobe Acrobat Reader. This Reader is supplied on the distribution CD, and an install file is also placed in the \acrobat sub-directory under the program installation directory. Install the Reader, restart Windows, and try viewing the documentation again.

Only a portion of the window can be seen, some parts or controls are cut off.

CodeCalc was designed to operate in 1024x768 resolution with "small fonts." "Large fonts," or "custom fonts" may be too large for the current resolution. Either decrease the font size or increase the screen resolution.

The software used to work, but now fails to run following a recent upgrade:

This is most likely due to an upgrade of the ESL API, which now has new functionality not supported by the driver currently loaded. Reload the ESL drivers, using the latest version, supplied with the upgrade. You can also download the latest ESL drivers from the Support -> Download -> Miscellaneous Files on the COADE website.

The software starts but indicates an error number 5007:

This means that the ESL needs to be updated for the latest version of the software. Click OK on the error message window, when the program starts then go to ESL menu and select "Generate Access Codes". Go to the ESL update page to send an update request.

The software will not start up properly and indicates an ESL (External Software Lock) problem.

Check that the necessary ESL drivers have been loaded correctly. Refer to Assidrv sub-folder underneath the program folder for documentation on the drivers.

To check that the drivers have been loaded properly, from the ESL menu run "Select HASP driver Status".

When accessing a Network ESL from a workstation, the ESL can not be found or get an Error 7 or 31.

First make sure that the license is Successfully transferred from the old HASP ESL to the new HL ESL. If you have not transferred the license refer to these instructions to do so. If you still encounter the same error when accessing the network ESL then you should configure the nethasp.ini file located in the Assidrv sub-folder. Refer to instructions in the file "Esl_RED.txt" in the same directory.

On startup, an ESL Error Message is displayed, either 5346 (invalid service) or 5441 (unknown HASP error).

Both of these errors are caused by the same thing. Later versions of COADE products utilize a new HASP service to reduce the default time-out setting from 36 hours to 1 hour. If your network is still using an older HASP license manager (which does not use this service), HASP error 140 (invalid service) is generated. HASP error 140 maps to COADE error 5346. The latest license manager can downloaded from the Support -> Download -> Miscellaneous Files on the COADE website.

For some installations, an out-of-date COADE Error Database exists, which does not include error 5346. In this case, error 5441 is generated (unknown HASP error).

The solution to both of these errors is to Un-install the older HASP license manager, and install the newer one which came with the latest version of the COADE product you are using (or download from our website).

Back to Top

Graphics:

When attempting to generate an input plot using the HOOPS graphics, the result is an empty window, with only the tool bar buttons (or other graphics issues):

  • Try changing the "color depth" or "resolution" from "Control Panel\Display\Settings".
  • If this doesn`t solve the problem, edit the registry and change one of the HOOPS settings. Here is the procedure:

    Start REGEDIT and open the key HKEY_CURRENT_USER. Next, click on HOOPS. In the right hand pane there is a key named HOOPS_PICTURE with a value of "opengl\window0". Change this value to "msw\window0". Then exit REGEDIT.
  • Try turning off "hardware acceleration".
  • This may be a result of faulty video card drivers, update the video card drivers from card manufacturer`s website.
  • If these steps fail, check your video card`s compatibility with the hoops graphics library at http://www.solidworks.com/pages/services/VideoCardTesting.html and at http://developer.hoops3d.com/graphicscards/graphicscards.html  

When mousing over toolbar buttons, tooltips are not displayed, or they are incorrect. What is wrong?

This is a known Microsoft problem. Here is a link to the Knowledge Base Article that discusses this issue. One known work-around is to avoid the use of OPENGL driver. Start REGEDIT and open the key HKEY_CURRENT_USER. Next, click on HOOPS. In the right hand pane there is a key named HOOPS_PICTURE with a value of "opengl\window0". Change this value to "msw\window0". Then exit REGEDIT.

Starting the program gives an error about Missing opengl32.dll :

This implies that either the graphics drivers (opengl32.dll) are missing or they are an older version. Update the video card drivers, they can be downloaded from card manufacturer`s website.

Back to Top


Program usage errors:

When attempting to open an existing file or add an item, message comes "Program has performed an illegal operation" or about a memory error:

This may be caused by many reasons, here are some of the solutions:

Program Dlls not registered : Run the file NetUser.bat in the program installation directory.

Dll mismatch : Older dll files may be causing an incompatibility, follow this procedure:

  • search for the file Mfc42.dll on the computer
  • right-click on the file to open a menu, then select properties and go to the Version tab. The instance of the file in the Windows/system (or Winnt/system32 for 2000) directory should be the latest version.
  • Rename the files with older versions, that are in directories besides Windows/system.
  • Repeat the above procedure for the files Msvcrt.dll and Msvcp60.dll.

XML Parser Error : Caused by non-existent or older XML parser software on the computer. Download the latest version of MSXML 3 from the Microsoft website and install it.

Graphics related Issue : Follow the steps outlined in the graphics section above, to rectify the issue.

Back to Top

Output Generation errors:

When attempting to send output to MS WORD, the system responds with an error such as Unable to create object. What is wrong ?:

This may be caused by many reasons, here are some of the solutions:

  • Norton Anti Virus Settings - If you are using Norton Anti Virus, go to the "Options" tab and ensure that the check box for Disable Scripting is not checked.
  • Office XP Security - If you are using MS Office XP, there is a new security tab under options. On the Security tab, click the button at the bottom right for "Macro Security". On this dialog, click the tab for "Trusted Sources". At the bottom of this screen, check the checkbox to "Trust Visual Basic Projects".

[Go Back]