CHM Security
Dienstag, Januar 19th, 2010Never ending story - CHM security …
Following link may help some admin’s because well described:
http://tinyurl.com/ylkdbza
Never ending story - CHM security …
Following link may help some admin’s because well described:
http://tinyurl.com/ylkdbza
WinHlp32.exe is required to display 32-bit Help files that have the “.hlp” file name extension. To view .hlp files on Windows 7, you need to install this application.
Sure preview at:
Having all the needed files to compile a chm, but when you run the hhc.exe command, the process hangs indefinitely.
We learned that some Windows updates caused the hhc.exe to unregister itself. A batch file that re-registered the server .dlls for the HTMLHelp workshop may work for you. Ran it every Wednesday morning. Rebooting the server also clears this situation.
Belong to Facebook? Want to know what’s happening with Microsoft’s Help 3? Join the “Help3″ Facebook group at:
HHPMod is a software tool created by Sid Penstone for converting WinHelp projects to HTML Help format. It rewrites the project created by HTML Workshop to restore the original Context IDs and the context-sensitive support files.
As a result of a contact from a user with a very large WinHelp project Sid has modified HHPMod to remove the limit on the number of topic files that it will handle. It has been tested with more than 2000 topics, and should handle as many as HTML Workshop can process. As well as handling much large numbers of topic files, it identifies files containing graphical “hot spots” for manual editing, and has fixed some display bugs.
The new version is 2.5.9, replacing 2.4.8. Download from Sid’s web site http://post.queensu.ca/~penstone/ .
When the user clicks an ms-its jump that includes a target in another CHM file, the topic appears at the correct target location, but the css styles are not applied and the graphics do not appear. Clicking refresh loads the graphics and styles.
Here’s an example jump:
<A href=”ms-its:filename.chm::html/TroubleShooting.htm#checklist”>
You can work around the css problem by referencing the css in the <head> section of your HTML files using the ms-its protocol but that doesn’t fix the graphic issue.
The solution is to replace “ms-its:” with the older “mk:@MSITStore:” scheme.
Paul O’Rear [MS] (was a Help MVP) has finally got his Namespace# 2.0 tool released on the MS web site. And it’s free! :-)
A nice MS Help 2.0 diagnostics tool that goes beyond the features of Namespace.exe (free tool with VS SDK). It allows you to view all Help 2.0 namespaces on your system and drill into the files and information associated with each namespace.
Great tool. Very similar features to our FAR H2 Utilities and reads Namespace information a little faster than FAR. Requires .NET 2.0 runtime (which you should already have if VS is installed).
WinHelp is a bit outdated and you may ask for a newer system which is a good replacer for WinHelp. Try the successor to WinHelp, HTMLHelp 1.x, which uses HTML topic files and provides an API for some programmatic access. HTMLHelp can be generated using Microsoft’s HTML Help Workshop tool, which produces a .CHM file but it’s a bit outdated too.
For the current state of play, see this article:
http://www.winwriters.com/articles/news/news_2007_1201.htm
You may also want to take a look at “Converting WinHelp (HLP) to HTMLHelp (CHM)”:
http://www.help-info.de/en/Help_Info_WinHelp/hw_converting.htm
Nikolay Dobrev posted a nice artical on how to create what he calls MS Help 2.x place holders. That is a base collection that you can plug / unplug all your other collections into, and so keep your companies H2 docs gathered together in once place.
Thanks for sharing this - see Nikolay’s Blog