aka Google saves
my assthe day (again)
It’s something that has probably been sitting on my system for the past few months but it’s not every day that you have a need to open up a .chm file.
It’s a popular format for lots of documentation on the web now as well as ebooks so I tend to have them saved in various locations around my hard drive. Today though I tried to open a file (located in a network share) and was a little perplexed to see a ‘Page cannot be displayed’ error. Being of an inquisitive nature it was not something I would simply put up with so after a bit of head scratching it was off to Google with the following query:
The number 1 result is from a Nik Cubrilovic based ‘down under’ as we like to say in the Northern hemisphere. It soon became apparent that I was one of many over the last few months who’d been afflicted by the same ‘bug’.
So what caused it and what can be done about it?
Well the common themes seemed to be Service Pack 2 and a ‘#’ in the path on the local computer. I am sorry to report none of these circumstances applied to me so I was really no better off. I’m still unsure why people would choose to use a ‘hash’ in a path but that’s another story.
Further reading down the post reveals a mysterious ‘unblock’ option which can be accessed (in some cases) by right clicking the file > propeties, once again though this did not apply to me (Service Pack 2 only) it was good to know however, these 2 bits of information seemed to suffice for a large number of users but alas I was still not able to view my file.
Then my salvation arrived in the form of a comment posted by Anish, it does involv a little registry hacking but was clear and easy to follow and it worked whooo…
You’ll notice the sub title of this page relates to Google and they didn’t provide me with the fix however, they made the journey from my problem to completion in microseconds and that’s what I am praising.