Download: Stable · Snapshot | Docs | Changes | Wishlist
Invoking context help from within Windows PuTTY after the PuTTY help files on a system have been replaced has been observed to cause WinHelp to crash.
Since the crash occurs in winhelp.exe, it's almost certainly a WinHelp bug, but perhaps there is something we can do to avoid triggering it. We're out of ideas, though.
The symptoms I observed (on Win98SE, and also on 2000 when I had access to it, IIRC) were:
The precise crash (on Win98SE at least) is: "WINHLP32 caused an invalid page fault in module WINHLP32.EXE at 0167:004099ba." (A Google Groups search finds an apparently unrelated reference, so it's not just us.)
Things I've tried, in desperation:
HELP_COMMAND. Changing from
JumpId, or filling in the first argument (
JI(`putty.hlp',`foo.bar')) makes no difference.
uCommandvalue to give to
HELP_TOPIC_ID= 259 - which would avoid the need to use the
JImacro at all. However, I've had no luck with it ("The topic does not exist. Contact your application vendor for an updated Help file. (129)") A newsgroup post reports it as broken on Win98.
March 2019: this is now moot, as we no longer ship the .HLP file (since vuln-chm-hijack).