<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
<channel>
<title>EndNote Users&apos; Group Blog</title>
<link>http://blogs.princeton.edu/library/endnote/</link>
<description></description>
<copyright>Copyright 2007</copyright>
<lastBuildDate>Thu, 10 Nov 2005 12:56:01 -0500</lastBuildDate>
<generator>http://www.sixapart.com/movabletype//?v=1.03</generator>
<docs>http://blogs.law.harvard.edu/tech/rss</docs> 

<item>
<title>AP501: Academic Productivity 501</title>
<description><![CDATA[<p>EndNote/RefWorks documentation with Princeton-specific tips can be found <a href="http://library.princeton.edu/help/en-rw.php">here</a>.</p>]]></description>
<link>http://blogs.princeton.edu/library/endnote/2005/11/ap501_academic.html</link>
<guid>http://blogs.princeton.edu/library/endnote/2005/11/ap501_academic.html</guid>
<category></category>
<pubDate>Thu, 10 Nov 2005 12:56:01 -0500</pubDate>
</item>
<item>
<title>ENDNOTE LISTSERV sign-up</title>
<description><![CDATA[<p>To sign up, go to <a href="http://new-lists.princeton.edu/listserv/endnote-users.html">https://new-lists.princeton.edu/listserv/endnote-users.html</a> and click "Join or leave the list (or change settings)"</p>]]></description>
<link>http://blogs.princeton.edu/library/endnote/2005/05/endnote_listser.html</link>
<guid>http://blogs.princeton.edu/library/endnote/2005/05/endnote_listser.html</guid>
<category></category>
<pubDate>Mon, 09 May 2005 20:51:53 -0500</pubDate>
</item>
<item>
<title>A BUG in ENDNOTE 8.0.2 for WINDOWS (follow these instructions before you update to EN 8.02)</title>
<description><![CDATA[<p>ISI Thomson has confirmed a rather serious bug in EndNote 8.0.2 for Windows.  There's no fix yet--I'm not sure they know what the problem is, exactly.  But there's a workaround that you should perform *before* you update to 8.0.2, and a repair trick (regrettably, it works only part of the time) if you forget or don't hear in time.<br />
If you have already upgraded to 8.0.2 and all's well, you can ignore the rest of this message. <p><br />
Reports so far are that the Mac version doesn't have the bug; it also doesn't have an update out at present (8.0.0 is still the current version).  But the strategy below is a good one for updating any version of EndNote: you don't want to lose your data when it's so easy to prevent problems.<p><br />
<strong>Here's the recommended upgrade strategy:</strong><br />
Before upgrading, open each one of your library files, and export each to EndNote's XML format (File >> Export >> "Save As Type" = 'XML' : you need the XML file b/c it preserves the ID numbers for each reference, which keeps the file in sync with your already-formatted documents). This doesn't harm the original libraries; it makes a new copy in XML format. <p><br />
VERY IMPORTANT!! Make a good backup copy of every .enl library file. The bug damages the library files when trying to open them, in such a way that none of the regular EndNote library repair tools work.  So if the bug bites and you don't have a good backup, and if the repair trick discussed below doesn't work, you've lost the data permanently. <br />
Turn off realtime protection on Symantec Antivirus, and temporarily close (exit, don't just disable) all antispyware programs (these interfere with the installation).  If you see an error message during the upgrade about "MSXML", that means you forgot this step, disabled instead of closing, or missed one of the programs. <br />
Upgrade: Windows users, go to Help >> EndNote Program Updates, then click "OK" and "Next" until the new version installs.  Mac users don't have the built-in updater: you need to go to the EndNote website and download an updater (note: if you have 8.0.0 for the Mac, no newer updates are presently available) <p><ul><br />
<li>Turn Symantec Antivirus Realtime Protections back on <br />
<li>Restart your computer (this should also restart the rest of your antivirus/antispyware protections) <br />
<li>Try to open every library you have. <br />
<li>If a library opens, even once, it's OK.  <br />
<li>If not, create a new, empty library, and import the matching XML file from Step 1. Then replace the bad file with this new one <br />
<li>If you didn't get this message in time, and you now have a damaged library/ies, see the repair trick and the recovery strategy below.<br />
 </ul><br />
Repair Trick: if you upgrade without an XML backup and end up damaging your file, you can find a Mac running EndNote 8.0 (there's no 8.0.2 for the Mac; 8.0.0 is the current version), and try to open the damaged library there.  Opening on a Mac (if it opens) repairs the library, after which it works fine in 8.0.2. This fixes some, but not all, damaged files. <br />
 <p><br />
Recovery Strategy: If the Mac repair trick doesn't work for you and you have a backup copy of your library, you can downgrade back to EndNote 8.0.1 or 8.0.0 (uninstall the new version, reboot, install the original version from your original CD, then reboot again), open an undamaged backup copy of the library and re-upgrade using the directions above.  This works only with a backup copy of the library, as the original has now been damaged and will no longer work even in the older version of EndNote. It's a good idea to make yet another backup beforehand, in case you damage this one, too.<br />
 <p><br />
If these steps don't work for you, contact EndNote tech support at www.endnote.com.<br />
</p>]]></description>
<link>http://blogs.princeton.edu/library/endnote/2005/05/do_this_before.html</link>
<guid>http://blogs.princeton.edu/library/endnote/2005/05/do_this_before.html</guid>
<category>bug fixes</category>
<pubDate>Mon, 09 May 2005 17:56:10 -0500</pubDate>
</item>
<item>
<title>Ask a question</title>
<description><![CDATA[<p>Post your questions to the <a href="https://new-lists.princeton.edu/listserv/endnote-users.html">EndNote listserv</a>; we will re-post some of them to the blog.</p>]]></description>
<link>http://blogs.princeton.edu/library/endnote/2005/04/ask_a_question.html</link>
<guid>http://blogs.princeton.edu/library/endnote/2005/04/ask_a_question.html</guid>
<category>ASK A QUESTION</category>
<pubDate>Fri, 01 Apr 2005 15:10:27 -0500</pubDate>
</item>
<item>
<title>UPDATE PATCH NEEDED for Windows XP</title>
<description><![CDATA[<p>An <a href="http://www.endnote.com/enwinxpalert.asp">update patch</a> is available to address incompatibilities between EndNote 8.0.0* and Service Pack 2 (SP2) for Microsoft Windows XP. (If you are not running Service Pack 2 for Windows XP installing this update will do no harm but is not required.) See <a href="http://www.endnote.com/support/ensupport.asp">this page</a> for ISI's solutions to other problems.</p>]]></description>
<link>http://blogs.princeton.edu/library/endnote/2005/03/solutions_to_pr.html</link>
<guid>http://blogs.princeton.edu/library/endnote/2005/03/solutions_to_pr.html</guid>
<category>bug fixes</category>
<pubDate>Fri, 25 Mar 2005 09:36:11 -0500</pubDate>
</item>
<item>
<title>Welcome to the EndNote Users&apos; Group</title>
<description><![CDATA[<p><strong>Welcome to the EndNote Users' Group</strong><br />
The Office of Information Technology and the University Library are providing and supporting EndNote bibliographic management software for the campus. The purpose of Princeton University's EndNote Users' Group is active information sharing and collaborative problem solving. This blog will be a repository of EndNote questions/answers, detailed documentation, and as well as provide the opportunity for interaction with campus EndNote users and "experts." <br />
<br></p>

<p>While this effort is under construction, feel free to contact members of the<br />
Library EndNote Team with your questions, comments, or suggestions: <a href="mailto:abwright@princeton.edu">Audrey Betsy Wright</a>; <a href="mailto:mwgeorge@princeton.edu">Mary George</a>; <a href="mailto:popescua@princeton.edu">Adriana Popescu</a><br />
</p>]]></description>
<link>http://blogs.princeton.edu/library/endnote/2005/03/welcome_to_the_1.html</link>
<guid>http://blogs.princeton.edu/library/endnote/2005/03/welcome_to_the_1.html</guid>
<category>WELCOME</category>
<pubDate>Tue, 15 Mar 2005 10:59:46 -0500</pubDate>
</item>


</channel>
</rss>