Windows problems
Blue Screen when installing VS.NET 2005 Pro on IBM T42 laptop and a solution
Windows can not shutdown - in case windows forms application failed to respond to System Shutdown (and than it is just NOT being SIGKILLed). Solution.
Running a VC++2005 developed application on another computer, which does not have Visual Studio 2005. Apparently, unmanaged windows application developed with VC++ 2005 has to be distributed with a manifest, as part of windows Side-by-side Assemblies. See detailed explanation on how to do that here. [in case you distribute your app incorrectly you will get "LDR: LdrpWalkImportDescriptor() failed to probe" runtime exception or "Unhandled Exception: System.DllNotFoundException: Unable to load DLL 'YourDll.dll': This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem. (Exception from HRESULT: 0x800736B1)"]
The bug (in Visual studio 2005) I faced here was that when I compiled my app at Debug mode, the created manifest included dependency on non existing Microsoft.VC80.DebugCRT manifest, instead of Microsoft.VC80.CRT. The problems is descried here (in troubleshooting section). Solution: the solution was to distribute a Release version.
Miktex 2.5 problem: While working with Latex in WinEdt, figures were not displayed in dvi viewer and sometimes were not displayed in pdf format as well. The problem had to do with Miktex 2.5 version. This version of Miktex is apparently known to be much slower and have some problems related to Yap (dvi viewer). Solution: I have uninstalled Miktex 2.5 and installed Miktex 2.4 (for example from this site), completely solving the problem (indeed, sometimes progress is performed in opposite direction).
Problems with DNS resolution after enabling IPv6. I have enabled Windows XP Peer-to-Peer Networking Component on XP SP2, to enable IPv6 protocol and Teredo Tunneling. After some time, while browsing the web, I was unable to access some Web sites. I noticed that DNS resolution for those sites was wrong (they were always resolved into 1.0.0.0). This bug is also described in Advanced Networking Pack for Windows XP -> known issues and also in Application Cannot Resolve Some Domain Names. Solution: (1) Disable the Windows XP Peer-to-Peer Networking Component. This was NOT enough. (2) From the command prompt, type “netsh interface ipv6 uninstall” to completely uninstall ipv6 from your machine.
Last updated 19-01-2007