Found an unusual problem this morning, and managed to help someone in our office resolve it without a support call to KSC. This is related to working with two-monitor setup, and temporarily changing to a single monitor. It will not affect the majority of users most of the time.
SpecsIntact doesn't seem to recognize the change to the monitor setup quite right for dialog boxes that were previously closed in the secondary monitor. It remembers the position the dialog box was last closed, and if that was in the secondary monitor (which now no longer exists), the dialog box is just "out there" somewhere. It appears as though the editor window is locked up, because the dialog box is off the screen and is a modal dialog box, meaning control is not allowed back to the editor window until a selection is made. Trying to end the task with Ctrl+Al+Del gives a message saying the system is waiting for a response from the user. Even after ending the task, restarting SI, updating to latest version - it still does the same thing. In our case we were trying to use the RID (Reference Identifier) button. We also made sure the display properties were set correctly, having the secondary monitor inactive.
Solution: Imagine there is a dialog box you can't see, and you need to somehow move it. Sorry, telekinetic powers don't seem to work with computers. The workaround I used is Alt, Space, M (to invoke the dialog box's move command in the application menu), hitting any arrow key at least once to grab the title bar. At this point it is possible to freely move the dialog box with the mouse to the active monitor, then choose a reference or blank tags, and close dialog box (IMPORTANT: Don't just hit cancel, or you will have to start the process over). Now SpecsIntact remembers that this dialog box was closed in the main monitor.
