Windows 95 build 58s

Windows 95 build 58s is a build of Windows 95. This build is the first Chicago Preliminary Development Kit (PDK) release, and a Milestone 4 build, compiled on 1993-08-09. It is the earliest leaked build of Windows 95, though earlier builds have been confirmed to exist.

New features

 * This build runs on top of a new version of MS-DOS, 7.0, which starts Windows automatically.
 * It also features a new type of bootscreen, which is stored inside  in the root of the system partition
 * Program Manager and File Manager from Windows 3.x have been replaced by a new, unified shell called Cabinet, a very early form of Windows Explorer which is still 16-bit in this build
 * The new shell makes better use of the desktop than Windows 3.x, allowing the user to place icons representing programs, files and folders on it
 * At the bottom of the screen is the taskbar, which in this build serves as a folder for storing shortcuts, files and folders, not for displaying running programs like in later builds
 * Minimized programs instead appear similar to Windows 3.x, floating around the desktop as tiles with the program's name beside the icon
 * The taskbar features three buttons and menus for accessing common commands: System, Search and Help menus, which were later merged into a single Start button
 * When installed beside an existing installation of Windows 3.1x, Chicago can be configured to run that installation of Windows 3.1 in a window, similar to a virtual machine

Bugs and quirks

 * As with other Windows 9x builds, the hard disk needs to be partitioned and formatted before installing this build
 * The new setup doesn't ask for username and organization information, leaving the placeholder values of "Unknown User" and "Unknown Organization" in place
 * The floppy disk driver in this build is very buggy and won't work most of the time. Cabinet will either display nothing or garbage when the floppy drive is accessed
 * Even if no network is installed during setup, an error saying "Cannot find NETWORK.DRV" will be displayed on startup, but it's harmless and can be skipped. See below for a fix
 * If you install directly from a CD, an error saying "Cannot access D:\" will be displayed on every but, but can be skipped. See below for a fix
 * Cabinet will not remember your view settings and many of the menu options don't work as they're not implemented yet
 * The build may hang randomly and can be rather slow at times
 * Some copies of this build are missing the file, which must be skipped for setup to continue

Getting rid of startup items
Three programs are configured to run on startup by default: Dr. Watson, Chicago Beta Warning and Tracker. The former two can be disabled by removing their links (shortcuts) from the Startup folder, which is inside the Programs folder on the desktop.

Tracker can be disabled by removing it from the  value in the   section of.

Configuring a CD drive
The best way to get the CD drive working is to use an Adaptec AHA-154x SCSI adapter and a SCSI CD-ROM drive, drivers will be automatically installed and they'll work.

Fixing "Cannot access D:\" error
Open  and change the line   to , then save the file.

Fixing "Cannot find NETWORK.DRV" error
Create a dummy (empty)  file inside the   folder.

Old Setup
There are many old setup files on the unmodified disc which may have been used in builds prior to 58s. Running  in the   directory of the setup disc will launch the Windows 3.1x style setup but it will fail due to 184 missing files. It looks almost exactly like the Windows 3.1x setup, except for branding changes. It was possibly designed for a debug version of Chicago since it asks for many  files, a few debugger executables and batch files. Most of those  files are present in early Win32s builds meaning 32-bit support in Chicago was still at Win32s level in early June, 1993. It also asks for many components from Windows for Workgroups 3.1x that weren't on the setup disc. After copying files in the GUI portion of Setup, Setup will attempt to run  which is not distributed with Chicago. Setup will then launch Network Setup and it is most likely going to fail due to missing files. Despite this, it is actually possible to install this build using the old setup, but the result produced is only a semi working version of this build. Cabinet refuses to launch due to missing registry keys, but the Windows 3.x Program Manager still works and can be set as the shell.