Windows 95 build 58s
|Build of Windows 95|
Windows 95 build 58s is a Milestone 4 build of Windows 95. This build is the first release of the Chicago Preliminary Development Kit (PDK). Though this build is the earliest leaked build of Windows 95, earlier builds have been confirmed to exist.
New features[edit | edit source]
- 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
LOGO.SYSin 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 (
CABINET.EXE), 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[edit | edit source]
- 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 removed. See below for a fix.
- If you install directly from a CD, an error saying "Cannot access D:\" will be displayed on every boot, 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 or crash randomly and can be rather slow at times.
- Some copies of this build are missing the file
_msnet.inf, which must be skipped for setup to continue.
Fixes and enhancements[edit | edit source]
Getting rid of startup items[edit | edit source]
Three programs are configured to run on startup by default: Dr. Watson (
DRWATSON.EXE), Chicago Beta Warning (
WARNING.EXE) and Tracker (
TRACKER.EXE). 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
load= value in the
[windows] section of
Configuring a CD drive[edit | edit source]
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. While ATAPI CD-ROM drive support is incomplete, this build can still access the ATAPI CD-ROM drive without hanging if installed prior to setup, unlike some of the later builds.
Fixing "Cannot access D:\" error[edit | edit source]
SETUP.INI and change the line
OldWinDir=, then save the file.
Fixing "Cannot find NETWORK.DRV" error[edit | edit source]
Create a dummy (empty)
NETWORK.DRV file inside the
\SYSTEM folder or configure a network.
Old setup[edit | edit source]
There are many old setup files on the unmodified disc which may have been used in builds prior to 58s. Running
SETUP31.EXE /O:OLDSETUP.INF in the
RETAIL directory of the setup disc will launch the Windows 3.1x style setup, but the installation process will fail at the text stage due to 184 missing files.
It looks almost exactly like the Windows 3.1x setup, except for branding changes from "Windows" to "Chicago". It was possibly designed for a debug build of Chicago since it asks for many
.SYM files, a few debugger executables and batch files. Most of those
.SYM files are present in early Win32s builds meaning 32-bit support in Chicago was still at Win32s level in early 1993-06. It also asks for many components from Windows for Workgroups 3.1x that are missing from the setup disc.
After copying files in the GUI portion of Setup, Setup will attempt to run
W31TOCHI.EXE which is not present in this build. Setup will then launch Network Setup and it will most likely fail due to missing files.
Despite this, it is possible to install this build using the old setup, but the result produced is only a semi-working version of this build with visual glitches. The boot screen is
SYSLOGO.RLE used by earlier builds instead of the new animated
LOGO.SYS boot screen. About dialog reports "Windows for Workgroups Version 4.00.58s" as the old setup copies the old
SHELL.DLL during installation. File Cabinet will fail to launch due to missing registry entries, but Program Manager (
PROGMAN.EXE) works fine. All program groups are present due to the Group File Converter (
GRPCONV.EXE) not being executed automatically upon boot. The old setup does not install MS-DOS, therefore it is required to have MS-DOS 7.0 installed before installing Windows.