Re: Cannot access CHM on a network drive with XP
- From: "Michael Asherman" <mda@xxxxxxxxxx>
- Date: Wed, 22 Jun 2005 00:34:51 -0400
Hi Lee,
Thanks for the suggestion. I deleted two printer icons relating to HP
DeskJet 500 and HP DeskJet 500C, leaving only a generic ASCII printer, and
then rebooted before testing again. FOXHELP.EXE still crashes as before
upon closing the application Help window. (The Printer icons were
originally set up with the standard HP printer drivers included in Windows
XP SP1, i.e. these were the Microsoft-supplied versions.)
I'm pretty sure that one aspect has slightly improved, though: I can now
launch the app again and bring up its Help after a previous instance of a
failure, without rebooting. Prior to this, Help would stay gronked after a
single such error, and wouldn't be usable without rebooting. I'm not
absolutely certain that nothing else could have caused this improvement, but
it suggests you might be on the right track. Is there more to "uninstalling
the printer drivers" than simply having deleted those icons from my Printers
folder. If so, would you please explain the procedure, as I do not often
have occasion to mess with printer settings.
I'm still unsure how to proceed, not only to fix what's happening on my
development machine, but also to understand if some change may be required
in the setup procedure for distributing my app.
Mike
"Lee Mitchell" <Leemi@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:M%23f9szqdFHA.2052@xxxxxxxxxxxxxxxxxxxxxxxx
> Hi Mike:
>
> I found a case where the same memory offset was caused by a printer driver
> conflict. I would uninstall all the printer drivers and try to reproduce
> the problem. If it does not occur, see if you have LaserJet printer
> drivers loaded.
>
>
> I hope this helps.
>
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> Sincerely,
> Microsoft FoxPro Technical Support
> Lee Mitchell
>
> *-- VFP9 HAS ARRIVED!! --*
> Read about all the new features of VFP9 here:
> http://msdn.microsoft.com/vfoxpro/
>
> *--Purchase VFP 9.0 here:
>
http://www.microsoft.com/PRODUCTS/info/product.aspx?view=22&pcid=54787e64-52
> 69-4500-8bf2-3f06689f4ab3&type=ovr
>
> Keep an eye on the product lifecycle for Visual FoxPro here:
> http://support.microsoft.com/default.aspx?id=fh;[ln];lifeprodv
> - VFP5 Mainstream Support retired June 30th, 2003
> - VFP6 Mainstream Support retired Sept. 30th, 2003
>
>
> <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: Andrew Howell
- 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
- Re: Cannot access CHM on a network drive with XP
- From: Michael Asherman
- Re: Cannot access CHM on a network drive with XP
- From: Lee Mitchell
- Cannot access CHM on a network drive with XP
- Prev by Date: RowColumnChange property always 0
- Next by Date: buffering and sql
- 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
|
