WOPR Word Installation Error

Topic

New Reply

I recently had to get a new computer, now using an HP Pavilion a6700f with Windows Vista Home Premium 64 bit with SP1.

I got Office 2003 installed jsut fine, but when I attempted to load WOPR 2003 into MS Word, I ran inot problems. When I try to load WOPR via the Commander button, I get the following error message:

procedure ‘frmWOPRCmdrfintInstall AddIn()’ in Microsoft Word encountered Error # 5180 – Word cannot open the document template.

Anyone know what this means and how to fix it? I had WOPR 2003 running just fine under XP Pro SP2, but there may be some setting I am missing after the reinstall of Office 2003.

Reply | Quote

Replies

I recently had to get a new computer, now using an HP Pavilion a6700f with Windows Vista Home Premium 64 bit with SP1.

I got Office 2003 installed jsut fine, but when I attempted to load WOPR 2003 into MS Word, I ran inot problems.

My first question would be whether anyone has successfully installed and used WOPR 2003 on Vista. As you know, several important paths changed in Vista (e.g., from c:documents and settings to c:users), and it’s possible that WOPR had hard-coded one or more the old pre-Vista paths. If we can rule out Vista as a problem, we can examine whether your privileges or some other consideration might be interfering with the program’s operation.

Reply | Quote

My first question would be whether anyone has successfully installed and used WOPR 2003 on Vista. As you know, several important paths changed in Vista (e.g., from c:documents and settings to c:users), and it’s possible that WOPR had hard-coded one or more the old pre-Vista paths. If we can rule out Vista as a problem, we can examine whether your privileges or some other consideration might be interfering with the program’s operation.

Good point…..has anyone successfully gotten WOPR to load under Vista? One thing I discovered today is that in order to have templates, macros, add-ins etc loaded all the time, they have to be in the Start folder for Word. WOPR does not install itself there, but I’m not sure just putting the install program there will actaully install the macros there as well. I’ll get back to you if I try it and it works.

As for other possibly hard-coded paths, is there any way we might get the macro text to check this out? Maybe Woody can help.

Reply | Quote

My first question would be whether anyone has successfully installed and used WOPR 2003 on Vista.

I very recently upgraded to Office 2007, but prior to that I was using Word 2003 with WOPR installed and at least mostly running. There were some oddities — I could not for the life of me get Word to start without opening and loading the WOPR startup/intro document, for instance. And after I bought and swapped in a new printer a couple of weeks ago (just prior to the Office 2007 upgrade), Enveloper decided to crash on (attempted) launch. But it had been working just fine with my prior printer (a DeskJet 6122), and the rest of the WOPR tool set appeared to be operating more or less normally.

Reply | Quote

I very recently upgraded to Office 2007, but prior to that I was using Word 2003 with WOPR installed and at least mostly running. There were some oddities — I could not for the life of me get Word to start without opening and loading the WOPR startup/intro document, for instance. And after I bought and swapped in a new printer a couple of weeks ago (just prior to the Office 2007 upgrade), Enveloper decided to crash on (attempted) launch. But it had been working just fine with my prior printer (a DeskJet 6122), and the rest of the WOPR tool set appeared to be operating more or less normally.

You did not say if you are running the Vista OS or not. We are wondering if there are hard-coded commands embedded in the WOPR software that are not compatible with Office 2007 and/or Vista, rather than XP/SP2 and Office 2003 (the latest combination I had working).

Have you solved the problem yet? I am also getting the WOPR installation document every time I open Word.

Interesting point about problems after installing a new printer. On my old system with XP/SP2 and Office 2003, I installed several new printers, an HP 6840 and an All-In-One 7410 with no problems. Is your new printer an HYP or some other brand?

Reply | Quote

You did not say if you are running the Vista OS or not. We are wondering if there are hard-coded commands embedded in the WOPR software that are not compatible with Office 2007 and/or Vista, rather than XP/SP2 and Office 2003 (the latest combination I had working).

Whoops — yes, I did have WOPR working under Vista (32-bit) with Word 2003.

Have you solved the problem yet? I am also getting the WOPR installation document every time I open Word.

Actually, I haven’t attempted to install WOPR 2003 under Word 2007; my impression all along has been that the WOPR utilities are pretty version-specific, and I don’t think I’d want to try version-crossing without some very specific guidance from people very familiar with the program’s underpinnings. And I’m not sure there’s an official WOPR tech support presence anywhere on the Web nowadays, outside of whatever informal answers one might find right here. [As far as I can tell, there also wasn’t/isn’t a new WOPR version for Office 2007.]

Interesting point about problems after installing a new printer. On my old system with XP/SP2 and Office 2003, I installed several new printers, an HP 6840 and an All-In-One 7410 with no problems. Is your new printer an HYP or some other brand?

The new printer is a Lexmark X7675 all-in-one; the retailer had it on sale, then offered a heavy additional discount for bringing in an old printer to recycle, so it was a deal and a half.

Reply | Quote

Whoops — yes, I did have WOPR working under Vista (32-bit) with Word 2003.

Hmmmmmmm……I may be having some problems because I have 64-bit Vista.

Actually, I haven’t attempted to install WOPR 2003 under Word 2007; my impression all along has been that the WOPR utilities are pretty version-specific, and I don’t think I’d want to try version-crossing without some very specific guidance from people very familiar with the program’s underpinnings. And I’m not sure there’s an official WOPR tech support presence anywhere on the Web nowadays, outside of whatever informal answers one might find right here. [As far as I can tell, there also wasn’t/isn’t a new WOPR version for Office 2007.]

There is no longer any offcial support for WOPR, and there have not been any versions after WOPR 2003.

The new printer is a Lexmark X7675 all-in-one; the retailer had it on sale, then offered a heavy additional discount for bringing in an old printer to recycle, so it was a deal and a half.

I’m not sure why a printer installation should affect Word or WOPR….but with Windows you can’t always tell what may happen. If you still have an old printer that worked wit WOPR, why not re-install it as the default printer with the Lexmark as a choice you can pick when you print? Maybe WOPR will work with the old printer as default, yet still work if you select the new printer in a particular document.

BTW, I sent an email to Woody Leonhard and I hope we will get an answer to this.

Reply | Quote

Any solution found to this problem? I recently had to reinstall Windows XP on my computer. Prior to the instal, WOPR was installed and working with my version of Word 2003. After the installation and the patches to Windows XP (service pack 3) and Word 2003, I tried installing WOPR and received an error on the installation when opening Word at the point where the instal program tells you to open Word. Some sort of Visual Basic error and a note saying that the macros were disabled in this document; even though my Macro security settings were on Low but after the instal they were on high. When I close Word and re-open it, the WOPR icon is on the taskbar. When I try and load it, I get the error message first noted above. I sent an email to Woody (with the exact wording of the error messages) over a week ago and haven’t received a response. Hoping someone else has or has found a solution.

Reply | Quote

Any solution found to this problem? I recently had to reinstall Windows XP on my computer. Prior to the instal, WOPR was installed and working with my version of Word 2003. After the installation and the patches to Windows XP (service pack 3) and Word 2003, I tried installing WOPR and received an error on the installation when opening Word at the point where the instal program tells you to open Word. Some sort of Visual Basic error and a note saying that the macros were disabled in this document; even though my Macro security settings were on Low but after the install they were on high. When I close Word and re-open it, the WOPR icon is on the taskbar. When I try and load it, I get the error message first noted above. I sent an email to Woody (with the exact wording of the error messages) over a week ago and haven’t received a response. Hoping someone else has or has found a solution.

I have also written to Woody (over a month ago) but never received any reply. I have had almost no replies to this thread. There doesn’t seem to be much interest in WOPR 2003 anymore.

One suggestion I have is that if XP SP 3 is a problem, un-install it. I had problems with SP3 too, and MS Tech Support recommend I uninstall it. Unless you have big security concers, SP3 isn’t all that necessary and it has caused other problems as well. There is a short macro available form MS that will prevent SP3 from being isntalled automatically by Windows Updates

Reply | Quote

Thanks for suggesting removing XP SP3. I removed it and WOPR installed without any problems. I subsequently re-installed SP3 (to correct a few glitches it’s removal caused in other programs) and WOPR continues to work. It appears, then, that SP3 installs something that prevents a fresh install of WOPR but doesn’t mess up a pre-SP3 install of WOPR.

Reply | Quote

Also having this WOPR 2003 / Office 2003 problem of:
“Procedure ‘fmrWOPRCmdr.fintInstallAddIn()’ in ‘Microsoft Word’ encountered Error #5180 – Word cannot open this document template.”

Along with:

Microsoft Visual Basic –

Compile error in hidden module: frmStatusScreen

Run time error ‘5’ Invalid procedure call or argument

Microsoft Word cannot open WOPR *.dot files

I’m running Win XP Pro sp2. Have uninstalled and reinstalled WORD. Have uninstalled and reinstalled WOPR 2003 several time.

Office 2003 is installed to C:Office03.

For a while I was getting the “Microsoft Office Word has encountered a problem and needs to close. …” crash when exiting the program (the error report listed over 30 modules!)

Have cleaned out all Add-Ins shown to be conflictive via Registry trial and error. Did have Acrobat PDFMaker, Dragon Naturally Speaking 9, and OmniPage Pro 15 listed in Registry.

The only thing I am theorizing as being of note recently on my system have been the spate of security updates, especially to Office 2003…? Is this possible?

P.s. Have also been getting In Excel 2003:

Microsoft Visual Basic –

Compile error in hidden module: DistMon

Is this relevant?

Thanks for any help!

Reply | Quote

Compile error in hidden module: DistMon

Welcome to the Lounge!

I can’t help you with your WOPR problem, unfortunately.

The error message you get in Excel is associated with the Adobe add-in PdfMaker.xla. This might be resolved by installing an update to Adobe Acrobat or Norton AntiVirus – see You receive a “Compile error in hidden module” error message when you start Word or Excel.

Reply | Quote

Welcome to the Lounge!

I can’t help you with your WOPR problem, unfortunately.

The error message you get in Excel is associated with the Adobe add-in PdfMaker.xla. This might be resolved by installing an update to Adobe Acrobat or Norton AntiVirus – see You receive a “Compile error in hidden module” error message when you start Word or Excel.

Goede Avond Hans!

Thanks so much for your help! I suspected Adobe Acrobat, but wasn’t sure.

I have just tried completely uninstalling Office Pro 2003 and WOPR 2003 and reinstalling in whole new locations. The Excel error has gone away. But the failure of the full install and functionality of WOPR 2003 has not been resolved, it continues as previously reported.

I will continue to seek an answer.

Thanks again!

Reply | Quote