Har som powell også læst lidt! Det er åbenbart et kendt problem med at hav af løsningsmuligheder.
Every time I start WebSeeker, I get the following error: Microsoft Visual C++ Runtime Error Program C:\\FOREFRONT\\WEBSKR32.EXE Abnormal Program Termination When I click OK the program shuts down. How can I get WebSeeker to run?
WebSeeker is detecting a beta version of Microsoft Internet Explorer. In order for WebSeeker to run you need to install a release version of Internet Explorer or uninstall Internet Explorer completely from your system. To download Internet Explorer, visit <
http://www.microsoft.com/ie/download/> <!------------------------------------------------------------------------------------------------------------------------->
Why do I get a \"Microsoft Visual C++ Runtime Library - Runtime Error!\" when I start my ArcInfo Desktop applications?
Software: ArcInfo Desktop
Version: 8.0.1
Platform: Windows NT
Cause: DLL version If you are receiving this error message, you will have to change your version of the comcat.dll.
Microsoft Visual C++ Runtime Library - Runtime Error!
Program: D:\\arcexe80\\bin\\ArcMap.exe abnormal program termination
Answer:
Some software applications are installing incompatible versions of Ole32.dll and Comcat.dll, causing errors with other software applications such as ArcInfo.
The compatible versions of these dlls installed by Microsoft Windows NT are:
Comcat.dll version 4.71 and Ole32.dll version 4.0
To determine the version of these dlls on your machine, right click on the file names (e.g., Comcat.dll and Ole32.dll), located under c:\\WINNT\\system32, click on Properties, and click on the Version tab. If you do not have version 4.71 of the Comcat.dll, you will need to install it. To download the version 4.71 of the Comcat.dll please visit the following website: <
http://arconline.esri.com/arconline/downloads/ao_/comcat.html> <!------------------------------------------------------------------------------------------------------------------------->
I received the following message when I tried to play a video using the latest Beta client (even if I just played from a local file). What needs to be done to fix this?
***********************************
Microsoft Visual C++ Runtime Library
***********************************
(X) Runtime Error!
Program C:\\IBMISVC\\PROGRAM\\ISCVIEW.EXE
ABNORMAL PROGRAM TERMINATION
[OK]
Please do the following to fix this problem:
1. Go to the MS-DOS Prompt on your WIN95/NT System and change to the following directory:C:\\IBMIVSC\\PROGRAM (NOTE: If you install the VideoCharger client in a different directory then replace C:\\IBMIVSC with the appropria te directory).
2. Enter the following command:regsvr32 mplayer.dll
<!------------------------------------------------------------------------------------------------------------------------->
Question:
When I debug my Java program in JBuilder 3.5 / 4 (often when using a JFileChooser or in a CORBA application) the debugger will crash with the error:
Microsoft C++ Runtime Library
Runtime Error!
Program: E:/JBuilder35/jdk1.2.2/bin/javaw.exe
abnormal program termination
What can I do?
There are two known ways to work around this problem:
Install JDK 1.3 and debug using that JDK (note, add the \"-classic\" VM parameter to your Project Properties | Run tab). See the Help System for information on JDK Switching.
Install JDK 1.3 and copy the following files into the JDK 1.2.2 that was installed with JBuilder 3.5:
jdk1.3/bin/dt_shmem.dll
jdk1.3/bin/dt_shmem_g.dll
jdk1.3/bin/dt_socket.dll
jdk1.3/bin/dt_socket_g.dll
jdk1.3/bin/jdwp.dll
jdk1.3/bin/jdwp_g.dll
Be sure to copy these files into the equivalent place in JDK 1.2.2, e.g. jbuilder35/jdk1.2.2/bin.
<!------------------------------------------------------------------------------------------------------------------------->
When opening a label with connections to a dBase IV database in one of the LLM-WIN(32) print modules, I get the following error message: \"Microsoft Visual C++ runtime error: Abnormal program termination\".
Solution: This error may occur if your dBase IV database has somehow become corrupted. The issue can be resolved by exporting the database from the application it was created in, creating a new structure for the exported records, and then importing the records into the new structure. The steps for performing this operation in the LLM-WIN(32) Database utility are detailed below:
In the LLM-WIN(32) Database utility, open the dBase IV file in question and select Utility | Export To ASCII File. The \"Export Data\" dialog opens.Accept the default options on this dialog box and click Export; the records in the database will be exported to the file indicated in the \"File Name\" box.
With the dBase records exported, make note of the details of the database\'s structure (column names, field lengths, etc.) such that you will be able to recreate the structure exactly after deleting it in the next step.
Once you have the pertinent information needed to recreate the structure, delete the structure by browsing to the folder where the *.dbf file in question is located and deleting it.
Having deleted the old structure, return to the LLM-WIN(32) Database utility and select File | Create New Database. Enter the same name as the old *.dbf file for the new database and click OK.
The \"Create Structure\" screen will be displayed; enter the pertinent structure information such that it matches that of the previously deleted structure and then select File | Save followed by File | Close.
Select Utility | Append From ASCII File; the \"Append Data\" dialog opens. Select the appropriate file type and then click Browse. Browse to the folder containing the file with the exported records, select it, and then click OK. Click Append to import the old records into the new structure.
At this point, the dBase structure has been \"refreshed\" and you should be able to open any label formats connected to it without error.