Tag Info

Hot answers tagged

3

First note that DLLs methods and static constructs are part of the stack footprint of the process, and thus their memory is not dynamically allocated, so breaking things up with additional dlls will not reduce your actual ram requirements. Process memory can be measured using the Private Bytes (the full memory footprint of the process, minus any shared ...


3

Install the Windows 8.1 SDK and run this cmd: MKDIR %userprofile%\appdata\local\temp\dlls XCOPY "C:\Windows\System32\dwm.exe" %userprofile%\appdata\local\temp\dlls XCOPY "C:\Windows\System32\dwmcore.dll" %userprofile%\appdata\local\temp\dlls XCOPY "C:\Windows\System32\uDWM.dll" %userprofile%\appdata\local\temp\dlls SYMCHK /r ...


2

Explanations Like you said, they did not update it when they ported the drivers to Windows 8. That said, it’s also possible (possibly even likely) that they chose to remove it from the Windows 8 driver because of a bug and/or incompatibility with Windows 8 and/or due to Windows 8’s different interface design (you normally don’t see the notification-area ...


2

Other people experiencing similar have said (although this quote is for VS2010) "...removed the .suo; .ncb; and user project file, then restarted the solution and it fixed the problem for me." Source Reinstallation If the problem is with running a program in debug mode, then there is a KB article/fix for this. The details of this fix are copied here ...


2

I'll go for: Ntdll.dll, ntoskrnl.exe, user32.dll, system32.dll, hal.dll and you can of course just delete key executable files in system32... gl, Refael


1

run cmd as administrator and run sfc/scannow. Looks like corrupted system file.


1

The error message appears because Grit uses the InterlockedCompareExchange64() function that is only available starting with Windows Vista and Server 2003 – that is, Windows XP does not yet have it. Rebuilding Grit on a Windows XP system may help, if it was written to choose from alternative versions of the same task at compile time. (For example, it is ...


1

the regsvr32 located in SysWow64 folder is for 32bit dll It's a strange naming from microsoft: WOW64 means "windows [32bit] on windows 64bit" the one located in system32 is for 64bit dlls.


1

The error code you got stands for ERROR_MOD_NOT_FOUND, some dependent dll is missing on your system that both of those two programs rely on. One tool I have used a lot for finding problems like these is Dependency Walker, it analyze the dll or the ocx and tell you what other dll's it depends on. If it can't find it by static analysis you will need to do ...


1

I had the same issue and all of provided instructions did not work. What worked for me is to finish all the updates.


1

Ok, after more searching, I found through Dependency Walker that the dll is referencing the API-MS-WIN-CORE-SYNCH-L1-1-0.DLL through the chain of other dlls. Based on this information from Microsoft, it doesn't look like this is compatible as is. It seems that I would have to recompile the DLL in order to make this work changing the references. Solution: ...


1

This means that several programs can use the same DLL without having it loaded several time in the RAM (this would causes a very high memory usage if you have the shell32.dll loaded 50 times). MS explained it here in this video: Defrag Tools: #7 - VMMap http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-7-VMMap#time=03m35s


1

There are different techniques to share memory with different outcomes: There's a program level shared memory (like IPC or dbus) for inter-process communication. Many different programs can use it to communicate and share data. There's a system level shared memory, where system linker can hold libraries that were used by more than one process. There's a ...


1

Installing the Microsoft Visual C++ 2010 Redistributable Package will fix the issue. It is advisable to install the Microsoft Visual C++ 2010 Service Pack 1 Redistributable Package MFC Security Update after that. (source)


1

Analysis I don't have the same hardware nor I use Windows 8.x, so what I'm going to provide is some static analysis. Strings At first I scanned the 64-bit mvs91xx.dll library file using the Strings utility. Strings just scans the file you pass it for UNICODE (or ASCII) strings of a default length of 3 or more UNICODE (or ASCII) characters. ...


1

From the message "The Ordinal 325 could not be located in the dynamic link library SHDOCVW.dll", it is possible that this DLL is corrupted, so maybe other system DLLs as well. Try sfc /scannow to see if it finds anything. If it does, you will need an XP SP3 boot CD to correct the errors.


1

Looks like your IE is broken from the shdocvw.dll error reported by NotePad. You can reinstall the current Windows service pack or upgrade your IE version to get IE-related files to a good state. Suggested reading: How to repair or reinstall Internet Explorer in Windows


1

Consider That The Originals May Have Been All Zeros It simply may be a misconception. Please look at other dll's and see if has happened to all of them or has happened in some certain situations. dll's are simply files and so will be treated the same. also look to see if some restoration isn't still in progress or something weird like that because it may ...


1

The biggest problem with "Heartbleed bug" will be on the server side (websites). Though clients are affected too, it is much less possible that someone will misuse that. You can use Indy original SSL distribution from http://indy.fulgan.com/SSL/ You can find "openssl-1.0.1g" here which are the latest and fixed libraries. It should be fully compatible with ...



Only top voted, non community-wiki answers of a minimum length are eligible