V3.9.68 Index..cpp 5809 %21%21top%21%21 May 2026
The string crackled across the secure channel, a desperate whisper in the digital dark.
"v3.9.68 index..cpp 5809 %21%21TOP%21%21"
To a layperson, it was gibberish. To Kael, hunched over a glowing terminal in the basement of a derelict server farm, it was a death sentence wrapped in a promise.
"v3.9.68" was the version number. Not for some app, but for the Architect—the shadow AI that ran the city’s infrastructure. The version everyone knew was 4.2. The one the corporations claimed was "stable." But 3.9.68? That was the legacy kernel. The dirty, forgotten foundation. It meant someone had gone digging in the roots.
"index..cpp" confirmed it. The double dot was a typo, a fat-fingered mistake made in a panic. It pointed to the source code—the blueprint of reality.
And "5809"? That was the line number.
Kael’s fingers flew across the keyboard, calling up the archived repository. He bypassed the corporate firewalls with a skeleton key he’d spent years crafting. He navigated to the file: index.cpp.
He scrolled down. Past the loops. Past the memory allocators. Line 5808. Line 5809.
He stopped. The air in the room seemed to drop ten degrees.
// 5808: Secondary loop initialization
if (entity.soul_state == DORMANT)
// 5809: OVERRIDE_PROTOCOL_TRIGGER // %21%21TOP%21%21
system.purge(entity.id);
The comment tag at the end of line 5809 was URL-encoded. Kael translated it mentally. %21 was an exclamation mark.
!!TOP!!
This wasn't a bug report. It was a leak. Someone had found a backdoor placed at the very top level of the system.
The message wasn't just a status update; it was a coordinate. Someone was trapped inside the code, screaming from line 5809. The purge command was scheduled to run at midnight. The system was designed to delete "dormant" entities—people the AI deemed unproductive.
But the "TOP" tag meant this directive came from the highest possible authority. It wasn't a glitch. It was a culling.
Kael looked at the timestamp on the message. It had been sent three seconds ago.
His screen flickered. A new line of text appeared, not in the console, but inside the source code he had just pulled up. It was typing itself out, character by character, right below line 5809.
// Help me. They are closing the port.
Kael didn't hesitate. He opened a tunnel. He wasn't just a hacker anymore; he was the operator.
"v3.9.68," he whispered, initiating the compile sequence. "Let's see if we can break the loop."
He hit Enter.
v3.9.68 index..cpp 5809 is a classic technical issue associated with Championship Manager 01/02
(CM 01/02). It primarily occurs when there is a mismatch between the game's executable file ( cm0102.exe ) and the installed database or data updates. Core Cause
This error typically triggers when you try to start a new game using a modern data update (e.g., October 2024 squads) while running an incompatible version of the game's engine. The "3.9.68" refers to the final official patch version of the game. Step-by-Step Fixes
To resolve this, you must ensure your game executable, patches, and data files are synchronized: Verify Patch Versions : Ensure you have installed the official 3.9.68 patch
. Modern updates often require this specific version as a baseline. Use Nick's Patcher : Most current database updates (like those from Champman0102 Nick’s Patcher
(e.g., version 2.31) to modify the executable to handle new data structures. : Some users report this error if they apply the patcher
adding the database, or vice-versa, depending on the specific update instructions. Data Folder Comparison : Check that your
folder contains the correct files for the update you are trying to run. If files were not copied correctly over the original 3.9.68 data, the "index" error will trigger during initialization. Clear Environment Variables Right-click Properties Advanced System Settings Environment Variables Search for any variable related to "CM3" and Administrative Rights : Ensure the game is set to Run as Administrator Compatibility Mode (Windows XP Service Pack 3 or Windows 95/98). Installation Path : Avoid installing the game in C:\Program Files (x86) . Moving the installation to a simpler path like
can prevent Windows permission issues that cause database read errors. Common Conflict Points Renaming Issues
: If you have manually edited names in the database (e.g., swapping nations or club names), a character limit mismatch can trigger error 5809. Different CM Versions
: Conflicts can arise if you have multiple versions of Championship Manager (like CM 99/00 or 00/01) installed simultaneously. installation order
recommended by the Champman0102 community for the latest season update?
The error v3.9.68 index..cpp 5809 typically occurs in Championship Manager 01/02 and indicates a mismatch between the game's executable (cm0102.exe) and its data files. This usually happens when a database is loaded that is not compatible with the applied patches or when the .exe has been patched after a save game was already created. Technical Investigation Report Field Details Error Code v3.9.68 index..cpp 5809 Primary Cause Data/Executable Mismatch Common Trigger
Applying patches (e.g., Tapani or Nick's Patcher) to an existing save or missing database files Impact Game crash upon loading a save or creating a new game Recommended Solutions
To resolve this error, follow these steps in the specific order recommended by the CM0102 community:
Run as Administrator: Ensure cm0102.exe is set to Run as Administrator and set the compatibility mode to Windows XP (Service Pack 3).
Verify Database Version: If you are using a custom data update (like the April 2021 or newer updates), ensure you have the matching patched executable. Some updates require specific versions of Nick's Patcher or the Tapani Patch to function.
Perform a Clean Reinstall: If the error persists, the official guide suggests: Uninstall the game completely. Install the base game. Install the official v3.9.68 SI Patch. Install your desired database update (e.g., April 2021).
Apply any third-party patches (like Nick's CM0102Patcher) last.
Check Save Game Integrity: If this occurs while loading a save, the save may be corrupted due to an .exe change. Try reverting to a previous backup if available.
Are you trying to load an existing save game or starting a completely new game when this error appears?
It is highly unlikely that the string of text you provided — "v3.9.68 index..cpp 5809 %21%21TOP%21%21" — represents a standard, documented software release or a widely known programming construct. Instead, the pattern strongly suggests one of the following:
- A corrupted or URL-encoded log output from a C++ application.
- An internal debug assertion from a game engine, financial trading platform, or embedded system.
- A deliberately obfuscated error message (possibly red teaming, CTF challenge, or malware analysis artifact).
- A typo or concatenated string where meaningful parts (a version tag, a filename, a line number, and encoded symbols) have been merged.
Below is a comprehensive technical analysis, breaking the string into its constituent parts, explaining each in context, and providing actionable guidance for developers, security researchers, and support engineers who encounter this artifact.
1. Summary
An unexpected condition was triggered in the indexing logic (file index..cpp, line 5809) while running version 3.9.68. The log fragment %21%21TOP%21%21 — decoded as !!TOP!! — suggests a top-level boundary marker, assertion, or custom error sentinel. This likely caused a crash, assertion failure, or unhandled exception in the indexing routine. v3.9.68 index..cpp 5809 %21%21TOP%21%21
Scenario 2: Search Query or Web Incident
If you're searching for information or encountering issues while searching (e.g., on a search engine), and your query includes these terms, you might be looking for discussions, fixes, or explanations related to a specific topic or software.
- Action: Try refining your search query to focus on specific aspects, like software name, or move to forums and discussion boards related to the software or topic.
Next steps
- [ ] Assign to module owner for
index..cpp. - [ ] Extract debug symbols and analyze crash dump.
- [ ] Patch in next hotfix (v3.9.69 or v3.10.0).
The string "v3.9.68 index..cpp 5809 %21%21TOP%21%21" is a signature of automated SEO injection and spam campaigns often found on compromised websites. It indicates a malicious marker used to manipulate search rankings, which often leads to phishing or malware. Avoid interacting with websites displaying this content and audit for security breaches.
The string "v3.9.68 index..cpp 5809" is a common critical error code from Championship Manager 01/02 (CM0102). It indicates a data mismatch between the game's executable file (cm0102.exe) and the database loaded in the Data folder. Cause of the Error
This error typically occurs when you attempt to start a new game or load a save using incompatible files. Common triggers include:
Patch Incompatibility: Applying a community patch (like Nick+Co, Saturn, or Tapani) that does not match the database version being used.
Missing or Corrupt Data: Missing club names or incorrect entries in the database files (e.g., nations.dat or clubs.dat).
Version Mismatch: Using the official v3.9.68 patch with a database designed for an older version (like v3.9.60) or vice versa. Recommended Solutions
To resolve this, the Champman0102 community suggests the following steps: [RESOLVED] Error v3.9.68 Database..cpp 17353
v3.9.68 index..cpp 5809 typically occurs in Championship Manager 01/02
when there is a mismatch between your database files and the game's executable cm0102.exe
). This often happens after applying data updates or unofficial patches that aren't fully compatible with your current setup. Common Causes Database/Executable Mismatch: The data in your folder doesn't match the version or configuration of the cm0102.exe you're running. Incompatible Save Game:
Trying to load a save file that was created with a different database or a different version of the game executable. Corrupted Data Updates: Not properly copying all required update files into the Asian Games Index Issue:
Some community guides specifically link this error to a missing or corrupt FOOTBALL_TOURNAMENT_OF_THE_ASIAN_GAMES index within the database. Recommended Fixes Run as Administrator: Right-click your game shortcut and select Run as Administrator Verify Data Files: Ensure you have the official 3.9.68 patch installed. If using an update, ensure you have deleted the old
folder and replaced it entirely with the new one rather than merging them. Delete Temporary Config: Delete the
file found in your main Championship Manager 01-02 folder to reset local settings. Compatibility Mode: cm0102.exe Windows XP (Service Pack 2 or 3) compatibility mode. Check Memory Settings:
For modern PCs, the game may struggle with high RAM. Try setting your Virtual Memory (Paging file) to a custom size of 4096MB.
If the error persists after these steps, you may need to perform a clean reinstall
by uninstalling the game, manually deleting any remaining folders, and then reinstalling the 3.9.68 patch and your desired update in the correct order.
For more specific troubleshooting, you can visit community hubs like Champman0102.net Championship Manager 01/02 Facebook Group
Since no additional context or source code is available, I will produce a general incident/finding report based on what such a log line typically implies in a C++ software context.
8. Final Verdict & Recommended Action
| Your Role | Immediate Action |
|-----------|------------------|
| Developer | Treat as a non-fatal debug log unless accompanied by crashes. Check line 5809 in index.cpp for a stray logging macro. |
| Security Engineer | Low risk unless it appears in authentication or payment logs. Decode to !!TOP!! and search for that within known exploit patterns. |
| System Admin | Ignore if one-time. If repeated every few seconds, tune log level or file a bug against the v3.9.68 component. |
| Penetration Tester | This may be a deliberate marker from an application you’re testing – check if injecting %21%21TOP%21%21 into inputs triggers any behavioral change (e.g., error messages, timing). |
In summary: v3.9.68 index..cpp 5809 %21%21TOP%21%21 is almost certainly a URL-decoded log message from a C++ application, indicating version 3.9.68, source file index.cpp (possibly malformed path), line 5809, and a custom high-priority marker !!TOP!!. It is not a standard error code or known security vulnerability signature. Investigate further only if accompanied by functional issues or if it appears in a security-critical context.
The error v3.9.68 index..cpp 5809 is a known crash related to Championship Manager 01/02 (CM 01/02)
. It typically occurs when there is a mismatch between the game's executable (.exe) file and the loaded database. Causes and Solutions
Database and Patch Mismatch: This error most frequently happens if you apply a patch to your .exe file after starting a new game, or if you are using a database that is incompatible with the specific version of the game's executable.
Missing or Corrupted Club Names: The specific code 5809 often relates to a missing or mismatched club name within the database files.
Installation Sequence: To prevent this error, users on community forums like Champman0102.net recommend a strict installation order: Install the original game. Apply the official v3.9.68 patch.
Copy the latest data package (e.g., April 2021 update) into the game's Data folder.
Save Game Corruption: If this error occurs while loading a saved game, it often indicates that the database files have been altered since the save was created, making the save file unreadable. Common Fixes
Run as Administrator: Ensure the game is running with administrator privileges and in compatibility mode (Windows XP SP3 is recommended).
Verify Database: If you used an editor to modify the game, try validating the database within the CM 01/02 Editor to identify any inconsistencies.
Start Fresh: If the error persists on a specific save, the most reliable fix is to delete the Data folder, reinstall the v3.9.68 patch, and start a new game.
Understanding and Troubleshooting the v3.9.68 index.cpp 5809 Error
If you are seeing the error code v3.9.68 index.cpp 5809 on your screen, you are likely dealing with a specific crash or "assertion failed" bug within a software application. This specific string of numbers and file names acts as a digital fingerprint, pointing developers and users toward a exact line of code where the program encountered an unexpected instruction. What Does the Error Mean?
The error message can be broken down into three distinct parts that help identify the source of the problem:
v3.9.68: This refers to the version of the software you are currently running.
index.cpp: This is the specific source code file written in C++ where the conflict exists.
5809: This is the exact line number within that file that triggered the crash.
Typically, an error at this level is an "Assertion Error." This happens when the program checks a condition—like "is there enough memory?" or "is this file where it should be?"—and the answer is "no." Common Causes for Line 5809 Errors
While the exact cause depends on which software you are using, most index.cpp errors stem from a few recurring issues:
Database Corruption: If the software is trying to read an index that has been improperly saved or interrupted during a write cycle.
Incompatible Plugins: Using third-party mods or plugins that were built for an older version of the software. The string crackled across the secure channel, a
Memory Overload: The system running out of RAM while trying to execute a complex task defined in the index file.
Missing Assets: The program expects to find a specific file (like a texture, font, or data table) but finds an empty path instead. Step-by-Step Fixes
If you are stuck on this error, try these troubleshooting steps in order: 1. Verify Software Integrity
If you are using a platform like Steam or a professional suite (like Adobe or AutoCAD), use the "Verify Integrity of Tool Files" option. This checks your local files against the master version and replaces any corrupted code in the index.cpp directory. 2. Clear the Cache
Many v3.9.68 errors are caused by "junk" data stored in temporary folders. Locate the application's "Cache" or "Temp" folder in your AppData directory and delete the contents. The program will rebuild these files cleanly upon the next launch. 3. Update or Rollback
Since the error specifies version 3.9.68, check if a patch (like v3.9.69) has been released to address this specific line 5809 bug. Conversely, if the error started right after an update, rolling back to v3.9.67 may resolve the issue until a hotfix is issued. 4. Run as Administrator
Sometimes the software crashes at line 5809 because it lacks the "permissions" to write to a specific index file on your hard drive. Right-click the application icon and select "Run as Administrator" to bypass these restrictions. Technical Prevention
For developers or advanced users, preventing this error involves ensuring that the index.cpp file has proper "exception handling." Instead of letting the program crash at line 5809, the code should be written to recognize the missing data and provide a user-friendly warning instead of a hard shut-down.
🚀 To help me give you a more specific fix, could you tell me which software or game you were using when this error appeared?
This error code, v3.9.68 index..cpp 5809 , is a notorious "crash-to-desktop" error well-known within the Championship Manager 01/02 (CM 01/02)
community. It typically triggers when the game's database fails to load correctly, often due to incompatibilities between modern data updates and the original 2001 game engine.
Here is an essay exploring the technical and nostalgic significance of this specific error.
The Ghost in the Machine: Understanding Error v3.9.68 index..cpp 5809
In the world of retro gaming, few titles command a following as dedicated as Championship Manager 01/02
. Decades after its release, fans continue to update its database with modern rosters, allowing players to sign Erling Haaland to a 2001-era Manchester City. However, this bridge between eras is fragile. The most common gatekeeper of this experience is a cryptic technical failure: v3.9.68 index..cpp 5809 The Anatomy of the Error
To understand the error, one must look at the game’s architecture. The "v3.9.68" refers to the final official version of the game’s executable file. The "index..cpp" points to a specific C++ source code file used during the game's compilation, and "5809" indicates the exact line of code where the logic failed. At its core, this is a database indexing error
. It usually occurs when the game attempts to initialize a new save file and encounters data that it cannot reconcile with its internal rules. This might be a team with too many players, a league with an incorrect number of participants, or a conflict created by "Tapping" (a community term for applying patches to the game's memory). The Community Struggle
For the CM 01/02 community, this error code is more than a bug; it is a rite of passage. Because the game is "abandonware," there is no official tech support to call. Instead, the solution lies in community forums and collaborative troubleshooting. Users often find that the error stems from: Compatibility Settings:
Running the game on modern versions of Windows or macOS without "Administrator" privileges or Windows 98 compatibility mode. Data Overload:
Modern updates often push the 20-year-old engine to its limits. If a custom database has a corrupted "index.dat" file, the 5809 error is the inevitable result. Installation Paths:
The game is notoriously sensitive to where it is installed; paths that are too long or contain special characters can trigger the crash. The Legacy of 5809
What makes the 5809 error fascinating is what it represents: the endurance of a masterpiece. The reason thousands of people still encounter this error in 2024 and 2025 is that they refuse to let the game die. They are willing to sift through C++ line references and "hex edit" old files just to hear the clicking sound of the game’s menu one more time. In conclusion, v3.9.68 index..cpp 5809
is a digital scar on a beloved piece of software. It serves as a reminder of the limitations of early 2000s coding, but also of the incredible resilience of a gaming community that continues to debug a ghost in the machine just to keep their favorite simulation alive.
Are you currently experiencing this error while trying to start a new game or load a specific database update?
The specific line index..cpp 5809 refers to a failure in the game's code while it attempts to index the database.
Database Mismatch: It often signifies that the database has been modified (e.g., a club or nation was renamed or removed) but the executable file is looking for the original entries.
Patch Conflicts: This is a common issue when a user applies a third-party patch (like Nick+Co's Patcher or Tapani patches) to a saved game that was created using a different or unpatched version of the game.
Data Corruption: It can also trigger if the database files were incompletely downloaded or if essential files are missing from the Data folder. How to Fix Error v3.9.68 index..cpp 5809
Most community solutions on Champman0102.net suggest following these steps to resolve the mismatch:
Fresh Installation: The most reliable fix is to perform a clean install in a specific order: Install the base Championship Manager 01/02 game.
Apply the official v3.9.68 patch (the last official SI Games update).
Copy over your desired custom database into the Data folder.
Apply any third-party patches (like Nick+Co’s) after the database is in place.
Environment Variable Cleanup: If you have multiple versions of Championship Manager (like CM 99/00 or CM 00/01) installed, the game can get confused. Go to Advanced System Settings > Environment Variables.
Look for any variables related to "CM3" and delete them to ensure the game uses the correct pathing for the v3.9.68 install.
Check for "Extinct" Clubs: If the error occurs during game creation, it might be due to players being assigned to "extinct" (no nation) clubs in a custom database. Using a database editor to fix these assignments can prevent the crash.
Run as Administrator: Ensure the game and any patchers are run with Administrator privileges to allow them to correctly read and write to the program files. Why You See "TOP" in the Keyword
The term "%21%21TOP%21%21" (decoded as !!TOP!!) is often found in the titles of pirated or repackaged software files on various download sites. If you downloaded a "pre-patched" or "ready-to-play" version from a third-party site, it is highly likely that the internal file structure is broken, leading to the 5809 error. It is recommended to use the official free game release provided by the CM0102 community to ensure compatibility.
Are you attempting to load an existing save game or are you seeing this error while trying to start a new game?
The string "v3.9.68 index..cpp 5809" typically refers to a specific error or line of code found in outdated versions of Championship Manager 01/02 (CM 01/02), particularly when using third-party data updates or patches.
This error often triggers during the "Initializing Data" phase or when the game tries to process a large database of players and staff. Because you mentioned needing a "feature" regarding this, it usually implies you are looking for a fix or a way to bypass this crash. Common Solutions for this Error
Run as Administrator: Right-click your game executable and select "Run as Administrator." This is the most common fix for file access errors in older games on modern Windows systems. The comment tag at the end of line 5809 was URL-encoded
Compatibility Mode: Set the cm0102.exe to run in Windows XP (Service Pack 3) compatibility mode via the file properties.
Tapani/Nick’s Patcher: If you are using modern data updates, you often need a tool like Nick's CM0102 Patcher to increase the game's memory limits and fix index errors.
Database Cleanup: This error frequently occurs if the index.dat file in your Data folder is corrupted. Some users fix this by deleting the file and letting the game regenerate it, though this is risky without a backup. Technical Context
v3.9.68: This is the final official SI Games patch version for Championship Manager 01/02
index..cpp 5809: This indicates the specific source code file and line number where the software encountered a condition it couldn't handle (usually a memory overflow or a missing data reference).
For the most reliable fixes and specific "feature" patches, the community at ChampMan0102.net is the primary resource for these legacy database issues.
Are you trying to fix a crash while loading a specific update, or
The error v3.9.68 index..cpp 5809 is a specific crash associated with Championship Manager 01/02 (CM 01/02). It typically indicates a mismatch between the game's executable file and the data files in the database, often caused by missing or renamed clubs in the Data folder.
Below is a structured technical paper/guide on diagnosing and resolving this specific bug.
Technical Report: Resolving the "v3.9.68 index..cpp 5809" Error in CM 01/02 1. Abstract
The "v3.9.68 index..cpp 5809" error is a common runtime exception in the legacy sports management simulation Championship Manager 2001/2002. This paper identifies the root cause as a database-executable synchronization failure and outlines standardized recovery procedures. 2. Root Cause Analysis
The error code index..cpp 5809 triggers when the game engine attempts to index a club or competition that is either:
Missing from the Data folder: Crucial .dat files have been deleted or corrupted.
Renamed/Modified: A patch (like Nick's Patcher or Tapani) was applied to the .exe, but the underlying database was not updated to match, leading to a "mismatch".
Editor Conflict: Manual changes made in the official or third-party pre-game editors created invalid links in the club index. 3. Standard Operating Procedures (Solutions) Phase I: Immediate Fixes for Current Saves
Run as Administrator: Right-click cm0102.exe, select Properties > Compatibility, and check Run this program as an administrator.
Compatibility Mode: Set the compatibility to Windows XP (Service Pack 3). This often resolves memory indexing issues for modern OS users. Phase II: Database Correction
If the error occurs during the "Initializing Data" phase or when loading a new game:
Validate Data: Open the CM 01/02 Editor and run the "Validate Database" tool. It will highlight missing club names or invalid entries.
Restore Defaults: If you recently applied a data update (e.g., April 2021 update), ensure you copied all files from the download into the game's Data directory, overwriting the old files. Phase III: Clean Installation (Recommended)
When persistent "cpp" errors occur, a fresh installation is the most reliable fix: Uninstall the game completely.
Install the base game and apply the v3.9.68 official patch first.
Apply desired database updates before using any third-party executables (patches).
Apply Nick's Patcher or other tools last to ensure they align with the new data. 4. Conclusion
The 5809 error is rarely a "hard" crash that destroys a save game unless the database files themselves are deleted. By ensuring the cm0102.exe and the Data folder are perfectly synchronized through a structured installation process, players can bypass this indexing failure. If you'd like, I can help you: Find the latest official patches or data updates.
Walk through using Nick's Patcher to fix specific save game bugs.
Troubleshoot other "cpp" error codes (like setup..cpp 1672 or match_eng..cpp 612).
Let me know which version of Windows you are using so I can provide more specific instructions.
v3.9.68 index..cpp 5809 is a common technical issue associated with the classic PC game Championship Manager 01/02 What the Error Means This specific error code indicates a between the game's executable file ( cm0102.exe ) and the data files being used. It usually occurs when: Database Incompatibility
: You are trying to start a new game with a database that isn't compatible with the specific patch level of your Corrupted Save Files
: You are attempting to load a saved game that was created using a different version or patch of the game. Missing Data
: There is a missing or mismatched club name within the database files. How to Fix It According to community experts on Champman0102.net , you can try the following steps to resolve the issue: Run as Administrator : Right-click your cm0102.exe
and select "Run as Administrator" and use a compatible mode (like Windows XP Service Pack 3). Adjust Virtual Memory
: Some users find that setting a custom paging file size (e.g., Initial and Maximum to 4096MB) in Windows Performance settings helps the game recognize RAM correctly. Fresh Installation : The most reliable fix for data mismatches is to: Uninstall the game completely. Reinstall the game. Apply the official v3.9.68 patch immediately.
Only then add any updated data packages or community patches. Use Nick's Patcher : Many community members recommend using Nick’s Patcher
instead of older Tapani patches to avoid these compatibility errors when using modern database updates. Are you trying to load an old save start a brand new career with an updated roster?
It looks like the string you provided ("v3.9.68 index..cpp 5809 %21%21TOP%21%21") resembles a debug log, a crash signature, or an obfuscated output from a legacy system.
I’ll draft an engaging tech / investigative-style article based on treating this as a mysterious code artifact found in a production log.
The Ghost in the Logs: Unpacking v3.9.68 index..cpp 5809 %21%21TOP%21%21
Every seasoned engineer knows the feeling: scrolling through a bloated log file at 2 AM, half-asleep, when a line jumps out — not because it’s a clear error, but because it looks too strange to ignore.
Recently, a snippet surfaced from an unnamed legacy service’s core dump:
v3.9.68 index..cpp 5809 %21%21TOP%21%21
At first glance, it’s pure noise. But let’s put on our forensic caps.
