Generic Random Notes
This page provides is used as a sounding board of issues that have come along the way while messing with computers.
To make it esier to navigate the issues, take a look at the index:
- Note #1: Unbound DNSSEC failed to parse trust anchor file
- Note #2: Enable DbgPrint output
- Note #3: UNC vs DOS vs Device vs NT object path
- Note #4: System Error VCRUNTIME140.dll runtime depedencies
Unbound DNSSEC failed to parse trust anchor file
While configuring Unbound to use DNSSEC you may get the error message:
“error: could not parse auto-trust-anchor-file”
After searching the web, the link https://github.com/NLnetLabs/unbound/issues/160 and more specifically comment https://github.com/NLnetLabs/unbound/issues/160#issuecomment-770402282 gave the answer!
You need to comment out the line:
This line is locate at the file
/etc/unbound/unbound.conf. Then, the unbound service must be restarted.
Enable DbgPrint output
DebugView (tool from SysInternals) doesn’t show output from DbgPrint on certain Windows versions. The issue is described in detail in this OSR post.
The workaround is to create the registry key listed below with the DWORD value 0xf
HKLM\SYSTEM\CCS\Control\Session Manager\Debug Print Filter\DEFAULT
UNC vs DOS vs Device vs NT object path
Quick notes on what path is what:
- DOS: C:\Windows\System32\cmd.exe
- DOS Device: \.\ or \?\
- UNC: \127.0.0.1\C$\Windows\System32\cmd.exe
- NT object: \??\C:\Windows\
System Error VCRUNTIME140.dll runtime dependencies
When dynamically linking C/C++ applications on Windows and the target system doesn’t have the appropriate libraries installed, the following error comes up:
The code execution cannot proceed because VCRUNTIME140.dll was not found. Reinstalling the program may fix this problem.
To get rid of this message and run the application, go to the project settings on Visual Studio, select C/C++ -> Code Generation and set Runtime Library to Multi-threaded DLL (/MD) if compiling in Release mode or Multi-threaded DLL (/MTd) if compiling in Debug mode.