Featured Library Initiative · Software Preservation

Infolib: a library automation legacy worth preserving

Created by Gerry O. Laroza.

Created to help libraries move toward automation, Infolib brought practical library workflows together in one application. Desiderata Solutions is preserving the recovered legacy software, documenting how it worked, and exploring how its useful ideas can live on for today’s libraries.

Infolib was historically available as a free public download. The Desiderata Solutions-hosted restored download remains temporarily unavailable while restoration and release-readiness work continues.
Infolib 2015Recovered legacy build
Bibliographic workCataloging
DiscoveryOPAC
ServiceCirculation
PreservationPreserve & document
← Back to Desiderata Solutions Projects

The Infolib Story

A practical system built to help libraries automate.

Infolib grew from Gerry O. Laroza’s commitment to helping libraries automate their services. For libraries that needed a practical local system, his software offered tools for day-to-day library work in one application. Years after the original hosting disappeared, a recovered copy of Infolib 2015 was entrusted by Gerry’s family for preservation and testing.

Desiderata Solutions is not the creator of Infolib and will never present the software as its own. Gerry O. Laroza remains the original author and developer. Desiderata Solutions’ role is stewardship: preserving the recovered materials, documenting the legacy system, testing a clean copy cautiously, and making the software’s history easier to find.

Recovered Legacy Build

What the recovered Infolib 2015 build contains.

The recovered build includes these modules and workflows. They are documented as features present in the software—not as a claim that every function is compatible with current Windows environments.

01

Cataloging

Documented in the recovered legacy build.

02

Article Indexing

Documented in the recovered legacy build.

03

Circulation

Documented in the recovered legacy build.

04

OPAC

Documented in the recovered legacy build.

05

Reports

Documented in the recovered legacy build.

06

Gate Monitoring

Documented in the recovered legacy build.

07

Maintenance & Setup

Documented in the recovered legacy build.

08

Barcode-related Work

Documented in the recovered legacy build.

Why Preserve Infolib?

Preserving software—and the memory around it.

Older library systems are part of the history of library automation in the Philippines and of the people who built practical tools for libraries with limited resources.

Preserving Infolib means preserving both software and memory: how librarians worked, what problems the system solved, and how Gerry’s work reached institutions that used it.

Restored Legacy Download

Infolib 2015 Free Legacy Download — Public Access Restoration in Progress

Infolib was historically made available to the public as a free download. The current pause is a restoration and release-readiness step, not a change in Infolib’s free/public status.

We are preserving and testing a recovered copy so dependable public access can be re-established without distributing institution-specific data, undocumented dependencies, or uncleared third-party components. The restored download will remain temporarily unavailable until the release package has a clean starter database, documented prerequisites and limitations, verified checksums, resolved redistribution questions, and completed testing for the environments that Desiderata Solutions will actually list.

When approved, the restored package will be presented as preserved legacy software rather than a currently supported commercial product, with Gerry O. Laroza clearly credited as creator.

What the restored download will tell users

  • Creator: Gerry O. Laroza. Desiderata Solutions is preserving and restoring access; Desiderata Solutions is not the original developer.
  • Status: Historically free legacy software, with public access to be re-established after restoration testing and release approval.
  • Tested environments: Only the exact Windows, Office, and runtime combinations actually verified will be listed.
  • Prerequisites: Required third-party components will be documented, with official vendor prerequisites linked where appropriate.
  • Known limitations: Any unresolved dependency or workflow limits that remain at release time will be stated plainly.
  • Integrity: The package version/date and SHA-256 checksum will be provided. Any separately approved compatibility-modified executable will be clearly distinguished from Gerry’s original executable.
  • Data safety: The public package will use a neutral starter database and will not include another institution’s records, patron/staff data, credentials, local paths, or institution-specific full text.
Current status Temporarily unavailable

Restoration and release-readiness work is still in progress.

Tell Us Your Infolib Story

Help preserve the history around the software.

Did Infolib help your library take its first steps into automation? Gerry’s family would love to hear what it made possible. Tell us where you used Infolib, approximately when you used it, what changed for your staff or library users, and any memory of Gerry or the software that you would like to preserve.

Your contact email is optional and will not be published. Your story and the identifying information you provide will be sent privately to Gerry’s family. Permission for Desiderata Solutions to publish your story or an edited excerpt remains separate and optional.

Required fields

Story permissions

Sharing a story is optional and will never be required for access to the restored Infolib legacy download.

Frequently Asked Questions

About the Infolib restoration.

Who created Infolib?

Infolib was created by Gerry O. Laroza. Desiderata Solutions is preserving and documenting the recovered legacy software; Desiderata Solutions is not claiming authorship of the original program.

Is Infolib available for download now?

Infolib was historically available to the public as a free download, but the recovered copy has not yet been re-published by Desiderata Solutions. The restored download should remain disabled until the release checklist is complete and Desiderata Solutions explicitly approves the exact package for publication. This is a restoration gate, not a new decision about whether Infolib should be free.

Why is the download temporarily unavailable if Infolib was already free?

Because the recovered materials must first be separated from institution-specific data and legacy dependencies that should not be redistributed blindly. The temporary hold protects users, Gerry’s legacy, and the institutions represented in historical data while Desiderata Solutions prepares a clean, documented release candidate.

Is Infolib compatible with Windows 10 or Windows 11?

No general compatibility claim should be made yet. Current verified runtime evidence covers one Windows 10 Home 22H2 computer with 64-bit Office LTSC 2024 using a private compatibility build. On that machine, the original 32-bit executable reaches the login screen but cannot connect because a 32-bit ACE provider is not registered. The private compatibility build connects and several modules have opened successfully, but Windows 11 has not been verified and several workflows still require further testing.

What prerequisites does the restored Infolib use?

Database access depends on the Microsoft ACE/Access Database Engine environment. OPAC, Circulation, and Reports currently share a Microsoft ReportViewer 11 dependency that is still being restored and retested. PDF/full-text and barcode-related components also need to be documented.

Will the public package contain another library’s records?

No. A release package must use a clean distribution database or other safe starter data. The recovered institution-specific database must not be distributed.

Can former users contribute to the project?

Yes. Former users can contribute historical context and stories about how Infolib was used. These accounts can help document the software’s real-world legacy and guide which workflows are worth preserving in a future web version.