![]() ![]() Also seems hard to believe based on these CREATED and MODIFIED dates that this latest version from the just-downloaded ZIP would actually be the very latest version of HELP for donor version 727 in August 2016. Seems the dates must have been manually manipulated rather than set by Windows. ![]() NOTE: looking at the Properties screenshot I posted above, I do find it odd that the "created date" for the file is AFTER the "modified date", with both of them being way back in January 2015. They both clearly accomplish the same result and remove the "blockage". Unblock button in right-click Properties dialog for CHM, or Streams utility from command-line. I obviously had completely forgotten about it until deciding to retrieve the latest CHM.ZIP file for donor build 727 today, and thus once again running into this issue.Īpparently either method will work, to make the HELP usable. I'm certain it was this UNBLOCK button solution I had used in the past, years ago. => I am guessing that the "unblock" button is invoking the STREAMS command (or its equivalent) on the specific file involved, for which the Properties dialog is being presented. Īnd in fact, when I went to the originally expanded version of the CHM file (from its delivery ZIP) and right-clicked on it, sure enough just as predicted there was an UNBLOCK button at the bottom of the dialog window that I could push:Īnd sure enough, after pushing the UNBLOCK button (the description area then went gray, and actually was not presented at all after closing and re-opening the right-click Properties) I was now able to fully use Help. Try the HHReg utility or read this technical note from the Microsoft Knowledge Base. chm help file, then go to his properties by clicking the file with the right mouse button. This button is not available in all systems though. Right click on the file then go to its properties and click the "unblock" button. In some cases, you can have access to an "unblock" button in the properties page of the help file. Make sure your help file isn't in a path with symbols such as "#" (sharp). Launch help file from local drive and not from a network path or via a mapped networked drive. When viewing your CHM documentation, Microsoft's HTML Help Viewer is showing an error page saying either that: Also the accepted 'Solution' did not resolve the issue for me.Actually, this problem had seemed familiar and I was certain I'd run into it before, although I certainly didn't use Streams to resolve it.Ī bit more research shows that it has already been anticipated in the README for FCXE: Just food for thought and I did not have to 'Unblock' any files. Another method that worked was mapping the path to the network locally by using mklink /d (symbolic linking in Windows 7 or newer) but mapping a network drive letter (Z: for testing) did not work. If the 'Unblock' method does not work, or you do not see the option, this should. Since the introduction of Microsoft Security Update 896358 in 2004, chm files located on a server will not work properly, most commonly clicking a topic in. Once you confirm, you can deploy if needed. When you pressed F1 or selected Help from the Help menu, you received the following error message: Cannot find help file: acad.chm Solution This error can. I suggest try the least and test it, then add if needed. The user may have not closed the original file or something like that. CHM helpfile is only visible if stored on the C: drive. xalspaero Created on Octocant open CHM file on win10 I have an old CHM file that wont open. It's probably not required at all but when I added it, it fixed the problem. "UrlAllowList"="\\\\ \\\\\* \\ies-inc.local As an additional note, weirdly the "UrlAllowList" key was required to make this work on another PC but not my test one. This is how my registry looks (I wasn't sure it would work with the wild cards but it seems to work for me): Windows Registry Editor Version 5.00 Most articles I read tell you to set the MaxAllowedZone to '1' which means that local machine zone and intranet zone are allowed but '4' allows access for 'all' zones. There are apparently different levels of authentication. It appears a lot of people have this problem but were unable to track down a solution. ![]()
0 Comments
Leave a Reply. |