Windows for Workgroups

Microsoft's peer-to-peer networking graft onto Windows 3.1, genuinely useful on a small office LAN and genuinely oversold as a NetWare replacement.

Origins

Windows for Workgroups arrived in October 1992 as Microsoft's first attempt to fold peer-to-peer networking directly into the Windows shell.² The timing was deliberate: development of Windows NT, with its own built-in networking, was well underway, and Microsoft needed something for the large installed base of 386 and 486 machines that NT's hardware appetite would exclude. The result was an environment almost identical to Windows 3.1 with a network client bolted on. Almost identical is the operative phrase, since the underlying DOS dependency remained unchanged.⁶

News about WFW circulated alongside early information about Windows NT during 1992, creating market confusion that would dog the product for its entire first year.² Microsoft's own networking story (WFW for the desktop, NT for the server) was coherent enough in theory, but the press and the reseller channel struggled to explain it against the dominant reality of Novell NetWare.

The First Year & the 3.11 Revision

Through most of 1993, Windows for Workgroups attracted criticism for slow sales and underwhelming features.² The "slow sales" charge was contested: the product shipped over a million units in its first year.² The features criticism was harder to dismiss. The original release offered peer-to-peer file and print sharing, but its all-real-mode file system implementation meant network throughput was unremarkable, and the product sat awkwardly between the desktop and the server room.

Microsoft's answer came in November 1993 with Windows for Workgroups 3.11, a revision that mattered more than its minor version number suggested.² The headline addition was a protected-mode implementation of the MS-DOS FAT filesystem, making 3.11 the first public appearance of what would become one of the core filesystem components of Windows 95.² The release also added support for multiple simultaneous network connections. What it did not include was long filename support or the fuller base-OS features planned for Windows 95, as those were held back.²

The TCP/IP-32 add-in, available for Windows for Workgroups, extended its reach onto TCP/IP networks and remained in common business use well beyond the product's nominal replacement by Windows 95.⁶⁷

Networking Architecture

The design premise was straightforward: any WFW machine could share its files, printers, and (via the /S switch on the appropriate driver) even its CD-ROM drive with other machines on the local network.¹²¹³ Connections could be made to Windows NT servers or to other WFW peers, and the NetWare client stack could run alongside the Microsoft networking layer, giving a machine access to both Microsoft and Novell resources simultaneously.⁶⁷

The BYTE editorial staff captured the practical reality clearly: on their own NetWare LAN, WFW and NetWare shared the same wire without conflict. Everyone kept using the NetWare shell for file and print services while WFW workgroups coexisted on top of it. The verdict from that experience was that WFW made Windows and NetWare both more capable and easier to access, so the products complemented rather than competed with each other.¹ Windows NT, by contrast, was designed to displace NetWare's back-end role entirely, which was a very different proposition.¹

WFW was not, however, a server-class product. A WFW machine sharing resources could be slowed noticeably by the overhead, and the practical guidance from the period advised against running screen savers on any machine acting as a shared resource, since they degraded throughput. A dedicated sharing machine could reallocate processor priority toward network services through the Performance Priority slider in the Network Control Panel.³

Installation & Hardware Detection

Windows for Workgroups introduced early device-sensing at install time, attempting to identify the video adapter, mouse, keyboard, and network adapter automatically.² This was modest compared to what Windows NT could do (NT extended detection to SCSI devices and other hardware), but it was real groundwork for the Plug and Play work that would reach users with Windows 95.²

Third-party add-ons treated WFW as a known, stable platform. Sun's PC-NFS product explicitly listed compatibility with MS-DOS, Windows, and Windows for Workgroups, and noted that NetWare and PC-NFS clients could coexist on the same WFW machine, confirming the heterogeneous-network role WFW occupied in practice.¹⁴ PCMCIA hardware such as the SCM SwapBox required its own Card and Socket Services software when installed under Windows or WFW, whereas Windows 95 handled the same hardware natively.⁹

Compatibility had limits. Intel's iRMX real-time OS, when configured to run concurrently with DOS/Windows, supported Windows 3.0, 3.1, and 3.11, but explicitly excluded Windows for Workgroups 3.1 and 3.11 from that concurrent mode, a small indicator of the edge cases WFW's hybrid architecture created.¹¹

In the Market

By late 1994, Windows for Workgroups 3.11 was a standard line item in the PC mail-order catalogs, priced at $145.⁴ OEM bundling was common: mid-1995 advertisements for Pentium 75, 90, and 100 MHz desktop and laptop systems routinely listed MS-DOS 6.2 and Windows for Workgroups as the standard software load, alongside MS Office Pro or MS Works.⁵ Windows 95 was visible on the horizon but not yet shipped, and WFW was the practical choice for a machine that needed networking without the overhead of NT.

Legacy

Windows for Workgroups 3.11 ended up being more important as a technology incubator than as a product in its own right. The protected-mode FAT filesystem that debuted in 3.11 was a direct ancestor of the Windows 95 filesystem architecture.² The TCP/IP-32 stack kept WFW machines on corporate networks long after Windows 95 arrived.⁶⁷ Even the modest hardware auto-detection at install time fed into the larger Plug and Play effort.²

What WFW was not (and what some of its marketing implied it might be) was a genuine NetWare alternative for organizations that needed centralized administration, strong security, or serious file server performance. It was a peer-to-peer product on top of a shell on top of DOS, and the architecture showed. The million-plus units shipped in year one, the long tail of OEM bundles, and the TCP/IP-32 add-in's continued presence on corporate desktops all point to a product that succeeded by being good enough for the smaller network, not by being exceptional at anything.

References

1. BYTE-1993-00 (1993)
2. Inside Windows 95 Adrian King 1994 (1994)
3. STR1020.TXT.generated
4. PCMagazine V13N17 19941011 (1994)
5. 1995 09 BYTE 20-09 20 Years (1995)
6. URP 10th edition
7. URP 11th edition
8. TheA+ReferenceBook Phil Croucher 2000 (2000)
9. 01-50-001 SCMSwapBoxHardwareSoftwareInstallation
10. 611032-003 iRMX Installation and Startup Dec95
11. URP 8th edition
12. URP 4th edition
13. SunExpert-v04n12-1993-12 (1993)