Cataloging
Documented in the recovered legacy build.
Featured Library Initiative · Software Preservation
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.
The Infolib Story
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
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.
Documented in the recovered legacy build.
Documented in the recovered legacy build.
Documented in the recovered legacy build.
Documented in the recovered legacy build.
Documented in the recovered legacy build.
Documented in the recovered legacy build.
Documented in the recovered legacy build.
Documented in the recovered legacy build.
Why Preserve Infolib?
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 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.
Restoration and release-readiness work is still in progress.
Frequently Asked Questions
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.
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.
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.
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.
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.
No. A release package must use a clean distribution database or other safe starter data. The recovered institution-specific database must not be distributed.
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.