The moricons.dll file in Windows contains icons originally designed for Microsoft's abandoned "Cairo" operating system project. These icons weren't repurposed from existing applications but were newly created for Cairo's planned object-oriented filesystem and its associated utilities. While some icons depict generic concepts like folders and documents, others represent specific functionalities like object linking and embedding, security features, and mail messaging within the Cairo environment. Ultimately, since Cairo never shipped, these icons found a home in various dialogs and system tools within Windows 95 and later, often used as placeholders or for functionalities not explicitly designed for.
Blue95 is a passion project aiming to recreate the nostalgic experience of a late 90s/early 2000s home computer setup. It's a curated collection of period-accurate software, themes, and wallpapers, designed to evoke the look and feel of Windows 95/98, packaged as a bootable ISO for virtual machines or physical hardware. The project focuses on free and open-source software alternatives to commercial applications of the era, offering a curated selection of games, utilities, and creative tools, all wrapped in a familiar, retro aesthetic. The goal is to capture the essence of that era's computing experience – a blend of discovery, simplicity, and playful experimentation.
Hacker News users generally expressed nostalgia and appreciation for Blue95's aesthetic, recalling the era of Windows 95 and early internet experiences. Several commenters praised the attention to detail and accuracy in recreating the look and feel of the period. Some discussed the practical limitations of older hardware and software, while others reminisced about specific games and applications. A few users questioned the project's purpose beyond nostalgia, but overall the reception was positive, with many expressing interest in trying it out or contributing to its development. The discussion also touched on the broader trend of retro computing and the desire to revisit simpler technological times.
Windows 95's setup process involved three distinct operating systems to ensure a smooth transition and maximize compatibility. It began booting from a DOS-based environment to provide basic hardware access and initiate the installation. Then, a minimal Windows 3.1-like environment took over, offering a familiar GUI for interacting with the setup program and allowing access to existing drivers. Finally, the actual Windows 95 operating system was installed and booted, completing the setup process and providing the user with the full Windows 95 experience. This multi-stage approach allowed the setup program to manage the complex transition from older systems while providing a user-friendly interface and maintaining compatibility with existing hardware and software.
Hacker News commenters discuss the complexities of Windows 95's setup process and the reasons behind its use of MS-DOS, a minimal DOS-based environment, and a pre-installation environment. Several commenters highlight the challenges of booting and managing hardware in the early 90s, necessitating the layered approach. Some discuss the memory limitations of the era, explaining the need to unload the DOS environment to free up resources for the graphical installer. Others point out the backward compatibility requirements with existing MS-DOS systems and applications as another driving factor. The fragility of the process is also mentioned, with one commenter recalling the frequency of setup failures. The discussion touches upon the evolution of operating system installation, contrasting the Windows 95 method with more modern approaches. A few commenters share personal anecdotes of their experiences with Windows 95 setup, recalling the excitement and challenges of the time.
Summary of Comments ( 61 )
https://news.ycombinator.com/item?id=43971616
Hacker News users discuss the mystery surrounding the unused icons in
moricons.dll, speculating about their purpose and the development process at Microsoft. Some suggest the icons were placeholders for future features or remnants of abandoned projects, possibly related to Cairo or object linking and embedding (OLE). One commenter links to a blog post claiming the icons were for a "Mac-on-DOS" environment called "Cougar," intended to make porting Macintosh software easier. Other comments focus on the general software development practice of leaving unused resources in code, attributing it to factors like time constraints, changing priorities, or simply forgetting to remove them. A few users recall encountering similar unused resources in other software, highlighting the commonality of this phenomenon.The Hacker News post "What were the MS-DOS programs that the
moricons.dllicons were intended for?" generated a moderate amount of discussion, with several commenters providing insights and speculation.One of the most compelling threads revolved around the purpose of these icons and why they seemed somewhat out of place for MS-DOS programs. Several commenters suggested that these icons were likely intended for a hypothetical or planned GUI environment for MS-DOS, which never fully materialized. They pointed to other similar initiatives from Microsoft around that time, like the short-lived "DOS Shell," as evidence that Microsoft was exploring graphical interfaces even before Windows 3.0 gained widespread adoption. This theory was supported by the more modern and detailed appearance of the icons compared to the simpler, character-based graphics typical of MS-DOS applications.
One commenter specifically hypothesized that the icons might have been intended for a "Windows-like" file manager for MS-DOS, perhaps even a precursor to the later Windows File Manager. This idea resonated with others, who noted the resemblance of some icons to later Windows icons.
Another user posited that these icons might have been utilized within the "MS-DOS Editor," suggesting they could have represented different file types or actions within the editor itself. However, this theory didn't gain much traction, with no other users confirming seeing icons in this context.
A few commenters focused on the technical aspects, discussing the format of the icons and the tools used to extract them. They mentioned the resource hacker utility and the internal structure of DLL files. This discussion, while technical, offered insight into how these icons were discovered and examined.
Finally, some comments simply expressed appreciation for the historical curiosity of the topic, enjoying the glimpse into a potential alternative path in the evolution of personal computing. They reflected on the rapid pace of technological change during that era and how these seemingly forgotten artifacts can offer fascinating glimpses into what might have been.
While there wasn't a definitive answer regarding the intended use of the
moricons.dllicons, the prevailing theory pointed towards a planned, but ultimately abandoned, graphical interface for MS-DOS. The comments collectively offered a blend of technical analysis, historical context, and informed speculation, painting a picture of Microsoft's experimentation in the transition from the command-line world of MS-DOS to the graphical world of Windows.