This content has been marked as final. Show 5 replies
The original file resides on my local machine. I need to move this project to a Public drive on our network so that the end-users can access the file.
--> Just to clarify, you are developing the help project on your own PC, then .. you need to put the finished help file out on a public drive..?
When I generate the local file and view it, everything is A-Okay. I then (tried) generated the project to a folder on the Public drive. The .CHM icon copies, but none of the project files.
-->The source project files won't. They are not supposed to. When you publish the help, only the compiled help file (CHM) goes. (The project files are for you, the author. Not for the end user.)
When I view the file from the Public drive, none of the pages display. The HTML Help viewer displays and the TOC is in place, but when I click a topic all that displays in the window is "Page Not Found".
--> How up to date is your PC on Windows hotfixes? There was one that came out in 2005 that broke the viewing of CHM files. Microsoft felt that because HTMLHelp files allow "remote code execution", that they were a security risk. So out came a Windows Hotfix (see MS knowledgebase #KB896358) that resulted in the "page not found" error when trying to launch a CHM from some location other than your local PC. Nice, huh? I am guessing this is the problem you are seeing.
My company's tech support provided a registry patch to correct this for us (in an .exe), so I'm not sure what exactly to change. (And honestly I never really looked into it, either.) Hopefully someone else can chime in about the fix?
The same message got sent twice. I can Edit but I can't delete?
Kathy pretty much covered what you need to know, but if you are going to publish to a network you ought to consider publishing as WebHelp rather than as a CHM, as that is what it was designed for.
I should also ask you, why exactly are you putting the CHM out on a server? Is it just for common access so people can grab it if needed? Or does the application it supports sit on the same server?
If you are only putting the file on the server for common access (instead of emailing it), you might want to inform people to copy it to their local PC before using it. (or ZIP it first to make them extract it locally). Or, if it needs to be on the server to support an application, you could consider generating your output in WebHelp format instead.
Either of these options avoids registry editing!