Microsoft Windows FAQ Frequently Asked Questions Copyright This document is compilation copyright (c) 1990-1994 by Tom Haapanen. It may be freely copied and/or distributed in its entirety as long as this copyright notice is not removed. It may not be sold for profit or incorporated into commercial products without the author's written permission. [Compilation copyright means that you can freely use individual sections of this document, but any significant collection of sections is subject to the copyright.] Note: Revision dates for each section are shown next to the section names on each index page! To find updated sections for a particular date, click the Search button in WinHelp and enter "Updated:" to see the various update dates available. CONTENTS ======== 1. Credits 2. Microsoft Windows 2.1. Windows 1.0 2.2. Windows 2.0 2.3. Windows/386 2.4. Windows 3.0 2.5. Windows 3.1 2.6. Windows 3.11 2.7. Windows for Workgroups 3.1 2.8. Windows for Workgroups 3.11 2.9. Windows NT 3.1 2.10. Win32s for Windows 3.1 2.11. Windows 4.0 ("Chicago" and Win32c) 2.12. Windows NT 3.5 ("Daytona") 2.13. Windows NT 4.0 ("Cairo") 2.14. Windows for Pen Computing 3.1 2.15. Multimedia Windows 2.16. Modular Windows 2.17. Win-OS/2 2.18. Chicago Q&A 2.18.1. What is Chicago? 2.18.2. What is Cairo? 2.18.3. Why does Microsoft have multiple Windows products? 2.18.4. When will Chicago and Cairo ship? 2.18.5. What is Daytona? 2.18.6. How will Chicago make the projected ship date? 2.18.7. What if Chicago ships before Cairo? 2.18.8. What are Chicago's key benefits? 2.18.9. What different Chicago packages will be available? 2.18.10. What will Chicago be called? 2.18.11. What will happen to MS-DOS? 2.18.12. How will Chicago perform on 4 MB? 2.18.13. Will Chicago run current applications? 2.18.14. Will I need to get new device drivers? 2.18.15. Will my current applications work well on Chicago? 2.18.16. When will Chicago's new UI be ready? 2.18.17. Will the new user interface mean a lot of retraining? 2.18.18. What is Plug and Play? 2.18.19. What hardware changes does Plug and Play require? 2.18.20. Won't it take a long time for Plug and Play? 2.18.21. Is the Chicago API different from the Windows NT API? 2.18.22. Will vendors need separate Chicago and NT versions? 2.18.23. When will Chicago applications be available? 2.18.24. Is Chicago completely 32-bit? 2.18.25. How do the 16-bit components fit in? 2.18.26. Will existing networking software work with Chicago? 2.18.27. What about Netware with Chicago? 2.18.28. Will vendors there be Chicago "server" version? 2.18.29. What about Chicago's portability? 2.18.30. What about systems management? 2.18.31. Will there be mobility features? 2.18.32. How will file synchronization work? 2.18.33. Will there be separate NT and Chicago SDKs? 2.18.34. What benefits are there to developers? 2.18.35. Will Visual Basic for Applications be included? 2.18.36. Will Chicago and NT use common device drivers? 2.18.37. Will WOSA services be included? 3. Internet and Usenet 3.1. Usenet 3.2. Usenet Windows newsgroups 3.3. Alternatives to Usenet 3.4. Windows-related mailing lists 3.5. Freeware and shareware by ftp 3.6. Popular Internet ftp sites 3.7. Using archie 3.8. Ftp by email 3.9. FAQs (Frequently Asked Questions) 3.10. More about Internet and Usenet 3.11. FTP archives on CD-ROM 4. Setting Up and Configuring Windows 4.1. System Configuration 4.1.1. Minimum Windows 3.1 configurations 4.1.2. Minimum Windows 3.0 configurations 4.1.3. Minimum Windows NT pre-release configuration 4.1.4. Standard mode vs. 386 Enhanced mode 4.2. Selecting a hardware configuration for Windows 4.2.1. Selecting a CPU/FPU 4.2.2. Selecting the memory size 4.2.3. Selecting a hard disk 4.2.4. Selecting a video adapter 4.3. System BIOS compatability 4.4. Video drivers 4.4.1. Identifying your video card 4.4.2. Locating a driver 4.4.3. Video card manufacturers 4.4.4. Using 256 (or more) colors in Windows 4.4.5. Panacea Winspeed 4.4.6. CGA drivers 4.5. Printer drivers 4.5.1. Eliminating the Ctrl-D in PostScript output 4.5.2. EPS graphics print in portrait even on landscape pages 4.5.3. Hewlett-Packard DeskJet printing problems 4.5.4. PostScript printer uses incorrect fonts 4.5.5. Selecting a PostScript printer driver 4.5.6. Using an Apple Imagewriter or Imagewriter II with Windows 4.6. Math coprocessors and WIN87EM.DLL 4.7. Multimedia 4.7.1. AdLib cards and .wav files 4.7.2. Using MIDI cards with Windows 3.1 4.7.3. SoundBlaster Pro and Windows 3.1 4.7.4. Using the PC's built-in speaker 4.8. System resources 4.9. Networking 4.9.1. Compatible Networks 4.9.2. Windows for Workgroups 4.9.2.1. Accessing Windows for Workgroups drives prior to starting Windows 4.9.2.2. Usin NetBIOS from MS-DOS 4.9.2.3. Sharing a CD-ROM drive with Windows for Workgroups 4.9.3. Windows for Workgroups with TCP/IP 4.9.3.1. DEC Pathworks with NDIS 4.9.3.2. FTP TCP/IP: general 4.9.3.3. FTP TCP/IP: NDIS setup 4.9.3.4. FTP TCP/IP: generic DOS kernel setup 4.9.3.5. SunSelect PC-NFS 4.9.3.6. WinQVT/Net 4.9.3.7. Wollongong Pathway Access/NFS 4.9.4. Novell's NWPOPUP utility won't initialize 4.10. WINSOCK.DLL-based TCP/IP networking 4.11. Integrating with Unix e-mail 4.12. Serial communications 4.12.1. Using COM3 and COM4 4.12.2. Using a high-performance 16550 serial port 4.12.3. DOS boxes and 16550 serial ports 4.12.4. SmartDrive and 16550 high-speed transfers 4.13. Disk drives and virtual memory 4.13.1. Virtual memory and swapfiles 4.13.2. Maximum swapfile size 4.13.3. Windows 3.x and Stacker 4.13.4. SCSI controllers 4.13.5. SmartDrive double buffering on SCSI drives 4.13.6. Windows 3.x and large hard disks 4.14. Troubleshooting 4.14.1. BMP wallpaper won't display correctly 4.14.2. Frequent GPFs (General Protection Faults) 4.14.3. File Manager won't format floppies 4.14.4. Incorrect system version; reinstall the 386 enhanced version of Windows 4.14.5. Mouse hangs when using communications software 4.14.6. Object Linking and Embedding (OLE 2.0) does not work 4.14.7. Parity errors with Windows 3.1 4.14.8. Performance deterioration in a 386 Enhanced mode DOS session 4.14.9. Problems creating a permanent swapfile in Windows 3.0 4.14.10. Program Manager claims only 8 KB of free memory 4.14.11. Using a slow expansion memory board with Windows 4.14.12. Windows 3.0 refuses to run without a file called WINA20.386 4.14.13. Windows 3.1 hangs or crashes during startup 4.14.14. Windows 3.1 hangs or waits a long time on exit 4.14.15. Windows 3.1 Resource Kit won't install 4.14.16. Windows 3.x waits a long time on startup 4.14.17. Windows for Workgroups 3.11 claims ports are in use 5. Windows and DOS 5.1. Configuring DOS sessions 5.1.1. DOS in a window 5.1.2. Lotus 1-2-3 in Windows 5.1.3. Reducing the amount of "jerkiness" in DOS window updating 5.1.4. Extended memory in DOS sessions 5.1.5. Changing the font size for a DOS window 5.1.6. Changing the number of lines inr a DOS window 5.1.7. Mouse in a DOS window 5.1.8. TSRs in DOS sessions 5.1.8.1. VGA graphics in a windowed DOS session 5.2. Troubleshooting DOS applications 5.2.1. Can't run VGA graphics in a window 5.2.2. Corrupted diskettes when copying files in a DOS session 5.2.3. High color and true color modes run out of resources 5.2.4. Out of Environment Space 5.2.5. Protected-mode software 5.3. DOS shells and extenders 5.3.1. QEMM/386 and DesqView/386 5.3.2. MKS Toolkit: setting up 5.3.3. MKS Toolkit: maximizing DOS session memory 5.3.3.1. MS-SH 6. Windows Tips, Tricks and Secrets 6.1. General 6.1.1. Automatically opening applications on startup, with predefined window positions 6.1.2. Changing or bypassing the startup logo 6.1.3. Changing the font used for the icon labels 6.1.4. Disabling the network warnings on startup 6.1.5. Limiting the size of the temporary swap file 6.1.6. Making Windows 3.x act like 2.x runtime 6.1.7. Printing PostScript files without a PostScript printer 6.1.8. Search path in Windows 6.1.9. Swapping the Ctrl and CapsLock keys 6.1.10. Minimizing Windows disk space usage 6.1.11. VT100 emulation for Windows 6.2. Program Manager 6.2.1. Assigning a hotkey to Program Manager 6.2.2. Changing the font used for the icon labels 6.2.3. Changing the program icon 6.2.4. Changing the title of the Program Manager window 6.2.5. Converting documents to PostScript format 6.2.6. Creating your own icons 6.2.7. Creating your own wallpaper 6.2.8. Previewing PostScript output 6.2.9. Restricting the Program Manager 6.2.10. Saving Program Manager settings without exiting Windows 6.2.11. Starting Windows without activating the applications in the Startup group 6.2.12. Starting an application in a different directory 6.2.13. Using environment variables 6.3. Windows accessories 6.3.1. Cardfile: converting to ASCII text 6.3.2. Clock: Windows 3.1 Clock limitations 6.3.3. Control Panel: accessing control panels directly 6.3.4. Help: changing the default window size 6.3.5. Help: changing the keyword colors 6.3.6. Notepad: F5 and current time 6.3.7. Recorder: recording more than 60 seconds of sound 6.3.8. Terminal: keypad 6.3.9. General: "Can't open TEMP.WRI" (or similar message) 6.4. Changing default directories 6.4.1. Bitmaps 6.4.2. Fonts 6.4.3. Icons 6.5. Fonts 6.5.1. Accessing foreign/accented characters 6.5.2. Converting font formats 6.5.3. Converting Macintosh Type 1 (ATM) fonts to Windows 6.5.4. Replacing your System font with a serif font 6.5.5. ZIP code bar code fonts 6.6. Applications 6.6.1. Access: printing a database diagram 6.6.2. Ami Pro 3.0: getting a menu of special characters 6.6.3. DayBook: running on Windows 3.1 6.6.4. Excel: Calling DLL routines 6.6.5. Excel: Doing log-log graphs 6.6.6. Excel: Multiple X-Y graphs on shared X-axis 6.6.7. Improv: converting hexadecimal numbers 6.6.8. Norton Desktop: Wider listbox for Scheduler 6.6.9. Norton Desktop: Using smaller fonts for lists 6.6.10. Procomm Plus: Adding fonts 6.6.11. WinQVTNet: Hiding a gateway 6.6.12. Word for Windows: changing bullet paragraph indent 6.6.13. Word for Windows: centering equations 6.6.14. Word for Windows 2.0: converting batches of WP files to Word 6.6.15. Word for Windows 2.0: custom toolbar icons 6.6.16. Word for Windows: drop caps (large 1st characters of paragraphs) 6.6.17. Word for Windows: fonts larger than 127 points 6.6.18. Word for Windows: foreign-language dictionaries and thesauri 6.6.19. Word for Windows: getting rid of the list of last files edited 6.6.20. Word for Windows: inserting today's date 6.6.21. Word for Windows: linking in subdocuments 6.6.22. Word for Windows: numbering equations 6.6.23. Word for Windows: overlining words 6.6.24. Word for Windows: printing even and odd pages 6.6.25. Word for Windows: removing hard returns on downloaded text 6.6.26. Word for Windows: setting the find file default directory 6.6.27. Word for Windows: turning echo off in a macro 6.6.28. Word for Windows 2.0: using a watermark 6.6.29. Word for Windows: using date formats from [Intl] section in WIN.INI 6.6.30. WordPerfect for Windows 1.0: changing the background color 6.6.31. WordPerfect for Windows 5.2: changing the button bar 6.6.32. WordPerfect for Windows: decrypting a password-protected file 6.6.33. WordPerfect for Windows 5.2: using smart quotes 6.6.34. WordPerfect for Windows 5.2: using bullets 6.7. Gang screens ("Easter Eggs") 6.7.1. Windows 3.0 6.7.2. Windows 3.1 6.7.3. Ami Pro 2.0 6.7.4. Borland (all Windows products) 6.7.5. Corel Draw! 3.0 6.7.6. Excel 3.0 6.7.7. Norton Desktop for Windows 2.0 6.7.8. PageMaker for Windows 4.0 6.7.9. Procomm Plus for Windows 1.0 6.7.10. Word for Windows 1.x 6.7.11. Word for Windows 2.0 7. Applications 7.1. Windows 2.x Applications 7.2. Troubleshooting 7.2.1. Access: version 1.1 upgrade 7.2.2. AllType: converted TrueType fonts not in same family 7.2.3. Ami Pro 3.0: can't read Word 2.0 or WordPerfect 5.2 files 7.2.4. Ami Pro: mixed landscape/portrait document eats system resources 7.2.5. Ami Pro: table of contents 7.2.6. Ami Pro 2.0: divide by zero error 7.2.7. Ami Pro 3.0: equation handling problems 7.2.8. Ami Pro 3.0: overlapped screen text 7.2.9. Ami Pro 2.0: printing with incorrect fonts 7.2.10. Ami Pro 3.0: slow printing 7.2.11. Ami Pro 3.0: unable to load Word or WordPerfect files 7.2.12. Corel Draw! 3.0: can't rotate bitmaps 7.2.13. Corel Draw! 4.0: can't install from CD-ROM 7.2.14. Excel 4.0: out of memory loading a workbook 7.2.15. FrameMaker: scrambled dot-matrix output 7.2.16. KA9Q: dropped packets 7.2.17. Norton Desktop for Windows: can't format in the background 7.2.18. Norton Desktop for Windows: crashes from selecting files 7.2.19. Mathematica 2.0 for Windows: problems with Windows 3.1, other problems 7.2.20. Mathematica 2.1 for Windows: crashing problems 7.2.21. NCSA Telnet [in DOS session]: crashes in a window 7.2.22. PageMaker 4.0: font selection box won't scroll 7.2.23. PageMaker 4.0: text color changes to almost invisible 7.2.24. PageMaker 4.0: WordPerfect and Word for Windows import 7.2.25. Paradox for Windows: dialog boxes can't be killed 7.2.26. Pathway Access 1.x: terminal font 7.2.27. PC Tools 7.1: restore problems 7.2.28. Procomm Plus for Windows: Pasted text has extra CR/LFs 7.2.29. Procomm Plus for Windows: Zmodem transfer startup 7.2.30. Quattro Pro for Windows 1.0: Accessing drive D: 7.2.31. Quattro Pro for Windows 1.0: Cut and paste to other applications 7.2.32. Quattro Pro for Windows: High resource requirements 7.2.33. Quattro Pro for Windows: Numeric format alignment 7.2.34. Quattro Pro for Windows: OLE and DDE problems 7.2.35. Quattro Pro for Windows: Saving over foreign formats 7.2.36. Quicken for Windows: conflicts with communications software 7.2.37. Ventura Publisher 3.0: divide by zero errors 7.2.38. WinFax Pro 2.0 7.2.39. Word for Windows: accessing fonts 7.2.40. Word for Windows 2.0: can't install additional components 7.2.41. Word for Windows 2.0: can't print envelopes 7.2.42. Word for Windows 2.0: equation editor fonts 7.2.43. Word for Windows 2.0: equations have too much white space 7.2.44. Word for Windows 2.0: file too big to save 7.2.45. Word for Windows 2.0: headers and graphics 7.2.46. Word for Windows 2.0: mixed landscape/portrait document eats system resources 7.2.47. Word for Windows 2.0b: printing from Print Preview 7.2.48. WordPerfect for Windows: mixed landscape/portrait document eats resources 7.2.49. WordPerfect for Windows 1.0: floppy access 7.2.50. WordPerfect for Windows 1.0: button bar won't display 7.2.51. WordPerfect for Windows 1.0: crashes with 256-color display driver 7.2.52. WordPerfect for Windows 5.2: incorrect table of contents 7.2.53. WordPerfect for Windows 1.0: mixing landscape and portrait pages 7.2.54. WordPerfect for Windows 1.0: printing with TrueType 7.3. Available Windows 3.x applications 7.3.1. Mainstream productivity applications 7.3.1.1. Desktop publishing 7.3.1.2. Integrated sofware 7.3.1.3. Spreadsheets 7.3.1.4. Word processing 7.3.1.5. Word processing utilities 7.3.2. Information management 7.3.2.1. Databases, non-programmable 7.3.2.2. Databases, programmable 7.3.2.3. Form processing and management 7.3.2.4. Project management 7.3.3. Graphics and illustration 7.3.3.1. Databases, image 7.3.3.2. Charting (flow and organizational) 7.3.3.3. Drawing and illustration 7.3.3.4. Graphics conversion 7.3.3.5. Image viewers 7.3.3.6. Painting and image editing 7.3.3.7. Presentation and business graphics 7.3.3.8. Technical and Scientific Plotting 7.3.4. Personal information and finance management 7.3.4.1. Financial Management 7.3.4.2. Personal Information Managers 7.3.5. Communications and networking 7.3.5.1. Networking and groupware 7.3.5.1.1. Groupware 7.3.5.1.2. Internet news and mail readers/utilities 7.3.5.1.3. Internet access utilities 7.3.5.1.4. TCP/IP Networking 7.3.5.1.5. X Window servers 7.3.5.2. Communications and terminal emulation 7.3.5.2.1. Communications (ASCII) 7.3.5.2.2. Communications (IBM mainframe) 7.3.5.2.3. Facsimile 7.3.5.2.4. Remote Access 7.3.6. Fonts 7.3.6.1. Font packages 7.3.6.2. Font managers 7.3.6.3. Font utilities 7.3.7. Utilities and fonts 7.3.7.1. Disk and file utilities 7.3.7.1.1. Archiving utilies 7.3.7.1.2. Backup software 7.3.7.2. Program launchers and desktops 7.3.7.2.1. Program Manager type 7.3.7.2.2. File Manager type 7.3.7.2.3. Integrated desktops 7.3.7.2.4. Icon docks/tool bars 7.3.7.2.5. Commandline utilities 7.3.7.2.6. Other program launchers 7.3.7.3. Other utilities 7.3.7.3.1. Benchmarking utilities 7.3.7.3.2. Clock utilities 7.3.7.3.3. Desktop enhancers 7.3.7.3.4. Miscellaneous 7.3.7.3.5. Task schedulers 7.3.7.3.6. Task managers 7.3.8. Technical and engineering 7.3.8.1. CAD software 7.3.8.2. Engineering 7.3.8.3. Mathematical 7.3.8.4. Simulation and modeling 7.3.8.5. Statistics 7.3.9. Home, entertainment and multimedia 7.3.9.1. Multimedia 7.3.9.1.1. CD audio players 7.3.9.1.2. Multimedia authoring 7.3.9.1.3. Multimedia playback 7.3.9.1.4. Sound editors 7.3.9.1.5. Video Editors 7.3.9.2. Entertainment 7.3.9.2.1. Games and entertainment 7.3.9.3. Home 7.3.9.3.1. Cooking 7.3.9.3.2. Fitness and Sports 8. Technical Support Contacts 8.1. Microsoft 8.1.1. Telephone 8.1.2. Internet 8.1.3. Compuserve 8.1.4. Microsoft Download Service 8.2. Wolfram Research 8.2.1. Internet 8.3. WordPerfect 8.3.1. Telephone 8.3.2. Bulletin Board Service ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 1. CREDITS =========== The author may be contacted by the following means: Internet: tomh@ metrics.com UUCP: uunet!metrics.com!tomh BITNET: tomh@ metrics.com CompuServe: >INTERNET: tomh@metrics.com Mail: Tom Haapanen Software Metrics Inc. 22 King St. S., suite 303 Waterloo, Ont. N2J 1N8, Canada The Word for Windows to Windows Help conversion utility, Dr. Help, used for creating and maintaining this document, was created by Roger Hadgraft, senior lecturer in Civil Engineering at Monash University, Clayton, Victoria, Australia. It can be used for converting most Word files into WinHelp files. Roger may be contacted as: Internet: roger.hadgraft@eng.monash.edu.au UUCP: uunet!eng.monash.edu.au!roger.hadgraft CompuServe: >INTERNET: roger.hadgraft@eng.monash.edu.au I would also like to express my gratitude to the countless people who have contributed information to the Windows FAQs, through Usenet news, email and personal conversations. You know who you are: I'm grateful for your help, as this FAQ would not be what it is without your help. Latest versions of this FAQ are available by anonymous ftp on ftp.metrics.com (198.133.164.1) in the directory ~/faq. ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 2. MICROSOFT WINDOWS ===================== --------------------------------------------------------------------------- 2.1. Windows 1.0 ================= Microsoft first began development of the Interface Manager (subsequently renamed Microsoft Windows) in September 1981. Although the first prototypes used Multiplan and Word-like menus at the bottom of the screen, the interface was changed in 1982 to use pull-down menus and dialogs, as used on the Xerox Star. Microsoft finally announced Windows in November 1983, with pressure from just-released VisiOn and impending TopView. This was after the release of the Apple Lisa (but prior to the Macintosh), and before Digital Research announced GEM, another competing graphical environment. Windows promised an easy-to-use graphical interface, device-independent graphics and multitasking support. The development was delayed several times, however, and the first version hit the store shelves (after 55 programmer-years of development!) in November 1985. The selection of applications was sparse, however, and Windows sales were modest, The following were the major features of Windows 1.0: * Graphical user interface with drop-down menus, tiled windows and mouse support * Device-independent screen and printer graphics * Co-operative multitasking of Windows applications --------------------------------------------------------------------------- 2.2. Windows 2.0 ================= Windows 2.0, introduced in the fall of 1987, provided significant useability improvements to Windows. With the addition of icons and overlapping windows, Windows became a viable environment for development of major applications (such as Excel, Word for Windows, Corel Draw!, Ami, Page Maker and Micrografx Designer), and the sales were spurred by the runtime ("Single Application Environment") versions supplied by the independent software vendors. When Windows/386 (see next section) was released, Microsoft renamed Windows to Windows/286 for consistency. The following are the major changes from earlier versions of Windows: * Overlapping windows * PIF files for DOS applications --------------------------------------------------------------------------- 2.3. Windows/386 ================= In late 1987 Microsoft released Windows/386. While it was functionally equivalent to its sibling, Windows/286, in running Windows applications, it provided the capability to run multiple DOS applications simultaneously in the extended memory. The following are the major changes from earlier versions of Windows: * Multiple DOS virtual machines with pre-emptive multitasking --------------------------------------------------------------------------- 2.4. Windows 3.0 ================= Microsoft Windows 3.0, released in May, 1990, was a complete overhaul of the Windows environment. With the capability to address memory beyond 640K and a much more powerful user interface, independent software vendors started developing Windows applications with vigor. The powerful new applications helped Microsoft sell more than 10 million copies of Windows, making it the best-selling graphical user interface in the history of computing. The following are the major changes from earlier versions of Windows: * Standard (286) mode, with large memory support * 386 Enhanced mode, with large memory and multiple pre-emptive DOS session support * No runtime versions available * Program Manager and File Manager added * Network support * Support for more than 16 colors * API support for combo boxes, hierarchical menus and private .ini files --------------------------------------------------------------------------- 2.5. Windows 3.1 ================= Microsoft Windows 3.1, released in April, 1992 provides significant improvements to Windows 3.0. In its first two months on the market, it sold over 3 million copies, including upgrades from Windows 3.0. It is currently continuing to sell at a rate of over 1 million copies per month. The following are the major changes from Windows 3.0: * No Real (8086) mode support * TrueType scalable font support * Multimedia capability * Object Linking and Embedding (OLE) * Application reboot capability * "Mouse Trails" for easier mouse use with LCD display devices * Better inter-application protection and better error diagnostics * API multimedia and networking support * Source-level API compatability with Windows NT --------------------------------------------------------------------------- 2.6. Windows 3.11 ================== Windows 3.11, available now, adds no new features but corrects some existing, mostly network-related problems. It is replacing Windows 3.1 at the retail and OEM levels, and the upgrade is available free from ftp.microsoft.com. --------------------------------------------------------------------------- 2.7. Windows for Workgroups 3.1 ================================ The Windows for Workgroups package, released in November, 1992, is the first integrated Windows and networking package offered by Microsoft. It provides peer-to-peer file and printer sharing capabilities (on a level comparable to LANtastic or Netware Lite) highly integrated into the Windows environment. The simple-to-use-and-install networking allows the user to specify which files on the user's machine should be made accessible to others. The files can then be accessed from other machines running either Windows or DOS. Windows for Workgroups also includes two additional applications: Microsoft Mail, a network mail package, and Schedule+, a workgroup scheduler. --------------------------------------------------------------------------- 2.8. Windows for Workgroups 3.11 ================================= Windows for Workgroups 3.11, available now, adds 32-bit file access, fax capabilites and higher performance to Windows for Workgroups 3.1. --------------------------------------------------------------------------- 2.9. Windows NT 3.1 ==================== Microsoft Windows NT is Microsoft's platform of choice for high-end systems. It is intended for use in network servers, workstations and software development machines; it will not replace Windows for DOS. While Windows NT's user interface is very similar to that of Windows 3.1, it is based on an entirely new operating system kernel. The following are the major changes from Windows 3.1: * Based on a new microkernel design * Portable architecture for Intel x86/Pentium, MIPS R4000/R4400 and DEC Alpha processors. Support for PowerPC and SPARC architectures is under development. * 32-bit addressing for access to up to 4 GB of memory * Fully protected applications with virtualized hardware access * Installable APIs for Win32, Win16, MS-DOS, POSIX and OS/2 * Installable file systems, including FAT, HPFS and NTFS * Built-in networking (LAN Manager and TCP/IP) with remote procedure calls (RPCs) * Symmetric multiprocessor support * Security designed in from start, to be initially C2 certified, with a B- level kernel design * API support for asynchronous message queues, advanced interprocess communication, registration databases, Bezier curves and graphics transformations. The following is the minimum platform for use with the client edition of Windows NT: * 33 MHz 386 processor * 12 MB memory * 100 MB hard disk * VGA graphics The Advanced Server Edition requires 16 MB of memory. Win32 in itself is not a version of Windows, but the name of application programming interface for Windows NT and "Chicago". --------------------------------------------------------------------------- 2.10. Win32s for Windows 3.1 ============================= Win32s is a set of libraries for Windows 3.1, which enable users to run most Windows NT 32-bit applications on Windows 3.1, without the extensive hardware requirements of Windows NT. The Win32s interface has effectively replaced the older Windows-32 programming interface used by 32-bit Windows applications such as previous versions of Mathematica. --------------------------------------------------------------------------- 2.11. Windows 4.0 ("Chicago" and Win32c) ========================================= This unannounced product is rumored to be released in late 1994. It will be a 32-bit system providing full pre-emptive multitasking, advanced filesystems, threading, networking and more. It will include MS-DOS 7.0, but will take over from DOS completely after starting. It will not include Windows NT's security, multiprocessor support, server capabilities or multiple API modules. It will include a completely revised user interface, along the lines of "Cairo", but not taken as far as that product. See the section entitled Chicago Q&A for more information about Chicago. --------------------------------------------------------------------------- 2.12. Windows NT 3.5 ("Daytona") ================================= "Daytona" is Microsoft's codename for an upcoming release of Windows NT, which will provide OLE 2.0, improved performance and reduced memory requirements. Availability is expected in mid-1994 --------------------------------------------------------------------------- 2.13. Windows NT 4.0 ("Cairo") =============================== "Cairo" is Microsoft's project for object-oriented Windows, and a successor to the "Daytona" release of Windows NT. Firm details are not available, but most rumors place expected availability sometime in 1995. Developers are encouraged to work with OLE 2.0 in order to start moving in the correct direction towards future "Cairo" compatability. --------------------------------------------------------------------------- 2.14. Windows for Pen Computing 3.1 ==================================== Microsoft developed Windows for Pen Computing for use on pen-based systems. In most aspects, it is basically equivalent to Windows 3.1 with extensions for pen support. These extensions include the use of a pen as a pointing device as well as handwriting recognition and conversion. Pen Windows first shipped in April, 1992. --------------------------------------------------------------------------- 2.15. Multimedia Windows ========================= The term Multimedia Windows describes a package with Windows 3.0 and the Multimedia Extensions. These extensions are included in Windows 3.1, and thus Multimedia Windows is no longer sold as a separate product. --------------------------------------------------------------------------- 2.16. Modular Windows ====================== Modular Windows is the operating system for Tandy Corp.'s Video Information System (VIS) multimedia player. It is essentially similar to Windows' core, but without any desktop accessories, TrueType fonts or a number of other features. --------------------------------------------------------------------------- 2.17. Win-OS/2 =============== Win-OS/2 is the Windows component of IBM's OS/2 2.0. It is based partially on Windows 3.0 and partially on 3.1. While it runs a majority of the commercial Windows applications, it is not covered by this document. --------------------------------------------------------------------------- 2.18. Chicago Q&A ================== The following questions and answers are from a document distributed by Microsoft in December, 1993. Microsoft is continually enhancing its Windows operating system product line to deliver easy to use yet powerful products that exploit the latest advances in microcomputer hardware technology. There is a great deal of interest in and speculation about the "Chicago" project, the technology development effort which will deliver the next major release of Windows for the mainstream desktop and portable PC. The purpose of this document is to answer the most common questions that customers have voiced about Chicago. ........................................................................... 2.18.1. What is Chicago? -------------------------- What is Chicago and how does it compare to the Microsoft* Windows* 3.1, Windows* for Workgroups and Windows NT* operating systems? Microsoft has a family of operating system products designed to fully utilize the range of PC hardware available in the market today, while providing a consistent user interface for end users and a programming environment for developers. Windows 3.x and Windows for Workgroups 3.x on MS-DOS* are designed for mainstream portable and desktop PC platforms. Windows NT is designed for the high-end business and technical workstation platforms and Windows NT Advanced Server is designed as a server platform. Chicago is the code name for a development project that will produce the successor to Windows 3.x and Windows for Workgroups 3.x. The Chicago project encompasses a variety of important new technologies that will make personal computers running Windows easy to use, and that will provide a more powerful multitasking system and a great platform for communications. Decisions about how those technologies will be packaged will be made later in the development cycle and will be based on customer and business needs. ........................................................................... 2.18.2. What is Cairo? ------------------------ What is Cairo? How does Chicago compare to Cairo? Cairo is the code name for a development project that will produce the successor to Windows NT. Chicago and Cairo will produce complementary products that will continue to provide a consistent user interface and programming environment across the entire range of PC hardware platforms. ........................................................................... 2.18.3. Why does Microsoft have multiple Windows products? ------------------------------------------------------------ Why does Microsoft have multiple Windows operating system products? Wouldn't it be simpler to just have one product? Does that mean ISVs have to decide between different operating system products when writing applications? There are two distinct design points for operating systems platforms. One is centered on the mainstream system, and the other is centered on the high-end system. It is not possible to have one operating system implementation that fully exploits the broad range of hardware available today. At the low end (currently represented by products such as the HP Omnibook and entry-level desktop machines), the primary design goal is to keep the operating system small and fast and to keep usage of machine resources to a minimum. At the high end (for example, a dual-processor technical workstation), the product would need to fully support multiprocessing and advanced 3-D graphics as well as be capable of running technical applications that use maximum machine and system resources. Over time, low-end machines will become more powerful, and over time, some of today's high-end features will migrate to the low end. In addition, some technical innovations will appear on the mainstream Windows system first, largely because of the timing of product releases, and because some features are focused on end users and ease of use. The Win32 API assures developers that, whichever system they target today, their applications will be able to run in the future as the platform evolves. Thus, while Chicago and Cairo may leapfrog one another with some features, depending on release cycles -- e.g., Chicago will sport the next major advance in the user interface, with Cairo inheriting it in its release a few months later -- the general principle over time is that the high-end product will be a superset of the functionality offered in the mainstream product. Any deviations from this principle are temporary, due to variations in the product release schedules. For ISVs and for development purposes, however, Microsoft has just one Windows platform, defined by the Windows-based 32-bit API, Win32. By following a few simple guidelines, ISVs can write a single application (executable) that runs on the Windows operating system product family. If they wish, ISVs can target specific operating system products because the functionality they provide is important to their particular application, but that is not a requirement. This situation is very much like the Intel microprocessor product line. At any point in time, the Intel product line offers multiple products targeted toward different PC products, ranging from the 80386SL for low- end portable products to the Pentium microprocessor for high-end workstations and application servers. What defines those products is the Intel instruction set, which enables applications to run on all Intel chips, even though the underlying implementation at the transistor level may be very different across the Intel product line. There are also some instructions offered on the Pentium chip that are not on the 80386SL, but ISVs would have to go out of their way to make their products run on only Pentium. And over time, Pentium will become more mainstream, just as the 80486 has become the mainstream microprocessor today, and technologies developed at the low end, such as System Management Mode, will be implemented on the high end as well. ........................................................................... 2.18.4. When will Chicago and Cairo ship? ------------------------------------------- When will Chicago ship? When will Cairo ship? Chicago is scheduled to ship in the second half of 1994. Cairo is scheduled to be released in the first half of 1995. ........................................................................... 2.18.5. What is Daytona? -------------------------- What is Daytona? When will it ship? Daytona is an interim release of Windows NT that is scheduled to ship this spring. ........................................................................... 2.18.6. How will Chicago make the projected ship date? -------------------------------------------------------- Major new releases of operating system products have in the past been significantly delayed. How will you make your projected shipment date for Chicago? Chicago will be released when customers tell us it is ready. The way to make shipment dates is to hit your intermediate milestones. To date, Chicago has been making its milestones with the release of the first Preliminary Developer's Kit (PDK) in August and the second PDK in December. Feedback from beta releases beginning in March will tell us more precisely when in the second half of 1994 Chicago will ship. ........................................................................... 2.18.7. What if Chicago ships before Cairo? --------------------------------------------- If Chicago ships before Cairo, how will users of Windows NT obtain the new functionality in Chicago? Any new functionality offered in Chicago will be made available to customers of Windows NT through the release of the Cairo product. ........................................................................... 2.18.8. What are Chicago's key benefits? ------------------------------------------ What are the key benefits and features of Chicago? What features will Chicago not have? For customers, Chicago will present a major step forward in functionality on mainstream desktop platforms by providing a system that is easy to use, offers responsive multitasking performance, and provides a great platform for communications. Ease of use will be delivered through the Plug and Play architecture and an improved, intuitive user interface. Chicago will be a complete, integrated protect-mode operating system that does not require or use a separate version of MS- DOS, implements the Win32* API, and provides pre-emptive multitasking and multiple threads of execution for 32-bit applications. The communications capabilities of Windows will be enhanced with integrated, high-performance networking, built-in messaging, and features such as Remote Network Access and File Synchronization designed for mobile and remote computer users. Chicago will also be a hassle-free upgrade for the current installed base of Windows-based users. Chicago will be compatible with most current applications and drivers for MS-DOS and Windows, and will provide an easy transition to the new user interface features. The applications performance of Chicago will meet or exceed the performance of Windows 3.1 on 80386 systems with 4MB of RAM running the same applications. For systems with more memory, performance will be significantly improved over Windows 3.1. The setup program will enable customers to uninstall Chicago, assuring customers a way to remove it if they are in any way unhappy with it, and will provide tools for system administrators to customize the configuration of Chicago. Chicago will not be processor independent, nor will it support symmetric multiprocessing systems, provide C2-level security, or provide full Unicode support. These features cannot be delivered on the mainstream platform in the near future while still meeting the performance and resource targets necessary to create a compelling upgrade for the huge installed base of users of the Windows operating system. If these features are important to a customer, Windows NT is the product to deploy. ........................................................................... 2.18.9. What different Chicago packages will be available? ------------------------------------------------------------ What different packages will you have for Chicago? Decisions about packaging the different technologies being developed as part of the Chicago project will be made later in the development cycle and will be based on customer and business needs. One option is to provide a base Chicago package with some add-on packages that deliver functionality required by specific market segments. This is much like the situation today in which the user of Windows 3.1 can upgrade to Windows for Workgroups by acquiring the add-on package that adds the 32-bit file system and 32-bit networking enhancements to Windows. ........................................................................... 2.18.10. What will Chicago be called? --------------------------------------- Since the term Chicago is a code name, what will you call the product(s) that you will eventually release? Decisions about names will be made after we decide on a packaging plan. ........................................................................... 2.18.11. What will happen to MS-DOS? -------------------------------------- What will happen to the MS-DOS product line? Microsoft will continue to enhance MS-DOS as long as customers require it. Future versions will be derived from the protected-mode technology developed in the Chicago project. Current MS-DOS-based applications and drivers will continue to be compatible with new versions of MS-DOS. ........................................................................... 2.18.12. How will Chicago perform on 4 MB? -------------------------------------------- Your performance goals on 4MB platforms sound very ambitious, considering all the functionality you're adding to Chicago. How will you achieve those goals? Chicago will implement new working set management technologies that will optimize the use of memory on low-configuration systems. The networking, disk and paging caches will be fully integrated. Protect-mode device drivers will be dynamically loadable, to ensure that only the drivers that are immediately needed are consuming memory. More components of the base operating system will be pageable. Great attention will be paid to effective page tuning, including hand-tuning source code. ........................................................................... 2.18.13. Will Chicago run current applications? ------------------------------------------------- Will Chicago run my current Windows-based applications? How about MS- DOS-based applications? Chicago will run most of the current applications for Windows and MS-DOS, as well as new applications written to the Win32 API. Some classes of applications will need to be revised to be compatible with Chicago, such as shell-replacement utilities and file-management utilities. Chicago's new shell provides a complete set of services that is tightly integrated with the operating system components. Shell programs will need to do more than simply replace components such as Program Manager or File Manager. And file-management utility vendors will want to revise their applications to take advantage of the Long File Name feature that Chicago offers. Microsoft is working closely with shell-replacement and file- utility vendors to enable them to revise their products to add value to and be compatible with Chicago. ........................................................................... 2.18.14. Will I need to get new device drivers? ------------------------------------------------- Will I have to get new device drivers to use my current devices with Chicago? Chicago supports current real-mode device drivers as well as new 32-bit protected mode device drivers. As a result, customers will be able to use their current devices either with their current device drivers, or with new device drivers made available with Chicago. Performance and functionality can be improved if the user installs the new Chicago drivers. Microsoft is making it easier for device manufacturers to deliver new drivers for common devices by defining a more layered, modular device driver architecture. For displays, printers and modems, Microsoft will deliver universal drivers. These drivers will implement common device functionality and expose an interface for device manufacturers to create "minidrivers" that implement the features specific to their devices. This approach was very successful with printers for Windows 3.1, resulting in rapid availability of fast, high-quality drivers for a wide range of printers. ........................................................................... 2.18.15. Will my current applications work well on Chicago? ------------------------------------------------------------- Will my current applications perform as well on Chicago as they do on Windows 3.1 today? For Chicago to be a compelling upgrade, Windows-based users must experience a level of performance after installing Chicago that meets or exceeds the performance they currently experience running an identical set of tasks on Windows 3.1. Because a large portion of the installed base of users of Windows today have 4MB systems, Chicago must meet its performance goals on 4MB systems. On systems with more than 4MB of RAM, Chicago will offer significantly improved performance. Understand, however, that there are user and application scenarios today that already use more than 4MB. Users who already require more than 4MB will continue to require more than 4MB with Chicago -- and if they are using more than 4MB, they should see improved performance. But they won't get away with using less memory in the future than they do today. It's an important distinction to maintain. ........................................................................... 2.18.16. When will Chicago's new UI be ready? ----------------------------------------------- You say Chicago will have a different user interface than Windows and Windows NT. When will that user interface be reflected in the beta versions of Chicago? The new user interface will be delivered with the first beta of Chicago, scheduled for March 1994. ........................................................................... 2.18.17. Will the new user interface mean a lot of retraining? ---------------------------------------------------------------- Won't a new user interface mean a lot of retraining for current Windows- based users? Will the advantages of the new user interface be worth the retraining costs? The user interface being developed for Chicago will offer dramatic gains in ease of learning and ease of use for the broad range of people using PCs today. Instead of mastering different kinds of tools to work with different resources on their computers, users of Chicago will be able to browse for and access all resources in a consistent fashion with a single tool. This will be much easier than learning separate applications such as Program Manager, File Manager, Print Manager, Control Panel, etc. as users of Windows must do today. A system toolbar that is always accessible will make it much easier to start and switch between full-screen tasks. The implementation of OLE 2.0, with its focus on the user's document rather than on the tool used to create it, and the direct manipulation of data through drag and drop in the user interface, will make working with documents easier and more intuitive. Current users of Windows will be immediately productive with Chicago and be able to learn the new features of the user interface as they work. Chicago's smart setup technology will use the current system settings to present an initial configuration that is familiar for the current Windows- based user. And for corporate customers and individuals who may not want to make any user interface changes initially, Chicago will enable them to continue running their current Program Manager and File Manager configurations. ........................................................................... 2.18.18. What is Plug and Play? --------------------------------- What is Plug and Play? What benefits does Plug and Play provide? Plug and Play is a technology jointly developed by PC product vendors that will dramatically improve the integration of PC hardware and software. It allows a PC to adapt itself dynamically to its environment; devices can be plugged into or unplugged from a machine, without the user having to do anything special -- the machine just works. Plug and Play is a general framework that advances that state of the PC architecture by defining how the software communicates with any device connected to the PC. Plug and Play technology enables installation and configuration of add-on devices without user intervention. Plug and Play will make it possible for a consumer to turn a standard desktop system into a great multimedia machine by just "plugging" in a Plug and Play sound card and CD-ROM, turning on the system, and "playing" a video clip. Plug and Play can enable new system designs that can be dynamically reconfigured. For example, imagine a docking station that enables you to remove the portable system while it is still running so that you can take it to a meeting, and the system automatically reconfigures to work with a lower-resolution display and adjusts for the absence of the network card and large disk drive. Or imagine an IR-enabled subnotebook that automatically recognizes, installs and configures an IR-enabled printer when you walk into the room, so your applications are ready to print to that printer. Plug and Play can also save development and support costs for the product manufacturer. Today, as many as 50 percent of support calls received by operating system and device manufacturers are related to installation and configuration of devices. With Plug and Play, device driver development is simplified because device manufacturers can write one driver that works across multiple bus types using the Universal Driver Model specified by the Plug and Play architecture. Today, device manufacturers have to include bus- specific code in each of their drivers. With Plug and Play, specific bus configuration data is contained in "bus drivers." Also, operating system preinstallation and configuration are simplified for OEMs because Plug and Play devices will automatically install and configure during setup. ........................................................................... 2.18.19. What hardware changes does Plug and Play require? ------------------------------------------------------------ What changes to current hardware and software are required to make Plug and Play a reality? How will vendors figure out how to develop new devices with Plug and Play capability? First, Plug and Play is compatible with existing systems, so nothing "breaks" because of Plug and Play. Plug and Play devices can be brought out over time -- in fact, this is already occurring -- and will work with existing systems. To deliver all of the above benefits requires changes to devices and drivers, the BIOS, and the operating system. Three fundamental capabilities are required for a system to provide Plug and Play functionality: * A unique identifier for every device on the system * A procedure for the BIOS and operating system to install and configure that device * A mechanism for the system and applications to recognize that a configuration change has occurred while the system is running All the changes to devices and drivers, the BIOS and the operating system are defined by a series of specifications for Plug and Play architecture. The Plug and Play architecture is an open, flexible and cost-effective framework for designing Plug and Play products. The Plug and Play architecture was jointly developed by a working group of leading vendors, who reviewed design proposals with hundreds of companies in the industry at conferences and through online forums. Plug and Play can be implemented by any operating system vendor and any hardware manufacturer. In addition to Microsoft, IBM has announced support for Plug and Play in OS/2. The Plug and Play architecture is flexible, because it provides a framework that works on multiple types of bus architectures (ISA, SCSI, PCMCIA, VL, PCI, etc.), and it is extensible to future bus designs. The Plug and Play architecture is also cost-effective, because it requires little or no incremental cost for vendors to implement in their products. ........................................................................... 2.18.20. Won't it take a long time for Plug and Play? ------------------------------------------------------ Won't it take a long time for these changes to be reflected in products? Acceptance of the Plug and Play architecture is widespread, as seen by the rapid progress the industry is making in delivering Plug and Play specifications and products. Specifications have already been released for ISA, SCSI and PCMCIA devices, and the Plug and Play BIOS. Additional specifications are in process, including PCI, ECP, VL, EISA, Micro Channel, and Access. The first Plug and Play devices were demonstrated at COMDEX/Fall 1993, representing a wide range of companies and products. Intel has released development kits that enable device and system vendors to deliver improved configuration capabilities for ISA and PCI systems running with Windows 3.1 in a manner that will provide compatibility with future Windows operating systems. Fully Plug and Play-capable systems (including all Plug and Play devices and a Plug and Play BIOS) will be available in the first half of 1994. These systems will be able to offer complete Plug and Play functionality when combined with Chicago. ........................................................................... 2.18.21. Is the Chicago API different from the Windows NT API? --------------------------------------------------------------- I've heard that Chicago implements a 32-bit API. Is that API different from the 32-bit API implemented on Windows NT? There is only one 32-bit Windows API, called Win32, with ISVs able to use the API set to provide different levels of functionality for Windows 3.1, Chicago and Windows NT. Chicago implements a large subset of the functionality of the Win32 API offered on Windows NT, and extends the Win32 API in some areas. These extensions will be delivered on Windows NT as soon as possible after the release of Chicago. ........................................................................... 2.18.22. Will vendors need separate Chicago and NT versions? ------------------------------------------------------------- If there are different implementations of the Win32 API available on different products in the Microsoft operating system product line, does that mean ISVs will have to have separate versions of their applications for Windows and Windows NT? No. By following some simple guidelines, ISVs can develop a single executable file that runs on Windows 3.x, Chicago and Windows NT. At the recent Professional Developers' Conference, we provided in-depth technical sessions on the proper way to design applications to do so, supplied tools in the SDK to help make such development easier, and showed several applications that ran across the entire Windows family. ........................................................................... 2.18.23. When will Chicago applications be available? ------------------------------------------------------ When will applications be available that exploit Chicago? Won't that take a long time? ISVs who are developing 32-bit applications for Windows 3.1 and Windows NT using the Win32 API and the guidelines we have provided will have applications that are able to run on Chicago immediately. There are already more than 250 Win32 applications available today, and more coming quickly. Other ISVs will wait until Chicago ships to provide their 32-bit applications; usually those applications start coming on-line about 90 days after the operating system ships. Chicago also will support today's 16- bit applications, so users can move to Chicago immediately and upgrade their applications as they become available. Chicago represents a major market opportunity for ISVs. Chicago will ship on almost all OEM systems soon after it is released, and it will be acquired as an upgrade by a substantial portion of the Windows installed base (the installed base will probably number more than 50 million by mid-1995). Customers who purchase new systems and upgrade their operating systems are the most active purchasers of new software applications. As a result, ISVs have a very significant business incentive to release versions of their applications that exploit Chicago. ........................................................................... 2.18.24. Is Chicago completely 32-bit? --------------------------------------- I've heard Chicago described as a 32-bit operating system, yet I've also heard that portions of Chicago are implemented with 16-bit code. Are both these statements correct? Chicago will provide a 32-bit platform for applications by implementing the Win32 API on a complete, protect-mode operating system. Chicago will also run well on mainstream Windows platforms (which for a large portion of the Windows installed base is a 4MB 80386 system), and Chicago will be compatible with applications and drivers for MS-DOS and Windows. These requirements must be met if Chicago is to meet customer needs and provide the volume to make ISVs successful. These requirements have driven all the design decisions for Chicago. The resulting design deploys 32-bit code wherever it improves performance without sacrificing application compatibility. The design retains existing 16-bit code where it is required to maintain compatibility or where size is a critical issue but has minimal impact on performance. All of the I/O subsystems and device drivers in Chicago, such as networking and file systems, are fully 32-bit as are all the memory management and scheduling components (the kernel and virtual memory manager). Many functions provided by the Graphics Device Interface (GDI) have been moved to 32-bit code, including the spooler and printing subsystem, the rasterizer, and the drawing operations performed by the graphics "DIBengine." Much of the window management code (user) remains 16-bit to retain application compatibility. ........................................................................... 2.18.25. How do the 16-bit components fit in? ---------------------------------------------- If portions of Chicago still remain 16-bit, what happens when a 32-bit application makes a function call that is implemented by the 16-bit Chicago component? Doesn't this slow down 32-bit applications on Chicago relative to 16-bit applications? When Win32-based applications call a 32-bit API that is implemented by a 16- bit component of the system, the function call is translated to its 16-bit equivalent for processing by the system. This translation process is referred to as "thunking." Although there is some overhead associated with a thunking operation, the Chicago thunk layer is very efficient. That overhead will be more than offset by the improved efficiency of the linear memory addressing scheme used by Win32-based applications. The overall impact of some "thunking" code is quite modest vs. all the other work the application and operating system have to do. For end users, perceptions of application performance are based on a combination of the efficiency of the application when executing its own code and the efficiency of the operating system code when the application has called an operating system service. On Chicago systems with adequate memory, end users will experience gains in system efficiency when running 16-bit applications, and they will experience gains in both system and application efficiency when running 32-bit applications. ........................................................................... 2.18.26. Will existing networking software work with Chicago? -------------------------------------------------------------- Will I need new networking software to connect Chicago to my network server? Customers will require Chicago to connect to their network servers when Chicago is installed, and to offer high-performance, reliable networking functionality. To meet this requirement, Chicago will continue to run existing real-mode networking components. However, we expect customers to want to upgrade to the new 32-bit networking components provided by Chicago. Chicago will enhance the open, flexible, high- performance 32-bit networking architecture offered today with Windows for Workgroups 3.11 that enables customers to mix and match networking components. Chicago will support NDIS 2.0, NDIS 3.0 and ODI drivers, and will provide 32-bit NetBEUI, IPX/SPX and TCP/IP protocols. Redirectors for SMB and NCP-based networks will be included. In addition, Chicago's new multiple-provider interface will make it possible for the user to view, browse and connect to multiple networks in a consistent fashion. ........................................................................... 2.18.27. What about Netware with Chicago? ------------------------------------------ What about NetWare? Are you working with Novell on NetWare support? Customers will require high-performance, reliable NetWare support the day Chicago is released. To meet that requirement, Microsoft is developing a 32-bit NCP Redirector that is seamlessly integrated with the Chicago user interface, and is encouraging Novell to do the same. Microsoft will offer Novell access to information and assistance to write a Chicago redirector. Novell engineers attended the Win32 Professional Developers' Conference and have been provided access to the Preliminary Developer's Kit for Chicago. With this approach, customers should be able to choose from multiple sources for reliable, high-performance NetWare connectivity software when Chicago is released. ........................................................................... 2.18.28. Will vendors there be Chicago "server" version? --------------------------------------------------------- Will there be a Chicago server? No, not in the sense of a "server product" such as Windows NT Advanced Server. Chicago will continue to improve upon the peer server capabilities offered in Windows for Workgroups by offering additional features for remote installation, control and administration. These features will make Chicago an even better product for an easy-to-use file and print-sharing LAN that is ideally suited as a small-business, small- department or remote office network. Similarly, Windows NT offers peer services as well for the high-end desktop. But for most server applications, and in the sense that most people ask about a "server product," Windows NT Advanced Server is the Microsoft server product. ........................................................................... 2.18.29. What about Chicago's portability? ------------------------------------------- I keep hearing rumors that you are working on a portable version of Chicago. Is this true? No, we are not working on a portable version of Chicago. Windows NT is our portable operating system, and it's already available on high-end Intel, MIPS, Alpha and Clipper machines; it will be available on the PowerPC by mid-1994 and on other high-end platforms over time. There is no reason to make Chicago portable. Chicago is optimized for Intel processors, and much of its internal code is Intel assembler, which puts Chicago at the heart of today's low-end and mainstream line. Portability is important for the new generation of high-powered Intel and RISC machines, on which Windows NT runs and for which Windows NT has been optimized. As these new high-end machines become more mainstream, which will happen over time, Windows NT will already offer the power, security, and reliability that users will demand to exploit these new machines. ........................................................................... 2.18.30. What about systems management? ---------------------------------------- What will Chicago do to make the client operating system more manageable? A primary goal for the Chicago project is to make Windows less expensive to deploy in a corporation. Chicago will include some specific features and enabling technologies that will make it easier for system administrators to install, configure, monitor, maintain and troubleshoot their Windows- based desktops. Chicago can be set up from a network server and at the desktop can be configured at the desktop to run locally or across the network. In each case, the administrator can establish a specific configuration for the installation, selecting from a flexible array of setup configuration options. Chicago desktops require only a floppy drive to start up, and paging of components to a swapfile on the network can be disabled to minimize network traffic. Once Chicago is installed, administrators will be able to centrally configure desktop settings such as file and printer sharing, network access, and passwords. They can remotely monitor Chicago desktops with peer services running to determine what resources are shared, what connections have been made, and what files are being used. Chicago enhances the security provided by Windows for Workgroups to include user- level security. To enable users to access their personal groups, applications, and data from any system on the network, Chicago will provide user profiles. Chicago will also provide the infrastructure for the delivery of enhanced desktop management services by third parties. A backup agent will be included with Chicago to enable administrators to back up desktop data to a network server. To integrate the desktop into SNMP-based enterprise management systems, Chicago will also include a Systems Network Management Protocol (SNMP) agent and a Management Information Base (MIB) for a number of system resources. The system registry and Plug and Play architecture provide a rich store of data about the software and hardware configuration on the desktop, and this information can be accessed by system management software using a DCE- compliant Remote Procedure Call (RPC) mechanism. ........................................................................... 2.18.31. Will there be mobility features? ------------------------------------------ What improvements will Chicago offer for people who use a mobile or remote computer? Chicago will provide great support for mobile form-factor devices and will make it easy for end users to access the resources of their desktop systems when they are away from their offices. The implementation of Plug and Play in Chicago will support insertion and removal of devices such as PCMCIA cards while the operating system is running. It will also support automatic reconfiguration of dockable computers when they are inserted or removed from the docking station, without rebooting the system. An enhanced version of Advanced Power Management will further extend battery life. The services provided by Windows for Pen Computing will be enhanced and incorporated into Chicago, including basic inking and rendering support. A special focus will be on remote connectivity. Any Chicago- based machine will be able to serve as a Remote Access dial-up server or a remote client for Windows NT Advanced Server, Novell NetWare servers or Chicago peer servers. The same technology will be used for serial cable and infrared connections between PCs. The Remote Access architecture will be integrated with the Chicago networking architecture by using the same network protocols and advanced security features. Remote Access will support wireless devices and allow application developers to make their applications "slow-link aware" to improve the user experience when working on a remote system via modem rather than on a high-bandwidth network. Furthermore, Chicago will provide a simple form of file synchronization and APIs for applications to access the file synchronization services to merge changes when both the source document and copy have been modified. Remote e-mail and Microsoft at Work fax capability will be included, as in Windows for Workgroups 3.11 today. ........................................................................... 2.18.32. How will file synchronization work? --------------------------------------------- Will the file synchronization feature in Chicago provide document management capabilities? Chicago's file synchronization services are optimized for the needs of the mobile computer user who wants to take copies of documents to a remote location and have them be automatically synchronized with the source documents. It is not intended as a replacement for sophisticated document management systems. Chicago's file synchronization allows customers to identify files that they want to stay up to date, to change those files, and to have the files automatically updated when the source file is available to the system. The update is performed by replacing the source file with the modified copy at the discretion of the user. If an application writes a "merge- handler," then specific data within the modified and source copies of a file can be merged, to create a new updated copy. ........................................................................... 2.18.33. Will there be separate NT and Chicago SDKs? ----------------------------------------------------- You say you have one API with Win32. Does that mean there will also be just one Windows SDK? Yes, there will be one Win32 SDK that developers can use to develop 32-bit applications for Windows 3.1, Chicago and Windows NT. In fact, we recently announced a new subscription service, the Microsoft Developer Network Level II that provides developers with not only the Win32 toolkit, but every system toolkit we offer, on a single CD, updated quarterly. ........................................................................... 2.18.34. What benefits are there to developers? ------------------------------------------------ What benefits does Chicago offer to developers? What are you doing to make developing Windows-based applications easier? The Microsoft Visual Basic programming system has dramatically streamlined and simplified the development of Windows-based applications, and it will be enhanced to support the development of 32-bit applications for Chicago. Microsoft also is enhancing its Visual C++ * development system and Microsoft Foundation Class tools. ........................................................................... 2.18.35. Will Visual Basic for Applications be included? --------------------------------------------------------- Will Chicago include Visual Basic for Applications? Visual Basic for Applications will be offered as a separate product. ........................................................................... 2.18.36. Will Chicago and NT use common device drivers? -------------------------------------------------------- Will Chicago and Windows NT share the same device drivers? Generally not, since Chicago and Windows NT have different device driver models. However, since both products support a modular, layered device driver architecture, there are areas of substantial synergy. For example, SCSI miniport adapters for Windows NT will be binary- compatible with Chicago, as will printer drivers and NDIS drivers for Windows NT. ........................................................................... 2.18.37. Will WOSA services be included? ----------------------------------------- Will WOSA services be included with Chicago? WOSA is a general, open framework for implementing multiple back-end services in Windows while providing a single front-end interface for end users. Services in Chicago such as messaging and remote network access are designed according to the WOSA framework. Whether or not support for additional WOSA services, such as ODBC support, will be shipped with Chicago is a packaging decision that will be made later in the development cycle and will be based on customer and business needs. All the WOSA- related toolkits are available today to developers through the Microsoft Developer Network Level II subscription service. ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 3. INTERNET AND USENET ======================= --------------------------------------------------------------------------- 3.1. Usenet ============ If you received this FAQ from somewhere other than Usenet or Internet, you may not be familiar with Usenet. Basically, Usenet is a loose collection of over 1,000,000 computers which exchange mail and news. The network is unstructured and highly distributed; most communication is either by TCP/IP over high-speed connections (or over dual-up links using public telephone lines), or UUCP over public telephone lines. Internet is the worldwide collection of computers linked using the TCP/IP protocol, consisting of somewhere between 5,000,000 and 10,000,000 computers, usually connected by high-speed TCP/IP network connections. Usenet news is a software system where a person can post an article to a selected newsgroup, and have every other news reader be able to read it. There are over 3,000 newsgroups (including the alt groups), and daily volume of news now exceeds 50 MB. While most Usenet systems are Unix-based, it is not a requirement, and there are a number of Usenet software packages available for Windows as well. If you have an Internet or UUCP connection, ask your system administrator whether you have Usenet news available. Some of the most common newsreading software packages are readnews, rn, trn, nn and notes. --------------------------------------------------------------------------- 3.2. Usenet Windows newsgroups =============================== There are a total of eight Usenet newsgroups dealing with Microsoft Windows: * comp.os.ms-windows.advocacy This group is intended for adversarial discussions, arguments and comparisons to other computers and operating systems. Applicable to all Windows platforms. * comp.os.ms-windows.announce This is a low-volume moderated group with only Windows-related announcements (and the text versions of the FAQs) and with no discussion. Moderated by Steve Graham (sgraham@shiloh.nimh.nih.gov). * comp.os.ms-windows.apps This group contains discussions, questions, and comments about the selection and use of Windows and Windows NT applications. * comp.os.ms-windows.setup This group is meant for questions and discussions about Windows and Windows for Workgroups setup process, driver availability and selection, and hardware compatability and selection. * comp.os.ms-windows.misc All other discussions about Windows and Windows for Workgroups should be in this group. * comp.os.ms-windows.video (proposed) Discussions about vide0 adapters, monitors and video drivers for usee with Microsoft Windows and Windows NT. * comp.os.ms-windows.networking.windows (proposed) Discussions about Windows' built-in networking capabilities: Windows for Workgroups, Windows NT, Windows NT Advanced Server and LAN Manager. * comp.os.ms-windows.networking.tcp-ip (proposed) Discussions about TCP/IP networking with Windows, WinSock, WinSock-based applications, newsreaders, PPP and SLIP. * comp.os.ms-windows.networking.misc (proposed) Discussions about Windows and other networks, including Netware, Banyan Vines, LANtastic and LAN Server. * comp.os.ms-windows.nt.setup Questions and discussions about the Windows NT setup process, driver availability and selection, and hardware compatability and selection. * comp.os.ms-windows.nt.misc All other discussions about Windows NT should be in this group. * comp.os.ms-windows.programmer.tools Discussions about the selection and use of tools for Windows software development. * comp.os.ms-windows.programmer.win32 All discussions about the Win32 applications programming interface (used in Windows NT and Win32s) and the Windows NT SDK belong in this group.. * comp.os.ms-windows.programmer.misc This group is for all other discussions about Windows software development. * comp.os.ms-windows.programmer.bitmaps (proposed) Discussions about programming with bitmaps, palettes and DIBs. * comp.os.ms-windows.programmer.controls (proposed) Discussions about programming with controls, dialogs, custom controls and VBXs. * comp.os.ms-windows.programmer. drivers (proposed) Discussions about programming Windows and Windows NT drivers and VxDs. * comp.os.ms-windows.programmer. graphics (proposed) Discussions about programming with graphics, GDI, fonts and printing. * comp.os.ms-windows.programmer.memory (proposed) Discussions about memory management, processes and DLLs. * comp.os.ms-windows.programmer.ole (proposed) Discussions about programming with OLE, COM and DDE. * comp.os.ms-windows.programmer.winhelp (proposed) Discussions about development of WinHelp and MultiMedia viewer applications. * comp.binaries.ms-windows This group is for postings of free and shareware Windows applications, utilities, display and printer drivers -- and for the latest FAQs. Moderated by Tin Le (tin@saigon.com). The following groups have been replaced by those shown above: * comp.windows.ms This group was for discussions about Microsoft Windows. * comp.windows.ms.programmer This group was for discussions about programming for Microsoft Windows. The following groups may also be of interest: * alt.winsock This group is for discussions about the use and programming of the Windows Sockets interface. * comp.databases.access (proposed) This group is for dicussions about Microsoft's Access database.. * comp.lang.basic.visual This groups is for Visual Basic (both Windows and MS-DOS versions) discussions. * comp.os.msdos.programmer This groups contains general MS-DOS programming questions. Some, especially those concerning compiler selection, may be of interest to Windows programmers. * bit.listserv.win3-l This group is a two-way gateway of the BITNET WIN3-L mailing list, dealing with all aspects of Windows 3.x. * bit.listserv.access-l This group is a two-way gateway of the BITNET ACCESS-L mailing list, dealing with Microsoft's Access database. The following groups are not for Microsoft Windows! * comp.windows.misc This group is for miscellaneous discussions about windowing systems in general. * comp.windows.news This group is for discussions about the Sun Microsystems NeWS windowing system. In general, these newsgroups are only available to computers connected to Usenet or Internet; they are not gatewayed into BITNET, CompuServe, Prodigy or other services. Some FidoNet BBS systems, however, do carry selected Usenet newsgroups. If you cannot obtain access to these groups on your system, contact the author of this FAQ for possible alternatives. --------------------------------------------------------------------------- 3.3. Alternatives to Usenet ============================ If you are unable to find a connection to the Internet (that procedure can not be easily defined, as the Internet does not have any sort of a formal structure), there are several alternatives available for finding more information about Windows, and for locating Windows software and drivers. BITNET users (as well as any other with an electronic mail connection to Internet) can subscribe to lists such as WIN3-L (win3-l@uicvm.bitnet), a mailing list dedicated to Windows discussions. This mailing list is similar in content to the comp.os.ms-windows.misc newsgroup; no programmer mailing list exists on BITNET. See the following list for a list of mailing lists. America OnLine also provides access to Usenet newsgroups. If you live in North America (or in one of selected Western European countries), you can subscribe to CompuServe, a commercial service. CompuServe has extensive Windows-oriented discussions and a fairly good selection of free software. Although the level of discussion is often less technical, it is much more structured than the Internet. CompuServe also has numerous vendor-supported forums, including ones organized by Microsoft for Windows and Windows NT. Many FidoNet-based BBS systems also carry the Usenet Windows newsgroups. Consult a local BBS listing to find your nearest FidoNet BBS. --------------------------------------------------------------------------- 3.4. Windows-related mailing lists =================================== The following mailing lists are Windows-related. Please use the requests address for administrative mail (such as getting added to the list): * Dr. Help List: drhelp@eng.monash.edu.au Requests: listserv@eng.monash.edu.au * LabView List: info-labview@pica.army.mil Requests: info-labview-requesr@pica.army.mil * Lotus Improv List: improv@bmt.gun.com Requests: improv-request@bmt.gun.com * MathCAD List: mathcad@eng.monash.edu.au Requests: listserv@eng.monash.edu.au * OWL List: owl-list@cs.rpi.edu Requests: owl-list@cs.rpi.edu * ProtoGen/ProtoView List: protoplus@netcom.com Requests: protoplus-request@netcom.com * WIN3-L (Windows 3.x) List: win3-l@uicvm.bitnet Requests: listserv@uicvm.bitnet --------------------------------------------------------------------------- 3.5. Freeware and shareware by ftp =================================== While CompuServe (which has a lot of software) and your local BBS may have large selections, the Internet provides an immense resource for all PC users. The key program to access this software is called ftp (File Transfer Protocol), and it's usable from most Internet system, but is not usable through UUCP links. If you do have ftp available to you, follow the example below to connect to ftp.cica.indiana.edu (do not type in the // comments): $ ftp ftp.cica.indiana.edu // make connection Connected to ... // cica responds Userid (user@cica): ftp // enter "ftp" as userid Password: real_userid@site // enter your own userid ftp> tenex // for binary transfers ftp> cd /pub/pc/win3 // where the goodies are ftp> ls -l // list the directory ftp> get ls-ltR // get the current index ftp> quit // we're done! $ _ Of course, you can get multiple files at a time -- read the ftp manual page for more information. Remember that shareware is not free: register the software you use to encourage the development of more low-cost software. --------------------------------------------------------------------------- 3.6. Popular Internet ftp sites ================================ The following ftp sites provide significant amounts of software of interest to Windows users: * ftp.cica.indiana.edu (129.79.20.84) Directory /pub/pc/win3 contains one of the largest selections of Windows software and device drivers anywhere. Mirrored by wuarchive. Please do not access ftp.cica.indiana.edu between 8am and 6pm EST to prevent overloading the system. * wsmr-simtel20.army.mil (26.2.0.74) Directory pd1: contains a very large selection of MS-DOS (and some Windows) software. Mirrored by wuarchive. * wuarchive.wustl.edu (128.242.135.4) Directory /mirrors/win3 contains a copy of the cica Windows archives, and directory /mirrors/msdos contains a copy of the simtel10 MS-DOS archive. * ftp.uu.net (137.39.1.9) Directory /vendors/microsoft contains a lot of the Microsoft developer support materials available on CompuServe, including tech notes, sample sources, the ODBC SDK and WinHelp documentation for Windows and Win32 SDKs. * garbo.uwasa.fi (128.214.12.3) Directories /win3 and /win31 contain a majority of the cica Windows archives, and a fair amount of non-cica material. Note that garbo.uwasa. fi is located in Finland, and North American users should avoid congesting transatlantic Internet links by ftping from this site. Mirrored by wuarchive. * cc.monash.edu.au Directory /pub/win3 contains a copy of the cica Windows archives. Note that monash is located in Australia, and North American users should avoid congesting transpacific Internet links by ftping from this site. * ftp.und.ac.za Directory /pub/pc/win3/vbasic contains a a variety of things useful to Visual Basic programmers. Note that und is located in SouthAfrica, and you should try to avoid congesting transpacific Internet links by excessive ftping from this site. If your ftp program complains about an unknown site, you can substitute the numeric Internet address (shown after each site name above) for the name in the ftp command. --------------------------------------------------------------------------- 3.7. Using archie ================== If you know the program you're looking for, but don't know where to find it, you might try using a utility called archie. This program allows you to search for a filename in all the available ftp sites. There are numerous archie servers available; to use one of them, telnet to the system, and sign on as archie. Follow instructions to search for a file. The following lists some of the know archie servers currently available for use; pick one in your geographical area: * archie.rutgers.edu United States (Northeast) * archie.sura.net United States (Southeast) * archie.unl.edu United States (West) * archie.mcgill.ca Canada * archie.au Australia and New Zealand * archie.funet.fi Europe * archie.doc.ic.ac.uk United Kingdom --------------------------------------------------------------------------- 3.8. Ftp by email ================== There are several sites that will perform general FTP retrievals for you in response to a similar mail query, although it appears that the info- server@cs.net server is permanently out of order. In general, please be considerate, and don't over-use these services. If people start using them to retrieve megabytes and megabytes of GIF or WAV files, they will probably disappear. Also, keep in mind that your system may be linked to the net using a long-distance UUCP connection, and your sysadmin may not be happy about large mail files using up modem time and filling overloaded spool directories. * bitftp@pucc.bitnet For information on this one (available only to BITNET sites) send it the message: help * ftpmail@decwrl.dec.com For information on this server, available to all Internet sites, send it a mail message with a body containing simply: help * mailserv@garbo.uwasa.fi One final choice is to use the garbo.uwasa.fi server, which lets you access the garbo.uwasa.fi archive (which contains most of the cica files). For instructions, send it a mail message with "Subject: garbo- request" and a single line of text "send help" to send help Please do not use this service if you are located in North America! --------------------------------------------------------------------------- 3.9. FAQs (Frequently Asked Questions) ======================================= Hundreds of Usenet newsgroups have their own FAQs, most of them in text format. You can retrieve almost all of these FAQs' latest versions by ftp from rtfm.mit.edu in the directory /pub/usenet/news-answers. --------------------------------------------------------------------------- 3.10. More about Internet and Usenet ===================================== To learn more about Internet and Usenet, I strongly recommend you purchase or borrow a copy of Ed Krol's The Whole Internet User's Guide and Catalog (ISBN 1-56592-025-2, $24.95), which covers email, news, ftp, archie and much more. This 400-page handbook is a thorough guide to getting around on the Net, clear enough for neophytes but with new information even for true Internet veterans. A wide range of other books are also available; check your local bookstore for the selection. To purchase The Whole Internet User's Guide and Catalog, check your local bookstore or contact the publisher, O'Reilly and Associates at 1-800-998- 9938 (103 Morris St., Sebastopol, CA 95472). --------------------------------------------------------------------------- 3.11. FTP archives on CD-ROM ============================= Walnut Creek offers copies of the cica, wuarchive and simtel FTP archives on CD-ROM, at prices ranging from $25 to $50, with annual subscriptions available. Call (800) 786-9907 or (510) 947-5996 for more information. ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 4. SETTING UP AND CONFIGURING WINDOWS ====================================== --------------------------------------------------------------------------- 4.1. System Configuration ========================== ........................................................................... 4.1.1. Minimum Windows 3.1 configurations ------------------------------------------ The minimum system configurations to run Windows 3.1 are as follows: * Standard Mode 286 processor, 640KB base memory, 256KB extended memory, EGA graphics * 386 Enhanced Mode 386 processor, 640KB base memory, 1MB extended memory, EGA graphics The following are recommended minimum configurations (based on the experiences of many net Windows users) for good performance. * Standard Mode 286/12 processor, 2MB total memory, VGA graphics, mouse * 386 Enhanced Mode 386SX/16 processor, 4MB total memory, VGA graphics, mouse ........................................................................... 4.1.2. Minimum Windows 3.0 configurations ------------------------------------------ The minimum system configurations to run Windows 3.0 are as follows: * Real Mode 8088 processor, 640KB base memory, CGA/Hercules graphics * Standard Mode 286 processor, 640KB base memory, 256KB extended memory, CGA/Hercules graphics * 386 Enhanced Mode 386 processor, 640KB base memory, 1MB extended memory, CGA/Hercules graphics The following are recommended minimum configurations (based on the experiences of many net Windows users) for good performance. (Real Mode is not configurable for good performance, and many applications will not run in it due to a lack of memory.) * Standard Mode 286/12 processor, 2MB total memory, VGA graphics, mouse * 386 Enhanced Mode 386SX/16 processor, 4MB total memory, VGA graphics, mouse ........................................................................... 4.1.3. Minimum Windows NT pre-release configuration ---------------------------------------------------- The minimum recommended system configuration to run the Windows NT pre- release Software Development Kit is as follows: * 386DX/33 processor * 12 MB memory * 100 MB hard disk * VGA graphics The recommended system configuration to run the final retail release of Windows NT, including networking and several applications, is expected to be the following (according to Microsoft): * 386DX processor * 8 MB memory * 100 MB hard disk * VGA graphics ........................................................................... 4.1.4. Standard mode vs. 386 Enhanced mode ------------------------------------------- If you own a 386- or 486-based system, you have the choice of running in either Standard or Enhanced mode. The following lists the advantages of each: Standard mode * Speed. Many aspects of Windows run substantially faster in Standard mode than in 386 Enhanced mode. 386 Enhanced mode * Virtual memory capability. * Multiple DOS sessions are pre-emptively multitasked. * DOS sessions may be run in a window. * Able to run 386-specific applications such as Mathematica, FrameMaker and wdeb386. --------------------------------------------------------------------------- 4.2. Selecting a hardware configuration for Windows ==================================================== ........................................................................... 4.2.1. Selecting a CPU/FPU --------------------------- As always, faster is better. However, CPU alone won't determine your system's Windows performance. You can get fairly good performance even with a 386SX/20 processor given sufficient memory, and if you have a video accelerator card, a 386DX/40 doesn't feel much slower than a 486DX/33. You most definitely won't be able to tell a 486DX/33 and a 486DX2/66 apart in "normal" Windows operation. Windows itself will not take advantage of a floating point unit such as the 287 or 387. ........................................................................... 4.2.2. Selecting the memory size --------------------------------- Again, the more memory the better. You can get tolerable performance with 2 MB, but 4 MB is a more realistic minimum for decent performance. If you have 8 MB, you can use a reasonably large disk cache (such as SmartDrive) and RAM disk; with 16 MB, you can disable swapping completely and get even better performance. Make sure your memory is either on the motherboard, or on a high-speed bus (such as EISA or MCA). The standard ISA bus will slow your memory accesses down to a crawl. ........................................................................... 4.2.3. Selecting a hard disk ----------------------------- For best Windows performance, you want a WD-compatible disk controller. As most SCSI controllers (such as the excellent Adaptec 1542B and 1740) are not WD-compatible, they can not use Windows' FastDisk 32-bit disk access facility. Worse yet, you may need to double-buffer your SCSI drive with SmartDrive, further degrading performance. The best bet for Windows 3.1 and future Windows NT performance is a high- speed IDE drive (all of which are WD-compatible). The controllers are inexpensive (and built into many motherboards), and the new drives are quite fast. IDE drives tend to be smaller, however, than their SCSI and ESDI counterparts, ranging from 40 MB up to about 500 MB (SCSI and ESDI drives currently on the market range from 300 MB to over 2 GB). The final option is to use an ESDI drive; these drives are usually identical to their SCSI counterparts, but with different interface electronics. As long as you don't use a controller with a custom BIOS (such as the WD-1009), you can use Windows' 32-bit disk access for better performance. While ESDI is generally somewhat slower than SCSI, the 32-bit access capability far outweighs that difference. ........................................................................... 4.2.4. Selecting a video adapter --------------------------------- Given Windows GUI orientation, a fast video adapter is essential for good performance. In addition, a better video adapter can provide higher resolution, higher refresh rates (for a steadier picture) and more on- screen colors (for more realistic picture reproduction). You should look for a card supporting a 70 Hz or 72 Hz refresh rate (provided your monitor can handle that), and likely at least A local bus or EISA graphics card will provide better performance, but the difference is not as significant with accelerated cards as it is with dub frame-buffer designs such as the ET4000 chipset. In general, don't pay double just to get an EISA card! The following will attempt to describe some of the high performance (i.e. better than VGA) video adapters currently on the market. The descriptions are frequently based on the chipsets rather than commercial product names, as numerous vendors will market adapters using basically identical hardware. All comments below are subjective and reflect the author's opinion only. Do not base a purchase decision solely on this listing, but always test a video adapter using your own applications prior to purchase, if possible. 4b: 4-bit color (16 colors) 8b: 8-bit color (256 colors) 15b: 15-bit color (32,768 colors) 24b: 24-bit color (16.7M colors) *interlaced * ATI: Mach 8 1280x1024x4b*, 1024x768x8b, 800x600x8b, 640x480x8b This is the original ATI accelerator chipset, which powers the ATI 8514 Ultra, Graphics Ultra and Graphics Vantage. The Ultra cards use VRAM video memory, while Vantage uses slower DRAM. The 8514 Ultra does not include onboard VGA, but both other cards do. All three cards are 8514 compatible. These cards, while no longer the fastest around, provide excellent Windows performance at all resolutions. The driver support is very good (with Windows NT beta drivers available), and ATI provides anti-aliased Crystal Fonts for better readability. * ATI: Mach 32 1280x1024x8b, 1024x768x15b, 800x600x24b, 640x480x24b The second-generation ATI accelerator chipset powers the ATI Ultra+ and Ultra Pro. The Ultra Pro uses VRAM video memory, while Ultra+ uses slower DRAM. Both cards are 8514 compatible. Both cards are extremely fast and provide blinding Windows performance. The driver support is excellent, with even beta Windows NT drivers available. ATI provides anti-aliased Crystal Fonts for better readability. One problem is that the highest performance Ultra+/Pro setup requires a 4 MB memory aperture, which is not possible on an ISA-based system with 16 MB of memory; disabling the memory aperture reduces performance by at least 5-10%. Effectively an ISA-based Ultra+ is slower in a 16 MB system than the original Mach 8-based Graphics Ultra. * ATI: Mach 64 1280x1024x8b, 1024x768x15b, 800x600x24b, 640x480x24b These are ATI's upcoming third-generation accelerator cards. * Avance Logic: ALG2101 1280x1024x4b*, 1024x768x8b, 800x600x15b, 640x480x15b The '2101 is a medium-speed performer with some serious reliability problems and buggy Windows drivers. * Avance Logic: ALG2201 1280x1024x8b*, 1024x768x15b, 800x600x24b, 640x480x24b The '2201 is the upcoming replacement for the '2101, with 24-bit true-color support, and intended for local bus designs. * C&T: 82C481 1280x1024x8b*, 1024x768x15b, 800x600x24b, 640x480x24b C&T's '481 chipset (often combined with the C&T Wingine chipset for VGA compatability) is a blazingly fast performer, but is currently hobbled by limited driver support. Check that the modes you need are supported before buying, and be prepared to have Windows fly! * Compaq: 128084 1024x768x8b, 800x600x15b, 640x480x8b Compaq's excellent QVision accelerator design is now getting to be a bit long in the tooth, and its performance is below nearly all of its competitors. * IIT: AGX015 1280x1024x8b*, 1152x960x8b, 1024x768x15b, 800x600x24b, 640x480x24b The AGX015 is IIT's implementation of the XGA specification, although at least the first available cards (Hercules' Graphite series) are not XGA- compatible. Despite some benchmark cheats, this remains an extremely fast card in real use, and wit has refresh rates of up to 90 Hz available. * S3: 87C801 1280x1024x8b, 1024x768x15b, 800x600x24b, 640x480x24b The '801 is a higher-performance (32-bit), lower-cost version of the '924 chipset, using inexpensive DRAM instead of the faster VRAM video memory. The performance edge over the original '911 is in excess of 50% on WinMark benchmarks. * S3: 87C805 1280x1024x8b, 1024x768x15b, 800x600x24b, 640x480x24b The '805 is a further development of the '801 chipset, optimized for EISA and local buses, and with more memory to allow hi-color and true-color modes at higher resolutions. Like the '801, it's a 32-bit DRAM design. * S3: 87C911 1280x1024x4b*, 1024x768x8b, 800x600x15b, 640x480x24b This is the original S3 accelerator chipset. It provides very good all- around performance, and is widely used in accelerator boards such as the Diamond Stealth. For better performance, look for the newer '801 or '928 chipsets, though. * S3: 87C924 1280x1024x4b*, 1024x768x8b, 800x600x15b, 640x480x24b The '924 is an updated version of the original S3 '911 chipset. Its performance is only somewhat improved over the original chipset (and less so than the '801 and '928), but it has some hardware bugs fixed (these bugs were previously worked around by the Windows drivers). * S3: 87C928 1280x1024x15b*, 1024x768x24b, 800x600x24b, 640x480x24b The '928 is a high-end version of the '805 chipset, intended for ISA as well as EISA and local buses, and supporting up to 4 MB of VRAM for true color at high resolutions. * Texas Instruments: TMS 34010 4096x4096x24b [the TMS34010 chipset effectively does not limit resolution] The TMS34010 is a true coprocessed card instead of a fixed-function accelerator. As it's design is not optimized for Windows, it is at its best in CAD applications and similar, which can take advatage of its display list processing capabilities. It provides very good Windows performance, but at a very high price point. Check performance of the specific model before buying, though -- the drivers are developed by individual vendors, and can have a trememndous impact on TMS34010 perforomance. * Texas Instruments: TMS 34020 4096x4096x24b [the TMS34020 chipset effectively does not limit resolution] The TMS34020 is a 200 MHz 32-bit implementation of the original 100 MHz 16- bit TMS 34010. It can provide outstanding Windows performance (on par with the ATI Ultra Pro), but it does so at a very high price point. The chipset is worth considering mainly if you also use your system for CAD. * Tseng Laboratories: ET4000/W32i 1024x768x24b The latest 32-bit implementation of the venerable ET4000 is amazingly speedy considering its low cost. Cards such as the Hercules Dynamite are performing on par with ATI's Mach32 accelerators at less than half the price. Highly recommended. * Video 7: HT216 1280x1024x4b*, 1024x768x8b, 800x600x15b, 640x480x15b Video 7's first accelerator chipset is an inexpensive design which provides middling performance, on par with the Compaq 128084 and the Weitek 5186. * Western Digital: WD90C31 1280x1024x4b*, 1024x768x8b, 800x600x15b, 640x480x15b Western Digital's new chipset is used by a number of display adapters, including the Paradise Windows Accelerator and the Diamond Speedstar 24x. While the chipset benchmarks moderately well (slotting between ATI's and S3's first- and second-generation chipsets), it has worse-than-expected real life performance, especially in scrolling. The current drivers are also quite buggy and unreliable. * Western Digital: WD90C33 1280x1024x8b, 1024x768x15b, 800x600x24b, 640x480x24b WD's second generation design will be targeted at local bus designs, and will attempt to improve performance with more accelerated operations and a 32-bit design (instead of the 32-bit/16-bit hybrid design in the WD90C31). * Weitek: W5186 1024x768x8b, 800x600x8b, 640x480x8b Weitek's initial foray into accelerator chipsets does not provide stellar performance, largely since the accelerated operations are limited to BitBlits and line drawing. An 16-bit/8-bit internal design and a lack of support for more than 256 colors don't add to the attraction of the W5186 chipset. * Weitek: W5286 1280x1024x4b*, 1024x768x8b, 800x600x15b, 640x480x24b The upcoming second-generation Weitek chipset will attempt to correct some of the problems of the W5186, using a 32-bit/8-bit internal design, true- color support (albeit only at low resolutions) and accelerated color expansion and pattern fills. It looks doubtful, though, that the W5286 would significantly surpass the top first-generation accelerators (such as the ATI Ultra and S3 87C911), let alone match the latest performers. --------------------------------------------------------------------------- 4.3. System BIOS compatability =============================== A number of different computers have BIOS incompatabilities with Windows 3.1. The following list contains BIOSes with such problems. Contact you manufacturer for an update if you have one of these systems. Manufacturer Version Problem ALR MPS Incompatible with Seagate IDE disks AMI 1987 Floppy access causes reboot AMI 1989 Intermittent crashes AMI 1991 Serial port problems for versions prior to 1991-07-07 AST Premium/286 Crashes, keyboard lockups and network errors Award BIOS <= 3.04 Floppy read errors before version 3.05 DTK BIOS <= 34 No IDE drive support DTK BIOS 36 Setup utilities must be disabled Peak BIOS 1.10 1.30 or newer is required Phoenix BIOS <= 1987 1988 or newer is required Quadtel BIOS <= 3.04 3.05 or newer is required Tandon All Old BIOSes cause keyboard failures Toshiba T3100/20 BIOS 4.2 is required Toshiba T3100e BIOS 1.7 is required Wyse All Setup detects 101 keyboard as 84 Zenith 286 Keyboard problems Zenith 386/16 BIOS 2.6E or newer is required Zenith TurboSport BIOS 2.4D or newer is required The BIOS name and version number (or date) are usually displayed when the system boots. As an alternative, you can use msd.exe, a DOS-based diagnostic utility included with Windows 3.1, to determine the BIOS your system is using. Also, there are several diagnostic utilities available in wuarchive's /mirrors/msdos/info directory: sysch233, sysid602 and ifp1p155. --------------------------------------------------------------------------- 4.4. Video drivers =================== ........................................................................... 4.4.1. Identifying your video card ----------------------------------- The first step in finding the correct Windows drivers for your video card is to determine the type of card you have. First, you may have a "brand- name" card; if so, your box and/or documentation will ientify the type of card. Second, you can look at the BIOS message (if any) displayed when you boot your system. Third, you can open up your system, and look for identification on the card itself -- usually either printed on the card itself or on some of the integrated circuits. As an alternative, you can use msd.exe, a DOS-based diagnostic utility included with Windows 3.1, to determine the manufacturer and type of video card in your system. Also, two utilities available from wuarchive, atmem10 and vgautils (in directory /mirrors/msdos/vga) may help you identify your video card. See the following section on locating a video card driver for a listing of possible names to look for. ........................................................................... 4.4.2. Locating a driver ------------------------- Once you have identified your card, you are ready to begin searching for the right driver. First, check whether Windows includes the driver you are searching for (Windows 3.1 includes generic VGA (640x480x16) and SuperVGA (800x600x16) drivers, as well as numerous specific drivers). Second, look at the diskettes you received in the video card package. These may contain the appropriate driver, saving you from a further search. If neither Windows nor the diskettes have the drivers, or they are out of date, you may wish to check ftp.cica.indiana.edu for the latest one. If there are none at cica, you can try one of the following: * Contact your dealer * Call the video card manufacturer * Download the latest driver from the manufacturer's BBS * Download the latest driver from the Microsoft BBS (206-936-6735) Note that Windows 3.1 drivers are normally dated after the release date of Windows 3.1 itself (April 6, 1992). ........................................................................... 4.4.3. Video card manufacturers -------------------------------- The following is a partial list of video display hardware vendors who support using Windows with their products. CAUTION: The numbers listed may not, by the time you read this, be up to date! Ahead Systems 510-623-0961 Appian Technology 206-649-5363 ATI Technologies 416-756-4591 Boca Research 407-241-1601 Diamond Computer 408-730-1100 Everex Systems 510-226-9694 Focus Information 510-657-9451 Headland Technology Video Seven 510-656-0503 Matrox Electronic 514-685-6008 Micro-Labs 312-648-6008 Micron Technology 208-368-2130 National Design 512-343-5054 NEC NEC 512-832-1962 Nth Graphics Nth Graphics 512-832-1962 Number Nine Computer Number Nine 617-862-7502 Orchid Technology Orchid 510-683-0327 Panacea WinSpeed 603-432-5193 Sigma Designs Sigma 510-770-0111 STB Systems STB 214-437-9615 Tecmar Tecmar 216-349-0853 Trident Microsystems Trident 415-691-1016 ViewSonic ViewSonic 213-944-2195 The following vendors do not provide BBS access, but do make updates available on CompuServe, in the forum indicated. Tseng Laboratories ET3000, ET4000 WINADV ........................................................................... 4.4.4. Using 256 (or more) colors in Windows --------------------------------------------- In order to use more than 16 colors in Windows, your display card and its driver must first support 256 colors. Second, your application must know about 256 colors in order to take advantage of this feature, as this requires palette switching and some additional programming. Many applications currently on the market only support 16 colors. In order to get 256 colors, your video card will need at least 320K (for 640x480), 512K (for 800x600) or 768K (for 1024x768) of RAM. For most video cards, 256-color drivers are also much slower than 16-color drivers. Some video cards support 15-bit (32,768 colors) or 24-bit (16,777,216 colors) video; these can also be used in Windows given the appropriate display driver and sufficient video memory. ........................................................................... 4.4.5. Panacea Winspeed ------------------------ One alternative to the specific manufacturer-supplied drivers is to use Panacea's Winspeed drivers. These drivers often provide a substantial speed improvement over vendor-supplied drivers, although some vendors have highly optimized drivers which can meet or exceed Winspeed's performance. ........................................................................... 4.4.6. CGA drivers ------------------- Windows 3.1 does not include CGA drivers, as the recommended minimum for running Windows 3.1 is EGA. If you need to run Windows on a CGA system, you can download the CGA drivers from the Microsoft BBS (206-936-6735). --------------------------------------------------------------------------- 4.5. Printer drivers ===================== The following is a partial list of printer manufacturers who support using Windows with their products. CAUTION: The numbers listed may not, by the time you read this, be up to date! Canon Canon 516-488-6528 Lexmark IBM laser printers 606-232-5653 NEC NEC 508-635-6328 Okidata Okidata 800-654-3282 Panasonic Panasonic, Roland 201-863-7487 The following vendors do not provide BBS access, but do make updates available on CompuServe, in the forum indicated. DEC DEC DECPCI Varityper Varityper Desktop Publishing ........................................................................... 4.5.1. Eliminating the Ctrl-D in PostScript output --------------------------------------------------- To prevent Windows from placing a Ctrl-D (printer reset) at the beginning of your PostScript output files, specify CtrlD=0 in the [ModelName,Port] section of your win.ini file. Note that this method does not appear to work with the generic PostScript Printer driver. ........................................................................... 4.5.2. EPS graphics print in portrait even on landscape pages -------------------------------------------------------------- If EPS (Encapsulated PostScript) graphics won't print correctly in landscape mode, try adding the following line to the [Model,Port] section of your win.ini file: LandscapeOrient=270 ........................................................................... 4.5.3. Hewlett-Packard DeskJet printing problems ------------------------------------------------- If you are getting incomplete pages printed on your DeskJet, make sure that there is the the entry PrtResFac=0 in the [ModelName,Port] section for the DeskJet in your win.ini file. Note that only the drivers supplied by Hewlett-Packard support HP scalable fonts and/or color printing, and these do not currently support TrueType fonts. ........................................................................... 4.5.4. PostScript printer uses incorrect fonts ----------------------------------------------- If you have a PostScript printer installed, and your documents print with the incorrect font whenever you select something out of the ordinary (for example, WingDings or one of the Lucida fonts), your printer driver is likely configured incorrectly. In Control Panel's printer setup, click Setup..., then Options..., and finally Advanced.... Now make sure you have the Use Printer Fonts for all True Type Fonts checkbox cleared. If you have this box checked, Windows will attempt to match each of your TrueType fonts to the "nearest" PostScript font, not always very successfully. Alternately you may choose to purchase Adobe Type Manager, and use Type 1 PostScript fonts instead of TrueType fonts to avoid the problem. ........................................................................... 4.5.5. Selecting a PostScript printer driver --------------------------------------------- If your PostScript printer model is not listed in the available printers listing, you should not choose the generic PostScript printer. Microsoft advises that "if you select PostScript Printer, you may encounter problems when printing". Instead, you may wish to try Apple LaserWriter as your first possibility. ........................................................................... 4.5.6. Using an Apple Imagewriter or Imagewriter II with Windows ----------------------------------------------------------------- the Apple Imagewriter and Imagewriter II are compatible with the C-Itoh 8510 printer, whose driver is included with Windows 3.1. You will alse need to use a null modem with the serial cable connection from your PC to the printer, and set your serial port to 9600/8N1. --------------------------------------------------------------------------- 4.6. Math coprocessors and WIN87EM.DLL ======================================= Windows 3.x itself does not take advantage of a math coprocessor. Windows applications, on the other hand, may or may not, depending on the application: for example, Excel will, while Word for Windows won't. In general, an 80x87 chip gives the greates speedup for trigonometric/log type of calculations, and does not significantly improve graphics speed in most cases. The WIN87EM.DLL is a dynamic link library which provides floating-point emulation for Windows applications. Any application which is capable of using an 80x87 will need this library on a machine without an 80x87. --------------------------------------------------------------------------- 4.7. Multimedia ================ ........................................................................... 4.7.1. AdLib cards and .wav files ---------------------------------- The standard AdLib driver supplied with Windows 3.1 is a MIDI-only driver and is not capable of playing .wav files. You can add this capability, however, by installing the driver contained in adlibw.zip, available at ftp .cica.indiana.edu and other sites. ........................................................................... 4.7.2. Using MIDI cards with Windows 3.1 ----------------------------------------- if your sound card plays MIDI files (such as canyon.mid), but none of the selections under Control Panel's Sound icon are available, your card/driver does not support wave files. You will need either to add a wave driver for your card (if available -- contact your sound card manufacturer) or to get a card which supports wave drivers. ........................................................................... 4.7.3. SoundBlaster Pro and Windows 3.1 ---------------------------------------- One of the most common symptoms of SoundBlaster Pro problems in Windows 3.1 is a complete hang of the system on exit from Windows. You need to use the SoundBlaster Pro drivers, not the SoundBlaster 1.5 drivers included with Windows 3.1. The drivers shipped with SB Pro may be out of date, like those on Microsoft's BBS and on CompuServe (this may, however, have changed by the time you read this). In any case, ftp.cica.indiana.edu has the set of updated drivers available as sounds/sbpw31.zip. You can also get them from Creative Labs' BBS at (408) 428-6660. Note that if you tell the driver to expect an IRQ other than the one the SoundBlaster Pro actually uses, Windows will complete the driver installation. When you than try to play a .WAV file, Windows will not recognize any device capable of playing it. ........................................................................... 4.7.4. Using the PC's built-in speaker --------------------------------------- Windows 3.1 does not contain a driver for playing sounds over the PC's built-in speaker, as the speaker is not quite standardized and not all machines would work as intended. If you would like to try, however, you should get a copy of the speaker driver, contained in the self-extracting archive speaker.exe, available at Microsoft's BBS, ftp.cica.indiana.edu and other sites. --------------------------------------------------------------------------- 4.8. System resources ====================== Free system resources are things such as window handles and global memory block handles (handle is a Windows programming term, but it is basically an identifier for a window or any other global item. Each window (dialog, icon, memory block, or whatever) requires a handle. Windows 3.0 has a limit of 64K of resources (32,768 handles), and Windows 3.1 has a limit of 128K of resources (65,536 handles). Windows NT does not have a global resource limit. You can't increase system resources by just adding more memory; the only real solution is to close some applications if you are running low. Windows 3.0 Program Manager was a resource hog, but the 3.1 version is much better. Some poorly-written applications will also not release all the resources they have grabbed when they exit. You can check for this by checking the Free System Resources figure, starting up the application, working in it for some time, and then exiting. If the Free System Resources figure is not the same as before you started, your application is not properly freeing its resources and it's time for you to call the vendor and complain! --------------------------------------------------------------------------- 4.9. Networking ================ ........................................................................... 4.9.1. Compatible Networks --------------------------- The following networks have either been tested by Microsoft, or reported by Usenet users to be functional with Windows 3.x: Network earliest version 3Com 3 Plus 1.0 3Com 3+Open 1.0 Banyan Vines 4.0 BW NFS ?.? DEC PathWorks 4.0 Frontier Tech Super-TCP 1.0 [Windows-based TCP/IP, SLIP and NFS] FTP NFS ?.? [Windows-based telnet application] IBM PC LAN 1.1 [except server] LAN Manager 1.0 LAN Server 1.0 LANtastic 4.0 Novell Netware 2.15 [shell & utilities must be version 3.01] Sun PC-NFS 3.5 [must use interrupt 3 instead of 5] Wollongong NFS 2.0 [Windows-based telnet, FTP; include SLIP] Note that many NFS packages have difficulty with Windows for Workgroups due to a bug in WfW FindNext implementation; check with the vendor to determine whether their NFS implementation has a workaround available. ........................................................................... 4.9.2. Windows for Workgroups ------------------------------ 4.9.2.1. Accessing Windows for Workgroups drives prior to starting Windows Unless you read the documentation very thoroughly, you will get the impression that you cannot access drives shared using Windows for Workgroups (or Windows NT) until you have started Windows for Workgroups on your own machine. However, there is a way of accessing the network (as a client only, not as a server) even from the DOS level. To access the network resources, simply enter the command net logon /yes at the DOS prompt. Omitting the /yes option will still work, but will ask you whether you are really sure you want to do this. To disconnect the network, enter net stop /yes Note that this will use up 100K of your maximum 640K of DOS memory. 4.9.2.2. Usin NetBIOS from MS-DOS You can start NetBIOS (including the NETBEUI protocol) by entering the following commands before starting Windows: NET START NETBIND NET START NETBEUI You will then have access to NetBIOS even for MS-DOS applications without using Windows for Workgroups. 4.9.2.3. Sharing a CD-ROM drive with Windows for Workgroups To share a CD-ROM drive with Windows for Workgroups, you must first use MSCDEX (Microsoft CD-ROM Extensions), v. 2.21 or later. If you do not have a more recent version, 2.21 is included on your WfWG distribution disks. In additition, you will need to specify the /s (share) option on the MSCDEX commandline in roder to allow sharing of the drive. Finally, depending on how a workstation uses the shared CD-ROM drive, it may or may not need the MSCDEX installed on that station (typically, using the CD-ROM strictly for file access will not require the use of MSCDEX). If you do install MSCDEX on workstations, do not specify the /s switch. ........................................................................... 4.9.3. Windows for Workgroups with TCP/IP ------------------------------------------ Microsoft does not officially support using Windows for Workgroups with TCP/IP. However, it's possible to use your existing TCP/IP protocol with a shared NDIS protocol stack. This will allow you to access NFS and TCP/IP (telnet and ftp) as usual, but with full Windows for Workgroups functionality available as well. Unfortunately you will generally lose the Windows-specific capabilities of your NFS software (such as mounting NFS drives from File Manager). See the following sections for examples of how to set up Windows for Workgroups with a TCP/IP and NFS-based network. 4.9.3.1. DEC Pathworks with NDIS The following example has been tested and is known to work with Pathworks. Note that this example does not include the usual config.sys options such as device=himem.sys; you can add these as usual. * config.sys DEVICE=c:\win\protman.dos /i:c:\win DEVICE=c:\win\depca.dos DEVICE=c:\decnet\dllndis.exe DEVICE=c:\win\workgrp.sys