Solution is :
Re: Office 97 does not install on XPSP2 system
My company recently had this problem - I discovered the solution while trying to manually register 'htmlmarq.ocx'
You should see htmlmarq.ocx and htmlmm.ocx separate keys. Rename them to something else, ie. htmlmarq.tmp and htmlmm.tmp.
You will now be able to install Office 97, including the HTML option, without incident.
DISCLAIMER: I don't know what this section of the registery does or why these files were apparently blocked (intentionally or accidently), but this solution worked flawlessly for me. If you feel uncomfortable, I'm betting you can rename the keys back to the originals and office will work, but if you need to reinstall, you'll possibly have to rename them again.
Posted:
Thu May 11, 2006 8:57 pm Post subject:
Thank you
Another happy user.
So far can't see advantages to upgrade to XP (for myself, I am installing on a clients new PC) or Office 2003
Seems to have lost more features than gained.
Excel can't save as ASCII comma delimited file! except as non-compatible.
File copy still shows a cartoon, still does not know how long it will take.
File search replaced options for assistant options.
I'm a fairly technical user. How do novice users cope?
I haven't tried this yet, but I am pretty sure it will work. I think I know why it works. My notebook came pre-installed with MS Works. I'll bet that perticular registry key pre-exists because MS Works was pre-installed.
The key cannt be overwritten even by the administrator. I would suspect this is an reg key ownership issue, or something like it. Renaming the key avoids the need for overwriting it -- thus successful installation occurs.
Will let you know how it goes. Yes, it's 2006 and I'm still using Office 97. I'm just too lazy to buy an OEM version.
I haven't tried this yet, but I am pretty sure it will work. I think I know why it works. My notebook came pre-installed with MS Works. I'll bet that perticular registry key pre-exists because MS Works was pre-installed.
The key cannt be overwritten even by the administrator. I would suspect this is an reg key ownership issue, or something like it. Renaming the key avoids the need for overwriting it -- thus successful installation occurs.
Will let you know how it goes. Yes, it's 2006 and I'm still using Office 97. I'm just too lazy to buy an OEM version.
I'm qouting myself (above). I used this work-around, and Office '97 installed perfectly. Fired up correctly too.
I took a look at the permissons on the keys I had to rename. The owners are ADMINISTRATOR and ADMINISTRATORS (a group). Both had FULL rights to those keys -- weird.
It must be the installer then. If it sees a pre-existing key with same name, it won't overwrite it. I guess that makes some sense. The installer should prompt the user that the condition exists, and give him an option to backup the keys, then overwrite them. But, that was 1997 before any one was thinking of WinXX.
Well, a legacy app like this is hard to toss out. Shows how little the newer versions of Office have enticed me.
BTW, I'm an IT guy. I will remember this scenario whenever an install can't access the registry to write a key. Very handy information.
Posted:
Sun Oct 07, 2007 5:12 pm Post subject:
Re: Solution, not just solidarity this time !!
R Burr wrote:
I am deeply grateful to Mr. Ford, whose solution to the "htmlmarq.ocx" problem has put my mind at ease. In short, it worked!!! I also appreciate the disclaimer.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
FAQ
Search
Register
Profile
Log in to check your private messages
Log in
Your solution worked fantastic! I can now create my PowerPoint presentations again! 
