Thanks Dan, Jason,
This does help, and given the growth of Evergreen, being able to account
for other screen implementations, etc., make a lot of sense. I just wanted
to make sure I was understanding things correctly.
I'll have to look at git as well--with multiple libraries, this would be
Title: Email Signature
Our two front desk CIRC PC's are:
Windows XP-Pro 32bit Core2 Duo E4600, 2.4GHz, 1024MB PC2-5300
SDRAM, 80gb 7200RPM HD
Purchased August 2008
They worked fine with the previous Evergreen version.
The consortium was upgraded to version 2.3.0
Title: Email Signature
Hi Bob,
Unfortunately this is not the first time I've heard of issues with
Evergreen 2.3+ and memory management.
Previously, memory problems had been reported sporadically even
while we were on 2.0, but since our upgrade to 2.3 the
Title: Email Signature
Good day everybody.
We are in the same consortium as Bob, and running 2.3.1 client.
We have been open to the public for about 2 3/4 hours today, and
our primary circ computers are showing 542,750k memory usage and
641,500k
Evergreen Newsletter / November-December 2012
Happy Holidays! ItÂ’s the last issue of 2012 and the fifth installment
overall. Thanks to all those contributors who continue to make this happen.
The Evergreen Hack-A-Way
By Rogan Hamby
In October we had our first ever Evergreen Hack-A-Way in
Dear Sir,
We are using Evergreen 2.2.2. While searching using a keyword through JSPAC
will display correct results. When the same search is made using TPAC, it
will also show the same number of results.
But the details of the results are displayed incorrectly.
For example We made a search using
