K-Meleon :: Bugs

Bugs : K-Meleon Forum

You can talk about issues with k-meleon here. But please, for confirmed bugs, use the bug tracker to report and give feedback on bugs.

Goto: Forum List•Message List•Search•Log In

Your Name:
Subject:

Help information

[quote=siria]
SPAM above...
- - - - - - - - - -

[b]KM 1.5.x[/b] needs 
MSVCR71.DLL, MSVCR71D.DLL: Visual Studio .NET [b]2003 (VC7.1)[/b]
[b]KM 1.6beta[/b] needs  
MSVCR80.DLL, MSVCR80D.DLL: Visual Studio [b]2005 (VC8)[/b]

There's some info about those VCredist dll's in this blog, for me it's too 'high', perhaps others can use it:

[b] http://www.virtualdub.org/blog/pivot/entry.php?id=296 [/b]

[quote]You might be able to get away with not redistributing the DLL, especially since the VS2005 and VS2008 DLLs are typically installed by .NET, but you're taking a big risk by doing this and you really shouldn't rely on it. Microsoft's advice has always been that you need to redistribute the DLL yourself if you are using it, and this is good advice, because you're rolling the dice on the user's machine if you aren't. You don't want to spend time fielding reports like "your popup tool stops working when I uninstall Photoshop."
(....)
In older versions of Visual C++, you could just copy the CRT DLLs next to the EXE. This no longer works starting with VS2005 (=KM1.6beta), where you'll get an error message about the DLL being incorrectly installed. This happens because starting with VS2005 the CRT relies on the manifest system to select and bind the CRT version. The short answer is that you need to copy the appropriate directories from the VC\redist\x86 or VC\redist\amd64 directory instead. In other words, for a VS2005-built application, you should have a directory called Microsoft.VC80.CRT next to the EXE, with DLLs and a .manifest file inside.[/quote]

(PS: Windows98 knows no manifests, and I can't remember for sure, but guess it worked to simply just copy the 2005-dlls into my KM folder :P)[/quote]

K-Meleon forum is powered by Phorum.