Thanks for that, though the thread appears to be addressing an issue with importing Word documents into your RoboHelp project, which I'm able to do without applying the fix.
In that thread, mcolegro's post from Jan 16 2014 had interesting info about the InstallRoot key in the registry. I could make sense of it, and after replicating the solution I re-installed RoboHelp 11 (in case the RoboHelp installer would pick up on the new InstallRoot key data).
Unfortunately, using the registry to point RoboHelp towards the newer version of Word didn't resolve the "Cannot find Word when generating Printed Documentation" issue. Mind you, I don't have an older version of Word installed, though there was a framework of keys to which I could logically add the InstallRoot key...
...and point it to where Word 15 (2013) was installed).
1 person found this helpful
Using the Process Monitor to analyze RoboHelp’s Registry activity, I note the following:
When attempting to print documentation, RoboHelp is failing multiple attempts to read keys from:
I believe RoboHelp is seeking to read keys from the wrong location, which is actually located here:
However, looking at values stored at (B), these appear to be related to RoboHelp 10, which means that copying those key values to (A) does not entirely make sense. For example, (B) has a DLLPath field that points to:
C:\Program Files (x86)\Adobe\Adobe RoboHelp 10\RoboHELP\ExternalComponent.dll
…and RoboHelp 11 does not have an ExternalComponent.dll module.
Regardless, I performed a test by copying the Components\16 fields from (B) to (A), and then I observed whether RoboHelp demonstrated any differences in behaviour. There was no significant change, so I reversed my copying of the Components\16 fields.
Aside from copying the fields, there is a Buffer Overflow error (with Length = 144) that is unusual. It occurs when RoboHelp seeks to read RegQueryValue from the following key:
HKLM\SOFTWARE\Wow6432Node\Adobe\RoboHelp\11.00\MontereyFrame\Open\WinHelp File (*.hlp)\DLL
…the value for which points to:
C:\Program Files (x86)\Adobe\Adobe RoboHelp 11\RoboHTML\hlp2html.dll
(which is a total 68 character length, and I confirmed that there were no extra spaces)
(144 character length appears to be recurring path length being sought, for example the Path for various editors that RoboHelp can potentially use).
Note: As has been mentioned previously, mucking about in the Registry is not a normal activity. I'd rather not be doing this, though I'd like to see the issue resolved. So I'm posting notes here that I can at least refer to Adobe Tech Support.
Eager did you get this matter resolved?