How Windows 98 Managed Temporary Internet Files

In Microsoft Windows 98, temporary internet files and cache management were deeply integrated into the operating system through Internet Explorer 4.0 and 5.0. This article explains how Windows 98 stored web assets, the role of hidden subdirectories and index databases, the configuration settings available to users, and how the operating system utilized this data for offline browsing and desktop integration.

The Storage Architecture and Directory Structure

Windows 98 stored web assets—such as HTML files, images, scripts, and multimedia—in a centralized location, typically found at C:\WINDOWS\Temporary Internet Files. When viewed through Windows Explorer, this directory appeared as a unified, flat list of cached files, complete with metadata like original URL, file size, and expiration date.

Beneath this shell-level abstraction, the physical file system told a different story. The actual files were stored inside a hidden folder named Content.IE5, which was further divided into randomized alphanumeric subfolders (such as 01A8ZX7K or W89X20P1). Windows 98 distributed files randomly among these subfolders to prevent FAT32 and FAT16 directory limits from degrading file-system performance when thousands of cached items accumulated.

The Role of index.dat

The entire cache system was cataloged by a binary database file named index.dat, located within the cache directory structure. Windows 98 relied on index.dat to:

  • Map human-readable URLs to the randomized, scattered files in the Content.IE5 subdirectories.
  • Store HTTP header metadata, including cache-control parameters, ETags, and last-modified dates.
  • Track the user's browsing history and cookie associations.

Because the operating system locked index.dat upon boot, it could not be deleted while Windows was running. Deleting cached files through standard deletion methods cleared the assets, but the index structure persisted until cleaned in real DOS mode or via specialized utilities.

Integration with Active Desktop and System Shell

With Windows 98, Microsoft merged the local file browser with the web browser through the "Active Desktop" update. Because the Windows shell (Explorer) and Internet Explorer shared the Trident layout engine, local files, system help files, and desktop web channels all utilized the same temporary internet cache. System components treated the local cache as a primary performance layer to avoid redundant network lookups, especially critical during an era dominated by dial-up internet access.

User Management and Configuration

Users controlled cache behavior via the Internet Properties dialog, accessible through the Control Panel or the Tools menu in Internet Explorer. Within the "Temporary Internet Files" section on the General tab, users could:

  • Adjust Disk Quota: Specify the maximum megabytes allocated for the cache. Once the limit was reached, the system purged the oldest or expired assets using a least-recently-used (LRU) algorithm.
  • Control Verification Frequency: Choose when the browser checked for newer versions of stored pages (Every visit to the page, Every time Internet Explorer is started, Automatically, or Never).
  • Purge Files: Manually clear assets using the "Delete Files" button, with an option to include offline content.
  • Relocate the Cache: Move the cache directory to a different drive partition to save space on the primary system drive.

Offline Browsing and Web Channels

Windows 98 placed heavy emphasis on offline browsing. The temporary internet cache allowed users to mark web pages or "Web Channels" for offline reading. The system would download the linked pages during scheduled synchronizations—often overnight via dial-up connections—and store them within the cache folders so users could browse the content later without an active internet connection.