Replies

The main part of my question is how to remove the three Tools menu WOPR items, which I did not put there in the first place,. nor was given the choice during the installation.

If they could be removed, then everything else works as it should.

Do they have some “behind the scenes” magic that makes them persist? (That is why I’m asking in this forum.)

(What would be nice, if WOPR is in Excel, would be the WOPR WorkBar — hint, hint.)

No, I don’t have Adobe stuff.

Up until now, changes to my toolbars “took” OK.

Now, even setting that Options->Save->Prompt to save Normal template to “on”, and doing something like changing the print margins and hitting Default, to get the prompt that does save Normal.dot, still the changes aren’t saved, even though Normal.dot has the new date/-time stamp.

What does work is to open the Normal.dot template itself, make the toolbar changes, then Save.
But I haven’t had to do this unitl just yesterday.

I had also removed that Microsoft Hidden Data Removal tool, along the way, as it seems it causes problems.

Update:

Now , after doing the explicit edit to a saved, named, Normal.dot, e.g., Normal 02-06-06.dot, when I go back into Word and do further changes, now they stick.
(In other words, it is working OK again, without having to resort to tricks.)

My questions so far seem to be about Word matters that also involve WOPR. In this case, something is messed up that may not be WOPR’s fauit, as it becomes one of many add-ins.

Update:

I did send a formal request to the WOPR tech support.

In the meanwhile, I found that starting as winword.exe /a doesn’t get the problem.
And starting with a re-named normal.dot, forcing the recreation of normal.dot, also doesn’t get the problem.

Another update:

But, now with the re-created normal.dot, my re-done changes to the toolbars do not stick.
E.g, I remove “Read” and replace “Print” with “Print….”.
When I exit and re-start Word, the toolbars are back to what they were before my changes.

As it turns out, I have all the functionality elsewhere, so it doesn’t matter, actually.

But now the WOPR Commander does not work — could this change be the reason?

Clicking the WOPR Commander icon in the Windows toolbar gets the usual menu, but the three sections of actual command are grayed out.
he only active ones are the Load, Uninstall, Add/Remove itesm a the top, and the Exit Microsoft Word at the bottom.
From About WOPR… through Toggle ‘Lil’WOPR Tools’ Toolbar is grayed out.

How do I fix this?

My practice has always been to save as HTML pages. I wanted to see how Word would handle such files.

I noitce that if I choose the “Open in Browser” option, which is probably more appropriate, anyway, I get a dialog box that warns:

“Hyperlinks can be harmful to your computer and data. To protect your computer, click only those hyperlinks from trusted sources.”

Wonder why it doesn’t give that warning when opening the file into Word.

Yes, that worked.
Thanks.

(If there was a choice of locations given by the WOPR installation, I don’t recall., and I haven’t gotten far enough along in my sudies to figure this out myself.)

C:Program FilesMicosoft OfficeOFFICE11STARTUP

But Word is Working as Designed — the point of the “Medium” setting is to have the user give the “yea or nay” on *every* macro.

(Chalk this up to a former WorPerfect user learning to use Word.)

In the Trusted Publishers tab, the “Trust all installed add-ins and templates” checkbox is already checked.

I guess the operative phrase in the “Medium” choice is “You can choose” — implying a dialog box is inevitable.

If set to “Medium” I get a “Security Warning” dialog box when Word starts warning me that Wopr_ui.dot contains macros, and has a button for me ot “Enable Macros.”

I don’t want ot have to hit this every time Word starts.

That is quite a different story than in the Word books, where it all looks so simple.

Following a link on her site I found that Microsoft Word MVPs PDF file by John McGhie where the advice to hit “Reset” in Format>Bullets and Numbering, which seems a less drastic solution than deleting Normal.dot.

(It is still spooky that even deleting Normal.dot doesn’t seem to give a clean slate, though.)