Hi Adrian, Thanks for the detailed directions. I will definitely try using Java 7. All my very best, Rob -- Rob Echlin, Documentation Systems Architect, Wind River From: Oxygen XML Editor Support [mailto:support@oxygenxml.com] Sent: Wednesday, June 05, 2013 11:18 AM To: Echlin, Robert Cc: Oxygen User Subject: Re: [oXygen-user] oxygen does not shutdown when Windows 7 shuts down Hello Robert, If it got stuck at shut down then it didn't have the change to save its options and that would explain some of the inconsistencies you have encountered. As far as we know this shutdown/log off issue was introduced in an update of Java SE 6 (between u22 and u29). This bug seems to have been resolved in Java SE 7, so you can install Java SE 7 on your system and bypass Oxygen's bundled JRE (for v13.2 it's Java SE 6 u29). If you have installed a 32-bit version of Oxygen you need the Windows x86 (i586) JRE, for 64-bit you need the Windows x64 JRE. Note that you can have a 32-bit edition of Oxygen on a 64-bit Windows in which case you still need the 32-bit edition of Java (same architecture as Oxygen). You can download Java SE 7 JRE here: http://www.oracle.com/technetwork/java/javase/downloads/jre7-downloads-18802... To bypass the JVM bundled with Oxygen, quit the application, navigate to the Oxygen installation folder (e.g. C:\Program Files\Oxygen XML Editor 14) and rename the 'jre' folder. e.g. 'jreold'. When you start Oxygen, it will automatically pick up and use your system installed Java VM. You can check the JVM version in Oxygen in: Help > About, System properties, "java.runtime.version" Oxygen does have the version and build number selectable (mouse drag selection) in the Help > About dialog box. Note that Oxygen also has a built-in problem reporting mechanism that composes a report with all the necessary details: Help > Report problem Regards, Adrian Adrian Buza oXygen XML Editor and Author Support Tel: +1-650-352-1250 ext.202 Fax: +40-251-461482 support@oxygenxml.com<mailto:support@oxygenxml.com> http://www.oxygenxml.com On 05.06.2013 16:44, Echlin, Robert wrote: Hi On Windows 7, oXygen 13.2 (both Author and Editor), does not exit when Windows attempts to shut down or log out. I can hit cancel and then I can usually shut them down manually. However, sometimes Author is then in a state of having the main text window all gray, and not responding to input. On a separate note, but possibly related, yesterday I was working on a new "DITA Scenario", and had to start over. I updated some other software and had to reboot. I am pretty sure Author got into that gray text window state at the shutdown. Then, later in the morning I had trouble with builds. The value of ${cfd} passed to the builds was incorrect, Author was instead passing the Editor installation folder in "C:\Program Files". After a few minutes of this, I decided to restart Author. When it restarted, it had renamed the Project File to a name with "temp" in it, and was running without it. I used SVN update to get a working version of the Project File and recreated my new "DITA Scenario". Notes: Installed: Oxygen Editor 13.2, build 2012052412 I generally run both Editor and Author simultaneously (both from the Editor installation), editing XSLT and Ant code in Editor and testing it in Author. Also installed: oXygen 11.2 I use it with other another XML build that needs its own oXygen Framework. I think that's because its "topic" XML type conflicts with the one in DITA. Using: Windows 7, Version 6.1.7601 SP 1 Build 7601 Standalone version, not integrated with Eclipse. My normal logout practice has been to log out only on Fridays, and to close oXygen Author and Editor when I leave work at the end of the day, in case an update restarts Windows. Somewhat relevant tools - ones that hook into Windows Explorer right-click menu with more than "Open with me!": - Q-Dir to replace Windows Explorer. Pretty much eliminates restarting Windows Explorer when it crashes. - TortoiseSVN - TortoiseGIT Why don't software companies make the "version" field selectable and copy-able, in the About box or equivalent? That would be a minor feature request, trivial to do, but useful every time someone reports a bug. Microsoft should do it, not just oXygenXML. All my very best, Rob -- Rob Echlin, Documentation Systems Architect, Wind River +1.613.270.5796 | Skype: rob.echlin.wr _______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com<mailto:oXygen-user@oxygenxml.com> http://www.oxygenxml.com/mailman/listinfo/oxygen-user