Windows 3.1 For Workgroups

Win31DOSBox: Windows 3.1 for 64-bit Windows

Windows 3.11 Workgroups Disk Images
Windows 3.0 / 3.1 For Workgroups 3.11
Windows 3.1 For Workgroups Download
Windows 3.1 For Workgroups
Change Homegroup To Workgroup

Using a PCI Matrox Millennium G200, it's possible to use Windows for Workgroups 3.11 at reasonably high resolutions and color depths. The AGP version might a. Windows for Workgroups 3.1 was released alongside Windows 3.1 in 1992 and featured support for networking. It was updated to Windows for Workgroups 3.11 in 1993. A separate simplified-Chinese release called Windows 3.2 was also made, fixing problems related to input of Chinese characters. Microsoft Windows for Workgroups (WfW) 3.11, released back in 1993, was the first operating system I ever used. As the name suggests, WfW was designed for networking in workgroups of a few people and workstations. This included centralized authentication, file and printer sharing based on Microsoft NetBEUI or NetBIOS (transported for example over Novell’s IPX/SPX Continue reading.

Windows 3.0 / 3.1 for Workgroups 3.11 Windows 3.x was the first to gain significant development and commercial traction. It combined the 8086, 286, and 386 modes of Windows 2 in to one package. It replaced the MSDOS Executive with a Program Manager and File Manager similar to those in OS/2 1.x.
Windows 3.11 The successor of Windows 3.10 was Windows 3.11 for Workgroups (WfW) with network abilities for use as a client in an network. The operating systems supports now beside Netbeui for the first time TCP/IP too. WFW could combine and show up to 25 computers in a working group. DOS drivers remains resistant after the Windows start.

Note: You probably do not need this system; use winevdm instead!

For most Windows 3.1 applications, this system is no longer needed. Instead, use the winevdm system that lets you run 16-bit Windows applications transparently in 64-bit Windows. I have created an installer that effortlessly installs winevdm (also known as otvdm), and you may read about and download it here. If you find an application that does not run under winevdm, then post a bug report on the winevdm GitHub page linked above.

A DOSBox-based Windows 3.1 system

64-bit Windows can run software written for Windows 3.x only through the use of an emulator such as DOSBox.

This page provides a setup program that makes it easy to create a Windows 3.11 system that runs under DOSBox. The setup program does the installation for you, but you will need to provide a full set of Windows 3.1x or Windows for Workgroups 3.11 installation files, disks, or disk images, or a Windows 3.1x or Windows for Workgroups 3.11 installation CD (or CD image file), or an MSDN download of Windows for Workgroups 3.11. You may use the installation files or disks from any roman-alphabet version of Windows 3.11. (No product code is required when installing Windows 3.x.)

Unlike most other Windows 3.1x implementations for modern Windows, this system can print to your current Windows default printer or any other printer installed in your host Windows system, and it can exchange text between the Windows 3.1x clipboard and the host Windows clipboard.

This system includes sound, display, and joystick drivers, but it does not include advanced features like WinG and Win32s, which can be added by following the guide described below. It also includes icons that will install WinVideo and QuickTime for Windows if you want them.

Note: This system was updated 5 January 2021; the installation program uses a 2018 version of DOSBox, but the system uses a custom build of DOSBox-X when running Windows 3.11.

Windows 3.1x installation files (or disks , disk images, CD, or CD image) should be easy to find on eBay or elsewhere. MSDN (VisualStudio.com) subscribers can download and use en_wfw311.exe, which contains the latest version of Windows for Workgroups 3.1x, or any other roman-alphabet language version of the MSDN download of WfW311 (e.g. fr_wfw311.exe). Microsoft's license agreement for Windows 3.x gave you the right to make an archival copy of the installation media. Perhaps you can find that copy and use it.

Note: The MD5 hash for the authentic MSDN version of en_wfw311.exe is AFA00ADE9F31F4C4470D2D5B1462D5D7

When you have the Windows 3.1x installation files or disks or disk images, download the system setup archive here. Extract the contents of the archive to any convenient directory. The contents include a folder named Win31DOSBox with a number of subfolders.

How to install Win31DOSBox

1. Find the Win31DOSBoxSETUP folder in the files that you extracted from the downloaded system setup archive. (I assume that you have Windows 3.11, but the installation should work with the earlier 3.1 version.)

2. Then copy any of the following into the Win31DOSBoxSetup folder, depending on how you obtained the Windows 3.11 installation files:

An .ISO file that contains the Windows for Workgroups 3.11 installation files (typically found with a name like Winfw311.iso). Just copy the .ISO file into the folder; do not mount it or extract items from it.
A set of the six to nine .IMG files containing disk images of the Windows 3.11 or Windows for Workgroups 3.11 installation floppy disks. Just copy the full set of image files; do not mount them or extract them. (Different versions will have different numbers of disks.)
A copy of the Microsoft Developer Network self-extracting archive of the Windows for Workgroups 3.11 installation files, named en_wfw311.exe. (or the corresponding file for any other roman-alphabet version). Just copy the archive; you need not extract the contents.
If you have all the installation files (from an ISO or a set of IMG files) in a single folder, then copy the full set of installation files. Do not make separate subfolders; simply copy all the files into the Win31DOSBoxSetup folder.

3. Run InstallWin31DOSBox.exe. If you copied an ISO or a set of IMG files, this installer program will extract the contents of those files and then install Windows 3.11.

Note: If you are installing Windows for Workgroups, be prepared to wait a minute or more while Windows Setup displays a message saying it is trying to identify your network adapter. (It won't find a network adapter, but I can't figure out how to make it skip this step.)

Troubleshooting: If you see any error messages while Windows is being installed, delete the entire contents of the Win31DOSBoxC-DRIVEWINDOWS folder and try again. You may also need to empty the SETUP folder and copy the installation files into it again.

4. When the installer is done, it will offer to run Win31DOSBox.exe to start Windows 3.11. Use Win31DOSBox.exe in the future to run Windows 3.11.

Details: In brief summary this is what the InstallWin31DOSBox.exe program does:

If you use an ISO or EXE version of the installation files, it expands the files and tests whether you are installing Windows 3.1x or Windows for Workgroups 3.11.
It then makes a copy of the Windows 3.x installer's SETUP.SHH automated setup file, modifies it (manipulating its format to use ANSI instead of Unicode) by adding printers, changing various options, etc.
It then runs the Windows 3.1 setup program, using the customized automated setup file created in the previous step, and exits the new installation.
It then copies system files, sound, video, and other drivers from the StorageAddFiles folder into the Windows folder, and modifies SYSTEM.INI and WIN.INI to use the S3 video drivers, SoundBlaster sound driver, and the joystick driver.
It also copies two PC Magazine utilities by Douglas Boling, HK and WINCMD, and a program-group creator program by Alan G. Hill named GROUPBLD.
It then starts up Windows 3.1x again, using WINCMD to run GROUPBLD and create and modify program manager groups, and then exits Windows 3.1x again.
It then offers to start the fully-installed Windows 3.1x system.

After these steps are complete, the system is then ready to run at any time from the Win31DOSBox.exe program.

You may delete the SETUP and DRIVERS folders after you have the system working as you want it.

You can use the Windows 3.11 Control Panel to change resolution and color depth.

I built this Windows 3.11 system by following the excellent guide provided by Dominus on the Vogons.org site. (I also got some ideas from an earlier, similar system.)

Note: If you want to emulate a Tseng 4000 video card instead of the default S3 card, you should change the dosbox.conf file in the DOSBox folder; study various DOSBox documents online for further information.

How to use Win31DOSBox

If you experience any problems with this system, try this: Shut down Windows 3.11 if it is running. Go to the DOSBox folder in the folder for the system; rename DOSBox-X.exe to any other name. Again run Win31DOSBox.exe. The system will now use an older version of DOSBox instead of the more recent DOSBox-X. You may or may not find this older version more reliable.

To open a document file from the host system in the default Windows 3.11 application for that file (for example, to open a .WRI file in Windows 3.11 Write.exe), drop the file on the Win31DOSBox.exe icon. If all goes well, Windows 3.11 will open, and the file will open automatically in its default application. When you close the file, Windows 3.11 will automatically exit. (In Windows 3.11, the folder containing the document will be visible as drive Y:.)

To 'map' a single folder in the host system to a drive letter in Win311, drop a folder from the host Windows Explorer on the Win31DOSBox.exe icon. The folder will be visible in Windows 3.11 as drive Y:.

To open a document in your Win311 system in the default application for that document in the host Windows system (for example, to open a .DOC file in Word 2016), use the Open File with Host App program found in the Win31DOSBox program group.

To copy a file from your Win311 system to the desktop folder of your host Windows system, use the Copy File to Host Desktop item found in the Win31DOSBox program group.

To print from Win311, print to the default printer in Win31; the output will be sent to your default Windows printer. Three printers are provided (the names will include the version number of the host Windows system, as shown below for Windows 10):

Win10 Printer: This is the default host Windows printer. If you use the Win311 Control Panel, Printers menu, you can 'connect' to a different output, named C:PTRSELECT.PS. When you print to this output, the host system will pop up a list of installed printers for you to choose the one to print to.
Win10 Clipboard: This 'prints' to the host Windows clipboard. Mostly used for copying text to the clipboard as described below.
PDF to Win10: This 'prints' a PDF file to the host Windows desktop. If the document you are printing is untitled, the resulting PDF will have an arbitrary filename based on the current date and time.

Change the default host printer for this system by following the instructions in the Drive and printer options settings section elsewhere on this page.

To copy from the 'host' clipboard to the Win31 clipboard, press Ctrl-Shift-Alt-V. (This runs the Clipboard to Host item in the Win31DOSBox program group.) A message will appear briefly saying that the clipboard has been imported. Now press Ctrl-V to paste that text into the current Win31 application.

You may also want to experiment with pressing the Pause key (on a full-sized keyboard) or Ctrl-Alt-F4 (on any keyboard); these use different methods for importing text from the host directly to a Win31 applications; the method used by the Pause key may be able to copy accented characters; the method used by Ctrl-Alt-F4 will only import plain ASCII text.

To copy text already in the Win31 clipboard to the 'host' clipboard, press Ctrl-Shift-Alt-C. (This runs the Get Host Clipboard item in the Win31DOSBox program group.) A brief message will appear saying the text has been exported.

To toggle between windowed and full-screen mode, press Ctrl-Alt-Enter. (This and other keyboard shortcuts are different from those in standard DOSBox. Use the System Menu - the icon at the upper left corner of the DOSBox window - and choose Keyboard Help... for details.)

Keyboard shortcuts: These keyboard shortcuts may be useful; they are not the same as the shortcuts in standard DOSBox!

Ctrl-Alt-Enter: Toggles between full-screen and windowed mode
Alt-Pause: Pause DOSBox
Ctrl-Alt-F4: pastes ASCII text into DOSBox
Ctrl-Alt-F10: Capture or release mouse to/from DOSBox window (or use Alt-Tab)
Ctrl-Alt-F11: Slow down the emulation
Ctrl-Alt-F12: Speed up the emulation
Ctrl-Alt-Home: Restart DOSBox
Ctrl-Shift-Alt-C: Copies Win31 clipboard to host clipboard (if HK.EXE is running in Win31)
Ctrl-Shift-Alt-V: Copies host clipboard to Win31 clipboard (if HK.EXE is running in Win 31); press Ctrl-V in a Win31 application to paste the transferred clipboard into the document
Pause: Pastes text into DOSBox

Drive letter mapping: When Win31DOSBox starts up, it automatically maps all the drive letters on the host system to the same drive letters in Win31 - except for host drives C: (used in DOSBox for the Win31DOSBoxC-DRIVE folder), X: (reserved for the option to map your actual host drive C: to a drive letter accessible in DOSBox), and Y: (used in DOSBox as the drive letter for the folder that contains a document file or folder dropped on the Win31DOSBox icon and opened in Win31DOSBox). This system does not automatically map any other drives that contain a modern Windows system (with folders like windowssystem32), to avoid any possible (though unlikely) damage.

Fine-tune the drive-mounting options by following the guide to Drive and printer option settings elsewhere on this page.

By default drive A: in Win31 is the folder Win31DOSBoxA-Drive. If you have a physical floppy drive in your system, it will be mapped as drive B: in Win31.

To use this system to run only one 16-bit Windows 3.x program and then close, use one of these three methods:

Either (a). Create a desktop shortcut to Win31DOSBox.exe. Select it; press Shift-F10; choose Properties, and in the Shortcut tab, in the Target field, add a space, then the name of the program you want to run, for example Write or Write.exe (no quotation marks). This method works most reliably when the program is in the Windows folder. You will see the Windows 3.11 desktop when the program runs, but Windows will close when you close the program. Note: This method uses Steven Henk Dom's RunExit utility, which this system installs in the Windows folder.

Or (b). First run the program (for example, Write) normally in Win31, and make sure its window is correctly positioned. Then shutdown Win31. Next, edit the SYSTEM.INI file in the C-DRIVEWINDOWS folder. Change the line that reads shell=progman.exe so that it reads instead shell=X:PathToMyapp.exe (using the drive and path of your application). Save the file. When you next run Win31, your program will start automatically and will fill the Windows 3.11 window. When you exit the program, Win31 will close. (If you see an error message from your program saying that a .DLL file is required, find that file in your program's own folder and copy it into the C-DRIVEWINDOWSSYSTEM folder in Win31DOSBox.) You can now either rename the DOSBoxWin31.exe program with the name of your 16-bit program, or create a desktop shortcut that uses that name. (I use this method to run the old Windows 3.1 version of Instant Recall.)

Or (c). Create a desktop shortcut to Win31DOSBox.exe. Select it; press Shift-F10; choose Properties, and in the Shortcut tab, in the Target field, add a space and then a string that looks like this: /shell=write.exe (note the forward slash immediately before 'shell='). The name after the equals sign should be the program that you want to run. Don't use spaces or quotation marks in this string. This method temporarily does what method (b) above does: When you launch the shortcut, the SYSTEM.INI file is modified so that the program you selected is used as the shell, instead of the Program Manager. Then, after Win31 starts up, the shell= line in SYSTEM.INI file is changed back to its original setting. With this method, you can create multiple shortcuts, each running a different program as the shell (but you can only run one at a time).

To force Win31DOSBox to run in a second monitor, or at any specific position on screen: Go to the Win31DOSBoxDOSBox folder and create inside it a text file named ScreenPos.txt. The file should consist of two lines, the first line with the desired horizontal position (in pixels) of the upper-left corner of the DOSBox window (counting from the left edge of your leftmost monitor, the second line with the desired vertical position of the upper-left corner, counting from the top of the topmost monitor. So, if you have two monitors, and you want DOSBox to run in monitor 2, you might have a file that looks like this - but remember that you will need to experiment to find the right numbers for your system:

1660
100

The temporary.conf and drives.bat files are re-created each time the program is run. Do not waste your time editing them.

Drive and printer option settings

You can fine-tune drive assignments ('mapping') and printer options by using Windows Notepad or any other text editor to modify the file Win31DOSBoxDOSBoxWin31DOSBox.ini. The options are these.

Under [drives], the options and their default settings are these:

MountHostDrives=true Change this to false if you do not want any host drives mounted in DOSBox. Whether this setting is true or false, you can still specify that host CDROM drives will be mapped in DOSBox, or that specific host drives will be mapped in DOSBox, by using the options below.
MountCDROMsOnly=false If this is set to true then only host CD-ROM drives will be mapped, not other drive letters, unless you specify additional drive letters in the next setting.
MountOnlyDriveLetters= By default, this value is empty (nothing after the equals sign). If you enter one or more host drive letters - for example DGHK - then only these drive letters will be mapped in DOSBox. If you include a drive letter that does not exist on the host system, that drive letter will be ignored.
MountWindowsDrives=false By default this system does not map host drives that have modern Windows systems installed on that drive. Change this option to true if you want to map host drives that have modern Windows systems. Use this option with extreme caution, and don't say I didn't warn you that you can seriously mess up a Windows system if you choose to enable it!
MountCasX=false Change this option to true if you want to map your host drive C:, which probably contains your Windows system to drive X: in DOSBox. Use this option with extreme caution, and don't say I didn't warn you that you can seriously mess up a Windows system if you choose to enable it!

Under [printer] the only current option is:

UseThisPrinter= By default this value is empty (nothing after the equals sign), and when you print from Win31DOSBox (without choosing the option to select a printer at each print job), the system prints to your default Windows printer. If you want Win31DOSBox to print by default to a printer that is not your default printer in your host system, enter its name (as the name appears in Windows Print dialogs) after the equals sign, for example: Office LaserJet 400 - and do not use quotation marks. Of course, Office LaserJet 400 is only an example; use the name of an actual printer attached to your system.

Send 'raw' output to your printer: If you really, really know what you're doing, you can send 'raw' output from Win31 to a PCL, PostScript, or other printer that uses its own printer language; Win31DOSBox will not create an intermediate PDF file before printing, as it usually does. To accomplish this, edit WIN.INI, and add one or both of these lines to the [ports] section:

C:PTROUTPUT.RAW=
C:PTRSELPTR.RAW=

If you then use the Printers applet in the Control Panel to 'Connect' C:PTROUTPUT.RAW= to your PCL or PostScript printer, Win31DOSBox will send the 'raw' output to your default host printer. If your default host printer cannot process the raw data, you will waste a lot of paper. If you 'Connect' your printer to C:PTRSELPTR.RAW= then you will be prompted to select a printer each time you print. Again, if your default host printer cannot process the raw data, you will waste a lot of paper. You really need to know what you are doing if you want to use this feature. Don't even think about trying it unless you're an expert.

Install programs in your Win31DOSBox system

Add the required software or installation files to the C-DRIVE folder, which is drive C: in Win31, If your program does not need to be installed, simply create a folder for it in the Win31DOSBoxC-DRIVE folder with a name like MYAPP and copy the program into it. Then run it in Win31DOSBox from C:MYAPP. If your software needs to be installed under Win311, read on:

To install new software in Win31 from installation files, start by creating a new folder in the host system's Win31DOSBoxC-DRIVE folder, perhaps called something like INSTALL. (This folder will appear in Win31DOSBox as C:INSTALL.) Copy the installation files from your new software into this new folder. Startup Win31DOSBox. In the Program Manager, use File/Run, and navigate to your software's install program in the C:INSTALL folder.

To install new software from a CD-ROM: Insert the CD-ROM in the drive and run the setup program from inside Win31, using the drive letter of your CD-ROM. (You may - but possibly won't - need to insert the CD-ROM before starting Win31DOSBox.)

If you have an ISO image of a CD-ROM, right-click it in your host Windows system and choose the Mount option (available under Windows 10; available under earlier versions if you install, for example, Virtual Clone Drive); this assigns a drive letter to the ISO image. Restart Win311 to access the contents of the image under its drive letter.

To install new software from diskettes or diskette images: If you have a physical floppy drive, it will automatically be mounted as drive B: in DOSBox. However, you probably have disk image files of the software that you want to install; drop one or more such images on the Extract to A-Drive Folder.exe application the Win31DOSBox folder, and it will automatically extract the files into the A-DRIVE folder; the files will be accessible on Drive A: in DOSBox.

If you have installation software that insists on scanning all your drives, save time by launching Win31DOSBox from the DOSBox No Host Drives.cmd shortcut in the Win31DOSBoxDOSBox folder. This will launch Win31DOSBox with only drive C: mounted in DOSBox; this drive contains the Windows folder. Drive C: in DOSBox is the Win31DOSBoxC-DRIVE folder in your host Windows system. That folder contains a dummy autoexec.bat and config.sys file that your software may want to write to. You may need to take further steps to add these commands to the standard dosbox.conf file in the same folder.

If your program requires SHARE.EXE (e.g. Microsoft Word 6.x), then proceed with caution, because these instructions are not designed for use with database applications! They will only work with applications like word-processors and spreadsheets. First, be certain that you have installed Windows for Workgroups 3.11, not plain Windows 3.1x. Edit the dosbox.conf file in the Win31DOSBoxDOSBox folder, and remove the 'rem' comment from the line near the end that reads 'rem fakeshar'. This will cause a program to be launched that can, in some cases, fool Windows into acting as if SHARE.EXE were running, even though the actual sharing features will not be available. This trick should allow you to install Word 6.0c (and possibly other Microsoft Office applications, though I have not tested these). (Not tested with earlier versions than Word 6.0c!!!)

The UTIL (Utilities) folder

The C-DRIVEUTIL folder contains a generous selection of utilities, mostly from PC Magazine, that may be useful in this system. One is used by the system (HK.exe) and the other is used by the installer (WINCMD) and can be used for many other purposes. You will also find the third-party GROUPBLD.EXE in the C-DRIVEWINDOWS folder; this is used by the installation program to create and modify Program Manager groups.

Third-party (non-PCMag) utilities:

Printclp – Prints the contents of the clipboard
RunExit – Runs a program than exits Windows; use from the command line
SprLoad (SuperLoad) – More options forth LOAD= and RUN= lines in WIN.INI
WinExit – When WinExit runs, you can click on its icon to exit Windows
without going through Program Manager

PC Magazine utilities:

InCtrl2 – Records files installed by an installation program so that
they can be removed later
RecEdit – Edits files created by the Windows 3.1 Recorder utility
TapeCalc – A calculator that creates a paper-type record of calculations
WinCmd – Runs automated macros (used in installing this system)
COA – Lets you change the location of an installed program without
reinstalling it
Defedit – Lets you set a default editor for document files with extensions
that haven't been associated with a particular program
Dropkick - Launches programs from a popup menu when you click a mouse
button on a blank space in the Windows 3.1 desktop.
Find – A text-search utility
HK – A hotkey manager (used by this system)
LnchCtrl – Lets you set the environment variables and the window size
and position when launching an application; also controls the behavior
of DOS applications run from Windows 3.1
MyGrps - Lets you use customize icons for Program Manager groups
Paste (PasteBoard) - lets you cut, copy, and paste text from several
sources or several areas within a file without switching back and forth
PLIcon - Controls the position of minimized icons on the desktop
SaveIt - Restores your Windows desktop to the state it was in when you
shut Windows down; programs running when you exited Windows are reopened
ScInvoke – Launches the default screensaver
SuperPad - A replacement for Microsoft Windows' Notepad that can edit
files of any size
WCompare – Highlights the differences in two text files; provides full
editing and printing capabilities
WinBar - Configurable rendition of the Windows 95 Taskbar that runs
under Windows 3.1
WinTidy – Saves and restores the layout of Program Manager groups
WMatch – Compares files in two directories
WSwin – A file and text-search utility

A note on WINCMD: This system uses Douglas Boling's WINCMD when initializing. Different versions of WINCMD were separately documented in PC Magazine, and this documentation is available via Google Books. However, the 27 April 1993 issue of PC Magazine, which contained the full documentation of the first release of WINCMD is missing from Google Books, so I have posted a scan of that initial documentation here.

Further notes

This system is a work in progress. Please send suggestions for further development.

The copy of DOSBox-X.exe used in this system is a custom build that does not use the same keyboard assignments as the original DOSBox-X, and has a few minor internal changes. One such change is that directories of hard-disk-folders are automatically refreshed and do not need the 'rescan' command used in DOSBox-X.

I am grateful to Douglas Boling and to many people associated with DOSBox and its support forum, especially those who use the names Qbix, Dominus, and ripsaw8080.

The printing and clipboard-exchange techniques used in this system are based on my DOSBoxWP system for running WordPerfect for DOS under DOSBox.

Edward Mendelson (em thirty-six [at] columbia [dot] edu, but with two initials and two numerals before the [at] sign, not spelled out as shown here).

Lua error in Module:Redirect at line 61: could not parse redirect on page 'Windows Janus'.

Windows 3.1x
Support status
A version of the Microsoft Windows operating system
300px
Developer	Microsoft
Written in	{{#property:p277}}
Source model	Closed source
Released to manufacturing	April 6, 1992; 28 years ago
Latest release	3.11 / December 31, 1993; 27 years ago^[1]
License	Commercial software
Preceded by	Windows 3.0 (1990)
Succeeded by	Windows 95 (1995)
Official website	{{#property:P856}}
Unsupported as of December 31, 2001

Windows 3.1x (codenamed Janus)^[2]^[3]^[4] is a series of 16-bitoperating systems produced by Microsoft for use on personal computers. The series began with Windows 3.1, which was first sold during April 1992 as a successor to Windows 3.0. Subsequent versions were released between 1992 and 1994 until the series was superseded by Windows 95. During its lifespan, Windows 3.1 introduced several enhancements to the still MS-DOS-based platform, including improved system stability, expanded support for multimedia, TrueTypefonts, and workgroup networking.

Windows 3.1 was originally released on April 6, 1992; official support for Windows 3.1 ended on December 31, 2001, and OEM licensing for Windows for Workgroups 3.11 on embedded systems continued to be available until November 1, 2008.^[5]

1Editions
- 1.1Windows 3.1
2Windows for Workgroups
3Add-ons
4Applications
6Controversy

Editions

Windows 3.1

Windows 3.1 (originally codenamed Janus), released on April 6, 1992, introduced a TrueTypefont system (and a set of highly legible fonts), which effectively made Windows a viable desktop publishing platform for the first time. Similar functionality was available for Windows 3.0 through Adobe Type Manager (ATM) font system from Adobe.

Windows 3.1 was designed to have backward compatibility with older Windows platforms. As with Windows 3.0, version 3.1 had File Manager and Program Manager, but unlike all previous versions, Windows 3.1 cannot run in real mode. It included Minesweeper as a replacement for Reversi (though Reversi was still included in some copies).

Windows 3.1 Multimedia PC Version (Beta only, released Nov 1992 – codenamed Bombay) included a media viewer, and the ability to play video files. It was targeted to the new multimedia PC and included sound and video integration with CD-ROM support.

Improvements over Windows 3.0

File:Windows 3.1.png

Windows 3.1 showing some of the personalization options available.

Windows 3.1 dropped real mode support and required a minimum of a 286 PC with 1 MB of RAM to run. The effect of this was to increase system stability over the crash-prone Windows 3.0. Some older features were removed, like CGA graphics support (although Windows 3.0's CGA driver still worked on 3.1) and compatibility with real mode Windows 2.x applications.

Truetype font support was added, providing scalable fonts to Windows applications, without having to resort to using a third-party font technology such as Adobe Type Manager. Windows 3.1 included the following fonts: Arial, Courier New, Times New Roman, and Symbol (a collection of scalable symbols) in regular, bold, italic, and bold-italic versions. Truetype fonts could be scaled to any size and rotated, depending on the calling application.^[6]

In 386 Enhanced Mode, windowed DOS applications gained the ability for users to manipulate menus and other objects in the program using the Windows mouse pointer, provided that DOS application supported mice. A few DOS applications such as late releases of Microsoft Word could access Windows Clipboard. Windows' own drivers couldn't work directly with DOS applications; hardware such as mice required a DOS driver to be loaded before starting Windows.

Icons could be dragged and dropped for the first time, in addition to having a more detailed appearance. A file could be dragged onto Print Manager icon and the file would be printed by the current printer, assuming it was associated with an application capable of printing, such as a word processor. Alternatively, the file could be dragged out of File Manager and dropped onto an application icon or window for processing.^[7]

While Windows 3.0 was limited to 16 MB maximum memory, Windows 3.1 can access a theoretical 4 GB in 386 Enhanced Mode. (The actual practical ceiling is 256 MB.^[8]) However, no single process can use more than 16 MB. File Manager was significantly improved over Windows 3.0. Multimedia support was enhanced over what was available in Windows 3.0 with Multimedia Extensions and available to all Windows 3.1 users.

Windows 3.1 was available via 720 KB, 1.2 MB, and 1.44 MB floppy distributions. It was also the first version of Windows to be distributed on CD-ROM — although this was more common for Windows for Workgroups 3.11, which typically came with MS-DOS 6.22 on one CD. Installed size on the hard disk was between 10 MB and 15 MB.

32-bit disk access (386 Enhanced Mode only) brought improved performance by using a 32-bit protected mode driver instead of the 16-bit BIOS functions (which necessitate Windows temporarily dropping out of protected mode).

Windows 3.1's calendar saves its files ending with .cal.^[9]

Windows 3.1 also introduced Windows Registry, a centralized database that can store configuration information and settings for various operating systems components and applications.

Windows 3.1 was the first version of Windows that could also launch Windows programs via Command.com while running Windows.

Windows 3.1 for Central and Eastern Europe

A special version named Windows 3.1 for Central and Eastern Europe was released that allowed use of Cyrillic and had fonts with diacritical marks characteristic of Central and Eastern European languages. Microsoft introduced its own code page (Windows-1250) and supported its use in violation of many countries' ISO standards (e.g., the official Polish codepage is ISO-8859-2, which was ignored by Microsoft but is supported by contemporary Internet Explorer versions). Similarly, Microsoft also released Windows 3.1J with support for Japanese, which shipped 1.46 million copies in its first year on the market (1993) in Japan.^[10]

Modular Windows

Modular Windows is a special version of Windows 3.1, designed to run on Tandy Video Information System.

Windows 3.11

Windows 3.11 was released on November 8, 1993. It did not add any feature improvements over Windows 3.1; it only corrected problems. Microsoft replaced all retail versions of Windows 3.1 with Windows 3.11 and provided a free upgrade to anyone who currently owned Windows 3.1.^[11]

Windows 3.2 was only released in Simplified Chinese

Windows 3.2

On November 22, 1993, Microsoft released a Simplified Chinese version of Windows for the Chinese market. A year later, an update was released, which identified itself as Windows 3.2. Thus, Windows 3.2 is an updated version of the Chinese version of Windows 3.1.^[12] The update was limited to this language version, as it fixed only issues related to the complex writing system of the Chinese language.^[13]

Windows 3.2 was generally sold by computer manufacturers with a ten-disk version of MS-DOS that also had Simplified Chinese characters in basic output and some translated utilities.

Windows for Workgroups

File:Windows for Workgroups.png

Network capabilities of Windows for Workgroups 3.11

Windows for Workgroups is an extension that allowed users to share their resources and to request those of others without a centralized authentication server. It used SMB protocol over NetBIOS.

Windows for Workgroups 3.1

Windows for Workgroups 3.1 (originally codenamed Winball and later Sparta), released in October 1992,^[14] is an extended version of Windows 3.1 that features native networking support. It comes with SMB file sharing support via NetBIOS-based NBF and/or IPX network transport protocols and introduces the Hearts card game and VSHARE.386, a VxD version of SHARE.EXE (a terminate-and-stay-resident program).

Windows for Workgroups 3.11

Windows for Workgroups 3.11 (originally codenamed Snowball) was released on August 11, 1993,^[15] and shipped in November 1993.^[16] It supported 32-bit file access, full 32-bit network redirectors, and VCACHE.386 file cache, shared between them. WFW 3.11 dropped standard mode support and requires a 386 machine to run.

A Winsock package was required to support TCP/IPnetworking in Windows 3.x. Usually third-party packages were used, but in August 1994, Microsoft released an add-on package (codenamed Wolverine) that provided TCP/IP support in Windows for Workgroups 3.11. Wolverine was a 32-bit stack (accessible from 16-bit Windows applications via WinSock Thunk), which gave it superior performance to most of the third-party TCP/IP Windows stacks available. However, it was only compatible with Windows for Workgroups 3.11, and lacked support for dial-up. Wolverine stack was an early version of the TCP/IP stack that would later ship with Windows 95, and provided an early testbed for the 16-to-32-bit compatibility layer that was crucial to Windows 95's success.

Following the release of MS-DOS 6.22 in 1994, WFW 3.11 largely replaced Windows 3.1 for OEM installations on new PCs due to its improved capabilities and greater stability.

Add-ons

Video for Windows

Video for Windows was first introduced in November 1992 as a reaction to Apple Computer's QuickTime technology which added digital video to Macintosh. Costing around $200,^[17] the software included editing and encoding programs for use with video input boards. A runtime version for viewing videos only was also made available. Originally released as a free add-on to Windows 3.1 and Windows 3.11, it then became an integral component of Windows 95 and later. Like QuickTime there were three components in Video for Windows. The technology introduced a file format designed to store digital video, Audio Video Interleave (AVI). The technology provided an application programming interface that allowed Windows software developers to add the ability to play or manipulate digital video to their own applications. Lastly, it included a suite of software for playing and manipulating digital video.

Windows for Pen Computing

Windows for Pen Computing was a series of Microsoft-produced add-ons for Microsoft Windows versions in the mid-1990s with additional tools for tablet PCs. Windows for Pen Computing (also known as Pen Windows and W4PC) was developed as Microsoft's Pen computing response to PenPoint OS by GO Corporation.^[18] Windows for Pen Computing was rendered obsolete by Tablet PC support for Windows XP Tablet PC Edition in 2002.

Win32s

Windows 3.1x was given limited compatibility with the then-new 32-bit Windows API used by Windows NT by another add-on package, Win32s. There was a rumor that Microsoft did not want to increase any mainstream Windows 3.1x version to something like 'Windows 3.2' because it could be confused with the Win32 API or otherwise distract consumers from upgrading to a 'real 32-bit OS' like the then-upcoming Windows 95 was, though Windows NT 3.1 and 3.5 were both 32-bit operating systems that looked similar in appearance. A game called FreeCell was included for testing the new Win32s functions.

Windows 3.11 Workgroups Disk Images

WinG

To entice game manufacturers to move from DOS to Windows, Microsoft provided a first attempt at high-speed graphics and animation capabilities for Windows 3.1x, introduced in September 1994. Windows' GDI capabilities were originally designed with static images in-mind, allowing only for write-only graphics calls. WinG provided a device-independent interface to graphics and printer hardware, and allowed programs to have both read and write capabilities to the WinGDC (WinG device context).^[19]

Applications

Windows 3.1x introduced new possibilities for applications, especially multimedia applications. During this era, Microsoft developed a new range of software that was implemented on this operating environment, called Microsoft Home, Microsoft Bob being one of the programs.

As the first versions of Windows to enjoy major commercial success and software support, Windows 3.1 and WFW 3.11 quickly replaced DOS as the platform for application software on PC compatibles. Multimedia software (especially games) proliferated, although many games continued to run on DOS until Windows 95.

Program Manager

Program Manager was included in all versions of Windows from version 3.0 until Windows XP Service Pack 1. A non-operable icon library named progman.exe is included in Windows XP Service Pack 2, and the file was removed entirely from Windows Vista.

If Program Manager is started under Windows XP Service Pack 2 and later, it does not appear to run, but when a .grp file created for Windows 3.1 is processed, it converts .grp file contents to a Start Menu folder.

Internet Explorer

Internet Explorer 2 through Internet Explorer 5 were released for Windows 3.1.^[20]

Windows 3.0 / 3.1 For Workgroups 3.11

Promotion and reception

Microsoft began a television advertising campaign for the first time on March 1, 1992. The advertisements, developed by Ogilvy & Mather, were designed to introduce a broader audience to Windows.^[21] Windows 3.1 was shipped worldwide on April 6, 1992, and reached three million sales two months later.^[22] The year of Windows 3.1's release was successful for Microsoft, which was named the 'Most Innovative Company Operating in the U.S.' by Forbes magazine, while Windows became the most widely used GUI-based operating environment.^[23]

Controversy

DR-DOS compatibility

The installer to the beta release used code that checked whether it was running on Microsoft-licensed DOS or another DOS operating system (such as DR-DOS). The code ran several functional tests that succeeded on MS-DOS and IBM PC DOS, but resulted in a technical support message on competing operating systems. If the system was not MS-DOS, the installer would fail. Digital Research, who owned DR-DOS, released a patch within weeks to allow the installer to continue. Microsoft disabled, but did not remove, this warning message for the final release of Windows 3.1. When Caldera bought DR-DOS from Novell, they brought a lawsuit against Microsoft over the AARD code, which was later settled.^[24]^[25]

Legacy

Windows 3.x was superseded by the release of Windows 95 in August 1995. Microsoft officially dropped support for all 16-bit versions of Windows on December 31, 2001.

Windows 3.1 found a niche market as an embedded operating system after becoming obsolete in the PC world. As of November 2008, both Virgin Atlantic and Qantas employed it for some of the onboard entertainment systems on long-distance jets. It also sees continued use as an embedded OS in retail cash tills.^[26] It is also used as a secondary application in DOSBox to enable emulation of Win16 games on 64-bit Windows.

On July 9, 2008, it was announced that Windows for Workgroups 3.11 for the embedded devices channel would no longer be made available for OEM distribution as of November 1, 2008.^[27]

On July 14, 2013, Linux kernel 3.11 was officially named 'Linux For Workgroups' as a tongue-in-cheek reference to 'Windows for Workgroups 3.11'.^[28]

On November 7, 2015, Orly Airport near Paris, France, had a major computer glitch that interrupted its operations for some time. The newspaper Le Canard Enchaîné later revealed that the glitch happened in an essential meteorological system called DECOR, which at the time of the incident still ran on Windows 3.1 – 23 years after the operating system's release and 14 years after Microsoft ceased to support it. The French Transportation Minister promised to have the system replaced by 2017, but the secretary general of the French air traffic controller union expressed his skepticism.^[29]

References

↑http://support.microsoft.com/kb/32905
↑Dandumont, Pierre (October 7, 2009). 'LNDCDJ : Janus / Windows 3.1'. Tom's Hardware (in français). Retrieved July 13, 2014.<templatestyles src='Module:Citation/CS1/styles.css'></templatestyles>
↑'Microsoft Windows 3.1'. Old Computer Museum. Retrieved July 13, 2014.<templatestyles src='Module:Citation/CS1/styles.css'></templatestyles>
↑Grabham, Dan (October 16, 2009). 'Windows retrospective: boot screens through the ages'. TechRadar. Retrieved July 13, 2014.<templatestyles src='Module:Citation/CS1/styles.css'></templatestyles>
↑'Microsoft retires Windows 3.11 on 18th birthday'. theregister.co.uk.<templatestyles src='Module:Citation/CS1/styles.css'></templatestyles>
↑Edson, Kate (March 1993). 'Windows 3.1 and TrueType Fonts'. PC Update, the magazine of Melbourne PC User Group, Australia. Retrieved October 24, 2014.<templatestyles src='Module:Citation/CS1/styles.css'></templatestyles>
↑Livingston, Brian (1993). More Windows 3.1 Secrets. San Mateo, CA: UDG Books Worldwide. ISBN1-56884-019-5.<templatestyles src='Module:Citation/CS1/styles.css'></templatestyles>
↑https://support.microsoft.com/en-us/kb/84388
↑Microsoft Windows 3.1 Programmer's Reference. Volume 4: Resources. Microsoft Corporation. 1992. ISBN1-55615-494-1.<templatestyles src='Module:Citation/CS1/styles.css'></templatestyles>
↑Virginia Kouyoumdjian (August 1994). 'DOS/V, Windows, Prices, and the Future...' Computing Japan. Retrieved September 4, 2009.<templatestyles src='Module:Citation/CS1/styles.css'></templatestyles>
↑'Windows 3.11'. WinWorld. Syngress MCSA/MCSE Managing and Maintaining a Windows Server 2003 Environment, Page 6. Retrieved March 11, 2015.<templatestyles src='Module:Citation/CS1/styles.css'></templatestyles>
↑'Microsoft Windows Simplified Chinese 3.2 Upgrade Is Available'. microsoft.com. Microsoft.<templatestyles src='Module:Citation/CS1/styles.css'></templatestyles>
↑'Microsoft Windows Simplified Chinese 3.2 Upgrade Is Available'. Microsoft. October 30, 2003. Retrieved September 4, 2009.<templatestyles src='Module:Citation/CS1/styles.css'></templatestyles>
↑'Windows for Workgroups Version History'. Microsoft. Retrieved September 23, 2010.<templatestyles src='Module:Citation/CS1/styles.css'></templatestyles>
↑'Windows 3.1'. GUIdebook. Retrieved September 4, 2009.<templatestyles src='Module:Citation/CS1/styles.css'></templatestyles>
↑'Windows history'. PC Museum. June 17, 2002. Retrieved September 4, 2009.<templatestyles src='Module:Citation/CS1/styles.css'></templatestyles>
↑PC Plus. Future Publishing. May 1993. p. 61.<templatestyles src='Module:Citation/CS1/styles.css'></templatestyles>
↑Eller, Marlin; Edstrom, Jennifer (1998). Barbarians Led by Bill Gates. Owl Books.<templatestyles src='Module:Citation/CS1/styles.css'></templatestyles>
↑Hecker, Chris (June 1, 1997). 'A Whirlwind Tour of WinG'. Gamasutra. Gamasutra. Retrieved November 17, 2014.<templatestyles src='Module:Citation/CS1/styles.css'></templatestyles>
↑'Old Version of Internet Explorer for Windows 3.1'. OldApps.com. Retrieved September 17, 2014.<templatestyles src='Module:Citation/CS1/styles.css'></templatestyles>
↑'Microsoft History 1992'. Microsoft. Archived from the original on October 17, 1996. Retrieved September 4, 2009.<templatestyles src='Module:Citation/CS1/styles.css'></templatestyles> Internet Archive
↑Gill Dunsford (February 23, 2007). 'Feature: Brand Microsoft'. Sales Promotion. Retrieved September 4, 2009.<templatestyles src='Module:Citation/CS1/styles.css'></templatestyles>
↑'Microsoft History 1993'. Microsoft. Archived from the original on October 17, 1996. Retrieved September 4, 2009.<templatestyles src='Module:Citation/CS1/styles.css'></templatestyles> Internet Archive
↑Dan Goodin (April 28, 1999). 'Microsoft emails focus on DR-DOS threat'. CNET News. Retrieved September 4, 2009.<templatestyles src='Module:Citation/CS1/styles.css'></templatestyles>
↑Graham Lea (January 13, 2000). 'Caldera vs Microsoft – the settlement'. BBC News. Retrieved September 4, 2009.<templatestyles src='Module:Citation/CS1/styles.css'></templatestyles>
↑Mark Ward (November 5, 2008). 'The end of an era – Windows 3.x'. BBC News. Retrieved September 4, 2009.<templatestyles src='Module:Citation/CS1/styles.css'></templatestyles>
↑John Coyne (July 9, 2008). 'It's the End for 3.11!!'. Microsoft. Retrieved September 4, 2009.<templatestyles src='Module:Citation/CS1/styles.css'></templatestyles>
↑Linus Torvalds (July 14, 2013). 'Linux 3.11 Kernel Commit'.<templatestyles src='Module:Citation/CS1/styles.css'></templatestyles>
↑Longeray, Pierre (November 13, 2015). 'Windows 3.1 Is Still Alive, And It Just Killed a French Airport'. Retrieved November 13, 2015.<templatestyles src='Module:Citation/CS1/styles.css'></templatestyles>