Anybody been able to view a '.CHM' using minlogon

  • Thread starter Thread starter Smedly Tonker
  • Start date Start date
S

Smedly Tonker

A while ago I posted the question about viewing '.CHM's under XPe and didn't
get any useful feedback. I'm changing my question to "Has anybody been able
to view ".CHM"s under minlogon?". I wondering if viewing ".CHM"s has a
undocumented dependency on the WinLogon component (I am able to view them
when I include this component).


Setup:
XPe using minlogon with most every component I could think of other than
winlogon.

Problem:
Every time I try to view a '.chm' (double click on it in explorer or execute
it on the command line) I get an application event in the event log. The
description is as follows:

The description for Event ID ( 1903 ) in Source ( HHCTRL ) cannot be found.
The local computer may not have the necessary registry information or
message DLL files to dsiplay messages from a remote computer. You may be
able to use /AUXSOURCE = flag to retrieve this description; see Help and
Support for details. The following infomation is part of the event:
http://go.microsoft.com/fwlink?LinkID=45839.

This is what I have done so far to resolve the problem:
- Made sure I had all the compenents for the help system
- Experimented with including the Winlogon component. When I include this
component I am now able to view '.CHM's. I'm wondering if viewing '.CHM's
requires you to have the group policy manager & require you to view '.CHM's
from something other than the system account that minlogon uses?

I belive the problem has something to do with the following knowledge base
article: http://support.microsoft.com/kb/896358, but have not had any luck
with fidning a fix to this problem.
 
Off hand i don't recall if this is true or not, have you searched the
newsgroup archives to see if others have reported this dependency?

Here's a tip when trying to determine if you have a minlogon/winlogon
conflict with a feature not operating properly with minlogon:
- build the config with winlogon and all its dependencies.
- test the feature (chm files in this case).
- if it works, go back to the same config, disable the winlogon component
and add the minlogon component, rebuild the config without running check
dependencies.

If it fails at that point, then you're right, you've found a feature
dependent on a function withing winlogon that was removed for minlogon.

That last step of swapping the components in the config is because some
people build 2 configs and not realize that winlogon starts a dependency
chain which may be bringing in another component satisfying the CHM
dependencies inadvertently, but making it appear it was winlogon. If it was
one of the downlevel dependencies, then swapping winlogon for minlogon would
still allow the CHMs to work.

Good luck. Andy
 
I retry adding WinLogon component as you suggested & then disable it - I'll
post my result when I get time.
 
Back
Top