This content has been marked as final. Show 7 replies
That's the message I would expect if they called a HLP file rather than a CHM. Sounds like that is the problem.
A CHM file is a CHM file, doesn't matter what builds it.
Would there be any reason that Vista might confuse a .CHM for a .HLP file? I think they're using Borland Delphi for the source code in the app. They're also using an XML file to somehow link the app to the help. I don't know the details of how this works, but I'm going to find out.
I have no experience of Vista but I cannot believe that is possible, certainly not without a lot of reports already.
If the CHM works OK independently of your application, then it has to be down to the call.
I'd have to agree with Peter; your developers haven't changed the call from one to HLP.
No, but they neither have changed their way to load the DLL. Probably they're using LoadLibrary with information from the registry. This doesn't seem to work under Vista anymore. The'll have to change to static biding instead.
Thanks for the additional info. I'm meeting with the Developer tomorrow am to see how the app, xml file, and .chm are working together. I'll be sure to ask about the LoadLibrary. Is this something specific to Delphi or is it/was it used for all apps that linked to a .CHM? Found out late yesterday that they're using Delphi 2005.
I'm not a real developer myself, but this is definitely a Windows thing. The application for which this problem has been reported before was written in C++.