• Microsoft Windows Frequently Asked Questions Prepared 03/07/95 • Keywords for All Knowledge Base Articles • Keywords for the Windows Knowledge Base • Knowledge Base Articles • Other Sources of Information • User Survey THE INFORMATION IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES EITHER EXPRESSED OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS, OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FORGOING EXCLUSION OR LIMITATION MAY NOT APPLY. Copyright (c) 1995 Microsoft Corporation. All rights reserved. • Microsoft Windows Frequently Asked Questions • Keywords for All Knowledge Base Articles • Categories and Keywords for All Knowledge Base Articles • Keywords for the Windows Knowledge Base • Knowledge Base Articles • Other Sources of Information • User Survey • Microsoft Windows Frequently Asked Questions • Keywords for All Knowledge Base Articles • Keywords for the Windows Knowledge Base • Personal Operating Systems Query Keywords for Knowledge Base • Knowledge Base Articles • Other Sources of Information • User Survey • Microsoft Windows Frequently Asked Questions • Keywords for All Knowledge Base Articles • Keywords for the Windows Knowledge Base • Knowledge Base Articles • Exception Errors with EMM386.SYS / EMM386.EXE • WW0335: Memory Management with Windows 3.0 and 3.1 • How to Rebuild the Default Windows REG.DAT File • Windows Driver Library Information • Windows and WFWG 3.1x Setup Error Codes (000 through 100) • WW0530: SMARTDrive and 32-Bit Disk Access • Windows 3.1 Err Msg: Call to Undefined Dynalink • Creating a New SYSTEM.INI Without Third-Party Drivers • Control Panel .CPL Files and Icon Installation • Windows Err Msg: Fault in MS-DOS Extender • Windows Err Msg: The Microsoft Windows 32-Bit Disk... • WW0654: Windows 3.1 and Serial Communications • Reinstalling Windows Without Losing Settings • Windows Err Msg: EMM386 Exception Error #6 • WW0524: Troubleshooting GP Faults (UAEs) • Troubleshooting MS-DOS 6.x and EMM386.EXE • Windows for Workgroups Mail Issues • How to Troubleshoot WFWG Network Connection Problems • Troubleshooting Serial Port Problems in Windows • WFWG Upgrade 3.11 Disk Directories (3.5 Inch, 1.44 MB) • WFWG: Creating a New SYSTEM.INI Without Third-Party Drivers • WFWG 3.11: Hardware Compatibility List - Modems for AWFAX • WG0974: VKDA.386 Corrects Keyboard Problems • Troubleshooting Insufficient Memory Errors • Using 32-Bit Disk Access on WD 2540 Hard Disk Drives • WFWG Err Msg: Error 58 on Protocol 0 • Troubleshooting Remote Access in Windows for Workgroups 3.11 • Summary List: Windows for Workgroups 3.11 Confirmed Problems • Installing Win32s in Windows and Windows for Workgroups • Troubleshooting At Work PC Fax in WFWG 3.11 • Extended Error Code Information • EMM386 Troubleshooting and Technical Information • Windows 3.1 Setup Error Codes (S208 through S214) • Windows 3.1 Hardware Compatibility List • WW0525: Troubleshooting 386 Enhanced Mode Problems • Windows 3.1 Resource Kit WIN.INI Section Settings • Top Questions and Answers for Windows 3.1 • Windows 3.1 Err Msg: Error Loading PROGMAN.EXE • Problems When Exiting Windows or WFWG After Running 386 Enh • What Is a Clean Boot for Windows 3.1? • WFWG Err Msg: Error 6118: The List of Servers for This... • What Is a Clean Boot for Windows for Workgroups? • Windows for Workgroups Hangs at Logo Screen • Troubleshooting 'Segment Load Failure' Errors • WFWG Err Msg: Windows 3.x Could Not Be Located... • How to Create a New WIN.INI Without Third-Party Information • System Slows After 32-Bit File Access Is Enabled • WG0949: Windows for Workgroups 3.11 Setup Information • WFWG 3.11: Hardware Compatibility List - Modems for RAS • WFWG 3.11: Hardware Compatibility List - Network Cards • Installing Novell NetWare 3.12 and 4.0x Support for Windows • EMM Exception Error #6 Exiting Windows for Workgroups 3.11 • "Not Enough Memory" Error Occurs When Browsing • Microsoft At Work PC Fax: Top Questions and Answers • WFWG 3.11: 3C509 MLID May Cause Lost Connections and Hangs • Recovering Windows 3.1 After Installing WFWG 3.11 • WG1001: Updated SERIAL.386 Driver for WFWG • WFWG Err Msg: Error 58: The Network Has Responded Incorrectly • RAS ErrMsg: Error 692: Hardware Failure in Port or Attached... • Windows for Workgroups: Error 58 on Protocol 0 - (Non-ODI) • Windows Err Msg: Cannot Find KRNLxxx.EXE • Floppy Disk Drive Problems in 386 Enhanced Mode • Err Msg: 'Incorrect System Version' When Starting MS-DOS App • Permanent Swap Files and the Disk Partition Table • Causes of General Protection Faults • Windows 3.1 Setup Error Codes (S000 through S022) • The WIN.INI [Compatibility] Section • WW0526: Windows 3.1 Setup • WW0532: Object Linking and Embedding (OLE) • Unexpected DOS Errors 0 - 23 and Windows • Troubleshooting Lost Network Connections • Windows for Workgroups: How VSHARE.386 Manages File Sharing • Troubleshooting MS Backup and MS Backup for Windows • Your Computer Fails the Microsoft Backup Compatibility Test • Using Novell's ODI Drivers with Windows for Workgroups • WG0666: WFWG 3.10 Setup Information • WFWG Err Msg with New NETAPI.DLL: Call to Undefined Dynalink • WW0863: Fixing System Hangs with MS-DOS Apps & Novell NetWare • WG0904: Support for Novell NetWare 4.0 • Using Novell's ODINSUP with VLM.EXE and WFWG 3.11 • EMM Exception Error #6 Exiting Windows for Workgroups 3.11 • Pentium-Based Machine Hangs with Communication Applications • RAS ErrMsg: NETBIOS Error 640: A Netbios Error Has Occurred... • WG1004: MSODISUP.386 Fixes Problems Using 3Com ODI MLIDs • Err Msg Starting WFWG: Cannot Find NWGDI.DLL • Problems Sending Mail After Installing AWFAX • Common Questions and Answers for Windows 3.11 • WFWG Err Msg: WINFILE Caused a GP Fault at 0009:028A... • Windows Err Msg: WDCTRL Validation Failed at Phase • WW1116: OLE Version 2.02 • MS-DOS Partitioning Summary • "Missing Operating System" and "No ROM BASIC" Error Messages • Windows Err Msg: Group File .GRP Invalid or Damaged... • Causes of System Integrity Errors in Windows 3.1 • Windows 3.1 Resource Kit SYSTEM.INI [386ENH] Section A-L • Windows 3.1 Resource Kit SYSTEM.INI [386ENH] Section M-Z • How Windows Determines the Recommended Maximum Swap File Size • Windows Err Msg: Error Loading SYSTEM.DRV • Troubleshooting Microsoft and Compatible Mice in Windows • WFWG Err Msg: Memory Is Insufficient to Run KRNL386.EXE • Real-Mode NDIS Drivers Included with Windows for Workgroups • Windows Err Msg: Cannot Find a Device File that May Be... • Information on System Resources in Windows • Setup, Network Card Settings, and Preliminary Troubleshooting • WFWG Err Msg: Protocol Manager Reported an Incomplete Binding • Parity Errors in Windows 3.x • WFWG: Creating a WGPO on a Novell NetWare Server • How Windows Handles Bad Permanent Swap Files • Windows Err Msg: Corrupt Swap File or Unsupported DOS Version • Recovering Windows 3.1 After Installing WFWG • Invalid VxD Dynamic Link Call to Device Number 000D • Error Messages or Hangs Using 3Com EtherLink III (3C509) • Most Common Questions and Answers About Microsoft WFWG 3.11 • Using Novell's ODINSUP and NETx with Windows • Extended Error 53 When Accessing Network Drives from MS-DOS • Additional NICs Supported in Windows for Workgroups 3.11 • Remote Access Service - Error 714: Configuration Error • WW1000: Updated VSHARE.386 for Windows/Windows for Workgroups • Err Msg Installing DeskJet 500 4.0 Driver: COMMCTRL.DLL Is... • Installing an Unlisted RAS Modem • Methods to Detect a Boot Sector Virus • Reasons for Windows 3.1 Setup to Fail While Upgrading • Media Player Cannot Play Audio CD If CDAudio=0 in MPLAYER.INI • Supported NICs and NDIS Drivers Included with WFWG • Overview of Memory-Management Functionality in MS-DOS • Cannot Run Windows on Packard Bell Running MS-DOS 6 or Later • Windows for Workgroups: Avoiding Hardware Conflicts • WFWG 3.11 Err Msg: Segment Load Failure • Troubleshooting HIMEM.SYS 3.10 XMS Test (TESTMEM) Failures • WG0992: Updated Files for Microsoft At Work PC FAX 1.0 • Windows Hangs with SMC Ethernet 16 Elite Ultra 16T Adapter • Other Sources of Information • User Survey • Microsoft Windows Frequently Asked Questions • Keywords for All Knowledge Base Articles • Keywords for the Windows Knowledge Base • Knowledge Base Articles • Other Sources of Information • Information About Knowledge Base Help Files • User Survey • Microsoft Windows Frequently Asked Questions • Keywords for All Knowledge Base Articles • Keywords for the Windows Knowledge Base • Knowledge Base Articles • Other Sources of Information • User Survey • Microsoft Knowledge Base Help File Survey Categories and Keywords for All Knowledge Base Articles Article ID: Q94671 CATEGORIES AND KEYWORDS FOR ALL KNOWLEDGE BASE ARTICLES ======================================================= To categorize articles within the Microsoft Knowledge Base and make finding information easier, a common set of keywords has been adapted for use throughout the KB. These keywords are used to categorize the subject of each article. Each article has one SUBJECT keyword. A secondary keyword indicating the TYPE of article can also be used. To query on one category, enter the category code and a wildcard. For example: kb3rdparty* To query on more than one category, enter each category code with a wildcard. For example: kb3rdparty* or kbinterop* or kbusage* To query on one subcategory, enter the complete code. For example: kbbuglist To query on more than one subcategory, enter all the complete codes. For example: kbbuglist or kbfixlist You can also mix categories and subcategories in one query. For example: kbtshoot or kbnetwork* NOTE: At the end of this article is a table that lists formerly used keywords and their replacements. INFORMATION CATEGORIES AND KEYWORDS =================================== Article subject Keyword ---------------------------------------------------------------- Interactions with third-party products kb3rdparty Interoperability with other MS products kbinterop How to use product features/functionality kbusage Printing kbprint Setup and installation issues kbsetup Networking kbnetwork Environment and configuration information kbenv OLE technology kbole Tools, utilities, applets, such as MS Draw or Write kbtool Programming kbprg User interface kbui Graphics kbgraphic Multimedia kbmm Hardware kbhw Microsoft At Work kbatwork Sound (audio) issues kbsound Display (video, monitor, resolution) issues kbdisplay Readme files kbreadme Lists of vendor phone numbers, disk directory listings, other lists or references kbref Support boundaries, policies, processes & procedures kbpolicy Other: Any subject not covered in other categories kbother Article types Keyword ---------------------------------------------------------------- Application Notes kbappnote Bug info for a particular version of a product kbbuglist Sample code kbcode Documentation errors kbdocerr Error message followup information kberrmsg FastTip scripts or maps kbfasttip Binary file information located in the Microsoft Software Library kbfile Fixed bug info for a particular version of a product kbfixlist Articles listing product-specific keywords kbkeyword Sample macro with article kbmacro Problems not classified as bugs kbprb FastTip Technical Library Catalog kbtlc Troubleshooting information kbtshoot The following table lists formerly used keywords and their replacements. For explanations of what these keywords represent, see the tables above. Old keyword(s) New keyword ----------------------------------------------------------------- 3rdparty, isv, 3rd party kb3rdparty phoneref, diskdir kbref errmsg, err msg kberrmsg docerr, doc err kbdocerr buglist kbbuglist fixlist kbfixlist softlib kbfile tshoot kbtshoot appnote kbappnote fasttip, ivr kbfasttip tlc kbtlc MORE INFORMATION ================ Future querying tools may allow for use of friendly names for information categories. With current searching tools, "printing" cannot be used as a keyword because that word is also used in many articles whose main subject is not printing. Until our tools allow searching on keywords separately from article text, we need to create unique spellings for Knowledge Base keywords. Therefore, all standard Knowledge Base keywords will begin with the letters "kb." Additional reference words: kbkeyword key word kbcdg dskbguide KBCategory: kbref KBSubcategory: Personal Operating Systems Query Keywords for Knowledge Base Article ID: Q96132 ---------------------------------------------------------------- ----------- The information in this article applies to: - Microsoft MS-DOS operating system versions 3.x, 4.x, 5.x, 6.x - Microsoft Windows operating system versions 3.0, 3.0a, 3.1, 3.11 - Microsoft Windows for Workgroups versions 3.1, 3.11 - Microsoft Workgroup Connections version 1.0 - Microsoft Workgroup Add-On for MS-DOS, version 3.11 - Microsoft Windows Sound System versions 1.0, 1.0a, 2.0 - Microsoft Video for Windows, versions 1.0, 1.1, 1.1a ---------------------------------------------------------------- ----------- SUMMARY ======= You can use keywords to easily query for specific topics in the Microsoft Knowledge Base. This article contains keywords for Microsoft Windows, Windows for Workgroups, MS-DOS, Windows Sound System, and Video for Windows. By using these keywords, you can quickly access common topics. These keywords are commonly found at the bottom of articles in a section titled "Additional reference words." For a list of categories and keywords for all knowledge base articles see Q94671. MORE INFORMATION ================ Product Keywords ---------------- Keyword Topic -------------------------------------------------------------- bbsstepup Downloadable version of MS-DOS 6.2x Step-Up doswin Microsoft Windows & MS-DOS 5 for IBM PS/2 or Microsoft Windows & MS-DOS 5 Upgrade mmwin Microsoft Windows with Multimedia Extensions mnk Microsoft Natural Keyboard msdos Microsoft MS-DOS penwin Microsoft Pen Windows (Windows for Pen Computing) stepup MS-DOS 6.2x Step-Up vfw Video for Windows wc Workgroup Connections for MS-DOS win30 Windows version 3.0 and 3.0a win31 Windows version 3.1 and 3.11 wfw Windows for Workgroups 3.1 and 3.11 wfwg Windows for Workgroups (preferred) wgao Workgroup Add-On for MS-DOS wps Windows Printing System wss Windows Sound System MS-DOS Component Keywords ------------------------- Keyword Topic --------------------------------------------------------- ----- Dblguard MS-DOS DoubleGuard Dblspace MS-DOS DoubleSpace Drvspace MS-DOS DriveSpace Defrag Microsoft Defragmenter MSAV Microsoft Anti-Virus for MS-DOS MSBackup Microsoft Backup for MS-DOS Multi-Config MS-DOS multiple-configuration issues MWAV Microsoft Anti-Virus for Windows MWBackup Microsoft Backup for Windows Windows and Windows for Workgroups Component Keywords ----------------------------------------------------- Keyword Topic -------------------------------------------------------------- AWFax Microsoft At Work PC Fax GPF General Protection Fault RAS Remote Access Services UAE Unrecoverable application errors WinBoot Windows Startup issues WinComm Windows communications/serial WinDrvr Windows driver-related information WinMem Windows memory WinShell Windows Shell issues Recent KB Keyword Changes ------------------------- Old Keyword New Keyword ----------- ----------- winhwre kbhw winmm kbmm winnet kbnetwork winset kbsetup winprint kbprint winole kbole winapp kbtool KBCategory: kbkeyword kbref KBSubcategory: Additional reference words: 3.00 3.00a 3.10 3.11 6.00 6.20 6.21 6.22 key word troubleshooting 1.0 1.00 Exception Errors with EMM386.SYS / EMM386.EXE Article ID: Q52195 ---------------------------------------------------------------- ------ The information in this article applies to: - Microsoft MS-DOS operating system versions 4.x, 5.0, 6.0, 6.2, 6.21, 6.22 ---------------------------------------------------------------- ------ SYMPTOMS ======== If you install the EMM386.EXE device driver included with MS-DOS, you may get the following error message: EMM386 Exception error #13 @ xxxx:xxxxxxxx CODE xxxx PRESS ENTER TO REBOOT. CAUSE ===== The error means that the 80386 microprocessor has encountered a general protection violation. Because the EMM386 driver operates the 80386 chip in virtual real mode, the microprocessor checks for valid memory accesses. If a program tries to access memory that it is not allowed to access, the 80386 chip generates an exception fault error, which is detected by EMM386. In essence, EMM386 is reporting an error detected by the CPU in virtual mode. WORKAROUND ========== You should remove EMM386 to determine if problems still occur without it. If problems still occur, correct them and reinstall EMM386. MORE INFORMATION ================ The 12 hexadecimal digits following the error (represented by x in the above error message) are the address of the machine language instruction following the instruction that caused the exception error. This number is given in CS:EIP format, where CS is the code segment, and the EIP is the instruction pointer (relative to the code segment). This value indicates where in memory the CPU was executing instructions when the exception occurred. It is sometimes possible to determine from this value what software caused the exception to occur. This error should not occur on systems that are 100 percent IBM compatible. Because of the hardware-intensive nature of the EMM386 device driver, strict IBM hardware compatibility is required. If this error does occur on your system, the EMM386.SYS or EMM386.EXE device driver may need to be modified by your machine's manufacturer. The following is a list of Intel 80386 protected mode exception errors and their names: Code Meaning ---- ------- 0 Divide error 1 Debugger interrupt 2 Nonmaskable interrupt 3 Breakpoint 4 Overflow interrupt 5 Array boundary violation 6 Invalid opcode 7 Coprocessor not available 8 Double fault 9 Coprocessor segment overrun 10 Invalid task state segment 11 Segment not present 12 Stack exception 13 General protection violation 14 Page fault 16 Coprocessor error KBCategory: kbref kbhw kberrmsg kb3rdparty KBSubcategory: msdos gpf win31 win30 wfw wfwg Additional reference words: 6.22 4.0 4.00 4.0a 4.00a 4.01 4.01a 5.00 5.00a 6 6.0 6.00 6.20 3.0 3.1 GP WW0335: Memory Management with Windows 3.0 and 3.1 Article ID: Q66420 ---------------------------------------------------------------- ---- The information in this article applies to: - Microsoft Windows operating system versions 3.0, 3.0a, 3.1, 3.11 -------------------------------------------------------------------- Microsoft Product Support Services offers an Application Note that describes memory management with Microsoft Windows. This Application Note,"WW0335: Memory Management with Windows," examines the three types of memory that Windows versions 3.0 and 3.1 can use (conventional, extended, and expanded) and discusses how the three modes of Windows (real, standard, and enhanced) operate and use memory. You can obtain this Application Note from the following sources: - CompuServe, GEnie, and Microsoft OnLine - Microsoft Download Service (MSDL) - The Internet (Microsoft anonymous ftp server) - Microsoft Product Support Services For complete information, see the "To Obtain This Application Note" section at the end of this article. THE TEXT OF WW0335 ================== ================================================================ ====== Microsoft Product Support Services Application Note (Text File) WW0335: Memory Management with Windows ================================================================ ====== Revision Date: 4/92 No Disk Included The following information applies to Microsoft Windows version 3.1. ----------------------------------------------------------------- --- | INFORMATION PROVIDED IN THIS DOCUMENT AND ANY SOFTWARE THAT MAY | | ACCOMPANY THIS DOCUMENT (collectively referred to as an | | Application Note) IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY | | KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO | | THE IMPLIED WARRANTIES OF MERCHANTABILITY AND/OR FITNESS FOR A | | PARTICULAR PURPOSE. The user assumes the entire risk as to the | | accuracy and the use of this Application Note. This Application | | Note may be copied and distributed subject to the following | | conditions: 1) All text must be copied without modification and | | all pages must be included; 2) If software is included, all files | | on the disk(s) must be copied without modification [the MS-DOS(R) | | utility DISKCOPY is appropriate for this purpose]; 3) All | | components of this Application Note must be distributed together; | | and 4) This Application Note may not be distributed for profit. | | | | Copyright 1992 Microsoft Corporation. All Rights Reserved. | | Microsoft, MS-DOS, and the Microsoft logo are registered | | trademarks and Windows is a trademark of Microsoft Corporation. | ----------------------------------------------------------------- ---- INTRODUCTION ============ This application note outlines the memory management capabilities of Microsoft Windows versions 3.0 and 3.1. References that apply to both versions will refer to Microsoft Windows versions 3.x. Microsoft Windows versions 3.x provide a protected mode graphical operating environment that runs existing MS-DOS applications and allows Windows applications to break the 640K barrier. Windows 3.1 memory management is simpler in many ways than that of previous versions. However, the flexibility of Windows 3.1 memory management continues to present a challenge to those who want to understand its operation in depth. This document examines the three types of memory that Windows 3.x can use or provide (conventional, extended, and expanded) and discusses how both standard and 386 enhanced modes of Windows 3.1 operate and use memory. MEMORY TYPES ============ Three different kinds of memory can be installed in your machine: conventional, extended, and expanded memory. In addition, IBM- compatible machines contain a 384K upper memory area (UMA). Conventional Memory ------------------- Conventional memory is the first 640K of memory in your machine. MS- DOS has a limit of 1024K of addressable memory (conventional memory plus the UMA), and all MS-DOS applications must run within this conventional memory. All Windows 3.x operating modes share this limitation for running MS-DOS applications, but standard and 386 enhanced modes break the 640K limitation for running Windows applications. Windows 3.x enhanced mode can create multiple virtual MS- DOS machines (for more information on virtual MS-DOS machines, see the section of this application note called "386 Enhanced Mode and Conventional Memory." NOTE: 386 enhanced mode Windows 3.1 also allows MS-DOS applications to break the 640K barrier if they are written to use the Microsoft DOS Protected Mode Interface (DPMI) specification. DPMI allows MS- DOS applications to run in protected mode under Windows 3.1, using up to 16 megabytes (MB) of extended memory directly. Applications must be specifically written for DPMI in order to take advantage of this feature. 384K Upper Memory Area (UMA) ---------------------------- Between the top of conventional memory at 640K and the start of extended memory at 1024K lies the 384K UMA. This area does not contain physical memory. Mapped into the 384K UMA are the system BIOS (basic input/output system) ROM chips and the display adapter memory. When you install other accessory cards, such as network adapters, they may also occupy space within the 384K UMA. It is important to remember that the 384K UMA is always located in the same area of the IBM- compatible computer's address space: from 640K to 1024K (A000 to FFFF hexadecimal). There are no exceptions to this rule. This means that a standard IBM-compatible machine with 640K of conventional memory installed really has 1 MB of address space. The system memory occupies the first 640K, and the 384K UMA occupies the area from 640K to 1 MB (1024K). This does not mean that the machine has 1 MB of memory. A machine with 1 MB of physical memory has an address space of 1408K. This consists of the 640K of conventional memory, the 384K UMA, and the 384K of extended memory starting at 1024K. Extended Memory --------------- Extended memory is the simplest type of add-on memory to understand. It is also the type of memory used by Windows 3.x running in either standard or 386 enhanced operating mode. Extended memory is a seamless continuation of the original 1 MB address space on 80286 and 80386 computers. Extended memory always starts exactly at 1024K, where the 384K UMA ends. There are no exceptions. It is not possible for an 8086 or 8088 machine to have extended memory. This is a hardware limitation of the 8086/8088 processors, which can handle only 1024K of total address space (that is, 640K of system memory plus the 384K UMA). This is one reason why Windows 3.1 cannot run on 8086/8088-based machines, as it requires a minimum of 256K of extended memory (or 1024K for enhanced mode). The 80286 processor can address 16 MB of total memory, and the 80386 processor can address up to 4 gigabytes (GB). NOTE: PC manufacturers often refer to extended memory as expansion memory, which is not to be confused with expanded memory. Windows 3.x and all applications running under Windows 3.x access extended memory through the Microsoft Extended Memory Specification (XMS). Rather than accessing extended memory directly, access is made through an XMS driver. The driver supplied by Microsoft for this purpose is called HIMEM.SYS. Older MS-DOS applications that check available extended memory through interrupt 15, service 88H will not see any extended memory with an XMS driver loaded. Such applications must be rewritten to use the XMS, instead of interrupt 15, to access extended memory. Expanded Memory --------------- Versions of Windows prior to 3.0 used mostly expanded memory. Windows 3.x does not use expanded memory but may be able to provide it to MS- DOS applications. It is important to understand the concept of expanded memory if you still run MS-DOS applications that use it. There are two different kinds of expanded memory, differentiated by their Lotus/Intel/Microsoft (LIM) Expanded Memory Specification (EMS) version numbers. LIM 3.2 Expanded Memory ----------------------- We discussed earlier how PC/XT machines with 8086/8088 processors can address only 1024K of memory, of which only 640K can be used as RAM for MS-DOS and MS-DOS applications. You can't add more than 640K of conventional memory to the system, but you can provide more than 640K through a technique called bank switching. Expanded memory uses an empty area in the 384K UMA of the machine to provide this functionality. To use an expanded memory card, you must load a device driver to let the card know how to communicate with the PC. This device driver is called an expanded memory manager (EMM). A LIM 3.2 EMM establishes a 64K page frame within the 384K UMA to perform EMS bank switching. The 64K page frame consists of four contiguous 16K pages. LIM 3.2 expanded memory won't work without a 64K contiguous page frame. The page frame is the area where the EMM maps information into and out of the RAM of the expanded memory card. Information is not physically copied from the EMS card to the RAM of the computer; the device driver simply makes the page frame point to the data on the expanded memory card. The data then appears in the page frame, and your application can access it. LIM 4.0 Expanded Memory ----------------------- LIM 3.2 expanded memory is fine for storing data such as spreadsheets in expanded memory; however, because the LIM 3.2 specification does not allow programs to run in expanded memory, it is not useful for multitasking. There are two of major differences between LIM 3.2 and 4.0. First, with LIM 4.0 you can have many more than four 16K pages. LIM 4.0 supports up to 64 pages, which are enough to bank 1 MB of memory at once. Second, the page frame itself no longer must be four contiguous 16K pages. In fact, you need no page frame at all. Whichever EMS version you are dealing with, the basic operating principle of bank switching is still at work. Although LIM 4.0 is a standard that offers many advantages over LIM 3.2, few applications have yet been written to take advantage of LIM 4.0. Backfilling ----------- With LIM 4.0s limit of 64 16K pages, you have enough pages to bank switch the entire conventional address range of the processor. However, there must be no active ROM or RAM of any sort where you put an expanded memory page. Thus, you can't map EMS pages on top of anything that is already occupying address space in your machine (such as loaded MS-DOS or video/system ROM). On the 80286 processor, you should disable as much motherboard memory as possible (down to 256K) and let the expanded memory card supply that memory. This process is called backfilling. This doesn't mean that your computer will have only 256K--your programs still see a 640K machine. But because the expanded memory card is now supplying the memory, it can bank switch the memory. This capability is called "large page frame" EMS, and it allows programs to run executable code in expanded memory, a major improvement over LIM 3.2. The 80386 processor has a built-in ability to readdress any page of memory to any other location. This means you don't have to backfill on an 80386 to get large page frame LIM 4.0 functionality, nor do you need an expanded memory board. It's easy to convert your 80386s extended memory to expanded memory with an 80386 EMM such as Microsoft's EMM386.EXE. If you're using an expanded memory board on an 80386 machine, read your manual carefully before you backfill. Not all memory boards have the register support to supply more than four 16K pages (LIM 3.2). Though a memory driver may conform to the LIM 4.0 specification, that does not mean the hardware can provide more than four pages. Also, because Windows 3.1 supports extended memory directly, backfilling expanded memory will not give you any advantages, and the memory on the motherboard is often faster than memory on an expanded memory board. LIMulators ---------- Some programs, known as LIMulators, emulate expanded memory on 8088- and 80286-based machines using hard disk space and/or extended memory. These programs are not much of an advantage, because although they supply expanded memory, they are not hardware. They must locate a 64K EMS page frame in conventional memory and also take up space for the driver itself. LIMulators generally take close to 80K of conventional memory to run. Because conventional memory is the most precious memory on your machine, we do not recommend these types of programs. They are also typically extremely slow. On 80386 machines, it is possible to use a 386 expanded memory manager (such as EMM386 or Quarterdeck's QEMM) to emulate expanded memory. These LIMulators use the XMS rather than interrupt 15 memory to emulate expanded memory and are much more efficient than other types of LIMulators. Expanded Memory Difficulties ---------------------------- LIM 3.2 expanded memory requires a page frame to work, and the page frame is located within the 384K UMA of your machine. Unfortunately, your EMM is not the only competitor for that memory space. Add-on boards, such as network cards; 3270 emulation cards; RLL, SCSI, and ESDI disk controllers; and even high-resolution video cards, can contend for this address space. Several potential difficulties can arise due to this contention: 1. LACK OF SPACE. The major problem is simply finding at least 64K of contiguous free space in which to locate the LIM 3.2 page frame. LIM 4.0 does not require a 64K page frame but is almost useless without it, as very few applications have been written to take advantage of the LIM 4.0 specification. Frequently, the address areas of various adapter cards need to be shuffled to open a contiguous 64K page frame. Complicating this process are boards such as the IBM 3270, which have nonmovable addresses in most machines. 2. MAPPING CONFLICTS. Most 386 EMMs (such as EMM386.EXE and Windows 3.1 386 enhanced mode) use a search algorithm to find unused memory addresses between C000 and DFFF located in the 384K UMA to use as page frames. Some cards (adapters) do not reserve their address space until you access the card, so the memory manager can inadvertently map EMS pages on top of an address the card will request. This is often true of Token Ring network adapters and can cause hanging and intermittent operation. In case of problems, the first thing to do is disable expanded memory. This procedure will determine whether a page conflict is causing your difficulty. If the problem goes away without expanded memory, the memory manager must be told to exclude the address the adapter is occupying from consideration as a page location. Consult your memory managers documentation for information on how to exclude an address range. The adapter may also have to be moved; you do this in different ways with different memory managers. WINDOWS 3.X MODES AND MEMORY USAGE: HOW EACH MODE WORKS ======================================================= This section examines how standard and 386 enhanced mode Windows 3.x use the different types of memory we have discussed (conventional memory, the 384K UMA, extended memory, and expanded memory). NOTE: Real mode is not available in Windows 3.1. Real mode for Windows 3.0 was supplied mainly for compatibility with older Windows 2.x applications. Most, if not all, of these older applications have now been updated to work properly with Windows 3.x. Valuable development time was saved in not maintaining this outdated mode, time that was then spent improving the two remaining Windows modes. STANDARD MODE WINDOWS 3.1: BREAKING THE 640K BARRIER ON 286 MACHINES ================================================================= === Standard Mode and Conventional Memory ------------------------------------- When standard mode Windows 3.1 is started, it adds the amount of free conventional and extended memory and looks at the total amount as one contiguous block of memory. Conventional memory has no special meaning under standard mode, except when running MS-DOS applications. While standard mode Windows 3.1 has MS-DOS application sup-port, the MS-DOS application(s) must run within conventional memory. Standard Mode and the 384K Upper Memory Area (UMA) -------------------------------------------------- In standard mode, Windows 3.x does not directly access the 384K UMA. Still, if a physical expanded memory board is present (or if a 386 memory manager is providing expanded memory under Windows 3.1), the EMM will use areas of the 384K UMA in order to provide a LIM 3.2 page frame. If you suspect a 384K UMA conflict is causing a problem, temporarily remove the external EMM for testing. Standard Mode and Expanded Memory --------------------------------- Standard mode Windows 3.1 does not use expanded memory. MS-DOS applications running under standard mode can access expanded memory only if a physical expanded memory board, along with the appropriate memory manager, is present in the machine. Compatible 386 EMMs such as EMM386.EXE can be loaded to provide expanded memory outside Windows. However, 386 EMMs cannot be used to provide expanded memory to MS-DOS applications running in standard mode Windows. If possible, the 386 EMM will be disabled when standard mode loads. For more information on using expanded memory with standard mode see the "Expanded Memory for MS-DOS Applications" section of this application note. Standard Mode and Extended Memory --------------------------------- Windows 3.x standard mode can access extended memory directly. It adds free conventional memory and free extended memory. It then provides the total as memory for Windows applications to use (minus the memory required by standard mode Windows itself). Standard mode accesses extended memory through the XMS driver HIMEM.SYS. MS-DOS applications that use extended memory can also be run from standard mode Windows. 386 ENHANCED MODE WINDOWS 3.X: ENTERING THE WORLD OF VIRTUAL MEMORY ================================================================= == 386 Enhanced Mode and Conventional Memory ----------------------------------------- Windows 386 enhanced mode deals with conventional memory in much the same way that standard mode does. When 386 enhanced mode Windows 3.1 is started, it adds the amount of free conventional and extended memory; in addition, Windows 3.1 can use hard disk space as virtual memory (the "swap" file) and look at the total amount as one contiguous block of memory. Conventional memory has no special meaning under 386 enhanced mode, except when running MS-DOS applications. In 386 enhanced mode, MS-DOS applications run by creating virtual MS-DOS machines with up to 640K of free memory. Each virtual MS-DOS machine inherits the environment that was present before Windows 386 enhanced mode was started. This means that every driver and terminate-and-stay-resident (TSR) program loaded before you run Windows, as well as the environment, is present and consumes memory in every subsequent virtual MS-DOS machine. The net memory available within virtual MS-DOS machines under 386 enhanced mode is slightly less than the free memory at the MS-DOS prompt before you start Windows, due to the overhead of creating and managing a virtual machine. 386 Enhanced Mode and the 384K Upper Memory Area (UMA) ------------------------------------------------------ Windows versions prior to 3.0 used the 384K UMA only to place the expanded memory page frame, and then to a maximum of only four 16K pages. Windows 386 enhanced mode uses the 384K UMA for two purposes: 1. To place MS-DOS protected mode application programming interface (API) translation buffers. 2. To place the LIM 3.2 expanded memory page frame (if required). As noted earlier, there may be adapters, such as network cards, trying to use the 384K UMA as well. Frequently, all the free pages in this area are used by 386 enhanced mode. API Translation Buffers in the 384K Upper Memory Area (UMA) ----------------------------------------------------------- Although Windows 3.1 386 enhanced mode breaks the 640K barrier for Windows applications, it still runs on top of MS-DOS. The copy of MS- DOS upon which Windows is running can execute and access data only within conventional memory. The same restriction applies to network software or other drivers loaded before 386 enhanced mode Windows. 386 enhanced mode allocates buffers in the 384K UMA to translate MS-DOS and network API calls from protected mode to real mode. Since the 384K UMA is within the first megabyte of address space, it can be accessed by MS-DOS in real mode. The translation buffers are used as a window through which applications running in protected mode can pass information to and from MS-DOS and the network drivers. Ideally, there would be enough free space in the 384K UMA to place both the translation buffers and the expanded memory page frame. Yet on many configurations there isnt enough room, and on those systems you have to make a choice. Either the expanded memory page frame can be eliminated, or the translation buffers can be allocated in conventional memory instead of in the 384K UMA. If the translation buffers are allocated in conventional memory, they take up space in every virtual machine that you create from Windows, and you will have less space in which to run MS-DOS applications. The translation buffers can be allocated either in the 384K UMA or in conventional memory, but never half and half. Fortunately, Windows 386 enhanced mode provides a method for specifying your preference. To do this, place the following setting in the [386enh] section of the SYSTEM.IN file: ReservePageFrame=Boolean If ReservePageFrame=true (the default), 386 enhanced mode Windows allocates the page frame first and the translation buffers second. This makes it likely that the translation buffers will be forced into conventional memory, but allows you to use expanded memory in MS-DOS applications. If ReservePageFrame=false, the translation buffers are allocated first and the page frame second if there is still room. The ReservePageFrame=false provides the most free memory within virtual machines, although some MS-DOS applications may not be able to use expanded memory. Remember, however, that Windows applications do not need expanded memory to function; only MS-DOS applications that can use expanded memory will be affected. NOTE: If you are using the EMM386.EXE driver, translation buffers are always placed in conventional memory. Page Frame Placement in the 384K Upper Memory Area (UMA) -------------------------------------------------------- As noted in the expanded memory discussion earlier in this application note, expanded memory support requires a page frame located in the 384K UMA. With LIM 4.0 expanded memory, it is not necessary to have a 64K contiguous page frame in this area. In fact, it's not necessary to have a page frame at all in LIM 4.0. Still, if you want to use expanded memory in your MS-DOS applications, you must have a 64K contiguous page frame (composed of four contiguous 16K pages in the 384K UMA) because most applications are written to take advantage of LIM 3.2 expanded memory. On a typical IBM-compatible machine there are only 12 free 16K pages in the 384K UMA, and on some machines (such as IBM PS/2s) there are only 8. Four contiguous pages are required for expanded memory support in MS-DOS applications, leaving only eight other free pages. Other items such as network adapters and many hard disk controllers, also need to occupy pages in the 384K UMA. Frequently, the combination of installed adapters can break up the free area in the 384K UMA so there is no 64K contiguous area in which to place the page frame. In this case, you will not see any free expanded memory in your MS-DOS applications. If you experience this problem, you may need to rearrange your adapter memory locations to get expanded memory support for MS-DOS applications. This is easiest to do on machines using the Micro Channel Architecture (MCA) or Extended Industry Standard Architecture (EISA) bus standards. IBM PS/2 models 50 and above are equipped with the MCA bus. PS/2 machines allow you to change adapter memory locations simply by restarting with the PS/2 Reference Disk and choosing Change Configuration. A similar procedure is available on most EISA bus machines, such as the COMPAQ SYSTEMPRO and the HP Vectra 486. Normal Industry Standard Architecture (ISA) bus machines such as the IBM PC/AT and COMPAQ 386 may require you to open the case and flip DIP switches or move jumpers on the cards to change memory addresses; check your hardware manual for more information on changing memory addresses. You can entirely disable expanded memory support under Windows 386 enhanced mode by adding the NoEMMDriver=yes setting to the [386enh] section of the SYSTEM.INI file. Controlling 386 Enhanced Mode 384K Upper Memory Area (UMA) Mapping ----------------------------------------------------------------- - In versions of Windows prior to 3.0, the WIN.INI file settings EMMExclude= and EMMInclude= were used to control expanded memory page frame placement. These settings are used under Windows 386 enhanced mode to control not only the expanded memory page frame but also the API translation buffer mapping. Under Windows 3.x these settings begin with the letters "EMM" only for compatibility reasons; they no longer apply only to expanded memory. The EMMPageFrame= setting, however, still applies only to the expanded memory page frame. In Windows 3.x these three settings have been moved from the WIN.INI file to the [386enh] section of the SYSTEM.INI file. Earlier versions of Windows (2.x) do not use the E000-EFFF range of the 384K UMA unless specifically instructed to do so. Windows 386 enhanced mode will use this segment unless the machine identifies itself as a PS/2. To explicitly exclude an area of the 384K UMA from mapping by Windows 386 enhanced mode, use the EMMExclude= setting. The EMMExclude= setting accepts a four-digit hexadecimal memory range, such as EMMExclude=E000-EFFF. Since there is no standard for hardware implementation of the E000-EFFF area, it is frequently necessary to exclude this range in order for 386 enhanced mode to function properly. Most adapter cards are automatically detected and excluded by Windows 386 enhanced mode. If you suspect a problem with a 384K UMA memory conflict, use the EMMExclude= setting. NOTE: If you suspect that your machine has multiple adapter mapping conflicts, it may be useful to exclude the entire UMA (A000-EFFF) for testing purposes. There are very few uses for the EMMInclude= setting. Normally Windows 3.1 386 enhanced mode automatically uses all free pages in the 384K UMA. Likewise, there are few uses for the EMMPageFrame= setting because it controls only the expanded memory page frame and not the translation buffers. 386 Enhanced Mode and Expanded Memory ------------------------------------- Windows 386 enhanced mode does not use expanded memory itself. It can, however, create expanded memory for use by MS-DOS applications written to use expanded memory, such as Lotus 1-2-3 versions 2.x. Expanded memory required by an MS-DOS application can be specified in the applications program information file (PIF). It is no longer necessary for Windows applications to use expanded memory because they can now access extended memory directly. Thus, the main issues for expanded memory under Windows 3.1 are page frame conflicts, as discussed above. Windows 386 enhanced mode provides large page frame LIM 4.0 expanded memory in all virtual MS-DOS machines. Although this feature is not currently useful for most MS-DOS applications that use expanded memory- -they use only the LIM 3.2 64K page frame itself, not the additional bankable pages in conventional memory that large page frame LIM 4.0 supplies--it may be useful in the future. A compatible external 386 memory manager such as EMM386.EXE can be loaded to provide expanded memory for MS-DOS applications running outside Windows 386 enhanced mode. Such a memory manager is not needed for expanded memory to be available inside Windows 3.x, and is actually turned off when Windows 386 enhanced mode is run. See the "Expanded Memory for MS-DOS Applications" section of this application note for more information. 386 Enhanced Mode and Extended Memory ------------------------------------- Like standard mode, Windows 386 enhanced mode can directly access extended memory. It adds free conventional memory and free extended memory plus virtual hard drive memory (the "swap" file). It then provides the total as memory for Windows applications to use (minus the memory required by 386 enhanced mode Windows itself). MS-DOS applications that use extended memory can also access extended memory in virtual machines under 386 enhanced mode Windows. The extended memory supplied to MS-DOS applications by Windows 3.1 386 enhanced mode can be virtualized. Running Protected Mode MS-DOS Applications ------------------------------------------ Windows 386 enhanced mode allows MS-DOS applications to run in protected mode if they are written to use the DPMI specification. Windows 386 enhanced mode uses the XMS driver to load itself and its drivers into extended memory before starting up. This is why 386 enhanced mode requires the presence of HIMEM.SYS or another compatible XMS device driver. 386 Enhanced Mode and Virtual Memory: A Virtual Memory Conceptual Analysis ------------------------------------- Virtual memory allows you to simultaneously run more programs than the amount of physical memory installed on your computer would normally allow. Virtual memory has been widely used for years in the world of mainframe computers. Windows 386 enhanced mode offers virtual memory to the PC-compatible world by using the special demand paging capabilities of the Intel 80386 processor. All Windows programs can take advantage of virtual memory in Windows 386 enhanced mode. When you start Windows 386 enhanced mode, choose About Program Manager from the Help menu. You will see that much more memory is available than is installed on your machine. Windows applications can use this extra memory without being written specially for it because Windows applications are device independent; they let Windows handle the memory management and simply ask Windows for memory allocations. With virtual memory, Windows applications keep asking for more memory, which Windows 386 enhanced mode is now able to deliver. If you have less physical memory and are forced to rely on virtual memory, the application runs more slowly; if you have more physical memory, it runs more quickly--in either case, it is almost always able to run. While a program is running in virtual memory, at any given moment some parts of its code and data are in physical memory while the rest of the program is swapped to the hard disk. When a reference is made to a memory address, if the information is in physical memory, the information is used without program interruption. However, if the desired information is not in physical memory, a page fault occurs, and the Windows 386 enhanced mode virtual memory manager (VMM) takes control. The required code or data is pulled into physical memory from the hard disk, and if necessary, some other information is swapped out. Pages are swapped out on a least recently used (LRU) basis. The pages that have not been accessed for the longest time are the first to be swapped out. All this swapping is invisible to the user, who sees only a little hard disk activity. Windows 386 enhanced mode virtual memory brings pages of data into physical memory when they are referenced: this is called a demand- paged system. This system does not attempt to predict which pages will be required in the future. The 386 enhanced mode virtual memory subsystem is implemented by the Windows 3.x VMM and the page swap device. The VMM maintains the virtual memory page table; it lists which pages are currently in physical memory and which are swapped to disk. Because Windows 386 enhanced mode is a multitasking environment, the VMM page table also contains a list of which memory pages belong to which process. When the VMM needs a page that is not currently in physical memory, it calls the page swap device. The page swap device allocates and deallocates virtual memory and maps pages into and out of physical memory. Some virtual memory systems rely on program segmentation to do their work. Windows applications are segmented; however, virtual memory under Windows 386 enhanced mode is not related to the segmentation of Windows applications. All memory, virtual and physical, is divided into 4K pages, and the system is managed on this basis. Page mapping starts at zero K and works up. Two kinds of pages can be allocated: physical pages and virtual pages. The number of physical pages is simply the amount of physical memory in the machine divided by 4K. In contrast, memory allocated to an application is made up of virtual pages. At any given time, a virtual page can be in physical memory or swapped to the hard disk. As mentioned earlier, Windows 386 enhanced mode virtual memory management uses the LRU page-replacement algorithm. The virtual page table contains flags for each page that indicate whether the page has been "accessed" and if the page is "dirty." Accessed means that a process made a reference to the page after it was originally loaded. Dirty means that a write was made to the page after it was loaded. Because a memory write qualifies as an access, the dirty attribute implies the accessed attribute. To illustrate, assume Windows 386 enhanced mode is out of physical memory space. A process requests additional memory. Windows has to decide which pages currently in physical memory it should swap to disk to fulfill the request. This decision is a three-step process: 1. The VMM scans the page table, looking for pages that have neither an accessed nor a dirty attribute. During the scanning process, the VMM clears the accessed attribute from all the pages. 2. If the VMM can find enough pages meeting the not accessed/not dirty requirement, it fulfills the request. It swaps the pages to disk and gives the resulting free memory to the process. 3. If the VMM can't find enough pages the first time through, it repeats the scan. However, this time through, none of the pages has an accessed attribute, because it was cleared by the first scan. Theoretically, therefore, more pages will meet the requirements, and the request can be fulfilled. If the required pages are still not found by the second scan, Windows then swaps out the pages regardless of their attributes. The benefit of Windows 386 enhanced mode virtual memory support is the ability to run more programs than can be supported by actual physical memory. The drawbacks are the disk space requirement for the virtual memory swap file and a decrease in overall execution speed when swapping is required. However, it's better to be able to run a program slowly in a virtual memory system than not to be able to run it at all. Virtual Memory Paging File Options and Controls ----------------------------------------------- Windows 386 enhanced mode can use one of two types of virtual memory paging files, or swap files: temporary or permanent. Only one type of swap file can be used at a time when running Windows 3.1. Do not attempt to create a swap file on a RAM disk; this is a self-defeating pursuit--you would be sacrificing physical memory to provide a place to create virtual memory to replace the physical memory you have used to create the RAM disk. Windows 3.0 in 386 enhanced mode requires a minimum of approximately 1.5 MB of hard disk space free on the paging drive to provide virtual memory support with a temporary swap file. With Windows 3.1, that number is down to 512K. A temporary swap file is simply a normal MS-DOS file created on the hard disk that can shrink and grow in size as necessary. The temporary swap file is called WIN386.SWP, and it is created automatically when Windows 3.x is started. The swap file does not have a hidden or system attribute and can be deleted, if necessary, any time you are not running Windows, although it is normally deleted automatically when you exit Windows 386 enhanced mode. Temporary swap file location and size can be adjusted by inserting parameters in the [386enh] section of the SYSTEM.INI file. In Windows 3.0, the temporary swap file is always created in your Windows 3.0 directory unless you set the PagingDrive= setting. If the PagingDrive= setting is set (for example, PagingDrive=D:), the swap file will be created in the root directory of the specified drive. There is no way to specify a subdirectory for the temporary swap file location in Windows 3.0. In Windows 3.1, the drive and subdirectory of the temporary swap file may be specified with the PagingFile= setting. Temporary swap file size is controlled by the MaxPagingFileSize= setting. The size of the temporary swap file can also be limited in a different way by the use of the MinUserDiskSpace= setting, which tells 386 enhanced mode to leave the specified amount of disk space in kilobytes free when creating a temporary swap file. A permanent swap file occupies a contiguous section of your hard disk. Using a permanent swap file improves the speed of the Windows 3.x virtual memory system because there are fewer processor mode transitions and the swap file's access requires less overhead than a normal MS-DOS file. The permanent swap file is a hidden file called 386SPART.PAR, which also has a system attribute; the file is always placed in the root directory of the specified drive. Since the permanent swap file must be contiguous, you can't create one larger than the largest contiguous free segment of your hard disk. Permanent swap files are created and deleted by running SWAPFILE.EXE in Windows 3.0 real mode, or from the Windows 3.1 Control Panel by choosing the 386 Enhanced icon and then choosing the Virtual Memory button. A SYSTEM.INI file setting is not used to point to the location of the permanent swap file. Instead, when the permanent swap file is created, Windows creates a file called SPART.PAR in your Windows 3.x directory. Windows 386 enhanced mode reads the SPART.PAR file to find out where the permanent swap file is and how large it is. SPART.PAR is marked read-only to keep you from accidentally deleting it. If you delete SPART.PAR, Windows will not know about the permanent swap file and won't be able to make use of it. Because SWAPFILE.EXE and the Virtual Memory utility both read SPART.PAR, they cannot be used to delete the permanent swap file if SPART.PAR is deleted. If Control Panel (or SWAPFILE.EXE with Windows 3.0) says that the maximum swap file size it can create is smaller than your free disk space, your hard disk is fragmented. If you want to create a larger permanent swap file than Control Panel (or SWAPFILE.EXE) reports possible, you must optimize your hard disk (optimizing is also known as unfragmenting, or compacting). Optimizing must be done with a third-party utility program such as Bridgeway Publishing FastTrax, Norton Utilities, Mace Utilities, Golden Bow VOpt, or Central Point PC Tools. It is important to run these programs outside the Microsoft Windows environment. If you have already created a permanent swap file, make sure you delete it using Control Panel before optimizing your hard disk. It is not necessary to delete the permanent swap file every time you optimize your hard disk--only when you want to increase the size of the permanent swap file by optimizing, then re-creating it. The Virtual Memory utility supports only disks that use 512-byte sectors for the swap file. If 512-byte sectors are not being used, this indicates a non-standard configuration such as a third-party disk partitioning driver. The Virtual Memory utility (and Windows 3.x itself) supports drives with 512-byte sectors that have been partitioned with the MS-DOS fdisk command. (NOTE: Certain OEM versions of MS-DOS have altered versions of fdisk that will partition drives using sector sizes other than 512 bytes.) Never run the Virtual Memory utility on a drive that uses a partitioning driver in the CONFIG.SYS file, with the exception of Compaqs ENHDISK.SYS. If you receive a message that your swap file is corrupted, use Control Panel (or SWAPFILE.EXE in Windows 3.0) to delete the corrupted swap file and create a new one. Paging to Network Drives ------------------------ Paging to a network drive, while certainly possible, is extremely slow and is not recommended. Only temporary swap files can be used on network drives. If you want to page to a network drive, the directory must not have an MS-DOS read-only attribute; you must have create and write access to the directory. NOTE: Because the root of a Novell network drive is the root of the server, it is not MSNet-Redirector compatible. Do not set the PagingDrive= setting to a Novell network drive. If you do so and multiple users run Windows 3.1 386 enhanced mode, their computers will hang because they will overwrite each others swap files, all with the same name and all created in the root directory of the server. WIN.COM AUTOMATIC STARTUP PARAMETERS ==================================== WIN.COM starts up automatically in the appropriate operating mode for your machine and the amount of memory installed. Operating modes are real mode (similar to Windows/286 2.x), which is only available in Windows 3.0; 286 standard mode (also known as 286 protected mode); and 386 enhanced mode (also known as 386 protected mode). However, Windows may be forced into any of the modes through the following command-line switches (provided the mode is supported by your hardware): Command Line Mode ----------------------------------------------- win /r Real (Windows 3.0 only) win /s or win /2 Standard win /3 386 enhanced Real Mode Requirements ---------------------- The requirements for WIN.COM to automatically start up in real mode are the following: - Windows 3.0 - 8088 processor or above - 384K of free conventional memory (393,216 bytes reported by chkdsk)Standard Mode Requirements The requirements for WIN.COM to automatically start up in standard mode are the following: - 80286 processor or above - 192K of free extended memory - XMS driver loaded (HIMEM.SYS) Practical Standard Mode Requirements ------------------------------------ Standard mode conventional/extended memory requirements are mutually dependent and are not fixed. A typical installation requires a minimum of 128K of memory free at the MS-DOS prompt to run standard mode, assuming sufficient extended memory is free. Standard mode requires between 384K and 512K of combined conventional and extended memory to run (approximately). For example, if only the minimum 192K of extended memory is free, approximately 322K of conventional memory is required to run standard mode. However, if available extended memory is increased to approximately 208K or greater, only 128K of conventional memory is required. 386 Enhanced Mode Requirements ------------------------------ The requirements for WIN.COM to automatically start up in 386 enhanced mode are the following: - 80386 processor or above - 1024K of free extended memory - XMS driver loaded (HIMEM.SYS) Practical 386 Enhanced Mode Requirements ---------------------------------------- See the above notes for standard mode regarding the interrelationship of conventional and extended memory requirements. A typical installation requires a minimum of 182K of memory free at the MS-DOS prompt to run 386 enhanced mode, assuming sufficient extended memory is free. Windows 386 enhanced mode requires between 580K and 624K combined conventional and extended memory to run (approximately). NOTE: 386 enhanced mode can start up in low memory situations because it provides virtual memory support; however, it may be extremely slow due to the large amount of disk swapping it must perform. All numbers are approximate and may vary widely depending on the configuration (for example, Windows device drivers chosen, MS-DOS version, display adapter, and so on). 128K of extended memory is recovered from shadow RAM usage on COMPAQ 386 machines. Memory requirements take into account memory that can be recovered from SMARTDrive (down to the minimum cache size specified). THE FREE SYSTEM RESOURCES PERCENTAGE ==================================== The Program Manager and File Manager About boxes in the Help menus of Windows 3.1's standard and 386 enhanced modes give percentage figures for free system resources and free memory. In Windows 3.0, these figures can be obtained from the About box of the Program Manager Help menu. To understand what the free system resources percentage means, you must understand some of the anatomy of Windows's internal structure. The part of Windows that runs Windows applications is made up of three main segments called KERNEL, GDI (graphics device interface), and USER. KERNEL loads and runs Windows applications and handles their memory management. GDI manages graphics and printing. USER controls user input and output, including the keyboard, mouse, sound driver, timer, and communications ports. These three segments exist as separate .EXE files and are located in the WINDOWS\SYSTEM subdirectory. GDI has a storage area limited to 64K, which is known as a local heap. Currently, USER has two such areas, hence 128K storage. The free system resources percentage reflects the remaining free percentage of USER or GDI local heap space, whichever is lower. Although Windows 3.1 allows you to run a much larger number of simultaneous Windows applications than any previous Windows version, like Windows 3.0, it is not without limitations. If you receive an "Out of memory" error and the Help About box shows a large amount of free memory, look at the free system resources percentage. Chances are you are low on system resources. Every window and icon that is created requires USER local heap space. It is theoretically possible to exhaust the system resources with only one application, such as Program Manager, if enough objects are created by the application. Another important aspect of Windows application memory management that is not included in the free system resources percentage is the number of selectors. A selector is a memory pointer that is consumed with each memory allocation made by a Windows application. Windows 3.1 has a fixed number of selectors (4096 in standard mode, 8192 in 386 enhanced mode). If a Windows application allocates a very large number of small data objects, it is possible to run out of selectors. This will also produce an "Out of memory" error message. Writing a Windows application to handle its own data objects more efficiently can help in this situation. If you experience a chronic problem with a particular application while few or no other applications are loaded, contact the application vendor. It is important that the vendor become aware of the problem so it can be corrected if possible. Writing an application to handle data objects more efficiently can help reduce "Out of memory" conditions. 386 ENHANCED MODE PERFORMANCE TIPS: GETTING THE MOST FROM YOUR MACHINE ================================================================= ===== The following suggestions should assist you in maximizing the performance of your Windows 386 enhanced mode installation. Many of these suggestions apply to standard and real modes as well. 1. USE SMARTDRIVE. The Microsoft SMARTDrive disk caching driver can produce the largest single Windows 3.1 performance improvement. Use SMARTDrive whenever possible. For basic information on SMARTDrive installation and operation, refer to the "Microsoft Windows Users Guide" version 3.1 manual. 2. KEEP YOUR HARD DISK OPTIMIZED. A fragmented hard disk greatly impacts Windows's performance, especially when a temporary swap file and/or SMARTDrive is installed. Use a hard disk optimizer program on a weekly basis to keep your disk contiguous. 3. CREATE A PERMANENT SWAP FILE. Using a permanent swap file improves performance over using a temporary one. Under Windows 3.1, if supported by your hardware, also select the Use 32-Bit Disk Access check box in Control Panel by choosing the 386 Enhanced icon, choosing the Virtual Memory button, then choosing the Change button. See "386 Enhanced Mode and Virtual Memory" section of this application note for more information on permanent swap file allocation. 4. TURN OFF GRAPHICS PORT TRAPPING. The speed of MS-DOS applications running under 386 enhanced mode can be noticeably improved by not selecting any of the Monitor Ports options in the Advanced section of the PIF Editor. The High Graphics option provides the widest range of MS-DOS application compatibility but is not required for most applications. 5. TURN OFF THE FILESYSCHANGE= SETTING. Windows 3.1 386 enhanced mode can monitor disk access by MS-DOS applications and send directory update messages to File Manager. This allows File Manager to be automatically updated by changes MS-DOS applications have made to files or directories. However, this option is not a necessity, and leaving it off (the default) speeds file access by MS-DOS applications. To disable this feature, set FileSysChange=no in the [386enh] section of the SYSTEM.INI file. 6. TURN OFF THE RESERVEPAGEFRAME= SETTING. Turn this setting off if you do not require expanded memory support for MS-DOS applications. Turning this option off ensures that you're getting the most possible memory in virtual MS-DOS machines. To disable this feature, set ReservePageFrame=no in the [386enh] section of the SYSTEM.INI file. 7. USE THE RIGHT NUMBER OF MS-DOS BUFFERS. If you are using SMARTDrive, set the number of MS-DOS disk access buffers in your CONFIG.SYS file to 15 (that is, BUFFERS=15). Using a greater number of buffers with SMARTDrive will actually decrease efficiency. If you are not using SMARTDrive, use BUFFERS=30. 8. USE THE LOWEST COMMON DISPLAY DRIVER. Using a display driver with a high resolution or large number of colors results in slower display performance. If you do not require the extra features of the display driver, use a driver with less capability. Usually this suggestion applies to display systems that are VGA compatible but offer an extended mode driver, such as the Video Seven or 8514. Using the standard VGA driver instead offers faster display performance but less resolution and/or color support. 9. USE THE PROPER HARD DISK INTERLEAVE. Frequently, a hard disk is formatted with the wrong interleave at the dealer or factory. You can use a program such as Gibson Research's SpinRite or Central Point's DiskFix to verify that you are using the proper interleave. Some programs can correct your interleave without reformatting the hard disk. 10. ENABLE 32-BIT DISK ACCESS. 32-Bit Disk Access is a method for accessing the hard disk with fewer changes in the processor mode. Windows can do this by using a device driver that traps interrupt 13 calls and handles them itself. To take advantage of this feature of Windows 3.1, you need to have a Western Digital WD-1003 or compatible hard disk controller. NOTE: To enable 32-Bit Disk Access in Windows 3.1, choose the 386 Enhanced icon in Control Panel. Choose the Virtual Memory button, then choose the Change button and create a permanent swap file. When you do this, select the 32-Bit Disk Access check box. EXPANDED MEMORY FOR MS-DOS APPLICATIONS ======================================= Under Real Mode Windows 3.0 --------------------------- Real mode Windows 3.0 and MS-DOS applications can both use the same external expanded memory manager (EMM). Expanded memory can be provided either by a physical expanded memory board, or by a 386 EMM. Common expanded memory boards include the AST RAMpage! and Intel Above Board. Common 386 EMMs include Microsoft's EMM386.SYS (included with Windows), Compaq's CEMM.EXE (included with COMPAQ 386 machines), Qualitas's 386 to the Max (386MAX.SYS), and Quarterdeck's QEMM.SYS. If a physical expanded memory board is used, you will get the best performance from real mode Windows by backfilling to provide large page frame LIM 4.0 support. Some boards do not have the hardware register support to provide large page frame LIM 4.0--only small page frame (see "Expanded Memory" section of this application note). All 386 EMMs provide large page frame LIM 4.0 support. Remember that MS-DOS applications require LIM 3.2 (a 64K contiguous page frame) to use expanded memory, but real mode Windows requires LIM 4.0 (does not require a 64K contiguous page frame). If you see expanded memory in Windows but not in your MS-DOS applications, you probably do not have a 64K contiguous page frame (LIM 3.2), and you may need to rearrange adapter locations. For more information, see "Expanded Memory" section of this application note. Under Standard Mode Windows 3.x ------------------------------- As noted in the "Standard Mode and Conventional Memory" section of this application note, Windows 3.x standard mode does not use expanded memory. MS-DOS applications running under standard mode can use expanded memory only with a physical expanded memory board such as an AST RAMpage! or Intel Above Board. You cannot use 386 EMMs to provide expanded memory support for MS-DOS applications running under standard mode. Still, 386-compatible EMMs can be loaded to provide MS-DOS- application expanded memory support outside standard mode in Windows 3.1. Such EMMs cannot be used in conjunction with standard mode Windows 3.0. Under 386 Enhanced Mode Windows 3.x ----------------------------------- Expanded memory emulation is provided internally for MS-DOS applications running under 386 enhanced mode. The only requirement is the presence of a 64K contiguous page frame for LIM 3.2 compatibility. For more information on page frame placement, see the "386 Enhanced Mode and the 384K Upper Memory Area (UMA)" section of this application note. Expanded memory for MS-DOS applications can be allocated and/or limited through PIF settings. External 386 Expanded Memory Managers ------------------------------------- Some 386 EMMs have a special feature that allows standard or 386 enhanced mode Windows to turn them off when Windows is run. Memory managers with this capability are EMM386.EXE and CEMM.EXE. Windows can turn off EMM386.EXE even if expanded memory is in use at the time. CEMM.EXE requires that no expanded memory be in use when standard or 386 enhanced mode Windows is run. Some 386 EMMs provide the capability of loading MS-DOS device drivers into free areas of the 384K UMA. CEMM.EXE does not provide this capability, but the combination of MS-DOS 5.0 and EMM386.EXE, or 386MAX.SYS and QEMM386.SYS does. DPMI AND VCPI ============= Specifications for Different Purposes ------------------------------------- The MS-DOS Protected Mode Interface (DPMI) was developed by a group of industry leaders including Borland, Eclipse, IBM, IGC, Intel, Locus, Lotus, Microsoft, Phar Lap, Quarterdeck, and Rational Systems. Several members of the DPMI committee were also involved in the creation of the Virtual Control Program Interface (VCPI). DPMI is primarily a creation of Microsoft, and VCPI was formulated primarily by Phar Lap Software. MS-DOS Extended Applications ---------------------------- MS-DOS extended applications execute code in the protected mode of the 80286 or 80386 processor. Unlike OS/2 applications, MS-DOS extended applications are launched from standard MS-DOS. Creating an MS-DOS extended application requires a method to switch the processor to protected mode and to allocate extended memory. Until DPMI, there was no standard method for MS-DOS extended applications to perform these tasks and multitask memory with other applications on 80286 processors. Hundreds of existing applications have been created using various types of MS-DOS extenders. OS/2 extender applications that do not already support DPMI will require minor modifications to do so. Comparing VCPI to DPMI ---------------------- VCPI and DPMI solve two different problems. VCPI provides an interface between applications using MS-DOS extenders on an 80386 machine and 386 EMMs. For example, the 386 EMMs (EMM386.EXE, QEMM.EXE, 386MAX.EXE, and CEMM.EXE) support the VCPI specification. VCPI allows applications using MS-DOS extenders to run simultaneously with 386 EMMs on a 386 machine. However, multitasking operating environments such as Windows 386 enhanced mode, OS/2, UNIX 386, and VM386 have memory and protection models that are not compatible with the VCPI interface. DPMI was created so these environments can run extended MS-DOS applications. Additionally, DPMI provides support for 80286-based machines, while VCPI does not. DPMI has the capability of running MS-DOS extended applications on a variety of processors and operating environments. GLOSSARY ======== 386 Expanded Memory Manager (EMM) --------------------------------- A device driver loaded that provides expanded memory on an 80386-based computer without a physical expanded memory board. 386 expanded memory managers (EMMs) operate through the 80386 processors hardware capabilities. 386MAX.SYS ---------- A 386 expanded memory manager (EMM) from Qualitas Corporation. CEMM.EXE -------- A 386 EMM from Compaq. CEMM is provided with all Compaq 386-based computers. It has an extension of .EXE rather than .SYS, even though it is installed in the CONFIG.SYS file like other 386 EMMs. Conventional Memory ------------------- The memory in your machine from zero K to 640K. DPMI ---- The MS-DOS Protected Mode Interface (MS-DOS extender industry standard). Applications that use the DPMI specification can run in protected mode and break the 640K barrier under standard or 386 enhanced mode. The DPMI specification is available from Intel Corporation. EMM386.EXE ---------- The Microsoft 386 expanded memory manager (EMM). See the "Microsoft Windows 3.1 Users Guide" for more information. EMM --- Expanded memory manager. EMS --- Expanded Memory Specification. Expanded Memory Specification (EMS) ----------------------------------- There are two expanded memory specifications, which are designated LIM 3.2 and LIM 4.0. Expanded Memory Manager (EMM) ----------------------------- A device driver that provides an interface to expanded memory. An expanded memory manager, or EMM, is either specific to a particular physical expanded memory board, or uses the 386 processor. Extended Memory --------------- Memory in your machine above 1 MB. Extended memory always starts at 1024K. Extended Memory Specification (XMS) ----------------------------------- The XMS provides a standard way for real mode applications to access extended memory. MS-DOS applications running under Windows 3.x can use the XMS to access extended memory. The XMS document and sample source code is available from Microsoft Sales Information Center (MSIC) at (800) 426-9400; international callers should call (206) 936-8661. HIMEM.SYS --------- Microsoft's high memory manager. Manages extended memory in accordance with the Extended Memory Specification (XMS). Large Page Frame ---------------- A slang term denoting the presence of bankable expanded memory pages in conventional memory. Large page frame is usually used to refer to a number of bankable pages equal to or greater than 384K (that is, bankable pages ranging from 256K to 640K). Note that the term "large page frame" is a misnomer. The page frame is actually never any larger than four 16K pages and is always located in the 384K UMA. Additional bankable pages in conventional memory do not make the page frame larger; they simply provide additional bankable pages. LIM 3.2 ------- The Lotus/Intel/Microsoft Expanded Memory Specification (EMS) version 3.2. It provides for a maximum of four 16K bankable pages that must be contiguous. LIM 4.0 ------- The Lotus/Intel/Microsoft Expanded Memory Specification (EMS) version 4.0. It provides for a maximum of 64 16K bankable pages that do not have to be contiguous. Page Frame ---------- An area within the 384K upper memory area (UMA) that is designated the expanded memory page frame. The page frame itself can be a maximum of four 16K pages. QEMM386.SYS ----------- A 386 expanded memory manager (EMM) by Quarterdeck Office Systems. Small Page Frame ---------------- A slang term denoting the presence of expanded memory that does not place bankable pages within conventional memory. UMA --- Upper memory area. Upper Memory Area (UMA) ----------------------- The area between 640K and 1024K present on all IBM-compatible machines. Sometimes called the reserved address space because this area was originally reserved by IBM for the ROM BIOS, video memory, and other hardware functions. VCPI ---- Virtual Control Program Interface. An 80386 memory management standard created by Phar Lap Software in conjunction with other software developers. VM -- Virtual (8086) machine. The VM exists in a protected memory space created through the hardware capabilities of the 80386 processor. Virtual Memory -------------- The space on a hard drive partition that 386 enhanced mode Windows can address as physical memory. Often referred to as the (temporary or permanent) "swap" file. VMM --- Virtual memory manager. Virtual Memory Manager (VMM) ---------------------------- Manages the disk space used as virtual memory. XMS --- Extended Memory Specification. TO OBTAIN THIS APPLICATION NOTE =============================== - On CompuServe, GEnie, and Microsoft OnLine, Application Notes are located in the Microsoft Software Library. You can find WW0335 in the Software Library by searching on the word WW0335, the Q number of this article, or S12782. WW0335 was archived using the PKware file-compression utility. - Application Notes are available by modem from the Microsoft Download Service (MSDL), which you can reach by calling (206) 936-6735. This service is available 24 hours a day, 7 days a week. The highest download speed available is 14,400 bits per second (bps). For more information about using the MSDL, call (800) 936-4200 and follow the prompts. To obtain WW0335, download WW0335.EXE. WW0335.EXE is a compressed, self-extracting file. After you download WW0335, run it to extract the file(s) it contains. - On the Internet, Application Notes are located on the Microsoft anonymous ftp server, which you can reach by typing "ftp ftp.microsoft.com" (without the quotation marks) at the ">" command prompt. - If you are unable to access the source(s) listed above, you can have this Application Note mailed or faxed to you by calling Microsoft Product Support Services Monday through Friday, 6:00 A.M. to 6:00 P.M. Pacific time at (206) 637-7098. If you are outside the United States, contact the Microsoft subsidiary for your area. To locate your subsidiary, call Microsoft International Customer Service at (206) 936-8661. KBCategory: kbfile kbenv kbhw kbappnote KBSubcategory: win30 win31 winmem Additional reference words: appnote 3.00 3.0 3.0a 3.00a 3.10 Win_Compuserve How to Rebuild the Default Windows REG.DAT File Article ID: Q80393 ---------------------------------------------------------------- ------ The information in this article applies to: - Microsoft Windows operating system versions 3.1, 3.11 - Microsoft Windows for Workgroups versions 3.1, 3.11 ---------------------------------------------------------------- ------ SUMMARY ======= During installation of Microsoft Windows, the REG.DAT file is not copied from the original distribution disks. Instead, REG.DAT is built using the Windows Registration Information Editor (REGEDIT.EXE) and the SETUP.REG file (located in the Windows SYSTEM subdirectory) during Setup. If the REG.DAT file is corrupted, one of the following error messages may be displayed: File Manager cannot open or print the specified file. Start the application used to create this file, and open or print it from there. -or- There is no application associated with this file. Choose Associate from the File menu to create an association. -or- There is a problem with REG.DAT. Delete REG.DAT and restart Windows. -or- Setup had a problem with REG.DAT, SHELL.DLL or disk space. -or- Windows registration database program is not valid -or- OLE server initialization failed -or- Windows registration database is not valid If, for whatever reason, the REG.DAT file is corrupted or deleted, you can rebuild the file using the information below. MORE INFORMATION ================ The REG.DAT file contains information about file associations and OLE objects. The Windows 3.1 Setup program calls the Registration Information Editor to add default associations (for Paintbrush, Notepad, and so on) and objects (Packager, Paintbrush, and Sound Recorder). Rebuilding the REG.DAT File for Applications Included with Windows ----------------------------------------------------------------- - You can manually create a new REG.DAT file or restore the defaults by following the steps below. NOTES ----- - Be sure to rename your existing REG.DAT file before you try to rebuild it. - These steps assume your Windows directory is on drive C and is named WINDOWS. 1. Run Program Manager or File Manager. 2. From the File menu, choose Run. 3. In the dialog box, type the following: regedit /u c:\windows\system\setup.reg 4. Choose OK. 5. In File Manager, select the REG.DAT file found in the Windows program directory, then choose Associate from the File menu and associate REG with REGEDIT.EXE. NOTE: When you removed the old REG.DAT file, you also removed your file associations list; therefore, you must choose REGEDIT.EXE using the Browse button. 6. Exit and restart Windows. The Registration Information Editor displays a dialog box letting you know whether the items were successfully added to the REG.DAT file. Rebuilding the REG.DAT File for Other Applications -------------------------------------------------- For applications other than the Windows-based programs included with Windows 3.1, the technique varies for rebuilding REG.DAT. Some applications, such as Microsoft Word for Windows 2.0, rebuild their entries every time the application is started. Other applications may register themselves only during their setup processes. NOTE: If you are using Word 2.0 for Windows, make sure to include the path to the Word for Windows program directory and the WW20.REG file located there (for example, C:\WINWORD\WW20.REG) so that the registration database is updated. If the application includes an .REG file, you can add that information to the registration database. To do so, either: - Choose Merge Registration File from the File menu in the Registration Information Editor. Then select the .REG file for the application to be added to the database and choose OK. -or- - Use the same steps described above, substituting the name of the .REG file. Otherwise, consult the application's documentation or contact your vendor for more information about rebuilding the REG.DAT file. -or- - Run Windows File Manager and double-click the application's .REG file. If you need to rebuild the registration database for all your applications, use the following steps: 1. From the File menu in File Manager, choose Search. 2. Search for *.REG from C:\. Ensure that the Search All Subdirectories check box is selected before you choose OK. 3. Run SETUP.REG by double-clicking the file icon or by highlighting it and then pressing ENTER. 4. Run every other .REG file brought up by the File Manager search (just as you did in step 3). For instructions on registering Microsoft Office version 4.x applications, query on the following words in the Microsoft Knowledge Base: ole and regedit and office Additional information about Registration Information Editor is available in Windows 3.1 Help. REFERENCES ========== "Microsoft Windows Resource Kit for Operating System Version 3.1," Chapter 11, page 360 KBCategory: kbsetup kbsound kbole KBSubcategory: win31 wfw wfwg Additional reference words: gpf 3.1 3.10 KBOLE win31 howto reg.dat 3.11 Microsoft Access 2.0 setup WinWord word for windows 6 6.0 Lotus 1-2-3 registry or Finding Files, Q126005. If you modify or delete these articles, Windows Driver Library Information Article ID: Q82006 ---------------------------------------------------------------- ------ The information in this article applies to: - Microsoft Windows operating system version 3.1 ---------------------------------------------------------------- ------ SUMMARY ======= Microsoft has made available the Windows Driver Library (WDL). The WDL offers support for many printers, displays, sound cards, and network card adapters not provided with Windows 3.1. If you have a modem, the drivers are available at no charge on CompuServe, GEnie, Microsoft OnLine, and the Microsoft Download Service (MSDL). However, note that standard connect-time fees and long-distance telephone charges, if any, will still apply during downloading. When you connect to any of these services, please read the WDL.TXT file for downloading instructions and a complete list of devices supported in the WDL. The phone number for the MSDL is (206) 936-MSDL (6735). There is no connect-time charge for using this service. On CompuServe, the WDL is in the Microsoft Software Library, which can be reached by typing "go msl" (without quotation marks) at the system prompt. (To find WDL.TXT, search on S13354.) On the GEnie and Microsoft OnLine systems, the WDL is in the Microsoft Software Library. (To find WDL.TXT, search on S13354.) If you do not have a modem, you can obtain an individual WDL driver on disk by calling Microsoft Product Support Services at (206) 637-7098. Below is the complete text of the WDL.TXT file that is distributed with the WDL. For a list of the changes to the WDL drivers, query on "Q84151" in the Microsoft Knowledge Base. MORE INFORMATION ================ Introduction ------------ The Microsoft Windows Driver Library (WDL) contains device drivers for printers, displays, audio devices, and network card adapters. These drivers enable these devices to run with Microsoft Windows operating system version 3.1. This library also contains a few additional items, such as Access Pack for Microsoft Windows software and a Novell NetWare upgrade. As new and updated drivers become available, they will be added to the WDL. This WDL.TXT file includes a list of all the devices supported by the drivers in the WDL and instructions for downloading the drivers. This file is updated on a regular basis. NOTE: All the drivers included in this library are intended for use with Windows 3.1. These drivers are NOT RECOMMENDED for use with Windows 3.0 except where files are specifically described as being Windows 3.0 compatible (for example, Access Pack for Microsoft Windows). Instructions for Downloading ---------------------------- 1. Locate your device in the listing included at the end of this WDL.TXT file. Note the name of the file listed next to the device. You need to download this file from your downloading service. 2. If you are downloading to a floppy disk, you need to have a formatted, blank disk. If you are downloading to your hard disk, create a new subdirectory in which you will place the files. CAUTION: Do not download files directly into your WINDOWS directory. Doing so could overwrite files essential to the proper operation of your system. 3. Follow the downloading procedure used by your downloading service. The file you download is the executable or program (.EXE) file that you identified in step 1. This file contains all the files you need to support your device. Download the .EXE file to your floppy disk or to the new subdirectory you created on your hard disk. 4. Change to the floppy disk drive (or the subdirectory on your hard disk) that contains the .EXE file. At the MS-DOS prompt, type the filename, and then press ENTER. When the .EXE file finishes running, all the files you need to support your device, such as a .DRV file and an OEMSETUP.INF file, are set up. You are also provided with a .TXT file that contains instructions for installing the device drivers (or other software) and a licensing agreement. If you have problems extracting files, try downloading the files again. Obtaining Drivers on Disk ------------------------- If you do not have a modem, you can obtain individual Windows drivers on disk by calling Microsoft Product Support Services at (206) 637-7098. WINDOWS DRIVER LIBRARY CONTENTS =============================== Version File Most Current Printer Number to Download .EXE File Date ----------------------------------------------------------------- Generic Printer Driver 1.68 GENDRV.EXE 02/03/93 Universal Printer Driver 3.1.4 UNIDRV.EXE 11/04/93 Microsoft PostScript Driver 3.58 PSCRIP.EXE 11/04/93 Agfa Compugraphic Genics 2.1 HPPCL.EXE 08/31/93 Apple: Personal LaserWriter NTR 3.56 APPLE.EXE 07/01/93 LaserWriter Pro 600 600DPI (8MB) APPLE.EXE 07/01/93 LaserWriter Pro 630 600DPI 3.56 APPLE.EXE 07/01/93 LaserWriter Select 360 300DPI 3.56 LWS360.EXE 03/11/94 LaserWriter Select 360 600DPI 3.56 LWS360.EXE 03/11/94 Apricot Laser 2.1 HPPCL.EXE 08/31/93 Brother HJ-100 1.10 BROHL.EXE 10/08/92 Brother HJ-770 1.10 BROHL.EXE 10/08/92 Brother HL-4 1.10 BROHL.EXE 10/08/92 Brother HL-8 1.10 BROHL.EXE 10/08/92 Brother HL-8D 1.10 BROHL.EXE 10/08/92 Brother HL-8e 1.10 BROHL.EXE 10/08/92 Brother M-1309 3.1.2 BRO9.EXE 10/08/92 Brother M-1324 1.9 BRO24.EXE 10/08/92 Brother M-1809 3.1.2 BRO9.EXE 10/08/92 Brother M-1824L 1.9 BRO24.EXE 10/08/92 Brother M-1909 3.1.2 BRO9.EXE 10/08/92 Brother M-1924L 1.9 BRO24.EXE 10/08/92 Bull Compuprint 4/12 1.20 BULL.EXE 10/08/92 Bull Compuprint 4/14 1.10 BULL.EXE 10/08/92 Bull Compuprint 4/22 1.10 BULL.EXE 10/08/92 Bull Compuprint 4/23 1.10 BULL.EXE 10/08/92 Bull Compuprint 4/40 1.10 BULL.EXE 10/08/92 Bull Compuprint 4/41 1.10 BULL.EXE 10/08/92 Bull Compuprint 4/51 1.10 BULL.EXE 10/08/92 Bull Compuprint 4/52 1.10 BULL.EXE 10/08/92 Bull Compuprint 4/54 1.10 BULL.EXE 10/08/92 Bull Compuprint 4/64 1.10 BULL.EXE 10/08/92 Bull Compuprint 4/66 1.10 BULL.EXE 10/08/92 Bull Compuprint 4/68 1.10 BULL.EXE 10/08/92 Bull Compuprint 922N 1.10 BULL.EXE 10/08/92 Bull Compuprint 923 1.10 BULL.EXE 10/08/92 Bull Compuprint 924 1.10 BULL.EXE 10/08/92 Bull Compuprint 924N 1.10 BULL.EXE 10/08/92 Bull Compuprint 970 1.10 BULL.EXE 10/08/92 Bull Compuprint 1070 1.10 BULL.EXE 10/08/92 Bull Compuprint PageMaster 411 1.2 BULL.EXE 10/08/92 Bull Compuprint PageMaster 721 1.2 BULL.EXE 10/08/92 Bull Compuprint PageMaster 821 1.2 BULL.EXE 10/08/92 Bull Compuprint PageMaster 10211.2 BULL.EXE 10/08/92 Bull Compuprint PM 201 1.30 JP350.EXE 12/09/92 Canon Bubble-Jet BJ-10ex(propr)1.25 CANON.EXE 10/08/92 Canon Bubble-Jet BJ-10ex (LQ) 1.0 CANON.EXE 10/08/92 Canon Bubble-Jet BJ-10sx 1.0 BJ10.EXE 04/30/93 Canon Bubble-Jet BJ-130 1.0 CANON.EXE 10/08/92 Canon Bubble-Jet BJ-20 (propr) 1.25 CANON.EXE 10/08/92 Canon Bubble-Jet BJ-20 (LQ) 1.0 CANON.EXE 10/08/92 Canon Bubble-Jet BJ-200 1.2 CANON3.EXE 10/13/93 Canon Bubble-Jet BJ-200e 1.01 BJ200E.EXE 08/11/94 Canon Bubble-Jet BJ-230 1.1 BJ230.EXE 04/30/93 Canon Bubble-Jet BJ-300 1.50 CANON2.EXE 10/20/92 Canon Bubble-Jet BJ-330 1.50 CANON2.EXE 10/20/92 Canon Bubble-Jet BJC-600 1.0 BJ600.EXE 01/31/94 Canon Bubble-Jet BJC-800 1.10 CANON.EXE 10/08/92 Citizen 120D 2.0 CIT9.EXE 10/08/92 Citizen 120D 2.0 CIT9.EXE 10/08/92 Citizen 124D 2.0 CIT24.EXE 10/08/92 Citizen 180D 2.0 CIT9.EXE 10/08/92 Citizen 200GX 2.0 CIT9.EXE 10/08/92 Citizen 200GX/15 2.0 CIT9.EXE 10/08/92 Citizen 224 2.0 CIT24.EXE 10/08/92 Citizen GSX-130 2.0 CIT24.EXE 10/08/92 Citizen GSX-140 2.0 CIT24.EXE 10/08/92 Citizen GSX-140+ 2.0 CIT24.EXE 10/08/92 Citizen GSX-145 2.0 CIT24.EXE 10/08/92 Citizen HSP-500 2.0 CIT9.EXE 10/08/92 Citizen HSP-550 2.0 CIT9.EXE 10/08/92 Citizen PN48 2.0 CIT24.EXE 10/08/92 Citizen Prodot 9 2.0 CIT9.EXE 10/08/92 Citizen Prodot 9x 2.0 CIT9.EXE 10/08/92 Citizen Prodot 24 2.0 CIT24.EXE 10/08/92 Citizen PROjet 1.30 JP350.EXE 12/09/92 Citizen Swift 9 2.0 CIT9.EXE 10/08/92 Citizen Swift 9x 2.0 CIT9.EXE 10/08/92 Citizen Swift 24 2.0 CIT24.EXE 10/08/92 Citizen Swift 24x 2.0 CIT24.EXE 10/08/92 Citizen Swift 24e 2.0 CIT24.EXE 10/08/92 Compaq Pagemarq 15 1.7 COMPAQ.EXE 04/30/93 Compaq Pagemarq 20 1.7 COMPAQ.EXE 04/30/93 Data Products LZR 2080 1.0 DATAPR.EXE 11/28/94 Diconix 150 Plus 1.10 DICONX.EXE 10/20/92 Digital DEClaser 1100 3.1 DEC1.EXE 02/03/93 Digital DEClaser 2100/Plus 3.1 DEC1.EXE 02/03/93 Digital DEClaser 2200/Plus 3.1 DEC1.EXE 02/03/93 Digital DEClaser 3200 3.1 DEC1.EXE 02/03/93 Digital DECmultiJET 1000 1.30 JP350.EXE 12/09/92 Digital DECmultiJET 2000 1.30 JP350.EXE 12/09/92 Digital LA70 3.1 DEC1.EXE 02/03/93 Digital LA75 3.1 DEC1.EXE 02/03/93 Digital LA75 Plus 3.1 DEC1.EXE 02/03/93 Digital LA324 3.1 DEC1.EXE 02/03/93 Digital LJ250/252 3.1 DEC1.EXE 02/03/93 Digital LN03/PLUS 3.1 DEC1.EXE 02/03/93 Epson ActionLaser II 1.53 EPLZR.EXE 10/08/92 Epson AP-3250 ESC/P 2 1.61 EPSON.EXE 05/18/94 Epson AP-5000 ESC/P 2 1.61 EPSON.EXE 05/18/94 Epson AP-5000+ ESC/P 2 1.61 EPSON.EXE 05/18/94 Epson AP-5500 ESC/P 2 1.61 EPSON.EXE 05/18/94 Epson DFX-5000 2.10 EP9.EXE 03/12/93 Epson DLQ-2000 2.11 EP24.EXE 10/08/92 Epson EPL-4000 1.53 EPLZR.EXE 10/08/92 Epson EPL-7000 1.53 EPLZR.EXE 10/08/92 Epson EX-800 2.10 EP9.EXE 03/12/93 Epson EX-1000 2.10 EP9.EXE 03/12/93 Epson FX-80 2.10 EP9.EXE 03/12/93 Epson FX-80 2.10 EP9.EXE 03/12/93 Epson FX-85 2.10 EP9.EXE 03/12/93 Epson FX-86e 2.10 EP9.EXE 03/12/93 Epson FX-100 2.10 EP9.EXE 03/12/93 Epson FX-105 2.10 EP9.EXE 03/12/93 Epson FX-185 2.10 EP9.EXE 03/12/93 Epson FX-286 2.10 EP9.EXE 03/12/93 Epson FX-286e 2.10 EP9.EXE 03/12/93 Epson FX-800 2.10 EP9.EXE 03/12/93 Epson FX-850 2.10 EP9.EXE 03/12/93 Epson FX-1000 2.10 EP9.EXE 03/12/93 Epson FX-1050 2.10 EP9.EXE 03/12/93 Epson JX-80 2.10 EP9.EXE 03/12/93 Epson L-750 2.11 EP24.EXE 10/08/92 Epson L-1000 2.11 EP24.EXE 10/08/92 Epson LQ-100 ESC/P 2 1.61 EPSON.EXE 05/18/94 Epson LQ-200 2.11 EP24.EXE 10/08/92 Epson LQ-400 2.11 EP24.EXE 10/08/92 Epson LQ-450 2.11 EP24.EXE 10/08/92 Epson LQ-500 2.11 EP24.EXE 10/08/92 Epson LQ-510 2.11 EP24.EXE 10/08/92 Epson LQ-570 ESC/P 2 1.61 EPSON.EXE 05/18/94 Epson LQ-570+ ESC/P 2 1.61 EPSON.EXE 05/18/94 Epson LQ-800 2.11 EP24.EXE 10/08/92 Epson LQ-850 2.11 EP24.EXE 10/08/92 Epson LQ-860 2.11 EP24.EXE 10/08/92 Epson LQ-870 ESC/P 2 1.61 EPSON.EXE 05/18/94 Epson LQ-950 2.11 EP24.EXE 10/08/92 Epson LQ-1000 2.11 EP24.EXE 10/08/92 Epson LQ-1010 2.11 EP24.EXE 10/08/92 Epson LQ-1050 2.11 EP24.EXE 10/08/92 Epson LQ-1060 2.11 EP24.EXE 10/08/92 Epson LQ-1070 ESC/P 2 1.61 EPSON.EXE 05/18/94 Epson LQ-1170+ ESC/P 2 1.61 EPSON.EXE 05/18/94 Epson LQ-1070 ESC/P 2 1.61 EPSON.EXE 05/18/94 Epson LQ-1500 2.11 EP24.EXE 10/08/92 Epson LQ-2500 2.11 EP24.EXE 10/08/92 Epson LQ-2550 2.11 EP24.EXE 10/08/92 Epson LX-80 2.10 EP9.EXE 03/12/93 Epson LX-86 2.10 EP9.EXE 03/12/93 Epson LX-400 2.10 EP9.EXE 03/12/93 Epson LX-800 2.10 EP9.EXE 03/12/93 Epson LX-810 2.10 EP9.EXE 03/12/93 Epson LX-850 2.10 EP9.EXE 03/12/93 Epson LX-850 2.10 EP9.EXE 03/12/93 Epson MX-80 2.10 EP9.EXE 03/12/93 Epson MX-80 F/T 2.10 EP9.EXE 03/12/93 Epson MX-100 2.10 EP9.EXE 03/12/93 Epson RX-80 2.10 EP9.EXE 03/12/93 Epson RX-80 F/T 2.10 EP9.EXE 03/12/93 Epson RX-80 F/T 2.10 EP9.EXE 03/12/93 Epson RX-100 2.10 EP9.EXE 03/12/93 Epson RX-100 2.10 EP9.EXE 03/12/93 Epson SQ-850 2.11 EP24.EXE 10/08/92 Epson SQ-870 ESC/P 2 1.61 EPSON.EXE 05/18/94 Epson SQ-1170 ESC/P 2 1.61 EPSON.EXE 05/18/94 Epson SQ-2000 2.11 EP24.EXE 10/08/92 Epson SQ-2500 2.11 EP24.EXE 10/08/92 Epson SQ-2550 2.11 EP24.EXE 10/08/92 Epson Stylus 300 ESC/p 2 1.61 EPSON.EXE 05/18/94 Epson Stylus 800 ESC/p 2 1.61 EPSON.EXE 05/18/94 Epson Stylus 1000 ESC/p 2 1.61 EPSON.EXE 05/18/94 Epson T-750 2.10 EP9.EXE 03/12/93 Epson T-1000 2.10 EP9.EXE 03/12/93 Fujitsu PrintPartner 10/W (2MB+)3.56 FJ10W3.EXE 07/01/93 Fujitsu PrintPartner 10 (2MB+) 3.56 FJ10W3.EXE 07/01/93 Fujitsu PrintPartner 10/W (2MB)3.56 FJ10W2.EXE 07/01/93 Fujitsu PrintPartner 10 (2MB) 3.56 FJ10W2.EXE 07/01/93 Fujitsu Breeze 100 1.30 JP350.EXE 12/09/92 Fujitsu Breeze 200 1.30 JP350.EXE 12/09/92 Fujitsu DL 900 1.60 FUJI24.EXE 12/09/92 Fujitsu DL 1100 1.60 FUJI24.EXE 12/09/92 Fujitsu DL 1100 Colour 1.60 FUJI24.EXE 12/09/92 Fujitsu DL 1200 1.60 FUJI24.EXE 12/09/92 Fujitsu DL 2400 1.60 FUJI24.EXE 12/09/92 Fujitsu DL 3300 1.60 FUJI24.EXE 12/09/92 Fujitsu DL 3350 1.60 FUJI24.EXE 12/09/92 Fujitsu DL 3400 1.60 FUJI24.EXE 12/09/92 Fujitsu DL 3450 1.60 FUJI24.EXE 12/09/92 Fujitsu DL 3600 1.60 FUJI24.EXE 12/09/92 Fujitsu DL 4400 1.60 FUJI24.EXE 12/09/92 Fujitsu DL 4600 1.60 FUJI24.EXE 12/09/92 Fujitsu DL 5600 1.60 FUJI24.EXE 12/09/92 Fujitsu DX 2100 1.10 FUJI9.EXE 10/20/92 Fujitsu DX 2200 1.10 FUJI9.EXE 10/20/92 Fujitsu DX 2300 1.10 FUJI9.EXE 10/20/92 Fujitsu DX 2400 1.10 FUJI9.EXE 10/20/92 HP DeskJet 2.10 HPDJET.EXE 07/21/93 HP DeskJet Plus 2.10 HPDJET.EXE 07/21/93 HP DeskJet Portable 2.10 HPDJET.EXE 07/21/93 HP DeskJet 500 2.10 HPDJET.EXE 07/21/93 HP LaserJet 2.1 HPPCL.EXE 08/31/93 HP LaserJet Plus 2.1 HPPCL.EXE 08/31/93 HP LaserJet 500 2.1 HPPCL.EXE 08/31/93 HP LaserJet 2000 2.1 HPPCL.EXE 08/31/93 HP LaserJet Series II 2.1 HPPCL.EXE 08/31/93 HP LaserJet IID 2.1 HPPCL.EXE 08/31/93 HP LaserJet IIP 2.1 HPPCL.EXE 08/31/93 HP LaserJet IIP Plus 2.1 HPPCL.EXE 08/31/93 HP LaserJet III 2.1 HPPCL5.EXE 11/16/92 HP LaserJet IIIP 2.1 HPPCL5.EXE 11/16/92 HP LaserJet IIID 2.1 HPPCL5.EXE 11/16/92 HP LaserJet IIISi 2.1 HPPCL5.EXE 11/16/92 HP LaserJet 4/4M 1.18 HPCL5E.EXE 06/24/93 HP LaserJet 4Si 1.18 HPCL5E.EXE 06/24/93 HP LaserJet 4Si MX 1.18 HPCL5E.EXE 06/24/93 HP PaintJet 2.1 HPPJET.EXE 03/11/94 HP PaintJet XL 2.1 HPPJET.EXE 03/11/94 HP QuietJet 1.10 HPQJET.EXE 10/08/92 HP QuietJet Plus 1.10 HPQJET.EXE 10/08/92 IBM Laser Printer 4029 3.02 IB4029.EXE 02/03/93 IBM Personal Printer II 2380 1.10 IB2390.EXE 10/08/92 IBM Personal Printer II 2381 1.10 IB2390.EXE 10/08/92 IBM Personal Printer II 2390 1.10 IB2390.EXE 10/08/92 IBM Personal Printer II 2391 1.10 IB2390.EXE 10/08/92 IBM Proprinter 1.10 PROP9.EXE 10/08/92 IBM Proprinter II 1.10 PROP9.EXE 10/08/92 IBM Proprinter III 1.10 PROP9.EXE 10/08/92 IBM Proprinter X24 2.15 PROP24.EXE 10/20/92 IBM Proprinter X24e 2.15 PROP24.EXE 10/20/92 IBM Proprinter XL 1.10 PROP9.EXE 10/08/92 IBM Proprinter XL II 1.10 PROP9.EXE 10/08/92 IBM Proprinter XL III 1.10 PROP9.EXE 10/08/92 IBM Proprinter XL24 2.15 PROP24.EXE 10/20/92 IBM Proprinter XL24e 2.15 PROP24.EXE 10/20/92 IBM QuickWriter 5204 1.10 IB5204.EXE 11/16/92 IBM QuietWriter III 1.60 QWIII.EXE 11/16/92 Kyocera F-Series (USA) 2.1 HPPCL.EXE 08/31/93 Kyocera F-5000 (USA) 2.1 HPPCL.EXE 08/31/93 Linotronic 100 3.56 LINO.EXE 07/01/93 Linotronic 200/230 3.56 LINO.EXE 07/01/93 Linotronic 300 v47.1 3.56 LINO.EXE 07/01/93 Linotronic 300 v49.3 3.56 LINO.EXE 07/01/93 Linotronic 330 3.56 LINO.EXE 07/01/93 Linotronic 500 3.56 LINO.EXE 07/01/93 Linotronic 530 3.56 LINO.EXE 07/01/93 Linotronic 630 3.56 LINO.EXE 07/01/93 Mannesmann Tally MT 130/24 1.10 MANNT.EXE 10/08/92 Mannesmann Tally MT 130/9 1.10 MANNT.EXE 10/08/92 Mannesmann Tally MT 131/24 1.10 MANNT.EXE 10/08/92 Mannesmann Tally MT 131/9 1.10 MANNT.EXE 10/08/92 Mannesmann Tally MT 230/18 1.10 MANNT.EXE 10/08/92 Mannesmann Tally MT 230/24 1.10 MANNT.EXE 10/08/92 Mannesmann Tally MT 230/9 1.10 MANNT.EXE 10/08/92 Mannesmann Tally MT 290 1.10 MANNT.EXE 10/08/92 Mannesmann Tally MT 330 1.10 MANNT.EXE 10/08/92 Mannesmann Tally MT 340 1.10 MANNT.EXE 10/08/92 Mannesmann Tally MT 730/735 1.10 MANNT.EXE 10/08/92 Mannesmann Tally MT 81 1.10 MANNT.EXE 10/08/92 Mannesmann Tally MT 82 1.10 MANNT.EXE 10/08/92 Mannesmann Tally MT 90 1.10 MANNT.EXE 10/08/92 Mannesmann Tally MT 91 1.10 MANNT.EXE 10/08/92 Mannesmann Tally MT 92 1.10 MANNT.EXE 10/08/92 Mannesmann Tally MT 92C 1.10 MANNT.EXE 10/08/92 Mannesmann Tally MT 93 1.10 MANNT.EXE 10/08/92 Mannesmann Tally MT 94 1.10 MANNT.EXE 10/08/92 Mannesmann Tally MT 98/99 1.10 MANNT.EXE 10/08/92 Minolta SP1000 (2MB) 3.56 MINOLT.EXE 04/30/93 Minolta SP1000 (2MB+) 3.56 MINOLT.EXE 04/30/93 Minolta SP1500 (2MB) 3.56 MINOLT.EXE 04/30/93 Minolta SP1500 (2MB+) 3.56 MINOLT.EXE 04/30/93 NEC Pinwriter CP6 2.0 NECP24.EXE 02/09/93 NEC Pinwriter CP7 2.0 NECP24.EXE 02/09/93 NEC Pinwriter P2plus 2.0 NECP24.EXE 02/09/93 NEC Pinwriter P5XL 2.0 NECP24.EXE 02/09/93 NEC Pinwriter P6 2.0 NECP24.EXE 02/09/93 NEC Pinwriter P6plus 2.0 NECP24.EXE 02/09/93 NEC Pinwriter P7 2.0 NECP24.EXE 02/09/93 NEC Pinwriter P7plus 2.0 NECP24.EXE 02/09/93 NEC Pinwriter P9XL 2.0 NECP24.EXE 02/09/93 NEC Pinwriter P2200 2.0 NECP24.EXE 02/09/93 NEC Pinwriter P3200 1.30 NECPIN.EXE 10/08/92 NEC Pinwriter P3300 1.30 NECPIN.EXE 10/08/92 NEC Pinwriter P5200 2.0 NECP24.EXE 02/09/93 NEC Pinwriter P5300 2.0 NECP24.EXE 02/09/93 NEC Pinwriter P6200 1.30 NECPIN.EXE 10/08/92 NEC Pinwriter P6300 1.30 NECPIN.EXE 10/08/92 NEC Pinwriter P9300 1.30 NECPIN.EXE 10/08/92 NEC Silentwriter LC 860 Plus 2.1 HPPCL.EXE 08/31/93 Okidata LaserLine 6 2.1 HPPCL.EXE 08/31/93 Okidata ML 380 2.0 OKI24.EXE 10/08/92 Okidata ML 390 2.0 OKI24.EXE 10/08/92 Okidata ML 390 Plus 2.0 OKI24.EXE 10/08/92 Okidata ML 391 2.0 OKI24.EXE 10/08/92 Okidata ML 391 Plus 2.0 OKI24.EXE 10/08/92 Okidata ML 393 2.0 OKI24.EXE 10/08/92 Okidata ML 393 Plus 2.0 OKI24.EXE 10/08/92 Okidata ML 393C 2.0 OKI24.EXE 10/08/92 Okidata ML 393C Plus 2.0 OKI24.EXE 10/08/92 Okidata OL-400 1.19 OKILED.EXE 10/08/92 Okidata OL-800 1.19 OKILED.EXE 10/08/92 Okidata OL-830 3.56 OK830.EXE 07/01/93 Olivetti DM 124 C 3.03 OLIVE.EXE 02/03/93 Olivetti ETV 5000 2.1 HPPCL.EXE 08/31/93 Olivetti JP 150 1.30 JP350.EXE 12/09/92 Olivetti JP 350 1.30 JP350.EXE 12/09/92 Olivetti JP 350S 1.30 JP350.EXE 12/09/92 Olivetti PG 108 2.1 HPPCL.EXE 08/31/93 Olivetti PG 208 M2 2.1 HPPCL.EXE 08/31/93 Olivetti PG 306 1.0 OLIPG.EXE 11/16/92 Olivetti PG 308 1.0 OLIPG.EXE 11/16/92 Olivetti PG 308 HS 2.1 HPPCL.EXE 08/31/93 Panasonic KX-P1081 2.10 PAN9.EXE 02/09/93 Panasonic KX-P1123 2.10 PAN24.EXE 12/09/92 Panasonic KX-P1124 2.10 PAN24.EXE 12/09/92 Panasonic KX-P1124i 2.10 PAN24.EXE 12/09/92 Panasonic KX-P1180 2.10 PAN9.EXE 02/09/93 Panasonic KX-P1624 2.10 PAN24.EXE 12/09/92 Panasonic KX-P1695 2.10 PAN9.EXE 02/09/93 Panasonic KX-P2123 2.10 PAN24.EXE 12/09/92 Panasonic KX-P2124 2.10 PAN24.EXE 12/09/92 Panasonic KX-P2180 2.10 PAN9.EXE 02/09/93 Panasonic KX-P2624 2.10 PAN24.EXE 12/09/92 Panasonic KX-P4420 2.1 HPPCL.EXE 08/31/93 Panasonic KX-P4450 1.10 PANKX.EXE 10/20/92 Panasonic KX-P4450i 1.10 PANKX.EXE 10/20/92 QMS-PS 2200 3.56 PS2000.EXE 07/01/93 QuadLaser I 2.1 HPPCL.EXE 08/31/93 Royal CJP 450 3.03 OLIVE.EXE 02/03/93 Seiko (Generic Printer Driver) Seiko CH 5504 3.06 SEIKO.EXE 02/03/93 Seiko CH 5514 3.06 SEIKO.EXE 02/03/93 Seiko CH 4104 3.04 SEIKO.EXE 02/03/93 Seiko (PostScript Driver) Seiko CH 5504 (PS) 3.56 SEIKO2.EXE 07/01/93 Seiko CH 5514 (PS) 3.56 CH5514.EXE 07/01/93 Seiko CH 4104 (PS) 3.56 PS4104.EXE 07/01/93 Sharp JX-9300 1.10 SHARP.EXE 10/08/92 Sharp JX-9500 1.10 SHARP.EXE 10/08/92 Sharp JX-9500E 1.10 SHARP.EXE 10/08/92 Sharp JX-9500H 1.10 SHARP.EXE 10/08/92 Sharp JX-9700 1.10 SHARP.EXE 10/08/92 Star Laserprinter 4 1.10 STAR.EXE 10/08/92 Star Laserprinter 8 1.10 STAR.EXE 10/08/92 Star Laserprinter 8 DB 1.10 STAR.EXE 10/08/92 Star Laserprinter 8 DX 1.10 STAR.EXE 10/08/92 Star Laserprinter 8 II 1.10 STAR.EXE 10/08/92 Star NB24-10 1.20 STAR.EXE 10/08/92 Star NB24-15 1.20 STAR.EXE 10/08/92 Star NL-10 1.20 STAR.EXE 10/08/92 Star NX-1000 1.20 STAR.EXE 10/08/92 Star NX-1000 Rainbow 1.20 STAR.EXE 10/08/92 Star NX-1001 1.20 STAR.EXE 10/08/92 Star NX-1020 Rainbow 1.20 STAR.EXE 10/08/92 Star NX-1500 1.20 STAR.EXE 10/08/92 Star NX-2400 1.20 STAR.EXE 10/08/92 Star NX-2410 1.20 STAR.EXE 10/08/92 Star NX-2415 1.20 STAR.EXE 10/08/92 Star NX-2420 1.20 STAR.EXE 10/08/92 Star NX-2420 Rainbow 1.20 STAR.EXE 10/08/92 Star NX-2430 1.20 STAR.EXE 10/08/92 Star SJ-48 1.20 STAR.EXE 10/08/92 Star XB-2410 1.20 STAR.EXE 10/08/92 Star XB-2415 1.20 STAR.EXE 10/08/92 Star XB-2420 1.20 STAR.EXE 10/08/92 Star XB-2425 1.20 STAR.EXE 10/08/92 Star XR-1000 1.20 STAR.EXE 10/08/92 Star XR-1020 1.20 STAR.EXE 10/08/92 Star XR-1500 1.20 STAR.EXE 10/08/92 Star XR-1520 1.20 STAR.EXE 10/08/92 Tandy LP-1000 2.1 HPPCL.EXE 08/31/93 Tegra Genesis 2.1 HPPCL.EXE 08/31/93 Tektronix: Phaser 200e 17 3.56 TEKTRO.EXE 07/01/93 Phaser 200e 39 3.56 TEKTRO.EXE 07/01/93 Phaser 200i 3.56 TEKTRO.EXE 07/01/93 TI Omnilaser 2108 3.56 TIOMNI.EXE 07/01/93 TI Omnilaser 2115 3.56 TIOMNI.EXE 07/01/93 Toshiba ExpressWriter 420 1.6 EXPRSS.EXE 10/08/92 Toshiba ExpressWriter 440 1.6 EXPRSS.EXE 10/08/92 Toshiba PageLaser12 2.1 HPPCL.EXE 08/31/93 Toshiba P351 3.00 TOSH24.EXE 08/12/92 Toshiba P351SX 1.3 P351SX.EXE 10/08/92 Toshiba P1351 3.00 TOSH24.EXE 08/12/92 Unisys AP-1324 1.19 UNI24.EXE 10/08/92 Unisys AP-1337 1.19 UNI24.EXE 10/08/92 Unisys AP-1339 1.19 UNI24.EXE 10/08/92 Unisys AP-1371 1.20 UN1371.EXE 10/08/92 Unisys AP-9205/AP-9210 1.27 UNILZ.EXE 10/08/92 Unisys AP-9210 2.1 HPPCL.EXE 08/31/93 Wang LDP8 2.1 HPPCL.EXE 08/31/93 Most Current Audio File to Download .EXE File Date --------------------------------------------------------------- Artisoft Sounding Board - ISA ARTIS.EXE 06/19/92 Artisoft Sounding Board - MCA ARTIS.EXE 06/19/92 IBM M-Audio Adapter AT BUS IBM.EXE 06/29/92 IBM M-Audio Adapter MC IBM.EXE 06/29/92 PC-Speaker Driver SPEAK.EXE 06/19/92 Thunderboard THUNDR.EXE 06/19/92 Most Current Display File to Download .EXE File Date --------------------------------------------------------------- CGA Driver CGA.EXE 06/19/92 MCGA Driver MMDISP.EXE 06/19/92 VGA (320x200, 256 colors) Palletized VGA Driver MMDISP.EXE 06/19/92 VGA (640x480, palettized 16 colors) VGAGRAY Driver MMDISP.EXE 06/19/92 VGA (640x480, 16 grays) Hercules Driver HERC311.EXE 01/31/94 EGA Driver EGA311.EXE 01/31/94 Appian RGDI & Compatible RGDI.EXE 06/19/92 ATI: ATI 8514/Ultra ATI.EXE 06/19/92 ATI Graphics Ultra ATI.EXE 06/19/92 ATI Graphics Vantage ATI.EXE 06/19/92 ATI VGA Wonder XL ATI.EXE 06/19/92 ATI VGA Wonder ATI.EXE 06/19/92 ATI VGA Wonder Plus ATI.EXE 06/19/92 Chips & Technology: CHIPS 655XX 640x480 256 colors CHIPS.EXE 10/27/92 CHIPS 655XX 800x600 256 colors CHIPS.EXE 10/27/92 CHIPS 655XX 1024x768 16 colors CHIPS.EXE 10/27/92 Cornerstone: Cornerstone MC168Ci CORNST.EXE 08/19/93 Cornerstone PC168Ci CORNST.EXE 08/19/93 Cornerstone MC128Ci CORNST.EXE 08/19/93 Cornerstone PC128Ci CORNST.EXE 08/19/93 DGIS 3.00 & Compatible DGIS30.EXE 10/08/92 HP UltraVGA V1.6: HPUltra 640X480 256clr (512k) HPULT.EXE 02/03/93 HPUltra 640X480 256clr HPULT.EXE 02/03/93 HPUltra 800X600 256clr HPULT.EXE 02/03/93 HPUltra 1024X768 256clr HPULT.EXE 02/03/93 (Large Fonts) HPUltra 1024X768 256clr HPULT.EXE 02/03/93 (Small Fonts) Super VGA: 640x480 256 colors SVGA.EXE 04/30/93 800x600 256 colors Large fonts SVGA.EXE 04/30/93 800x600 256 colors Small fonts SVGA.EXE 04/30/93 1024x768 256 colors Large fonts SVGA.EXE 04/30/93 1024x768 256 colors Small fonts SVGA.EXE 04/30/93 Tseng ET4000 640X480 16 colors TSEN1A.EXE 06/19/92 Tseng ET4000 800X600 16 colors TSEN1B.EXE 06/19/92 Tseng ET4000 1024X768 16 colors TSEN1C.EXE 06/19/92 Tseng ET4000 1280X1024 16 colors TSEN1D.EXE 06/19/92 Tseng ET4000 640X480 256 colors TSEN2A.EXE 06/19/92 Tseng ET4000 800X600 256 colors TSEN2B.EXE 06/19/92 Tseng ET4000 1024X768 256 colrs TSEN2C.EXE 06/19/92 Tseng ET4000 32K colors TSENG3.EXE 06/19/92 Tseng ET4000 64K colors TSENG4.EXE 06/19/92 S3-928 Chip S3-928.EXE 11/04/93 S3-801 Chip S3-801.EXE 11/04/93 S3-924 Chip S3-924.EXE 11/04/93 Western Digital (90C30) Paradise: WD 90C30 640X480 256 colors WD9030.EXE 02/03/93 WD 90C30 640X480 32K colors WD9030.EXE 02/03/93 WD 90C30 640X480 32K colors: WD9030.EXE 02/03/93 (Ventura, PageMaker only) WD 90C30 640X480 64K colors WD9030.EXE 02/03/93 WD 90C30 800X600 256 clr(512k) WD9030.EXE 02/03/93 WD 90C30 800X600 256 clr(1MB) WD9030.EXE 02/03/93 WD 90C30 800X600 32K colors WD9030.EXE 02/03/93 WD 90C30 800X600 32K colors: WD9030.EXE 02/03/93 (Ventura, PageMaker only) WD 90C30 800X600 64k colors WD9030.EXE 02/03/93 WD 90C30 1024X768 16 colors WD9030.EXE 02/03/93 WD 90C30 1024X768 256 clr(1MB) WD9030.EXE 02/03/93 WD 90C30 1280X960 16 colors WD9030.EXE 02/03/93 WD 90C30 1280X1024 16 colors WD9030.EXE 02/03/93 Western Digital (90C31) Paradise: WD 90C31 640X480 16 colors WD9031.EXE 02/03/93 WD 90C31 640X480 256 colors WD9031.EXE 02/03/93 WD 90C31 640X480 32K colors WD9031.EXE 02/03/93 WD 90C31 640X480 32K colors: WD9031.EXE 02/03/93 (Ventura, PageMaker only) WD 90C31 640X480 64K colors WD9031.EXE 02/03/93 WD 90C31 800X600 16 colors WD9031.EXE 02/03/93 WD 90C31 800X600 256 clr(512k) WD9031.EXE 02/03/93 WD 90C31 800X600 256 clr(1MB) WD9031.EXE 02/03/93 WD 90C31 800X600 32K colors WD9031.EXE 02/03/93 WD 90C31 800X600 32K colors: WD9031.EXE 02/03/93 (Ventura, PageMaker only) WD 90C31 800X600 64k colors WD9031.EXE 02/03/93 WD 90C31 1024X768 16 colors WD9031.EXE 02/03/93 WD 90C31 1024X768 256 clr(1MB) WD9031.EXE 02/03/93 WD 90C31 1280X960 16 colors WD9031.EXE 02/03/93 WD 90C31 1280X1024 16 colors WD9031.EXE 02/03/93 Most Current Network Card Adapters File to Download .EXE File Date --------------------------------------------------------------- 3Com EtherLink 3COM.EXE 11/16/92 3Com EtherLink/MC 32 3COM.EXE 11/16/92 3Com EtherLink 16 (3C507) ELNK16.EXE 04/02/93 3Com EtherLink III (3C509) ELNK3.EXE 04/02/93 3Com EtherLink EISA (3C579) ELNK3.EXE 04/02/93 3Com EtherLink II (3C503) ELNKII.EXE 04/02/93 3Com EtherLink II/16 TP ELNKII.EXE 04/02/93 (3C505 - 16-TP) 3Com EtherLink MC (3C523) ELNKMC.EXE 04/02/93 3Com EtherLink Plus (3C505-B) ELNKPL.EXE 04/02/93 3Com TokenLink III (3C619) IBMTOK.EXE 04/02/93 3Com TokenLink III (3C629) IBMTOK.EXE 04/02/93 Accton Technology: EtherCoax-16 (EN1642) NE2000.EXE 04/02/93 EtherCombo-16 (EN1640) NE2000.EXE 04/02/93 EtherPair-16 (EN1641) NE2000.EXE 04/02/93 Advanced Micro Devices: AM2100 AM2100.EXE 04/02/93 PCnet-ISA Ethernet Controller AM2100.EXE 04/02/93 PCnet Family Ethernet AMDPCN.EXE 04/22/94 Alta Research: EtherCombo-16 T/C NE2000.EXE 04/02/93 Allied Telesis AT1500T AT1500.EXE 03/12/93 Allied Telesis AT1500BT AT1500.EXE 03/12/93 Allied Telesis AT1500FT AT1500.EXE 03/12/93 Allied Telesis AT-1700 AT1700.EXE 12/13/93 Appex Tech WinLAN Adapter ISA APXWLI.EXE 01/31/94 Appex Tech Packet WinLAN Adapter APXWLP.EXE 01/31/94 Apricot: LS 386SX-20 w/ i82592 ETH592.EXE 03/12/93 LS PRO w/ i82596 ETH596.EXE 03/12/93 XEN-LS 486SX-20 w/ i82592 ETH592.EXE 03/12/93 Cabletron: E2000 Series DNI CTRON.EXE 04/02/93 E2100 Series DNI CTRON.EXE 04/02/93 E2100 Series Ethernet Adapters CTRE21.EXE 04/22/94 E3000 Series DNI CTETH.EXE 03/12/93 E3000 Series Ethernet Adapters CTRE30.EXE 04/22/94 E3100 Series DNI CTETH.EXE 03/12/93 E3100 Series Ethernet Adapters CTRE31.EXE 04/22/94 T2000 Series Token Ring Adapter CTRT20.EXE 04/22/94 T2015 Token Ring DNI CTTOK.EXE 04/02/93 T3015 Token Ring DNI CTTOK.EXE 04/02/93 Chips and Technology: MK561 Ethernet CNT561.EXE 12/28/93 Compaq: 32-Bit DualSpeed Token Ring NETFLX.EXE 12/13/93 32-Bit NetFlex Controller NETFLX.EXE 12/13/93 (Etnernet Mode) 32-Bit NetFlex Controller NETFLX.EXE 12/13/93 (Token Ring Mode) Compex ENET16/U COMPEX.EXE 10/27/92 Crescendo Communications C321M CRESDO.EXE 03/12/93 Digital Communications Associates: DCA 10-Net DCA586.EXE 10/27/92 DCA 10-Net Fiber Optic DCA586.EXE 10/27/92 DCA 10-Net Twisted Pair DCA586.EXE 10/27/92 DCA 10-Net MCA DCA586.EXE 10/27/92 DCA IRMAtrac Token-Ring Convert IRMA.EXE 03/12/93 DCStrac Token Ring Adapter DCATOK.EXE 12/13/93 Digital Equipment Corporation: DEC Etherworks LC DEPCA.EXE 04/02/93 DEC Etherworks MC DEPCA.EXE 04/02/93 DEC Etherworks Turbo DEPCA.EXE 04/02/93 DEC EtherWorks Turbo EISA DEC425.EXE 04/22/94 DEC DEPCA DEPCA.EXE 04/02/93 WaveLAN Adapters DECWAV.EXE 12/28/93 WaveLAN AT WAVELN.EXE 04/02/93 D-Link DE-220/TP/CT/C/T/CAT DE220.EXE 12/13/93 Everex SpeedLink /PC16 (EV2027) EVEREX.EXE 04/22/94 Gateway Communications: G/Ethernet 16 Combo GETHER.EXE 03/12/93 Hewlett-Packard: HP EtherTwist MCA (HP27246) HPLAN2.EXE 03/12/93 HP PC LAN Adapter/8 TL (HP27250) HPLAN.EXE 10/28/92 HP PC LAN Adapter/8 TP (HP27245) HPLAN.EXE 10/28/92 HP PC LAN Adptr/16 TP (HP27247A) HPLAN.EXE 10/28/92 HP PC LAN Ad/16 TL Plus-HP27252 HPLAN.EXE 10/28/92 HP PC LAN Ad/16 TP Plus-HP27247B HPLAN.EXE 10/28/92 HP Ethertwist EISA LAN 32-HP27248 HPLAN.EXE 10/28/92 IBM PCMCIA-NIC IBMPCM.EXE 10/27/92 IBM Token Ring IBMTOK.EXE 12/09/92 IBM Token Ring /A IBMTOK.EXE 04/02/93 IBM Token Ring II IBMTOK.EXE 04/02/93 IBM Token Ring 4/16 IBMTOK.EXE 04/02/93 IBM Token Ring 4/16 A IBMTOK.EXE 04/02/93 IBM PCMCIA Ethernet Adapter IBMPCM.EXE 03/11/94 IBM Token-Ring 16/4 Adapter II IBMTR2.EXE 12/13/93 IBM Token Ring 16/4 LanStreamer Server Adapter/A IBMLAN.EXE 12/13/93 ICL EtherTeam 16 NOKIA.EXE 03/12/93 ICL EtherTeam 16i Adapter ICL16I.EXE 12/13/93 Intel Corporation: EtherExpress 16 EXP16.EXE 12/13/93 EtherExpress 16TP EXP16.EXE 12/13/93 EtherExpress Flash 32 EISA NDIS3 INTFL3.EXE 04/22/94 EtherExpress Flash 32 EISA NDIS2 FL32.EXE 07/26/94 EtherExpress MCA EXP16.EXE 12/13/93 EtherExpress TPE Hub Adapter INTHUB.EXE 10/27/92 EtherExpress Pro Ethernet Adpt. EPRO.EXE 07/26/94 EtherNet PCMCIA Adapter INTPCM.EXE 12/13/93 TokenExpress 32 EISA 16/4 INTT32.EXE 04/22/94 Token Express MCA 16/4 OLITOK.EXE 04/02/93 Token Express EISA 16/4 OLITOK.EXE 04/02/93 Token Express ISA 16/4 OLITOK.EXE 04/02/93 Kingston Technology EtherRx KNE210.EXE 12/28/93 Madge Smart 16/4 XT RingNode MADGE.EXE 10/27/92 Madge Smart 16/4 AT RingNode MADGE.EXE 10/27/92 Madge Smart 16/4 EISA RingNode MADGE.EXE 10/27/92 Madge Smart 16/4 MC RingNode MADGE.EXE 10/27/92 National SemiConductor: At/Lantic EtherNODE 16*AT3 NE2000.EXE 04/02/93 EtherNODE *16AT NE2000.EXE 04/02/93 Net NSC InfoMover Eth PCMCIA 1.9 NSCPCM.EXE 10/04/94 Sonic EISA-DP83932EB NATSEM.EXE 03/12/93 NCR StarCard (8-bit) NCRSTR.EXE 10/27/92 NCR StarLAN 16/4 Token MC NAU STRN.EXE 04/02/93 NCR WaveLan AT Adapter WAVELN.EXE 04/02/93 NCR WaveLan MC Adapter WAVELN.EXE 04/02/93 Net Andrew MasterSeries TR 1.0 ANDTOK2.EXE 10/04/94 Net Compaq NetFlex Family 3.11 CPQNFX.EXE 10/04/94 Net ICL EtherTeam Family Eth 1.0 ICLETH.EXE 10/04/94 Net Racal 16/4 Token-Ring 2.16 RICTOK.EXE 10/04/94 Net Racore 16/4 Token-Ring 2.16 RACTOK.EXE 10/04/94 Net RAD 16/4 Token-Ring 2.16 RADTOK.EXE 10/04/94 Net TI TMS380/2000 16/4 TR 1.12 TITOK.EXE 10/04/94 New Media PCMCIA Ethernet LAN NMCETH.EXE 03/11/94 Novell NE1000 NE1000.EXE 04/02/93 Novell NE/2 NE2000.EXE 04/02/93 Novell NE2000 NE2000.EXE 04/02/93 Novell NE2000T NE2000.EXE 04/02/93 Novell NE2000 Plus NE200P.EXE 12/28/93 Olicom 16-Bit EISA 16/4 OLITOK.EXE 04/02/93 Olicom 16-Bit ISA 16/4 OLITOK.EXE 04/02/93 Olicom 16-Bit MCA 16/4 OLITOK.EXE 04/02/93 Olicom Token Ring Server 16/4 OLIT32.EXE 04/22/94 Proteon ISA Token Ring (1346) PRO4AT.EXE 03/12/93 Proteon ISA Token Ring (1347) PRO4AT.EXE 03/12/93 Proteon ISA Token Ring (1390) P139X.EXE 04/02/93 Proteon ISA Token Ring (1392) P139X.EXE 04/02/93 Proteon ISA Token Ring (1340) PRO4.EXE 03/12/93 Proteon ISA Token Ring (1342) PRO4.EXE 03/12/93 Proteon ISA Token Ring (1346) PRO4.EXE 03/12/93 Proteon ISA Token Ring (1347) PRO4.EXE 03/12/93 Proteon MCA Token Ring (1840) PRO4.EXE 03/12/93 Proteon ProNET-4/16 p1892 PROTEO.EXE 04/30/93 Proxim RangeLAN Wireless PROXIM.EXE 03/12/93 Pure Data PDE9025-32 16/4 OLITOK.EXE 04/02/93 Pure Data PDI8023-16 PDIETH.EXE 10/27/92 Pure Data PDI8023-8 PDIETH.EXE 10/27/92 Pure Data PDI9025-16 4 OLITOK.EXE 04/02/93 Pure Data PDI90211 (Wireless) WAVELN.EXE 04/02/93 Pure Data PDuC8023 PDIETH.EXE 10/27/92 Pure Data PDuC9025 16/4 OLITOK.EXE 04/02/93 Pure Data PDuC90211 (Wireless) WAVELN.EXE 04/02/93 Racal-Datacom NI5210/8 RACAL.EXE 10/27/92 Racal-Datacom NI5210/16 RACAL.EXE 10/27/92 Racal-Datacom NI6510 NI6510.EXE 12/13/93 Racal-Datacom NI9210 RACAL.EXE 10/27/92 Racal-Datacom Interlan ILANAT RACAL.EXE 10/27/92 Racal-Datacom ES3210 RACAL.EXE 10/27/92 Racal-Datacom EtherBlaster NI6510.EXE 12/13/93 Racore TokenLite 16/4 (M8116) RACLMO.EXE 07/13/94 Racore TokenLite 16/4 (M8119) RACLMO.EXE 07/13/94 Silcom Direct 16 Token-Ring Adapter SILCOM.EXE 07/13/94 Standard Microsystems: SMC PC130 SMCARC.EXE 04/02/93 SMC PC130E SMCARC.EXE 04/02/93 SMC PC130W SMCARC.EXE 04/02/93 SMC PC130WS SMCARC.EXE 04/02/93 SMC 3000 Series SMC3.EXE 04/02/93 SMC 8003E/A SMCMAC.EXE 04/02/93 SMC 8003EP SMCMAC.EXE 04/02/93 SMC 8003EPC SMCMAC.EXE 04/02/93 SMC 8013EPC SMCMAC.EXE 04/02/93 SMC 8003EWC SMCMAC.EXE 04/02/93 SMC 8003WC SMCMAC.EXE 04/02/93 SMC 9000 SMC900.EXE 12/28/93 Thomas Conrad (All Types) TCCARC.EXE 03/12/93 Thomas Conrad TC6042 TCCARC.EXE 03/12/93 Thomas Conrad TC6045 TCCARC.EXE 03/12/93 Thomas Conrad TC6142 TCCARC.EXE 03/12/93 Thomas Conrad TC6145 TCCARC.EXE 03/12/93 Thomas Conrad TC6242 TCCARC.EXE 03/12/93 Thomas Conrad TC6245 TCCARC.EXE 03/12/93 Thomas Conrad Token Ring Adapter TCCTOK.EXE 10/27/92 Tiara EtherStar LanCard/E TIARA.EXE 12/13/93 Tulip NCC-16 TULIP.EXE 10/27/92 Ungermann-Bass: UB NIU (All Types) UB.EXE 03/12/93 UB NIC/ps UB.EXE 03/12/93 UB NIUpc (PC2030) UB.EXE 03/12/93 UB NIUpc/3270 UB.EXE 03/12/93 UB NIUpc/EOTP (PC4035) UB.EXE 03/12/93 UB NIUps (PC3030) UB.EXE 03/12/93 UB NIUps/EOTP (PC3035) UB.EXE 03/12/93 UB PC5000 MasterLAN UB5000.EXE 12/28/93 UB pcNIU UB.EXE 03/12/93 UB pcNIU/ex 128K UB.EXE 03/12/93 UB pcNIU/ex 512K UB.EXE 03/12/93 Xircom Credit Card Ethernet XIRPCM.EXE 12/13/93 Xircom Pocket Ethernet I XIRCOM.EXE 03/12/93 Xircom Pocket Ethernet II XIRCOM.EXE 03/12/93 Xircon Packet Etnernet III XIRPE3.EXE 12/28/93 Zenith Data Systems: Z.Note 325L Notebook PC IMLM.EXE 04/02/93 Most Current Miscellaneous Software File to Download .EXE File Date --------------------------------------------------------------- Access Pack ACCP.EXE 03/12/93 Arches Wallpaper ARCHES.EXE 10/27/92 C and D Printer Fonts CDFONT.EXE 07/10/92 Chitz Wallpaper CHITZ.EXE 10/27/92 Chord Sound File CHORD.EXE 10/27/92 Marble Wallpaper MARBLE.EXE 10/27/92 MONOUMB.386 MONO.EXE 07/10/92 MSCDEX CDEXT.EXE 07/10/92 MS-DOS Executive MSEXE.EXE 08/12/92 Microsoft Mail Help MMHELP.EXE 10/27/92 Microsoft Schedule Plus Help SPHELP.EXE 10/27/92 Mystify Screen Saver SSMYST.EXE 10/27/92 Novell NetWare Upgrade NOVELL.EXE 07/10/92 Microsoft IPX Upgrade Utility NOVELL.EXE 07/10/92 Reversi REVERS.EXE 07/10/92 SYSINI.WRI WRI.EXE 07/10/92 TADA Sound File TADA.EXE 10/27/92 Tartan Wallpaper TARTAN.EXE 10/27/92 VPD.386 VPD386.EXE 07/10/92 Wacom ArtPad Tablet 1.0 ARTPAD.EXE 12/05/94 Wacom ArtZ Tablet 1.0 ARTZ.EXE 12/05/94 WININI.WRI WRI.EXE 07/10/92 KBCategory: kbnetwork kbdisplay kbsound kb3rdparty kbfile kbref kbmm KBSubcategory: wfw win31 wfwg windrvr Additional reference words: 3.10 getwdl soundblaster handicaps disability disabilities accessibility Windows and WFWG 3.1x Setup Error Codes (000 through 100) Article ID: Q82772 ---------------------------------------------------------------- ---- The information in this article applies to: - Microsoft Windows operating system versions 3.1, 3.11 - Microsoft Windows for Workgroups versions 3.1, 3.11 ---------------------------------------------------------------- ---- SUMMARY ======= When a Setup error message contains an error code, it also includes some text indicating what Setup was trying to do, for example, copying a file. The text of the error message indicates whether the error is fatal or not. In some nonfatal cases, Setup may be performing an operation (such as copying a file) that is needed to run Windows. Other times the error may prevent some specific feature of Windows from operating properly. In many cases, the error code is an MS-DOS extended error code. These error codes are between 0 and 100. Setup-specific error codes have two different formats, depending on whether the error occurs during the character (MS-DOS) mode or Windows graphical user interface (GUI) mode portion of Setup. The character mode Setup specific error numbers are in the format "Snnn", where "nnn" is any three digits. The GUI mode error numbers are codes greater than 200. MORE INFORMATION ================ In both character and GUI modes, the following MS-DOS error codes may be reported: 02 File not found - possible corrupt disks. 03 Path not found - possible hardware problem or incompatible software (virus?). 04 Too many open files - should never occur. May occur in maintenance mode Setup if WIN.COM, WIN.CNF, or another component is crosslinked with another file. 05 Access denied - make sure the file is not write protected or protected by virus protection software. 06 Handle invalid - serious problem, unknown. 07 Memory control blocks destroyed - serious problem, unknown. 08 Insufficient memory - free up memory and run Setup again. May also occur if very long or corrupt SYSTEM.INI, WIN.INI or SETUP.INF files exist. 09 Memory block address invalid - serious problem, unknown. 10 Environment invalid - serious problem, unknown. 11 Format invalid - serious problem, unknown. 12 Access code invalid - serious problem, unknown. 13 Data invalid - serious problem, unknown. 14 Unknown unit - serious problem, unknown. 15 Disk drive invalid - serious problem, unknown. 16 Attempted to remove current directory - serious problem, unknown. 17 Not same device - serious problem, unknown. 18 No more files - serious problem, unknown. 19 Write-protected disk - should never occur (different error message). 20 Unknown unit - serious problem, unknown. 21 Drive not ready - should never occur (different error message). 22 Unknown command - serious problem, unknown. 23 Data error (CRC) - possible corrupt disks. 24 Bad request-structure length - serious problem, unknown. 25 Seek error - possible corrupt disks. 26 Unknown media type - possible corrupt disks. 27 Sector not found - possible corrupt disks. 28 Write fault - possible corrupt disks. 30 Read fault - possible corrupt disks. 31 General failure - possible corrupt disks. 32 Sharing violation - should never occur (different error message). 33 File-lock violation - should never occur (different error message). 34 Disk change invalid - serious problem, unknown. 35 FCB unavailable - serious problem, unknown. When setting up to or from a network, the following MS-DOS error codes can occur: 50 Unsupported network request - serious problem, unknown. 51 Remote machine not listening - serious problem, unknown. 52 Duplicate name on network - serious problem, unknown. 53 Network name not found - serious problem, unknown. 54 Network busy - retry operation. 55 Device no longer exists on network - check with network administrator. 56 NetBIOS command limit exceeded - check with network administrator. 57 Error in network adapter hardware - check with network administrator. 58 Incorrect response from network - check with network administrator. 59 Unexpected network error - check with network administrator. 60 Remote adapter incompatible - serious problem, unknown. 64 Network name deleted - serious problem, unknown. 65 Network access denied - check with network administrator. 66 Incorrect network device type - serious problem, unknown. 67 Network name not found - serious problem, unknown. 68 Network name limit exceeded - check with network administrator. 69 NetBIOS session limit exceeded - check with network administrator. 70 Temporary pause in file sharing - check with network administrator. 71 Network request not accepted - check with network administrator. 72 Print or disk redirection paused - serious problem, unknown. 80 File already exists - serious problem, unknown. Setup will use MS-DOS to make sure it can write over existing files. 82 Cannot make directory - check with network administrator. 83 Fail on Int 24H (critical error) - some drivers will fail an access when an error occurs without issuing an Int 24H (which causes Setup to display an error message allowing you to retry the operation rather than just failing it). The cause of the error is bad disks or network problems. Some viruses and virus-protection software can cause this error to occur. 84 Too many redirections - serious problem, unknown. 85 Duplicate redirection - serious problem, unknown. 86 Invalid password - check with network administrator. 87 Invalid parameter - serious problem, unknown. 88 Net write fault - check with network administrator. KBCategory: kbsetup kbdisplay kberrmsg KBSubcategory: win31 wfw wfwg Additional reference words: 3.10 3.11 3.1 WW0530: SMARTDrive and 32-Bit Disk Access Article ID: Q83325 ---------------------------------------------------------------- - The information in this article applies to: - Microsoft Windows operating system version 3.1 ---------------------------------------------------------------- - Microsoft has an Application Note available titled "WW0530: SMARTDrive and 32-Bit Disk Access." This Application Note discusses the enhancements in Windows 3.1 features for accessing and using the hard disk drive of your computer. You can obtain this Application Note from the following sources: - CompuServe, GEnie, and Microsoft OnLine - Microsoft Download Service (MSDL) - The Internet (Microsoft anonymous ftp server) - Microsoft FastTips Technical Library - Microsoft Product Support Services For complete information, see the "To Obtain This Application Note" section at the end of this article. THE TEXT OF WW0530 ================== ================================================================ ====== Microsoft(R) Product Support Services Application Note (Text File) WW0530: SMARTDrive and 32-Bit Disk Access ================================================================ ====== Revision Date: 4/92 No Disk Included The following information applies to Microsoft Windows(TM) version 3.1. ----------------------------------------------------------------- --- | INFORMATION PROVIDED IN THIS DOCUMENT AND ANY SOFTWARE THAT MAY | | ACCOMPANY THIS DOCUMENT (collectively referred to as an | | Application Note) IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY | | KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO | | THE IMPLIED WARRANTIES OF MERCHANTABILITY AND/OR FITNESS FOR A | | PARTICULAR PURPOSE. The user assumes the entire risk as to the | | accuracy and the use of this Application Note. This Application | | Note may be copied and distributed subject to the following | | conditions: 1) All text must be copied without modification and | | all pages must be included; 2) If software is included, all files | | on the disk(s) must be copied without modification [the MS-DOS(R) | | utility DISKCOPY is appropriate for this purpose]; 3) All | | components of this Application Note must be distributed together; | | and 4) This Application Note may not be distributed for profit. | | | | Copyright 1992 Microsoft Corporation. All Rights Reserved. | | Microsoft and MS-DOS are registered trademarks | | and Windows is a trademark of Microsoft Corporation. | ---------------------------------------------------------------- ---- INTRODUCTION ============ Microsoft Windows operating system version 3.1 has a number of enhancements over previous versions that improve both its usability and its performance. Foremost among these enhancements are Windows 3.1's improved features for accessing and utilizing the hard drive of your PC. SMARTDRIVE 4.0 DISK CACHE ========================= Microsoft's first release of the Windows graphical environment included a disk caching program called SMARTDrive 3.03. SMARTDrive has been improved with each subsequent release of Windows and has been entirely redesigned in Windows version 3.1. SMARTDrive 4.0 in Windows 3.1 provides faster and more intelligent disk caching that takes better advantage of the revolutionary way that Windows and Windows- based applications use extended memory. SMARTDrive 4.0 gives Windows 3.1: - Improved performance by speeding up hard disk and RAM access. - Improved stability in 386 enhanced mode by double buffering data when needed. The remainder of this section compares the performance of SMARTDrive 4.0 to SMARTDrive 3.x and illustrates how SMARTDrive 4.0 works at a more technical level. WHAT IS SMARTDRIVE? =================== SMARTDrive is a disk caching program that intercepts system calls to the hard disk to control read/write access to the disk. SMARTDrive intercepts any calls to the hard disk and loads the needed data into a cache it establishes in RAM. (Unless specified otherwise, SMARTDrive automatically determines a reasonable cache size based on the amount of free extended memory available when it initially loads; the maximum amount it will take is around 2 MB.) Subsequent calls to the hard disk are intercepted by SMARTDrive, which scans the cache for the requested data. If the data is already present in the cache, SMARTDrive can access it directly in RAM. If the data is not in the cache, SMARTDrive accesses the hard disk and loads the necessary data into the cache. The least recently used data residing in RAM is cached back to the hard disk to make room for the new data. By loading blocks of data from the hard disk into RAM, SMARTDrive helps decrease the number of calls to the hard disk. This can dramatically speed up applications that repeatedly access the hard disk for data because accessing the hard disk is considerably slower than accessing RAM. Essentially, SMARTDrive attempts to maintain information in RAM that an application needs at any given time from the hard disk. SMARTDRIVE 3.X ============== To understand why SMARTDrive needed to be redesigned, lets look at how SMARTDrive 3.x works and examine some of the shortcomings of its design. First, SMARTDrive 3.x is a read-only track cache, which means that it caches on a track basis and for read operations only. This means that the internal data structures of the SMARTDrive program are tied to the logical geometry of the disk (that is, what MS-DOS sees). In the diagram below, you can see that SMARTDrive 3.x caches at the ROM BIOS INT13 level and uses the BIOS-specified disk geometry to decide the size of its caching element (that is, track size). INT13 is the most common method for interacting with hard disks (and has evolved into the industry standard). SMARTDrive under Windows 3.0 can be loaded into either extended memory or expanded memory. Application (Read/Write INT21) | - - - - - - - - - - - - - - - - - | MS-DOS Call HD Driver | HD Driver INT 13 | ---------> SMARTDrive 3.x Chains INT13 ---------< | ROM BIOS | Hard Drive SMARTDRIVE 4.0 ============== SMARTDrive 4.0 is designed as a block-oriented disk cache. It hooks into the system at the MS-DOS device driver level rather than at the ROM BIOS INT13 level (as with SMARTDrive 3.x). Each block device driver on the MS-DOS device driver chain is "front-ended" by a SMARTDrive 4.0 module that provides the actual caching. This new design yields the following benefits: - It is independent of the INT13 interface. - It is independent of disk geometry. Application (Read/Write INT21) | - - - - - - - - - - - - - - - | MS-DOS Call HD Driver | ---------> SMARTDrive 4.0 HOOKS Driver ---------< | HD Driver INT 13 | ROM BIOS | Hard Drive Independent of INT13 Interface ------------------------------ Many device drivers do not use the INT13 (BIOS) interface (for example, Bernoulli drives, some hard cards, and many SCSI and WORM drives). This means that SMARTDrive 4.0 can cache these devices, whereas SMARTDrive 3.x cannot. SMARTDrive 4.0 can cache any disk controller that uses an MS-DOS block device driver. Independent of Disk Geometry ---------------------------- Some disk managers and disk controllers use a disk geometry mapping scheme that causes the logical geometry to be different from the physical geometry (for example, many PS/2 systems, Ontrack's Disk Manager, and several disk controllers). The INT13-based disk caches are sensitive to this and often have problems. For example, some disk management software actually changes the ROM BIOS-specified disk geometry, which confuses INT13-based disk caches (including SMARTDrive 3.x). There usually is an interface to determine the true geometry, but this requires detection of the specific disk manager driver and generally complicates the disk cache software. Often, logical tracks actually cross physical track boundaries, causing the track caches to incur performance penalties (intertrack seeks and rotational latencies, for example). To get around the ROM BIOS 1024-cylinder limitation, disk managers and controllers sometimes fold multiple tracks into one logical track. This results not only in problems with the physical track boundaries as noted above, buts forces track caches to have a very large track buffer as well. In some cases, this buffer can be as large as 31.5K and must reside in conventional memory. The design of SMARTDrive 4.0 eliminates this geometry mismatch problem. OTHER SMARTDRIVE 4.0 FEATURES ============================= Write-Behind Cache ------------------ SMARTDrive 4.0 is a write-behind cache, also known as lazy write. A write-behind cache adds significant performance improvements wherever files are being written to disk. For example, an application writes data to what it thinks is the hard disk. SMARTDrive takes this data and places it in the cache, rather than physically writing it to the disk. This write-behind data stays in the cache until one of the following occurs: 1. The cache fills up. The oldest block in the cache is freed up, and if it is write-behind data, physically written to the disk. 2. The system goes idle. SMARTDrive writes the oldest write-behind data block to the physical disk. As long as the system is idle, SMARTDrive continues to write to the disk until all the write- behind data is written. This write-behind data also comes from Windows-based and MS-DOS-based applications that are idle. 3. SMARTDrive detects that you have pressed CTRL+ALT+DEL. When you restart by pressing CTRL+ALT+DEL, SMARTDrive writes all write- behind data to the physical disk. This is a synchronous operation-- SMARTDrive does not give up control until all data is written. 4. A block is older than five seconds. If a block is older than five seconds, it is written to the physical disk. Shrink Algorithm ---------------- Similar to SMARTDrive 3.x, SMARTDrive 4.0 implements a shrink algorithm that frees memory for Windows (that is, the cache set up by SMARTDrive is removed from memory). The difference is that SMARTDrive 4.0 watches for the Windows startup broadcast while SMARTDrive 3.x provides an IOCTL interface. The net effect is identical, but the SMARTDrive 4.0 code is much simpler. Upon exiting Windows, the process is reversed and the memory is reacquired by SMARTDrive 4.0. Automatic Load High ------------------- When an upper memory block (UMB) provider (such as EMM386.EXE) is loaded, SMARTDrive 4.0 (SMARTDRV.EXE) automatically attempts to load itself high. Unlike the Windows 3.0 SMARTDrive, SMARTDrive 4.0 can only be loaded into extended memory. DOUBLE BUFFERING AND BUS MASTERING ================================== The second major benefit of SMARTDrive 4.0 is the protection it provides through double buffering. Double buffering is a response to bus mastering, which is supported by certain (usually older) disk controllers. Bus mastering refers to a situation in which the hard disk controller takes over the bus to directly transfer data to or from system RAM, bypassing the CPU entirely. A problem occurs when Windows 3.x virtual machines and/or popular memory managers (such as EMM386.EXE and QEMM.SYS) are running in virtual 8086 mode. The read or write address that is passed to MS-DOS from the bus master controller is often not the same as the actual physical memory address. This can cause data to be read from the wrong location, or worse, can cause data to be written to the wrong RAM address, resulting in erratic system behavior and potential file corruption. When paging is enabled on an 80386 or faster processor, it is possible for the physical address (the actual location of the memory) to be different from the virtual address (the address that programs are using to access memory). Paging is enabled by all device drivers that can provide load high capability and by Windows in 386 enhanced mode. For example, say SMARTDrive wants to write to an area of memory that has a virtual address in conventional memory, but a physical address in extended memory. When the hard drive controller takes over the bus and transfers data from the UMB to the disk, the controller does not use the CPU, so there is no address translation, resulting in the wrong data being written to disk. To avoid this problem, double buffering copies the data into a buffer in conventional memory and then passes the information to the hard disk controller. So, the virtual address always equals the physical address when using devices that only recognize conventional memory. Installing Double Buffering --------------------------- To install the SMARTDrive double-buffering feature, add the following line to your CONFIG.SYS file: device=c:\windows\smartdrv.exe /double_buffer Including this line does not install the cache, only the double- buffering driver. The cache must be installed from the AUTOEXEC.BAT file or MS-DOS command line. Most disk controllers do not need double buffering. These include all MFM, RLL, and IDE controllers as well as many ESDI and SCSI devices. The Setup program in Windows 3.1 will install the double buffer in the following cases: 1. If the computer has an 80386 or faster processor 2. If 32-Bit Disk Access was not installed in the SYSTEM.INI file (see next section) You should install the double buffer in these cases in the interest of added safety. Another new feature of SMARTDrive 4.0 that helps you determine if double buffering is necessary is the smartdrv command. Once your system is running with SMARTDrive loaded, type "smartdrv" (without the quotation marks) at the MS-DOS prompt and press ENTER. Information similar to the following is displayed: Microsoft SMARTDrive Disk Cache version 4.0 Copyright 1991, 1992 Microsoft Corp. Cache size: 1,048,576 bytes Cache size while running Windows: 1,048,576 bytes Disk Caching Status drive read cache write cache buffering --------------------------------------------------- A: yes no no B: yes no no C: yes yes yes D: yes yes --- For help, type "Smartdrv /?". Note the column labeled "buffering." For each drive that is being cached, one of three values is displayed--"yes," indicating that double buffering is needed; "no," indicating that double buffering is not needed; or "---," indicating that SMARTDrive has not yet determined the necessity of double buffering. If the buffering column displays a "no" for each drive, the double buffer driver is unnecessary, and you can safely remove it from your CONFIG.SYS file. Setting Up SMARTDrive 4.0 ------------------------- The Setup program in Microsoft Windows 3.1 automatically installs SMARTDrive (SMARTDRV.EXE) in the first line of your AUTOEXEC.BAT file. In general, you should let the Setup program configure SMARTDrive's cache size for you. However, please note it is critical that SMARTDRV.EXE load after any block devices that reside on your system, such as: - Hard disk partitioning software (for example, DMDRVR.BIN and SSTOR.SYS) - Hard disk drivers (for example, SCSI drives, hard cards, and Bernoulli drives) - Data encryption software (for example, Stacker and DoubleDisk) The configuration of SMARTDRV.EXE is controlled by command-line parameters. Most configuration options can be modified without restarting; however, without the Windows Resource Kit utility SMARTDrive Monitor (SMARTMON.EXE), the configuration cannot be altered while running Windows. Also note that SMARTDrive: - Needs a minimum cache size of 16K. - Creates a cache size of 16K by default if you supply an invalid cache size. - Gives you benefits up to a cache size of 2 MB, whereupon the benefits typically plateau. 32-BIT DISK ACCESS ================== Another new feature of Windows 3.1 is its use of 32-Bit Disk Access. 32-Bit Disk Access is not a program but rather a term used to refer to a system of Windows components working together. The main purpose of these components is to allow Windows to interact directly with the hard disk, bypassing the BIOS, which is normally used for communicating with the hard disk. Under 386 enhanced mode Windows, where 32-Bit Disk Access is supported, you get the following benefits: - Faster hard disk access - Ability to run more MS-DOS-based applications - Faster overall system response, even when running MS-DOS-based applications in the background - More powerful off-the-shelf disk utilities to choose from, since independent software vendors (ISVs) are writing programs that take advantage of this new set of services WHAT IS 32-BIT DISK ACCESS? =========================== - A SYSTEM OF WINDOWS COMPONENTS. Some of these components are called 32-Bit Disk Access devices, but they are useless without the rest of the components to support them. Each of these components is discussed below. - A REPLACEMENT FOR THE HARD DISK BIOS. 32-Bit Disk Access serves as a device driver that interacts with the hard disk controller. 32-Bit Disk Access watches for INT13H calls and handles them if they are for the disk it represents; otherwise, it passes the calls on to the BIOS in the usual way, as if 32-Bit Disk Access were not available. - AN EXACT MATCH FOR THE HARD DISK CONTROLLER (NOT THE SPECIFIC HARD DISK). There are some standards for hardware communication that work on many different controllers. The most widely adopted standard is that introduced by Western Digital in its 1003 controllers. This is the standard supported by Windows 3.1 and more than 90 percent of hard disk controllers, with the exception of ESDI and SCSI controllers. - AN OPEN STANDARD FOR CERTAIN CONTROLLERS. 32-Bit Disk Access is an open standard that is being promoted to all manufacturers of hard disk controllers. This means that every manufacturer has the opportunity to write a device driver that supports 32-Bit Disk Access functionality for its hardware. Many hardware manufacturers are writing 32-Bit Disk Access device drivers that will be available at the time Windows 3.1 ships or shortly thereafter. - AN OPTION, NOT A SYSTEM REQUIREMENT. Without the 32-Bit Disk Access device driver installed, you lose the hardware-access benefits provided by 32-Bit Disk Access, but your system is otherwise unaffected. Windows 3.1 without 32-Bit Disk Access has the same disk access capabilities of Windows 3.0. DISK ACCESS UNDER MS-DOS ======================== The 32-Bit Disk Access feature bypasses the system BIOS to more directly control hard disk access. It acts, in a sense, as the hard disk controller. Before discussing how disk access has changed under Windows 3.1, let's look at how MS-DOS handles calls to the hard disk. In the MS-DOS-based PC, when an application wants to read from the disk, it tracks the following sequence: H/W INT21H INT13H I/O ------> -----> -----> ----- ------ ---- ---------- ----- | APP | |MS-DOS| |BIOS| |Controller| ->|Drive| ----- ------ ---- ---------- ----- 1. The application makes an INT21H call to MS-DOS. 2. MS-DOS locates the requested part of the file on the hard disk. 3. MS-DOS issues an INT13H call to talk to the hard disk BIOS. The BIOS contains a program to control each device in the system. 4. The BIOS driver talks directly to the hard disk controller. Each hard disk controller requires its own BIOS driver, but these BIOS drivers are usually not specific to the hard disk itself, but rather to the controller board (or adapter) that connects the hard disk to the rest of the system. This system works well, because MS-DOS is able to identify the files and directories and keep track of their locations, regardless of the type of hard disk MS-DOS is accessing. But, on the other hand, the system BIOS is wholly linked to the hard disk, which provides disk independence for the applications but does not allow the BIOS to differentiate between a call from MS-DOS or a program such as SMARTDrive. But remember that not all disk device drivers reside in ROM. If you purchase an off-the-shelf disk drive and install it, your computer's ROM BIOS may not know how to communicate with it. If this is the case, you must install a device driver that is specific to your new hard disk. This additional device driver is usually installed in your CONFIG.SYS file when you install the software that comes with your hard disk. With some devices, such as a CD-ROM drive, a device driver that provides the BIOS interface and INT13H interface to the CD-ROM drive appears in your AUTOEXEC.BAT file. This type of device driver traps INT13H calls to the hard disk and makes sure the calls are understood by the hard disk. Usually, the device driver handles any attempts to access the hard disk; the calls never get passed on to the real ROM BIOS. If the call is not for the device that the device driver represents, then the INT13H call is passed on to the BIOS, where it is handled in the usual way. 32-Bit Disk Access represents a way for Windows to provide a BIOS that better suits customers' device support needs. 32-BIT DISK ACCESS SPEEDS UP DISK ACCESS ======================================== On many machines, the resident hard disk BIOS is slow and inefficient. Since 32-Bit Disk Access is specific to devices, it is often more efficient, leading to very impressive performance increases. 32-Bit Disk Access also allows Windows 3.1 to handle BIOS requests in protected mode, rather than in real mode, which may also speed up disk access. The following diagram charts the flow of calls under Windows in standard mode: H/W INT21H INT13H I/O ------> -----> -----> ----- ------ ---- ---------- ----- | APP | |MS-DOS| |BIOS| |Controller| ->|Drive| ----- ------ ---- ---------- ----- Under 386 enhanced mode Windows, the flow of calls is more complicated: ------------------------------------------------- | Enhanced Mode Virtual Devices | ------------------------------------------------- Protected / \ / \ Mode / \ / \ ----------/-----\------/--------\------------------------------- ---- Virtual / \ / \ Mode / \ / \ ----- INT21H ------ INT13H ---- H/W ---------- ----- | APP | |MS-DOS| |BIOS| I/O |Controller|-->|Drive| ----- ------ ---- -----> ---------- ----- Windows 3.1 and Windows applications run in protected mode. Windows has to switch back into real mode (or virtual 8086 mode) to run older code (for MS-DOS and the BIOS calls, for example). Switching modes is very time consuming. For example, when a non-Windows application running under 386 enhanced mode tries to read from a file, the following occurs: Windows starts out in virtual mode running the application. Windows makes an INT21H call to read from the file. 386 enhanced mode traps this interrupt and switches to protected mode, where a number of virtual device drivers look at the call and try to qualify it. If none of the device drivers intercepts the call, the call is accepted and is subsequently handed off to MS-DOS. Windows then switches back to virtual mode to let MS-DOS handle the call. MS-DOS reads a particular location on the disk and then generates an INT13H call to talk to the BIOS. Windows in 386 enhanced mode then traps the call again and switches to protected mode to perform certain tasks, hands the call back to the real BIOS, and switches back to virtual mode. The BIOS handles the call and accesses the hard disk controller to set the physical read in motion. Once the BIOS reads the call, Windows goes back to protected mode to perform more tasks and then returns to virtual mode to let MS-DOS see the returned call. Windows returns the INT21H call, switches to protected mode to perform yet more tasks, and then finally switches back to virtual mode to communicate with the application that issued the call to begin with. All this mode switching takes time but is necessary due to the nature of the 80386 processor, MS-DOS, and the PC BIOS. With a 32-Bit Disk Access device installed, Windows can start trapping INT13H calls and handling them entirely in protected mode. With 32-Bit Disk Access, the call diagram now looks like this: ---------------------------- H/W ---------- ----- |Enhanced Mode |32-Bit Disk| I/O |Controller| ->|Drive| |Virtual Devices | Access| -----> ---------- ----- ----------------------------- Protected / \ / Mode / \ / -----------/-------\- ----/--------------------------------------- Virtual / \ / Mode / \ / ----- INT21H ------ INT13H ---- | APP | |MS-DOS| |BIOS| ----- ------ ---- With 32-Bit Disk Access, Windows no longer has to go through two mode transitions--one mode to get to the BIOS and the other mode to get back. Only two mode switches per INT13H call, rather than four, are now being performed. 32-BIT DISK ACCESS SUPPORT FOR NON-WINDOWS APPLICATIONS ======================================================= Sometimes Windows shows an adequate amount of free memory and large Windows-based applications run just fine, yet an "Out of Memory" message is generated when a non-Windows application is started. Also, in spite of the available memory, Windows-based applications may slow down and constantly access the hard disk after a non-Windows application is started. These discrepancies occur because of the difference between virtual memory (which is often large) and physical memory (RAM, which is usually limited). On a given machine, virtual memory might be four times the size of RAM. But, while virtual memory works well for Windows-based applications, it doesn't always meet all the system's memory needs for MS-DOS-based applications. Because each non-Windows application runs in its own virtual machine, each application takes up 640K or more of virtual memory. When the virtual machine is actually running, all of the program code needs to occupy RAM. Parts of the non-Windows application cannot be paged out while keeping other parts in RAM, as is the case with Windows-based applications. The virtual machine in which the non-Windows application runs must be treated as a single block. This is true even if the application is currently inactive in the background. With Windows-based applications, most of the program remains resident on the hard disk, while only the parts that are actually being used are loaded in RAM. Problems occur when Windows tries to do this with non-Windows-based applications. If a part of the application that is not currently being used--a data buffer, for example--is paged out, it can always be read back in whenever the application needs to access it. However, if the application makes a call to MS-DOS to read some data from the disk into a buffer, MS-DOS starts handling the call by making a call to INT13H to talk to the BIOS, which in turn talks to the hard disk controller, resulting in the transfer of data into the buffer. So when the application needs to transfer the page into the buffer, which is currently out on disk, the application tries to call MS-DOS to read the page. Because MS-DOS is already occupied, the application can't call MS-DOS; and MS-DOS is not reentrant, so the second call from the application fails. Nor can the application have the page read by calling the BIOS, because the BIOS is also in the middle of a call, so it can't be reentered either. This situation results in a type of deadlock: the application can't let the current call finish until the page is put in the buffer, but the page cannot be placed in the buffer until the current call finishes. The only way to ensure that this deadlock situation does not occur is to make sure that Windows never has to page anything in while the application is in the middle of an MS-DOS or BIOS call. Because Windows cannot predict ahead of time what the application will try to access, the only way to be 100-percent safe from deadlocking is to make sure everything the application might try to access is already in RAM (that is, never paged out to disk). In other words, all 640K-plus of the virtual machine in which the non-Windows application is running has to remain resident in RAM, thereby using up a lot of physical memory. Running several non-Windows-based applications at once uses large amounts of RAM, so you may soon end up with only a small amount of free RAM left for everything else you're trying to do, such as run Windows-based applications. When you check the Program Manager About dialog box (from the Help menu), it shows that you have plenty of memory--virtual memory--and you do. But if you try to start another non-Windows application, which requires yet another 640K of RAM, the application won't start. So, Windows starts running sluggishly and/or may generate the "Out of Memory" message. So how does 32-Bit Disk Access help? Windows 3.0 offered a contiguous paging file (which is created with Swapfile) for any pages using the INT13H BIOS calls. Windows 3.1 handles the same task by making calls to the 32-Bit Disk Access system. Unlike MS-DOS or the BIOS, the 32- Bit Disk Access system can queue up multiple requests and is completely reentrant. Windows no longer needs to rely on MS-DOS or the BIOS; so regardless of what the application is doing, Windows can always page calls in from the hard disk. Free from a potential deadlock situation, Windows 3.1 can now make the virtual machines that are running completely pageable. Non-Windows-based applications no longer need to take up so much RAM, since they can now use virtual memory the way Windows-based applications do. When Windows needs some RAM space, it can now page out pieces of these virtual machines. With Windows 3.1 and 32-Bit Disk Access, you can run multiple non- Windows-based applications and Windows-based applications without generating an "Out of Memory" message. When the About box tells you that you have 14 MB of memory, you can actually use all 14 MB for running your applications, whether they are Windows or non-Windows. Improved Performance for Non-Windows Applications Under Windows --------------------------------------------------------------- In the previous example, we saw how 32-Bit Disk Access in Windows can page non-Windows-based applications to free up enough RAM for those applications when they need to use it. The 32-Bit Disk Access feature also improves Windows performance all around, making the system run much more quickly. Switching between non-Windows-based applications by pressing ALT+TAB is faster with 32-Bit Disk Access. Without 32-Bit Disk Access, a non- Windows application can only be swapped out to disk if it is configured to not run in the background. This means when you press ALT+TAB to switch to such an application, Windows has to read the entire program into RAM, causing the task switching to take a long time. When Windows is paging using 32-Bit Disk Access, Windows can load in just the small amount of information that the application is actually using, so task switching becomes almost instant. And, since only a small part of the application needs to be in RAM at one time, Windows may not have to access the hard disk at all. THE COMPONENTS OF THE 32-BIT DISK ACCESS SYSTEM =============================================== The 32-Bit Disk Access system is composed of the following 386 enhanced mode virtual devices: - WDCTRL, which is the 32-Bit Disk Access device that talks to standard Western Digital 1003 or ST506 hard disk controllers (about 90 percent of the installed base). WDCTRL is only installed if Setup detects a compatible hard disk controller. - BlockDev, which coordinates calling block I/O services between devices and the 32-Bit Disk Access devices that provide those services for specific hard disk controllers. BlockDev is always installed. - PageFile, which handles the virtual memory paging file and calls through BlockDev if any 32-Bit Disk Access devices are available. PageFile is always installed. - INT13, which traps and emulates INT13H BIOS calls by calling BlockDev. INT13 is only installed if at least one 32-Bit Disk Access device is present. Because WDCTRL is the only 32-Bit Disk Access device included in the Windows box, the standard Windows components only support 32-Bit Disk Access for Western Digital-standard controllers. When you run Setup, it automatically detects these controllers and adds the following lines to the [386Enh] section of your SYSTEM.INI file: device=*int13 device=*wdctrl If you want to disable 32-Bit Disk Access, start the Control Panel and choose the 386 Enhanced icon, or comment the lines out of your system by placing a semicolon (;) at the beginning of both lines. You do not need to delete any files from your hard disk, as the 32-Bit Disk Access devices are contained within the file WIN386.EXE. 32-BIT DISK ACCESS AND HARD DISK PROTECTION =========================================== Microsoft identified machines where the use of WDCTRL can stop the system. Usually, this is caused by hard disk controllers that appear to be Western Digital 1003 compatible but are really not. WDCTRL has been put though rigorous testing to make sure it is as safe as possible, and is designed with a built-in safety measure--every time it starts, it performs elaborate tests to make sure it can communicate in the same language as the hard disk controller before it attempts to read and write data. WDCTRL starts testing by taking a peripheral look at some data on the hard disk for tell-tale traces of a Western Digital 1003-compatible controller. If the controller passes that test, WDCTRL then starts calling up larger pieces of data to try to elicit the correct response. Finally, after much redundant checking, WDCTRL tries actually reading data from the disk. If it is able to read data, WDCTRL then tries to write data and read it back. Only after the read/write test is passed does WDCTRL continue and start Windows, reassured that it will not cause any catastrophic errors on the hard disk. However, there are still a few exceptions. There are drives that appear to be WD1003 compatible but are not, and which cannot be detected by WDCTRL. In addition, there can be problems even with compatible controllers on some portable computers, specifically those that power down the hard disk to conserve power without telling the running software. If the disk is powered down and then back up while it is being tracked by WDCTRL, the tracking information will be incorrect, and serious damage can result. For these reasons, 32-Bit Disk Access is not turned on by default. When you install Windows, 32- Bit Disk Access is disabled until you make the decision to enable it through Control Panel. Only original equipment manufacturers (OEMs) who preinstall Windows 3.1 on a 100-percent-compatible system can turn 32-Bit Disk Access on before the user receives the system without jeopardizing the user's hard disk. When something does go wrong, WDCTRL may do different things, depending on where it is in its verification code. The initial tests have reported WDCTRL as extremely safe. The controllers that WDCTRL fails with are considered incompatible with 32-Bit Disk Access, so WDCTRL simply does not load when it senses these unsupported controllers. This procedure is invisible to the user; he or she just won't receive the benefits of 32-Bit Disk Access. If WDCTRL fails a test after it is installed, Windows displays an error message that warns that something is wrong, most likely that the hard disk might have been damaged, and advises to restart the machine (so that WDCTRL does not load, and 32-Bit Disk Access is disabled). THIRD-PARTY 32-BIT DISK ACCESS DEVICES ====================================== Windows 3.1 ships with only one 32-Bit Disk Access device--WDCTRL. However, Microsoft is working with most of the major hardware and software vendors to help them design 32-Bit Disk Access devices for their products. Concerns regarding distribution and quality of testing for these third-party devices are currently being addressed. ---------------------------------------------------------------- ------ TO OBTAIN THIS APPLICATION NOTE =============================== - On CompuServe, GEnie, and Microsoft OnLine, Application Notes are located in the Microsoft Software Library. You can find WW0530 in the Software Library by searching on the word WW0530, the Q number of this article, or S13374. WW0530 is a compressed, self-extracting file. After you download WW0530, run it to extract the file(s) it contains. - Application Notes are available by modem from the Microsoft Download Service (MSDL), which you can reach by calling (206) 936-6735. This service is available 24 hours a day, 7 days a week. The highest download speed available is 14,400 bits per second (bps). For more information about using the MSDL, call (800) 936-4200 and follow the prompts. To obtain WW0530, download WW0530.EXE. WW0530.EXE is a compressed, self-extracting file. After you download WW0530, run it to extract the file(s) it contains. - On the Internet, Application Notes are located on the Microsoft anonymous ftp server, which you can reach by typing "ftp ftp.microsoft.com" (without the quotation marks) at the ">" command prompt. - You can have this Application Note mailed or faxed to you from the automated Microsoft FastTips Technical Library, which you can call 24 hours a day, 7 days a week at (800) 936-4200. NOTE: The FastTips Technical Library is available only to customers within the U.S. and Canada. - If you are unable to access the source(s) listed above, you can have this Application Note mailed or faxed to you by calling Microsoft Product Support Services Monday through Friday, 6:00 A.M. to 6:00 P.M. Pacific time at (206) 637-7098. If you are outside the United States, contact the Microsoft subsidiary for your area. To locate your subsidiary, call Microsoft International Sales Information Center at (206) 936-8661. KBCategory: kbother kbfile kbappnote KBSubcategory: Additional reference words: appnote 3.10 win31 Windows 3.1 Err Msg: Call to Undefined Dynalink Article ID: Q84795 ---------------------------------------------------------------- ---- The information in this article applies to: - Microsoft Windows operating system versions 3.1, 3.11 ---------------------------------------------------------------- ---- SUMMARY ======= When you run Microsoft Windows, incorrect or outdated dynamic link library (.DLL) files can cause the following error message: Call to Undefined Dynalink This article discusses several software products and files that can cause this error message with outdated files, including: - Access Pack for Microsoft Windows - Ace File Database - Artisoft LANtastic for Windows - LaserTools PCPanel - Microsoft Bookshelf - Microsoft Dr. Watson - Microsoft LAN Manager - Microsoft printer drivers - Microsoft SHELL.DLL file (Program Item Properties dialog) - Powersoft PowerBuilder - Novell NetWare utilities MORE INFORMATION ================ Access Pack for Microsoft Windows --------------------------------- After you install Access Pack for Microsoft Windows (available on the Windows Driver Library [WDL]), you may receive the "Call To Undefined Dynalink" error message when you try to run one of the Access Pack utilities. The error occurs because one or more of the following conditions exist: - The MOUSE.DRV= entry in the [BOOT] section of the SYSTEM.INI file points the wrong mouse driver. - The KEYBOARD.DRV= entry in the [BOOT] section of the SYSTEM.INI file points the wrong keyboard driver. - The Access Pack mouse driver (AP-MOU.DRV) in your Windows SYSTEM subdirectory is not the current version. - The Access Pack keyboard driver (typically AP-KBD.DRV, AP-KBDHP.DRV, or AP-KBDOL.DRV) in your Windows SYSTEM subdirectory is not the current version. If the MOUSE.DRV= entry in the [BOOT] section of the SYSTEM.INI file points to anything other than AP-MOU.DRV, change it to read MOUSE.DRV=AP-MOU.DRV, and then copy the AP-MOU.DRV file from the WDL disk to your Windows SYSTEM subdirectory. For example, if Windows is installed in the C:\WINDOWS directory and your WDL disk is in drive A, type the following at the MS-DOS command prompt and then press ENTER: copy a:\ap-mou.drv c:\windows\system If the KEYBOARD.DRV= entry in the [BOOT] section of the SYSTEM.INI file points to KEYBOARD.DRV, KBDHP.DRV, or KBOLI,DRV, change it to point to the appropriate Access Pack keyboard driver (AP-KBD.DRV, AP-KBDHP.DRV, or AP- KBDOL.DRV), and then copy the corresponding file from the WDL disk to your Windows SYSTEM subdirectory. For example, if Windows is installed in the C:\WINDOWS directory, your WDL disk is in drive A, and you change your KEYBOARD.DRV= entry from KEYBOARD.DRV to AP-KBD.DRV, type the following at the MS-DOS command prompt and then press ENTER: copy a:\ap-kbd.drv c:\windows\system NOTE: If your current keyboard driver is not AP-KBD.DRV, AP-KBDHP.DRV, or AP-KBDOL.DRV, contact your mouse vendor to determine if it is compatible with the Microsoft Mouse driver. If it is not, your mouse vendor may provide Access Pack-compatible drivers. If the MOUSE.DRV= entry in the [BOOT] section of the SYSTEM.INI file points to the Access Pack mouse driver (AP-MOU.DRV), replace the file with the correct mouse driver from the WDL disk. For example, if Windows is installed in the C:\WINDOWS directory and your WDL disk is in drive A, type "copy a:\ap-mou.drv c:\windows\system" (without the quotation marks) at the MS-DOS command prompt and then press ENTER. If the KEYBOARD.DRV= entry in the [BOOT] section of the SYSTEM.INI file points to AP-KBD.DRV, AP-KBDHP.DRV, or AP-KBDOL.DRV, replace the file with the correct keyboard driver from the WDL disk. For example, if Windows is installed in the C:\WINDOWS directory, your WDL disk is in drive A, any you are using AP-KBD.DRV, type "copy a:\ap-kbd.drv c:\windows\system" (without the quotation marks) at the MS-DOS command prompt and then press ENTER. NOTE: If the Access Pack keyboard drivers are installed properly, most Access Pack features work correctly even if an improper mouse driver is installed. However, the MouseKeys and SerialKeys features are disabled, and you cannot run the Access Utility to customize the settings or view Help. For more information about how to run Access Pack for Microsoft Windows with unsupported hardware, query on the following words in the Microsoft Knowledge Base: using and access pack and unsupported hardware For more information, query on the following words in the Microsoft Knowledge Base: access.wri and wdl Ace File -------- The database program Ace File version 1.0 for Windows may cause a "Call to Undefined Dynalink" error message when you choose Open from the File menu and select Database. Ace Software can be contacted at (408) 451-0100. There is currently no solution to this problem. Contact Ace Software for an upgrade. Artisoft LANtastic for Windows ------------------------------ You may receive a "Call to Undefined Dynalink" error message or "FatalExit code=0x0404" if you are running an earlier version of the LANtastic version 3.0 install program WINSTALL.EXE. These error messages occur if the date of the WINSTALL.EXE file is earlier than 10/23/91. They do not occur if you use Windows 3.1 to update an existing version of Windows 3.0 that was already configured for the network. To correct this problem, obtain an updated version of the WINSTALL.EXE file by contacting LANtastic technical support. Lasertools PCPanel ------------------ When running under Windows 3.1, the LaserTools utility Printer Control Panel (PCPanel) may cause a "Call to Undefined Dynalink" error message. PCPanel is produced by LaserTools and ships with some NEC printers, the Texas Instruments MicroLaser, and Okidata Lasers. PCPanel looks for HPPCL or PostScript data being sent to the printer and then modifies the data being sent. This function may not work correctly with Windows 3.1 and may cause error messages and/or printing problems. This problem has been corrected in version 2.3 of PCPanel, and is available from LaserTools. To Obtain Version 2.3: Current owners of PCPanel can receive a new copy by calling LaserTools at (800) 995-6487. NEC Silentwriter owners who purchased their printer after January 1, 1992 receive this upgrade free of charge. Silentwriter owners who purchased their printers before January 1, 1992 are charged a $15.00 handling and shipping fee. The software upgrade center accepts popular credit cards or a check by mail. The mailing address is: NEC Redemption Center P.O. Box 3503, Wallingford, CT 06494 The upgrade package includes installation instructions, and also revised .WPD files for Silentwriter Model 95 usage with Windows 3.1. This 800 number is for SOFTWARE UPGRADES only, and is not a technical support center. NEC Bulletin Board System (BBS): (508) 635-4706 Temporary Workaround: Until you receive the updated version of PCPanel, you can work around the problem by removing PCPanel. The following paragraph is taken from the "Printer Control Panel Owner's Manual": If you install Printer Control Panel for Windows 3.0, certain information is added to your Windows 3.0 files. If you wish to remove that information from your working copy of Windows 3.0, you must use the Re-INSTALL program to do so. Simply choose the Remove PCPANEL From Windows selection from the Windows 3.0 menu in INSTALL. You'll want to remove Printer Control Panel as an application in Windows 3.0 also. Refer to Appendix A. NOTE: Appendix A shows how to delete the PCPanel icon. According to LaserTools technical support, you can remove the Printer Control Panel with the following steps: 1. In the PCPrinter or LaserTools directory, type: install /u 2. Select "Skip this step without modifying the AUTOEXEC.BAT." 3. Choose Remove Printer Control Panel For Windows. NOTE: The MS-DOS-based TSR can remain in place. Microsoft Dr. Watson -------------------- If you have an earlier version of TOOLHELP.DLL (dated before 3-10-92) in your Windows directory, you will receive a "Call to Undefined Dynalink" error message. When earlier versions of Dr. Watson were installed under Windows 3.0, DRWATSON.EXE and TOOLHELP.DLL were installed into the Windows directory. When Dr. Watson version 0.80 is installed during the installation of Windows 3.1, DRWATSON.EXE is installed into the Windows directory, and TOOLHELP.DLL is installed into the Windows\SYSTEM directory. To correct this problem, delete the TOOLHELP.DLL file from the Windows directory. NOTE: This problem can also occur with an earlier version of SHELL.DLL (see below), OLECLI.DLL, OLESVR.DLL, and COMMDLG.DLL. All these files should be located in the Windows\SYSTEM directory and should be dated 3/10/92 or later. Microsoft LAN Manager --------------------- If you receive a "Call to Undefined Dynalink" error message when starting Windows 3.1 with Microsoft LAN Manager loaded, you most likely have outdated versions of LAN Manager network dynamic link libraries (DLLs). Using the proper versions of the DLLs corrects the problem. Normally, the original DLLs, NETAPI.DLL and PMSPL.DLL, are in the NETPROG subdirectory of the LAN Manager directory and they are updated in place. The original DLLs are backed up to NETAPI.BAK and PMSPL.BAK. To prevent the destruction of the original files when multiple installations or updates take place, the files are not updated if the .BAK files are already present. The problem can result from a variety of causes: - If the backup files are present but the DLLs are out of date, then the files are not updates and the out-of-date DLLs are used. - If the LAN Manager directory isn't found during setup, but the out-of-date DLLs are in the path, they are used. - If Windows was set up for a different network, and you changed to LAN Manager 2.0 from Windows Setup in maintenance mode, the drivers aren't copied correctly. MS-DOS maintenance mode Setup copies the files correctly. The LAN Manager 2.0 files are called NETAPI20.DLL and PMSPL20.DLL on the Windows disks. They may be present in the system directory in some cases. If the files are not, they can be expanded from the Windows disks using the EXPAND utility. These files should be copied to the NETPROG subdirectory of the LAN Manager directory and renamed to NETAPI.DLL and PMSPL.DLL. Note that these LAN Manager 2.0 DLLs should NOT be used with LAN Manager 2.1. The DLLs and drivers provided with LAN Manager 2.1 should be used. If the error message results on a LAN Manager 2.1 configuration, NETAPI.DLL and PMSPL.DLL may have been overwritten by LAN Manager 2.0 libraries and should be expanded from the LAN Manager 2.1 disks. This can occur if you specified LAN Manager 2.0 as your network when installing Windows 3.1 and then changed to LAN Manager 2.1. This will happen most likely when using batch mode installations on dissimilar machines. If the .BAK files are larger than the .DLL files, then this has probably occurred. Microsoft SHELL.DLL File (Program Item Properties Dialog) --------------------------------------------------------- Choosing the Change Icon button in the Program Item Properties dialog box in Windows 3.1 may cause the "Call to Undefined Dynalink" error message if the SHELL.DLL file is dated earlier than 3-10-92: To update the SHELL.DLL file: 1. Expand the SHELL.DLL file from the original Windows 3.1 disks (Disk 4 of the 1.44-MB 3.5-inch disk set, or Disk 5 of the 1.2- MB 5.25-inch disk set) to the Windows\SYSTEM directory. To do this, at the MS-DOS command prompt, type the following expand [drive1]:\shell.dl_ [drive2]:\windows\system\shell.dll where "drive1" is the drive designating the location of the Windows 3.1 disk, and "drive2" is the drive on which Windows 3.1 is installed. 2. Remove any SHELL.DLL files that may exist in the Windows directory. Microsoft Printer Drivers ------------------------- The "Call to Undefined Dynalink" error message may occur if Windows version 3.1 attempts to use a Windows version 3.0 printer driver. You must remove the Windows version 3.0 printer driver and install the Windows version 3.1 printer driver to correct the problem. NOTE: You must remove duplicate printer driver entries from the Installed Printers list or you will be unable to install a new Windows version 3.1 printer driver from the Windows disks. Be sure to search all drives and directories for outdated printer drivers. This is especially important if you are running on a network, where printer drivers may be stored in multiple directories. Novell NetWare Utilities ------------------------ When you start Windows for Workgroups, the wallpaper appears, the "Call to Undefined Dynalink" error message flashes on the screen, and you return to an MS-DOS prompt. If you have the Novell NetWare Tools for Windows installed and their files are dated earlier than 1992 you need to update the utilities. Powersoft Powerbuilder ---------------------- Using Powersoft PowerBuilder 1.0a with Windows 3.1 may result in a "Call to Undefined Dynalink" error message. PowerBuilder uses a custom version of TOOLHELP.DLL. This design is not compatible with the TOOLHELP.DLL file shipped with Windows 3.1. To run PowerBuilder successfully with Windows 3.1, please contact Powersoft for a PowerBuilder update. The products included here are manufactured by vendors independent of Microsoft; we make no warranty, implied or otherwise, regarding these products' performance or reliability. KBCategory: kbnetwork kberrmsg kbtlc kb3rdparty kbsetup KBSubcategory: wfw wfwg win31 Additional reference words: 3.10 3rdparty 3.11 acefile show up laser tools power builder dynamic link library dyna link handicapped handycapped disability accp.exe Creating a New SYSTEM.INI Without Third-Party Drivers Article ID: Q85560 ---------------------------------------------------------------- ------ The information in this article applies to: - Microsoft Windows operating system versions 3.1, 3.11 ---------------------------------------------------------------- ------ SUMMARY ======= You can use your original Windows disks to create a new SYSTEM.INI file for your specific hardware. This can be useful for troubleshooting purposes or for replacing a damaged or deleted SYSTEM.INI file. NOTE: As a precaution, you may want to start the Setup program with the original SYSTEM.INI file, and then press PRINT SCREEN so that you have a printed copy of the your settings. You can then use this as a reference when you reset them. MORE INFORMATION ================ To create a new SYSTEM.INI file that is configured for your specific hardware but does not contain any references to third-party device drivers, do the following: 1. Rename the SYSTEM.INI file to SYSTEM.BAK. 2. Expand the file SYSTEM.SR_ from the original Windows disks to the Windows directory with the following command: c:\windows\expand a:\system.sr_ c:\windows\system.ini NOTE: This file can be found on Disk 1 of the Windows 3.1 1.44-megabyte (MB) 3.5-inch disk set or on Disk 2 of the 1.2-MB 5.25-inch disk set. 3. Change to the Windows drive, and then change to the Windows directory. For example: c: cd \windows 4. Type "setup" (without the quotation marks) to start the MS-DOS-based portion of Windows Setup. 5. Select the correct hardware options for your system. (They are blank by default.) NOTE: For a list of valid choices, move your cursor to the blank field and then press ENTER. 6. Accept the changes. (At this point, you can have Setup copy new drivers if you want.) 7. Open the new SYSTEM.INI file in a text editor (for example, MS-DOS 5.0 Editor). Make the following changes to the SYSTEM.INI file: a. Add PROGMAN.EXE to the SHELL= line in the [Boot] section. b. Remove or remark out the Taskman.exe= line in the [Boot] section. c. To enable 32-bit disk access, add the following lines to the [386Enh] section: 32BitDiskAccess= device=*int13 device=*wdctrl Replace with On if you want 32-bit disk access enabled; replace it with Off if you do not want 32-bit disk access enabled. For more information about 32-bit disk access, see Appendix D in the Windows Resource Kit manual, or query on the following words in the Microsoft Knowledge Base: windows and 3.1 and 32-bit and disk and access 8. Start Windows. If you do not receive any errors, you have successfully re-created your SYSTEM.INI file. If you receive error S020 or S021, the SYSTEM.INI file you created may be corrupted. To correct this problem, do the following: a. Check for a duplicate SYSTEM.INI file by typing "dir c:\ system.ini /s" (without the quotation marks) at the MS-DOS command prompt. b. Run CHKDSK to check for lost allocation units by typing "chkdsk /f" (without the quotation marks) at the MS-DOS command prompt. c. Make sure your hard disk has sufficient free space. d. Delete the corrupted SYSTEM.INI file and then follow the steps outlined above again, starting with number 2. e. If all else fails, reinstall Windows. KBCategory: kbref kbtshoot kbtlc KBSubcategory: win31 Additional reference words: 3.10 3.11 recreate re-create system.src tshoot rebuild clean expanding system.bkp troubleshoot hardware system.tmp vanilla "how to create a new" third-party Control Panel .CPL Files and Icon Installation Article ID: Q86023 ---------------------------------------------------------------- -- The information in this article applies to: - Microsoft Windows operating system versions 3.1, 3.11 - Microsoft Windows for Workgroups versions 3.1, 3.11 ---------------------------------------------------------------- -- SUMMARY ======= This article describes the relationship of .CPL files and the icons that appear in the Microsoft Windows and Microsoft Windows for Workgroups Control Panel. This article includes information on the following: - A general description of .CPL files - How to replace Control Panel icons - A list of the default .CPL files shipped with Windows - What to do if you receive a "Cannot Find Components" message - How to use the Windows 3.1 icons elsewhere - Multimedia settings in the CONTROL.INI file - Possible general protection (GP) faults in the Control Panel MORE INFORMATION ================ Description of .CPL Files ------------------------- You can add additional icons and functionality to the Control Panel in Windows 3.1 and Windows for Workgroups versions 3.1 and 3.11 by adding "installable" .CPL files. These .CPL files must be located in the Windows SYSTEM directory or the corresponding icon does not appear in the Control Panel. However multimedia .CPL files can be referenced in another directory by specifying a new path in the [MMCPL] section of the CONTROL.INI file. You should design and structure the .CPL file to conform to the CPLINFO specification as outlined in the Microsoft Windows Programmer's reference. Simply attaching a .CPL extension to a file of unspecified format doesn't work. The CPLINFO specification contains information concerning the icon, application or device name, identification numbers, and other data. NOTE: If VER.DLL is missing from the WINDOWS or Windows SYSTEM directory, only the 386 Enhanced icon and the Sound icon appear in Control Panel. Replacement of Control Panel Icons ---------------------------------- When you run the Control Panel in Windows 3.1 or Windows for Workgroups (WFWG), some of the icons may not display if the corresponding .CPL file is corrupt or missing. To correct this problem, you must expand the files from the Windows disks back to the Windows SYSTEM directory. Note that the network icon does not display if the network is not properly installed. This is not a problem with the MAIN.CPL, but with the network installation. Use the following steps to add a missing Control Panel icon: 1. Exit Windows. 2. Copy EXPAND.EXE from your Windows or WFWG disk to your WINDOWS directory. NOTE: EXPAND.EXE is located on Windows 3.1 disk 3 (both disk sizes), on WFWG 3.1 disk 8 (5.25) or disk 6 (3.5), and on WFWG 3.11 disk 6 (both disk sizes). 3. Put the Windows disk with the correct *.CP_ file in your floppy disk drive. Depending on the Windows version and disk size you have, *.CPL files are located on the following disks: Windows 3.1 3.5" Disk 5.25" Disk ------------------------------------- CPWIN386.CP_ Disk 1 Disk 1 DRIVERS.CP_ Disk 4 Disk 5 MAIN.CP_ Disk 4 Disk 5 SND.CP_ Disk 4 Disk 6 WFWG 3.1 3.5" Disk 5.25" Disk ------------------------------------- CPWIN386.CP_ Disk 2 Disk 2 DRIVERS.CP_ Disk 6 Disk 7 MAIN.CP_ Disk 3 Disk 5 SND.CP_ Disk 7 Disk 8 WFWSETUP.CP_ Disk 2 Disk 2 WFWG 3.11 3.5" Disk 5.25" Disk ------------------------------------- CPWIN386.CP_ Disk 2 Disk 2 DRIVERS.CP_ Disk 5 Disk 6 FAX.CP_ Disk 6 Disk 4 MAIN.CP_ Disk 3 Disk 3 SND.CP_ Disk 6 Disk 8 4. Type the following at the MS-DOS command prompt expand A:\xxxxx.CP_ C:\WINDOWS\SYSTEM\xxxxx.CPL where xxxxx is the name of the file and drive A is the drive containing the floppy disk with the .CPL files. 5. Reopen the Control Panel (it is not necessary to exit Windows because the Control Panel performs its search for .CPL files when it initializes). Default .CPL Files Shipped with Windows 3.1 ------------------------------------------- Windows 3.1 ships with the following four "installable" Control Panel objects. Compressed Expanded Name Size Name Size Icon ----------------------------------------------------------------- --- CPWIN386.CP_ 48841 CPWIN386.CPL 104816 Control Panel's 386 Enhanced Mode icon DRIVERS.CP_ 21385 DRIVERS.CPL 41440 Control Panel's Drivers icon for installing and removing Multimedia drivers MAIN.CP_ 89396 MAIN.CPL 148560 Control Panel's Color, Fonts, Ports, Mouse, Desktop, Keyboard, Printers, International Date/Time, Network (if installed) icons SND.CP_ 4986 SND.CPL 8192 Control Panel's Sound icon, which allows you to assign sounds to many system events NOTE: The Windows Driver Library disks include an additional .CPL file, SBPMIXER.CPL (file size 25792, dated 2/1/92), for computers with Creative Labs Sound Blaster Pro sound cards. This icon is an audio-mixing board for the Sound Blaster Pro. "Cannot Find Control Panel Components" Error Message ---------------------------------------------------- The Windows 3.1 or Windows for Workgroups 3.1 and 3.11 Control Panel (CONTROL.EXE) may return the following message upon execution: Cannot find the Control Panel components (files with .CPL extension). Verify that they are installed in your Windows SYSTEM directory. This error usually occurs when the .CPL files cannot be found in the SYSTEM directory, or if the files have become corrupt. First, you should confirm existence of the following .CPL files in your Windows SYSTEM directory: CPWIN386.CPL DRIVERS.CPL MAIN.CPL SND.CPL WFWSETUP.CPL <=== Windows for Workgroups version 3.1 only. If any file is missing, you need to expand it from your Windows disks. If all files are there, then it is possible that the files are corrupted. In this case you should exit Windows, delete all of the SYSTEM\*.CPL files, then expand each .CPL from your Microsoft Windows disks into your Windows SYSTEM subdirectory, as described in this article. Using a .CPL File Icon Elsewhere -------------------------------- The Windows version 3.1 Control Panel contains only one icon embedded in the executable file CONTROL.EXE. If an embedded icon from the Windows 3.0 CONTROL.EXE file is used as a replacement icon for a program item, a similar Windows 3.1 icon may be located in one of the Control Panel data files (*.CPL). Because of the modular structure of the Windows 3.1 Control Panel, most icons that were embedded in earlier versions of the CONTROL.EXE file have been moved to different associated data files located in the SYSTEM subdirectory. These files include CPWIN386.CPL, DRIVERS.CPL, MAIN.CPL, and SND.CPL. To use one of the icons placed in the .CPL files for a program item in Windows 3.1, use the following steps: 1. In Program Manager, select the program item whose icon needs to be changed. 2. From the File menu, choose Properties to open the Program Item Properties dialog box. 3. Choose the Change Icon button. 4. Type the appropriate .CPL filename in the File Name box, then choose the OK button. Multimedia Settings in the CONTROL.INI -------------------------------------- The [MMCPL] section of the CONTROL.INI file contains information which concerns the size and placement of the Control Panel window, the number of iconized applications in the Control Panel, and a path setting for multimedia .CPL files residing outside of the Windows SYSTEM subdirectory. The settings include: Setting Description -------------------------------------------------------- x= Horizontal window coordinate y= Vertical window coordinate h= Height in pixels w= Width in pixels numapps= The number of applications in the Control Panel In addition Microsoft Windows for Pen Computing may add the following lines to the [MMCPL] file: cppen=c:\windows\cppen.cpl cphw=c:\windows\cphw.cpl cprot=c:\windows\cprot.cpl cpcal=c:\windows\cpcal.cpl These entries allow the Control Panel to find .CPL file in subdirectories other than the Windows SYSTEM subdirectory. GP Faults in Control Panel -------------------------- If you experience general protection (GP) faults when opening Control Panel, it is likely that one of the .CPL files is corrupted or damaged. Please follow the instructions in the previous section of this article to replace the icon. REFERENCES ========== "Microsoft Windows Programmer's Reference, Volume3: Messages, Structures, and Macros," version 3.1, pgs. 260, 543-549. "Microsoft Windows for Pen Computing: Programmer's Reference, Windows Software Development Kit," version 3.1, pgs. 288-289. KBCategory: kbmm kbdisplay kbsound kberrmsg KBSubcategory: win31 wfw wfwg winshell Additional reference words: gpf 3.0 3.10 lost loss gone penwin *.cpl program item properties adding soundblaster Windows Err Msg: Fault in MS-DOS Extender Article ID: Q87239 ---------------------------------------------------------------- ---- The information in this article applies to: - Microsoft Windows operating system versions 3.1, 3.11 - Microsoft Windows for Workgroups versions 3.1, 3.11 ---------------------------------------------------------------- ---- SUMMARY ======= This article discusses the following two error messages with stack dump: Bad Fault in MS-DOS Extender -and- Standard Mode: Fault outside of MS-DOS Extender Raw fault frame: EC=0344 CS=031F IP=85E2 AX=001D BX=0005 CX=1800 DX=155F SI=0178 DI=0178 BP=016E DS=027F ES=027F SS=027F SP=0166 MORE INFORMATION ================ Bad Fault in MS-DOS Extender ---------------------------- This error message occurs when the fault handler dispatcher in DOSX.EXE generates another cascaded fault while trying to handle a protected-mode exception. This error is usually caused by one of the following factors: - HIMEM.SYS is unable to control the A20 line. - DOS=HIGH is not functioning properly (related to HIMEM.SYS control). - The RAM, static RAM (SRAM), single in-line memory module (SIMM), or dynamic RAM (DRAM) chips are not functioning properly. - You are running DR DOS. - The third-party memory manager is not configured correctly. - You have an old, out-of-date ROM BIOS. - Your CMOS settings are incorrect. - Your Windows files are old or corrupted. To test this, create a new directory on the hard drive, and install Windows in that directory. - Your disks are corrupted. - Your system is infected with the Form, Forms, Noint, or Yankee Doodle virus. Standard Mode Fault Outside MS-DOS Extender ------------------------------------------- This error message occurs when the Kernel generates a processor exception during initialization (before it has installed its own exception handlers) or when the Kernel determines that it cannot handle an exception. The causes are the same as those for the "Fault in MS-DOS Extender" error. Meaning of Stack Dump and Raw Fault Frame ----------------------------------------- The portion of the display labeled "Stack Dump:" should always be the same and does not carry much valuable information. The portion of the display labeled "Raw Fault Frame" EC=0344 CS=031F IP=85E2 AX=001D BX=0005 CX=1800 DX=155F SI=0178 DI=0178 BP=016E DS=027F ES=027F SS=027F SP=0166 contains information generated by the 80286 or 80386 processor in response to the original fault. The meaning of these settings is as follows: Setting Meaning ------- ------- EC=xxxx An exception code produced by the processor in response to the original fault. IP=xxxx The program counter of the faulting instruction (8086 register "IP"). CS=xxxx The code segment of the faulting instruction. If this is "0053" or "005B", the (original) fault was in DOSX.EXE, the "MS-DOS Extender." FL=xxxx The flag's image at the time of the original fault. SP=xxxx The stack pointer at the time of the original fault. SS=xxxx The stack segment at the time of the original fault. If this is "004B", the fault occurred on a stack belonging to DOSX.EXE. The CS and IP sections tell at what point in the faulting program that the original problem was detected. KBCategory: kbother kbdisplay kberrmsg KBSubcategory: wfw wfwg win31 Additional reference words: 3.10 money Windows Err Msg: The Microsoft Windows 32-Bit Disk... Article ID: Q88410 ---------------------------------------------------------------- ---- The information in this article applies to: - Microsoft Windows operating system versions 3.1, 3.11 - Microsoft Windows for Workgroups versions 3.1, 3.11 ---------------------------------------------------------------- ---- SYMPTOMS ======== When you start Microsoft Windows or Windows for Workgroups, you receive one of the following error messages: - The Microsoft Windows 32-bit disk driver (WDCTRL) cannot be loaded. There is unrecognizable disk software installed on this computer. -or- - The Microsoft Windows 32-bit disk driver (WDCTRL) cannot be loaded. There is a conflict with another virtual device. -or- - This application has tried to access the hard disk in a way that is incompatible with the Windows 32-bit disk access feature (WDCTRL). This may cause the system to become unstable. -or- - The Microsoft Windows 32-bit disk driver (WDCTRL) cannot be loaded. There is unrecognizable disk software installed on this computer. The address that MS-DOS uses to communicate with the hard disk has been changed. Some software, such as disk-caching software, changes this address. If you aren't running such software, you should run a virus-detection program to make sure the computer is virus free. To continue starting Windows without using the 32-bit disk driver, press any key. CAUSE ===== The above error messages can be displayed when: - The system is infected with a virus. -or- - You are running the PC Cillin anti-virus program. -or- - The Device=*WDCTRL entry occurs more than once in [386Enh] section of the SYSTEM.INI file. -or- - You are using a third-party replacement for WDCTRL and you have reinstalled Windows. -or- - You are loading a real-mode driver in the CONFIG.SYS file that alters the manner in which Windows monitors and controls INT 13h. -or- - Using a QD6500A VLB controller that was installed in Windows 3.1 and then installing WFW 3.11. After the install there will be an *int13, WDCTRL, and QDICTRL.386 in [386Enh] section of system.ini. QDICTRL.386 alone breaks the IFSHLP.SYS. Remark out the QDICTRL.386 line and use the WDCTRL. Leave the QD6500.SYS line in the config.sys. MORE INFORMATION ================ The System Is Infected with a Virus ----------------------------------- During startup, if Windows detects that a particular undocumented interrupt has been hooked by a "program" it does not recognize, Windows displays one of the above messages. Quite often, the program it does not recognize is a virus. The Stoned, Bloomington, and Form viruses can cause these errors. To correct this problem, run virus-detection software to detect and remove any viruses from the hard disk drive. The Anit-CMOSa virus will also cause this; McAfee v2.14 will find, but not cure it. You Are Running the PC Cillin Anti-Virus Program ------------------------------------------------ PC Cillin anti-virus software can cause these error messages. For more information on PC Cillin and problems with Windows, query on the following words in the Microsoft Knowledge Base: pc cillin and windows You Are Using a Third-Party Replacement for WDCTRL and You Have Reinstalled Windows ------------------------------------------- If you have a Western Digital Caviar 2540 hard disk drive (or another model that uses WDCDRV.386 as a replacement for WDCTRL) and you reinstall Windows to the same directory, Windows puts WDCTRL in the SYSTEM.INI file but does not remove the third-party driver. Removing the DEVICE=*WDCTRL entry from the SYSTEM.INI file corrects this problem. You are Loading a Real-Mode Driver in the CONFIG.SYS File That Alters the Manner in Which Windows Monitors and Controls INT 13h ---------------------------------------------------------------- Real-mode drivers that manipulate the way in which INT13 calls are handled may prevent the 32-bit disk access driver from loading. KBCategory: kb3rdparty kberrmsg KBSubcategory: win31 wfw wfwg Additional reference words: 3rdparty err msg 3.10 3.11 scanning anti-virus unrecognized 32 bit disk access 32-bit diskaccess mcafee mcaffee pccillin pccillan cillan forms form michelangelo monkey [mon] stealth ripper Over the Top twice genb jenb jenp WW0654: Windows 3.1 and Serial Communications Article ID: Q92447 ---------------------------------------------------------------- ----- The information in this article applies to: - Microsoft Windows operating system versions 3.1, 3.11 ---------------------------------------------------------------- ----- Microsoft has an Application Note, "Windows 3.1 and Serial Communications" (WW0654), that provides information about serial communications in the Windows 3.1 environment. This Application Note includes a discussion of improvements in Windows 3.1, a conceptual overview, and a discussion of why conflicts occur. You can obtain this Application Note from the following sources: - CompuServe, GEnie, and Microsoft OnLine - Microsoft Download Service (MSDL) - The Internet (Microsoft anonymous ftp server) - Microsoft FastTips Technical Library - Microsoft Product Support Services For complete information, see the "To Obtain This Application Note" section at the end of this article. THE TEXT OF WW0654 ================== ================================================================ ====== Microsoft(R) Product Support Services Application Note (Text File) WW0654: WINDOWS 3.1 AND SERIAL COMMUNICATIONS ================================================================ ====== Revision Date: 10/92 No Disk Included The following information applies to Microsoft Windows(TM) version 3.1. -------------------------------------------------------------------- | INFORMATION PROVIDED IN THIS DOCUMENT AND ANY SOFTWARE THAT MAY | | ACCOMPANY THIS DOCUMENT (collectively referred to as an | | Application Note) IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY | | KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO | | THE IMPLIED WARRANTIES OF MERCHANTABILITY AND/OR FITNESS FOR A | | PARTICULAR PURPOSE. The user assumes the entire risk as to the | | accuracy and the use of this Application Note. This Application | | Note may be copied and distributed subject to the following | | conditions: 1) All text must be copied without modification and | | all pages must be included; 2) If software is included, all files | | on the disk(s) must be copied without modification [the MS-DOS(R) | | utility DISKCOPY is appropriate for this purpose]; 3) All | | components of this Application Note must be distributed together; | | and 4) This Application Note may not be distributed for profit. | | | | Copyright 1992 Microsoft Corporation. All Rights Reserved. | | Microsoft and MS-DOS are registered trademarks and Windows | | is a trademark of Microsoft Corporation. | | IBM, Micro Channel, and PS/2 are registered trademarks of | | International Business Machines Corporation. | | Logitech is a trademark of Logitech, Inc. | ---------------------------------------------------------------- ---- INTRODUCTION ============ This Application Note provides information about serial communications in the Microsoft Windows version 3.1 operating system environment. The first section, "What's New in Windows Version 3.1," gives an overview of improvements in Windows 3.1. The section "Conceptual Overview" explains basic and advanced concepts in serial communications, including port addresses, device contention, and so forth. The section "Why Conflicts Occur" discusses the most common reasons why you may experience difficulties with serial communications, and the section "How to Resolve Conflicts" explains what to do once you have identified the problem. If you need help with a specific problem, you may want to start by reading the "Troubleshooting" section. WHAT'S NEW IN WINDOWS VERSION 3.1 ================================= Here are some highlights about improvements in how Windows 3.1 handles serial communications. Performance Improvements ------------------------ - Windows 3.1 supports the high-speed 16550AFN UART buffer; Windows 3.0 does not. (The 16550AFN buffer is supported for Windows-based applications only.) - Windows 3.1 supports baud rates of up to 57.6K. (You may need to update your application to take advantage of these higher baud rates.) Some users experienced lockups during high-speed, full- duplex transfers while using Windows 3.0. These problems are resolved in Windows 3.1. - Windows 3.1 has a new serial driver interface that allows data to be passed in blocks, instead of one character at a time. (Each block is treated as a single character.) This means faster data throughput and fewer transmission errors. Windows 3.0 passes data one character at a time. - Windows 3.0 uses a "constant polling" method to determine when serial ports are occupied. Windows 3.1 uses the EnableCommNotification API; this enables applications to directly notify Windows of serial events, thereby increasing overall system performance. Better Support for Your Ports ----------------------------- - Windows 3.1 provides better support for COM ports 3 and 4. You can now configure these ports by using Windows Control Panel. - Windows 3.1 fully supports IRQ sharing; Windows 3.0 does not. (To take advantage of this feature, your PC must have Extended Industry Standard Architecture (EISA) or Micro Channel(R) Architecture (MCA), or you must have a serial I/O card that supports IRQ sharing.) CONCEPTUAL OVERVIEW =================== This section provides a general introduction to the subject of serial communications and explains many of the concepts and issues that are discussed throughout the "Windows 3.1 and Serial Communications" Application Note. SERIAL VS. PARALLEL PORTS ========================= Input/output (I/O) ports provide the means for your PC to send or receive data through external devices such as modems, printers, fax machines, and so forth. Virtually all PCs have both parallel and serial ports. There are several distinctions between serial and parallel I/O ports. Parallel ports are generally used only for printers, which is where the name LPT, for line printer, originates. Parallel ports transmit data in complete bytes, and in most cases they handle outgoing data only; they cannot receive information. (The IBM[R] PS/2[R] parallel ports are bidirectional; in addition, you can use certain peripherals, such as network card adapters, to enable your ports to transmit data bidirectionally.) You do not configure parallel ports; they are preconfigured for your machine. Serial ports are generally used for communications, or COM devices, which include serial printers, modems, fax machines, and so forth. Serial ports are capable of both sending and receiving data. You can configure settings--such as parity, stop bits, and data length--for your serial ports. (In Windows, you can specify these settings by using Control Panel.) Serial ports transmit data one bit at a time, sequentially (or serially). PORT ADDRESSES AND IRQS ======================= Every time you start your PC, your system BIOS checks your COM ports to see what serial devices are installed on your PC and posts this information to the system BIOS data area (BDA). Windows "reads" the BDA, and uses the default interrupt request line (IRQ) for each device that is registered there. Usually, each COM port requires a unique IRQ to communicate with your PC. Certain PCs and some I/O cards support IRQ sharing. NOTE: Some earlier BIOS versions may not check for devices on COM ports 3 and 4. If you have devices installed on COM port 3 or 4 and your system BIOS does not recognize these ports, you need to register the addresses for COM3 and COM4 by using Windows Control Panel. This is explained in the procedure "To register a serial device" later in this Application Note. How Should My COM Ports Be Configured? -------------------------------------- Generally, PCs come with built-in ports COM1 and COM2 preset to the following values: Port Address IRQ ---------------------------- COM1 03F8 4 COM2 02F8 3 In most cases, the default values for COM ports 1 and 2 should work for your system. You can view your COM port settings by using Windows Control Panel. Most PCs do not have built-in ports for COM3 and COM4. The default settings for these additional ports are listed here: Port Address IRQ ------------------------------------ COM3 03E8 4 COM3 (PS/2) 3220 3 COM4 02E8 3 Because COM1 and COM3 both use IRQ4 as the default, and COM2 and COM4 both use IRQ3, you may need to reassign the IRQ if you use serial devices (such as a fax card or modem) on COM ports 3 or 4. You can reassign IRQs by using Control Panel. For more information, see the procedure "To reassign the IRQ" later in this Application Note. (You do not need to reassign the IRQ if you have an MCA or EISA machine, or a serial I/O card that supports IRQ sharing.) 16550AFN UART CHIP SUPPORT ========================== Every serial port uses a Universal Asynchronous Receiver-Transmitter (UART) chip to send and receive data. Inside your PC, data travels in parallel form. When you send or receive data by means of a serial device, the UART chip converts the data to a serial format so that your port can read it. Many machines still use either the 8520 or the 16450 UART chip. The main advantage of the 16550AFN UART chip is its first in, first out (FIFO) buffering scheme, which can dramatically improve performance for modem transfer speeds of 9600 baud or higher. If you usually set your modem to 2400 or 1200 baud, chances are you don't need the 16550AFN UART. NOTE: The 16550, an earlier version of the chip, was used in IBM PS/2 computers, models 50, 60, and 80, and replaced by the 16550AFN in the PS/2 model 70. You may want to check with your manufacturer to determine which version of the 16550 chip is installed in your machine. The 16550 chip does not support FIFO buffering. MS-DOS-BASED VS. WINDOWS-BASED APPLICATIONS =========================================== Windows-based applications share a single time slice; each MS-DOS- based application running under Windows receives its own time slice. A time slice is the amount of processor time allocated to an application, usually measured in milliseconds. The smaller the time slice, the more efficiently Windows can run multiple tasks; therefore, in general, you will notice better performance with Windows-based applications running under Windows. You can also use "Windows-aware" software to emulate timeslice sharing for MS-DOS-based applications and thereby improve performance. You run MS-DOS-based applications under Windows by writing PIF files that specify how you want Windows to schedule processor time for these applications. (For more information about PIF files, refer to Chapter 8, "PIF Editor," in the version 3.1 "Microsoft Windows User's Guide.") WHY CONFLICTS OCCUR =================== For serial communications to be successful, three settings must match: the port addresses in the BIOS data area, the COM port entries in the SYSTEM.INI file, and the switches on your serial hardware (if you have any installed). This section discusses the situations that can occur if these settings do not match, as well as other situations that can cause conflicts. Determining whether these settings match, and changing them if they do not, is discussed in the section "How to Resolve Conflicts" later in this Application Note. IRQ SHARING =========== Many serial communications problems result from two devices attempting to use the same IRQ. For example, if you install a serial mouse on COM1 and a modem on COM3, both devices could attempt to use IRQ4 (the default setting) at the same time. Unless your PC supports IRQ sharing (the ability to have multiple ports using the same IRQ), this could cause your mouse or modem to lose functionality. MCA and EISA machines support IRQ sharing. In addition, some serial I/O cards support IRQ sharing even if your machine is not specifically configured to do so. Windows 3.1 fully supports such serial I/O cards. For more information, see the "IRQ Sharing" section under "How to Resolve Conflicts" later in this Application Note. BIOS DATA AREA AND ADDRESS PACKING ================================== There are four sequential spaces in the BDA for COM port addresses 1 through 4. The BIOS lists port addresses so that no blank spaces occur between addresses. Windows reads the BDA sequentially and actually expects a blank address where there is no COM port. This can cause conflicts when Windows assigns IRQs. For example, if you have a mouse on COM1, a printer on COM2, and a modem on COM4, Windows expects the BDA to look something like this: (COM1) (COM2) (COM3) (COM4) 0040:0000 F8 03 F8 02 00 00 E8 02 Because the BIOS does not use zeros as placeholders, however, the BDA actually looks something like this: (COM1) (COM2) (COM3) (COM4) 0040:0000 F8 03 F8 02 E8 02 00 00 This behavior is known as address packing, or address shifting. Windows assigns IRQs in the order that it finds a COM port address. In this situation, Windows would assign IRQ4 (the default for COM3) to the device that is actually on COM4. This could cause loss of functionality on COM4 because IRQ4 is already being used by COM1. BIOS packing can affect COM ports 1 and 2 as well. For instance if you have no device on COM1, your COM2 address may register in the COM1 BIOS area. Whether or not you experience problems as a result of address packing may depend on what COM ports you are using, what type of hardware you have, and whether you are using MS-DOS-based communications software. To correct this type of situation, you write a Debug script. A Debug script records the correct port addresses in your system memory. This procedure is described in the section "How to Resolve Conflicts" under '"Address Packing." MS-DOS-BASED COMMUNICATIONS SOFTWARE AND WINDOWS 3.1 ==================================================== MS-DOS-based applications and Windows-based applications handle serial communications in different ways. This section discusses guidelines for using your MS-DOS-based communications programs under Windows 3.1. For more information, see chapters 7, "Non-Windows Applications," and 8, "PIF Editor," in the version 3.1 "Microsoft Windows User's Guide." General Guidelines ------------------ You use 386 enhanced mode Windows, and PIF files, to give Windows control of your MS-DOS-based communications applications. We don't recommend running MS-DOS-based communications applications in standard mode Windows, as this may cause data loss or other problems. For better performance, run your MS-DOS-based applications in full- screen mode rather than in a window. If you run an MS-DOS-based communications application in the background during a data transfer, run it minimized as an icon rather than in a window. PIF File Guidelines ------------------- - Select the Background check box (under Execution in the main PIF Editor dialog box), or your MS-DOS-based application will stop running when you switch away from it. - Select the Lock Application Memory check box (in the PIF Editor Advanced Options dialog box), or you may receive an error message. (This setting applies only if you have a permanent swap file and 32- bit disk access is enabled.) - If you encounter errors during data transfers, specify a larger Background Priority or Foreground Priority setting (in the Multitasking Options area of the Advanced Options dialog box). Device Contention ----------------- In the Windows multitasking environment, two applications sometimes simultaneously request the use of a device (such as a COM port or modem). This is known as device contention. When you are running MS- DOS-based communications applications under Windows in 386 enhanced mode, you need to set device contention options in Control Panel. Doing so specifies how you want Windows to handle device requests from your MS-DOS-based applications. Problems that can occur as a result of serial device contention include the inability to access a COM port. For more information, see the procedure "To set device contention options" later in this Application Note. UART Support for MS-DOS-Based Applications ------------------------------------------ Windows 3.1 provides application support for the new 16550AFN UART buffer (see the section on the UART earlier in this Application Note). However, MS-DOS-based applications may not recognize the 16550AFN UART, treating it instead like the earlier 8250 version. This, in turn, may result in data loss. Whether you experience these problems also depends to a certain extent on your hardware manufacturer. Pacific Commware's TurboCom is an advanced serial port communications driver for Windows that provides UART support for MS-DOS-based applications running under Windows. TurboCom also supports IRQ sharing and baud rate speeds of up to 57.6K. If you regularly use MS-DOS-based communications software or software that requires a baud rate of 9600 bits per second (bps) or higher, you may want to use the TurboCom driver. For additional information, contact your local dealer, or call Pacific Commware at (510) 540-8080. NOTE: If your communications software runs at 2400 baud or lower, using the 16550AFN UART probably won't noticeably improve your system's performance. Address Packing and MS-DOS-Based Applications --------------------------------------------- If Windows assigns an IRQ that is being used by an MS-DOS-based program, you may receive the message "The COM port is currently assigned to a DOS application. Do you want to reassign the port to Windows?" The problem occurs when your machine BIOS packs addresses before posting them to the BDA. Windows reads the BDA sequentially, assigning the default IRQ for COM1 to the first entry it finds, the IRQ for COM2 to the second entry, and so forth. For example, if you have a device on COM2 but not on COM1, and your system BIOS packs addresses, the COM2 address "shifts" into the BDA slot for COM1. Consequently, Windows assigns IRQ4 (the default for COM1) to the device that is actually on COM2. MS-DOS-based communications programs access the COM ports directly, without posting their port address to the BDA. Using the same example, if you have no serial device on COM1, and your MS-DOS-based communication program is using COM2, the MS-DOS-based program still uses the default IRQ for COM2. You can remedy this situation by writing a Debug script. For more information, see the procedure "To write a Debug script" later in this Application Note. THIRD-PARTY COMMUNICATIONS DRIVERS ================================== Some Windows-based third-party programs install their own drivers to replace the drivers provided by Windows. If these third-party drivers are installed in your system when you upgrade from Windows 3.0 to Windows 3.1, Setup does not install the Windows communications driver (COMM.DRV). In most instances, it is best to use the Windows 3.1 driver, rather than a driver designed for Windows 3.0. If you are experiencing driver problems (such as an inability to use higher baud rates, or problems accessing the modem), you can reinstall COMM.DRV or contact the manufacturer of your third-party driver for an update. You can tell whether you have the Windows communications driver, or whether it has been replaced by the driver(s) that came with your communications software, by looking in your SYSTEM.INI file. See the procedure "To check for third-party drivers" later in this application note. HOW TO RESOLVE CONFLICTS ======================== You should now be familiar with the most common reasons for serial communications problems in Windows 3.1. This section describes a few simple procedures you can follow to correct these problems. RESOLVING IRQ CONFLICTS ======================= If you have serial devices on both COM1 and COM3, or COM2 and COM4, and your machine architecture does not support IRQ sharing, you need to reassign the IRQ for COM3 or COM4. (If you are using a serial card that supports IRQ sharing, read the section that follows this procedure.) To properly reassign the IRQ: 1. Determine the valid IRQ settings for the serial device by referring to the manufacturer's documentation. Most serial devices such as I/O cards or internal modems can use either of several valid IRQs. For example, a modem on COM3 may be able to use IRQ5 if IRQ4 is not available. 2. Determine which IRQs are available on your PC. You can do this by referring to the table provided below, or you can use the Microsoft Diagnostic (MSD) utility. (Refer to the procedure, "To use MSD to determine available IRQs" later in this Application Note.) MSD is included with Windows version 3.1. 3. Point both your serial device and Windows to the IRQ that you have determined is valid and available. Set your serial device to the alternate IRQ by following the directions in the manufacturer's documentation. Point Windows to the alternate IRQ by using Control Panel to place an entry in your SYSTEM.INI file. NOTE: Your serial device setting MUST match the COMxIRQ setting in your SYSTEM.INI file. If these two settings do not match, the COM port will not function properly. Standard IRQ Settings (Table) ----------------------------- The following table shows the most common IRQ settings. You can use Control Panel to specify an IRQ from this table if it matches your hardware requirements. Or, if you'd like to view a table similar to this that lists the current settings in your PC, you can use MSD. IRQ Number Description --------------------------------------- 0 Timer 1 Keyboard 2 Link to IRQs 8-15 3 COM2, COM4 4 COM1, COM3 5 LPT2, or Reserved 6 Floppy disk controller 7 LPT1, LPT3 8 Real time clock 9 Redirected IRQ2 10 Reserved 11 Reserved 12 PS/2 mouse 13 Math coprocessor 14 Hard disk controller 15 Reserved The IRQs with "Reserved" entries in the corresponding Description column are often available. (This does not guarantee they are currently available on your PC.) You can use Control Panel to choose one of the "Reserved" IRQs, such as IRQ10, and then restart your system to see whether the COM port now works. NOTE: You must also change the hardware setting to the same IRQ. To do this, follow the manufacturer's instructions. If the first IRQ you choose does not work, you can try the next IRQ from this table, and so forth. If you do not have a PS/2 mouse port, you may be able to use IRQ12. Or, you can use MSD to view the IRQs that are actually available on your PC. To Use MSD to Determine Available IRQs -------------------------------------- 1. Quit Windows. 2. At the MS-DOS command prompt, type "msd"(without the quotation marks). An initial screen appears, providing information about MSD. Choose the OK button to view the MSD main menu. 3. From the MSD main menu screen, choose the IRQ Status button. The IRQ Status screen shows which IRQs are currently assigned (not available). 4. Make a note of each IRQ number where the entry in the corresponding Detected column reads No. A No entry in the Detected column indicates that the corresponding IRQ is available. If you do not find a "No" entry in the Detected column, there are no available IRQs, and you should not attempt to reassign IRQs. 5. Use Control Panel to assign one of the available IRQs to the COM port whose IRQ you want to change. See the next procedure. You must also change the hardware setting to the same IRQ. Follow the manufacturer's instructions. NOTE: Windows 3.1 does not support nonstandard IRQ settings. If your serial communications device requires an IRQ that is different than what is described in the MSD listing, we cannot guarantee the results. To Reassign the IRQ from Control Panel -------------------------------------- 1. In the Main group, choose the Control Panel icon. 2. In the Control Panel window, choose the Ports icon. 3. In the Ports dialog box, select the COM port for the device whose IRQ you want to change, and then choose the Settings Button. 4. In the Settings dialog box, choose the Advanced button. 5. Open the Interrupt Request Line (IRQ) list box, and select a number. This number must match your hardware setting. 6. Choose the OK button twice to exit the settings dialog boxes, and then choose the Close button to exit the Ports dialog box. IRQ-Sharing Serial I/O Cards ---------------------------- If you are using an IRQ-sharing I/O card on a machine that does not have MCA or EISA architecture, you need to add the following line to the [386Enh] section of the SYSTEM.INI file: COMIrqSharing=TRUE NOTE: This setting does not, by itself, provide your system with IRQ- sharing support. You must have the correct hardware configuration, and the hardware must be installed according to the manufacturer's specifications. ADDRESS PACKING =============== If you are using an MS-DOS-based communications program, Windows may assign an IRQ to a Windows serial device that is already in use by your MS-DOS-based program. If this happens, you may receive the error message "The COMx port is currently assigned to an MS-DOS application. Do you want to reassign the port to Windows?" To remedy this situation, you need to familiarize yourself with the BDA. (This error message may also occur if you have a BIOS that does not search for serial devices on COM ports 3 or 4. If this is the case, you can use Control Panel to register the devices.) To View the BDA by Using Debug ------------------------------ 1. Quit Windows. 2. At the MS-DOS command prompt, type "debug" (without the quotation marks), then press ENTER. A hyphen (-) prompt appears. 3. Type "d40:0" (without the quotation marks), then press ENTER. This returns a listing of the BIOS data area (BDA). The first row of the BDA shows the COM port and LPT port addresses, divided by a center hyphen. COM ports are listed to the left of the hyphen; LPT ports are listed to the right. 4. Once you have interpreted the BDA (see the following procedure), type "q" (without the quotation marks) to quit Debug. To Interpret the BDA COM Address Entries ---------------------------------------- This table shows the four standard COM addresses as they should be listed in the BDA. (The COMx headings do not appear in the BDA.) (COM1) (COM2) (COM3) (COM4) 0040:000 F8 03 F8 02 E8 03 E8 02 If you have a serial device on COM port 3 or 4, and the BDA does not show an entry for the device, you can use Control Panel to register the device in the BDA. However, if the BDA shows any of the standard addresses in a location other than what is shown here (for example, address F8 02 in the space for COM1, or address E8 02 in the space for COM3), then you need to write a Debug script. NOTE: If you see an address in your BDA that is not shown here, your hardware may use nonstandard serial port addresses. In this case you need to register the nonstandard address by using Control Panel. See the procedure "To register a serial device." To Write a Debug Script ----------------------- 1. Open any standard text editor, such as Windows Notepad. 2. Type the following three lines: E40:0 F8 03 F8 02 E8 03 E8 02 q You must press ENTER after typing "q" (without the quotation marks). If you do not, the Debug script will cause your system to remain indefinitely in Debug mode. 3. Save the file as FIXCOM.DEB, or any filename with a .DEB extension. 4. Add the following line to the end of your AUTOEXEC.BAT file: DEBUG < FIXCOM.DEB > NUL The "> NUL" ending keeps the Debug script from echoing to the screen. NOTE: Do not place this entry after a program execution line, such as WIN. If you do, the Debug script will not execute. 5. Save your AUTOEXEC.BAT file and reboot your PC. You can view the BDA again to see whether the address changes have taken effect. NOTE: The port address setting on your physical serial device must match what you specify in the Debug script. If your hardware requires a nonstandard address, you can specify that address in the Debug script. SERIAL DEVICES ON COM3 AND COM4 DO NOT REGISTER =============================================== Some earlier BIOS versions only recognize devices installed on COM ports 1 and 2. If your system BIOS does not recognize serial devices on COM ports 3 and 4, you can use Control Panel to notify Windows that you have devices installed at these locations. However, if your BIOS registers such devices but incorrectly records them at different addresses in the BDA (due to address shifting or packing), you cannot use Control Panel to correct this situation. Instead, you need to write a Debug script. Refer to the previous procedure. To determine whether your system BIOS registers devices on COM port 3 or 4, you need to read the BDA. Refer to the procedure "To view the BDA by using Debug." CAUTION: Setting the port address by using Control Panel does not override a BDA value. What the BIOS reads replaces any entries you make by using Control Panel, if there is a discrepancy between the two. This procedure is not a substitute for writing a Debug script if your BIOS incorrectly registers COM addresses. To Register a Serial Device --------------------------- 1. In the Main group, choose the Control Panel icon. 2. In the Control Panel window, choose the Ports icon. 3. In the Ports dialog box, select the port you want to identify to Windows, and then choose the Settings button. 4. In the Settings dialog box, choose the Advanced button. 5. Open the Base I/O Port Address list box and select an address. Check your hardware documentation for the appropriate value. 6. Open the Interrupt Request Line (IRQ) list box, and select an IRQ. Check your hardware documentation for the appropriate value. Selecting values in this dialog box places COMxBase and COMxIRQ entries in your SYSTEM.INI file. For more information on COMxBase and other SYSTEM.INI file entries, refer to the SYSINI.WRI file in your Windows directory. DEVICE CONTENTION ================= You need to specify the device contention options for each MS-DOS- based communications application you are running under Windows. To Set Device Contention Options -------------------------------- 1. In the Main group, choose the Control Panel icon. 2. In the Control Panel window, choose the 386 Enhanced icon. 3. Select the port that is connected to the device you want to control. 4. In the Device Contention group, select the option you prefer. Each option is described below. Always Warn Select this option to have Windows display a dialog box whenever more than one application requests use of a COM port at the same time. The dialog box lets you specify which MS-DOS-based application should receive control of the COM port. In most cases, you should select Always Warn. NOTE: The Always Warn option does not replace IRQ sharing. When you specify that one application receive control of a COM port, the other application requesting to use the port is interrupted. Optimally, once the first application completes its operation (for example, a fax transmission), the COM port becomes available again and the other application can resume. However, sometimes giving control of a COM port to one application over another can indefinitely hang the application that is required to wait. Never Warn When you select this option, Windows provides COM port access to MS- DOS-based applications even if it detects that the requested port may already be in use by another application. Selecting this option may cause unexpected problems, such as data loss or an interruption during application processing. Idle (in sec.) Select this option to specify the number of seconds Windows should wait before giving port access to an application without notifying you. For instance, if you specify 10 seconds, Windows displays a dialog box when any application requests the use of a port that was occupied within the last 10 seconds. The dialog box lets you specify which MS-DOS-based application should receive control of the COM port. Otherwise, Windows provides COM port access without a warning. For more information about these options, see page 247 of Chapter 7, "Non-Windows Applications," in the version 3.1 "Microsoft Windows User's Guide." THIRD-PARTY DRIVERS =================== The Windows 3.1 Setup program updates many drivers that were included in Windows 3.0. Setup cannot update third-party drivers, however. You should obtain updates from the manufacturer for any third-party drivers that you are using under Windows 3.1. To Check for Third-Party Communications Drivers ----------------------------------------------- 1. Open your SYSTEM.INI file by using any text editor, such as Windows Notepad. 2. Under the [boot] section, look for the following entry: comm.drv=comm.drv If this entry reads differently, then your system is using a third- party Windows-level driver. 3. Under the [386Enh] section, look for the following entries: device=*vcd device=*combuff If either of these entries reads differently, or if there is an additional entry, then your system is using third-party communications drivers. To determine whether you need an update, contact your manufacturer. To use third-party drivers that have not been updated, you need to add the following line to the [386Enh] section of your SYSTEM.INI file: COMMdrv30=TRUE Once you obtain an update for your third-party driver, you can remove this entry from your SYSTEM.INI file. TROUBLESHOOTING COMMUNICATIONS PORT PROBLEMS ============================================ This section can help you to identify what is causing a problem and then point you to the appropriate section in this Application Note for an explanation of how to resolve the problem. COMMUNICATIONS APPLICATION CANNOT ACCESS A SERIAL PORT ====================================================== Are you using MS-DOS-based communications software? Refer to the "MS- DOS-Based Communications Software and Windows 3.1" section in this Application Note. Related procedure: "To set device contention options" Is the serial device using an available IRQ? Refer to the "Resolving IRQ Conflicts" section in this Application Note. Related procedures: "To use MSD to determine available IRQs" "To reassign the IRQ from Control Panel" PC LOCKS UP WHEN ACCESSING SERIAL PORT ====================================== Is the serial device using a unique IRQ? Refer to the "Resolving IRQ Conflicts" section in this Application Note. Related procedures: "To use MSD to determine available IRQs" "To reassign the IRQ from Control Panel" Is the serial device on COM4? Refer to the "Serial Devices on COM3 and COM4 Do Not Register" section. Related procedure: "To register a serial device" ERROR MESSAGES ============== "The COM Port is Currently Assigned to a DOS Application..." ------------------------------------------------------------ If you receive this error message, refer to the procedure "To write a Debug script." MODEM PROBLEMS ============== Does your system BIOS recognize your internal modem? Refer to the "Address Packing and MS-DOS-Based Applications" section for information about reading the BDA. Related Procedures "To view the BDA by using Debug" "To interpret the BDA COM address entries" "To register a serial device" Do you have a modem on COM3 and a mouse on COM1, or a modem on COM4 and a mouse on COM2? Unless your machine or serial I/O card supports IRQ sharing, this configuration is not recommended. Refer to the "Resolving IRQ Conflicts" section in this Application Note. Related Procedure: "To reassign the IRQ from Control Panel" Do you have an internal modem and a serial I/O card? Have you observed any of the following symptoms: The modem dials and rings but does not connect. The system reboots when the modem attempts to dial out. The system reboots when the modem should have connected. The cursor does not work in Window Terminal. If your internal modem uses a COM port that is addressed by your serial I/O card, you may experience IRQ conflicts. To correct this problem, disable the COM port setting on the serial I/O card. For example, if your internal modem is set to use COM2, and you have a serial I/O card that recognizes COM2, you may need to disable COM2 on the serial I/O card for the modem to work correctly. MOUSE PROBLEMS ============== General Guidelines ------------------ The mouse uses a different driver for MS-DOS-based applications than it does for Windows-based applications. In general, all mouse drivers should come from the same vendor. For example, do not use a Microsoft driver as the Windows mouse driver and a third-party driver as the MS- DOS mouse driver. Do not install a modem on COM3 if you have a mouse on COM1, or a modem on COM4 if you have a mouse on COM2, unless your machine or serial I/O card supports IRQ sharing. Refer to the "Resolving IRQ Conflicts" section in this Application Note. Mouse Doesn't Work in Enhanced Mode ----------------------------------- If your PC has no COM1 or if you have disabled COM1 and you have a mouse installed on COM2, you may experience problems using the mouse in 386 enhanced mode. Refer to the "BIOS Data Area and Address Packing" section in this Application Note. Logitech(TM) Mouse ------------------ The Logitech virtual mouse driver (LVMD.386) is hard coded for the standard base port addresses and IRQs. If you use the Logitech mouse with a nondefault port address or IRQ, it may fail to work in 386 enhanced mode. 100%-Microsoft-Compatible Mouse ------------------------------- Any "100% Microsoft compatible" mouse that you purchase from your dealer is not interchangeable with the Microsoft mouse. If your 100%- Microsoft-compatible mouse comes with a driver disk that contains both Windows and MS-DOS mouse drivers, install these in place of the Microsoft mouse drivers. Installing such drivers places a new setting in the Mouse section of Windows Setup. After you install a 100%- Microsoft-compatible mouse, use Windows Setup to select your mouse type. Microsoft Mouse --------------- If you are using the Microsoft Mouse with Windows 3.1, make sure each of the following is true: - You are using version 8.2 or 8.2a of MOUSE.COM and MOUSE.SYS (the mouse drivers for MS-DOS-based applications). Version 8.2 or 8.2a of the driver is included with Windows 3.1. - MOUSE.DRV (the mouse driver for Windows-based applications) is in the Windows SYSTEM subdirectory, is the only copy of this file on your system, and is the most current version of the driver. - The mouse is assigned a unique IRQ (unless the serial port supports IRQ sharing). For more information, see the "IRQ Sharing" section in this Application Note. - The mouse is not installed on COM3 or COM4. To see what version of the MS-DOS mouse driver you have At the MS-DOS command line from the MS-DOS mouse directory (usually, MSMOUSE), type: mouse /? To see what Windows mouse driver you are using >From the Main group, choose the Windows Setup icon. The mouse type should be "Microsoft, or IBM PS/2." To change your Windows mouse driver 1. In the Main group, choose the Windows Setup icon. 2. From the Options menu, choose Change System Settings. 3. Open the Mouse list box and select the type of mouse that you are using. 4. Choose the OK button to close the dialog box. COM4 PROBLEMS ============= If your communications software doesn't recognize a serial device on COM port 3 or 4, you may have a system BIOS that was manufactured before those COM ports became standard. Refer to the "Serial Devices on COM3 and COM4 Do Not Register" section earlier in this application note. The COM4 default address of 02E8 conflicts with some peripheral devices, including the 8514/A, Ultra (ATI), and S3 (Orchid Fahrenheit 1280 STB WIND/X, Diamond Stealth VRAM) display adapters, and certain network adapters. Do not readdress COM4 in this situation. Contact your hardware manufacturer for information about how to reset the adapter's default address. PROBLEMS RUNNING WINDOWS IN 386 ENHANCED MODE ============================================= Problems of this type may be related to a number of causes, including outdated driver files or IRQ conflicts. You can try the troubleshooting steps outlined below if you experience any of the following problems when trying to run Windows in 386 enhanced mode: -Windows stops running or returns to the MS-DOS prompt -General protection (GP) fault -Windows defaults to standard mode If the steps outlined below do not help, then the problem is probably not caused by a serial communications conflict. Refer to the Windows Resource Kit for more information about problems running Windows in 386 enhanced mode. To Check for Outdated Driver Files ---------------------------------- Before starting Windows from the MS-DOS prompt, change to the Windows directory, and then start Windows. If Windows runs in 386 enhanced mode only when you start it from the Windows directory, you may have an outdated driver file in some other directory. When Windows starts, it looks for the files it needs in the following order: The current directory The Windows directory The Windows SYSTEM subdirectory All the directories listed in the PATH statement in the AUTOEXEC.BAT file All the directories in a network path If you suspect that you have outdated driver files, you need to delete them from your system. To Delete Outdated Driver Files ------------------------------- 1. Use File Manager to find all versions of the driver file(s) on your system. Compare each version by date. 2. Delete all other versions of the driver file(s) except the most current version. Retain a single copy of the most current version in the Windows SYSTEM subdirectory. To Identify an IRQ Conflict --------------------------- 1. Remove any serial hardware you have installed on your system (mouse, network card, fax board, modem, and so forth) and then restart Windows. If Windows now runs in 386 enhanced mode with no problems, the problem may be caused by an IRQ conflict. 2. Reinstall each separate piece of serial hardware, one at a time, restarting Windows between each addition. This isolates the hardware that is causing the IRQ conflict. When the problem recurs, you can assume it is caused by the hardware you have just reinstalled. 3. Reassign the IRQ for the piece of hardware in question. Refer to the procedure in this Application Note on "To reassign the IRQ from Control Panel." ---------------------------------------------------------------- ---- TO OBTAIN THIS APPLICATION NOTE =============================== - On CompuServe, GEnie, and Microsoft OnLine, Application Notes are located in the Microsoft Software Library. You can find WW0654 in the Software Library by searching on the word WW0654, the Q number of this article, or S13673. WW0654 is a compressed, self-extracting file. After you download WW0654, run it to extract the file(s) it contains. - On the Internet, Application Notes are located on the Microsoft anonymous ftp server, which you can reach by typing "ftp ftp.microsoft.com" (without the quotation marks) at the ">" command prompt. You can find WW0654.EXE in the SOFTLIB/MSLFILES directory. - Application Notes are available by modem from the Microsoft Download Service (MSDL), which you can reach by calling (206) 936-6735. This service is available 24 hours a day, 7 days a week. The highest download speed available is 14,400 bits per second (bps). For more information about using the MSDL, call (800) 936-4200 and follow the prompts. To obtain WW0654, download WW0654.EXE. - You can have this Application Note mailed or faxed to you from the automated Microsoft FastTips Technical Library, which you can call 24 hours a day, 7 days a week at (800) 936-4200. NOTE: The FastTips Technical Library is available only to customers within the U.S. and Canada. - If you are unable to access the source(s) listed above, you can have this Application Note mailed or faxed to you by calling Microsoft Product Support Services Monday through Friday, 6:00 A.M. to 6:00 P.M. Pacific time at (206) 637-7098. If you are outside the United States, contact the Microsoft subsidiary for your area. To locate your subsidiary, call Microsoft International Sales Information Center at (206) 936-8661. KBCategory: kbfile kbdisplay kbappnote KBSubcategory: Additional reference words: appnote gpf 3.10 comm port lpt 1.0 Reinstalling Windows Without Losing Settings Article ID: Q94196 ---------------------------------------------------------------- ---- The information in this article applies to: - Microsoft Windows operating system versions 3.1, 3.11 ---------------------------------------------------------------- ---- SUMMARY ======= There may be situations in which you need to reinstall Microsoft Windows to troubleshoot a problem possibly related to file corruption or accidental deletion of files from the Windows directory or the Windows SYSTEM subdirectory. In most cases, it is not advisable to simply reinstall over an existing Windows installation because with that procedure, some files may not be properly updated. Installing Windows to a new directory ensures a "clean" installation; however, any modifications to Windows initialization (.INI) files or the registration database (REG.DAT) are lost with such an installation. Also, programs that install files into the Windows directory, such as Microsoft Word for Windows and Microsoft Excel, cannot run from the new copy of Windows. Any Windows-based applications must be reinstalled under the new installation of Windows. Furthermore, any customization of Program Manager groups, desktop colors and wallpaper, screen-saver settings, and other user-defined environment settings must be re-created. MORE INFORMATION ================ Use the following steps to reinstall Windows 3.1 without losing current settings, such as .INI and REG.DAT file modifications, customized Program Manager groups (.GRPs), and other desktop settings. 1. Install Windows into a new directory, such as C:\WIN. Verify that Windows runs from this new directory. If Windows ran during installation but does not run from this new directory, something has changed on the computer, or file corruption has occurred since Windows was installed. The following causes should be considered: - Changes to the path - Deletion of files from the Windows directory - Low conventional memory - File corruption - Hardware failures 2. In this new installation, rename the .GRP files using .GRN, the .INI files using .INN, and the .FOT files (located in the Windows SYSTEM subdirectory) using .FOZ. Rename the REG.DAT file using REG.DAN. To do this, quit Windows and type the following commands at an MS-DOS command prompt: rename c:\win\*.grp *.grn rename c:\win\*.ini *.inn rename c:\win\reg.dat reg.dan rename c:\win\system\*.fot *.foz NOTE: The *.FOT files have an internal direct path to the *.TTF files, which if copied to the old C:\WINDOWS\SYSTEM subdirectory, can create problems with the fonts after the C:\WIN directory is removed. 3. Remove the Read-Only attribute from any files in the C:\WINDOWS and C:\WINDOWS\SYSTEM directories. Copy all the files from the new installation into the original Windows directory (C:\WINDOWS) by typing the following at an MS-DOS command prompt: attrib -s -h c:\windows\*.* /s attrib -r c:\windows\*.* /s xcopy c:\win c:\windows /s If Windows now runs from the C:\WINDOWS directory, the reinstallation has been successful, and no settings were lost. To save disk space, delete the C:\WIN directory from File Manager or from MS-DOS version 6.0 or later using the DELTREE command. Also, delete files with the extensions .INN, .GRN, and the file REG.DAN in the C:\WINDOWS directory, and the files ending with .FOZ in the C:WINDOWS\SYSTEM subdirectory. If Windows does not run, continue with the following steps. 4. Rename the original .INI files using .INO, and rename the .INN files using .INI as follows: rename c:\windows\*.ini *.ino rename c:\windows\*.inn *.ini Edit the PROGMAN.INI file and replace all occurrences of C:\WIN with C:\WINDOWS. If Windows runs now, the problem is being caused by a corruption or improper setting in one of the original .INI files. The best solution is to back up all data files from Windows-based applications and then reinstall the applications. This ensures the correct WIN.INI, SYSTEM.INI, and directory settings for each application. Note that you must re-create any customization of Program Manager groups and desktop settings. To free up disk space, delete excess files as shown in step 3 above. 5. If Windows does not run now, back up all application data files and reinstall the applications under the new Windows installation after renaming the .INN, .GRN, .FOZ, and REG.DAN files as follows: rename c:\win\*.inn *.ini rename c:\win\*.grn *.grp rename c:\win\reg.dan reg.dat rename c:\win\system\*.foz *.fot REFERENCES ========== "Microsoft Windows Resource Kit," version 3.1, Chart 1.6, "Reinstalling Windows Without Losing Settings," page 15 "Getting Started With Microsoft Windows," version 3.1, Chapter 1, "Setting Up Windows," pages 1-15 KBCategory: kbsetup kbtshoot KBSubcategory: win31 Additional reference words: tshoot how to preserve 3.10 reinstal save setup install rebuild Windows Err Msg: EMM386 Exception Error #6 Article ID: Q94279 ---------------------------------------------------------------- ---------- The information in this article applies to: - Microsoft Windows operating system versions 3.1, 3.11 - Microsoft Windows for Workgroups versions 3.1, 3.11 ---------------------------------------------------------------- ---------- SUMMARY ======= You may receive the following error message while running an MS-DOS-based application under Windows or Windows for Workgroups: EMM386 Exception Error #6 This error message indicates that an MS-DOS-based application has caused the processor to execute an invalid instruction. Although the error message is provided by EMM386.EXE, it is not the cause, nor is it directly related to the problem. The error is probably caused by a corrupt .EXE file or a bad memory chip. MORE INFORMATION ================ When Windows starts, it turns off EMM386.EXE but leaves its error handler installed. When the CPU notifies Windows of a problem, it passes the error to the default handler, which in this case is EMM386.EXE. EMM386 Exception Error #6 indicates an "invalid opcode." According to "Microsoft's 80386/80486 Programming Guide" second edition (pages 122-123), this error can be caused by either of the following: - The processor tries to decode a bit pattern that does not correspond to any legal machine instruction. - The processor tries to execute an instruction that contains invalid operands. Both situations indicate the same thing--the CPU is trying to execute instructions, but is being given random values from the wrong memory location. This can be caused by one of the following: - The application gave an invalid jump instruction, causing a jump to an invalid memory location. - The application gave a correct jump, but the memory it jumped to is corrupted. The most likely cause of these problems is either a corrupted file (.EXE, .DLL, or virtual device driver [VxD]) or a bad memory chip. If the problem occurs on more than one distinct program, it is probably caused by a bad memory chip. For example, if the problem occurs when you choose Open from the File menu in Microsoft Windows Write and Microsoft Windows Notepad, the error is probably being caused by a corrupted common dialog box .DLL file (COMMDLG.DLL). But if the problem occurs in two applications that do not share any .DLL files, the error is likely caused by a bad memory chip. If you are using MS-DOS 6.2 or later or Windows for Workgroups version 3.11, you may be able to correct this problem by removing HIGHSCAN from the EMM386.EXE command in your CONFIG.SYS file. Exception Error #6 with Microsoft Backup for Windows ---------------------------------------------------- If you receive the "EMM386 Exception Error #6" while you are running Microsoft Backup for Windows, you may have an incompatible third-party virtual device driver (VxD). Use a text editor, such as Microsoft Windows Notepad, to edit the [386Enh] section of the SYSTEM.INI file and use a semicolon to remark out the following lines: device=fastback.386 -or- device=virwt.386 NOTE: VFINTD.386 is the virtual device driver for MS-DOS 6.x Backup for Windows and should not be removed. Exception Error #6 With Older Version of After Dark --------------------------------------------------- This error can occur while running older version of Berkeley Systems' After Dark with other applications (such as Intuit's Quicken) in Microsoft Windows. To solve the problem, remove After Dark. The products included here are manufactured by vendors independent of Microsoft; we make no warranty, implied or otherwise, regarding these products' performance or reliability. KBCategory: kbtool kberrmsg kb3rdparty KBSubcategory: msdos win31 wfw wfwg Additional reference words: 3.10 mwbackup 006 6.0 6.00 6.2 6.20 3rdparty quickin afterdark ms-dos WW0524: Troubleshooting GP Faults (UAEs) Article ID: Q95505 ---------------------------------------------------------------- ------ The information in this article applies to: - Microsoft Windows operating system versions 3.0, 3.0a, 3.1, 3.11 - Microsoft Windows for Workgroups version 3.1, 3.11 ----------------------------------------------------------------- ----- Microsoft has an Application Note titled "WW0524: Troubleshooting GP Faults (UAEs)" that can help you troubleshoot general protection (GP) faults in Windows 3.1, Windows for Workgroups 3.1 and 3.11, and unrecoverable application errors (UAEs) in Windows 3.0. You can obtain this Application Note from the following sources: - CompuServe, GEnie, and Microsoft OnLine - Microsoft Download Service (MSDL) - The Internet (Microsoft anonymous ftp server) - Microsoft FastTips Technical Library - Microsoft Product Support Services For complete information, see the "To Obtain This Application Note" section at the end of this article. THE TEXT OF WW0524 ================== ================================================================ ====== Microsoft(R) Product Support Services Application Note (Text File) WW0524: Troubleshooting GP Faults (UAEs) ================================================================ ====== Revision Date: 8/94 No Disk Included The following information applies to Windows(TM) & Windows for Workgroups, versions 3.0, 3.1, and 3.11. ---------------------------------------------------------------- ------ | INFORMATION PROVIDED IN THIS DOCUMENT AND ANY SOFTWARE THAT MAY | | ACCOMPANY THIS DOCUMENT (collectively referred to as an Application| | Note) IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER | | EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE IMPLIED | | WARRANTIES OF MERCHANTABILITY AND/OR FITNESS FOR A PARTICULAR | | PURPOSE. The user assumes the entire risk as to the accuracy and | | the use of this Application Note. This Application Note may be | | copied and distributed subject to the following conditions: 1) All| | text must be copied without modification and all pages must be | | included; 2) If software is included, all files on the disk(s) | | must be copied without modification (the MS-DOS(R) utility diskcopy| | is appropriate for this purpose); 3) All components of this | | Application Note must be distributed together; and 4) This | | Application Note may not be distributed for profit. | | | | Copyright (C) 1992-1994 Microsoft Corporation. All Rights Reserved.| | Microsoft and MS-DOS are registered trademarks and Windows is a | | trademark of Microsoft Corporation. | | 3+Open, 3+Share, and 3Com are registered trademarks of 3Com | | Corporation. Adaptec is a trademark of Adaptec, Inc. Adobe Type | | Manager and ATM are registered trademarks of Adobe Systems, Inc. | | AST is a registered trademark of AST Research, Inc. AT&T is a | | registered trademark of American Telephone and Telegraph Company. | | Banyan and VINES are registered trademarks of Banyan Systems, Inc. | | Bitstream is a registered trademark of Bitstream, Inc. COMPAQ is a | | registered trademark of Compaq Computer Corporation. DEC is a | | registered trademark and Pathworks is a trademark of Digital | | Equipment Corporation. Everex is a trademark of Everex | | Systems, Inc. Hewlett-Packard is a registered trademark of | | Hewlett-Packard Company. AT, IBM, Micro Channel, OS/2, and PS/2 are| | registered trademarks of International Business Machines | | Corporation. Intel is a registered trademark of Intel Corporation. | | Artisoft and LANtastic are registered trademarks of Artisoft, Inc. | | NEC is a registered trademark of NEC Corporation. NetWare and | | Novell are registered trademarks of Novell, Inc. PC Tools is a | | trademark of Central Point Software, Inc. Qemm is a trademark of | | Quarterdeck Office Systems. SpeedStor is a registered trademark of | | Storage Dimensions. Stacker is a trademark of STAC Electronics. | | TCS is a registered trademark of Eurotherm International P.L.C. | | Toshiba is a registered trademark of Kabushiki Kaisha Toshiba. | | Zenith is a registered trademark of Zenith Electronics Corporation.| | |--------------------------------------------------------------- -----| INTRODUCTION ============ This document describes general protection (GP) faults (referred to as unrecoverable application errors [UAEs] in Windows 3.0), details the causes of these errors, and provides a systematic approach to eliminate them. WHAT IS A GENERAL PROTECTION (GP) FAULT? ======================================== GP faults occur only in the standard and 386 enhanced modes of Windows; they cannot occur in the real mode of Windows 3.0. A GP fault signifies that something unexpected has happened within the Windows environment, typically an improper memory access. For example, an application or a Windows component might read or write to a memory location that has not been allocated to it (memory that it does not "own"), potentially overwriting and corrupting other program code in that area of memory. Another situation where a GP fault may occur involves the passing of parameters between applications and the Windows environment. Invalid parameters can cause invalid instructions to be executed, resulting in GP faults. This is usually the result of an application's internal program code incorrectly passing specific data that could not be correctly interpreted by Windows or a Windows-based application. What Is a System Integrity Violation? ------------------------------------- A system integrity violation error message indicates that an MS- DOS-based application has caused a GP fault. Similar to a GP fault, system integrity violations indicate that an MS-DOS-based application has accessed memory that does not belong to it. Because Windows is managing memory in this situation, the MS-DOS- based application's memory access often corrupts Windows program code or data. The result is an application execution error generated from Windows that reports the "application has violated system integrity due to an invalid general protection fault and will be terminated." This message can also occur when an MS-DOS- based application has tried to directly access a hardware component of the system. HOW DO WINDOWS 3.1 AND WINDOWS FOR WORKGROUPS 3.1 AND 3.11 HANDLE GP FAULTS? ========================================= The parameter validation feature allows Windows 3.1 and both versions of Windows for Workgroups to check for invalid parameters passed between Windows and Windows-based applications. Windows 3.1 and Windows for Workgroups are also designed to better manage and maintain which applications "own" specific memory locations and system resources. As a result, Windows 3.1 and Windows for Workgroups are better at recovering a particular application's memory and system resources if the application causes a GP fault and subsequently stops responding (hangs). When you see a GP fault message while running Windows 3.1 or Windows for Workgroups, the message provides specific information about which applications and Windows components were running at the time of the error, and where the error occurred. If the GP fault is not too severe, Windows can continue to run the application that caused the fault, allowing you to save your work before you close the application. Performing a Local Reboot ------------------------- Depending on the severity of a GP fault in Windows 3.1 or Windows for Workgroups, you may be able to press CTRL+ALT+DEL to display information concerning system integrity and the application that caused the fault. The severity of a GP fault can be measured by how well an application functions after the fault has occurred. When you press CTRL+ALT+DEL after a less severe fault occurs, the following message appears: System has either become busy or has become unstable - Press any key to return to Windows and wait - Press CTRL+ALT+DEL again to restart your computer (all unsaved information will be lost) When you get this message, you can return to Windows and wait for the system to recover, but you will probably have to restart the system. When you press CTRL+ALT+DEL after a more severe fault occurs, the following message appears: This Windows application has stopped responding to the system - Press ESC to cancel and return to Windows - Press ENTER to close this application (all unsaved information will be lost) - Press CTRL+ALT+DEL again to restart your computer (all unsaved information will be lost) When you get this error message, you can usually press the ESC key to return to your application and save your work (if possible) or press the ENTER key to close the application and return to Windows; this is known as a local reboot. Once you have saved your work or returned to Windows, quit Windows and restart your computer to prevent additional GP faults. PREPARING TO TROUBLESHOOT GP FAULTS =================================== The procedures in the following section provide a proven way to troubleshoot GP faults. Many of these troubleshooting steps require changes to system configuration files. These changes are not intended to be permanent; they should be used as techniques for isolating the conflict that caused the GP fault. Before you begin making changes, you should back up your system files and make a startup (also known as system or boot) disk. This gives you the ability to restart your computer and edit your CONFIG.SYS or AUTOEXEC.BAT files should any changes cause the system to hang. This also ensures that you can return to your original system configuration by restoring your original system files after you have determined the source of the problem. To create a startup disk with the necessary files: 1. Insert a formatted disk in your floppy disk drive, type the following command, and press ENTER: sys c: a: If you are using a version of MS-DOS earlier than 5.0, you also need to copy the COMMAND.COM file to drive A by typing the following command and pressing ENTER: copy c:\command.com a: 2. Copy an ASCII text editor (such as MS-DOS Editor [including QBASIC.EXE] or Edlin) to the disk in drive A by typing the following commands, pressing ENTER after each: copy c:\dos\edit.com a: copy c:\dos\qbasic.exe a: If you are running version 4.0 or earlier of Microsoft MS-DOS, your editor is called Edlin. To copy Edlin to drive A, type the following command and press ENTER: copy c:\dos\edlin.com a: 3. Copy your AUTOEXEC.BAT, CONFIG.SYS, SYSTEM.INI, and WIN.INI files to the disk in drive A with the following commands: copy c:\autoexec.bat a: copy c:\config.sys a: copy c:\windows\system.ini a: copy c:\windows\win.ini a: NOTE: If your Windows directory is on a drive other than C, substitute the appropriate drive letter for "c" in the above steps. SYSTEMATICALLY ISOLATING GP FAULTS ================================== It is important that you follow the steps in this section in sequence. GP faults are usually caused by the interaction of two or more applications; therefore, skipping steps may prolong the time required to isolate the problem. NOTE: Most people find the cause of the GP fault in the first half of these procedures. Eliminate the Basics -------------------- 1. Ensure the application was not designed for an earlier version (2.x) of Windows. If you are running Windows in standard or 386 enhanced mode, check to see if you are running an application that was designed for an earlier version (2.x) of Windows. Applications designed for Windows 2.x cause errors when run under Windows 3.0 or 3.1 in standard or 386 enhanced mode. Windows displays a warning message when you run an application designed for Windows version 2.0, 2.03, 2.1, or 2.11. Such applications should be run only under Windows 3.0 in real mode, as the dialog box suggests. Since real mode is not available in Windows 3.1 or Windows for Workgroups, contact the manufacturer of the application for possible workarounds or to obtain a software upgrade. 2. Run the MS-DOS CHKDSK command with the /F switch. NOTE: Before you run this command, you must quit Windows. By running CHKDSK /F, any lost allocation units or other file allocation table (FAT) errors are corrected. For more information on CHKDSK, refer to your MS-DOS documentation. NOTE: If you are using MS-DOS 6.2 or later, run SCANDISK instead of CHKDSK /F. 3. Ensure system resources are above 60 percent. From the Help menu in Program Manager, choose About Program Manager. You should be running Windows in the highest mode your hardware supports, and your system resources should be close to 60 percent. If system resources are lower than 60 percent, you may have an application running in the background using resources. If this is the case, close all applications before proceeding. 4. Check the MS-DOS version you are running. Your machine should have the proper MS-DOS version for its hardware type. Original equipment manufacturer (OEM) versions of MS-DOS (such as COMPAQ(R) MS-DOS or IBM(R) PC-DOS) should be used only on their respective OEM hardware platforms (that is, COMPAQ MS-DOS on COMPAQ machines only and IBM PC-DOS on IBM machines only). NOTE: Microsoft MS-DOS 5 Upgrade and Microsoft MS-DOS 6 Upgrade are platform independent-they function correctly on all 100- percent IBM PC/AT(R)-compatible machines. 5. Determine if the problem occurs in standard mode. If you are having problems with GP faults in 386 enhanced mode, try running Windows in standard mode (WIN /S) to see if the GP faults still occur. If the errors are present in both standard and 386 enhanced mode, the problem may be caused by a conflict between Windows and a hardware device, or you may have a corrupted file. NOTE: Standard mode is not available in Windows for Workgroups 3.11. Start Windows for Workgroups 3.11 by typing WIN /D:T to prevent loading any 386 enhanced mode virtual device drivers. 6. Run Windows without using the WIN.INI file. To determine if you are having problems with corrupted fonts, a corrupted printer driver, or software loading from the run= or load= line, rename the WIN.INI file with the following command, then restart Windows: ren c:\windows\win.ini winini.old If this procedure corrects the problem, ensure the load= and the run= lines in the [windows] section of the WIN.INI file are either blank or preceded with a semicolon (;) to prevent any software from loading. If this fails to correct the problem, contact Microsoft Product Support Services for assistance in isolating the problem within the WIN.INI file. If the previous procedure does not correct the problem, rename WININI.OLD to WIN.INI, by typing the following command: copy c:\windows\winini.old win.ini 7. Reinstall the software that is causing the GP fault. If the GP fault can be tracked to a specific application, reinstall the software causing the GP fault. The files on disk may have been corrupted or damaged, or the application may have been improperly installed. Contact the software vendor for assistance if you need help reinstalling the application. Eliminate Other Software Conflicts Within Windows ------------------------------------------------- It is essential to determine whether the GP fault is caused by a conflict between Windows and your hardware or a conflict between Windows and other software. To do this, eliminate possible software conflicts before testing your hardware. After you remove the software listed below, restart your computer and try to reproduce the GP fault. To eliminate possible software conflicts: 1. Ensure that the StartUp group is empty. 2. Ensure that no screen savers, including built-in Windows screen savers, are running. In the Control Panel window, choose the Desktop icon and ensure the Screen Saver Name list box is empty. 3. Ensure Windows is not being run from a menu program, such as MS- DOS Shell. Configure Windows for the Lowest Level Configuration ---------------------------------------------------- Use the Windows Setup program to configure Windows for the minimum necessary hardware devices. Run the MS-DOS version of Windows Setup (from the Windows directory [usually named WINDOWS], type setup) and select the lowest level configuration of device drivers. When you troubleshoot GP faults, use only the standard Windows device drivers listed below, if possible. Display: VGA (Version 3.0) Mouse: No mouse or other pointing device Network: No network installed (This is not an option for Windows for Workgroups.) NOTE: Systems with EGA cards and/or monitors should use the EGA display driver. Check for Unsupported Third-Party Drivers ----------------------------------------- 1. The installation programs of some applications modify the SYSTEM.INI and WIN.INI files to enhance the overall functionality of Windows or provide additional features to the Windows environment. For example, programs such as Adobe Type Manager(R) (ATM[R]), Bitstream(R), and SuperPrint add device drivers to the SYSTEM.INI file. Temporarily comment out all lines relating to third-party drivers to ensure that Windows uses a minimum configuration for testing purposes. (To comment out a line, use an ASCII text editor, such as Windows Notepad, to edit the .INI file and place a semicolon at the beginning of the appropriate line.) If this corrects the problem, the problem was most likely caused by one of the drivers you commented out. To identify which line is causing the problem, replace the commented-out lines one by one until the problem reoccurs. 2. The statements below are those most commonly altered by third- party software manufacturers. Make sure your configuration does not differ from the default Windows configuration shown below: SYSTEM.INI | WIN.INI --------------------------------------------- [boot] | [windows] shell=progman.exe | load= system.drv=system.drv | run= keyboard.drv=keyboard.drv | mouse.drv=mouse.drv | display.drv=vga.drv | comm.drv=comm.drv | sound.drv=mmsound.drv | Eliminate Software Conflicts at the MS-DOS Level ------------------------------------------------ Check for incompatible terminate-and-stay-resident (TSR) programs or unsupported device drivers in your CONFIG.SYS and AUTOEXEC.BAT files. Temporarily comment out all lines relating to device drivers and TSR programs that are not required to start your system. These may include virus-detection programs, disk-imaging programs, undelete utilities, caching programs, CD-ROM drivers, multimedia drivers, terminal-emulation software, and so on. (To comment out a line, use a text editor, such as MS-DOS Editor or Edlin, open the AUTOEXEC.BAT or CONFIG.SYS file, and type "rem" (without the quotation marks) at the beginning of the line, then save the file and restart your computer.) NOTE: Do not comment out network files if the Windows files are on a network server. Minimum MS-DOS configuration for Windows versions 3.0 and 3.1: CONFIG.SYS | AUTOEXEC.BAT ---------------------------------------------------------------- - files=50 | path c:\;c:\dos;c:\windows buffers=30 | prompt $p$g device=c:\\himem.sys | set temp=c:\ stacks=9,256 (Windows 3.1 only) | Minimum MS-DOS configuration for Windows for Workgroups 3.1 (with the Microsoft Windows network): CONFIG.SYS | AUTOEXEC.BAT ---------------------------------------------------------------------- - files=50 | c:\\net start buffers=30 | path c:\;c:\dos;c:\windows device=c:\\himem.sys | prompt $p$g stacks=9,256 | set temp=c:\ *device=c:\\protman.dos | /I:\protocol.ini | device=c:\\.dos | device=c:\ \workgrp.sys | *NOTE: This should appear on a single line in your CONFIG.SYS file. Minimum MS-DOS configuration for Windows for Workgroups 3.11 (with the Microsoft Windows network): CONFIG.SYS | AUTOEXEC.BAT -------------------------------------------------------------- files=50 | c:\\net start buffers=30 | path c:\;c:\dos;c:\windows device=c:\\himem.sys | prompt $p$g stacks=9,256 | set temp=c:\ device=c:\\ifshlp.sys | CAUTION: Before modifying these files, make sure you don't comment out lines pertaining to other hardware-specific device drivers, such as disk-compression utilities, extended memory boards, third- party disk-partitioning programs, and so on. If you do not know the purpose of a line in your CONFIG.SYS or AUTOEXEC.BAT file, do not comment it out. The following drivers may be required to start the computer or to access your hard disk: Device driver | Function ---------------------------------------------------------------- SSWAP.COM | Stacker(TM) disk compression STACKER.COM | Stacker disk compression DASDDRVR.SYS | IBM BIOS fix DMDRVR.SYS | Ontrack disk partition SSTORE.SYS | SpeedStor(R) disk compression ASPI4DOS.SYS | Adaptec(TM) SCSI BIOS extensions SCSIHA.SYS | Adaptec SCSI buffering device If the previous procedure corrects the problem, the problem is related to one of the drivers or TSR programs that you commented out. To identify which line is loading the TSR program or device driver that causes the error, restore the commented-out lines one by one until the problem reoccurs. Eliminate Potential Network Conflicts ------------------------------------- If the machine is running on a network, disabling the network software is the easiest and quickest way to determine whether the network software is causing the problem. To disable the network software: 1. If Windows is running on the local hard disk drive (that is, you are not running a network installation of Windows [installed by running SETUP /N]), comment out all network drivers and statements from the AUTOEXEC.BAT and CONFIG.SYS files. 2. Configure Windows for "No network" by changing to the WINDOWS directory (CD \WINDOWS), typing "setup" (without the quotation marks), and changing the installed network to "No network installed." NOTE: "No network installed" is not a choice in Windows for Workgroups. For Windows for Workgroups 3.1, comment out the network statements in the CONFIG.SYS and AUTOEXEC.BAT files. When you restart your system, ignore the error messages about the network. For Windows for Workgroups 3.11, type "win /n" (without the quotation marks) to disable network functionality. 3. Ensure login scripts are not altering the PATH environment variable. Check the PATH environment variable prior to starting Windows. To do this, type "set" (without the quotation marks) to display the path. Replace the current path command with the minimum path required to test for GP faults. For example path=c:\windows;c:\dos or, if Windows is running over the network path=:\windows;:\;c:\dos;:\ where is your hard disk drive, is a network drive, is the directory containing the shared Windows program files, and is the directory containing the network files. NOTE: If you need to test a specific application, include the application's directory in the path. 4. Make sure that your WINDOWS directory does not contain any .DRV files. These files should be located either in the WINDOWS\SYSTEM subdirectory or in the shared directory on the server if you are running a network installation of Windows. NOTE: If you are running a network installation of Windows, you should not have a WINDOWS\SYSTEM directory on your local hard disk drive or in the shared Windows directory on the network server. 5. Make sure you are using the correct version of the network shell. (Use the version that ships with Windows.) Eliminate Potential Video Conflicts ----------------------------------- If a poorly designed or corrupted video driver is installed, GP faults may occur at seemingly random times, sometimes very frequently. You may also see a blank screen or the system may hang when you quit an MS-DOS-based application that is running in a window. These problems can be caused by a poorly designed or corrupted video driver or by the use of the incorrect video grabber file. Use the following steps to ensure you are using a compatible video driver: 1. Quit Windows and use the Microsoft Diagnostics (MSD) program to check the video hardware. If you have a video BIOS dated earlier than 1988, contact your video card manufacturer to see if a more recent version of the BIOS is required for use with Windows. If a high-resolution card, such as the ATI or Orchid coprocessor card, is installed, make sure that it is configured correctly for your hardware--these cards may require that you select a vertical scan rate and monitor type. 2. Install the generic VGA driver by quitting Windows and running Setup from the WINDOWS directory. If this driver is already installed, press the ESC key when you are prompted with the following message: To replace the currently installed driver, press ESC. This ensures that new video driver, font, and video grabber files are installed. If this fails to correct the problem, repeat this procedure and install the VGA 3.0 driver. If the problems persist, install the EGA video driver. If none of these drivers improves the situation, reinstall the standard VGA video driver and continue troubleshooting. NOTE: The VGA (version 3.0) driver is not available in Windows 3.0. EGA is not available in Windows for Workgroups 3.11. 3. Make sure that the correct 286 and 386 grabber files are installed. The following entries should be present in the [boot] section of the SYSTEM.INI file; the corresponding files should be in the WINDOWS\SYSTEM subdirectory: In Windows 3.0: 286grabber=vgacolor.gr2 386grabber=vga.gr3 In Windows 3.1 and Windows for Workgroups 3.1: 286grabber=vgacolor.2gr 386grabber=vgadib.3gr or 386grabber=vga.3gr In Windows for Workgroups 3.11: 386grabber=vga.3gr Ensure You Are Using the Correct Switch for HIMEM.SYS ----------------------------------------------------- HIMEM.SYS is the default device driver Windows uses in the standard and 386 enhanced modes to access extended memory, including the high memory area (HMA)--the first 64K of extended memory (1024K-1088K). HIMEM.SYS accesses the HMA through the A20 line of memory using A20 "handlers." The method used to access the HMA depends on the hardware you are using, so HIMEM.SYS has been designed to use several different A20 handlers. HIMEM.SYS follows a routine at load time to determine which A20 handler is appropriate for your machine. Unfortunately, some nonstandard machines do not respond to the HIMEM.SYS tests, which can result in the wrong A20 handler being selected. Using the incorrect A20 handler can result in many problems, such as slow system performance and GP faults. The system may also hang when HIMEM.SYS loads, leaving the following message on the screen: HIMEM: DOS XMS Driver, Version x.xx - MM/DD/YY The /MACHINE switch is used to gain control of the A20 line by forcing HIMEM.SYS to use a specific handler. For example: device=c:\\himem.sys /machine:1 -or- device=c:\\himem.sys /m:1 To test the different HIMEM.SYS switches on your machine, edit the CONFIG.SYS file with an ASCII text editor and add the /MACHINE switch with one of the machine-specific handler numbers (1-16). If you do not know which number to use, refer to your current MS-DOS or Windows documentation. For most IBM PC/AT 100 percent- compatible machines, one of the IBM PC/AT compatible A20 handler switches (/M:1, /M:11, /M:12, /M:13) should work. If your computer is not listed in the documentation, you are not sure which number to use, or the machine number for your computer doesn't correct the problem, try these machine numbers in the following order: 1, 11, 12, 13, 8, 2-7, 9-10, 14-16. Check your current MS-DOS or Windows documentation for the list of machines that require a specific A20 handler. WARNING: When you are testing to see which A20 handler is appropriate, make sure you have a startup MS-DOS disk with an ASCII text editor (such as MS-DOS Editor or Edlin), because some A20 handlers will cause your machine to hang. For MS-DOS versions 6.2 and later, you can force the testing of XMS memory with the TESTMEM:ON parameter. If you continue to have problems accessing extended memory, try enabling and disabling XMS testing. For example: device=c:\\himem.sys /testmem:on -or- device=c:\\himem.sys /testmem:off Ensure Windows Is Configured for the Correct Computer Type and Network ----------------------------------------------------------------- ----- Some machines and networks require that you override the Windows Setup default setting for the computer type and network. If the correct selection is not made during Setup, Windows may not operate correctly, or you may receive GP faults. Machines that must be specifically selected during Windows Setup include the following: Windows | Workgroups Machine 3.0 | 3.1/3.11 | 3.1 | 3.11 ----------------------------------------------------------------- ------- AST(R)--all 80386- and 80486-based machines X | X | | AST Premium 386/25 and 386/33 (CUPID) | | X | X AT&T(R) PC | X | X | X AT&T NSX 20--Safari Notebook | X | X | X Everex(TM) Step 386/25 (or compatible) X | X | X | X Hewlett-Packard(R)--all machines X | X | X | X IBM PS/2(R) Model 70P | X | X | X IBM PS/2 Model L40sx | X | X | X Intel(R) 386SL-based system with APM | X | X | X MS-DOS system with APM | X | X | X NCR-all 80386- and 80486-based machines | X | X | X NCR PC386sx X | X | | NCR PC 925 X | | | NEC(R) PowerMate SX Plus X | X | X | X NEC ProSpeed 386 X | X | X | X Toshiba(R) 1200XE | X | X | Toshiba 1600 X | X | X | X Toshiba 5200 X | X | X | X Zenith(R)-all 80386-based machines X | X | | Zenith Data Systems-all 80386-based machines | X | | Zenith-all 386/486-based machines | | | X Networks that must be specifically selected during Windows Setup include the following: NOTE: This information does not apply to Windows for Workgroups. Windows Network 3.0 | 3.1/3.11 --------------------------------------------------------------------- 3Com(R) 3+Open(R) LAN Manager (XNS only) X | 3Com 3+Open | X 3Com 3+Share(R) X | X Artisoft(R) LANtastic(R) | X Banyan(R) VINES(R) 4.0 X | X DEC(R) Pathworks(TM) | X IBM OS/2(R) Lan Server | X IBM PC LAN Program X | X LAN Manager versions 1.x (or 100-percent compatible) X | X LAN Manager 2.0 (or 100-percent compatible) X | X LAN Manager 2.1 (or 100-percent compatible) | X Novell(R) NetWare(R) | X TCS(R) 10NET | X If your computer and/or network is on either of these lists and you did not select your computer type or network specifically during Setup, quit Windows and run the MS-DOS version of Setup from the WINDOWS directory. This allows you to make the proper selection without having to reinstall Windows. Use 386 Enhanced Mode for Troubleshooting ----------------------------------------- If GP faults occur in 386 enhanced mode but do not occur in standard mode, your system may have a memory conflict in the upper memory blocks (UMBs). Such errors occur only in 386 enhanced mode and most frequently in Windows 3.0, because version 3.0 does not inherit UMB usage from the expanded memory manager (EMM). To eliminate the possibility of a UMB conflict: 1. Edit the SYSTEM.INI file with the MS-DOS Editor or Edlin and insert the following line in the [386Enh] section: EMMExclude=A000-EFFF NOTE: This line is not case sensitive. If you are using an expanded memory manager, such as EMM386.EXE or Qemm(TM), with Windows 3.1 and Windows for Workgroups, you must either disable it or exclude the memory range shown above with the appropriate EMM. This information is inherited by Windows from the EMM and overrides any entries in the SYSTEM.INI file. The following is an example of excluding the memory range with EMM386.EXE: device=c:\windows\emm386.exe noems x=A000-EFFF IMPORTANT: If you are using Windows 3.1 or Windows for Workgroups, and you are not using an EMM, use the command WIN /D:X to load Windows from the MS-DOS command prompt. The /D:X switch excludes the memory range A000-EFFF from mapping, similar to the statement EMMExclude=A000-EFFF in the [386Enh] section of the SYSTEM.INI file. However, as with the EMMExclude= statement, this switch is overridden by any settings inherited from the EMM. 2. If making the above change corrects the problem, determine the position of all hardware adapters in the adapter segment and exclude them specifically, rather than excluding the entire region. If necessary, you can use multiple EMMExclude= lines to do this. If you leave the entire range excluded, Windows cannot set up expanded memory for MS-DOS-based applications. If you are using a Micro Channel(R) Architecture (MCA) bus machine, such as an IBM PS/2, you can determine the adapter location by restarting the machine with the IBM Reference Disk in drive A. If you are using an Industry Standard Architecture (ISA) bus machine, consult your adapter documentation and/or your manufacturer's technical support service for information on the memory locations the bus machine uses. 3. Disable virtual hard disk access. If you are running Windows 3.1 or Windows for Workgroups, start Windows with the /D:V parameter (WIN /D:V). If this prevents the GP faults, add the following line in the [386Enh] section of the SYSTEM.INI file: VirtualHDIRQ=OFF If you are running Windows 3.0, edit the SYSTEM.INI file and comment out the VirtualHDIRQ= line in the [386Enh] section. (To comment out a line, use an ASCII text editor, such as Windows Notepad, to edit the .INI file and place a semicolon at the beginning of the appropriate line.) 4. Ensure your permanent swap file is not corrupted. If you are running Windows 3.1 or Windows for Workgroups, you can remove your permanent swap file by using the 386 Enhanced icon in the Control Panel window. If you are running Windows 3.0, restart Windows in real mode and run the Swapfile program with the following steps: a. Start Windows in real mode by typing "win /r" (without the quotation marks). b. Close any applications that load automatically. c. From the File menu, choose Run. d. Type "swapfile" (without the quotation marks) and then press the ENTER key. If removing the permanent swap file corrects the problem, optimize your hard disk with a program such as Symantec's Speed Disk or PC Tools(TM) Compress and then reinstall the permanent swap file. 5. Turn off 32-bit disk access and 32-bit file access. If you are running Windows 3.1 or Windows for Workgroups, start Windows with the /D:F parameter (WIN /D:F) to disable 32-bit disk access. If you are running Windows for Workgroups 3.11, start Windows with the /D:C parameter (WIN /D:C) to disable 32-bit file access. The /D:F and the /D:C parameters (WIN /D:FC) can be combined to disable 32-bit disk access and 32-bit file access at the same time. REINSTALLING WINDOWS ==================== If you have followed all the above steps and still receive GP faults, there is most likely a problem with the machine or the way the hardware is configured. Use the following procedure to reinstall Windows to eliminate any possible remaining software or disk-integrity conflicts: 1. Remove any hardware such as external drives, modems, sound cards, and so forth from the machine. If the machine uses other special hardware, such as a full-page monitor, printer-sharing devices, or hardware keys used for copy protection, these items should be removed or swapped for standard devices that are known to work correctly. 2. Use the machine's CMOS Setup program to disable any feature that moves memory. (Consult your hardware documentation for specific instructions on modifying the CMOS settings.) This includes video shadowing, ROM BIOS shadowing, and any feature dealing with A20 handling. Also make sure the machine's primary startup (boot) drive is drive A. 3. Delete any reference to Windows on the PATH command in your AUTOEXEC.BAT file. Also, remove the DEVICE command for HIMEM.SYS from the CONFIG.SYS file. For more information, see the "Eliminate Software Conflicts at the MS-DOS Level" section on page 6 of this document. 4. Run Windows Setup with the following steps: a. To run Windows Setup in Custom mode, type "a:setup" (without the quotation marks) and press ENTER. When prompted for Express or Custom Setup, press C for Custom Setup. b. When you are prompted with the current Windows directory name, choose a new directory (such as WINTEST) to make sure the files are copied to a new location on your hard disk. c. At the configuration screen, ensure the appropriate options are selected for your specific hardware. Make sure the Computer setting is correct, set the Mouse option to "no mouse or pointing device," and set the Display option to VGA. Press the ENTER key to continue. d. In the Windows Setup dialog box, clear the Set Up Printers check box (press ALT+P) and the Set Up Applications Already On Hard Disk(s) check box (press ALT+A), then choose the Continue button. e. Clear all five check boxes in the Component section of the Windows Setup dialog box and choose the Continue button. Since you don't have mouse functionality at this time, clear the check boxes as you did in the previous step by pressing the ALT key plus the underlined letter in the component name. f. Choose the Change button in the Virtual Memory dialog box and then choose the OK button. g. Under New Settings, select None in the Type box. h. Choose the Change button and then choose the Yes button. i. Choose the Continue button to allow Windows Setup to update your CONFIG.SYS and AUTOEXEC.BAT files. You now have the minimum Windows installation, with the new Windows files in a different location on the hard disk. If this doesn't eliminate the GP faults, a hardware or BIOS conflict exists somewhere in your system. ----------------------------------------------------------------- -------- TO OBTAIN THIS APPLICATION NOTE =============================== - On CompuServe, GEnie, and Microsoft OnLine, Application Notes are located in the Microsoft Software Library. You can find WW0524 in the Software Library by searching on the word WW0524, the Q number of this article, or S13364. WW0524 was archived using the PKWARE file-compression utility. - Application Notes are available by modem from the Microsoft Download Service (MSDL), which you can reach by calling (206) 936-6735. This service is available 24 hours a day, 7 days a week. The highest download speed available is 14,400 bits per second (bps). For more information about using the MSDL, call (800)936-4200 and follow the prompts. To obtain WW0524, download WW0524.EXE. WW0524.EXE is a compressed, self-extracting file. After you download WW0524, run it to extract the file(s) it contains. - On the Internet, Application Notes are located on the Microsoft anonymous ftp server, which you can reach by typing "ftp ftp.microsoft.com" (without the quotation marks) at the ">" command prompt. - You can have this Application Note mailed or faxed to you from the automated Microsoft Windows 3.0 and 3.1 FastTips Technical Libraries, which you can call 24 hours a day, 7 days a week at (800) 936-4200. NOTE: The FastTips Technical Library is available only to customers within the U.S. and Canada. - If you are unable to access the source(s) listed above, you can have this Application Note mailed or faxed to you by calling Microsoft Product Support Services Monday through Friday, 6:00 A.M. to 6:00 P.M. Pacific time at (206) 637-7098. If you are outside the United States, contact the Microsoft subsidiary for your area. To locate your subsidiary, call Microsoft International Sales Information Center at (206) 936-8661. KBCategory: kbnetwork kbdisplay kbsound kbtool kb3rdparty kbtshoot kbfile kbappnote KBSubcategory: wfw wfwg Additional reference words: appnote 3.1 3.10 3.00 3.0 3.00a t-shoot tshoot gpf gp fault win31 Troubleshooting MS-DOS 6.x and EMM386.EXE Article ID: Q98768 ---------------------------------------------------------------- ---- The information in this article applies to: - Microsoft MS-DOS operating system versions 6.0, 6.2, 6.21, 6.22 - Microsoft Windows for Workgroups versions 3.1, 3.11 ---------------------------------------------------------------- ---- SYMPTOMS ======== You encounter unexpected behavior (for example, your system stops responding [hangs] or a program hangs) when using the version of EMM386.EXE included with the following products: Product Version of EMM386.EXE ---------------------------------------------------------- MS-DOS 6.0 4.45 MS-DOS 6.2 and 6.21 4.48 MS-DOS 6.22 4.49 Windows for Workgroups 3.1 4.44 Windows for Workgroups 3.11 4.48 WORKAROUND ========== Use the steps in the following sections to pinpoint and then correct the problems. Troubleshooting MS-DOS 6.x and EMM386.EXE ----------------------------------------- 1. Turn your machine off, then turn it back on (cold boot) to fully reinitialize the system. 2. Start MS-DOS interactively by pressing the F8 key as soon as the text "Starting MS-DOS..." appears. 3. When prompted to load EMM386.EXE, choose N for No. If the problem persists without loading EMM386.EXE, something other than EMM386.EXE is causing the problem. 4. If the problem disappears when EMM386.EXE is not loaded, edit the CONFIG.SYS file as follows using an ASCII text editor (such as MS-DOS Editor): device=c:\dos\emm386.exe x=a000-f7ff nohi noems novcpi nomovexbda notr NOTE: If the problem is specific to the use of the CTRL+ALT+DEL key combination (warm boot) and EMM386.EXE, add the ALTBOOT parameter to the above line. 5. Cold boot the machine after making the above changes. If the problem persists, the system may have faulty RAM chips or may require a special machine switch for HIMEM.SYS. In addition, any CMOS settings (such as shadow RAM) may need to be disabled, or the system ROM BIOS may need to be upgraded for compatibility with MS-DOS 6.x. Consult the system vendor for information on CMOS settings and/or the availability of BIOS upgrades. 6. If the problem disappears after loading EMM386.EXE as specified above, EMM386.EXE itself is not the source of the problem. Instead, the problem may be related to some service(s) that EMM386.EXE provides. If the above procedure corrected the problem, remove each command-line option for EMM386.EXE one by one and cold boot the machine. If the problem reappears, use the information below to find a resolution. X=A000-F7FF ----------- If excluding the entire upper memory area (UMA) resolves a system problem, EMM386.EXE may be scanning too aggressively and setting up upper memory blocks (UMBs) on top of some adapter ROM or RAM. Use any available hardware documentation (including documentation on the add-on hardware devices such as video, network, and disk controller cards) to identify any ROM or RAM present in the UMA for that device, and exclude all pertinent regions. If the hardware documentation is not available or does not give the required information, you can use the Microsoft Diagnostic Utility (MSD) to identify the memory regions. NOHI ---- EMM386.EXE has the ability to load a portion of itself into UMBs. If the NOHI option corrects the problem with EMM386.EXE, EMM386.EXE may be loading into an occupied UMB. (Excluding the appropriate ranges in the UMA may correct this problem; see the "X=A000-F7FF" section above.) If all such regions are excluded, EMM386.EXE cannot be loaded high on the system, and NOHI must be used. Contact the system manufacturer or vendor for additional information on compatibility with EMM386.EXE. NOEMS ----- If the NOEMS parameter corrects the problem with EMM386.EXE, EMM386.EXE may be inadvertently conflicting with some hardware ROM or RAM address in the UMA when attempting to establish an expanded memory (EMS) page frame. If EMS is required to run MS-DOS-based applications, use the parameter FRAME= or M (where is the defined hexadecimal address) to explicitly specify placement of the EMS page frame in a nonconflicting region. If no applications require EMS, simply continue to use the NOEMS parameter. NOVCPI ------ The NOVCPI switch disables Virtual Control Program Interface (VCPI) support and can be used only in conjunction with the NOEMS parameter. If using NOVCPI corrects the problem, the application may not be fully compatible with the EMM386.EXE VCPI allocation scheme. Either continue using the NOVCPI parameter, or do not load EMM386.EXE when using the application. NOMOVEXBDA ---------- Some machines use the last kilobyte of conventional memory for an extended BIOS Data Area. By default, EMM386.EXE remaps this memory area into the UMA instead of conventional memory. If this causes unexpected system behavior, the NOMOVEXBDA parameter MUST be used. NOTR ---- EMM386.EXE has a detection code to search for the presence of a token ring network adapter. This detection code may cause some computers to hang. The NOTR switch can be used to disable this search. MORE INFORMATION ================ For more information about EMM386.EXE command-line parameters and syntax, refer to MS-DOS Help by typing "help emm386.exe" (without quotation marks) at the MS-DOS command prompt and pressing ENTER. KBCategory: kbother kbdisplay kbtshoot kbtlc KBSubcategory: wfw msdos msdoswfw wfwg Additional reference words: 6.22 6.00 6.20 golden emm hang lockup crash tshoot conflict emm386 Windows for Workgroups Mail Issues Article ID: Q99108 ---------------------------------------------------------------- --- The information in this article applies to: - Microsoft Windows for Workgroups versions 3.1, 3.11 ---------------------------------------------------------------- --- SUMMARY ======= This article discusses several of the most common issues and procedures for setting up and using Windows for Workgroups Mail. This article is divided into the following topics: - "Re-creating the Mail Initialization Procedure" describes the steps you should use in case errors occur when you initialize Mail for the first time. These procedures are useful if you incorrectly specify the option of connecting to an existing postoffice or becoming the Workgroup Postoffice (WGPO). - "Setting up a Postoffice Across the Network" describes the steps for setting up and administering a postoffice on one machine while placing the WGPO on another machine. This section includes postoffice naming conventions and troubleshooting steps. - "Creating a WGPO on a Novell NetWare Server" corrects a documentation error in the "Windows for Workgroups Mail User's Guide" and provides additional information needed to successfully set up a Novell NetWare Postoffice. - "Moving a WGPO from One Machine to Another" describes steps for moving a WGPO to a new server without transferring WGPO administration responsibilities. - "Changing the WGPO Administrator" describes steps for transferring WGPO administration and management responsibilities from one person to another. - "Allowing Multiple Users to Log On to Windows for Workgroups Mail on the Same Machine" explains how to set up one machine for multiple postoffice accounts. - "Removing a Mail User and Installing a New User on a WFWG Machine" describes steps for removing a Windows for Workgroups Mail and Schedule+ user from a WFWG machine and adding a new user to that machine, without reinstalling Windows for Workgroups. - "Set Access Privileges or Open Other's Appt. Book Options Unavailable/Disabled" explains why these options are unavailable. NOTE: There may be situations in which your needs exceed the capabilities of Windows for Workgroups Mail, even with the procedures outlined below. If that is the case, you may want to consider upgrading to Microsoft Mail version 3.0, or higher. RE-CREATING THE MAIL INITIALIZATION PROCEDURE ============================================= When you first run Windows for Workgroups Mail, you are given the option to connect to an existing postoffice or create a new postoffice. After you make your selection, you cannot go back and change your selection. Steps to Reinitialize Mail -------------------------- If you want to change your initial selection, you must use the following steps to reinitialize Mail so that you can select the option you want. 1. Open the MSMAIL.INI file in an ASCII text editor, such as Microsoft Windows Notepad. 2. Disable the ServerPath= and the login= lines by typing a semicolon (;) at the beginning of each line. 3. Add or edit the CustomInitHandler= line so that it appears as follows: CustomInitHandler=WGPOMGR.DLL,10 4. Run Mail. The initialization procedure begins. How Mail Initialization Works ----------------------------- The initialization procedure is defined for Mail in the MSMAIL.INI file on the CustomInitHandler= line. This setting is defined as: CustomInitHandler=WGPOMGR.DLL, When you run Mail, it checks for the existence of the CustomInitHandler= line in the MSMAIL.INI file. If this line exists, Mail attempts to execute the procedure defined by this parameter setting. If the execution fails because the dynamic-link library (DLL) file WGPOMGR.DLL cannot be found or the procedure is undefined, Mail continues without reporting an error. The procedure, located in WGPOMGR.DLL, displays the Connect Or Create dialog box to allow you to either connect to an existing remote postoffice or create a new Workgroup Postoffice. - If you choose the Cancel button, WGPOMGR.DLL closes Mail. - If you choose the OK button, WGPOMGR.DLL removes the CustomInitHandler= line from the MSMAIL.INI file and returns to Mail, automatically signing you in to the postoffice. SETTING UP A POSTOFFICE ACROSS THE NETWORK ========================================== With Windows for Workgroups Mail, the Workgroup Postoffice can be set up from one computer to another computer across the network. For the example below, assume the following conditions are true: - The postoffice is set up and administered from machine 1. - The postoffice files are actually kept on machine 2. NOTE: The user on machine 1 is the Postoffice Manager, but the postoffice files are stored on machine 2 - Machine 1 is a Windows for Workgroups machine. - Machine 2 is a machine with server/sharing capabilities, such as a Windows for Workgroups machine, a LAN Manager 2.1 server, or a Novell server. NOTE: Novell servers require some special attention. Refer to the "Creating a WGPO on a Novell NetWare Server" section in this article. Steps to Connect to Other Machines ---------------------------------- After Windows for Workgroups Setup is complete on machine 1, the designated administrator of the Workgroup Postoffice should take the following steps: 1. On machine 1, from the Main group, start Workgroups Mail. 2. Choose Create A New Workgroup Postoffice. 3. To connect to machine 2, choose the Network button. If Machine 2 is a Windows for Workgroups machine or a LAN Manager 2.1 server, type the server name and share name (that is, <\\server\share>) where you want the postoffice created, then choose OK. NOTE: You must have access rights to the server and the share. If machine 2 is a Novell server, you must be logged onto the Novell server and have the correct permissions. Then, you should connect to the server and use one of these conventions: server/share:directory \\server\share\directory remapped drive:\directory For more information about the Novell naming conventions, check your Novell NetWare documentation. For more information about Windows for Workgroups naming conventions, see the "Windows for Workgroups Server, Share, and Mail Naming Conventions" section in this article. NOTE: Do not use the double-backslash convention mentioned above on Novell NetWare 4.x servers. If you do, you receive the following error message when you try to connect to the mail server: Mail could not connect to your mail server. If you remove one of the backslashes, you do not encounter this error message. 4. After the Workgroup Postoffice is established, check to ensure that the postoffice is shared properly on machine 2. Postoffice Naming Conventions ----------------------------- The following name length limitations exist in Microsoft Windows for Workgroups Mail: Server Name: 15 characters (including spaces) Share Name: 12 characters (including spaces) Workgroup Postoffice Share: 8 characters Windows for Workgroups Mail clients cannot connect to a Workgroup Postoffice if the share name contains more than eight characters, or if the Workgroup Postoffice server name or share name contains any spaces. For example, the following are examples of invalid Workgroups Postoffice server or share names: \\ser ver\wgpo \\server\wg po \\server\post office The following is a valid Workgroups Postoffice server or share name: \\server\wgpo NOTE: Microsoft recommends that the share name "WGPO" be used for consistency across all Workgroup Postoffices. Resolving Local Postoffice Connection Problems ---------------------------------------------- If a Windows for Workgroups mail administrator sets up the Workgroup Postoffice (WGPO) on another workgroup user's machine, that other user cannot connect to the postoffice and receives one of the following error messages: The selected network path cannot be found -or- This operation is not supported on this machine For example, if the mail administrator, working at a machine named "Admin", creates the WGPO on a machine called "machine1," the user of machine1 is unable to connect to the WGPO. To work around this problem, you must manually edit or create a new MSMAIL.INI file for machine1. NOTE: Windows for Workgroups Mail defaults to uniform naming conventions (UNC) to specify the location of the postoffice. UNC cannot be used to connect a user to a share on his/her local machine. Browsing for the WGPO share on the local machine results in the "not supported" error message. Manually typing in the UNC name of the share (\WGPO) results in the path not being found, as does typing in the local path (F:\WGPO). Workaround ---------- 1. Copy the MSMAIL.INI file from a machine that is already connected to the WGPO. 2. Edit the MSMAIL.INI file for machine1 as follows: a. Change the ServerPath= statement to reflect the local path. b. Change the login= statement to reflect the machine1 mailbox (as set up by the Mail Administrator). 3. Copy the newly edited MSMAIL.INI file to the WINDOWS directory on machine1. Note that you can use the Mail Administrator's MSMAIL.INI file as the source for the MSMAIL.INI file for machine1. If you use this file, be sure to remove all references to the WGPOMGR.DLL file. CREATING A WGPO ON A NOVELL NETWARE SERVER ========================================== Appendix B of the "Windows for Workgroups Mail User's Guide" for version 3.1 describes how to create a Workgroup Postoffice (WGPO) on a Novell NetWare server. Step 7 of the instructions directs the user to create the WGPO by following the steps explained in Chapter 5 of the "User's Guide." The last step in Chapter 5 is to share the newly created WGPO. This step should NOT be done since the postoffice will be on a NetWare server. If the user attempts to share the WGPO directory on the NetWare server, the following error message is displayed: You can only share resources that are on your computer. If you are trying to share a printer, make sure that it is a local printer and that the TEMP directory is on a local drive. Sharing the NetWare postoffice is not necessary because connections to the WGPO are made with the ServerPath= entry in the MSMAIL.INI, which reflects the appropriate NetWare Workgroup Postoffice location. Sharing a redirected, network drive is not possible in Windows for Workgroups. MOVING A WGPO FROM ONE MACHINE TO ANOTHER ========================================= If you need to transfer a WGPO from one server to another and you don't want to transfer your administrator responsibilities, follow these steps: 1. Be sure that you have full access to the share where the WGPO will be moved. 2. Use File Manager to move the WGPO to its new location; be sure to move all subdirectories. 3. For each user and the WGPO Administrator, open the MSMAIL.INI file in a text editor (such as Notepad), and change the ServerPath= line so that it points to the new server. For example: ServerPath=c:\windows\wgpo 4. Save your changes, and restart the system. The WGPO administrator should be able to administer the postoffice an all users should be able to connect to the WGPO as they did before. CHANGING THE WGPO ADMINISTRATOR =============================== This section describes the procedure for transferring WGPO administrator responsibilities from one person to another. In this procedure, the following conventions are used: - Admin1 is the current Postoffice Administrator. - Admin2 will become the new Postoffice Administrator. The following fields are required: Name: Mailbox: Password: (You must know the passwords for Admin1 and Admin2.) Steps to Change Administrators ------------------------------ 1. Copy the MSMAIL.INI file from the WGPO machine to a floppy disk so that you can use it later when establishing the Admin2 account. 2. From Admin1's machine, sign on to Mail, select the Mail option, then select Postoffice Manager. 3. Select the Details option, and write down the required information for Admin1 and Admin2 (obtain the passwords from the Administrators; passwords don't appear in the details dialog box). 4. If Admin1 no longer needs a mail account, delete the user account for Admin2 and edit the details of the Admin1 account so that it matches the new Postoffice Administrator's account (Admin2). 5. Open Admin1's MSMAIL.INI file in a text editor (such as Notepad) and remove the following lines: WGPOMgr1=3.0;Mail;;13 WGPOMgr2=3.0;Mail;&Postoffice Manager...;14;WGPOMGR.DLL;0;;Manage Workgroup Postoffice;MSMAIL.HLP;2870 NOTE: These two lines are the last two lines of the [Custom Commands] section. 6. Admin1 should exit and sign out of Mail. 7. On Admin2's machine, open the MSMAIL.INI file that was copied to the floppy disk. Using a text editor (such as Windows Notepad), cut the following lines from this file: WGPOMgr1=3.0;Mail;;13 WGPOMgr2=3.0;Mail;&Postoffice Manager...;14;WGPOMGR.DLL;0;;Manage Workgroup Postoffice;MSMAIL.HLP;2870 Then, paste these two lines into the [Custom Commands] section of Admin2's MSMAIL.INI file (located in the Windows for Workgroups or Windows directory). Be sure that these lines are the last two lines in the [Custom Commands] section. 8. Save the changes made to the MSMAIL.INI file, then start Mail. NOTE: A message may appear that states Mail was unable to find your .MMF file. A dialog box that displays the .MMF file that was detected then appears. Select the .MMF and choose OK to select the .MMF file found on the hard disk drive. 9. Open Mail and select the Mail option to verify the Postoffice Administrator option is now available on Admin2's machine. 10. If necessary, create a user account for Admin1. ALLOWING MULTIPLE USERS TO LOG ON TO WFWG MAIL ON THE SAME MACHINE ================================================================= = You can set up Windows for Workgroups Mail so that multiple users can log on with individual Mail files. Steps to Establish Multiple Users --------------------------------- 1. Set up the Workgroup Postoffice. This cannot be done on the machine that will be used by multiple users. 2. Start Windows for Workgroups Mail on the machine that multiple users will be using, log on to the remote Postoffice, and then exit and sign out of Mail. This creates an MSMAIL.INI file. 3. Open the MSMAIL.INI file in a text editor (such as Notepad), and change the line Noserveroptions=1 to: Noserveroptions=0 This allows you to select the Server option in Mail. 4. Start Mail again and choose the Options menu. 5. Select the Server option, and change the MMF path in the File box from C:\WINDOWS\MSMAIL.MMF to C:\WINDOWS\.MMF where is the name of the user who logged in. 6. Choose OK. This renames the MSMAIL.MMF file to the Mailbox Name with an .MMF extension. 7. To add another user, rename the MSMAIL.INI file and log on to the mail server with the new user's name. Then, exit and sign out of Mail and follow steps 2 through 7. Repeat for as many users as necessary. NOTE: The last account that you create is the default account name to use when starting Mail. REMOVING A MAIL USER AND INSTALLING A NEW USER ON A WFWG MACHINE ================================================================ The postoffice administrator may need to remove and recreate Mail and Schedule+ accounts on a machine if that machine is used by a different person than the person for whom Mail and Schedule were first configured. Use the following steps to remove a user from a machine and then add a new user, without having to remove and reinstall Windows for Workgroups: 1. To remove the old user from the Mail, start Mail and select the Postoffice Manager option. Select the name of the user to be deleted, and then choose Remove User. 2. To add the new employee's account, select Add User and then set up the mailbox information for the new user. Choose OK to save your entries. 3. On the machine containing the old user's Mail and Schedule+ files, start File Manager, making sure that neither Mail nor Schedule+ are running, and delete the following files from the \Windows directory: MSMAIL.MMF MSMAIL.INI SCHDPLUS.INI .CAL.<=== where is the old user's login name 4. Start Mail from the icon on the user's machine. 5. You should receive a message asking if you want to connect to an existing postoffice or create a new postoffice. Select the connect to an existing postoffice option. 6. From the Network Disk Resources dialog box, select the postoffice server and share; for example, "\\server\wgpo" (without the quotation marks). 7. You should receive a message asking if you have an account on the postoffice. Respond Yes if you have set up the user's account as described in step 2. 8. When the Mail Sign In screen is displayed, sign in to Mail. When the Mail screen appears, exit Mail. 9. To make the necessary changes for the user's Schedule+ account, have each user's on the Postoffice (except the user you are removing and the user you are setting up) perform these steps: a. Log in to Schedule+. b. Make a change of some type. c. Exit Schedule+ d. Restart Schedule+, and then exit a second time. This updates each existing user's .CAL file on the server (except the user you are removing from the system). 10. To set up Schedule+ for the new user, you need to delete the old user's .CAL file from the postoffice's CAL subdirectory. These files have a numerical filename and a .CAL extension; for example, "00000003.CAL." To determine which .CAL file to delete, look at the file dates. All of the .CAL files except the old user's .CAL file should have the current day's date because step 9 updated them. Delete the .CAL file that has a noncurrent date. 11. Log in to Schedule+ using the new user's Mail login name and password. SET ACCESS PRIVILEGES OR OPEN OTHER'S APPT. BOOK OPTIONS UNAVAILABLE/DISABLED ======================================================== When you run Schedule+ with Microsoft Windows for Workgroups version 3.11 while using Microsoft At Work PC Fax, you cannot choose Set Access Privileges from the Options menu or Open Other's Appt. Book from the File menu (both options are unavailable [dimmed]). No error messages appear, and both Mail and Schedule+ seem to work correctly. If you select the FAX Only option when setting up Microsoft At Work PC Fax instead of the FAX And Email option, Mail works correctly only if it was set up before the At Work PC Fax software. However, Mail runs Schedule+ offline only, disabling any of the online options in Schedule+. When the FAX Only option is selected, the transport entry in the SCHDPLUS.INI file is changed to the following value: ScheduleTransport=TRNOFF To activate the Set Access Privileges option, change the line to read as follows: ScheduleTransport=TRNSCHED.DLL When you restart Schedule+ after making this change, the offline calendar file updates the server's copy of the calendar file, and you can then use the Set Access Privileges, Open Other's Appt. Book, Work Online, and Work Offline menu options. REFERENCES ========== "Microsoft Windows for Workgroups Mail User's Guide," for version 3.1, Appendix B "Microsoft Windows for Workgroups Resource Kit" for version 3.1 KBCategory: kbnetwork kb3rdparty kbtool KBSubcategory: wfw wfwg Additional reference words: 3.1 3.10 wfwg post office novell LANmanager limit schedule setup How to Troubleshoot WFWG Network Connection Problems Article ID: Q104322 ---------------------------------------------------------------- ------ The information in this article applies to: - Microsoft Windows for Workgroups version 3.1 ---------------------------------------------------------------- ------ SUMMARY ======= In a Microsoft Windows for Workgroups version 3.1 network, hardware- and software-related problems can cause one or more computers to lose the ability to browse or communicate with other computers. These problems range from no network functionality at all to random errors when transmitting data across the network. This article provides troubleshooting steps that you can use to diagnose and resolve workstation communication problems in a Windows for Workgroups network. Note that troubleshooting communication problems is not always a straight-forward process. If one of the procedures outlined below doesn't work, go on to the next until the problem is fixed. To increase your knowledge of the major issues, you may want to read this entire article before you proceed. (This may also reduce the time needed to solve the problem.) BEFORE YOU BEGIN ================ Before proceeding with the troubleshooting steps, consider the following: - Has this configuration ever worked before, or did this just start happening? If it just started, what has changed between the time this configuration was working and the time it stopped working? - Has new hardware, cabling, or software been added? If this new addition is removed, does the problem go away? - Is this problem occurring on one computer, several, or all of them? If the problem is happening on all computers, it may be cabling or connector related. If the problem is happening on only one or a few computers, it may be software or hardware related. - Is the connection to the computer active? (If the card has transmit/ receive data lights, are they blinking?) IMPORTANT: Make backup copies of the following system configuration files before doing any troubleshooting: CONFIG.SYS AUTOEXEC.BAT PROTOCOL.INI SYSTEM.INI WIN.INI TROUBLESHOOTING STEPS ===================== Check Setup and Startup ----------------------- 1. Check for any error messages while the computer is booting. To prevent error messages from scrolling off the screen, place a PAUSE statement at the beginning and the end of your AUTOEXEC.BAT file. 2. Verify that the computer you are trying to view is in 386 enhanced mode and has sharing enabled. To check this, open Control Panel, choose Network, and make sure the Sharing Enabled box is selected. 3. If this is a new network (that is, another network was NOT previously used), verify that the network card settings in the Network dialog box of Control Panel are correct. If Windows for Workgroups was installed over Windows 3.1 and another network (such as Novell NetWare), it is possible that the Windows for Workgroups Setup program did not detect the previous network, which may be conflicting with Windows for Workgroups. You probably need to remove changes the previous network made to Windows configuration files (primarily the SYSTEM.INI file). 4. Run CHKDSK on the drive where Windows is installed. If Windows system files are corrupted, Windows is unstable and may need to be reinstalled. If CHKDSK shows errors, repair the errors by running CHKDSK with the /F parameter or by using a disk utility to repair the files on the hard disk drive. If there is data corruption, it may be necessary to reinstall Windows for Workgroups. 5. Clean boot each computer (that is, load only those drivers necessary to start the computer). For more information about performing a clean boot, query on the following words in the Microsoft Knowledge Base: wfwg and clean boot Browse Other Machines --------------------- Attempt to view other computers on the network in File Manager. Choose the Connect Net Drive button or choose Connect Net Drive from the Disk menu, and type the computer name preceded by two backslashes, for example \\ in the Path box, and then press ENTER. If you can view other computers on the network by manually entering computer names but you cannot view these computers during normal operations, consider the following possible causes: - The entry for VBROWSE.386 may not be on the network= line in the [386Enh] section of the SYSTEM.INI file, or VBROWSE.386 may be missing from the Windows SYSTEM directory, or VBROWSE.386 may be corrupted. If the network= line is missing, use a text editor (such as Windows Notepad) to add the following to the [386Enh] section of the SYSTEM.INI: network=VBROWSE.386 If necessary, reinstall the VBROWSE.386 file in the Windows SYSTEM subdirectory. - A "browse server" may not have been selected on the network. In Windows for Workgroups, a computer that maintains a list of Workgroups servers is selected. Sometimes this takes from 5 to 15 minutes to establish. If no browse server exists, you cannot browse servers on the network. Wait a few minutes and try again. If the local workstation name (but no other computer name) appears in the Show Shared Directories On dialog box, the network card is probably configured correctly, but the problem may be in the network cabling or the other computer's network card configuration. Check Cabling ------------- Make sure the network cabling is connected to both the computer you are using AND the computer you are trying to communicate with. Most network problems are caused by faulty cabling and/or connectors. Check the cabling and connectors on each workstation. If the network is using Thin Ethernet, connect two computers with a single cable, T- connectors, and terminators that are known to work properly. If the network is using twisted-pair (RJ-45) cable, you must use a HUB or concentrator. Windows for Workgroups does not support direct connections of RJ-45 cable between computers. This check isolates possible cabling and/or connector problems that may not be clearly visible. NOTE: It may also be necessary to reroute network cabling away from sources of electrical interference (such as fluorescent lights). If the network topology is 10Base2 (Thin Ethernet or Thinwire), place a 50 Ohm terminator on the network card. If the local computer name now appears in the Show Shared Directories On dialog box (but not when the regular cabling is attached), some type of cabling and/or connector problem exists. Examples include an electrical short in the cabling, improper termination, and using the wrong type of cabling. Check to ensure that each computer's T- connector is secured on each network card, that 50 Ohm terminators are at each end of the network, and that RG-58 cabling (not RG-59 or RG-62) is being used. If the local computer name does not appear in the Show Shared Directories On dialog box, the problem is with the local network card's configuration (either hardware or software). (Refer to "Test the Network Card," later in this article.) If your wiring is 10Base2 (Thin Ethernet), a quick test to see if the cabling is the problem is to remove the T-connector and place a terminator directly on the BNC connector on the network card. If doing so causes the machine to be able to "see itself" in File Manager, the problem is most likely with the existing cabling. If placing a terminator on the network card doesn't identify the problem (or your cabling is other than 10Base2), try the following steps: 1. Change the IRQ and/or I/O address that the network card is using. To do so with software-configurable network cards: a. Open Control Panel, then choose the Network icon. b. Choose Adapters, then choose Setup. c. Select a different IRQ and/or I/O address. You may need to try several selections if you do not know what your other hardware is configured to use. 2. Reinstall the network card drivers as follows: a. Clean boot your system. To do this, remove the Windows for Workgroups network drivers and any unnecessary entries from the CONFIG.SYS and AUTOEXEC.BAT files. For more information about a clean boot, query on the following words in the Microsoft Knowledge Base: wfwg and clean boot b. Rename the PROTOCOL.INI file, which is usually in the Windows directory unless you are using disk-compression software. If disk- compression software (such as SuperStor) is used, the PROTOCOL.INI file should be in the root directory. c. Restart the computer and start Windows for Workgroups. You will receive at least one error message about the network drivers being loaded; this is to be expected. d. In Control Panel, choose Network, then choose Adapters. The list of Currently Installed Adapters should be blank. Choose Add and select your network card from the list that appears. NOTE: If the network card is hardware-configurable (with jumpers or DIP switches), the settings on this screen need to match the actual settings of the jumpers or switches on the card, unless they say "Automatic or unused." If the card is software-configurable, you may need to select a different IRQ, I/O Address, or RAM Address to resolve a connectivity problem. For example, some disk controllers come configured using I/O 300h, which is also the default for some network cards. e. Restart the computer and attempt to communicate with other computers on the network as described in "Browse Other Machines" above. 3. Check the SYSTEM.INI file for the following lines and remark them out if they exist. To remark out a line from the SYSTEM.INI file, place a semicolon (;) at the beginning of the line. InDOSPolling=True TimerCriticalSection= V86ModeLanas= 4. Rebuild the Windows startup files (WIN.INI and SYSTEM.INI). For more information about rebuilding the SYSTEM.INI file, query on the following words in the Microsoft Knowledge Base: system.sr_ and wfw To rebuild the default WIN.INI file, expand WIN.SR_ from Windows for Workgroups Disk 3. To do this, place Disk 3 in a floppy disk drive, type the following, and press ENTER: c:\windows>expand x:win.sr_ -r If Windows for Workgroups is still not working after you complete the steps above, and it has worked previously, the next step is to reinstall Windows for Workgroups in another directory. Reinstalling Windows for Workgroups in a clean directory should restore the configuration to the point at which it was working when first installed. When you start the Windows for Workgroups Setup program, choose Custom Setup, and enter a new directory name, such as C:\WFWTEST. If Windows for Workgroups still is not working correctly, it is most likely that some type of problem with your cabling, connectors, or network card exists. Test the Real Mode Redirector ----------------------------- The following test uses the Windows for Workgroups network components to generate a NetBIOS name conflict on the network (each computer must have a unique computer name on the network). To do this test, set two computers to the same computer name and check to see if an error message is generated. If an error message is displayed, the computers are communicating. If no error occurs, a hardware problem exists on the network. 1. To change the computer name, do one of the following: - Change the value for Computername in the Network dialog box of Control Panel. -or- - Edit the SYSTEM.INI file and change the setting for ComputerName= in the [Network] section to the name of another computer. 2. Reboot the computer, then start the real mode redirector by typing the following at the MS-DOS command prompt: net start workstation 3. The following error should appear: LANA 0 reported error 52: A duplicate workgroup or computer name exists on the network. For information about LANA numbers, type NET HELP 3280. If the error message is displayed, the two computers are communicating. If the error message is not displayed, a hardware problem exists with one or more of the following: - The network card configuration is incorrect on one or more of the computers (hardware, input/output, IRQ, UMB conflict, and so on). - One or more of the network cards is malfunctioning. - There is some problem with the cabling or connectors. This could be an electrical short; interference; or a cable, connector, or terminator that is not the correct specification for your network. To troubleshoot shorts and interference problems, either test the cabling with a testing device, or replace it with cables and connectors that are known to work correctly. For more information about cable and connector specifications, query on the following words in the Microsoft Knowledge Base: wfw and lan and cable and specifications 4. Change the computer name back to its original, unique name. 5. Restart the computer. Start the real mode redirector by typing the following at the MS-DOS command prompt: net start workstation 6. Try to view another computer (which must be in Windows for Workgroups 386 enhanced mode) by typing the following: net view \\ If you can communicate with other computers using the real mode redirector, the problem may be related to an upper memory block (UMB) conflict, a hardware conflict, or a virtual device driver (VxD) that is interfering with Windows for Workgroups. 7. If you can view another computer's shared resources using the real mode redirector, type the following to stop the real mode redirector: net stop If the problem still occurs, use the WIN /D:X switch, as described in the next section. Use the WIN /D:X Switch ----------------------- 1. Start Windows for Workgroups by typing the following at the MS-DOS command prompt: win /d:x 2. Try to view other computers in File Manager. If using the WIN /D:X switch corrects the problem, the network card's memory address needs to be excluded with a UMB provider (such as EMM386.EXE) or by adding an "EMMEXCLUDE=memoryaddress" (without the quotation marks) to the [386Enh] section of the SYSTEM.INI file. For example, if your network uses a UMA address from C800-CFFF, add the following line to the [386Enh] section of your SYSTEM.INI file: EMMExclude=C800-CFFF If using WIN /D:X doesn't allow you to view any other computers in File Manager, but you could view other computers when you quit Windows and started the real mode redirector, the problem may be caused by one of the following: - An IRQ, DMA channel, I/O, or RAM address conflict exists between the network card and another hardware device. -or- - The settings in the Network dialog box of Control Panel do not match the actual hardware settings on the network card. Change the Network Card Settings -------------------------------- To change the IRQ, DMA, I/O, and/or RAM address settings, proceed as follows: 1. Open Control Panel, and choose the Network icon. 2. Choose Adapters, then choose Setup. 3. Select a different setting (or the actual hardware setting) for your network card. 4. With some network cards, you must also change jumpers or switch settings on the card to match the settings in Control Panel. For information about configuring jumpers and switches on your network card, check the documentation that came with the card, or contact your network card manufacturer. 5. Save your changes and exit Control Panel. NOTE: If you cannot start Windows to open Control Panel, edit the PROTOCOL.INI file and change the settings for Interrupt=, RamAddress=, DMAChannel=, and IOBase= to unused values (for software-configurable cards) or to the actual hardware settings (for hardware-configurable cards). When you change hardware settings (such as IRQ and I/O addresses) on software-configurable network cards (such as the Intel EtherExpress 16), you must either quit Windows, turn the computer completely off, and then restart it, or select the Restart Computer option in Windows for the new settings to take effect. Test the Network Card Drivers ----------------------------- Run the Maintenance Mode of Windows for Workgroups Setup program to reinstall the network card drivers. If reinstalling the network card drivers does not enable the local computer to "see itself" in File Manager or view other computers on the network using the real mode redirector, there are several other possible causes: - The correct Media Access Control (MAC) network card driver is not being used. If the card is emulating another card (such as the NE2000), it may be necessary to change jumpers or switches on the card to allow the driver to work properly. For more information about configuring the network card and obtaining updated drivers, contact your network card manufacturer. - The card may be in a slot that is functioning incorrectly. To verify this, try putting the network card in another slot in the computer or install the network card in another computer to determine if the card itself is defective. - The network card may be malfunctioning. Try using a different network card or run diagnostic tests that may have come with the card. - The bus speed on the computer may be too fast for the network card. Most network cards are designed to work at ISA (8.33 mHz) bus speed; setting the bus speed any faster may cause unreliable performance. The bus speed setting is usually changed in the computer's CMOS setup. Try lowering the computer's bus speed if intermittent problems occur. - There may be a bad or missing connection. Some network cards, such as the Intel EtherExpress 16, come with a utility that checks the integrity of wiring and connectors between two computers. If one of these utilities is available, use it to determine whether or not the two computers are physically connected. (Refer to the "Use a Network Card Diagnostic Test" section below.) Use a Network Card Diagnostic Test ---------------------------------- You can run a diagnostic test on the network card to ensure it is functioning correctly. Some network card diagnostic programs can also test communication between computers and the network (this tests the card and the cabling). If this test works, then Windows for Workgroups should also work, provided the correct drivers are being used. If this low-level test does not allow two network cards to communicate, some type of hardware problem exists with a network card, the cabling, or the connectors. Contact your hardware vendor if either the network card diagnostic test or the network test fails. NOTE: If you have the Windows for Workgroups Resource Kit, you can use the NETSTAT program included with the kit. This program tests (from MS-DOS or Windows) the status of a remote network card. This requires that the correct network card drivers be loaded on each network card and (at least) the real mode redirector be started on each computer. If you have Intel EtherExpress network cards (which come with the Windows for Workgroups Starter and User Kits), you can use the SOFTSET utility (available from the Microsoft Download Service [MSDL] or the Intel bulletin board service [BBS]) to troubleshoot both the network card, as well as test the integrity of the network cabling (with the Test Network option). If your network card is not on the supported network card list, you may want to contact the network card manufacturer for information on the correct emulation or for an updated Media Access Control (MAC) network card driver. The manufacturer may also have information on jumpers and switches that may need to be reconfigured for a particular emulation mode, for example NE2000 emulation. For more information about diagnosing problems with your network card or cabling, contact your hardware vendor. KBCategory: kbnetwork kb3rdparty kbtshoot kbsetup KBSubcategory: wfw wfwg Additional reference words: tshoot 3.10 Troubleshooting Serial Port Problems in Windows Article ID: Q105940 ---------------------------------------------------------------- ----- The information in this article applies to: - Microsoft Windows operating system versions 3.0, 3.0a, 3.1, 3.11 - Microsoft Windows for Workgroups version 3.1, 3.11 ---------------------------------------------------------------- ----- SYMPTOMS ======== When you use the Microsoft Windows or Microsoft Windows for Workgroups Terminal program, you have problems connecting to the modem, or you receive the following error message: The COM port is currently assigned to a MS-DOS application. Do you want to reassign the port to Windows? You may also have difficulty attaching to the modem through other Windows- based communications packages, or your mouse (or other serial device) may not operate properly in Windows. CAUSE ===== Most problems associated with the serial ports occur when a machine does not recognize that it has the specified communications (COM) port available. Windows supports the use of COM ports 3 and 4, although the following steps may be necessary to make them accessible. For example, if your mouse is not working in Windows, or you cannot access your modem through Windows, you may need to rewrite the BIOS Data Area for your serial ports. By placing an address for each serial port in a Debug script file, you can ensure future compatibility if you add or remove a device. (Creating a Debug script file should not be required for Windows for Workgroups 3.11.) RESOLUTION ========== 1. When you troubleshoot communications problems in Windows, an MS-DOS- level communications program is often required to test the modem and ports outside Windows. If an MS-DOS-based application cannot be used, you can test the modem connections by typing the following command at the MS-DOS command prompt outside Windows Echo ATDT > COMx where "x" represents the COM port in question. The modem should respond with a dial-tone or just a communication signal. To stop the dial tone, type Echo ATH0 > COMx where "x" represents the COM port in question. The ATDT command is a signal to the modem that is interpreted as Attention Dial Tone. The first command, Attention, signals to the modem that it is about to receive information, and the Dial Tone command instructs the modem to enable a line to dial out. NOTE: The modem may not always give a dial tone with this test procedure because a number does not follow the command; however, the modem should give some kind of signal that information was received. 2. To determine if your machine is recognizing the existence of the COM port your modem or mouse is on, do the following: a. Use the MS-DOS DEBUG command to look at the BIOS table. NOTE: You may also run the Microsoft Diagnostics utility (MSD). b. Quit Windows. At the MS-DOS command prompt, type: debug This returns a hyphen prompt (-). c. At the hyphen prompt, type: d40:0 This returns a listing of the BIOS data and the hyphen prompt. NOTE: After you review the table, you can type "Q" (without the quotation marks) to quit Debug. d. Look at the table of data on the screen. The first row is the important one. It shows a line resembling the following: 0040:0000 F8 03 F8 02 E8 03 00 00-78 03 00 00 00 00 00 00 All values to the left of the hyphen are COM ports; all values to the right are LPT ports. The example above shows that the computer has COM1 at address 03F8 (it is listed in reverse byte order), COM2 at 02F8, and COM3 at 03E8. COM4 is not found; therefore, 0000 is displayed just to the left of the hyphen. If the machine does not recognize the COM port desired to be used by Terminal (identified by the 0000 entries), continue as follows. If the machine does recognize the desired COM port, skip to the "SYSTEM.INI Modifications" section below in this article. 3. The following instructions help you write the Debug script and place it in the AUTOEXEC.BAT file: a. Use a text editor such as Microsoft Windows Notepad and create the following file: E40:0 F8 03 F8 02 E8 03 E8 02 q NOTE: You must follow the "Q" with a carriage return (press ENTER). b. Save the three-line file, and give it a name such as: c:\fixcom.deb. c. Execute the Debug script file by typing the following at an MS-DOS command prompt outside Windows: debug < fixcom.deb > nul d. If step 3 works correctly, add a line to the end of the AUTOEXEC.BAT file (but before launching Windows), such as the following: debug < fixcom.deb > nul NOTE: The > NUL ending is just to keep the script from being echoed back to the screen. You can use Debug again to look at d40:0 and see if the change took effect. e. Save the AUTOEXEC.BAT file and reboot the machine. This procedure should work even if the machine does not have devices on all four serial ports. This also corrects problems if a device has been removed from COM1 and the addresses have slid down, which may cause mouse problems. You should now be able to run MSD or Debug and see all four COM ports. SYSTEM.INI Modifications ------------------------ If the port is recognized by the machine, note the address that is listed when using Debug, and, for Windows 3.0 and 3.0a, edit the SYSTEM.INI file and include the following COMxBase= lines to coincide with the base I/O address used by the hardware. The examples given above for COM1 and COM2 do not require any changes to the SYSTEM.INI file. If you are using Windows 3.0, the examples given below for COM3 and COM4 require the following entries in the [386Enh] section of the SYSTEM.INI file: COMxBase Setting Windows 3.0 Default --------------------------------------------------- COM1Base=3F8h COM2Base=2F8h COM3Base=3E8h COM4Base=2E8h For Windows 3.1 and Windows for Workgroups 3.1 and 3.11, choose the Ports icon in Control Panel to set the base I/O address and interrupt for each COM port instead of editing the SYSTEM.INI file.(This is the only step required for Windows for Workgroups 3.11.) The defaults for Windows 3.1 and Windows for Workgroups 3.x are: COM1Base=3F8h COM2Base=2F8h COM3Base=3E8h COM4Base=2E8h MORE INFORMATION ================ If you are using a serial mouse on COM1 and you have an internal modem on COM3, this configuration may not work because the mouse is using the interrupt that COM3 wants to share. This behavior also occurs if you are using a serial mouse on COM2 and want to use an internal modem on COM4. This configuration is more likely to work on machines that allow for IRQ sharing (such as Micro Channel Architecture [MCA] computers). If COM3 is required, it should be reconfigured at the board level to use a different interrupt that is free, such as IRQ 5. KBCategory: kbhw kbtshoot kbtlc KBSubcategory: win30 win31 wfw wfwg wincomm ms-dos Additional reference words: tshoot 3.00 3.0 3.0a 3.00a 3.1 3.10 3.11 BIOS slide slip move sliding debugging terminal.exe com1 com2 com3 com4 AT DT DOS w_works hometool works for windows WFWG Upgrade 3.11 Disk Directories (3.5 Inch, 1.44 MB) Article ID: Q106431 ---------------------------------------------------------------- ----- The information in this article applies to: - Microsoft Windows for Workgroups versions 3.11, 3.11a ---------------------------------------------------------------- ----- SUMMARY ======= This article contains the directory listing of the Windows for Workgroups Upgrade version 3.11 1.44-megabyte (MB) 3.5-inch disks (dated 11/1/93). MORE INFORMATION ================ Disk 1 ------ Volume in drive B is MSWFWUPG1 Volume Serial Number is 3137-0B10 Directory of B:\ COMMDLG DL_ 49,872 11-01-93 3:11a CONTROL HL_ 93,013 11-01-93 3:11a DISK1 8 11-01-93 3:11a DOSAPP FO_ 14,476 11-01-93 3:11a GDI EX_ 148,271 11-01-93 3:11a KBDDV DL_ 943 11-01-93 3:11a KRNL386 EX_ 53,067 11-01-93 3:11a NCDW DL_ 23,031 11-01-93 3:11a SETUP EXE 244,321 11-01-93 3:11a SETUP HL_ 47,275 11-01-93 3:11a SETUP INF 57,634 11-01-93 3:11a SETUP SHH 8,858 11-01-93 3:11a SETUP TXT 53,519 11-01-93 3:11a SVGA256 DR_ 51,222 11-01-93 3:11a USER EX_ 174,119 11-01-93 3:11a WFWSETUP DL_ 156,046 11-01-93 3:11a WIN CN_ 8,359 11-01-93 3:11a WINHELP EX_ 147,927 11-01-93 3:11a WINSETUP EX_ 102,978 11-01-93 3:11a XMSMMGR EXE 14,144 11-01-93 3:11a 20 file(s) 1,449,083 bytes 3,072 bytes free Disk 2 ------ Volume in drive B is MSWFW2 Volume Serial Number is 062B-2E0F Directory of B:\ 386MAX VX_ 17,978 11-01-93 3:11a 8514 DR_ 44,018 11-01-93 3:11a 8514FIX FO_ 3,174 11-01-93 3:11a 8514OEM FO_ 3,758 11-01-93 3:11a 8514SYS FO_ 3,251 11-01-93 3:11a APP850 FO_ 14,504 11-01-93 3:11a BLUEMAX VX_ 18,007 11-01-93 3:11a CGA40850 FO_ 3,228 11-01-93 3:11a CGA40WOA FO_ 3,081 11-01-93 3:11a CGA80850 FO_ 2,627 11-01-93 3:11a CGA80WOA FO_ 2,606 11-01-93 3:11a COMM DR_ 3,226 11-01-93 3:11a COMMCTRL DL_ 30,192 11-01-93 3:11a CPWIN386 CP_ 47,012 11-01-93 3:11a DISK2 8 11-01-93 3:11a DOSX EX_ 23,767 11-01-93 3:11a EGA40850 FO_ 3,657 11-01-93 3:11a EGA40WOA FO_ 3,531 11-01-93 3:11a EGA80850 FO_ 2,870 11-01-93 3:11a EGA80WOA FO_ 2,882 11-01-93 3:11a FRAMEWRK DL_ 123,170 11-01-93 3:11a HPEBIOS 38_ 1,494 11-01-93 3:11a HPSYSTEM DR_ 1,929 11-01-93 3:11a IFSHLP SY_ 3,343 11-01-93 3:11a KBDBE DL_ 1,880 11-01-93 3:11a KBDBR DL_ 1,790 11-01-93 3:11a KBDCA DL_ 1,946 11-01-93 3:11a KBDDA DL_ 1,833 11-01-93 3:11a KBDFC DL_ 2,076 11-01-93 3:11a KBDFI DL_ 1,875 11-01-93 3:11a KBDFR DL_ 1,759 11-01-93 3:11a KBDGR DL_ 1,769 11-01-93 3:11a KBDHP DR_ 6,045 11-01-93 3:11a KBDIC DL_ 1,336 11-01-93 3:11a KBDIT DL_ 1,650 11-01-93 3:11a KBDLA DL_ 1,884 11-01-93 3:11a KBDNE DL_ 1,827 11-01-93 3:11a KBDNO DL_ 1,851 11-01-93 3:11a KBDPO DL_ 1,788 11-01-93 3:11a KBDSF DL_ 1,817 11-01-93 3:11a KBDSG DL_ 1,296 11-01-93 3:11a KBDSP DL_ 1,871 11-01-93 3:11a KBDSW DL_ 1,863 11-01-93 3:11a KBDUK DL_ 1,093 11-01-93 3:11a KBDUS DL_ 946 11-01-93 3:11a KBDUSX DL_ 1,255 11-01-93 3:11a KEYBOARD DR_ 5,422 11-01-93 3:11a LANGDUT DL_ 1,281 11-01-93 3:11a LANGENG DL_ 1,281 11-01-93 3:11a LANGFRN DL_ 1,306 11-01-93 3:11a LANGGER DL_ 1,280 11-01-93 3:11a LANGSCA DL_ 1,278 11-01-93 3:11a LANGSPA DL_ 1,343 11-01-93 3:11a LMOUSE CO_ 19,633 11-01-93 3:11a LMOUSE DR_ 6,978 11-01-93 3:11a LVMD 38_ 3,403 11-01-93 3:11a LZEXPAND DL_ 13,532 11-01-93 3:11a MMSOUND DR_ 2,545 11-01-93 3:11a MOUSE DR_ 7,084 11-01-93 3:11a MSC3BC2 DR_ 2,519 11-01-93 3:11a MSCMOUSE DR_ 2,578 11-01-93 3:11a MSCVMD 38_ 2,685 11-01-93 3:11a NOMOUSE DR_ 320 11-01-93 3:11a POWER DR_ 8,497 11-01-93 3:11a POWER HL_ 6,748 11-01-93 3:11a SCHDPLUS EX_ 263,857 11-01-93 3:11a SCONFIG DL_ 23,494 11-01-93 3:11a SHELL DL_ 22,990 11-01-93 3:11a SL DL_ 8,567 11-01-93 3:11a SL HL_ 7,820 11-01-93 3:11a SUPERVGA DR_ 38,830 11-01-93 3:11a SYSTEM DR_ 1,641 11-01-93 3:11a SYSTEM SR_ 748 11-01-93 3:11a V7VDD 38_ 16,884 11-01-93 3:11a V7VGA 3G_ 7,861 11-01-93 3:11a V7VGA DR_ 41,089 11-01-93 3:11a VDD8514 38_ 24,764 11-01-93 3:11a VDDSVGA 38_ 26,953 11-01-93 3:11a VDDVGA30 38_ 17,129 11-01-93 3:11a VDDXGA 38_ 17,931 11-01-93 3:11a VER DL_ 6,052 11-01-93 3:11a VGA 3G_ 9,885 11-01-93 3:11a VGA DR_ 38,508 11-01-93 3:11a VGA30 3G_ 8,623 11-01-93 3:11a VGA850 FO_ 2,883 11-01-93 3:11a VGA860 FO_ 2,848 11-01-93 3:11a VGA861 FO_ 2,882 11-01-93 3:11a VGA863 FO_ 2,870 11-01-93 3:11a VGA865 FO_ 2,874 11-01-93 3:11a VGADIB 3G_ 9,153 11-01-93 3:11a VGAFIX FO_ 2,423 11-01-93 3:11a VGALOGO LG_ 1,158 11-01-93 3:11a VGALOGO RL_ 9,906 11-01-93 3:11a VGAOEM FO_ 2,839 11-01-93 3:11a VGASYS FO_ 2,754 11-01-93 3:11a VPOWERD 38_ 1,610 11-01-93 3:11a WIN SR_ 1,400 11-01-93 3:11a WIN386 EX_ 256,635 11-01-93 3:11a WINDOWS LO_ 785 11-01-93 3:11a XGA DR_ 46,006 11-01-93 3:11a XLAT850 BI_ 428 11-01-93 3:11a XLAT860 BI_ 409 11-01-93 3:11a XLAT861 BI_ 410 11-01-93 3:11a XLAT863 BI_ 410 11-01-93 3:11a XLAT865 BI_ 406 11-01-93 3:11a 105 file(s) 1,429,191 bytes 3,072 bytes free Disk 3 ------ Volume in drive B is MSWFW3 Volume Serial Number is 2234-2E0F Directory of B:\ DISK3 8 11-01-93 3:11a MAIN CP_ 80,992 11-01-93 3:11a MPLAYER EX_ 19,241 11-01-93 3:11a MSD EXE 166,302 11-01-93 3:11a MSMAIL EX_ 156,898 11-01-93 3:11a MSSCHED DL_ 122,853 11-01-93 3:11a MSSFS DL_ 150,350 11-01-93 3:11a NETWORKS WR_ 26,563 11-01-93 3:11a PBRUSH EX_ 92,305 11-01-93 3:11a PRINTERS WR_ 17,282 11-01-93 3:11a PRINTMAN EX_ 38,766 11-01-93 3:11a README WR_ 32,954 11-01-93 3:11a STORE DL_ 131,214 11-01-93 3:11a SYSINI WR_ 19,900 11-01-93 3:11a TERMINAL EX_ 75,972 11-01-93 3:11a VFORMS DL_ 76,851 11-01-93 3:11a WINFILE EX_ 95,358 11-01-93 3:11a WININI WR_ 6,920 11-01-93 3:11a WRITE EX_ 139,061 11-01-93 3:11a 19 file(s) 1,449,790 bytes 3,072 bytes free Disk 4 ------ Volume in drive B is MSWFW4 Volume Serial Number is 483A-2E0F Directory of B:\ AB DL_ 52,238 11-01-93 3:11a APPS INF 57,961 11-01-93 3:11a CARDFILE EX_ 43,461 11-01-93 3:11a CARDS DL_ 37,140 11-01-93 3:11a CLIPBRD EX_ 35,055 11-01-93 3:11a CMC DL_ 40,403 11-01-93 3:11a DISK4 8 11-01-93 3:11a EFAXPUMP DL_ 36,666 11-01-93 3:11a EMM386 EX_ 50,090 11-01-93 3:11a FAXOPT DL_ 51,613 11-01-93 3:11a FAXVIEW EX_ 44,655 11-01-93 3:11a GLOSSARY HL_ 39,170 11-01-93 3:11a IFSMGR 38_ 36,268 11-01-93 3:11a IMPEXP DL_ 31,513 11-01-93 3:11a MIDIMAP DR_ 30,768 11-01-93 3:11a MMSYSTEM DL_ 32,154 11-01-93 3:11a MORICONS DL_ 34,241 11-01-93 3:11a MPLAYER HL_ 6,842 11-01-93 3:11a MSHEARTS EX_ 54,683 11-01-93 3:11a MSMAIL HL_ 54,304 11-01-93 3:11a NETWORK INF 58,618 11-01-93 3:11a OLECLI DL_ 41,113 11-01-93 3:11a PACKAGER EX_ 36,954 11-01-93 3:11a PRINTMAN HL_ 39,548 11-01-93 3:11a PROGMAN EX_ 51,048 11-01-93 3:11a SCHDPLUS HL_ 73,894 11-01-93 3:11a SCHEDMSG DL_ 36,677 11-01-93 3:11a SOL EX_ 56,003 11-01-93 3:11a SOUNDREC HL_ 8,752 11-01-93 3:11a UNIDRV DL_ 69,914 11-01-93 3:11a WGPOMGR DL_ 42,528 11-01-93 3:11a WINFILE HL_ 55,044 11-01-93 3:11a WINTUTOR DA_ 47,238 11-01-93 3:11a WINTUTOR EX_ 58,791 11-01-93 3:11a 34 file(s) 1,445,355 bytes 3,072 bytes free Disk 5 ------ Volume in drive B is MSWFW5 Volume Serial Number is 4D08-2F0F Directory of B:\ ARIAL FO_ 384 11-01-93 3:11a ARIAL TT_ 45,505 11-01-93 3:11a ARIALBD FO_ 388 11-01-93 3:11a ARIALBD TT_ 44,999 11-01-93 3:11a ARIALBI FO_ 394 11-01-93 3:11a ARIALBI TT_ 49,996 11-01-93 3:11a ARIALI FO_ 386 11-01-93 3:11a ARIALI TT_ 41,572 11-01-93 3:11a CALC EX_ 25,112 11-01-93 3:11a CLIPBRD HL_ 19,305 11-01-93 3:11a COUR FO_ 385 11-01-93 3:11a COUR TT_ 46,925 11-01-93 3:11a COURBD FO_ 388 11-01-93 3:11a COURBD TT_ 49,896 11-01-93 3:11a COURBI FO_ 396 11-01-93 3:11a COURBI TT_ 56,303 11-01-93 3:11a COURI FO_ 391 11-01-93 3:11a COURI TT_ 53,037 11-01-93 3:11a DDEML DL_ 21,454 11-01-93 3:11a DEMILAYR DL_ 28,792 11-01-93 3:11a DISK5 8 11-01-93 3:11a DRIVERS CP_ 19,039 11-01-93 3:11a FAXSTUB DL_ 23,722 11-01-93 3:11a MAILMGR DL_ 23,763 11-01-93 3:11a MAILSPL EX_ 28,708 11-01-93 3:11a MAPI DL_ 30,212 11-01-93 3:11a MOUSE CO_ 27,411 11-01-93 3:11a MOUSE SY_ 26,904 11-01-93 3:11a MSADLIB DR_ 9,112 11-01-93 3:11a MSFAX HL_ 19,448 11-01-93 3:11a PABNSP DL_ 23,294 11-01-93 3:11a PBRUSH HL_ 27,901 11-01-93 3:11a PIFEDIT EX_ 23,043 11-01-93 3:11a PIFEDIT HL_ 23,828 11-01-93 3:11a PROGMAN HL_ 20,745 11-01-93 3:11a RECORDER EX_ 21,776 11-01-93 3:11a SERIFE FO_ 18,813 11-01-93 3:11a SERIFF FO_ 23,670 11-01-93 3:11a SNDBLST DR_ 8,979 11-01-93 3:11a SNDBLST2 DR_ 9,286 11-01-93 3:11a SOUNDREC EX_ 28,854 11-01-93 3:11a SSERIFF FO_ 23,661 11-01-93 3:11a SYMBOL FO_ 389 11-01-93 3:11a SYMBOL TT_ 43,841 11-01-93 3:11a SYMBOLE FO_ 18,938 11-01-93 3:11a SYMBOLF FO_ 23,852 11-01-93 3:11a TERMINAL HL_ 22,584 11-01-93 3:11a TIMER DR_ 2,832 11-01-93 3:11a TIMES FO_ 391 11-01-93 3:11a TIMES TT_ 59,592 11-01-93 3:11a TIMESBD FO_ 399 11-01-93 3:11a TIMESBD TT_ 54,934 11-01-93 3:11a TIMESBI FO_ 404 11-01-93 3:11a TIMESBI TT_ 52,562 11-01-93 3:11a TIMESI FO_ 399 11-01-93 3:11a TIMESI TT_ 53,710 11-01-93 3:11a TRNOFF DL_ 2,497 11-01-93 3:11a UNIDRV HL_ 29,017 11-01-93 3:11a VADLIBD 38_ 1,631 11-01-93 3:11a VFAT 38_ 19,452 11-01-93 3:11a VSBD 38_ 2,114 11-01-93 3:11a VTDAPI 38_ 1,549 11-01-93 3:11a WINGDING FO_ 390 11-01-93 3:11a WINGDING TT_ 46,247 11-01-93 3:11a WINOA386 MO_ 27,311 11-01-93 3:11a WRITE HL_ 26,010 11-01-93 3:11a 66 file(s) 1,439,230 bytes 3,072 bytes free Disk 6 ------ Volume in drive B is MSWFW6 Volume Serial Number is 240F-2F0F Directory of B:\ 40291730 WP_ 1,035 11-01-93 3:11a 40293930 WP_ 1,627 11-01-93 3:11a ARCADE BM_ 344 11-01-93 3:11a ARGYLE BM_ 240 11-01-93 3:11a AWCAS DL_ 6,531 11-01-93 3:11a AWCLASS1 DL_ 7,883 11-01-93 3:11a AWCLASS2 DL_ 8,342 11-01-93 3:11a AWFAXIO DL_ 10,814 11-01-93 3:11a AWFXPROT DL_ 6,867 11-01-93 3:11a AWT30 DL_ 7,574 11-01-93 3:11a CALC HL_ 11,331 11-01-93 3:11a CANON10E DR_ 2,393 11-01-93 3:11a CANON130 DR_ 2,630 11-01-93 3:11a CANON330 DR_ 4,909 11-01-93 3:11a CANYON MI_ 15,734 11-01-93 3:11a CAN_ADF EX_ 33,823 11-01-93 3:11a CARDFILE HL_ 16,305 11-01-93 3:11a CASTLE BM_ 441 11-01-93 3:11a CHARMAP EX_ 10,645 11-01-93 3:11a CHARMAP HL_ 4,032 11-01-93 3:11a CHIMES WA_ 8,713 11-01-93 3:11a CIT24US DR_ 7,323 11-01-93 3:11a CIT9US DR_ 6,006 11-01-93 3:11a CLIPSRV EX_ 9,882 11-01-93 3:11a CLOCK EX_ 9,094 11-01-93 3:11a CONTROL EX_ 9,227 11-01-93 3:11a CONTROL INF 17,667 11-01-93 3:11a CONTROL SR_ 1,132 11-01-93 3:11a COURE FO_ 7,503 11-01-93 3:11a COURF FO_ 9,676 11-01-93 3:11a CPQGR3 EX_ 9,772 11-01-93 3:11a CPQVGA GR_ 9,772 11-01-93 3:11a DEC1150 WP_ 1,752 11-01-93 3:11a DEC2150 WP_ 1,714 11-01-93 3:11a DEC2250 WP_ 1,834 11-01-93 3:11a DEC3250 WP_ 1,873 11-01-93 3:11a DECCOLOR WP_ 1,252 11-01-93 3:11a DECLPS20 WP_ 1,432 11-01-93 3:11a DICONIX DR_ 1,999 11-01-93 3:11a DING WA_ 4,960 11-01-93 3:11a DISK6 8 11-01-93 3:11a DLLSCHED DL_ 4,262 11-01-93 3:11a DMCOLOR DL_ 12,956 11-01-93 3:11a EFAXDRV DR_ 5,475 11-01-93 3:11a EFAXRUN DL_ 13,310 11-01-93 3:11a EGYPT BM_ 221 11-01-93 3:11a EPSON24 DR_ 5,100 11-01-93 3:11a EPSON9 DR_ 6,857 11-01-93 3:11a ESCP2 DR_ 4,002 11-01-93 3:11a EXECJET DR_ 5,123 11-01-93 3:11a EXPAND EXE 16,378 11-01-93 3:11a FAX CP_ 924 11-01-93 3:11a FAXCODEC DL_ 8,147 11-01-93 3:11a FAXCOVER DL_ 13,965 11-01-93 3:11a FAXMGR EX_ 4,671 11-01-93 3:11a FAXNSP DL_ 8,646 11-01-93 3:11a GENDRV DL_ 44,284 11-01-93 3:11a HIMEM SY_ 10,074 11-01-93 3:11a HONEY BM_ 338 11-01-93 3:11a HPDSKJET DR_ 24,456 11-01-93 3:11a HPPLOT DR_ 31,689 11-01-93 3:11a IBM39521 WP_ 1,571 11-01-93 3:11a IBM4019 DR_ 26,747 11-01-93 3:11a IBM5204 DR_ 4,140 11-01-93 3:11a IFKERNEL DL_ 3,304 11-01-93 3:11a IOS 38_ 15,603 11-01-93 3:11a KEYVIEW EX_ 1,513 11-01-93 3:11a L200230& WP_ 1,601 11-01-93 3:11a L300_471 WP_ 1,725 11-01-93 3:11a L300_493 WP_ 1,604 11-01-93 3:11a L330_52& WP_ 1,607 11-01-93 3:11a L500_493 WP_ 1,681 11-01-93 3:11a L530_52& WP_ 1,667 11-01-93 3:11a L630_52& WP_ 1,644 11-01-93 3:11a LBPII DR_ 23,523 11-01-93 3:11a LBPIII DR_ 32,129 11-01-93 3:11a LINEARIZ DL_ 14,781 11-01-93 3:11a LM21DRV UP_ 525 11-01-93 3:11a LPT 38_ 2,678 11-01-93 3:11a MAIL WR_ 14,150 11-01-93 3:11a MCICDA DR_ 7,458 11-01-93 3:11a MCISEQ DR_ 14,450 11-01-93 3:11a MCIWAVE DR_ 15,095 11-01-93 3:11a MIDIMAP CF_ 5,093 11-01-93 3:11a MMTASK TS_ 755 11-01-93 3:11a MODERN FO_ 3,711 11-01-93 3:11a MPU401 DR_ 4,731 11-01-93 3:11a MSCDEX EX_ 14,829 11-01-93 3:11a MSD IN_ 341 11-01-93 3:11a MSHEARTS HL_ 7,521 11-01-93 3:11a MSREMIND EX_ 17,361 11-01-93 3:11a MT_TI101 WP_ 1,328 11-01-93 3:11a N2090522 WP_ 1,395 11-01-93 3:11a N2290520 WP_ 1,308 11-01-93 3:11a N2990523 WP_ 1,427 11-01-93 3:11a N890_470 WP_ 1,345 11-01-93 3:11a NDDEAPI DL_ 9,022 11-01-93 3:11a NEC24PIN DR_ 9,374 11-01-93 3:11a NETFAX DL_ 9,317 11-01-93 3:11a NOTEPAD EX_ 17,938 11-01-93 3:11a NOTEPAD HL_ 7,269 11-01-93 3:11a OKI24 DR_ 4,920 11-01-93 3:11a OKI9 DR_ 3,669 11-01-93 3:11a OKI9IBM DR_ 3,367 11-01-93 3:11a OLESVR DL_ 13,144 11-01-93 3:11a PACKAGER HL_ 14,752 11-01-93 3:11a PAINTJET DR_ 2,637 11-01-93 3:11a PANSON24 DR_ 3,865 11-01-93 3:11a PANSON9 DR_ 4,172 11-01-93 3:11a PBRUSH DL_ 4,423 11-01-93 3:11a PROPRINT DR_ 3,150 11-01-93 3:11a PROPRN24 DR_ 3,126 11-01-93 3:11a PRTUPD INF 15,855 11-01-93 3:11a PS1 DR_ 3,269 11-01-93 3:11a PSCRIPT DR_ 125,229 11-01-93 3:11a QWIII DR_ 4,119 11-01-93 3:11a RAMDRIVE SY_ 3,295 11-01-93 3:11a RASSTART EX_ 5,705 11-01-93 3:11a RECORDER DL_ 7,001 11-01-93 3:11a RECORDER HL_ 10,840 11-01-93 3:11a REDBRICK BM_ 371 11-01-93 3:11a REGEDIT EX_ 18,192 11-01-93 3:11a REGEDIT HL_ 14,435 11-01-93 3:11a REGEDITV HL_ 9,444 11-01-93 3:11a RINGIN WA_ 7,892 11-01-93 3:11a RINGOUT WA_ 2,546 11-01-93 3:11a RIVETS BM_ 154 11-01-93 3:11a RMM D3_ 5,026 11-01-93 3:11a ROMAN FO_ 5,423 11-01-93 3:11a SCRIPT FO_ 4,695 11-01-93 3:11a SCRNSAVE SC_ 2,317 11-01-93 3:11a SENDFILE DL_ 3,511 11-01-93 3:11a SERIAL 38_ 5,955 11-01-93 3:11a SETUP RE_ 1,257 11-01-93 3:11a SF4019 EX_ 30,999 11-01-93 3:11a SIGVIEW EX_ 3,048 11-01-93 3:11a SMALLE FO_ 11,251 11-01-93 3:11a SMALLF FO_ 9,391 11-01-93 3:11a SMARTDRV EX_ 15,491 11-01-93 3:11a SND CP_ 4,434 11-01-93 3:11a SOL HL_ 6,996 11-01-93 3:11a SQUARES BM_ 161 11-01-93 3:11a SSERIFE FO_ 18,807 11-01-93 3:11a SSFLYWIN SC_ 8,648 11-01-93 3:11a SSMARQUE SC_ 8,609 11-01-93 3:11a SSSTARS SC_ 8,287 11-01-93 3:11a SYSEDIT EX_ 10,035 11-01-93 3:11a TASKMAN EX_ 2,029 11-01-93 3:11a THATCH BM_ 211 11-01-93 3:11a THINKJET DR_ 2,094 11-01-93 3:11a TOOLHELP DL_ 9,232 11-01-93 3:11a TRNSCHED DL_ 8,002 11-01-93 3:11a TTY DR_ 14,795 11-01-93 3:11a TTY HL_ 7,549 11-01-93 3:11a VCACHE 38_ 2,587 11-01-93 3:11a VCOMM 38_ 2,590 11-01-93 3:11a VPMTD 38_ 1,626 11-01-93 3:11a VSHARE 38_ 7,651 11-01-93 3:11a VXDLDR 38_ 3,256 11-01-93 3:11a WIN386 PS_ 419 11-01-93 3:11a WIN87EM DL_ 7,917 11-01-93 3:11a WINHELP HL_ 17,871 11-01-93 3:11a WININIT EX_ 13,478 11-01-93 3:11a WINLOGO BM_ 11,025 11-01-93 3:11a WINMINE EX_ 11,938 11-01-93 3:11a WINMINE HL_ 6,118 11-01-93 3:11a WINNET INF 14,691 11-01-93 3:11a WINVER _ 1,639 11-01-93 3:11a WSWAP EX_ 10,131 11-01-93 3:11a ZIGZAG BM_ 205 11-01-93 3:11a 170 file(s) 1,411,197 bytes 3,072 bytes free Disk 7 ------ Volume in drive B is MSWFW7 Volume Serial Number is 4018-2F0F Directory of B:\ AM1500T 38_ 11,216 11-01-93 3:11a BP1CP2 PC_ 34,398 11-01-93 3:11a DD1CP1 PC_ 30,920 11-01-93 3:11a DECLAN 38_ 14,851 11-01-93 3:11a DISK7 8 11-01-93 3:11a EE16 38_ 12,922 11-01-93 3:11a ELNK16 38_ 12,596 11-01-93 3:11a ELNKII 38_ 14,740 11-01-93 3:11a ELNKMC 38_ 11,956 11-01-93 3:11a EPL75523 WP_ 1,466 11-01-93 3:11a FINSTALL DL_ 98,999 11-01-93 3:11a FINSTALL HL_ 14,634 11-01-93 3:11a HPEISA 38_ 13,826 11-01-93 3:11a HPELI523 WP_ 1,487 11-01-93 3:11a HPIID522 WP_ 1,468 11-01-93 3:11a HPIII522 WP_ 1,453 11-01-93 3:11a HPIIP522 WP_ 1,462 11-01-93 3:11a HPISA 38_ 15,885 11-01-93 3:11a HPPCL DR_ 48,031 11-01-93 3:11a HPPCL5E DR_ 153,870 11-01-93 3:11a HPPCL5E HL_ 16,172 11-01-93 3:11a HPPCL5E1 DL_ 32,760 11-01-93 3:11a HPPCL5E2 DL_ 24,558 11-01-93 3:11a HPPCL5E3 DL_ 46,699 11-01-93 3:11a HPPCL5E4 DL_ 10,899 11-01-93 3:11a HPPCL5EO HL_ 12,297 11-01-93 3:11a HPPCL5MS DR_ 100,098 11-01-93 3:11a HP_3D522 WP_ 1,534 11-01-93 3:11a HP_3P522 WP_ 1,480 11-01-93 3:11a IBM17521 WP_ 976 11-01-93 3:11a IBMTOK 38_ 16,647 11-01-93 3:11a L100_425 WP_ 1,529 11-01-93 3:11a N890X505 WP_ 1,347 11-01-93 3:11a NCM40519 WP_ 662 11-01-93 3:11a NCM80519 WP_ 1,194 11-01-93 3:11a NDIS 38_ 13,807 11-01-93 3:11a NDIS2SUP 38_ 11,498 11-01-93 3:11a NE1000 38_ 15,376 11-01-93 3:11a NE2000 38_ 15,608 11-01-93 3:11a NE3200 38_ 16,272 11-01-93 3:11a NETAPI DL_ 59,968 11-01-93 3:11a NETBEUI 38_ 24,236 11-01-93 3:11a NETDDE EX_ 40,497 11-01-93 3:11a NETWATCH EX_ 16,869 11-01-93 3:11a NWLINK 38_ 16,329 11-01-93 3:11a NWNBLINK 38_ 20,957 11-01-93 3:11a O5241503 WP_ 1,418 11-01-93 3:11a O5242503 WP_ 1,399 11-01-93 3:11a OL840518 WP_ 1,487 11-01-93 3:11a P4455514 WP_ 1,528 11-01-93 3:11a PHIIPX WP_ 1,169 11-01-93 3:11a PMSPL DL_ 14,869 11-01-93 3:11a PSCRIPT HL_ 29,034 11-01-93 3:11a Q2200510 WP_ 1,529 11-01-93 3:11a Q820_517 WP_ 1,443 11-01-93 3:11a SEIKO_04 WP_ 1,312 11-01-93 3:11a SEIKO_14 WP_ 1,391 11-01-93 3:11a SMC8000W 38_ 16,314 11-01-93 3:11a TESTPS TX_ 1,087 11-01-93 3:11a TIM17521 WP_ 994 11-01-93 3:11a TIM35521 WP_ 1,491 11-01-93 3:11a TKPHZR21 WP_ 1,417 11-01-93 3:11a TKPHZR31 WP_ 1,503 11-01-93 3:11a VREDIR 38_ 51,474 11-01-93 3:11a VSERVER 38_ 49,085 11-01-93 3:11a WFWAUDIT DL_ 11,645 11-01-93 3:11a WFWNET DR_ 167,247 11-01-93 3:11a WFWNET HL_ 32,308 11-01-93 3:11a WINCHAT EX_ 18,808 11-01-93 3:11a WINPOPUP EX_ 13,314 11-01-93 3:11a 70 file(s) 1,439,723 bytes 3,072 bytes free Disk 8 ------ Volume in drive B is MSWFW8 Volume Serial Number is 1A21-2F0F Directory of B:\ ADMINCFG EX_ 2,571 11-01-93 3:11a AM2100 DO_ 5,714 11-01-93 3:11a DEPCA DO_ 9,707 11-01-93 3:11a DISK8 8 11-01-93 3:11a DNCRWL02 DO_ 19,078 11-01-93 3:11a E20ND DO_ 6,247 11-01-93 3:11a E21ND DO_ 6,630 11-01-93 3:11a E30ND DO_ 6,251 11-01-93 3:11a E31ND DO_ 6,267 11-01-93 3:11a ELNK16 DO_ 6,444 11-01-93 3:11a ELNK3 38_ 11,512 11-01-93 3:11a ELNK3 DO_ 8,531 11-01-93 3:11a ELNKII DO_ 7,233 11-01-93 3:11a ELNKMC DO_ 6,585 11-01-93 3:11a ES3210 DO_ 7,114 11-01-93 3:11a EXP16 DO_ 6,348 11-01-93 3:11a HPLAN DO_ 8,964 11-01-93 3:11a HPLANB DO_ 6,954 11-01-93 3:11a HPLANE DO_ 8,042 11-01-93 3:11a HPLANP DO_ 7,514 11-01-93 3:11a I82593 DO_ 4,638 11-01-93 3:11a IBMNET DO_ 6,571 11-01-93 3:11a IBMNETA DO_ 6,590 11-01-93 3:11a IBMTOK DO_ 6,284 11-01-93 3:11a LMSCRIPT EX_ 3,200 11-01-93 3:11a LMSCRIPT PI_ 222 11-01-93 3:11a LOGONOFF EX_ 3,583 11-01-93 3:11a MODEM INF 130,552 11-01-93 3:11a MSNET DR_ 4,214 11-01-93 3:11a MSODISUP 38_ 10,504 11-01-93 3:11a NCC16 DO_ 8,562 11-01-93 3:11a NDDENB DL_ 8,472 11-01-93 3:11a NDIS39XR DO_ 9,687 11-01-93 3:11a NDIS89XR DO_ 9,830 11-01-93 3:11a NDISHLP SY_ 2,957 11-01-93 3:11a NE1000 DO_ 8,478 11-01-93 3:11a NE2000 DO_ 8,599 11-01-93 3:11a NE3200 DO_ 9,637 11-01-93 3:11a NET EX_ 233,319 11-01-93 3:11a NET MS_ 30,356 11-01-93 3:11a NETDDEX EX_ 4,397 11-01-93 3:11a NETH MS_ 43,170 11-01-93 3:11a NETWATCH HL_ 7,974 11-01-93 3:11a NI5210 DO_ 5,539 11-01-93 3:11a NI6510 DO_ 4,751 11-01-93 3:11a NWSUP 38_ 3,070 11-01-93 3:11a ODIHLP EX_ 1,670 11-01-93 3:11a OLITOK DO_ 30,730 11-01-93 3:11a PAD INF 5,401 11-01-93 3:11a PE2NDIS DO_ 22,779 11-01-93 3:11a PENDIS DO_ 15,755 11-01-93 3:11a PRO4 DO_ 11,753 11-01-93 3:11a PRO4AT DO_ 8,848 11-01-93 3:11a PRORAPM DW_ 15,880 11-01-93 3:11a PROTMAN DO_ 7,680 11-01-93 3:11a PROTMAN EX_ 5,415 11-01-93 3:11a PSS INF 935 11-01-93 3:11a RASAPI16 DL_ 23,951 11-01-93 3:11a RASCAUTH DL_ 13,760 11-01-93 3:11a RASCONF DL_ 10,387 11-01-93 3:11a RASEXE EX_ 2,444 11-01-93 3:11a RASFILE DL_ 6,969 11-01-93 3:11a RASMAC 38_ 24,132 11-01-93 3:11a RASMAN DL_ 12,735 11-01-93 3:11a RASMON EX_ 22,776 11-01-93 3:11a RASMXS DL_ 18,053 11-01-93 3:11a RASPHONE EX_ 104,152 11-01-93 3:11a RASPHONE HL_ 81,831 11-01-93 3:11a RASSAUTH DL_ 12,768 11-01-93 3:11a RASSER DL_ 8,428 11-01-93 3:11a RASSRV DL_ 6,264 11-01-93 3:11a SLAN DO_ 8,086 11-01-93 3:11a SMARTND DO_ 51,755 11-01-93 3:11a SMCMAC DO_ 10,330 11-01-93 3:11a SMC_ARC DO_ 10,972 11-01-93 3:11a SWITCH INF 3 11-01-93 3:11a T20ND DO_ 24,414 11-01-93 3:11a T30ND DO_ 24,380 11-01-93 3:11a TCCARC DO_ 6,017 11-01-93 3:11a UBNEI DO_ 16,659 11-01-93 3:11a UBNEPS DO_ 12,910 11-01-93 3:11a VNETSUP 38_ 5,192 11-01-93 3:11a WFWNETCP CP_ 2,365 11-01-93 3:11a WINCHAT HL_ 9,868 11-01-93 3:11a WINMETER EX_ 10,523 11-01-93 3:11a WINPOPUP HL_ 6,430 11-01-93 3:11a 86 file(s) 1,398,270 bytes 38,400 bytes free NOTE: The RASMAC.38_ file that now ships with Windows for Workgroups version 3.11a does not contain compression code. As a result, the directory listing for disk 8 varies with the following information if you have the non-compression RASMAC.386 file: RASMAC 38_ 14,710 11-01-93 3:11a 86 file(s) 1,388,848 bytes 48,128 bytes free KBCategory: kbref KBSubcategory: Additional reference words: wfw wfwg 3.11 dirwfw list noupd WFWG: Creating a New SYSTEM.INI Without Third-Party Drivers Article ID: Q107131 --------------------------------------------------------------- The information in this article applies to: - Microsoft Windows for Workgroups versions 3.1, 3.11 --------------------------------------------------------------- SUMMARY ======= You can use your original Microsoft Windows for Workgroups version 3.1 or 3.11 disks to create a new SYSTEM.INI file for your specific hardware and version of the network operating system. Creating a new SYSTEM.INI file can be useful for troubleshooting or for replacing a damaged or deleted SYSTEM.INI file. MORE INFORMATION ================ To create a new SYSTEM.INI file that does not contain references to third- party device drivers but that is configured for your specific hardware, do the following: 1. Rename the SYSTEM.INI file to SYSTEM.BKP. 2. Expand the file SYSTEM.SR_ from the original Windows for Workgroups 3.1 or 3.11 disks to your Windows directory (usually C:\WINDOWS) by typing the following at the MS-DOS command prompt and pressing ENTER: c:\windows\expand a:system.sr_ c:\windows\system.ini NOTE: For Windows for Workgroups 3.1, this file is located on Disk 3 for both the 1.44-megabyte (MB) 3.5-inch and 1.2-MB 5.25-inch disk sets. For Windows for Workgroups 3.11, this file is located on Disk 2 for both the 1.44-MB 3.5-inch and 1.2-MB 5.25-inch disk sets. 3. Change to the Windows for Workgroups drive and then change to the Windows directory. For example, at the MS-DOS command prompt, type the following, pressing ENTER after each line: c: cd \windows 4. To start the MS-DOS portion of Windows for Workgroups Setup, type "setup" (without the quotation marks) at the MS-DOS command prompt. 5. The options are either blank or contain some incorrect defaults similar to the following: Keyboard: keyboard.typ Codepage: woafont.fon Select the correct hardware options for your system. 6. Accept the changes. NOTE: When you accept the changes, you are given the option to have Setup copy new drivers. 7. Open the new SYSTEM.INI file in a text editor, such as MS-DOS 6.0 or 6.2 Editor. Make the following changes to the SYSTEM.INI file: - Add PROGMAN.EXE to the SHELL= line in the [boot] section. - Remove or remark out the TASKMAN.EXE= line in the [boot] section. - Add the following NETWORK.DRV= line to the [boot] section: [boot] Network.drv=wfwnet.drv - For Windows for Workgroups 3.1, change the network= line in the [386Enh] section to the following: [386Enh] network=vnetbios.386,vnetsup.386,vredir.386,vserver.386, vbrowse.386,vwc.386 - For Windows for Workgroups 3.11, change the network= line in the [386Enh] section to the following: [386Enh] network=*vnetbios,vnetsup.386,vredir.386,vserver.386,*vwc NOTE: The network= setting in the [386Enh] section of the SYSTEM.INI file should be on one line and should not contain spaces or wrapping around the second line. - To enable 32-bit disk access, add the following lines to the [386Enh] section: 32BitDiskAccess= device=*int13 device=*wdctrl NOTE: To enable 32-bit disk access, replace with "True" (without the quotation marks). If you do not want 32-bit disk access enabled, replace with "False" (without the quotation marks). For more information about 32-bit disk access, see Appendix D in the Windows Resource Kit, or query on the following words in the Microsoft Knowledge Base: Windows and 3.1 and 32-bit and disk and access 8. Start Windows for Workgroups without attempting to load any network drivers: - To start Windows for Workgroups 3.1 in standard mode, type the following at the MS-DOS command prompt: win /s NOTE: Standard mode is not accessible in Windows for Workgroups 3.11. - For Windows for Workgroups 3.11, type the following at the MS-DOS command prompt: win /n 9. In the Main group, choose Control Panel and then choose the Network icon. For Windows for Workgroups 3.11, open the SYSTEM.INI file in a text editor, such as Notepad. 10. Add the workgroup and computer names. For Windows for Workgroups 3.11, add the ComputerName= and Workgroup= settings in the [Network] section. 11. In Windows for Workgroups 3.1, do the following: - Choose the Adapters button. In Windows for Workgroups 3.11, do the following: - Choose the Network Setup icon in the Network group, then choose the Drivers button. 12. Add the network interface card (NIC). NOTE: You may need to first remove and then reinstall the NIC driver. 13. When Windows prompts you to restart the computer, choose the Continue button. 14. Exit Windows and restart Windows in 386 enhanced mode. KBCategory: kbusage kbenv kb3rdparty kbtlc KBSubcategory: wfw wfwg Additional reference words: 3.10 3.11 re-create recreate rebuild rebuilding system.src 3rdparty clean WFWG 3.11: Hardware Compatibility List - Modems for AWFAX Article ID: Q107346 --------------------------------------------------------------- The information in this article applies to: - Microsoft Windows for Workgroups version 3.11 --------------------------------------------------------------- SUMMARY ======= This article contains lists of modems that are known to be compatible or incompatible with Microsoft At Work PC Fax. Modems that do not appear in this list have not been tested by Microsoft Corporation. NOTE: The manufacturer of your modem may have updated the hardware since this list was compiled, causing its modem(s) to be compatible (or no longer to be compatible) with Microsoft At Work PC Fax. MORE INFORMATION ================ Compatible U.S. Modems ---------------------- Vendor Model Class Ext/Int --------------------------------------------------------------- Cardinal 14400 v32bis 1,2 E GVC FM-9648 1 E GVC FAX Modem 14400bps 2 E GVC FAX Modem 14400bps 2 I GVC FAX Modem 2400bps 1 I GVC 9624Vbis 2 E Hayes Optima96+Fax96 5101AM 1 E Hayes Optima 144 +Fax144 5100AM 1 E Hayes Optima24+Fax96 4000AM 1 E Intel SatisFAXtion 400e 1 E Intel SatisFAXtion 400I CAS I Intel SatisFAXtion 300I 1 I Intel SatisFAXtion 200I CAS I Practical Peripheral PM14400FX v.32bis 1 I Practical Peripheral PM14400FXMT 1 E Practical Peripheral PM14400FXSA 1 E Practical Peripheral PM9600FXMT 1 E Practical Peripheral PM2400FX Mini (RC229DP) 1 E Practical Peripheral PM2400EFX 1 I Practical Peripheral PP 24/96 (PP224ATF) 1 I Practical Peripheral RC229DP (Same as Mini) 1 I Supra FAX v32bis 144 1 E Supra FAX v32bis 144 1 I Supra FAX 24/96 1 I U.S. Robotics Sportster 144 1 I U.S. Robotics Sportster 144 1 E U.S. Robotics Sportster 9600 1 E U.S. Robotics Courier Dual 1 E Zoom Pocket 1 E Zoom AFX 96 224ATF 1 E Zoom v32bis 1,2 E ATI Technology 2400et e 1 E ATI Technology 14400etc e 1 E ATT Paradyne DataPort 144 1,2 E ATT Microelectronics AK144 1 I Best Data Products 1442FX14400 1,2 E Best Data Products Smart One 1,2 I Boca Research, Inc. Boca Modem 14400 1 E Cirrus Logic CL-MD 9624at/ec2 1 I Compaq 224ATF 1 I Computer Peripheral ViVa 2496if 2 I Computer Peripheral ViVa 14.4/fax 1,2 E Computer Peripheral ViVa 14.4/fax 1,2 I Data Race RediCARD 1 PCMCIA Data Race ActionFAX 1 I Digicom System (DSI) Scout Plus 1 E Epson EFM144 1 PCMCIA Epson EFM96 1 PCMCIA Ericsson Semafor 2324C 1 E Gateway Telepath FM144 1 E Gateway Telepath II 1 I Sierra VoDaFax 2 I Sierra Class 1 1 I TDK Data Fax Modem 1 I UDS Motorola FasTalkFAX32BX LP II 1 E UDS Motorola V.3257 1 E ZyXEL U-1496 Plus 2 E Macronix, Inc. Maxfax96/144 1,2 I Macronix, Inc. MaxLite 144 2 E Megahertz Corp. 144bps Pocket Fax ModemP2144 1,2 E Megahertz Corp. 96/96 Pocket 1 E Megahertz Corp. XJ1144 1 PCMCIA Megahertz Corp. CC324FM 1 PCMCIA MultiTech MT1432M 2 E MultiTech MT932ba 2 E MultiTech MT224ba 2 E Twincom Twin 144/DF 1,2 E Twincom Twin 144/Dfi 1,2 I Adtech Micro Comm Panion 96/24 1 E Adtech Micro Data Fax 96/24 1,2 I Adtech Micro Hiper Fax 14/14 1 I Adtech Micro Comm Panion 14/14 1 E Alphanetics 224ATF 1 I CMS Enhancements v.24bis/MNP5 2 E E-Tech UFOMate P1496MX 2 E Everex EV-960 2 I Holmes Microsystems Fax 'em Pocket 96 1,2 E LASAT Unique 144 1 E Microcom MicroPorte 4232bis 1 E PCDigital 96/48 1 I PSI Integration COMstation One 1 I Compatible International Modems ------------------------------- Country Vendor Model Class Type ----------------------------------------------------------------- ---- AUS AVTEK MegaPlus Fax V.32bis CD930 2 Pocket AUS AVTEK Mega-Date Fax CD900 1 E AUS Maestro RC224FMI 1 E AUS Maestro 144FMFI 1 E AUS Netcomm Pocket PA-PM2100BE 1 Pocket AUS Netcomm PM1500PK Modem 24 1 Pocket AUS Netcomm SmartModem E7F 2 E FRA 3X 396D 1,2 E FRA Kortex KX Pro 2400 Pocket 1 Pocket FRA Kortex Pocket 1 Pocket FRA NovaFax 14400 Fax 1 Pocket FRA PNB Baby-Pro TT1496 1,2 Pocket GER Dr. Neuhaus Fury DNE 5005 2 PCMCIA GER Dr. Neuhaus Fury DNE 1086 2 E GER Intel CAS/9600 CAS I ITA CDC-SPA CDC-9623 FAX-ECE 1,2 E ITA CDC-SPA CDC-9623 FAX-ICE 1,2 I ITA DIGICOM SNM41PC 1 I ITA SYSNET SMF 36Fax 1,2 E SWE Dynalink 1414VE 1,2 E SWE GVC FM-144vbis 2 E SWE Hidem 2442 FAX 2 E SWE Hidem 14400/Fax 2 E SWE Lasat Unique 14.4 1,2 E SWE Lightspeed 1414 Series 1,2 E SWE Motorola UDS Fasttalk Fax 32bx-32bx 1 E SWE Semafor 1496A 1 E SWE Semafor 2324C 1 E SWE UCOM Fastlink 14400 2 E SWE UCOM Traveller 144 Pocket SWE UFOMATE P1496MX 1,2 Pocket SWE U.S. Robotics Courier V.32bis 1 E SWE U.S. Robotics Sportster 14.4 Fax 1 E SWE U.S. Robotics WorldPort 14.4 1 Pocket UK ANDEST Roadrunner Rocket 1 Pocket UK DataFlex Rapier Plus 1,2 E UK Intel SatisFAXtion CAS I UK PSION-DACOM Port. Fax PTM50F 1,2 Pocket UK SmartLink Pocket Fax Modem 2400 1 Pocket UK SmartLink V32.bis/Fax 2 E UK U.S. Robotics WorldPort 14.4 1 Pocket Incompatible U.S. Modems ------------------------ Vendor Model Class Ext/Int --------------------------------------------------------------- Cardinal MB2296SR 2 I Macronix MAXFAX 9624 2 I Macronix VOMAX 2000 2 E Megahertz 2400 BPS Pocket Fax/Modem P224 FMV 1 E National Tyin 2000 2 E Practical Peripherals PM2400FXSA 2 E RACAL MXF 9632 2 E Zoom FX96/24 2 E Zoom FC96/24 2 I US Robotics Worldport 2496 1 E Incompatible International Modems --------------------------------- Vendor Model Class Ext/Int --------------------------------------------------------------- BIT Blitzer Mx-6 1 E BIT Blitzer XM124s RFAX 2 E Cray Comm Quantum 144 1 E Digicomm SNM28 SR 2 I Dr. Neuhaus Fury 241 2 I ELSA Microlink 14.4 PC 2 I Kortex KX PRO 2400 CAS I La Commande Electonique LCE Minifax 1 E MicroFax Class 2 Pocket Modem 2 E Multitech MT932ba 2 E Sysnet SMF - 04FAX 1 I US Robotics Worldport 2496 1 E The products included here are manufactured by vendors independent of Microsoft; we make no warranty, implied or otherwise, regarding these products' performance or reliability. KBCategory: kbref kbhw kb3rdparty kbatwork KBSubcategory: wfw wfwg wincomm awfax Additional reference words: 3.11 MODEMS works passed failed faxmodems hardware compatibility list hcl SatisFAXion 3rdparty WG0974: VKDA.386 Corrects Keyboard Problems Article ID: Q109561 ---------------------------------------------------------------- ----- The information in this article applies to: - Microsoft Windows for Workgroups version 3.11 ---------------------------------------------------------------- ----- Microsoft has an Application Note, "WG0974: VKDA.386 Corrects Keyboard Problems" When you start Windows for Workgroups version 3.11 on certain computers, your system may stop responding (hang) at the password dialog box or in Program Manager (if you set your password to null during Setup). Application Note WG0974 contains a new virtual keyboard driver to correct this problem. You can obtain this Application Note from the following sources: - CompuServe, GEnie, and Microsoft OnLine - The Internet (Microsoft anonymous ftp server) - Microsoft Download Service (MSDL) - Microsoft FastTips Technical Library - Microsoft Product Support Services For complete information, see the "To Obtain This Application Note" section at the end of this article. THE TEXT OF WG0974 ================== ================================================================ ====== Microsoft(R) Product Support Services Application Note (Text File) WG0974: VKDA.386 CORRECTS KEYBOARD PROBLEMS ================================================================ ====== Revision Date: 8/94 1 Disk Included The following information applies to Microsoft Windows(TM) for Workgroups, version 3.11. ---------------------------------------------------------------- ------- | INFORMATION PROVIDED IN THIS DOCUMENT AND ANY SOFTWARE THAT MAY | | ACCOMPANY THIS DOCUMENT (collectively referred to as an Application | | Note) IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER | | EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE IMPLIED | | WARRANTIES OF MERCHANTABILITY AND/OR FITNESS FOR A PARTICULAR | | PURPOSE. The user assumes the entire risk as to the accuracy and | | the use of this Application Note. This Application Note may be | | copied and distributed subject to the following conditions: 1) All | | text must be copied without modification and all pages must be | | included; 2) If software is included, all files on the disk(s) | | must be copied without modification (the MS-DOS(R) utility | | diskcopy is appropriate for this purpose); 3) All components of | | this Application Note must be distributed together; and 4) This | | Application Note may not be distributed for profit. | | | | Copyright (C) 1994 Microsoft Corporation. All Rights Reserved. | | Microsoft and MS-DOS are registered trademarks and Windows is a | | trademark of Microsoft Corporation. | | AST is a registered trademark of AST Research. | | COMPAQ is a registered trademark and Aero and LTE Elite are | | trademarks of Compaq Computer Corporation. | | DEC is a trademark of Digital Equipment Corporation. | | GRiD is a registered trademark of GRiD Systems. | | IBM and PS/2 are registered trademarks of International Business | | Machines Corporation. | | Tandy is a registered trademark of Tandy Corporation. | |---------------------------------------------------------------- -----| SYMPTOMS ======== When you start Windows for Workgroups version 3.11, your system may stop responding (hang) at the password dialog box or in Program Manager if you set your password to null during Setup. The WG0974 disk included with this Application Note contains a new virtual keyboard driver that corrects this problem for the following computers: Manufacturer | Model(s) ----------------------------------------------------------------------- Acer America | Pac 150, 1100LX Portable | Advent | Machines using Blue Lightning chip set Corporation | | Ambra Corporation | Machines using Blue Lightning chip set, | including B466DL, B466TL, D466DL, D466TL, and | D466BL | AST(R) | Ascentia 900N 486/75 laptop | Compaq | All Aero(TM) machines, LTE Elite(TM) 4/50 or 75CX | Compudyne | Specific models unknown | Crystal Data | 486 machines Systems | | DEC(TM) | 316 SX, 320 SX | GRiD(R) Systems | 320S with Tandy(R)/Phoenix BIOS V 1.10 | GTSI | 0783 486 SX/25 (SFA and desktop) | IBM(R) | Valuepoint PS/2(R) 450TX2/D machine types | 6382, 6384, and 0783 | KLH | computers | Tandy | 2500 SX/20, 2500 SX/25, 2500 SX/33, and 4020 | Twinhead | 486/33, Superset 590 386/25 | Victor | 300 SX/33 and 400 SX NOTE: Machines manufactured by Compaq after April 1, 1994, that ship with Windows 3.1 come preinstalled with a virtual keyboard driver (VKD) that corrects this problem. Upgrading to Windows for Workgroups 3.11 leaves this VKD in place and allows the keyboard to work properly. However, if you install Windows for Workgroups 3.11 to a new directory, the keyboard stops functioning. If you perform such an installation, you must manually install the new VKD. CAUSE ===== The keyboard controllers in these machines generate unnecessary interrupts each time a key is pressed and released. The keyboard stops responding because the Windows for Workgroups 3.11 VKD, unlike the Windows 3.1 VKD, does not ignore these extra interrupts. RESOLUTION ========== To correct this problem, use one of the following methods: - Install the new VKDA.386 file provided with this Application Note. -or- - Install the Microsoft Mouse version 9.x driver. The replacement VKD that comes with this software (MOUSEVKD.386) handles the extra interrupts generated by the keyboards. NOTE: You may also be able to download a new VKD from the your computer manufacturer's bulletin board service (BBS). For example, SP0738.ZIP, which is available on the COMPAQ(R) BBS, contains a new VKD that corrects this problem. Contact your computer manufacturer to see if an updated driver is available. To install the new VKDA.386 file -------------------------------- 1. Insert the enclosed WG0974 disk in the appropriate floppy disk drive. 2. To copy the file to the Windows SYSTEM subdirectory, type the following at the MS-DOS command prompt and then press ENTER copy :\vkda.386 where is the floppy disk drive containing the WG0974 disk and is the drive and directory of your Windows SYSTEM subdirectory. For example, if the WG0974 disk is in drive A and your Windows directory is called WINDOWS and is on drive C, type the following at the MS-DOS command prompt and then press ENTER: copy a:\vkda.386 c:\windows\system 3. Use a text editor to edit the keyboard= entry in the [386Enh] section of the SYSTEM.INI file. Change keyboard=*vkd to: keyboard=c:\windows\system\vkda.386 ---------------------------------------------------------------- ----- TO OBTAIN THIS APPLICATION NOTE =============================== - On CompuServe, GEnie, and Microsoft OnLine, Application Notes are located in the Microsoft Software Library. You can find WG0974 in the Software Library by searching on the word WG0974, the Q number of this article, or S14510. WG0974 is a compressed, self-extracting file. After you download WG0974, run it to extract the file(s) it contains. - On the Internet, Application Notes are located on the Microsoft anonymous ftp server, which you can reach by typing "ftp ftp.microsoft.com" (without the quotation marks) at the ">" command prompt. You can find WG0974.EXE in the SOFTLIB\MSLFILES directory. - Application Notes are available by modem from the Microsoft Download Service (MSDL), which you can reach by calling (206) 936-6735. This service is available 24 hours a day, 7 days a week. The highest download speed available is 14,400 bits per second (bps). For more information about using the MSDL, call (800) 936-4200 and follow the prompts. To obtain WG0974, download WG0974.EXE. WG0974.EXE is a compressed, self-extracting file. After you download WG0974.EXE, run it to extract the file(s) it contains. - You can have this Application Note mailed to you from the automated Microsoft FastTips Technical Library, which you can call 24 hours a day, 7 days a week at (800) 936-4200. NOTE: The FastTips Technical Library is available only to customers within the U.S. and Canada. - If you are unable to access the source(s) listed above, you can have this Application Note mailed to you by calling Microsoft Product Support Services Monday through Friday, 6:00 A.M. to 6:00 P.M. Pacific time at (206) 637-7098. If you are outside the United States, contact the Microsoft subsidiary for your area. To locate your subsidiary, call Microsoft International Sales Information Center at (206) 936-8661. The products included here are manufactured by vendor independent of Microsoft; we make no warranty, implied or otherwise, regarding these products' performance or reliability. KBCategory: kbhw kbfile kbappnote kb3rdparty KBSubcategory: wfw wfwg windrvr Additional reference words: appnote hangs freezes lockup locks up Contura Aero Troubleshooting Insufficient Memory Errors Article ID: Q112676 ---------------------------------------------------------------- ---------- The information in this article applies to: - Microsoft Windows operating system versions 3.0, 3.0a, 3.1, 3.11 - Microsoft Windows for Workgroups versions 3.1, 3.11 ---------------------------------------------------------------- ---------- SYMPTOMS ======== You receive insufficient memory errors in Windows or Windows for Workgroups when you try to run an application or perform a task. The specific error messages vary but are similar to the following: - Application Execution Error Insufficient memory to run this application. Quit one or more Windows applications and then try again. -or- - There is not enough memory available. CAUSE ===== These errors may be caused by any of the following: - Insufficient Memory in the Global Heap - Insufficient Windows System Resources - File Corruption, Application Problems, or Configuration Problems - Low Memory Below 1 Megabyte (MB) - Low Windows Selectors - The BIOS Is Configured Incorrectly for Your System Each of these issues, and possible workarounds, is discussed below. Although these issues are listed in the order they are most likely to occur, troubleshooting insufficient memory errors in Windows is not always a straightforward step-by-step process. To increase your knowledge of the major issues and decrease your troubleshooting time, you may want to read this entire article before you proceed. MORE INFORMATION ================ Insufficient Memory in the Global Heap -------------------------------------- Cause: The entire memory area that Windows controls is called "global memory" or the "global heap." The global heap begins at the location where MS-DOS first loads Windows into memory and ends at the top of available memory, which most often is at the top of physical memory. A Windows-based application returns an insufficient memory error if the amount of free memory in the global heap, after swapping, is insufficient to run the application or perform the selected task. To determine how much memory is free in the global memory heap, set your Windows swap file to None in Control Panel's 386 Enhanced Virtual Memory dialog box and then choose About Program Manager from the Help menu in Program Manager. The Memory value reported is free memory in the global heap. If your application requires more memory than is available in the global heap, you may receive an "out of memory" error message. Increasing the size of the swap file may allow Windows to swap enough information to disk to free memory in the global heap. Resolution: To free more memory for your application, close one or more Windows-based applications or increase the size of your permanent swap file. If this does not correct the out of memory errors, you may need to update your system with additional RAM. Insufficient Windows System Resources ------------------------------------- Cause: Insufficient memory errors also occur when Windows calculates that not enough system resources exist to perform the desired operation. Status: In Windows 3.1 and Windows for Workgroups, system resources are determined by the following four heaps: - GDI.EXE (64-kilobyte [K] data segment) The GDI.EXE heap contains information about graphical objects, such as pens, brushes, cursors, fonts, icons, buttons, scroll bars, and so on. In Windows 3.1 and Windows for Workgroups, the GDI heap is likely to be the bottleneck; therefore, closing heavily graphics-oriented applications results in GDI resources being freed. - USER.EXE (64K data segment) The USER.EXE heap contains information about the windows currently in existence, dialog boxes, controls in dialog boxes, and so on. - menu (64K data segment) - menu strings (64K data segment) The menu and menu string heaps are new in Windows 3.1. These heaps, originally combined in USER.EXE under Windows 3.0, were designed to free up space in the USER heap. These heaps are created dynamically (that is, at run time) by the USER heap. They are not contained in any .EXE files and are each limited to 64K. When you choose About Program Manager from the Help menu, Windows and Windows for Workgroups report the heap with the smallest amount available as the amount of free system resources. To maintain backwards compatibility with earlier versions of Windows and Windows-based applications, all four heaps were each designed with a 64K data segment limit. Resolution: Some applications may not release all the system resources they use after they are closed. If you have a chronic problem with one or more applications, contact the manufacturer of the applications for more information. Some 16-bit Windows applications (such as Microsoft Word for Windows, Microsoft Access, Microsoft Visual Basic, and Microsoft Excel) require ample free amounts of both USER.EXE and GDI.EXE heaps because of the graphical user interface (GUI). If these applications do not find available space to load their information into these heaps, they generate an insufficient memory error (or a similar error). A large Excel workbook and large graphical images on machines running high resolution video drivers rely heavily on the GDI resource because of their graphical nature. If your system resources are often low, keeping few applications running is probably the best solution; however, you may also want to try the following: - Minimize seldom-used groups to conserve system resources. - Do not use wallpaper, or use a small bitmap and tile it. - Try not to open groups that have many icons. - If you run an application that uses system resources every time it runs, try to keep it open instead of closing and reopening it many times. - Try not to load fonts that are not needed. - Check your screen savers to make sure that they are not overusing resources. File Corruption, Application Problems, or Configuration Problems ---------------------------------------------------------------- Cause: Insufficient memory errors may occur when two or more memory resident programs or drivers conflict, when Windows accesses corrupted files or files that are still in compressed form, or when there is a problem in the application you are running. Resolution: Try to isolate the problem to a specific application. Clean boot the computer so that only the necessary Windows and application-specific device drivers and terminate-and-stay-resident (TSR) programs are loading in the CONFIG.SYS and AUTOEXEC.BAT files. For more information about a "clean boot" for Windows and Windows for Workgroups, query on the following words in the Microsoft Knowledge Base: clean and boot and append Disable any applications that start automatically when you start Windows (check the WIN.INI file and the StartUp group), run Windows Setup and change to standard Windows drivers (VGA, No Mouse, No Network), and use the Program Manager (PROGMAN.EXE) as your Windows shell. If the insufficient memory errors occur only in a specific application, try reinstalling the application to a new directory or manually expand any necessary files to rule out file corruption. If the application has never worked, it is possible that the files on the original installation disks are corrupted. Try to install the offending application on another computer using the same disks. If these procedures do not eliminate the problem, contact the manufacturer of the application that is causing the errors. Low Memory Below 1 Megabyte (MB) -------------------------------- Cause: When Windows creates a new task (that is, starts a new application), the Windows loader creates a task database (TDB) for it. The TDB contains vital information about the task, such as its current directory, its instance handle, and so on. To maintain compatibility with 16-bit Intel processors and MS-DOS, Windows creates the TDB in memory below 1 MB in the global heap. Because the only memory below 1 MB in the global heap is conventional memory, the TDB must be created below 640K (conventional memory). Status: Memory below 1 MB is limited and should be used sparingly. TDBs are not the only block of memory that may end up below 1 MB. Applications such as Microsoft Word for Windows, Microsoft Remote Access Services (RAS), Microsoft Anti-Virus , Microsoft Mail, Microsoft Schedule+, and multimedia packages are examples of applications that load .DLL files into the first megabyte of memory when loading or performing certain operations. Every segment in the Windows global heap is marked with certain attributes that tell Windows how to manage the segment. First and foremost, the segments are marked as Fixed or Moveable. A fixed segment always resides at the same physical memory location where it was first allocated (although it can be paged if it is not "page-locked"). Movable code can be moved or marked as Discardable code. This means that Windows can move moveable segments in memory if necessary to make room for other memory allocations or, if the code is marked as Discardable, Windows can discard the code by determining the "least recently used" (LRU) discardable segment. Windows can later reload the discardable code by accessing the application's .EXE file. The enhanced mode global heap is composed of a series of free and in-use blocks stored contiguously in memory. When Windows is asked by an application to allocate a block of memory, KRNL386.EXE starts at the beginning or end of the global heap, depending on the type of code the application loads, and iterates through each of the blocks until it finds a suitably sized free block. KRNL386.EXE starts to allocate fixed segments from the bottom up in the global heap. At the top of the global heap, Windows allocates discardable segments. Between the fixed and discardable segments, Windows allocates moveable segments. When an application starts and Windows needs to allocate fixed segments, Windows starts searching from the bottom up for a sufficiently large free block below the area of moveable segments. This is to avoid memory fragmentation. If it cannot find a segment large enough it begins moving moveable segments up in memory to make room. If that doesn't work, Windows begins discarding discardable segments. TDBs must be located below 1 MB, but fixed and moveable memory segments do not. An insufficient memory error that appears when you try to start an application may occur because fixed segments, which are loaded starting from the bottom of the global heap to avoid memory fragmentation, end up loading in the first megabyte. These fixed memory segments cannot be moved if they are "page-locked," hence they may consume memory space that Windows would otherwise use to load the TDBs. KRNL386.EXE's desire to keep fixed memory as low as possible conflicts with the need to keep memory below 1 MB as free as possible. Because of the way Windows allocates memory, memory below 1 MB is a limited resource even when you are running Windows-based applications. Program developers are encouraged to ensure that their programs and .DLL files do not use this space needlessly. Fixed memory segments should not be used unless absolutely necessary. Resolution: To troubleshoot this problem, optimize conventional memory as much as possible. If you have MS-DOS version 6.0 or 6.2, use MemMaker to optimize conventional memory. You may also want to change the order in which your programs or drivers load. This may alter where the fixed code gets located and minimize memory fragmentation. For a workaround, create a multi-boot configuration to minimize what loads into conventional memory for particular operations. This may free enough space so that Windows can load the TDBs. Disable any applications that start automatically when you start Windows (check the WIN.INI file and StartUp group), run Windows Setup and change to standard Windows drivers (VGA, No Mouse, No Network), and use the Program Manager (PROGMAN.EXE) as your Windows shell. For troubleshooting, remove any third-party Windows drivers or virtual device drivers (VxDs) by rebuilding the WIN.INI and SYSTEM.INI files. For more information about this procedure, query on the following words in the Microsoft Knowledge Base: win.ini and win.sr_ and create -and- system.ini and system.sr_ and create Low Selectors ------------- Cause: An important aspect of Windows-based application memory management that is NOT included in the free system resources percentage is the number of selectors. A selector is a memory pointer that is consumed with each memory allocation made by a Windows-based application. Windows has a fixed number of selectors (4096 in standard mode, 8192 in 386 enhanced mode). If a Windows-based application allocates a very large number of small data objects, it is possible to run out of selectors. This also produces an insufficient memory message. Resolution: These problems are application specific. Writing a Windows-based application to handle its own data objects more efficiently can help in this situation. If you experience a chronic problem with a particular application while none or few other applications are loaded and the computer is clean-booted, contact the application vendor. It is important that the vendor become aware of the problem so that it can be corrected if possible. The BIOS Is Configured Incorrectly for Your System -------------------------------------------------- If your BIOS is incorrectly configured for a floppy disk drive, you may receive the aforementioned error messages when you attempt to install software. For example, an error can occur if you have a 1.44-megabyte 3.5- inch floppy disk drive installed and the BIOS is set for a 1.2-megabyte 5.25-inch disk drive. REFERENCES ========== "Windows 3.1 Technical Reference Manual" "Microsoft Systems Journal," October 1993, pages 69-75 "Programming Windows 3.1," by Charles Petzold, pages 271-303 KBCategory: kbhw kbdisplay kbtshoot kberrmsg KBSubcategory: win30 win31 wfw wfwg winmem Additional reference words: 3.00 3.0 3.0a 3.10 3.1 3.11 browser err msg not enough memory tshoot mb mega byte Using 32-Bit Disk Access on WD 2540 Hard Disk Drives Article ID: Q113751 ---------------------------------------------------------------- ---- The information in this article applies to: - Microsoft Windows operating system versions 3.1, 3.11 - Microsoft Windows for Workgroups versions 3.1, 3.11 ---------------------------------------------------------------- ---- The following article contains information about the use of Windows and Windows for Workgroups with third-party products or configurations that have not been tested and are not supported by Microsoft. If the steps or procedures described in this article do not function properly, contact the manufacturer of the third-party product for more information or use a supported configuration. SYMPTOMS ======== After you enable 32-bit disk access, the system becomes unstable or stops responding (hangs) during startup, or Windows displays one of the following error messages: - The Microsoft Windows 32-bit disk driver (WDCTRL) validation failed at phase 07, 1F. -or- - The Microsoft Windows 32-bit disk driver (WDCTRL) validation failed at phase 03, 3F. -or- - Windows: This application has tried to access your hard disk in a way that is incompatible with the Windows 32-bit disk access feature (WDCTRL). This may cause your system to become unstable. -or- - Insufficient memory or address space to run Windows in Enhanced mode. Remove TSR programs to free memory. CAUSE ===== These errors occur when you use a system that includes a hard disk drive with more than 1024 cylinders. Western Digital has confirmed that the Caviar model 2540 516-megabyte hard disk drive uses BIOS parameter settings that are incompatible with the 32- bit disk access device driver included with Windows 3.1 and Windows for Workgroups 3.1 and 3.11 (WDCTRL). You can, however, use 32-bit file access (VFAT) in Windows for Workgroups 3.11. You may also receive these error messages when you use a Quantum LPS540AT configured to its default specifications (1120 cylinders, 59 logical sectors/track, and 16 heads). According to Quantum Technical Support, this drive can be configured with 1024 cylinders, 63 logical sectors/track, and 16 heads to avoid the error message. The MAXTOR 7548AT IDE hard disk drive has 1060 cylinders, 16 heads, and 63 sectors per track and causes one of the above error messages. Reducing the cylinder count in the CMOS setup to 1024 cylinders corrects this problem. If you continue to get one of the above error messages after setting the number of cylinders to 1024 in your CMOS settings, you may need to added the NOMOVEXBDA parameter to the EMM386.EXE command in your CONFIG.SYS file. The DTC 2278VL hard disk controller uses a device driver called DTC2278.SYS that can cause these error messages. Please contact DTC for more information on this issue. WORKAROUND ========== To work around this problem, choose one of the following methods: - Western Digital offers the following two workarounds on its bulletin board service (BBS): - If the BIOS in the system does not support drives with more than 1,024 cylinders, download a utility program called WDSWT.COM. This program can stamp the drive with a parameter translation brand so that it reports 1024 cylinders to the Windows 32-bit disk access driver (WDCTRL). This procedure is reversible--in case you need to install the AC2540 in a system that DOES support drives with more than 1,024 cylinders. NOTE: WDSWT.COM is for use on the AC2540 only; it is not for use on the AC2700 (730 megabytes) or AC3100 (1,083 megabytes) drives. -or- - Download the self-extracting file WIN31.EXE. This file contains the driver WDCDRV.386, which can be used to replace WDCTRL. For more information about using WDSWT.COM or WDCDRV.386, contact Western Digital Technical Support. - Update your computer's ROM BIOS to a version that supports logical block addressing (LBA) to automatically translate over 1024 cylinders. Contact your computer manufacturer for more information about this procedure. - Disable 32-bit disk access in Control Panel. To access this setting, choose the 386 Enhanced icon in Control Panel and then choose the Virtual Memory button. You can still use 32-bit file access (VFAT) in Windows for Workgroups 3.11, but VFAT mounts using the real-mode mapper (RMM.D32) instead of 32-bit disk access. - Change the CMOS parameters for the drive to 1024 cylinders or fewer, and then run Fdisk and reformat the drive. This workaround allows use of WDCTRL but does result in a loss of 11.8 MB of disk space. For more information about these workarounds, contact Western Digital Technical Support. MORE INFORMATION ================ The Western Digital Caviar 2540 model is a 540-megabyte (MB) hard disk drive that uses a drive parameter setting of 1048 cylinders, 16 heads, and 63 sectors. 32-bit disk access is a set of protected-mode device drivers that work together to enhance your system's BIOS. It filters interrupt (Int) 13H calls to the hard disk controller and directs them in the most efficient way for the system (either through the 32-bit interface with the hard disk controller or through the system BIOS). The Windows 32-bit disk access driver (WDCTRL) supports disk controllers that are compatible with the Western Digital 1003 controller interface standard, but WDCTRL is compatible only with hard disk drives with 1024 or fewer cylinders. 32-bit file access (VFAT) in Windows for Workgroups 3.11 is not affected by the method used to work around this problem. On drives with more than 1024 cylinders without 32-bit disk access, VFAT mounts over the real-mode mapper (RMM.D32). Replacing WDCTRL with Western Digital's 32-bit disk access driver, WDCDRV.386, should allow VFAT to work properly. VFAT and WDCTRL should both work properly if the computer BIOS supports logical block addressing. The products included here are manufactured by vendors independent of Microsoft; we make no warranty, implied or otherwise, regarding these products' performance or reliability. KBCategory: kb3rdparty kbdisplay kbtlc KBSubcategory: wfw wfwg Additional reference words: 3.1 3.11 err msg VFAT dmdrvr.bin disk manager gateway gateway200 pentium p5 p5-60 2000 03, 3f 033f 33f P5-66 07,1F 07, 1F 071F 540 12.5 million fastdisk AC 2540 7548 7546A 3rdparty WFWG Err Msg: Error 58 on Protocol 0 Article ID: Q114370 ---------------------------------------------------------------- ------ The information in this article applies to: - Microsoft Windows for Workgroups version 3.11 ---------------------------------------------------------------- ------ SYMPTOMS ======== When you start Microsoft Windows for Workgroups version 3.11 with Novell connectivity installed through IPXODI, the following error may occur: The following error occurred while loading protocol number 0. Error 58: The network responded incorrectly. You may need to reconfigure the protocol using Network Setup. If your computer is a portable, make sure it is connected to its docking station." NOTE: Choosing OK in this dialog box allows Windows to load; however, the Microsoft Windows Network is disabled. CAUSE ===== When you install Novell IPXODI support in Windows for Workgroups 3.11, Setup must make certain assumptions about the IPXODI configuration since Windows for Workgroups 3.11 does not ship with any of the Novell ODI files. One of the assumptions concerns the specific name of the multiple link interface driver (the Novell ODI network interface card driver). This name is referenced in the PROTOCOL.INI file on the Bindings= line(s). If the driver name specified on the Bindings= line does not match the name of the multiple link interface driver (MLID) being used, the above error may be generated. RESOLUTION ========== To correct this error, make a note of the actual name of the MLID file listed after LSL.COM in the AUTOEXEC.BAT or STARTNET.BAT file. Edit the PROTOCOL.INI file and verify that the Bindings= line matches the MLID file described above. If the Bindings= entry does not match the MLID name, correct the line so that it does. NOTE: On some configurations there may be two Bindings= lines. Example ------- The following example uses a 3Com Etherlink III (3C5x9) NIC, which is one of the more common cards with which the above error message occurs. Below are excerpts of the files created by Network Setup. AUTOEXEC.BAT: C:\WINDOWS\NET START C:\\LSL.COM C:\\<3C5X9.COM> (This is the MLID.) C:\\IPXODI.COM C:\WINDOWS\ODIHLP.EXE C:\\NETX.EXE PROTOCOL.INI: [NWLINK] Bindings=3C509 [NETBEUI] Bindings=3C509 Note that the MLID filename in the AUTOEXEC.BAT file is 3C5x9.COM, but the PROTOCOL.INI file references 3C509; including the file extension will result in the problem not being resolved. The corrected PROTOCOL.INI should read as follows: [NWLINK] Bindings=3C5x9 [NETBEUI] Bindings=3C5x9 For more information about this error in non-ODI configurations, query on the following words in the Microsoft Knowledge Base: netbeui and wfwg and ndis and tshoot KBCategory: kbnetwork kbtshoot kb3rdparty kbsetup kberrmsg kbtlc KBSubcategory: wfw wfwg Additional reference words: adapter 3.11 netware Troubleshooting Remote Access in Windows for Workgroups 3.11 Article ID: Q115593 ---------------------------------------------------------------- ----- The information in this article applies to: - Microsoft Windows for Workgroups version 3.11 ---------------------------------------------------------------- ----- SUMMARY ======= This article contains a step-by-step guide for troubleshooting Remote Access Services (RAS) in Windows for Workgroups 3.11. MORE INFORMATION ================ Steps to Troubleshoot Problems with Remote Access Services ---------------------------------------------------------- 1. Determine whether the modem works at the MS-DOS command prompt. Exit Windows and issue the command "Echo ATDT5555555 > COMx" (without the quotation marks, where x is the number of the communications port) at the MS-DOS command prompt. If you hear the tone from the modem dialing 555-5555, proceed to step 2. If you do not hear a dial tone, the modem may need to be reconfigured for the correct port address and interrupt. Also, if the modem is external, check the serial cable to ensure a good connection and make sure the proper cable is being used. If the modem is internal, move the modem to a different slot in the computer and check the configuration of the jumps on the modem (if any exist). Refer to with the modem documentation for setup and technical support information. 2. Determine whether the modem works in Windows Terminal. In the Accessories group, open Terminal and type the command "ATDT" (without the quotation marks). If the correct communications (COM) port is selected for the modem, a dial tone should be heard and OK or 0 (zero) should be returned to the modem terminal screen. Pressing ENTER should cancel the command to the modem and the message "NO CARRIER" should be returned to the screen. If you do not hear a dial tone after the ATDT command, choose Communications from the Settings menu to make sure the correct Connector (COM Port) setting is selected. If you do not see the text echoed back to the screen as you type the command, choose Terminal Preferences from the Settings menu and select the Local Echo option under Terminal Modes. If the modem does not work in Terminal, the modem may not be correctly configured for Windows (or possibly MS-DOS). If so, try the following: - Disable 32-bit file access. To do so, choose the 386 Enhanced icon in Control Panel, choose the Virtual Memory button, choose the Change button, and then clear the Use 32-Bit Disk Access check box. - In the Windows directory, open the SYSTEM.INI file and check the [Boot] section for the proper communications driver used globally throughout Windows. The line should read, COMM.DRV=COMM.DRV. If COMM.DRV= is set to anything other than COMM.DRV, change the line to read COMM.DRV=COMM.DRV. Also, make sure the COMM.DRV file in the Windows SYSTEM subdirectory has the file date 11/1/93 and a file size of 5968 bytes. If the modem still does not work in Terminal, obtain the Microsoft Application Note WW0654, "Windows 3.1 and Serial Communications." You can have this Application Note mailed or faxed to you from the automated Microsoft FastTips Technical Library, which you can call 24 hours a day, 7 days a week at (800) 936-4200. NOTE: The FastTips Technical Library is available only to customers within the U.S. and Canada. 3. Check RAS again after performing the above steps. If Terminal is working and RAS is still not working, add the line COMxFIFO=0 to the [386Enh] section of the SYSTEM.INI file using a text editor. This command turns off the 16-bit buffer built into the 16550 UART chip, forcing one-bit operation of serial data through the UART chip. 4. Check the file RASMAC.386 in the Windows SYSTEM subdirectory. If RASMAC.386 is dated 11/1/93, disable software compression. To do this, choose Disable Software Compression from the Options menu in RAS. (The next time you open the Options menu, a check mark should be beside Disable Software Compression.) If disabling software compression helps, use hardware compression instead. 5. Try a lower bits-per-second (bps) rate. Slowing the speed of the modem can often help decrease noise on the phone lines. It can also help with compatibility problems when using high-speed modems (9600 bps and above) that differ slightly in their compression and error-correction standards. If the lower bps rate works, you may want to disable hardware flow control and/or modem compression. To do this, choose the Phone Book Edit button in RAS, choose the Modem button, and then clear the Enable Hardware Flow Control and/or Enable Modem Compression options. 6. Check the modem documentation to see if the recommended initialization string differs from the one in the MODEM.INF file found in the Windows SYSTEM subdirectory. If it does, try entering the command manually. Choose the Phone Book Edit button, choose Modem, and select the Enter Modem Commands Manually option. This allows you to enter a modem command string manually to determine whether the default one in the MODEM.INF is related to the problem. 7. Check the BIOS date of the modem. Check the BIOS date of the modem with the manufacturer to see if a newer BIOS is available. To check the BIOS date of the modem using Terminal, issue the command ATIx (where x is a value between 1 and 9). For example, in Terminal, issue the command ATI3, then . A BIOS version number should be displayed on the screen, (for example, V1.200 or ver .59). If there is a newer BIOS available, update the BIOS by downloading the firmware (software) from the modem manufacturer's bulletin board service (BBS) or CompuServe Information Service (CIS) forum if available. Some modem manufacturers have a single-chip upgrade available if the BIOS of the modem is not software upgradeable. 8. Determine whether the modem is supported in RAS. If it is an unsupported modem, refer to step 6 above for information about checking for the correct communication string sent by RAS from the MODEM.INF file. You can make your own section by cutting and pasting the information from a related modem section with your own section heading (such as [my modem]). This method is not supported, but it may be the only way RAS can communicate with your modem. Common Error Messages in RAS ---------------------------- Error 615: When you use RAS in Windows for Workgroups 3.11, you may receive the message "Error 615: The port was not found." This error can occur when the Remote Access Phone Book file and the current Remote Access configuration are inconsistent. If you have changed your communications equipment (for example, your serial port or modem), be sure to reconfigure RAS. (For more information, see "Reconfiguring Remote Access" in the online help file.) If the error persists, remove and re-create the affected Phone Book entry or reinstall RAS. The Remote Access Phone Book (RASPHONE.PBK) is in the Windows subdirectory. Error 640: The message "Error 640: A Net BIOS error has occurred" is generated when the modem does not negotiate the connection correctly or when the line is noisy. Set the modem to a lower initial bits-per-second (bps) speed, and then dial again. (For more information, refer to "Setting Modem Features" in the online help in RAS.) If reducing the modem speed does not correct this error, RAS is probably running out of conventional memory to set up its session. RAS uses conventional memory (about 90 kilobytes [K]) without being in the Answer mode as the server. With RAS set up as the server and in Answer mode, RAS uses about 120K of conventional memory. You may want to clean boot to see if you can make more conventional memory available. Most RAS NetBIOS error 640 messages occur when your system has less than 500K free conventional memory at MS-DOS before starting Windows for Workgroups. Remove any terminate-and- stay-resident (TSR) programs and other network drivers to determine whether more conventional memory solves the problem. NOTE: Having the NET START command in the AUTOEXEC.BAT file and IFSHLP.SYS in the CONFIG.SYS file are required to run RAS. For more information on Error 640, query on the following words in the Microsoft Knowledge Base: netbios and error and 640 Error 692: When dialing using RAS, you may receive the message "Error 692: Hardware Failure in Port or Attached Device" even though all other communication software is working correctly. This error message is reported when RAS cannot correctly communicate with the modem. To correct this problem, you must first know the reason RAS cannot communicate with the modem. Check the selected modem for RAS with the following steps: 1. Choose the RAS icon in the Network group. 2. Choose Setup from the menu list and then choose Configure. 4. Check the device selected and the port to which it is assigned. The modem's handshaking requirements may not match what is being sent by RAS, or the emulation for the modem may be incorrect. RAS uses a file called MODEM.INF in the Windows SYSTEM subdirectory to send the right communication strings to the modem through the selected modem in RAS. If you use a text editor (such as Windows Write) with the No Conversion option selected to open the MODEM.INF file, you can find the modem you have selected in RAS to look at the COMMAND_INIT string. COMMAND_INIT string is the communication string RAS sends to set up the modem for communication. Refer to the modem documentation or check with the modem manufacturer for the correct communication string for your modem. For more information on this error message, query on the following words in the Microsoft Knowledge Base: RAS and ERROR and 692 NOTE: The following updated communication Application Notes are available from Microsoft: - WG0992: Updated Files for Microsoft At Work PC Fax 1.0 - WG1001: Updated SERIAL.386 Driver for Windows for Workgroups To obtain these Application Notes: - On CompuServe, GEnie, and Microsoft OnLine, Application Notes are located in the Microsoft Software Library. You can find WG0992 and WG1001 in the Software Library by searching on the words WG0992 and WG1001; or S14577 and S14599, respectively. These files are compressed, self-extracting files. After you download the files, run them to extract the file(s) they contain. - On the Internet, Application Notes are located on the Microsoft anonymous ftp server, which you can reach by typing "ftp ftp.microsoft.com" (without the quotation marks) at the ">" command prompt. You can find WG0992.EXE and WG1001. EXE in the SOFTLIB\MSLFILES directory. - Application Notes are available by modem from the Microsoft Download Service (MSDL), which you can reach by calling (206) 936-6735. This service is available 24 hours a day, 7 days a week. The highest download speed available is 14,400 bits per second (bps). For more information about using the MSDL, call (800) 936-4200 and follow the prompts. To obtain WG0992 and WG1001, download WG0992.EXE and WG1001.EXE, respectively. These files are compressed, self-extracting files. After you download these files, run them to extract the file(s) they contain. - You can have this Application Note mailed to you from the automated Microsoft FastTips Technical Library, which you can call 24 hours a day, 7 days a week at (800) 936-4200. NOTE: The FastTips Technical Library is available only to customers within the U.S. and Canada. - If you are unable to access the source(s) listed above, you can have these Application Notes mailed to you by calling Microsoft Product Support Services Monday through Friday, 6:00 A.M. to 6:00 P.M. Pacific time at (206) 637-7098. If you are outside the United States, contact the Microsoft subsidiary for your area. To locate your subsidiary, call Microsoft International Sales Information Center at (206) 936-8661. KBCategory: kbother kbtshoot kbfile KBSubcategory: wfw wfwg awfax ras Additional reference words: 3.11 tshoot remote access service baud softlib Summary List: Windows for Workgroups 3.11 Confirmed Problems Article ID: Q120554 ---------------------------------------------------------------- ---- The information in this article applies to: - Microsoft Windows for Workgroups version 3.11 ---------------------------------------------------------------- ---- The following is a list of confirmed problems in Windows for Workgroups version 3.11. For more information on each issue, query in the Microsoft Knowledge Base on the article identifier (ID). ======================================================= Summary Listing for Windows for Workgroups Version 3.11 ======================================================= Article ID Article Title ---------- ------------------------------------------------------------- Q86705 Problems When Exiting Windows or WFWG After Running 386 Enh Q89484 GP Fault in WFWG Mail May Suppress Password Q89880 Toolbar Buttons Extend Beyond the Toolbar in File Manager Q89973 Net Watcher: Lines Appear in Share Name When Scrolled Q89977 Print Manager Help Error: Cannot Use CTRL+UP ARROW Q90422 WFWG Err Msg: Application Has Violated System Integrity Q91000 "How To Use Help" Command in WFWG Setup Does Not Work Q91114 WFWG Err Msg: NET3651: There Is No Protocol Added... Q92577 WFWG: GP Fault in Video Driver When Using ClipBook Viewer Q92634 Invalid Err Msg in Print Manager w/14-Character Machine Name Q92877 WFWG May Hang If TCP/IP Hasn't Registered at Logon Time Q92880 WFWG Mail Incorrectly Displays Bad Network Connection Icon Q92996 Local Printer Causes 1st Network Print Job to Disappear Q94766 Workstation Not Showing Status w/Print Mgr Minimized on Server Q99387 WFWG: Status Bar Option in Chat Shows Incorrect Shortcut Key Q105502 CAS Modem Fails to Receive Faxes with WFWG 3.11 Q106022 Network Dialog Err Msgs Truncated with Small Fonts Q106042 WFWG Err Msg: This Application Was Communicating on...Network Q106274 Certain Network Adapters Can Use DMA Channels 0-3 Only Q106365 Positions of Minimized Icons Are Not Saved in File Manager Q106367 WinPopup Message Incorrectly States Message Was Sent Q107199 Windows Help Does Not Save Maximized Window Position Q107471 WFWG 3.11 Err Msg: Segment Load Failure Q107473 WFWG 3.11 Err Msg: Access Denied Q107476 Video Seven VRAM II Video Adapter Hangs WFWG 3.11 Setup Q107580 Net Watcher Event Log May Not Clear Q107994 "Not Enough Memory" Error Occurs When Browsing Q108100 PC-NFS Error: NFS903F Missing or Invalid PROTOCOL.INI Data Q108818 WFWG May Hang at Startup with 32-Bit File Access & NoEmmDriver Q109054 Games Group Installed Even If Games Are Not Selected Q109447 WG0971: NDIS2SUP.386 Corrects Problems Restarting WFWG Q109448 WG0970: VNETBIOS.386 Corrects Real-Mode Transport Problems Q109562 WG0973: RMM.D32 Corrects 5-Second Delay When Starting Apps Q111333 Errors on Token Ring Network with Banyan Vines 5.52 and WFWG Q111566 Microsoft Mail Err Msg: Error: Unable to Allocate Hook... Q111567 WFWG Setup with HP Ethertwist Cards: No Network Installed Q111568 Video Display Problems with MS-DOS Prompt and Trident Card Q111569 Cannot See Writing with Pen Pointing Device and Super VGA Q111570 System Hangs Using Super VGA Driver with Compaq QVision Q111571 Video Corruption with Diamond Stealth and WFWG VGA Driver Q111572 Basic Redir Repeatedly Prompts for User Name & Password Q111573 Standby Mode with APM, Mail, & AWFAX May Result in a GP Fault Q111574 Server Problems After Extended Use w/EtherExpress & EXP16ODI Q111575 Security Settings File Error with Shared Windows Installation Q111683 New Installation of WFWG with IPX.COM Gives Erroneous Dialog Q111685 AWFAX: Invalid Directory Accepted in Share Fax Modem Dialog Q111796 WG0988: IBMTOK.386 Corrects Problems with Exiting WFWG Q111797 WG0991: Updated NE2000.386 Allows WFWG to Start Correctly Q111798 WG0992: Updated Files for Microsoft At Work PC FAX 1.0 Q111882 TI MicroLaser w/EXP16ODI.COM Driver May Cause 15-Second Delay Q111966 WFWG WinPopup Incorrectly Reports Print Job Completed Q111980 WG0990: ELNK3.386 Corrects System Hangs (Non-802.3 Packets) Q112024 WG1002: SCHEDMSG.DLL Corrects French Headers Q112198 WinPopup Sends Multiple Messages to a Workgroup Q112300 WG1001: Updated SERIAL.386 Driver for WFWG Q112368 Chat Text Is Pasted in the Wrong Window Q112739 Error Renaming Expanded Directory When Running NetWare 3.x Q113455 AWFAX: Excel Macro File Does Not Render Correctly When Faxed Q113456 Problems Sending Faxes from MAPI-Enabled Applications Q114337 SETUP /H Installs NETDDE with Novell-Only Setup Q115321 Incorrect Time Stamp on File Copied to Disk w/Inadequate Space Q119204 Setup Problems on NEC Docking Station When Checking for APM Q119208 AWFAX: CAS Modem Receives Fax with Jagged Print Q104551 WW0863: Fixing System Hangs with MS-DOS Apps & Novell NetWare Q109561 WG0974: VKDA.386 Corrects Keyboard Problems Q112161 WG1004: MSODISUP.386 Fixes Problems Using 3Com ODI MLIDs Q116233 WG1027: Updated NWLINK.386 Allows Routing Across Cisco Routers KBCategory: kbnetwork kbdisplay kb3rdparty kbbuglist KBSubcategory: wfw wfwg Additional reference words: 3.11 Installing Win32s in Windows and Windows for Workgroups Article ID: Q120901 ---------------------------------------------------------------- ---- The information in this article applies to: - Microsoft Windows operating system versions 3.1, 3.11 - Microsoft Windows for Workgroups versions 3.1, 3.11 - Microsoft Win32s, versions 1.0, 1.1, 1.15, 1.2 ---------------------------------------------------------------- ---- SUMMARY ======= Win32s is a set of DLLs and a virtual device driver (VxD) that allows Win32-based applications to run on top of Windows or Windows for Workgroups. If you receive the following error message when you run or install a Win32-based application This program cannot be run in DOS mode Win32s is either not installed or not installed properly. You can use Freecell to test your installation of Win32s. MORE INFORMATION ================ Win32s Version 1.2 Availability and Support ------------------------------------------- Win32s is available from many sources. Microsoft Personal Operating System environments Support Engineers support the installation of Win32s when it is obtained from any of the following sources: - CompuServe GO MSL Search for PW1118.EXE Display results and download - Microsoft Download Service (MSDL) Dial (206) 936-6735 to connect to MSDL Download PW1118.EXE - Internet (anonymous FTP) ftp ftp.microsoft.com Change to the \SOFTLIB\MSLFILES directory Get PW1118.EXE - Mosaic on the World Wide Web by using URL ftp ftp.microsoft.com Change to the \SOFTLIB\MSLFILES directory Get PW1118.EXE - MSDN (Win32 SDK and NT DDK CD) - Win32 SDK CD Microsoft Windows and Windows for Workgroups support engineers may not be able to assist you with individual application or Win32s development questions. Contact your software manufacturer or Microsoft Developer Support for assistance in these areas. Win32s Problems --------------- Freecell is an application available with Win32s in the above locations. To test your installation of Win32s, run Freecell. If you are experiencing problems but Freecell runs properly, contact the manufacturer of the product you are attempting to run or install for further information. If Freecell generates an error, continue reading the following information. One of the following error messages occurs when you run Freecell and Win32s is not installed properly: - File Error: Cannot find OLECLI.DLL -or- - Win32s - Error: Improper installation. Win32s requires WIN32S.EXE and WIN32S16.DLL to run. Reinstall Win32s. -or- - Win32s - Error: Improper installation. Windows requires w32s.386 in order to run. Reinstall Win32s. -or- - Error: Cannot find file freecell.exe (or one of its components)... Also, if Win32s is not installed properly, the display may be corrupted as soon as you run Freecell. Resolutions ----------- If Win32s is not installed correctly, check the following: - If you are having video problems, check to see if you have an S3 video card. Certain S3 drivers do not work with Win32s. Either use the generic drivers shipped with Windows, or contact your video card manufacturer for an updated driver. - Make sure that the following line is in your SYSTEM.INI file: device=*vmcpd - If you have a printer driver by LaserMaster, remove it or comment it out. (It interferes with installing Win32s.) Reboot the computer so that the changes you made take effect. After you successfully reinstall Win32s, reinstall the driver or remove the comment characters. The driver interferes with installing Win32s because the LaserMaster drivers create a WINSPOOL device. The extension is ignored when the filename portion of a path matches a device name. As a result, when Setup tries to write to WINSPOOL.DRV, it fails because it attempts to write to WINSPOOL. In fact, any Win32-based application that tries to link to WINSPOOL.DRV also fails; however, most Win32-based applications that print under Win32s do not use the WINSPOOL application programming interfaces (APIs) because they are not supported in Win32s. As a result, you can usually disable this driver while installing Win32s and then re-enable it afterwards. - Delete the WIN32S directory, the WIN32APP directory, and the W32SYS.DLL, W32S16.DLL, and WIN32S.EXE files from your hard disk. Edit the WIN32S.INI file on your hard disk. Change the line(s) SETUP=1 to read SETUP=0. Reboot your computer and reinstall Win32s. Although it is possible to install Win32s over an old installation of Win32s, it is recommended that you remove the old files before installing the new ones. - Make sure that paging is enabled. From the Control Panel, choose the 386 Enhanced icon, choose Virtual Memory, then choose Change. Verify that the drive type is not set to None. - Make sure that SHARE is enabled. Edit the AUTOEXEC.BAT file and add the following line if it is not already there: C:\DOS\SHARE.EXE -or- If you are running Windows for Workgroups or you have a file by the name VSHARE.386 on your system, you do not need to load SHARE in the AUTOEXEC.BAT file. If you have this file, edit the SYSTEM.INI file and add the following line to the [386Enh] section: Device=VSHARE.386 Network Installation of Win32s ------------------------------ The following information describes how to install Win32s on a network setup of Windows on a Novell NetWare server (SETUP /A and /N). To set up Win32s to a shared Windows directory on a Novell NetWare server, you must have full read/write access to that directory. Win32s does set up correctly the first time. The Setup program detects the shared directory (SETUP /A) as the Windows directory and copies the files to it. Setup also modifies the .INI files for the copy of Windows from which you are performing Setup. For all other installations, the SYSTEM.INI files must be modified manually; otherwise, the full setup program tries to run again and attempts to write the files to the server directory again. Add the following lines to each SYSTEM.INI file: [Boot] drivers=F:\\winmm16.dll NOTE: The drivers= line may contain additional drivers. [386Enh] device=F:\\win32s\w32s.386. Both lines should contain the full network path to the files in the shared Windows directory. The Win32s Setup program installs the Win32s directory, which is ordinarily created in the Windows SYSTEM subdirectory, into the shared Windows directory. KBCategory: kbpolicy kbdisplay kbinterop kberrmsg KBSubcategory: win31 wfw wfwg Additional reference words: 3.10 3.11 win32 Troubleshooting At Work PC Fax in WFWG 3.11 Article ID: Q122032 ---------------------------------------------------------------- -- The information in this article applies to: - Microsoft Windows for Workgroups version 3.11 ---------------------------------------------------------------- -- SUMMARY ======= This article contains a step-by-step guide to troubleshooting Microsoft At Work PC Fax in Microsoft Windows for Workgroups 3.11. Additional information about At Work PC Fax is available in the following sources: - Windows for Workgroups 3.11 Resource Kit, Chapters 4 and 10 - Help (available in the Fax area of Control Panel) - Additional articles in the Microsoft Knowledge Base. You can have access to the Microsoft Knowledge Base through the following services: - CompuServe (GO MSKB and search on the keyword AWFAX) - America Online (search on AWFAX in the Microsoft area) - Microsoft TechNet CD - The Internet - Microsoft FastTips at (800) 936-4200 (Only a selected number of Knowledge Base articles are available on the FastTips service.) MORE INFORMATION ================ With Microsoft At Work PC Fax, you can send and receive faxes through your fax modem. At Work PC Fax works through the Windows for Workgroups Mail interface. (However, you do not have to be using Mail in order to use At Work PC Fax.) To send a fax, compose a message in Mail, then place the fax number on the To line of the Mail message using the following formats: [fax:1234567] -or- [fax:name@1234567] Finally, choose Send. You can attach files (for example, bitmaps, documents, or spreadsheets) in the message and fax these documents all from within Mail. In addition, you have the option of printing to the At Work PC Fax printer driver from within a Windows-based application. If the sending and receiving fax modems are both Class 1 compatible, you can send binary files through At Work PC Fax. Note that if either fax modem is not Class 1 compatible, the transmission is in a non-editable facsimile format (as if you were sending from a fax machine.) At Work PC Fax Setup -------------------- To set up At Work PC Fax, open Control Panel and double-click the Fax icon. The first time you set up At Work PC Fax, you are prompted with a dialog box for "Email and Fax" or "Fax Only." If you are on a network and use Microsoft Mail in Windows for Workgroups, choose "Email and Fax." If you do not use Mail (that is, if you are on a stand-alone system or just do not use Mail), choose "Fax Only." After making this selection, select the appropriate settings for your fax modem. There should then be a short delay, during which your EFAXPUMP.INI file is being created, and then you should be prompted for your fax number. Enter this information. (The country code for the USA is "1"). If you receive the following message A modem was not detected on the selected port. Do you wish to install anyway? Choose No. Make sure that you have selected the correct port and that your fax modem is on (if it is an external modem). If the fax modem is properly detected, you are prompted to run Microsoft Mail if you are not already doing so. Sign into Mail. This create a new MSMAIL.MMF file. (This is the file that holds mail or fax messages.) You should now see a Fax icon that is "idle." (Minimize everything on your screen if you have difficulty finding the icon.) The Fax icon indicates that you are properly set up and ready to use the faxing capability. (See the "At Work PC Fax Usage" section below.) Setting Up a Shared Network Fax ------------------------------- After you have At Work PC Fax set up on one machine, you can then share this fax modem with other members of the network. (NOTE: You are actually sharing a directory, not the fax modem itself.) The machine with the fax modem in it can be considered the fax server. Other members of the network can then fax from their own machines using this shared fax modem. Incoming faxes are received at the server, where they can either be manually routed to others on the network, or placed in a shared folder in Microsoft Mail. From the shared folder, others can access the faxes. Faxes are NOT automatically routed to the intended recipients--they are received by the fax server only. To set up your shared fax modem: 1. Set up and test the machine with the fax modem installed. 2. On the fax server, open Control Panel, double-click the Fax icon, and choose Shared Network Fax. 3. Choose Create Directory. 4. Choose Create Share and change the access type to Full. To set up a Windows for Workgroups 3.11 workstation to use a remote fax modem: 1. Open Control Panel and double-click the Fax icon. 2. Select Fax Only if you are not using Microsoft Mail; select Email And Fax if you want to use At Work PC Fax and Microsoft Mail. (You receive this message the first time you open the Fax icon only.) 3. Choose Add. 4. Select Shared Network Fax. 5. Choose the Network button. 6. In the Path box, type the location of the fax server using the following format: \\\ NOTE: The default is MSFAX. 7. Choose OK. 8. Select the connection you have just established and choose OK. If you have more than one connection to shared fax modems, you can set one as the active modem. (If there is only one connection to a shared fax modem, this is not an option.) 9. Start and sign in to Microsoft Mail. 10. Assuming the fax server is running Mail and the Fax icon is on the desktop, the workstation should also start up At Work PC Fax. NOTE: When the server goes down or the fax modem goes offline, users connected to that shared fax modem cannot actually send faxes. However, even when the fax modem is offline, you can create faxes and choose Send--they will be transmitted when the fax modem is back online. At Work PC Fax Usage -------------------- To use At Work PC Fax, you must have Microsoft Mail running and the fax modem online. (On the Fax/Mode menu, the Work Off-Line option must not have a check mark beside it.) If you are attaching to a shared fax modem, both the fax server and the workstation must be running Microsoft Mail, and the fax modem must be online. To send a fax, use one of the following methods. Method #1 - Faxing from Mail: 1. Open Microsoft Mail and make sure your fax modem is online. (The Fax icon appears on the desktop.) 2. In Mail, choose Compose. Type the body of the mail message, or choose Attach and attach any files you want to fax. NOTE: If you attach a file, it must be a printable document with an extension that Windows for Workgroups recognizes unless you are sending a binary file, in which case any file can be sent. (Class 1 fax modems must be available on both ends if you are transferring a binary file.) 3. On the To: line, type one of the following formats: [fax:1234567] -or- [fax:John@1234567] 4. Choose Send. 5. From the View menu, choose New Messages. Method #2 - Printing from within an application to the At Work PC Fax printer driver (Microsoft At Work Fax on Fax): 1. In your Windows-based application, choose Print from the File menu. Print with the "Microsoft At Work PC Fax on Fax" printer driver. Microsoft Mail starts. Sign in if necessary. 2. You are prompted with the Compose dialog box. 3. On the To: line, use one of the following formats: [FAX:1234567] -or- [FAX:John@1234567] 4. Choose Send. At Work PC Fax Initial Troubleshooting -------------------------------------- If you are having any difficulty with At Work PC Fax installation or usage, set up your configuration as outlined below for testing. This "clean" configuration helps to narrow down possible software conflicts and ensure that the fax modem itself is working properly. 1. Restart your machine with the following clean configuration: CONFIG.SYS ---------- DEVICE=C:\WFWG\HIMEM.SYS SHELL=C:\DOS\COMMAND.COM /P DEVICE=C:\WFWG\IFSHLP.SYS (disk-compression drivers if needed) (SCSI driver if needed) AUTOEXEC.BAT ------------ C:\WFWG\NET START PATH=C:\DOS;C:\WFWG PROMPT $P$G SET TEMP=C:\TEMP 2. Change to the standard VGA video driver as follows: a. Exit Windows. b. From your Windows for Workgroups directory, type "setup" (without the quotation marks). c. Change the Display Type to VGA. Replace the files when prompted if the driver already exists on your hard disk. 3. Modify the following entries in the SYSTEM.INI file to match the values listed below. [boot] system.drv=system.drv shell=progman.exe comm.drv=comm.drv display.drv=vga.drv 4. Remark out the Load= and Run= lines in the [windows] section of your WIN.INI. (You can remark out an existing entry by placing a semicolon (;) at the beginning of that line.) 5. Remove any programs that are loading in your StartUp group. 6. Check to make sure you have the correct Windows for Workgroups communications driver. In your Windows SYSTEM subdirectory, check the file attributes of COMM.DRV. The file should be dated 11/1/93. The file size should be 5968 bytes. If it is not, rename the current COMM.DRV and expand the correct one from the original Windows for Workgroups Disk #2. To do this, type the following from an MS-DOS command prompt expand :\comm.dr_ :\windows\system\comm.drv where is the floppy disk drive containing Windows for Workgroups Disk #2 and is your drive containing Windows. 7. Determine whether the fax modem works at the MS-DOS command prompt by exiting Windows for Workgroups and typing the following command echo atdt5555555 > com where is the number of the communications (COM) port. If you do not hear a dial tone, the fax modem may need to be reconfigured for the correct port address and interrupt. Also, if you have an external fax modem, check the serial cable to ensure a good connection and that the proper cable is being used. If you have an internal fax modem, check to ensure that the hardware configuration is correct. Refer to the fax modem documentation for setup and technical support information. 8. Determine whether the fax modem works in Windows Terminal as follows: In the Accessories group, open Terminal and type the command "atdt" (without the quotation marks). - If the correct COM port is selected for the fax modem, you should hear a dial tone and "OK" or zero (0) should be returned to the terminal screen. Pressing ENTER should cancel the command to the fax modem and the message "NO CARRIER" should be returned to the screen. - If you do not hear a dial tone after the ATDT command, choose Communications from the Settings menu to make sure the correct COM port setting is selected. - If you do not see the text echoed back to the screen as you type the command, choose Terminal Preferences from the Settings menu and select the Local Echo option under Terminal Modes. If the fax modem does not work in Terminal, the modem may not be correctly configured for Windows. Gathering Information About Your Fax Modem ------------------------------------------ By entering Terminal and typing some commands, you can gather information about your fax modem. The following information can be helpful should you need to contact Microsoft Product Support Services: - The fax modem manufacturer and model. - The class of the fax modem. The class can be 1, 2, 2.0, or CAS. At Work PC Fax works with all but Class 2.0 fax modems. Some fax modems are both Class 1 and Class 2 compatible. To determine the class of fax modem, type the following command in Terminal: at+fclass=? This should return "0,1" or "0,2" or "0,1,2". This value indicates your fax modem is Class 1, Class 2, or both Class 1 and 2 compatible, respectively. - For information about the BIOS of the fax modem, type the following command in Terminal: ati where is a number 1-9. KBCategory: kbusage kbdisplay kbatwork kbhw kbtshoot KBSubcategory: wfw wincomm awfax wfwg Additional reference words: 3.11 tshoot Superguide Extended Error Code Information Article ID: Q74463 ---------------------------------------------------------------- ---- The information in this article applies to: - Microsoft MS-DOS operating system versions 3.x, 4.x, 5.0, 6.0, 6.2, 6.21, 6.22 ---------------------------------------------------------------- ---- SUMMARY ======= The following MS-DOS function provides detailed extended error information concerning a failed Interrupt 21H function call: Interrupt 21H Function 59H - Get Extended Error Information This routine returns codes named as the DOS extended error code, error class, recommended action, and error locus. - The extended error code identifies exactly what occurred. - The error class provides more information identifying the error based on the internal workings of the operating system. - The recommended action codes are suggestions meant to help but are not solutions. - The error locus codes attempt to provide information about the origin of the error or what device caused the error. MORE INFORMATION ================ The MS-DOS function returns the four codes in the following registers: AX Extended error code BH Error class BL Recommended action CH Error locus Extended Error Codes -------------------- Hex Decimal Meaning --- ------- ------- 01 01 Function number invalid 02 02 File not found 03 03 Path not found 04 04 Too many open files 05 05 Access denied 06 06 Handle invalid 07 07 Memory control blocks destroyed 08 08 Insufficient memory 09 09 Memory block address invalid 0A 10 Environment invalid 0B 11 Format invalid 0C 12 Access code invalid 0D 13 Data invalid 0E 14 Unknown unit 0F 15 Disk drive invalid 10 16 Attempted to remove current directory 11 17 Not same device 12 18 No more files 13 19 Write-protected disk 14 20 Unknown unit 15 21 Drive not ready 16 22 Unknown command 17 23 Data error (CRC) 18 24 Bad request-structure length 19 25 Seek error 1A 26 Unknown media type 1B 27 Sector not found 1C 28 Printer out of paper 1D 29 Write fault 1E 30 Read fault 1F 31 General failure 20 32 Sharing violation 21 33 File-lock violation 22 34 Disk change invalid 23 35 FCB unavailable 24 36 Sharing buffer exceeded 25-31 37-49 Reserved 32 50 Unsupported network request 33 51 Remote machine not listening 34 52 Duplicate name on network 35 53 Network name not found 36 54 Network busy 37 55 Device no longer exists on network 38 56 NetBIOS command limit exceeded 39 57 Error in network adapter hardware 3A 58 Incorrect response from network 3B 59 Unexpected network error 3C 60 Remote adapter incompatible 3D 61 Printer queue full 3E 62 Not enough room for print file 3F 63 Print file was deleted 40 64 Network name deleted 41 65 Network access denied 42 66 Incorrect network device type 43 67 Network name not found 44 68 Network name limit exceeded 45 69 NetBIOS session limit exceeded 46 70 Temporary pause 47 71 Network request not accepted 48 72 Print or disk redirection paused 49-4F 73-79 Reserved 50 80 File already exists 51 81 Reserved 52 82 Cannot make directory 53 83 Fail on Int 24H (critical error handler) 54 84 Too many redirections 55 85 Duplicate redirection 56 86 Invalid password 57 87 Invalid parameter 58 88 Net write fault Error Class Codes ----------------- Class Meaning ----- ------- 1 Out of resource 2 Temporary situation 3 Authorization 4 Internal 5 Hardware failure 6 System failure 7 Application program error 8 Not found 9 Bad format 10 Locked 11 Media 12 Already exist 13 Unknown Recommended Action Codes ------------------------ 1 Retry. If not cleared in reasonable number of attempts, prompt user to Abort or Ignore. 2 Delay then retry. If not cleared in reasonable number of attempts, prompt user to Abort or Ignore. 3 Get corrected information from user (bad filename or disk drive). 4 Abort application with cleanup. 5 Abort application without cleanup (cleanup may increase problems). 6 Ignore error. 7 Prompt user to correct error and then retry. Error Locus Codes ----------------- 1 Unknown 2 Block device (disk or disk emulator) 3 Network 4 Serial device 5 Memory related An application program may use the MS-DOS Interrupt 21H Function 59H call when a function call fails during the execution of the application. The program may take a number of possible different actions as a result, which could include retrying the function, aborting, or just displaying the DOS extended error code. For example, an application might display the following after a failed interrupt call: DOS extended error 27 /11 /4 /2 This represents: Extended error 27 Sector not found Error class 11 Media Recommended action 4 Abort application with cleanup Error locus 2 Block device (disk or disk emulator) KBCategory: kbhw kbdisplay kberrmsg KBSubcategory: msdos Additional reference words: 6.22 3.20 3.21 3.30 3.30a 4.00 4.01 5.00 6.00 6.20 EMM386 Troubleshooting and Technical Information Article ID: Q78557 ---------------------------------------------------------------- ---- The information in this article applies to: - Microsoft MS-DOS operating system versions 5.x, 6.0, 6.2, 6.21, 6.22 - Microsoft Windows operating system versions 3.1, 3.11 - Microsoft Windows for Workgroups versions 3.10, 3.11 ---------------------------------------------------------------- ---- SUMMARY ======= The following topics are discussed in this article: - Troubleshooting steps to use if EMM386.EXE locks up the machine - How EMM386.EXE locates UMBs and the EMS page frame: UMA scanning algorithm EMM386 and the E000 segment - Common EMS questions concerning the following: - "WARNING: Unable to set page frame base address--EMS unavailable" message - "Size of expanded memory pool adjusted" message - EMM386.EXE and Windows - EMM386.EXE version history NOTE: This information applies to the versions of EMM386.EXE included with MS-DOS, Microsoft Windows, and Microsoft Windows for Workgroups. MORE INFORMATION ================ IF EMM386.EXE LOCKS UP THE COMPUTER =================================== If EMM386.EXE locks up the computer, follow these troubleshooting steps: 1. If the DEVICE=EMM386.EXE in the CONFIG.SYS file contains the HIGHSCAN parameter, remove HIGHSCAN from the command, save the CONFIG.SYS file, and restart your computer. (HIGHSCAN cannot be used on some computers.) 2. Start EMM386.EXE with the exclude option. EMM386.EXE may have incorrectly identified an area being used by the system as a "hole" (a region that can be used as a UMB or an EMS page frame). As a result, EMM386.EXE overwrites a portion of memory that is used by a hardware adapter in your computer. By excluding addresses in the range A000-EFFF, EMM386.EXE does not use any part of the excluded region for a UMB or EMS page frame. Identifying the correct region(s) to exclude requires experimentation. Start by excluding a large region and then reducing the size of the region. For example: DEVICE=EMM386.EXE NOEMS X=A000-EFFF DEVICE=EMM386.EXE NOEMS X=C000-DFFF DEVICE=EMM386.EXE NOEMS X=C800-CFFF You can use multiple exclusions on the EMM386.EXE device line. For example: DEVICE=EMM386.EXE NOEMS X=C000-C7FF X=E000-EFFF Refer to the documentation included with your hardware device(s) for information on the upper memory addresses the adapter card uses. Examples of devices that use upper memory addresses include network cards, SCSI adapters, video cards, and scanners. 3. If your computer has a SCSI disk controller and requires a device driver for the SCSI adapter, be sure the DEVICE= line for the SCSI driver appears before the DEVICE=EMM386.EXE line. Examples of SCSI device drivers include ASPI4DOS.SYS and USPI14.SYS. 4. If you are experiencing problems with the computer hanging, try loading the SMARTDrive double buffer driver. NOTE: The SMARTDrive double buffer driver line should appear before the DEVICE=EMM386.EXE line in the CONFIG.SYS file. MS-DOS 6.0 or later, Windows 3.1 or later, or Windows for Workgroups -------------------------------------------------------------------- If you use MS-DOS 6.0 or later, Microsoft Windows 3.1 or later, or Microsoft Windows for Workgroups the SMARTDrive double buffer driver is loaded from the CONFIG.SYS file as follows: device=c:\windows\smartdrv.exe /double_buffer In the AUTOEXEC.BAT file, add a /L to the end of the SMARTDRV.EXE line. For example: c:\windows\smartdrv.exe /L If the problems persist, add a plus sign (+) to the end of the double buffer device line as follows: device=c:\windows\smartdrv.exe /double_buffer+ MS-DOS 5.x ---------- If you use the SMARTDRV.SYS driver included with MS-DOS 5.x the SMARTDrive double buffer driver is loaded in the CONFIG.SYS as follows: device=c:\dos\smartdrv.sys /b+ 5. Experiment with different HIMEM.SYS A20 handlers. This is done using the /MACHINE: switch on the HIMEM.SYS device line. For information on the HIMEM.SYS /MACHINE: switch and troubleshooting A20 handler problems: - Consult your MS-DOS, Windows, or Windows for Workgroups documentation -or- - Query on the following words in the Microsoft Knowledge Base: tshoot and himem.sys and control and a20 line HOW EMM386.EXE LOCATES UMBs AND THE EMS PAGE FRAME ================================================== UMA Scanning Algorithm ---------------------- By default EMM386.EXE scans the following UMA region: MS-DOS 5.0: C800-DFFF Windows 3.1, Windows for Workgroups 3.1: C600-DFFF MS-DOS 6.0 and later, Windows for Workgroups 3.11 and later: C000-EFFF NOTES: The E000-EFFF region is handled differently on certain hardware (see the following section). Under MS-DOS 6.0 and later and Windows for Workgroups 3.11, the F000-F7FF range can be included by using the HIGHSCAN switch. EMM386.EXE and the E000 Segment ------------------------------- On Compaq machines, the E000 segment has either shadow RAM or the segment is unused. For shadow RAM, the shadow area is reclaimed by EMM386.EXE if the Int 10 vector has not been hooked before EMM386.EXE loads. This is because the shadow region contains a remapped copy of the video ROM from the C000 region. EMM368.EXE excludes E000 on MCA machines (IBM PS/2s) since the E000 segment has the system ROM. On other machines, E000 may be excluded by default. If you think the E000 range is available, you can explicitly include the E000 segment by adding I=E000-EFFF to the DEVICE=EMM386.EXE command in the CONFIG.SYS file. NOTE: When EMM386.EXE encounters the include switch, it includes the region without scanning it for potential conflicts. COMMON EMS ISSUES ================= WARNING: Unable to Set Page Frame Base Address--EMS Unavailable --------------------------------------------------------------- This error is displayed if EMM386.EXE cannot locate a 64K contiguous "hole" in the UMA for the EMS page frame. According to the LIM 3.2 specification, a page frame consists of four contiguous 16K pages, and a LIM provider must set the page frame. According to the LIM 4.0 specification, an EMS provider need not set a 64K page frame, but it should set a 16K page at the minimum. Although EMM386.EXE conforms to the LIM 4.0 specification, it does not load as an EMS provider if it does not find a 64K contiguous hole that can be used for the page frame. This is because the majority of LIM 3.2 applications assume the existence of a page frame. EMM386.EXE can be forced to load without a LIM 3.2 (64K) page frame by using the Pn parameters. If you force EMM386.EXE to load as a LIM 4.0 provider, do not attempt to run LIM 3.2 applications. Consult with your application vendor to determine the required LIM version. NOTE: If you require a LIM 3.2 (64K) page frame, it may be necessary to modify the settings on your hardware devices to free a contiguous, 64K region in the UMA. Size of Expanded Memory Pool Adjusted ------------------------------------- This error message is displayed if EMM386.EXE cannot provide all the EMS memory requested on the command line. For example, if you use the DEVICE=EMM386.EXE 2048 and your computer only has 1024K of XMS memory, EMM386.EXE displays this error message and provides as much EMS as possible. (Note that EMM386.EXE uses some XMS memory for its own code and data, and this reduces the amount of XMS memory available for EMS.) Windows Cannot Provide EMS with the NOEMS Switch ------------------------------------------------ According to the LIM 4.0 specification, an EMS page can also reside in conventional memory (0-640K). The EMM386 EMS line starts at 256K by default. If the NOEMS option is specified, all the holes in the adapter region A000-FFFF are used for UMBs, and EMM386.EXE does not provide any EMS. Once Windows 3.0 is started and an MS-DOS session is started, EMM386.EXE may or may not be able to provide EMS. If Windows is running in 386 enhanced mode, EMM386.EXE can provide EMS in an MS-DOS session; however, the EMS pages are in conventional memory. This can cause problems because of the behavior of LIM 3.2 applications as described above. In a Windows 3.1 386 enhanced mode MS-DOS session, EMS is not provided. EMM386.EXE VERSION HISTORY ========================== MS-DOS 5.0 4.20 MS-DOS 5.00a 4.33 MS-DOS 6.0 4.45 MS-DOS 6.2 4.48 MS-DOS 6.21 4.48 MS-DOS 6.22 4.49 Windows 3.1 4.44 Windows 3.11 4.44 Windows for Workgroups 3.1 4.44 Windows for Workgroups 3.11 4.48 Some of the products included here are manufactured by vendors independent of Microsoft; we make no warranty, implied or otherwise, regarding the performance or reliability of these products. KBCategory: kb3rdparty kbdisplay kbtshoot kbtlc KBSubcategory: msdos wfwg wfw win31 Additional reference words: 6.22 5.00 5.00a 6.00 6.20 3.10 tshoot 3rdparty freeze stop lock conflict Windows 3.1 Setup Error Codes (S208 through S214) Article ID: Q82771 ---------------------------------------------------------------- The information in this article applies to: - Microsoft Windows operating system versions 3.1, 3.11 ---------------------------------------------------------------- SUMMARY ======= When a Setup error message contains an error code, it also includes some text indicating what Setup was trying to do, for example, copying a file. The text of the error message indicates whether the error is fatal or not. In some nonfatal cases, Setup may be performing an operation (such as copying a file) that is needed to run Microsoft Windows. Other times the error may prevent some specific feature of Windows from operating properly. In many cases, the error code is an MS-DOS extended error code. These error codes are between 0 and 100. Setup-specific error codes have two different formats, depending on whether the error occurs during the character (MS- DOS) mode or the Windows graphical user interface (GUI) mode portion of Setup. The character mode Setup-specific error numbers are in the format "Snnn", where "nnn" is any three-digit number. The GUI mode error numbers are codes greater than 200. MORE INFORMATION ================ GUI Mode Setup Error Codes -------------------------- 208 Out of disk space during file copy in VerInstallFile. Because of the disk space checks that Setup does, this problem should occur only if you have upgraded over an invalid Windows installation (that is, files have been deleted manually). Make sure there is enough disk space and then run Setup again. Also make sure that VER.DLL does not exist in the WINDOWS directory. It should only be in the WINDOWS\SYSTEM directory. 209 File in use. This error occurs if some file that needs to be replaced by Setup is in use or opened by another some other software. Make sure Setup is the only application running or exit Windows and run Setup from the MS-DOS prompt. 210 Destination file is write-protected. Type ATTRIB -r at the MS-DOS prompt, where is the indicated file and run Setup again. This problem may also be caused by virus- protection software, in which case, this software should be disabled while running Setup. 211 Buffers allocated for file expansion operations are too small. This error should never occur. If it does, free up some memory and run Setup again. 212 Unknown version mismatch happened during attempt to install file. This problem can be caused by the incorrect version of VER.DLL running or by corrupt files. Make sure you do not have VER.DLL in your WINDOWS directory. It should only be in the WINDOWS\SYSTEM directory. 213 File expansion initialization failed. This problem is probably due to insufficient memory. 214 Source file is unreadable. This problem is probably due to drive hardware problems, corrupt files or disks, or, if you are setting up from a network, network problems. Setup error 214 can also be caused by incorrect CMOS settings for floppy drives or third party extended memory managers. KBCategory: kbsetup kberrmsg KBSubcategory: win31 Additional reference words: 3.10 3.11 qemm winfest Windows 3.1 Hardware Compatibility List Article ID: Q83210 ---------------------------------------------------------------- ---- The information in this article applies to: - Microsoft Windows operating system version 3.1 ---------------------------------------------------------------- ---- SUMMARY ======= The Hardware Compatibility Test (HCT) is a series of tests run from a shell within Microsoft Windows version 3.1. The tests are run in standard mode only for 80286-based systems, and in both standard and 386 enhanced mode for 80386- or 80486-based systems. The tests evaluate such things as: - Memory-resident programs - Screen display - Interpretation of keystrokes and mouse actions - Performance of selected tasks within Windows File Manager and Windows Print Manager The HCT includes additional tests for computers with math coprocessors and multimedia capabilities. If the results of the HCT show that the system has satisfactorily passed compatibility requirements, the system may be added to the Windows HCL and can display the Windows Compatible logo. The following computers, displays, printers, networks, pointing devices and keyboards have been certified for use with Microsoft Windows version 3.1. This list was current at the time it was published (4/92). Additional systems may have been certified subsequent to publication and may not be listed below. MORE INFORMATION ================ Computers Compatible with Windows Version 3.1 --------------------------------------------- :3C! PRO 3 :3C! PRO4 :3C! Slim 386 C :3C! Slim 386 X :3C! Slim 486 C :3C! Slim 486 X Acer 1100/33 Acer 1120SX Acer 1125E AcerAnyware 386S AcerFrame 3000SP AcerMate 386/33 AcerPower 386SX AcerPower 486/33 AcerPower 486SX AcerPower 500/20 AcerPower 500/33 Acros 340 Acros 400 Acros 525 Acros 615 Acros 620 Acros 723 Add-X AS 316sx Add-X AS 320sx Add-X AS 450 ADLER ROYAL P45 AEG Olystar 70 H20V Alcatel 701/33 Alcatel 701/33 Alcatel 7100/33 Alcatel 7100/33 Alcatel 801/20 Alcatel 801/20 Alcatel 8100/20 Alcatel 8100/20 Alcatel 8551 Alcatel 8551 Alcatel 901/33 Alcatel 901/33 Alcatel 9300/33 Alcatel 9300/33 Alcatel APC 701/33 Alcatel APC 7100/33 Alcatel APC 801/20 Alcatel APC 8100/20 Alcatel APC 8551 Alcatel APC 901/33 Alcatel APC 9300/33 ALIF 386DX25 ti ALIF 386DX33/64c ti ALIF 386SX16 ti ALIF 433DX128 ti ALR Business STATION 386/33 ALR Business STATION 486/33 ALR Business STATION 486/50 ALR Business STATION 486ASX/20 ALR Business STATION 486SX/20 ALR BusinessVEISA 386/33 ALR BusinessVEISA 486/33 ALR BusinessVEISA 486/50 ALR MPS 386/33 ALR MPS 486/33 ALR MPS 486/50 ALR MPS 486ASX/20 ALR PowerFlex 386SX/16 ALR PowerFlex 386SX/20 ALR PowerFlex 486ASX/20 ALR PowerFlex 486DX/25 ALR PowerFlex Flyer ALR PowerFlex Flyer 386SX/25 ALR PowerFlex Flyer 486SX/20 ALR PowerPRO VM 386/33 ALR PowerPRO VM 486/33 ALR PowerPRO VM 486/50 ALR PowerPRO VM 486ASX/20 ALR VIP 386SL/25 Notebook ALR VIP M 386SX/20 Notebook ALR VIP M 486SX/20 Notebook Amkly 386/25E Amkly 386/33E Amkly 486/25E Amkly 486/33E Amkly Station 386SX/20 Amkly Station 486/33 Amkly Station 486SX/20 Amkly Station 486SX/25 Amstrad PC-5286HD40 Apricot FTs Apricot FTs 386-25 Apricot LS 386SX-20 Apricot XEN-LS 386SX 16M Apricot XEN-LS 386SX-20 Apricot XEN-LS 486SX 20 MHz ARES 486-33 ASEM DS 286 16 ASEM DS 386E-20 ASEM SP 486E ASI 386DX-25 ASI 386DX-33 ASI 386SX-16 ASI 386SX-20 ASI 486DX-33 ISA ASI 486SX-20 AST Advantage! 386SX/20 AST Advantage! 486SX/20 AST Advantage! 486SX/25 AST Bravo 3/25S AST Bravo 386SX/20 AST Bravo 486/25 AST Bravo 486/33 AST Premium 386/33 AST Premium 386SX/16 AST Premium 486/33 AST Premium Exec 386SX/20 AST Premium Exec 386SX/25 AST Premium Exec 386SX/25 Color AST Premium II 386/25 AST Premium II 386/33 AST Premium II 386SX/20 AST Premium II 486/33 AST Premium II 486SX/20 Astrix 486/33 Complete AT&T 6386/25 WGS AT&T 6386E WGS Austin 386/25VL Winstation Austin 386/33 Multi-Media Austin 386/33 Multi-Media Winstation Austin 386/33 Winstation Austin 386/33-40VL Winstation Austin 386/40 Winstation Austin 386/SX16-20VL Winstation Austin 386SX (16/20/25) Winstation Austin 486/33E Wintower Austin 486/33I Winstation Austin 486/33VLI Winstation Austin Bell PAT48PX-433c/256 KB Cache Beaver Avanti 025 Brett 386DX-25 Brett 386DX-33/64K Cache Brett 386SX-16 Brett 386SX-20 Brett 386SX-25 Brett 486DX-33:256K Cache Brett 486SX-20 Brother BCN3386DX/33C Brother BCN5486SX Canon HS-20H Canon US-20Y Chicony NB5500SXL Chicony NB6600SL Chips MK38600DX Chips MK38605DX Commodore C286-12 Commodore C286-16 Commodore C286-LT Commodore C386-25 Commodore C386-25C Commodore C386SX-16 Commodore C386SX-20 Commodore C386SX-20C Commodore C386SX-LT Commodore C486-25C Commodore C486-33C Commodore C486SX-20 Commodore PC 60-III Commodore PC 70-III Commodore T386-25C Commodore T486-25C COMPAQ DESKPRO 286 COMPAQ DESKPRO 286e COMPAQ DESKPRO 386 COMPAQ DESKPRO 386/20 COMPAQ DESKPRO 386/20e COMPAQ DESKPRO 386/25 COMPAQ DESKPRO 386/25e COMPAQ DESKPRO 386/25M COMPAQ DESKPRO 386/33 COMPAQ DESKPRO 386/33L COMPAQ DESKPRO 386N COMPAQ DESKPRO 386s COMPAQ DESKPRO 386s/20 COMPAQ DESKPRO 386s/20N COMPAQ DESKPRO 486/25 COMPAQ DESKPRO 486/33L COMPAQ DESKPRO 486/33M COMPAQ DESKPRO 486/50L COMPAQ DESKPRO 486s/16M COMPAQ DESKPRO 486s/25M COMPAQ LTE 386/20 COMPAQ LTE 386s/20 COMPAQ LTE Lite 20 COMPAQ LTE Lite 25 COMPAQ PORTABLE 386 COMPAQ PORTABLE 486c COMPAQ PORTABLE II COMPAQ PORTABLE III COMPAQ SLT 286 COMPAQ SLT 386/20 COMPAQ SYSTEMPRO 386/33 COMPAQ SYSTEMPRO 486/33 COMPAQ SYSTEMPRO/LT 386/25 COMPAQ SYSTEMPRO/LT 486/33 COMPAQ SYSTEMPRO/LT 486SX/25 CompuAdd 316s CompuAdd 320SC CompuAdd 325LP CompuAdd 325SC CompuAdd 333 CompuAdd 333LP CompuAdd 420S CompuAdd 425 CompuAdd 433E CompuAdd 433I Compudyne 286/12 Compudyne 3DN/25 Compudyne 3DX/25 Compudyne 3DX/33 Compudyne 3SX/16 Compudyne 3SX/16HM Compudyne 3SX/20 Compudyne 3SX/20HM Compudyne 4DX/33 Compudyne 4DX/33 Y Compudyne 4DX/33LB Compudyne 4DX/33LBTMC Compudyne 4SX/20 Cube 386 ATX Series Cube 486 ATX Series Cumulus GLC 386DX-25 with cache Cumulus GLC 386DX-25 without cache Cumulus GLC 386DX-33 with cache Cumulus GLC 386SX-16 with cache Cumulus GLC 386SX-16 without cache Cumulus GLC 386SX-20 with cache Cumulus GLC 386SX-20 without cache Cumulus GLC 486DX-25 with cache Cumulus GLC 486DX-25 without cache Cumulus GLC 486DX-33 with cache Cumulus GLC 486DX-33 without cache Cumulus GLC 486SX-20 with cache Cumulus GLC 486SX-20 without cache Cumulus GLC 487SX-20 with cache Cumulus WorkBox 386/dx/25 Cumulus WorkBox 386/sx/16 Cumulus WorkBox 386/sx/20 Cumulus WorkBox 486/sx/20 Daewoo CPC-2000 DAK Industries BSR 386SX/16 Data General Dasher II-386Sx/20A Data General Dasher II-486/eeTE Data General Dasher II-486Sx/20A Data General Walkabout /320 Data I/O Club 286 Datamedia NETmate/sx20i Datamedia NETmate/sx420i Datamedia NETmate/sx425i Datapoint Svenska DPC386SX Datatech Grafika 3D Datatech Grafika 3E Digital Equipment Corporation (DEC) DECpc 316sx DECpc 320 SX Notebook DECpc 320p DECpc 333 Portable DECpc 420sx DECpc 433T DECStation 210 DECStation 212 DECStation 212lp DECStation 316 DECStation 316+ DECStation 316sx DECStation 320 DECStation 320sx DECStation 325c DECStation 425 DECStation 425c Dell PowerLine 420DE Dell PowerLine 420SE Dell PowerLine 425DE Dell PowerLine 425SE Dell PowerLine 433DE Dell PowerLine 433P Dell PowerLine 433SE Dell PowerLine 450DE Dell PowerLine 450SE Dell System 210 Dell System 310 Dell System 316 Dell System 316SX Dell System 320LT Dell System 320LX Dell System 320N Dell System 320N+ Dell System 320SX Dell System 325 Dell System 325D Dell System 325P Dell System 333D Dell System 333P Dell System 486D/20 Dell System 486D/25 Dell System 486D/33 Dell System 486P/16 Dell System 486P/20 Dell System 486P/25 Dell System 486P/33 Donatec 486DX33 Cache DTK PEM-4001 80386-40 w/cache DTK PKM-3330Y 80486-33 w/cache Elonex PC 325XB Elonex PC-325XM Elonex PC-333B Elonex PC-333M Elonex PC-420SXB Elonex PC-420SXM Elonex PC-450B Elonex PC-450M Eltech Research PCdel 4200 486SX/20 Eltech Research PCdel 4300 486/33 Eltech Research PCdel 9970 386/33 Epson EISA Series 486/33 Epson EISA Series 486/50 Epson EISA Series 486SX/25 Epson EL Plus Epson EL2 Plus Epson EL3/33 Epson EL3/33 Epson EL3s Plus Epson EL4s Plus Epson Equity 320SX Plus Epson Equity 386/20 Epson Equity 386/25 Epson Equity 386/25 Plus Epson Equity 386/33 Plus Epson Equity 386SX Epson Equity 386SX Plus Epson Equity 386SX/16 (diskless) Epson Equity 386SX/20 Plus Epson Equity 486SX/25 Plus Epson Express Station Epson NB-SL/20 Epson NB-SL/25 Epson NB-SL/25C Epson NB3s (UK) Epson NB3s (USA) Ergo Electronics Macro-3/40 Ergo Electronics Macro-4/33 Ergo Electronics Macro-4X/20 Ergo Electronics Microtower-3/25 Ergo Electronics Microtower-3/40 Ergo Electronics Minipro-3/25 Ergo Electronics System-3/40 Everex AGI 386/33 EV-1851 Everex AGI 486/33 EV-18134 Everex Step 386/20 EV-1816 Everex Step 386/25 EV-1816 Everex Step 386/33 EV-18108 Everex Step 486/33 EV-18113 12-slot EISA Everex Step 486/33 EV-1878 Everex Step 486/33 EV-8038 Everex Step 486sx/20 EV-18108+EV-18116 Everex Step Server 386/33 EV-18108 Everex Tempo 286/16 EV-1824 Everex Tempo 386/25 EV-1869 Everex Tempo Modular 386/25 Everex Tempo Modular 386/33 Everex Tempo Modular 486sx/25 Everex Tempo-C 286/16 EV 18122 Everex Tempo-C 386/33 EV-18103 Everex Tempo-C 386SX/20 EV-8048 Everex Tempo-C 386sx/20 EV18121 Everex Tempo-C 486sx/20 EV 18103 Flytech Carry-1 80386SX Flytech Carry-1 80386SX Flytech Carry-1 FT-5320 Fujitsu MY320 Fujitsu MY333 Fujitsu MY420 Fujitsu S-420 Fujitsu S-4863 Future AT 386DX-40 Future AT 386SX-20 Future AT 486 EISA 33 Future AT 486DX-33 Future AT 486SX-20 G2 HL 386/33C G2 SL 286/16 G2 SL 386/20 G2 SL 386/33 G2 SL 486/25 G2 SL 486/33C Gateway 2000 386-25 ISA Gateway 2000 386-33C ISA Gateway 2000 386SX-20 Gateway 2000 386SX/16 Gateway 2000 486-33 EISA Gateway 2000 486-33 ISA GRiD 1720 GRiD 1750 GRiD 1755 GRiD 286 is GRiD 286-MFP GRiD 286N GRiD 325sc GRiD 386 is-16 GRiD 386 is-20 GRiD 386 is-25 GRiD 386mc GRiD 386NX GRiD 386sx-MFP GRiD 386sx-MFP20 GRiD 486ei-25/SRV GRiD 486ei-33 GRiD ADT/425se GRiD MFP-320s GRiD MFP/420s GS 316M GS 31IE GS 31IM GS 325S GS 340D GS 386 DXH/40 GS 386 SL/20 GS 386S/16 GS 386SXM 125 GS 386SXM/16 GS 425S GS 486SX/25 GS 610 GS 725 GS Mastersport286 Hantarex Vegas 3625N Hantarex Vegas 3633 Hantarex Vegas 386 Hantarex Vegas 4620S Hantarex Vegas 4633 Hauppauge D3/33-01 Hauppauge D3/33-02 Headstart 486/20XP Headstart 486SX HERMES H 260S HERMES H 320 HERMES H 400 HERMES H 400 E HERMES H 410 HERMES WALKSTATION 386 33 HERMES WALKSTATION 386 SX HERMES WALKSTATION SX20 Hertz 386/33 Hertz 386/SX Hertz 486/33 HP Vectra 286/12 HP Vectra 386/16N HP Vectra 386/20N HP Vectra 386/25 HP Vectra 386s/20 HP Vectra 486/20 HP Vectra 486/25 HP Vectra 486/33T HP Vectra 486s/20 HP Vectra ES/12 HP Vectra QS/16 HP Vectra QS/16N HP Vectra QS/16s HP Vectra QS/20 HP Vectra RS/16 HP Vectra RS/20c HP Vectra RS/20c HP Vectra RS/25c IBM 30/286 with Snapin 386 IBM 50 with Snapin 386 IBM 60 with Snapin 386 IBM 8540 IBM 8550 IBM 8550Z IBM 8557-SX IBM 8570-486 IBM 8580 IBM AT /Inboard 386 AT IBM AT 6MHz w/Snapin 386 IBM L40SX IBM Model 25SX IBM PS/1 286 IBM PS/2 55 Note ICL CS386s ICL CX386s/25 ICL DRS M75 ICL FX486s ICL MX486 ICL NB386s Intel 300SX20 Intel 301Z Intel 302/25 Intel 386/33H Intel 401 Intel 403E Intel 403E 33MHz 486CPU EISA Intel LP386SX-20 Intel LP486/33E Intel X486E ITOS 286/12 ITOS 386SX/16 ITOS 386SX/20 ITOS 486/33 KLH 386DX-40 KLH 486DX-33 KLH 486SX Kontron IPLite Color 486/33 Kontron PIC 386DX/20 Leading Edge D3/33 Leading Edge D3/33MT Leading Edge D3/SX20c Leading Edge D4/33 Leading Edge D4/SX20 Leading Edge MT33 Leading Edge N3/SX25 Leading Technology PC Partner LX Leading Technology PC Partner QI Leading Technology PC Partner QI Leading Technology PC Partner VX Leading Technology PC Partner VX Leading Technology PC Partner XI Leading Technology PC Partner ZI Leading Technology PC Partner ZX Leading Technology PC Partner ZX Linear Dynamics 386DX-40 Linear Dynamics 486DX-33 Linear Dynamics 486SX Lodestar Computers 386-33 Lodestar Computers 386-33 System Lueski G-M340V-130-4M Lueski G-MT 433-210-4M Maxstation 486/20XP Maxstation 486SX Maxum 3020 Maxum 3133 Maxum 3140 Maxum 4133 Memorex Telex 8036 Memorex Telex 8057 Memorex Telex 8067 Memorex Telex 8080 Memorex Telex 8090 Memorex Telex 8257 Memorex Telex 8267 Memorex Telex 8280 Mind 386-25 Mind 386-33 Mind 386-40 Mind 386SX-16 Mind 386SX-25 Mind 486-25 Mind 486-33 Mind 486-33 EISA Mind 486-50 Mind 486SX-20 MInd 486SX-25 Mitac 3026E Mitac 3027F Mitac 3060D Mitac 3060F Mitac 3060G Mitac 3062E Mitac 3062F Mitac 3072F Mitac 4060F Mitac 4060G Mitac D3033 Mitac D4033 Mitac D4125 Mitsubishi MP-386 NCR System 3000 Model 3210 NCR System 3000 Model 3320 (3420) NCR System 3000 Model 3320 (3431) NCR System 3000 Model 3335 NCR System 3000 Model 3345 NEC PowerMate 286/12 NEC PowerMate 286c NEC PowerMate 386/20 NEC PowerMate 386/33E NEC PowerMate 386/33i NEC PowerMate SX/16 NEC PowerMate SX/20 NEC UltraLite 286V NEC UltraLite SL/20 Nevis SVC 486/33 Normerel Comete Normerel Hexagone Normerel Jupiter 386 Normerel Jupiter 486 Normerel Saturn 386 Normerel Saturn 486 Normerel Saturn 486DX Northgate 386SX/25 Northgate 486DX/33 Northgate EISA 486 Northgate Elegance SP Northgate Elegance ZXP Northgate Slimline SP 486DX/33 Olivetti CP 486 Olivetti CP 486/33 Olivetti Laptop D33 Olivetti Laptop S20 Olivetti LSX5010 Olivetti LSX5020 Olivetti M300-25 Olivetti M380 Olivetti M480-10 Olivetti M480-30 Olivetti M486 Olivetti Notebook S20 Olivetti Notebook V16 Olivetti P500 Olivetti P500-10 Olivetti P560 Olivetti P750 Olivetti P750-S Olivetti P800 Olivetti PC Pro 290 SP Olivetti PC Pro 486SX Olivetti PCS 386SX Opus Panther SX Opus PC 4-286/16 Opus PC 5-386 Opus PC 7/40 Opus PCSX Opus Powerstation SX Osborne 386-33 Osborne 386SX-20 Osborne 386SX-25 Osborne 486-33 EISA Packard Bell 486-33 Packard Bell 486-33DX PC 340 PC Brand 286-12 system PC Brand 386/33 Cache System PC Brand 386/SX-16 System PC Brand 386/SX-20 System PC Brand 386/SX-25 Notebook PC Brand 386sx-20 Cache System PC Brand 386SX-20 System PC Brand 386SX-20 System PC Brand 386sx-25 Cache System PC Brand 386sx-25 System PC Brand 486-33 System PC Brand 486-50 System PC Brand 486/33 EISA Cache System PC Brand 486/50 Cache System PC Brand 486/50 EISA Cache System PC Brand 486sx-20 Cache System PC Brand 486sx-20 System Philips MPC Philips PCD 215 Philips PCD 315 Philips PCL 304 Pioneer P386 C Pioneer P386 X Pioneer P486 CT Pioneer P486 X Poly 12/486-33/sf Poly 486-33E Poly 486-50V Poly 486/25sx Poly 486/33E (EISA) Positive PC-1000 286-12 Positive PC-1000 386sx-20 Positive PC-1000 386sx-20c Positive PC-1000 386sx-25 Positive PC-1000 386sx-25c Positive PC-1000 486-33 Positive PC-1000 486-50 Positive PC-1000 486sx-20c Positive PC-2000 286-12 Positive PC-2000 386sx-20 Positive PC-2000 386sx-20c Positive PC-2000 386sx-25 Positive PC-2000 386sx-25c Positive PC-2000 486-33 Positive PC-2000 486/50 Positive PC-2000 486sx-20c Positive PC-3000 386/sx-20 Positive PC-3000 386sx-25 Positive PC-3000 486/50 Positive PC-325 Positive PC-340 Precision 386sx/20 ISA Precision 486/33 ISA Premier 386DX-40 Premier 486DX-33 Premier 486SX Professional 486/20XP Professional 486SX Proj 559R QNIX Omni 386sx/20c RadiSys EPC-2 RadiSys EPC-3 RadiSys EPC-4 RadiSys EPC-5 RadiSys EPC-6 RadiSys EPC-7 RadiSys RIC 386 Reply Model 32 386/33c Reseach Machines M-Series PC 286 Reseach Machines M-Series PC 386 Research Machines Nimbus AX/2 Samsung Desk Master 386S/25N (SD740) Samsung Desk Master 486S/25 (SD923N) Sanyo MBC-17 PLUS Sanyo MBC-17LX Sanyo MBC-17NB Sanyo MBC-18NB Sanyo MBC-18PLUS Sanyo MBC-18SXMT Sanyo MBC-27MT Seanix ASI 9000 (386DX) Seanix ASI 9000 (386SX) Seanix ASI 9000 (486DX) Siemens Nixdorf 8810 /30 Siemens Nixdorf 8810 /50 Siemens Nixdorf PCD-2B Siemens Nixdorf PCD-2M Siemens Nixdorf PCD-2N Siemens Nixdorf PCD-3Bsx Siemens Nixdorf PCD-3M Siemens Nixdorf PCD-3Msx Siemens Nixdorf PCD-3Nsl Siemens Nixdorf PCD-3Nsx/16 Siemens Nixdorf PCD-3Nsx/20 Siemens Nixdorf PCD-3Rsx Siemens Nixdorf PCD-3T Siemens Nixdorf PCD-3Tsx Siemens Nixdorf PCD-4Gsx Siemens Nixdorf PCD-4M Siemens Nixdorf PCD-4Msx Siemens Nixdorf PCD-4Rsx Siemens Nixdorf PCD-4T Siemens Nixdorf PCD-4Tsx Siemens Nixdorf PCE-4C Siemens Nixdorf PCM-3Dsx/20 Siemens Nixdorf PCM-4T Siemens Nixdorf PWS M30 Siemens Nixdorf PWS M50 Siemens Nixdorf PWS M60 Siemens Nixdorf PWS M70 Steiner POWER STC i80386DX-33 Steiner POWER STC i80386SX-16/20 Steiner POWER STC i80386SX/25 Steiner POWER STC i80486-33 Steiner POWER STC i80486-33 ISA Steiner POWER STC i80486SX-20/25 SWAN 286/16 Desktop SWAN 386/33M Desktop SWAN 386/33M Tower SWAN 386SX/16 Desktop SWAN 386SX/20 SWAN 386SX/20 Notebook SWAN 386SX/25 Desktop SWAN 486/33 Desktop SWAN 486/33 Tower SWAN 486/33E Desktop SWAN 486/33M Desktop SWAN 486/33M Tower SWAN 486SX/20 Desktop SWAN 486SX/20 Tower SWAN 486SX/20M Desktop SWAN 486SX/20M Tower SWAN 486SX/25 Desktop SWAN 486SX/25 Tower SWAN 486SX/25M Desktop SWAN 486SX/25M Tower SWAN 487SX/20 Desktop SWAN 487SX/20 Tower SWAN 487SX/25 Desktop SWAN 487SX/25 Tower SYNCOMP MEGA+386i-33 PC SYNCOMP MEGA+386i-40 PC SYNCOMP MEGA+486i-33 PC SYNCOMP MICRO 386i-33 PC SYNCOMP MICRO 386i-40 PC SYNCOMP MICRO 386SXi-16 PC SYNCOMP MICRO 386SXi-20 PC SYNCOMP MICRO 386SXi-25 PC SYNCOMP MINI 386i-33 PC SYNCOMP MINI 386i-40 PC SYNCOMP MINI 486i-33 PC SYNCOMP MINI 486SXi-20 PC SYNCOMP MINI SXI-16 PC SYNCOMP NETerm 386SXi-16 PC SYNCOMP NETerm 386SXi-20 PC SYNCOMP ProSport Portable Tandem CP 386SX/20 Tandem EP 486/25 Tandon 286/N Tandon 386/20 Tandon 386/25 Tandon 386/33 Tandon 386/33 Tower Tandon 386/N Tandon 386/N-16 Tandon 386/N-20 Tandon 386/N-25 Tandon 486/33 Tandon 486/50 Desktop Tandon 486/50 Tower Tandon Corp. MCS 286/12 Tandon Corp. MCS 386sx/20 Tandon Corp. MCS 386sx/20c Tandon Corp. MCS 386sx/25 Tandon Corp. MCS 386sx/25c Tandon Corp. MCS 486/33 Tandon Corp. MCS 486/50 Tandon Corp. MCS 486sx/20c Tandon Corp. MCS Pro 386/33 Tandon Corp. MCS Pro 486/33 Tandon Corp. MCS Pro 486/50 Tandon Corp. MCS Pro 486sx/20 Tandon Corp. Option 286/12 Tandon Corp. Option 386sx/20 Tandon Corp. Option 386sx/20c Tandon Corp. Option 386sx/25 Tandon Corp. Option 386sx/25c Tandon Corp. Option 486/33 Tandon Corp. Option 486/50 Tandon Corp. Option 486sx/20c Tandon Corp. Option Pro 386/33 Tandon Corp. Option Pro 486/33 Tandon Corp. Option Pro 486/50 Tandon Corp. Option Pro 486sx/20 Tandon Notebook 386sx/16 Tandon Notebook 386sx/25 Tandon Pac 286 8Mhz Tandon PacII 386sx-25c Tandon PacII 386sx/20 Tandon PacII 486/33 Tandon PacII 486/50 Tandon Tower 386/33 Tandon Tower 486/33 Tandy 2500SX Tandy 2500SX/20 Tandy 2500SX/25 Tandy 2500XL Tandy 2500XL2 Tandy 2810 Tandy 2820 Tandy 3000NL Tandy 3810 Tandy 3820 Tandy 4000 Tandy 4000LX Tandy 4000SX Tandy 4016DX Tandy 4016SX Tandy 4020LX Tandy 4020SX Tandy 4025LX Tandy 4820SX/T Tandy 4825SX Tandy 4833LX/T Tandy 4850 Tandy 5000MC Texas Instruments TravelMate 3000 Texas Instruments TravelMate 3000 WinSX Tiki-386 DX-33 Tiki-386 SX Tiki-386 SX Light Tiki-486 SX-20 Tiki-486-33e Tiki-486-33i Tiko PS 325 Tiko PS 325C Tiko PS 340C Tiko PS 420C Tiko PS 433C Toshiba DynaBook V386 Toshiba J-3100ZX Toshiba T1200XE Toshiba T2000 Toshiba T2000SX Toshiba T2200SX Toshiba T3100e Toshiba T3100SX Toshiba T3200 Toshiba T3200SX Toshiba T3200SXC Toshiba T3300SL Toshiba T4400SX Toshiba T5200 Toshiba T5200C Toshiba T6400 Toshiba T6400SXC Toshiba T8500 Tri Gem SX386E TriGem 286E+ TriGem 486XE TriGem SX386/20NP TriGem SX386M+ TriGem SX486E TRIUMPH ADLER P45 TRIUMPH ADLER TA DARIO 386 SX TRIUMPH ADLER TA DARIO 486 TRIUMPH ADLER TA DARIO 486 SX TRIUMPH ADLER TA DARIO 486 SXE TRIUMPH ADLER TA DARIO S/20 TRIUMPH ADLER TA WALKSTATION 386 33 TRIUMPH ADLER TA WALKSTATION 386 SX TRIUMPH ADLER TA WALKSTATION SX20 Tulip AT 386/25 Tulip NB 386sx Tulip TR 486e Tulip Vision 1 Tulip Vision Line DC Compact Tulip Vision Line DC/DT 286 Tulip Vision Line DC/DT 386SX Tulip Vision Line DE/TR 486dx/e-33 Tulip Vision Line DE/TR 486sx/e-25 Tulip Vision Line DT 486dx/e-33 Tulip Vision Line DT 486sx/e-25 Tulip Vision Line TR 486sx/e Tulip Vision Line WS 386sx Ultra-Comp 386-25 Non-Cache Power Ultra-Comp 386-33 Power Ultra-Comp 386SX-20 Power Ultra-Comp 486-33 EISA Power Ultra-Comp 486-33 ISA Power Ultra-Comp 486SX-20 Power Unisys Option LWS 286 Unisys Option LWS 386 Unisys Option PP 386DX Unisys Option PP 386SX Unisys Option PW2 3162 Unisys Option PW2 3203 Unisys Option PW2 3206 Unisys Option PW2 3256 Unisys Option PW2 3336 Unisys Option PW2 3336 80386/DX Unisys Option PW2 4336 Unisys Option PW2 500/16A Unisys Option PW2 500/20A Unisys Option PW2 600/20SX Unisys Option PW2 800/20 Unisys Option PW2 800/20C Unisys Option PW2 800/25A Unisys Option PW2 800/33A Unisys Option PW2 800/486-25A Unisys Option PW2 Advantage Model 3163 Unisys Option PW2 Advantage Model 3256 Victor V286/16M Victor V286/16MW Victor V286D Victor V386-25M Victor V386-33M Victor V386/20MWX Victor V386/20MX Victor V386/25MT Victor V386/25MW Victor V386/33MT Victor V386/33MW Victor V386DSX Victor V486/20MTX Victor V486/20MWX Victor V486/20MX Victor V486/33M Victor V486/33MT Victor V486/33MW Victor V486/33SFE Victor Vicki 286 Victor Vicki 386sx Video Technology Laser 286/X Video Technology Laser 386 Video Technology Laser 386SXE Video Technology Laser 486 Video Technology Laser 486SX Video Technology Laser LT321 Video Technology Laser PAL 386SX Viglen Genie 3DX33 Viglen Genie 3SX25 Viglen Genie 4DX33 Viglen Genie 4SX20 WANG EC 480/25C WANG EC 480/33C WANG EXEC 3000 WANG EXEC 3051 WANG EXEC 3100 WANG EXEC 3110 WANG EXEC 3120 WANG EXEC 3131 WANG EXEC 3450 WANG EXEC 3500 WANG EXEC 3501 WANG MC 350/16S WANG PC 240 WANG PC 280 WANG PC 280/20 WANG PC 321/16S WANG PC 321/20S WANG PC 350/33C WANG PC 350/40C WANG PC 361/20S WANG PC 361/25SC WANG PC 380/33C WANG PC 381 Western 386SX25VC Western 486H33 Western386V33 WYSE Decision 386/25 WYSE Decision 386/40 WYSE Decision 386SX/16 (slimline) WYSE Decision 386sx/16s WYSE Decision 386sx/16s (slim line) WYSE Decision 386sx/20 WYSE Decision 486/25 WYSE Decisionmate SX Laptop (slim line) WYSE pc Model 3016sx XYCOM 8450-5164 Zenith Data Systems Z-320/SX Zenith Data Systems Mastersport 286 Zenith Data Systems Mastersport 386SX Zenith Data Systems 486DX 25 Zenith Data Systems Z-LS/20 Zenith Data Systems Supersport SX Zenith Data Systems Z-386/25 Zenith Data Systems Z-386SX Zeos 386-25CA Zeos 386-25NC Zeos 386-35MWS Zeos 486-33E Zeos 486-33U Zeos 486SX-20 Zeos MXA386-33 Zeos Notebook 386SX16 Displays -------- COMPAC Portable Plasma EGA (enhanced graphics adapter) with color display EGA (enhanced graphics adapter) with black and white display EGA (enhanced graphics adapter) with monochrome display Herculees with high-resolution monochrome display IBM 8514/A IBM MCGA (multicolor graphics array) IBM XGA Olivetti/AT&T monochrome or PVC display Super VGA TIGA VGA VGA with monochrome display Video 7 (FastWrite, 1024i, VRAM, VRAMII) Printers -------- Agfa 9000 Series PS Agfa Compugraphic 400PS Agfa Compugraphic Genics Agfa-Compugraphic 9400P Apple Laser Writer Apple Laser Writer II NT Apple Laser Writer II NTX Apple Laser Writer Plus Apricot Laser AST TurboLaser/PS AT&T 435 AT&T 470/475 AT&T 473/478 C-Itoh 8510 Canon Bubble-Jet BJ-300 Canon Bubble-Jet BJ-330 Canon Bubble-Jet BJ-10e Canon Bubble-Jet BJ-130e Canon LBP-4 Canon LBP-8 II Canon LBP-8 III Citizen 120D Citizen 180D Citizen 200GX Citizen 200GX/15 Citizen GSX-130 Citizen GSX-140 Citizen GSX-140+ Citizen GSX-145 Citizen HSP-500 Citizen HSP-550 Citizen PN 48 Dataproducts LZR-2665 Diconix 150 Plus Digital Colormate PS Digital DEClaser 1150 Digital DEClaser 2150 Digital DEClaser 2250 Digital DEClaser 3250 Digital LN03R ScriptPrinter Digital PrintServer 20/turbo Digital PrintServer 40 Epson DFX-5000 Epson EPL-6000 Epson EPL-7000 Epson EPL-7500 Epson EX-1000 Epson EX-800 Epson FX-100 Epson FX-100+ Epson FX-1050 Epson FX-185 Epson FX-286 Epson FX-286e Epson FX-80 Epson FX-80+ Epson FX-85 Epson FX-850 Epson FX-86e Epson GQ-3500 Epson JX-80 Epson L-1000 Epson L-750 Epson LQ-1000 Epson LQ-1050 Epson LQ-1070 ESC/P 2 Epson LQ-1170 ESC/P 2 Epson LQ-1500 Epson LQ-2500 Epson LQ-2550 Epson LQ-500 Epson LQ-510 Epson LQ-570 ESC/P 2 Epson LQ-800 Epson LQ-850 Epson LQ-870 ESC/P 2 Epson LQ-950 Epson LX-80 Epson LX-800 Epson LX-810 Epson LX-86 Epson MX-100 Epson MX-80 Epson MX-80 F/T Epson MX-80 F/T+ Epson SQ-2000 Epson SQ-2500 Epson T-1000 Epson T-750 Fujitsu DL 2400 Fujitsu DL 2600 Fujitsu DL 3300 Fujitsu DL 3400 Fujitsu DL 5600 Fujitsu DL 2100 Fujitsu DL 2200 Fujitsu DL 2300 Fujitsu DL 2400 Hermes H 606 Hermes H 606 PS(13 fonts) Hermes H 606 PS(35 fonts) HP 7470A (HP Plotter) HP 7475A (HP Plotter) HP 7550A (HP Plotter) HP 7580A (HP Plotter) HP 7580B (HP Plotter) HP 7585B (HP Plotter) HP 7586B (HP Plotter) HP ColorPro (HP Plotter) HP ColorPro with GEC (HP Plotter) HP DeskJet HP DeskJet 500 HP DeskJet 500C HP DeskJet Plus HP DraftMaster I (HP Plotter) HP DraftMaster II (HP Plotter) HP DraftPro (HP Plotter) HP DraftPro DXL (HP Plotter) HP DraftPro EXL (HP Plotter) HP LaserJet HP LaserJet 2000 HP LaserJet 500+ HP LaserJet IID HP LaserJet IID PostScript HP LaserJet III HP LaserJet III PostScript HP LaserJet IIID HP LaserJet IIID PostScript HP LaserJet IIIP HP LaserJet IIISi HP LaserJet IIISi PostScript HP LaserJet IIP HP LaserJet IIP Plus HP LaserJet IIP PostScript HP LaserJet Plus HP LaserJet Series II HP PaintJet HP PaintJet XL HP ThinkJet (2225 C-D) IBM Color Printer IBM ExecJet IBM Graphics IBM Laser Printer 4019 IBM LaserPrinter 4019 PS17 IBM LaserPrinter 4019 PS39 IBM LaserPrinter 4029 PS17 IBM LaserPrinter 4029 PS39 IBM Personal Page Printer II-30 IBM Personal Page Printer II-31 IBM Personal PagePrinter IBM Proprinter IBM Proprinter II IBM Proprinter III IBM Proprinter X24 IBM Proprinter X24e IBM Proprinter XL IBM Proprinter XL II IBM Proprinter XL III IBM Proprinter XL24 IBM Proprinter XL24e OceColor G5242 PS IBM PS/1 IBM QuickWriter 5204 IBM QuietWriter III Kyocera F-5000 (USA) Kyocera F-Series (USA) Linotronic 200/230 Linotronic 330 Linotronic 530 Linotronic 630 Microtek TrueLaser NEC Colormate PS/40 NEC Colormate PS/80 NEC Pinwriter CP6 NEC Pinwriter CP7 NEC Pinwriter P2200 NEC Pinwriter P5200 NEC Pinwriter P5300 NEC Pinwriter P5XL NEC Pinwriter P6 NEC Pinwriter P7 NEC Pinwriter P9XL NEC Silentwriter LC 860 Plus NEC Silentwriter LC890 NEC Silentwriter LC890XL NEC Silentwriter2 290 NEC Silentwriter2 90 NEC Silentwriter2 990 OceColor G5241 PS Oki OL840/PS Okidata ML 192 Okidata ML 192 Plus Okidata ML 193 Okidata ML 193 Plus Okidata ML 193-IBM Okidata ML 320 Okidata ML 320-IBM Okidata ML 321 Okidata ML 321-IBM Okidata ML 380 Okidata ML 390 Okidata ML 391 Okidata ML 391 Plus Okidata ML 393 Okidata ML 393 Plus Okidata ML 393C Okidata ML 393C Plus Okidata ML 92-IBM Okidata ML 93-IBM Okidata OL-400 Okidata OL-800 Olivetti DM 109 Olivetti DM 309 Olivetti ETV 5000 Olivetti PG 108 Olivetti PG 208 M2 Olivetti PG 303 Olivetti PG 306 Olivetti PG 306 PS (13 fonts) Olivetti PG 306 PS (35 fonts) Olivetti PG 308 HS Olivetti PG 308 HS PostScript Panasonic KX-P1123 Panasonic KX-P1124 Panasonic KX-P1180 Panasonic KX-P1624 Panasonic KX-P1695 Panasonic KX-P4420 Panasonic KX-P4455 V51.4 QMS ColorScript 100 QMS-PS 2200 QMS-PS 800 QMS-PS 800 Plus QMS-PS 810 QMS-PS 820 QuadLaser I Seiko ColorPoint PS Model 04 Seiko ColorPoint PS Model 14 Tandy LP-1000 Tegra Genesis Tektronix Phaser II PX Tektronix Phaser II PXi Tektronix Phaser III PXi TI 850/855 TI microLaser PS17 TI microLaser PS35 TI OmniLaser 2108 TI OmniLaser 2115 Toshiba P1351 Toshiba P351 Toshiba PageLaser 12 Triumph Adler SDR 7706 Triumph Adler SDR 7706 PS13 Triumph Adler SDR 7706 PS35 Unisys AP9210 Unisys AP9415 Varityper VT-600 Wang LCS15 Wang LCS15 FontPlus Wang LDP8 Networks -------- 3Com 3+Open LAN Manager 3Com 3+Share Artisoft LANtastic version 3.0 or higher Banyan VINES version 4.0 or higher DEC Pathworks version 4.0 or higher IBM OS/2 LAN Server version 1.2 or higher IBM PC LAN Program Microsoft LAN Manager Microsoft Networks (or 100% compatible) Novell NetWare workstation shell version 3.01 or higher TCS 10Net version 4.1 or higher Pointing Devices ---------------- Genius serial mouse HP mouse (HP-HIL) IBM PS/2 mouse Logitech mouse Microsoft BallPoint mouse Microsoft Mouse Mouse Systems serial or bus mouse Olivetti/AT&T keyboard mouse Keyboards --------- All AT-type keyboards (8486 keys) AT&T '301' keyboard AT&T '302' keyboard Enhanced 101- or 102-key U.S. and non-U.S. keyboards Hewlett-Packard Vectra keyboard (DIN) Olivetti 101/102 A keyboard Olivetti 83-key keyboard Olivetti 86-key keyboard Olivetti M24 102-key keyboard PC-XT 83-key keyboard PC/XT-type keyboard (84 keys) KBCategory: kbnetwork kbdisplay kbref kb3rdparty kbhw KBSubcategory: win30 win31 Additional reference words: 3.1 3.10 hcl supported video WW0525: Troubleshooting 386 Enhanced Mode Problems Article ID: Q83259 ---------------------------------------------------------------- ---- The information in this article applies to: - Microsoft Windows operating system versions 3.1, 3.11 ---------------------------------------------------------------- ---- Microsoft Product Support Services offers an Application Note titled "WW0525: Troubleshoooting 386 Enhanced Mode Problems" that can help you troubleshoot 386 enhanced mode problems. Symptoms of these problems include: - Windows stopping or returning to the MS-DOS prompt - General protection (GP) faults - Windows defaulting to standard mode when you type "win" (without the quotation marks) at the MS-DOS prompt You can obtain this Application Note from the following sources: - CompuServe, GEnie, and Microsoft OnLine - Microsoft Download Service (MSDL) - The Internet (Microsoft anonymous ftp server) - Microsoft FastTips Technical Library - Microsoft Product Support Services For complete information, see the "To Obtain This Application Note" section at the end of this article. THE TEXT OF WW0525 ================== ================================================================ ====== Microsoft Product Support Services Application Note (Text File) WW0525: Troubleshooting 386 Enhanced Mode Problems ================================================================ ====== Revision Date: 3/92 No Disk Included The following information applies to Microsoft Windows version 3.1. ----------------------------------------------------------------- --- | INFORMATION PROVIDED IN THIS DOCUMENT AND ANY SOFTWARE THAT MAY | | ACCOMPANY THIS DOCUMENT (collectively referred to as an | | Application Note) IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY | | KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO | | THE IMPLIED WARRANTIES OF MERCHANTABILITY AND/OR FITNESS FOR A | | PARTICULAR PURPOSE. The user assumes the entire risk as to the | | accuracy and the use of this Application Note. This Application | | Note may be copied and distributed subject to the following | | conditions: 1) All text must be copied without modification and | | all pages must be included; 2) If software is included, all files | | on the disk(s) must be copied without modification [the MS-DOS(R) | | utility DISKCOPY is appropriate for this purpose]; 3) All | | components of this Application Note must be distributed together; | | and 4) This Application Note may not be distributed for profit. | | | | Copyright 1992 Microsoft Corporation. All Rights Reserved. | | Microsoft, MS-DOS, and the Microsoft logo are registered | | trademarks and Windows is a trademark of Microsoft Corporation. | ---------------------------------------------------------------- ---- Introduction ------------ Microsoft Windows version 3.1 has two modes of operation: standard and 386 enhanced modes. 386 enhanced is the highest-level mode of operation because it utilizes the virtual mode of the 80386i processor. However, you may experience the following problems when attempting to run Windows 3.1 in 386 enhanced mode: - Windows stopping or returning to the MS-DOS prompt - General protection faults (GPFs) - Windows defaulting to standard mode when you type "win" (without the quotation marks) at the MS-DOS prompt Troubleshooting Procedure ------------------------- The following steps may correct or reduce these problems: 1. Ensure that the system has the minimum configuration required to run Windows 3.1 in 386 enhanced mode. These requirements are: - An 80386 or faster processor - 200K of free conventional memory - 1024K of free extended memory - 2 MB of free disk space 2. Try to force Windows into 386 enhanced mode by typing "win /3" (without the quotation marks). If this is successful, the computer probably has available less than the 1024K of extended memory required for Windows to default to 386 enhanced mode on startup. Verify that you are running an extended memory manager (HIMEM.SYS is the extended memory manager that comes with Windows 3.1). If so, you should free up extended memory so that Windows can default to 386 enhanced mode. The best way to accomplish this is to start your computer with minimal CONFIG.SYS and AUTOEXEC.BAT files. Using a text editor such as Notepad, comment out any lines that load extraneous device drivers, terminate-and-stay-resident (TSR) programs, and so forth, that are not required to run your machine. To comment out a line, type "rem" (without the quotation marks) at the beginning of the line. Caution: If you do not know the purpose of a line in your CONFIG.SYS or AUTOEXEC.BAT file, leave that line as is. Other things that might help free up extended memory include reducing the size of any disk cache, such as SMARTDRV.EXE, or RAM drive. Although you can force Windows into enhanced mode if there is less than 1024K of extended memory, this is not recommended because this condition can adversely affect the performance of Windows. 3. Try starting Windows by typing: win /d:xvs If this is successful, try each of the following switches individually to see which is required: WIN /D:X This switch excludes the entire upper memory block region from A000-FFFF. It is functionally equivalent to adding EmmExclude=A000-EFFF to the [386enh] section of the SYSTEM.INI file. NOTE: If any upper memory block (UMB) provider is installed in the CONFIG.SYS file, this switch has no effect in the region the UMB provider is using. The UMB provider has priority in the UMB area. For this reason, you should disable the UMB provider (such as EMM386.EXE), restart the system, and then try the WIN /D:X switch. WIN /D:V This switch is equivalent to adding the line VirtualHDIrq=OFF to the [386enh] section of the SYSTEM.INI file. For more information about the VirtualHDIrq= setting, consult the SYSINI.WRI file in the \WINDOWS directory. WIN /D:S This switch is equivalent to adding the line SystemROMBreakPoint=OFF to the [386enh] section of the SYSTEM.INI file. After determining which switch, or combination of switches, allows Windows 3.1 to successfully start in 386 enhanced mode, use a text editor such as Notepad to add the corresponding line, or lines, to the [386enh] section of the SYSTEM.INI file. 4. Create a BOOTLOG.TXT file by typing "win /b" (without the quotation marks) to start Windows. This switch will create a file called BOOTLOG.TXT in the \WINDOWS directory. Once this file has been created, you can view it using any text editor (such as Notepad). In this file, Windows creates a list of the basic Windows drivers as they are loaded. If there is a problem with one of these drivers loading, a statement will appear in the BOOTLOG.TXT file showing which driver could not load. This information is valuable in determining which component of Windows is not able to function properly. NOTE: This switch will append new information to the end of an existing BOOTLOG.TXT file. Therefore, you may want to rename or delete any existing BOOTLOG.TXT file in the \WINDOWS directory before using the /B switch. The following is a list of error codes that may appear in the BOOTLOG.TXT file: 0 Out of memory 2 File not found 3 Path not found 5 Attempt to dynamically link to a task 6 Library requires separate data segments for each task 8 Insufficient memory to start application 10 Incorrect Windows version 11 Invalid .EXE file (non-Windows .EXE file or error in .EXE file image) 12 OS/2 application 13 MS-DOS 4.0 application 14 Unknown .EXE file type 15 Attempt in protected (standard or 386 enhanced) mode to load an .EXE file created for an earlier version of Windows 16 Attempt to load a second instance of an .EXE file containing multiple writeable data segments 17 Attempt in a large-frame EMS mode to load a second instance of an application that links to certain nonshareable DLLs already in use 18 Attempt in real mode to load an application marked for protected mode only 5. At the MS-DOS prompt, change to the \WINDOWS directory before starting Windows. When Windows starts, it reads the .INI files that specify the locations of many of the files that Windows needs in order to start. When Windows reads the .INI files, it looks for the specified files in the following locations: a. The current directory b. The \WINDOWS directory c. The \WINDOWS\SYSTEM subdirectory d. All of the directories listed in the PATH environment variable in the AUTOEXEC.BAT file e. All of the directories in the list of directories mapped on a network For example, if there is an outdated MOUSE.DRV file (the Windows Microsoft Mouse driver) in the current directory, Windows may not be able to start. 6. Verify that Windows can run in standard mode by typing "win /s" (without the quotation marks) at the MS-DOS prompt. If Windows can run in standard mode, you may have installed a mouse, keyboard, video, or printer driver designed for a previous version of Windows, or you may have made an incorrect selection for your hardware. To change the printer driver, start the Control Panel and choose the Printers icon. To change the mouse, keyboard, video, or network driver, from the Program Manager File menu, choose Run, type "setup," (without the quotation marks) and choose the OK button. This command brings up the System Information screen; from the Options menu, choose Change System Settings. Also, check the "Microsoft Windows Version 3.1 Hardware Compatibility List" that ships with Windows to see if your computer requires special handling. If it does, exit Windows and then reinstall it, using only a minimum of drivers (use no mouse or network driver and use the lowest resolution video driver) and the SETUP /I switch. Another option is to delete Windows and reinstall it using the SETUP /I switch, along with the minimal configuration described above. This may be necessary if it is not possible to determine which component of Windows is preventing proper operation. 7. Check your AUTOEXEC.BAT and CONFIG.SYS files for TSR programs, sufficient buffers, files, and environment space. Some TSR programs are not compatible with Windows 3.1 and may need to be commented out during Windows operation. Again, if you do not know the purpose of a line, do not comment it out. 8. Disable the autoswitching or autosensing feature on the video card if applicable. Verify that you are using the latest version of the BIOS (basic input/output system) for that video card (see step 13). 9. Disable system or video ROM shadowing if it is supported by the system. 10. Verify that you are using the correct version of MS-DOS for the system. You should be using a version of MS-DOS that is 3.1 or later and is designed for the machine. Do NOT use an original equipment manufacturer (OEM) version of MS-DOS on a computer that was not manufactured by that OEM (for example, do not use COMPAQ MS-DOS on an IBM computer). 11. Ensure that HIMEM.SYS loads successfully. If it does not, or if a problem is suspected, try ALL A20 handlers available to the version of HIMEM.SYS being used. The DEVICE=C:\HIMEM.SYS line in your CONFIG.SYS file should include the /M:x switch, where x denotes a handler number. For example, if you are using a PS/2, this line should read DEVICE=C:\HIMEM.SYS /M:2. For more information about the /M switch, see pages 543-547 of the version 3.1 "Microsoft Windows User's Guide." NOTE: Some A20 handlers may lock up your computer, so it is important to have a system MS-DOS floppy disk available that contains an ASCII text editor (such as Edlin or Edit) should this problem occur. 12. Install Windows in an empty directory. Do not install Windows version 3.1 over a 2.x version, because some files and drivers may not be updated properly. 13. Confirm that you are using a system BIOS that is dated 1988 or later. If you are using a BIOS with a date earlier than 1988, you may encounter problems when trying to run Windows 3.1 in 386 enhanced mode. The BIOS date will vary depending on the brand of your BIOS and the manufacturer of your machine. The BIOS version and date are typically displayed when you first start up the system. If the date is not displayed when the system is started, or if you have any questions about the compatibility of your BIOS with Windows 3.1, you should contact your hardware manufacturer. 14. Remove any additional hardware from the system (mouse, network card, fax board, modem, and so forth). After all the nonessential hardware has been removed, restart the system, and run Windows 3.1. If you can now run in 386 enhanced mode, it is likely that an interrupt request line (IRQ) conflict exists. Replace one piece of hardware at a time, restarting the machine after each new piece of hardware is replaced, and run Windows in 386 enhanced mode. Do this until the symptom reoccurs, at which point you've most likely found an IRQ conflict. For more information on how to deal with IRQ conflicts, contact the manufacturer of the piece of hardware in question. 15. If none of the above steps has corrected the problem, you may want to contact your hardware manufacturer for additional information. TO OBTAIN THIS APPLICATION NOTE =============================== - On CompuServe, GEnie, and Microsoft OnLine, Application Notes are located in the Microsoft Software Library. You can find WW0525 in the Software Library by searching on the word WW0525, the Q number of this article, or S13365. WW0525 was archived using the PKWARE disk-compression software. - Application Notes are available by modem from the Microsoft Download Service (MSDL), which you can reach by calling (206) 936-6735. This service is available 24 hours a day, 7 days a week. The highest download speed available is 14,400 bits per second (bps). For more information about using the MSDL, call (800) 936-4200 and follow the prompts. To obtain WW0525, download WW0525.EXE. WW0525.EXE is a compressed, self-extracting file. After you download WW0525, run it to extract the file(s) it contains. - On the Internet, Application Notes are located on the Microsoft anonymous ftp server, which you can reach by typing "ftp ftp.microsoft.com" (without the quotation marks) at the ">" command prompt. You can find WW0525.EXE in the SOFTLIB/MSLFILES directory. - You can have this Application Note mailed or faxed to you from the automated Microsoft Windows 3.1 FastTips Technical Library, which you can call 24 hours a day, 7 days a week at (800) 936-4200. NOTE: The FastTips Technical Library is available only to customers within the U.S. and Canada. - If you are unable to access the source(s) listed above, you can have this Application Note mailed or faxed to you by calling Microsoft Product Support Services Monday through Friday, 6:00 A.M. to 6:00 P.M. Pacific time at (206) 637-7098. If you are outside the United States, contact the Microsoft subsidiary for your area. To locate your subsidiary, call Microsoft International Sales Information Center at (206) 936-8661. KBCategory: kbfile kbdisplay kbtshoot kbappnote KBSubcategory: Additional reference words: appnote tshoot gpf 3.10 S13365 winmem win31 Windows 3.1 Resource Kit WIN.INI Section Settings Article ID: Q83433 SUMMARY ======= The information contained in this article is contained in the WININI.WRI file in the Microsoft Windows Resource Kit for the Microsoft Windows operating system version 3.1. The WININI.WRI file may be viewed within the Windows Write utility in the Windows Accessories Group. The WININI.WRI file contains specific information about the entries. MORE INFORMATION ================ WIN.INI File Settings --------------------- Windows initialization files contain information that defines your Windows environment. Windows and Windows applications can use the information stored in these files to configure themselves to meet your needs and preferences. There are two standard Windows initialization files: 1. WIN.INI, which primarily contains settings that you can use to customize your Windows environment according to your preferences. 2. SYSTEM.INI, which primarily contains settings that you can use to customize Windows to meet your system's hardware needs. Caution: Changing settings can lead to undesirable results when you run Windows. Before changing any setting, read "Changing Settings" later in this document. Format of the WIN.INI File -------------------------- The WIN.INI file contains several sections, each of which consists of a group of related settings. The sections and settings are listed in the WIN.INI file in the following format: [section name] keyname=value In this example, [section name] is the name of a section. The enclosing brackets ([]) are required, and the left bracket must be in the leftmost column on the screen. The keyname=value statement defines the value of each setting. A keyname is the name of a setting. It can consist of any combination of letters and digits, and must be followed immediately by an equal sign (=). The value can be an integer, a string, or a quoted string, depending on the setting. You can include comments in initialization files. You must begin each line of a comment with a semicolon (;). Sections in the WIN.INI File ---------------------------- The sections described in the list below most often appear in the WIN.INI file. Your WIN.INI file might not have all of these sections, or it might have additional sections, depending on your system's hardware and software requirements and configuration. For example, if you install a printer or set up applications, additional sections and settings might be inserted by your applications or the software that controls your printer. Refer to your application's documentation for information on those sections and settings. The following sections appear in WIN.INI and in this document in the following order (however, the order of these sections is not important): Section Does ------- ---- [windows] Affects several elements of your Windows environment. [desktop] Controls the appearance of the screen background (desktop) and the positioning of windows and icons. [extensions] Associates specified types of files with corresponding applications. [intl] Describes how to display items for different countries and languages. [ports] Lists all available output ports. [fonts] Lists the font files that are loaded by Windows. [FontSubstitutes] Lists the fonts that Windows uses in place of other fonts, only if the other fonts are not installed on your system. [TrueType] Describes options for using and displaying TrueType fonts. [mci extensions] Associates specified types of files with Media Control Interface devices. [network] Describes network settings and previous network connections. [embedding] Lists the server objects used in OLE. [Windows Help] Lists settings used to specify the default size, placement, and text colors of the Help window and dialog boxes. [sounds] Lists sound files assigned to system and application events. [PrinterPorts] Lists installed printers that Windows can access. [devices] Lists installed printers that provide compatibility with Windows versions 2.x. [programs] Lists additional paths that Windows will search to find a program file when you try to open an associated data file. [colors] Defines colors for parts of the Windows display. Updating WIN.INI from Previous Versions of Windows -------------------------------------------------- If you update your system to Windows version 3.1 from Windows version 3.0, Setup automatically updates your WIN.INI file by making the following changes: In the [windows] section, Setup adds three new settings: KeyboardDelay= ScreenSaverTimeout= DosPrint= If the following settings are already present in the 3.0 version of the WIN.INI file, Setup will not change them. If they are not present, Setup will add them: Device= Documents= Programs=com exe bat pif In the [extensions] section, Setup adds one new setting: bmp=pbrush.exe ^.bmp Setup adds two new settings, if they are not already present in the 3.0 version of the WIN.INI file: pcx=pbrush.exe ^.pcx rec=recorder.exe ^.rec In the [ports] section, Setup adds: LPT1.DOS LPT2.DOS Setup adds three additional settings, if they are not already present in the 3.0 version of WIN.INI: FILE: COM3:=9600,n,8,1,x COM4:=9600,n,8,1,x Setup adds the following section and settings to support TrueType fonts: [FontSubstitutes] Helv=MS Sans Serif Tms Rmn=MS Serif Times=Times New Roman Helvetica=Arial Setup adds the following sections and settings to support multimedia: [mci extensions] wav=waveaudio mid=sequencer rmi=sequencer Setup adds the following sections and settings to support sound: [sounds] SystemDefault=ding.wav, Default Beep SystemExclamation=chord.wav, Exclamation SystemStart=tada.wav, Windows Start SystemExit=chimes.wav, Windows Exit SystemHand=chord.wav, Critical Stop SystemQuestion=chord.wav, Question SystemAsterisk=chord.wav, Asterisk Setup adds the following section and settings to support OLE: [embedding] SoundRec=Sound,Sound,SoundRec.exe,picture Package=Package,Package,packager.exe,picture PBrush=Paintbrush Picture,Paintbrush Picture,pbrush.exe,picture Setup also makes additional changed, depending on the applications and devices installed on your system. How to Read this Document ------------------------- In this document, WIN.INI settings are listed alphabetically within sections. However, the settings do not appear alphabetically in the WIN.INI file. If you want to change a setting, you will have to search for it within the appropriate section. This document lists the syntax, purpose, and recommended method for changing each setting using the following format: SettingName= Default: This is Windows' built-in value for this setting. Purpose: This paragraph briefly describes the function of the setting and its default value (if applicable). To change: This sentence states the recommended method for changing the value of this setting. The indicates whether the value should be a number, a letter, a range of numbers, or something else. Changing Settings ----------------- When the Setup program created the WIN.INI, file it assigned default values to the settings. Some settings that are listed in this document, may not appear in your WIN.INI file. These settings have the default value. You might want to change one or more of these values to change the appearance or performance of Windows to suit your needs. Caution: Always back up your WIN.INI file before you make changes so that you can restore the original file in cause you accidently damage the WIN.INI file or make changes that cause problems when running Windows. There are two ways to change WIN.INI settings: By using Control Panel to change most settings. This is the safest and most recommended way because there is no need to open the WIN.INI file, where it is easier to make mistakes. For more information on Control Panel, see Chapter 5, "Control Panel," in the Windows User's Guide. By using a text editor, such as Notepad, to edit the WIN.INI file directly. (Don't use a formatting editor; it can corrupt your WIN.INI file.) This is the method you must use to change the settings that cannot be changed with Control Panel. After you have edited the WIN.INI file, you must restart Windows for the settings to take affect. For more information on how to use Notepad, see Chapter 12, "Additional Accessories," in the Windows User's Guide. Caution: Be extra careful when using a text editor to edit the WIN.INI file. Incorrect changes to WIN.INI can cause unexpected results when you run Windows. In addition, some editors can damage certain characters (those with ANSI values of greater than 127). It is recommended that you use Notepad to change the settings that cannot be changed with Control Panel. The listings in this document indicate which settings you can change with Control Panel. [windows] Section Settings -------------------------- The [windows] section contains settings that affect the following parts of your Windows environment: Applications that start when you start Windows Warning beep Printing Window border width Keyboard speed Mouse settings Definition of files as documents or programs The [windows] section can contain the following settings: Beep= Default: Yes Purpose: If this setting is enabled, Windows sounds a warning beep when you attempt to do something that is not allowed. To change: Choose the Sound icon from the Control Panel window. BorderWidth= Default: 3 Purpose: Sets the width of the borders around all the windows on your desktop except those that have a fixed size. The allowed range is 1 (narrowest) to 49 (widest). To change: Choose the Desktop icon from the Control Panel window. CoolSwitch=<0-or-1> Default: 1 Purpose: Turns fast task switching on or off. A value of 1 turns this feature on. A value of 0 turns it off. To change: Choose the Desktop icon in the Control Panel window and select or clear the Fast "Alt+TAB" Switching check box. ____________________________________________________________ CursorBlinkRate= Default: 530 Purpose: Indicates how many milliseconds elapse between each blink of the selection cursor. To change: Choose the Desktop icon from the Control Panel window. _____________________________________________________________ Device=, , Default: None Purpose: Defines the default printer. The value can be any device name given in the [devices] section. An explicit port and driver must be assigned to the device. The value is the filename (without the extension) of the device-driver file. The value is any portname given in the [ports] section. To change: Choose the Printers icon from the Control Panel window or the Printer Setup command from the Print Manager Options menu. _____________________________________________________________ DefaultQueueSize= Default: 8 Purpose: Specifies the number of messages an application's message queue can hold. To change: Use Notepad to edit the WIN.INI file. (You should never need to change this setting.) ____________________________________________________________ DeviceNotSelectedTimeout= Default: 15 Purpose: Specifies the default number of seconds for Windows to wait for a device to be switched on. A value is saved for each printer listed in the [PrinterPorts] section. If the device is not turned on during this time, Windows won't print to the device. Note that for some devices, Windows immediately displays an error message if the device is not already turned on. To change: Use Notepad to edit the WIN.INI file. This setting serves only as the system default value. To change the value for a particular printer, choose the Printers icon from the Control Panel window or the Printer Setup command from the Print Manager Options menu. This changes the corresponding value only in the [PrinterPorts] section. ____________________________________________________________ Documents= Default: None Purpose: Defines files that are considered "documents" by Windows File Manager. The listings in the [extensions] section also determine which files File Manager recognizes as document files, and associates them with a particular application. The extensions listed here are not associated with any application. Use this setting to define only document file extensions that are not in the [extensions] section. Separate extension names with a space, and do not include the preceding periods. To change: Use Notepad to edit the WIN.INI file. ____________________________________________________________ DosPrint= Default: No Purpose: Specifies whether Windows should use MS-DOS interrupts when printing. When this setting is yes, MS-DOS interrupts are used. When this setting is no, printing output is sent directly to the port that the printer is assigned to. To change: Choose the Printers icon from the Control Panel window or the Printer Setup command from the Print Manager Options menu, and then clear the Fast Printing Direct to Port check box in the Connect dialog box. ____________________________________________________________ DoubleClickHeight= Default: 4 Purpose: Specifies the height (in pixels) that the mouse pointer can move between clicks in a double-click. If the mouse pointer is moved further up or down, the two clicks will be treated as separate single clicks. For example, if DoubleClickHeight=10, the mouse pointer cannot move vertically more than 5 pixels between clicks for the two clicks to be recognized as a double-click. If you enter an odd number, it is rounded up to the nearest even number. To change: Use Notepad to edit the WIN.INI file. ____________________________________________________________ DoubleClickSpeed= Default: 452 Purpose: Establishes the maximum amount of time between clicks of the mouse button that the system will permit for one double- click. The lower the value, the less time you have to click twice in order to effect a double-click. To change: Choose the Mouse icon from the Control Panel window. ____________________________________________________________ DoubleClickWidth= Default: 4 Purpose: Specifies the width (in pixels) that the mouse pointer can move between clicks in a double-click. If the mouse pointer is moved further right or left, the two clicks will be treated as separate single clicks. For example, if DoubleClickWIDTH=10, the mouse pointer cannot move horizontally more than 5 pixels between clicks for the two clicks to be recognized as a double-click. If you enter an odd number, it is rounded up to the nearest even number. To change: Use Notepad to edit the WIN.INI file. ____________________________________________________________ KeyboardDelay= Default: 2 Purpose: Establishes how much time elapses after you hold down a key before the key starts to repeat. To change: Choose the Keyboard icon from the Control Panel window. ____________________________________________________________ KeyboardSpeed= Default: 31 Purpose: Establishes how much time elapses between repetitions of a character on the display when you hold down a keyboard key. This setting does not work for all keyboards. If you delete this setting from WIN.INI, Windows Setup will not set this speed, but the speed will still be set if you choose the Keyboard icon in Control Panel (even if you cancel out of it). To change: Choose the Keyboard icon from the Control Panel window. ____________________________________________________________ Load= Default: none Purpose: Specifies one or more applications that will run as icons when Windows is started. This value is a list of one or more program filenames for applications, or documents that are associated with an application, each separated by a space. Make sure you specify the complete path if the application or document is not located in the Windows directory. To change: Add the application to the Startup group in Program Manager and then, select the Minimize on Use check box in the Properties dialog box. ____________________________________________________________ MenuDropAlignment=<0-or-1> Default: 0 Purpose: Specifies whether menus open so that they are right aligned or left aligned with the menu title. If this setting is 0, menus open so that they are left aligned. If it is 1, menus open so that they are right aligned. To change: Use Notepad to edit the WIN.INI file. ____________________________________________________________ MenuShowDelay= Default: 0 for 386 computers; 400 for 286 computers Purpose: Specifies how long to wait before displaying a cascading menu. To change: Use Notepad to edit the WIN.INI file. ____________________________________________________________ MouseSpeed=<0-or-1-or-2> Default: 1 Purpose: Establishes the relationship between mouse movement and cursor movement when the value of either MouseThreshold1 or MouseThreshold2 is exceeded. When this occurs, Windows causes cursor movement to accelerate according to the value of MouseSpeed. If it is 0, there is no acceleration. If it is 1, the cursor is moved twice the normal speed when mouse movement exceeds the value of MouseThreshold1. If it is 2, the cursor is moved twice the normal speed when mouse movement exceeds the value of MouseThreshold1 or four times the normal speed if mouse movement exceeds MouseThreshold2. To change: Choose the Mouse icon from the Control Panel window. ____________________________________________________________ MouseThreshold1= Default: 5 Purpose: Establishes the maximum number of pixels that the mouse can move between mouse interrupts before Windows alters the relationship between mouse movement and cursor movement. If the mouse movement exceeds this threshold and MouseSpeed is greater than zero, Windows moves the cursor at twice the normal speed. To change: Choose the Mouse icon from the Control Panel window. ____________________________________________________________ MouseThreshold2= Default: 10 Purpose: Establishes the maximum number of pixels that the mouse can move between mouse interrupts before Windows alters the relationship between mouse movement and cursor movement. If the mouse movement exceeds this threshold and MouseSpeed is equal to 2, Windows moves the cursor at four times the normal speed. To change: Choose the Mouse icon from the Control Panel window. ____________________________________________________________ MouseTrails= Default: None Purpose: Specifies the number of pointers shown on the screen when the MouseTrails option is selected. You can specify a number between 1 and 7. Note: This setting is supported only if you are using an EGA, VGA or SuperVGA display driver. To change: Choose the Mouse icon from the Control Panel window or, if the Mouse dialog box in Control Panel does not include the MouseTrails option, use Notepad to edit the WIN.INI file. ____________________________________________________________ NetWarn=<0-or-1> Default: 1 Purpose: Specifies whether Windows should display a warning message if your system is configured to run a network and the network is not running or the wrong network is running. All Windows network-related options will be disabled if the network is disabled or incorrect. Setting this value to 0 will disable the warning message. To change: Choose the Network icon from the Control Panel window. ____________________________________________________________ NullPort= Default: "None" Purpose: Specifies the name used for a null port. This name appears in the Printers-Connect dialog box when a device is installed (that is, the device driver is present) but is not connected to any port. This value also appears for such a device in the [devices] section of WIN.INI. To change: Use Notepad to edit the WIN.INI file. ____________________________________________________________ Programs= Default: com exe bat pif Purpose: Defines which files Windows regards as applications. Extension names are separated by a space and do not include the preceding periods. To change: Use Notepad to edit the WIN.INI file. ____________________________________________________________ Run= Default: None Purpose: Causes Windows to run one or more specified applications when Windows is started. The value is a list of one or more filenames of applications, or documents associated with applications, each separated by a space. Make sure you specify the complete path if the application or document is not located in the Windows directory. To change: Add the application to the Startup group in Program Manager. ____________________________________________________________ ScreenSaveActive=<0-or-1> Default: 0 Purposes: Specifies whether a screen saver should be displayed if Windows is not actively being used. Setting this value to 1, enables a screen saver. Setting this value to 0 disables a screen saver. To change: Choose the Desktop icon from the Control Panel window. ____________________________________________________________ ScreenSaveTimeOut= Default: 120 Purpose: Specifies the amount of time that Windows must be idle before the screen saver appears. To change: Choose the Desktop icon from the Control Panel window. ____________________________________________________________ Spooler= Default: Yes Purpose: Specifies whether or not to send output to the printer through Print Manager. Changing this value to no disables Print Manager. To change: Choose the Printers icon from the Control Panel window and select or clear the Use Print Manager check box. ____________________________________________________________ SwapMouseButtons=<0-or-1> Default: 0 Purpose: Specifies whether or not to swap the right and left mouse buttons. If the value is 1, the buttons are swapped. To change: Choose the Mouse icon from the Control Panel window. ____________________________________________________________ TransmissionRetryTimeout= Default: 90 for PostScript printers; 45 for all other printers. Purpose: Specifies the default amount of time to give Windows for attempted transmission retries. A value is saved for each printer in the [PrinterPorts] section. If a successful transmission does not occur during this time, Windows Print Manager displays a message stating that the printer is not receiving characters. To change: Use Notepad to edit the WIN.INI file. This setting serves only as the system default value. To change the value for a particular printer, choose the Printers icon from the Control Panel window or choose the Printer Setup command from the Print Manager Options menu. Changing this setting by using Control Panel or Print Manager changes the corresponding value only in the [PrinterPorts] section. ____________________________________________________________ [desktop] Section Settings The [desktop] section contains optional settings that control the appearance of the screen background (desktop) and the positioning of windows and icons on the screen. The [desktop] section can contain the following settings: ____________________________________________________________ GridGranularity= Default: 0 Purpose: Specifies the size (in units of eight pixels) of the grid that Windows uses to position windows on the screen. You can specify a number between 0 and 49. To change: Choose the Desktop icon from the Control Panel window. ____________________________________________________________ IconSpacing= Default: 77 Purpose: Specifies the number of pixels that will appear horizontally between icons. Increasing this number increases the amount of horizontal space between icons. To change: Choose the Desktop icon from the Control Panel window. ____________________________________________________________ IconTitleFaceName= Default: MS Sans Serif Purpose: Specifies the font used for displaying icon titles. Change this value if the icon title is difficult to read. To change: Use Notepad to edit the WIN.INI file. ____________________________________________________________ IconTitleSize= Default: 8 Purpose: Specifies the size of the font used for displaying icon titles. Change this value if the icon title is difficult to read. To change: Use Notepad to edit the WIN.INI file. ____________________________________________________________ IconTitleStyle=<0-or-1> Default: 0 Purpose: Specifies whether the icon title text should be bold. When the value is set to 1, the icon title text is bold. When the value is set to 0, the icon title appears in regular text. To change: Use Notepad to edit the WIN.INI file. ____________________________________________________________ IconTitleWrap=<0-or-1> Default: 1 Purpose: Specifies whether or not to wrap icon titles. A value of 1 enables icon title wrapping and increases icon vertical spacing by 3 lines. A value of 0 disables icon title wrapping To change: Choose the Desktop icon from the Control Panel window. ____________________________________________________________ IconVerticalSpacing= Default: Windows determines the default value based on the icon title font and the display you are using. Purpose: Specifies the number of pixels that will appear vertically between icons. Increasing this number increases the amount of vertical space between icons. To change: Use Notepad to edit the WIN.INI file. ____________________________________________________________ Pattern= Default: "(None)" (This string appears when no pattern is specified). Purpose: Specifies a pattern that is used to paint the screen background. The eight numeric values define a bitmap eight pixels wide and eight pixels high. Each decimal value represents a byte, and each byte represents a row of eight pixels. The following shows the effect of setting a bit: Setting Effect 0 Sets the corresponding pixel to the background color specified by the Background setting in the [colors] section). 1 Sets the corresponding pixel to the foreground color (specified the WindowText setting in the [colors] section). For example, if you set the value to the decimal value 175, the top row of pixels in the bitmap will appear as the binary equivalent (10101111) according to the preceding table. To change: Choose the Desktop icon from the Control Panel window. ____________________________________________________________ TileWallpaper=<0-or-1> Default: 0 Purpose: Specifies whether to center the desktop wallpaper or tile it across the screen. When this setting is 0 the wallpaper is centered. When this value to 1 the wallpaper is tiled. To change: Choose the Desktop icon from the Control Panel window. ____________________________________________________________ Wallpaper= Default: "(None)" (This string appears when no pattern is specified) Purpose: Supplies the name of a bitmap file. This bitmap appears on the screen background. You need to include the full pathname of the file if it is not in the Windows or system directory. To change: Choose the Desktop icon from the Control Panel window. ____________________________________________________________ [extensions] Section Settings The [extensions] section contains settings that link groups of document files with an application so that opening one of the document files automatically starts the application. The [extensions] section can contain settings of the following type: ____________________________________________________________ = Purpose: Contains a list of filename extensions that identify documents, and corresponding command lines that are invoked when you choose a file that has the associated extensions. The keyname is an extension of one to three characters. The value is an ordinary DOS command line. The command line always begins with an application filename (with the .EXE extension). This can be followed by any command parameters the application needs, usually including the document filename. The caret (^) character can be used when the original document filename is needed in the command line; the caret is replaced by the document filename without any extension. The most typical entries list the application name and the document name; for example: cal=calendar.exe ^.cal If you run a file called MYFILE.CAL after this association has been made, the Calendar progam will start and automatically open the file named MYFILE. To change: Choose Associate from the File menu in File Manager. ____________________________________________________________ [intl] Section Settings The [intl] section describes how to display dates, times, currency amounts, and other items for countries other than the United States. The default values reflect U.S. options. To change any setting in this section, choose the International icon from the Control Panel window. The [intl] section can contain the following settings: ____________________________________________________________ iCountry= Default: 1 Purpose: Specifies the country code. This number matches the country's international telephone code, except for Canada, which is 2. ____________________________________________________________ iCurrDigits= Default: 2 Purpose: Specifies the number of digits to put after the decimal separator in currency. ____________________________________________________________ iCurrency= Default: 0 Purpose: Specifies a currency format according to the following: Value Format __________________________________________________ 0 $2 1 2$ 2 $ 2 3 2 The actual currency symbol is specified by the sCurrency value. ____________________________________________________________ iDate= Default: 0 Purpose: Specifies a numerical date format according to the following: Value Format ___________________________________________________ 0 12/31/90 1 31/12/90 2 90/12/31 The actual date divider is specified by the sShortDate value. This setting is not used by Windows 3.x and exists only for compatibility with Windows 2.x. ____________________________________________________________ iDigits= Default: 2 Purpose: Specifies the number of digits to display after the decimal separator in numbers. ____________________________________________________________ iLZero=<0-or-1> Default: 0 Purpose: Specifies whether to put leading zeros in decimal numbers according to the following: Value Format ____________________________________________________ 0 .7 1 0.7 The actual decimal separator is specified by the sDecimal setting. ____________________________________________________________ iMeasure=<0-or-1> Default: 1 Purpose: Specifies the measurement system according to the following: Value System ___________________________________________________ 0 Metric 1 English ____________________________________________________________ iNegCurr= Default: 0 Purpose: Specifies a negative number format according to the following: Value Format ____________________________________________________ 0 ($1) 1 -$1 2 $-1 3 $1- 4 (1$) 5 -1$ 6 1-$ 7 1$- 8 -1 $ 9 -$ 1 0 $ 1- The actual currency symbol is specified by the sCurrency setting. ____________________________________________________________ iTime= Default: 0 Purpose: Specifies whether to format time using a 12-hour clock or a 24-hour clock. Value Format Meaning 0 1:00 12-hour clock 1 13:00 24-hour clock The actual time separator is specified by the sTime setting. ____________________________________________________________ iTLZero= Default: 0 Purpose: Specifies whether to put leading zeros in time according to the following: Value Format __________________________________________________ 0 9:15 1 09:15 The actual time separator is specified by the sTime setting. ____________________________________________________________ s1159= Default: AM Purpose: Specifies the string that follows times before noon in the 12-hour time format. ____________________________________________________________ s2359= Default: PM Purpose: Specifies the string that follows times after noon in the 12- hour format or that follows all times in the 24-hour format (for example, GMT). ____________________________________________________________ sCountry= Default: United States Purpose: Specifies the name of the country whose standard setting you want to use. ____________________________________________________________ sCurrency= Default: $ Purpose: Specifies the currency symbol you want to use. ____________________________________________________________ sDecimal= Default: . Purpose: Specifies the punctuation used to separate the fractional part of a decimal number from the whole number part. ____________________________________________________________ sLanguage= Default: enu Purpose: Specifies the language you want to work in. Windows applications that provide language-specific tasks, such as sorting or spell-checking, use this setting. The following are the standard values: Value Language dan Danish deu German eng International English enu U.S. English esn Modern Spanish esp Castilian Spanish fin Finnish fra French frc French Canadian isl Icelandic ita Italian nld Dutch nor Norwegian ptg Portuguese sve Swedish ____________________________________________________________ sList= Default: , Purpose: Specifies the character used to separate items in a list. In U.S. English, the most common separator is a comma. ____________________________________________________________ sLongDate= Default: dddd, MMMM dd, yyyy (e.g., Friday, June 1, 1990) Purpose: Specifies your choice for the long date format, including abbreviations for the words and different separators, according to the following: Date Picture Item Format M Month 1-12 MM Month 01-12 MMM Month Jan-Dec MMMM Month January-December d Day 1-31 dd Day 01-31 ddd Day Mon-Sun dddd Day Monday-Sunday yy Year 00-99 yyyy Year 1900-2040 If you want to include the letters d, y, or m in the separator strings, you must enclose the separator strings in single quotation marks, if you are editing the WIN.INI file directly. Control Panel will automatically insert single quotation marks in the correct places. In addition, Control Panel will accept only certain date-picture combinations. Therefore, you should use Control Panel to change this setting. ____________________________________________________________ sShortDate= Default: M/d/yy (e.g., 6/1/90) Purpose: Specifies your choice for the short date format, including abbreviations for the words and different separators, according to the list described above in the sLongDate listing. Control Panel will accept only certain date- picture combinations. Therefore, you should use Control Panel to change this setting. ____________________________________________________________ sThousand= Default , Purpose: Specifies the symbol used to separate thousands in a number with more than three digits. An example, if the value is a comma (,), is 3,000. ____________________________________________________________ sTime= Default: : Purpose: Specifies the character used to separate the hours, minutes, and seconds in time. An example, if the value is a colon (:), is 15:29:31. ____________________________________________________________ [ports] Section The [ports] section lists all available communications and printer ports, and defines default values; it also lists files to which printer output can be sent. The [ports] section can contain up to 10 occurrences of the following setting. Any additional occurrences are ignored by Windows. ____________________________________________________________ :=,,,[[,p]] Purpose: Specifies an available output port. You can specify no more than 10 ports. The keyname must be the name of an output port as it is recognized by MS-DOS. This keyname can be COMx: (serial port, where x represents the port number), LPTx: (a parallel port, where x represents the port number), EPT: (used for a specific IBM printer), LPTx.DOS (a parallel port used to bypass Windows printing and print directly to a port, where x represents the port number), FILE:, or a filename. For COM ports, the value specifies the port's baud rate; the value gives the length of a word (in bits); the value gives the number of stop bits to be used; and the [[,p]] option specifies that hardware handshaking is in effect. LPT (parallel), EPT, FILE, and LPTx.DOSports do not take any parameters. The LPTx.DOS ports are used (instead of the corresponding LPT port) to print directly to the port and bypass the Windows' special output handling. This port is provides compatiblity with Windows version 3.0. Specifying a filename for the will direct output to that file. A filename, unlike the other port names, must not be followed by a colon (:). By using FILE:=, Windows will prompt you to specify a filename for the print file when you print. To change COM port settings: Choose the Ports icon from the Control Panel window. To change or add other ports: Use Notepad to edit the WIN.INI file. ____________________________________________________________ LPT1.DOS= LPT2.DOS= LPT3.DOS= LPT4.DOS= Default: None Purpose: Enables printing directly to a parallel port. Use these settings to bypass Windows' special parallel port output handling when printing. To change: Use Notepad to edit the WIN.INI file. ____________________________________________________________ [fonts] Section Settings The [fonts] section describes one or more font files that are loaded when Windows is started. The [fonts] section can contain one or more occurrences of the following setting: ____________________________________________________________ = Purpose: Specifies a font file. The keyname is the descriptive name of a font. The value is the filename of a file that contains font resources. To change: Choose the Fonts icon from the Control Panel window. ____________________________________________________________ [FontSubstitutes] Section Settings The [FontSubstitutes] section describes fonts which are recognized by Windows as the same typeface. This is useful if you want to work on documents created using Windows 3.0 that include fonts whose names have changed in Windows 3.1. The [FontSubstitutes] section contains one or more occurrences of the following setting: ____________________________________________________________ = Default: Helv=MS Sans Serif Tms Rmn=MS Serif Times=Times New Roman Helvetica=Arial Purpose: Specifies the font that Windows will use in place of another font, only if that font is not installed on your system. For example, if you are viewing a document that is formatted in Helvetica, but Helvetica is not installed on your system, Windows will use Arial to display the document. To change: Use Notepad to edit the WIN.INI file. ____________________________________________________________ [TrueType] Section Settings The [TrueType] section describes options that affect the use and display of TrueType fonts in your Windows applications. The [TrueType] section can contain the following settings: ____________________________________________________________ OutlineThreshold= Default: 256 Purpose: Specifies the number of pels-per-em at which Windows will render TrueType fonts as outline fonts instead of as bitmap fonts. Using bitmap fonts is faster, but requires more memory. If you are low on memory, decrease this value. Do not specify a value over 300. If you do, you might encounter problems using TrueType fonts. To change: Use Notepad to edit the WIN.INI file. ____________________________________________________________ TTEnable=<0-or-1> Default: 1 Purpose: Enables or disables TrueType fonts. Setting this value to 1 enables TrueType fonts so that they are available in your Windows applications. Setting this value to 0 disables TrueType fonts. In this case, TrueType fonts are not available in your applications. To change: Choose the Fonts icon from the Control Panel window. ____________________________________________________________ TTIfCollisions=<0-or-1> Default: 0 Purpose: Specifies whether or not to use TrueType fonts in place of other fonts if both types of fonts are installed on your system and have the same font name. If this value is set to 1, the TrueType font will be used. For example, Windows provides both a bitmap and a TrueType version of the Symbol font. If you set this value to 0, Windows will use the TrueType version. To change: Use Notepad to edit the WIN.INI file. ____________________________________________________________ TTOnly=<0-or-1> Default: 0 Purpose: Specifies whether or not to list only TrueType fonts in the fonts dialog box in Windows applications. If this value is set to 1, only TrueType fonts are listed. If this value is set to 0, all fonts installed on your system are listed. To change: Choose the Fonts icon from the Control Panel window. ____________________________________________________________ [mci extensions] Section Settings The [mci extensions] section contains settings that associate different types of media files with different Media Control Interface device drivers. Whenever a media file is selected, Windows will use the associated driver to play it. The [mci extensions] section can contain one or more occurrences of the following setting: ____________________________________________________________ = Purpose: Associates files that have the specified extension with the specified MCI device driver. Windows uses the specified driver to play the media file associated with it. To change: Use Notepad to edit the WIN.INI file. ____________________________________________________________ [network] Section Settings The [network] section describes network settings and previous network connections. The [network] can contain the following settings: ____________________________________________________________ = Purpose: Shows the network connections that are restored each time Windows is started. To change: Choose the Network Connections command from the Disk menu in File Manager. ____________________________________________________________ InRestoreNetConnect ____________________________________________________________ Restore=<0-or-1> Default: 1 Purpose: Specifies whether or not to reconnect to the network servers you were connected to in your previous Windows session. This setting works for MSNet, Lan Manager Basic, and Lan Manager 2.0. If this value is set to 1, you will be reconnected to the network servers each time you start Windows. If this value is set to 0, you will not be reconnected. To change: Choose the Networks option from the Control Panel window, or if the Network dialog box for your network does not include a reconnect option, use Notepad to edit the WIN.INI file. ____________________________________________________________ = Purpose: Shows the path for a network printer and the port the printer is assigned to. This connection is restored each time Windows is started. To change: Choose the Printers option from the Control Panel window, or the Network Connections command from the Options menu in Print Manager. ____________________________________________________________ [embedding] Section Settings The [embedding] section lists the OLE objects, their description, the program that is used to create them, and their file format. This information also appears in the Registration Info Editor. It is recommended that you use the Registration Info Editor to register applications or edit application information for OLE. The [embedding] section is included in the WIN.INI file only to maintain compatibility with Windows 3.0 and 3.0 applications. The [embedding] section can contain one or more occurrences of the following setting: ____________________________________________________________ =,,, Purpose: Specifies the objects used as servers for OLE. The keyname specifies the name of the server object. The keynames provide a description of the server object. The second description appears in the list of registered file types in the Registration Info Editor. The keyname identifies the path and name of the executable file for the application that is used to create the object. The keyname identifies the format of the file. The value for this setting is most often "picture", which is metafile format. To change: Run the Registration Info Editor (REGEDIT.EXE) from File Manager or from Program Manager. ____________________________________________________________ [Windows Help] Section Settings The [Windows Help] section includes settings that specify the size and placement of the Help window and dialog boxes, as well as the color of text that, when chosen, displays a macro, pop-up window, or new panel. The [Windows Help] section can include the following settings: ____________________________________________________________ M_WindowPosition=,, ,, H_WindowPosition=,, ,, A_WindowPosition=,, ,, C_WindowPosition=,, ,, Purpose: Defines the default size and position of the main Help window, and the History, Annotate, and Copy dialog boxes. The first defines the x coordinate of the upper- left corner. The second defines the y coordinate of the upper-left corner. Both these numbers define the default position of the main Help window, and the History, Annotate, and Copy dialog boxes. The third defines the default width of the Help window and dialog boxes. The fourth defines the default height of the Help window and dialog boxes. Both height and width are measured in pixels. The fifth specifies whether or not the main Help window is maximized. A value of 1 indicates that it is maximized. A value of 0 indicates that the main window is the default height and width. Changing this value has no effect on the size of the dialog boxes, since they cannot be maximized. To change: Move or size the main Help window, or the History, Annotate, or Copy dialog boxes. The values are updated in the WIN.IN file automatically. ____________________________________________________________ JumpColor= Purpose: Specifies the color of text that, when chosen, leads to a new panel of help information. For example, entering 000 000 000 as values results in black text on a white background. To change: Use Notepad to edit the WIN.INI file. ____________________________________________________________ PopupColor= Purpose: Specifies the color of text that, when chosen, displays a pop-up panel (the type of panel used for glossary definitions). For example, entering 000 000 000 as values results in black text on a white background. To change: Use Notepad to edit the WIN.INI file. ____________________________________________________________ MacroColor= Purpose: Specifies the color of text that, when chosen, runs a Help macro. To change: Use Notepad to edit the WIN.INI file. ____________________________________________________________ IFJumpColor= Purpose: Specifies the color of text that, when chosen, leads to a new panel of help information, located in a different help file. To change: Use Notepad to edit the WIN.INI file. ____________________________________________________________ IFPopupColor= Purpose: Specifies the color of text that, when chosen, displays a pop-up panel (the type of panel used for glossary definitions), located in a different help file. To change: Use Notepad to edit the WIN.INI file. ____________________________________________________________ [sounds] Section Settings The [sounds] section lists the system events that support sound and the sound files that are assigned to each event. The [sounds] section can contain one or more occurrences of the following setting: ____________________________________________________________ =, Purpose: Specifies the sound file assigned to and a description of a system event. The is the name of the sound file. The is a text string that describes the system or application event. To change: Choose the Sound icon in the Control Panel window. ____________________________________________________________ [PrinterPorts] Section Settings The [PrinterPorts] section lists the printers Windows can use and the printer driver, port assignment, and timeout values for each printer. The [PrinterPorts] section can contain one or more occurrences of the following setting: ---------------------------------------------------------------- ------ =, , , [[,,, ,...]] Purpose: Specifies driver, port, and timeout information for a printer. The keyname is the name of the printer. The value is the printer driver filename. The value is the name of the port assigned to the printer. If a printer is not assigned to a port the value is the string specified in the NullPort setting (in the [windows] section). The value determines the amount of time (in seconds) allowed for attempted transmission retries. The value determines the number of seconds Print Manager will wait for the device to be switched on. If the timeout values are not specified for a particular port, Windows uses the default settings listed in the [windows] section for that port. Caution: When changing a setting in this section, be sure it does not conflict with a corresponding setting in the [devices] section. Problems may occur if an installed printer does not appear in the [PrinterPorts] section. To change: Choose the Printers icon from the Control Panel window or choose the Printer Setup command from the Print Manager Options menu. ____________________________________________________________ [devices] Section Settings The [devices] section lists the installed printers. The settings in this section match those in the [PrinterPorts] section, without the timeout values. This section is necessary only for Windows version 2.x applications, which look to the [devices] section for this information. The [devices] section can contain one or more occurrences of the following setting: ____________________________________________________________ =, [[,,...]] Purpose: Specifies an installed printer. The keyname is the name of the printer. The value is the printer driver filename. The value specifies the port that is assigned to the printer. If the printer is not currently assigned to a port, the value is the string specified in the NullPort setting (in the [windows] section). Caution: When changing a setting in this section, be sure it does not conflict with a corresponding setting in the [PrinterPorts] section. Problems may occur if an installed printer does not appear in the [PrinterPorts] section. To change: Choose the Printers icon from the Control Panel window or choose the Printer Setup command from the Print Manager Options menu. ____________________________________________________________ [Programs] Section Settings If you use File Manager or Program Manager to open a document file that is associated with a file type in the Registration Database, and File Manager or Program Manager cannot find the program file that starts the application specified by the file type, Program Manager or File Manager will look in the [Programs] section ot the WIN.INI file for the path to the program file. If the path is not in the [Programs] section, Program Manager or File Manager will display a dialog box in which you can specify the path. The path you specify is then added to the [Program] section. The [Program] section can contain one or more occurrences of the following settings: ____________________________________________________________ =:\ Purpose: Specifies the drive, directory, and executable program file needed to start an application. The keyname specifies the name of the program file that Windows was searching for when you tried to open the associated data file. The keyname specifies the drive on which the program file is located. The keyname specifies the directory in which the program file is located. The second keyname specifies the name of the executable program file, located in the specified drive and directory, needed to start the associated application. ____________________________________________________________ [colors] Section Settings The [colors] section defines the colors for components of the Windows display. The colors section can contain settings of the following type: ____________________________________________________________ = Purpose: The , , and values are integers that specify the relative intensities of red, blue, and green, respectively. These settings can range from 0 (minimum intensity) to 255 (maximum intensity). The keyname can be any one of the following: Keyname Refers to ActiveBorder Border of the active window ActiveTitle Active title bar AppWorkspace Application workspace for Windows applications Background Screen background (desktop) ButtonFace Button face ButtonHilight Highlight around the top and left side of buttons ButtonShadow Button shadow ButtonText Button text GrayText Text that is dimmed (as in an unavailable command name) Hilight Background of highlighted text HilightText Highlighted text InactiveBorder Border of the inactive window InactiveTitle Inactive title bar InactiveTitleText Inactive title-bar text Menu Menu background MenuText Menu text Scrollbar Scroll bar TitleText Title-bar text Window Window workspace WindowFrame Window frame WindowText Window text To change: Choose the Color icon from the Control Panel window. Reference(s): Microsoft Windows Resource Kit 3.1, "WININI.WRI". KBCategory: kbref kbdisplay kbsound KBSubcategory: Additional reference words: 3.1 3.10 win31 Top Questions and Answers for Windows 3.1 Article ID: Q85194 The information in this article applies to: - Microsoft Windows operating system version 3.1 ---------------------------------------------------------------- ------ SUMMARY ======= This document is a list of the Top Questions and Answers for Microsoft Windows 3.1. It is distributed via CompuServe, the MSDL, the Microsoft Knowledge Base and other distribution channels. MORE INFORMATION ================ Most Common Questions and Answers Microsoft Windows Operating System Version 3.1 Setup ----- Q: What is the most common reason for an unsuccessful Windows installation? A: Terminate-and-stay-resident programs (TSRs) loaded from the CONFIG.SYS and AUTOEXEC.BAT files are the number one cause of an unsuccessful Windows installation. If you are having difficulty with Windows Setup, insert a system disk in your floppy drive and start your computer. The system disk should contain AUTOEXEC.BAT and CONFIG.SYS with no device drivers or TSRs loaded, unless necessary to access the hard drive. If you use any special drivers for your hard drive, such as Disk Manager or Stacker, make sure the drivers are in your new CONFIG.SYS and AUTOEXEC.BAT files and also on the floppy disk. Q: During installation, when Windows Setup attempts to switch from the MS-DOS-character portion of Setup to the graphical-mode Windows portion of the installation, the hourglass cursor disappears and Setup hangs, or Windows exits to MS-DOS. Why? A: This may happen if there is a corrupted or earlier version of SETUP.INF or SETUP.EXE located in the WINDOWS or WINDOWS\SYSTEM directory. Search these directories and rename either of these files if found. For example, rename SETUP.INF to SETUP.OLD. Then run the Windows Setup program from the Windows disks again. Printing -------- Q: What could be causing printing problems that didn't occur in Windows version 3.0? A: When you set up Windows 3.1, some printer drivers may not get updated correctly. To make sure your printer driver was updated correctly, do the following. 1. Remove the printer driver that you are using from your system. Run Control Panel and choose Printers. Select the printer driver and choose the Remove button. 2. Use File Manager to change to the WINDOWS\SYSTEM directory. Select the printer driver filename and press the DEL key. 3. Reinstall the printer driver by running Control Panel and choosing Printers. Choose the Add button, select your printer, and choose the Install button. NOTE: By reinstalling your printer driver, almost all (90 percent of) TrueType and third-party printing problems will be corrected. Q: When I print in landscape mode on a Linotronic printer, the Encapsulated PostScript (EPS) graphic portions of the document are rotated. Why? A: If you are using the Linotronic or another PostScript printer driver, try adding the following line to the [ModelName,Port] section of the WIN.INI file. This is the section that says [Linotronic 200/230,LPT1], and not the section that says [PostScript,LPT1]: LandScapeOrient=270 Q: Can I print in color using my Hewlett-Packard (HP) DeskJet 500c printer? A: Using the printer driver supplied by Hewlett-Packard, you can print in color using this printer. However, printer drivers supplied by Hewlett-Packard do not support TrueType fonts. If you want to use TrueType fonts, you can use the printer driver that comes with Windows 3.1; however, you won't be able to print in color. Applications ------------ Q: Since upgrading from Windows 3.0 to version 3.1, I can no longer use the OLE features in Excel or Word for Windows. Why? A: If you upgrade from Windows 3.0 to Windows 3.1, and you had installed in Windows 3.0 an application that support OLE), Windows 3.1 may not recognize the OLE database. You need to update the database, which is a file named REG.DAT. To update the REG.DAT file, do the following: 1. From the File menu in Program Manager, choose the Run command. 2. In the Command Line box, type: regedit The Registration Information Editor appears. 3. From the File menu, choose the Merge Registration File. 4. Select the registration file that corresponds to the OLE server application you are using. For example, if you are using Microsoft Publisher, choose MSPUB.REG. 5. Choose the OK button. Q: When I tried to upgrade to Windows 3.1 using DR-DOS 6.0, I received the following error message. Why? Standard Mode: Fault in MS-DOS Extender A: Microsoft can only ensure the stability of Windows 3.1 running on MS-DOS or PC-DOS versions 3.1 or later. Digital Research has announced the availability of a software update for running Windows with DR-DOS. Microsoft neither endorses nor ensures the stability of Windows 3.1 running on DR-DOS either with or without the Digital Research software update. Q: Does SMARTDrive make my system run more slowly in Windows 3.1? A: If SMARTDrive is set up to use double buffering, it is going to run more slowly than without double buffering. To make SMARTDrive faster when it is using double buffering, try adding the /L switch to the SMARTDrive command line in your AUTOEXEC.BAT file. This switch forces SMARTDrive to load its buffer "low," into conventional memory. Note: When your hard disk requires the use of double buffering, Windows places a SMARTDrive command in your CONFIG.SYS file as well as in your AUTOEXEC.BAT file. You must place the /L switch on the command line in your AUTOEXEC.BAT file. Q: In my CONFIG.SYS file, I have the line: DEVICE=C:\WINDOWS\SMARTDRV.EXE /DOUBLE_BUFFER Why is it there? And why can't I run Windows in 386 enhanced mode even through I have a 386 computer with 4 megabytes of memory? A: When Windows is set up, it tests to see if it can understand the hard drive. If the hard drive uses a SCSI controller or a caching controller, then Windows adds the line DEVICE=C:\WINDOWS\SMARTDRV.EXE /DOUBLE_BUFFER to CONFIG.SYS. Sometimes, double buffering may not be activated even though you have the line in CONFIG.SYS. If you have a SCSI controller and double buffering is not active, then you may not be able to run Windows in 386 enhanced mode. To force double buffering, add a + to the end of the SMARTDrive (SMARTDRV.EXE line): DEVICE=C:\SMARTDRV.EXE /DOUBLE_BUFFER+ Usage ----- Q: Why doesn't my Novell NWPOPUP.EXE messaging utility initialize properly? When I exit Windows I get all my messages. A: If you are running Windows in 386 enhanced mode and a version of Novell NetWare's NWPOPUP.EXE with a file date earlier than 3/10/92 is in your WINDOWS directory, or if NWPOPUP.EXE is located in a directory prior to the Windows directory entry in the PATH= statement, then NWPOPUP.EXE will get loaded and will not initialize properly under Windows 3.1. It may also be necessary to try placing the following line in the [386Enh] section of your SYSTEM.INI file: TimerCriticalSection=10000 This increases the amount of time (specified in milliseconds) before the critical section is timed out. Q: I am the system administrator for a Novell network. Most of my workstations run with no problem, but two of my workstations only run in standard mode and not in 386 enhanced mode. If I do not log onto the network, then I can run in 386 enhanced mode. A: There are four possible causes to the problem you are experiencing: - incorrect network software drivers - IRQ conflict - RAM address conflict - Base address conflict 1. Read the NETWORKS.WRI file for the steps necessary to upgrade your current versions of IPX and NETX. If necessary contact your network card manufacturer if you need new low-level drivers. 2. Most machines do not support having two devices using the same IRQ at the same time. This means that if you are using your network card on IRQ3 or IRQ4, then you will have to either disable COM2 or COM1, which use the same respective IRQ, or reconfigure the network card for a free IRQ. On most machines, IRQ5 and IRQ2 are free, meaning no other hardware device is attempting to use them. 3. Many network cards use a RAM address in the Upper Memory area between 640K and 1024K. If your card is using this range, then exclude use of this range with EMM386.EXE or an EMMEXCLUDE statement in the SYSTEM.INI file's [386Enh] section. Some cards will not function properly at D000 and need to be reconfigured for D800. 4. Many hardware devices have Base memory addresses (for example, COM ports). There may be a conflict with an existing device. Try reconfiguring the network card for an address of 300h or greater. Q: When I choose the Ports icon in Control Panel, the Advanced button in the Ports dialog box is unavailable (dimmed). Why is this? A: If the Windows 3.1 COMM.DRV file is not installed correctly, the Advanced button in the Ports dialog box will be unavailable. If you upgrade from Windows 3.0 to 3.1 and you were using a third-party communications driver in 3.0, the Windows 3.1 Setup program will not update the communications driver. To make sure your COMM.DRV file is installed correctly, try the following: 1. Make sure you have the following setting in the [boot] section of your SYSTEM.INI file: COMM.DRV=COMM.DRV 2. Using the MS-DOS expand command (installed in the WINDOWS directory of your hard drive during Windows setup), reinstall the COMM.DRV from the Windows Setup disks (Disk 1 for 3.5-inch disks; Disk 2 for 5.25-inch disks) into the SYSTEM subdirectory of your WINDOWS directory by typing the following: expand a:\comm.dr_ c:\windows\system\comm.drv Q: Can I set up a permanent or temporary swap file on a "stacked" disk drive? A: Windows 3.1 does not support the use of a permanent or temporary swap file on a "stacked" drive. A stacked drive is one on which you are running the Stac Electronics' Stacker utility. Q: I have a sound card that plays the Windows file CANYON.MID, but when I choose the Sound icon from Control Panel, all of the dialog box selections are unavailable (dimmed). Why? A: You are using a sound card that is a MIDI synthesizer. You must use a card that supports the playing of audio files (files with the .WAV filename extension). For example, if you are using the original Adlib Music Synthesizer Card, it must be upgraded to the Adlib 2000 or Gold card. Error Messages: Q: When I start File Manager, I see the following error message. What causes this? Cannot read from drive I. A: An MS-DOS version 4.x file named GRAPHICS.COM might be the cause. Try removing from your AUTOEXEC.BAT file the command line that specifies GRAPHICS.COM. If you choose the OK button when you receive this error message, File Manager displays all of your drives; however, it cannot access any of your files. The MS-DOS version 5.0 GRAPHICS.COM file does not cause this problem. Q: What should I do when I receive the "Inadequate DPMI server" error message? A: This error message appears when the files KRNL386.EXE and WIN386.EXE are from different versions of Windows (when one is from 3.0 and the other from 3.1). To see if this is the problem, check the dates on the these files. They are located in the SYSTEM subdirectory of your WINDOWS directory. It is possible that an older version of these files may be in the path or the WINDOWS directory; search the entire path for these files. If necessary, use the MS-DOS expand command to reinstall the files from the Windows Setup program. (The expand command is installed in the WINDOWS directory of your hard drive during Windows setup.) This error message can also appear when your system memory-configuration settings (sometimes referred to as CMOS settings) don't match the amount of memory the system actually has. The way you change the settings depends on the type of hardware you have. For more information about changing these settings, see your hardware documentation. Q: When switching to the MS-DOS Prompt from Windows, I receive the following error message: Incorrect system version. Please install the 386 Enhanced section and run Setup again. What does this mean and what should I do? A: There are two possible solutions to this problem: 1. An old WINOA386.MOD may be located in the WINDOWS directory or the path. Delete the old file and use the MS-DOS expand command to expand an updated version from the Windows 3.1 disks by typing: expand a:\winoa386.mo_ c:\windows\system\winoa386.mod (The expand command is installed in the WINDOWS directory of your hard drive during Windows setup.) 2. In the SYSTEM.INI file, there are three lines that specify what kind of video driver Windows uses when running in 386 enhanced mode. These are 386Grabber= and display.drv= (located in the [boot] section) and display= (located in the [386Enh] section). The "Incorrect system version" error message usually occurs when one of these entries is not consistent with the others. To reset these drivers: 1. Exit Windows and change to the WINDOWS directory. 2. Type setup and press ENTER. 3. Select the current Display option and press ENTER. 4. From the Display list box, select VGA (version 3.0) and press ENTER. 5. If you are asked to use an existing driver, press the ESC key to load new drivers. Q: When running Windows, why do I get the following error message "Call to Undefined Dynalink"? A: This error is usually caused by an old .DLL file located in the WINDOWS directory. The most common one is TOOLHELP.DLL. Locate this file and rename it. Then, restart Windows. The correct version of this file is located in the WINDOWS\SYSTEM directory and has a date of 3/10/92 and a size of 14128. This problem can also occur with an earlier version of SHELL.DLL, OLECLI.DLL, OLESVR.DLL, and COMMDLG.DLL. All of these file should be located in the WINDOWS\SYSTEM directory and have a date of 3/10/92. KBCategory: kbprint kbdisplay kbsound kb3rdparty kbref kbtool kbnetwork kbsetup kbusage KBSubcategory: win31 Additional reference words: 3.10 3.1 Windows 3.1 Err Msg: Error Loading PROGMAN.EXE Article ID: Q85862 ---------------------------------------------------------------- ------ The information in this article applies to: - Microsoft Windows operating system versions 3.0, 3.0a, 3.1, 3.11 - Microsoft Windows for Workgroups versions 3.1, 3.11 - Microsoft MS-DOS operating system versions 6.0, 6.2, 6.21, 6.22 ----------------------------------------------------------------- ----- SYMPTOMS ======== You may receive the following error message when you try to start Microsoft Windows or run Microsoft Windows Setup: Error Loading PROGMAN.EXE CAUSE ===== The following can cause of this error message: - An incorrect or missing SHELL= line in the [boot] section of the SYSTEM.INI file - An incorrect version of the SHELL.DLL file - VSafe program - A CHKLIST.MS file in the Windows directory - The [boot] section heading is missing in your SYSTEM.INI file. - The PROGMAN.INI file is corrupt. MORE INFORMATION ================ The following sections cover the different causes of the above error message. Incorrect or Missing SHELL= Line -------------------------------- You receive the error message if the SHELL= line in the [boot] section of your SYSTEM.INI file is missing or is set to a file that does not exist. Under Windows version 3.0, you receive an unrecoverable application error (UAE) if the SHELL= line is missing or set incorrectly. The SHELL= line in the [boot] section of the SYSTEM.INI file should read as follows: SHELL=PROGMAN.EXE If this error continues, or if an undefined dynalink error occurs, check the [boot] section in the SYSTEM.INI file for the line referring to SYSTEM.DRV=. This line must be present and should read as follows (unless it is modified by a third-party application, such as Adobe Type Manager): SYSTEM.DRV=SYSTEM.DRV Incorrect Version of SHELL.DLL ------------------------------ Earlier releases of the SHELL.DLL file may prevent Program Manager from starting. Use the EXPAND utility (EXPAND.EXE) to expand the correct version of SHELL.DLL to the Windows SYSTEM directory. The following is an example of the command to be used with the EXPAND utility from Windows 3.1: expand :shell.dl_ :\windows\system\shell.dll The drive letters ( and in this example) vary depending on the location of the source and destination of your files. SHELL.DL_ can be found on Disk 5 (5.25-inch) or on Disk 4 (3.5-inch) of the Windows 3.1 operating system disks. Earlier versions of PROGMAN.EXE do not work with the new SHELL.DLL file. Use the EXPAND command to expand the correct version of PROGMAN.EXE to the Windows directory. For example, if you are expanding PROGMAN.EX from a disk in drive a to C:\WINDOWS, type the following command: expand a:progman.ex_ c:\windows\progman.exe The drive letters ( and in this example) vary depending on the location of the source and destination of your files. PROGMAN.EX_ can be found on Disk 4 (5.25-inch) or on Disk 4 (3.5-inch) of the Windows 3.1 operating system disks. VSafe Virus-Scanning Software ----------------------------- The VSAFE.SYS and/or VSAFE.COM virus-protection programs can cause the above error message. To correct this problem, remove VSAFE.SYS from the CONFIG.SYS file, and remove VSAFE.COM from the LOAD= line in the WIN.INI file and your Startup group. CHKLIST.MS File in the Windows Directory ---------------------------------------- Microsoft Anti-Virus creates CHKLIST.MS files and places them in almost every directory that it checks. If a CHKLIST.MS file is placed in the Windows directory, the error message above is generated. To correct this problem, delete the CHKLIST.MS file from your Windows directory. NOTE: The file may be reinserted in the directory the next time you use Anti-Virus; you must delete the file again if the error message reappears. The [boot] Section Heading is Missing in Your SYSTEM.INI File ------------------------------------------------------------- To correct this problem use a text editor such as Microsoft MS-DOS Editor to edit the SYSTEM.INI file and add the correct heading. The PROGMAN.INI File is Corrupt -------------------------------- To correct this problem use a text editor such as Microsoft MS-DOS Editor to edit the PROGMAN.INI file and correct entries. KBCategory: kbsetup kbtool KBSubcategory: win30 win31 wfw wfwg msav Additional reference words: 3.0 3.00 3.00a 3.0a 3.10 3.1 6.00 6.20 install installing setup.exe Problems When Exiting Windows or WFWG After Running 386 Enh Article ID: Q86705 ---------------------------------------------------------------- --------- The information in this article applies to: - Microsoft MS-DOS operating system versions 5.x, 6.x - Microsoft Windows operating system versions 3.1, 3.11 - Microsoft Windows for Workgroups versions 3.1, 3.11 ---------------------------------------------------------------- --------- SYMPTOMS ======== When you quit Windows or Windows for Workgroups after running in 386 enhanced mode, the system stops responding (hangs). CAUSE ===== This problem can occur when one or more of the following conditions exist: - Your system does not properly support loading MS-DOS high (DOS=HIGH) in the CONFIG.SYS file. - Your system is using an incorrect A20 handler for HIMEM.SYS. - You are using a WINSTART.BAT file. - Your system has a upper memory block (UMB) conflict. - Your network interface card (NIC) is not correctly terminated. - You are loading a network card driver (such as 3C509.COM) after running NET START (typically in your AUTOEXEC.BAT file). STATUS ====== Microsoft has confirmed this to be a problem in Windows versions 3.1 and 3.11 and Windows for Workgroups versions 3.1 and 3.11. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available. WORKAROUND ========== To work around this problem: - Remove DOS=HIGH from your CONFIG.SYS file and restart the system. - Try using a different A20 handler. For more information about A20 handlers, see your MS-DOS "User's Guide." - Discontinue using a WINSTART.BAT file to load memory-resident programs; load them from your AUTOEXEC.BAT file instead. - Run MemMaker or perform other step to resolve any potential UMB conflicts. For more information on UMB conflicts, query on the following words in the Microsoft Knowledge Base: umb and ms-dos and conflict and emm386.exe and tshoot MORE INFORMATION ================ For more information about WINSTART.BAT, refer to your Microsoft Windows or Windows for Workgroups "User's Guide." KBCategory: kbnetwork kbbuglist kbtshoot kb3rdparty kbenv KBSubcategory: winmem win31 wfw wfwg Additional reference words: 3.10 3.11 5.00 5.00a 6.00 6.20 6.21 6.22 exit exiting quit quiting tshoot Novell MLID What Is a Clean Boot for Windows 3.1? Article ID: Q87290 ---------------------------------------------------------------- ------ The information in this article applies to: - Microsoft Windows operating system versions 3.1, 3.11 ---------------------------------------------------------------- ------ SUMMARY ======= A "clean boot" (starting your computer after all unnecessary commands have been removed from your CONFIG.SYS and AUTOEXEC.BAT files) is used as a basic troubleshooting step to test possible conflicts between Windows 3.1 and various terminate-and-stay-resident (TSR) programs and device drivers. There are different types of clean boots; the correct one to use depends on whether or not Microsoft Windows has been installed. More information about clean booting can be found on pages 99-100 of the "Getting Started with Microsoft Windows" version 3.1 manual and on pages 528-531 of the version 3.1 "Microsoft Windows Users Guide." NOTE: This article explains how to clean boot your system up to the point when you start Windows. To start Windows without loading any third-party programs, you must clear the StartUp group, clear the LOAD= and RUN= entries in the WIN.INI file, and ensure the SHELL= entry in the SYSTEM.INI file is loading PROGMAN.EXE. Also, make sure the SYSTEM.INI file does not include third-party virtual device drivers (VxDs) or other third-party Windows components. MORE INFORMATION ================ Before Clean Booting -------------------- Create a bootable floppy disk that contains the MS-DOS system files and any other files that are required to make the system operational, such as disk-compression utilities (for example, Stacker), disk partitioning drivers (for example, Disk Manager), and other third-party device drivers. To Clean Boot Before Running Windows 3.1 Setup ---------------------------------------------- If there is no disk compression software, disk partitioning software, or other third-party drivers necessary to boot the computer, the machine can be booted on a floppy disk that contains only the MS-DOS system files, without a CONFIG.SYS or AUTOEXEC.BAT file. If there is disk partitioning, disk compression, or other third-party software required to boot the computer, the startup files on the disk created above should appear as follows: CONFIG.SYS AUTOEXEC.BAT ---------- ------------ FILES=45 PROMPT $P$G BUFFERS=20 AFTER Windows 3.1 is installed, a clean boot should appear as follows: CONFIG.SYS AUTOEXEC.BAT ---------- ------------ FILES=45 PROMPT $P$G BUFFERS=20 PATH=C:\WINDOWS;C:\DOS;C:\ DEVICE=C:\\HIMEM.SYS SET TEMP=C:\ STACKS=9,256 SHELL=C:\\COMMAND.COM /E:1024 /P Exceptions ---------- The following are examples of drivers that SHOULD NOT be removed; they are used when the computer is turned on to make the hard drive accessible. This is not a complete list, but it does include most of the commonly used drivers: Hard Disk Drivers: SQY55.SYS, SSTBIO.SYS, SSTDRIVE.SYS, AH1544.SYS, ILIM386.SYS, ASPI4DOS.SYS, SCSIHA.SYS, SCSIDSK.EXE, SKYDRVI.SYS, ATDOSXL.SYS, NONSTD.SYS Disk Partitioners: DMDRVR.BIN, SSTOR.SYS, HARDRIVE.SYS, EDVR.SYS, FIXT_DRV.SYS, LDRIVE.SYS, ENHDISK.SYS Disk Compression Utilities: STACKER.COM, SSWAP.COM, SSTOR.EXE, DEVSWAP.COM If the purpose of a device driver or program is unknown, DO NOT remove it. Most device drivers and programs will display a message describing their purpose when they are initialized. A clean boot DOES NOT include: - DOS=HIGH,UMB - EMM386.EXE - INSTALL=SHARE.EXE - INSTALL=FASTOPEN.EXE - Third-party memory managers - RAM disk devices - JOIN, GRAPHICS, PRINT, SUBST, APPEND - MODE for printer redirection - Multiple path statements - MS-DOS-level mouse drivers - Third-party disk caches - Various third-party TSRs - LOGIMENU, CLICK - Virus checkers - Drivers for scanners/fax - Drivers for CD ROM/network - Tape backup spoolers/redirectors/buffers - Data acquisition units - Keyboard accelerators/buffers For information on clean booting Windows 3.0, query on the following words in the Microsoft Knowledge Base: clean and boot and windows and 3.0 KBCategory: kbdisplay kbtlc kbtshoot KBSubcategory: win31 Additional reference words: tshoot clean-boot PRINT.COM RAMDRIVE.SYS JOIN.EXE PRINT.EXE MODE.COM GRAPHICS.COM SUBST.EXE 3.10 3.11 cleanboot WFWG Err Msg: Error 6118: The List of Servers for This... Article ID: Q90215 ---------------------------------------------------------------- ---- The information in this article applies to: - Microsoft Workgroup Connections version 1.0 - Microsoft Workgroup Add-On for MS-DOS, version 3.11 - Microsoft Windows for Workgroups version 3.11 ---------------------------------------------------------------- ---- SYMPTOMS ======== On a machine running Workgroup Connections, Workgroup Add-On for MS-DOS, or Windows for Workgroups 3.11, you receive the following error message: Error 6118: The list of servers for this workgroup is not currently available. Under Windows for Workgroups 3.11, you may also receive the following error message: The list of servers for this workgroup is not currently available. In this case, you can see the workgroup but not the individual computers in the workgroup. You may be able to see the computers under other workgroups. You can connect to a server by manually typing in the path, but you cannot browse a list of available servers. Or, other computers are able to browse the network but not all workstations show up on the browse list. CAUSE ===== These errors can occur if you browse or run NET VIEW when connecting to network drives and one of the following conditions exists: - Your machine has file and print sharing disabled (Windows for Workgroups only). -or- - There is a space character in the workgroup name. -or- - There are no browse master machines on the network (Windows for Workgroups only). -or- - You are using the Windows for Workgroups basic redirector and you have ten network connections established. If there is no master or backup browser present in the workgroup, you cannot see individual computers in a workgroup when you browse. You may see the computers in other workgroups if there is a browser present in that workgroup. If there is only one workgroup present on the network and there is no browser present, you see the workgroup listed but no servers. WORKAROUND ========== To work around this problem: - Enable file and/or print sharing. -or- - Remove the space character from the workgroup name. -or- - Type the following at the MS-DOS command prompt and then press ENTER: net view /workgroup:"work group" NOTE: The quotation marks are not optional. -or- - Use a text editor (such as MS-DOS Editor or Windows for Workgroups Notepad) to edit the SYSTEM.INI file on one machine in the workgroup and add the following entry to the [Network] section: MaintainServerList=yes You can also set a second computer in the workgroup to Auto and the remainder at "no." On each computer that you edit the SYSTEM.INI file, you must quit and restart Windows for Workgroups. -or- - Disconnect from one or more network servers. MORE INFORMATION ================ MaintainServerList controls the ability of the computer to act as a browse master. If this entry is set to Auto, the computer acts as a backup browser or master browser as needed. If the entry is set to Yes, the computer acts as the master browser. If the entry is set to No, the computer acts as neither. There must be at least one computer acting as a browser in the workgroup in order for you to be able to browse. REFERENCES ========== Microsoft Windows for Workgroups version 3.11 SYSINI.WRI file Windows for Workgroups "Resource Kit Addendum for Operating System Version 3.11," Chapter 1, page 44 and Chapter 4, page 15. KBCategory: kbnetwork KBSubcategory: wc wg wfw wfwg wgao Additional reference words: 3.10 3.11 err msg errmsg browsemaster double- click domain workgroup name connect network drive dialog box File Manager net use 10 What Is a Clean Boot for Windows for Workgroups? Article ID: Q90511 ---------------------------------------------------------------------- The information in this article applies to: - Microsoft Windows for Workgroups versions 3.1, 3.11 ---------------------------------------------------------------- ------ SUMMARY ======= A "clean boot" (starting your computer after all unnecessary commands have been removed from your CONFIG.SYS and AUTOEXEC.BAT files) is used as a basic troubleshooting step to test possible conflicts between Windows for Workgroups and various terminate-and-stay-resident (TSR) programs and device drivers. There are different types of clean boots; the correct one to use depends on whether or not Windows for Workgroups has been installed. For more information on clean booting, see Chapter 6 of the "Getting Started with Microsoft Windows for Workgroups" version 3.1 manual and Chapter 11 of the version 3.1 "Microsoft Windows for Workgroups Users Guide." NOTE: This article explains how to clean boot your system up to the point when you start Windows. To start Windows without loading any third-party programs, you must clear the StartUp group, clear the LOAD= and RUN= entries in the WIN.INI file, and ensure the SHELL= entry in the SYSTEM.INI file is loading PROGMAN.EXE. Also, make sure the SYSTEM.INI file does not include third-party virtual device drivers (VxDs) or other third-party Windows components. MORE INFORMATION ================ Before Clean Booting -------------------- Create a bootable floppy disk that contains the MS-DOS system files and any other files that are required to make the system operational, such as disk- compression utilities (for example, Stacker), disk partitioning drivers (for example, Disk Manager), and other third-party device drivers. To Clean Boot Before Running Windows Setup ------------------------------------------ If there is no disk compression software, disk partitioning software, or other third-party drivers necessary to start the computer, the machine can be started from a floppy disk that contains only the MS-DOS system files, without a CONFIG.SYS or AUTOEXEC.BAT file. If there is disk partitioning, disk compression, or other third-party software required to boot the computer, the startup files on the disk created above should appear as follows: CONFIG.SYS AUTOEXEC.BAT ---------- ------------ FILES=45 PROMPT $P$G BUFFERS=20 Windows for Workgroups 3.1 Clean Boot ------------------------------------- AFTER Windows for Workgroups version 3.1 is installed, a clean boot should appear as follows: CONFIG.SYS AUTOEXEC.BAT ---------- ------------ FILES=45 NET START BUFFERS=20 PROMPT $P$G DEVICE=C:\\HIMEM.SYS PATH C:\Windows;C:\DOS;C:\ SET TEMP=C:\ DEVICE=\PROTMAN.DOS /I: DEVICE=.DOS DEVICE=WORKGRP.SYS SHELL=C:\\COMMAND.COM /E:1024 /P STACKS=9,256 Windows for Workgroups 3.11 Clean Boot -------------------------------------- AFTER Windows for Workgroups version 3.11 is installed, a clean boot should appear as follows: CONFIG.SYS AUTOEXEC.BAT ---------- ------------ FILES=45 NET START BUFFERS=20 PROMPT $P$G DEVICE=C:\\HIMEM.SYS PATH=C:\Windows;C:\DOS;C:\ SET TEMP=C:\ DEVICE=IFSHLP.SYS SHELL=C:\\COMMAND.COM /E:1024 /P STACKS=9,256 Exceptions ---------- The following are examples of drivers that SHOULD NOT be removed; they are used when the computer is turned on to make the hard drive accessible. This is not a complete list, but it does include most of the commonly used drivers: Hard Disk Drivers: SQY55.SYS, SSTBIO.SYS, SSTDRIVE.SYS, AH1544.SYS, ILIM386.SYS, ASPI4DOS.SYS, SCSIHA.SYS, SCSIDSK.EXE, SKYDRVI.SYS, ATDOSXL.SYS, NONSTD.SYS. Disk Partitioners: DMDRVR.BIN, SSTOR.SYS, HARDRIVE.SYS, EDVR.SYS, FIXT_DRV.SYS, LDRIVE.SYS, ENHDISK.SYS. Disk Compression Utilities: STACKER.COM, SSWAP.COM, SSTOR.EXE, DEVSWAP.COM If the purpose of a device driver or program is unknown, DO NOT remove it. Most device drivers and programs will display a message describing their purpose when they are initialized. A clean boot DOES NOT include: - DOS=HIGH,UMB - EMM386.EXE - INSTALL=SHARE.EXE - INSTALL=FASTOPEN.EXE - Third-party memory managers - RAM disk devices - JOIN, GRAPHICS, PRINT, SUBST, APPEND - MODE for printer redirection - Multiple path statements - MS-DOS-level mouse drivers - Third-party disk caches - Various third-party TSRs - LOGIMENU, CLICK - Virus checkers - Drivers for scanners/fax - Drivers for CD ROM/network - Tape backup spoolers/redirectors/buffers - Data acquisition units - Keyboard accelerators/buffers For information on clean booting Windows 3.0, query on the following words in the Microsoft Knowledge Base: clean and boot and windows and 3.0 KBCategory: kbusage kbdisplay kbtshoot KBSubcategory: wfwg Additional reference words: 1.0 1.00 3.10 3.11 LAN Manager LANman clean- boot PRINT.COM RAMDRIVE.SYS JOIN.EXE PRINT.EXE MODE.COM GRAPHICS.COM SUBST.EXE cleanboot tshoot Windows for Workgroups Hangs at Logo Screen Article ID: Q92873 ----------------------------------------------------------------- --- The information in this article applies to: - Microsoft Windows for Workgroups versions 3.1, 3.11 ---------------------------------------------------------------- ---- SYMPTOMS ======== Your computer stops responding (hangs) when the Windows for Workgroups logo screen is displayed. CAUSE ===== This problem can occur if either your network card or Windows for Workgroups installation is configured incorrectly. After you upgrade to Windows for Workgroups, the network card may not respond, which causes your system to hang. WORKAROUND ========== To isolate and correct this problem, follow these steps: 1. Turn the machine off completely and then restart the machine (cold boot). This forces the network card to reinitialize and may correct the problem. 2. If you are running Windows for Workgroups version 3.1, start Windows in standard mode (at the MS-DOS command prompt, type "win /s" without the quotation marks). If you are running Windows for Workgroups 3.11, use "win /d:t" (without the quotation marks). If this corrects the problem, you may need to exclude the network card adapter memory range by adding the following statement to the [386Enh] section of your SYSTEM.INI file EMMEXCLUDE=xxxx-zzzzz where xxxx-zzzz is the specific memory range for the network adapter. Use the value A000-EFFF for troubleshooting purposes. You may also need to exclude this memory range from your memory manager (for example, EMM386.EXE X=A000-EFFF). 3. The system may also hang if the network adapter is configured incorrectly. The configuration settings include IRQ, Base I/O port, and Base Memory Address. To correct your settings under Windows for Workgroups 3.1, delete the PROTOCOL.INI, PROTMAN.DOS, WORKGRP.SYS, and other Workgroup network driver files. Then, from Control Panel, choose the Network icon, and indicate the correct network adapter and configuration settings. To correct your settings under Windows for Workgroups 3.11: a. Start Windows for Workgroups by typing "win /n" (without the quotation marks) and then press ENTER. b. In the Network group, choose the Network Setup icon. c. Configure Windows for Workgroups for No Network and exit Windows for Workgroups. d. Rename the PROTOCOL.INI file to PROTOCOL.PSS. For example, type "ren c:\windows\protocol.ini c:\windows\protocol.pss" (without the quotation marks) at the MS-DOS command prompt and then press ENTER. e. Run Windows for Workgroups. f. In the Network group, choose the Network Setup icon. g. Configure Windows for Workgroups for the appropriate network card using the correct settings. h. Exit and restart Windows for Workgroups. NOTE: Each time the PROTOCOL.INI file is updated, the old one is saved with a sequentially numbered extension (that is, PROTOCOL.000, PROTOCOL.001, PROTOCOL.002, and so forth). Using this naming convention, you may be able to recover an earlier PROTOCOL.INI that was configured correctly. 4. Windows may hang if you have installed the incorrect NDIS NIC network card driver in your CONFIG.SYS file. To verify that the driver you selected matches the network card you are using, choose the Network icon from Control Panel. If the network card you are using is not listed during Setup, check the manufacturer's suggested emulation. The network card supplier may need to provide an NDIS-compatible driver. If the card you are trying to install is not listed in Control Panel, contact your network card manufacturer to obtain a specific NDIS driver that works with Windows for Workgroups. The order of the network drivers in the CONFIG.SYS file is also important. For example, protocol manager (PROTMAN.DOS) must be loaded before any other Windows for Workgroup network drivers. If PROTMAN.DOS is not loaded first, you may receive various error messages referring to the protocol manager. For troubleshooting purposes, remove the Windows for Workgroups network drivers from the CONFIG.SYS and AUTOEXEC.BAT files. When you start Windows for Workgroups, you should receive a message about no network functionality. Accept the message and continue loading Windows for Workgroups. 5. If you still experience the problem, check to make sure that the adapter is seated properly in the expansion slot. Check for other hardware-related problems such as incorrect cabling, improper installation of T-connectors and terminators, and other connections within the workgroup. For more information, query on the following words in the Microsoft Knowledge Base: protocol and manager and reported and binding and eliminate KBCategory: kbnetwork kbsetup kbenv kbprb kbtshoot KBSubcategory: wfw wfwg Additional reference words: 3.10 3.11 protman halt tshoot Troubleshooting 'Segment Load Failure' Errors Article ID: Q94380 ---------------------------------------------------------------- ---- The information in this article applies to: - Microsoft Windows operating system versions 3.0, 3.0a, 3.1, 3.11 - Microsoft Windows for Workgroups versions 3.1, 3.11 ---------------------------------------------------------------- ---- SUMMARY ======= Microsoft Windows loads programs into memory in segments (64K blocks of memory) marked fixed, movable, or discardable. Windows can unload discardable segments when it needs more memory for other applications. When an application needs to access a segment of code that is not in memory, Windows loads it from the hard disk. If Windows cannot load the segment for some reason, it generates a "Segment Load Failure" error. MORE INFORMATION ================ "Segment Load Failure" errors are generated if a discarded code segment has been damaged or moved, or if Windows lacks the system resources to load a file, as in the case when there are not enough MS-DOS file handles. "Segment Load Failure" errors may also be caused by corrupt binary files. Reinstalling Windows or Windows for Workgroups into a new directory or over itself may alleviate the error. You can troubleshoot "Segment Load Failure" errors in the same manner that you would troubleshoot a general protection (GP) fault or an unrecoverable application error (UAE). For more information on these troubleshooting procedures, query on the following words in the Microsoft Knowledge Base: gp and tshoot KBCategory: kbother kbtshoot KBSubcategory: win30 win31 wfw wfwg winmem Additional reference words: gpf 3.00 3.00a 3.10 howto moveable 3.11 WFWG Err Msg: Windows 3.x Could Not Be Located... Article ID: Q95087 ---------------------------------------------------------------- -------- The information in this article applies to: - Microsoft Windows for Workgroups versions 3.1, 3.11 - Microsoft Windows operating system version 3.11 ---------------------------------------------------------------- -------- SYMPTOMS ======== When you upgrade from Microsoft Windows version 3.0 or 3.1 to Windows for Workgroups or Windows version 3.11, you receive the following error message: Windows 3.x could not be located on your computer. This version of Windows for Workgroups requires that Windows 3.x already be installed. You must either install Windows 3.x onto your computer, or purchase the complete version of Windows for Workgroups. CAUSE ===== This problem can occur if: - You do not have the appropriate version of Windows 3.0 or 3.1 installed on the computer for Windows or Windows for Workgroups to install properly. -or- - You are using an original equipment manufacturer (OEM) version of Windows 3.1 that was preinstalled and has the WIN.COM file renamed. For example, this problem occurs on some Toshiba laptops (because WIN.COM is renamed as WIN_.COM). This problem also occurs on some Acer Power 500 computers (because WIN.COM is renamed as WINDOWS.COM). -or- - The SYSTEM.INI file contains the line: SETUPSTATE=1 -or- - The SHELL= entry in the [boot] section of the SYSTEM.INI file refers to WINSETUP.EXE. WORKAROUND ========== 1. Install the appropriate version of Windows on your computer. 2. Use any text editor (such as Notepad) to edit the SYSTEM.INI file and delete the "SETUPSTATE=" line from the [boot.description] section of the file (if it is present). 3. Change the "SHELL=" line in the [boot] section of the SYSTEM.INI file from shell=winsetup.exe to: shell=progman.exe 4. Save and then close the file. 5. Install the upgrade or add-on again. If you have an OEM version of Windows, you may need to use the following steps: 1. Rename WIN_.COM or WINDOWS.COM (in the Windows directory) to WIN.COM. 2. Run Setup. 3. Rename WIN.COM back to WIN_.COM or WINDOWS.COM. MORE INFORMATION ================ The upgrade for Microsoft Windows version 3.0 and the add-on for Microsoft Windows version 3.1 require that the appropriate version of Windows 3.0 or 3.1 be installed on the computer for Windows for Workgroups to install properly. The upgrade and add-on Setup programs allow the Windows for Workgroups files to be placed in the existing Windows directory or in a new directory. The upgrade for Microsoft Windows version 3.0 users installs a full version of Windows for Workgroups on computers running Windows 3.0. The add-on for Microsoft Windows version 3.1 installs a full version of Windows for Workgroups on computers running Windows 3.1. KBCategory: kbsetup kbdisplay kberrmsg kb3rdparty kbtlc KBSubcategory: win31 wfw wfwg Additional reference words: 3.10 3.11 peer quick short partial win30 addon five-user edition 5 1 one-user path 3rdparty How to Create a New WIN.INI Without Third-Party Information Article ID: Q96698 ---------------------------------------------------------------- ------ The information in this article applies to: - Microsoft Windows operating system versions 3.1, 3.11 - Microsoft Windows for Workgroups versions 3.1, 3.11 ---------------------------------------------------------------- ------ SUMMARY ======= You can use your original Microsoft Windows or Windows for Workgroups disks to create a new WIN.INI file. This may be useful for troubleshooting or for replacing a damaged or deleted WIN.INI file. NOTE: Before creating a new WIN.INI file, you can rename your current WIN.INI file and run Windows; this is often an effective first troubleshooting step. MORE INFORMATION ================ To create a new WIN.INI file that does not contain any references to third-party information but is configured for your specific system, do the following: 1. Rename the WIN.INI file to WIN.BKP. 2. Expand the file WIN.SR_ from the original Windows 3.1 disks to your Windows directory with the following command c:\\expand a:\win.sr_ c:\windows\win.ini where is your Windows directory. NOTE: The WIN.SR_ file is found on Disk 1 of the Windows 3.1 and 3.11 disks (both disk sizes), on Disk 3 of the Windows for Workgroups 3.1 disks (both sizes), and on Disk 2 of the Windows for Workgroups 3.11 disks (both sizes). 3. Using an ASCII text editor, such as MS-DOS Editor or Edlin, edit the WIN.INI file. Make the following changes: a. Add the COOLSWITCH=1 line to the [windows] section. b. Add TXT to the DOCUMENTS= line. For example: Documents=txt c. Delete the SetupWin=1 line from the [windows] section. 4. Save the changes to your WIN.INI file and quit the text editor. 5. Start Windows and run Control Panel. NOTE: The fonts displayed in Windows may be quite large and bulky. This is due to the absence of the [fonts] section in the WIN.INI file. The following steps should correct this problem. 6. Reinstall your printer driver with the following steps: a. Choose the Printers icon. b. Choose your printer from the list of installed printers. c. Choose the Install button. d. Choose the Close button. 7. Reinstall the TrueType fonts. a. In Control Panel, choose the Fonts icon. b. Choose the OK button. c. In the directories list, select the Windows \SYSTEM subdirectory. d. Choose the Select All button and then choose the OK button. e. Choose the Close button. 8. Quit and then restart Windows. 9. If the new WIN.INI file seems to correct the problem you are troubleshooting and your original WIN.INI file is available, you can cut and paste application-specific sections from the old WIN.INI file. If your original WIN.INI file is not available, reinstall the applications. KBCategory: kbother kbtshoot KBSubcategory: win31 wfw wfwg Additional reference words: 3.10 recreate re-create win.src win.sr_ rebuild t_shoot tshoot trouble shoot expanding 3.11 windrvr 3.5-inch 5.25-inch 1.2 megabyte 1.44 System Slows After 32-Bit File Access Is Enabled Article ID: Q106266 ---------------------------------------------------------------- ----- The information in this article applies to: - Microsoft Windows for Workgroups version 3.11 ---------------------------------------------------------------- ----- SYMPTOMS ======== Your system seems slower after you enable 32-bit file access. CAUSE ===== Enabling 32-bit file access can result in slower system performance in the following situations: - VFAT is unable to mount. This can happen as a result of one or more of the following problems (note that the numbers below correspond to the numbered steps in the "VFAT is Unable to Mount" subsection of this article): 1. The real-mode network redirector has been loaded into memory. 2. A memory-resident program or device driver has a file open while Windows loads. 3. The drive is involved in a SUBST, ASSIGN, or JOIN action. Because of the way they alter apparent disk characteristics, the SUBST.EXE, ASSIGN.COM, and JOIN.EXE programs are not compatible with installable file systems (IFS), such as 32-bit file access. These utilities can't be used if 32-bit file access is enabled. 4. The cache size selected is too large or invalid. 5. Required components are missing, corrupted, or not in the specified directory. - Windows for Workgroups version 3.11 is in a low-memory situation after enabling VFAT. Running VFAT/VCACHE with SMARTDrive may place Windows for Workgroups into a low-memory situation because memory used by SMARTDrive is not available to VCACHE.386 and vice-versa. Since VCACHE.386 provides the caching on VFAT-enabled drives and network drives, while SMARTDrive caches CD-ROM drives and floppy disk drives, it is possible that systems with too large a percentage of memory allocated to caching have some performance reduction. WORKAROUND ========== Low-Memory Situation -------------------- If you are in a low-memory situation (that is, you are running both SMARTDrive and VFAT), make sure that the amount of memory allocated to SMARTDrive's WinCacheSize and the cache size allocated to VCACHE.386 do not exceed roughly 30 percent of total system RAM. For example, on a machine with 4 megabytes (MB) RAM, if you have allocated 1024 kilobytes (K) to VCACHE, set the SMARTDrive WinCacheSize to 128K. To do this, use a command similar to the following c:\windows\smartdrv.exe <1024> <128> where <1024> is the InitCacheSize (the cache size at MS-DOS) and <128> is the size of the cache in Windows. VFAT Is Unable to Mount ----------------------- If VFAT is unable to mount, try the following: 1. You can unload the real-mode network redirector by typing "net stop" (without the quotation marks) at the MS-DOS command prompt before starting Windows for Workgroups. 2. To ensure that no device driver or terminate-and-stay-resident (TSR) program has any files open upon entering Windows for Workgroups, clean start the machine. For more information on clean start configurations for Windows for Workgroups version 3.11, query on the following words in the Microsoft Knowledge Base: wfw and clean and start 3. Do not use the SUBST, ASSIGN, or JOIN utilities with 32-bit file access enabled. If you must use one of these utilities, disable 32-bit access first. 4. Verify that the cache size selected is valid. For more information, see the "Low-Memory Situation" section above. 5. The components used by VFAT vary depending on the system's hard disk drive (HD) controller type and whether or not disk compression (such as DoubleSpace, DriveSpace, or Stac Electronics Stacker) is used. If you suspect the components are missing, corrupted, or not in the specified directory, verify the components files sizes, or re-expand them from your original Windows for Workgroups version 3.11 disks. File Size ---- ---- IOS.386 28,352 RMM.D32 11,894 RMM.D32 11,473 (version of RMM.D32 included with Microsoft PSS Application Note WG0973) VCACHE.386 9,862 VFAT.386 32,925 VXDLDR.386 5,678 NOTE: VFAT cannot load on a volume compressed with MS-DOS 6.0 DoubleSpace. This problem was resolved in MS-DOS 6.2 and later. IMPORTANT: The SYSTEM.INI file entries shown in the examples below are made by Control Panel and do not require manual editing. These examples are provided to show the component files involved and to aid in troubleshooting. You should avoid manually editing your SYSTEM.INI file. Example 1: Uncompressed WD 1003 Compatible Drive ------------------------------------------------ Western Digital 1003 or ST506 compatible drives without compression require the following entries in the [386Enh] section of the SYSTEM.INI file: [386Enh] device=*BLOCKDEV device=*PAGEFILE device=*int13 device=*wdctrl device=vcache.386 device=vfat.386 All entries marked with an asterisk (*) are contained in the WIN386.EXE file. All files should be located in your Windows SYSTEM subdirectory unless otherwise noted. Example 2: Compressed or Not WD 1003-Compatible Drive ----------------------------------------------------- If the drive is compressed, or if another hard disk in the machine is not WD 1003 compatible, then the line "device=*BLOCKDEV" should be replaced with the following: device=IOS.386 device=VXDLDR.386. In addition, the real mode mapper (RMM.D32) must exist in the Windows SYSTEM subdirectory. Example 3: Not WD 1003-Compatible Drive --------------------------------------- If 32-bit disk access cannot be used by a particular hard disk controller (because it is not WD 1003 compatible), the VFAT entries for the SYSTEM.INI file's [386Enh] section should include the following: [386Enh] device=*PAGEFILE device=vcache.386 device=vfat.386 device=IOS.386 device=VXDLDR.386 Again, RMM.D32 must exist in the Windows SYSTEM directory. MORE INFORMATION ================ VFAT is a 32-bit virtual MS-DOS file allocation table (FAT) file system and can only mount on hard disk volumes. If 32-bit disk access drivers are not available for a particular hard disk controller, additional handling of INT 13h calls is required. The IOS.386, VXDLDR.386, and RMM.D32 files provide this functionality and allow VFAT/VCACHE to work on these drives. (Drives affected include most SCSI and ESDI drives, a few IDE drives, and compressed volumes residing on any type of hard disk.) 32-bit disk access drivers may also be provided by an original equipment manufacturer (OEM) to work with a specific hard disk controller, replacing Microsoft's *WDCTRL. As a troubleshooting step, these drivers should be temporarily disabled and IOS.386, VXDLDR.386, and RMM.D32 should be used instead. KBCategory: kbtool kbtshoot kbfile kbappnote KBSubcategory: Additional reference words: appnote dblspace wfw wfwg 3.11 fastdisk slow slower slows tshoot WG0949: Windows for Workgroups 3.11 Setup Information Article ID: Q106511 ---------------------------------------------------------------- ---- The information in this article applies to: - Microsoft Windows for Workgroups version 3.11 ---------------------------------------------------------------- ---- Microsoft has an Application Note titled "Setup Information" (WG0949) for Microsoft Windows for Workgroups version 3.11. You can obtain this Application Note from the following sources: - CompuServe, GEnie, and Microsoft OnLine - The Internet (Microsoft anonymous ftp server) - Microsoft Download Service (MSDL) - Microsoft FastTips Technical Library - Microsoft Product Support Services For complete information, see the "To Obtain This Application Note" section at the end of this article. THE TEXT OF WG0949 ================== ================================================================ ====== Microsoft(R) Product Support Services Application Note (Text File) WG0949: SETUP INFORMATION ================================================================ ====== Revision Date: 6/94 No Disk Included The following information applies to Microsoft Windows for Workgroups, version 3.11. ---------------------------------------------------------------- ------- | INFORMATION PROVIDED IN THIS DOCUMENT AND ANY SOFTWARE THAT MAY | | ACCOMPANY THIS DOCUMENT (collectively referred to as an Application | | Note) IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER | | EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE IMPLIED | | WARRANTIES OF MERCHANTABILITY AND/OR FITNESS FOR A PARTICULAR | | PURPOSE. The user assumes the entire risk as to the accuracy and | | the use of this Application Note. This Application Note may be | | copied and distributed subject to the following conditions: 1) All | | text must be copied without modification and all pages must be | | included; 2) If software is included, all files on the disk(s) | | must be copied without modification (the MS-DOS(R) utility | | diskcopy is appropriate for this purpose); 3) All components of | | this Application Note must be distributed together; and 4) This | | Application Note may not be distributed for profit. | | | | Copyright (C) 1993 Microsoft Corporation. All Rights Reserved. | | Microsoft and MS-DOS are registered trademarks and Windows and | | Windows NT are trademarks of Microsoft Corporation. | | Artisoft and LANtastic are registered trademarks of Artisoft, Inc. | | AT&T is a registered trademark of American Telephone and Telegraph | | Company. | | Banyan and VINES are registered trademarks of Banyan Systems, Inc. | | DEC is a registered trademark and Pathworks is a trademark of | | Digital Equipment Corporation. | | TCS is a registered trademark of Eurotherm International P.L.C. | | IBM and OS/2 are registered trademarks of International Business | | Machines Corporation. | | NetWare and Novell are registered trademarks of Novell, Inc. | | Olivetti is a registered trademark of Ing. C. Olivetti. | | PC-NFS and Sun Microsystems are registered trademarks of Sun | | Microsystems, Incorporated. | |---------------------------------------------------------------- -----| INTRODUCTION ============ This Application Note discusses installation requirements for Microsoft Windows for Workgroups version 3.11, the differences between the Setup programs for Windows for Workgroups 3.11 and Microsoft Windows operating system 3.1, new device drivers and files that ship with Windows for Workgroups, and the Setup options /A, /N, and /H. INSTALLATION REQUIREMENTS ========================= To install and use Windows for Workgroups 3.11, you must be using MS- DOS version 3.3 or later. To upgrade from a previous installation of Windows, your Windows version must be 3.1 or later, and your Windows files must be included in your PATH statement. (If you have a version of Windows earlier than 3.1, you need to do a complete Windows for Workgroups installation, not an upgrade.) If you want to preserve your Program Manager groups and other existing Windows settings, you need to install Windows for Workgroups in the directory of your current Windows installation. DISK SPACE REQUIREMENTS ======================= Windows for Workgroups 3.11 requires approximately 4.5 megabytes (MB) more disk space than Windows 3.1. The following table illustrates the disk space requirements for the most common installation types. Type of Installation Windows 3.1 Windows for Workgroups 3.11 ----------------------------------------------------------------- ------- Full installation (286) 8.6 MB Not Available Upgrade 3.x (286) 5.2 MB Not Available Full installation (386) 9.5 MB 18.0 MB Upgrade 3.x (386) 5.2 MB 9.0 MB Network administrator (setup /A) 15.3 MB 21.0 MB Network setup (setup /N) .3 MB 1.2 MB SUPPORTED NETWORKS ================== The following networks are supported for use with Windows for Workgroups 3.11: - Artisoft(R) LANtastic(R) (versions 3.x, 4.x, and 5.x) - Banyan(R) VINES(R) (versions 4.11, 5.0, and 5.52) - BW-NFS (version 3.0) - DEC(R) Pathworks(TM) (versions 4.0, 4.1, and later) - IBM(R) OS/2(R) Lan Server (versions 1.2, 1.3, 1.3 CSD, and 2.0 without API) - Microsoft LAN Manager (version 2.1) - Microsoft Windows Network - Microsoft Windows NT(TM) (version 3.1) - Microsoft Workgroup Client (all versions) - Novell(R) NetWare(R) (versions 3.x, 4.0, and later) - Sun Microsystems(R) PC-NFS(R) (version 5) - TCS(R) 10Net (versions 4.1x, 4.2, and 5.0) Before you run a shared copy of Windows for Workgroups that is installed over one of these networks, read the following guidelines. For some networks, you need to take some preliminary steps before running a shared copy of Windows for Workgroups. Novell NetWare Network ---------------------- If you are running a shared copy of Windows for Workgroups on a Novell workstation, be sure to log on to the Novell server before starting Windows for Workgroups. Microsoft LAN Manager and Windows for Workgroups ------------------------------------------------ Before you run a shared copy of Windows for Workgroups on a LAN Manager or Windows for Workgroups workstation, be sure to start the network workstation services. You can do this with the NET START WORKSTATION command. If you are using the Windows for Workgroups network drivers, you can start the workstation services automatically by placing one of the following entries in the [Network] section of your SYSTEM.INI file: autostart=full autostart=basic Setting AUTOSTART to FULL installs the enhanced network redirector. The enhanced redirector supports named pipes and LAN Manager application programming interface (API) functions. Setting AUTOSTART to BASIC installs the basic network redirector, which uses less system memory but does not support named pipes. Neither redirector supports network messaging services or pop-up messages. LAN Manager automatically installs the redirector based on entries in your AUTOEXEC.BAT and CONFIG.SYS files. These settings are specified in the LAN Manager network documentation. NOTES - With Windows for Workgroups 3.11, you can connect to and use files, directories, and printers that are shared on a Microsoft Windows NT or a Microsoft LAN Manager server. To view the name of a LAN Manager server, at least one computer on the network must have a workgroup name that matches the name of the primary domain of the LAN Manager server. - Unlike in version 3.1, if you are running a shared copy of Windows for Workgroups 3.11, you cannot share your workstation's resources once you have started the real mode redirector. Using Windows for Workgroups with a Different Network Operating System ----------------------------------------------------------------- ----- In addition to the Windows for Workgroups 3.11 network functionality, you can install Windows support for a third-party network operating system. The network operating systems currently supported are: - Banyan VINES (versions 4.11, 5.00, and 5.52) - BW-NFS (version 3.0) - Novell NetWare Shell (versions 3.x and 4.x) - Sun Microsystems PC-NFS (version 5.0) No third-party files are included with Windows for Workgroups 3.11. You must obtain all third-party network operating system files from your network vendor. You must install the third-party network operating system before you select the Windows support option. NOTE: This procedure is not useful unless the drivers you obtain from your vendor are compatible with Windows for Workgroups. To use Windows for Workgroups with a different network: 1. In the Network group in Program Manager, choose the Network Setup icon. 2. In the Network Setup dialog box, choose the Networks button. The Compatible Networks dialog box appears. 3. Select the Other option button under the heading "You can install Windows support for an additional network" and then select the network you want to set up. If that network does not appear in the list, select Unlisted Or Updated Network. You are then prompted to insert the disk containing the network driver supplied by your vendor. After you insert the floppy disk in your drive, Setup installs the network driver. The new network should then appear in the Available Network Types group. 4. Select your network and choose the Add button. This adds the network to the Other Networks In Use list. 5. Choose the OK button twice to exit the Network dialog boxes. IMPORTANT: To use the new driver(s), you must reboot your machine. INSTALLING WINDOWS SUPPORT FOR A THIRD-PARTY NETWORK ONLY ========================================================= You can install Windows support for a third-party network only; however, you lose Windows for Workgroups peer-to-peer functionality if you do so. You can install support for the following networks: - Artisoft LANtastic (versions 3.x, 4.x, and 5.x) - Banyan VINES (versions 4.11, 5.0, and 5.52) - BW-NFS (version 3.0) - DEC Pathworks (versions 4.0, 4.1, or later) - IBM OS/2 Lan Server (versions 1.2, 1.3, 1.3 CSD, and 2.0 without API) - Microsoft Windows Network (version 3.11 Basic) - Novell NetWare (versions 3.x, 4.0, and later) - Sun Microsystems PC-NFS (version 5) - TCS 10Net (versions 4.1x, 4.2, and 5.0) DIFFERENCES IN SETUP PROGRAMS FOR ================================= WINDOWS 3.1 AND WINDOWS FOR WORKGROUPS 3.11 =========================================== This section discusses new features in the Windows for Workgroups Setup program, including network detection and dialog box changes. NETWORK DETECTION ================= - Windows for Workgroups 3.11 Setup performs network card detection. If Setup fails to detect your network card, it prompts you to choose from a list of available network adapters. - After a failed installation attempt, you can also force Setup to perform network card detection by using the /F switch (setup /F). - You can select No Network as a network type during Setup. DIALOG BOXES ============ - Windows for Workgroups Setup 3.11 asks for the computer name and the workgroup in the initial user name dialog box. - After Setup completes printer installation, the Install New Network Adapter, Network Adapters, and Compatible Networks dialog boxes may appear, as the following table illustrates. Dialog box Express Setup Custom Setup ---------------------------------------------------------------- - Install New Network Adapter Conditional Conditional Network Adapters No Yes Compatible Networks Conditional Yes The Install New Network Adapter dialog box does not appear during either Express or Custom Setup if the Network Card Detection (NCD) utility detects your network card and you confirm the detected network card. Confirming the detected network card places a network adapter entry in the PROTOCOL.INI file. If you don't confirm the detected network card, the Install New Network Adapter dialog box appears. If you are upgrading from a Workgroup Connection or LAN Manager 2.1 installation, there is already a valid network adapter entry in the PROTOCOL.INI file, and this dialog box is skipped. The Compatible Networks dialog box does not appear during Express Setup if you are upgrading from a LAN Manager 2.1 installation. Selecting a network in this dialog box places a multinet= entry in the [Network] section of the SYSTEM.INI file. If Setup detects the existing LAN Manager 2.1 installation, Setup places the multinet= entry in the SYSTEM.INI file and therefore skips the Compatible Networks dialog box. - Once Setup is complete, the option to restart Windows is no longer available. (To load or upgrade network drivers, you must reboot your machine.) SETUP OPTIONS (SETUP /A, SETUP /N, AND SETUP /H) ================================================ SETUP /A AND SETUP /N ===================== You run Setup with the /A and /N options to configure a workstation to run Windows from a shared directory. Administrative Setup (setup /A) copies all the files from the Windows distribution disks to a single directory and marks them as read-only. This directory can then be used to install and run a shared copy of Windows. Setup /N sets up the shared copy of Windows. In a stand-alone Windows 3.1 installation, the Windows directory and SYSTEM subdirectory are on your personal hard disk drive. In a shared Windows installation, the Windows directory can be located on the user's hard disk drive or on a network drive, and can be customized for each user. There is no SYSTEM subdirectory, as such, in a network installation; system files are typically located in a shared directory on a network server. In Windows for Workgroups 3.11, as in Windows 3.1 running on a network, the personal Windows directory contains all files with .INI, GRP, and .PIF extensions, as well as REG.DAT, WIN.COM, WINVER.EXE, and any MS-DOS device driver files. The personal Windows directory may also contain the MS-DOS network device drivers and the NET.EXE, MSIPX.COM, and NETX.COM files. (These files may also be copied to the root directory of the boot drive, as explained in the following section.) The shared directory contains all other Windows files. NOTE: If you are setting up a third-party network operating system under Windows for Workgroups, you must place the necessary files provided by the third-party network operating system manufacturer in the shared Windows directory created by the setup /a command. When you run setup /n, Setup does not prompt you for these files. Where Setup Places Network Files -------------------------------- The Windows 3.1 Setup program reads the SETUP.INF file to determine where to install files. SETUP.INF uses the file classifications WINDIR and SYSDIR to refer to files that Setup installs in the Windows directory and SYSTEM subdirectory, respectively. The Windows for Workgroups 3.11 Setup program reads the NETWORK.INF file to determine where to install files. Setup places files with the windir classification in the personal Windows directory and files with the sysdir classification in a shared server directory. NETWORK.INF also uses two new file classifications, NETDIR and DEVDIR. Where Setup places these files depends on the type of installation. Real-mode network device drivers (devdir files) are copied to the personal Windows directory on a local nonremovable, noncompressed drive. These include PROTMAN.DOS, PROTOCOL.INI, and WORKGRP.SYS. If the personal Windows directory is on a remote, removable, or compressed volume, then these files are copied to the root of the boot drive. These device drivers must be correctly referenced in the CONFIG.SYS file. Real-mode network utilities and terminate-and-stay-resident (TSR) programs (netdir files) are copied to the personal Windows directory on a nonremovable hard disk. These include NET.EXE, MSIPX.COM, NETX.COM, and ROUTE.COM. If the personal Windows directory is on a remote or removable volume, these files are copied to the same directory as the devdir files. These utilities and TSRs must be correctly referenced in the AUTOEXEC.BAT file. NOTE: If your personal Windows directory is on a remote volume, you still must have your own hard disk drive to run Windows for Workgroups. Windows for Workgroups does not support diskless workstations or systems without hard disk drives. The following table illustrates where Setup places the netdir and devdir files for different installations. Location of Location of Location of Windows installation netdir files devdir files ----------------------------------------------------------------- --- Nonremovable hard disk drive Windows Windows Compressed nonremovable hard disk drive Windows Root Removable drive (for example, SCSI) Root Root Remote drive (setup /N) Root Root BATCH MODE SETUP (SETUP /H) =========================== You can use Setup with the /H option to automate the Setup program. Windows for Workgroups 3.11 and Windows 3.1 come with a system- settings template file called SETUP.SHH, which you can copy or modify to create a custom system-settings file. In addition to the settings specified in the Windows 3.1 template file, the Windows for Workgroups template file includes parameters for the computer name, workgroup, network card, protocol, and compatible network. The SETUP.SHH file is located on Windows for Workgroups 3.11 Disk 1 and is copied to the shared Windows for Workgroups directory when you run setup /A. You can modify the template file with any text editor that can save unformatted text (ASCII) files. For more information about batch mode setup, refer to Chapter 3 of the Microsoft Windows for Workgroups "Resource Kit." ---------------------------------------------------------------- ---- TO OBTAIN THIS APPLICATION NOTE =============================== - On CompuServe, GEnie, and Microsoft OnLine, Application Notes are located in the Microsoft Software Library. You can find WG0949.TXT in the Software Library by searching on the word WG0949, the Q number of this article, or S14370. - Application Notes are available by modem from the Microsoft Download Service (MSDL), which you can reach by calling (206) 936-6735. This service is available 24 hours a day, 7 days a week. The highest download speed available is 14,400 bits per second (bps). For more information about using the MSDL, call (800) 936-4200 and follow the prompts. To obtain WG0949, download WG0949.TXT. - On the Internet, Application Notes are located on the Microsoft anonymous ftp server, which you can reach by typing "ftp ftp.microsoft.com" (without the quotation marks) at the ">" command prompt. You can find WG0949.TXT in the SOFTLIB\MSLFILES directory. - You can have this Application Note faxed or mailed to you from the automated Microsoft FastTips Technical Library, which you can call 24 hours a day, 7 days a week at (800) 936-4200. NOTE: The FastTips Technical Library is available only to customers within the U.S. and Canada. - If you are unable to access the source(s) listed above, you can have this Application Note mailed or faxed to you by calling Microsoft Product Support Services Monday through Friday, 6:00 A.M. to 6:00 P.M. Pacific time at (206) 637-7098. If you are outside the United States, contact the Microsoft subsidiary for your area. To locate your subsidiary, call Microsoft International Sales Information Center at (206) 936-8661. KBCategory: kbnetwork kb3rdparty kbfile kbappnote KBSubcategory: wfw Additional reference words: appnote wfwg 3.11 WFWG 3.11: Hardware Compatibility List - Modems for RAS Article ID: Q107374 ------------------------------------------------------------ The information in this article applies to: - Microsoft Windows for Workgroups version 3.11 ------------------------------------------------------------ SUMMARY ======= This article contains a list of modems that have been tested and certified by Microsoft to be compatible with Windows for Workgroups 3.11 when using the Remote Access Services. Microsoft will add additional information to this article as it becomes available. NOTE: This list is independent of the Microsoft At Work PC Fax supported modems list. MORE INFORMATION ================ U.S. Modems ----------- Angia DataStart for CompaqLTE ATI 2400 etc/e ATI 9600 etc/e AT&T 2224 CEO AT&T Comsphere 3810 AT&T Comsphere 3811 AT&T Comsphere 3820 AT&T Comsphere 3830 AT&T Dataport AT&T Paradyne PCMCIA AT&T 4024 Bocamodem M1440 Cardinal 2400e Cardinal 9600 Cardinal 14400 Cardinal 14400 Internal Codex 2264 Codex 3220 Codex 3260 Codex 3261 Codex 3262 Codex 3263 Codex 3265 Codex 3260 Fast Codex 3261 Fast Codex 3262 Fast Codex 3263 Fast Codex 3265 Fast Codex 3220 Plus Compaq SpeedPAQ 144 CXR Telcom 1445 DataRace RediModem V.32bis Datatrek 2424AMH Datatrek Elite 624D Datatrek V.32 DP Defender1000D w/HayesUltra Digicom Scout Digicom Scout Plus DSI 9624LE Plus DSI 9624E ETech UFOMATE P1496MX Evercom 24 Evercom 24E Evercom 24E+ Gateway 2000 Internal Alt Gateway 2000 Internal Gateway 2000 Nomad 14400 GVC SM2400 GVC SM96 GVC FM14400 Hayes Compatible 1200 Hayes Compatible 2400 Hayes Compatible 9600 Hayes Pocket Modem 2400 Hayes Smartmodem 2400 Hayes Smartmodem 9600 Hayes Optima 9600 Hayes Optima 14400 Hayes Ultra 9600 Hayes Ultra 14400 Hayes V Series Smartmodem9600 Intel SatisFAXtion 100 Intel SatisFAXtion 400e Intel 9600EX Intel 14400EX Macronix Maxlite Fax 9696 Macronix VOMAX 2000 Megahertz P2144 Pkt Faxmodem Megahertz T3144 for Toshiba Megahertz Z3144 for Zenith Megahertz C5144 for CompaqLTE Megahertz XJack PCMCIA MicroCom QX 4232bis MicroComQX 4232HS MicroGate MG96 MicroGate MG144 MicroPorte 1042 MultiTech MultiModem 224 MultiTech MultiModem MT932 NEC 9635E Plus NEC 14.4 Data/Fax PCMCIA Null Modem Octocom 8324 Octocom 8396 PDI-1000 Practical Peripherals 2400 Pkt Practical Peripherals 2400SA Practical Peripherals 2400MNP Practical Peripherals 9600SA Practical Peripherals 14400SA Practical Peripherals 14400FX Racal GSM w/ Hayes Ultra Racal RMD 2412 Racal RMD 2422 Racal RMD 2412/2 Racal RMD 3221 Racal RMD 3222 Racal RMD 3226 Racal RMD 3223 Racal RMD 9632PA Racal RMD 9642PA SD ACM400 w/ AT&T 3820 SupraModem 2400 Supra Fax Modem 9624 Internal Supra Fax Modem V32 Supra Fax Modem V32bis Supra Fax Modem Plus Telebit QBlazer Telebit T1000 Telebit T1500 Telebit T1600 Telebit T2000 Telebit T2500 Telebit T3000 Telebit TrailBlazer Plus Telebit WorldBlazer Telebit WorldBlazer-Rackmount UDS Motorola V.3225 UDS Motorola V.3227 UDS Motorola V.3229 UDS Motorola FasTalk V.32/42b U.S. Robotics Courier Dual U.S. Robotics Courier HST U.S. Robotics Courier V.32bis U.S. Robotics Sportster 2400 U.S. Robotics Sportster 9600 U.S. Robotics Sportster 14400 Ven-Tel 9600 Plus II Ven-Tel Pocket 24 V.42bis FAX Ven-Tel 14400 Fax Ven-Tel 14400 Fax Internal Western Datacom Worldcom Zoom AFX Zoom FX 9624V Zoom VFX V.32bis ZyXel U-1496 ZyXel U-1496E International Modems -------------------- Hayes Ultra 14400 - UK Smartlink Pocket 2400 - UK Smartlink V32Bis/Fax - UK Dataflex Rapier+ V32Bis - UK Psion Dacom PDM 50F - UK Andest Rocket - UK Intel SatisFAXtion - UK USR Worldport 14400 - UK GVC SM2400 - SWE GVC SM96 - SWE GVC FM14400 - SWE Hidem 14400/FAX - SWE Hidem 2442P/FAX - SWE LASAT Unique 144 - SWE LIGHTFAX 1440LC - SWE MultiTech MT932 - SWE UCOM FASTLINK 144 - SWE UCOM TRAVELLER 144 - SWE UDS Motorola FasTalk V32- SWE UFOMATE P1496MX - SWE USR Courier V.32bis - SWE USR Sportster 14400 - SWE USR Worldport 14400 - SWE DYNALINK - SWE SBN 2314C - SWE SEMAFOR 2324C - SWE SEMAFOR 1496A - SWE Avtek CD900 - AUS Avtek CD930 - AUS Banksia XM124/R FAXMODEM- AUS Banksia MX-6 V.32bis - AUS Maestro RC224FMI - AUS Maestro 144FMEI - AUS Netcomm Pocket Rocket PA- AUS Netcomm Smartmodem E7F - AUS Netcomm Pocket M/F 2400-AUS Dr Neuhaus Fury 2403 TI - GER Elsa MicroLink 14400 Int- GER Hayes Optima 9600 - GER Hayes Optima 14400 - GER Hayes Ultra 9600 - GER Hayes Ultra 14400 - GER KORTEX KXPRO 9600 - FRN KORTEX KXPRO 2400 - FRN ARN DX - FRN NOVA FAX NFX14400 - FRN PNB Baby RIO 14400 - FRN PNB AMAZONE 2400 - FRN CXR AJ2423 - FRN CXR AJ9636 - FRN LCE 126P - FRN LCE 132P - FRN 3X 396D - FRN 3X 514D - FRN KORTEX KXPRO 14400 - FRN KORTEX KXPOCKET 9600 - FRN COM1 MV215 - FRN COM1 MV219 - FRN COM1 MV216 - FRN COM1 MC215 - FRN ATTEL MX 96192 - FRN DATACONSYST DAC124 - ITA SYSNET SMF-04 - ITA SYSNET SMF-36 - ITA CDC 6438 - ITA CDC 6436 - ITA DIGICOM SNM28 - ITA KBCategory: kbref kbhw KBSubcategory: wfw wfwg awfax Additional reference words: 3.11 unsupported incompatible works won't work HCL WFWG 3.11: Hardware Compatibility List - Network Cards Article ID: Q107375 ---------------------------------------------------------------- ---- The information in this article applies to: - Microsoft Windows for Workgroups version 3.11 ---------------------------------------------------------------- ---- SUMMARY ======= This article lists network interface cards (NICs) that have been tested by Microsoft and certified to be compatible with Windows for Workgroups 3.11. The list is alphabetical by manufacturer. Microsoft will add additional information to this article as it becomes available. MORE INFORMATION ================ Company Network Card -------------------------------------------------------- Accton Technology EtherCombo-16 (EN1640) Accton Technology EtherPair-16 (EN1641) Accton Technology EtherCoax-16 (EN1642) Accton Technology EtherCombo-16 (EN1650) Accton Technology EtherPair-16 (EN1651) Accton Technology EtherCoax-16 (EN1652) Accton Technology EtherDuo-16 (EN1656) Allied Telesis AT-1500T Allied Telesis AT-1500BT Allied Telesis AT-1500FT Allied Telesis AT-1700T Allied Telesis AT-1700BT Allied Telesis AT-1700FT Alta Research EtherCombo-16 T/C AMD AM2100 AMD PCnet-ISA Single Chip Ethernet Controller AMI Series 65 EISA LAN Card Apricot XEN-LS 486SX-20 w/ i82592 Apricot LS PRO w/ i82596 Apricot LS 386SX-20 w/ i82592 Cabletron E2010-X Cabletron E2112 Cabletron E3010-X Cabletron E3112-X Cabletron T2015 Cabletron T3015 Chips N Tech MK561 Compaq 32-bit NetFlex Controller Compaq 32-bit DualSpeed Token Ring Compex ENET16/U Cresendo Communications C321M DCA IRMATrac Token-Ring/Convertible 16/4 DEC DEC EtherWORKS LC DEC DEC EtherWORKS MC DEC DEC EtherWORKS Turbo DEC DEPCA DEC WaveLAN AT D-Link Systems DE220CT Gateway Communications G/Ethernet 16 Combo Hewlett-Packard HP EtherTwist MCA Adapter (HP27246) Hewlett-Packard HP Ethertwist 8 TP (HP27245) Hewlett-Packard HP Ethertwist 16 TP (HP27247) Hewlett-Packard PC LAN Adapter/16+ TP (HP27247B) Hewlett-Packard Ethertwist EISA LAN Adapter/32 (HP27248) Hewlett-Packard PC LAN Adapter/16+ TL (HP27252A) Hewlett-Packard HP Ethertwist 8 TL (PC27250A) IBM Ethernet Cards IBM PCMCIA Ethernet Credit Card IBM Token Ring IBM Token Ring /A IBM Token Ring II IBM Token Ring 4/16 IBM Token Ring 4/16 A IBM Token Ring 16/4 Adapter II IBM Token-Ring 16/4 LANstreamer Server Adapter/A ICL Etherteam 16 ICL Etherteam 16i Intel Corp. EtherExpress 16 Intel Corp. EtherExpress 16TP Intel Corp. EtherExpress 16 TPE Intel Corp. EtherExpress 16C Intel Corp. EtherExpress MCA Intel Corp. EtherExpress MCA TP Intel Corp. EtherExpress TPE Hub Intel Corp. Token Express MCA 16/4 Intel Corp. Token Express EISA 32 Intel Corp. TokenExpress EISA 16/4 Intel Corp. TokenExpress ISA 16/4 Intel Corp. Token Express 16s Madge Networks Smart 16/4 XT Ringnode Madge Networks Smart 16/4 AT Ringnode Madge Networks Smart 16/4 EISA Ringnode Madge Networks Smart 16/4 MC Ringnode National Semiconductor EtherNODE *16AT National Semiconductor AT/LANTIC EtherNODE 16*AT3 National Semiconductor PCMCIA Ethernet National Semiconductor Sonic EISA (DP83932EB) National Semiconductor TROPIC Token Ring NCR StarLAN 16/4 Token-Ring MC NAU NCR Systems BV WaveLAN/AT NCR Systems BV WaveLAN/MC Novell NE1000 Novell NE2000 Novell NE2000T Novell NE2000 Plus Novell NE/2 Olicom 16 bit ISA 16/4 Olicom 16 bit EISA 16/4 Olicom 32-bit EISA Server Adapter Olicom 16 bit MCA 16/4 Proteon P1346 Proteon P1347 Proteon P1390 Proteon P1392 Proteon P1840 Proteon P1892 Proteon P1990 Proxim RangeLAN Wireless PureData PDI508+ PureData PDI516+ PureData PDI8023-8 PureData PDI8023-16 PureData PDI8023+ 16CAT PureData PDuC8023 PureData PDI9025-16 4 PureData PDE9025-32 16/4 PureData PDuC9025 16/4 PureData PDI90211 PureData PDuC90211 PureData PDI7023BT PureData PDI7023 Combo Racal-Datacom Interlan AT Racal-Datacom NI5210 Racal-Datacom NI6510 Racal-Datacom InterLAN EtherBlaster Racal-Datacom NI9210 Standard Microsystems PC130E Standard Microsystems PC130 Standard Microsystems PC270E Standard Microsystems PC550W Standard Microsystems PC600W Standard Microsystems PC650WS Standard Microsystems Ethernet 3016 Standard Microsystems SMC 8003EP Standard Microsystems SMC 8003EPC Standard Microsystems SMC 8003E/A Standard Microsystems SMC 8013EPC Standard Microsystems SMC 8013EWC Standard Microsystems SMC 8013WC Standard Microsystems PC9000 Thomas Conrad TC6145 Thomas Conrad TC6245 Thomas Conrad TC4045 3Com Corporation EtherLink II/16 TP (3C505-16-TP) 3Com Corporation EtherLink III (3C509) 3Com Corporation EtherLink III EISA (3C579) 3Com Corporation EtherLink/MC32 (3C527) 3Com Corporation EtherLink MC (3C523) 3Com Corporation TokenLink III 16/4 MCA (3C629) 3Com Corporation TokenLink III 16/4 ISA (3C619) Tiara 10Base-T LanCard/E*AT Tulip Computers TNCC-16 CAT Ungermann-Bass NICps/2 Ungermann-Bass NIUpc (PC2030) Ungermann-Bass NIUps (PC3030) Ungermann-Bass NIUps/EOTP (PC3035) Ungermann-Bass NIUpc/EOTP (PC4035) Ungermann-Bass PC5000 Xircom PE-1 Xircom PE-2 Zenith Data Systems Z.Note 325L Notebook PC KBCategory: kbnetwork kb3rdparty kbhw kbref KBSubcategory: wfw wfwg Additional reference words: 3.11 incompatible unsupported supported works won't work good bad HCL adapter adapters Installing Novell NetWare 3.12 and 4.0x Support for Windows Article ID: Q107808 ---------------------------------------------------------------- ---- The information in this article applies to: - Microsoft Windows for Workgroups versions 3.1, 3.11 - Microsoft Windows operating system versions 3.1, 3.11 ---------------------------------------------------------------- ---- This article contains information about using Windows for Workgroups with a third-party product that has not been tested and is not supported by Microsoft. If the steps or procedures described in this article do not function properly, contact the manufacturer of the third-party product for more information. SYMPTOMS ======== After you install Novell NetWare version 3.12 or 4.0x client software to a shared copy of Windows or Windows for Workgroups, you may receive the following error message: NetWare shell incompatible Cannot use a device specified in the SYSTEM.INI file. The device may be necessary to run Windows in 386 enhanced mode. If you experience problems, run the Setup program again. C:\WINDOWS\vnetware.386 CAUSE ===== The Novell NetWare client install for versions 3.12 and 4.0x uses VLM.EXE in place of NETX.EXE. If you are using VLM.EXE, the Novell NetWare client software does not properly update a shared copy of Windows (SETUP /A and SETUP /N); therefore, you must add the new Windows support files provided by Novell NetWare. RESOLUTION ========== To correctly install the NetWare client software to both the shared copy of Windows on the NetWare server and to all user directories, perform the steps below. NOTE: These steps assume that you have run SETUP /A on the server and SETUP /N to a user directory that has not been modified by the NetWare 4.0x client install: 1. Create an empty subdirectory on the local drive. 2. Create two blank files in this directory named WIN.INI and SYSTEM.INI. 3. Run the Novell NetWare client install utility. This utility is provided by Novell and will add the files needed for Windows. During the NetWare client install process, step 3 gives the option to install support for Windows and to provide the location of the Windows directory. You must choose Yes to install support for Windows, and point it to the empty subdirectory created in Step 1. 4. Once the installation is finished, delete all *.INI files in the subdirectory specified in step 1. 5. Change to the mapped drive and directory in which the shared Windows directory (SETUP /A) is located, and remove the read-only attribute from all files in the shared Windows directory. 6. The NetWare client install creates the following two subdirectories under the subdirectory created in step 1: NLS and SYSTEM 7. Copy the files from the SYSTEM subdirectory to the shared Windows directory on the NetWare server (where the SETUP /A was installed). This should copy the following five files: NETWARE.DRV NETWARE.HLP VNETWARE.386 VIPX.386 NWPOPUP.EXE 8. Delete these files in the SYSTEM subdirectory and remove the SYSTEM subdirectory. 9. Copy the remaining files in the subdirectory created in step 1, along with the entire NLS subdirectory, to the shared Windows directory on the NetWare server. 10. Delete the NLS subdirectory and the subdirectory created in step 1. 11. You then need to mark all files in the shared Windows directory with the read-only attribute. This can be done by typing attrib *.* +r in the subdirectory in which the shared copy of Windows was installed. 12. Add the following lines to the [386Enh] section of the SYSTEM.INI file in the Windows user directory for all workstations that will be running either the NetWare 3.12 or 4.0x client: TimerCriticalSection=10000 ReflectDOSInt2A=TRUE UniqueDOSPSP=TRUE PSPIncrement=5 OverlappedIO=OFF NOTE: With Windows for Workgroups 3.11, these lines should already exist if support for Novell NetWare 4.x was installed during Setup. 13. You can then run the client install to all other workstations on the network running Novell NetWare version 3.12 or 4.0 as needed. When the install utility asks if you want to install support for Windows, choose No. Each workstation will use the updated Novell files in the shared Windows directory. NOTE: Novell NetWare install adds a group to Windows Program Manager for the Novell Utilities. If you want to install this group after following the above steps, continue with the following steps; otherwise, you can stop here. 14. Copy the NWUTILS.GRP file from the shared Windows directory to each Windows user directory on all workstations to which you want to add the group. 15. From each workstation, run Windows. 16. In Program Manager, choose New from the File menu. 17. Select the Program Group option button, then choose OK. 18. In the Description box, type "NetWare" (without the quotation marks). 19. In the Group File box, type "NWUTILS.GRP" (without the quotation marks). 20. Choose OK. NOTE: The above steps do not work properly with Windows for Workgroups 3.1 because that version does not support connectivity with Novell NetWare using Novell's ODI specification. The Novell products included here are manufactured by a vendor independent of Microsoft; we make no warranty, implied or otherwise, regarding these products' performance or reliability. KBCategory: kbnetwork kbtlc kberrmsg kb3rdparty KBSubcategory: wfwg Additional reference words: 3.10 3.11 nw4 nw wfw wfwg install setup configure configuration winshare winuser err msg 3rdparty EMM Exception Error #6 Exiting Windows for Workgroups 3.11 Article ID: Q107978 ---------------------------------------------------------------- ----- The information in this article applies to: - Microsoft Windows for Workgroups version 3.11 ---------------------------------------------------------------- ----- SYMPTOMS ======== When you exit Windows for Workgroups version 3.11, your system may stop responding (hang). If EMM386.EXE is loaded, you may receive the following error message: EMM Exception Error #6 CAUSE ===== This problem occurs because: - The processor is trying to decode a bit pattern that does not correspond to any legal machine instruction. -or- - The processor is trying to execute an instruction that contains invalid operands. Both of these causes mean that the processor (CPU) is trying to execute code from an incorrect area in memory. Either an application is passing an invalid jump instruction (causing a jump to an incorrect memory location) or the jump instruction is correct but the memory that the instruction accesses is corrupted. NOTE: Although you receive an EMM exception error, EMM386.EXE is not causing the problem. When the processor encounters a problem executing an instruction, it looks for an error handler. When you exit Windows for Workgroups it uses the default error handler. If EMM386.EXE is installed, you receive the EMM Exception Error. If EMM386.EXE is not installed, the machine may stop responding (hang). WORKAROUND ========== To troubleshoot this problem, follow the steps in this procedure. After each step, you should reboot your computer, run Windows for Workgroups, and then attempt to successfully exit Windows for Workgroups. When Windows for Workgroups exits successfully, you have isolated the problem. 1. If you ran MS-DOS 6 or 6.2 MemMaker before installing Windows for Workgroups, run MemMaker again. 2. Eliminate potential software conflicts as follows: a. Remove any third-party device drivers and terminate-and-stay-resident (TSR) programs that are not required to access your hard drive from your CONFIG.SYS and AUTOEXEC.BAT files. For moreinformation on device drivers the should not be remarked out, query on the following words in the Microsoft Knowledge Base: wfw clean boot b. Ensure that the Windows for Workgroups StartUp group is empty. c. Ensure that no screen savers, including built-in Windows screen savers, are running. In the Control Panel, choose the Desktop icon and verify that the Screen Saver Name list box is empty. d. Ensure that Windows is not being run from a menu program, such as MS-DOS Shell. e. Edit the WIN.INI file and comment out the LOAD= and RUN= lines (unless they are already blank). To comment out these lines, place a semicolon (;) in front of the line. For example: ;load= f. Edit the SYSTEM.INI file and comment out any third-party virtual device drivers (VxDs). g. If possible, disable NDIS2 protocols like TCP or DLC. 3. Eliminate potential hardware conflicts: a. Turn off hardware caching. b. Turn off shadow ram and video memory. 4. Edit the CONFIG.SYS file and exclude A000-F7FF to eliminate potential upper memory area (UMA) conflicts. To do this, add "X=A000-F7FF" to the DEVICE command for EMM386.EXE in the CONFIG.SYS file. 5. Remark out the device command for EMM386.EXE in the CONFIG.SYS file and then run Windows for Workgroups with the "/D:X" parameter. For example, type "win /d:x" (without the quotation marks) at the MS-DOS command prompt and then press ENTER. 6. Start Windows for Workgroups with the WIN /N command. This loads Windows for Workgroups without loading any network support. If the problem does not occur without network software loaded, a hardware device may be conflicting with your network card. If Windows for Workgroups still hangs when you exit, you still have a memory conflict; however, it is not in the upper memory area (UMA). KBCategory: kbother kbdisplay kberrmsg KBSubcategory: wfwg Additional reference words: 3.11 err msg errors "Not Enough Memory" Error Occurs When Browsing Article ID: Q107994 ---------------------------------------------------------------- ---- The information in this article applies to: - Microsoft Windows for Workgroups version 3.11 ---------------------------------------------------------------- ---- SYMPTOMS ======== When you try to browse network connections from a Windows for Workgroups 3.11 workstation, you receive the following error message: There is not enough memory available. WORKAROUND ========== To work around this problem, manually insert the path for the computer name and share name. You may also be able to work around this problem by doing one of the following: - Run MS-DOS Prompt from the Program Manager Main group, and type "exit" (without the quotation marks) to return to Windows for Workgroups. - Run MS-DOS Prompt from the Program Manager Main group, type "net view", (without the quotation marks) and then type "exit" (without the quotation marks)to return to Windows for Workgroups. - Increase the available conventional memory. Depending on your system configuration, you'll need 475 to 600K free for Windows for Workgroups to browse correctly. - Remove all applications from your Program Manager Startup group. - Use only one protocol. - If you are using a third-party shell, switch back to Program Manager. - The protocol file may be corrupt. Reinstall the protocol. - Disabling NETWORK DDE may allow you to browse when memory optimization fails. NOTE: If running MS-DOS Prompt corrects the problem, create a one-line batch file that reads COMMAND.COM /C. If running NET VIEW from MS-DOS Prompt corrects the problem, create a one-line batch file that reads COMMAND.COM /C NET VIEW. Name the batch file FIX.BAT and create an icon in the Startup group using FIX.BAT as the command line and Browse Fix as the Description. STATUS ====== Microsoft has confirmed this to be a problem in Windows for Workgroups version 3.11. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available. MORE INFORMATION ================ If you try to connect to a network drive in File Manager, you may see only a workgroup name listed in the browse list. Trying to force the list of computers to appear by choosing the workgroup name may cause the error above to be displayed. This error occurs only if the local computer is not providing the browse list. KBCategory: kbnetwork kberrmsg kbbuglist KBSubcategory: wfw wfwg Additional reference words: 3.11 browsemaster unc universal naming convention browselist winnt Microsoft At Work PC Fax: Top Questions and Answers Article ID: Q109056 ---------------------------------------------------------------- ---- The information in this article applies to: - Microsoft Windows for Workgroups version 3.11 ---------------------------------------------------------------- ---- SUMMARY ======= This article contains commonly asked questions and answers for Microsoft At Work PC Fax. MORE INFORMATION ================ 1. Q. Why does Mail constantly poll for new messages with At Work PC Fax installed? A. This behavior occurs only if you are attached to a shared fax modem. To correct this problem: 1. Open Mail. 2. From the Fax menu, choose Mode. 3. Select the Work Off-Line check box. (When you are ready to send a fax, remove the check mark and choose View New Messages from the Fax menu.) 2. Q. Sometimes when I try to open a new fax message, Mail generates a general protection fault. This problem seems to occur randomly. How can I correct this problem? A. Microsoft is researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available. 3. Q. When I start Mail and the fax tries to go online, I receive the following error. How can I avoid this error? Fax Transport cannot go on-line. Off-Line operation will continue. A. This error occurs under the following circumstances: - You have an external fax modem, and it is turned off or not correctly connected to the port. - You are attached to a shared network fax that is on a server not running Microsoft Mail, or the MAPI engine has not been started. - The shared fax user is connecting to the wrong share. Check the EFAXPUMP.INI file to ensure the path to the network fax is correct. - The network fax is working offline. (Go to Microsoft Mail on the network fax machine and choose Mode from the Fax menu to ensure the fax is working online.) 4. Q. What causes a fax to render correctly but then appear in my Inbox? A. If you send a fax to the same number that was entered during At Work PC Fax Setup in Control Panel, At Work PC Fax recognizes that it cannot call itself; therefore, it renders the fax and places it in your Inbox. 5. Q. Why does my Intel CAS modem fail to render the fax every time I try to send one? A. Changing the Image Quality setting from Best Available to Fine should correct this problem. To do this: 1. Go to Microsoft Mail. 2. From the Fax menu, choose Options. 3. Change the Image Quality from Best Available to Fine. KBCategory: kbtool kbfasttip kbatwork kbtshoot KBSubcategory: wfw wfwg awfax gpf Additional reference words: 3.11 Microsoft pc at work fax Microsoft at work fax efax q&a qanda issues tshoot WFWG 3.11: 3C509 MLID May Cause Lost Connections and Hangs Article ID: Q111712 ---------------------------------------------------------------- ---- The information in this article applies to: - Microsoft Windows for Workgroups version 3.11 ---------------------------------------------------------------- ---- SYMPTOMS ======== If you use the 3COM EtherLink III (3C509) network interface card (NIC) and the 3COM ODI MLID (3C509.COM or 3C5x9.COM) with Windows for Workgroups version 3.11 and Novell NetWare is installed as your secondary network, you may encounter the following problems: - Copying large blocks of data across the network cause the computer to stop responding (hang). - The computer inadvertently loses network connections. CAUSE ===== The 3C509 NIC has a 4-kilobyte (K) FIFO buffer. This allows 2K to receive and 2K to transmit. If more information than this is passed through the card at one time, that information is lost. In addition, the 3C509 uses approximately 88 percent of the CPU's resources when it is transmitting. RESOLUTION ========== Microsoft, in joint effort with 3COM has developed an Application Note (WG1004) to correct this problem. This Application Note provides an updated MSODISUP.386 file. For more information, query on the following words in the Microsoft Knowledge Base: appnote and msodisup.386 and WG1004 As a temporary workaround for this problem, try one of the following: - Use the IPX Monolithic driver. -or- - Use only the NDIS 3 drivers that ship with Windows for Workgroups 3.11. -or- - Use NetBEUI as your only protocol. -or- - With the "IPX/SPX Compatible Transport with NetBIOS" set as the default protocol, place the following setting in the [Networks] section of the SYSTEM.INI file: [Networks] SlowLANAs=0 -or- - If you installed Windows for Workgroups 3.11 over Windows for Workgroups version 3.1, use the MSIPX protocol from Windows for Workgroups 3.1. KBCategory: kbnetwork kb3rdparty kbfile kbappnote KBSubcategory: Additional reference words: appnote 3.11 wfw wfwg Recovering Windows 3.1 After Installing WFWG 3.11 Article ID: Q111737 ---------------------------------------------------------------- ------ The information in this article applies to: - Microsoft Windows operating system versions 3.1, 3.11 - Microsoft Windows for Workgroups version 3.11 ---------------------------------------------------------------- ------ Microsoft cannot guarantee this procedure will work in every situation. If this procedure fails, you must reinstall Windows 3.1 and Windows-based applications to a new directory. SUMMARY ======= After you install Windows for Workgroups version 3.11, it may be possible to restore your installation of Microsoft Windows 3.1. MORE INFORMATION ================ This procedure can be used only if you ran Windows for Workgroups Setup once. If you ran Setup more than once, it is not possible to restore the original Windows configuration files; therefore, Windows 3.1 must be reinstalled to an empty directory. Also, any third-party software that replaces Windows virtual device drivers (VxDs) may need to be reinstalled after you reinstall Windows 3.1. If you did run Windows for Workgroups Setup one time only, and you want to restore your Windows 3.1 installation, follow the steps below. 1. Start your machine with MS-DOS. 2. Edit the CONFIG.SYS and AUTOEXEC.BAT files to remove the Windows for Workgroups 3.11 IFSHLP.SYS and NET START lines. For example, remove "device=c:\windows\ifshlp.sys" from the CONFIG.SYS file and "c:\windows\net start" from the AUTOEXEC.BAT file. 3. Copy the WININI.W31 and SYSINI.W31 files from the Windows directory to a floppy disk. 4. Run Windows version 3.1 Setup and choose Custom Setup. A message then appears stating that Setup has found a previous version of Microsoft Windows on your system and recommends that you perform an upgrade. Specify the Windows for Workgroups directory as the target directory and press ENTER. When the System Information screen appears, change the "Network = Microsoft Windows Network (version 3.11)" entry to: Network = No Network Installed 5. The Windows 3.1 Setup program detects some newer drivers (for example, COMM.DRV) and prompts you to replace them with the Windows 3.1 drivers. Press the ESC key to replace each file with the older version of the file. 6. After Setup loads Windows, it begins to copy files to your system. Setup again finds newer versions than those provided with Windows 3.1. Setup prompts you to keep or replace each file. Replace each file by choosing Yes when prompted. Setup finds version conflicts for the following files: SYSEDIT.EXE DDEML.DLL OLECLI.DLL MAIN.CPL TOOLHELP.DLL PRINTMAN.EXE WINFILE.EXE SHELL.DLL COMMDLG.DLL CLIPBRD.EXE WINOA386.MOD 7. From the floppy disk used in step 3, copy the WININI.W31 file to the Windows directory as WIN.INI and the SYSINI.W31 file to the Windows directory as SYSTEM.INI. For example, if your Windows directory is C:\WINDOWS and the floppy disk is in drive A, type the following two commands at the MS-DOS command prompt and press ENTER after each line: copy a:winini.w31 c:\windows\win.ini copy a:sysini.w31 c:\windows\system.ini 8. Reboot your computer and start Windows 3.1 by typing "win" (without the quotation marks) at the MS-DOS command prompt and then pressing ENTER. 9. Remove the program icons that were added by the Windows for Workgroups Setup program. To do so: a. Delete the following icon from the Main group: Clipbook Viewer b. Delete the Network group. c. Delete the Hearts icon from the Games group. 10. Remove the Windows for Workgroups 3.11 files below from the Windows directory and Windows SYSTEM subdirectory. Files in the Windows directory to delete: AWCAS.DLL AWCLASS1.DLL AWCLASS2.DLL AWFAXIO.DLL AWFAXPROT.DLL AWT30.DLL CARDS.DLL CLIPSRV.EXE DLLSCHED.DLL EFAXPUMP.DLL EFAXRUN.DLL FAXCODEC.DLL FAXCOVER.DLL FAXMGR.EXE FAXEPT.DLL FAXVIEW.EXE IFKERNEL.EXE IFSHLP.SYS IMPEXP.DLL KEYVIEW.EXE LINEARIZ.DLL LOGONOFF.EXE MSFAX.HLP MSHEARTS.EXE MSHEARTS.HLP MSMAIL.EXE MSMAIL.HLP MSMAIL.INI MSMAIL.MMF MSREMIND.EXE MSSCHED.DLL NCDINFO.INI NDDENB.DLL NDISHLP.SYS NET.EXE NET.MSG NETDDE.EXE NETFAX.DLL NETH.MSG NETWATCH.EXE NETWATCH.HLP RINGIN.WAV RINGOUT.WAV NOTE: The file DEPCA.DOS in the list above is a network interface card (NIC) driver for a DEC Etherworks Turbo/TP Network Adapter. The NIC driver for your particular network card may be different. Files in the Windows SYSTEM subdirectory to delete: AB.DLL CMC.DLL COMMCTRL.DLL DEMILAYR.DLL EFAXDRV.DRV FAX.CPL FAXNSP.DLL FAXSTUB.DLL FRAMEWRK.DLL IFSMGR.386 IOS.386 LM21DRV.UPD LMSCRIPT.EXE LMSCRIPT.PIF LPT.386 MAILMGR.DLL MAILSPL.EXE MAPI.DLL MSSFS.DLL NCDW.DLL NDDEAPI.DLL NDIS.386 NDIS2SUP.386 NETBEUI.386 NETWORK.INF NWLINK.386 NWNBLINK.386 PABNSP.DLL RMM.D32 SCONFIG.DLL SENDFILE.DLL SERIAL.386 STORE.DLL UNIDRV.DLL UNIDRV.HLP VCACHE.386 VCOMM.386 VFAT.386 VFORMS.DLL VNETSUP.386 VPMTD.386 VREDIR.386 VSERVER.386 VSHARE.386 VXDLDR.386 WFWAUDIT.386 WFWNET.DRV WFWSETUP.DLL WINNET.INF NOTE: The file DECLAN.386 in the list above is the 386 enhanced mode version of the network interface card (NIC) referenced in the section above. The NIC driver for your particular network card may be different. 11. Quit and then restart Windows. 12. Correct the Windows Setup icon command line. a. From the Program Manager Main group, select Windows Setup either by using the keyboard or by clicking the icon once (do not double-click the Setup icon). b. From the File menu, choose Properties. c. Change the Command Line entry from WINSETUP.EXE to SETUP.EXE. d. Choose OK. After you follow these steps, Windows 3.1 should be successfully reinstalled. However, if Windows 3.1 does not perform as expected (for example, you receive error messages or the system stops responding [hangs]), you must reinstall Windows 3.1 and all Windows-based software to a new directory. KBCategory: kbsetup KBSubcategory: win31 wfw wfwg Additional reference words: 3.10 3.1 3.11 uninstall un-install deinstall remove recover WG1001: Updated SERIAL.386 Driver for WFWG Article ID: Q112300 ---------------------------------------------------------------- ----- The information in this article applies to: - Microsoft Windows for Workgroups version 3.11 ---------------------------------------------------------------- ----- Microsoft has an Application Note, "WG1001: Updated SERIAL.386 Driver for Windows for Workgroups. When you use Windows for Workgroups version 3.11 with serial communications software, you may experience the following problems: - If you are using a Pentium-based machine with a 16550 UART chip, your system stops responding (hangs) if there is data in the chip when the serial communications application attempts to open the communications port. - When you are using communications software, you may be able to make one connection after starting Windows for Workgroups, but any subsequent connections fail and may hang your system. The WG1001 disk included with this Application Note contains an updated SERIAL.386 driver that corrects both of these problems. You can obtain this Application Note from the following sources: - CompuServe, GEnie, and Microsoft OnLine - Microsoft Download Service (MSDL) - The Internet (Microsoft anonymous ftp server) - Microsoft FastTips Technical Library - Microsoft Product Support Services For complete information, see the "To Obtain This Application Note" section at the end of this article. THE TEXT OF WG1001 ================== ================================================================ ====== Microsoft(R) Product Support Services Application Note (Text File) WG1001: UPDATED SERIAL.386 DRIVER FOR WINDOWS(TM) FOR WORKGROUPS ================================================================= ===== Revision Date: 3/94 1 Disk Included The following information applies to Microsoft Windows for Workgroups, version 3.11. ---------------------------------------------------------------- ------- | INFORMATION PROVIDED IN THIS DOCUMENT AND ANY SOFTWARE THAT MAY | | ACCOMPANY THIS DOCUMENT (collectively referred to as an Application | | Note) IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER | | EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE IMPLIED | | WARRANTIES OF MERCHANTABILITY AND/OR FITNESS FOR A PARTICULAR | | PURPOSE. The user assumes the entire risk as to the accuracy and | | the use of this Application Note. This Application Note may be | | copied and distributed subject to the following conditions: 1) All | | text must be copied without modification and all pages must be | | included; 2) If software is included, all files on the disk(s) | | must be copied without modification (the MS-DOS(R) utility | | diskcopy is appropriate for this purpose); 3) All components of | | this Application Note must be distributed together; and 4) This | | Application Note may not be distributed for profit. | | | | Copyright (C) 1994 Microsoft Corporation. All Rights Reserved. | | Microsoft and MS-DOS are registered trademarks and Windows is a | | trademark of Microsoft Corporation. | | Pentium is a trademark of Intel Corporation | |---------------------------------------------------------------- -----| Introduction ------------ When you use Windows for Workgroups version 3.11 with serial communications software, you may experience the following problems: - If you are using a Pentium(TM)-based machine with a 16550 UART chip, your system stops responding (hangs) if there is data in the chip when the serial communications application attempts to open the communications port. A problem with the 16550 UART implementation causes the chip to become trapped in a mode in which data is always detected in its FIFO buffer. - When you are using communications software, you may be able to make one connection after starting Windows for Workgroups, but any subsequent connections fail and may hang your system. This problem occurs when SERIAL.386 sends an extra NUL character through the port when the communications software calls the CloseComm application program interface (API) function. While this does not normally cause problems, your second connection may fail with some modems. The WG1001 disk included with this Application Note contains an updated SERIAL.386 driver that corrects both of these problems. To install the updated SERIAL.386 file -------------------------------------- 1. Quit Windows for Workgroups. 2. Make a backup copy of the currently installed SERIAL.386 file by typing the following at the MS-DOS command prompt and then pressing ENTER ren :\serial.386 serial.old where : is the location of your Windows SYSTEM subdirectory. For example, if your Windows directory is called WINDOWS and is on drive C, type the following at the MS-DOS command prompt and then press ENTER: ren c:\windows\system\serial.386 serial.old 3. Insert the enclosed WG1001 disk in the appropriate floppy disk drive. 4. To copy the file to the Windows SYSTEM subdirectory, type the following at the MS-DOS command prompt and then press ENTER copy :\serial.386 where is the floppy disk drive containing the WG1001 disk and is the drive and directory of your Windows SYSTEM subdirectory. For example, if the WG1001 disk is in drive A and your Windows directory is called WINDOWS and is on drive C, type the following at the MS-DOS command prompt and then press ENTER: copy a:\serial.386 c:\windows\system STATUS ====== Microsoft has confirmed this to be a problem in Microsoft Windows for Workgroups version 3.11. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available. ---------------------------------------------------------------- ----- TO OBTAIN THIS APPLICATION NOTE =============================== - On CompuServe, GEnie, and Microsoft OnLine, Application Notes are located in the Microsoft Software Library. You can find WG1001 in the Software Library by searching on the word WG1001, the Q number of this article, or S14599. WG1001 is a compressed, self-extracting file. After you download WG1001, run it to extract the file(s) it contains. - Application Notes are available by modem from the Microsoft Download Service (MSDL), which you can reach by calling (206) 936-6735. This service is available 24 hours a day, 7 days a week. The highest download speed available is 14,400 bits per second (bps). For more information about using the MSDL, call (800) 936-4200 and follow the prompts. To obtain WG1001, download WG1001.EXE. WG1001.EXE is a compressed, self-extracting file. After you download WG1001.EXE, run it to extract the file(s) it contains. - On the Internet, Application Notes are located on the Microsoft anonymous ftp server, which you can reach by typing "ftp ftp.microsoft.com" (without the quotation marks) at the ">" command prompt. You can find WG1001.EXE in the SOFTLIB\MSLFILES directory. - You can have this Application Note mailed to you from the automated Microsoft FastTips Technical Library, which you can call 24 hours a day, 7 days a week at (800) 936-4200. NOTE: The FastTips Technical Library is available only to customers within the U.S. and Canada. - If you are unable to access the source(s) listed above, you can have this Application Note mailed to you by calling Microsoft Product Support Services Monday through Friday, 6:00 A.M. to 6:00 P.M. Pacific time at (206) 637-7098. If you are outside the United States, contact the Microsoft subsidiary for your area. To locate your subsidiary, call Microsoft International Sales Information Center at (206) 936-8661. KBCategory: kbother kbfile kbappnote KBSubcategory: wfw Additional reference words: appnote 3.1 3.10 WFWG appnote wincomm WFWG Err Msg: Error 58: The Network Has Responded Incorrectly Article ID: Q113238 ---------------------------------------------------------------- ----- The information in this article applies to: - Microsoft Windows for Workgroups version 3.11 --------------------------------------------------------------------- SYMPTOMS ======== Using NET START NETBEUI with Microsoft Windows for Workgroups 3.11 causes the computer to stop responding (hang) while loading Windows for Workgroups or causes the following error message when Windows loads: Error 58: The network has responded incorrectly. CAUSE ===== This error message occurs if you run NET START NETBEUI before loading Windows for Workgroups with the "IPX/SPX Compatible Transport with NetBIOS" and NetBEUI protocols installed. RESOLUTION ========== To correct this problem: - Use NET START without the NetBEUI parameter. -or- - Remove the "IPX/SPX Compatible Transport with NetBIOS" protocol. -or- - Type "net stop netbeui" (without the quotation marks) before loading Windows for Workgroups. (This unloads the real-mode NetBEUI protocol.) MORE INFORMATION ================ Some NetBIOS applications require the use of NET START NETBEUI to access NetBIOS under Windows for Workgroups 3.1. Most NetBIOS applications do not require this under Windows for Workgroups 3.11. For example, Delrina WinFax Pro 3.0 for Networks requires NET START NETBEUI in order for its real-mode drivers to load. Since NET START NETBEUI disables file and print sharing in Windows for Workgroups, and can cause the above error message, run NET START NETBEUI, load the WinFax real-mode drivers, and then run NET STOP NETBEUI before loading Windows for Workgroups. KBCategory: kbnetwork kberrmsg kbenv KBSubcategory: wfw wfwg Additional reference words: 3.11 hangs crash hung RAS ErrMsg: Error 692: Hardware Failure in Port or Attached... Article ID: Q116053 ---------------------------------------------------------------- -------- The information in this article applies to: - Microsoft Windows for Workgroups version 3.11 ---------------------------------------------------------------- --------- SYMPTOMS ======== When you dial a Remote Access Services (RAS) server, the modem starts to initialize and then the following error message is displayed: Error 692: Hardware failure in port or attached device. Or, when you try to manually dial a RAS server, the following error message appears after you choose the Done button: all devices connected The computer then stops responding (hangs). NOTE: In this situation, other Windows-based communication applications (such as Windows for Workgroups Terminal) appear to work correctly. CAUSE ===== These error messages occur if RAS cannot correctly communicate with the modem. There are several possible causes: - The modem is turned off or malfunctioning. Try resetting the modem. - The serial cable is incorrect. If you suspect this is the case, refer to the "Cabling Requirements" section in Help for more information about requirements for correct cabling. - If the serial cable is loose. Remove the cable and then reattach it. - The handshaking options for the modem need to be adjusted. - The modem is unsupported, or the chosen emulation may be incorrect. RAS uses a file called MODEM.INF in the Windows SYSTEM subdirectory to send the right communication strings to the modem through the selected modem in RAS. Use a text editor, such as Windows Write, with the No Conversion option selected to open the MODEM.INF file. Then find the modem you have selected in RAS and check the COMMAND_INIT string, which is the communication string RAS sends to set up the modem for communication. Refer to the modem documentation or check with the modem manufacturer for the correct communication string for your modem. - You did not choose the correct modem for use with RAS. Check your modem installation as follows: 1. Choose the RAS icon in the Network group. 2. Choose Setup from the menu list. 3. Select Configure. 4. Check the device selected and the port to which it is assigned. - The COMM.DRV file located in the Windows SYSTEM subdirectory is not the one that ships with Windows for Workgroups version 3.11. See the appropriate section below. - You are using an XJACK modem and need an updated MODEM.INF file. See the appropriate section below. - You are using an GVC FM14400 modem need an updated MODEM.INF file. See the appropriate section below. - You are using a US-Robotics 14400 Sportster. See the appropriate section below. If you are not using one of the above modems, or if you are using one of them but have followed the procedures in this article without success, use the steps in the next section to try to isolate the problem. MORE INFORMATION ================ Checking for the Correct COMM.DRV File -------------------------------------- The COMM.DRV file that ships with Windows for Workgroups 3.11 has a file date of 11/01/93 and a file size of 5968 bytes. If the COMM.DRV file is incorrect, rename it and then expand a new copy from Windows for Workgroups 3.11 Disk 2 (for both the 5.25-inch and 3.5-inch disk sets) by using the following command expand :\comm.dr_ c:\windows\system\comm.drv where names the drive containing Disk 2. You Are Using an XJACK Modem and Need an Updated MODEM.INF File --------------------------------------------------------------- Obtain the new MODEM.INF file that Megahertz has written for its PCMCIA modems. The file can be found in the Modem Vendor forum on CompuServe (go modemvend) in the MEGAHERTZ library. The file to download is RASDRI.EXE. To install the new MODEM.INF file, rename the original MODEM.INF in the Windows SYSTEM subdirectory, and copy the new file to that same directory. You Are Using a GVC FM14400 Modem --------------------------------- Obtain the new GVC MODEM.INF file from the GVC bulletin board service (BBS). The file to download is WFWRA.EXE. To install the new MODEM.INF file, rename the original MODEM.INF in the Windows SYSTEM subdirectory, and copy the new file to that same directory. You Are Using a US-Robotics 14400 Sportster or Courier V.32bis -------------------------------------------------------------- NOTE: Microsoft does not encourage nor support user changes to .INF files; therefore, Microsoft Product Support Services (PSS) does not support the procedure in this article. Although we have tested the following procedure and it appears to function as described; we strongly recommend that you make a backup copy of your .INF file before you proceed. To correct this problem, edit the modem initialization entry (COMMAND_INIT=) in the [US Robotics Sportster 14400] or [US Robotics Courier V.32bis] section of the MODEM.INF file as follows: 1. Run Microsoft Windows for Workgroups Write and open the MODEM.INF file. 2. Choose the No Conversion button. 3. From the Find menu, choose Find. 4. In the Find What box, type "[US Robotics Sportster 14400]" or "[US Robotics Courier V.32bis]" (without the quotation marks) and then choose Find Next. 5. Choose Cancel and then change "AT&F" to "ATZ&F" (without the quotation marks). For example, change COMMAND_INIT=AT&F&C1&D2 V1 S0=0 S2=128 S7=55 W1 S95=44 to: COMMAND_INIT=ATZ&F&C1&D2 X7 V1 S0=0 S2=128 S7=55 W1 S95=44 6. Save the MODEM.INF file. 7. Quit and restart RAS Phonebook. This issues a reset command that resets the modem to the factory defaults. KBCategory: kb3rdparty kberrmsg KBSubcategory: wfw wfwg wincomm Additional reference words: 692 serial network freeze lock string Windows for Workgroups: Error 58 on Protocol 0 - (Non-ODI) Article ID: Q119803 ---------------------------------------------------------------- ----- The information in this article applies to: - Microsoft Windows for Workgroups version 3.11 ---------------------------------------------------------------- ----- SYMPTOMS ======== When you start Windows for Workgroups, you receive one of the following error messages: - The following error occurred while loading protocol number 0. Error 58: The network responded incorrectly. -or- - Hardware failure error 5736 CAUSE ===== The RAMBIOS.SYS device driver in the CONFIG.SYS file can cause this error. RAMBIOS.SYS is an older driver used by video cards to control Flashc cards and allow for video RAM shadowing. It is not necessary on most 386 and higher computers. Some network cards use the same RAM address as RAMBIOS.SYS, which causes the network card to fail when binding. NOTE: You can also receive the above error message if you are using the HP Jet Direct Card and the device=HPVNPD.386 is removed or remarked out of the [386enh] section of the SYSTEM.INI file. For information on resolving this issue, contact Hewlett Packard (HP). RESOLUTION ========== Open the CONFIG.SYS file in a text editor (such as the MS-DOS Editor) and remove the following line: device=c:\rambios.sys KBCategory: kbnetwork kbdisplay kberrmsg kb3rdparty kbhw KBSubcategory: wfw wfwg Additional reference words: rambios 3.11 Windows Err Msg: Cannot Find KRNLxxx.EXE Article ID: Q70467 ---------------------------------------------------------------- ---- The information in this article applies to: - Microsoft Windows operating system versions 3.0, 3.0a, 3.1, 3.11 - Microsoft Windows for Workgroups versions 3.1, 3.11 ---------------------------------------------------------------- ---- SYMPTOMS ======== You may receive one of the following error messages when you try to start Windows or Windows for Workgroups: - Cannot find KRNL386.EXE - Cannot find KRNL286.EXE - Cannot find KRNL.EXE (version 3.0 only) CAUSE ===== These messages indicate that Windows cannot find the kernel necessary to run 386 enhanced, standard, or real mode (version 3.0 only). The kernel provides system services such as memory and resource management. WORKAROUND ========== To correct this problem: 1. Boot with clean AUTOEXEC.BAT and CONFIG.SYS files. 2. Make sure that your Windows directory is on your MS-DOS path. 3. Make sure that your path statement does not contain more than 128 characters. 4. Make sure that the correct kernel file indicated in the warning message actually exists in your Windows SYSTEM subdirectory. If you are running a shared copy of Windows, make sure the file is in the shared Windows directory. 5. Add the Windows SYSTEM subdirectory to your MS-DOS path. 6. Make sure your MS-DOS version is compatible with your computer. 7. If you are using a shared installation of Windows on a network server, make sure that your personal Windows directory and the shared Windows directory are on your MS-DOS path and are listed in that order. 8. Ensure you don't have any upper memory block (UMB) conflicts. For more information, query on the following words in the Microsoft Knowledge Base: troubleshooting and emm386.exe 4.45 9. Rebuild the SYSTEM.INI file. 10. As a last resort, reinstall Windows. KBCategory: kbenv kberrmsg kbtshoot KBSubcategory: win30 win31 wfw wfwg Additional reference words: tshoot 3.00 3.0 3.00a 3.0a 3.10 3.1 3.11 kernel kernel286 kernel386 KRNL386 KRNL286 win31 wfw wfwg Floppy Disk Drive Problems in 386 Enhanced Mode Article ID: Q75488 ---------------------------------------------------------------- ------ The information in this article applies to: - Microsoft Windows operating system versions 3.0, 3.0a, 3.1, 3.11 ----------------------------------------------------------------- ----- SYMPTOMS ======== If you are experiencing errors reading, writing, or formatting floppy disk drives while running Windows in 386 enhanced mode, follow the steps listed below to troubleshoot and resolve the problem. WORKAROUND ========== 1. Exit Windows. 2. To determine whether your system is reading the floppy disk directory, insert a disk in drive A, and type the following at the MS-DOS command prompt: dir a: NOTE: If you remove the disk from drive A and type "dir a:" (without the quotation marks) and the directory lists again, it is an indication of an improper CMOS version or incorrect hardware setup (for example, a 3.5-inch drive on a jumper for an XT computer). 3. To determine whether your system writes to the floppy disk drive, type the following at the MS-DOS command prompt copy a: where is any valid file on your hard disk. If the commands in steps 2 and 3 do not work, the problem is at the MS-DOS level. 4. Restart your computer using the minimum information in your AUTOEXEC.BAT file and CONFIG.SYS file that your computer needs to start up. For more information about how to do this, query on the following words in the Microsoft Knowledge Base: troubleshooting and autoexec.bat and config.sys and files NOTE: Anti-Virus software commonly causes this problem. 5. Does the floppy disk drive read problem go away when you run Windows in standard mode or real mode? To test this, start Windows by typing the following at the MS-DOS command prompt: win /s If everything works correctly in Windows, you know that the problem is related only to running Windows in 386 enhanced mode. If the problem is specifically related to 386 enhanced mode, you may be loading SYMEVNT.386 from Norton Utilities 8.0. For more information about SYMEVNT.386, query in the Microsoft Knowledge Base on the following words: symevnt.386 and norton If the problem is specifically related to 386 enhanced mode but you are not loading SYMEVNT.386, using the switches below may lessen the problem. Add these switches to the SYSTEM.INI file in the [386Enh] section in the order shown. If you find one of the switches works, you can try removing previous switches that had no effect. Note that the switches listed in item (b) should be added or removed as a pair. (See the MORE INFORMATION section of this article for an explanation of these switches.) a. IRQ9GLOBAL=YES b. HIGHFLOPPYREADS=NO EMMEXCLUDE=E000-EFFF c. VirtualHDIrq=OFF 6. Insert a semicolon (;) before the Load= and Run= lines in the WIN.INI file to ensure that nothing else is being loaded that could cause a problem. 7. Check to see if you can successfully issue commands in Windows at the MS-DOS command prompt. If commands work at the MS-DOS level, it indicates a BIOS or hard disk drive/floppy controller BIOS problem. 8. Is the floppy disk drive icon displayed in File Manager? If not, check your BIOS version and contact your hardware manufacturer for an update. 9. Disable any BIOS and video shadowing. Each computer may have a different way of disabling its shadowing. You will need to check your system documentation and follow the instructions provided there to perform this task. 10. Check for third-party or external floppy disk drivers. 11. Check the type and version of MS-DOS. MS-DOS versions earlier than 3.3 do not support 1.44-MB drives. 12. Check for hardware devices that may be using the same IRQ as the floppy disk drive controller. (By default, the floppy disk drive controller uses IRQ 6.) 13. Check to see if an IDE ATIO card is in use. This is an integrated card that contains a game port, serial port, parallel port, IDE, and floppy disk drive controller. Remove this card and insert a card that has only the IDE floppy disk drive controller on it. MORE INFORMATION ================ The following paragraphs explain the switches used in step 5 above. IRQ9Global= -------------------- Default: No Purpose: If enabled, this switch converts IRQ9 masks to global. Enable this setting if your system stops responding (hangs) when accessing a floppy disk drive, or make sure your system accesses the floppy disk drive before you start Windows. HighFloppyReads= ------------------------- Default: Yes Purpose: Normally, Windows turns a DMA verify to the area E000:0000- EFFF:FFFF into a read. In rare cases, this might cause the system to fail because some software might, as a result, write over the system's shadow RAM if you have it in this area. If this happens, disable this setting and set EMMExclude to E000-EFFF. EMMExclude= ---------------------------- Default: None Purpose: Specifies a range of memory that Windows will not scan to find unused address space. This has the side effect of turning off the RAM and ROM search code for the range. The range (two paragraph values separated by a hyphen) must be between A000 and EFFF. This scanning can interfere with some adapters that use the same memory area. The starting value is rounded down and the ending value is rounded up to a multiple of 16K. For example, you could set EMMExclude=C800-CFFF to prevent Windows from scanning the addresses C800:0000 through CFFF:000F. You can specify more than one range by including more than one EMMExclude line. VirtualHDIrq= ---------------------- Default: On Purpose: If enabled, Windows in 386 enhanced mode can terminate interrupts from the hard disk controller, bypassing the ROM routine that handles these interrupts. Some hard disk drives may require this setting to be disabled for interrupts to be processed correctly. If this setting is disabled, the ROM routine handles the interrupts, which slows down system performance. KBCategory: kbtshoot kbhw kbdisplay KBSubcategory: win30 win31 Additional reference words: tshoot 3.00 3.00a 3.10 3.11 central point norton Err Msg: 'Incorrect System Version' When Starting MS-DOS App Article ID: Q81609 ---------------------------------------------------------------- ------ The information in this article applies to: - Microsoft Windows operating system versions 3.1, 3.11 - Microsoft Windows for Workgroups versions 3.1, 3.11 ----------------------------------------------------------------- ----- SYMPTOMS ======== You may receive one of the following error messages when you try to run an MS-DOS-based application under Microsoft Windows or Windows for Workgroups in the 386 enhanced mode: - Incorrect system version; reinstall the 386 enhanced mode of Windows - Incompatible Version of Operating System CAUSES ====== The problem is probably caused by one of the following: - The video grabber does not match the virtual display device. - An old WINOA386.MOD file resides in the Windows\SYSTEM subdirectory. - The machine has a duplicate COMMAND.COM file (dated prior to your current version) in the Windows directory. - You have a WINOA386.MOD file in both the Windows and Windows\SYSTEM subdirectory. WORKAROUND ========== To correct these problems, see the appropriate section below. Wrong Video Grabber ------------------- The SYSTEM.INI file contains three entries that specify which video driver you use in the 386 enhanced mode of Windows. These are the "386Grabber" and "display.drv" entries in the [boot] section and the "display" entry in the [386Enh] section. The error message above usually occurs when one of these entries is not consistent with the others--usually due to using a Windows version 3.0 video driver with Windows version 3.1. If you are using display drivers not included with Windows 3.1, contact your display adapter manufacturer to get an updated driver installation disk. In many cases, you can work around this problem by manually installing the version 3.0 driver files that are included on the Windows 3.1 Setup disks. If your display driver works in Windows 3.0 using the standard VGA virtual display device file (specified by "display=*vddvga" in the [386Enh] section of the SYSTEM.INI file), then do the following: 1. Copy and expand the VDDVGA30.386 file from the Windows 3.1 Setup Disk 1 (5.25-inch or 3.5-inch disk set) into your Windows 3.1 SYSTEM subdirectory. To expand the VDDVGA30.386 file, use the Expand utility (EXPAND.EXE) in the Windows directory. If you are unsure of the syntax for using Expand, type "expand /?" (without quotation marks) at the MS-DOS command prompt. 2. Change the line "display=..." in the [386Enh] section of SYSTEM.INI to read: display=VDDVGA30.386 If your display driver works in Windows 3.0 using the standard VGA grabber file (specified by "386Grabber=VGA.3GR" in the [boot] section of the SYSTEM.INI file), then do the following: 1. Copy and expand the VGA30.3GR file from the Windows 3.1 Setup disks (Disk 3 for the 5.25-inch disk set and Disk 2 for the 3.5-inch disk set) into your Windows 3.1 SYSTEM subdirectory. To expand the VGA30.3GR file, use the Expand utility (EXPAND.EXE) in the Windows directory. If you are unsure of the syntax for using Expand, type "expand /?" (without quotation marks) at the MS-DOS command prompt. 2. Change the line "386Grabber=" in the [boot] section of the SYSTEM.INI file to read: 386Grabber=VGA30.3GR Old WINOA386.MOD File --------------------- To determine if this is the problem, do the following: 1. Run File Manager. 2. Change to the root directory (C:\). 3. From the File menu, choose Search. 4. In the Search For box, type "*.MOD" (without quotation marks). Make sure the Search All Subdirectories check box is selected, and choose the OK button. 5. When the Search Results window appears, choose All File Details from the View menu. 6. If the WINOA386.MOD file is not in the Windows\SYSTEM directory, or if the file is has a date earlier than March 10, 1992, delete it. 7. If you deleted a file in step 6, copy and expand the WINOA386.MOD file from the Windows 3.1 Setup Disk 4 (5.25-inch or 3.5-inch disk set) into your Windows 3.1 SYSTEM subdirectory. To expand the WINOA386.MOD file, use the Expand utility (EXPAND.EXE) in the Windows directory. If you are unsure of the syntax for using Expand, type "expand /?" (without quotation marks) at the MS-DOS command prompt. Duplicate COMMAND.COM File -------------------------- You should have two COMMAND.COM files on your machine: one in your root directory and the other in the directory that contains your MS-DOS files (typically C:\DOS). If you have an extra COMMAND.COM file, it is probably in your Windows directory and it is probably dated prior to the version of COMMAND.COM loaded when you booted MS-DOS. You need to delete this file. To verify that this is the problem, double-click on the COMMAND.COM file in the root directory and it will launch a virtual MS-DOS machine. Duplicate WINOA386.MOD File --------------------------- To work correct this situation, delete the WINOA386.MOD file from the Windows directory. KBCategory: kbother kbdisplay kbtshoot kberrmsg KBSubcategory: wfwg win30 win31 wfw wfwg Additional reference words: tshoot 3.10 3.1 3.00 3.0 3.11 applications c:\windows Permanent Swap Files and the Disk Partition Table Article ID: Q82373 ---------------------------------------------------------------- ---- The information in this article applies to: - Microsoft Windows operating system versions 3.1, 3.11 ---------------------------------------------------------------- ---- SYMPTOM ======= When creating a swap file, you may receive an error message similar to the following: The partitioning scheme used on your hard disk prevents the creation of a permanent swap file. This error message can display whether you use the Virtual Memory dialog box during a custom Windows Setup, or the 386 Enhanced option in Control Panel to create swap files. CAUSE ===== This message can result from one of the following: - A partition manager - A virus - Uninitialized fields in the partition table MORE INFORMATION ================ Windows is very careful about what hard disks it uses when it creates permanent swap files. Windows would cause serious disk errors and data loss if it incorrectly modified a disk that is formatted with special software. To prevent damaged disks and lost data, Windows makes absolutely sure that it understands the exact format of the disk. One of the checks performed by Control Panel (and Setup, because Setup uses Control Panel to create a swap file when a custom setup is performed) is to look for disk partitioning software, such as Disk Manager or SuperStor. This is done by examining the partition table on the disk. If partitioning software is found, Control Panel displays an error message. This message does not imply that the partitioning software is incompatible with Windows; it simply means that a permanent swap file cannot be created on that disk. The following conditions can cause Control Panel to mistakenly detect partitioning software: - Another operating system is installed on the computer and happens to use the same partition type number (there are only 255 partition type numbers available); that partition is detected as one using partitioning software. There is no way to work around this problem if this is the cause. - The machine is infected with a virus. Some viruses create their own "foreign" disk partitions and set themselves up as the boot operating system (for example, the Michelangelo virus). If no other explanation for the disk partition error can be found, the disk should be scanned for viruses. When the virus is removed, Windows should be able to create the permanent swap file. - The disk drive may have been partitioned in the past with partitioning software, and was later repartitioned using MS-DOS version 4.01 or 5.0 FDISK. MS-DOS and FDISK support only four partitions on a disk, while some partition software supports more than four. Therefore, FDISK does not reset partitions in the extra entries. As a result, Windows interprets these invalid entries as an incompatible disk partition. - Ontrack Software Disk Manager-N utility partitions and formats part of a hard drive as a Novell file server. When a machine configured with Disk Manager-N is started, the Novell utility attached to the master boot record (MBR) loads and gives you the option of starting the system on the MS-DOS partition or to the Novell file server partition. If your hard disk has been partitioned with Disk Manager-N, you cannot create a permanent swap file under Microsoft Windows 3.1. The following text was taken from the Disk Manager README file: DISK MANAGER - N DISK MANAGER - N is a disk installation utility tailored specifically for the NOVELL local area network. This utility replaces the COMPSURF utility from NOVELL. DISK MANAGER - N installs disks running under NETWARE 86, ADVANCED NETWARE 86, and ADVANCED NETWARE 286. KBCategory: kbnetwork kbdisplay kb3rdparty kbsetup kberrmsg KBSubcategory: win31 Additional reference words: 3.10 scheme swapfile 3.11 Michael Angelo Causes of General Protection Faults Article ID: Q82710 ---------------------------------------------------------------- ------ The information in this article applies to: - Microsoft Windows operating system versions 3.1, 3.11 ---------------------------------------------------------------- ------ SUMMARY ======= The Intel 80286, 80386, and 80486 CPUs can detect when a program does something wrong. The most common problems are stack faults, invalid instructions, divide errors (divide by zero), and general protection faults. These generally indicate nonstandard code in an application. MORE INFORMATION ================ The following faults can occur in a Windows application, in Windows itself, or in a Windows device driver (for example, a video display driver). Stack Fault (Interrupt 12) -------------------------- Reasons for a stack fault are: - An instruction tries to access memory beyond the limits of the Stack segment (POP, PUSH, ENTER, LEAVE, or a stack relative access: MOV AX, [BP+6]). - Loading SS with a selector marked not present, but otherwise valid (shouldn't happen under Windows). Stack faults are always fatal to the current application in Windows. Invalid Instruction (Interrupt 6) --------------------------------- The CPU detects most invalid instructions, and generates an Interrupt 6. This is always fatal to the application. This should never happen, and is usually caused by executing data instead of code. Divide Error (Interrupt 0) -------------------------- This is caused when the destination register cannot hold the result of a divide operation. It could be divide by zero, or divide overflow. General Protection Fault (Interrupt 13) --------------------------------------- All protection violations that do not cause another exception cause a general protection exception. This includes, but is not limited to: - Exceeding the segment limit when using the CS, DS, ES, FS, GS segments. This is a very common bug in programs, usually caused by miscalculating how much memory is required in an allocation. - Transferring execution to a segment that is not executable (for example, jumping to a location that contains garbage). - Writing to a read-only or a code segment. - Loading a bad value into a segment register. - Using a NULL pointer. A value of 0 is defined as a null pointer. In protected mode, it is always invalid to use a segment register that contains 0. KBCategory: kbenv kbdisplay KBSubcategory: win31 winmem gpf Additional reference words: 3.10 gpfault 3.0a Windows 3.1 Setup Error Codes (S000 through S022) Article ID: Q82770 ---------------------------------------------------------------- ---- The information in this article applies to: - Microsoft Windows operating system versions 3.1, 3.11 ---------------------------------------------------------------- ---- SUMMARY ======= When a Setup error message contains an error code, it also includes some text indicating what Setup was trying to do, for example, copying a file. The text of the error message indicates whether the error is fatal or not. In some non-fatal cases, Setup may be performing an operation (such as copying a file) that is needed in order to run Windows. Other times the error may prevent some specific feature of Windows from operating properly. In many cases, the error code is an MS-DOS extended error code. These error codes are between 0 and 100. Setup-specific error codes have two different formats, depending on whether the error occurs during the character (MS-DOS) mode or the Windows graphical user interface (GUI) mode portion of Setup. The character mode Setup-specific error numbers are in the format "Snnn", where "nnn" is any three digits. The GUI mode error numbers have codes greater than 200. MORE INFORMATION ================ Character Mode Setup Error Codes -------------------------------- S001 Could not open SETUP.INF. SETUP.INF should reside on the first Windows Setup disk for first-time installations or upgrades and should reside in the WINDOWS\SYSTEM subdirectory when Setup is used to change the system configuration after Windows has been set up. If you are changing the configuration, make sure SETUP.INF does not exist in the WINDOWS directory and copy SETUP.INF from the first Windows Setup disk to the WINDOWS\SYSTEM subdirectory and try again. If it is a first-time installation or upgrade, make sure to set the current drive and directory to the location of the Setup program and then run Setup from the MS-DOS prompt. S002 Could not load SETUP.INF. Usually due to lack of memory. May also be due to a corrupt SETUP.INF. Should not occur during a first-time installation or upgrade. After making sure that there is enough memory, follow the instructions for S001. S004 Entry not found in SETUP.INF: [winexec].krnl386. Should not occur during first-time installation or upgrade. Setup has probably found an invalid SETUP.INF on the user's system. Follow the instructions for S001. S005 Entry not found in SETUP.INF: [winexec].krnl286. Setup has probably found an invalid SETUP.INF on the user's system. Follow the instructions for S001. S006 Entry not found in SETUP.INF: [winexec].dosx. Setup has probably found an invalid SETUP.INF on the user's system. Follow the instructions for S001. S007 Entry not found in SETUP.INF: [special_adapter].cdrom. Setup has probably found an invalid SETUP.INF on the user's system. Follow the instructions for S001. S008 Entry not found in SETUP.INF: [winexec].exechimem. Setup has probably found an invalid SETUP.INF on the user's system. Follow the instructions for S001. S009 Entry not found in SETUP.INF: [winexec].himemcmd. Setup has probably found an invalid SETUP.INF on the user's system. Follow the instructions for S001. S010 Entry not found in SETUP.INF: [data].welcome. Setup has probably found an invalid SETUP.INF on the user's system. Follow the instructions for S001. S012 Entry not found in SETUP.INF: [machine] . Setup has probably found an invalid SETUP.INF on the user's system. Follow the instructions for S001. S013 Entry not found in SETUP.INF: [machine] . Setup has probably found an invalid SETUP.INF on the user's system. Follow the instructions for S001. S014 Entry not found in SETUP.INF: [winexec].execstd. Setup has probably found an invalid SETUP.INF on the user's system. Follow the instructions for S001. S015 Entry not found in SETUP.INF: [winexec].execcmd. Setup has probably found an invalid SETUP.INF on the user's system. Follow the instructions for S001. S016 Entry not found in SETUP.INF: [user] section. Setup has probably found an invalid SETUP.INF on the user's system. Follow the instructions for S001. S017 Entry not found in SETUP.INF: [user] section empty. Setup has probably found an invalid SETUP.INF on the user's system. Follow the instructions for S001. S018 Entry not found in SETUP.INF: [user] section corrupt. Setup has probably found an invalid SETUP.INF on the user's system. Follow the instructions for S001. S019 WIN.COM not created. This may be due to missing files, a bad SETUP.INF or OEMSETUP.INF, lack of disk space, or an inability to create or modify the WIN.COM file. When you first install Windows or change display drivers, Setup creates the file WIN.COM from the file WIN.CNF and displays the dependent logo files, usually named *.lgo and *.rle. The logo files are specified in the .INF file for the chosen display. Make sure you do not have virus-protection software that does not allow executables to be modified. Try changing the display after exiting Windows and running Setup from the MS-DOS prompt. If you are selecting an original equipment manufacturer (OEM) display, try one of the display drivers that are shipped with Windows 3.1 to see if the OEMSETUP.INF file is not valid or if it specifies files that do not exist. If selecting a supplied display driver does not work, make sure the SETUP.INF file is valid (see error S001 above). S020 SYSTEM.INI was not correctly updated. This will occur when attempting to configure Windows with a new device or for a new system software configuration. The main reason for this problem occurring is lack of memory or a corrupt SYSTEM.INI file. It is also possible to get this error because of a corrupt .INF file. Make sure there is enough memory and that the SYSTEM.INI file is of a reasonable size (not much more than 5K) and try the operation again. Try selecting a different component (for example, select No Network instead of the network selected or select VGA instead of the display that is selected). If this succeeds, copy the SYSTEM.INI file to a backup disk and try again. If not, the SYSTEM.INI or SETUP.INF file is probably corrupted. S021 SYSTEM.INI was not correctly updated. See S020 above. S022 Setup did not save its state in the SYSTEM.INI file. This is due to either insufficient memory or a corrupt SYSTEM.INI file. KBCategory: kbsetup kbdisplay kberrmsg KBSubcategory: win31 Additional reference words: 3.1 3.10 3.11 messages The WIN.INI [Compatibility] Section Article ID: Q82860 ---------------------------------------------------------------- - The information in this article applies to: - Microsoft Windows operating system versions 3.1, 3.11 ---------------------------------------------------------------- - SUMMARY ======= This article discusses the Microsoft Windows version 3.1 WIN.INI [Compatibility] section. MORE INFORMATION ================ Compatibility bits are defined in the [Compatibility] section of the WIN.INI file for the following applications: - Microsoft Publisher - Microsoft Money - Microsoft Works - WordPerfect - Lotus Freelance - CC Mail - Microsoft Visual Basic - Ami Pro - Pixie - ObjectVision - Cricket Presents - Just Write - ExploreNet - Aporia - Packrat - Microcourier - Guide - Microsoft Excel - Ascend - MGX Draw - AccPack - Charisma - Persuasion - Ingress - Lotus Notes - Microsoft Draw - Turbo Tax When an application loads under Windows 3.1, KERNEL.EXE checks to see if the application was compiled exclusively for Windows 3.1. If the application was compiled for Windows 3.0, and will therefore run under Windows 3.0 or 3.1, KERNEL.EXE checks the module name and determines if any bits are defined for that name in the [Compatibility] section of the WIN.INI file. The following is a detailed explanation of compatibility bits. The symbolic name is defined in WINDOWS.H. The problem, listed for each application, will be fixed if the compatibility bit is defined. If these switches are in the [Compatibility] section of the WIN.INI file then these problems will not occur. The Windows 3.1 Setup program automatically inserts these switches into the WIN.INI, regardless of whether or not that application is on the machine. The symbolic names are internal only, they are not in the WINDOWS.H that ships with the Software Development Kit (SDK). Bit: 1 ------ Symbolic name: GACF_IGNORENODISCARD Meaning: Ignore NODISCARD flag if passed to GlobalAlloc(). C 6.x Runtime install library was allocating global memory improperly by incorrectly specifying the GMEM_NODISCARD bit. Apps: Publisher WIN.INI Line: notshell=0x0001 Problem: Setup for MS apps. does not work on 1M 286 machine. Money WIN.INI Line: notshell=0x0001 Problem: Setup for MS apps. does not work on 1M 286 machine. Works WIN.INI Line: notshell=0x0001 Problem: Setup for MS apps. does not work on 1M 286 machine. Bit: 2 ------ Symbolic name: GACF_FORCETEXTBAND Meaning: Separate text band from graphics band. Forces separate band for text, disallowing 3.1 optimization where Text and Graphics are printed in the same band. Word Perfect was assuming text had to go in second band. Apps: WordPerfect WIN.INI Line: WPWINFIL=0x0006 Problem: Can't print graphics in landscape mode. The compatibility switch doesn't completely fix the problem, just fixes it for certain memory configurations. Freelance WIN.INI Line: rem=0x8022 Problem: Freelance couldn't print presentation (.pre) files. Bit: 4 ------ Symbolic name: GACF_ONELANDGRXBAND Meaning: One graphics band only. Allows only one Landscape graphics band. Take as much memory as possible for this band. What doesn't fit in that band doesn't print. Apps: WordPerfect WIN.INI Line: WPWINFIL=0x0006 Problem: Can't print graphics in landscape mode. The compatibility switch doesn't completely fix the problem, just fixes it for certain memory configurations. Bit: 8 ------ Symbolic name: GACF_IGNORETOPMOST Meaning: Ignore topmost windows for GetWindow(HWND,GW_HWNDFIRST) Apps: CCMail WIN.INI Line: ccmail=0x0008 Problem: CCMail would GP fault when running any Windows applet from CCMail because it assumed the applet it starts will be at the top of the window list when winexec returns. Because of the addition of TOPMOST windows in Win 3.1, this isn't the case. The compatibility bit fixes this so GetWindow doesn't return a topmost window. Bit: 10 ------- Symbolic name: GACF_CALLTTDEVICE Meaning: Set the DEVICE_FONTTYPE bit in the FontType for TT fonts returned by EnumFonts(). Apps: Ami Pro WIN.INI Line: Amipro=0x0010 Problem: Font mapping problems, described below. WordPerfect WIN.INI Line: win2wrs=0x1210 Problem: WordPerfect was assuming TT fonts enumerated by the printer would have the device bit set. TT fonts are not device fonts, so this bit wasn't set. There were various font mapping problems, such as TNR appearing in Script or Symbol. Bit: 20 ------- Symbolic name: GACF_MULTIPLEBANDS Meaning: Manually break graphics output into more than one band when printing. Apps: Freelance WIN.INI Line: Rem=0x08022 Problem: Freelance wouldn't print graphics when there was enough memory and unidrv used only one band for printing. If the first band was the entire page, it didn't issue any graphics calls, thinking it was the text only band. This forces unidrv to use multiple bands. Bit: 40 ------- Symbolic name: GACF_ALWAYSSENDNCPAINT Meaning: SetWindowPos() must send a WM_NCPAINT message to all children, disallowing the 3.1 optimization where this message is only sent to windows that must be redrawn. Apps: Pixie WIN.INI Line: pixie=0x0040 Problem: File window overlaps the toolbox and doesn't repaint when a new file is opened. Pixie used the receipt of WM_NCPAINT messages to determine that they may need to reposition themselves at the top of the list. Win 3.0 used to send the messages to windows even when they didn't need to be sent; in particular if the window was within the bounding rect of any update region involved in a window management operation. ObjectVision WIN.INI Line: Vision=0x0040 Problem: Repaint problems with dialog boxes left on the screen after file.open or file.new operations. Cricket Presents WIN.INI Line: cp=0x0040 Problem: Tool window is not available when opening the app. Bit: 80 ------- Symbolic name: GACF_EDITSETTEXTMUNGE Meaning: Strings that are passed to Edit Controls by WM_SETTEXT are forced to upper case. Just Write was expecting this behavior, which was a bug in 3.0. Apps: Just Write WIN.INI Line: JW=0x42080 Problem: Just Write wouldn't change the extension in the file.open dialog when opening a file of a different format. Just Write calls SetDlgItemText to set the default extension in edit controls during WM_INITDIALOG processing. SetDlgItemText ultimately calls text insert routine which had a bug in 3.0 where it converted the case of the text passed in dependent on edit control style. Thus, under 3.0, SetDlgItemText was (wrongly) modifying the string passed in. The app has worked around the bug in 3.0 and is now failing in 3.1 since the bug has been fixed. The compatibility bit reverts to 3.0 behavior. Bit: 100 -------- Symbolic name: GACF_MOREEXTRAWNDWORDS Meaning: Add 4 to the extra bytes (CBWNDEXTRA) in the window instance and class instance structures. In Windows 3.0, even if you didn't allocate extra window/class words, you could still access them and corrupt Windows internally. In Windows 3.1, you are prevented from accessing extra words you didn't allocate so that apps won't corrupt windows. This switch forces extra words for all classes/windows created by the given application. Apps: Compton's MM Ency WIN.INI Line: TME=0x0100 Problem: Crashes choosing atlas. Caused by not initializing the WNDCLASS.cbWndExtra field. ExploreNet WIN.INI Line: netset2=0x0100 Problem: Application error selecting update in "Input Form" window. Caused by the app specifying 0 extra bytes when creating the window class. Aporia 1.4 WIN.INI Line: aporia=0x0100 Problem: Aporia icons don't appear on the desktop. Hangs the system. App says it wants 1 extra byte in the RegisterClass, then does a SetWindowWord (2 bytes), then GetWindowLong (4 Bytes). Bit: 200 -------- Symbolic name: GACF_TTIGNORERASTERDUPE Meaning: Don't enumerate Duplicate bit map fonts for TT fonts. Times New Roman was displayed and printed as a vector font. We install bit map fonts for Arial and Times New Roman at sizes 8,10 (EGA resolution). When we enumerate fonts for face names Arial and Times New Roman, we would enumerate the sizes available in the bit map fonts and one size for the corresponding true type font. This confused the font mapper in WordPerfect. It would somehow get confused into believing that a TNR font was available for only the two bit map sizes and map a request for a larger size to a Roman vector font. Apps: Word Perfect WIN.INI Line: Win2wrs=0x01210 Problem: Some fonts displayed as vector fonts. GDI will not enumerate raster fonts which have the same face or family name as a TT font if TT is enabled and the compatibility bit is set. Visual Basic WIN.INI Line: vb=0x0200 Problem: Reports duplicate font sizes. Bit: 800 -------- Symbolic name: GACF_DELAYHWHNDSHAKECHK Meaning: Don't check hardware handshaking on SetCommState(). Do not check hardware handshaking (CTS and DSR) on SetCommState(). (Reverts to 30 behavior.) Packrat could not Dial. It only checked for DSR, but this is not set until carrier detect. A bug existed in win30 where SetCommState never checked DSR and CTS. If a serial printer was off-line, data would be sent to the COM port anyway, causing lost data. Apps: Packrat WIN.INI Line: packrat=0x0800 Problem: Packrat didn't dial using modem on COM2. Microcourier WIN.INI Line: mcourier=0x800 Problem: Couldn't connect to modem using COM2. Bit: 1000 --------- Symbolic name: GACF_ENUMHELVNTMSRMN Meaning: Enumerates TmsRmn and Helv. Some apps are broken because they relied on 3.0 fonts Helv and Tms Rmn by name. Font Substitution covers much of these problems but we cannot legally enumerate Helv and Tms Rmn for future apps, so it was dropped. We still have the exact same fonts, but now under the names MS Sans Serif and MS Serif, and will enumerate them as Helv and Tms Rmn when this bit is set. (We are allowed to do this for backwards compatibility.) Apps: Spinnaker + WIN.INI Line: plus=0x01000 Problem: Text alignment and spacing problems in buttons and titles. Fix only works if Smallfonts come after serif and sans serif entries. Setup does this automatically. Milestones, etc. WIN.INI Line: milesv3=0x1000 Problem: Text is unreadable when the app is started. App does its own font mapping and gets confused when it can't find Tms Rmn. Guide WIN.INI Line: guide=0x1000 Problem: Text problems. Excel WIN.INI Line: Excel=0x1000 Problem: Can't get past point where you have to enter a point size in the tutorial. WordPerfect WIN.INI Line: win2wwrs=0x1210 Problem: Uses a vector font for TmsRmn. Bit: 2000 --------- Symbolic name: GACF_ENUMTTNOTDEVICE Meaning: Turns off DEVICE_FONTTYPE. Some apps fail to enumerate more that one size of true type fonts because they interpret the DEVICE_FONTTYPE flag incorrectly. They assume the font must be device resident and disregard the case where the font is downloaded (as TT can be). Therefore, when TT is correctly enumerated with the device bit set, the apps check the device capabilities to see if the printer can scale fonts. If the device cannot, the app assumes one size of for the current font. This problem is not seen on postscript printers which can download and scale fonts, nor on dot matrix printers which cannot download fonts. This Compatibility bit simply checks all the above conditions and selectively turns the DEVICE_FONTTYPE off. Apps: Pagemaker 4.0 WIN.INI Line: pm4=0x2000 Problem: Not all point sizes listed for some printers. Designer 3.1 WIN.INI Line: designer=0x2000 Problem: Font size reverts to 6 point when selecting a TT font in the font dialog. Ascend 3.1 WIN.INI Line: planner=0x2000 Problem: TT fonts only allow one point size. MGXDraw 3.0 WIN.INI Line: draw=0x2000 Problem: Shows no font sizes for TT fonts. AccPack WIN.INI Line: winsim=0x2000 Problem: Lists only one point size for TT fonts. Charisma WIN.INI Line: charisma=0x2000 Problem: Not all point sizes listed for some printers. Persuasion WIN.INI Line: pr2=0x2000 Problem: Lists only one point size for TT fonts. Just Write WIN.INI Line: jw=0x42080 Problem: Lists only one or two point sizes for TT fonts. Bit: 4000 --------- Symbolic name: GACF_SUBTRACTCLIPSIBS Meaning: This flag affects the way window invalidation works for non- WS_CLIPSIBLINGS parent windows and their children (e.g., dialog boxes and dialog controls). Normally, if two children of a non-WS_CLIPSIBLING parent overlap, and an area that contains both of those windows is invalidated (either by a call to InvalidateRect or through window rearrangement), both of the windows will get invalidated, even if one or both is WS_CLIPSIBLINGS. With GACF_SUBTRACTCLIPSIBS, any sibling window underneath a WS_CLIPSIBLINGS window will not be invalidated in the part of the window that is beneath the WS_CLIPSIBLINGS window. This situation arises most commonly when windows that are supposed to appear overlapped don't seem to overlap properly. Applications that implement drop down combo boxes as child windows of dialog boxes will exhibit this problem (e.g., Lotus Notes 2.1 drive drop downs). It's often hard to tell whether a drop down is implemented as a top-level window (e.g., the Windows system combo boxes) or as a child window -- if there seem to be overlapping problems, then GACF_SUBTRACTCLIPSIBS could be the solution. Apps: Lotus Notes 2.0 & 1 WIN.INI Line: _BNOTES=0x24000 Problem: Pull down drive list box pops down behind a list box which is already on the screen. Ingress WIN.INI Lines: wagl=0x4000 waglr=0x4000 Problem: Overlapping child controls. Bit: 8000 --------- Symbolic name: GACF_FORCETTGRAPHICS Meaning: Apps: Freelance WIN.INI Line: rem=0x8022 Problem: Freelance wouldn't print TT unless print TT as graphics was selected. Bit: 10000 ---------- Symbolic name: GACF_NOHRGN1 Meaning: This bit affects applications that depend on a bug in the 3.0 GetUpdateRect() function. Under 3.0, GetUpdateRect would not always return the rectangle in logical DC coordinates: if the entire window was invalid, the rectangle was sometimes returned in window coordinates. This bug was fixed for 3.0 and 3.1 apps in Windows 3.1: coordinates are ALWAYS returned in logical coordinates. This bit re- introduces the bug in GetUpdateRect(), for those applications that depend on this behavior. Apps: MSDraw WIN.INI Line: ED=0x00010000 Problem: Canvas not redrawn properly opening specific MSDraw objects in Winword. Bit: 20000 ---------- Symbolic name: GACF_NCCALCSIZEONMOVE Meaning: 3.1 optimized WM_NCCALCSIZE if a window was just moving, where 3.0 always sent it. This bit causes it to be sent always, as in 3.0. Apps: Lotus Notes WIN.INI Line: _BNOTES=0x24000 Problem: Navigator bar of window fails to redraw when the window is moved across the desktop. Bit: 40000 ---------- Symbolic name: GACF_SENDMENUDBLCLK Meaning: Passes double-clicks on a menu bar on to the app. With this bit set, if the user double clicks on the menu bar when a menu is visible, we end processing of the menu and pass the double click message on to the application. This allows Just Write to detect double click on the system menu of a maximized MDI child. The normal (and expected) behavior is for Windows to detect the double click on a sys menu of a maximized child and send the app a WM_SYSCOMMAND SC_CLOSE message which is what happens with a non-maximized MDI child window. Apps: Just Write WIN.INI Line: JW=0x00042080 Problem: Sub-editors (such as footer and header editors) couldn't be closed by double-clicking the system menu. Bit: 80000 ---------- Symbolic name: GACF_30AVGWIDTH Meaning: Changed the way we calculate avg width, this fixes it for postscript. Scale all fonts by 7/8. This flag has been added for TurboTax for printing with pscript driver. Turbo Tax has hard coded average width it uses for selecting fonts. Since we changed the way we calculate avg width to match what is in TT, Turbo Tax is broken. Apps: TurboTax WIN.INI Line: turbotax=0x80000 Problem: 1040 tax forms wouldn't print correctly. If a third party vendor fixes the problems in their application, they can recompile it so that it requires Windows 3.1; the compatibility bits will not be used. If the third party vedor wants their application to run under Winodws 3.0 and 3.1, then they can change the module name or edit the WIN.INI. KBCategory: kbenv KBSubcategory: win31 gpf Additional reference words: 3.10 bitmap WW0526: Windows 3.1 Setup Article ID: Q83194 ---------------------------------------------------------------- ---- The information in this article applies to: - Microsoft Windows operating system version 3.1 ---------------------------------------------------------------- ---- Microsoft Product Support Services has an Application Note available titled "WW0526: Windows Setup." This Application Note describes the Windows version 3.1 Setup program and new setup modes, and it tells how to troubleshoot setup problems. You can obtain this Application Note from the following sources: - CompuServe, GEnie, and Microsoft OnLine - Microsoft Download Service (MSDL) - The Internet (Microsoft anonymous ftp server) - Microsoft FastTips Technical Library - Microsoft Product Support Services For complete information, see the "To Obtain This Application Note" section at the end of this article. THE TEXT OF WW0526 ================== ================================================================ ====== Microsoft Product Support Services Application Note (Text File) WW0526: WINDOWS SETUP ================================================================ ====== Revision Date: 3/92 No Disk Included The following information applies to Microsoft Windows version 3.1. ----------------------------------------------------------------- --- | INFORMATION PROVIDED IN THIS DOCUMENT AND ANY SOFTWARE THAT MAY | | ACCOMPANY THIS DOCUMENT (collectively referred to as an | | Application Note) IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY | | KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO | | THE IMPLIED WARRANTIES OF MERCHANTABILITY AND/OR FITNESS FOR A | | PARTICULAR PURPOSE. The user assumes the entire risk as to the | | accuracy and the use of this Application Note. This Application | | Note may be copied and distributed subject to the following | | conditions: 1) All text must be copied without modification and | | all pages must be included; 2) If software is included, all files | | on the disk(s) must be copied without modification [the MS-DOS(R) | | utility DISKCOPY is appropriate for this purpose]; 3) All | | components of this Application Note must be distributed together; | | and 4) This Application Note may not be distributed for profit. | | | | Copyright 1992 Microsoft Corporation. All Rights Reserved. | | Microsoft, MS-DOS, and the Microsoft logo are registered | | trademarks and Windows is a trademark of Microsoft Corporation. | -------------------------------------------------------------------- A NEW SETUP PROGRAM =================== The Windows 3.1 Setup program has been changed substantially from the Windows 3.0 Setup program. Setup was changed in order to improve its ease of use and to give you more control over the setup process. When upgrading your machine from Windows 3.0 to Windows 3.1, the setup process will maintain your group files, system drivers and settings, desktop settings, applications, type managers, and CONFIG.SYS file settings, including the order in which your device drivers are loaded. Windows 3.1 Setup will update existing Windows device drivers (if 3.1 has updated versions), add any new entries to your .INI files, and install TrueType fonts. The Setup program also has a tutorial that will familiarize you with the Microsoft Windows operating system version 3.1 and show you how to use the mouse. When you select the Setup Existing Applications option, Setup will prompt you to identify applications with identical filenames. This new feature allows Setup to create program information files (PIFs) for MS- DOS applications that use the same .EXE filename. WHAT SETUP DOES =============== When Setup is first invoked, it searches your system for memory- resident programs, such as device drivers or terminate-and-stay- resident (TSR) programs, which are known to cause problems with Setup or Windows 3.1. If Setup does detect a memory-resident program, it will advise you to remove that device driver or TSR program from your CONFIG.SYS or AUTOEXEC.BAT file, restart your system, and then start Setup again. Setup will also check the available space on your hard drive. If Setup detects a lack of space for a full installation, it will provide an option for a partial installation of Windows. If the setup process does not complete for some reason (such as a power failure), you can start Setup again, and it will detect that the setup process has not been completed. At this point, Setup will offer suggestions on how to correct the condition that caused the previous setup to fail. NEW SWITCHES FOR SETUP ====================== The Windows 3.1 Setup program has new command-line switches in addition to those of the Windows 3.0 Setup program. The following is a list of the command-line switches that can be used with the Windows 3.1 Setup program: setup /? -- Displays the Help dialog box and a list of available command-line switches. setup /n -- Sets up a shared copy of Windows from a network server. setup /i -- Disables the hardware detection that the Setup program normally performs. Using the setup /i option allows you to check the accuracy of the settings on the System Information screen and possibly make corrections. setup /o: -- Specifies the SETUP.INF file, where is the name of the SETUP.INF file that will be used by Setup. setup /s: -- Specifies a path to the Setup disk, where is the full path to the Setup disk. setup /b -- Forces Setup to run in monochrome mode. setup /t -- Causes Setup to search the drive for software that is incompatible and should not be run at the same time as Setup or Windows 3.1. setup /c -- Turns off the search for memory-resident programs. setup /a -- Starts an administrative Setup program that places Windows onto a network server. Setup expands and copies all the files on every disk to a given directory and then marks the files read-only. setup /h: -- Starts Batch Mode Setup, which requires little or no user interaction. is the name of the system settings file that contains your configuration settings. If is not in the directory from which Windows is being set up, the path to it must also be included. MODES OF WINDOWS SETUP ====================== The Windows 3.1 Setup program has new setup modes, Express and Custom modes, as well as a new Batch Mode Setup feature that allows for automation of the setup procedure. Express Setup ------------- The Express Setup mode is new to Windows 3.1 and is the default installation mode. It automatically detects the system hardware and applies standard defaults to all other installation options. When upgrading from Windows 3.0 using Express Setup, the only entry requirement is your name. If using Express Setup for a new installation of Windows 3.1, you will be required to enter your name and select a printer, printer type, and printer port, if applicable. Custom Setup ------------ The Custom Setup mode is very similar to the Windows 3.0 Setup process, with some additional features. A custom installation allows you to have full control in selecting the Windows directory, system hardware, optional component installation, changes to the CONFIG.SYS and AUTOEXEC.BAT files, printer installation, and setup of existing applications. If you are upgrading from an existing 3.0 installation, some options, such as the Printer Installation dialog box, will not be selected by default, in order to preserve the existing drivers. Batch Mode Setup ---------------- The Batch Mode Setup process is designed to simplify and speed up the installation of Windows 3.1 onto multiple machines that will be using the same or very similar configuration information. Batch Mode Setup uses the /h: switch, as described above. Setup uses the information provided in the specified file to determine the configuration during the setup process; minimal user input is required. If hardware or setup options are not specified in the file, Batch Mode Setup will use defaults for these options and will perform automatic detection of the system's hardware. The file containing the configuration information typically has an extension of .SHH. Windows 3.1 includes a sample file, with explanatory comments, called SETUP.SHH that can be modified to meet your needs. For more information about the Batch Mode Setup program for Windows 3.1, see the Microsoft Windows Resource Kit. For more information, call the Microsoft Sales Information Center (MSIC) at (800) 426-9400. Maintaining Windows with Setup ------------------------------ Once you have successfully installed Windows 3.1, you can use the Windows Setup program to update your installation whenever your hardware or software configuration changes. To update your Windows 3.1 installation, start Setup either from inside Windows or from the WINDOWS directory command prompt. When you start Setup from the command prompt, you can change the Windows device drivers for your system hardware, change code page and language options, and install third-party Windows device drivers. When you start Setup from within Windows, you can change the video, mouse, keyboard, and network drivers. You can also have Setup search your hard disk for applications and set up icons for any applications it finds. You can also use Setup to add or remove, completely or partially, the optional components that come with Windows 3.1. The following are the components that can be added or removed through Setup: README files Windows accessories Games Screen savers Wallpaper and sounds TROUBLESHOOTING SETUP ===================== The MS-DOS Portion of Setup --------------------------- The first part of the Windows 3.1 setup process runs with MS-DOS. If the Setup program stops during this part of the installation, it may be due to one of the following problems: 1. Inability to correctly detect the system's hardware (which may result in your machine stopping). To correct this problem, run Setup again by typing "setup /i" (without the quotation marks). This command causes Setup to bypass its hardware detection and run the Custom Setup process. When the System Information screen comes up, choose the settings that match the hardware on your system. 2. Incompatible hardware or software. Run Setup again, and it will display a failure detection message, prompting you to take the necessary steps to continue. Continue the setup process and specify the correct hardware when the System Information screen appears. If the System Information selections appear correct, a memory-resident program may be interfering with the setup process. In such an instance, exit Setup and restart the machine with minimal CONFIG.SYS and AUTOEXEC.BAT files. Using a text editor such as Notepad, comment out any entries in these files that are not absolutely necessary for the operation of the machine. (To comment out an entry, type "rem" [without the quotation marks] at the beginning of the line.) NOTE: If you do not know the purpose of a line in your CONFIG.SYS or AUTOEXEC.BAT file, leave that line as is. Also, if the system has RAM or ROM shadowing, this should be disabled, as it can interfere with both Setup and Windows 3.1. 3. Hard disk problems. If your hard disk has a number of lost clusters (allocation units), is excessively fragmented, or has a number of bad sectors, Windows Setup may not be able to run. In such a case, the best course of action is to run the MS-DOS command CHKDSK. Note the amount of available disk space and whether CHKDSK reports any lost allocation units. If lost allocation units are reported, you can correct this problem by typing "chkdsk /f" (without the quotation marks). CAUTION: If the number of lost allocation units is excessive (anything more than 10-20 lost allocation units), there may be a problem elsewhere in the system. Running CHKDSK /F with an excessive number of lost allocation units may result in data corruption on your hard disk. It is best to speak with your support consultant in such an instance to determine the best course of action. Bad sectors and fragmented disks can be corrected by using third-party utility packages such as Norton Utilities from Symantec, or PC Tools from Central Point. The Windows Portion of Setup ---------------------------- Partway through the installation, the setup process will switch from MS-DOS to Windows. Windows Setup will inform you that it is trying to start Windows. At the point where the Setup program switches from MS- DOS to Windows, the screen may go black and the machine may stop. The following are possible causes and their resolutions: 1. Conflicts with memory-resident applications (TSR programs and/or device drivers). When you started Setup, your system had an program in memory that writes directly to your video screen, rather than going through the BIOS--for example, a TSR network messaging program that notifies you when a print job completes. Other memory-resident programs can also interfere with Windows Setup. Setup will detect and warn you about many incompatible memory-resident programs when it first starts. (The file SETUP.TXT, located on Disk 1, provides additional information about using these programs with Setup or Windows. The information about memory-resident programs is listed alphabetically by program name.) Make sure that any extraneous applications and device drivers have been closed or commented out of your CONFIG.SYS and AUTOEXEC.BAT files before starting Windows 3.1 Setup. To comment out an entry, type "rem" (without the quotation marks) at the beginning of the line. NOTE: If you do not know the purpose of a line in your CONFIG.SYS or AUTOEXEC.BAT file, leave that line as is. 2. Inability to correctly detect hardware. Type "setup /i" (without the quotation marks) at the command prompt. When the System Information screen comes up, make sure that the settings displayed match the hardware on the system. If the settings shown do not match, change them to the correct settings. 3. Incompatible hardware or software. Run Setup again; Setup will display a message indicating which device is incompatible and prompt you to specify a different device. On the System Information screen, verify that all the settings are correct and modify them if they are not. If you are still unable to proceed through Setup, try installing Windows by typing "setup /i" (without the quotation marks), choosing the lowest resolution supported by your monitor, and selecting the No Mouse Or Other Pointing Device option. If the Setup program proceeds, you can run Setup again after Windows installs to correctly configure Windows for your machine. Install the proper configuration components one at a time. If you encounter problems with one or more of the components, contact the manufacturer of the component in question for more information. 4. Incorrect version of MS-DOS. Windows 3.1 requires MS-DOS version 3.1 or later. To determine what version of MS-DOS is present on your system, type "ver" (without the quotation marks) at the MS-DOS command prompt, and you will receive a message indicating your MS-DOS version. If necessary, install a newer version of MS-DOS and then run Setup again. When you attempt to install Windows 3.1 with a version of MS-DOS prior to 3.1, Setup will display an error message and terminate. It is also important that the version of MS-DOS on your machine is designed for that machine. CAUTION: Do not run an original equipment manufacturer (OEM) version of MS-DOS on a machine not manufactured by that OEM (for example, COMPAQ MS-DOS on an IBM machine). If the Setup program does not detect that you have inserted the disk that you were prompted for, one of the following conditions may be true: 1. A disk-caching utility may be caching the floppy disk drive. To remove the disk cache, use a text editor such as Notepad to open the CONFIG.SYS or the AUTOEXEC.BAT file and comment out the line pertaining to the disk-caching utility. To comment out a line, type "rem" (without the quotation marks) at the beginning of the line. After saving the file and exiting your editor, restart your system and run Setup again. 2. The system may not have received the message that the floppy disk has been changed. Under MS-DOS 3.2 and later, you can try to correct this problem by adding either DRIVPARM or DRIVER.SYS to your CONFIG.SYS file and then restarting your computer. For example, if you are setting up Windows 3.1 from drive A, and it is a high-density 5.25-inch drive, you would add ONE of the following lines to your CONFIG.SYS file: drivparm=/d:0 /f:1 -or- device=c:\dos\driver.sys /d:0 /f:1 NOTE: If your MS-DOS files are located in a directory other than C:\DOS, make the appropriate change to the path in the above device= line. For more information on either of these commands, please refer to your MS-DOS user's guide. NONSTANDARD WINDOWS 3.0 DRIVERS =============================== If you are using a nonstandard display driver, such as Super VGA, with Windows 3.0, you may receive an error message or encounter difficulty while starting Windows 3.1. The following are error messages that can be caused by an incompatible display driver: - "Error loading VGA.DRV" will appear if the driver cannot be loaded. NOTE: "VGA.DRV" will change to match the name of the currently installed display driver. - "Error loading USER.EXE" or "Error loading GDI.EXE" can be caused by other nonstandard Windows drivers or components. If you encounter any of these messages, you may need to exit Setup and run Setup within Windows 3.0 to return Windows 3.0 to a standard configuration. Once Windows 3.0 is at a standard configuration, run Windows 3.1 Setup. Contact your hardware manufacturer to see if there are any special concerns. If none of the above steps allows Setup to install Windows 3.1 on your system, you may need to contact your hardware manufacturer for more information. ---------------------------------------------------------------------- TO OBTAIN THIS APPLICATION NOTE =============================== - On CompuServe, GEnie, and Microsoft OnLine, Application Notes are located in the Microsoft Software Library. You can find WW0526 in the Software Library by searching on the word WW0526, the Q number of this article, or S13373. WW0526 was archived using the PKware file-compression utility. - Application Notes are available by modem from the Microsoft Download Service (MSDL), which you can reach by calling (206) 936-6735. This service is available 24 hours a day, 7 days a week. The highest download speed available is 14,400 bits per second (bps). For more information about using the MSDL, call (800) 936-4200 and follow the prompts. To obtain WW0526, download WW0526.EXE. WW0526.EXE is a compressed, self-extracting file. After you download WW0526, run it to extract the file(s) it contains. - On the Internet, Application Notes are located on the Microsoft anonymous ftp server, which you can reach by typing "ftp ftp.microsoft.com" (without the quotation marks) at the ">" command prompt. You can find WW0526.EXE in the SOFTLIB/MSLFILES directory. - You can have this Application Note mailed or faxed to you from the automated Microsoft Windows 3.1 FastTips Technical Library, which you can call 24 hours a day, 7 days a week at (800) 936-4200. NOTE: The FastTips Technical Library is available only to customers within the U.S. and Canada. - If you are unable to access the source(s) listed above, you can have this Application Note mailed or faxed to you by calling Microsoft Product Support Services Monday through Friday, 6:00 A.M. to 6:00 P.M. Pacific time at (206) 637-7098. If you are outside the United States, contact the Microsoft subsidiary for your area. To locate your subsidiary, call Microsoft International Sales Information Center at (206) 936-8661. KBCategory: kbsetup kbdisplay kbfile kbappnote KBSubcategory: Additional reference words: appnote 3.10 WW0532: Object Linking and Embedding (OLE) Article ID: Q83248 ---------------------------------------------------------------- - The information in this article applies to: - Microsoft Windows operating system version 3.1 ---------------------------------------------------------------- - Microsoft Product Support Services offers an Application Note that describes object linking and embedding (OLE), compares OLE to dynamic data exchange (DDE), and explains how to insert, view, and edit embedded objects. This Application Note is titled "Object Linking And Embedding (OLE)" (WW0532). You can obtain this Application Note from the following sources: - CompuServe, GEnie, and Microsoft OnLine - Microsoft Download Service (MSDL) - The Internet (Microsoft anonymous ftp server) - Microsoft FastTips Technical Library - Microsoft Product Support Services For complete information, see the "To Obtain This Application Note" section at the end of this article. THE TEXT OF WW0532 ================== ================================================================ ====== Microsoft(R) Product Support Services Application Note (Text File) WW0532: OLE ================================================================ ====== Revision Date: 9/94 No Disk Included The following information applies to Microsoft Windows(TM) and Windows for Workgroups, versions 3.1 and 3.11. ---------------------------------------------------------------- ------ | INFORMATION PROVIDED IN THIS DOCUMENT AND ANY SOFTWARE THAT MAY | | ACCOMPANY THIS DOCUMENT (collectively referred to as an Application| | Note) IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER | | EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE IMPLIED | | WARRANTIES OF MERCHANTABILITY AND/OR FITNESS FOR A PARTICULAR | | PURPOSE. The user assumes the entire risk as to the accuracy and | | the use of this Application Note. This Application Note may be | | copied and distributed subject to the following conditions: 1) All| | text must be copied without modification and all pages must be | | included; 2) If software is included, all files on the disk(s) | | must be copied without modification (the MS-DOS utility diskcopy is| | appropriate for this purpose); 3) All components of this | | Application Note must be distributed together; and 4) This | | Application Note may not be distributed for profit. | | Copyright(C) 1992-1994 Microsoft Corporation. All Rights Reserved.| | Microsoft and MS-DOS are registered trademarks and Windows is a | | trademark of Microsoft Corporation. | |---------------------------------------------------------------- ----| INTRODUCTION TO OLE =================== OLE is a technique for implementing "OLE document" features by making simple extensions to existing applications that run under Microsoft Windows. This technique allows you to view and manipulate various forms of information (for example, spreadsheets, text, and graphics) in the context of a single document. Rather than having to manually switch between different applications, you can alter data by simply selecting and double-clicking the object of interest. The process of running application code is automated and is invisible to you. THE PROGRESSION FROM CLIPBOARD TO DDE TO OLE ============================================ The need to integrate information from different applications is not new. In the past, users have taken advantage of the Windows Clipboard, and more recently, dynamic data exchange (DDE) to accomplish this. The Clipboard provides a basic means for moving data between applications. You select the desired information in the source document, transfer the information to the Clipboard by choosing Copy from the Edit menu, then place the information in the target document using the Paste command on the Edit menu. Data transfers through the Clipboard are static. This means that if the source information changes, you must manually copy the revisions to the target document if you want the target document to stay current. Additionally, the target application must understand the format of the data being transferred to it through the Clipboard. A word processor that accepts an ASCII text string, for example, will not be likely to understand a set of cells from a spreadsheet. DDE complements the Clipboard's static data exchange capability by creating a link between the target document and the source document. The target document uses this link to dynamically retrieve the associated data whenever it is updated in the source document. Therefore, you do not need to remember to update each file that contains the data. Microsoft created OLE because there are scenarios that are not served by either Clipboard or DDE linking--in particular, situations that involve OLE documents. Note that OLE does not replace either DDE or the Clipboard, but rather complements them by providing additional functionality. OLE employs both the Clipboard and DDE linking mechanisms, and the Copy, Paste, and Paste Link commands. That is, you still select and copy the data from the source, and paste or paste link the data to the client. The OLE specification defines a set of rules that client applications can use to decide whether to import pasted information as an object or as converted data when both options are possible. A new Paste Special command is also defined to give you explicit control over the choice of format. BENEFITS OF OLE =============== - An application that implements OLE allows you to move away from an application-centered view of computing, in which the tool used to complete a task is a single application, and move toward a document- centered view, in which you employ as many tools as necessary to complete the job. - OLE allows applications to specialize in performing one job very well. A word processing application that implements OLE, for example, does not necessarily need any illustration tools; users can put illustrations into their documents and edit those illustrations using any illustration application that supports OLE. An example of such a relationship is the one between Microsoft Word for Windows and the illustration application Microsoft Draw, which is included with Word. - Applications are automatically extensible for future data formats because the content of an object does not matter to the containing document. - You can concentrate on the tasks you are performing, instead of on the applications required to complete the tasks. - Files can be more compact because OLE linking to objects allows a file to use an object without having to store that object's data. - A document can be printed or transmitted without using the application that originally produced the document. - Linked objects in a file can be updated dynamically. FEATURES OF OLE NOT FOUND IN DDE ================================ Feature | Description ---------------------------------------------------------------- -------- | Extensibility for future | The OLE libraries can be updated in enhancements | future releases to support new data | formats, link tracking, and other | new features of OLE as they are | developed. | Persistent OLE embedding and | The OLE libraries do most of the OLE linking of objects | work of activating objects when an | embedded document is reopened, by | reestablishing the conversation | between a client and server. In | contrast, establishing a DDE link is | either your responsibility (if there | is no link) or the application's | responsibility (if the link is | persistent). | Rendering of common data | The OLE libraries assume the burden formats | of rendering common data formats in | a display context. DDE applications | must do this work themselves. | Server rendering of | The OLE libraries facilitate the specialized data formats | rendering of specialized data | formats in the client's display | context. The server application or | object handler actually performs the | rendering. The client application | has to do very little work to render | the embedded or linked data in its | display context. | Activation of embedded and | The OLE libraries support activating linked objects | a server application (the | application associated with the | object) to edit a linked or embedded | object to render data. Activating | servers for data rendering and | editing is beyond the scope of DDE. | Creation of objects and links| The OLE libraries do most of the from the Clipboard | work when an application is using | the Windows Clipboard to copy and | paste links or exchange objects. In | contrast, DDE applications must | directly call the Windows Clipboard | functions to perform such | operations. | Creation of objects and links| The OLE libraries provide direct from files | support for using files to exchange | data. No DDE protocol is defined for | this purpose. OLE LINKING AND OLE EMBEDDING TERMINOLOGY ========================================= OLE DOCUMENT ============ An OLE document is a document that contains data in several different formats (see Figure 1). An OLE document uses the facilities of different OLE applications to present the different kinds of data it contains. Note that an OLE document can incorporate links to information, rather than the information itself. If a document uses links, it requires minimal storage and is updated automatically whenever the linked data changes. Figure 1. An OLE document When you are working with an OLE document, you do not need to know which data formats are compatible with one another or how to find and start the applications that created the data. Whenever you choose part of an OLE document, the server application starts automatically. For example, an OLE document could be a brochure that includes text, charts, cells of financial data, and illustrations. By selecting different data within the brochure, you can automatically switch between the word processor, spreadsheet, and graphics programs that produced its components. CLIENT ====== A client is a document that contains objects managed by other applications, or the application that manages such documents. The OLE client applications that are included with Microsoft Windows 3.1 are Write and Cardfile. Figure 1 shows Write acting as a client. Other examples of OLE clients are Microsoft Word for Windows and Microsoft Excel for Windows. SERVER APPLICATION ================== A server application is an application that provides editing and rendering services for a linked and embedded object. When you double- click an object in a client document, the server application is invoked. A new instance of the server application is started even if one is already running. (The advantage of starting a new instance of the server application is that it is initially dedicated to the current object and does not contain any unrelated document windows.) Figure 2. Microsoft Draw--an OLE server application Paintbrush is an OLE server application that is included with Microsoft Windows 3.1. Other examples of OLE server applications are Microsoft Excel, Microsoft PowerPoint, and Microsoft Draw. OBJECT ====== An object is any data that can be displayed in an OLE document and manipulated by a user. An object can be anything from a single cell in a spreadsheet to an entire document or illustration. When an object is incorporated into a document, it maintains an association with the application that produced it. OLE applications are "opaque"; that is, the client application never looks inside the object and therefore doesn't need to understand its contents. The client simply calls functions in the OLE libraries when it needs to display an object or invoke the server application for editing purposes. Figure 3. The Insert Object dialog box from Microsoft Word for Windows EMBEDDED OBJECT =============== An embedded object is an object that is completely contained within the client document. For example, when a range of spreadsheet cells from Microsoft Excel is embedded in a Microsoft Write file, all the data associated with the cells, including any formulas, is saved as part of the Write file. The name of the server for the spreadsheet (Microsoft Excel) is saved along with the data. While working with the Write file, you can double-click this embedded object (the range of cells), and Microsoft Excel will start automatically so that you can edit those cells. LINKED OBJECT ============= A linked object is a reference, or link, to data shared by a server application and a client. If the range of spreadsheet cells from our example is a linked object instead of an embedded object, the data is stored in a Microsoft Excel file and only the link to the data is saved with the Write file. The server then "presents" the data, in the proper format, to the client document (see "Presentation Data" below). You can still double-click the object to bring up the server application (in this case, Microsoft Excel) and edit the information. PRESENTATION DATA ================= Presentation data is formatted data sent from the server application to the client so that the client can display and print the object. (Presentation data is referenced by an ObjectLink.) OBJECT CLASS ============ The object class describes the type of information an object contains, and is assigned by the server application. Examples of Microsoft object classes include picture (Microsoft Paintbrush), worksheet (Microsoft Excel for Windows), and document (Microsoft Word for Windows). DOCUMENT NAME/ITEM NAME ======================= The document name and item name identify the object within whatever server application or document it resides. OBJECTLINK ========== An ObjectLink is a DDE and Clipboard format that carries a descriptor of a source object. The ObjectLink contains the class, document, and item that identify a linked object. An ObjectLink is represented internally by three null-terminated strings followed by a null string (that is, a null character). (This format describes a linked object.) OWNERLINK ========= An OwnerLink is a DDE and Clipboard format that carries a descriptor of the owner of an OLE object. An OwnerLink has the same format as an ObjectLink, and is used to communicate information about the owner of an object, which may be distinct from the source. (This format describes an embedded object.) NATIVE ====== Native is the format of the data that defines the object; this format and its interpretation are known only to the server application. Native format data is transferred between the client and the server application in the case of embedded objects, where a client document provides permanent storage and the server application provides editing features. VERB ==== The types of actions you can perform on an object are called verbs. For example, two common verbs for an object are play and edit. The nature of an object determines the verbs that you can initiate; for example, you typically play a voice annotation and edit a text file. The typical use for an object is called the "primary verb." Double- clicking an object usually executes the action specified by the primary verb. Other possible verbs for an object are called "secondary verbs." (Note that many objects support only one verb.) PACKAGE ======= A package is a type of OLE object that encapsulates another object, a file, or a command line inside a graphic representation (such as an icon or bitmap). When you double-click the graphic object, the OLE libraries execute the primary verb of the object contained in the package. The graphic part of a package is always an embedded object, not a link; thus, the graphic is saved as part of the client document. The package contents can be an embedded object, a linked object, a static object, or a command line. Packages are useful for presenting compact "token" views of large files or OLE objects. An application can also use packages as hyperlinks. You can use Microsoft's Object Packager (PACKAGER.EXE), a packager application that ships with Windows 3.1, to associate a file or data selection with a particular icon or graphic. (The secondary verb for a package is "edit package"; when you choose this verb, Object Packager starts.) OLE LIBRARIES ============= DATA TRANSFER IN OLE ==================== Applications use three dynamic-link libraries (DLLs)--OLECLI.DLL, OLESVR.DLL, and SHELL.DLL--to implement OLE. OLECLI.DLL and OLESVR.DLL support OLE, while SHELL.DLL supports the system registration database. These libraries can be included with any products developed under Windows versions 3.1 and 3.11 to ensure the products will run under Windows version 3.0. COMMUNICATION BETWEEN OLE LIBRARIES =================================== Client applications use functions from the OLE application programming interface (API) to inform the client library, OLECLI.DLL, that a user wants to perform an operation on an object. The client library uses DDE messages to communicate with the server library, OLESVR.DLL. The server library is responsible for starting and stopping the server application, directing the interaction with the server application's callback functions, and maintaining communication with the client library. When a server application modifies an embedded object, the server application notifies the server library of changes. The server library then notifies the client library, and the client library calls back to the client application, informing it that the changes have occurred. Typically, the client application then forces the embedded object to be redrawn in the document file. If the server application changes a linked object, the client library is notified that the object has changed and should be redrawn. OBJECT HANDLERS =============== Some server applications implement a fourth kind of OLE library called an "object handler." Object handlers are DLLs that act as intermediaries between client and server applications. Typically, an object handler is supplied by the developer of a server application as a way of improving performance. For example, an object handler can be used to redraw a changed object if the presentation data for that ob- ject could not be rendered by the client library. OBJECT INSERTION METHODS ======================== INSERTING AN EMBEDDED OBJECT ============================ The basic procedure for inserting an embedded object is simple. For example, to insert a Paintbrush drawing in a Write document: 1. In the server application (Paintbrush), select the drawing, then choose the Copy command from the Edit menu. 2. Switch to the client application (Write), position the insertion point at the correct location, and choose the Paste command from the Edit menu. Generally, in applications that support OLE, the Paste command will embed the object that is on the Clipboard, as in the previous example. Under some circumstances, however, the application may choose not to embed the object. For example, suppose that the object is represented on the Clipboard not only by the embedded object format but also by an alternative format that completely represents the original data and that the client application knows how to edit. In this case, the client may choose to insert this editable alternative data rather than OLE embedding the object. (An example of this concept, though not practical, is one in which the server and client are the same application--for example, Word for Windows version 2.0). Most applications, however, will not be able to provide full editing capabilities for any alternative format, and they will simply embed the object and allow the source application to provide editing tools. Therefore, in most applications that support OLE, when the Clipboard contains an object from another application, the Paste command embeds the object in the current document. Note that in applications that do not support OLE, the Paste command simply inserts a static copy of the data, without providing easy access to the tools required for later editing of the data. INSERTING A LINKED OBJECT ========================= Inserting links to objects is just as easy as OLE embedding objects. To continue the example using Paintbrush and Write, suppose that instead of OLE embedding the drawing, you wanted to insert a link to the drawing. The following steps would be required: 1. In the server application (Paintbrush), select the drawing and choose Copy from the Edit menu. 2. Switch to the client application (Write), position the insertion point at the correct location, and choose Paste Link from the Edit menu. This procedure inserts in the Write document a link to the drawing. The drawing is displayed in the Write document but is stored in the original Paintbrush file. The link is an "automatic" link, meaning that whenever the Paintbrush drawing file is changed, the drawing in the Write file is updated dynamically. Once a link exists in one document, it can be inserted in other documents using the Copy and Paste commands. When a linked object, including the ObjectLink format, is copied, all information describing the object is copied to the Clipboard as one self-contained unit. When the object is pasted into a client, it possesses the same attributes as the original object from which it was copied. PASTE SPECIAL ============= The Paste Special command on the Edit menu allows you to control the manner and format in which an object is inserted into a client document. For example, you may want the data to be inserted as an embedded object (rather than translated into a client-editable format), so that the tools of the server application can easily be invoked to edit the object. Alternatively, certain special tools or editing operations might be available only when the data is in a format that cannot be manipulated by the client application. The dialog box activated by the Paste Special command enables you to control the insertion of the object in the following ways: - The Data Type list allows you to choose the format for the inserted object. The first choice is generally the "object class name," which is the format the data takes in the server application. Examples of object class names are Microsoft Excel Worksheet, Microsoft PowerPoint Slide, and Microsoft Paintbrush Bitmap. The other choices are the formats available on the Clipboard: Formatted Text (meaning RTF, or rich-text format), Unformatted Text, Picture, and Bitmap. - Paste and Paste Link buttons are provided so that you can override the default choice made by the client application. Both choices translate the data into the selected format and insert the data into the document. The Paste button does not establish a link to the original source of the data. If you have selected the object class name rather than a data format, the data is inserted as an embedded object instead of being translated into a client-editable format. The Paste Link button establishes an automatic link to the original source of the data. NOTE: Not all Windows applications contain the Paste Special command. INSERT OBJECT ============= To facilitate the OLE embedding of blank objects, applications may implement an Insert Object command. In applications that include an Insert menu (for example, Microsoft Word for Windows), the command appears on that menu and is labeled "Object." In applications that do not include an Insert menu, the command appears on the Edit menu and is called "Insert Object." The dialog box that appears when you choose the Insert Object command contains the Object Type list, a list of object names drawn from the registration database maintained by the system in the REG.DAT file. To embed an object, select its name from the list, and choose the OK button (or press ENTER). This activates the server application for the selected object. The server application then displays a blank window in which you can create and edit the object. After creating and editing the object, choose Update from the File menu of the server application. This command inserts the object where the insertion point was positioned in the client when the Insert Object command was chosen. You can then close the server application by choosing Exit from the File menu, and return to the client document. NOTE: Not all Windows applications contain the Insert Object command. OBJECT ACTIONS ============== VIEWING OBJECTS =============== Complex OLE documents may contain several linked or embedded objects (OLE objects), interspersed with objects that are native to the docu- ment. Because OLE objects support different operations than those supported by the native objects, it is convenient if you can visually distinguish OLE objects from native ones. For this purpose, applica- tions should provide visual indications of OLE object boundaries. The boundaries of a particular object should appear whenever the object is selected. In addition, applications should provide a way for all object boundaries to be turned on or off at once, to facilitate easy viewing of all OLE objects in a document. For example, applications may reveal object boundaries, as well as other normally hidden infor- mation, through a Hidden Structure command on the View menu or through a Show All check box in a Preferences dialog box. The exact method of indicating object boundaries depends on the nature of the client application and the type of OLE object. Three possible methods are: 1. Complete borders surrounding the object. For VGA monitors, the border should be dark gray; for non-VGA monitors, the border should be a 50-percent gray pattern. 2. Special graphic characters (for example, "{" and "}") at the beginning and end of the object. 3. Distinctive formatting (for example, a dotted underline) that is not used elsewhere in the client. EDITING OBJECTS =============== Double-Clicking the Object -------------------------- Once linked or embedded objects are inserted in a document, the standard user interface provides three methods for editing them. The first method involves double-clicking the object or object boundary to invoke a new instance of the server application, with the OLE object as the active document. Note that in the following situations, a new instance of the server application is not started: - The object is already open in an existing instance of the server application. In this case, the existing instance should be brought to the front. - The server application is a multiple document interface (MDI) application and is the same as the client application. The appropriate behavior depends on whether the link is external or internal. EXTERNAL LINKS: Suppose that one Word document contains a link to another Word document. In this case, double-clicking the link should not start a new instance of Word. Instead, if the document window for the server document is already open within the current instance of Word, then that document window should be brought to the front. If no document window is open for the server document, a new document window should be opened for it within the current instance of Word. INTERNAL LINKS: In contrast to the preceding example, suppose that the link in the original Word document refers to another part of that same document. If you double-click the link, the current document window should scroll to show the source of the link. When the server application's window opens, the object is loaded into the window. For embedded objects, the window is initially sized to show only the portion of the object displayed in the client. You can resize the window to display additional portions of the embedded object. When linked objects are used, the entire linked file is loaded, and the linked portion is selected. You can then modify the object with the tools provided by the server application. Updating Objects from Non-MDI Server Applications ------------------------------------------------- When a non-MDI application (for example, Paintbrush) functions as a server application for an embedded object, the Save command on the File menu changes to Update. This change occurs only for embedded objects, not for linked objects. The Update command updates the object in the client but does not close the server application. The server application remains open so you can make further changes after noting the effects (for example, repagination) of the update on the client. Updates to embedded objects can be undone through the Undo command on the client's Edit menu. If you attempt to exit the server application without updating the object, a warning message is displayed, asking if you want to update the client document ("Update ?"). When an embedded object is being edited, the Save As command on the File menu can be used to save a copy of the object in a separate file. If the client file has not yet been updated, the "Update ?" warning message is displayed before the Save As dialog box appears. Choosing New from the File menu also displays the "Update ?" warning message. When the server closes, the focus returns to the client. If you attempt to close the client while server documents for that client are still open, the server documents are closed first, after the usual checks for unsaved data. Updating Objects from MDI Server Applications --------------------------------------------- The procedure for editing and updating objects from MDI server applications is similar to the procedure for non-MDI server applications, with the following exceptions. If the focus changes from the embedded object window to a "normal" document window (that is, one containing an existing file or a new document), the Update command on the File menu changes back to Save. If the embedded object window regains the focus, Save becomes Update again. When New is chosen from the File menu, the window containing the embedded object remains open. Therefore, the "Update ?" warning message is not displayed if the client file has not yet been updated. Updating Objects Using the Links Command ---------------------------------------- The second method for editing OLE objects involves two commands on the Edit menu. The Links command produces a dialog box that allows you to change the type of updating (automatic or manual) for links, update linked objects, cancel links, repair broken links, and invoke the verbs associated with linked objects. The Links dialog box should use object-specific verbs if possible; otherwise, the generic verbs "activate" and "edit" should be used. When the Links dialog box opens, the Links list shows each link in the document; links in the current selection are highlighted. Embedded objects in the current selection are not shown in the list. As you select different links in the Links list, the verbs on the two object- specific buttons will change accordingly. Below the Links list, the dialog box contains two Update option buttons: Automatic and Manual. These buttons reflect whether the currently selected links are automatically updated whenever the linked file changes or whether they must be manually updated. The Update Now button in the Links dialog box updates all links selected in the Links list. The presentations of the linked objects in the client are updated to reflect the current data in the linked (server) files. The Cancel Link button in the Links dialog box permanently breaks the link between the client and the server application. The linked object in the client is changed to a picture that can no longer be edited or updated through the standard OLE techniques. The picture can still be edited using the cut/copy/paste techniques, but it will not retain all the data present in the original linked object. No link boundaries will be displayed for the picture. The Change Link button in the Links dialog box is dimmed if the selection in the Links list includes multiple links to multiple files. Otherwise, if all the selected links are linked to the same file, the button is active and leads to a dialog box exactly like the File Open dialog box, except that the title is Change Link (in most applications). The Change Link dialog box allows you to change the file to which a link refers. This feature has two uses. First, it allows broken links to be reestablished. Second, the dialog box allows a single client that operates on linked data files to be successively connected to different linked files. This flexibility in providing data to the client is particularly useful for applications such as spreadsheets and databases. In addition to these standard options, an application's Links dialog box may also include a list box for changing the format in which the object is displayed. Updating and Acting Upon Objects Using the "Object Class Name" Object Command -------------------------------------- The third method for editing OLE objects involves the "Object Class Name" Object command on the Edit menu, which allows you to choose one of an object's verbs. If the selection in the document is a single embedded object, the class name placeholder is typically replaced by the class and name of the object (for example, "Microsoft Excel Worksheet"). If an object supports only one verb, the name of the verb should precede the class name in the menu item (for example, "Edit WPDocument Object"). When an object supports more than one verb, choosing this menu item brings up a menu listing each of the verbs associated with the selected object. REGISTRATION ============ When a server application is installed, it registers itself as an OLE server application with the system registration database (REG.DAT). This database is supported by SHELL.DLL. To register itself as an OLE server application, a server application records in the database that it supports one or more OLE protocols. The protocols currently supported are "StdFileEditing" and "StdExecute." StdFileEditing is the protocol for linked and embedded objects. StdExecute is used only by applications that support the OleExecute function. The entries in the registration database are used whenever an application or library needs information about an OLE server application. For example, client applications that support the Insert Object command refer to the database in order to list the OLE server applications that could provide a new object. The client applications also use the registration database to retrieve the name of the server application for the Paste Special dialog box. The registration database stores key/value pairs, where keys and values are null-terminated strings. Keys are hierarchically structured, with the names of the components and keys separated by backslash (\) characters. To be available for OLE transactions, a server application should register the key/value pairs shown in the following example when the server application is installed. The class name and server application path should be registered for every class the server application supports. If a class has an object-handler library, it should be registered using the "handler" keyword. An application should also register all the verbs its class or classes support. An application's verbs must be sequential; for example, if an object supports three verbs, the primary verb is 0 and the other verbs must be 1 and 2. The following example shows the form of the key/value pairs as they would be added to a database using the Registration Information Editor, REGEDIT.EXE. An application could also use the registration API to add this information to the database. HKEY_CLASSES_ROOT\ = readable version of class name HKEY_CLASSES_ROOT\<.ext> = HKEY_CLASSES_ROOT\\protocol\StdFileEditing\server = HKEY_CLASSES_ROOT\\protocol\\StdFileEditing\handler = HKEY_CLASSES_ROOT\\protocol\StdFileEditing\verb\0 = HKEY_CLASSES_ROOT\\protocol\StdFileEditing\verb\1 = Server applications that support the OleExecute function also add the following line to REG.DAT: HKEY_CLASSES_ROOT\\protocol\StdExecute\Server = Server applications can register data formats that they accept on calls to the OleSetData function or that they can return when a client calls the OleRequestData function. Clients can use this registered information to initialize newly created objects or to manipulate data with the server application. Client applications should not depend on the requested data format because the calls can be rejected by the server application. For compatibility with earlier applications, the system registration service also reads and writes registration information in the [embedding] section of the WIN.INI initialization file. A sample [embedding] section follows: [embedding] ExcelWorksheet=Worksheet created by Microsoft Excel,Excel Worksheet, EXCEL.EXE, picture WordDocument=Word Document,Word Document,C:\WINWORD\WINWORD.EXE, picture SoundRec=Sound Recorder Waveform Audio,Sound,SoundRec.exe,picture Package=Package,Package,packager.exe,picture PBrush=Paintbrush Picture,Paintbrush Picture,pbrush.exe,picture The syntax is: =,,/, [picture] The keyword "picture" indicates that the server application can produce metafiles for use when rendering objects. Note that a server application can register the entire path for its executable file, or register only the file's name and arguments. Registering only the filename without the path will cause the server application to fail if the application is installed in a directory that is not mentioned in the PATH environment variable in the AUTOEXEC.BAT file. Generally, registering the path and filename is recommended instead of registering only the filename. In the above example, you may want to verify that the directory containing EXCEL.EXE is mentioned in your PATH environment variable. ---------------------------------------------------------------- ---- TO OBTAIN THIS APPLICATION NOTE =============================== - On CompuServe, GEnie, and Microsoft OnLine, Application Notes are located in the Microsoft Software Library. You can find WW0532 in the Software Library by searching on the word WW0532, the Q number of this article, or S13368. WW0532 is a compressed, self-extracting file. After you download WW0532, run it to extract the file(s) it contains. - Application Notes are available by modem from the Microsoft Download Service (MSDL), which you can reach by calling (206) 936-6735. This service is available 24 hours a day, 7 days a week. The highest download speed available is 14,400 bits per second (bps). For more information about using the MSDL, call (800) 936-4200 and follow the prompts. To obtain WW0532, download WW0532.EXE. WW0532.EXE is a compressed, self-extracting file. After you download WW0532, run it to extract the file(s) it contains. - On the Internet, Application Notes are located on the Microsoft anonymous ftp server, which you can reach by typing "ftp ftp.microsoft.com" (without the quotation marks) at the ">" command prompt. - You can have this Application Note mailed or faxed to you from the automated Microsoft FastTips Technical Library, which you can call 24 hours a day, 7 days a week at (800) 936-4200. NOTE: The FastTips Technical Library is available only to customers within the U.S. and Canada. - If you are unable to access the source(s) listed above, you can have this Application Note mailed or faxed to you by calling Microsoft Product Support Services Monday through Friday, 6:00 A.M. to 6:00 P.M. Pacific time at (206) 637-7098. If you are outside the United States, contact the Microsoft subsidiary for your area. To locate your subsidiary, call Microsoft International Sales Information Center at (206) 936-8661. KBCategory: kbfile kbdisplay kbsound kbappnote kbole KBSubcategory: wfw wfwg win31 Additional reference words: appnote 3.10 win31 Unexpected DOS Errors 0 - 23 and Windows Article ID: Q83356 ---------------------------------------------------------------- ---- The information in this article applies to: - Microsoft Windows operating system versions 3.0, 3.0a, 3.1, 3.11 ----------------------------------------------------------------- --- SUMMARY ======= The following error message may be displayed when you start a Windows-based application Unexpected DOS Error where is a number between 0 and 23. Causes for unexpected errors include incompatible terminate-and-stay- resident (TSR) programs, low BUFFER settings, and incompatible virtual device drivers. MORE INFORMATION ================ The following numbers represent specific Unexpected DOS Errors in Windows 3.0. An asterisk (*) indicates that the error is trapped and handled by Program Manager (PROGMAN.EXE). *0 Out of memory *2 File not found *3 Path not found *5 Attempt to dynamically link to a task *6 Library requires separate data segments for each task *10 Incorrect Windows version 11 Invalid .EXE file 12 OS/2 Application *13 MS-DOS 4.0 application 14 Unknown EXE type *15 Attempt to load an EXE created for an earlier Windows version *16 Attempt to load a second instance of an .EXE containing multiple, writeable data segments *17 Attempt in large-frame EMS mode to load a second instance of an application that links to certain non-shareable DLLs already in use 18 Attempt in real mode to load an application marked for protected mode only Unexpected DOS Error 1 can occur with third-party video drivers. Unexpected DOS Error 2 can occur if you install Time$heet Professional on a system with the Certus NoVi TSR program loaded. Unexpected DOS Error 5 can occur when virus-scanning software is running (noted with VDEFEND) or if the buffers= line in CONFIG.SYS is set low (that is, less than 10). Unexpected DOS Error 6 can occur if you run Time$heet Professional on a system with the Certus NoVi TSR program. Unexpected DOS Error 11 can occur if you use a third-party video driver. Resetting Windows to a default video driver (such as standard VGA) corrects the problem. Unexpected DOS error 11 can occur if WINOA386.MOD is corrupted. Unexpected DOS Error 13 can occur under Windows 3.1 if you try to run a program created with Microsoft C version 7. No resolution is available. Unexpected DOS Error 13 can occur under Windows 3.1 if you try to run an MS-DOS-based terminal emulator program (for example, KEA's Z-Stem). Unexpected DOS Error 14 can occur under Windows 3.0 if you run Borland Paradox version 4.0. Unexpected DOS Error 21 can occur when you try to run Math CAD for Windows, version 4.0. To resolve this problem, obtain Math CAD's Fax #2000. Unexpected DOS error 23 can occur when you run Microsoft Golf. Unexpected DOS error 23 can occur when you try to start an MS-DOS prompt or an application and WINOA386.MOD is missing from the Windows directory or the Windows SYSTEM subdirectory and is not in the path. Unexpected DOS Error 23 can occur, along with the message "Cannot find WINOLDAP.MOD," when you try to set up Microsoft Mail 3.2 extensions for Workgroups after you start Windows for Workgroups with the /D:T switch. KBCategory: kbref kbdisplay kberrmsg kb3rdparty KBSubcategory: wfw wfwg win30 win31 Additional reference words: 3.00 3.00a WordPerfect Ami Pro AMIPRO MS-DOS 3.10 3.11 Troubleshooting Lost Network Connections Article ID: Q90226 -------------------------------------------------------------------- The information in this article applies to: - Microsoft Windows for Workgroups versions 3.1, 3.11 ---------------------------------------------------------------- ---- This article provides troubleshooting steps and suggestions that may assist you in solving network connectivity problems. Microsoft cannot guarantee the success of any specific steps provided in this article. SUMMARY ======= Windows for Workgroups may sometimes lose (drop) network connections. This problem is most likely to occur if one of the following conditions exists: - You are running a network installation (SETUP /N) of Windows for Workgroups. NOTE: Microsoft does not recommend running Windows for Workgroups from a network installation (SETUP /N) because doing so is a common stress condition that can cause a loss of network connections. If your system is run this way, store data and applications on a client or server that does NOT contain the shared Windows directory (created with SETUP /A); this appears to reduce the frequency of the problem. - Several people in a workgroup are running the same application from a server. NOTE: Network connections also can be lost when many users run the same application from a server (for example, 10 clients use the same installation of Microsoft FoxPro for MS-DOS). MS-DOS-based applications seem most susceptible to this problem, but Windows-based applications can be affected as well. Windows-based applications generally report segment load failures when the network connection is lost. MS-DOS-based applications that leave a lot of files open, such as database programs, are more susceptible to this problem. If network connections are lost or dropped, the system or application may stop responding(hang), the network installation of Windows for Workgroups may become corrupted, and MS-DOS-based applications may produce unexpected results. WARNING: If you lose your Windows for Workgroups connections, immediately save all open data files to backup files on your local drive or a remote drive where you still have a valid connection. MORE INFORMATION ================ Loss of network connections can occur when you use any version of the redirector, but the basic redirector, invoked by using the "NET START BASIC" command, is most likely to have this problem. The problem seems to be caused by a timing issue in the NetBEUI protocol. It may also be related to the network buffer size because it occurs when data is being sent over the wire. In testing, this problem didn't occur unless the system was running under the conditions listed above; however, the problem may occur when a system is not under any stress, but this is very rare. Other factors that can cause connection problems include the following: - Network cards: Some network cards are more prone to these problems than others. - Machine speed: The slower the machine, the more likely that its network connections may be lost. This problem usually originates with the server but affects clients only. Attempting to Recover --------------------- To determine if you have lost network connections, go to the server and use Net Watcher to see if the machine that is not responding still has a valid session open. This method does not always work because some applications can reopen the network connections. Some applications may not be affected by a lost network connection if they are not dependent on file pointers being maintained on the server. Sometimes you can issue the NET USE command at the command prompt to determine whether or not a session has been disconnected. This technique works best when the machine is not using a network installation (SETUP /N) of Windows. Issuing the DIR command may restore the network connection and allow the application to continue or at least exit without causing the system to stop responding (hang). You can also try to close all open files and attempt to quit Windows. If the problem results from a network installation of Windows having lost its network connections, you will get a message telling you that you do not have enough memory to complete the operation. Avoiding the Problem -------------------- The following steps may help prevent this problem: - Increase FILES= to 128 or higher in the CONFIG.SYS file. - Increase FCBS= to 25 or higher in the CONFIG.SYS file. - Increase Sessions= to 20 or higher in the PROTOCOL.INI file. - Set NCBS= to 40 in the PROTOCOL.INI file. - Set NetHeapSize= to 52 in the [386Enh] section of the SYSTEM.INI file. - Set TimerCriticalSection= to 5000 or higher in the [386Enh] section of the SYSTEM.INI file. - If you are using a network installation of Windows (Setup /N) set maintainserverlist= to NO in the [network] section of the SYSTEM.INI file. KBCategory: kbnetwork kbtshoot KBSubcategory: wfw wfwg Additional reference words: 3.10 3.11 sessions install tshoot Windows for Workgroups: How VSHARE.386 Manages File Sharing Article ID: Q90239 ---------------------------------------------------------------- --- The information in this article applies to: - Microsoft Windows for Workgroups, version 3.1 ---------------------------------------------------------------- --- SUMMARY ======= The Windows for Workgroups file sharer, VSHARE.386, contains several improvements over the MS-DOS file sharing utility, SHARE.EXE. These improvements allow Windows for Workgroups to share files in a manner similar to other network operating systems. This article defines the file sharer (NOT the file server) and its function in the operating system. MORE INFORMATION ================ To be able to allow multiple users or programs concurrent access to files and resources, an operating system must provide two basic services: - Arbitration of access requests - Updating of in-memory information that describes resources Under MS-DOS, these two functions are handled by a component known as the file "sharer." This component is separate from the MS-DOS kernel. For MS-DOS versions 3.00 and later, this functionality is provided by the terminate-and-stay-resident (TSR) program, SHARE.EXE. Microsoft Windows for Workgroups version 3.1 when running in Enhanced Mode, replaces this with a new program, VSHARE.386. VSHARE.386 is intended as a drop-in replacement for SHARE.EXE. Because VSHARE is an Enhanced Mode virtual device driver (VxD), it has features which improve file sharing under Enhanced Mode. Because it was designed to work with Windows for Workgroups, VSHARE has features to make it "friendlier" than SHARE.EXE, especially in the area of access control. If SHARE.EXE is loaded and you start Windows for Workgroups in Enhanced Mode, VSHARE takes over as file sharer until you exit Windows. If you usually run Windows for Workgroups in Enhanced Mode, you may not need to run SHARE.EXE at all (this can save 5K or more of conventional memory). For each file open on the local computer, MS-DOS maintains a copy of information about the file in memory. This includes both global information that pertains to the file on disk, such as the file's location on disk and its size, and local information that pertains to each open instance of the file, such as the application's file pointer. If a file is opened by multiple programs, and one application changes a global attribute of the file, the sharer updates the information for all file handles open on that file. NOTE: The file handles that applications use to keep track of files point to the copies of information about files maintained by MS-DOS in memory. If the real mode sharer SHARE.EXE is present without VSHARE, then all information needed to open a file must be in memory at all times, even when Enhanced Mode virtual memory is being used. (Virtual memory cannot be swapped into or out of memory while MS-DOS is busy with a file system request.) When you use VSHARE instead of (or in addition to) SHARE, file open information for multiple Virtual Machines (VMs) does not need to be in memory at the same time, only when each VM is active. (MS-DOS applications run in separate VMs, and the Windows for Workgroups file server runs its own separate VM.) NOTE: This means you can use the Enhanced Mode PerVMFiles setting with VSHARE, which means you can open more files using VSHARE than using SHARE when running Windows for Workgroups in Enhanced Mode. See the "Microsoft Windows Resource Kit," version 3.1, for a discussion of the PerVMFiles setting. Unlike SHARE (which uses global conventional memory), VSHARE uses extended memory to store its copy of open file information. This greatly increases the number of open files that Windows for Workgroups, especially the server, can work with at once. Applications which use file locking, such as Microsoft Mail, are less likely to run out of file locks with VSHARE than with SHARE. Because Windows for Workgroups is designed to function as a peer server, the access control rules used by SHARE have been relaxed somewhat in VSHARE. SHARE forbids the opening of "compatibility mode" files while a "sharing" file is open, and vice versa. SHARE forbids the opening of "compatibility mode" files from different machines or VMs. Since a large percentage of MS-DOS applications and Windows applications still use compatibility mode, SHARE prevents the Windows for Workgroups server from operating effectively with several clients connected to one server (the only way SHARE could operate in this environment is if all the files on the server had read-only attributes). This makes it inconvenient for network administrators to set up directories of shared files on a network file server. Using VSHARE, a compatibility mode read request can be active from different machines and at the same time as most sharing requests. This makes it easy to set up a directory of shared files under Windows for Workgroups. The access rules are only relaxed for "safe" access requests. If a process tries to open a file to write to it, for example, the more restrictive set of rules is used. This new file access behavior is known as "softcompat mode." There may be a reason to disable this, if there is a conflict with an older application that has problems with the new access rules. This can be done by placing "SOFTCOMPATMODE=FALSE" in the [386ENH] section of the Windows SYSTEM.INI file. There are no applications known to require this setting. It is necessary to use a file sharer on any machine being used as a file server or peer server. If an access violation happens on a server and "Sharing Violation" error message appears, it interferes with server performance. This is because MS-DOS is in a critical section while the error message pop-up is visible. For this reason, VSHARE disables sharing violation pop-up messages on MS-DOS versions 4.01 and greater. If this causes problems, you can add the "ENABLESHARINGPOPUPS=TRUE" setting to the [386ENH] section of the Windows SYSTEM.INI file. There are no applications known to require this setting. The file sharer can also be used to control access to MS-DOS device drivers, if these are opened using MS-DOS file system calls. With SHARE present, it is possible to get sharing violations on the NUL and CON devices. VSHARE does not generate sharing violation error messages when you access these devices. You can restore SHARE device sharing functionality by adding "TRADITIONALDEVICESHARING=TRUE" to the [386ENH] section of the Windows SYSTEM.INI file. There are no applications known to require this setting. Some applications are incompatible with file access checking. In general, it is not recommended that you run such applications under Windows for Workgroups, especially while the file server is running. You can use the SYSTEM.INI switch "IGNORESHARINGVIOLATIONS=TRUE" to diagnose such problems that occur when VSHARE is installed. This switch turns off file access checking for all files and devices in the system. Use this switch to diagnose problems only; you should not use it to correct problems. It usually causes more problems than it solves. If any application refuses to run with SHARE or VSHARE installed, contact the application vendor for assistance. Sometimes problems occur where a "network aware" version of an application does not keep application documents open. These applications attempt to arbitrate document access by using a semaphore or marker in the document file or on disk. This technique usually fails in a multi-user network environment due to synchronization problems. In order to write an application properly to handle multi- user or multi-application access to data files, the first instance of the application accessing any data file should KEEP THE FILE OPEN to allow the file sharer and MS-DOS to communicate to subsequent applications that the file is in use. This suggestion applies equally to SHARE and VSHARE. There is no way that the file sharer can know that a file is "busy" unless it is actually kept open by the application. Troubleshooting Tip ------------------- If problems with file sharing are suspected, remember that the file sharer responsible for a specific file is the sharer running on the machine where the file is physically located. If file sharing problems occur while you access a file on a network drive, modifying the VSHARE settings on the local machine will not help. KBCategory: kbusage kbtshoot KBSubcategory: wfw wfwg Additional reference words: 3.10 tshoot \* 311CHECK \* nowin4 - jeffthi Troubleshooting MS Backup and MS Backup for Windows Article ID: Q94639 ---------------------------------------------------------------- ---- The information in this article applies to: - Microsoft MS-DOS operating system versions 6.0, 6.2, 6.21, 6.22 - Microsoft Windows operating system versions 3.0, 3.0a, 3.1, 3.11 ----------------------------------------------------------------- --- SUMMARY ======= If you encounter problems running Microsoft Backup for MS-DOS or Microsoft Backup for Windows, use the steps in the following section to correct the problems. NOTE: If your computer fails the compatibility test, query on the following words in the Microsoft Knowledge Base for more information: compatibility and test and fails Common problems caused by incorrect system configuration include the following: - Microsoft Backup appears to stop responding (hang) when run from the MS-DOS command prompt in Windows. - Microsoft Backup for Windows causes Windows to close, leaving the MS-DOS command prompt displayed on the screen. - Windows reports that the DMA buffer size needs to be increased to 64. MORE INFORMATION ================ Troubleshooting Microsoft Backup for Windows and Microsoft Backup ----------------------------------------------------------------- 1. Microsoft does not recommend or support running the MS-DOS-based version of Microsoft Backup (MSBACKUP.EXE) with Windows. If you choose to do this, you should create a program information file (PIF) with the following settings for Microsoft Backup: Display Usage: Full Screen Execution: Exclusive 2. Your CONFIG.SYS file should include the following settings (the values shown are minimums): FILES=30 BUFFERS=30 STACKS=9,256 3. The DMABufferSize= line should be set to at least 32 in the [386Enh] section of the SYSTEM.INI file. In some situations, the DMA buffer size needs to be set to 40 (either in the SYSTEM.INI file, or using EMM386.EXE, or both). 4. If you are using MSBACKUP.EXE in Windows or the Windows version of Microsoft Backup (MWBACKUP.EXE), you should place the following line in your SYSTEM.INI file if Setup did not install it: device=c:\dos\vfintd.386 If you omit this line, Backup displays the following error message: Microsoft Backup is not properly installed on this system. Please reinstall Microsoft Backup, or make the following changes to your SYSTEM.INI file: [386Enh] DEVICE=[ms-dos path]VFINTD.386 KBCategory: kbtool kbdisplay kbtshoot kbenv KBSubcategory: msdos Additional reference words: 6.22 6.00 6.20 3.00 3.00a 3.10 win31 win3 win30 tshoot ms-dos back up msbackup mwbackup Your Computer Fails the Microsoft Backup Compatibility Test Article ID: Q97577 ---------------------------------------------------------------- ---- The information in this article applies to: - Microsoft MS-DOS operating system versions 6.0, 6.2, 6.21, 6.22 ----------------------------------------------------------------- --- SYMPTOMS ======== Your computer fails the Microsoft Backup compatibility test. CAUSE ===== Your computer may fail the Microsoft Backup compatibility test for the following reasons: - The floppy drive controller card does not support direct memory access (DMA). - A software compatibility problem exists in MS-DOS. - You are using a third-party virtual device driver (VxD) in Windows. - The floppy disk is not properly seated. - The floppy disks you are using are failing or are formatted incorrectly. - You are loading APPEND.EXE, causing the following error message: The file does not exist. The file cannot be compared. - You are running POWER.EXE. - You are using a third-party extended memory manager (such as QEMM with FL=0 and FEMS). - The buffers and files settings in your CONFIG.SYS file are inadequate. - You don't have enough free disk space for Microsoft Backup to create temporary files. WORKAROUND ========== Troubleshooting the MS-DOS-Based Version of Microsoft Backup ------------------------------------------------------------ If you are running the MS-DOS-based version of Microsoft Backup, start your computer with the Clean Start function key (F5) and try the compatibility test again. If the compatibility test still fails, check the CONFIG.SYS file for the following settings: buffers=30 files=30 stacks=9,256 If the buffers and files are not at least 30, increase them to 30 and save the CONFIG.SYS file. Restart the computer using an interactive boot (F8). Respond "Y" only to buffers and files, and then retry the compatibility test. If the test fails again, follow the instruction in the "Manual Backup to Path Test" section below. Troubleshooting Microsoft Backup for Windows -------------------------------------------- If you are running Microsoft Backup for Windows: 1. Run File Manager and format a floppy disk to see if you are having problems formatting floppy disks from Windows. 2. Try running Windows in standard mode and then running the compatibility test. If the compatibility test works in standard mode but does not work in 386 enhanced mode, remove any virtual device drivers (VxDs) that may conflict with VFINTD.386. For example, tape backup VxDs may conflict with VFINTD.386. The following software VxDs (loaded in the [386enh] section of the SYSTEM.INI file) can cause the compatibility test to fail: DEVICE=MYABU.386 DEVICE=FASTBACK.386 DEVICE=VFD.386 DEVICE=CPBVXD.386 DEVICE=VIRWT.386 DEVICE=CMSTAPE.386 DEVICE=CMSTAPED.386 DEVICE=CMSDTAPE.386 DEVICE=ABACKUP.386 NOTE: Backup for Windows may fail by either dropping to the MS-DOS command prompt, blanking the screen, or hanging the system when it reaches 99% completion. Manual Backup to Path Test -------------------------- If the compatibility test fails, you cannot back up to drive A or B using the specific drive options. Instead, you must back up to the MS-DOS path. When you back up to the MS-DOS path, all your floppy disks must be formatted before you begin backing up. This feature (backing up to the MS-DOS path) is implemented in Microsoft Backup to provide maximum compatibility with the various hardware being produced. NOTE: Be sure the disks being used for the compatibility test are formatted using the MS-DOS FORMAT command. The disks may have been pre-formatted, or formatted using a third-party utility, such as PC Tools or Norton Utilities. This may cause the compatibility test to fail. To find out if they were formatted using such a utility, check the date on the FORMAT.COM in the DOS directory. It should be 3-10-93 for MS-DOS 6.0. To test backing up to the MS-DOS path, do the following: 1. Start Microsoft Backup or Microsoft Backup for Windows. 2. Choose the Select Files Button and select approximately 2 MB of files--enough that all the files cannot fit on one floppy disk. For more information on selecting files, see the Selecting Files For Backup Help topic. 3. After you have selected approximately 2 MB of files, choose the OK button. 4. In the Backup To box, select MS-DOS Path. 5. In the Backup To text box, type "A:\" or "B:\" (without the quotation marks) and then choose the Start Backup button. 6. Change the disk in the floppy disk drive when you are prompted to do so. 7. When Microsoft Backup has completed the backup, choose the OK button. 8. Choose the Compare button. 9. Choose the Select Files Button and select the files you backed up. 10. Choose the Start Compare button. If the compare successfully completes, you can safely back up to the MS-DOS path. KBCategory: kbtool kbtshoot kbenv KBSubcategory: msdos Additional reference words: 6.00 6.20 MSBACKUP.EXE MWBACKUP.EXE diskette win31 disks bad fail failure trouble shoot shooting troubeshoot troubleshooting tshoot t-shoot lockup device=c:\windows c:\mybackup c:\abackup MSBACKUP MWBACKUP Using Novell's ODI Drivers with Windows for Workgroups Article ID: Q97767 The information in this article applies to: - Microsoft Windows for Workgroups version 3.1 ---------------------------------------------------------------- -- The following article contains information about using Windows for Workgroups with third-party products or configurations that have not been tested and are not supported by Microsoft. If the steps or procedures described in this article do not function properly, use a supported configuration or contact the manufacturer of the third-party product for more information. SUMMARY ======= Some Novell NetWare network-based applications require the Novell open data-link interface (ODI) transport/media-access-control drivers to operate. Windows for Workgroups version 3.1 uses MSIPX to emulate IPX and does not support Novell's ODI drivers. Novell has developed a workaround using ODINSUP.COM to enable the ODI drivers with Windows for Workgroups. Microsoft can ensure connectivity between Windows for Workgroups version 3.1 and Novell NetWare only while running MSIPX.COM. If Novell's procedure for enabling the ODI drivers does not work, contact Novell Technical Support for more information or possible solutions. NOTE: Microsoft Windows for Workgroups version 3.11 works well with Novell NetWare. You must have ODI working first. If you have ODI working and connecting to your Novell server, all you need to do under Windows for Workgroups version 3.11 is add ODI support to your Network Setup (no MSIPX is needed). The remainder of this article applies to Windows for Workgroups 3.1 only. MORE INFORMATION ================ While the specification of Windows for Workgroups version 3.1 is MSIPX, an exclusively NDIS-compliant protocol, Novell's ODINSUP.COM, allows NDIS protocol stacks to run unmodified over the ODI LSL and talk to an ODI LAN driver. Novell's LSL can be accessed by adding the ODINSUP driver. Novell makes these files available on its bulletin board service (BBS) and in the Novell CompuServe forum. The current filename is DOSUP7.ZIP; however, it may change from time to time. Contact your Novell service person or the Novell CompuServe forum for more information on availability. Below are the steps to configure Windows for Workgroups 3.1 using an NE2000 network card with Novell's ODINSUP driver. The modified configuration files include the following: CONFIG.SYS AUTOEXEC.BAT NET.CFG PROTOCOL.INI Before You Begin ---------------- Since this configuration requires the Novell IPXODI drivers, you must have your machines set up and attached to a Novell server using IPXODI.COM at MS-DOS before proceeding to the "Setup Instructions" below. Be sure to back up your AUTOEXEC.BAT file so that you can restore this configuration later if necessary. Setup Instructions ------------------ 1. Install Windows for Workgroups with your network card and Novell NetWare as a secondary network. 2. Edit the CONFIG.SYS file and remove or remark out the following lines: DEVICE=C:\WINDOWS\ DEVICE=C:\WINDOWS\MSIPX.SYS NOTE: If you are using a different network card, the NDIS network card driver ( in the above example) will be different. 3. Edit the AUTOEXEC.BAT file as follows. a. Remove or remark out the following lines: C:\WINDOWS\NET START -and- C:\WINDOWS\MSIPX.COM b. Verify that your AUTOEXEC.BAT contains these lines: C:\\LSL.COM C:\\.COM C:\\ODINSUP.COM C:\WINDOWS\Net Start Netbind C:\\IPXODI.COM C:\\NETX.EXE 4. Edit the NET.CFG file and verify that it contains the following lines. If these lines don't exist, add them to the appropriate sections of the NET.CFG file. If you do not have a NET.CFG file, create one using a text editor (such as Microsoft Windows Notepad), and save it in the directory that LSL.COM is executed from. PROTOCOL ODINSUP BIND NE2000 BUFFERED LINK DRIVER NE2000 <== where NE2000 is the filename of your netcard's ODI driver> INT n <== where "n" is the one-digit interrupt number MEM nnnnn <== where "nnnnn" is the five-digit memory address PORT ### <== where "nnn" is the three-digit I/O port address FRAME ETHERNET_802.2 FRAME ETHERNET_802.3 FRAME ETHERNET_II FRAME ETHERNET_SNAP PROTOCOL IPX 0 ETHERNET_802.3 NOTE: if you've been using ODI to attaching to a Novell server at DOS and you haven't specified the INT, MEM, PORT, DMA, SLOT, etc., parameters in the NET.CFG file, you probably don't need to add them now. However, depending on the ODI MAC driver (Novell refers to this as the "MLID") you are using, you may need to place the INT, MEM, PORT, etc., lines after the FRAME lines. Additionally, list your network's frame type FIRST in the list of "FRAME ETHERNET_xxxx" entries. (This probably will be "ETHERNET_802.3" or "ETHERNET_II.") 5. Edit the PROTOCOL.INI file as follows: Replace the "BINDINGS=" lines in the [MS$NETBEUI] and [IPX$] sections with the Novell ODI MAC driver (MLID) as follows: [MS$NETBEUI] DRIVERNAME=NETBEUI$ SESSIONS=10 NCBS=32 ;BINDINGS=MS$NE2000 <== NDIS MAC driver, NE2000.D0S BINDINGS=NE2000 <== ODI MLID, NE2000.COM LANABASE=1 [IPX$] DRIVERNAME=IPX$ MEDIATYPE=NOVELL/ETHERNET ;BINDINGS=MS$NE2000 <== NDIS MAC driver, NE2000.DOS BINDINGS=NE2000 <== ODI MLID, NE2000.COM IMPORTANT: If the ODI MLID filename begins with a numeral, you must preface the filename with an "X" (without the quotation marks) in the "BINDINGS=" statement. For example, 3COM's 3C509 network adapter card uses an ODI MLID with a filename of "3C509.COM." In the PROTOCOL.INI file, the "BINDINGS=" statements would need to be BINDINGS=x3C509 WARNING: After you make these modifications, do NOT make any changes in the Networks dialog box of Control Panel. If you do, the CONFIG.SYS, AUTOEXEC.BAT, and PROTOCOL.INI files will be overwritten. EXAMPLES ======== Below are samples of what modified CONFIG.SYS, AUTOEXEC.BAT, NET.CFG, and PROTOCOL.INI files look like if you are using Novell's ODINSUP driver. CONFIG.SYS ---------- FILES=30 BUFFERS=30 DEVICE=C:\WINDOWS\PROTMAN.DOS /I:C:\WINDOWS DEVICE=C:\WINDOWS\WORKGRP.SYS LASTDRIVE=P DEVICE=C:\WINDOWS\HIMEM.SYS STACKS=9,256 AUTOEXEC.BAT ------------ PATH=C:\WINDOWS C:\WINDOWS\SMARTDRV.EXE LSL NE2000 ODINSUP C:\WINDOWS\NET START NETBIND IPXODI NETX SET TEMP=C:\WINDOWS\TEMP Q: LOGIN SUPERVISOR NET.CFG ------- PROTOCOL ODINSUP BIND NE2000 BUFFERED LINK DRIVER NE2000 ;The following 4 lines are required with ODINSUP and ethernet cards. FRAME ETHERNET_802.3 FRAME ETHERNET_802.2 FRAME ETHERNET_II FRAME ETHERNET_SNAP PROTOCOL.INI ------------ [NETWORK.SETUP] VERSION=0X3100 NETCARD=NE2000,1,NE2000 TRANSPORT=MS$NETBEUI,MS$NETBEUI TRANSPORT=IPX,IPX LANA0=NE2000,1,IPX LANA1=NE2000,1,MS$NETBEUI [PROTMAN] DRIVERNAME=PROTMAN$ PRIORITY=MS$NETBEUI [NE2000] DRIVERNAME=NE2000 IOBASE=0X300 INTERRUPT=3 [MS$NETBEUI] DRIVERNAME=NETBEUI$ SESSIONS=10 NCBS=32 BINDINGS=NE2000 LANABASE=1 [IPX] DRIVERNAME=IPX MEDIATYPE=NOVELL/ETHERNET BINDINGS=NE2000 For additional information concerning Novell's ODINSUP.COM, contact Novell Technical Support at (800) 638-9273. Novell NetWare and ODINSUP.COM are manufactured by Novell, a vendor independent of Microsoft; we make no warranty, implied or otherwise, regarding these products' performance or reliability. KBCategory: kbnetwork kbsetup kb3rdparty kbfasttip KBSubcategory: wfw wfwg Additional reference words: 3.10 3.1 tcp/ip lsl.com WG0666: WFWG 3.10 Setup Information Article ID: Q99751 ---------------------------------------------------------------- ----- The information in this article applies to: - Microsoft Windows for Workgroups version 3.1 ---------------------------------------------------------------- ----- Microsoft has an Application Note that discusses the installation requirements for Microsoft Windows for Workgroups, the differences between the setup programs for Windows for Workgroups and Microsoft Windows operating system version 3.1, new device drivers and files that ship with Windows for Workgroups, and the administrative setup options (the /A and /N switches). This Application Note is titled "WG0666: Setup Information." You can obtain this Application Note from the following sources: - CompuServe, GEnie, and Microsoft OnLine - Microsoft Download Service (MSDL) - The Internet (Microsoft anonymous ftp server) - Microsoft FastTips Technical Library - Microsoft Product Support Services For complete information, see the "To Obtain This Application Note" section at the end of this article. THE TEXT OF WG0666 ================== ================================================================ ====== Microsoft(R) Product Support Services Application Note (Text File) WG0666: SETUP INFORMATION ================================================================ ====== Revision Date: 5/93 No Disk Included The following information applies to Microsoft Windows(TM) for Workgroups version 3.1. ----------------------------------------------------------------- --- | INFORMATION PROVIDED IN THIS DOCUMENT AND ANY SOFTWARE THAT MAY | | ACCOMPANY THIS DOCUMENT (collectively referred to as an | | Application Note) IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY | | KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO | | THE IMPLIED WARRANTIES OF MERCHANTABILITY AND/OR FITNESS FOR A | | PARTICULAR PURPOSE. The user assumes the entire risk as to the | | accuracy and the use of this Application Note. This Application | | Note may be copied and distributed subject to the following | | conditions: 1) All text must be copied without modification and | | all pages must be included; 2) If software is included, all files | | on the disk(s) must be copied without modification [the MS-DOS(R) | | utility DISKCOPY is appropriate for this purpose]; 3) All | | components of this Application Note must be distributed together; | | and 4) This Application Note may not be distributed for profit. | | | | Copyright 1992 Microsoft Corporation. All Rights Reserved. | | Microsoft and MS-DOS are registered trademarks and Windows | | is a trademark of Microsoft Corporation. OS/2 is a registered | | trademark licensed to Microsoft Corporation. | | | | 3+Share and 3Com and registered trademarks and 3+Open is a | | trademark of 3Com Corporation. AT&T is a registered trademark of | | American Telephone and Telegraph Company. Banyan and VINES are | | registered trademarks of Banyan Systems, Inc. DEC is a registered | | trademark and Pathworks is a trademark of Digital Equipment | | Corporation. TCS is a registered trademark of Eurotherm | | International P.L.C. IBM and OS/2 are registered trademarks of | | International Business Machines Corporation. NetWare and Novell | | are registered trademarks of Novell, Inc. Olivetti is a registered | | trademark of Ing. C. Olivetti. | ---------------------------------------------------------------- ---- INTRODUCTION ============ This application note discusses installation requirements for Microsoft Windows for Workgroups, the differences between the Setup programs for Windows for Workgroups and Microsoft Windows operating system version 3.1, new device drivers and files shipped with Windows for Workgroups, and the administrative Setup options (the /A and /N switches). INSTALLATION REQUIREMENTS ========================= To install and use Windows for Workgroups you must be using MS-DOS version 3.3 or later. To upgrade from a previous installation of Windows, your Windows version must be 3.0 or later, and your Windows files must be included in your PATH statement. (If you have a version of Windows earlier than 3.0, you need to do a complete Windows for Workgroups installation, not an upgrade.) If you want to preserve your Program Manager groups and other existing Windows settings, you need to install Windows for Workgroups in the directory of your current Windows installation. DISK SPACE REQUIREMENTS ======================= Windows for Workgroups requires approximately 4.5 megabytes (MB) more disk space than Windows 3.1. The following table illustrates the disk space requirements for the most common installation types. Type of Installation Windows 3.1 Windows for Workgroups 3.1 ----------------------------------------------------------------- ---- Full installation (286) 8.6 MB 13.8 MB Upgrade 3.x (286) 5.2 MB 6.6 MB Full installation (386) 9.5 MB 15.0 MB Upgrade 3.x (386) 5.2 MB 10.0 MB Network administrator (Setup /A) 15.3 MB 21.0 MB Network setup (Setup /N) .3 MB 1.2 MB SUPPORTED NETWORKS ================== The following networks are supported for use with Windows for Workgroups: Microsoft Workgroup Client (all versions) Microsoft LAN Manager (version 2.1) Novell(R) NetWare(R) (all versions) Before starting a shared copy of Windows for Workgroups that is installed over one of these networks, please use the following guidelines: Novell NetWare Network ---------------------- If you are running a shared copy of Windows for Workgroups on a Novell workstation, be sure to log on to the Novell server before starting Windows for Workgroups. LAN Manager or Windows for Workgroups Network --------------------------------------------- If you are running a shared copy of Windows for Workgroups on a LAN Manager or Windows for Workgroups workstation, be sure to start the network workstation services before you start Windows for Workgroups. You can do this with the "net start workstation" command. If you are using the Windows for Workgroups network drivers, you can start the workstation services automatically by placing either of the following entries in the [network] section of your SYSTEM.INI file: AUTOSTART=FULL AUTOSTART=BASIC Setting AUTOSTART to FULL installs the enhanced network redirector. The enhanced redirector supports named pipes and LAN Manager application programming interface (API) functions. Setting AUTOSTART to BASIC installs the basic network redirector, which uses less system memory but does not support named pipes. Neither redirector supports network messaging services, or pop-up messages. LAN Manager automatically installs the redirector based on entries in your AUTOEXEC.BAT and CONFIG.SYS files. These settings are specified in the LAN Manager network documentation. NOTE: Setup adds the AUTOSTART switch for you if you are installing on a 286-based machine. UNSUPPORTED NETWORKS ==================== The following networks that are supported under Windows 3.1 are not specifically supported in the Windows for Workgroups package. (Drivers for these networks are not shipped with Windows for Workgroups but might be available through your network vendor.) No Network Installed Artisoft LANtastic (all versions) Banyan(R) VINES(R) (all versions) DEC(R) Pathworks(TM) (all versions) IBM(R) OS/2(R) LAN Server (all versions) IBM PC-LAN Program (all versions) Microsoft LAN Manager (version 2.0 and earlier) Microsoft Networks or compatible (all versions) TCS(R) 10Net (all versions) 3Com(R) 3+Share(R) (all versions) 3Com 3+Open(TM) (all versions) Setup does not detect these networks, and therefore cannot notify you if they are installed on your system. Check with your network vendor to obtain the necessary drivers before you install Windows for Workgroups over any of these networks. Then, perform the procedure below. Drivers that support using Banyan VINES and DEC Pathworks with Windows for Workgroups are available from Banyan Systems and Digital Equipment Corporation. To use Windows for Workgroups with a different network ------------------------------------------------------ NOTE: This procedure won't be useful unless the drivers you obtained from your vendor are compatible with Windows for Workgroups. 1. Open Control Panel, and from the Settings menu, choose Network. (Or choose the Network icon.) 2. In the Network Settings dialog box, choose the Networks button. The Compatible Networks dialog box appears. 3. From the Available Network Types list, select Unlisted Or Updated Network, and then choose the Add button. You will be prompted to insert the disk containing the network driver supplied by your vendor. When you insert the floppy disk, Setup installs the network driver. The new network should now appear in the Available Network Types group. 4. Select the network, and then choose the Add button. This adds the network to the Other Networks In Use list. 5. Choose the OK button twice to exit the Networks dialog boxes. Close Control Panel and then reboot your machine. Important: To use the new driver(s), you must reboot your machine. DIFFERENCES IN SETUP PROGRAMS FOR WINDOWS 3.1 AND WINDOWS FOR WORKGROUPS 3.1 ========================================== This section discusses new features in the Windows for Workgroups Setup program, including network detection and dialog box changes. NETWORK-DETECTION ISSUES ======================== - Setup no longer prompts for a network type. Setup always selects Windows for Workgroups as the network type. - Windows for Workgroups Setup performs network card detection. If Setup fails to detect your network card, it prompts you to choose from a list of available network adapters. DIFFERENCES IN DIALOG BOXES =========================== - Setup now asks for the computer name and the workgroup in the initial user name dialog box. - After Setup completes printer installation, the Install New Network Adapter, Network Adapters, and Compatible Networks dialog boxes may appear, as the following table illustrates. Dialog Box Express Setup Custom Setup ------------------------------------------------------------- Install New Network Adapter Conditional Conditional Network Adapters No Yes Compatible Networks Conditional Yes The Install New Network Adapter dialog box does not appear during either Express or Custom Setup if the Network Card Detection (NCD) utility detects your network card and you confirm the detected network card. Confirming the detected network card places a network adapter entry in PROTOCOL.INI. If you don't confirm the detected network card, then the Install New Network Adapter dialog box appears. If you are upgrading from a Workgroup Connection or LAN Manager 2.1 installation, there is already a valid network adapter entry in PROTOCOL.INI, and this dialog box is skipped. The Compatible Networks dialog box does not appear during Express Setup if you are upgrading from a LAN Manager 2.1 installation. Selecting a network in this dialog box places a multinet= entry in the [network] section of SYSTEM.INI. If Setup detects the existing LAN Manager 2.1 installation, Setup places the multinet= entry in SYSTEM.INI and therefore skips the Compatible Networks dialog box. - The option to Restart Windows once Setup is complete is no longer available. This is because in order to load or upgrade network drivers, you must reboot your machine. DRIVERS AND FILES SHIPPED WITH WINDOWS FOR WORKGROUPS ===================================================== Setup does not delete drivers that were installed with Windows 3.1 but not shipped with Windows for Workgroups. The following table shows the drivers and files that are shipped with Windows 3.1 and Windows for Workgroups. Driver or File Windows 3.1 Windows for Workgroups ----------------------------------------------------------------- --- Quad video driver Yes No ATI VIP video driver Yes No 82C441 video driver Yes No ET 4000 video driver No Yes--however, Windows for Workgroups does not detect this display. You must manually select the driver. Olivetti(R)/AT&T(R) Yes No Keyboard Mouse driver MSCDEX CD-ROM driver Yes Yes--updated. If there is an and TBMI2.COM file existing MSCDEX driver or TBM12.COM file, Setup copies the new driver and file to the Windows directory and modifies the AUTOEXEC.BAT file to point to the new (updated) driver and file. WFWNET.DRV No Yes VNETBIOS.386 No Yes VNETSUP.386 No Yes VREDIR.386 No Yes VSERVER.386 No Yes VBROWSE.386 No Yes VWC.386 No Yes NETAPI.DLL No Yes PMSPL.DLL No Yes NETDDE.EXE No Yes NDDENB.DLL No Yes WFWSETUP.CPL No Yes NETWORK.INF No Yes LM21DRV.UPD No Yes WFWNET.HLP No Yes CLIPSRV.EXE (ClipBook No Yes server) CLIPBRD.EXE (ClipBook No Yes Viewer) WINCHAT.EXE (Chat) No Yes WINMETER.EXE No Yes (WinMeter) MSMAIL.EXE (Mail) No Yes SCHDPLUS.EXE No Yes (Schedule) NETWATCH.EXE No Yes (NetWatcher) MSHEARTS.EXE (Hearts) No Yes CALENDAR.EXE Yes No (Calendar) SSMYST.SCR (Mystify Yes No screen saver) ARCHES.BMP (Arches Yes No wallpaper) CHITZ.BMP (Chitz Yes No wallpaper) FLOCK.BMP (Flock Yes No wallpaper) MARBLE.BMP (Marble Yes No wallpaper) TARTAN.BMP (Tartan Yes No wallpaper) CHORD.WAV (Chord Yes No sound) TADA.WAV (Trumpet Yes No sound) APPS.HLP (Application Yes No Compatibility Help) COMMCTRL.DLL No Yes FRAMEWRK.DLL No Yes MAILMGR.DLL No Yes MAILSPL.EXE No Yes MAPI.DLL No Yes MSSFS.DLL No Yes PABNSP.DLL No Yes DEMILAYR.DLL No Yes SENDFILE.DLL No Yes STORE.DLL No Yes VFORMS.DLL No Yes AB.DLL No Yes NDDEAPI.DLL No Yes VSHARE.386 No Yes VCD.386 Yes Yes VDMAD.386 Yes Yes VPICD.386 Yes Yes VPD.386 Yes Yes ADMINISTRATIVE SETUP OPTIONS (SETUP /A AND SETUP /N) ==================================================== You run Setup with the /A and /N options to configure a workstation to run Windows from a shared directory. Setup with the /A option (Administrative Setup) copies all the files from the Windows distribution disks to a single directory and marks them read only. This directory can then be used to install and run a shared copy of Windows. Setup /N sets up the shared copy of Windows. In a stand-alone Windows 3.1 installation, the Windows directory and SYSTEM subdirectory are on your personal hard drive. In a shared Windows installation, the Windows directory can be located on the user's hard disk drive or on a network drive, and can be customized for each user. There is no SYSTEM subdirectory, as such, in a network installation; system files are typically located in a shared directory on a network server. In Windows for Workgroups, as in Windows 3.1 running on a network, the personal Windows directory contains all files with .INI, .GRP, and .PIF extensions, as well as REG.DAT, WIN.COM, WINVER.EXE, and any MS- DOS device driver files. The personal Windows directory may also contain the MS-DOS network device drivers and the NET.EXE, MSIPX.COM, and NETX.COM files. (These files may also be copied to the root directory of the boot drive, as explained in the following section.) The shared directory contains all other Windows files. WHERE SETUP PLACES NETWORK FILES ================================ The Windows 3.1 Setup program reads SETUP.INF to determine where to install files. SETUP.INF uses the file classifications "windir" and "sysdir" to refer to files that Setup installs in the Windows directory and SYSTEM subdirectory, respectively. The Windows for Workgroups Setup program reads NETWORK.INF to determine where to install files. Setup places files with the windir classification in the personal Windows directory and files with the sysdir classification in a shared server directory. NETWORK.INF also uses two new file classifications, "netdir" and "devdir." Where Setup places these files depends on the type of installation. Real-mode network device drivers (devdir files) are copied to the personal Windows directory on a local nonremovable, noncompressed drive. These include PROTMAN.DOS, PROTOCOL.INI, and WORKGRP.SYS. If the personal Windows directory is on a remote, removable, or compressed volume, then these files are copied to the root of the boot drive. These device drivers must be correctly referenced in CONFIG.SYS. Real-mode network utilities and terminate-and-stay-resident (TSR) programs (netdir files) are copied to the personal Windows directory on a nonremovable hard disk. These include NET.EXE, MSIPX.COM, NETX.COM, and ROUTE.COM. If the personal Windows directory is on a remote or removable volume, these files are copied to the same directory as the devdir files. These utilities and TSRs must be correctly referenced in the AUTOEXEC.BAT file. NOTE: If your personal Windows directory is on a remote volume, you still need to have your own hard disk drive to run Windows for Workgroups. Windows for Workgroups does not support diskless workstations or systems with no hard disk drive. The following table illustrates where Setup places the netdir and devdir files for different installations. Location of Location of Location of Windows Installation Netdir Files Devdir Files -------------------------------------------------------------- Nonremovable hard disk drive Windows Windows Compressed (nonremovable hard Windows Root disk) drive Removable drive (for example, Root Root SCSI) Remote drive (Setup /N) Root Root SETUP /H (BATCH MODE SETUP) =========================== You can use Setup with the /H option to automate the Setup program. Windows for Workgroups and Windows 3.1 come with a system-settings template file called SETUP.SHH, which you can copy or modify to create a custom system-settings file. In addition to the settings specified in the Windows 3.1 template file, the Windows for Workgroups template file includes parameters for the computer name, workgroup, network card, protocol, and compatible network. The SETUP.SHH file is located on Windows for Workgroups 3.1 Disk 1 and is copied to the shared Windows for Workgroups directory when you run Setup /A. You can modify the template file with any text editor that can save unformatted text (ASCII) files. For more information about batch mode setup, refer to Chapter 3 of the "Microsoft Windows for Workgroups Resource Kit." ---------------------------------------------------------------- ---- TO OBTAIN THIS APPLICATION NOTE =============================== - On CompuServe, GEnie, and Microsoft OnLine, Application Notes are located in the Microsoft Software Library. You can find WG0666 in the Software Library by searching on the word WG0666, the Q number of this article, or S13676. WG0666 is a compressed, self-extracting file. After you download WG0666, run it to extract the file(s) it contains. - On the Internet, Application Notes are located on the Microsoft anonymous ftp server, which you can reach by typing "ftp ftp.microsoft.com" (without the quotation marks) at the ">" command prompt. You can find WG0666.EXE in the SOFTLIB/MSLFILES directory. - Application Notes are available by modem from the Microsoft Download Service (MSDL), which you can reach by calling (206) 936-6735. This service is available 24 hours a day, 7 days a week. The highest download speed available is 14,400 bits per second (bps). For more information about using the MSDL, call (800) 936-4200 and follow the prompts. To obtain WG0666, download WG0666.EXE. - You can have this Application Note mailed or faxed to you from the automated Microsoft FastTips Technical Library, which you can call 24 hours a day, 7 days a week at (800) 936-4200. NOTE: The FastTips Technical Library is available only to customers within the U.S. and Canada. - If you are unable to access the source(s) listed above, you can have this Application Note mailed or faxed to you by calling Microsoft Product Support Services Monday through Friday, 6:00 A.M. to 6:00 P.M. Pacific time at (206) 637-7098. If you are outside the United States, contact the Microsoft subsidiary for your area. To locate your subsidiary, call Microsoft International Sales Information Center at (206) 936-8661. KBCategory: kbnetwork kbdisplay kbsound kb3rdparty kbfile kbappnote kbsetup KBSubcategory: wfw wfwg Additional reference words: appnote 3.10 set up WFWG Err Msg with New NETAPI.DLL: Call to Undefined Dynalink Article ID: Q101238 ---------------------------------------------------------------- ---- The information in this article applies to: - Microsoft Windows for Workgroups versions 3.1, 3.11 ---------------------------------------------------------------- ---- SYMPTOMS ======== If you use the NETAPI.DLL file and NetWare with Microsoft Windows for Workgroups (WFWG) version 3.1, you receive the following error message: Undefined call to Dynalink -or- Call to Undefined Dynalink CAUSE ===== The NETAPI.DLL file included with WINUP7.ZIP is designed for use with Microsoft Windows 3.1. The NETAPI.DLL file included with WINUP8.ZIP is designed to add support for Novell named pipes. Windows for Workgroups 3.1 and 3.11 do not support Novell named pipes. WORKAROUND ========== To correct the problem, follow these steps: 1. Close the error message. This exits Windows for Workgroups. 2. Rename the NETAPI.DLL file in the \WINROOT directory and any others found in the PATH statement. 3. Use the NETAPI.DLL file provided with Windows for Workgroups by expanding it from your original disks. For example, type the following at the MS-DOS command prompt, and then press ENTER: expand a:\netapi.dl_ c:\windows\system\netapi.dll NOTE: Refer to the following table to determine on which disk the NETAPI.DL_ file is located: 5.25-inch disks 3.5-inch disks --------------------------------------------- WFWG 3.1 disk 1 disk 2 WFWG 3.11 disk 8 disk 7 MORE INFORMATION ================ For additional information, please see the following article(s) in the Microsoft Knowledge Base: Article-ID: Q121462 Title : Obtaining Latest Novell Client Windows Drivers and DLLs For more information on named pipes, query on the following words here in the Microsoft Knowledge Base: novell named pipes The Novell products included here are manufactured by a vendor independent of Microsoft; we make no warranty, implied or otherwise, regarding these products' performance or reliability. KBCategory: kbnetwork kberrmsg kb3rdparty KBSubcategory: wfw wfwg Additional reference words: 3.1 3.10 3.11 novell \WINROOT OLDDLLS subdirectory WW0863: Fixing System Hangs with MS-DOS Apps & Novell NetWare Article ID: Q104551 ---------------------------------------------------------------- ----- The information in this article applies to: - Microsoft Windows operating system versions 3.1, 3.11 ---------------------------------------------------------------- ----- If you run Novell NetWare with Microsoft Windows or Windows for Workgroups, your system may stop responding (hang) when you start an MS-DOS-based application or an MS-DOS command prompt. Microsoft has an Application Note, "System Hangs When Running MS-DOS-Based Applications with Novell NetWare," that provides troubleshooting steps and files that may correct the problem. You can obtain this Application Note from the following sources: - CompuServe, GEnie, and Microsoft OnLine - Microsoft Download Service (MSDL) - The Internet (Microsoft anonymous ftp server) - Microsoft Product Support Services For complete information, see the "To Obtain This Application Note" section at the end of this article. THE TEXT OF WW0863 ------------------ ================================================================ ====== Microsoft(R) Product Support Services Application Note (Text File) WW0863: SYSTEM HANGS WHEN RUNNING MS-DOS-BASED APPLICATIONS WITH NOVELL(R) NETWARE(R) ================================================================ ====== Revision Date: 1/94 1 Disk Included The following information applies to Microsoft Windows(TM), version 3.1. ---------------------------------------------------------------- ------ | INFORMATION PROVIDED IN THIS DOCUMENT AND ANY SOFTWARE THAT MAY | | ACCOMPANY THIS DOCUMENT (collectively referred to as an Application| | Note) IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER | | EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE IMPLIED | | WARRANTIES OF MERCHANTABILITY AND/OR FITNESS FOR A PARTICULAR | | PURPOSE. The user assumes the entire risk as to the accuracy and | | the use of this Application Note. This Application Note may be | | copied and distributed subject to the following conditions: 1) All| | text must be copied without modification and all pages must be | | included; 2) If software is included, all files on the disk(s) | | must be copied without modification (the MS-DOS utility diskcopy is| | appropriate for this purpose); 3) All components of this | | Application Note must be distributed together; and 4) This | | Application Note may not be distributed for profit. | | | | Copyright (C) 1993 Microsoft Corporation. All Rights Reserved | | Microsoft and MS-DOS are registered trademarks and Windows is a | | trademark of Microsoft Corporation. | | CompuServe is a registered trademark of CompuServe, Inc. | | NetWire is a registered servicemark and NetWare and Novell are | | registered trademarks of Novell, Inc. | |--------------------------------------------------------------------| Introduction --------- --- If you are running Novell NetWare when you start an MS-DOS-based application or an MS-DOS command prompt from Microsoft Windows or Windows for Workgroups, the screen may turn black and leave the cursor flashing in the upper-left corner. If you have configured a program information file (.PIF) so that your MS-DOS-based application starts in a window, the screen is completely black; the flashing cursor does not appear when the system stops responding (hangs). Cause ----- The following factors can contribute to this problem (in order of probability): - Third-party device drivers or terminate-and-stay-resident (TSR) programs - An incorrect system configuration - A problem in VIPX.386 - A problem in the Windows 3.1 virtual timing driver (VTD) This problem is uncommon and is difficult to reproduce since it is critical interrupt and/or timing dependent and generally occurs only on large networks with high traffic volumes, which generate many interrupts. Resolution ---------- To troubleshoot this problem, use the steps below. It is important to follow these steps in order and leave each change in place, even though one particular step alone may not correct the problem. Two or more independent problems may combine to cause the symptoms described above. 1. Remove or comment out all unnecessary commands from your CONFIG.SYS and AUTOEXEC.BAT files to prevent conflicts with third-party device drivers or TSR programs. (To comment out a line, type REM at the beginning of the line. After you make these changes, restart your machine.) Starting your machine with a minimal configuration is called a "clean boot." A clean boot is a basic troubleshooting step to test possible conflicts between Windows and various TSR programs and device drivers. NOTE: Once you implement all the steps in this procedure and correct the problem, you can begin to undo the changes you made to clean boot your system. If the problem recurs, you can isolate the device driver, TSR, or application that is causing the problem. 2. Ensure your Startup group is empty, and comment out the LOAD= and RUN= lines in the [windows] section of the WIN.INI file. (To comment out a line, place a semicolon [;] at the beginning of the line.) After you make these changes, restart Windows. 3. In the [386Enh] section of the SYSTEM.INI file, set the InDOSPolling= setting as follows: InDOSPolling=FALSE 4. Remove the TimerCriticalSection= setting from the [386Enh] section of the SYSTEM.INI file, then restart your system. If this doesn't correct the problem, reinsert the line as follows: TimerCriticalSection=10000 5. Upgrade to version 3.32 or later of the Novell shell and Windows driver components available on Novell's CompuServe(R) NOVLIB forum as DOSUP7.ZIP. These components are also available through NetWire(R) and authorized Novell resellers. 6. Novell has updated and released a new VIPX.386 driver that is designed to correct a majority of the critical interrupt problems. Upgrade to version 1.15 or later of the Novell VIPX.386 driver, which is included with this Application Note. To install the new VIPX.386, follow these steps: a. Rename or back up the old VIPX.386 file. b. Copy VIPX.386 from the enclosed WW0863 disk to your Windows SYSTEM subdirectory. For example, if you inserted the WW0863 disk in drive A and your Windows directory is called WINDOWS and is on drive C, type the following command at the MS-DOS command prompt and then press ENTER: copy a:\vipx.386 c:\windows\system c. If you are using IBM(R) LAN Support, put the network card's IRQ in the [VIPX] section of your SYSTEM.INI file. d. Reboot the machine, and then load the ODI drivers. You should also upgrade to version 2.11 or later of IPXODI.COM and version 2.02 or later of LSL.COM. These files are available on Novell's CompuServe NOVLIB forum in a self-extracting file called BSDUP2.EXE. 7. Reboot your system to see if the problem still occurs. If it does, go on to step 8. 8. The VTDA.386 file included with this application note is designed to fix a very small percentage of timer-related problems. To install VTDA.386, follow these steps: a. Copy VTDA.386 from the enclosed WW0863 disk to your Windows SYSTEM subdirectory. For example, if you inserted the WW0863 disk in drive A and your Windows directory is called WINDOWS and is on drive C, type the following command at the MS-DOS command prompt and then press ENTER: copy a:\vtda.386 c:\windows\system b. In a text editor, such as Microsoft Windows Notepad, open the SYSTEM.INI file (located in your Windows directory). c. In the [386Enh] section, change device=*vtd to: device=vtda.386 d. Save the file. e. Quit and then restart Windows. ---------------------------------------------------------------- ------- TO OBTAIN THIS APPLICATION NOTE =============================== - On CompuServe, GEnie, and Microsoft OnLine, Application Notes are located in the Microsoft Software Library. You can find WW0863.EXE in the Software Library by searching on the word WW0863, the Q number of this article, or S14296. WW0863 is a compressed, self-extracting file. After you download WW0863, run it to extract the file(s) it contains. - Application Notes are available by modem from the Microsoft Download Service (MSDL), which you can reach by calling (206) 936-6735. This service is available 24 hours a day, 7 days a week. The highest download speed available is 14,400 bits per second (bps) For more information about using the MSDL, call (800) 936-4200 and follow the prompts. To obtain WW0863, download WW0863.EXE. WW0863.EXE is a compressed, self-extracting file. After you download WW0863.EXE, run it to extract the file(s) it contains. - On the Internet, Application Notes are located on the Microsoft anonymous ftp server, which you can reach by typing "ftp ftp.microsoft.com" (without the quotation marks) at the ">" command prompt. - If you are unable to access the source(s) listed above, you can have this Application Note mailed to you by calling Microsoft Product Support Services Monday through Friday, 6:00 A.M. to 6:00 P.M. Pacific time at (206) 637-7098. If you are outside the United States, contact the Microsoft subsidiary for your area. To locate your subsidiary, call Microsoft International Sales Information Center at (206) 936-8661. KBCategory: kbnetwork kbfile kbappnote kb3rdparty KBSubcategory: win31 wfw wfwg Additional reference words: appnote 3.10 3.1 3.11 WG0904: Support for Novell NetWare 4.0 Article ID: Q104632 ---------------------------------------------------------------- ----- The information in this article applies to: - Microsoft Windows for Workgroups version 3.1 ---------------------------------------------------------------- ----- Microsoft has an Application Note, "WG0904: Support for Novell(R) Netware(R) 4.0," that contains updated Windows for Workgroups files (NET.EXE, WORKGRP.SYS, VREDIR.386, and VBROWSE.386) and information about using these files with a Novell NetWare version 4.0 client configuration. You can obtain this Application Note from the following sources: - CompuServe, GEnie, and Microsoft OnLine - Microsoft Download Service (MSDL) - The Internet (Microsoft anonymous ftp server) - Microsoft Product Support Services For complete information, see the "To Obtain This Application Note" section at the end of this article. THE TEXT OF WG0904 ================== ---------------------------------------------------------------- ---- ========================================================= ============= Microsoft(R) Product Support Services Application Note (Text File) WG0904: SUPPORT FOR NOVELL(R) NETWARE(R) 4.0 ================================================================= ===== Revision Date: 9/93 1 Disk Included The following information applies to Microsoft Windows(TM) for Workgroups, version 3.1. ---------------------------------------------------------------- ------ | INFORMATION PROVIDED IN THIS DOCUMENT AND ANY SOFTWARE THAT MAY | | ACCOMPANY THIS DOCUMENT (collectively referred to as an Application| | Note) IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER | | EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE IMPLIED | | WARRANTIES OF MERCHANTABILITY AND/OR FITNESS FOR A PARTICULAR | | PURPOSE. The user assumes the entire risk as to the accuracy and | | the use of this Application Note. This Application Note may be | | copied and distributed subject to the following conditions: 1) All| | text must be copied without modification and all pages must be | | included; 2) If software is included, all files on the disk(s) | | must be copied without modification (the MS-DOS utility diskcopy is| | appropriate for this purpose); 3) All components of this | | Application Note must be distributed together; and 4) This | | Application Note may not be distributed for profit. | | | | Copyright (C) 1993 Microsoft Corporation. All Rights Reserved | | Microsoft and MS-DOS are registered trademarks and Windows is a | | trademark of Microsoft Corporation. | | CompuServe is a registered trademark of CompuServe, Inc. | | NetWare and Novell are registered trademarks of Novell, Inc. | ----------------------------------------------------------------- ----- Introduction ------------ This Application Note contains updated Windows for Workgroups files (NET.EXE, WORKGRP.SYS, VREDIR.386, and VBROWSE.386) and information about using these files with a Novell NetWare version 4.0 client configuration. Providing Windows for Workgroups support for NetWare 4.0 first requires proper installation of Novell's client software. If the setup steps described in this document do not function properly, contact Novell for more information. Microsoft can ensure connectivity between Windows for Workgroups and Novell NetWare only when you are running MSIPX.COM. If you cannot enable the open data-link interface (ODI) drivers using Novell's procedure (included with NetWare 4.0), call Novell Technical Support at (800) 638-9273. Although the current specification of Windows for Workgroups is MSIPX, an exclusively NDIS-compliant protocol, Novell's ODINSUP.COM, allows NDIS protocol stacks to run unmodified over the ODI link support layer (LSL) and talk to an ODI LAN driver. Novell's LSL can be accessed by using the ODINSUP driver. Microsoft recommends using ODINSUP.COM version 1.22 with this Application Note. Novell makes this file available on its bulletin board service and in the Novell CompuServe(R) forum. The current filename is DOSUP7.ZIP. For more availability information, contact Novell or look on the Novell CompuServe forum. When you use ODINSUP.COM with Windows for Workgroups and NetWare 4.0, the following configuration files are modified: CONFIG.SYS STARTNET.BAT or AUTOEXEC.BAT NET.CFG PROTOCOL.INI SYSTEM.INI Before You Begin ---------------- Since this configuration requires the Novell IPXODI drivers, set up your machines and connect to a Novell server from an MS-DOS command prompt using IPXODI.COM before proceeding with the setup instructions below. Be sure to back up your files so that you can restore your original configuration if necessary. Setup Instructions ------------------ 1. Install Windows for Workgroups with your network interface card (NIC) and with Novell NetWare as a secondary network. 2. Run the Novell NetWare 4.0 client installation program. 3. Edit the CONFIG.SYS file and remove or remark out (using the REM command) the following lines device=c:\windows\ device=c:\windows\msipx.sys where is the name of your NDIS network card driver. If you already have ODI connections, these entries are not present. NOTE: The NetWare 4.0 installation program changes the LASTDRIVE= statement from drive P to drive Z. Leave this change intact. 4. By default, the NetWare 4.0 installation program creates a STARTNET.BAT file (from which the NetWare files are run) in the NWCLIENT subdirectory. You need to edit this file unless the NetWare drivers are to be loaded from the AUTOEXEC.BAT file (in which case, you need to make the same changes in the AUTOEXEC.BAT file). If these drivers are loading from the AUTOEXEC.BAT file, remove the @CALL STARTNET.BAT line, which the NetWare installation procedure inserts. When you are finished editing the STARTNET.BAT or AUTOEXEC.BAT file, it should read as follows: Lines Comments ---------------------------------------------------------------- ----- SET NWLANGUAGE=ENGLISH This is new under 4.0. LSL ODI MAC driver for your NIC For example, this line would read NE2000 if you have an Novell NE2000 NIC. ODINSUP.COM Manually add this driver from the DOSUP7.ZIP file. C:\WINDOWS\NET START NETBIND Make sure this line is in either your AUTOEXEC.BAT or STARTNET.BAT, depending on which one is used to start NetWare connectivity. IPXODI VLM.EXE This file replaces NETX.EXE in NetWare 4.0. 5. In the AUTOEXEC.BAT file, remove or remark out the following lines: c:\windows\net start c:\windows\msipx.com IMPORTANT: Steps 6 and 7 provide the changes made in the NET.CFG and PROTOCOL.INI files if you are using a Novell NE2000 NIC. If you are using a different card, many of the changes made will be specific to your NIC and therefore different than those below. 6. To use ODINSUP.COM with Windows for Workgroups 3.1, the NET.CFG file should appear as follows. Some of the settings below appear as a result of the NetWare 4.0 installation program; you may need to manually edit others. NOTE: If you were using ODINSUP.COM with NetWare 3.11, the 4.0 installation removes the changes that were made to the NET.CFG file. The final file should read as follows: Lines Comments ---------------------------------------------------------------- ----- PB BUFFERS 7 This line is added. PROTOCOL ODINSUP This line exists if ODI is installed before you begin this procedure. BIND NE2000 If you are using a NIC other than the NE2000, a different MAC driver appears here. BUFFERED Link Driver NE2000 This line varies depending on the NIC you are using. Port This line is set to the I/O base being used. INT This line is set to the IRQ being used. Both the Port and INT settings assume that the defaults are not being used. If the defaults are being used, these lines do not appear. MEM This line appears only if your NIC is memory address configurable. Frame Ethernet_802.2 These frame types are required. Frame Ethernet_802.3 Frame Ethernet_II Frame Ethernet_SNAP Protocol IPX 0 Ethernet_802.3 NetWare DOS Requester First Network Drive = F This setting is new with NetWare 4.0 and is the reason LASTDRIVE no longer needs to be set to P. 7. To use ODINSUP.COM with Windows for Workgroups 3.1, the PROTOCOL.INI file should appear as follows. Some of the settings below appear as a result of the NetWare 4.0 installation program; you may need to manually edit others. IMPORTANT: If you were using ODI with Windows for Workgroups before upgrading Novell NetWare to 4.0, this file does not require editing. NOTE: To determine the correct MLID name, type the ODI NIC driver name at an MS-DOS command prompt. Lines Comments ---------------------------------------------------------------- ----- [network.setup] version=0x3100 netcard=NE2000,1,NE2000 Use the MLID name for this entry. transport=ms$netbeui,MS$NETBEUI transport=IPX,IPX lana0=NE2000,1,ipx Use the MLID name for this entry. lana1=NE2000,1,ms$netbeui Use the MLID name for this entry. [protman] DriverName=PROTMAN$ PRIORITY=MS$NETBEUI [MS$NETBEUI] DriverName=netbeui$ SESSIONS=10 NCBS=32 BINDINGS=NE2000 Use the MLID name for this entry. LANABASE=1 [NE2000] Add this entire section or convert it from the MS$NE2000 section. DRIVERNAME=NE2000 Use the MLID name for this entry. IOBASE=0x300 This entry should match the IOBASE setting in the NET.CFG file. INTERRUPT=11 This entry should match the INTERRUPT setting in the NET.CFG file. [MS$NE2000] Remark out this entire section by placing a semicolon at the beginning of each line, including the section header. [MS$IPX] Remark out this entire section by placing a semicolon at the beginning of each line, including the section header. [IPX] Add this section. DRIVERNAME=IPX$ MediaType=Novell/Ethernet This section will vary depending on the transceiver type. BINDINGS=NE2000 Use the MLID name for this entry. 8. Make the following changes in the SYSTEM.INI file: In the [boot] section of the SYSTEM.INI file, the Novell NetWare 4.0 installation changes the line network.drv=wfwnet.drv to read: network.drv=netware.drv Simply change the NETWORK.DRV line so that it reads as follows: network.drv=wfwnet.drv NOTE: Do not change the SECONDNET.DRV=NETWARE.DRV setting. After you make these changes, update your Windows for Workgroups installation with the four files on the enclosed WG0904 disk: NET.EXE, WORKGRP.SYS, VREDIR.386, and VBROWSE.386. Copy NET.EXE and WORKGRP.SYS to the Windows directory. Copy VREDIR.386 and VBROWSE.386 to the Windows SYSTEM subdirectory. For example, if you insert the WG0904 disk in drive A and your Windows directory and Windows SYSTEM subdirectory are C:\WINDOWS and C:\WINDOWS\SYSTEM, respectively, type the following commands at an MS-DOS command prompt, pressing ENTER after each line: copy a:\net.exe c:\windows copy a:\workgrp.sys c:\windows copy a:\*.386 c:\windows\system 9. Reboot and restart Windows for Workgroups. For more information concerning ODINSUP.COM, call Novell Technical Support. ---------------------------------------------------------------- ---- TO OBTAIN THIS APPLICATION NOTE =============================== - On CompuServe, GEnie, and Microsoft OnLine, Application Notes are located in the Microsoft Software Library. You can find WG0904 in the Software Library by searching on the word WG0904, the Q number of this article, or S14298. WG0904 is a compressed, self-extracting file. After you download WG0904, run it to extract the file(s) it contains. - Application Notes are available by modem from the Microsoft Download Service (MSDL), which you can reach by calling (206) 936-6735. This service is available 24 hours a day, 7 days a week. The highest download speed available is 14,400 bits per second (bps) For more information about using the MSDL, call (800) 936-4200 and follow the prompts. To obtain WG0904, download WG0904.EXE. WG0904.EXE is a compressed, self-extracting file. After you download WG0904.EXE, run it to extract the file(s) it contains. - On the Internet, Application Notes are located on the Microsoft anonymous ftp server, which you can reach by typing "ftp ftp.microsoft.com" (without the quotation marks) at the ">" command prompt. - If you are unable to access the source(s) listed above, you can have this Application Note mailed to you by calling Microsoft Product Support Services Monday through Friday, 6:00 A.M. to 6:00 P.M. Pacific time at (206) 637-7098. If you are outside the United States, contact the Microsoft subsidiary for your area. To locate your subsidiary, call Microsoft International Sales Information Center at (206) 936-8661. KBCategory: kbnetwork kbfile kbappnote kbsetup kb3rdparty KBSubcategory: wfw wfwg Additional reference words: appnote 3.1 3.10 Using Novell's ODINSUP with VLM.EXE and WFWG 3.11 Article ID: Q107648 ---------------------------------------------------------------- ---- The information in this article applies to: - Microsoft Windows for Workgroups version 3.11 ---------------------------------------------------------------- ---- This article contains information about using Windows for Workgroups with third-party products or configurations that have not been tested and are not supported by Microsoft. If the steps or procedures described in this article do not function properly, use a supported configuration or contact the manufacturer of the third-party product for more information. SUMMARY ======= The Novell ODINSUP driver allows NDIS 2 protocols (such as MS TCP/IP) to run on top of Novell ODI drivers. This is similar to the behavior of the MSODISUP driver that comes with Windows for Workgroups 3.11. The difference is that the MSODISUP driver allows only NDIS 3 protocols to run on top of it. MORE INFORMATION ================ The following instructions assist you in setting up Windows for Workgroups 3.11 to run on the Novell ODINSUP driver with NetWare clients that are using Novell's VLM.EXE redirector. By doing this, you can use NDIS 2 protocols (such as MS TCP/IP and MS DLC) to run on top of the Novell ODI drivers. The steps below outline setting up Windows for Workgroups 3.11 with the MS TCP/IP, NetBEUI, and NWLink protocols in addition to Novell's real-mode IPX protocol. The network card used throughout this article is the 3COM1 3c509 Etherlink III. Before You Begin ---------------- You should run the Novell NetWare 4.0 client installation program and have a working NetWare 4.0 client. You should also set up a working NET.CFG file in the same directory from which you load LSL.COM. By default, NetWare 4.0 loads the network drivers in a STARTNET.BAT file and then "calls" this file from the AUTOEXEC.BAT file. Be sure to back up this file along with your AUTOEXEC.BAT file so that you can restore this configuration later if necessary. Setup Instructions ------------------ 1. Install Windows for Workgroups using the Custom Setup option. In the Network Setup dialog box, select the Other option button, select Novell, and then choose the Drivers button. Select the network card driver for your adapter along with both the NetBEUI and the "IPX/SPX Compatible Transport with NetBIOS" protocols. (For the examples in this article, we chose the Etherlink III network card.) Next, in the same Network Drivers dialog box, choose Setup and select Real Mode NDIS Driver. This is important because even though you are actually running on an ODI driver with ODINSUP, Windows for Workgroups thinks you are running an NDIS driver. Choose OK and continue with Setup. Ignore the error messages about ODI drivers. After you finish Setup, you reboot your computer and start Windows by using the /N switch (WIN /N), then install MS TCP/IP according to the directions that come with the package. NOTE: If there are any other NDIS 2 protocols (such as MS DLC) you want to install, install them now. Also, make sure that you choose which protocol you want to be the default protocol in the Network Drivers dialog box. 2. After completing MS TCP/IP setup, edit the SYSTEM.INI file and remove the NDIS 2 driver, , from the netcard= line of the [Network Drivers] section. NOTE: If you are using a different network card, the NDIS network card driver ( in the above example) will be different. 3. Edit the CONFIG.SYS file and set LASTDRIVE=Z. This allows you to connect all available drive letters to both NetWare and Windows for Workgroups servers. 4. If you are using a STARTNET.BAT file, remove the NET START line from the AUTOEXEC.BAT file and then edit the STARTNET.BAT file so that it contains the following network-related lines. If you are not using a STARTNET.BAT file, put these lines in your AUTOEXEC.BAT file. SET NWLANGUAGE=ENGLISH C:\WINDOWS\NET INIT (This loads protman and NDIS protocols.) C:\\LSL.COM C:\\.COM C:\\ODINSUP.COM C:\WINDOWS\NET START NETBIND (This binds the protocols to ODINSUP.) C:\\IPXODI.COM C:\\VLM.EXE (The rest of these files are for MS TCP/IP.) C:\WINDOWS\UMB C:\WINDOWS\TCPTSR C:\WINDOWS\TINYRFC C:\WINDOWS\NMTSR.EXE C:\WINDOWS\EMSBFR.EXE 5. Edit the NET.CFG file and verify that it contains the following lines. If these lines don't exist, add them to the appropriate sections of the NET.CFG file. If you do not have a NET.CFG file, create one using a text editor (such as Microsoft Windows Notepad), and save it in the directory from which LSL.COM is executed. Note that some of the lines in the NET.CFG file are indented; this indentation must be maintained. PB BUFFERS 7 PROTOCOL ODINSUP BIND <3c509> (where <3c509> is the filename of your network card's ODI driver) BUFFERED LINK DRIVER <3c509> (where <3c509> is the filename of your network card's ODI driver) INT (where is the one-digit interrupt number) MEM (where is the five-digit memory address) PORT (where is the three-digit I/O port address) FRAME ETHERNET_802.2 FRAME ETHERNET_802.3 FRAME ETHERNET_II FRAME ETHERNET_SNAP PROTOCOL IPX 0 ETHERNET_802.3 First Network Drive = F NOTE: If you've been using ODI to attach to a Novell server at DOS and you haven't specified the parameters INT, MEM, PORT, DMA, SLOT, and so forth in the NET.CFG file, you probably don't need to add them now. However, depending on the ODI MAC driver you are using (Novell refers to this as the "MLID"), you may need to place these parameters after the FRAME lines. Additionally, list your network's frame type FIRST in the list of "FRAME ETHERNET_" entries (where will probably be <802.2>, <802.3>, or ). 6. Edit the PROTOCOL.INI file by replacing the BINDINGS= lines in the [NWLINK], [NETBEUI], [MS$NDISHLP], and [TCPIP] sections with the Novell ODI MAC driver (MLID) as follows: [NWLINK] ;BINDINGS= (where corresponds to your NDIS MAC driver; in this case, ELINK3.DOS. The semicolon comments out this line.) BINDINGS= (where corresponds to your ODI MLID; in this case, 3c509.COM. The "x" must be added if the ODI MLID filename begins with a numeral.) [NETBEUI] ;BINDINGS= (where corresponds to your NDIS MAC driver; in this case, ELINK3.DOS. The semicolon comments out this line.) BINDINGS= (where corresponds to your ODI MLID; in this case, 3c509.COM. The "x" must be added if the ODI MLID filename begins with a numeral.) LANABASE=0 SESSIONS=10 NCBS=12 DriverName=netbeui$ [MS$NDISHLP] DriverName=ndishlp$ ;BINDINGS= (where corresponds to your NDIS MAC driver; in this case, ELINK3.DOS. The semicolon comments out this line.) BINDINGS= (where corresponds to your ODI MLID; in this case, 3c509.COM. The "x" must be added if the ODI MLID filename begins with a numeral.) [TCPIP] IPAddress0=<130 25 40 20> (where <130 25 40 20> corresponds to your own IP addresses.) DefaultGateway0=130 25 0 1 SubNetMask0=255 255 0 0 NBSessions=6 NetFiles=C:\WINDOWS DriverName=TCPIP$ ;BINDINGS= (where corresponds to your NDIS MAC driver; in this case, ELINK3.DOS. The semicolon comments out this line.) BINDINGS= (where corresponds to your ODI MLID; in this case, 3c509.COM. The "x" must be added if the ODI MLID filename begins with a numeral.) LANABASE=2 IMPORTANT: If the ODI MLID filename begins with a numeral, you must preface the filename with an "x" (without the quotation marks) in the BINDINGS= statement. For example, the 3COM 3C509 network adapter card uses an ODI MLID with the filename 3C509.COM. In the PROTOCOL.INI file, the BINDINGS= statements would need to be: BINDINGS=x3C509 WARNING: After you make these modifications, do NOT make any changes in the Networks dialog box of Control Panel. If you do, the AUTOEXEC.BAT, SYSTEM.INI and PROTOCOL.INI files will be overwritten. You should make backup copies of these files in case this occurs. EXAMPLES ======== Below are samples of what modified CONFIG.SYS, AUTOEXEC.BAT, NET.CFG, and PROTOCOL.INI files look like if you are using Novell's ODINSUP with Windows for Workgroups 3.11 Setup with the MS TCP/IP, NetBEUI, and "IPX/SPX Compatible Transport with NetBIOS" protocols. CONFIG.SYS ---------- DEVICE=C:\WINDOWS\HIMEM.SYS DOS=HIGH BUFFERS=30 FILES=50 DEVICE=C:\DOS\SETVER.EXE SHELL=C:\DOS\COMMAND.COM C:\DOS\ /p /e:2048 STACKS=9,256 LASTDRIVE=Z DOS=HIGH DEVICE=C:\WINDOWS\IFSHLP.SYS AUTOEXEC.BAT ------------ C:\WINDOWS\NET INIT C:\NOVELL\LSL C:\NOVELL\3C509 C:\NOVELL\ODINSUP C:\WINDOWS\NET START NETBIND C:\NOVELL\IPXODI C:\NOVELL\VLM C:\WINDOWS\UMB C:\WINDOWS\TCPTSR C:\WINDOWS\TINYRFC C:\WINDOWS\NMTSR.EXE C:\WINDOWS\EMSBFR.EXE PATH=C:\WINDOWS;C:\DOS;C:\ SET TEMP=C:\TEMP C:\WINDOWS\SMARTDRV.EXE /X NET.CFG ------- SHOWDOTS=ON PB BUFFERS 7 PROTOCOL ODINSUP BIND 3c509 BUFFERED LINK DRIVER 3c509 port 300 int 5 frame ethernet_802.3 frame ethernet_802.2 frame ethernet_II frame ethernet_SNAP PROTOCOL IPX 0 ETHERNET_802.3 First Network Drive = F PROTOCOL.INI ------------ [network.setup] version=0x3110 netcard=ms$elnk3,1,MS$ELNK3,1 transport=ms$nwlinknb,NWLINK transport=ms$netbeui,NETBEUI transport=ms$ndishlp,MS$NDISHLP transport=tcpip,TCPIP lana0=ms$elnk3,1,ms$netbeui lana1=ms$elnk3,1,ms$nwlinknb lana2=ms$elnk3,1,ms$ndishlp lana3=ms$elnk3,1,tcpip [MS$ELNK3] DriverName=ELNK3$ MAXTRANSMITS=6 [NWLINK] BINDINGS=x3C509 [NETBEUI] BINDINGS=x3C509 LANABASE=0 SESSIONS=10 NCBS=12 DriverName=netbeui$ [protman] DriverName=PROTMAN$ PRIORITY=MS$NDISHLP [MS$NDISHLP] DriverName=ndishlp$ BINDINGS=x3C509 [TCPIP] DefaultGateway0=130 25 0 1 SubNetMask0=255 255 0 0 IPAddress0=130 25 40 20 NBSessions=6 NetFiles=C:\WINDOWS DriverName=TCPIP$ BINDINGS=x3C509 LANABASE=2 For additional information concerning Novell's ODINSUP.COM, contact Novell Technical Support or on the Novell CompuServe forums. The Novell products included here are manufactured by a vendor independent of Microsoft; we make no warranty, implied or otherwise, regarding these products' performance or reliability. KBCategory: kbnetwork kb3rdparty kbusage kbtlc KBSubcategory: wfw wfwg Additional reference words: 3.11 3rdparty EMM Exception Error #6 Exiting Windows for Workgroups 3.11 Article ID: Q107978 ---------------------------------------------------------------- ----- The information in this article applies to: - Microsoft Windows for Workgroups version 3.11 ---------------------------------------------------------------- ----- SYMPTOMS ======== When you exit Windows for Workgroups version 3.11, your system may stop responding (hang). If EMM386.EXE is loaded, you may receive the following error message: EMM Exception Error #6 CAUSE ===== This problem occurs because: - The processor is trying to decode a bit pattern that does not correspond to any legal machine instruction. -or- - The processor is trying to execute an instruction that contains invalid operands. Both of these causes mean that the processor (CPU) is trying to execute code from an incorrect area in memory. Either an application is passing an invalid jump instruction (causing a jump to an incorrect memory location) or the jump instruction is correct but the memory that the instruction accesses is corrupted. NOTE: Although you receive an EMM exception error, EMM386.EXE is not causing the problem. When the processor encounters a problem executing an instruction, it looks for an error handler. When you exit Windows for Workgroups it uses the default error handler. If EMM386.EXE is installed, you receive the EMM Exception Error. If EMM386.EXE is not installed, the machine may stop responding (hang). WORKAROUND ========== To troubleshoot this problem, follow the steps in this procedure. After each step, you should reboot your computer, run Windows for Workgroups, and then attempt to successfully exit Windows for Workgroups. When Windows for Workgroups exits successfully, you have isolated the problem. 1. If you ran MS-DOS 6 or 6.2 MemMaker before installing Windows for Workgroups, run MemMaker again. 2. Eliminate potential software conflicts as follows: a. Remove any third-party device drivers and terminate-and-stay-resident (TSR) programs that are not required to access your hard drive from your CONFIG.SYS and AUTOEXEC.BAT files. For moreinformation on device drivers the should not be remarked out, query on the following words in the Microsoft Knowledge Base: wfw clean boot b. Ensure that the Windows for Workgroups StartUp group is empty. c. Ensure that no screen savers, including built-in Windows screen savers, are running. In the Control Panel, choose the Desktop icon and verify that the Screen Saver Name list box is empty. d. Ensure that Windows is not being run from a menu program, such as MS-DOS Shell. e. Edit the WIN.INI file and comment out the LOAD= and RUN= lines (unless they are already blank). To comment out these lines, place a semicolon (;) in front of the line. For example: ;load= f. Edit the SYSTEM.INI file and comment out any third-party virtual device drivers (VxDs). g. If possible, disable NDIS2 protocols like TCP or DLC. 3. Eliminate potential hardware conflicts: a. Turn off hardware caching. b. Turn off shadow ram and video memory. 4. Edit the CONFIG.SYS file and exclude A000-F7FF to eliminate potential upper memory area (UMA) conflicts. To do this, add "X=A000-F7FF" to the DEVICE command for EMM386.EXE in the CONFIG.SYS file. 5. Remark out the device command for EMM386.EXE in the CONFIG.SYS file and then run Windows for Workgroups with the "/D:X" parameter. For example, type "win /d:x" (without the quotation marks) at the MS-DOS command prompt and then press ENTER. 6. Start Windows for Workgroups with the WIN /N command. This loads Windows for Workgroups without loading any network support. If the problem does not occur without network software loaded, a hardware device may be conflicting with your network card. If Windows for Workgroups still hangs when you exit, you still have a memory conflict; however, it is not in the upper memory area (UMA). KBCategory: kbother kbdisplay kberrmsg KBSubcategory: wfwg Additional reference words: 3.11 err msg errors Pentium-Based Machine Hangs with Communication Applications Article ID: Q110568 ---------------------------------------------------------------- ----- The information in this article applies to: - Microsoft Windows operating system versions 3.1, 3.11 - Microsoft Windows for Workgroups versions 3.1, 3.11 ---------------------------------------------------------------- ----- SYMPTOMS ======== Pentium-based machines with a peripheral component interface (PCI) bus and a 16550 UART chip stop responding (hang) or exhibit other unexpected behavior when you use communication applications, such as Microsoft At Work PC Fax or Microsoft Terminal. In some cases, you may be able to run the software successfully once but then experience problems when you try to run it a second time (before Windows is restarted). CAUSE ===== The PCI bus uses a new universal asynchronous receiver transmitter (UART) chip that identifies itself as a 16550 chip but does not handle the 16-bit buffer the same way that the 16550 UART chip does. These problems occur if there is data in the chip when the serial communications application attempts to open the communications port. A problem with the chip implementation causes the chip to become trapped in a mode in which data is always detected in its FIFO buffer. RESOLUTION ========== To correct this problem under Windows for Workgroups 3.11, obtain the updated SERIAL.386 file included with PSS Application Note WG1001: Updated SERIAL.386 Driver for Windows for Workgroups. For more information about WG1001, query on the following words in the Microsoft Knowledge Base: wg1001 and appnote The products included here are manufactured by vendors independent of Microsoft; we make no warranty, implied or otherwise, regarding these products' performance or reliability. KBCategory: kbhw kbfile kbappnote kb3rdparty KBSubcategory: win31 wfw wfwg ras awfax Additional reference words: appnote 3.11 3.10 3.1 gateway2000 exit restarted gateway Dell XPS AMI motherboard kit machine built-in com comm port ports NEC Image 466ES PCs print Remote Access Services RAS ErrMsg: NETBIOS Error 640: A Netbios Error Has Occurred... Article ID: Q111094 ---------------------------------------------------------------- ----- The information in this article applies to: - Microsoft Windows for Workgroups version 3.11 ---------------------------------------------------------------- ----- SYMPTOMS ======== When you dial in from Windows for Workgroups 3.11 Remote Access Services (RAS) client to a RAS server, the following error message is displayed: NETBIOS error 640: a netbios error has occurred (with failed code 0x5) NOTE: This problem may occur with some modems and not with others. CAUSE ===== The "NETBIOS error 640" message can be caused by the following conditions: - The connection speed is too fast for the current line quality. - The correct modem has not been selected from the Configuration menu. - The cable being used does not support all the pinouts needed for RAS. - Your modem is not fully compatible with the Microsoft RAS compression. - You are loading PC Anywhere virtual device drivers (AW5VCD.386 and VPCAW5.386) from the [386Enh] section of your SYSTEM.INI file. Comment out these drivers and add DEVICE=*VCD to the same section of the SYSTEM.INI file. - You logged on to the domain you are trying to connect to before connecting with RAS. - Microsoft LAN Manager OS/2 RAS server has NetBiosRetries set too high. - The Windows NT server is low on available memory. - There is an incompatibility with your third-party video driver. RESOLUTION ========== If you receive the "NETBIOS error 640" message several seconds after connecting to the RAS server, use the following procedure to determine what is causing the error. After each step, try to establish a RAS connection. 1. Choose Setup and ensure RAS is configured for the correct modem. 2. Make sure you are using the correct cabling. For more information, run RAS and check online Help. 3. Make sure you are not logged on to the domain you are trying to connect to before connecting with RAS. 4. Make sure you are not using a 9-to-25-pin converter that was supplied with a mouse. Many 9-to-25-pin converters supplied with mouse hardware do not carry modem signals. 5. Disable hardware flow control and lower the connection speed as follows: a. Edit the RAS phone book and select Modem from the Advanced options. b. Clear the Enable Hardware Flow Control check box. c. Change the connection speed to the lowest setting. If the connection is successful, try increasing the connection speed until the maximum throughput of the line is found. 6. If RAS software compression is enabled, disable it. 7. Try using the standard Windows for Workgroups VGA video driver. 8. If you are trying to connect to a Microsoft LAN Manager OS/2 RAS server, make sure NetBiosRetries is not set too high. For example, some Microsoft customers have reported this problem when NetBiosRetries is set to 6. To correct this problem, lower the LAN Manager server NetBiosRetries value in the [NetBEUI] section of the PROTOCOL.INI file. 9. If you are trying to connect to a Microsoft Windows NT server, make as much memory available as possible on the server. KBCategory: kbnetwork kbdisplay kberrmsg KBSubcategory: wfw wfwg ras Additional reference words: 3.11 err msg errmsg vxd vxds 4 8 WG1004: MSODISUP.386 Fixes Problems Using 3Com ODI MLIDs Article ID: Q112161 ---------------------------------------------------------------- ----- The information in this article applies to: - Microsoft Windows for Workgroups version 3.11 ---------------------------------------------------------------- ----- Microsoft has an Application Note titled "WG1004: Updated MSODISUP File Corrects Problems Using 3Com 3c509 and 3c5x9 ODI MLIDs," which corrects system hangs and lost network connection problems that can occur if you are using a 3Com ODI MLID with Windows for Workgroups and the EtherLink III network interface card (NIC). You can obtain this Application Note from the following sources: - CompuServe, GEnie, and Microsoft OnLine - Microsoft Download Service (MSDL) - The Internet (Microsoft anonymous ftp server) - Microsoft FastTips Technical Library - Microsoft Product Support Services For complete information, see the "To Obtain This Application Note" section at the end of this article. THE TEXT OF WG1004 ------------------ ================================================================ ====== Microsoft(R) Product Support Services Application Note (Text File) WG1004: UPDATED MSODISUP FILE CORRECTS PROBLEMS USING 3COM(R) 3C509 AND 3C5X9 ODI MLIDS ================================================================ ====== Revision Date: 3/94 1 Disk Included The following information applies to Microsoft Windows(TM) for Workgroups, version 3.11. ---------------------------------------------------------------- ------- | INFORMATION PROVIDED IN THIS DOCUMENT AND ANY SOFTWARE THAT MAY | | ACCOMPANY THIS DOCUMENT (collectively referred to as an Application | | Note) IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER | | EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE IMPLIED | | WARRANTIES OF MERCHANTABILITY AND/OR FITNESS FOR A PARTICULAR | | PURPOSE. The user assumes the entire risk as to the accuracy and | | the use of this Application Note. This Application Note may be | | copied and distributed subject to the following conditions: 1) All | | text must be copied without modification and all pages must be | | included; 2) If software is included, all files on the disk(s) | | must be copied without modification (the MS-DOS(R) utility | | diskcopy is appropriate for this purpose); 3) All components of | | this Application Note must be distributed together; and 4) This | | Application Note may not be distributed for profit. | | | | Copyright (C) 1994 Microsoft Corporation. All Rights Reserved. | | Microsoft and MS-DOS are registered trademarks and Windows is a | | trademark of Microsoft Corporation. | | 3Com and EtherLink are registered trademarks of 3Com Corporation. | | NetWare and Novell are registered trademarks of Novell, Inc. | ----------------------------------------------------------------- ------ Introduction ------------ If you use the 3Com EtherLink(R) III (3c509) network interface card (NIC) and a 3Com ODI MLID (3C509.COM or 3C5X9.COM) with Windows for Workgroups version 3.11 and Novell(R) NetWare(R) is installed as your secondary network, your system may: - Stop responding (hang) when you copy large files across the network. -or- - Inadvertently lose network connections. The WG1004 disk included with this Application Note contains an updated MSODISUP.386 file that corrects both of these problems. The updated file correctly adjusts the counter for the number of outstanding packets to be copied off the NIC after the MLID fails to copy an incoming packet off the NIC. The updated file allows you to successfully use multiple 3Com NICs with Windows for Workgroups. The updated file ensures that all adapter names are available for binding when multiple ODI drivers are loaded. For example, you can now have the 3c503 and 3c509 drivers loaded so that you can run two NICs on separate networks or send one protocol to one NIC and a different protocol to another NIC. NOTE: Although you can use multiple different NICs, you cannot use more than one of the same NIC. For example, you can use a 3c503 NIC and a 3c509 NIC, but you cannot use two 3c503 NICs. The WG1004 disk included with this Application Note contains an updated NETWORK.INF file that corrects binding entry errors with the 3Com EtherLink III 3c5x9 driver. The updated NETWORK.INF uses MLID=*:3C5X9.COM instead of MLID=*:3C509.COM. To install the updated files ---------------------------- 1. Quit Windows for Workgroups. 2. Make a backup copy of the currently installed MSODISUP.386 file by typing the following at the MS-DOS command prompt and then pressing ENTER ren :\msodisup.386 msodisup.old where : is the location of your Windows SYSTEM subdirectory. For example, if your Windows directory is called WINDOWS and is on drive C, type the following at the MS-DOS command prompt and then press ENTER: ren c:\windows\system\msodisup.386 msodisup.old 3. Repeat step 2, but substitute NETWORK.INF for MSODISUP.386 and NETWORK.OLD for MSODISUP.OLD. For example, if your Windows directory is called WINDOWS and is on drive C, type the following at the MS-DOS command prompt and then press ENTER: ren c:\windows\system\network.inf network.old 4. Insert the enclosed WG1004 disk in the appropriate floppy disk drive. 5. To copy the MSODISUP.386 and NETWORK.INF files to the Windows SYSTEM subdirectory, type the following at the MS-DOS command prompt and then press ENTER copy :*.* where is the floppy disk drive containing the WG1004 disk and is the drive and directory of your Windows SYSTEM subdirectory. For example, if the WG1004 disk is in drive A and your Windows directory is called WINDOWS and is on drive C, type the following at the MS-DOS command prompt and then press ENTER: copy a:*.* c:\windows\system ---------------------------------------------------------------- -------- TO OBTAIN THIS APPLICATION NOTE =============================== - On CompuServe, GEnie, and Microsoft OnLine, Application Notes are located in the Microsoft Software Library. You can find WG1004 in the Software Library by searching on the word WG1004, the Q number of this article, or S14593. WG1004 is a compressed, self-extracting file. After you download WG1004, run it to extract the file(s) it contains. - Application Notes are available by modem from the Microsoft Download Service (MSDL), which you can reach by calling (206) 936-6735. This service is available 24 hours a day, 7 days a week. The highest download speed available is 14,400 bits per second (bps). For more information about using the MSDL, call (800) 936-4200 and follow the prompts. To obtain WG1004, download WG1004.EXE. WG1004.EXE is a compressed, self-extracting file. After you download WG1004.EXE, run it to extract the file(s) it contains. - On the Internet, Application Notes are located on the Microsoft anonymous ftp server, which you can reach by typing "ftp ftp.microsoft.com" (without the quotation marks) at the ">" command prompt. You can find WG1004.EXE in the SOFTLIB\MSLFILES directory. - You can have this Application Note mailed to you from the automated Microsoft FastTips Technical Library, which you can call 24 hours a day, 7 days a week at (800) 936-4200. NOTE: The FastTips Technical Library is available only to customers within the U.S. and Canada. - If you are unable to access the source(s) listed above, you can have this Application Note mailed to you by calling Microsoft Product Support Services Monday through Friday, 6:00 A.M. to 6:00 P.M. Pacific time at (206) 637-7098. If you are outside the United States, contact the Microsoft subsidiary for your area. To locate your subsidiary, call Microsoft International Sales Information Center at (206) 936-8661. KBCategory: kbnetwork kb3rdparty kbfile kbappnote KBSubcategory: Additional reference words: appnote 3.11 wfwg wfw Err Msg Starting WFWG: Cannot Find NWGDI.DLL Article ID: Q112294 ---------------------------------------------------------------- ----- The information in this article applies to: - Microsoft Windows for Workgroups version 3.11 ---------------------------------------------------------------- ----- SYMPTOMS ======== When you are using Novell files from WINUP9.EXE and you start Windows for Workgroups version 3.11, you receive the following error message: Cannot Find NWGDI.DLL -or- NWDRV-3.00-00: The NetWare VLM is not loaded or is not configured correctly. All network functions are disabled. CAUSE ===== This error is displayed if one of the following conditions exists: - You are using NETWARE.DRV and are running virtual loadable modules (VLMs). - You allow Windows for Workgroups 3.11 Setup to add the files from WINUP9.EXE, or you are using the NetWare VLM Client Kit 1.02 to install the files from WINUP9.EXE. Neither Windows for Workgroups Setup nor the NetWare VLM Client Kit 1.02 copy the new file (NWGDI.DLL) to the Windows SYSTEM subdirectory. You must have NWGDI.DLL to run the new NETWARE.DRV with VLMs. - NETWARE.DRV is incorrectly installed for use with VLM.EXE. If this is the case, you need to reinstall NETWARE.DRV for use with NETX.EXE. - You are running an IPXODI or a monolithic IPX configuration and have the VLM NETWARE.DRV or VLM NETWARE.HLP file in your Windows SYSTEM subdirectory. RESOLUTION ========== If you are using NetWare VLM.EXE client software, copy NETWARE.DRV and NWGDI.DLL from the VLMDRVS directory, which is created when you expand WINUP9.EXE to your Windows SYSTEM subdirectory. The dates and file sizes are as follows: Configuration Filename File size File date ----------------------------------------------------------------- ---- VLM configurations NETWARE.DRV 146,736 11-24-93 NWGDI.DLL 81,792 11-19-93 NOTE: The above information does not apply if you are using NETX.EXE. MORE INFORMATION ================ For additional information, please see the following article(s) in the Microsoft Knowledge Base: Article-ID: Q121462 Title : Obtaining Latest Novell Client Windows Drivers and DLLs KBCategory: kbnetwork kb3rdparty kberrmsg KBSubcategory: wfw wfwg Additional reference words: Application Error: Call to Undefined Dynalink 3rdparty err msg 3.11 Problems Sending Mail After Installing AWFAX Article ID: Q112612 -------------------------------------------------------------------- The information in this article applies to: - Microsoft Windows for Workgroups version 3.11 ---------------------------------------------------------------- ---- SYMPTOMS ======== After you install Microsoft At Work PC Fax, you may no longer be able to send mail to users sharing the same post office. When you send a message to a member of the post office, the message returns with an "Undeliverable Mail" error message. The text of the mail message reads "The message recipient was invalid." -or- The PostOffice List icon in the Address Book may be unavailable in Microsoft Mail. -or- The Open Other's Appt. Book option may be unavailable in Microsoft Schedule+. CAUSE ===== If Microsoft Mail was installed with Microsoft Windows for Workgroups version 3.1 and you choose to install Microsoft At Work PC Fax for "Fax Only" rather than "Email And Fax" in Windows for Workgroups 3.11, the MSMAIL.INI file is not properly updated. RESOLUTION ========== If Microsoft Mail was not installed before you started At Work PC Fax, make the following changes: 1. Rename the following files: MSMAIL.INI EFAXPUMP.INI SCHDPLUS.INI. 2. Choose the Fax icon in Control Panel. 3. Select the Email And Fax option and choose OK. 4. Select the appropriate settings for your fax board. 5. Install Microsoft Mail. If Microsoft Mail was installed prior to starting At Work PC Fax, do the following: 1. Remove the [Providers] section of the MSMAIL.INI file. 2. Rename the EFAXPUMP.INI file. NOTE: If you are receiving the following error message when starting Microsoft Schedule+ Your schedule transport DLL does not support the current transport. You will only be able to work off-line. PCMail users are supported. also perform the following step: a. In the SCHDPLUS.INI file, remove the following statement: ScheduleTransport=TRNOFF NOTE: The "ScheduleTransport=TRNOFF" entry in the SCHPLUS.INI file causes the "This account is for a resource" check box in the Schedule Plus Options dialog box to be unavailable. -or- Rename the SCHDPLUS.INI file. 3. Choose the Fax icon in Control Panel. 4. Select the Email And Fax option and choose OK. 5. Select the appropriate settings for your fax board. KBCategory: kbnetwork kbtool kbatwork kberrmsg KBSubcategory: wfw wfwg awfax Additional reference words: 3.11 fax missing postoffice computer efax grey gray greyed grayed out address book "Your schedule transport does not support the current" Common Questions and Answers for Windows 3.11 Article ID: Q114301 ---------------------------------------------------------------- ----- The information in this article applies to: - Microsoft Windows operating system version 3.11 ---------------------------------------------------------------- ----- SUMMARY ======= This article contains common questions and answers regarding the differences between Windows 3.1 and Windows 3.11. The answers cover why Microsoft released Windows 3.11, who can benefit from it, what files changed, and issues with OS/2 for Windows. This article is a reprint of the Windows 3.11 Q&A document written by Product Management and made available on the online services. This article is reproduced in the Knowledge Base for reference only. MORE INFORMATION ================ 1. What is Windows 3.11? How is it different from Windows 3.1? Microsoft Windows 3.11 is a "refresh" release that implements packaging changes designed to reduce counterfeiting. The release also includes some updated device drivers and a few bug fixes to address issues such as diskless workstation support. 2. Why were these changes made? It's been nearly two years since Windows 3.1 was introduced to the market. These new drivers and bug fixes will improve the experience of a customer buying Windows for the first time. Also, these changes had already been incorporated in our Windows for Workgroups 3.11 release. 3. Who should update to Windows 3.11? There is no new functionality in the 3.11 release of Windows and all of the drivers being added or refreshed have been available on the Windows Driver Library up on CompuServe and Microsoft's Download Service. So unless a customer is having a problem related to one of the areas covered by the fixes detailed below, there should be no need for them to update to this release. If a customer does need to update they should call Microsoft at (800) 871-3270 for more information. 4. What is the difference between Windows 3.11 and Windows for Workgroups 3.11. Windows 3.11: Windows 3.11 is simply Windows 3.1 plus the additional video and printer drivers and the five bug fixes described below. As mentioned above, there is no new functionality or performance improvements, features, etc. Windows for Workgroups 3.11: WFW 3.11 offers a number of enhancements to our Windows 3.1 product. WFW 3.11 includes enhanced performance, from 50-150% faster disk I/O and up to 100% faster network access. It also includes integrated networking, Microsoft Mail, Microsoft Schedule+, Microsoft At Work PC Fax, and Microsoft's Remote Access Services, and a number of other enhancements for both standalone and networked Windows PCs. 5. Does Win 3.11 work with OS/2 for Windows? No it does not. From what we have been able to learn without the benefit of source code, which IBM refused to provide Microsoft, OS/2 for Windows patches Windows in memory at fixed address locations. Such a design makes OS/2 for Windows extremely fragile because it depends on Windows code being frozen over time. Microsoft encourages developers to write well-behaved Windows applications using documented application program interface (API) functions and good programming practices. By establishing these ground rules we can move the platform forward and maintain support for these applications. Windows 3.11 did not break any well-behaved applications that we are aware of. Though we regret the inconvenience to customers, IBM has to be responsible for writing well-behaved applications -- they have taken shortcuts with OS/2 for Windows that have put their customers in a bad position. We presume that one or more of the bug fixes incorporated in Windows 3.11 (which were included in Windows for Workgroups 3.11 released November 6, 1993) changed the fixed address locations that are patched by OS/2 for Windows. As a result, OS/2 for Windows no longer runs correctly. 6. Did Microsoft do this to thwart IBM? No we did not. We have been talking publicly about this release since August of last year -- well before IBM even announced their OS/2 for Windows product. Negotiations with Novell and a desire not to interrupt the Christmas selling season caused us to delay, but Windows has been on the market for nearly two years now and we felt that customers would benefit from a refresh of the product. 7. What should customers do that have purchased OS/2 for Windows and want to update to Windows 3.11? IBM has the means at its disposal to permit purchasers of OS/2 for Windows to use it with Windows 3.11. First IBM can release a new version of OS/2 for Windows that patches Windows 3.11 at the appropriate address locations in memory. Second, IBM can provide customers with the KERNEL, USER, and GDI modules from Windows 3.1 that do not contain the bug fixes which apparently are the source of the problem. Alternatively customers can purchase the full OS/2 2.1 product from IBM. 8. What about customers who buy Windows 3.11 and then want to run OS/2 for Windows? We think IBM bears the responsibility for designing OS/2 for Windows in such a way that virtually guaranteed it would break if Microsoft made any changes in Windows. Nonetheless, in an effort to assist our mutual customers, Microsoft will provide purchasers of Windows 3.11 who experience difficulty running the product with OS/2 for Windows with the unimproved Windows 3.1 files which we modified in Windows 3.11 to fix various bugs. Our Product Support Services will distribute these as soon as a diskette can be made available. 9. What exactly are the code changes made to Win 3.11 and what do they do? First the following drivers have been added or refreshed in the Windows 3.11 release: - HPLJIV driver - 256 Color generic SVGA video driver - which will support TSENG ET4000 chip sets and V7, but not ATI Ultra or S3 chip sets. - As well as the following drivers: PSCRIPT.DRV UNIDRV.DLL PSCRIPT.HLP UNIDRV.HLP HPPCL5MS.DRV HPDSKJET.DRV HPPCL5E.DRV HPPCL.DRV HPPCL5E.HLP PAINTJET.DRV HPPCL5E1.DLL L100_425.WPD HPPCL5E2.DLL L300_471.WPD HPPCL5E3.DLL L300_493.WPD HPPCL5E4.DLL L500_493.WPD HPPCL5EO.DLL L200230&.WPD FINSTALL.DLL L330_52&.WPD FINSTALL.HLP L630_52&.WPD EPSON24.DRV EPSON9.DRV V7VDD.386 V7VGA.DRV In addition, the following 5 files were changed: - KRNL386.EXE: Minimal kernel changes to more gracefully shut down the Windows system after installing products which call the ExitWindows API to shut Windows down before returning focus to program manager. - GDI.EXE: Changes which assist ISVs currently writing graphics applications, especially those that call the 'draw rectangle function'. This will minimize the number of API calls the programmer needs to write and maximize the system resources available on the system when using graphics intensive applications. - COMMDLG.DLL: Changes which allow Windows applications on diskless workstations to use common dialog boxes. (Formerly available as a PSS application note). - PSCRIPT.DRV and UNIDRV.DLL: These files were updated to eliminate a font enumeration conflict that occurred with many word processors when 60 or more fonts are used in a single document. - VTDA.386: The updated VTDA.386 solves a very small percentage of timer- related problems that occur when starting an MS-DOS-based application under Windows on a Novell NetWare network. KBCategory: kbdisplay kb3rdparty kbnetwork kbfile kbappnote KBSubcategory: wfwg Additional reference words: appnote 3.11 awfax RAS WFWG Err Msg: WINFILE Caused a GP Fault at 0009:028A... Article ID: Q118323 ---------------------------------------------------------------- ---- The information in this article applies to: - Microsoft Windows for Workgroups version 3.11 ---------------------------------------------------------------- ---- SYMPTOMS ======== When you format a floppy disk in File Manager, you receive the following error message: WINFILE caused a General Protection fault in module WINFILE at 0009:028A NOTE: This error message may occur immediately if the Quick Format option is chosen. CAUSE ===== This general protection (GP) fault is caused by SYMEVNT.386, a device added to the [386Enh] section of the SYSTEM.INI file by Norton Utilities version 8.0: device=symevnt.386 ;Added By NU8 RESOLUTION ========== Symantec has confirmed this to be a problem in SYMEVNT.386. To correct this problem, download file NU8DRV.EXE from the Symantec bulletin board service (BBS). Before you obtain the NU8DRV.EXE file, you can work around this problem by opening the SYSTEM.INI file a text editor (such as Windows Notepad) and adding a semicolon preceding the device=symevnt.386 line to disable it: ;device=symevnt.386 ;Added By NU8 Then restart Windows to make this change take effect. NOTE: Disabling the above line is a temporary fix only, and it may cause problems with using Norton Utilities. MORE INFORMATION ================ For more information, contact Symantec Technical Support by phone or through the Symantec forum on CompuServe (GO SYMANTEC). KBCategory: kbtool kberrmsg kb3rdparty kbprb KBSubcategory: wfw wfwg gpf Additional reference words: err msg 3rdparty remark out control panel winfile.exe Windows Err Msg: WDCTRL Validation Failed at Phase Article ID: Q119674 ---------------------------------------------------------------- ---- The information in this article applies to: - Microsoft Windows operating system versions 3.1, 3.11 - Microsoft Windows for Workgroups versions 3.1, 3.11 ---------------------------------------------------------------- ---- SUMMARY ======= This article lists the meaning of the various phases that are displayed in the following error message at Windows startup if 32-bit disk access is enabled The Microsoft Windows 32-bit disk driver (WDCTRL) validation failed at phase . where is a specific phase. MORE INFORMATION ================ Below are the various phases that can appear in the above error message and a brief description of each: Phase 0: Int 13h, AH=8, GetDriveParms results failed; compare with FDPT (Fixed Disk Parameter Table, pointer got through int 41h/46h-xxxx) Phase 1: Number of heads differ Phase 2: Number of sectors differ Phase 3: Number of cylinders differ The next phases are read: Phases 4 - A -> HCS:0/0/1 (Head/Cylinder/Sector notation) Phases B - 11 -> Sector #503 (to control sector mapping) Phases 12 - 18 -> HCS:last-1/last-1/last-1 Phase 4/B/12: Read Sector 1/503/"last-but one" through int 13 failed Phase 5/C/13: Status reg of Controller says failure Phase 6/D/14: Wrong sector count Phase 7/E/15: Wrong sector number Phase 8/F/16: Wrong cylinder number Phase 9/10/17: Wrong sector size (not equal to 512 bytes) or drive Phase A/11/18: Wrong status from controller or difference in direct read data from int 13 read data. KBCategory: kbother kberrmsg KBSubcategory: win31 wfw wfwg winboot Additional reference words: 3.10 3.11 err msg wdctrl fastdisk WW1116: OLE Version 2.02 Article ID: Q123087 ---------------------------------------------------------------- - The information in this article applies to: - Microsoft Windows operating system versions 3.1, 3.11 - Microsoft Windows for Workgroups versions 3.1, 3.11 ---------------------------------------------------------------- - Microsoft has an Application Note available titled "WW1116: OLE Version 2.02" that contains an updated version of OLE for use with Microsoft Windows for Workgroups and Microsoft Windows versions 3.1 and 3.11. OLE 2.02 includes several improvements that affect other Microsoft applications, such as Microsoft Word for Windows and Microsoft Access. You can obtain this Application Note from the following sources: - CompuServe, GEnie, and Microsoft OnLine - Microsoft Download Service (MSDL) - The Internet (Microsoft anonymous ftp server) - Microsoft Product Support Services For complete information, see the "To Obtain This Application Note" section at the end of this article. THE TEXT OF WW1116 ================== ================================================================ ====== Microsoft(R) Product Support Services Application Note (Text File) WW1116: OLE VERSION 2.02 ================================================================ ====== Revision Date: 11/94 1 Disk The following information applies to Microsoft Windows(TM) and Windows for Workgroups, versions 3.1 and 3.11. ----------------------------------------------------------------- ---- | INFORMATION PROVIDED IN THIS DOCUMENT AND ANY SOFTWARE THAT MAY | | ACCOMPANY THIS DOCUMENT (collectively referred to as an Application | | Note) IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER | | EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE IMPLIED | | WARRANTIES OF MERCHANTABILITY AND/OR FITNESS FOR A PARTICULAR | | PURPOSE. The user assumes the entire risk as to the accuracy and | | the use of this Application Note. This Application Note may be | | copied and distributed subject to the conditions contained in the | | WW1116 package. | | | | Copyright (C) 1994 Microsoft Corporation. All Rights Reserved | | Microsoft, MS-DOS, and Win32s are registered trademarks and | | Windows is a trademark of Microsoft Corporation. DEC and PATHWORKS | | are registered trademarks of Digital Equipment Corporation. UNIX | | is a registered trademark of UNIX Systems Laboratories. | ---------------------------------------------------------------- ----- Introduction ------------ The WW1116 disk included with this Application Note contains an updated version of OLE for use with Microsoft Windows for Workgroups and Microsoft Windows versions 3.1 and 3.11. OLE 2.02 includes the following improvements: A. Removes the 20-user limit on read-only files read over networks Applications Affected: Microsoft Word for Windows, versions 2.x and 6.0 B. Removes some incompatibilities between OLE applications and network operating systems, such as DEC(R) PATHWORKS(R) and UNIX(R) Applications Affected: Microsoft Works for Windows, version 3.0 C. Corrects a general protection (GP) fault that occurs when you use multiple palettes Applications Affected: Microsoft Access, versions 1.x and 2.0 NOTE: Microsoft Access users implementing OLE should also order Application Note WX1124. D. Corrects a GP fault that occurs on machines with Win32s(R) present but not loaded Installing the Updated Files ---------------------------- The WW1116 disk included with this Application Note contains OLE202.EXE, a compressed file that includes a setup program that installs the OLE 2.02 library files in your Windows SYSTEM subdirectory. Use the following steps to install OLE 2.02: 1. Run Windows File Manager. 2. Select a drive on which you can temporarily store the OLE 2.02 library files. This drive must have at least 2 megabytes of available disk space. 3. From the File menu, choose Create Directory. Type a name for the temporary directory you are creating. For example, type "tempdisk" (without the quotation marks). 4. Insert the WW1116 disk included with this Application Note in the appropriate floppy disk drive, and copy OLE202.EXE from the WW1116 disk to the newly created directory. 5. Select the newly created directory and double-click OLE202.EXE. NOTE: For information about how to perform these steps, refer to Windows Help or your printed Windows documentation. At this point, OLE202.EXE expands the following files: Filename in DISK Size Filename in Size directory (bytes) Windows SYSTEM (bytes) subdirectory ------------------------------------------------------ _MSSETUP.BAT 255 Not applicable -- _MSSETUP.EXE 9,813 Not applicable -- _MSTEST.EXE 89,504 Not applicable -- COMPOBJ.DL_ 61,376 COMPOBJ.DLL 108,544 LICENSE.TXT 9,912 Not applicable -- MSCOMSTF.DLL 77,072 Not applicable -- MSCUISTF.DLL 70,192 Not applicable -- MSDETSTF.DLL 25,232 Not applicable -- MSINSSTF.DLL 67,104 Not applicable -- MSSHLSTF.DLL 14,400 Not applicable -- MSUILSTF.DLL 6,352 Not applicable -- OLE2.DL_ 170,041 OLE2.DLL 302,592 OLE2.RE_ 5,549 OLE2.REG 27,026 OLE202.INF 1,209 Not applicable -- OLE2CONV.DL_ 35,579 OLE2CONV.DLL 57,328 OLE2DISP.DL_ 87,252 OLE2DISP.DLL 164,832 OLE2NLS.DL_ 66,586 OLE2NLS.DLL 150,976 OLE2PROX.DL_ 24,410 OLE2PROX.DLL 51,712 SETUP.EXE 39,920 Not applicable -- STDOLE.TL_ 2,194 STDOLE.TLB 4,304 STORAGE.DL_ 89,197 STORAGE.DLL 157,696 TYPELIB.DL_ 111,855 TYPELIB.DLL 177,216 VER.DLL 9,008 Not applicable -- 6. Press the F5 key to update the File Manager display. 7. Double-click the LICENSE.TXT file to open it in Windows Notepad, and then choose Word Wrap from the Edit menu. Review the licensing agreement, then exit Notepad and return to File Manager. 8. Double-click SETUP.EXE. The OLE 2.02 library files are now installed on your system. Refer to the "Filename in Windows SYSTEM subdirectory" column in the table above to see the expanded filenames and sizes. 9. Delete the temporary directory you created in step 3 and all the files contained in it. ---------------------------------------------------------------- ------ TO OBTAIN THIS APPLICATION NOTE =============================== - On CompuServe, GEnie, and Microsoft OnLine, Application Notes are located in the Microsoft Software Library. You can find WW1116 in the Software Library by searching on the word WW1116, the Q number of this article, or S15010. WW1116 is a compressed, self-extracting file. After you download WW1116, run it to extract the file(s) it contains. - Application Notes are available by modem from the Microsoft Download Service (MSDL), which you can reach by calling (206) 936-6735. This service is available 24 hours a day, 7 days a week. The highest download speed available is 14,400 bits per second (bps). For more information about using the MSDL, call (800) 936-4200 and follow the prompts. To obtain WW1116, download WW1116.EXE. WW1116.EXE is a compressed, self-extracting file. After you download WW1116, run it to extract the file(s) it contains. - On the Internet, Application Notes are located on the Microsoft anonymous ftp server, which you can reach by typing "ftp ftp.microsoft.com" (without the quotation marks) at the ">" command prompt. You can find WW1116.EXE in the SOFTLIB\MSLFILES directory. - If you are unable to access the source(s) listed above, you can have this Application Note mailed or faxed to you by calling Microsoft Product Support Services Monday through Friday, 6:00 A.M. to 6:00 P.M. Pacific time at (206) 637-7098. If you are outside the United States, contact the Microsoft subsidiary for your area. To locate your subsidiary, call the Microsoft International Sales Information Center at (206) 936-8661. KBCategory: kbfile kbappnote kbole KBSubcategory: wfw wfwg win31 Additional reference words: 3.10 3.11 MS-DOS Partitioning Summary Article ID: Q69912 ---------------------------------------------------------------- ---- The information in this article applies to: - Microsoft MS-DOS operating system version 2.x, 3.x, 4.x, 5.x, 6.0, 6.2, 6.21, 6.22 ---------------------------------------------------------------- ---- SUMMARY ======= This article contains a summary of MS-DOS partitioning information. For information on how MS-DOS assigns drive letters, query on the following words in the Microsoft Knowledge Base: msdos and order and assign and drive and letter MORE INFORMATION ================ A hard disk's master boot record (MBR) is located in the first sector of the disk (cylinder 0, side 0, sector 1). The partition table is located at offset 01BE, containing up to four 16-byte entries. The fourth byte of each partition table entry is used to mark the partition type. MS-DOS began supporting hard disks in version 2.0. In MS-DOS versions 2.x, MS-DOS supports one type 01 partition of up to 32 megabytes (MB) in size, which use a 12-bit file allocation table (FAT). Fdisk creates only one MS-DOS partition per drive. In MS-DOS 3.0, partitions larger than 15 MB use a 16-bit FAT, which allows a smaller cluster size and thus more efficient disk usage. As a result, MS-DOS 2.x hard drives larger than 15 MB are incompatible with later versions of MS-DOS. Again, Fdisk creates only one MS-DOS partition per drive. In version 3.3, MS-DOS introduced support for more than one logical drive per hard disk. Logical drives are treated as completely separate disks under MS-DOS, even though they may occupy the same physical hard disk. This was supported by introducing nonbootable MS-DOS partitions known as extended MS-DOS partitions. Fdisk reports these as EXT DOS; other MS-DOS partitions began to be reported as PRI DOS (for primary MS-DOS). Each primary MS-DOS partition is a logical drive, and extended MS-DOS partitions contain from 1 to 23 logical drives (MS-DOS supports drive letters up to Z). Logical drives in extended MS-DOS partitions have the same FAT type as a primary MS-DOS partition of the same size. Only one PRI DOS partition and one EXT DOS partition is allowed per drive. On machines with two physical hard drives, a PRI DOS partition is not required on the second physical disk. A PRI DOS partition is required on the first physical disk. (MS-DOS would not support more than two physical disks.) Version 4.0 introduced logical drives larger than 32 MB. Full usage of these logical drives requires the MS-DOS program SHARE.EXE to be loaded. The following table explains the versions 4.x and later MS-DOS partition types: Partition FDISK Introduced Type Reports Size FAT Type in MS-DOS Version ----------------------------------------------------------------- ---- 01 PRI DOS 0 - 15 MB 12-Bit 2.0 (a) 04 PRI DOS 16 - 32 MB 16-Bit 3.0 05 EXT DOS 0 - 2 GB (b) n/a 3.3 06 PRI DOS 32 MB - 2 GB (b) 16-bit 4.0 (a) 15 MB size limitation added in 3.0 (b) 2 GB (gigabytes) includes a limit of 1024 cylinders per drive imposed by the standard AT ROM BIOS interrupt 13 protocol MS-DOS 5.0 and later also support up to eight physical hard disk drives. SHARE.EXE is not required for full large-drive support; this support is included in the MS-DOS kernel. MS-DOS versions 5.0 and later support the same partitioning strategy as versions 4.x, including FDISK's refusal to create more than one primary MS-DOS partition on a physical disk. However, because some original equipment manufacturers (OEMs) partitioning software allows you to create more then one primary MS-DOS partition, MS-DOS 5.0 and later have kernel support for up to 4 primary DOS partitions. This makes it easier to upgrade from previous versions of OEM-modified MS-DOS. FDISK still refuses to create more than one PRI DOS partition on a physical disk. NOTE: Many original equipment manufacturers (OEMs) have changed their MS-DOS to support more than one primary MS-DOS partition, larger type 04 partitions, and/or introduced new partition types. KBCategory: kbref KBSubcategory: msdos Additional reference words: 6.22 3.0 3.00 3.10 3.1 3.3 3.30 3.3a 3.30a 4.0 4.00 4.01 4.01a 5.00 5.0 5.00a 5.0a 6.00 6.0 6.20 6.2 6.21 "Missing Operating System" and "No ROM BASIC" Error Messages Article ID: Q80304 ---------------------------------------------------------------- ----- The information in this article applies to: - Microsoft MS-DOS operating system versions 3.x, 4.x, 5.x, 6.0 6.2 ----------------------------------------------------------------- ---- SUMMARY ======= "Missing Operating System," "No ROM BASIC," and other messages can appear as a result of improperly configured hardware. These types of messages can be given from the BIOS as well as from the MS-DOS master boot record (MBR). The following information illustrates other messages related to this situation and an explanation for such cases. CAUSE ===== The three most common situations to encounter such messages include the following. Case 1 ------ CMOS setting for hard drive improperly set This message is displayed by the MBR bootstrap code when it is unable to load the boot sector from the active partition. In this case, the ROM BIOS returned an error on the sector read because it found that the requested sector was out of the valid range specified by the disk parameter table. Because an improper CMOS setting would make the the disk parameter table invalid, a read request that would normally work failed when the ROM BIOS did a check on it. In most cases, the CMOS setting may be very close so other errors are not generated, but the system will not boot. The solution is to run the hardware CMOS setup and enter the correct drive type. If you are uncertain about how to do this, contact your hard drive, BIOS, or machine manufacturer. Case 2 ------ No active partition defined If there is no active partition defined, the MS-DOS MBR returns an error to the BIOS. In other words, the master boot code will attempt to go to ROM Basic when no bootable disk is found. Because clones do not have ROM Basic, they handle that case by displaying an error message. What message the BIOS will say depends on the BIOS. The solution is to run FDISK and set the primary MS-DOS partition to active. Case 3 ------ The primary MS-DOS partition is defined and marked bootable, but the boot sector is invalid. In this case, again the message is displayed by the MBR bootstrap code when it is unable to load the boot sector from the active partition. This illustrates that something is wrong with the MS-DOS boot sector. The solution is to use the MS-DOS SYS command, which regenerates the boot sector and copies the bootup files to the active partition. Another possible solution would be to re-format the disk. If SYS or FORMAT does not help the situation, the error message might be caused by a non-DOS MBR that gives this message for another reason. Other possible messages relating to these cases may include the following: Non-system disk or disk error Boot error Press F1 to retry For more information on related information, query on the following words: Master Boot Record KBCategory: kbenv KBSubcategory: msdos Additional reference words: 6.22 3.00 3.10 3.20 3.21 3.30 3.30a 4.00 4.01 5.00 5.00a 6.00 6.20 Windows Err Msg: Group File .GRP Invalid or Damaged... Article ID: Q81214 ---------------------------------------------------------------- ------ The information in this article applies to: - Microsoft Windows operating system versions 3.0, 3.0a, 3.1, 3.11 ----------------------------------------------------------------- ----- SYMPTOMS ======== When you start Windows, you may get the following error message: Group file .GRP is invalid or damaged; reconstruct the group. When you choose the OK button to continue, you may see a blank screen within Program Manager, or you may be missing some of your groups. CAUSE ===== This problem could occur for any of the following reasons: - You are running in real mode. (This applies to Windows 3.0 and 3.0a only.) To conserve memory, real mode limits the number of groups that can be displayed in Program Manager. Typically you will be limited to 8-10 groups. Combine some of your groups or start up in standard or enhanced mode. - A group (.GRP) file is deleted or damaged. - The Windows files were moved into another directory without reinstalling, and the PROGMAN.INI file was not updated to reflect this change. RESOLUTION ========== You can rebuild the Main, Accessories, and Games groups by doing the following: 1. From the Program Manager's File menu, choose Run. 2. Program Manager prompts you for a command line. Type setup /p and choose the OK button. Be sure to leave a space between "setup" and "/p", or you the error message "Specified path is invalid" will be displayed. ("Setup/p" is interpreted as one single filename which cannot be found.) NOTE: Setup /P rebuilds only the Main, Accessories, and Games group with the default Windows application icons. Any other external groups or icons that may have been damaged or lost are not restored with this Setup switch. There is no automatic method available for individual groups that may have been damaged or lost. If you do not want your Main, Games, or Accessories group to be reset to their defaults, edit the PROGMAN.INI file as follows: 1. From Program Manager's File menu, choose Run. 2. Type progman.ini and press ENTER. This starts Notepad and opens the PROGMAN.INI file. 3. In the [Groups] section, find the damaged or missing group and delete that line (see the example below). Renumber the remaining lines so they are in proper numerical order and the first group is labeled "group1." 4. From Notepad's File menu, choose Save. 5. Exit and restart Windows. NOTE: Upon exiting Windows, the Save Changes command may be unavailable (dimmed) until the group file error is corrected. The following is an example of a PROGMAN.INI file with a bad TOOLBOOK.GRP file: [Settings] Window=-1 -2 641 419 1 SaveSettings=1 MinOnRun=0 AutoArrange=0 [Groups] Group1=C:\WIN3\GAMES.GRP Group2=C:\WIN3\WINDOWSA.GRP Group3=c:\win3\TOOLBOOK.GRP Group4=C:\WIN3\MAIN.GRP Group5=C:\WIN3\ACCESSOR.GRP It should appear as follows (please note that the [Settings] section has not changed): [Settings] Window=-1 -2 641 419 1 SaveSettings=1 MinOnRun=0 AutoArrange=0 [Groups] GROUP1=C:\WIN3\GAMES.GRP GROUP2=C:\WIN3\WINDOWSA.GRP GROUP3=C:\WIN3\MAIN.GRP GROUP4=C:\WIN3\ACCESSOR.GRP To rebuild single groups manually, follow the procedure outlined in the "Microsoft Windows User's Guide" on pages 87-88 for version 3.0 and on pages 76-77 for version 3.1. The "/p" parameter is not documented in the documentation sent with the Windows product. REFERENCES ========== "Microsoft Windows User's Guide," version 3.0, pages 87-88 "Microsoft Windows User's Guide," version 3.1, pages 76-78 KBCategory: kbref kbtshoot KBSubcategory: win30 win31 wfw wfwg Additional reference words: tshoot 3.0 3.00 3.0a 3.00a 3.1 3.10 3.11 reconstructing Causes of System Integrity Errors in Windows 3.1 Article ID: Q82665 ---------------------------------------------------------------- ---- The information in this article applies to: - Microsoft Windows operating system versions 3.0, 3.0a, 3.1, 3.11 - Microsoft Windows for Workgroups versions 3.1, 3.11 ---------------------------------------------------------------- ---- SUMMARY ======= System Integrity errors are caused by unexpected CPU faults. The following information provides a general overview of CPU fault causes. For more information, refer to your Intel 80386 CPU manual or "The 80386 Book," by Ross P. Nelson (published by Microsoft Press). MORE INFORMATION ================ The following are some of the more common CPU faults: - Invalid opcode - Stack exception - General protection (GP) fault - Page fault NOTE: Not all occurrences of these faults are invalid. Valid, expected faults occur from all of the above except stack exceptions. Invalid Opcode -------------- An invalid opcode fault occurs when an instruction that is not legal is executed. The most frequent cause of this invalid fault is executing a value that is not an instruction. Stack Exception --------------- A stack exception fault occurs when an invalid stack operation is attempted. The most frequent cause of this invalid fault is trying to PUSH or POP a WORD or DWORD at an address that causes the operation to span across SP value 00000h or 0FFFFh. For example, attempting to POP a WORD with SP=0FFFFh, is attempting to read one byte of the WORD at offset 0FFFFh and the other byte of the word at offset 00000h. The CPU does not support this operation. General Protection (GP) Fault ----------------------------- Many things can cause a GP fault. As the name implies, this fault means something was attempted that is not allowed because it would violate the protection features built into the CPU. As with invalid opcode faults, a typical cause of this invalid fault is executing garbage, but unlike the invalid opcode, the instruction is legal; however, the particular form of the instruction is illegal at the time. Page Fault ---------- A page fault occurs when an access is made to memory that is not currently mapped, (not currently available). The most frequent causes of this invalid fault are wild pointer accesses to memory that is not legal to look at in the current time frame. This is often a manifestation of "protection." For example, a device wants to protect a piece of memory, always, or at the current time, so that only that particular device can use it. It makes the memory unavailable by using the paging features of the CPU so that any application that tries to read or write to this memory will be stopped by an invalid page fault. This helps prevent the wild pointer in the application from damaging critical information in memory. KBCategory: kbenv KBSubcategory: win30 win31 wfw wfwg gpf winmem Additional reference words: 3.00 3.00a 3.10 crash drwatson Windows 3.1 Resource Kit SYSTEM.INI [386ENH] Section A-L Article ID: Q83435 SUMMARY ======= The information in this article can be found in the SYSINI.WRI file in the Microsoft Windows Resource Kit for the Microsoft Windows operating system version 3.1. The SYSINI.WRI file can be viewed in Microsoft Windows Write. Write is an application contained in the Windows Accessories Group. The [386Enh] section of the SYSTEM.INI file contains information specific to running Windows in 386-enhanced mode, including information used for virtual-memory page swapping. MORE INFORMATION ================ The [386Enh] section can contain the following settings: ____________________________________________________________ 32BitDiskAccess= Default: Off if your hard disk is capable of supporting 32- bit disk access. Otherwise, this setting is not present in the SYSTEM.INI file. Purpose: Turns 32-bit disk access on or off. To change: Choose the 386 Enhanced icon in the Control Panel window. If this setting is not present in the SYSTEM.INI file, the 32-bit Disk Access check box will not appear in the Control Panel Virtual Memory dialog box. ____________________________________________________________ A20EnableCount= Default: The value computed by the Win386 loader. Purpose: Specifies the initial A20 enable count. (For more information about the A20 enable count, see your Extended Memory specification). To change: Use Notepad to edit the SYSTEM.INI file. (You should never need to change this setting.) ____________________________________________________________ AllVMsExclusive= Default: False Purpose: If enabled, this setting forces all applications to run in exclusive full-screen mode, overriding all contrary settings in the applications' program information files (PIFs). Enabling this setting might prolong the length of the Windows session when you are running network and memory-resident software that is incompatible with Windows. To change: Use Notepad to edit the SYSTEM.INI file. ____________________________________________________________ AltKeyDelay= Default: .005 Purpose: Specifies how much time Windows waits to process a keyboard interrupt after it processes an ALT interrupt. Some applications expect a slower processing rate than Windows in 386 enhanced mode normally uses. Increase this value if such an application has trouble handling the ALT key. To change: Use Notepad to edit the SYSTEM.INI file. ____________________________________________________________ AltPasteDelay= Default: .025 Purpose: Specifies how much time Windows waits before pasting any characters after the ALT key has been released. Some applications may require more time for recognition of the ALT keystroke. To change: Use Notepad to edit the SYSTEM.INI file. ____________________________________________________________ AllEMSLocked= Default: False Purpose: If enabled, this setting locks the contents of expanded memory used by all Windows and non- Windows applications into memory (instead of swapping it to disk) and overrides the non- Windows application PIF settings for EMS Memory Locked. Set this value to True if you are using a disk cache program that uses expanded memory. To change: Use Notepad to edit the SYSTEM.INI file. ____________________________________________________________ AllXMSLocked= Default: False Purpose: If enabled, this setting locks the contents of the extended memory used by all Windows and non- Windows applications into memory (instead of swapping it to disk), and overrides non-Windows application PIF settings for XMS Memory Locked. To change: Use Notepad to edit the SYSTEM.INI file. (You should never need to change this setting). ____________________________________________________________ AutoRestoreScreen= Default: True Purpose: Specifies whether the display for non-Windows applications should be restored by Windows or the applications themselves when they become active. If enabled, Windows saves the display information for a non-Windows application in memory when you switch away from the application. When you switch back to the application, Windows uses this information to restore the screen. If disabled, the application must restore its own display by repainting the screen. This requires less memory, but can slow down performance since Windows can usually restore the screen faster. Note: This setting only applies to VGA displays and affects only applications that notify Windows that they can update their own screen automatically when Windows initiates a display update call. To change: Use Notepad to edit the SYSTEM.INI file. ____________________________________________________________ BkGndNotifyAtPFault= Default: True for VGA displays; False for 8514 displays. Purpose: Specifies when a notification should be sent to a non-Windows application or to Windows to prevent the application from attempting to access the display (which might corrupt the display of a different application). This notification can be sent while switching to a different application or when attempting to access the actual display. If disabled, Windows sends a notification when switching between applications. Disable this setting if you are using a display that has special hardware, (for example, 8514 and TIGA). If you are using a VGA display, enabling this setting should work in most cases. To change: Use Notepad to edit the SYSTEM.INI file. ____________________________________________________________ CGA40WOA.FON= Default: None Purpose: Specifies the filename of the fixed-pitch display font used for non-Windows applications with a display of 40 columns and 25 or fewer lines. To change: Quit Windows and run Setup from the MS-DOS prompt. Change the Codepage or Display setting. ____________________________________________________________ CGA80WOA.FON= Default: None Purpose: Specif