Modern software loves RAM. The new CM2 SCR easily consumes 800MB to 1.2GB of memory. In contrast, the old version runs comfortably in under 150MB. For netbooks, thin clients, or virtual machines with limited resources, the old version is the only viable choice.
| Category | Score (out of 10) | |-------------------|-------------------| | Nostalgia factor | 9.5 | | Stability today | 3.0 | | Performance | 6.5 | | Feature parity | 4.0 | | Ease of uninstall | 7.0 |
Final thought: The old CM2 was a masterpiece of compatibility hacking, but time has not been kind. It’s a museum piece now – useful for retro computing enthusiasts, but a liability for daily work. If you find an old copy on a CD or download site, treat it as a curio, not a solution.
Would I install it on my main PC in 2025? No.
Do I miss it? Every time I try to find “Protect Sheet” in Excel’s ribbon. cm2 scr old version
Newer CM2 SCR revisions (v2.x) fixed:
Backward compatibility mode in new versions can emulate the old SCR behavior by setting a hidden compatibility register (address 0xFFE0 0008, bit 0 = 1). However, the watchdog timing quirk is not emulated – legacy software must be patched.
Is the Old Version worth playing?
Is the Old Script worth using?
Note: If "CM2" refers to something else in your specific context (like a specific obscure software tool or a different game entirely), please clarify! However, based on common gaming acronyms, this review covers the most likely candidate.
This review is written from the perspective of a long-time power user who refused to adapt to the Ribbon UI. Modern software loves RAM
The latest CM2 SCR releases (v3.0 and above) have migrated to a subscription model. Core features that were once free—such as batch export, regex-based filtering, and multi-threaded processing—are now locked behind a "Pro" paywall. The old version retains all these features as a one-time purchase (or completely free, depending on the original license).
Here’s something only heavy users noticed: In native Office 2003, Ctrl+Z undid the last action. In CM2’s old version, if you used a command from the classic menu (e.g., Format > Borders and Shading), that action was sometimes not recorded in the Undo stack properly. You’d hit Undo, and it would skip back two steps. This was infuriating and never fully fixed in pre-2015 builds.