Re: Cannot access CHM on a network drive with XP
- From: "Michael Asherman" <mda@xxxxxxxxxx>
- Date: Tue, 21 Jun 2005 15:55:13 -0400
<PD.Lees@xxxxxxxxxxxxxx> wrote in message
news:1119376394.718506.251020@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Gary,
>
> > I have CHM for my application that I have been using for years. Today I
> > discovered that I can open the CHM that is on a network drive with XP
but
> > cannot read any of the contents.
>
> Have you installed the latest Windows security updates in the last few
> days (specifically the 896358 update, described in article
> http://support.microsoft.com/?kbid=896358)? If so, it's likely that
> Windows is now blocking access to the help files as a security measure.
> The contents of help files that are stored on a network drive, or that
> you download to your hard drive from the Internet, are now blocked
> unless you use the workarounds described in article 896358 and also in
> these articles:
>
> http://support.microsoft.com/?kbid=896054
> http://support.microsoft.com/?kbid=902225
>
> To restore access to help files on a network drive, you need to use one
> of the "Method 2" solutions described in article 896054. There are two
> solutions: one that individual users can implement, and another that
> allows network administrators to unblock access to HTML Help files
> across all the machines in an intranet. In each case, it's necessary to
> set the MaxAllowedZone registry value to at least 1 so that the block
> on help files in the Local Intranet zone is removed.
>
> --
> Pete (Microsoft Help MVP)
>
Hi Pete,
I've been experiencing a somewhat different problem with HTML Help for at
least a few weeks. I don't see any indication of having made the 896358
update, but perhaps there is some relationship.
The particular problem I'm seeing is that I get an error when I close a HTML
Help window launched via VFP's context-sensitive help mechanism in my
application. No such problem with VFP's own context-sensitive help under the
VFP Dev. Sys., however. I'm running a VFP6SP5 application on XP Pro SP1 +
Windows Updates as of 3/27/05.
The help file in question is being accessed through a local filing system
path, not across the network. This is the most vanilla sort of HTML Help
integration scenario, purely through VFP, without any ActiveX usage. It
used to work, and then I noticed the problem suddenly started appearing, but
I didn't make the possible connection to Windows Update at the time.
Here are some more details from Microsoft's friendly error dialog, with the
usual offer to send this report to MS:
Error Signature
AppName: foxhhelp.exe AppVer: 6.0.8161.0 ModName: ntdll.dll
ModVer: 5.1.2600.1217 Offset: 00033aed
Can you offer any explanation as to why I'm experiencing this problem, even
with a local help file, and would you please suggest the best way to resolve
it?
Thanks,
Mike Asherman
.
- Follow-Ups:
- Re: Cannot access CHM on a network drive with XP
- From: Lee Mitchell
- Re: Cannot access CHM on a network drive with XP
- References:
- Cannot access CHM on a network drive with XP
- From: Gary Brueggeman
- Re: Cannot access CHM on a network drive with XP
- From: PD . Lees
- Cannot access CHM on a network drive with XP
- Prev by Date: Re: PNG file to BMP file
- Next by Date: Re: clipper and vfp filelocking ignored !
- Previous by thread: Re: Cannot access CHM on a network drive with XP
- Next by thread: Re: Cannot access CHM on a network drive with XP
- Index(es):
Relevant Pages
|
