Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
In my external usb harddisk when I click on only the folder names "MISC" I get the error
Microsoft Visual C++ Runtime Library
Program: C:\Windows\Explorer.EXE
This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information.
Other folders open perfectly without the error.I tried changing the folder name but it did not help.I can use windows explorer to open/expand the folder and sub folder on the left.If I open the root of the folder MISC I get the error.Tried sfc /scannow,avg virus scan of the drive,spybot s&d scan of the system.All clean.No new program was Installed recently.Please guide what to do!
This application has requested the Runtime to terminate it in an unusual way.
This occurs when some code linked to the MS C runtime calls the C abort function. Since Explorer doesn't rely on the MS C runtime the most logical conclusion is that you have a misbehaving shell extension. Shell extensions are loaded into the Explorer process and can quite easily wreak havoc like this. I would try this disk on a different machine to test out that theory. Or find a tool that disables shell extensions.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
I have the following line of code in a batch(.bat) file that I have to run:
"c:\Program Files (x86)\Common Files\ArcGIS\bin\ESRIRegAsm.exe" /p:desktop MfeArcGis10.UI.dll
When I run this batch file, the ESRIRegAsm.exe is executed but I get the following error:
Can someone explain what this batch script is doing. From what I understand it is executing the executable with two arguments, however I do not know what the first argument means. Also what does the given error mean? How would I fix it?
First, take a look at Calling esriRegasm manually (outside an ArcGIS-installation).
It looks like MfeArcGis10.UI.dll is a plugin / dynamic linked library (DLL). It is necessary to register components/classes of this DLL in Windows registry under HKEY_LOCAL_MACHINE for usage by ArcGIS. This registry key requires administrator privileges for write access.
So you need to right click on this batch file and click in context menu on Run as Administrator, enter the password for the administrator account, and then the registration process should work.
Note: The batch file must be in same directory as file MfeArcGis10.UI.dll or ESRIRegAsm.exe will not be able to find the plugin file containing the information which must be added to Windows registry.
More useful pages How to register COM components containing also a link to ESRIRegAsm utility. The last page explains option /p:.
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 8 years ago.
Improve this question
While debugging I receive this exception:
A first chance exception of type 'System.Reflection.TargetException' occurred in mscorlib.ni.dll
Visual studio says:
Source information is missing from the debug information of this module.
How can I fix this ?
A first chance exception of type
First chance exceptions are usually OK. Its the second one you have to worry about (it means the first chance was not handled).
Visual studio says: Source information is missing from the debug information of this module.
You might be able to a acquire symbols from Microsoft. See Use the Microsoft Symbol Server to obtain debug symbol files.
Usually, I set up a project to use Microsoft's symbol server. I then debug my project, and Visual Studio will fetch symbols for libraries from Microsoft.
Fetching from Microsoft takes some time. So after the first fetch, I turn off the feature. This way, you get the symbols that are available without the latency for missing symbols for subsequent debug sessions.
I don't know what Microsoft makes available for Windows Phone because I have not done enough development with it. To date, I've only tried porting native libraries through the command line.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
1) If I open a new vb6 standard exe project and don't add any code but just
2) compile right away to the desktop and give it a name containing the word 'Update' it has a UAC shield overlaying it.
And then if I run it I get the UAC dialog.
I have no antivirus except microsoft essentials on my windows vista home basic computer.
If it doesn't have Update (even just leaving out the letter 'e') in the name there's no UAC and no shield on the program's dialog.
I imagine that this is just an oddity on my computer or is there a list of words that trigger UAC?
This has nothing to do with VB6. It's a Windows feature called Installer Detection Technology introduced with Windows Vista. You can read it up on this TechNet page. Basically, installer detection applies to
32-bit applications
Applications without a requestedExecutionLevel
Interactive processes running as a Standard User with LUA enabled
Also mentioned is a check for certain keywords in the filename like "install," "setup," "update," etc. You can easily check this by renaming your compiled executable and/or adding a manifest.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I inherited a headache. I have a small legacy (GUI) app that was developed 10 years ago and the VB6 source code is long gone. It works currently on a couple of old XP PCs and I was asked to see if I could get it working on Windows 7 64bit. Well… that was a no go, so I tried a 32bit version to verify that 64 wasn’t the issue and it didn’t work. So I then created an XP virtual machine and it didn’t work either. The issue is the same on all three environments. You double click the .exe and nothing is displayed but when you look under task manager, it’s there and pegging the CPU.
I downloaded Dependency Walker and it seems that all the required dlls and OCX files are there. Can anyone suggest anything else? I’m really at a loss here. Anything would be appreciated!
The standard approach is to download and run ProcessMonitor, set it to filter just your executable, run your executable and ProcessMonitor will capture what DLLs/Files/ Registry settings are being used by your application.
Have you confirmed you have the VB6 runtime files installed?
http://support.microsoft.com/kb/290887
I'm not sure if they are included in Win7 anymore and they were only in XP in one of the later service packs.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
I just came across this directory and it seems totally a different world.
Anyone knows what's that?
The .NET Framework is an environment (runtime) on top of which code executes. A .NET assembly is a container for code written to execute using the .NET Framework. Assemblies can be either libraries (.dll files) or executables (.exe files).
The .NET Framework has a set of common libraries that can be used by any application which executes under the control of the .NET Framework and the C:\Windows\Assembly folder is where these common libraries are stored.
The reason that the folder displays differently to other folders is because of the special role of this folder as the common location for shared libraries. Microsoft created a special view of this folder that provides easy access to information about the assemblies in that folder as well as providing easy access to operations commonly performed on an assembly such as the Uninstall option in the right-click menu for an assembly.
Using a search engine
It is used to store .NET assemblies,
which can be shared between
application.