Update: Annnnd, when I resumed work after lunch (no reboot) it worked to double-click the BOOK file to open it.
Suspicious, I rebooted my system... and it doesn't work again (same sequence as in previous email, below). It's off a network file share, but that shouldn't be the problem because (a) I open a folder on the share to find the BOOK file to double click it without a problem, and (b) I've worked the exact same way for over a year, on the same network, share, and files without a hiccup. I got NO clue what to do.... David -------- Original Message -------- Subject: Cannot find the file named... From: "David Artman" <[email protected]> Date: Mon, February 25, 2013 10:33 am To: "Framers" <framers at lists.frameusers.com> Hi, all; Latest, out-of-the-blue functional bug on FM8.0p277, Win 7: 1) Navigate to working folder for project [just like every day]. 2) Double-click BOOK file. FrameMaker opens, them immediately displays the following message: "Cannot find the file named __. Make sure that the file exists. 3) Click OK on that message. 4) On the FrameMaker menu, click File > 1 [file_name]. FrameMaker immediately displays the same error message as in step 2, then FrameMaker displays the Open dialog, at the project folder root (i.e., last folder to which I wrote files). 5) Double-click the BOOK file in the Open dialog. The BOOK file opens in FrameMaker. Same behavior if I try to do the above with a standalone FM file. I have, over the course of days, installed software that does various things to interface with the hardware that I am documenting, so it's possible something went pear-shaped with Windows. I'm *inclined* to blame FM because (a) Windows knows the BOOK should open Frame, and sends it to Frame, and only THEN does Frame claim not to find it; and (b) it's FrameMaker 8. By Adobe. So, yeah.... Any ideas what I could do to repair whatever's gone wrong? I'm comfy manipulating INI file and the Windows Registry. But I can't reinstall FM8, though I *have* rolled back and reapplied all patches (p266 is 155 MB, so I imagine it's pretty thoroughly updating everything). This problem persists through daily reboots. Thanks in advance; David
