-
Notifications
You must be signed in to change notification settings - Fork 96
Home
One-Core-API is a compatibility layer, developed to restore software (and hardware) interoperability for legacy Windows NT operating systems.
Currently, One-Core-API provides binary releases compatible with:
- Windows XP (RTM, SP1, SP2, SP3)
- Windows XP Professional x64 Edition (SP1, SP2)
- Windows Server 2003 (RTM, SP1, SP2)
- Windows Vista (Experimental support is currently available via the Canary branch).
Caution
One-Core-API performs deep-level modifications to kernel-mode and user-mode components. Due to the extreme complexity of bridging the architectural gap between NT 5.x and NT 6.x+, NO ONE CAN GUARANTEE STABLE OPERATION OR SYSTEM INTEGRITY.
- Risk of Corruption: Stability issues, including irreversible system corruption and Blue Screens of Death (BSOD), are documented risks.
- No Warranty: Use this software at your own risk. Always perform full system backups before installation.
- Antivirus Conflict: Third-party Antivirus (AV) solutions are officially unsupported. Heuristic engines frequently conflict with OCA's API redirection. Uninstall any AV software prior to deployment.
As is well documented, Windows XP reached its end of official support from Microsoft in 2014, with the specialized POSReady 2009 version concluding in 2019. Consequently, hardware driver development largely stagnated between 2012 and 2016; NVIDIA was the last major manufacturer to provide official support for the platform. Simultaneously, software developers began deprecating XP compatibility.
For users who prefer Windows XP or Server 2003—whether for nostalgia, performance, or specific workflow requirements—running modern software on current hardware has become nearly impossible. Aside from specific projects like MyPal 68/78 or Supermium, virtually no modern software remains compatible with the native NT 5.x kernel. One-Core-API was created to resolve this issue by re-establishing the necessary software and hardware bridges.
The transition from Windows XP to Windows Vista marked a significant architectural leap. Windows XP lacks approximately 90% to 95% of the new technologies and APIs introduced in Windows Vista and subsequent versions. Implementing these modern technologies into a legacy environment is an immense challenge that necessitates deep system-level modifications.
Current Development Observations:
- Stability: One-Core-API is under intense active development. Due to the complexity of the project, stability issues may arise, and system corruption is a potential risk.
- Testing: It is impossible to predict every potential conflict across infinite hardware and software configurations. The project relies on a small dedicated team (including lead developers and contributors like Murak, Svyatpro, and CoccodrillooXDS) and community feedback.
- Vista Support: Expanding the compatibility layer to Windows Vista is a current priority, with initial implementations available for testing in the Canary builds.
- Main: The primary repository containing validated binary releases for XP and Server 2003.
- Canary Branch: The development branch featuring the latest fixes and experimental Windows Vista support.
- One-Core-API Extras: Supplementary package providing extended features for OCA-based systems such as custom fonts, win32ss from Longhorn 5048 and more.
- One-Core-API Tools: Specialized utility designed for the deployment of One-Core-API.
Use the links below to access detailed technical documentation:
| Section | Description |
|---|---|
| Installation Guide | Step-by-step procedures for deployment and uninstallation. |
| Application Compatibility | The AppDB: Verified browsers, IDEs, frameworks, and games (DX10/11). |
| Known Limitations | Documented bugs, architectural constraints, and software conflicts. |
| Bug Reporting | Requirements for submitting technical issues and crash dumps. |
| Showcase | Visual evidence and proof-of-concept demonstrations. |
We encourage users to report any encountered errors to assist in the growth of the legacy Windows community. Please provide detailed reports rather than general complaints to facilitate faster resolutions.
- Official Discord Server: Join the One-Core-API Discord
- Issue Tracking: Please check the existing Issues on GitHub before submitting a new report.