Effectively Remove Trojan, Virus, Spyware from Windows Startup

I’ve been helping people to remove trojan, virus, spyware and unnecessary programs from Windows startup for many years now. It’s very interesting because you will learn the Windows startup methods from finding out where will the program be hidden. The old method by running System Configuration Utility(msconfig) doesn’t work so well now because there are many other ways to start the programs when Windows is being booted up without being displayed in System Configuration Utility(msconfig). Even some smart trojans are hidden from Task Manager, Processes tab.Spywares, it is by nature to create random filenames and file sizes so avoid detection. That is why you always need 2-3 antispywares to completely remove spywares. Using anti-spyware software such as Ad-Aware, SpyBot and XoftSpy is good to identify spyware files but I can assure you that it’s not smart enough to 100% completely remove trojan, virus or spyware from startup. For example, one of my friend’s computer has been infected by spyware because everything is so slow. I find it hard to even download, update or copy the anti-spyware scanners to the computer. However, I manage to copy the updated anti-spyware software to the computer, scanned it, and removed the potential infections. I restarted the computer and it is still slow. That shows that spyware is still being ran during startup.I am going to show you one of the best way to remove trojan, virus or spyware from startup but it requires you have at least some knowledge in computers, otherwise you’ll be removing the wrong startup programs which may cause the Windows to be unbootable.HijackThis is a general homepage hijackers detector and remover. Hijackers are spywares, trojans and viruses. They infect your computer without your knowledge.
Initially based on the article Hijacked!, but expanded with a lot of other checks against hijacker tricks. It is continually updated to detect and remove new hijacks. It does not target specific programs/URLs, just the methods used by hijackers to force you onto their sites.As a result, false positives are imminent, and unless you are sure what you’re doing, you should always consult with knowledgeable folks from forums before deleting anything or you can go a Google search on the filename to know if that file is a virus.There are 2 types of scan methods.1. Do a system scan and save a logfile.- This is for newbie who doesn’t want to mess around with their computers. It will scan your computer and create a hijackthis.log file which you can paste it to forums and request for help.2. Do a system scan only.- Same as first method but it doesn’t create log files. Mostly for advance user who would like to troubleshoot themselves.Again I would like to stress out that IF you’re unsure what to fix after running the scan, please request for help in forums. Simply removing any startup programs would result in an unbootable Windows.

UGC NET June 2009 Library & Information Science Questions
5×15=75
1.What is WIPO?
Explain its functions.
2.What is ‘Right to Information Act’. Explain its essential ingredients.
3.Mention the important publications on IASLIC.
4.Distinguish between print and electronic source information.
5.Enumerate the key parameters for evaluation of web resource.
6.Define ‘Digest’ and explain the steeps involved in its preparation.
7.What is RDA explain its initiatives.
8.What are the standards devised for exchange of electronic information?
9.Explain the concept of information consolidation and repacking.10.What is Bandwidth?11.Describe application of XML.
12.What is Web Browser?
13.State the disingvisty feature of DOI and URL.
14.Explain ‘Sampling error’ with examples.Distinguish Digital Library from Virtual Library.
15.Distinguish Digital Library from Virtual Library.
15×5=75
1.Discuss the economic and social implications of information in the knowledge Society.
2.Enumerate the stat which has enacted Library legislation in India so far.
3.Define a database. Describe the various types of database with suitable examples.4.Examine the need for classification and cataloguing in digital era.5.Explain the different bibliographic standards available for library practices.
40×1=40
1.The emerging trends in ICT have revolutionized the pattern of information seeking and use in libraries. How information literacy programmes help to improve the usage of information.OrKnowledge Management is a fate of corporate sector. State the extent to which the contemporary librarians can claim as Knowledge Managers.
Or
The scenario of collection building underwent sea changes with the advent of electronic resource. In the light of the statement discuss the collection development policy required in the 21st century.

Toolbar for UGC-Infonet Digital Library Consortium, INFLIBNET's New Website

UGC Chairperson, Prof. Sukhdeo Thorat has launched INFLIBNET's new website on 23rd June 2008. Archives of the Annual Reports, Newsletters, and other documents are available for downloads. INFLIBNET has also developed toolbar for UGC-Infonet Digital Library Consortium. The toolbar is available for free download at the INFLIBNET website under download link. It has a list of publishers and the resources available for access to the universities. URL of the website is http://www.inflibnet.ac.in

Koha 3.0.0 RC1 Released

Koha 3 is the next-generation release of the award-winning Koha open-source integrated library system.
Release Notes for Koha 3.0.0 RC1
Koha 3 is the next-generation release of the award-winning Koha open-source integrated library system.
You can obtain Koha 3.0 RC1 from the following URL: http://download.koha.org/koha-3.00.00-stableRC1.tar.gz
These Release Notes cover What's New in Koha 3, information about the new Revision control system (Git), and Version-release process, pointers to Download, Installation, and Upgrade documentation, a brief introduction to the new Templates, a call to Translation and Documentation writers, and finally, Known Issues with this version.
What's New in Koha 3?
1. Zebra plugin - Zebra is a high-performance, general-purpose structured text indexing and retrieval engine. It supports large data sets (tens of millions of records) and includes support for SRU, Z39.50 and several query languages: CCL, CQL, and PQF. For more information about Zebra, please see: http://indexdata.dk/zebra
Koha's new search engine, built on top of Zebra, supports features such as relevance ranking, field weighting, truncation, stemming, use of fuzzy operators, language-specific indexing, sorting, etc.
Indexes are updated in real-time with circulation transactions, enabling limits by availability and statuses.
Faceted refine-by limits are available from both staff and opac interfaces.
For libraries that don't want the overhead of maintaing Zebra, Koha 3 ships with a NoZebra option, in which bibliographic and authority data is indexed in the RDBMS.
2. New installer - based on the common Perl module ExtUtils::MakeMaker, the new installer makes it a snap to get Koha running on just about any platform.
The installer comes complete with a Developer's Toolkit target ('dev') that can be used to get a development environment linked directly to revision control, to support rapid prototyping and an agile development process.
3. Standard APIs - Koha 3 supports a number of important library search and retrieval standards and microformats, such as SRU/W, Z39.50 (http://www.loc.gov/standards/sru/), UnAPI (http://unapi.info/) and COinS/OpenURL http://www.niso.org/committees/committee_ax.html http://ocoins.info
Also supported is the popular Internet standard: OpenSearch (http://opensearch.a9.com/) created by Amazon's A9.
Records are stored internally in an SGML-like format and can be retrieved in MARCXML, Dublin Core, MODS, RSS, Atom, RDF-DC, SRW-DC, OAI-DC, and EndNote; and the OPAC can be used by citation tools such as Zotero. Creating new export formats is a trivial exercise in writing XSLT; records can be passed through XSLT transformations either directly out of the index, or via a separate parsing function.
To retrieve and interact with Circulation and Patron data, Koha 3 includes support for 3M's Standard Interchange Protocol (SIP2), using the OpenNCIP libraries
There are also an ever-expanding set of native REST APIs to handle interoperability with external tools such as third-party cataloging clients. These APIs provide authentication as well as add/edit/delete control over bibliographic data within a Koha system. For more information, see: http://wiki.koha.org/doku.php?id=en:development:web_services
Koha 3 also includes pluggable authentication - easy integration with LDAP and Active Directory via the Auth_with_ldap module.
The Amazon.com module can be enabled to enrich bibliographic data with jacket covers, professional reviews, ratings and comments from Amazon users, as well as point to 'Similar Items' within the catalog. OCLC's xISBN, and LibraryThing's ThingISBN can likewise be enabled to provide an 'Editions' tab on item detail pages. New with Koha 3 is service throttling for these services, to keep within subscription limits.
4. Cross-platform, multi-RDBMS, Web-server agnostic - Run Koha on the platform of your choice: Linux, Windows, Mac OS X, FreeBSD, Solaris. Koha 3 also includes better support for multi-RDBMS (MySQL 5.0 and PostgreSQL), and runs under Apache2, IIS, or the web server of your choosing.
5. Multi-lingual support - Koha was designed from the ground up for multilingual libraries. Koha 3 can handle Chinese, Japanese, and even right-to-left languages such as Arabic and Hebrew with ease (BiDi).
Koha's index engine (Zebra) can handle record formats containing any UNICODE compliant script, such as Arabic, Chinese, Hebrew, Japanese and Korean. Zebra has this support via the ICU libraries created and maintained by IBM.
You can translate Koha into your language using the built-in translation tools, or by visiting translate.koha.org
6. New templates - Koha's staff and patron interfaces are developed with a template system that's easy to theme. The default templates are composed of 100% valid XHTML and CSS. Koha aims to meet or exceed U.S. Government Section 508 and W3C's WAI-AA standards for sight and motor impaired individuals. All Javascript usage comes with fallback modes that work in any web browser.
7. Koha 3 has quite a few new modules, as well as enhancements to existing modules, including: news writer, label creator, calendar, OPAC comments, MARC staging and overlay, notices, transaction logs, guided reports with a data dictionary and task scheduler, classification sources/filing rules.
Revision Control
With Koha 3, we've started using a new distributed revision control system called Git; it's the same system in use by many other projects, including the Linux Kernel. To learn more about how to develop Koha using Git, please see the Wiki page: http://wiki.koha.org/doku.php?id=en:development:git_usage
Version Numbering
With Koha 3, version numbering has been changed to use a method similar to Perl's:
major.minor[.revision[.build]]
major: one digit
minor: two-digit
revision: two-digit
build: three-digit
This release of Koha 3.0 is versioned 3.00.00.094. Every database change or significant enough code change requires an update to the 'build' number, and developers will be able to easily upgrade their systems using the built-in updater.
Koha 3.0 Release Schedule
This release of Koha 3.0 includes the following general improvements over the beta release:-
General Bugfixing (everyone)
New messaging enhancements (acmoore)
Lots of nomenclature cleanup
New testing suite (acmoore and gmcharlt)
SIP2 and LDAP fixes (atz)
Improved I18N/L10N, lang detection (kados)
Additional translations
Lots more, consult git.koha.org for the complete changelog
This release candidate of Koha 3.0 will be followed by a stable release. Subsequent releases of 3.0 will be bugfix releases, and won't include any new features.
New features will be available in Koha 3.2 and subsequent releases.
Upgrading from a Previous Version of Koha
The upgrade process from a previous version of Koha is documented on the Wiki at the following page:
Upgrading from 2.2 or earlier version: http://wiki.koha.org/doku.php?id=22_to_30
Upgrading from a previous version of 3.0: Please consult INSTALL files for details on how to upgrade
Templates
You may have heard that the templates for Koha 3 have been re-skinned; there is also the start of a template style guide on the Wiki: http://wiki.koha.org/doku.php?id=en:documentation:templates_style_guide
Kudos to Owen Leonard and the Nelsonville Public Library for their contributions!
Translations
Koha 3.0 (this release) currently has complete translations for the following languages:
OPAC: de-DE (German), el-GR (Greek), es-ES (Spanish), en (English), fr-FR (French) hu-HU (Hungarian), it-IT (Italian), pt-PT (Portuguese), tr-TR (Turkish), ru-RU (Russian), uk-UA (Ukranian) zh-Hans-CN (Simplified Chinese in China), zh-Hans-TW (Simplified Chinese in Taiwan)
Staff Client: fr-FR (French), en (English), hy-Armn (Armenian), ru-RU (Russian), uk-UA (Ukranian) zh-Hans-CN (Simplified Chinese in China), zh-Hans-TW (Simplified Chinese in Taiwan)
Additionally, Koha 3 (this release) has partial translations for the following languages:
OPAC: am-Ethi (Amharic), bg-Cyrl (Bulgarian), fa-Arab (Persian), fi-FI (Finnish) gl (Galego), he-Hebr (Hebrew), id-ID (Indonesian), ja-Japn (Japanese), kn-Knda (kannada), ko-Kore (Korean), mi-NZ (Maori), pl-PL (Polish), tet (Tetum)
Staff Client: de-DE (German), el-EL (Greek), es-ES (Spanish), hu-HU (Hungarian), ja-Japn (Japanese), tr-TR (Turkish),
The Koha Team welcomes additional translations; please see http://www.kohadocs.org/usersguide/apb.html for information about translating Koha, and join the koha-translate list to volunteer: http://lists.nongnu.org/mailman/listinfo/koha-translate
Documentation
User-contributed documentation for Koha 3 is available on the Koha Wiki (http://wiki.koha.org). The Koha Team welcomes documentation contributions; please join the Koha-devel list to volunteer: http://lists.nongnu.org/mailman/listinfo/koha-devel
Known Bugs
Known bugs are documented on the Koha wiki: http://bugs.koha.org and at the 3.0 RM's QA notes Wiki page: http://wiki.koha.org/doku.php?id=en:development:qanotes3.0
© 1999-2008 The Koha Development Team & Katipo Communications Ltd.

Websites of Library Associations in India

1. Indian Library Association [ILA]
http://www.ila-india.org/

2. Indian Association of Special Libraries and Information Centers (IASLIC) http://www.iaslic1955.org/

3. Society for Information Science [SIS] Not Updated
http://sis-india.netfirms.com/

4. Developing Library Network (DELNET)
http://delnet.nic.in/

5. Information and Library Network (INFLIBNET)
http://www.inflibnet.ac.in/

6. Kerala Library Association
http://www.keralalibraryassociation.org/

7. Gujarat Library Association
[Gujarat Granthalaya-Seva Sangh - GGSS]
http://ggss.org.in/

8. Madras Library Association
http://www.accel-india.com/mala/

9. Bengal Library Association
[Bangiya Granthagar Parishad]
http://www.blacal.org/

10. Delhi Library Association [DLA]
http://www.dlaindia.org/

11. Ahmedabad Library Network (ADINET)
http://www.alibnet.org

12. Bombay Science Librarian's Association (BOSLA)
http://www.bosla.org.in/

13. Mysore Library Network (MYLIBNET
http://www.mylibnet.org/

14. Indian Theological Library Association
http://www.geocities.com/itla_in/home.html

15. Society for Advancement of Library and Information Science [SALIS]
http://autolib-india.net/salis.html

Microsoft to offer free Repository software

by Christopher Blanchard
Below is a post from Open Access guru Peter Suber, excerpting a blog post from Savas Parastatidis, talking about Microsoft's plans to offer free repository software. Any thoughts?? . . .
Savas Parastatidis, Microsoft and "Research-Output" Repositories, Savas:web, March 24, 2008. This excerpt omits several paragraphs of text, three images, a code snippet, and a video of a prototype. See the original for a fuller picture.
What is Microsoft going to show at the Open Repositories 2008 conference in few days? Why is the entire "scholarly communications" section of the Microsoft Research Technical Computing team going there? ...Lee Dirks, Alex Wade, Santosh Balasubramanian (an honorary member!), and I are going to be there to interact with the community and to showcase —for the first time externally— our "research-output" repository platform....
Our goal is to abstract the use of underlying technologies and provide an easy-to-use development model, based on .NET and LINQ, for building repositories on top of robust technologies.
The platform has a "semantic computing" flavor. The concepts of "resource" and "relationship" are first-class citizens in our platform API. We do offer a number of "research-output"-related entities for those who want to use them (e.g. "technical report", "thesis", "book", "software download", "data", etc.), all of which inherit from "resource". However, new entities can be introduced into the system (even programmatically) while the existing ones can be further extended through the addition of properties.
This means, obviously, that arbitrary relationships between resources can be established. Our platform comes with a number of "known" predicates (e.g. "added by", "authored by", "cites", etc.) but it is extensible to accommodate any new predicates developers want to introduce....
Our system will be the back-end of a future version of the Microsoft Research web site. After Milestone 1, we’ll focus on an immediate public release, which is going to be free for download by the community. In fact, we are seriously thinking of even releasing the code to CodePlex for the community to take and extend....
We are already well into the process of developing a collection of tools and interfaces on top of the platform as tangible examples of how to use it. We already have implementations of OAI-PMH...and working on Search and a simple Web UI. We are also working on WPF and Silverlight tools for visualizing the relationships between the resources within our repository....
At the Open Repositories 2008 conference, we will formally unveil our work in advance of its official release and initiate interactions/exchanges with the DSpace, EPrints, Fedora, and other players in the repository community. This is crucial to us because —like every other project our group undertakes— we are intensely focused on interoperability.
I want to be very transparent here: our effort is intended to provide a repository option to those institutions/organizations that already license or have access to Microsoft software (including the free versions of the products, like SQL Server Express). Our platform is intended to sit on top of the existing Microsoft "stack". By providing this new research-output repository platform at no cost, we can offer added value for our existing (and future) customers in the academic and research space. It is critical to point out that we are making every effort to ensure our platform is optimized to make the best use of Microsoft technologies AND to also interoperate with all other existing systems and platforms in the repository ecosystem. We are actively seeking engagement and feedback from the community! ...
Update. Tony Hey (Microsoft VP for External Research) writes to add, "My hope is that we can help create both EPrints and DSpace front ends so that librarians can choose which back end they prefer."

For the past several years, many have said that now is the time to be a librarian, that the profession is greying. There are a lot of opportunities out there for new librarians, and I was encouraged by that news. But now, after reading an article in Library Journal, that may be changing with technology. All of these new jobs may not be needed as the library turns into a Barnes & Noble, where clerks rely on the computer for help in any subject. Professional librarians may only be able to find work with corporations such as Amazon or B&N, making lists for them for the online content.