Copyright: Copyright 1993 Microsoft Corp.
Citation: Copyright 1993 Microsoft Corporation. All rights reserved.


 Tips for Windows for Workgroups 3.11

Prepared 02/24/94

 Windows for Workgroups 3.11

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.


Windows for Workgroups 3.11
 Tips for Windows for Workgroups 3.11

 Windows for Workgroups 3.11

 MRU Limits for File Manager, Print Manager in WFWG

 Disconnect Network Printer Only in Print Manager

 Minimum System Requirements for Windows for Workgroups

 WFWG Err Msg: Insufficient Memory Available... when Starting

 SHIFT Key Must Be Held After Login to Disable Startup Group

 Add/Remove Components Does Not Delete INI Files

 Functionality of NET STOP /Y Command in WFWG

 Serial Network Connections Not Supported in WFWG

 NET START WORKSTATION Command AutoStart= Switch in WFWG

 Print Manager Status Bar Reports Share Name Information

 GP Fault in Mail for Workgroups May Suppress Password

 Accessing Microsoft LAN Manager Servers with WFWG

 WFWG and Novell: LASTDRIVE=Z Makes [ and ] Active Drives

 Cannot Browse LAN Manager 1.x Servers in WFWG

 WFWG: LAN Architecture Cable Specifications

 Wang's WINLOC Interface May Hang Windows for Workgroups

 Zenith Znote Does Not Resume Net Operation When Paused

 System Hangs with ASPI4DOS.SYS Version 3.0 or Earlier

 System May Not Boot after Installing Intel Ether Express

 Toolbar Buttons Extend Beyond the Toolbar in File Manager

 WinMeter Abnormally High with Some Programs

 Setting Up a Postoffice Across the Network

 Net Watcher: Lines in Share Name When Scrolled

 Print Manager Help Error: Cannot Use CTRL+UP ARROW

 Artisoft NE3 Network Card Compatibility

 WFWG Err Msg: Invalid or Missing COMMAND.COM

 WC Mail Defaults to Two Lines Per Page When Printing

 Shared Folder Icons (Hands) can Disappear in WFWG

 How Does WFWG Upgrade from LAN Manager 2.1?

 Upgrading from Workgroup Connections to WFWG with OEM Drivers

 Running NetBIOS Over DECnet Protocol

 NetWare Printing in Windows for Workgroups

 Password Caching in Windows for Workgroups

 Print Manager Error Indications in Windows for Workgroups

 Managing Network Printers in Print Manager and Control Panel

 Network Printing in Windows for Workgroups

 Path Used for Spool Files for a Shared Printer

 Two-Password Shares and Password Caching

 How To: File Handles Open When WFWG Server is Down

 WFWG Err Msg: No Configuration Servers Found... DCA's Comnap

 Persistent Connections and Windows for Workgroups

 Workgroups Mail and Mail 3.0 Do Not Work with COMPAQ DOS 3.31

 Intel EtherExpress (EE) 16 Network Card Configuration

 Schedule+ Err Msg: Schedule Transport DLL Does Not Support...

 Conventional Memory Change with WFWG and DYNAMIC=YES Setting

 WFWG May Momentarily Stop the Computer With Workgroups Mail

 Cannot Change Order of First Print Job in WFWG

 Screen Momentarily Garbled at Windows for Workgroups Startup

 Cannot Find HOME Directory Share on IBM LAN Server

 Client Not Notified of Remote Printer Problem

 NDOS Can Cause Windows to Exit Unexpectedly

 Information on Network Card Detection (NCD)

 WFWG Err Msg: Error Loading MMTLHI.DRV... With ET 4000 Video

 WFWG Err Msg: This Application Has Violated... LAN Manager

 Windows for Workgroups File Manager and Extended Characters

 NetWare NCOPY to Local Drive Gives Sharing Violation

 Using PING.EXE with Windows for Workgroups

 Password Cache Not Used With UNC File Access

 WFWG Err Msg: An Error Occurred While Trying to Reconnect...

 WFWG Err Msg: MS-DOS Error SYS0002

 Installing WFWG Over Existing Mail 3.0 and Schedule+ 1.0

 Cannot Set Default Appointment Time in Schedule+

 NetWatcher Shows Same User Multiple Times

 Hearts Requires EGA (or Above) and Mouse

 GP Fault in WINHELP.EXE After Starting Microsoft Mail

 Mail Message File Size in Windows for Workgroups

 Device Contention Errors with Parallel Port Network Cards

 WFWG Servers Cannot Act as a Gateway, Router, or Bridge

 MSIPX and NETX Command Line Switches with WFWG

 Share Names With a "$" Character at the End Are Hidden

 Shared CD-ROM or Floppy Drives Must Contain a Disk At Startup

 Corrupt CONNECT.DAT May Cause Invalid Errors in WFWG

 FastTips: Mail and Schedule+ Questions and Answers

 FastTips: Sharing CD-ROMs and Printers Questions & Answers

 Setup and Control Panel: Different Recommended Swap File Size

 Exiting Wing Commander Hangs Computer

 No Network Services After Install Over LAN Manager 2.0

 File Manager Displays Actual Total Disk Space

 Network Problems with AMI Pro and JustWrite

 How To Use Help Command in WFWG Setup Does Not Work

 Problems Upgrading Drivers When Installing WFWG on LAN Manager

 File Manager Allows Disconnect of Shared WFWG Directory

 TBMI2.COM Removed from AUTOEXEC.BAT in WFWG

 QEMM LASTDRIVE Program Is Incompatible with WFWG

 Network Dysfunctional After Removing Novell NetBIOS Support

 Message Looks Read or Opened After Move, Copy, or Print

 Setup Word for Windows Before Running Program Over A Network

 NET START from MS-DOS Prompt Can Hang Computer

 Font Corruption in Ventura Publisher 4.0

 WFWG Err Msg: NET3651: There is No Protocol Added...

 Write Err Msg: '<Filename> Could Not Be Found' and WFWG Hangs

 WFWG Err Msg: One or More Files Could Not Be Found that...

 Computer Hangs After Removing Token Ring Card

 File Manager: Five Extensions Maximum

 How To: Troubleshooting a Network DDE Link with WFWG

 How To: Setting Up a Resource in Schedule+ with WFWG

 NET.EXE Does Not Always Load Full Redirector by Default

 WFWG: MSDLC.EXE Needed for Attachmate's Extra! for Windows

 WG0667: Peer-to-Peer vs. Client-Server Networks

 WG0668: Advanced Mail and Schedule+ Help Files and Demos

 WFWG and Windows: System Hangs When Copying Files

 WFWG Err Msg: An Error Has Occurred. ClipBook Viewer Cannot...

 WFWG: Null Password Bypasses Login

 Most Recently Used (MRU) Lists of Previous Connections in WFWG

 WFWG: GP Fault in Video Driver when Using ClipBook Viewer

 ClipBook: Paste Link with Ami Pro May Paste Corrupt Data

 WFWG: Server Responds Slowly After RAS Connection is Made

 14 or 15 Character Machine Name Causes Print Manager Error

 Schedule+ Q&A: Remote Usage

 Schedule+ Q&A: MS-DOS, Macintosh, and Connectivity

 Schedule+ Q&A: Time and Date Issues

 Schedule+ Q&A: Scheduling Meetings

 Schedule+ Q&A: OLE and Attachments

 Schedule+ Q&A: Reminders Application

 Schedule+ Q&A: Printing

 WFWG Err Msg: "Extended Error 65" or "File Manager Cannot..."

 3Com EtherLink II Card Not Detected During Setup of WFWG

 No Files Found with SMC 90C65 Based Arcnet Cards in WFWG

 WFWG: Problems when Windows Express Version 3.0 Run as Shell

 Setup Overwrites _DEFAULT.PIF and DOSPRMPT.PIF

 WFWG Setup Modifies Wrong Lines in CONFIG.SYS

 Must Use Quotation Marks if Shared Resource Names Have Spaces

 3Com EtherLink III (3C509) in EISA Machines

 WFWG Err Msg: Add SystemROMBreakpoint=FALSE to SYSTEM.INI

 File Manager Does Not Allow Copying of Open Files

 WFWG: Exiting from Shell Does Not Exit Windows for Workgroups

 File Manager: Can't Redirect Local Drives; Use Net Redirector

 After Failed WFWG Setup, Not Enough Space to Setup Again

 Windows for Workgroups Hangs at Logo Screen

 WFWG: Err Msg: Invalid Keyword/Argument. Check Configuration.

 NET.EXE Pop-up Interface Hard to Read on Monochrome Monitors

 WFWG may Hang if TCP/IP hasn't Registered at Logon Time

 WFWG NET.EXE Err Msg: MS-DOS Popup for Workgroups Could Not...

 Mail Reports Bad Network Connection When Low On Disk Space

 Installing WFWG over IBM Lan Server Causes Netbind Error

 Schedule+ Q&A: Modifying Other Calendars

 Schedule+ Q&A: Tasks

 UB Cards Not Initialized If Memory Window Is Not Excluded

 Schedule+ Q&A: Scheduling Resources

 Schedule+ Q&A: Display

 Persistent Connections May Not Work with Real Mode Redirector

 Network Print Jobs May Disappear from Print Manager in WFWG

 No Drop Cables Allowed from Thin Ethernet T-Connector to NIC

 WFWG Network Adapter Card & Cable Replacement Instructions

 Startup and Exit Sounds May Not Work with WFWG

 Token Ring Cards and Local Addressing with WFWG

 WFWG: Network Button Does Not Appear in Open Dialog Box

 Intel EtherExpress Card Conflicts with Scanning Hardware

 Using Custom IRQ and I/O Settings with Windows for Workgroups

 PostScript EPS Files Are Device Independent

 WFWG Err Msg: Error 2184: The Service Has Not Been Started

 WFWG: Cannot Connect to Local Postoffice

 Windows Components Not Installed by Default SETUP.SHH File

 Xircom Network Simplicity Adapters Not Supported with WFWG

 WFWG May Hang Loading in Enhanced Mode Without a Terminator

 Unable to Connect to a Server Using Thomas Conrad TC6242 Card

 WFWG: Error Attempting to Move Local Schedule+ .CAL File

 WFWG Err Msg: Local Copy of Schedule+ Cannot Be Accessed

 Installing WinLogin with Windows for Workgroups

 WFWG May Hang if InDOSPolling=Yes with an Intel EtherExpress

 FastBack Plus Windows Changes VDMAD.386 to *VDMAD with WFWG

 Unable to Share Printer when SUBST Is Used for TEMP Directory

 WFWG File Manager Shows Multiple WIN.INI Files

 How To: Customizing the WFWG Mail and Schedule+ Chime Sound

 SMC_ARC.DOS May Result in a POR Failure or Adapter Not Found

 NetDDE Passwords Must Be Uppercase when Using NDDEShareAdd

 Using the HP 27247A Network Interface Card with WFWG

 LMLogon=YES/NO is Not Recognized by Control Panel

 WFWG: Schedule+ May Not Print Entire Appointment Field

 SMC Microchannel Adapter Works with SMC EtherCard Driver

 WFWG Err Msg: "Failure: Hardware Not Found..." with Intel EE16

 WFWG: Recovering Windows 3.1 After Installation With DR-DOS

 WFWG Err Msg: Windows 3.x Could Not Be Located...

 NIC at I/O Port of 0360h May Prevent Local Printing

 WFWG Open File Handle Limits

 Re-creating the Postoffice Initialization Procedure

 DynaComm Elite Requires a DLC Provider to Function with WFWG

 Disabling Peer-To-Peer Network Functionality with WFWG

 WFWG: Network Card Detection Hangs Machine During Setup

 Windows for Workgroups and NetBEUI Protocol

 WFWG Err Msg: "Mail Could Not Connect to Your Mail Server"

 PCMail: Differences Between WFWG Mail and PC Mail 3.0

 WFWG: Printing with Banyan Vines Connectivity

 Print Conflicts Between Remote and Local MS-DOS Applications

 Setting Up WFWG on a Novell Workstation Without a Hard Disk

 Using SQL Server over Novell NetWare with WFWG

 NET START NETBEUI/BASIC/FULL/WORKSTATION/REDIR/LIST

 IBM PC Network Baseband Adaptr/A Untested, Not on WDL

 Paradox for Windows Cannot Access WFWG Shared Directory

 Running Windows for Workgroups on a DEC Pathworks Network

 Using IBM LAN Server 1.3 with Windows for Workgroups

 Using Novell's ODI Drivers with Windows for Workgroups

 WFWG: Incorrect AutoStart=<Full-or-Base> Entry in SYSINI.WRI

 Spooling Print Jobs from MS-DOS-based Applications in WFWG

 Windows for Workgroups Mail Issues

 WFWG: Status Bar Option in Chat Shows Incorrect Shortcut Key

 PIF Hot Key Causes Errors or Help to Appear in Mail/Schedule+

 Windows for Workgroups: Avoiding Hardware Conflicts

 WFWG Err Msg: An Error Occurred While Reconnecting...[SYS0000]

 How to Use Keystrokes to Insert Special Characters

 Windows for Workgroups and Windows NT Interoperability

 Creating a Custom Separator Page for PCL5 Printers

 WFWG: Schedule+ Prompts to Archive and Delete Old Appointments

 No Inbox in Windows for Workgroups Mail or Microsoft Mail 3.0

 Files Modified by Workgroup Connections Setup Program

 Running PC-NFS 5.0 with Windows for Workgroups

 WFWG Err Msg with New NETAPI.DLL: Undefined Call to Dynalink

 WFWG: Where Workgroup Mail Finds the Default Account Name

 WFWG Err Msg: Network Name Was Deleted

 WFWG: Separator Page Prints First Name of User Only

 FastTips: Troubleshooting Windows for Workgroups Q&A

 FastTips: Using Microsoft At Work PC Fax with WFWG 3.11 Q&A

 FastTips: Windows for Workgroups 3.11 Setup Issues Q&A

 WG0904: Support for Novell NetWare 4.0

 FastTips: Using Novell NetWare with WFWG 3.11 Q&A

 WFWG Mail: DoubleSpace and Highest Security Options

 Differences Between LAN Manager and WFWG WinPopup

 Net Watcher Audit Log Shows Two Entries for Failed Password

 Sharing Printers on Serial Ports in Windows for Workgroups

 CAS Modem Fails to Receive Faxes with WFWG 3.11

 Network-Based Installation Issues with WFWG 3.11

 HPPCL5E.DRV Does Not Save Paper Tray Selection

 GP fault in MS Mail "Work Offline" Dialog when Exiting WFWG

 MSD Version 2.1 Does Not Detect Gateway2000 ColorBook

 WFWG 3.11: UNC Filenames with Word Fail on Novell Network

 Network Dialog Err Msgs Truncated with (Small Fonts)

 WFWG Setup Leaves Two Sets of Mail and Schedule+ Icons

 Windows for Workgroups Hangs at Startup with HP VxD HPVNPD.386

 IRQ Option Includes Only IRQs 2-5 for Novell/Anthem NE2000

 WFWG Chat Err Msg: No Connection to <Computername>

 WFWG Err Msg: This Application Was Communicating on...Network

 Windows for Workgroups 3.11 Hangs with 09-07-93 EXP16ODI.COM

 Cannot Attach to NetWare Server After Installing WFWG 3.11

 SPX-Compatible Applications and Windows for Workgroups 3.11

 WFWG Setup May Not Detect Existing 32-Bit Disk Access Drivers

 Cannot Run 32-Bit File Access with NE2000 ODI Driver

 Standard Mode Video Grabber May be Deleted from WFWG 3.11

 Mail Doesn't Remember Password

 File Manager GP Fault on BW-NFS Network

 32-Bit File Access Requires MS-DOS 6.2 DoubleSpace

 WFWG 3.11 ErrMsg: Error 13: The Data Is Invalid

 System Slows After 32-Bit File Access Is Enabled

 WINVER.EXE Reports Incorrect Version

 NE1500T Network Card Cannot Talk to Network

 Most Common Questions and Answers About Microsoft WFW 3.11

 WFWG Err Msg: The 32-Bit File System is Incompatible...SUBST

 The IPX/SPX Compatible Protocol Supports Only One Network Card

 File Manager Doesn't Save Positions of Minimized Icons

 WFWG Hangs at Startup with Future Domain 32-Bit Disk Access

 WinPopup Message Incorrectly States Message Was Sent

 Cursor Remains an Hourglass When Loading Schedule+

 SmartVu Disabled on Dell Computers with VFAT

 The F1 Key in Chat and NetWatcher May Not Open Help

 Windows for Workgroups 3.11: How to Disable Printer Alerts

 Extended Characters May Be Displayed Incorrectly in WinPopup

 WG0949: Windows for Workgroups 3.11 Setup Information

 Windows for Workgroups 3.11: Using the Generic IPXODI Driver

 Incorrect I/O Address Detected on SMC Elite+ Network Adapter

 NET Command Returns Error in VM While Network Setup Is Active

 File Server Hangs Network After Accessing Shared CD-ROM

 OEM Modems May Be Supported by Windows for Workgroups

 RAS Returns Poorly Formatted or Unreadable Error Messages

 WFWG: Creating a New SYSTEM.INI Without Third-Party Drivers

 Windows for Workgroups 3.11 Retail Package Options

 WFWG: Scrambled Display Using Generic Super VGA Driver

 WFWG 3.11: Hardware Compatibility List - Modems for AWFAX

 Network Card Drivers That Must Load in Conventional Memory

 Windows for Workgroups: 32-Bit File Access Is Slow with MSIPX

 WFWG 3.11: Hardware Compatibility List - Computers

 WFWG 3.11: Hardware Compatibility List - Modems for RAS

 WFWG 3.11: Hardware Compatibility List - Network Cards

 Intel SatisFaxtion 100 & 400E Are Class 1 and CAS Compatible

 Fax Modem Class Required for Binary File Transfers

 Meaning of WFWShell Line in the SYSTEM.INI File

 Fax Monitor Is Idle on CAS Modems While Receiving Faxes

 Setting Up a Shared Copy of WFWG on LAN Manager-Based Servers

 Total Number of Workgroups That Can Be Displayed

 Video Seven VRAM II Video Adapter Hangs WFWG 3.11 Setup

 Comprehensive List of WFW 3.11 User's Guide Doc Errors

 WG0788: Customizing WFWG 3.11 for Individuals w/ Disabilities

 WFWG 3.11 Err Msg: Error 2138: The Workstation Service...

 Err Msg: Error Loading PROTMAN.DOS After Using SETUP /H

 WFWG: Adapter Media Type Information Is Incorrect

 WFW Mail Will Not Cache a Blank Password

 Using Novell NetWare's RPRINTER with WFWG 3.11

 MS-DOS Virtual Machine Hangs with Full Redirector Loaded

 Novell: Direct Hosting Works on ODI Drivers Only

 Net Watcher Event Log Does Not Clear when Scroll Bars Present

 NET USE in VM with NetWare Diskless Workstation

 Mail Components Are Always Installed

 No Servers If Real-Mode Redirector Started Before WFWG 3.11

 Windows for Workgroups Protocol Limits

 WFWG Err Msg: Warning: A Serious Disk Error Has Occurred...

 Using Novell's ODINSUP and NETx with Windows

 How to Disable Write Caching for the 32-Bit File System

 Using Novell's ODINSUP with VLM.EXE and WFWG 3.11

 32-Bit File Access Causes ScanDisk to Report Error

 WFWG 3.11 Err Msg: Executable Not Found

 RAS May Not Function on a Network Installation

 Err Msg in MS-DOS Session: Cannot Write to Drive C:/Cancel...?

 Several WFW<nn> Files in Your Windows Directory

 NET START FULL Invokes Intel SatisFAXtion Fax Popup

 WFWG Setup Installs Older Logitech Mouse Driver

 WFWG: Can't Connect to Share That Has Multiple Passwords

 Incorrect Sort Order in File Manager with Some Languages

 Upgrade over IBM LAN Server Leaves Drivers in Startup Files

 EMM Exception Error #6 Exiting Windows for Workgroups 3.11

 WFWG Err Msg: There Is Not Enough Memory Available

 NDIS2 Drivers Load but NDIS3 Drivers Don't--Errors 6200 & 58

 WFWG 3.11: Real-Mode Redirector and Direct Hosting

 WFWG 3.11 PIF Editor Has Standard Mode Command

 Using Wollongong TCP/IP with Windows for Workgroups 3.11

 NET USE * /HOME Err Msg: The syntax Is Incorrect

 Suffix String Not Available for Microsoft At Work PC Fax

 Installing a Banyan VINES Network with WFWG 3.11

 WFWG Err Msg: Your Network Adapter MS$AE1 Is Not Working...

 3Com Etherlink 16 Network Adapter Unstable in Turbo Mode

 WFWG Err Msg: Error 59: An Unexpected Network Error...

 Dr. Watson Removed in Windows for Workgroups 3.11 Setup

 32-Bit File Access Maximum Cache Size

 PC-NFS Error: NFS903F Missing or Invalid PROTOCOL.INI Data

 Comprehensive List of WFWG 3.11 Resource Kit Doc Errors

 IBM ValuePoint with BIOS Date 4/29/93 Hangs at Logo Screen

 32-Bit File Access and Stacker 3.1 Utilities

 WFWG Err Msg: No Domain Server Was Available to Validate...

 Problems Accessing B&W NFS Mounted Drives in WFWG 3.11

 WinPopup Cannot Run... Error with VREDIR.386

 32-Bit File Access Cache Size Is Incorrectly Displayed

 WFWG 3.11 Err Msg: Error 1: An Internal Error Occurred

 WFWG Err Msg: Selected Server Cannot Be Found on the Network

 Err Msg: An Error Occurred Accessing the Security Settings...

 ODIHLP.EXE Cannot Be Unloaded

 After Dark AD-DOS.COM and Novell NetWare LSL.COM

 Extended Error 53 When Accessing Network Drives from MS-DOS

 WFWG Err Msg: The Specified Drive Letter or Device Is Invalid

 ODIHLP.EXE Load Error Messages

 Loading NetBEUI or NetPopup in Conventional Memory

 WFW 3.11 may Fail After Upgrading (Missing SlotNumber= Entry)

 Additional NICs Supported in Windows for Workgroups 3.11

 Remote Access Service - Error 714: Configuration error

 WFWG Hangs on Logo Screen (32-Bit File Access and NoEmmDriver)

 Using Windows for Workgroups 3.11 with Beame and Whiteside

 Games Group Installed Even If Games Are Not Selected

 Microsoft At Work PC Fax: Top Questions and Answers

 WFWG 3.11: The Network Group and WINSETUP /P

 WG0971: NDIS2SUP.386 Corrects Problems Restarting WFWG

 WG0970: VNETBIOS.386 Corrects Real-Mode Transport Problems

 Windows for Workgroups Err Msg:  Setup Error #3

 NETWORKS.WRI from Windows for Workgroups 3.11 (Part 2 of 4)

 Err Msg Changing Virtual Memory Setting: 32-Bit File Access...

 Repeating Window Displays with Microsoft 256-Color SVGA Driver

 WG0974: VKDA.386 Corrects Keyboard Problems on Ambra Computers

 WG0973: RMM.D32 Corrects 5-Second Delay When Starting Apps

 WFWG Err Msg: The 32-Bit File System Cannot Be Used When...

 Reinstalling the "Microsoft At Work PC Fax on FAX:" Driver

 How to Flush 32-Bit File Access Cache (VCACHE)

 Windows for Workgroups 3.11 Disk 8 Contains Disk 1 Files

 Incoming Faxes Received but Never Appear in Inbox

 Cannot Dial Automatically from Works 2.0 with WFWG 3.11

 MoreFonts Not Supported with Windows for Workgroups

 Cannot Find NONET.DRV with WordPerfect 6.0 for Windows

 WFWG 3.11 Err Msg: General Protection Fault in WFWSETUP.DLL

 Recovering Folders from a Corrupted Microsoft Mail File

 At Work PC Fax ErrMsg: Attachment Type Was Not Supported

 Gateway with PCI Bus Hangs with Communication Applications

 Deleting Fax from Outbox Does Not Remove It from the Queue

 How to Re-Create the Network Group and Its Program Icons

 Printer Drivers Included in WFWG 3.1 But Not WFWG 3.11

 Faxes from Server Are Sent Before Faxes from Other Machines

 Specifying Command-Line Parameters for NDIS 2 Drivers

 No Master Browse Server Available with TCP/IP

 GVC Ethernet Netcard Requires Updated Driver for WFW 3.11

 Removing WinFax Pro from Windows for Troubleshooting

 Shiva Support for Windows for Workgroups 3.11

 List of Hardware Devices and Common I/O Base Address Conflicts

 Hardware Failure Errors with RAS & US-Robotics 14400 Sportster

 RAS ErrMsg: NETBIOS Error 640: A Netbios Error Has Occurred...

 Windows for Workgroups 3.11 Point-to-Point Server Update

 WFWG 3.11 Resource Kit Err Msg: THREED.VBX Is Out of Date

 WFWG Error Msg: This Postoffice Cannot Be Updated

 Errors on Token Ring Network with Banyan Vines 5.52 and WFWG

 Clean Boot for WFWG 3.11 with NetWare Connectivity

 Changing to EGA or Hercules Video Support in WFWG 3.11

 Err Msg on TI 4000 with DOS 6 BATTERY.PRO & 32-Bit Disk Access

 WFWG: Racal NI6510 Driver Doesn't Work with Etherblaster NIC

 Error 6101: The String Specified by the Workgroup...

 WFWG 3.11 and Sun PC-NFS 5.0 Err Msg: Invalid COMMAND.COM

 Microsoft Mail Err Msg: Error: Unable to allocate hook...

 WFWG Setup with HP Ethertwist Cards: No Network Installed

 Video Display Problems with MS-DOS Prompt and Trident Card

 Cannot see Writing with Pen Pointing Device and Super VGA

 System Hangs Using Super VGA driver with Compaq QVision

 Video Corruption with Diamond Stealth and WFWG VGA Driver

 Persistent Connections may not Restore with Basic Redirector

 Advanced APM, Microsoft Mail, & AT Work Fax can Cause GP Faut

 WFWG May Stop Serving After Several Hours with Intel EE16 ODI

 Security Settings File Error with Shared Windows Installation

 WFWG 3.11: How to Obtain Microsoft DLC and Microsoft TCP/IP

 New Installation of WFWG with IPX.COM Gives Erroneous Dialog

 Share Fax Modem Dialog Allows Creation of Invalid Directory

 Incorrect Detection of Artisoft's NodeRunner Network Card

 WFWG 3.11: 3C509 MLID May Cause Lost Connections and Hangs

 CD-ROM Always Shows 127 MB Used and Zero Bytes Free

 WG0988: IBMTOK.386 Corrects Problems with Exiting WFWG

 WG0991: Updated NE2000.386 Allows WFWG to Start Correctly

 WG0992: Updated Files for Microsoft At Work PC FAX 1.0

 Using At Work PC Fax with Other Communications Software

 Problems Installing IBM Quietwriter Driver with WFWG 3.11

 Problems Sending Faxes to European Numbers

 WFWG Err Msg on Gateway 2000 P5: Microsoft Windows 32-Bit...

 AWFAX Hangs When Faxing a Microsoft Works for Windows Document

 RAS Err Msg: Error 642: One of Your NetBIOS Names Is...

 WFWG 3.11: TI MicroLaser May Cause Computer to Hang


MRU Limits for File Manager, Print Manager in WFWG

Article ID: Q88100

---------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

---------------------------------------------------------------

SUMMARY

=======

Windows for Workgroups maintains lists of the most recently used (MRU)

network drives and network printer connections. This feature allows up

to 12 network drive connections and 12 network printer connections to

be maintained.

MORE INFORMATION

================

The network drive connection information is stored in the [MRU_Files]

section of the WIN.INI file. The network printer information is stored

in the [MRU_Printers] section of the WIN.INI file.

The network drive connections list is accessed by opening the Disk

menu in File Manager. Choose the down arrow on the Path box to see the

list of maintained network drive connections.

The network printer connections list can be accessed by opening the

Printer menu in Print Manager. Choose the down arrow on the Path box

to see the list of maintained network printer connections.

There are no entries in the [MRU_Files] and [MRU_Printers] sections

by default.

Additional reference words: 3.10 WFWG


Disconnect Network Printer Only in Print Manager

Article ID: Q89299

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

----------------------------------------------------------------------

SUMMARY

=======

In Windows for Workgroups version 3.1, the Print Manager must be used

to disconnect network printers.

You cannot disconnect network printers through the Control Panel in

Windows for Workgroups. In earlier versions of Windows, this feature

has been available in the Printers option of Control Panel.

NOTE: You can still connect a network printer through the Control

Panel Printers option.

MORE INFORMATION

================

Steps to Disconnect a Network Printer in Windows for Workgroups

---------------------------------------------------------------

1. Open the Print Manager.

2. From the Printer menu, choose Disconnect Net Printer.

3. Select the network printer you want to disconnect, then

   choose the OK button.

Additional reference words: 3.1 3.10 wfwg win3


Minimum System Requirements for Windows for Workgroups

Article ID: Q89333

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

----------------------------------------------------------------------

SUMMARY

=======

Below are the minimum system requirements for Microsoft Windows for

Workgroups. Requirements differ for a client (a machine that is not sharing

its printers/directories) and a server (a machine that is sharing its

printers/directories).

MORE INFORMATION

================

The minimum client installation of Windows for Workgroups requires:

 - 80286 microprocessor or better for version 3.1

 - 80386sx microprocessor or better for version 3.11

 - 2048 kilobytes (K) total memory for version 3.1

 - 3 megabytes (MB) total memory for version 3.1 (2 MB with no

   network installed)

 - 6.2 MB of hard drive space (14.5 MB recommended)

The minimum server installation of Windows for Workgroups requires:

 - 80386sx microprocessor or better

 - 3072K total memory (4096K recommended)

 - 3 megabytes (MB) total memory for version 3.1 (4 MB recommended)

 - 10.5 MB of hard drive space (14.5 MB recommended)

If the server is also acting as a Mail postoffice, additional hard drive

space is required on the server.

Additional reference words: 3.10 WFWG minimum setup


WFWG Err Msg: Insufficient Memory Available... when Starting

Article ID: Q89353

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

----------------------------------------------------------------------

SYMPTOMS

========

The following error may appear when you start Windows for Workgroups:

   Insufficient memory available

The error message appears in a dialog box with "Windows for

Workgroups" in the title bar.

CAUSE

=====

There are too many drivers listed in the Drivers portion of Control

Panel. When Windows for Workgroups starts, all of these drivers are

loaded into conventional memory, and the amount of conventional memory

available is reduced with the loading of each driver. When there is

too little conventional memory for Windows for Workgroups to load the

next driver, an error message appears.

WORKAROUND

==========

The amount of available conventional memory must be increased. You can

increase conventional memory by taking one or a combination of the

following actions:

 - Load fewer drivers in the CONFIG.SYS and AUTOEXEC.BAT files.

 - Load some of the drivers in the CONFIG.SYS or AUTOEXEC.BAT files

   into high memory.

 - Load fewer drivers in the Drivers portion of Control Panel.

 - Set LASTDRIVE (in CONFIG.SYS) to a letter such as J or K, rather

   than Z. Since each letter uses about 100 bytes more memory than the

   preceding letter, limiting the drive letters in this way can prevent

   the error from occurring. (Note that this does limit the number of

   network drives that you can access.)

Additional reference words: 3.10 3.1 wfwg


SHIFT Key Must Be Held After Login to Disable Startup Group

Article ID: Q89354

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

SUMMARY

=======

To disable the Startup group from functioning in Windows for

Workgroups, press the SHIFT key immediately after the login prompt.

MORE INFORMATION

================

In Microsoft Windows operating system version 3.1, the Startup group

is used to load applications automatically when starting Windows. You

can disable these programs by holding down the SHIFT key as Windows

loads. Because Windows for Workgroups prompts you for a case-sensitive

password when loading, you must enter your password before holding down

the SHIFT key to disable the Startup group.

If warnings or error messages appear after you type your password,

respond appropriately while holding down the SHIFT key.

NOTE: Since Windows for Workgroups checks to see if the SHIFT key has

been pressed immediately after the logon prompt, you may need to press

the SHIFT key while you press OK or ENTER in response to that prompt.

Then continue to hold down the SHIFT key to prevent starting applications.

Additional reference words: 3.1 3.10 wfwg err msg


Add/Remove Components Does Not Delete INI Files

Article ID: Q89355

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows operating system version 3.1

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

---------------------------------------------------------------

SUMMARY

=======

You can use the Windows version 3.1 Setup program to add or remove

selected Windows components that are being run within Windows.

However, if you remove components that created .INI files (such as

Mail version 3.0 and Schedule+ version 1.0), the associated .INI files

are not deleted.

MORE INFORMATION

================

After you remove a Windows component, you should back up, then delete

the associated .INI file. This ensures that when the component is

added back into Windows, it installs with defaults.

You do not need to delete the .INI file when you replace corrupt .EXE

or .HLP files for a component.

Additional reference words: WFWG MAIL Schedule


Functionality of NET STOP /Y Command in WFWG

Article ID: Q89356

---------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

---------------------------------------------------------------

SUMMARY

=======

To unload the real mode redirector, log off from workgroup services,

and disconnect from the currently connected servers, type the

following at the MS-DOS command prompt:

   net stop /y

The /Y switch allows you to perform the above functions without having

to provide any input.

MORE INFORMATION

================

To connect to available network servers from MS-DOS and load the

workgroup software for MS-DOS (real mode redirector), type ONE of the

following at the MS-DOS command prompt:

 - net start workstation

 - net start basic

 - net start full

VSERVER.386 is the server VxD. A computer can still be a server after

executing the NET START WORKSTATION command in 386 enhanced mode, but

it cannot be a browse master. Browse service requires the virtual

redirector (VREDIR.386) to load the browse service (VBROWSE.386).

Typing "net stop" (without the quotation marks) unloads the real-mode

redirector and the following prompts appear:

   You are currently logged on as <user name>

   Do you want to log off? (Y/N)[N]:

If you have existing connections and you respond "Y," the following

message appears:

    Continuing will cancel these connections:

   "device=\\server\share"

   Do you want to continue this operation? (Y/N)[N]:

If you respond "Y," the following displays:

   <user name> was logged off successfully.

   Command completed successfully.

If you type "net stop /y" (without the quotation marks), the above two

prompts default to a response of "Y" and you are not required to

respond.

Additional reference words: 3.10 wfwg 3.1 real mode


Serial Network Connections Not Supported in WFWG

Article ID: Q89481

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

----------------------------------------------------------------------

Serial interfaces for network connections are not supported in

Microsoft Windows for Workgroups. Using modems for network connections

is also unsupported.

Windows for Workgroups is designed for peer-to-peer networking.

Compatible network cards must be used for network functionality.

This feature may be implemented in future versions of Windows for

Workgroups.

Additional reference words: 3.1 3.10 wfwg


NET START WORKSTATION Command AutoStart= Switch in WFWG

Article ID: Q89482

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

 - Microsoft Workgroup Connections version 1.0

----------------------------------------------------------------------

SUMMARY

=======

Workgroup Connections workstation services may run either the basic or

full redirector.

Type the following to load full workstation services (full services

are the default):

   net start workstation

-or-

   net start full

Type the following to load the basic redirector services:

   net start basic

You can change the default workstation service to basic by adding the

entry AutoStart=Basic in the [Network] section of the SYSTEM.INI file.

MORE INFORMATION

================

The full redirector differs from the basic redirector in that it

allows named-pipe support and full LAN Manager API support.

The AutoStart= entry specifies which network terminate-and-stay-

resident (TSR) programs are loaded when the NET START command is

issued with no arguments. By default, this performs only a NETBIND to

complete loading of protocols and adapter drivers. If a later NET

command requires loading of a redirector, the full redirector is

loaded by default.

If, however, you change the entry to AutoStart=Basic as the Workgroup

Connections installation program does, the NET START command placed in

your AUTOEXEC.BAT file starts the basic redirector. When the

redirector loads, the NetBEUI TSR also loads (if you don't already

have a NetBIOS protocol present).

Other NET START options include:

   NET START [{POPUP | BASIC | FULL | WORKSTATION | NETBIND |

   NETBEUI}] [/LIST] [/YES]

   POPUP           Loads the pop-up interface into memory.

                   Use this option if the pop-up interface

                   is not automatically loaded each time you

                   start your computer.

   BASIC           Starts the basic redirector.

   FULL            Starts the full redirector.

   WORKSTATION     Starts the default redirector.

   NETBIND         Binds protocols and network card drivers.

   NETBEUI         Starts the NetBIOS interface.

   /LIST           Displays a list of the Workgroup Connection

                   components that have been started.

   /YES            Carries out the NET START command without

                   first prompting you to provide information or

                   confirm actions.

This entry takes a comma-separated list; for example

   AutoStart=NETBEUI,BASIC,POPUP

causes the indicated three services to start when NET START is issued

from AUTOEXEC.BAT.

Additional reference words: 3.10 wfwg 3.1 named pipe wc


Print Manager Status Bar Reports Share Name Information

Article ID: Q89483

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

----------------------------------------------------------------------

SUMMARY

=======

Under Microsoft Windows for Workgroups, the Print Manager status bar

for a shared printer may report a different printer name than the

default printer name.

You can correct this by changing the Comment field in the Share

Printer As dialog in Print Manager, on the Workstation that is sharing

the printer.

MORE INFORMATION

================

When running Windows for Workgroups in 386 enhanced mode, you can

share a local printer that is physically connected to your computer

with others on the network. When sharing a printer in Print Manager

the status bar may show a different printer name than the default

printer.

For example, if a Hewlett-Packard (HP) LaserJet IIIsi is being shared,

but you type HP LaserJet II in the comment field in the Share Printer

As dialog in Print Manager. The Print Manager status bar will show HP

LaserJet II.

Steps to Resolve the Problem

----------------------------

1. From the Main group, start Print Manager.

2. From the Printer menu, choose Share Printer As.

3. Type the user defined printer name in the Comment field. (This is

   what will appear as the printer name on other computers.)

4. Choose the OK button.

Additional reference words: 3.10 wfwg 3.1


GP Fault in Mail for Workgroups May Suppress Password

Article ID: Q89484

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

----------------------------------------------------------------------

SYMPTOMS

========

If you receive a general protection (GP) fault in Windows for Workgroups

Mail, neither Mail nor Schedule+ will prompt you for a password until

Windows for Workgroups is restarted. This does not apply to Microsoft Mail

version 3.0 or Schedule+ version 1.0.

STATUS

======

Microsoft has confirmed this to be a problem in Windows for Workgroups

version 3.1 and version 3.11. We are researching this problem and will post

new information here as it becomes available.

MORE INFORMATION

================

You can reproduce the problem by adding a custom command that calls an

inappropriate dynamically linked library (.DLL) in the MSMAIL.INI file in

Mail for Workgroups.

Steps to Reproduce Problem

--------------------------

1. Exit and sign out from Mail.

2. Edit the MSMAIL.INI file in the WINDOWS directory.

3. Add the following line to the [Custom Commands] section. This adds

   the Icon option to the File menu, but references the MORICONS.DLL

   file incorrectly:

      Icon=3.0;File;$Icon;13;moricons.dll;1;;

   (MORICONS.DLL can be replaced with another DLL such as PBRUSH.DLL;

   either will cause a GP fault).

4. Save the MSMAIL.INI file, then restart Mail.

5. From the File menu, choose Icon. A GP fault appears. Choose the

   Close button, then choose the OK button.

6. Mail stops at this point.

7. Restart Mail. (No password is required.)

8. From the File menu, choose Exit and Sign Out.

9. Restart Mail. (No password is required.)

This continues until Windows for Workgroups is restarted.

Additional reference words: 3.10 wfwg msmail


Accessing Microsoft LAN Manager Servers with WFWG

Article ID: Q89517

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

----------------------------------------------------------------------

SUMMARY

=======

Windows for Workgroups (WFWG) enables you to connect to and use files,

directories, and printers that are shared on a Microsoft LAN Manager

server. In addition, if you use LAN Manager, you can connect to and

use the resources shared on Windows for Workgroups machines.

To browse a LAN Manager server appearing in the Windows for Workgroups

Connect Network and Connect Network Printers dialog boxes, 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.

MORE INFORMATION

================

Use Control Panel to set options for LAN Manager. Options include logging

onto a LAN Manager domain when logging into Windows for Workgroups, and

changing passwords for various LAN Manager servers and domains. (Logon

scripts run when your LAN Manager password is validated by the logon

server.)

Setting LAN Manager Options

---------------------------

To set LAN Manager options, do the following:

1. In the Control Panel window, double-click the Network icon, or use

   the arrow keys to select the Network icon, and then press ENTER.

2. Choose the Networks button.

3. If Microsoft LAN Manager appears in the Other Networks In Use list,

   select it and then choose the Settings button.

   If Microsoft LAN Manager is not in the Other Networks In Use list

   select it and then choose the Add button. If a dialog box appears

   asking you to insert a disk, insert the disk and choose the OK button.

   Then choose the Settings button in the Network Settings dialog box.

4. If you want to log on to a LAN Manager domain when you log on to

   Windows for Workgroups, select the Log On To LAN Manager Domain

   check box and then type the name of the domain you want to log on to

   in the Domain Name box.

5. If you want to change your passwords for LAN Manager servers or

   domains, choose the Set Password button.

6. In the LAN Manager Settings dialog box, choose the OK button.

7. In the Compatible Networks dialog box, choose the OK button.

8. In the Network Settings dialog box, choose the OK button.

A message appears prompting you to restart Windows. Choose the Restart

Windows button for your changes to take effect.

If you select the Log On To LAN Manager Domain option when you start

Windows for Workgroups, a dialog box appears asking you to type your

password for the domain. (You can also specify a different domain to

log on to.) If you do not want to be prompted for your domain password

eac h time you start Windows for Workgroups, select the Save This

Password In Your Password List check box.

NOTE: You can also use the LMAnnounce= parameter if you have existing

LAN Manager clients that need to see a WFWG server (for example, a

print server) in the server lists under Windows or from the NET VIEW

command.

REFERENCES

==========

"Microsoft Windows for Workgroups User's Guide," Appendix B

Microsoft Windows for Workgroups Resource Kit

Additional reference words: 3.10 wfwg lm


WFWG and Novell: LASTDRIVE=Z Makes [ and ] Active Drives

Article ID: Q89558

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

----------------------------------------------------------------------

SYMPTOMS

========

The following symbols may appear as NetWare login drives when Novell

NetWare Connectivity is loaded in Windows for Workgroups if the line

LASTDRIVE=Z exists in the CONFIG.SYS file:

  "[" and "]"

CAUSE

=====

Setting LASTDRIVE=Z conflicts with Novell NetWare defaults and NetWare

is unable to set up a valid login drive.

WORKAROUND

==========

To resolve the problem, change the line to LASTDRIVE=P, instead of Z.

MORE INFORMATION

================

The value of the LASTDRIVE statement is set to P by default when

Novell NetWare connectivity is loaded in Windows for Workgroups. The

LASTDRIVE statement specifies the range of drive letters you can use

for connecting to other Windows for Workgroups computers. For example,

if your LASTDRIVE is set to P you can use letters from A to P to

connect to other Windows for Workgroups computers.

If you set up Novell NetWare connectivity, the letter that follows the

LASTDRIVE value is your login drive. (This is because Novell uses

LASTDRIVE +1.) For example:

 - If LASTDRIVE=P, then your login drive is Q. Although you can use

   any letter to connect to NetWare directories, letters after the

   value of the LASTDRIVE statement (that is drives after P) are

   reserved for NetWare directories only.

 - If LASTDRIVE=F, then your login drive is G and drives after F

   are unavailable for connecting to other Windows for Workgroups

   computers.

NOTE: If your login script(s) has been set up to use drive F as the

login drive, setting LASTDRIVE=P may result in errors during boot up.

To resolve those errors, change you login script(s) to reflect the

login drive change, or change LASTDRIVE to E. Please note these

limitations:

 - If you set LASTDRIVE to E and your users have machines with

   single hard drives (C), you are limiting them to 2 network

   connections (D and E).

 - If you set LASTDRIVE to E, and your users have local hard

   drives with only 2 partitions (C and D) and a CD-ROM drive

   (E), they cannot establish any network connections.

The Novell NetWare product included here is manufactured by a vendor

independent of Microsoft; we make no warranty implied or otherwise

regarding these products' performance or reliability.

Additional reference words: 3.10 wfwg novel last drive


Cannot Browse LAN Manager 1.x Servers in WFWG

Article ID: Q89559

---------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

 - Microsoft Workgroup Connections version 1.0

---------------------------------------------------------------

SUMMARY

=======

Windows for Workgroups (WFWG) computers are unable to browse (view)

LAN Manager 1.x server names in the Connect Network Drive, Connect

Network Printer, and Select Computer dialog boxes. In addition, you

cannot view servers in Workgroup Connections by using the NET VIEW

\\Servername command.

This is because LAN Manager 1.x does not use domains.

MORE INFORMATION

================

LAN Manager version 2.0 was the first version to create domains for

groups of users. Because LAN Manager 1.x does not use domains, Windows

for Workgroups cannot tell that domains exist unless explicitly told.

To access LAN Manager 1.x servers in Windows for Workgroups, manually

type the path to the network resource in the dialog box.

Additional reference words: 3.10 wfwg lm wc


WFWG: LAN Architecture Cable Specifications

Article ID: Q89708

---------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

---------------------------------------------------------------

SUMMARY

=======

This article contains information on the basic cable types, lengths,

and other limitations of various network configurations.

MORE INFORMATION

================

The following charts outline the minimum standards required to conform

to the IEEE specifications for network architecture.

ETHERNET (IEEE 802.3)

---------------------

                        Thinnet         Thicknet        Twisted-Pair

                        (10Base2)       (10Base5)       (10BaseT)

Topology                Local Bus       Bus             Star

Cable Type              RG-58           Thicknet        Unshielded

                        3/8" Shielded   Twisted-Pair    Twisted-Pair

Impedance               50 Ohm          50 Ohm          -

Terminator              50 Ohm          50 Ohm          85-115 Ohm UTP

Resistance              +- 2 Ohm        +- 2 Ohm        135-165 Ohm TP

Maximum Cable           185 Meters      500 Meters      100 Meters

Segment Length          (c. 606 ft)     (c. 1640 ft)    (c. 328 ft)

Minimum Distance        0.5 Meters      2.5 Meters      2.5 Meters

Between Nodes           (c. 23 inches)  (c. 8 ft)       (c. 8 ft)

Maximum No. Connected   5               5               Not supported

Segments                                                in star

                                                        configuration

Maximum No. Connected

Computers/Segment       30              100             N/A

TOKEN RING (IEEE 802.5)

-----------------------

Topology                        Star

Cable Type                      Shielded or Unshielded

Twisted Pair

Terminator                      100-120 Ohm UTP

Resistance                      150 Ohm TP

Maximum Cable                   45-200 Meters

Segment Length                  (c. 148-656 ft)

Depending on Cable type

Minimum Distance                2.5 Meters

Between Nodes                   (c. 8 ft)

Maximum No. Connected           33 Multistation

Segments                        Access Units (MAU's)

Maximum No. Connected           UTP 72 per concentrator

Computers/Segment               TP 260 per concentrator

ARCNET

------

Topology                        Series of Stars

Cable Type                      RG-62 or RG-59

Terminator                      RG-59: 75 Ohm

Resistance                      RG-62: 93 Ohm

Maximum Cable   (on average)    W-W: 120 M (393 ft)

Segment Length                  A-A: 606 M (1988 ft) Max

                                A-A: 0.3 M (1 ft) Min

                                P-W: 30 M (98 ft)

                                P-A: 30 M (98 ft)

                                NOTATION:

                                W=Workstation

                                A=Active Hub

                                P=Passive Hub

                                Note: Unused passive hub ports must be

                                terminated.

Minimum Distance                Varies with Cable

Between Nodes

Maximum No. Connected           Not supported

Segments

Maximum No. Connected           Varies with Cable

Computers/Segment

Additional reference words: 3.1 3.10 3.11 wfwg


Wang's WINLOC Interface May Hang Windows for Workgroups

Article ID: Q89782

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

----------------------------------------------------------------------

SUMMARY

=======

Wang's WINLOC program causes Windows for Workgroups to stop responding

(hang) when you attempt to communicate with the Wang VS network.

CAUSE

=====

The WINLOC program is a driver/protocol configuration that is designed

to work specifically with the Wang WLOC network card. WINLOC takes

preemptive control of the network interface card, which puts it in

conflict with the Windows for Workgroups network redirector.

There is no workaround at this time.

The products included here are manufactured by vendors independent of

Microsoft; we make no warranty, implied or otherwise, regarding these

products' performance or reliability.

Additional reference words: 3rdparty 3.10 Sparta Peer wfwg


Zenith Znote Does Not Resume Net Operation When Paused

Article ID: Q89833

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

SYMPTOMS

========

Zenith Data System Znote 386 laptops models 320L, 325L, and 325Lc may

lose all network connections if they  enter stand-by mode while

running in MS-DOS or Windows.

RESOLUTION

==========

To resolve the problem, increase the stand-by timer value, or

reconnect network drives after they are lost.

You can set the timer to any time between one minute and three hours.

MORE INFORMATION

================

With stand-by mode there is a timer set within the system that detects

absence of activity and automatically stops the CPU clock, shuts off

the video subsystem and allows the hard disk motor to spin down. This

laptop feature helps to extend the batteries' life span.

Znote stand-by mode functions as follows:

 - The Znote does not enter stand-by mode when connected to AC power.

 - The system always enters stand-by mode if you close the lid while

   the unit is running on battery power.

 - The unit also enters stand-by mode if you press FN+F6.

 - If the unit enters stand-by mode, you generally need to reboot it

   to resume normal functions.

All Znote models include network cards and pre-installed network

client shells for Microsoft LAN Manager, Novell NetWare, and Banyan

VINES.

For further information, contact the Zenith Customer Assistance Center

at (800) 227-3360 between 7 AM and 7 PM Central time, Monday through

Friday.

The Zenith Znote computers included here are manufactured by vendors

independent of Microsoft; we make no warranty implied or otherwise,

regarding these products' performance or reliability.

Additional reference words: 3.10 3.1 wfwg z-note z note standby stand

by


System Hangs with ASPI4DOS.SYS Version 3.0 or Earlier

Article ID: Q89836

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows operating system version 3.1

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

----------------------------------------------------------------------

SYMPTOMS

========

When you use Adaptec's ASPI4DOS.SYS driver versions 3.0 or earlier, you may

experience problems executing File Manager within Microsoft Windows for

Workgroups or Microsoft Windows 3.1. After you start File Manager, the

cursor may remain as an hourglass and the system may subsequently stop

responding (hang).

Your system may also stop (hang) when you attempt to save files.

CAUSE

=====

Adaptec's 1542B SCSI controller card requires ASPI4DOS.SYS driver version

3.0a or later to operate correctly with version 3.1 of Microsoft Windows or

Windows for Workgroups.

ASPI4DOS.SYS, version 3.0, works correctly with Microsoft Windows version

3.0.

RESOLUTION

==========

You need to obtain an updated driver from Adaptec. The file name is

UPGRADE.EXE.

MORE INFORMATION

================

If you attempt to share a CD-ROM drive on a Windows for Workgroups machine,

and you experience frequent system hangs, VSERVER errors or general

protection (GP) faults, check your ASPI4DOS.SYS driver. It may be too new

for your system BIOS.

ASPI4DOS.SYS drivers dated later than 6/91 have trouble with some versions

of system BIOS.

For more information on ASPI4DOS.SYS, contact Adaptec technical support.

The Adaptec product included here is manufactured by a vendor independent

of Microsoft; we make no warranty, implied or otherwise, regarding this

product's performance or reliability.

Additional reference words: 3.10 3.11 lockup hang wfwg win31


System May Not Boot after Installing Intel Ether Express

Article ID: Q89842

---------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

---------------------------------------------------------------

SYMPTOMS

========

Some revisions of the Intel Ether Express 16 may conflict with Trident

or TSENG Labs video cards. This may prevent the system from booting or

may cause it to boot without video capability.

CAUSE

=====

Intel has confirmed that this hardware conflict occurs when its

network card and a VGA card, both of which have a capacitor on the

reset line, are used on motherboards that cannot manage multiple

capacitors on the reset line. Intel has removed the capacitor from its

cards to eliminate this problem.

MORE INFORMATION

================

To identify the Intel cards that may cause this problem, look at the

last five digits of the serial number for the card. This eleven-digit

number can be found on the box or on the bar code label on the card

itself.

The last five digits of the serial number are in the format WWYSS,

where "WW" indicates the work week number, "Y" indicates the year, and

"SS" indicates the manufacturing site number.

The following cards have a capacitor on the reset line and may cause

the above behavior:

   If YSS=207, then WW must be less than 20.

   If YSS=213, then WW must be less than 25.

   If YSS=212, then WW must be less than 21.

Additional reference words: 3.1 EE16 SVGA TVGA 8800 8900 ETHEREXPRESS


Toolbar Buttons Extend Beyond the Toolbar in File Manager

Article ID: Q89880

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

----------------------------------------------------------------------

SYMPTOMS

========

When you customize the toolbar in File Manager, some buttons may extend to

the right beyond the edge of the File Manager window and become

inaccessible.

CAUSE

=====

This most often occurs if you use Windows for Workgroups at lower video

resolutions. At lower resolutions you may not be able to use all of the

icons available for the toolbar because they extend into an inaccessible

area of File Manager.

STATUS

======

Microsoft has confirmed this to be a problem in Windows for Workgroups

version 3.1 and 3.11 QWIII.DRV. We are researching this problem and will

post new information here as it becomes available.

RESOLUTION

==========

There is no workaround for this problem. You can avoid the problem by

maximizing File Manager to determine the maximum number of toolbar icons

that you can have.

MORE INFORMATION

================

Steps to Reproduce Problem

--------------------------

1. Install the VGA driver that is provided with Windows for

   Workgroups.

2. From the Main group, start File Manager.

3. From the Options menu, choose Customize Toolbar.

4. Choose the first button in the Available Buttons list, then choose

   the Add button.

5. Continue with step 4 until the Available Buttons list is empty,

   then choose the Close button.

6. Maximize File Manager and note that all the toolbar icons cannot be

   accessed.

Additional reference words: 3.10 3.11 wfwg


WinMeter Abnormally High with Some Programs

Article ID: Q89881

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

---------------------------------------------------------------

SUMMARY

=======

The WinMeter application that comes with Windows for Workgroups may

report abnormally high CPU activity when some programs are run,

including the following programs:

   - MS-DOS virtual machine (VM) (that is, COMMAND.COM)

   - POINTER.EXE from the Microsoft Mouse software

   - Norton Desktop for Windows

These programs make it appear that the system is busier then it really

is. Try disabling the program(s), then check WinMeter again.

MORE INFORMATION

================

WinMeter reports CPU performance by monitoring CPU idle cycles. If a

program does not allow the CPU to return to idle after issuing an

instruction, WinMeter shows higher levels of activity than normal.

One such application is COMMAND.COM. Keyboard polling in MS-DOS

creates an instructional loop that causes the CPU to rarely return to

a completely idle state. The behavior of WinMeter is therefore

determined by the applications that are running on the system. This

behavior is normal and expected. WinMeter is merely reporting the

behavior of the applications.

Steps to Reproduce Problem

--------------------------

1. Start Windows in 386 enhanced mode.

2. From the Accessories group, start WinMeter.

3. From the Main group, start MS-DOS Prompt.

4. Press ALT+ENTER to create an MS-DOS window.

5. WinMeter shows higher activity, possibly as high as 100 percent. It

   remains that way while the MS-DOS window is the active window.

Changing the foreground and background priority values of the MS-DOS

command prompt and the Exclusive execution option has no effect on the

program's behavior.

However, if you do select the MS-DOS virtual machine to run in the

background, WinMeter shows higher than normal activity whenever the

MS-DOS window is maximized but not highlighted, as well as minimized

and highlighted.

Additional reference words: 3.10 Max 3.1 wfwg ndw 3rdparty win meter


Setting Up a Postoffice Across the Network

Article ID: Q89895

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

----------------------------------------------------------------------

SUMMARY

=======

With Windows for Workgroups Mail, the Workgroup Postoffice can be set

up from one computer to another computer across the network.

MORE INFORMATION

================

Assume the following in this example of a remotely created and

administered Workgroups Postoffice:

 - 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 Post Office 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. For more

   information, query on the following in the Microsoft Knowledge

   Base:

      Novell and Netware and Server and WGPO

After Windows for Workgroups setup is complete on machine 1, the

designated administrator of the Workgroups Mail 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

   the OK button.

   NOTE: You must have access rights to the \\server\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 using one of these conventions:

      server/share:directory

      \\server\share\directory

      remapped drive:\directory

   For more information on the Novell naming conventions, check

   your Novell NetWare documentation.

4. After the Workgroup Postoffice has been created, check to ensure

   that the postoffice is shared properly on machine 2.

Additional reference words: 3.10 3.1 wfwg novel wgpo post office


Net Watcher: Lines in Share Name When Scrolled

Article ID: Q89973

------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

------------------------------------------------------------

SYMPTOMS

========

In Net Watcher, vertical lines appear in the share name when you

scroll the share window and when the client window is active. If you

enlarge the client window (on the left) so that the share window (on

the right) cannot display a full share name, scroll bars appear. If

you have a client name selected when you scroll the share window,

vertical lines appear, drawn through the share name. The same is true

for the client window if the share window is enlarged and active.

STATUS

======

Microsoft has confirmed this to be a problem in Windows for

Workgroups Net Watcher version 3.1 and version 3.11.

We are researching this problem and will post new information here as

it becomes available.

Additional reference words: 1.00 wfwg


Print Manager Help Error: Cannot Use CTRL+UP ARROW

Article ID: Q89977

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

SYMPTOMS

========

Using the CTRL+UP ARROW and CTRL+DOWN ARROW key combinations do not

allow you to change the order in which the documents print.

The "Changing Document Order" section in Print Manager Help

incorrectly states these key combinations allow you to change the

order in which the documents prints.

STATUS

======

Microsoft has confirmed this to be a problem in Windows for Workgroups

Print Manager Help version 3.1 and version 3.11

We are researching this problem and will post new information here as

it becomes available.

Additional reference words: 3.10 docerr wfwg


Artisoft NE3 Network Card Compatibility

Article ID: Q90123

----------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

----------------------------------------------------------------

The following article contains information on the use of 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.

SUMMARY

=======

Windows for Workgroups does not include an adapter choice for the

Artisoft NE3 8-bit Network card. However, the card can emulate a

Western Digital (SMC) 8003, 8-bit network card. There are no physical

changes to the card (jumpers) necessary for emulation.

MORE INFORMATION

================

The Artisoft NE3 network card is an earlier model and has been out of

production for several years. The configuring software (NE3.EXE) can

provide useful information about the card settings. This information

can be seen by typing "NE3 ?" (without the quotation marks) from the

MS-DOS command line in the NE3 directory.

Important settings for the card include:

 -Interrupt (labeled J10)

  Available interrupts=2/3/4/5/6/7

  Default interrupt=3

 -RamBase (Software configurable)

  Default=D000

 -I/O Base (Labeled J1)

  Default=280

For more information regarding the Artisoft NE3 network card, please

contact Artisoft technical support.

Additional reference words: 3.10 wfwg


WFWG Err Msg: Invalid or Missing COMMAND.COM

Article ID: Q90197

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

SYMPTOMS

========

If your AUTOEXEC.BAT file sets the path to COMMAND.COM using a SET

COMSPEC= statement after the NET START command, then the NET START

command may fail with the following error message and your machine

may stop responding (hang):

   invalid or missing command.com

NOTE: This problem DOES NOT occur if COMMAND.COM is in the root

directory.

CAUSE

=====

You can set the path to COMMAND.COM with a SHELL= statement in the

CONFIG.SYS file or the COMPSPEC= statement in the AUTOEXEC.BAT file.

The NET START command fails only when the path to COMMAND.COM is set

via SET COMSPEC=, not SHELL=. This is more of a problem with MS-DOS

version 4.0, which automatically installs the SET COMPEC= statement in

the AUTOEXEC.BAT file, and with OEM versions of MS-DOS which do not

put COMMAND.COM in the root directory.

WORKAROUND

==========

To fix this problem, restart your computer using a startup (boot)

disk in drive A, and edit the CONFIG.SYS and/or AUTOEXEC.BAT files.

Move the SET COMSPEC= line so that it is above the NET START command,

or remove the SET COMSPEC= statement and use the SHELL= line in the

CONFIG.SYS file.

Additional reference words: 3.10 hang hung locked freeze frozen


WC Mail Defaults to Two Lines Per Page When Printing

Article ID: Q90214

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Workgroup Connections version 1.0

--------------------------------------------------------------------

SUMMARY

=======

When you print a mail message from Workgroup Connections Mail, only

two lines print per page because the default number of lines per page

is two.

WORKAROUND

==========

To change the number of lines printed per page, choose Configuration

from the Print menu, choose Lines, and change the number of lines

printed per page to 58.

STATUS

======

Microsoft has confirmed this to be a problem in Workgroup Connections

Mail version 1.0.

We are researching this problem and will post new information here as

it becomes available.

Additional reference words: 3.10 1.0 wfwg wc


Shared Folder Icons (Hands) can Disappear in WFWG

Article ID: Q90232

--------------------------------------------------------------------

The information in this article applies to:

 -  Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

SYMPTOMS

========

The list of current share names, passwords and comments is stored in a

cache or buffer. If you share a large number of resources, the size of the

share list exceeds the buffer size, dumping the list entirely. This results

in shared folder icons (with hands) reverting to standard folder icons (no

hands) in both the main File Manager directory listing and Connect dialog

box. Also, the share confirmation dialog box no longer appears when you

remove or rename a shared resource.

STATUS

======

Microsoft has confirmed this to be a problem in Windows for Workgroups

File Manager version 3.1 and version 3.11. We are researching this problem

and will post new information here as it becomes available.

Additional reference words: 3.10 disappears unavailable no wfwg


How Does WFWG Upgrade from LAN Manager 2.1?

Article ID: Q90257

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

SUMMARY

=======

Windows for Workgroups  Setup detects if LAN Manager 2.1 is running by

determining whether the LAN Manager redirector is present in memory.

If it is, Setup then tries to upgrade using the information in the LAN

Manager SETUP.INI file.

MORE INFORMATION

================

LAN Manager 2.1 is only detected if it is loaded and running during

Setup. This means that the NET START WORKSTATION command must have

been executed in order for Setup to find it. Setup does not check the

CONFIG.SYS or AUTOEXEC.BAT or any other file to find LAN Manager.

If Setup does find LAN Manager 2.1, it uses the information in the LAN

Manager 2.1 SETUP.INI file to upgrade the configuration to Windows for

Workgroups and to remove the LAN Manager statements from the

CONFIG.SYS and AUTOEXEC.BAT files.

Setup checks the SETUP.INI for the following entries:

   [setup]

   DRIVER0 = card protocol [protocol [protocol [protocol]]]

   DRIVER1 = card protocol [protocol [protocol [protocol]]]

   DRIVER2 = (etc.)

It then uses the [netcard] and [transport] sections in LM21DRV.UPD to

map the LAN Manager driver names to Windows for Workgroups driver

identification numbers. A new PROTOCOL.INI is created using the mapped

drivers. The settings for the drivers are copied from the LAN Manager

PROTOCOL.INI file.

If a mapping does not exist for a driver in SETUP.INI, Setup will warn

the user that the driver could not be upgraded and the driver will be

skipped. The user will have to add this device back by hand using the

Control Panel, which may require the use of Windows for Workgroups

compatible original equipment manufacturer (OEM) disks.

Setup uses the the [ConfigSys] and [StartupCmd] sections in SETUP.INI

file to delete any lines from the CONFIG.SYS and AUTOEXEC.BAT files

that LAN Manager added. If the user has modified any of these lines so

that they no longer match the lines in the SETUP.INI file, they might

not be deleted. Setup also deletes any lines from the AUTOEXEC.BAT

file that contain these phrases: LOAD NETBEUI, LOAD TCPIP, NET START,

NET LOGON, or NET LOGIN.

Additional reference words: 3.10 lanman wfwg


Upgrading from Workgroup Connections to WFWG with OEM Drivers

Article ID: Q90258

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

 - Microsoft Workgroup Connections version 1.0

--------------------------------------------------------------------

If Windows for Workgroups Setup detects a Workgroup Connections

installation, it does not attempt to detect any network information,

but instead copies the information in the PROTOCOL.INI file.

All references to Workgroup Connections drivers and files are replaced

with Windows for Workgroups references. All Workgroup Connections

files are included with Windows for Workgroups, so this presents no

problem except in the case of original equipment manufacturer (OEM)

drivers. Windows for Workgroups Setup does not copy or preserve any

OEM drivers. If OEM drivers were used in the Workgroup Connections

installation, you need to use the OEM disks containing the necessary

drivers during the Windows for Workgroups installation or run Control

Panel after Windows for Workgroups installation.

Additional reference words: 3.10 3.11 wfwg wc


Running NetBIOS Over DECnet Protocol

Article ID: Q90260

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

The following article contains information on the use of 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.

SUMMARY

=======

When Windows for Workgroups is configured for DECNet Protocol on Lana

0, and NetBEUI on Lana 1, running NetBIOS applications on Lana 0 may

require that you increase the NETHEAPSIZE= entry [386Enh] section of

the SYSTEM.INI file.

MORE INFORMATION

================

The default setting is NETHEAPSIZE=20. You may have to increase it to

a value greater than 24. Try incrementing this value by 10 or 20 until

your NetBIOS application behaves correctly.

DECNet is manufactured by a vendor independent of Microsoft; we make

no warranty, implied or otherwise, regarding this product's

performance or reliability.

Additional reference words: 3.10 3.11 wfwg dec network


NetWare Printing in Windows for Workgroups

Article ID: Q90269

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

In general, Microsoft Windows for Workgroups Print Manager extends the

printing capabilities from those in Microsoft Windows version 3.1. In

the case of NetWare printers, the capabilities are much the same as in

Windows 3.1. Only the jobs submitted by the user are shown, and jobs

may be paused, resumed, or deleted. These actions can be done from the

document menu or the appropriate buttons on the toolbar.

The NetWare product included here is manufactured by Novell, a vendor

independent of Microsoft; we make no warranty, implied or otherwise,

regarding this product's performance or reliability.

Additional reference words: 3.10 3.11 net ware tool bar wfwg novel


Password Caching in Windows for Workgroups

Article ID: Q90271

-------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

-------------------------------------------------------------------

SUMMARY

=======

In Windows for Workgroups, password caching is a feature that maintains a

list of the passwords you have used and the resources to which they apply.

Passwords are saved and retrieved transparently to the user. The password

cache facilitates restoration of connections to shared resources when you

log on.

This article describes the functionality of file caching in Windows

for Workgroups.

MORE INFORMATION

================

Password List File

------------------

When you log on to Windows for Workgroups, the network driver looks up your

username in the [Password Lists] section of SYSTEM.INI. This entry gives

the path to your password list file (PWL), which is encrypted to maintain

system security. Part of this file is decrypted using your logon password.

If the decryption is successful, your password cache file is unlocked. When

you log off, the password to your PWL file is erased from memory.

If there is no SYSTEM.INI entry for your username, or if the file named

there doesn't exist, a new PWL file is created for you, initially with no

passwords in it. Windows for Workgroups asks you to confirm your logon

password before it encrypts your PWL file.

When you need to establish a connection to a network resource (either

explicitly, from the Connect dialog box, or implicitly, at logon), the

network driver first attempts to make the connection with a blank password.

If the resource requires a password, the network driver then searches your

PWL file for an entry corresponding to the resource to which you are

connecting. That password is used on the next attempt to make a connection.

If there is no entry in the file for the resource, or if the password

recorded in the file is not correct (if, for example, the owner of the

server changed the password), a password prompt is displayed.

Whenever a password prompt is displayed, and the password you type turns

out to be the correct one for the resource, it is saved in your PWL file

for later use. If the server is running with share-level security (this

applies to Windows for Workgroups servers and to some Microsoft LAN Manager

servers), the server name and share name are recorded in the PWL file. If

the server is running with user-level security, the password you used works

for any share on that server, so a separate record containing only the

server name is created.

Additionally, if you choose to have your logon validated at a LAN Manager

domain controller, your LAN Manager logon password is stored in your PWL

file also, so that the only logon password you need to type is the one that

encrypts the PWL file.

NOTE: If a Windows for Workgroups client belongs to a workgroup and a

domain, and is using the same password (which may be cached) to logon, a

problem may occur if the passwords expire at different times and are no

longer synchronized. This can occur if the Windows for Workgroups

administrator enforces password changing (also called "aging"). The user is

prompted to change the workgroup password, but not the domain password.

When the domain password eventually expires, the user may not be able to

remember it and may not be able to logon to the domain.

How to Prevent the Saving of a Password in your PWL File

--------------------------------------------------------

Sometimes you may not want Windows for Workgroups to save a password. To

prevent the saving of a password, clear the Save This Password In Your

Password List option in the Enter Network Password dialog box. Next time

Windows for Workgroups attempts to connect to this resource, another

password prompt appears.

If you connect from the MS-DOS prompt (using the NET USE command), use the

/SAVEPW:NO option to prevent Windows for Workgroups from recording the

password in the PWL file.

If you connect without saving the password, Windows for Workgroups does not

add the password to your PWL file, but it does not delete the password if

it's already in the PWL file.

PWL File Limits

---------------

Windows for Workgroups does not limit the length of time a password

remains valid. The PWL file is limited to 255 password entries. Once

there are 255 entries in the PWL file, adding another password causes

Windows for Workgroups to delete the oldest password. Each time a

password entry is used to make a connection, it's marked as the

"newest" entry, so frequently-used passwords are not the first

candidates for removal.

Password Caching Does Not Work When You Connect Using a UNC Name

----------------------------------------------------------------

If you try to open a file on a password-protected share by typing the UNC

name, password caching is not activated, so Windows for Workgroups cannot

make later connections for you. This happens because password caching is

done by the network driver, at the user interface (UI) level (the UI level

is where most interaction with the password cache occurs in Windows for

Workgroups). To make it possible for password caching to be available in

all circumstances, it would need to be implemented in the redirector

instead of at the UI level. Password caching at the redirector level would

have made Windows for Workgroups more complicated, due to the additional

interfaces, which would result in slower connection time. Password caching

at the redirector level would also increase the amount of memory used by

the basic and full redirectors, leaving less available memory for other MS-

DOS-based applications.

Security of the Windows for Workgroups Password Cache

-----------------------------------------------------

The password list file is encrypted with an algorithm that meets the U.S.

government Data Encryption Standard (DES). This encryption technology is

the highest security allowed in software exported from the United States.

The odds of breaking the encryption algorithm are less than those for

random guesses of what the password might be.

Even if your logon password is blank, Windows for Workgroups generates

seemingly random data in your PWL file, so you cannot discover the

passwords if you look at the PWL file using a file viewer. Currently, no

user interface exists that allows you to unencrypt passwords in the PWL

file, so password caching in Windows for Workgroups is as secure as the

choice of the password used to encrypt your PWL file.

On the other hand, if someone knows that the file is encrypted with a blank

password, they can access the shares for which passwords are cached.

Location of the PWL File

------------------------

Your PWL file can reside on any directory that Windows for Workgroups can

access without a password. If you move your PWL file, you must edit the

[Password Lists] section of your SYSTEM.INI file so it lists the correct

path. If you want to put the PWL file on a network server, there are some

restrictions:

1. Because persistent connections are not restored until after the PWL

   file is open, if the file is to be stored on a Windows for

   Workgroups or LAN Manager server, you must type the path in UNC

   format, such as \\server\share\user\user.pwl (rather than

   x:\user\user.pwl).

2. Because the file is accessed using UNC when it is located on a

   network server, the server or share cannot require a password to

   connect. Additionally, Because the PWL file is not yet open, caching

   the password for the file's location does not help.

3. If you do not have write access to the server, you cannot save any

   new passwords in your PWL file.

REFERENCES

==========

"Microsoft Windows for Workgroups User's Guide," version 3.1, page 144.

Additional reference words: 3.10 universal naming convention win31 wfwg


Print Manager Error Indications in Windows for Workgroups

Article ID: Q90272

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

SUMMARY

=======

In Windows for Workgroups, Print Manager notifies the user of printing

errors differently than in earlier versions of Windows.

MORE INFORMATION

================

Most errors, such as "printer out of paper," no longer are displayed

in a dialog box. This is so print spooling doesn't halt. Instead of a

dialog box, the print queue is marked as being in an "error state." A

descriptive error message displays in the Print Manager status bar.

When the error is corrected, the print queue can be restarted by

choosing Resume Printing Document from the Document menu.

The options for error notification in the Background Printing dialog

box refer to driver specific situations such as a plotter requiring a

pen change. These messages are displayed as configured in the dialog

box.

Additional reference words: 3.10 wfwg


Managing Network Printers in Print Manager and Control Panel

Article ID: Q90274

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

SUMMARY

=======

You can manipulate network printers from either Control Panel or Print

Manager. However, the capabilities provided from these applications

differ greatly. You can perform only some network printer operations

from Control Panel, whereas you can perform all possible operations

from Print Manager.

MORE INFORMATION

================

In Control Panel, the network driver provides only the minimal support

needed for making a new network connection when setting up a printer

for the first time. This is for backward compatibility with Microsoft

Windows version 3.1 and for use when running Windows for Workgroups

Setup. (Note you might not make network connections during Windows for

Workgroups Setup because the Winnet driver is not loaded during

installation.)

Print Manager provides full functionality for printer configuration,

including connecting to and disconnecting from network printers and

managing documents in network print queues.

Some rules apply to the managing of network print queues:

 - On a locally connected printer, regardless of the shared status, any

   print job can be deleted. Print jobs sent across the network can

   only be paused.

 - On a locally connected printer, the topmost (currently printing) job

   cannot be moved. All locally submitted print jobs must remain above

   all network jobs in the queue. Therefore, the topmost network job

   cannot be moved up, and the bottommost local job cannot be moved

   down. At least three local jobs or at least two remote jobs must be

   in a queue before you can reposition any print job. (Note: Queue

   management menu items and buttons are not always dimmed when the

   options fail because of these rules.)

 - On a network (shared) printer, you can only pause and delete your

   own print jobs, and then only before they start printing. You can only

   move your print job down in the queue, and only before it starts

   printing.

Additional reference words: 3.10 wfwg


Network Printing in Windows for Workgroups

Article ID: Q90275

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

SUMMARY

=======

Network printing in Windows for Workgroups is nearly identical to

printing under Microsoft Windows version 3.1. The following

information is based on a default configuration:

 - Print Manager is enabled.

 - Send Documents Directly To Network check box is selected.

 - Background Printing check box is selected.

 - Printing to a Windows for Workgroups server with a shared printer

   resource in enabled.

MORE INFORMATION

================

Printing from an MS-DOS-Based Application

-----------------------------------------

When an MS-DOS-based application writes data to a printer port

connected to a network printer, the network redirector intercepts the

data and sends it across the network to the appropriate server. For

most server types, including Windows for Workgroups and Microsoft LAN

Manager, the server writes the data into a spool file on disk as the

data is received.

Because MS-DOS-based applications do not generally close the port they

print to, the redirector on the client machine decides when the job is

finished based on the amount of time the application has allowed to

elapse without printing. In Windows for Workgroups, if the application

does not print any data for the number of seconds specified by the

PRINTBUFTIME= entry in the [Network] section of SYSTEM.INI (45 seconds

by default), then the redirector assumes the print job is done. Care

is taken so that the time in which the printing application is in a

suspended state within Windows for Workgroups is not counted against

the timeout value.

When the print job is done, the network redirector tells the server to

begin closing it. At this point, the server can close the spool file

and begin sending its contents directly to the printer hardware.

Printing from a Windows-Based Application

-----------------------------------------

When a Windows for Workgroups client prints from a Windows-based

application, Windows (GDI.EXE) passes the application data to the

appropriate printer driver, which converts it into a data stream that

is fully formatted and ready to send to the printer hardware. If

Windows determines that the target printer is a network printer, then

it passes this data to the Winnet driver. The Winnet driver calls the

redirector to send the data to the server, and close the print job

when completed.

Note in both of these cases, the data sent across the network has been

fully formatted for the target printer, and the client computer must

have a printer driver correctly configured for the printing device

attached to the server computer. Once the print job has arrived at the

server, it is sent to the physical printer without modification.

Separator Pages Handled Differently

-----------------------------------

There is an exception to the above information. If a print server is

configured to print a separator page and a job is received from the

network, the server's printer driver is used for the formatting of the

separator page's data. All other formatting is done in advance at the

client machine.

Additional reference words: 3.10 wfwg non-windows 3.11


Path Used for Spool Files for a Shared Printer

Article ID: Q90277

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

SUMMARY

=======

When you share a printer with Windows for Workgroups, there is a

hidden resource associated with the shared printer; this resource is

the directory where temporary spool files are stored when clients

print to the printer. Windows for Workgroups uses the directory

indicated by the TEMP environment variable.

MORE INFORMATION

================

If you select the Reshare At Startup check box, making a print share

persistent, the current value of the TEMP environment variable is

recorded along with the share information in the SHARES.PWL file. If

you subsequently change the value of TEMP, the share still uses the

old path. To start using a new path, you must stop and restart the

printer share.

Because you cannot share redirected devices, you get an error message

if you attempt to share a printer when its port has been redirected to

a network device. If you set your TEMP variable to a network drive,

you get the same error message. In this case, change the TEMP variable

to refer to a local drive.

Additional reference words: 3.10 3.11 wfwg


Two-Password Shares and Password Caching

Article ID: Q90284

-------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

-------------------------------------------------------------------

SUMMARY

=======

Windows for Workgroups permits two levels of access to a shared

directory or ClipBook page:

 - Read-Only Access

 - Full Access

Each type of access may have a password associated with it, and the

type of access granted to a client depends on which password he/she

provides. This article discusses how Windows for Workgroups handles

the password caching for dual-password shares.

MORE INFORMATION

================

Password caching is implemented differently for two-password shares.

If the password typed for a two-password share was cached and

retrieved the same way as other passwords, a client who knows both

passwords would be confined to a single type of access because the

password cache would prevent any further password prompts and

therefore any chance of typing the other password.

When Windows for Workgroups restores a persistent connection to a

two-password share, it is assumed that the last type of access used is

the one desired. If a password for the resource is present in the

cache, Windows for Workgroups uses it and does not prompt you for

input.

If you make an explicit connection (made from the Connect Network

Drive dialog box) to a two-password share, Windows for Workgroups

gives you the option of typing the other password for the resource. If

a password was found in the password cache, it is filled in as a

suggested password to use (it is displayed as asterisks). You can

accept that password or type a different one.

If one of the passwords is blank, Windows for Workgroups still prompts

you for a password. This gives you the opportunity to type the

nonblank password. If you type nothing, Windows for Workgroups

connects you to the share with the blank password.

Additional reference words: 3.10 win31 wfwg


How To: File Handles Open When WFWG Server is Down

Article ID: Q90320

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

SYMPTOMS

========

If a server from which you are editing a file (for example, a Word for

Windows document) is restarted, the file handle(s) associated with the

open file(s) will no longer be valid. If this happens, you may not be

able to continue editing the file(s), and you will not be able to save

them.

The error message you receive when attempting to edit or save the

file(s) after the server is restarted may not accurately indicate the

problem. The wording for the error message is not consistent from one

application to another.

WORKAROUND

==========

The only solution is to save a copy of the file to a directory on your

computer, and edit it from there.

Additional reference words: 3.10 3.11 wfwg win3 howto re-started

re-booted rebooted


WFWG Err Msg: No Configuration Servers Found... DCA's Comnap

Article ID: Q90321

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

----------------------------------------------------------------------

SYMPTOMS

========

If you attempt to execute DCA's Comnap for 3270 services in Windows

for Workgroups, and the workgroup you have selected is not the same as

the domain for which Comnap is looking, the following error message is

generated:

   No configuration servers found within time limit.

   Comm Server Network Access initialization failed.

Comnap does a domain specific broadcast to locate the Comm Server.

WORKAROUND

==========

To work around this problem, change the Workgroup Name to the same

domain name that the LAN Manager server is on.

To change your Workgroup name, take the following steps:

1. From Control Panel, choose the Network icon .

2. Change your Workgroup name, then choose the OK button.

3. Restart the computer for the changes to take effect.

DCA's Comnap included here is manufactured by a vendor independent of

Microsoft; we make no warranty, implied or otherwise, regarding this

product's performance or reliability.

Additional reference words: 3.1 3.10 wfwg 3.11


Persistent Connections and Windows for Workgroups

Article ID: Q90322

-----------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

 - Microsoft Workgroup Connections version 1.0

-----------------------------------------------------------------

SUMMARY

=======

If resource connections are persistent in Windows for Workgroups or

Workgroup Connections, connecting to and disconnecting from resource

connections in Windows for Workgroups and Workgroup Connections

changes the list of persistent connections.

MORE INFORMATION

================

Disconnecting from a network drive is permanent, and removes it from

the list of persistent connections. There is no one-time-only

disconnect feature, although you can replace a persistent connection

for one session with a temporary connection. This can only be done in

Windows for Workgroups through the Connect Network and Connect Network

Printer dialog boxes.

To use a resource for one session, without disrupting the persistent

connection list, clear the selection of the Reconnect At Startup check

box when connecting to that resource.

The CONNECT.DAT file contains a list of persistent connections. When

starting the network, either from Windows Connections or Windows for

Workgroups, this list is used to keep track of the connections. These

connections are established when you either log on to the network in

Windows Connections, or when Windows for Workgroups is started.

For example, if a persistent printer resource is set in Windows for

Workgroups and is then disconnected from Windows Connections by using

the NET command, the resource will not automatically reconnect when

starting Windows for Workgroups.

Novell Users

------------

You must log on to Novell before starting Windows for Workgroups

for persistent connections to be established when starting Windows for

Workgroups.

Additional reference words: 1.0 1.00 3.1 3.10 LAN Manager LANman

3.11 wc wfwg


Workgroups Mail and Mail 3.0 Do Not Work with COMPAQ DOS 3.31

Article ID: Q90324

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

----------------------------------------------------------------------

SUMMARY

=======

Workgroups Mail and Microsoft Mail 3.0 do not function properly with

COMPAQ MS-DOS 3.31 due to changes made to the MS-DOS kernel that

affect file-sharing capabilities. This is only true for COMPAQ MS-DOS

3.31. Workgroups Mail and Mail 3.0 work properly with MS-DOS 3.3 or

later. COMPAQ is the only OEM that shipped MS-DOS 3.31.

For Mail to function properly, upgrade to MS-DOS 5.0 or later.

MORE INFORMATION

================

Workgroups Mail and Mail 3.0 do byte-range locking of their .MMF

files. This enables Mail to lock only portions of the .MMF file rather

then the entire file.

Changes made to the COMPAQ MS-DOS 3.31 kernel do not enable this to

function properly.

COMPAQ MS-DOS 3.31 is manufactured by a vendor independent of

Microsoft; we make no warranty, implied or otherwise, regarding this

product's performance or reliability.

Additional reference words: 3.10 msmail wfwg


Intel EtherExpress (EE) 16 Network Card Configuration

Article ID: Q90325

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

---------------------------------------------------------------

SUMMARY

=======

The Intel EtherExpress (EE) 16 network card that ships with Windows

for Workgroups is a software configurable card. This card is shipping

in the following Windows for Workgroups packages:

 - Windows for Workgroups Starter Kit

 - Windows for Workgroups User Kit

 - Windows for Workgroups add-on for 2 users of Microsoft Windows

   version 3.1

 - Windows for Workgroups add-on for 1 user of Microsoft Windows

   version 3.1

The settings for the card can be configured and tested in MS-DOS using

the program SOFTSET.

MORE INFORMATION

================

SOFTSET is a utility program that allows you to configure and test the

Intel EE 16 card. The Inel EE 16 works with thick or thin Ethernet

cable. The board has a DIX(15 pin, D-shaped) and a BNC Connector.

If you suspect there is a hardware conflict with the Intel EE 16 card,

you may want to place the card in 8-bit mode. To do this within

Windows for Workgroups, take the following steps:

1. From Control Panel, choose Network.

2. Choose the Adapters button.

3. Select the Intel EE 16 Adapter, then choose the Setup button.

4. Choose the Advanced button.

5. Set I/O Channel Ready to NEVER. This changes the IOCHRDY= line

   in the PROTOCOL.INI to NEVER.

You can also configure other settings on the Intel EE 16 card (that

is, IRQ, I/O, and RAM addresses). For more information on changing

the software configurable settings, consult the documentation for

the card.

Additional reference words: WFWG 1.00 Intel adapter 3.11 3.1


Schedule+ Err Msg: Schedule Transport DLL Does Not Support...

Article ID: Q90326

---------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

 - Microsoft Schedule+ for Windows, version 1.0

---------------------------------------------------------------

SYMPTOMS

========

The following error message may appear when you start Microsoft

Schedule+ for Windows or the Schedule+ component of Windows for

Workgroups (WFWG):

   Your schedule transport DLL does not support the current

   transport. You will only be able to work offline. PCMail

   users are supported.

CAUSE

=====

This occurs if you are using the wrong (or corrupt) TRNSCHED.DLL file.

RESOLUTION

==========

Make sure you only have one TRNSCHED.DLL file on your hard disk and

that it is the correct one for your Schedule+ version.

Windows for Workgroups Schedule+

--------------------------------

If you are using Windows for Workgroups Schedule+, the file

TRNSCHED.DLL should be located in the WINDOWS directory, and have the

following properties:

For version 3.11:

   TRNSCHED.DLL    12960        11/1/93 3:11:00am

For version 3.1:

   TRNSCHED.DLL    12960        10/1/92 3:11:00am

The TRNSCHED.DLL file is located on your original installation disks

as follows:

              5.25-inch disks   3.5-inch disks

   -------------------------------------------

   WFWG 3.1       disk 8           disk 6

   WFWG 3.11      disk 8           disk 6

Schedule+ for Windows

---------------------

If you are using version 1.0 of Microsoft Schedule+ for Windows, the

file TRNSCHED.DLL should have the following properties:

   TRNSCHED.DLL   12928   7/12/92 12:00:00am

If you are using version 1.0 or 1.0a of Microsoft Schedule+ with Windows

for Workgroups, you should use the Windows for Workgroups Schedule+

TRNSCHED.DLL file from the WINDOWS directory as described above.

Additional reference words: 3.10 unable sparta sched+ plus

scheduler schedule wfwg


Conventional Memory Change with WFWG and DYNAMIC=YES Setting

Article ID: Q90328

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

----------------------------------------------------------------------

SUMMARY

=======

After you install Windows for Workgroups on a computer running

Microsoft LAN Manager version 2.1, you may notice a change in

available conventional memory.

MORE INFORMATION

================

This may be caused by having DYNAMIC=YES in the [PROTMAN] section of

the PROTOCOL.INI file. The DYNAMIC=YES command causes PROTMAN.DOS to

allocate memory to facilitate demand protocol architecture (DPA).

Because Windows for Workgroups does not provide DPA functionality,

this memory is wasted.

To recover the memory used for DPA, change DYNAMIC=NO, or remove the

line all together.

DPA was first implemented with LAN Manager 2.1, and PROTMAN 2.0.

DPA allows for the dynamic loading/binding and unloading/unbinding

of protocols under MS-DOS.

Additional reference words: 3.10 WFWG PROTMAN PROTMAN.DOS SPARTA

lanman


WFWG May Momentarily Stop the Computer With Workgroups Mail

Article ID: Q90330

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

----------------------------------------------------------------------

SYMPTOMS

========

If the same computer is operating as both the postoffice server and

the browse master for a workgroup, the system may appear to stop

responding (hang) when Workgroup Mail is active.

You may have to wait for as long as three to four minutes for the

system to return to your control.

CAUSE

=====

Windows for Workgroups dynamically elects a computer in a workgroup to

act as the browse master for a period of time. If this computer

happens to be the same computer that is acting as the postoffice

server, performance may drop significantly when Mail is active.

WORKAROUND

==========

If your computer is acting as the postoffice server and you are

experiencing severe performance problems, add the following line to

the [Network] section of the SYSTEM.INI file:

   MaintainServerList=no

This setting prevents your computer from ever becoming the browse

master. Note that this setting should only be used in extreme cases.

Additional reference words: 3.10 wfwg 3.1 lockup stop crash freeze up


Cannot Change Order of First Print Job in WFWG

Article ID: Q90332

---------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

---------------------------------------------------------------

SUMMARY

=======

When you print from Windows for Workgroups, Print Manager does not

allow you to reorder the first job in the print queue. When Print

Manager receives a print job, it begins to process it immediately,

even if the printer queue has been paused. This behavior is by design.

MORE INFORMATION

================

To change the order of print jobs other than the first, use either of

the procedures below:

 - In Print Manager, select the print job you want to reorder. Then,

   from the Document menu, choose Move Document Up or Move Document

   Down.

   -or-

 - Select the print job, then choose the Move Document Up

   or Move Document Down button on the Print Manager toolbar.

You can only move documents up and down on a printer that is connected

to your computer. If the printer you are using is not connected to

your machine, you can only move a print job down.

NOTE: The "Changing Document Order" section of Program Manager Help

describes how to use the keyboard to change document print order.

Using the CTRL+UP ARROW and CTRL+DOWN ARROW key combinations does not

allow you to change the order in which the documents print.

Additional reference words: 3.10 unable sparta peer grey greyed

wfwg


Screen Momentarily Garbled at Windows for Workgroups Startup

Article ID: Q90333

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

SYMPTOMS

========

When you start Windows for Workgroups (WFWG), the screen may become

garbled momentarily after the logo and wallpaper appear. After a few

seconds, or if the mouse is moved, the screen restores the wallpaper

and the Windows for Workgroups login dialog appears.

CAUSE

=====

Some third-party video drivers write to the display to reset. These

drivers attempt to write to the display in a manner that matches the

Windows startup screen, so you do not notice. Because Windows for

Workgroups has made changes to Windows startup, you see the video

driver reset.

WORKAROUND

==========

To solve this problem, replace the video driver on your computer with

a video driver included with Windows for Workgroups.

Additional reference words: 3.10 3.1 wfwg redrawn refresh


Cannot Find HOME Directory Share on IBM LAN Server

Article ID: Q90335

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

The following article contains information on the use of 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

========

When you use Windows for Workgroups with IBM LAN Server 1.3, you

cannot connect to your HOME directory share on the LAN Server.

CAUSE

=====

This is not a problem with Windows for Workgroups but a limitation due

to the design of IBM LAN Server. The HOME directory share on IBM LAN

Server does not exist until you actually attempt to write to it, at

that point, the IBM LAN Server creates the directory share on a

server. When Windows for Workgroups attempts to connect to the HOME

directory share, it does not exist.

WORKAROUND

==========

Have a different user on the network connect to the HOME directory

before you log on to Windows for Workgroups by executing the NET USE

command. This may cause the HOME directory share to be created.

The IBM product included here is manufactured by a vendor independent

of Microsoft; we make no warranty, implied or otherwise, regarding

this product's performance or reliability.

Additional reference words: 3.1 3.10 wfwg


Client Not Notified of Remote Printer Problem

Article ID: Q90340

-------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

-------------------------------------------------------------------

In Windows for Workgroups, if you print to a remote printer from an

application installed on another server (that is, if the application

is not running from your local hard drive), you receive no

notification if a printer error occurs.

By contrast, if the application is installed locally on your machine

(the client) and a printer error occurs on a remote printer, you DO

receive notification of that error.

The error message appears on the print server, in Print Manager, but

Windows for Workgroups does not notify the client of the problem.

Additional reference words: 3.10 err msg errmsg win31 wfwg


NDOS Can Cause Windows to Exit Unexpectedly

Article ID: Q90344

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

 - Microsoft Windows operating system version 3.1

--------------------------------------------------------------------

The following article contains information on the use of 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.

SUMMARY

=======

If you run Symantec's Norton Utilities NDOS as your command

interpreter in MS-DOS, you must modify the DOSPRMPT.PIF file to point

to NDOS.COM instead of COMMAND.COM.

By default, Windows sets up an MS-DOS Prompt icon in the Main group of

Program Manager that invokes COMMAND.COM. Attempting to use this icon

to start MS-DOS Prompt can result in Windows exiting unexpectedly at

some point. It doesn't always happen immediately, but usually you

eventually run into this problem while running MS-DOS programs or

utilities.

MORE INFORMATION

================

If a replacement command interpreter is in use, there will be a SHELL=

line in the CONFIG.SYS file specifying the full path (for example

shell=c:\norton\ndos.com). If you use a replacement command

interpreter, you should use the PIF Editor to modify the DOSPRMPT.PIF

file to run the replacement interpreter instead of COMMAND.COM.

To modify DOSPRMPT.PIF:

1. Start PIF Editor.

2. Open DOSPRMPT.PIF.

3. Replace COMMAND.COM in the Program Filename field with the name of

   the replacement command interpreter.

4. Save the File.

Additional reference words: 3.10 wfwg


Information on Network Card Detection (NCD)

Article ID: Q90387

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

 - Microsoft Workgroup Connections version 1.0

--------------------------------------------------------------------

SUMMARY

=======

Hardware Detection in Windows for Workgroups Setup has been extended

from Microsoft Windows operating system version 3.1 to include network

card detection (NCD).

MORE INFORMATION

================

NCD occurs between the MS-DOS-based and Windows-based portions of

Windows for Workgroups Setup and is finished by the time you see your

first dialog box. If Setup detects a network adapter, it writes any

information it can detect plus information from the NETWORK.INF file

to the NCDINFO.INI file in the Windows for Workgroups directory

(C:\WINDOWS by default). Setup later uses this information when it

suggests a network adapter for you to install.

If your computer has multiple network cards, NCD does not detect all

cards; it stops after it detects the first one. Since very few

machines use more than one card, multiple card detection was not built

into NCD. You can configure Windows for Workgroups to use additional

network cards by running Control Panel (if you are running Windows for

Workgroups 3.1) or by running Windows Setup (if you are using Windows

for Workgroups 3.11).

Like Windows hardware detection, NCD can be skipped by running Setup

with the /I option (SETUP /I). You may need to use this switch if NCD

prevents Setup from completing your Windows for Workgroups

installation.

NOTE: When you select a network adapter from Control Panel, NCD does

not run. The settings displayed in the Networks option are factory

defaults taken from the NETWORK.INF file. You need to supply the

correct adapter configuration information.

WHEN NCD IS USED

================

Because Setup may fail during NCD, under the following circumstances,

Setup does not perform NCD:

 - Workgroup Connections is installed, detected by the presence

   of WRKGRP.SYS in the CONFIG.SYS file.

 - Windows for Workgroups is installed, detected by the presence of

   the network.drv=wfwnet.drv statement in the SYSTEM.INI file.

 - Setup with the /I option is run.

 - Original equipment manufacturer (OEM) provided network adapter

   information is in the NCDINFO.INI file in the Windows for

   Workgroups target directory. OEMs may put network adapter

   information in the [OEMDetected] section with the key name,

   NETCARD1=.

 - Setup failed during a previous installation, detected by the

   presence of the Ignore_HW_Detect= statement in the SYSTEM.INI

   file. Just before Setup starts NCD, Ignore_HW_Detect= is added

   to the SYSTEM.INI file under the [boot] section. If Setup sees this

   flag, it assumes that the last installation failed due to NCD problems.

   Setup then skips NCD and clears the statement when it has successfully

   completed installation.

NOTE: Setup may suggest a network adapter to you even if NCD was not

run because Setup may be able to determine what the network adapter

was from a previous installation of Windows for Workgroups, Workgroup

Connections, or Microsoft LAN Manager.

NCD FAILURE

===========

NCD can fail in any of the following ways:

NCD Fails to Detect the Network Adapter

---------------------------------------

The Unlisted Or Updated Network Adapter selection is selected in the

Network Identification list box.

Solution: You must manually select your network adapter. Make sure the

hardware settings for your adapter are correct.

NCD Detects the Adapter, But Not All the Necessary Settings

-----------------------------------------------------------

Your network adapter is selected in the Network Identification list

box. When you choose the OK button, hardware settings are displayed.

NCD detects as many settings as possible, but may not detect them all.

For example, Setup may not be able to detect the interrupt request

line (IRQ) used by the adapter. If this happens, Setup displays the

factory default for the particular setting it cannot detect.

Unfortunately, Setup does not inform you if a particular setting was

not detected. Some of the displayed settings are factory defaults

while others were properly detected settings. Also, the factory

defaults may not match the actual settings on the network adapter. If

you do not know the correct settings, and accept Setup's suggestions,

the network drivers will fail to initialize.

Solution: You must select the correct adapter settings during Setup,

or change the settings in Control Panel after Windows for Workgroups

is installed.

NCD Detects the Wrong Network Adapter

-------------------------------------

This is usually due to some incorrect or old information left on your

hard drive. Causes include:

 - Old or incorrect versions of Microsoft LAN Manager drivers.

 - Old or incorrect IPX.COM in the PATH or the root directory of the

   boot drive.

 - Old or incorrect EISA Setup information.

 - Old or incorrect information from an earlier Windows for Workgroups

   or Workgroup Connections installation.

Solution: During Setup (or from Control Panel) change the incorrect

network adapter to the correct one, making sure the hardware settings

are correct.

NCD Interferes with the Hardware, Failing Installation

------------------------------------------------------

One of several things may happen:

 - Your machine can stop responding (hang) or restart when Setup

   informs you that it is going into Windows.

 - Setup can cause a general protection (GP) fault or hang or restart

   your machine just before the Virtual Memory dialog box displays.

 - If you are running Setup over a network, the network adapter may be

   reset or disabled (until you restart your computer), making Setup

   unable to copy files from the remote drive.

Solution: Run Setup again. Windows for Workgroups does not perform NCD

if it failed the first time. However, if your computer hangs again,

use the /I switch with Setup.

HOW NCD WORKS

=============

NCD attempts to detect the network adapter many different ways. It

runs detection methods that are least likely to fail Setup first. It

then goes to more sensitive detection methods. A brief summary of

detection methods (in order of sensitivity):

 - Use the OEM provided information in the [OEMDetected] section of

   NCDINFO.INI.

 - Look for Micro-Channel Architecture (MCA) adapters in an MCA

   machine. (Only finds adapters known by their MCA identifications

   as of the release of Windows for Workgroups.)

 - Look for adapters in Extended Industry Standard Architecture (EISA)

   machines using the built-in EISA configuration capabilities. (Only

   finds adapters known by their EISA identifications as of the release

   of Windows for Workgroups.)

 - Try to extract information from Novell's IPX.COM. (Successful only

   if: IPX is running, NETx is running, IPX.COM is in the path or in

   the root directory of the boot drive and IPX.COM has been created for

   an adapter known by its IPX identification as of the release of

   Windows for Workgroups.)

 - Attempt to identify the network adapter by communicating with the

   physical hardware and seeing if it reacts in a characteristic manner.

HOW AND WHERE NCD INFORMATION IS STORED

=======================================

When Setup detects a network adapter, it writes the information in the

file, NCDINFO.INI, under the [LastDetectedFromSetup] section. All

values that cannot be detected are marked -1 or 0xffff. For example:

   NETCARD1=301,-1,0x300,16,0xffff,-1,0xffff,-1,-1,0,-1,

            0xffffffff,1,0x1b67

Explanation of Values

---------------------

   NETCARD1   - Key name.

   301        - Network adapter number. Assigned and used

                internally by Microsoft, this is the same

                number used in the NETWORK.INF and

                OEMSETUP.INF files. In this case it is the

                Intel EtherExpress 16.

   -1         - IRQ.

   0x300      - Base Input/Output (I/O) address.

   16         - Number of I/O ports used.

   0xFFFF     - Base RAM address (in paragraphs).

   -1         - Kilobytes of address space used by RAM.

   0xFFFF     - Base ROM address (in paragraphs).

   -1         - Kilobytes of address space used by ROM.

   -1         - DMA Channel used.

   0          - Bus type (0=ISA, 1=MCA, 2=EISA, 3=TURBO,

                4= PCMCIA).

   -1         - Slot number.

   0xFFFFFFFF - MCA/EISA identification.

   0x1b67     - CRC-16 Check-Sum of the above information.

   1          - Card specific information. In this case it

                stands for IOCHRDY=LATE.

Additional reference words: 3.10 wfwg wc 3.11


WFWG Err Msg: Error Loading MMTLHI.DRV... With ET 4000 Video

Article ID: Q90421

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.1

----------------------------------------------------------------------

SYMPTOMS

========

After installing Microsoft Windows for Workgroups (and selecting the

"ET 4000 1 MB, 1024x768 256 color (Large Fonts)" or the "ET 4000 1 MB,

800x600 256 color (Large Fonts)" display driver, you may receive one

of the following error messages:

   Error loading MMTLHI.DRV

-or-

   Cannot Load MMTLHI.DRV

WORKAROUND

==========

To work around this problem, try one of the following steps. (Note

that these suggestions may not work in all cases.)

 - Install the corresponding ET 4000 (Small Fonts) display driver.

-or-

 - Obtain and install the ET 4000 (Large Fonts) display driver from

   the Windows Driver Library (WDL). For information on obtaining

   the WDL, query on the following words in the Microsoft Knowledge

   Base:

      Windows and Driver and Library and Information

 - Install another display driver supported by your display

   configuration, such as the Windows for Workgroups VGA, or Super VGA

   (800 x 600, 16 colors) display driver.

STATUS

======

Microsoft has confirmed this to be a problem in Windows for Workgroups

version 3.1. We are researching this problem and will post new

information here as it becomes available.

Additional reference words: 3.10 3.1 wfwg


WFWG Err Msg: This Application Has Violated... LAN Manager

Article ID: Q90422

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

----------------------------------------------------------------------

SYMPTOMS

========

Windows for Workgroups allows approximately 30 seconds for the

processing of a Microsoft LAN Manager Logon Script. If the Logon

Script takes longer than 30 seconds to process, you may receive the

following error:

   This Application has Violated System Integrity.

WORKAROUND

==========

To resolve this problem, shorten the LAN Manager Logon Script so that

it executes in the allotted 30-second limit.

STATUS

======

Microsoft has confirmed this to be a problem in Windows for Workgroups

version 3.1 and version 3.11.

MORE INFORMATION

================

Microsoft Windows for Workgroups supports interconnectivity with

Microsoft LAN Manager servers. Some Microsoft LAN Manager

installations have the ability to process a Logon Script when you

log on. This script is essentially a batch file that executes and

allows you to restore network connections, synchronize the local system

clock with the remote server, and so on.

If the Logon Script is complex enough to exceed the 30-second time

limit, or sits idle while expecting input, the above error message may

result.

If the LANMan Logon Script contains NET USE commands to restore

network server or printer connections, it may be possible to shorten

the script and eliminate the problem by having the Windows for

Workgroups File Manager (or Print Manager) restore the connections

instead.

Additional reference words: 3.10 3.1 wfwg inter connectivity

inter-connectivity


Windows for Workgroups File Manager and Extended Characters

Article ID: Q90450

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

----------------------------------------------------------------------

SYMPTOMS

========

The Microsoft Windows for Workgroups File Manager may be unable to

manipulate files or directories whose names contain extended characters.

Starting an application from File Manager by double-clicking a filename

that contains an extended character may fail, or File Manager may not

display the extended characters correctly and attempt to change to a

directory name containing an

extended character.

STATUS

======

Microsoft has confirmed this to be a problem in Windows for Workgroups

versions 3.1 and 3.11. We are researching this problem and will place more

information here as it becomes available.

MORE INFORMATION

================

Each character available to the operating system has a unique number.

MS-DOS reserves characters 0 through 31 for control characters. The

keyboard contains characters 32 through 127. The characters 128

through 255 are referred to as "extended characters."

Although MS-DOS may allow the use of these extended characters in

filenames and directory names, the Windows for Workgroups File Manager

may have difficulty manipulating files and directories named in this

manner.

Steps to Reproduce Problem for Directory Name

---------------------------------------------

1. At an MS-DOS command prompt, create a directory with an extended

   character embedded in its name. For example,

   a. Type:

         md test

   b. Press ALT+255 (255 on the numeric keypad not on the keyboard).

   c. Type:

         dir

   d. Press ENTER.

2. From the Windows for Workgroups File Manager, attempt to

   double-click the newly created TEST DIR. Note that File Manager

   represents the directory as TEST_DIR, and that attempts to make it

   the current directory result in being returned to the root

   directory of the current drive.

Steps to Reproduce Problem for a Filename

-----------------------------------------

1. At an MS-DOS command prompt, copy an existing ASCII text file to a

   filename that contains an extended character. For example, to use

   the SETUP.TXT file in the WINDOWS directory, type the following at

   the WINDOWS directory MS-DOS command prompt:

      copy \windows\setup.txt \windows\test<ALT+255>fil.txt

   NOTE: <ALT+255> means press ALT+255 (255 on the numeric keypad and

   not on the keyboard).

2. From the Windows for Workgroup File Manager, double-click the newly

   created TEST FIL.TXT. Note that File Manager represents the file as

   TEST_FIL.TXT, and returns the follow message:

      File Manager cannot find the specified file (or one of its

      components). Make sure the path and filename are correct and

      that all required libraries are available.

Additional reference words: 3.10 3.1 wfwg


NetWare NCOPY to Local Drive Gives Sharing Violation

Article ID: Q90451

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.1

----------------------------------------------------------------------

SYMPTOMS

========

When running Microsoft Windows for Workgroups in 386 enhanced mode or

standard mode with the MS-DOS SHARE utility loaded, and using the Novell

NetWare version 3.11 NCOPY command to copy files to a local disk drive, you

may receive the following error

   Sharing violation reading drive <x>:

where <x> is the local target drive issued to the NCOPY command.

CAUSE

=====

According to the Microsoft Windows 3.1 NETWORKS.WRI file:

   Current versions of the NetWare shell are not fully compatible

   with SHARE.

Because Windows for Workgroups loads VSHARE.386 (the virtual SHARE device

driver) when in 386 enhanced mode, the NCOPY anomaly may manifest itself

anytime Windows for Workgroups is running in 386 enhanced mode, or is

running in standard mode with the MS-DOS SHARE utility loaded.

WORKAROUND

==========

Using the Windows for Workgroups File Manager, or the MS-DOS COPY or XCOPY

command instead allows the files to copy successfully.

The Novell product included here is manufactured by a vendor independent of

Microsoft; we make no warranty, implied or otherwise, regarding this

product's performance or reliability.

Additional reference words: 3.10 3.1 wfwg copy


Using PING.EXE with Windows for Workgroups

Article ID: Q90475

---------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

---------------------------------------------------------------

SUMMARY

=======

PING.EXE is a utility provided with Microsoft LAN Manager 2.1 TCP/IP

support. This utility does not function properly under Windows for

Workgroups.

PING.EXE attempts to spawn NMTSR.EXE out of the

LANMAN.DOS\DRIVERS\PROTOCOL\TCPIP directory when PING.EXE is initially

run. To use PING.EXE, you must have the TCP/IP protocol installed in

Windows for Workgroups, and you must manually load NMTSR.EXE before

using PING.EXE.

MORE INFORMATION

================

PING.EXE is a TCP/IP utility with the Microsoft LAN Manager 2.1

product, which allows you to see if another machine is active on the

network. By providing PING.EXE with a specific network address, you

can test to see if another machine is responding to network

broadcasts.

To manually load NMTSR.EXE to be visible in all virtual machines when

running Windows, start NMTSR.EXE in the AUTOEXEC.BAT file or at the

MS-DOS command prompt before starting Windows by typing:

   c:\lanman.dos\drivers\protocol\tcpip\nmtsr.exe

Additional reference words: 3.1 3.10 VM wfwg 3.11


Password Cache Not Used With UNC File Access

Article ID: Q90482

---------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

---------------------------------------------------------------

SUMMARY

=======

Windows for Workgroups allows files to be accessed by using a Universal Net

Connection (UNC). When you access a file using this method, the Windows for

Workgroups password cache file is not used.

For example:

1. You connected to \\SERVER\SHARE, and provided a password. The

   password is stored in your password cache file.

2. You reconnect to \\SERVER\SHARE and the password is provided by the

   password cache file. You are not prompted to enter a password.

3. In the Microsoft Write File Open dialog box, you open the file

   README.TXT on that server by typing

       \\server\share\readme.txt

   where "server" is your server, and "share" is your share.

   This causes Windows for Workgroups to prompt you for a

   password even though it is in the password cache file.

MORE INFORMATION

================

This behavior is caused by Windows use of MS-DOS file management. Due to

the nonreentrant nature of MS-DOS, Windows for Workgroups is unable to open

the password cache file because it is in the process of opening the file

specified in the UNC.

Additional reference words: 3.1 3.10 name naming wfwg 3.11


WFWG Err Msg: An Error Occurred While Trying to Reconnect...

Article ID: Q90490

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

----------------------------------------------------------------------

SYMPTOMS

========

When you start or exit Windows for Workgroups, the following error

message may be displayed:

   An error occurred while trying to reconnect (local identifier) to

   (shared resource) SYSXXXX.

This error may occur more than once, and may reference the same or

different shares.

WORKAROUND

==========

Information for persistent connections is stored in the CONNECT.DAT

file. In certain circumstances, this file may become corrupt (that is,

when switching between MS-DOS and Windows level connectivity). You may

delete this file to correct this problem.

NOTE: You will have to reestablish any persistent connections using

File Manager, Print Manager, and/or NET.EXE (both shares you are

connecting to, and resources you are sharing).

For further information on the SYSXXXX-type error messages, query

on the following words in the Microsoft Knowledge Base:

   wfwg and error and codes and sys

Additional reference words: 3.10 3.1 wfwg 3.11 sys0053 sys 0053


WFWG Err Msg: MS-DOS Error SYS0002

Article ID: Q90513

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

SYMPTOMS

========

When you attempt to run the real mode network redirector, NET.EXE,

from a network installation of Windows for Workgroups on a Novell

network, you may receive the following error message:

  MS-DOS error SYS0002 occurred trying to open the file "x:\system.ini"

CAUSE

=====

This error occurs because NET.EXE starts from your shared Windows for

Workgroups directory and your personal copy of the SYSTEM.INI file is

located in your personal Windows for Workgroups directory.

WORKAROUND

==========

To run the real mode redirector successfully, you need to add a search

drive that includes both the SYSTEM.INI and NET.EXE files.

MORE INFORMATION

================

After Windows for Workgroups installation, a typical NetWare search

path might look as follows:

   SEARCH1:=Z:.[XXX\SYS:PUBLIC \]

   SEARCH2:=Y:.[XXX\SYS:USER\JEFF\WFWG\] - (User directory. Setup /N)

   SEARCH3:=X:.[XXX\SYS:WINDOWS\WFWG\]   - (Shared directory. Setup /A)

   and so on

When you start the redirector by typing

   net start workstation

NET.EXE is first found on drive X. Drive X only contains the expanded

Windows for Workgroups files with no specific installation

information. Your SYSTEM.INI file is actually located on drive Y.

To successfully start the real mode network redirector, make sure both

NET.EXE and SYSTEM.INI are located on a drive together. The boot drive

(drive C typically) is a good drive for this. To start the redirector,

change to drive C first, or add drive C to your NetWare search path

prior to the shared Windows for Workgroups directory:

   SEARCH1:=Z:.[XXX\SYS:PUBLIC \]

   SEARCH2:=Y:.[XXX\SYS:USER\JEFF\WFWG\] - (User directory. Setup /N)

   SEARCH3:=C:\ - (Location of NET.EXE and SYSTEM.INI)

   SEARCH4:=X:.[XXX\SYS:WINDOWS\WFWG\]   - (Shared directory. Setup /A)

   and so on

Additional reference words: 3.10 wfwg


Installing WFWG Over Existing Mail 3.0 and Schedule+ 1.0

Article ID: Q90524

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

----------------------------------------------------------------------

SUMMARY

=======

Be cautious when installing Windows for Workgroups over an existing

installation of Mail 3.0 and Schedule+ version 1.0. Because Windows

for Workgroups installs Workgroups Mail and Schedule+, existing Mail

and Schedule+ files and settings may be overwritten.

MORE INFORMATION

================

Take the following steps to safely install Windows for Workgroups with

Mail 3.0:

NOTE: The following procedure does not work with the SETUP /A and SETUP /N

options.

1. Start Windows for Workgroups Setup.

2. Choose the Custom Installation option.

3. Continue through Setup until the Set Up Only Windows Components You

   Select check box appears. Select the check box and choose the

   Continue button.

4. The next screen allows you to choose different components. Choose

   the Files button on the Accessories line.

5. On the next screen, all accessories will appear under the Install

   These Files On The Hard Disk list box. From that list box, choose:

      Mail

      Mail Help

      Schedule+

      Schedule+ Help

   Then choose the Remove button.

   All of the above files will appear in the Do Not Install These

   Files list box.

6. Choose the OK button to continue with Setup.

Workgroups Mail and Schedule+ will not install and will not conflict

with the existing Mail and Schedule+ installations.

Additional reference words: 3.10 Mail WFWG 3.11


Cannot Set Default Appointment Time in Schedule+

Article ID: Q90526

---------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

 - Microsoft Schedule+ for Windows, version 1.0

---------------------------------------------------------------

When you create a new appointment in Windows for Workgroups Schedule+

or Schedule+ 1.0, the Start Time and End Time are determined by

the currently selected time slot.

There is no way to specify a default appointment time in Schedule+.

This is by design.

Additional reference words: 3.10 unable sparta morning afternoon plus

scheduler schedule wfwg


NetWatcher Shows Same User Multiple Times

Article ID: Q90529

---------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

---------------------------------------------------------------

SYMPTOMS

========

When you use the Windows for Workgroups application NetWatcher, the

server may notice a single user connected several times, each time

opening the same file. This is normal for a user using Schedule+.

CAUSE

=====

This situation is caused by running Schedule+ and the Schedule+

Reminders program. Each would have the user's schedule file open. If

the user then has a meeting request from another user open, the file

is opened a third time.

This behavior is by design.

Additional reference words: 3.10 Sparta Peer Net Watcher wfwg


Hearts Requires EGA (or Above) and Mouse

Article ID: Q90560

------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

------------------------------------------------------------------

The Microsoft Hearts Network card game (MSHEARTS.EX) included with

Windows for Workgroups requires a minimum display resolution of EGA,

and a Windows-compatible mouse.

Additional reference words: 3.10 wfwg


GP Fault in WINHELP.EXE After Starting Microsoft Mail

Article ID: Q90710

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

SYMPTOMS

========

WINHELP.EXE may cause a general protection (GP) fault if you perform the

following steps:

1. From Program Manager's Help menu, choose Contents. (Or, start

   WINHELP.EXE by choosing Help from any Windows-based program.)

2. Minimize Windows Help.

3. Start Microsoft Mail by choosing its icon in Program Manager's

   Main program group.

4. In the Welcome To Mail dialog box, where you are prompted for a

   postoffice, press the F1 key.

The GP Fault dialog box should allow you to close WINHELP.EXE and then

continue using Windows for Workgroups Mail without crashing your

system or causing any further problems.

STATUS

======

Microsoft has confirmed this to be a problem in Windows for Workgroups

version 3.1 and version 3.11.

We are researching this problem and will post new information here as

it becomes available.

Additional reference words: 3.10 wfwg 3.11


Mail Message File Size in Windows for Workgroups

Article ID: Q90925

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

 - Microsoft PC Mail, version 3.0

--------------------------------------------------------------------

SUMMARY

=======

Mail message files vary in size, depending on the size and type of

messages stored in the file. Folders and the Personal Address Book

also take additional space in the mail message file (MMF).

MORE INFORMATION

================

An empty mail message file is about 43K in size. The mail message

file grows with each additional Message, Folder, and Personal Address

Book entry.

There are about 128 bytes overhead for each message and about 256

bytes overhead for each attachment or object-linking-and-embedding

(OLE) object in a message. Because there is no real data compression

in the mail message file, a message containing 100K of information

actually adds 100K plus the message overhead to the mail message file.

Each folder adds from 42 to 300 bytes to the mail message file.

Personal Address Book entries are stored in the mail message file. One

Personal Address Book entry of 500 characters would add about 720

bytes to the mail message file.

Additional reference words: 3.10 3.1 wfwg win31


Device Contention Errors with Parallel Port Network Cards

Article ID: Q90926

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.1

----------------------------------------------------------------------

SYMPTOMS

========

If you use Windows for Workgroups with a network interface card (NIC)

that plugs into the parallel port, device contention errors may occur.

(Only two supported NICs plug into the parallel port: the Xircom

Pocket Ethernet I and II.)

CAUSE

=====

These errors occur because Windows for Workgroups sees the LPT port as

being used by two different resources: the network and the printer.

WORKAROUND

==========

To work around this problem, do one of the following:

Workaround 1

------------

If you do not need the LPT port for local printing, you can disable

the check for device contention by removing the following line in the

SYSTEM.INI file:

   DEVICE=VPD.386

Disabling VPD.386 doesn't affect the ability of Windows for Workgroups

to print over the network. However, if you are printing locally, no

warning appears and printouts may have garbled characters, or you may

experience network communication problems.

Workaround 2

------------

In Control Panel, choose the 386 Enhanced Mode icon. Set the Idle Time

for the port in question to zero (0). This turns off VPD trapping for

that port.

MORE INFORMATION

================

For more information on device contention in Windows, query on the

following words in the Microsoft Knowledge Base:

   device contention windows

Additional reference words: 3.10 wfwg win31 notebook laptop adapter


WFWG Servers Cannot Act as a Gateway, Router, or Bridge

Article ID: Q90927

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

SUMMARY

=======

Microsoft Windows for Workgroups (WFWG) version 3.1 does not include

the functionality to join network segments, regardless of topology or

operating system.

MORE INFORMATION

================

Windows for Workgroups includes the functionality to connect a Windows

for Workgroups workstation to one or more separate network segments

through separate network interface cards. It does not include the

functionality to join these separate segments to each other.

Example of Connecting to Two Different Topologies

-------------------------------------------------

A Windows for Workgroups machine cannot be used to join multiple

network segments of different types. However, you can connect a single

workstation to two different networks. For example, you can use one

network card to connect a Windows for Workgroups workstation to a LAN

Manager Ethernet network using the NetBEUI protocol and then use a

second network card to connect to a Novell network using the MSIPX and

NetBEUI protocols. This  workstation can communicate with (and use and

share resources on) both networks, but it cannot join the two networks

together.

This type of connection is sometimes referred to as internal bridging

or routing. To connect networks of different topologies or operating

systems, you must use the correct hardware device. For example, to

connect an Ethernet network to a Token Ring network, you must use a

device called a gateway (which supports this function).

Example of Connecting to Two Different Segments

-----------------------------------------------

You cannot use a Windows for Workgroups machine to join multiple

network segments of the  same type. If, for example, a workstation has

two network cards installed (both of the same type, such as Ethernet),

you can connect 1 to 10 workstations on one segment (Segment 1) and 20

workstations on the other (Segment 2). The 10 workstations on Segment

1 will be able to communicate with each other, as will the 20

workstations on Segment 2. The machine that is connected to both

segments (through the two separate network cards) can communicate with

all 30 workstations, but it does not join the segments together in a

way that enables them to share and use resources on the other segment.

In other words, a Windows for Workgroups machine can connect to

different segments of a network, but it cannot replace a hardware

device designed to join network segments. To connect multiple network

segments, a device that supports this function is required, such as a

multiport repeater or Multistation Access Unit (MAU). The device is

specific to the network topology and existing network.

Additional reference words: 3.1 3.10 wfwg win31


MSIPX and NETX Command Line Switches with WFWG

Article ID: Q90928

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

SUMMARY

=======

This article is a description of the command line switches available

with MSIPX and NETX, which are included with Windows for Workgroups

for Novell connectivity.

NOTE: This information applies to Windows for Workgroups version 3.11,

ONLY if you have upgraded from version 3.1. MSIPX is not included with

version 3.11.

MORE INFORMATION

================

MSIPX command line switches:

   /i Displays version information

   /d Displays hardware options

   /o <num> Load using hardware option<num>

   /c=[path]<filename> Use an alternate configuration file

   /? Display help screen

Each of these switches can be activated in one of three ways:

   msipx i   msipx -i   msipx /i

NETX command line switches:

   /? Display shell usage switches

   /I Display shell version and type

   /U Unload the NetWare shell from memory

   /F Forcibly unload the NetWare shell, in spite of TSRs

      loaded after the shell (CAUTION: The /F option could

      hang your workstation)

   /PS=<server> Specify a preferred server

   /C=[path]<filename.ext> Name of your NetWare shell configuration file

      (NOTE: For use with MS-DOS version 3.0 through MS-DOS version 5.0)

Windows for Workgroups includes MSIPX.COM and MSIPX.SYS to provide

Novell connectivity. MSIPX.COM is Novell's IPX.COM bound to a "shim,"

which looks like a net card to IPX but provides an NDIS (network

driver interface specification) interface to PROTMAN.DOS (protocol

manager). MSIPX.SYS is the stub that binds the MSIPX transport

protocol to the network adapter MAC (media access control) driver.

Windows for Workgroups also ships with NETX.COM, the Novell NetWare

command line shell and redirector. It has not changed from the

NETX.COM shipped with Windows 3.1.

For more information on NDIS, query in the Microsoft Knowledge Base on

the words:

   MAC and NDIS

Additional reference words: 3.10 3.1 wfwg Novell 3.11


Share Names With a "$" Character at the End Are Hidden

Article ID: Q90929

------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

------------------------------------------------------------------

SUMMARY

=======

When sharing directories or drives with Windows for Workgroups, if a

dollar sign ($) character is added to the end of a share name, the

share name does not appear in a browsed list of available shares on

the server.

If you know the full name of the hidden share, you can access it

normally by typing its name with a $ at the end.

MORE INFORMATION

================

For example, if drive C: is shared as ROOT$ on the machine SERVER,

then ROOT$ does  not appear when SERVER is browsed by a workstation.

However, if a user enters  \\SERVER\ROOT$ as the path in the Connect

Network Drive dialog box, the user can connect to the hidden server.

This functionality is also supported in LAN Manager.

Additional reference words: 3.1 3.10 wfwg win31 hide


Shared CD-ROM or Floppy Drives Must Contain a Disk At Startup

Article ID: Q90930

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

----------------------------------------------------------------------

SYMPTOMS

========

If you select the Re-share At Startup option when sharing a floppy or

CD-ROM drive, and you start Windows for Workgroups without a disk

in the shared drive, the following error may be displayed.

   System Error Cannot Read from Drive X.

(where X: is the driver letter representing the shared drive)

If you choose the Cancel button, the following error message will be

displayed:

   An error occurred while trying to share X. Error 5291. The

   path X:\ does not exist. Do you want to continue to share X each

   time you start Windows for Workgroups?

CAUSE

=====

The Windows for Workgroups File Manager allows the sharing of local

disk resources including fixed disks, floppy drives, and CD-ROM

drives. You can make these shares persistent by selecting the Re-share

At Startup option. If you select this option and the shared CD-ROM or

floppy drive does not contain a disk when Windows for Workgroups is

restarted, the above errors may occur.

WORKAROUND

==========

To eliminate these error messages, make sure that the shared drive

contains a disk before starting Windows for Workgroups.

There are several ways to recover from the error condition, depending

on the intended result.

 - To immediately reestablish the share, insert a disk in the shared

   drive and choose Retry in the System Error Cannot Read From

   Drive X dialog box.

 - To not reestablish the share for the current session, but attempt

   to reestablish the share in future sessions, choose Cancel at the

   System Error Cannot Read From Drive X dialog box and choose Yes at

   the Do You Want To Continue To Share X Each Time You Start Windows

   for Workgroups? dialog box.

 - To not reestablish the share for the current or future sessions,

   choose Cancel in the System Error Cannot Read From Drive X dialog

   box and choose No at the Do You Want To Continue To Share X Each

   Time You Start Windows For Workgroups? dialog box.

Additional reference words: 3.10 3.1 wfwg re-establish 3.11


Corrupt CONNECT.DAT May Cause Invalid Errors in WFWG

Article ID: Q90931

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

SYMPTOMS

========

If the CONNECT.DAT file (which Windows for Workgroups uses for

storing a list of previous connections) is corrupt, the following

error message may occur when you start Windows for Workgroups:

   An error occurred while reconnecting LPT1: to

   \\Sharename\Printer

   [SYS0000]

   Do you want to continue restoring connections?

This error occurs even if the share is actually available and can be

printed to without errors. It may also occur on connections to disk

shares, where an error message occurs, but the share is still

available.

WORKAROUND

==========

1. Make a list of persistent connections from the File Manager

   and the Print Manager.

2. Exit Windows for Workgroups completely.

3. In the WINDOWS directory rename or delete the CONNECT.DAT file.

4. Restart Windows for Workgroups.

5. Run File Manager. From the Disk menu, choose Connect Network Drive

   and manually restore any previous connections.

6. Run Print Manager. From the Printer menu, choose Connect Network

   Printer and manually restore any previous connections.

MORE INFORMATION

================

You cannot rename CONNECT.DAT with File Manager because another

CONNECT.DAT with 0 bytes may immediately be created if there are

persistent connections present.

For more information on CONNECT.DAT, query on the following words:

   contents and connect.dat

Additional reference words: 3.10 wfwg


FastTips: Mail and Schedule+ Questions and Answers

Article ID: Q90974

-----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

-----------------------------------------------------------------------

SUMMARY

=======

This article contains the complete text of the "Mail and Schedule+

Questions & Answers" fax script.

This fax script is available to customers who call the Microsoft

FastTips Service for Operating Systems at (800) 936-4200.

MORE INFORMATION

================

======================================================================

  Microsoft(R) Product Support Services Application Note (Text File)

            WG0692: MAIL AND SCHEDULE+ QUESTIONS & ANSWERS

======================================================================

                                                  Revision Date: 10/92

                                                      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.                           |

 --------------------------------------------------------------------

1. Q. What are the general requirements for using Microsoft Mail

      and Microsoft Schedule+ with Microsoft Windows for Workgroups?

   A. To effectively use Mail and Schedule+, all computers within a

      workgroup should be connected to one postoffice. Only one

      postoffice should be created for a workgroup. Schedule+ relies

      on the established Mail connections in order to work correctly.

      For more information, please refer to the user's guides for Mail

      and Schedule+.

2. Q. What steps are involved in creating a new postoffice for

      Microsoft Mail?

   A. To use Mail, create only one postoffice for all computers in a

      designated workgroup. If you will be the postoffice

      administrator, use the following four steps to do this:

      1. When you start Mail for the first time, select the Create

         A New Workgroup Postoffice option. Unless you specify

         otherwise, this creates a new subdirectory named WGPO in the

         postoffice administrator's Windows directory by default.

      2. Enter your administrator account details in the dialog

         box. You must include entries for Name and Mailbox. A

         password is optional. The Name value is your alias for Mail.

         The Mailbox value is used for internal referencing in Mail.

         The Password value defaults to the word "password"; however,

         you can change this value or remove it if you choose not to

         have a password.

      3. In File Manager, select the WGPO directory.

      4. From the Disk menu, choose Share As, and select the Full

         option button under Access Type. You may want to type

         "Postoffice" (without the quotation marks) in the Comment

         field so that people at other workstations can identify this

         directory when they connect to the postoffice.

3. Q. I cannot access the initial mail dialog box that allows you

      to either connect to or create a postoffice. How can I correct

      this problem?

   A. This problem occurs when more than one postoffice exists within

      a workgroup. Extra postoffices must be deleted. If you delete

      the extra postoffices, those computers that were formerly

      postoffices must connect to the existing postoffice. To delete

      extra postoffices, use the following four steps:

      1. Quit Mail.

      2. From File Manager, select the MSMAIL.INI file. From the

         File menu, choose Rename. In the To box, type "msmail.bak"

         (without the quotation marks), then choose the OK button.

      3. Restart Mail. In the Welcome To Mail dialog box, select

         the Connect To An Existing Postoffice option.

      4. Select the server name and shared directory for the

         postoffice. If you do not have an account, add your

         information to the postoffice.

       NOTE: You must have entries for the Name, Mailbox, and Password

       boxes. Be sure to use the same entries that you were using

       before you renamed the MSMAIL.INI file so that you can access

       your old mail messages.

4. Q. I'm receiving the error messages "Cannot establish a DOS or

      Windows Mail Server" and "Cannot connect to the Workgroup

      Postoffice." How can I correct this problem?

   A. If you receive the error message "Cannot establish a DOS or

      Windows Mail Server" or "Cannot connect to the Workgroup

      Postoffice," a postoffice may not have been created yet or your

      postoffice server may be down. Check with the workgroup or

      system administrator to find out if a postoffice has been

      created. If a postoffice has not been created, determine who

      will be the postoffice administrator and refer to the previous

      procedure for creating a postoffice.

      If a postoffice has been created, you may need to modify the

      MSMAIL.INI file to reflect the location of the postoffice. Use

      the following three steps:

      1. Quit Mail.

      2. Open the MSMAIL.INI file from the Windows directory in an

         ASCII text editor, such as Microsoft Windows Notepad.

      3. Note the entry beside the ServerPath= setting. This should

         match the server name and the shared directory name of the

         postoffice. The proper syntax is as follows:

           serverpath=\\servername\directoryname

5. Q. I can't move mail messages or delete them from a folder. How

      can I correct this problem?

   A. If you cannot move or delete mail messages from a folder, you

      may have a corrupt MSMAIL.MMF file. This file contains all your

      mail folders and messages. To repair the MSMAIL.MMF file, use

      the following three steps:

      1. From the File menu in Microsoft Mail, choose Exit And Sign

         Out.

      2. Restart Mail.

      3. If the built-in Mail utility detects any corrupt mail

         files, a dialog box should appear with the message "Your

         database file is corrupt, repair now?" Choose the Yes button.

      The Mail Message File utility should repair any damage to the

      MSMAIL.MMF file and, when completed, return to Mail.

6. Q. I am receiving the error message "Schedule file could not be

      opened. You may not have the necessary access privileges or the

      file may not be available." How can I correct this problem?

   A. When you choose Open Other's Appt. Book from the File menu in

      Schedule+, you may receive the error message "Schedule file

      could not be opened. You may not have the necessary access

      privileges or the file may not be available." This error occurs

      when the person whose file you are trying to access has not

      granted you access privileges. You must have at least the Read

      Appointments And Tasks privilege to open another's Appointment

      Book. The default setting for privileges is View Free/Busy

      Times, which allows you to view other schedules from Planner.

      Schedule+ defaults to the Appointment Book. To access Planner,

      you must select the tab labeled Planner from the left side of

      the Schedule+ screen. To set access privileges for other users,

      choose Set Access Privileges from the Options menu. For more

      information on access privileges, please refer to the "User's

      Guide."

7. Q. How can I import appointments from Microsoft Windows

      Calendar or WordPerfect Office into Microsoft Schedule+?

   A. Schedule+ has a feature that allows you to import appointments

      from Windows Calendar 3.1 and WordPerfect Office. To import your

      appointments from either of these applications, use the

      following three steps:

      1. In Schedule+, choose Import Appointments from the File

         menu.

      2. In the List Files Of Type box, select the file type that

         corresponds to the appointment book application.

      3. Select a file to import, then choose the OK button.

8. Q. I changed my password in Microsoft Mail and the new password

      works correctly in Mail; however, Schedule+ is prompting me for

      my old password. Is this a problem?

   A. No. If you change your password in Mail, the Schedule+ password

      is affected. After you successfully create a new password in

      Mail, you are prompted for your old password in Schedule+ before

      you can enter the application. If you change your password in

      Schedule+, Mail accepts your new password without prompting you

      for your old password.

Additional reference words: 3.10 ivrfax fast tips wfwg


FastTips: Sharing CD-ROMs and Printers Questions & Answers

Article ID: Q90977

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

SUMMARY

=======

This article contains the complete text of the "Sharing CD-ROMs and

Printers Questions & Answers" fax script.

This fax script is available to customers who call the Microsoft

FastTips Service for Personal Operating Systems at (800) 936-4200.

MORE INFORMATION

================

======================================================================

  Microsoft(R) Product Support Services Application Note (Text File)

       WG0694: SHARING CD-ROMS AND PRINTERS QUESTIONS & ANSWERS

======================================================================

                                                  Revision Date: 10/92

                                                      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.                           |

| NetWare and Novell are registered trademarks of Novell, Inc.       |

 --------------------------------------------------------------------

1. Q. When you are using Microsoft Windows for Workgroups, what

      are the system requirements for using File Manager or Print

      Manager to share resources?

   A. To share network resources using File Manager or Print Manager,

      you must have at least 3 megabytes (MB) of RAM on your machine

      and be operating in 386 enhanced mode. You can only share

      resources that are on your machine; you cannot share resources

      to which you are connected over the network.

2. Q. How can I share my local CD-ROM drive using Microsoft

      Windows for Workgroups?

   A. To share a CD-ROM drive using Windows for Workgroups, use the

      following five steps:

      1. Load the device-dependent CD-ROM driver in the CONFIG.SYS

         file. This driver can be obtained from your CD-ROM vendor.

      2. Load MSCDEX.EXE /S in the AUTOEXEC.BAT file. MSCDEX.EXE

         must be version 2.21 and loaded with the /S switch to allow

         sharing capability. MSCDEX.EXE can be obtained from your CD-

         ROM vendor. If you are running Novell(R) NetWare(R) with

         Windows for Workgroups, MSCDEX must be loaded prior to MSIPX.

      3. After you make these modifications, save the files,

         restart the machine, then start Windows.

      4. The CD-ROM drive can be shared in the same way any other

         local hard disk drive can be shared. Choose the CD-ROM icon

         and select the directories to be shared.

      5. In File Manager, choose Share As from the Disk menu. In

         the Share Directory dialog box, type the Share Name

         information, any comments you want to use to describe the

         shared resource, and then set the Access Type and Password

         options.

      For more information on troubleshooting CD-ROM sharing issues,

      please refer to your Windows for Workgroups documentation.

3. Q. Are there differences between Windows for Workgroups Print

      Manager and Print Manager in Windows 3.1?

   A. Yes. Please note the following three differences in the Windows

      for Workgroups Print Manager:

      1. The user interfaces for both Print Manager and the

         Printers icon in Control Panel are different from those used

         in Microsoft Windows operating system version 3.1. For

         example, you must disconnect printers from Print Manager

         only; you can no longer disconnect printers from Control

         Panel.

      2. The toolbar in Print Manager is a new feature. Unlike the

         toolbar in File Manager, the Print Manager toolbar cannot be

         customized.

      3. Print Manager cannot pause print jobs locally.

      For more information, please refer to your Windows for Workgroups

      documentation.

Additional reference words: 3.10 ivrfax fast tips wfwg


Setup and Control Panel: Different Recommended Swap File Size

Article ID: Q90978

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

You may notice that the recommended permanent swap file size is

different in Windows for Workgroups Setup than it is in Control Panel.

This is because Setup is running Windows for Workgroups in standard

mode, while Control Panel is probably being run from enhanced mode

Windows. The algorithm for calculating the recommended size of the

permanent swap file differs in the two modes of Windows.

Additional reference words: 3.10 3.11 swapfile wfwg


Exiting Wing Commander Hangs Computer

Article ID: Q90981

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

 - Microsoft Workgroup Connections version 1.0

--------------------------------------------------------------------

SYMPTOMS

========

Your computer may stop responding (hang) after you exit Wing Commander

version 2.0.

CAUSE

=====

This game requires extensive conventional, extended, and expanded

memory. You should not start the network redirectors before playing

this game.

WORKAROUND

==========

If you automatically start the network in your AUTOEXEC.BAT file,

remove the network from memory before playing Wing Commander by typing

"net stop" (without the quotation marks) at any MS-DOS command

prompt.

The product included here is manufactured by a vendor independent of

Microsoft; we make no warranty, implied or otherwise, regarding this

product's performance or reliability.

Additional reference words: 3.10 3.11 wfwg wc


No Network Services After Install Over LAN Manager 2.0

Article ID: Q90982

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

SYMPTOMS

========

After you install Windows for Workgroups over Microsoft LAN Manager

version 2.0, the network services do not start because Setup did not

add a NET START command to AUTOEXEC.BAT.

RESOLUTION

==========

LAN Manager version 2.0 is not a supported network for Windows for

Workgroups. You can perform a successful upgrade by removing the

references to the LAN Manager network from AUTOEXEC.BAT before running

Windows for Workgroups Setup.

Additional reference words: 3.10 3.11 wfwg


File Manager Displays Actual Total Disk Space

Article ID: Q90994

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

 - Microsoft Windows NT operating system version 3.1

---------------------------------------------------------------------

SUMMARY

=======

When you use Windows for Workgroups or Windows NT File Manager, the

total disk size displayed in the status bar may differ from the

specified formatted size of the disk.

For example:

 - 1.44 megabyte (MB) disks display as having 1.38 MB total space.

 - 1.2 MB disks display as having 1.15 MB total space.

 - 720 kilobyte (K) disks display as having 713K total space.

MORE INFORMATION

================

While these totals may seem incorrect, File Manager is actually

displaying the exact amount of total disk space based on 1K actually

being 1024 bytes and 1 MB being 1024K.

File Manager determines the amount of space on a disk by using the

following formula:

(Allocation units * number of bytes in each allocation unit)/1024/1024

For example:

   1.44 Disk: (2047*512)/1024/1024 = 1.390136718 bytes

NOTE: Microsoft Windows 3.1 File Manager displays total disk space in

kilobytes rather than megabytes. As a result, 1.44 MB disks display as

having 1.423K.

Additional reference words: 3.1 3.11 floppy wfwg


Network Problems with AMI Pro and JustWrite

Article ID: Q90999

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

SYMPTOMS

========

If two users attempt to open a JustWrite 2.0 or AMI Pro document at

the same time over the network, both users are able to modify the

file, and any changes made by one of them are lost. The intended

behavior is that the first user gets exclusive access, and the second

gets read-only access.

At present, it is recommend that multiple users NOT use these

applications with the same file at the same time, even though the AMI

Pro version 2.0 is advertised as a "Networked" version.

Additional reference words: 3.10 3.11 wfwg


How To Use Help Command in WFWG Setup Does Not Work

Article ID: Q91000

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

 - Microsoft Windows operating system version 3.1

--------------------------------------------------------------------

SYMPTOMS

========

When you run Microsoft Windows or Windows for Workgroups Setup to

change your Windows configuration, help is not available from the Help

menu option How To Use Help. Choosing How To Use Help results in

Windows Help opening and closing quickly.

STATUS

======

Microsoft has confirmed this to be a problem in Windows for Workgroups

version 3.1 and version 3.11. We are researching this problem and will post

new information here as it becomes available.

Additional reference words: 3.10 3.11 wfwg


Problems Upgrading Drivers When Installing WFWG on LAN Manager

Article ID: Q91017

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

SYMPTOMS

========

When you install Windows for Workgroups on a machine that uses

Microsoft LAN Manager, Setup may display an error message saying it

cannot upgrade a driver. This may occur with any original equipment

manufacturer (OEM) specific device drivers in LAN Manager.

CAUSE

=====

The LAN Manager configuration is upgraded by comparing the DRIVER0

entry in the LAN Manager SETUP.INI file against the list of known LAN

Manager drivers in the [netcard] section of LM21DRV.UPD. If they do

not match, the driver cannot be automatically upgraded.

WORKAROUND

==========

You have to select from the drivers that Windows for Workgroups

provides or use an OEM installation disk.

Additional reference words: 3.10 lanman err msg


File Manager Allows Disconnect of Shared WFWG Directory

Article ID: Q91020

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

SYMPTOMS

========

When you run Windows for Workgroups from a shared network directory

(created by using the SETUP /A command), File Manager allows you to

disconnect the network drive from which you are running Windows for

Workgroups, without a warning, when the shared directory is on a

Novell NetWare server.

When you run a SETUP /N configuration with Windows 3.1, this is not

possible. The NetWare dialog in Windows 3.1 does not allow you to

disconnect a search drive.

With Windows for Workgroups, you can disconnect any network drive,

even when it's a NetWare search drive.

If you disconnect the network drive from which Windows for Workgroups

is running, the machine may stop responding (hang).

STATUS

======

Microsoft has confirmed this to be a problem in Windows for Workgroups

version 3.1 and version 3.11. We are researching this problem and will post

new information here as it becomes available.

Additional reference words: 3.10 wfwg 3.11


TBMI2.COM Removed from AUTOEXEC.BAT in WFWG

Article ID: Q91028

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

Whenever you use the Network setup option of Microsoft Windows Setup

to add or remove Novell NetWare connectivity from Windows for

Workgroups, TBMI2.COM is removed from the AUTOEXEC.BAT file. TBMI2.COM

does not cause any problems with Windows for Workgroups and can be

added back to the AUTOEXEC.BAT file.

TBMI2.COM acts as an interface between NetWare and the standard mode

Windows task switcher.

Additional reference words: 3.11 3.10 net ware wfwg


QEMM LASTDRIVE Program Is Incompatible with WFWG

Article ID: Q91047

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

SUMMARY

=======

QuarterDeck's QEMM LASTDRIVE program is incompatible with Windows for

Workgroups.

MORE INFORMATION

================

If you try to add drive letters using QEMM's LASTDRIVE program,

Windows for Workgroups connects the drive but doesn't show any

directory entries or file information. Also, if you run MS-DOS Prompt,

you can't switch to the connected drive.

NOTE: The MS-DOS LASTDRIVE= statement in the CONFIG.SYS file works

correctly.

Additional reference words: 3.10 3.11 wfwg


Network Dysfunctional After Removing Novell NetBIOS Support

Article ID: Q91059

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

SYMPTOMS

========

You remove Novell NetBIOS support from your Windows for Workgroups

network, and now you have no network functionality.

CAUSE

=====

To support Novell NetBIOS, you must add two statements to the

SYSTEM.INI file. If you then remove Novell NetBIOS support, Control

Panel does not remove the statements, resulting in no network

functionality.

WORKAROUND

==========

To regain network functionality, you must manually remove these lines

if they exist:

   V86ModeLANAs=0,1

   LANAs=0,1

MORE INFORMATION

================

Adding the two statements to your SYSTEM.INI is necessary to make the

Windows for Workgroups network redirector ignore the Novell NetBIOS

provider on LANA0. If you later remove Novell NetBIOS support, Control

Panel moves NetBEUI support back to LANA0, but does not remove the

statements, making the redirector ignore LANA0. Because the redirector

cannot find a valid NetBIOS provider, it cannot load.

You can find instructions for Novell NetBIOS support in the

NETWORKS.WRI file in the Windows for Workgroups directory.

The products included here are manufactured by Novell, a vendor

independent of Microsoft; we make no warranty, implied or otherwise,

regarding these products' performance or reliability.

Additional reference words: 3.11 NOVEL 3rdparty 3.10 wfwg


Message Looks Read or Opened After Move, Copy, or Print

Article ID: Q91066

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

If you perform any operation on a Microsoft Mail message, the letter

icon at the left of the message subject is dimmed and open as if you

had read it. This happens if you move, print or copy a message. This

behavior is by design. The read status icon is a signal that the

message has been "dealt with," not necessarily that it has been read.

Additional reference words: 3.10 gray grey unavailable wfwg 3.11


Setup Word for Windows Before Running Program Over A Network

Article ID: Q91074

-------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Word for Windows, versions 2.0, 2.0a, and 2.0b

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

 - Microsoft Windows operating system version 3.1

-------------------------------------------------------------------

SUMMARY

=======

If you want to run Word for Windows from a network or shared workgroup

drive, you must first run the Word Setup program and choose the

Workstation Installation option. Word for Windows does not operate

correctly if you start the program by running the WINWORD.EXE file

from a network server. A general protection (GP) fault eventually

occurs when you run Word for Windows in this manner.

MORE INFORMATION

================

For more information on installing Word for Windows on a network

workstation, refer to Appendix A (pages 793-802) in the "Microsoft

Word for Windows User's Guide."

For information on licensing Word for Windows for use on multiple

workstations, contact your Microsoft dealer or Microsoft Consumer

Sales at (800) 426-9400.

REFERENCES

==========

"Microsoft Word for Windows User's Guide," version 2.0, pages 793-802.

"Microsoft Word for Windows Getting Started," version 2.0, pages 7-11

Additional reference words: 3.10 2.00 2.00a 2.00a-CD 2.00b w4wsetup

wfwg w4wnetwork w4werror err msg errmsg launch start


NET START from MS-DOS Prompt Can Hang Computer

Article ID: Q91095

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

SYMPTOMS

========

If you start MS-DOS Prompt from Windows for Workgroups and use the NET

START command, your machine may stop responding (hang). You also may

be forced out of Windows for Workgroups and lose data from any open

files in other applications.

RESOLUTION

==========

Microsoft does not recommend that you use the NET START command inside

of Windows for Workgroups. The NET START command should only be used

before entering Windows for Workgroups.

Additional reference words: 3.10 freeze crash wfwg


Font Corruption in Ventura Publisher 4.0

Article ID: Q91096

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

 - Microsoft Windows operating system version 3.1

--------------------------------------------------------------------

SYMPTOMS

========

In Ventura Publisher version 4.0 under Microsoft Windows or Microsoft

Windows for Workgroups, you may notice some font corruption in a few

Ventura Publisher fonts. Text may display in one or two columns only.

This may occur when using these fonts: CG Times, Univers, and Univers

CD. If you change to a TrueType font included with Windows for

Workgroups, the problem no longer occurs.

STATUS

======

Microsoft is researching this problem and will post new information

here in the Microsoft Knowledge Base as it becomes available.

The product included here is manufactured by a vendor independent of

Microsoft; we make no warranty, implied or otherwise, regarding these

products' performance or reliability.

Additional reference words: 3.11 3.10 3rdparty wfwg tt true type


WFWG Err Msg: NET3651: There is No Protocol Added...

Article ID: Q91114

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

SYMPTOMS

========

If the Microsoft LAN Manager directory is in the MS-DOS PATH statement

before the Windows for Workgroups directory, you may receive the

following error:

   NET3651: There is no protocol loaded. A protocol is required to

   complete the command.

To avoid this error and retain network functionality in Windows for

Workgroups, remove the LAN Manager from the PATH statement in the

AUTOEXEC.BAT file.

CAUSE

=====

Windows for Workgroups Setup looks for a PATH statement in the

AUTOEXEC.BAT file and removes the LAN Manager directory. If the syntax

of the PATH statement has been changed, Setup fails to recognize it

and does not remove the LAN Manager directory.

Setup recognizes:

   SET PATH=C:\DOS;C:\LANMAN.DOS\NETPROG;C:\WINDOWS

However, it does not recognize:

   PATH C:\DOS;C:\LANMAN.DOS\NETPROG;C:\WINDOWS

When the NET START command is executed from AUTOEXEC.BAT, LAN

Manager's NET command is activated, causing the above error.

STATUS

======

Microsoft has confirmed this to be a problem in Windows for Workgroups

version 3.1 and version 3.11. We are researching this problem and will post

new information here as it becomes available.

Additional reference words: 3.10 3.11 wfwg


Write Err Msg: '<Filename> Could Not Be Found' and WFWG Hangs

Article ID: Q91127

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

SYMPTOMS

========

If you run the Write application that ships with Windows for

Workgroups (WFWG), you may receive the "<filename> could not be found"

error message if any of the following situations occur:

 - You connect to a server in File Manager.

 - You drag and drop a document into Write.

 - The network connection to that server is lost.

If you choose the OK button, the message returns. At this point, you

are in a loop and cannot exit Write.

WORKAROUND

==========

The only way to exit Write (and Windows for Workgroups) is to restart

the computer.

STATUS

======

We are researching this problem and will post new information here in

the Microsoft Knowledge Base as it becomes available.

Additional reference words: 3.10 hang crash freeze err msg


WFWG Err Msg: One or More Files Could Not Be Found that...

Article ID: Q91152

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

SYMPTOMS

========

If you perform a network installation of Windows for Workgroups (using

the SETUP /N command), the following error message may be displayed

when you attempt to start Windows for Workgroups:

   One or more files could not be found that were needed to start

   Windows in enhanced or standard mode.

With a local installation, you would get a list of files that it could

not find, but in this case the list is empty.

CAUSE

=====

This message occurs when a network connection to the shared Windows

for Workgroups directory has not been established, and WIN.COM cannot

find the files it needs to start Windows for Workgroups.

RESOLUTION

==========

To solve this problem, start the redirector, log on, and connect to

the server containing the shared Windows for Workgroups directory.

Additional reference words: 3.10 wfwg 3.11


Computer Hangs After Removing Token Ring Card

Article ID: Q91169

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

SYMPTOMS

========

Your computer may stop responding (hang) after you remove your IBM

Token Ring adapter if you have installed Novell NetWare as a secondary

network in Windows for Workgroups. When you start your computer, the

AUTOEXEC.BAT file processes successfully until it reaches the NET

START command. It displays the following message:

   Microsoft NetBind version 2.1

Your computer then hangs. To start your computer and gain access to

your hard drive, you must use a bootable floppy.

RESOLUTION

==========

To correct the problem, remove the network device driver statements

from the CONFIG.SYS file.

MORE INFORMATION

================

If you are not using an IBM Token Ring adapter or have not installed

Novell NetWare as your secondary network, you may receive errors after

removing your network adapter. During CONFIG.SYS processing, the

following displays:

   MAC0006: Network interface hardware not found or not responding.

   MAC0001: Init failure

   Press any key to continue...

Once you press a key and the AUTOEXEC.BAT file begins processing, the

following is displayed:

   Error 5733: The protocol manager has reported an incomplete

   binding.

Although these errors do not prevent you from using your computer,

they may be signs of an unstable configuration. Microsoft recommends

that you remove the network device drivers from CONFIG.SYS and

AUTOEXEC.BAT until your network adapter is back in your computer.

The products included here is manufactured by vendors independent

of Microsoft; we make no warranty, implied or otherwise, regarding

these products' performance or reliability.

Additional reference words: 3.10 3.11 crash freeze wfwg


File Manager: Five Extensions Maximum

Article ID: Q91189

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

Windows for Workgroups File Manager is extensible, meaning

dynamic-link libraries (DLLs) can be added. You can access DLL options

from toolbar icons or add-on menus. The maximum number of DLLs that

can be added to File Manager is five.

DLLs are added to File Manager by adding entries to the [AddOns]

section of WINFILE.INI. No errors are generated if there are more than

five entries.

NOTE: An Undelete feature can be added to File Manager increasing the

total number of DLLs to six.

Additional reference words: 3.10 wfwg 3.11


How To: Troubleshooting a Network DDE Link with WFWG

Article ID: Q91197

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

----------------------------------------------------------------------

SUMMARY

=======

In Windows for Workgroups (WFWG), the Windows Clipboard Viewer was

completely rebuilt as ClipBook Viewer, which includes capabilities to

transfer information over the network (called network dynamic data

exchange [DDE]).

MORE INFORMATION

================

To test network DDE, both machines should be running the same video

driver, such as VGA (16 colors), which shipped with Windows for

Workgroups.

Network DDE works like object-linking-and-embedding (OLE) over a

network. There are several logical steps to troubleshoot a network DDE

problem:

1. Make sure that the machines can communicate with each other. To

   test this, try to copy a file from one machine to another.

   Remember that a Windows for Workgroups machine needs to be in

   enhanced mode and have 4 megabytes (MB) of memory to have server

   functionality.

2. To make sure that the problem is not application-related, do a

   network DDE link using Paintbrush and Write. The steps are as

   follows:

   a. Open a bitmap in Paintbrush and copy it to the Clipboard.

   b. Open ClipBook. From the Edit menu, choose Paste. This brings

      up a dialog box that asks for a Page (Share) Name.

   c. Type "test" (without the quotation marks) as the Page Name and

      choose OK. (Make sure the Share Item Now box is selected.)

   d. When the next dialog box comes up, choose Start Application

      On Connect.

   e. From the Client machine, open ClipBook. From the File menu,

      choose Connect.

   f. Select the server name from the list, then select the "test"

      file.

   g. From the Edit menu, choose Copy.

   h. Start Write. From the Edit menu, choose Paste Link. This should

      create a Network DDE link from Paintbrush on the server machine

      to Write on the client machine.

   i. Test the link by drawing in Paintbrush on the server and see

      if Write is updated on the client.

If Write isn't updated, there is a problem with Network DDE. If the

above steps work, the problem is in one or both of the applications

that were having the original problem.

Each of the applications can be tested with Write or Paintbrush to

determine which application is at fault. Some applications may have to

be upgraded to work properly with Network DDE. Check with the

application vendor for more information on a specific application.

Additional reference words: 3.10 3.1 wfwg netdde win31 tshoot howto

3.11


How To: Setting Up a Resource in Schedule+ with WFWG

Article ID: Q91200

---------------------------------------------------------------

The information in this article applies to:

- Microsoft Windows for Workgroups versions 3.1 and 3.11

- Microsoft Schedule+ for Windows version 1.0

---------------------------------------------------------------

SUMMARY

=======

Rooms or other physical items, such as a conference room or vehicle,

can be set up as a resource to be scheduled using Microsoft's

Schedule+ program included with Windows for Workgroups (WFWG).

Only the postoffice administrator can set up a resource to be

scheduled.

MORE INFORMATION

================

Workgroups for Windows Mail Postoffice (WGPO) and Windows for

Workgroups Schedule+ must be installed and set up before beginning

this process.

1. The Mail Postoffice administrator needs to create an account for the

   room. An example would be for the Conference room #1.

2. Create a mail account called CONFER1 for the Name and CONFER1 for

   the Mailbox. The password must be the same as the administrator's

   password for the Mail Postoffice.

3. Exit and sign out of Mail and Schedule+.

4. Rename the MSMAIL.MMF file in your local Windows directory.

5. Start Schedule+. When it prompts for a name and password, use

   CONFER1 as the name and enter the password. This starts the account

   for this room.

6. From the Schedule+ Options menu, choose General Options. Select

   This Account Is For A Resource, then chose OK.

7. If each person running Schedule+ is to have the ability to add

   and delete appointments for the room CONFER1, follow these steps.

   (If only one person will add or delete appointments, skip this step

   and go on to step 8.)

   a. Choose Exit and Sign Out from the File menu.

   b. From your local Windows directory, delete the MSMAIL.MMF file

      that Schedule+ just created.

   c. Rename your previous MSMAIL.MMF file back to MSMAIL.MMF.

   d. Start Schedule+. From the File menu, choose Open Other's Appt.

      Book.

   3. Choose the room that was set up (CONFER1). The room is now set up.

8. If there is to be only one person in charge of setting up

   and modifying the times for the room CONFER1, do the following:

   a. From the Options menu, choose Set Access Privileges.

   b. Set the default Privilege to "Read Appointments & Tasks."

   c. Select the Add option and choose the person who is to be in

      charge of making appointments to the room CONFER1.

   d. Select the Assistant option for this person, then choose OK.

   e. Choose Exit and Sign Out from the File menu.

   f. From your local Windows directory, delete the MSMAIL.MMF file

      that Schedule+ just created.

   g. Rename your previous MSMAIL.MMF file back to MSMAIL.MMF.

   h. Start Schedule+.

   i. From the File menu, choose Open Other's Appt. Book.

   j. Choose the room that was set up (CONFER1). The room is now

      set up.

Additional reference words: 3.10 3.1 wfwg win31 how to 3.11


NET.EXE Does Not Always Load Full Redirector by Default

Article ID: Q91221

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Workgroups Connections versions 1.0 and 2.0

--------------------------------------------------------------------

In Workgroup Connections Setup, if you select "Do not run Workgroup

Connections," the AUTOSTART= statement is left blank in SYSTEM.INI. If

you execute a NET command requiring a loaded network redirector,

NET.EXE should load the full redirector by default, regardless of the

NET command. Depending on what command you execute, NET.EXE may not

load the full redirector.

NET LOGON and NET START RDR both require network redirectors. If no

redirector is loaded or specified by the AUTOSTART= statement, NET.EXE

should load the full redirector. However, if you execute NET LOGON,

NET.EXE loads the full redirector; if you execute NET START RDR, it

loads the basic redirector.

Additional reference words: 3.10 wfwg 3.11


WFWG: MSDLC.EXE Needed for Attachmate's Extra! for Windows

Article ID: Q92428

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

SUMMARY

=======

Attachmate Corporation's Extra! for Windows requires a Data Link Control

(DLC) driver to work with Windows for Workgroups. This driver supplies the

DLC protocol and allows 3270 emulators to communicate with host systems.

The Microsoft DLC driver, MSDLC.EXE, is included with Microsoft LAN Manager

version 2.1a or later and can be installed with the additional information

provided in the Windows for Workgroups Resource Kit. MSDLC.EXE is supported

by the Microsoft LAN Manager support group.

The MSDLC protocol for Windows for Workgroups version 3.11 is available

from the Microsoft Download Service (MSDL) at (206) 936-6735. The

downloadable file is named WFWDLC.EXE. NOTE: The file WFWDLC.EXE is

intended for use with Windows For Workgroups version 3.11 only and is not

guaranteed to work with any other version of Workgroups.

Other versions of MSDLC.EXE are NOT available from the MSDL. The only way

to obtain this driver is to purchase the Microsoft LAN Manager product.

Microsoft LAN Manager licensing states that you may use the DLC driver with

an unlimited number of LAN Manager and Windows for Workgroups clients.

MORE INFORMATION

================

For more information on using MSDLC.EXE, please refer to the "Windows

for Workgroups Resource Kit" guide, Appendix E, pages E-15 to E-18.

Extra! for Windows is manufactured by a vendor independent of Microsoft; we

make no warranty, implied or otherwise, regarding this product's

performance or reliability.

Additional reference words: 3.10 extra wfwg 3rdparty 3.11 msdl


WG0667: Peer-to-Peer vs. Client-Server Networks

Article ID: Q92451

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

---------------------------------------------------------------------

SUMMARY

=======

Microsoft has an application note that discusses the differences

between the peer-to-peer and client-server networking models.

NOTE: The text for this application note was taken from the Windows

for Workgroups Resource Kit.

To obtain this application note, call Microsoft Product Support

Services at (206) 454-2030.

This application note can be found in the Software/Data Library by

searching on the word WG0667, the Q number of this article, or S13702.

WG0667 was archived using the PKWARE file-compression utility.

MORE INFORMATION

================

The text of the application note is included below.

======================================================================

  Microsoft(R) Product Support Services Application Note (Text File)

            WG0667: PEER-TO-PEER VS. CLIENT-SERVER NETWORKS

======================================================================

                                                  Revision Date: 11/93

                                                      No Disk Included

The following information applies to Microsoft Windows(TM) 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(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.                           |

| Novell and NetWare are registered trademarks of Novell, Inc.       |

 --------------------------------------------------------------------

        A COMPARISON OF CLIENT-SERVER AND PEER-TO-PEER NETWORKS

        -------------------------------------------------------

This application note discusses the differences between the peer-to-

peer and client-server networking models.

  NOTE: The text for this application note was taken from the Windows

  for Workgroups Resource Kit.

Part of a network's overall design includes a decision about how

network resources will be shared and managed. Early networks used

central file servers to manage access to shared files and printers.

These servers were often workstations dedicated to sharing resources

or running network file server-related applications (for example,

database engines). Examples of network operating systems (NOSs) that

support the central file server model include Microsoft LAN Manager

and Novell(R) NetWare(R). The peer-to-peer network model was developed

more recently. Network workstations in a peer-to-peer model can access

resources shared by another user and share resources on their local

workstations to allow access by other members of their workgroup.

Windows for Workgroups supports the peer-to-peer networking model.

The central file server model requires that all file sharing take

place on the LAN server itself. That is, if the file server is the

central repository of information, then all exchanges of information

between workstations on a LAN must first pass through the file server.

This model is commonly implemented in an environment where the

workstations don't have the processing power or the resources capable

of supporting networking server functionality. For example, the

workstations may not have enough memory or may have small-capacity

hard disks.

In the peer-to-peer networking model, each workstation (or at least

one workstation) in a file-transfer scenario acts as both a client and

a server. As a client, the workstation can access the network

resources shared by another workstation. This model is commonly

implemented in an environment where workstations have the processing

power and resources to provide network server functionality or where

the cost of dedicating a workstation as a server is prohibitively

high. The peer-to-peer model is more flexible than the central file

server model because a workstation can directly access the shared

resources of another workstation.

To illustrate the differences between the central file server model

and the peer-to-peer networking model, let's say two workstations,

Workstation A and Workstation B, want to share a document. The

document was created on Workstation A and resides on Workstation A's

hard disk.

In the central file server model, Workstation A must connect to the

server, place the document on the server's hard disk, then inform

Workstation B that the document is available. Workstation B can then

connect to the server and access the document left there by

Workstation A. In the meantime, unless Workstation A is working with

the specified document directly on the file server (that is, making

modifications to the version of the document that resides on the file

server), the version of the document that may reside on Workstation

A's hard disk will likely become out of sync with the version of the

document Workstation B is now using.

In the peer-to-peer networking model, Workstation A simply grants

Workstation B permission to access the directory where the files are

located on Workstation A's hard disk. Workstation B can then directly

connect to Workstation A and access the document. Another way to

provide Workstation B with the document that Workstation A created is

to have Workstation B give Workstation A access to a shared directory

on Workstation B. Then Workstation A can copy the document from its

hard disk to the shared directory on Workstation B--however, the

latter procedure suffers from the same scenario as the central file

server model where the versions of the documents may get out of sync.

Since both workstations are considered to be peers, both support

client and server functionality.

Additional reference words: 3.10 3.11 Wfwg


WG0668: Advanced Mail and Schedule+ Help Files and Demos

Article ID: Q92494

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

---------------------------------------------------------------------

SUMMARY

=======

Microsoft has an Application Note that contains advanced Help files

and graphical demonstrations that provide a detailed overview of

standard features in Microsoft Mail and Schedule+. The Application

Note contains the following files:

Microsoft Mail Help Files and Demonstrations

--------------------------------------------

 - CBTLIB3.DLL

 - CLKLIB.DEX

 - DEMOFX.DEX

 - MSMAIL.HLP

 - MSMAIL.LES

 - PLAY.EXE

Microsoft Schedule+ Help Files and Demonstration

------------------------------------------------

 - SCHDPLUS.HLP

 - SCHDPLUS.LES

To obtain this Application Note, call Microsoft Product Support

Services at (206) 454-2030.

This Application Note can be found in the Software/Data Library by

searching on the word WG0668, the Q number of this article, or S13703.

WG0668 was archived using the PKWARE file-compression utility.

MORE INFORMATION

================

The text of the Application Note is included below.

======================================================================

  Microsoft(R) Product Support Services Application Note (Text File)

       WG0668: ADVANCED MAIL AND SCHEDULE+ HELP FILES AND DEMOS

======================================================================

                                                  Revision Date: 11/93

                                                        Disks Included

The following information applies to Microsoft Windows(TM) 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(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

------------

The enclosed WG0668 disks contain advanced help files and graphical

demos that provide a detailed overview of standard features in

Microsoft Mail and Schedule+.

The following information explains how to add the advanced help files

and demos to your current Windows for Workgroups Mail and Schedule+

applications and how to use the help files and demos.

To Install the Help Files and Demos

-----------------------------------

1. Quit Microsoft Windows.

2. Change to the Windows directory by typing the following lines at

   the MS-DOS command prompt and pressing ENTER after each line

      cd \

      cd \<windows>

   where <windows> is the path to your Windows directory. For example:

      cd \win31

3. Insert Disk 1 of the enclosed WG0668 disks in your floppy disk

   drive.

4. Copy the help and demo files to the Windows directory by typing the

   following at the MS-DOS command prompt and pressing ENTER

      copy <drive>:\*.*

   where <drive> is the floppy disk drive containing the WG0668 disk.

   For example:

      copy b:\*.*

5. Remove Disk 1 from your floppy disk drive and insert Disk 2.

6. Repeat step 4.

At this point, the files are in place and ready for access from within

Windows for Workgroups Mail or Schedule+.

To Run the Advanced Help Files and Demos

----------------------------------------

1. Start Microsoft Windows.

2. From Program Manager, choose Run from the File menu.

3. In the Command Line box, type "winhelp.exe" (without the quotation

   marks).

4. Choose the OK button. You are now in Windows Help.

5. From the File menu, choose Open.

6. From the File Name list box, select MSMAIL.HLP for Mail help or

   SCHDPLUS.HLP for Schedule+ help.

7. Choose the OK button.

   From the list of help topics, click the topic you want to learn

   more about (or use the TAB key to move to the topic and then press

   ENTER). Many of these topics contain demonstrations of Mail and

   Schedule+. You can access the demos by choosing the Demo button

   when available.

    NOTE: Not all topics will have a demonstration.

Features Not Available in Windows for Workgroups Mail and Schedule+

-------------------------------------------------------------------

While these help files provide many advanced examples and additional

information, the files also outline a few features that are not

available in the Windows for Workgroups versions of Mail and

Schedule+. To obtain the full features of Mail 3.0 and Schedule+ 1.0,

contact Microsoft Consumer Sales at (800) 426-9400. Listed below are

the features mentioned in the help context that are not available in

the versions of Mail and Schedule+ included with Windows for

Workgroups:

 - Postoffice-to-postoffice directory synchronization (multiple

   postoffices)

 - Support for gateways to other mail systems

 - An administrator utility to configure and administer the postoffice

   from any workstation on the network

 - Support files for external postoffice mail transfer through a

   network or modem

 - A spelling checker in Mail

 - Shared groups in Mail

Additional reference words: 3.10 3.11 Wfwg


WFWG and Windows: System Hangs When Copying Files

Article ID: Q92516

------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows operating system versions 3.0, 3.0a, and 3.1

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

------------------------------------------------------------------

SYMPTOMS

========

Your machine may stop responding (hang) or suddenly exit to the MS-DOS

command prompt when you copy a large number of files over the network.

Usually Windows for Workgroups provides an error message that says to

increase NetHeapSize, but the machine may also exit to the MS-DOS

command prompt or hang.

RESOLUTION

==========

To correct this problem, increase the NetHeapSize in the [386Enh]

section of your SYSTEM.INI file. The default value is 12; for

troubleshooting, try 32, 64, or 128.

Increasing NetHeapSize can reduce problems when your network is

running under a heavy load and you are running the real mode

redirector.

NOTE: NetHeapSize is ignored by the virtual redirector.

Additional reference words: 3.1 3.10 freeze crash novel novell win31

3.11 wfwg 3.00 3.00a


WFWG Err Msg: An Error Has Occurred. ClipBook Viewer Cannot...

Article ID: Q92543

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

 - Microsoft Excel for Windows, version 4.0

 - Microsoft Word for Windows, versions 2.0 and 6.0

--------------------------------------------------------------------

SYMPTOMS

========

When you paste a range of cells from Microsoft Excel for Windows to

ClipBook Viewer (creating a new ClipBook page), you may receive the

following error message:

   An error has occurred. ClipBook Viewer cannot complete this

   procedure.

If you are using Word for Windows, version 6.0, the following error

message is displayed:

   There is insufficient memory. Save the document now.

CAUSE

=====

This is due to a problem in Excel for Windows and the method it uses

to render its Clipboard image.

WORKAROUND

==========

If you are using Microsoft Word for Windows, version 2.x, choose a

smaller range to allow the cells to paste correctly.

If you are using version 6.0 of Microsoft Word for Windows, follow

these steps:

1. Save your Excel file.

2. Define the area to be copied as the Print Area.

3. Choose Page Setup from the Files menu, and change the Scaling "Fit

   to:" option to 1 pages wide by 1 tall.

4. Copy the range and paste it into your Microsoft Word document.

5. In Microsofat Excel, revert to your saved file and reset the

   Print Area and Page Setup options.

MORE INFORMATION

================

All information copied to Clipboard or ClipBook Viewer is formatted by

the source application. Excel for Windows does not successfully create

a picture format when the range of cells is larger than 32 by 32

centimeters, which generates the above error message. (The error

message also occurs if you simply paste a 30-column-by-1-row range.)

Similar behavior may occur when pasting from Excel into Word for

Windows if you choose Paste Special from the Edit menu in Word and

then select Picture from the Date Type list box:

   There is not enough memory to complete this operation.

STATUS

======

Microsoft is researching this problem and will post new information

here as it becomes available.

Additional reference words: 3.10 3.11


WFWG: Null Password Bypasses Login

Article ID: Q92555

---------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

---------------------------------------------------------------

SUMMARY

=======

Microsoft Windows for Workgroups allows multiple users to use the same

machine through the use of PassWord cache Lists (PWLs). Windows for

Workgroups also supports null passwords (an empty password).

MORE INFORMATION

================

If Windows for Workgroups has the Logon At Startup option selected in

Control Panel, and the previous user has a PWL file with a null

password, the Logon dialog box is bypassed at startup.

To allow a different user to log on to the Windows for Workgroups

machine, the previous user must be logged off. To do this, use the

Logoff button in the Control Panel.

Windows for Workgroups always provides the previous user's name at the

logon prompt during Windows for Workgroups startup.

Additional reference words: 3.1 3.10 by-passed wfwg 3.11


Most Recently Used (MRU) Lists of Previous Connections in WFWG

Article ID: Q92573

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

----------------------------------------------------------------------

SUMMARY

=======

When a network connection is made with Chat, ClipBook, File Manager,

or Print Manager in Windows for Workgroups (WFWG), it is placed in the

WIN.INI file in a Most Recently Used (MRU) list.

The purpose of the Most Recently Used sections of the WIN.INI file is

to maintain a list of previous connections for the network-aware

utilities in Windows for Workgroups. Once an entry is made in the Most

Recently Used list, it can only be removed by either adding enough new

connections or editing the WIN.INI file.

MORE INFORMATION

================

In the WIN.INI file, the previous connections are stored in three

different sections:

 - Chat and ClipBook connections are stored in the [MRU_Chat] section.

   The limit on the number of previous connections in this section

   is 12.

 - File Manager connections are stored in the [MRU_Files] section.

   The limit on the number of previous connections in this section

   is 12.

 - Print Manager connections are stored in the [MRU_Printers] section.

   The limit on the number of previous connections in this section

   is 12.

At the top of each of these sections is an Order= line and it keeps

the order of the most recently used connections. Below the Order= line

is the list of all the connections that correspond to the letters in

the Order= line.

For example, if the Order=dabc line is present, the most recent

connection made was the connection listed under d=, while the

connection that has gone the longest without being used is listed on

the c= line.

Removing a Connection from the MRU List

---------------------------------------

To remove a connection from a Most Recently Used list, use the

following steps:

1. Edit the WIN.INI file using any text editor.

2. Locate the appropriate Most Recently Used section.

3. Delete the line that lists the connection.

4. Reorder the lines so that there is no break in the order. For

   example, when there are connections listed from "a" to "e" as in

   the following list (when "d=\\george" is deleted), change "e=\\lisa"

   to "d=\\lisa".

      [MRU_Chat]

      Order=cadeb

      a=\\john

      b=\\bill

      c=\\susan

      d=\\george

      e=\\lisa

5. Remove references to any connections that no longer exist from

   the Order= line. In the above example, "e" was renamed to "d,"

   so the Order= should be changed to Order=cadb.

6. Save the changes to the WIN.INI file and restart Windows for

   Workgroups.

Connections are also removed if the limit is exceeded by adding a

new connection. Once the limit is exceeded, the last connection

referenced in the Order= line is removed and the new connection

becomes the first on the Order= line.

Additional reference words: 3.10 3.1 wfwg win31 3.11


WFWG: GP Fault in Video Driver when Using ClipBook Viewer

Article ID: Q92577

---------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

---------------------------------------------------------------

SYMPTOMS

========

Microsoft Windows for Workgroups ClipBook viewer version 3.1 creates a

thumbnail drawing of a ClipBook page when you choose Paste from the Edit

menu.

If your third-party video driver does not correctly implement small text

fonts, you will receive a general protection (GP) fault in the video

driver.

STATUS

======

Microsoft has confirmed this to be a problem in Windows for Workgroups

versions 3.1 and 3.11. We are researching this problem and will post new

information here as it becomes available.

WORKAROUND

==========

To work around this problem, use the video graphics adapter (VGA) or Super

VGA driver provided with Windows for Workgroups or contact your third-party

vendor to obtain an updated driver.

Additional reference words: 3.1 3.10 3rdparty third party 3.11


ClipBook: Paste Link with Ami Pro May Paste Corrupt Data

Article ID: Q92578

---------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

---------------------------------------------------------------

SYMPTOMS

========

When you use the Windows for Workgroups ClipBook Viewer program with

Lotus Ami Pro, you may see raw rich text format (RTF) data when data

is paste-linked into Ami Pro.

CAUSE

=====

Ami Pro appears to have a timing problem with network dynamic data

exchange (DDE) and the Paste Link command. If the Network DDE is

delayed due to network traffic, Ami Pro may interpret incoming RTF

data as text.

WORKAROUND

==========

The only workaround is to try the Paste Link command again.

For more information, please contact Lotus Development Corporation's

Ami Pro technical support.

Ami Pro is manufactured by Lotus Development Corp., a vendor

independent of Microsoft; we make no warranty, implied or otherwise,

regarding this product's performance or reliability.

Additional reference words: 3rdparty wfwg 3.1 3.10 3.11


WFWG: Server Responds Slowly After RAS Connection is Made

Article ID: Q92598

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

SYMPTOMS

========

You may notice a general slowdown of your Windows for Workgroups

server machine if another user has connected to it using Microsoft

Remote Access Services (RAS) version 1.0.  RAS version 1.1 does not

exhibit this behavior.

WORKAROUND

==========

To avoid this problem, add the following statement to the [network]

section of the SYSTEM.INI file on the remote computer:

   MaintainServerList=no

NOTE: The "Microsoft Windows for Workgroups Resource Kit" manual for

version 3.1 incorrectly states on page E-10 that the

MaintainServerList=No line should be added to the [386enh] section.

MORE INFORMATION

================

After the computer with RAS 1.0 has connected to the server

workstation, the network adapter on the server constantly sends

broadcast messages or packets. This is known as a "broadcast storm."

Until you restart the server machine, the "storm" continues.

The nature of this problem often makes it difficult to detect. You may

notice a sluggish keyboard response or experience slow network

operations. If you have a CPU meter on the server machine, it

registers 100% CPU usage when this problem occurs.

Additional reference words: lanman docerr wfwgrk 3.10 wfwg 3.11


14 or 15 Character Machine Name Causes Print Manager Error

Article ID: Q92634

---------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

---------------------------------------------------------------

SYMPTOMS

========

Microsoft Windows for Workgroups allows you to provide a machine name

of up to 15 characters. However, long machine names can cause a

problem with Print Manager.

With machine names of 14 or 15 characters, Print Manager

inappropriately displays an error message for the status of any port

attached to that server.

For example, if your machine is connected to \\LONGMACHINENAME\PRINTER

on LPT1, Print Manager displays:

    !Error

in the Status column for that printer.

In the Status bar at the bottom of the Print Manager, the following

messages are also displayed:

   The Printer is Stalled.

   The computer name is invalid.

WORKAROUND

==========

To work around this problem, reduce the length of the computer name to

13 characters or less.

STATUS

======

Microsoft has confirmed this to be a problem in Windows for Workgroups

version 3.1 and version 3.11. We are researching this problem and will post

new information here as it becomes available.

Additional reference words: 3.1 3.10 wfwg 3.11


Schedule+ Q&A: Remote Usage

Article ID: Q92642

---------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

 - Microsoft Schedule+ for Windows, version 1.0

---------------------------------------------------------------

SUMMARY

=======

This article provides answers to common questions about moving your

copy of Schedule+ from one machine to another, as well as accessing

your copy from another machine.

MORE INFORMATION

================

1. Q. How do you take Schedule+ "on the road"?

   A. If you want to take your calendar with you to another machine

      (for example, a portable for travel), use the Move

      Local File command on the File menu to copy the calendar to a

      floppy disk.

      Then, load Schedule+ on the destination computer. Use the Move

      Local File command to move it back. The command moves the

      calendar file to the location you specify and changes the

      SCHDPLUS.INI file so it searches for your calendar in the new

      location. This command might also be used if you decide you

      want to keep your calendar in the directory where you store

      data instead of in the Schedule+ program directory.

2. Q. Does Schedule+ have a "dial-in" capability?

   A. No. You can use Schedule+ offline (as described above) to

      view your local calendar or use LAN Manager RAS to access your

      calendar at the office, view other people's calendars, and

      schedule meetings. However, you cannot dial in, like you can

      with the MS-DOS Mail remote client. Also note that when you use

      Schedule+ offline, you cannot use any of the group-related

      capabilities. You cannot generate meeting requests and leave

      them in your outbox (like you do when you are using the Windows

      Mail client).

Additional reference words: plus 1.0 wfwg 3.1 3.10


Schedule+ Q&A: MS-DOS, Macintosh, and Connectivity

Article ID: Q92645

---------------------------------------------------------------

The information in this article applies to:

 - Microsoft Schedule+ for Windows, version 1.0

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

---------------------------------------------------------------

SUMMARY

=======

This article lists questions and answers regarding MS-DOS and

Macintosh connectivity with the Schedule+ program included with

Windows for Workgroups.

MORE INFORMATION

================

1. Q. Can you participate in a Schedule+ account if you are running

      the Macintosh Client of Microsoft Mail for PC Networks?

   A. No. To run Schedule+, one of the following conditions must exist:

      - You are running a Mail 3.0 Windows client against a Microsoft

        Mail Post Office (or another transport with a messaging driver

        transport).

      - You are running Mail for AppleTalk Networks. In this case, you

        can run Schedule+ for AppleTalk networks.

2. Q. Why is there no bridge between Schedule+ for Windows and Schedule+

      for AppleTalk Networks so that users on the two platforms can share

      free/busy information and send meeting requests to each other?

   A. Currently there are no plans for future development of Schedule+

      for AppleTalk Networks. Microsoft's development resources on the

      Macintosh platform are limited; the highest priority is to develop

      new versions of Mail for AppleTalk Networks. A new calendar and

      scheduling solution for the Macintosh would need to be developed

      to achieve transport independence.

3. Q. What is the Schedule+ connectivity format?

   A. It is a specification of a file format that allows third-party

      MS-DOS and Windows scheduling applications to share free/busy

      information and exchange meeting requests with Schedule+. This

      format allows Microsoft to point a customer to a third-party

      vendor  for an MS-DOS scheduling solution that works with

      Schedule+.

      The format was designed to support the use of group scheduling

      applications from different vendors on a network. The specification

      describes an interchange format that scheduling applications can

      read and write so that users of third-party products can see

      free/busy data of a Schedule+ user and vice versa. It also

      describes how, using FFAPI (Mail File Format API), these

      applications can send meeting requests and responses to Schedule+,

      and interpret meeting requests received from Schedule+.

      Note that any product can share free/busy information with

      Schedule+, but only products using Microsoft Mail as the

      transport (or in the future any application that supports MAPI)

      can exchange native meeting requests. A copy of the specification

      can be found in the Sourcebook.

Additional reference words: 3.1 3.10 1.0 plus wfwg interoperation

3.11 interoperability


Schedule+ Q&A: Time and Date Issues

Article ID: Q92672

---------------------------------------------------------------

The information in this article applies to:

 - Microsoft Schedule+ for Windows, version 1.0

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

---------------------------------------------------------------

SUMMARY

=======

This article lists questions and answers about the time and date

features in the Schedule+ program included with Windows for

Workgroups.

MORE INFORMATION

================

1. Q. Are there options for altering the time and date displays (for

      example, to use a 24-hour or a European date format)?

   A. Yes. From the Windows Control Panel, choose the International

      icon. Here you can specify the format used for the date

      and the time. This change is reflected in Schedule+ also.

2. Q. Does Schedule+ account for time zone changes when a you request

      a meeting with someone in another time zone?

   A. No. However, if you have upgraded to Microsoft PC Mail version

      3.0, you can modify the template files (using TEMPLATE.EXE) to

      include a field for time zones. This way, you can at least find

      out what time zone somebody is in by selecting Details.

Additional reference words: 3.1 3.10 plus 1.0 wfwg 3.11


Schedule+ Q&A: Scheduling Meetings

Article ID: Q92698

---------------------------------------------------------------

The information in this article applies to:

 - Microsoft Schedule+ for Windows, version 1.0

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

---------------------------------------------------------------

SUMMARY

=======

This article lists common questions and answers about scheduling

meetings with Schedule+.

MORE INFORMATION

================

1. Q. Does Schedule+ include all hours of each day as valid

      meeting times when the Auto-Pick command is used to search

      for a meeting time?

   A. To determine a meeting time, Auto-Pick looks only at weekdays

      (Monday-Friday) within the time defined by the Day Starts At

      and Day Ends At settings in the General Options dialog box.

      Schedule + looks only at the meeting initiator's settings to

      determine the valid times. Schedule+ does not recognize the

      nonworking hours of other users and you cannot define days

      other than Saturday or Sunday as nonworking days.

2. Q. Does Schedule+ support recurring meetings? For example, can I

      request a weekly staff meeting with my group so that when those

      people accept the meeting, it is automatically entered into their

      calendars for each week?

   A. Schedule+ supports recurring APPOINTMENTS, but not recurring

      MEETINGS. Schedule+ does not allow a you to request a recurring

      meeting with other people. This means you must request the meeting

      for a single occurrence and then remind the attendees to use the

      recurring appointment command to enter it for each week.

Additional reference words: 3.1 3.10 plus 1.0 wfwg non-working


Schedule+ Q&A: OLE and Attachments

Article ID: Q92699

---------------------------------------------------------------

The information in this article applies to:

 - Microsoft Schedule+ for Windows, version 1.0

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

---------------------------------------------------------------

SUMMARY

=======

This article lists common questions about using object linking and

embedding (OLE) or attachments with the Schedule+ program included

with Windows for Workgroups.

MORE INFORMATION

================

1. Q. Does Schedule+ support OLE?

   A. Schedule+ does not support OLE in any way. You cannot embed

      objects in appointments, in the notepad, or in the meeting

      request messages. This may be confusing because a meeting

      request message is a specialized Microsoft Mail message, and

      Mail supports OLE. However, Schedule+ does not support this

      feature.

2. Q. Does Schedule+ support attachments, so that I can attach an

      agenda to my meeting request or attach a note to an appointment

      in my daily calendar?

   A. Schedule+ does not have an attachments feature per se. However,

      you can type an unlimited quantity of text into the appointment

      description. You can even scroll through the appointment entry

      using the cursor key. To see the entire note text in your

      calendar printout, you must print using the Text View format.

Additional reference words: plus 1.0 3.1 3.10 wfwg 3.11


Schedule+ Q&A: Reminders Application

Article ID: Q92700

---------------------------------------------------------------

The information in this article applies to:

 - Microsoft Schedule+ for Windows, version 1.0

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

---------------------------------------------------------------

SUMMARY

=======

The following are common questions and answers about the Reminders

application that is included with the Schedule+ component of Microsoft

Windows for Workgroups.

MORE INFORMATION

================

1. Q. Does Schedule+ support customized reminder sounds?

   A. Yes. If the user is running Windows 3.1 he/she can modify the

      sound that is assigned to the Schedule+ Reminders in the

      Sound Control Panel. (Note: A sound driver must be installed

      first in the Control Panel Drivers)

2. Q. How does the Reminders application work?

   A. The Reminders application is a separate application from

      Schedule+. The default installation (that is, Express Setup)

      installs Reminders into the Windows Startup group. This

      explains why you are asked to sign in when you start Windows,

      but after you sign in, no application seems to be started.

      In reality Reminders has started, but because it is a hidden

      application, this is not apparent. Reminders continues to run

      until you exit Windows or choose Turn Off Reminders from the

      File menu in Schedule+. You will be reminded of upcoming

      appointments while you are running Windows or any other Windows

      application.

Additional reference words: 3.1 3.10 1.0 1.00 plus wfwg 3.11


Schedule+ Q&A: Printing

Article ID: Q92705

---------------------------------------------------------------

The information in this article applies to:

 - Microsoft Schedule+ for Windows, version 1.0

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

---------------------------------------------------------------

SUMMARY

=======

This article contains specific questions and answers regarding the

Schedule+ component of Microsoft Windows for Workgroups.

MORE INFORMATION

================

1. Q. Can you customize print views in Schedule+?

   A. There are no printing customization capabilities built into

   Schedule+. However, you can export your appointments into Schedule+

   (either ASCII text or text format) and then use a standard text editor

   to customize the information.

2. Q. When printing from Schedule+ there are three different print sizes.

   What are the dimensions of these print sizes?

   A. The formats are designed to match the most popular appointment book

   sizes:

       Standard = 8 1/2"  x  11 1/2"

       Junior = 5 1/2"  x  8 1/2"

       Pocket = 3 3/4"  x  6 3/4"

Additional reference words: plus 1.0 3.1 3.10 wfwg 3.11


WFWG Err Msg: "Extended Error 65" or "File Manager Cannot..."

Article ID: Q92708

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

SYMPTOMS

========

If you try to rename a file, copy a file to another filename, or

otherwise alter a file shared from a Windows for Workgroups server

from within the MS-DOS Prompt of another Windows for Workgroups

machine, you may receive the following error message:

   Extended Error 65

If you attempt to alter a file shared from a Windows for Workgroups

server from File Manager on another Windows for Workgroups machine,

you may receive the following error message:

   File Manager cannot create or replace <Filename>:

   Access Denied. Make sure the disk is not full or

   write-protected.

CAUSE

=====

These errors occur because the share is designated as having read-only

access from the server machine.

RESOLUTION

==========

To resolve the problem, assign full-access permission for the share on

the Windows for Workgroups server, as follows:

1. In the File Manager application, choose Share As from the Disk

   menu.

2. From the Access Type list, select Full.

Additional reference words: 3.10 wfwg FM access password properties


3Com EtherLink II Card Not Detected During Setup of WFWG

Article ID: Q92771

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

----------------------------------------------------------------------

SUMMARY

=======

When you run the Windows for Workgroups (WFWG) Setup program, the 3Com

EtherLink II network card may not be detected if the card is not

initialized or if it is using an input/output (I/O) address of 0300h.

NOTE: The network card will be initialized if you load a network

software driver, such as IPX.COM, to your system.

If the card is not detected, you must set it up up manually when you

run the Setup program or you must use the Network option in the

Windows Control Panel after the setup is complete.

MORE INFORMATION

================

The Windows for Workgroups Setup program sets the transceiver type to

external, regardless of the actual transceiver setting. The

transceiver location is determined by the type of network cabling you

are using:

 - Thin Ethernet networks and twisted-pair networks (in the case of

   the EtherLink II TP card) use the transceiver located on the

   EtherLink II card.

 - Thick Ethernet networks use an external transceiver with the 3Com

   Etherlink II cards.

To change the transceiver location for a 3Com card:

1. In the Windows Control Panel, choose the Network icon.

2. Select the Adapters option and select Advanced.

The default setting for the 3Com Etherlink II cards is External. If

you are using thin Ethernet or twisted pair, change this setting to

Onboard.

NOTE: If you run Windows for Workgroups with Novell NetWare

connectivity  on a network that has thick EtherNet cabling, you may

receive the following error message:

   A File Server Could Not Be Found

This type of cable, also known as thicknet or 10Base5, uses external

transceivers. Many network adapter cards need to be properly

configured to use this cable. To configure your network properly:

1. Run Control Panel.

2. Select the Networks option.

3. Choose Adapters, and select External transceiver.

For example, a 3COM Etherlink II netcard must have the transceiver set

to External to attach to a Netware server, otherwise the error

message appears.

Additional reference words: 1.0 1.00 3.1 3.10 LAN Manager LANman elink

3.11 elinkii elinkii.DOS wfw wfwg win31


No Files Found with SMC 90C65 Based Arcnet Cards in WFWG

Article ID: Q92772

---------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

---------------------------------------------------------------

SYMPTOMS

========

Arcnet network interface cards based on the Standard Microsystems

Corporation (SMC) 90C65 controller chip may generate the "No Files

Found" error when you attempt to view a directory of a network drive

in File Manager with Microsoft Windows for Workgroups (WFWG).

RESOLUTION

==========

There is no work around for this problem. The only correction is a

hardware modification to the card. Contact the manufacturer of the

network card for specific information on upgrading the affected chip.

MORE INFORMATION

================

If a network card with this chip is used on a Windows for Workgroups

server with the NetBEUI protocol, a Windows for Workgroups workstation

can browse and successfully connect to the server, but the "No Files

Found" error is generated even though there are files in the shared

directory. Other symptoms of this problem are the inability to run:

 - Novell's TurboKit drivers

 - Artisoft's Lantastic SMCARC drivers

 - Possibly other NetBEUI protocol networking software products

The SMC120 Arcnet card uses their top-of-the-line ASL30519 Arcnet

controller chip. The SMC 90C65 Arcnet Controller Chip contains a

subset of the instructions in SMC's ASL30519 Arcnet Controller Chip.

The 90C65 chip is used in several OEM Arcnet network interface cards,

but is not used in any SMC Arcnet boards.

The products included here (other than Windows) are manufactured by

vendors independent of Microsoft; we make no warranty, implied or

otherwise, regarding these products' performance or reliability.

Additional reference words: 3.10 3.1 wfwg wfw win31 err msg

3.11 winhwre 3rdparty


WFWG: Problems when Windows Express Version 3.0 Run as Shell

Article ID: Q92773

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

----------------------------------------------------------------------

The following article contains information on the use of 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

========

If you use hDC Windows Express 3.0 as the Windows shell with Microsoft

Windows for Workgroups, the following errors may occur:

 - The LOAD= and RUN= lines in the WIN.INI file may not run correctly.

 - Closing Windows Express may not end the current Windows session.

CAUSE

=====

Because of the differences between the shell logic used in Windows

Express and Windows for Workgroups, Windows Express loads itself as a

normal application without establishing a Windows shell. Because no

shell has been established, the only way to end the Windows session is

to restart (reboot) the computer.

WORKAROUND

==========

To work around this problem, use Program Manager as the Windows shell

and do one of the following to run Windows Express:

 - Use Windows Program Manager to Add an icon for Windows Express to

   the StartUp group.

   -or-

 - Add EXPRESS to the RUN= line in your WIN.INI file.

MORE INFORMATION

================

When you use Windows Express version 3.0 as the Windows shell, it

expects to be started before all other Windows applications. However,

when you use this application with Windows for Workgroups, Windows

Express cannot be started first because Windows for Workgroups starts

two hidden applications (NETDDE.EXE and CLIPSRV.EXE) prior to loading

Windows Express.

This feature is by design.

For additional information about Windows Express, contact hDC Computer

Corporation.

hDC Windows Express 3.0 is manufactured by hDC Computer Corporation, a

vendor independent of Microsoft; we make no warranty, implied or

otherwise, regarding this product's performance or reliability.

Additional reference words: 3.10 3.1 wfwg wfw win31 3rdparty 3.11


Setup Overwrites _DEFAULT.PIF and DOSPRMPT.PIF

Article ID: Q92776

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

During Windows for Workgroups Setup, the two program information files

(PIFs) _DEFAULT.PIF and DOSPRMPT.PIF are overwritten.  Windows for

Workgroups Setup overwrites these two files to ensure that they are in

the proper format for a Windows 3.1 PIF. Windows 3.0 PIFs have

slightly different formats.

To preserve any changes you might have made to these files, rename

them before you run Setup.

Additional reference words: 3.10 wfwg 3.11


WFWG Setup Modifies Wrong Lines in CONFIG.SYS

Article ID: Q92780

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

SYMPTOMS

========

Microsoft Windows for Workgroups Setup may ignore REM statements in

the CONFIG.SYS file. If you are using a utility such as Bootcon, this

can create configuration problems because Bootcon uses REMs to delimit

multiple boot configurations. Windows for Workgroups Setup may

inadvertently modify the wrong configuration. For example, Setup may

change the path of the Microsoft LAN Manager Net command to the

Windows for Workgroups directory.

WORKAROUND

==========

To avoid this problem, back up CONFIG.SYS before you install Windows

for Workgroups. After installation, you may need to edit the

CONFIG.SYS file to ensure Windows for Workgroups drivers and other

network drivers are correctly loaded under the proper boot

configuration.

As an alternative, you can upgrade to MS-DOS 6.2 and use the

Multi-Config feature instead of Bootcon.

STATUS

======

Microsoft has confirmed this to be a problem in Windows for Workgroups

version 3.1 and version 3.11. We are researching this problem and will

post new information here as it becomes available.

Additional reference words: 3.10 3.11 wfwfest multi-boot multi-config


Must Use Quotation Marks if Shared Resource Names Have Spaces

Article ID: Q92781

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

If a shared resource name includes a space, you must use quotation

marks around the name whenever you refer to the resource in a dialog

box or at the command prompt. For example, if you name your computer

"My Computer," you must use quotation marks in the NET USE command

line as follows:

   NET USE F: "\\My Computer\Public"

NOTE: While this works for the NET USE command, Microsoft recommends

that you do not put a space in your computer name. Microsoft Mail may

fail if the computer name contains a space.

Additional reference words: 3.10 wfwfest wfwg 3.11


3Com EtherLink III (3C509) in EISA Machines

Article ID: Q92788

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.1

--------------------------------------------------------------------

SYMPTOMS

========

If the 3Com EtherLink III (3C509) network card is configured in EISA mode

and is in an EISA machine, the driver (ELNK3.DOS) fails to load when you

start the system.

CAUSE

=====

This problem occurs on any EISA bus machine that has only one EISA

3Com EtherLink III card because Windows for Workgroups version 3.1 Setup

adds an IOADDRESS= parameter to the PROTOCOL.INI file.

NOTE: This problem does not occur in later versions of Windows for

Workgroups.

WORKAROUND

==========

Remove the IOADDRESS= line from the appropriate section of the PROTOCOL.INI

file.

MORE INFORMATION

================

The EISA mode of the 3Com EtherLink III card forces the card to an I/O

address that cannot be set from Control Panel. Later, when the machine is

restarted, the driver (ELNK3.DOS) double-checks to see that a driver is

present at the IOADDRESS= location. In the EISA case, this is not true so

the driver reports an error, and does not load.

Because the ELNK3.DOS driver can find the EtherLink III card in either an

ISA bus or an EISA bus machine, it does not need the IOADDRESS= or SLOT=

parameter in the PROTOCOL.INI file. These settings should only be used if

there is more than one EtherLink III card in the machine.

Additional reference words: ether link wfwg set up boot 3C579


WFWG Err Msg: Add SystemROMBreakpoint=FALSE to SYSTEM.INI

Article ID: Q92790

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

 - Microsoft Windows operating system version 3.1

--------------------------------------------------------------------

SYMPTOMS

========

If you install Windows or Windows for Workgroups when the third-party

memory manager is not loaded, and then later you activate the memory

manager, you may receive an error message stating that the

"SystemROMBreakpoint=FALSE" line must be added to your SYSTEM.INI

file.

You may also receive this error message if you do not indicate where

the WINDOWS directory is located when you install a third-party memory

manager.

WORKAROUND

==========

To work around either of the above situations, add the

"SystemROMBreakpoint=FALSE" line to the [386enh] section of the

SYSTEM.INI file.

MORE INFORMATION

================

The "SystemROMBreakpoint=FALSE" line should be installed in the

SYSTEM.INI file by the Setup program for Windows for Workgroups or

Windows when some third-party memory managers (such as QEMM, 386MAX,

and BlueMAX) are installed.

Additional reference words: 3.10 3.11 wfwg win31


File Manager Does Not Allow Copying of Open Files

Article ID: Q92791

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

 - Microsoft Windows operating system version 3.1

--------------------------------------------------------------------

SUMMARY

=======

If you use File Manager to copy a file that is being used by another

application, the following error message is generated:

   Access denied, source file may be in use.

However, if you use the COPY command from MS-DOS Prompt to copy a file

that is being used by another application, the file copies

successfully.

MORE INFORMATION

================

For security reasons, File Manager refuses to copy files that another

application might be in the process of changing. The COMMAND.COM

portion of MS-DOS does not check to see of if the file is being

changed by another application.

NOTE: To avoid losing data, do not try to copy files that are being

modified by either Windows-based or MS-DOS-based applications.

Additional reference words: 3.10 3.11 open file copies open-file


WFWG: Exiting from Shell Does Not Exit Windows for Workgroups

Article ID: Q92793

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

SUMMARY

=======

Some shell programs may not behave correctly when you run them with

Windows for Workgroups; when you exit these shell programs, you may

not exit Windows. In this situation, the correct behavior for a shell

program is to exit windows.

An example of a shell program is Windows Program Manager. When you

exit Program Manager, you also exit Windows.

MORE INFORMATION

================

In Windows version 3.0, an application determines that it is the shell

by checking the number of tasks that are currently running. Because

Windows for Workgroups starts some tasks before the shell, this manner

of determining shell status does not work. To correctly determine

shell status, applications should check the "shell=" line in the

[boot] section of SYSTEM.INI file.

For information about how your shell determines shell status, contact

the supplier of your shell program.

Workaround

----------

1. Create a directory called WINDOWS\WFWINIT.

2. Copy the following files from your WINDOWS directory to the newly

   created WINDOWS\WFWGINIT directory:

      PRINTMAN.EXE

      CLIPSRV.EXE

      NETDDE.EXE

3. Delete or rename the original files.

4. Create program items in your startup group that start each of these

   files from the WINDOWS\WFWGINT directory.

Additional reference words: 3.10 3.11 WFW WFWG


File Manager: Can't Redirect Local Drives; Use Net Redirector

Article ID: Q92871

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

You cannot redirect or substitute a network drive for a local drive in

File Manager. If you need this functionality, use the MS-DOS-based

real-mode redirector, Net.

In general, redirecting local drives is not recommended. However, in

some cases, you may need to do this in order to work with a program

that is hard-coded for a specific drive. For example, some

installation programs allow you to install from the drive A only. You

can redirect drive A to a network drive with Net and then use the

installation program successfully.

Additional reference words: 3.10 3.11 wfwg


After Failed WFWG Setup, Not Enough Space to Setup Again

Article ID: Q92872

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

SYMPTOMS

========

Microsoft Windows for Workgroups Setup does not perform an upgrade

over Microsoft Windows version 3.1 if it does not detect enough free

disk space. If Setup fails for some reason and you run Setup a second

time, it may refuse to upgrade your system.

CAUSE

=====

This problem occurs if Setup incorrectly detects insufficient free

disk space. Setup assumes it is upgrading Windows 3.1 and does not

account for the Windows for Workgroups files it has already

transferred.

WORKAROUND

==========

To work around this problem, delete some Windows for Workgroups files

before you start Setup. The following are some files you can safely

delete:

   NETAPI.DLL

   PMSPL.DLL

   WIN386.EXE

You can also delete files with the extensions .BMP and .HLP. These

files are copied again when you run Setup.

NOTE: Avoid deleting files with the extensions .INI and .GRP. Such

files contain information about your custom Windows configuration.

MORE INFORMATION

================

Windows for Workgroups Setup uses WINVER.EXE to determine which

version of Windows it is installing over. Unfortunately, WINVER.EXE is

one of the last files to transfer. Often in a failed installation,

WINVER.EXE does not get copied; therefore, Setup thinks that it is

upgrading Windows 3.1.

Additional reference words: 3.10 3.11 wfwg


Windows for Workgroups Hangs at Logo Screen

Article ID: Q92873

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

SYMPTOMS

========

Your computer may stop responding (hang) when the Windows for Workgroups

(WFWG) 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 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 verify these settings, choose

   the Network icon from Control Panel.

   To correct your settings, delete the PROTOCOL.INI, PROTMAN.DOS

   (WFWG 3.1 only), WORKGRP.SYS (WFWG 3.1 only), and other Workgroup

   network driver files. Then, from Control Panel, choose the Network

   icon, and indicate the correct network adapter and configuration

   settings.

   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

Additional reference words: 3.10 3.11 protman halt wfwg tshoot


WFWG: Err Msg: Invalid Keyword/Argument. Check Configuration.

Article ID: Q92874

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

SYMPTOMS

========

When you use the Windows Driver Library (WDL) driver for the Racal

Interlan AT network interface card (NIC), RACAL.EXE, you may receive

the following error message:

   Invalid keyword/argument. Check configuration.

WORKAROUND

==========

To correct this problem, locate the entry below in PROTOCOL.INI

   [MS$ILANAT_NIF]

   Drivername=NP600$

and modify it to read

   [MS$ILANAT_NIF]

   Drivername=ILANAT$

NOTE: Each time you change network settings in Control Panel, this

entry is reset to the incorrect value. You must modify PROTOCOL.INI

each time you change network settings.

Additional reference words: 3.10 3.11 wfwg


NET.EXE Pop-up Interface Hard to Read on Monochrome Monitors

Article ID: Q92876

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

SYMPTOMS

========

If you use a color display adapter with a monochrome monitor, you may

have trouble reading the NET.EXE pop-up interface.

MORE INFORMATION

================

If NET.EXE detects a monochrome display, it adjusts the colors

appropriately. But if you use a color display adapter with a

monochrome monitor, you need to use the MS-DOS MODE command to set the

display type as follows:

   mode mono

This ensures that the interface is readable.

Additional reference words: 3.10 wfwg pop up 3.11


WFWG may Hang if TCP/IP hasn't Registered at Logon Time

Article ID: Q92877

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

The following article contains information on the use of 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

========

If you load TCP/IP as a protocol and then immediately start Windows

for Workgroups from your AUTOEXEC.BAT file, your machine may stop

responding (hang) when you attempt to log on.

CAUSE

=====

This problem occurs because TCP/IP requires time to register on the

network before you log on.

WORKAROUND

==========

To work around the problem, place a pause statement in your AUTOEXEC.BAT

file before the statement that starts Windows, as in the following example:

   pause

   win

You can also use the MS-DOS 6.0 and 6.2 CHOICE command to force a timed

pause (for example, use "c:\dos\choice /N /T:n,10 Please wait for the

computer to register with the network..."). Refer to your MS-DOS

documentation for more information.

STATUS

======

This problem occurs with the versions of TCP/IP that shipped with Windows

for Workgroups 3.11 and Microsoft LAN Manager. This problem may or may not

occur with other implementations of TCP/IP.

Microsoft has confirmed this to be a problem in Windows for Workgroups

version 3.1 and version 3.11. We are researching this problem and will

post new information here in the Microsoft Knowledge Base as it

becomes available.

Additional reference words: 3.10 stack wfwfest wfwg


WFWG NET.EXE Err Msg: MS-DOS Popup for Workgroups Could Not...

Article ID: Q92878

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

---------------------------------------------------------------------

SYMPTOMS

========

You may receive the following error message in Windows for Workgroups

if you try to remove NET.EXE from memory:

   MS-DOS Popup for Workgroups could not be removed

CAUSE

=====

This error is generated if you attempt to unload terminate-and-

stay-resident (TSR) programs out of sequence. To remove TSR programs,

you must unload them in the reverse sequence that you loaded them.

(For example, you would first unload the last driver you loaded.)

MORE INFORMATION

================

NET.EXE can be loaded each time you need it, or you can load it as a

TSR with the NET STOP POPUP command. If you load a TSR after NET.EXE,

you must first unload that TSR before you unload NET.EXE.

This problem often occurs if you load TSRs from the AutoStart line in

the [network] section of the SYSTEM.INI file.

Additional reference words: 3.10 3.11 lifo wfwg


Mail Reports Bad Network Connection When Low On Disk Space

Article ID: Q92880

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

SYMPTOMS

========

Mail sometimes shows a bad network connection icon in its status bar

when the network is functioning correctly. For example, you may see

the bad network connection icon and you can still use File Manager to

connect to your mail server. You may also receive mail while Mail is

displaying the bad network connection.

CAUSE

=====

The icon is displayed because you are very low on disk space. The icon

is trying to tell you that it failed to download a message because

there was insufficient space in your mail file. Mail waits and retries

5 minutes later.

STATUS

======

Microsoft has confirmed this to be a problem in Windows for Workgroups

Mail version 3.1 and version 3.11. We are researching this problem and

will post new information here as it becomes available.

Additional reference words: 3.10 wfwg 3.11


Installing WFWG over IBM Lan Server Causes Netbind Error

Article ID: Q92881

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

SYMPTOMS

========

If you install Windows for Workgroups on a machine that was once an

IBM OS/2 Lan Server client, you may receive a "Netbind" error followed

by an "Undefined Dynalink" error when you start Windows for

Workgroups.

CAUSE

=====

These errors indicate that there are still IBM Lan Server drivers in

the CONFIG.SYS and AUTOEXEC.BAT files.

RESOLUTION

==========

The following lines need to be removed or remarked out (using REM)

from the CONFIG.SYS file:

 - Any lines that reference PROTMAN.EXE (Windows for Workgroups uses

   PROTMAN.DOS)

 - Any lines that reference DXMEOMOD.SYS

In the AUTOEXEC.BAT file, any reference to the Lan Server software

directory in the PATH= statement should be removed.

Additional reference words: 3.10 3.11

 \*


Schedule+ Q&A: Modifying Other Calendars

Article ID: Q92885

---------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

 - Microsoft Schedule+ for Windows, version 1.0

---------------------------------------------------------------

SUMMARY

=======

This article discusses creating appointments in another person's

schedule using the Schedule+ component of Windows for Workgroups.

MORE INFORMATION

================

1. Q. Are meetings entered by someone other than myself distinguished in

   any way?

   A. Yes. If you double-click an appointment created by someone else, the

   name of the person who created it is displayed at the bottom of the

   appointment details. However, the appointment is not identified by an

   icon or special color in the appointment book.

2. Q. How do you sign in as another user in order to view or modify that

   person's calendar?

   A. You do not need to sign in as another user in order to open that

   person's calendar. Schedule+ allows you to grant access privileges to

   other users with the Options/Set Access Privileges command. Once you

   have assigned privileges to another user, that person can view your

   calendar while signed in under his/her own account by choosing Open

   Other's Appointment Book from the File menu.

3. Q. When I have an Assistant, do we both receive meeting messages for my

   meetings or does only my Assistant receive them?

   A. You can specify either of the above. If you choose General Options

   from the Options menu, you can see a check box that specifies Send

   Meeting Messages Only to my Assistant.

Additional reference words: 3.1 3.10 3.11 plus 1.00 sched plus wfwg


Schedule+ Q&A: Tasks

Article ID: Q92886

---------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

 - Microsoft Schedule+ for Windows, version 1.0

---------------------------------------------------------------

SUMMARY

=======

This article discusses managing tasks using the Schedule+ component of

Microsoft Windows for Workgroups.

MORE INFORMATION

================

1. Q. Do tasks "roll over" from one day to the next if they are not

   completed?

A. Schedule+ has a model for tasks that is different from most programs of

   this type. Tasks are not associated with a particular day (however, you

   can assign a due date). You enter and view tasks in Tasks mode, which

   is completely different from Appointment Book mode. By the nature of

   this model, tasks are always present until you complete them or delete

   them from the list.

   The Show Active Tasks command allows you to view current tasks (those

   without a due date or with a due date or start work date prior to

   today) only. By contrast, other scheduling programs follow a model in

   which tasks are created on a particular day. Using that model, tasks

   may not appear until that day and then "roll over" to following days

   until they are completed.

2. Q. Is there any interaction between Microsoft Project and Schedule+ so

   that tasks assigned to me in Project can be put in my task list?

A. In the version of Schedule+ that ships with Windows for Workgroups 3.1,

   other applications cannot make calls to Schedule+. This feature is

   under review and will be considered for inclusion in a future release.

Additional reference words: 3.10 3.11 1.00 sched plus wfwg


UB Cards Not Initialized If Memory Window Is Not Excluded

Article ID: Q92916

---------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

---------------------------------------------------------------

SYMPTOMS

========

Ungermann-Bass Ethernet cards use a shared-memory window in the upper

memory area (UMA). The Network Driver Interface Standard (NDIS) media

access control (MAC) driver attempts to initialize the card when it

loads. During this process, it initializes the shared-memory window;

however, if a memory manager has been set up to use this memory

window, initialization fails.

If the memory window has not been excluded from an upper memory

manager (such as EMM386), error messages similar to those below may be

displayed when the media access control driver loads:

   MS$NIUPCTP: Initialization started.

   MS$NIUPCTP: The NIU failed its diagnostic tests. Please check the

   network connection, configuration parameters, and hardware

   installation.

   MS$NIUPCTP: Initialization failed.

When NET.EXE attempts to bind, you also receive the following error

message:

   Error 5733: The protocol manager has reported an incomplete binding.

WORKAROUND

==========

To correct this problem, exclude the shared-memory window with your

memory manager. Using EMM386.EXE, exclude the memory address for the

shared-memory window by specifying the X= parameter on the device line

in the CONFIG.SYS file for EMM386. For example, for the Ungermann-Bass

NIUpc with the shared-memory windows configured for D800-DFFF, you

would use the following:

   DEVICE=C:\WINDOWS\EMM386.EXE NOEMS X=D800-DFFF

NOTE: The Ungermann-Bass NIUpc/EOTP is software configurable for A000,

A800, B000, B800, C000, C800, D000, D800, E000, E800. The most common

default configurations are D800-DFFF or C800-CFFF.

The Ungermann-Bass products included here are manufactured by a vendor

independent of Microsoft; we make no warranty, implied or otherwise,

regarding these products' performance or reliability.

Additional reference words: 3.10 3.11 MAC wfwg


Schedule+ Q&A: Scheduling Resources

Article ID: Q92917

---------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

 - Microsoft Schedule+ for Windows, version 1.0

---------------------------------------------------------------

SUMMARY

=======

This article discusses setting up and scheduling of Resources with

the Schedule+ component of Microsoft Windows for Workgroups.

MORE INFORMATION

================

1. Q. How do you set up a resource, such as a conference room?

   A. Schedule+ makes it easy to set up shared resources such as

      conference rooms and Audio/Visual equipment so that they can

      be reserved over Schedule+. The network administrator creates

      an account for the resource using the Mail Admin program. Then

      he/she logs into Schedule+ under that account and selects the

      This Account Is For A Resource check box in the General

      Options dialog box (accessed by choosing General Options from

      the Options menu).

      This automatically changes the default access privilege to

      "create appts and tasks." That means that people can book the

      resource by selecting it from the address book while they select

      attendees for a meeting. Users will also be able to use the File,

      Open Other's Appt Book command to look at the calendar for the

      resource and book time in it directly. It is also possible to

      assign an assistant to a resource and alter the default privilege

      to View Free and Busy Times if the administrator wants somebody

      to be in control of allocating the resource.

2. Q. Because each resource requires a user account, does this mean that

      each resource requires a user license?

   A. No. Microsoft licensing requires a license per workstation that

      runs the software, not per user account.

Additional reference words: 3.1 3.11 3.10 1.0 1.00 plus wfwg resource


Schedule+ Q&A: Display

Article ID: Q92918

---------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

 - Microsoft Schedule+ for Windows, version 1.0

---------------------------------------------------------------

SUMMARY

=======

This article discusses customizing the display of the Schedule+

component of Windows for Workgroups.

MORE INFORMATION

================

1. Q. Can the display be customized to show different colors?

   A. Yes. This can be done by choosing Display from the Options menu and

   adjusting the settings.

2. Q. Can users customize the display of time intervals in the daily

   calendar (for example, to display the day in 15-minute intervals)?

   A. It is not possible to customize the view; however, you can schedule

   appointments to start or end at any time. To alter a start or end time

   to something other than :00 or :30, double-click the appointment and

   use the Start or End controls to change the time. The start time is

   displayed in the appointment description and is used to set off the

   reminder at the appropriate time.

Additional reference words: 3.1 3.10 3.11 1.0 1.00 plus video wfwg

color


Persistent Connections May Not Work with Real Mode Redirector

Article ID: Q92989

----------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

----------------------------------------------------------------

SUMMARY

=======

Windows for Workgroups has a persistent connections feature that

automatically reconnects the workstation to previously connected

network shares when the redirector is started. This feature should

work with either the real mode redirector (NET.EXE) or the virtual

redirector (VREDIR.386).

In the Windows for Workgroups Connect Network Drive dialog box, the

Reconnect At Startup check box controls whether or not the network

drive connections you make are persistent (remain connected until you

disconnect them or clear the Reconnect At Startup check box).

If the real mode redirector is started and this check box is not

selected, persistent connections are not made.

MORE INFORMATION

================

The Reconnect At Startup check box is selected by default, but if you

clear this option, the setting remains deactivated until you select it

again. The setting for this check box is maintained in the [Network]

section of the SYSTEM.INI file. If the check box is selected, the

Reconnect= line is set to Yes.

The virtual redirector and the real mode redirector interpret this

switch in different ways. The virtual redirector uses this switch to

determine whether the Reconnect At Startup check box should be

selected the next time you open the Connect Network Drive dialog box.

The real mode redirector uses this switch to determine whether network

drive connections made while the redirector is started will be

persistent. If the switch is off (that is, the Reconnect At Startup

option is not selected), the persistent connections are not made when

the real mode redirector is started.

Additional reference words: 3.10 wfwg win31 saved ms-dos 3.11


Network Print Jobs May Disappear from Print Manager in WFWG

Article ID: Q92996

------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

------------------------------------------------------------------

SYMPTOMS

========

On a Windows for Workgroups server that is sharing a local printer, network

print jobs may disappear from the Print Manager. If the local printer

encounters an error, such as running out of paper, while printing a local

job and other network jobs are queued, the Print Manager pauses and the

first network job listed in the queue disappears. If more than one network

job is waiting to print, the second and subsequent network print jobs are

not affected. This error only occurs if the current print job is from the

local machine.

There is no way to recover a lost network print job; you must resend it to

the printer.

STATUS

======

Microsoft has confirmed this to be a problem in Windows for Workgroups

version 3.1 and version 3.11. We are researching this problem and will post

new information here as it becomes available.

Additional reference words: 3.10 wfwg win31 remote 3.11


No Drop Cables Allowed from Thin Ethernet T-Connector to NIC

Article ID: Q93019

---------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

---------------------------------------------------------------

SUMMARY

=======

The following configuration is not supported by 802.3 10BASE2 (Thin

Ethernet) cable:

    tT ----RG58/u (Main Cable)-------------Tt

     |	|

     |<---RG58/u (Drop Cable)	|

     |	|

    NIC	       NIC

Key

---

t = terminator

T = T-connector

NIC = network interface card

The additional drop cable depicted in the above diagram should not be

used. The T-connector should be connected directly to the network

interface card.

MORE INFORMATION

================

Because Thin Ethernet network interface cards are not impedance

matched, some of the signal coming off the main cable reflects off the

network interface card and back on to the main cable.

If the distance is short (less than one to two inches), the echo lands

right on top of the main signal and no distortion occurs.

If the distance is long (more than one to two inches), the time taken

for the signal to travel down the drop cable, bounce off the card, and

come back, is significant and can make the echo land on top of the

next pulse, which can result in scrambled signals.

Additional reference words: 3.10 wfwg


WFWG Network Adapter Card & Cable Replacement Instructions

Article ID: Q93037

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

----------------------------------------------------------------------

SUMMARY

=======

This article contains the instructions included with the Microsoft

Windows for Workgroups Network Card and Cable Replacement package.

MORE INFORMATION

================

Microsoft Windows for Workgroups Network Card and Cable Replacement

Instructions

-------------------------------------------------------------------

We appreciate your investment in the Microsoft Windows for Workgroups

product. We're sorry that you've experienced problems with the

networking hardware that shipped with the Windows for Workgroups

Starter Kit/User Kit. To get you up and running as soon as possible,

we have enclosed complete replacement hardware in this package.

Please follow these instructions to replace your current hardware:

1. Carefully remove your current Windows for Workgroups hardware (this

   includes the network card[s], cable, T-connectors, and terminators)

   from your PC(s).

2. Carefully remove the new hardware contained in this package.

3. Install the new hardware. Follow the directions in the installation

   video (if you received one with your Windows for Workgroups software),

   or follow the directions in the "Windows for Workgroups Getting

   Started" manual.

4. Put the old network card(s) in the anti-static bag(s) and place it,

   along with old cable, T-connectors, and terminators, in this reusable

   box.

5. Address the box using the enclosed pre-paid, pre-addressed Federal

   Express shipping label (found with the packing slip).

6. For Federal Express pick-up, please call (800) 238-5355.

7. Reinstall the Windows for Workgroups software.

To help us identify the problems you experienced, we need you to send

the package back to us as soon as possible. Thank you for your help--

and sorry for the inconvenience!

Additional reference words: 3.10 3.11 wfwg win31 nic Intel EE16 Ether

Express


Startup and Exit Sounds May Not Work with WFWG

Article ID: Q93038

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

----------------------------------------------------------------------

SYMPTOMS

========

If the sound files for Windows for Workgroups are on a network drive,

the Startup or Exit system sounds, which are assigned in the Sound

section of Control Panel, may not play when you start or exit Windows

for Workgroups.

CAUSE

=====

The network redirector may not be active during the startup or exit of

Windows for Workgroups.

WORKAROUND

==========

Startup and Exit sounds should be placed on a local drive. Any other

system sound files can be placed on a network share.

MORE INFORMATION

================

On an installation created by SETUP /N on a Microsoft LAN Manager or

Windows for Workgroups server, the Startup and Exit sounds do work

correctly; this is because the real mode redirector is active.

On an installation created by SETUP /N on a Novell server, the sounds

work only if they are located on the Novell server. This is because

MSIPX, not the real mode redirector, is loaded.

Additional reference words: 3.10 wfwg win31 3.11


Token Ring Cards and Local Addressing with WFWG

Article ID: Q93039

------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

------------------------------------------------------------------

SUMMARY

=======

Some token ring network interface cards (NICs) can use a "local

addressing" feature with Windows for Workgroups. This feature allows

the network card's internal network address to be bypassed and defined

manually.

MORE INFORMATION

================

The local address is defined by placing the following line in the

network card section of the PROTOCOL.INI file:

   [MS$IBMTR1]            (Using the IBM Token Ring card)

   Netaddress="<value>"   (The quotation marks are required)

The value for the Netaddress= setting must be stated as a series of 12

hexadecimal digits within quotation marks, with no spaces separating

the digits. There is no default for the Netaddress= setting.

The address must be within the range 400000000000 through

40007FFFFFFF; however, for strict IBM compatibility, use only decimal

digits (0-9), as in "400001020304."

If the Netaddress= value is incorrectly entered (without quotation

marks, for example), one of the following error messages may be

displayed during startup:

While loading PROTMAN.DOS:

   PRO0006E: Integer overflow in PROTOCOL.INI parameter

   Unable to open Protocol Manager

While loading the netcard driver:

   MAC0001: Initialization Failure

   Press any key to continue...

While executing NET USE in AUTOEXEC.BAT:

   Error 3653: The protocol manager could not be found.

To correct these errors, verify that there are 12 digits, that they

are within quotation marks, and that there are no spaces between

entries.

You may also experience the following problems if there are duplicate

computers on the network using the same Netaddress= value:

 - Computers cannot connect to the network. (This problem occurs when

   the first computer to enter the ring causes another machine that is

   attempting to use the same Netaddress= value to fail.)

-or-

 - Losing the connection to the ring when starting Windows for

   Workgroups or starting the real mode redirector.

-or-

 - Inability to browse or connect to other computers within Windows for

   Workgroups.

No error messages are displayed if you start a machine that is

attempting to use a network address that is already in use, but

network access problems, as described above, do occur.

To troubleshoot a possible network address conflict, remove the

Netaddress= line in the PROTOCOL.INI by placing a semicolon at the

beginning of that line. If problems persist, there is may be some

other conflict, such as IRQ, I/O address, or device driver.

The following token ring network cards support local addressing with

Windows for Workgroups:

   Netcard                   Driver

   --------------------------------------

   ProNET-4/16 (P1892)       NDIS89XR.DOS

   3Com TokenLink            TLNK.DOS

   IBM Token-Ring Adpater    IBMTOK.DOS

   IBM Token-Ring II         IBMTOK.DOS

   IBM Token-Ring A          IBMTOK.DOS

   IBM Token-Ring 16/4       IBMTOK.DOS

   IBM Token-Ring 16/4 A     IBMTOK.DOS

Additional reference words: 1.0 1.00 3.10 3.11 wfwg win31 LAN Manager

LANman


WFWG: Network Button Does Not Appear in Open Dialog Box

Article ID: Q93164

---------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

---------------------------------------------------------------

SUMMARY

=======

With Windows for Workgroups, a button labeled "Network" appears in the Open

common dialog box. If the Network button doesn't appear in the Open dialog

box of specific applications, one of the following conditions exists:

 - The application does not support common dialog boxes.

 - The application does not have enough stack space left.

 - The common dialog template of the application doesn't have enough room.

 - There is a control ID conflict. (The ID is psh14.)

MORE INFORMATION

================

The Application Does Not Support Common Dialog Boxes

----------------------------------------------------

An application must be written to use the Common Dialog Boxes dynamic link

library provided with Windows for Workgroups (COMMDLG.DLL). If it was not,

the Network button does not appear in the Dialog box.

To determine if an application uses common dialog boxes, rename CMOMDLG.DLL

to COMMDLG.OLD, and then run the application. If the application uses

COMMDLG.DLL, you receive the following error message:

   Cannot find COMMDLG.DLL

The Application Does Not Have Enough Stack Space Left

-----------------------------------------------------

An application must have approximately 7 kilobytes (K) of stack space to

display the Network button in the Open dialog box. The amount of free stack

space is application dependent and cannot be altered by Windows for

Workgroups.

The Applications Common Dialog Template Doesn't Have Enough Room

----------------------------------------------------------------

Applications use a template when a common dialog box is called. After the

application has added its buttons, Windows adds buttons to space that is

left. If there is not enough room below the OK button, the Network button

is not added. Use of the common dialog template is application dependent

and cannot be altered by Windows for Workgroups.

There is a Control ID Conflict. (The ID is psh14.)

--------------------------------------------------

If there is a control ID conflict, the Network button does not appear in

the Open dialog box. For more information, please contact the vendor of the

application with which you are having problems.

Additional reference words: wfwg 3.10 3.11


Intel EtherExpress Card Conflicts with Scanning Hardware

Article ID: Q93165

---------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

---------------------------------------------------------------

SYMPTOMS

========

You install Windows for Workgroups, and your graphics scanning device

doesn't work

CAUSE

=====

The base I/O port address for many graphics scanning devices is 300.

Because this is also the default I/O port address for the Intel

EtherExpress card that is included with the Windows for Workgroups

Starter Kit, many graphics scanning devices don't work with Windows

for Workgroups until you change the port address on one of the cards.

WORKAROUND

==========

To work around this problem, change the base I/O port address on either

the graphics scanning device or the EtherExpress card.

To change the port for the EtherExpress card:

1. Run Control Panel and choose the Network icon.

2. Choose the Adapters button.

3. Select the EtherExpress card from the Network Adapters In Use list.

4. Choose the Setup button.

5. Change the Base I/O Port address to an address that does not

   conflict with your graphics scanning device (or any other hardware

   devices) in your system.

Additional reference words: 3.1 3.10 3.11 card nic hardware software

package text scan scanner wfwg


Using Custom IRQ and I/O Settings with Windows for Workgroups

Article ID: Q93169

---------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

---------------------------------------------------------------

SUMMARY

=======

The Microsoft Windows for Workgroups 3.1 Setup program detects certain

networks and allows for specific IRQ and I/O address settings for

individual network interface cards (NICs). Setup does not accept any

settings other than those it provides. This behavior can be a problem

if you are using a network card that allows an IRQ or I/O address

setting other than those provided by Windows for Workgroups. This

article includes procedures that may help you work around such

problems.

MORE INFORMATION

================

To change the IRQ or I/O address for a single installation:

1. During Windows for Workgroups Setup, install the appropriate

   network card and select any of the available settings.

2. Open the PROTOCOL.INI file in an ASCII text editor, such as

   Microsoft Windows Notepad.

3. Locate the network card section for your card. Section headings

   appear as follows:

      [netcardname]

   where "netcardname" is a unique identifier for your network card. (For

   example, the heading for an Intel EtherExpress 16 is [ms$ee16], and

   the heading for an NE 1000 compatible card is [ms$ne1clone].) If you

   are not sure what the identifier for your card is, check the [netcard]

   section of the NETWORK.INF file. This section contains a list of

   supported network cards and their corresponding identifiers.

4. Once you locate the [netcard] section, find two lines similar to the

   following:

      IRQ=

      IOADDRESS=

   Note: The exact wording of these lines varies from card to card.

5. Change these lines to reflect the settings that your network card is

   actually using. The IRQ value must be a valid number between 0 and 15.

   The IOADDRESS value must be a valid hexadecimal I/O address or must

   take the form 0xNNN, where "NNN" is the address, (for example,

   IOADDRESS=0x300).

6. Save these changes, then reboot your computer.

   Note: If you regenerate the PROTOCOL.INI file by reinstalling Windows

   or by removing and then reinstalling the network card in the Network

   dialog box of Control Panel, these changes are lost.

To change the IRQ or I/O address for multiple installations:

Note: The changes below affect all subsequent installations of Windows

for Workgroups that have the specified network card. Be sure to make a

backup of the NETWORK.INF file before you make any changes to it.

1. Open the NETWORK.INF file in a ASCII text editor, such as Microsoft

   Windows Notepad.

2. Locate the [netcard_protocol] section for your network card. These

   sections generally have the following form:

      [netcardname_nif] or [netcardname_xif]

   where "netcardname" is a unique identifier for your network card.

3. Once you locate the [netcard_protocol] section for your card, find

   the following two lines:

      io=<description,type,range,default,flags>

      irq=<description,type,range,default,flags>

   where "type" is the parameter type, "range" is the range of values for

   the parameter, and "default" is the default value or the parameter.

   Note: Some fields may be missing in the actual statements. The

   following is an example:

      irq=IRQ,,text,"3,4,5,9",3

      io=IOADDRESS,,hex,"0x280,0x3f0,0x10","0x300"

   The following table describes the common type, range, and default

   values:

      Type    Range                Default   Definition

      -------------------------------------------------------------------

      Static  Default              N/A       The value cannot be changed

      Text    "Value, value,..."   Yes       List of text values

      Int     "First, last, step"  Yes       Integer range

      Hex     "First, last, step"  Yes       Integer range in hexadecimal

4. The values for the I/O address or the IRQ can then be modified by

   changing the values inside a text list or the first, last, or step

   values of an integer or hexadecimal range. For example

      irq=IRQ,,text,"3,4,5,9",3 can be changed to include irq 7.

      irq=IRQ,,text,"3,4,5,7,9",3

   io=IOADDRESS,,hex,"0x280,0x3f0,0x10","0x300" can be changed to include

   I/O address 200h by lowering the first value as follows:

      io=IOADDRESS,,hex,"0x200,0x3f0,0x10","0x300"

   Note: The default value following the range MUST be a value in the

   range.

5. Save the changes to the NETWORK.INF file. The Setup program then

   displays the setting that you added as a selection in the appropriate

   box.

For more information, refer to Chapters 5 and 6 of the "Windows for

Workgroups Resource Kit" manual.

Additional reference words: 3.10 3.11 wfwg


PostScript EPS Files Are Device Independent

Article ID: Q93206

---------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows operating system version 3.1

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

---------------------------------------------------------------

SUMMARY

=======

When you print from Windows to an encapsulated PostScript (EPS) file,

Windows creates a device independent file. EPS files can be imported

into other PostScript files, and aren't designed to be copied to a

printer. For example, you can create a graphic, print it to an EPS

file and import that into another document in a device-independent

format.

Most EPS files (including those generated by Windows) print when you

copy them to a printer. However, because these are in device

independent format, device features that may need to be selected

differently by the printer driver for different devices (paper size,

paper bin, resolution, and so on) won't necessarily work when you copy

an EPS file to a printer.

MORE INFORMATION

================

If you want to print to a file that can be copied to a printer:

1. Run Control Panel.

2. Select or install the printer driver for the specific printer

   to which you plan to copy the file.

3. Choose the Connect button.

4. Select FILE: from the Ports list box and choose the OK button.

5. Choose the Setup button.

6. Choose the Options button.

7. Select the Printer option.

8. Choose the OK button twice.

When you print, Windows prompts you for the filename. Print to a

unique file (for example OUTPUT.PRN). You can now copy this file to

the printer and your output should be correct.

Additional reference words: 3.1 3.10 3.11 win31 wfwg


WFWG Err Msg: Error 2184: The Service Has Not Been Started

Article ID: Q93248

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.1

--------------------------------------------------------------------

SYMPTOMS

========

The NET STOP command is designed to disable the Windows for Workgroups

real mode redirector, which is started by typing the following at the

MS-DOS command prompt:

   net start workstation/full/basic

If you use NET STOP from the Windows for Workgroups MS-DOS command

prompt and have not previously loaded the real mode redirector, the

following error message is displayed:

   Error 2184: The service has not been started.

NET STOP logs you off of the network but does not disable the protect

mode redirector (VREDIR.386). All network options remain available,

but you are prompted to log on if you attempt to use them.

WORKAROUND

==========

If you want to disable the protected mode redirector, exit Windows for

Workgroups.

Microsoft has confirmed this to be a problem in Windows for Workgroups

version 3.1.

Additional reference words: 3.10


WFWG: Cannot Connect to Local Postoffice

Article ID: Q93260

----------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

----------------------------------------------------------------

SYMPTOMS

========

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.

CAUSE

=====

WFWG 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 (<machinename>\WGPO) results in

the path not being found, as does typing in the local path (F:\WGPO).

WORKAROUND

==========

Use one of the following workaround options to edit or reconstruct the

user's MSMAIL.INI file, allowing the user to logon to the postoffice

on his/her local machine.

Option 1

--------

1. Copy the MSMAIL.INI file from a machine that is already connected

   to the WGPO.

2. Edit the MSMAIL.INI file for Machine1:

   a. Change the "serverpath=" statement to reflect the local path.

   b. Change the "login=" statement to reflect the Machine1 mailbox

      (as setup 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.

Option 2

--------

To create the Machine1 MSMAIL.INI file from scratch:

1. Create a file in a text editor (such as note pad).

2. Type the following:

[Microsoft Mail]

WG=1

LocalMMF=1

NoServerOptions=1

DemosEnabled=0

NetBios=1

;the following line should reflect the local path to the WGPO

;subdirectory (e.g. ServerPath=F:\WGPO)

ServerPath=<pathname>

;the following line should reflect the mailbox for the user of Machine1

;(as setup by Mail Administrator)

Login=<mailboxname>

OfflineMessages=C:\WINDOWS\MSMAIL.MMF

MAPIHELP=C:\WINDOWS\MSMAIL.HLP

Window=96 96 638 406 1 1 1 0

[Custom Commands]

IMEX=3.0;File;;10

;Please note that the following set of lines should be typed as two

;lines -- one beginning EXF= and one beginning IMF=

EXF=3.0;File;&Export Folder...;11;IMPEXP.DLL;0;;Exports folders to a

backup file;MSMAIL.HLP;2860

IMF=3.0;File;&Import Folder...;12;IMPEXP.DLL;1;;Imports folders from a

backup file;MSMAIL.HLP;2861

[Custom Messages]

;Please note that the following set of lines should be typed as a

;total of 5 lines, each beginning IPM.Microsoft Schedule.

IPM.Microsoft

Schedule.MtgReq=3.0;;;;SchedMsg.DLL;;1111100000000000;;;;

IPM.Microsoft

Schedule.MtgRespP=3.0;;;;SchedMsg.DLL;;1100100000000000;;;;

IPM.Microsoft

Schedule.MtgRespN=3.0;;;;SchedMsg.DLL;;1100100000000000;;;;

IPM.Microsoft

Schedule.MtgRespA=3.0;;;;SchedMsg.DLL;;1100100000000000;;;;

IPM.Microsoft

Schedule.MtgCncl=3.0;;;;SchedMsg.DLL;;1100100000000000;;;;

3. Save the file as MSMAIL.INI in the WINDOWS subdirectory of the

   postoffice machine.

NOTE: For the MSMAIL.INI file to work correctly, this text should be

typed exactly as it appears above.

Additional reference words: 3.10 3.11 WFW wfwg schedule


Windows Components Not Installed by Default SETUP.SHH File

Article ID: Q93313

--------------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------------

SUMMARY

=======

If you install Windows for Workgroups using the default SETUP.SHH file for

automated setup, the following components are not installed:

 - Calculator

 - Calculator Help

 - Cardfile

 - Cardfile Help

 - Character Map

 - Character Map Help

 - Chat

 - Chat Help

 - ClipBook Viewer Help

 - Clock

 - Dr. Watson

 - Expand

 - File Manager Help

 - Glossary Help

 - Help

 - Help Help

 - Mail

 - Mail Help

 - Media Player

 - Media Player Help

 - Net Watcher

 - Net Watcher Help

 - Notepad

 - Notepad Help

 - Object Packager

 - Object Packager Help

 - Paintbrush

 - Paintbrush Help

 - PIF Editor Help

 - Print Manager Help

 - Recorder

 - Recorder Help

 - Registration Editor Advanced Help

 - Registration Editor Help

 - Schedule Plus

 - Schedule Plus Help

 - Sound Recorder

 - Sound Recorder Help

 - Terminal

 - Terminal Help

 - Windows Tutorial

 - WinMeter

 - README files

 - Game files

 - Screen Saver files

 - Bitmap files

These components are referred to in the [dontinstall] section of SETUP.SHH.

To install them during Setup, you must remove or comment the appropriate

items. For example, to install all of the above components, modify the

[dontinstall] section, using semicolons with each item, to look like this:

   [dontinstall]

   ;accessories

   ;readmes

   ;games

   ;screensavers

   ;bitmaps

MORE INFORMATION

================

In Microsoft Windows operating system 3.1, the [dontinstall] section

is used to specify components to be installed. If an item appears in

this section, the appropriate components were installed. In Windows

for Workgroups, however, the opposite is true -- any items appearing

in this section (all by default) are not installed.

If you have already completed installation, you can add any or all of

these components to your Windows for Workgroups installation by using

the Add/Remove Windows Components option on the Options menu of

Windows for Workgroups Setup.

Additional reference words: 3.10 wfwg 3.11


Xircom Network Simplicity Adapters Not Supported with WFWG

Article ID: Q93476

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

----------------------------------------------------------------------

SYMPTOMS

========

If you use the Xircom Network Simplicity adapter with either of the

Pocket Ethernet Adapter drivers included with Windows for Workgroups,

the following error message is displayed when your system boots up:

   Pocket Ethernet Adapter Address Eeprom Unreadable.

   Press any key to continue...

CAUSE

=====

The Xircom Network Simplicity series of network adapter cards are not

supported with Windows for Workgroups. They are very similar to

Xircom's Pocket Ethernet Adapters; however, they are not Network

Driver Interface Specification (NDIS) certified, and do not work with

either of the Pocket Ethernet Adapter drivers included with Windows

for Workgroups.

MORE INFORMATION

================

The Network Simplicity adapters were developed for Novell NetWare Lite

and are proprietary to Novell NetWare Lite.

The Network Simplicity adapters can be identified by a "Network

Simplicity" label on the case and "NS" on the end of the serial

number.

For additional information, contact Xircom technical support.

The Novell and Xircom products included here are manufactured by

vendors independent of Microsoft; we make no warranty, implied or

otherwise, regarding these products' performance or reliability.

Additional reference words: 1.0 1.00 3.1 3.10 3.11 LAN Manager LANman

light err msg errmsg


WFWG May Hang Loading in Enhanced Mode Without a Terminator

Article ID: Q93478

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

----------------------------------------------------------------------

SYMPTOMS

========

 - Windows for Workgroups may stop responding (hang) at the logo

   screen when starting in enhanced mode.

   -or-

 - Windows for Workgroups may hang after the logo screen when started

   in standard mode if the real mode redirector has been started.

   -or-

 - The computer may stop responding in MS-DOS if a NET USE or NET VIEW

   command is used.

CAUSE

=====

There is no terminator connected to the network interface card (NIC).

The NIC requires a terminator even if the card isn't on the network.

The Intel EtherExpress 16, which is shipped with some versions of

Windows for Workgroups, requires a terminator if it is configured with

Thin net cable.

WORKAROUND

==========

To work around this problem, you can either attach a terminator to the

coaxial jack on the network card. or you can use the procedure below.

1. Start Windows for Workgroups in standard mode by typing:

      win/s

2. From Control Panel, choose the Network icon.

3. Choose the Adapters button and select the Intel EtherExpress 16.

4. Choose the Advanced button and select Transceiver Type.

5. In the Transceiver Type field, select Thick Net (AUI/DIX).

6. Choose OK, then choose Close until you are back in Control Panel.

MORE INFORMATION

================

The Windows for Workgroups add-on user kit does not ship with a

terminator. Normally, the add-on user kit is installed on an existing,

functional Windows for Workgroups network. Because a functional

Windows for Workgroups network must be already terminated on both

ends, it is not necessary to provide an additional terminator to add a

new user.

Additional reference words: 3.10 3.11 wfwg win31 ether express ee16

winnet lock up lockup lock-up crash freeze hang


Unable to Connect to a Server Using Thomas Conrad TC6242 Card

Article ID: Q93583

---------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

---------------------------------------------------------------

SYMPTOMS

========

If you use a Thomas Conrad TC6242 network adapter card with Windows

for Workgroups, you must set the card for enhanced mode. If the card

is set for compatible mode, you cannot connect to resources from

Microsoft MS-DOS. If you try to connect to a server from Windows, you

receive the following error message:

   Unable to read from drive <x>

where "x" is the drive letter of the server to which you are trying to

connect.

WORKAROUND

==========

To correct this problem, set the jumper on the TC6242 card to enhanced

mode by setting the eighth pin on switch block sw1 to the down

position (On).

MORE INFORMATION

================

Enhanced Mode

-------------

Enhanced mode should be used when you want to optimize communication

performance and minimize memory address conflicts with other hardware.

This mode is also designed for the Thomas Conrad accelerated drivers,

which feature expanded memory addressing options and faster data

transfer. In enhanced mode, the adapter's base I/O address is memory

mapped. Enhanced mode is the default setting for this card.

Compatible Mode

---------------

Compatible mode should be used when you are using third-party drivers.

This mode operates with any Novell RX-Net-compatible driver or the

Thomas Conrad GXL/ARC driver (a global, high performance network shell

driver for ArcNet adapters). In this mode, the adapter's I/O address

must be manually set on switch block sw3.

Additional reference words: 3.10 3.11 wfw wfwg


WFWG: Error Attempting to Move Local Schedule+ .CAL File

Article ID: Q93700

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

----------------------------------------------------------------------

SYMPTOMS

========

If you enter a space after your logon name when logging into the

Windows for Workgroups (WFWG) Schedule+ application, the following

error message occurs when WFWG attempts to move the local .CAL file

from within Schedule+:

   There is not enough memory to display this dialog box. Please close

   some windows and try again.

The error message can also occur when you choose Create Archive or

Export Appointments from the Schedule+ File menu.

WORKAROUND

==========

Edit the SCHDPLUS.INI file using the steps outlined below to resolve

the problem:

1. Open the SCHDPLUS.INI file using a text editor such as Notepad.

2. In the [Microsoft Schedule+] section of the file, the path and

   filename of the local .CAL file appears as follows

      LocalPath=D:\WFW\USER .CAL

   where USER is the user name used at logon.

3. Delete the space immediately following the user name. For example:

      LocalPath=D:\WFW\USER.CAL

4. Save the SCHDPLUS.INI file.

5. Close Notepad and restart Schedule+.

The local .CAL file can now be moved without errors.

Additional reference words: 3.10 3.11


WFWG Err Msg: Local Copy of Schedule+ Cannot Be Accessed

Article ID: Q93705

---------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

 - Microsoft Schedule+ for Windows, version 1.0

---------------------------------------------------------------

SYMPTOMS

========

The following error message may appear when you start Microsoft

Schedule+ for Windows or the Schedule+ component of Windows for

Workgroups:

   Local copy of Schedule+ cannot be accessed in the location

   specified in the SCHDPLUS.INI file.

CAUSE

=====

This error can be caused by a corrupt SCHDPLUS.INI file, an incorrect

entry in the SCHDPLUS.INI file, or a corrupt .CAL file.

WORKAROUND

==========

The following paragraphs list appropriate solutions for each problem:

 - The SCHDPLUS.INI file has an incorrect entry or is corrupt.

   If the incorrect entry is not easily detectable, rename

   SCHDPLUS.INI to SCHDPLUS.OLD and restart the program. Based on the

   presence of the .CAL file and "serverpath=" entry in MSMAIL.INI,

   the program regenerates the SCHDPLUS.INI file.

 - The .CAL file is corrupt:

   Rename the .CAL file and restart the program. Because a duplicate

   copy is kept on the Workgroup Post Office (WGPO), the .CAL file is

   automatically copied at startup. Be aware that any changes

   previously made to the .CAL file while working offline will not be

   reflected in the downloaded .CAL file.

Additional reference words: 3.10 3.11 sched+ scheduler schedule plus

wfwg


Installing WinLogin with Windows for Workgroups

Article ID: Q93780

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

 - Microsoft WinLogin version 1.0

--------------------------------------------------------------------

SUMMARY

=======

To install Microsoft WinLogin with Windows for Workgroups, you must

follow the procedures in this article for all computers that will be

running the WinLogin application.

NOTE: These procedures only work with a Windows for Workgroups network

or Microsoft LAN Manager network, as they can connect through the

MS-DOS level before starting Windows for Workgroups.

MORE INFORMATION

================

Make the following changes for each computer that will be running

Windows for Workgroups and WinLogin:

1. From your Windows for Workgroups Disk 3 (either 5.25-inch or

   3.5-inch disks), expand a copy of the MSNET.DR_ file and place this

   file in the WINDOWS\SYSTEM directory.

   Type the following command at the MS-DOS command prompt to expand

   the file:

      expand x:\MSNET.DR_ c:\windows\system\msnet.drv

   where x is the floppy drive that contains the MSNET.DR_ file.

2. In the [BOOT] section of the SYSTEM.INI file, change the following

   line:

      NETWORK.DRV=WFWNET.DRV

   to:

      NETWORK.DRV=MSNET.DRV

3. In the [386Enh] section of the SYSTEM.INI file, comment out the

   following line:

      NETWORK=VNETBIOS.386,VNETSUP.386,VREDIR.386,VSERVER.386,

      VBROWSE.386,VWC.386

   by placing a semicolon (;) as the first character, as follows:

      ;NETWORK=VNETBIOS.386,VNETSUP.386,VREDIR.386,VSERVER.386,

      VBROWSE.386,VWC.386

4. Add the following line to the [386Enh] section of the SYSTEM.INI

   file:

      NETWORK=*VNETBIOS,*DOSNET

5. (Optional) To keep the WinLogin application transparent to users,

   you may want to add the following as the last line in the

   AUTOEXEC.BAT file:

      net start enhanced

   This starts the MS-DOS redirector without any intervention from the

   user, and after the computer is started, the user needs to type a

   user name and password only. The user can then start Windows for

   Workgroups (along with the WinLogin application).

6. To install the WinLogin Client Software, you must first log in at

   the MS-DOS level and connect to the server\share locations where

   WinLogin is installed before you start Windows for Workgroups.

7. Start Windows for Workgroups. You will receive an error message

   stating that you do not have network connections because you are

   using the MSNET.DRV driver.

8. Start File Manager. You will not have Network options; however, you

   will see the network drives that you connected to before starting.

9. Install the Client software from either a disk drive or network

   drive.

Once the software is installed, you must do one of the following to

have all Windows for Workgroups functionality returned:

 - Edit the SYSTEM.INI file in the users directory and remove the

   remarks from steps 2, 3, and 4 above.

-or-

 - Using the INI Editor, add to the WinLogin database the lines in

   SYSTEM.INI that reflect Windows for Workgroups entries (steps 2, 3,

   and 4 above).

Once the changes have been made, you have full functionality of both

WinLogin and Windows for Workgroups. You can share resources as well

as connect to shared resources.

It is not necessary to create a persistent connection to the server

containing the WinLogin database because the WinLogin application can

connect and disconnect as necessary.

Additional reference words: 3.10 wfwg 1.0 win login winnet


WFWG May Hang if InDOSPolling=Yes with an Intel EtherExpress

Article ID: Q94302

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

---------------------------------------------------------------------

SYMPTOMS

========

If InDOSPolling=Yes is present in the SYSTEM.INI file and an Intel

EtherExpress 16 network interface card (NIC) is being used in the

machine, Windows for Workgroups may stop responding (hang) for several

minutes or may lock up when trying to access network drives from any

program.

CAUSE

=====

nDOSPolling prevents Windows for Workgroups from running other

applications when memory-resident software has the InDOS flag set.

WORKAROUND

==========

The only workaround for this problem is to remove the line from the

[386Enh] section of the SYSTEM.INI file. Use a text editor (such as

Notepad) to delete the line.

For more information on InDOSPolling, query on the following words in

the Microsoft Knowledge Base:

   indospolling and system.ini

Additional reference words: 3.10 win31 wfwg winnet freeze crash lockup lock

up


FastBack Plus Windows Changes VDMAD.386 to *VDMAD with WFWG

Article ID: Q94307

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

SYMPTOMS

========

When you install FastBack Plus for Windows, version 1.0, using Windows

for Workgroups, the following warning message appears:

   SYSTEM.INI Includes Non-Standard Drivers!

   Some other application (possibly a backup product from a

   different manufacturer) has modified your SYSTEM.INI file to use

   incompatible, non-standard VDMAD and/or VFD drivers. These drivers

   may cause failures in many applications, including FastBack

   Plus Windows.

   Install will first backup your SYSTEM.INI as SYSTEM.FBP, and then

   restore it to use the Microsoft standard drivers. This change is

   necessary for correct operation.

FastBack Plus Windows continues installation and changes the virtual DMA

device entry in the SYSTEM.INI file to device=*VDMAD.

CAUSE

=====

The warning message is the result of a change in the name of the

virtual DMA device driver in Windows for Workgroups. Windows versions

3.0 and 3.1 specify this device in the [386Enh] section of the

SYSTEM.INI file as follows:

    device=*VDMAD

With Windows for Workgroups, this entry is changed to:

   device=VDMAD.386

WORKAROUND

==========

To allow Windows for Workgroups to function properly, you need to

restore the default Windows for Workgroups entry. Use any text editor

(such as Notepad) and change the virtual DMA device entry in the

[386Enh] section of the SYSTEM.INI file to:

   device=VDMAD.386

STATUS

======

Fifth Generation Systems has confirmed that FastBack Plus Windows

operates properly with the default Windows for Workgroups setting for

the virtual DMA device driver. Future versions of FastBack Plus

Windows should recognize this change with Windows for Workgroups.

FastBack Plus Windows is manufactured by Fifth Generation Systems,

Inc., a vendor independent of Microsoft; we make no warranty, implied

or otherwise, regarding this product's performance or reliability.

Additional reference words: 3.10 3.11 wfwg win31 3rdparty fast back +


Unable to Share Printer when SUBST Is Used for TEMP Directory

Article ID: Q94309

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

----------------------------------------------------------------------

SYMPTOMS

========

The following error message appears if a Windows for Workgroups

server is attempting to share a printer in Print Manager and the TEMP

directory is set to a drive that was created using the MS-DOS SUBST

command:

   The specified drive letter or device is invalid. If you specified a

   drive, it may be past the value specified by the LASTDRIVE command

   in the CONFIG.SYS file.

CAUSE

=====

The SUBST command allows specifying a drive letter for a PATH, which

enables easier access to programs and data files. In Windows for

Workgroups, these virtual drives cannot be shared, and because the

TEMP directory is used during printing, TEMP also cannot be shared.

WORKAROUND

==========

To work around this problem, assign the TEMP variable to a valid (not

virtual) directory. For example, if Windows is installed on the local

drive C in the WINDOWS directory, add the following line in the

AUTOEXEC.BAT file:

   SET TEMP=C:\WINDOWS\TEMP  (or any other valid directory)

MORE INFORMATION

================

Steps to Reproduce Problem

--------------------------

1. Add the following lines to the AUTOEXEC.BAT file:

      SUBST X: C:\WINDOWS\TEMP

      SET TEMP=X:

2. Add the following command to the CONFIG.SYS file if it is not already

   present:

      LASTDRIVE=Z

3. Restart the computer and then start Windows for Workgroups.

4. From the Main Group, run Print Manager.

5. Select the printer to be shared.

6. From the Printer menu, choose Share Printer As.

7. Choose the OK button.

8. The above error message appears.

For more information on Windows for Workgroups and the SUBST command, query

on the following words in the Microsoft Knowledge Base:

   subst and wfwg

Additional reference words: 3.10 win31 wfwg


WFWG File Manager Shows Multiple WIN.INI Files

Article ID: Q94310

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

----------------------------------------------------------------------

SYMPTOMS

========

The Windows for Workgroups File Manager may show multiple WIN.INI files if

the WIN.INI file is renamed, moved, or deleted with File Manager. All the

files and directories previously listed correctly will be listed as WIN.INI

even if the screen is refreshed.

WARNING: Microsoft does not recommend or support modifying the WIN.INI file

in the above manner from any version of Windows File Manager.

Quit Windows completely before renaming, moving, or deleting the WIN.INI

file.

WORKAROUND

==========

To restore the listings, exit and restart File Manager.

STATUS

======

Microsoft does not recommend renaming, moving, or deleting core Windows

files (including WIN.INI and SYSTEM.INI) while Windows is running.

MORE INFORMATION

================

The only file that causes this behavior is the WIN.INI file. Renaming,

moving, or deleting other files does not affect File Manager's listing of

files and directories.

Steps to Reproduce Behavior

---------------------------

1. Load File Manager.

2. Open the Windows directory and select the WIN.INI file.

3. From the File menu, choose Rename.

4. Enter a different name for WIN.INI, such as WIN.BAK.

5. Choose the OK button.

All files and directories are now listed as WIN.INI.

Additional reference words: 3.10 win31 wfwg duplicate wow winfile


How To: Customizing the WFWG Mail and Schedule+ Chime Sound

Article ID: Q94312

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

SUMMARY

=======

The Mail and Schedule+ programs packaged with Windows for Workgroups

(WFWG) have the option to play a sound when mail is received or when

you have scheduled a reminder. The chime is the system default sound.

It is not possible to change the chime without changing the system

default sound unless the appropriate entry is added to the WIN.INI

file.

MORE INFORMATION

================

To customize the sound, proceed as follows:

1. Use a text editor (such as Notepad) to open the WIN.INI file.

2. To customize the Mail chime, add the following entry to the

   [Sounds] section of the WIN.INI file:

      MailBeep=<wavefilename>,MailBeep

   where <wavefilename> is the name of the wave (.WAV) file you

   wish to play.

3. To customize the Schedule+ Reminders sounds, add the following

   entry to the [Sounds] section of the WIN.INI file:

      SchdplusReminder=<wavefilename>,SchedulePlusReminders

   where <wavefilename> is the name of the wave (.WAV) file you

   wish to play.

4. Save your changes, then restart Windows for the changes to

   take effect.

You can replace the wave file name with any playable wave (.WAV) file

either by using the Control Panel Sound option or by editing the

WIN.INI file. To play wave files that aren't in the Windows directory,

add a valid path to the file.

The Mail chime is active by default. To change this setting:

1. Run Mail.

2. From the Mail menu, choose Options and clear the Sound Chime check

   box.

NOTE: The computer must be configured with either a sound card or the

PC speaker driver to use this feature.

Additional reference words: 3.10 win31 wfwg notify


SMC_ARC.DOS May Result in a POR Failure or Adapter Not Found

Article ID: Q94363

-----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

-----------------------------------------------------------------------

SYMPTOMS

========

The following error message may occur during startup if the SMC_ARC.DOS

driver is being used:

   SMC Arcnet Mac Driver 10/01/91 Version 2.05 PS110,PS210 Board in a PS/2

   System

   \dev\smc_arc Error:POR failure or Adapter not found

This error indicates that the system board is being detected as a PS/2

board even though it is an ISA or EISA board.

WORKAROUND

==========

To work around the problem, edit the MAC driver section (example:

[MS$SMC270])of the Windows for Workgroups PROTOCOL.INI file adding the

following line:

   Micro_Channel=0

Here is an example of how the section reads:

[MS$SMC270]

DriverName=SMC_ARC$

interrupt=2

iobase=0x2E0

memorybase=0xD000

MICRO_CHANNEL=0

WARNING: When editing the PROTOCOL.INI file manually, always remember

that modifications made with the Network settings in Control Panel may

result in the loss of any manual editing. Therefore, it may be

necessary to add this entry again after modifying settings through

Control Panel.

Additional reference words: 3.1 3.10 wfwg ps2 micro channel err msg boot

process bootup start up


NetDDE Passwords Must Be Uppercase when Using NDDEShareAdd

Article ID: Q94640

-----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

-----------------------------------------------------------------------

SUMMARY

=======

If you receive an invalid password error when accessing a shared ClipBook

page on another machine, the password may not have been entered from the

user interface provided in ClipBook. The standard user interface

automatically converts all entries to uppercase characters, and the

programmable interface NDDEShareAdd does not. If the password was not

entered in uppercase characters, the passwords, though identical in all

other respects, do not match.

MORE INFORMATION

================

All passwords must be in uppercase characters before calling NDDEShareAdd.

The application program interface (API) does not change the password

characters to uppercase automatically. The API encrypts the passwords in

lowercase characters. On the server, the password characters entered in the

password dialog box are automatically changed to uppercase. The encrypted

versions of both passwords are compared as binary, and if different strings

are encrypted, the comparison fails.

Tests that use a user interface to have the user enter the password always

work because that user interface changes the password characters to

uppercase before calling NDDEShareAdd.

NOTE: Only applications with mixed-case strings in their data or resources

exhibit this problem.

NDDEShareAdd is a NetDDE command. This only affects users that have created

their own NetDDE applications, are using a third-party NetDDE application,

or are accessing the NetDDE interface by using an applications DDE

interface.

Additional reference words: 3.10 ndde access denied wfwg


Using the HP 27247A Network Interface Card with WFWG

Article ID: Q94655

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

SUMMARY

=======

The HP 27247A Network Interface Card is supported for use with Windows for

Workgroups (WFWG). There are several revisions of this network card and the

configuration options available for the card depend on which revision of

the card is being used.

The Windows for Workgroups Network Adapters setup lists the available

interrupt request lines (IRQs) for the HP 27247A network interface card

(NIC) as IRQ 3, 4, 5, 7, 9, 10, and 11. This is incorrect; use of IRQ 9 is

not possible.

If IRQ 9 is selected, the following error message occurs when you start the

machine:

   HP LAN ADAPTER/16+ Illegal value in PROTOCOL.INI

   after parameter: Interrupt=

IRQ 9 is not a valid selection for the HP 27247A network card. To select a

different available IRQ:

1. Run Control Panel.

2. Choose the Network icon.

3. In the Network Setting dialog box, choose the Adapters button. The

   Network Adapters dialog appears.

4. Choose the Setup button.

5. Change the Interrupt (IRQ) setting to something other than 9.

6. Choose the OK button to save your changes.

7. Exit Windows and run the Setup utility for the card provided by HP and

   change the IRQ setting to the same value you used in step 5.

MORE INFORMATION

================

Earlier versions of the HP 27247A network card may not work on IRQ 10 or

11. The 60001 series HP27247A cards cannot be used with IRQs 10 or 11,

while the 60002 (and later) series can be used with these IRQs.

If you are trying to use an IRQ that the card does not support, such

as IRQ 10 or 11 on the 60001 series, or an IRQ that is already in use,

the following error message may occur when you start your system:

   Error 5733: The protocol manager has reported an incomplete binding.

To prevent this error message from occurring, change the IRQ for the card

to a valid, unused IRQ. If you have an earlier 60001 series card, try using

IRQ 3, 4, 5, or 7.

Hewlett-Packard (HP) manufactured several revisions of the 27247A network

card. The version of the network card can be identified by the number

stamped on the network card's bracket (which should be visible from outside

the computer case) or by a label on the network card that indicates either

60001 or 60002 (or later).

60001 Series

------------

The 60001 series can be configured for Windows for Workgroups on IRQ 3, 4,

5, and 7 (if no other hardware device is using the selected interrupt).

60002 Series (and Later)

------------------------

The 60002 series and later can be configured for Windows for Workgroups on

IRQ 3, 4, 5, 7, 10, and 11 (if no other hardware device is using the

selected interrupt).

Additional reference words: 3.1 3.10 win31 wfwg LAN Manager errmsg


LMLogon=YES/NO is Not Recognized by Control Panel

Article ID: Q94756

-----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

-----------------------------------------------------------------------

SUMMARY

=======

The LMLogon= setting in the [network] section of the SYSTEM.INI file

determines functionality in Windows for Workgroups and Workgroup

Connections with a LAN Manager Domain.

Workgroup Connections requires the LMLogon=YES switch for

functionality. This is different from the way Control Panel in Windows

for Workgroups adds this switch. Any modifications made through the

Control Panel Network interface within Windows for Workgroups set the

LMLogon value to Zero (0) or one (1).

There is a problem when this setting is equal to "YES" (altered by

Workgroup Connections). The LAN Manager Settings dialog box in the

Windows for Workgroups Control Panel, Network, Networks Options, does

not show Log On To LAN Manager Domain as selected. In other words, the

check box appears to not be selected. However, Windows for Workgroups

behaves as if the Log On To LAN Manager Domain is selected.

MORE INFORMATION

================

The LAN Manager Settings dialog box in Control Panel, Network,

Networks Options, Settings does not display a check in the box next to

Log On To LAN Manager Domain if LMLogon=YES is specified in the

[network] section of the SYSTEM.INI file. If this box is selected in

Control Panel, the SYSTEM.INI setting are changed to LMLogon=1 and LAN

Manager validation is enabled.

It is possible to be logged on and validated by a LAN Manager server

that is password protected and never be prompted for a password. This

can  happen if you are using LAN Manager validation and either

LMLogon=1 or LMLogon=YES. However if you are using LMLogon=YES,

Control Panel never indicates that LAN Manager has been loaded. This

can make it seem as if Windows for Workgroups is allowing unsecured

access to a secure server. In actuality, you have been properly

validated and the password is part of the password cache.

It is also possible to never type in a password, not even a Windows

for Workgroups password, and have access to a LAN Manager server that

is password protected. In this situation, the Windows for Workgroups

password was originally entered as null (enter key), then password

caching was selected, and at some point the LAN Manager password was

typed in and recorded as part of the cache. With validation turned on

and LMLogon=1 or LMLogon=YES, you can gain access to the server

without typing any password. As above, you would receive no indication

that LAN Manager had been loaded if LMLogon=YES.

NOTE: When null is entered as the Windows for Workgroups password, the

prompt to logon to Windows for Workgroups is bypassed.

For more information on Workgroup Connections settings, query on the

following words in the Microsoft Knowledge Base:

   Workgroup and Connections and LMLogon

Additional reference words: 3.10 WFWG WC Logon


WFWG: Schedule+ May Not Print Entire Appointment Field

Article ID: Q94767

-----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

 - Microsoft Schedule+ for Windows, version 1.0

-----------------------------------------------------------------------

SYMPTOMS

========

When you print with version 1.0 of Microsoft Schedule+ or with the

Schedule+ accessory included with Windows for Workgroups, the text in

the appointment fields may be truncated. There is no method to

customize the printout so that all information is displayed.

WORKAROUND

==========

The only way to work around this limitation is to export the data to a

text file and then import it to another application, such as Notepad

or another word processor, to be printed.

Schedule+ prints approximately 29 characters of the appointment field when

printing the Pocket size page, 96 characters when printing the Junior size,

and 116 characters when printing the Standard size. Schedule+ indicates

that there is more information by adding ellipsis (...) to the end of the

line.

STATUS

======

Microsoft has confirmed this to be a limitation of the Windows for

Workgroups Schedule+ accessory included with 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.

Additional reference words: 3.10 3.11 win31 wfwg plus schedplus 1.0


SMC Microchannel Adapter Works with SMC EtherCard Driver

Article ID: Q94889

-----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

-----------------------------------------------------------------------

The following article contains information on the use of 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

========

When installing the "SMC EtherCard Plus Elite /A" Microchannel card in

Windows for Workgroups, the card may not be detected correctly because it

is not directly supported.

WORKAROUND

==========

Standard Micro Systems (SMC) technical support has confirmed that when

prompted for the card type in Windows for Workgroups Setup, you should

select:

   "SMC (WD) ETHERCARD PLUS /A (MCA) (WD 8003E/A OR 8003ET/A)"

For additional information, contact SMC technical support.

The SMC and EtherCard products included here are manufactured by vendors

independent of Microsoft; we make no warranty, implied or otherwise,

regarding these products' performance or reliability.

Additional reference words: 3.10 3rdparty wfwg


WFWG Err Msg: "Failure: Hardware Not Found..." with Intel EE16

Article ID: Q94896

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

----------------------------------------------------------------------

SYMPTOMS

========

If an Intel EtherExpress 16 is installed on a machine and there is a

hardware conflict, such as an I/O Port address or an interrupt request

line (IRQ) being duplicated on two devices, the following error

message may occur during startup:

   Failure: EtherExpress 16 Hardware Not Found, Driver not loaded.

   Failure: NDIS environment invalid, Driver not loaded.

WORKAROUND

==========

Because the Intel EtherExpress 16 is a software-configured network card,

the only workaround to this error message is to put the card into another

machine and use the following steps to reconfigure it.

NOTE: This message may occur if the network card isn't seated properly

in the machine. Check to be sure that this isn't the problem before

reconfiguring the card as discussed below.

 1. On the first machine, load Windows for Workgroups.

 2. Run Control Panel.

 3. In the Control Panel window, choose the Network icon.

 4. Choose the Adapters option to remove the driver for the Intel

    EtherExpress 16 network card.

 5. When prompted to Restart Computer or Continue, choose Continue, then

    exit Windows and turn off the machine.

 6. Remove the Intel card from the first machine, turn off a second machine

    which doesn't have a hardware conflict, remove any network cards from

    the second machine, and place the Intel card into the second machine.

 7. Turn on the second machine and load Windows for Workgroups.

 8. Run Control Panel.

 9. In the Control Panel window, choose the Network icon, and choose the

    Adapters option to remove any other network card drivers and install

    the driver for the Intel EtherExpress 16.

10. Change either the I/O Port address or the IRQ to an unused value on the

    first machine.

11. When prompted to Restart Computer or Continue, choose Restart Computer

    and then let the machine restart. Once it has restarted, turn the

    second machine off and remove the Intel card.

12. Place the card back into the first machine, turn it on, and load

    Windows for Workgroups.

13. Run Control Panel.

14. In the Control Panel window, choose the Network icon and choose the

    Adapters option to add the driver for the Intel EtherExpress 16. Use

    Setup to configure it for the new settings, which were set up on the

    second machine.

15. When prompted to Restart Computer or Continue, choose Restart

    Computer and then let the machine restart. The error message should

    no longer occur and Windows for Workgroups should operate normally.

16. If the error message still occurs, there may still be a hardware

    conflict and the above steps should be repeated until it is resolved.

The Intel EtherExpress 16 network interface card is set up exclusively

with software, either with Windows for Workgroups or Intel's Softset

utility. If there is a hardware conflict, the options changed by the

Setup software are never written to the card because the software

can't communicate with it due to the I/O Port address or IRQ conflict.

Because there is no other way to adjust the hardware settings on the

Intel EtherExpress 16, it has to be configured in another machine and

then moved back to the original machine.

Additional reference words: 3.10 win31 wfwg winnet Ether Express boot

bootup software configured


WFWG: Recovering Windows 3.1 After Installation With DR-DOS

Article ID: Q94899

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

----------------------------------------------------------------------

The following article contains information on the use of 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.

Microsoft has tested Windows for Workgroups with versions 3.3 and

later of Microsoft MS-DOS and PC-DOS. Microsoft does not recommend or

support running Windows or Windows for Workgroups with Digital

Research DOS (DR-DOS).

IMPORTANT: Read these instructions before proceeding. 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 on a computer running DR-DOS

version 6.0, the system may stop responding (hang) while loading the

protocol manager, PROTMAN.DOS. If the problem occurs and Windows for

Workgroups was installed over Windows 3.1, use the following

procedures to return to Windows 3.1.

MORE INFORMATION

================

NOTE: This procedure can be used ONLY if the Setup program for Windows for

Workgroups was run one time. If the Setup program was run more than once,

it is not possible to restore the original Windows configuration files and

therefore Windows 3.1 must be reinstalled to an empty subdirectory.

Additionally, any third-party software that replaces Windows virtual device

drivers (VxDs) may need to be reinstalled after reinstalling Windows 3.1.

1. Start up the machine with DR-DOS 6.0 from the DR-DOS startup disk. DR-

   DOS immediately runs a batch file. Press CTRL+C (or CTRL+BREAK) to stop

   the batch file. The A> prompt appears.

2. Edit the CONFIG.SYS and AUTOEXEC.BAT files to remove the Windows for

   Workgroups network device drivers. These drivers are PROTMAN.DOS,

   WORKGRP.SYS, and the network interface card driver (media access

   control [MAC] driver). If NetWare connectivity has been added, also

   remove the referenced lines.

    Below is an example of lines to remove:

       CONFIG.SYS

       ----------

       DEVICE=C:\WINDOWS\PROTMAN.DOS /I:C:\WINDOWS

       DEVICE=C:\WINDOWS\WORKGRP.SYS

       DEVICE=C:\WINDOWS\EXP16.DOS   ;or other specific MAC driver

       DEVICE=C:\WINDOWS\MSIPX.SYS   ;if NetWare Connectivity added

       AUTOEXEC.BAT

       ------------

       C:\WINDOWS\NET START

       C:\WINDOWS\MSIPX    ;if NetWare Connectivity added

       C:\WINDOWS\NETX     ;if NetWare Connectivity added

3. Copy the files WININI.W31 and SYSINI.W31 to a floppy disk. These files

   should be located in the WINDOWS directory.

4. Run the Windows version 3.1 Setup program. Choose the Custom Setup

   button. A blue screen will appear 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 to upgrade. When the

   System Information screen appears, change the line

       Network = Windows for Workgroups (version 3.1)

   to:

       Network = No Network Installed (or the specific network in use)

   The Windows 3.1 Setup program detects some newer drivers (for example,

   COMM.DRV) and prompts you to replace them with the ones from Windows

   3.1. In the following example, Setup detects conflicts between the

   version of COMM.DRV currently on your system and the version that Setup

   is attempting to copy. You can choose to use the currently installed

   file or replace it with the file Setup is trying to copy.

   Example

   -------

       Current file : Version 3.10a   Language: U.S. English

                     220800 bytes           10/1/92  3:11

       Proposed file: Version 3.10    Language: U.S. English

                     220800 bytes           03/10/92 3:10

   The replacement file is an older version than your current file.

    - To keep your currently installed driver file, press ENTER.

    - To replace the currently installed driver file, press ESC.

   At this point, each driver file should be replaced by pressing the ESC

   key.

   After Setup loads Windows, the Setup program begins to copy files,

   again finding newer versions than those provided with Windows 3.1.

   Setup prompts for action on each conflicting file as follows:

   The following file conflicts with the version already on your system:

       File: CLIPBRD.EXE

       Description: Windows for Workgroups

       The new version of the file ((Unknown)) you are trying to install is

       older than the currently installed version (3.10a).

       Do you want to replace the file that is already on your system?

          Yes      Help        No

   Replace these files by selecting the Yes option. Setup finds version

   conflicts with the following files:

       COMM.DRV

       DDEML.DLL

       GDI.EXE

       MAIN.CPL

       USER.EXE

       PRINTMAN.CPL

       WINFILE.EXE

       SHELL.DLL

       COMMDLG.DLL

       CLIPBRD.EXE

5. From the floppy disk used in step 3, copy WININI.W31 to the WINDOWS

   directory as WIN.INI and SYSINI.W31 to the WINDOWS directory as

   SYSTEM.INI.

6. Reboot the system, and start Windows 3.1 by typing WIN at the command

   prompt and pressing ENTER.

7. Remove the program icons that were added by the Windows for Workgroups

   Setup program.

   Delete the following icons from the Main Group:

      Clipbook Viewer

      Mail

      Schedule+

   Delete the following icons from the Accessories group:

      Chat

      WinMeter

      Net Watcher

   Delete the following icons from the Games Group:

      Hearts

8. Remove the files from the WINDOWS directory and the WINDOWS\SYSTEM

   subdirectory that are specific to Windows for Workgroups.

   Files in the WINDOWS directory to delete:

   CARDS.DLL     IMPEXP.DLL    MSSCHED.DLL  NDDENB.DLL    SCHEDMSG.DLL

   TRNSCHED.DLL  WGPOMGR.DLL   CLIPSRV.EXE  MSHEARTS.EXE  MSMAIL.EXE

   MSREMIND.EXE  NET.EXE       NETDDE.EXE   NETWATCH.EXE  SCHDPLUS.EXE

   WINCHAT.EXE   WINMETER.EXE  MSMAIL.HLP   MSHEARTS.HLP  NETWATCH.HLP

   SCHDPLUS.HLP  WINCHAT.HLP   WFWNET.HLP   NET.MSG       NETH.MSG

   RINGIN.WAV    RINGOUT.WAV

   Files in the SYSTEM directory to delete:

   WFWSETUP.CPL  VBROWSE.386   VCD.386      VDMAD.386     VNB.386

   VNETBIOS.386  VNETSUP.386   VPD.386      VPICD.386     VREDIR.386

   VSERVER.386   VSHARE.386    VWC.386      AB.DLL        COMMCTRL.DLL

   DEMILAYR.DLL  FRAMEWRK.DLL  MAILMGR.DLL  MAPI.DLL      MSSFS.DLL

   NDDEAPI.DLL   PABNSP.DLL    SENDFILE.DLL STORE.DLL     VFORMS.DLL

   WFWNET.DRV    MAILSPL.EXE   NETWORK.INF  MIDIMAP.OLD   LM21DRV.UPD

After performing these steps, Windows 3.1 should be successfully

reinstalled. However, if Windows 3.1 does not perform as expected, you must

reinstall Windows 3.1 and all Windows-based software to a new subdirectory.

For more information about DR-DOS, contact Novell.

For additional information on reinstalling other Windows versions,

query on the following words:

   windows reinstall

DR-DOS is manufactured by Novell, a vendor independent of Microsoft;

we make no warranty, implied or otherwise, regarding this product's

performance or reliability.

Additional reference words: 3.10 win31 wfwg 3rdparty uninstall

deinstall


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 and 3.11

------------------------------------------------------------------------

SYMPTOMS

========

When upgrading from Microsoft Windows 3.0 or 3.1 to Windows for Workgroups,

you may 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

=====

The Workgroup upgrade for Microsoft Windows version 3.0 and the Workgroup

add-on of 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.

NOTE: This problem can also occur if SETUPSTATE=1 is in the SYSTEM.INI file

when you upgrade to Windows for Workgroups.

WORKAROUND

==========

1. Install the appropriate version of Windows on your computer.

2. Using a text editor such as Notepad, open your SYSTEM.INI file

   and delete the SETUPSTATE= line from the [boot.description] section,

   if present. Save your changes and close the file.

3. Install the Workgroup upgrade or add-on Setup program again.

MORE INFORMATION

================

The Workgroup 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 Workgroup upgrade for Microsoft Windows version 3.0 users installs a

full version of Windows for Workgroups on machines running Windows 3.0. The

Workgroup add-on of Microsoft Windows version 3.1 installs a full version

of Windows for Workgroups on machines running Windows 3.1

Additional reference words: 3.10 3.11 peer quick short partial installation

win31 win30 win3.0 win3. wfwg addon five-user edition 5 1 one-user


NIC at I/O Port of 0360h May Prevent Local Printing

Article ID: Q95112

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

SYMPTOMS

========

If the Network Interface Card (NIC) used with Windows for Workgroups (WFWG)

is set to use an I/O Port address of 0360h, Windows may be unable to print

locally. Also, this setting may cause lost network connections after a

print job is sent to the local parallel port or the server may lock up when

a job is printed from another workstation.

CAUSE

=====

Parallel port LPT1 normally uses an I/O Port address of 0378h. Some network

cards (especially NE2000 compatibles) use 20 address segments; this places

the top of their address space at I/O Port address 0379h. So if a network

card is set to an I/O Port address of 0360h, there may be a hardware

conflict with the printer's I/O Port address.

WORKAROUND

==========

To work around this problem, set the network card to an I/O Port address of

0340h or lower. For more information on changing this setting on a network

card, consult the user's manual for the card.

Additional reference words: 3.10 win31 wfwg winnet dropped lost


WFWG Open File Handle Limits

Article ID: Q95118

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

----------------------------------------------------------------------

SUMMARY

=======

Windows for Workgroups (WFWG) version 3.1 is limited to 255 open file

handles per machine. This Windows for Workgroups limitation is due to the

MS-DOS limit of 255 open files at one time.

Windows for Workgroups 3.11 has the following open file handle limits:

 - In an MS-DOS virtual machine (VM) you are limited to 254.

 - In the WFWG Server VM you are limited to 1024.

 - If you are using 32-bit file access there is a theoretical limit equal

   to the amount of free RAM.

MORE INFORMATION

================

Some applications may require a server to have more than 255 files

open at one time. For example, a database application may have 255

files open at one time on a Windows for Workgroups server. If this

limit is exceeded, then an application-specific error message

concerning open files or memory may occur.

There are no workarounds to these limitations for Windows for

Workgroups.

REFERENCES

==========

"MS-DOS User's Guide and Reference," version 5.0, pages 252, 493-494

Additional reference words: 3.10 win31 wfwg maximum fox dbase paradox


Re-creating the Postoffice Initialization Procedure

Article ID: Q95200

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

SUMMARY

=======

When you first run Windows for Workgroups Mail, you are given the

option to connect to an existing post office or create a new post

office. After you make your choice, you cannot go back and choose

again. If you want to change your initial selection, you must use the

steps in this article to reinitialize Mail so that you can select the

option you want.

Steps to Re-Create the Mail Initialization Procedure

----------------------------------------------------

1. Open the MSMAIL.INI file in an ASCII text editor, such as 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.

MORE INFORMATION

================

The initialization procedure is defined for Mail in the MSMAIL.INI

file on the CustomInitHandler= line. This setting is defined as:

   CustomInitHandler=WGPOMGR.DLL,<procedure #>

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 post

office or create a new workgroup post office.

 - 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 post office.

Additional reference words: 3.10 3.11 wfwg


DynaComm Elite Requires a DLC Provider to Function with WFWG

Article ID: Q95397

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

SUMMARY

=======

FutureSoft technical support has confirmed that DynaComm Elite, a 3270

emulation package for Windows, requires a data link control (DLC)

provider to work correctly with Windows for Workgroups.

This article contains information concerning the Microsoft DLC (MSDLC)

protocol included with Microsoft LAN Manager for use with Windows for

Workgroups. If you need information not found in this article to set

up connectivity between Windows for Workgroups and the MSDLC protocol,

information and support are provided through the fee-based Microsoft

LAN Manager technical support line at (206) 635-7020.

MORE INFORMATION

================

If you are using Windows for Workgroups with Microsoft LAN Manager,

the file MSDLC.EXE is required to provide the DLC protocol stack.

For information on configuring MSDLC.EXE with Windows for Workgroups,

refer to the "Windows for Workgroups Resource Kit" for version 3.1,

pages E-14 to E-20, or contact Microsoft LAN Manager technical support.

For additional DLC protocol stack information, contact FutureSoft

Engineering.

DynaComm Elite is manufactured by FutureSoft Engineering, a vendor

independent of Microsoft; we make no warranty, implied or otherwise,

regarding this product's performance or reliability.

Additional reference words: 3.10 win31 wfwg 3rdparty wrk future soft

winnet


Disabling Peer-To-Peer Network Functionality with WFWG

Article ID: Q95470

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.1

----------------------------------------------------------------------

The following article contains information on the use of 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.

SUMMARY

=======

Although Microsoft Windows for Workgroups is designed to provide

peer-to-peer networking functions (such as local file sharing and

local printer sharing), you may occasionally need to disable the

ability to share local resources, or you may need to disable network

functionality completely.

This article contains procedures to disable various features and

capabilities of Windows for Workgroups. You can re-enable a feature by

reversing the procedure.

MORE INFORMATION

================

To Disable Sharing Local Resources

----------------------------------

To disable the ability to share local resources (both files and

printers), while maintaining the ability to connect to other network

servers, follow these steps:

1. Clear the Enable Sharing box in the Network Settings dialog box of

   Control Panel.

2. Use a text editor (such as Notepad) to add the following entry to

   the [network] section of the SYSTEM.INI file located in the Windows

   directory:

      [network]

      NoSharingControl=1

To Disable Sharing Local Files

------------------------------

To disable the ability to share resources (files) from the File

Manager, use a text editor to modify the WINFILE.INI file in the

Windows directory, and add the following section heading and entry:

   [restrictions]

   NoShareCommands=1

To Disable All Network Functionality

------------------------------------

To disable network functionality completely, including the ability to

share local resources, use a text editor to modify the [boot] section

of the SYSTEM.INI file located in the Windows directory. Change the

"network.drv=" entry from:

   network.drv=wfwnet.drv

to:

   network.drv=

NOTE: It is not possible to disable local printer sharing without also

disabling local file sharing.

Additional reference words: 3.10 win31 wfwg whitepaper winnet no net nonet


WFWG: Network Card Detection Hangs Machine During Setup

Article ID: Q95576

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

SYMPTOMS

========

If you disable hardware detection during Windows for Workgroups Setup

because network card detection (NCD) has made your machine stop

responding (hang), Setup doesn't perform any hard disk drive and video

adapter detection either. This results in 32-bit disk access support

not being installed.

RESOLUTION

==========

Microsoft recommends that you not use the /I switch to avoid NCD because

Windows for Workgroups automatically skips NCD the second time you run

Setup if it failed before. The following line is added to the [boot]

section of the SYSTEM.INI file before NCD takes place:

   ignore_hw_detect=true

If this switch is present in the SYSTEM.INI file, Setup skips NCD, but

continues to check your hard disk drive and video adapter.

NOTE: If you run Setup a second time and your computer hangs again,

use the /I switch.

Additional reference words: 3.10 3.11


Windows for Workgroups and NetBEUI Protocol

Article ID: Q95630

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

 - Microsoft Workgroup Connections version 1.0

--------------------------------------------------------------------

SUMMARY

=======

Microsoft Windows for Workgroups is a peer-to-peer networking

operating system. Every network operating system must provide a way to

organize the data that is to be sent and received over the network.

The primary way Windows for Workgroups accomplishes this is through

the NetBEUI protocol.

NOTE:  In addition to NetBEUI, Windows for Workgroups version 3.11 has

a routable protocol that you can use with routers.

MORE INFORMATION

================

Some protocols are aided by a transport. A transport handles the

organization of application messages, leaving the protocol to handle

only data. NetBEUI (NetBIOS Extended User Interface) is a protocol

that manages the packaging of both data and application messages.

NetBEUI and the Sliding Window Algorithm

----------------------------------------

NetBEUI, developed by IBM in 1985, is a windowing protocol. It uses an

adaptive sliding window algorithm, enabling it to determine how to

balance the load between sending and receiving data based on the size

of the network.

For example, when a workstation sends information over the network, an

acknowledgment is sent back telling the workstation the data reached

its destination. By utilizing adaptive windowing provided by NetBEUI,

the workstation can send additional information before it receives an

acknowledgment. With NetBEUI, it is possible to send more data overall

and increase throughput. This must be done on a controlled level so no

data is lost.

NetBEUI and Data Loss

---------------------

NetBEUI controls data loss in two ways:

 - By limiting the amount of data a receiver can store before it sends

   an acknowledgment. This is called the "receive window."

 - By limiting the amount of data that can be sent by the sending

   workstation before it must send an acknowledgment. This is referred

   to as a "send window."

To increase network throughput, the send window is sized greater than

or equal to the receive window. Having a larger send window increases

the chance of losing data. The lost data causes the sender to resend

the data and could potentially slow down the network. NetBEUI adjusts

these parameters dynamically so that the network load is optimized for

the size of the network.

Reliable Connection-Oriented vs. Unreliable Connectionless-Oriented

-------------------------------------------------------------------

The sliding window algorithm provides increased performance for a type

of network traffic called "reliable connection-oriented," or session

meaning that data is sent to a specific address on the network and it

must be acknowledged.

The other kind of traffic, "unreliable connectionless-oriented" or

datagram, does not require an acknowledgment. It is not sent to an

individual address. A datagram is broadcast to either a group of

workstations on the network (multicast address), or to everyone on the

network that understands the data (broadcast address). The benefit of

using a datagram is that it provides the ability to communicate with a

workstation without knowing its exact address. It can be used as a

precursor to the reliable connection-oriented method of exchanging

data.

NetBEUI and Routing

-------------------

NetBEUI is not a routable protocol. A routable protocol has the

ability to communicate with servers on networks in different cities,

or on different networks within the same city via routers or bridges.

NetBEUI can be routable only if it is on a Token Ring network. It can

accomplish this due to built-in Token Ring source routing. Not as

sophisticated as conventional routing, Token Ring source routing does

not include the ability to control the path that the data takes to

other networks. NetBEUI is optimized for the local area network

environment.

NetBEUI in Microsoft LAN Manager and Windows for Workgroups

-----------------------------------------------------------

If you load NetBEUI services from MS-DOS in Windows for Workgroups,

the functionality is the same as with LAN Manager.

In each implementation of the NetBEUI protocol, the services are

achieved through NetBIOS services provided to the presentation layer

of the OSI model, they all provide windowing services to optimize

throughput, and they all implement their session layer services via

DLC CCB2 and CCB3 protocols. They are functionally equivalent.

Loading NetBEUI at MS-DOS (before Windows)

------------------------------------------

NetBEUI is limited by static resources when loaded at the MS-DOS

level. Two examples of resources are the number of network connections

that can be made and the number of drives that can be shared. These

network resources are controlled by the SESSIONS= entry in the

PROTOCOL.INI file. If the line reads SESSIONS=6, no more than six

connections can be established.

Within windows, there are two settings which also must be pre-

allocated. They are NETHEAPSIZE=, for both standard and enhanced mode,

and NETDMASIZE= for enhanced mode only. These settings are in the

SYSTEM.INI file. The NETHEAPSIZE= setting controls the buffers windows

sets up in conventional memory for transferring data over the network.

Increasing this value decreases available conventional memory in MS-

DOS sessions. The NETDMASIZE= setting specifies the direct memory

access buffer size for NetBIOS transport software.

Loading NetBEUI from Windows

----------------------------

Loading NetBEUI from Windows is also referred to as loading the

protected mode protocol. VNB.386 is the virtual device driver that is

responsible for providing NetBEUI services in enhanced mode. VNB.386

allocates resources dynamically, so the static settings discussed

above are ignored. This means that if you have six network

connections, and you want a seventh it is possible even though your

SESSIONS= entry is set to 6.

One additional advantage is memory. VNB.386 starts with Windows, and,

as a result, does not use conventional memory; it loads into protected

mode. This means more memory at the MS-DOS command prompt in Windows.

Additional reference words: 1.00 3.10 wfwg 3.11


WFWG Err Msg: "Mail Could Not Connect to Your Mail Server"

Article ID: Q95790

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

---------------------------------------------------------------------

SYMPTOMS

========

If Windows for Workgroups Mail is unable to find the MASTER.GLB file

in the GLB subdirectory of the Workgroup Mail postoffice directory

structure, you will receive the following error message:

   Mail could not connect to your mail server

CAUSE

=====

Mail is unable to find MASTER.GLB under any one of the following

conditions:

 - The Workgroup postoffice computer is unavailable.

 - The postoffice directory is not shared.

 - You are using the wrong workgroup postoffice name.

 - The workgroup postoffice name is invalid.

 - The ServerPath= line in your MSMAIL.INI file is incorrect.

 - NetWare connectivity is installed.

MORE INFORMATION

================

The following information describes these conditions in detail.

Workgroup Postoffice Computer Unavailable

-----------------------------------------

To use the Windows for Workgroups mail system, one workgroup computer

must be set up as the postoffice. This computer handles user accounts

and mail messages for the workgroup. To provide these services, the

postoffice computer must contain the workgroup postoffice directory

structure and it must be running in 386 enhanced mode (it must also be

turned on).

NOTE: There can be only one postoffice per workgroup.

The Postoffice Directory Is Not Shared

---------------------------------------

If the postoffice computer is not sharing the postoffice directory

structure, no one will be able to access the postoffice. Workgroup

users will be able to work off line, but they will not be able to

receive or send messages.

Use File Manager to make sure the postoffice directory structure is

being shared on the postoffice computer.

Using Wrong Workgroup Postoffice Name

--------------------------------------

By default, the workgroup postoffice is named WGPO. However, in your

workgroup, the name may be different. Make sure the name you are using

for the postoffice is correct. (It should be the same as the share

name on the workgroup postoffice computer.)

Workgroup Postoffice Name is Invalid

------------------------------------

By default, the workgroup postoffice is named WGPO. You can use

another name provided that it doesn't exceed 8 characters and doesn't

contain any spaces. For example, changing the share name from "WGPO"

to "Post Ofc" (without the quotation marks) would cause unsuccessful

connections. Make sure that the name each user is trying to connect to

matches the name that was used as the share name on the postoffice

computer.

To correct this error, change the share name of the postoffice

directory to a valid name with eight or fewer characters. To do this:

1. Open File Manager on the postoffice machine.

2. Select the postoffice directory.

3. From the Disk menu, choose Share As.

4. From the Share Directory menu, change the Share Name entry to a

   name with eight or fewer characters. (Spaces count as characters.)

ServerPath= Line in MSMAIL.INI Is Incorrect

-------------------------------------------

When you log on to the workgroup mail system, Workgroup Mail checks

the ServerPath= line in your local MSMAIL.INI file to locate the post

office computer and directory structure.

If you are using universal naming convention (UNC) style paths to

refer to the postoffice computer, make sure the computer name and

share name are correct. If you are not sure of the names, you can use

File Manager to connect to the postoffice computer and verify the

computer and share names.

If you are using a redirected drive letter (M for example) for your

postoffice, make sure you have a network connection in File Manager

that agrees with the ServerPath= statement.

NetWare Connectivity Is Installed

---------------------------------

When you load the real mode redirector, the NetWare portion of the

protocol stack intercepts Interrupt 21h calls before any other protocol

(such as Microsoft NetBEUI). When you start Mail, Interrupt 21h is used to

find the postoffice computer. This results in a problem if your post

office is referred to by a UNC style path. NetWare does not understand

UNC and does not forward the UNC information to NetBEUI. Therefore, if

NetWare connectivity is installed, Mail displays the error message if

you start the real mode redirector before you start Windows. To avoid

this problem, do one of the following:

 - Switch to a redirected drive letter style path.

   -or-

 - Do not load the real mode redirector before you start Windows.

To switch to a redirected drive letter style path:

1. Add the following to the PROTOCOL.INI file.

   a. Increase the value for SESSIONS= to 20.

   b. Increase the value for NCBS= to 40.

2. In the MSMAIL.INI file, set the SERVERPATH= setting to the valid

   server drive (for example, SERVERPATH=M:).

3. Quit Windows and redirect the drive letter (M in this example) to

   the appropriate server and share name (\\<servername>\<sharename>).

Additional reference words: 3.10 errmsg


PCMail: Differences Between WFWG Mail and PC Mail 3.0

Article ID: Q95996

----------------------------------------------------------------

The information in this article applies to:

 - Microsoft Mail for PC Networks, version 3.0

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

----------------------------------------------------------------

SUMMARY

=======

This article describes the differences between Windows for Workgroups

Mail and Microsoft Mail for PC Networks, version 3.0.

MORE INFORMATION

================

The Workgroup postoffice architecture is similar to the architecture

for Microsoft Mail for PC Networks, version 3.0. This is so users with

connectivity needs beyond their workgroup can easily upgrade.

The postoffice structure and Windows client are identical except for the

following:

 - No Demo files are in the workgroup postoffice. Microsoft Mail for PC

   Networks does include these files.

 - There is no spell checker with Windows for Workgroups Mail. The spell

   checker is supplied with Microsoft Mail for PC Networks.

 - The postoffice in Windows for Workgroups does not support connections

   to external postoffices or gateways. For example, a Windows for

   Workgroups postoffice cannot connect to another postoffice or

   gateway.

 - The default ADMIN.TPL and ADMIN.INF files in Windows for Workgroups

   Mail are created with predefined user information in the workgroup

   postoffice. For example, the user templates included in Windows for

   Workgroups Mail contain template information regarding Phone number

   #1, Phone number #2, Office, Department, and Notes. These must be

   created separately in Microsoft Mail for PC Networks.

 - Microsoft Mail for PC Networks includes an administration program not

   created in Windows for Workgroups Mail. In Windows for Workgroups,

   the administration program is accessed via the Mail menu in the

   Windows Mail client.

 - Microsoft Mail for PC Networks includes an administration utility

   that is used to administer and configure the postoffice. The

   ADMIN.EXE program can be used to configure and administer the

   postoffice from any workstation on the network running MS-DOS. In

   Windows for Workgroups, the administration program is accessed via

   the Mail menu in the Windows Mail client. Only the administrator can

   log on under his or her account and administer the postoffice on

   the workstation only.

Additional reference words: 3.00 wfwg 3.1 3.10 3.11


WFWG: Printing with Banyan Vines Connectivity

Article ID: Q96092

----------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.1

----------------------------------------------------------------

SYMPTOMS

========

Sometimes when you print from Windows for Workgroups to a Banyan VINES

network printer, you can print only one job per Windows session. If

you send a second print job, that job is lost and an error message may

be displayed. For example, if you try to print from Microsoft Windows

Write, you receive the following error message:

   CANNOT PRINT

   Be sure that your printer is connected properly & use the Printers

   option in the Control Panel to verify that the printer is configured

   properly.

NOTE: If you print from Microsoft Word version 2.0 for Windows, the

second print job is lost but no error message appears.

CAUSE

=====

This problem is caused by the Banyan VINES redirector, REDIRALL.EXE.

Banyan is aware of this problem. We will post new information here in

the Microsoft Knowledge Base as it becomes available. For more

information, contact Banyan Systems, Inc.

WORKAROUND

==========

1. Open the WIN.INI file in an ASCII text editor, such as Windows

   Notepad.

2. In the [ports] section, add a universal naming convention (UNC)

   name for the desired printer. For example:

     LPT1:=

     ...

     \\SERVERNAME\PRINTERNAME=

3. Save the WIN.INI file.

4. Open the Control Panel window, choose the Printers icon.

5. Select the printer to be shared.

6. Choose the Connect button.

7. In the Ports window, choose the networks path name you specified in

   step 2.

8. Choose the OK button, and then close the Control Panel.

9. Exit Windows, then restart Windows to make your changes take

   effect.

Banyan VINES is manufactured by Banyan Systems, a vendor independent

of Microsoft; we make no warranty, implied or otherwise, regarding

this product's performance or reliability.

Additional reference words: 3.10 3rdparty


Print Conflicts Between Remote and Local MS-DOS Applications

Article ID: Q96131

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

SUMMARY

=======

In Windows for Workgroups, Print Manager manages all local and remote

print jobs except for those from local MS-DOS-based applications. A

conflict arises if a remote client sends a print job at the same time

an MS-DOS-based application is printing.

MORE INFORMATION

================

Since Print Manager does not control local MS-DOS-generated print jobs

and MS-DOS-based programs usually do not close printer ports when

their print jobs are complete, the redirector must use the

MS-DOS-based application's idle time to determine when to print the

remote print job. The time the redirector waits is specified in the

[Network] section of the SYSTEM.INI file in the PRINTBUFTIME=

statement. By default, this value is set to 45 seconds.

If the above situation occurs, you are warned that a potential device

conflict exists and if you continue, the printed output may be

incorrect or garbled. The local (print server) print job goes directly

to the port, breaking up and potentially interrupting the remote print

job.

If you have a shared printer on your machine, do not override a device

conflict warning. You may be able to work around this problem by

setting PRINTBUFTIME= to a lower value (such as 10 seconds).

Additional reference words: 3.10 wfwg


Setting Up WFWG on a Novell Workstation Without a Hard Disk

Article ID: Q96567

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.1

--------------------------------------------------------------------

The following article contains information on the use of 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.

SUMMARY

=======

Running Microsoft Windows for Workgroups on a computer with one

5.25-inch or 3.5-inch high-density disk drive and a hard disk with 9.5

megabytes (MB) available memory is fully supported. (We recommend that

you have a hard disk with 14.5 MB available memory). Windows for

Workgroups is not designed to be installed on workstations without

hard disks (computers without hard disks that are connected to a

network), and Microsoft does not support running Windows for

Workgroups with any type of diskless workstation. However, a

workaround to set up Windows for Workgroups on Novell workstations

that do not have hard disks is available.

This article contains information that you can use to install Windows

for Workgroups on a Novell NetWare workstation that does not have a

hard disk.

NOTE: A true diskless workstation (one with no floppy disk drive or

hard disk drive) using a network adapter with a boot ROM does not work

with Windows for Workgroups. This is because the boot ROM establishes

a network connection and does not allow the Windows for Workgroups

network drivers to coexist with the boot ROM.

MORE INFORMATION

================

To set up Windows for Workgroups on a diskless workstation on a Novell

network, use the following procedure:

1. Start the computer with a network boot disk and log on as

   supervisor.

   NOTE: If you upgraded from Windows 3.1 by using the SETUP /A command

   should remove the Windows 3.1 shared directory before continuing. For

   more information on upgrading a shared networked Windows directory,

   query on the following words in the Microsoft Knowledge Base:

      winnet and attrib and flag

2. Run SETUP /A from the Windows for Workgroups Disk 1. This process

   expands the Windows for Workgroups files and places them in a shared

   network directory.

3. Have each user start his or her computer with a network boot disk

   and log on. Run SETUP or SETUP /N (recommended) from the shared

   directory created in step 2. When prompted for the directory name,

   enter the network user's home directory.

   (A network boot disk contains the MS-DOS operating system and

   necessary files to establish network connection, that is, IPX and

   NETX. The boot disk must have approximately 1 MB of free disk space.

   The free disk space needed varies depending on which NDIS network card

   driver is installed.)

   NOTE: Windows 3.1 directories created with SETUP /N can only be

   upgraded to Windows for Workgroups with SETUP /N. Windows 3.1

   installations created with SETUP must be upgraded by SETUP.

4. After selecting the network adapter type and settings, the

   Compatible Networks dialog box appears. Select Novell NetWare and

   choose the Add button.

   During the setup process the following message appears:

      Setup cannot find or cannot update your system

      files on drive A:. If you started your system from

      a floppy disk, be sure to remove write-protection

      from your system startup (boot) disk. Then insert

      the disk into drive A and choose Retry.

      To copy system files to your Windows directory

      choose Cancel.

   This is normal. If your bootable floppy boot contains approximately 1

   MB of free disk space, select Retry.

When the setup process is finished, the boot disk will contain the

following files:

Filename        Size  Date      Time    Function

---------------------------------------------------------------------

COMMAND  COM     47845 04-09-91   5:00a  MS-DOS Command Interpreter

IPX      COM     26207 01-02-92   4:06p  Novell IPX (Not used by WFWG)

NET      MSG     70629 10-01-92   3:11a  Message help file for net.exe

CONFIG   OLD        22 02-18-93  12:24p  Old CONFIG.SYS before setup

AUTOEXEC OLD        24 02-18-93  12:29p  Old AUTOEXEC.BAT before setup

EMM386   EXE    110174 10-01-92   3:11a  386 Expanded Memory Manager

HIMEM    SYS     13824 10-01-92   3:11a  Manages the use of ext. memory

RAMDRIVE SYS      5873 10-01-92   3:11a  RAM disk device driver

SMARTDRV EXE     43609 10-01-92   3:11a  Disk cache

PROTOCOL INI       636 02-18-93   2:34p  Protocol initialization file

NETX     COM     52443 10-01-92   3:11a  Novell NETX (Updated by WFWG)

NETH     MSG    104570 10-01-92   3:11a  Message help file for net.exe

WORKGRP  SYS      7268 10-01-92   3:11a  WFWG real mode device driver

NET      EXE    415252 10-01-92   3:11a  WFWG redirector

PROTMAN  DOS     21680 10-01-92   3:11a  Protocol manager

PROTMAN  EXE     13760 10-01-92   3:11a  Protocol manager accessory

NDISDRVR DOS     24666 10-01-92   3:11a  NDIS network adapter driver

                                         (name depends on adapter)

MSIPX    COM     27130 10-01-92   3:11a  IPX to NDIS driver

MSIPX    SYS      4301 10-01-92   3:11a  IPX to NDIS shim

ROUTE    COM      4262 10-01-92   3.11a  Novell TR source routing drvr

PROTOCOL 000         0 02-18-93   2:34p  Old PROTOCOL.INI

CONFIG   SYS       204 02-18-93   2:38p  New CONFIG.SYS

AUTOEXEC BAT       117 02-18-93   2:38p  New AUTOEXEC.BAT

       23 file(s)     994496 bytes

                   141146 bytes free

The following lines are added/modified in the AUTOEXEC.BAT and

CONFIG.SYS files:

AUTOEXEC.BAT                      CONFIG.SYS

--------------------------------------------------------------

A:\SMARTDRV.EXE                   device=A:\protman.DOS /i:A:\

A:\net start                      device=A:\workgrp.sys

A:\msipx                          device=A:\ndisdrvr.DOS

A:\route (Token ring users only)  device=A:\msipx.sys

A:\netx                           LASTDRIVE=P

PATH=U:\WFWUSER;y:\wfwshare;a:\   DEVICE=A:\HIMEM.SYS

SET TEMP=U:\WFWUSER\TEMP          STACKS=9,256

Notes on Using Workstations Without Hard Disks

----------------------------------------------

 - A workstation without a hard disk has the same system requirements

   for running Windows for Workgroups 3.1 as a workstation with a hard

   disk drive. (The RAM requirement may be greater if you are using a

   RAM drive).

 - Running Windows for Workgroups in standard mode (the highest mode on

   an 80286 computer) makes it necessary to log on to the Windows for

   Workgroups network before you run Windows. Network commands such as

   Net Start and Net Logon Username will require information from the

   SYSTEM.INI file in the Windows user directory. Copy this file from the

   Windows for Workgroups user directory to the network boot disk. Note

   that changes made in the Networks dialog box in Control Panel will not

   update the SYSTEM.INI file on the boot disk. If you make changes in

   Control Panel, you must recopy the SYSTEM.INI file to the boot floppy

   disk before the changes can take effect.

 - To share local workstation resources (such as floppy disk drives,

   printers, and CD-ROM drives), you must create a RAM drive and set your

   SET TEMP environment variable to its location. The RAM drive needs to

   be of considerable size (2048K or larger) if you are planning to share

   a local printer because Print Manager will queue jobs into the RAM

   drive. To set up a 2 MB RAM drive, add the following line to your

   CONFIG.SYS file:

        DEVICE=A:\RAMDRIVE.SYS 2048 /E

Additional reference words: 3.10 win31 wfwg winnet disk less

hard-diskless


Using SQL Server over Novell NetWare with WFWG

Article ID: Q96568

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

----------------------------------------------------------------------

SUMMARY

=======

To use Microsoft SQL Server on a Novell NetWare network with Microsoft

Windows for Workgroups clients, the Microsoft Network Integration Kit

for Novell is required. This product allows SQL Server DB-Library

clients (MS-DOS, OS/2, or Windows) and ODBC clients to connect to SQL

Server using native SPX connections over NetWare, as opposed to using

the Novell named-pipe implementation.

The Novell OS/2 requester client software (DOSNP.EXE), a terminate-

and-stay-resident (TSR) program that allows use of named pipes with

IPX.COM, is no longer required to connect to SQL servers on Novell

NetWare networks.

MORE INFORMATION

================

If you need information not provided in this article when setting up

Microsoft SQL Server, contact Microsoft SQL Server Startup support at

(206) 637-7095. This service is available to SQL Server customers for

the first 30 days after purchase. To purchase additional SQL Server

support after setup,contact Microsoft at (800) 227-4679.

For more information on the Microsoft Network Integration Kit for

Novell, contact your local Microsoft-authorized reseller or call

Microsoft Consumer Sales at (800) 426-9400.

Additional reference words: 1.0 1.00 3.10 LAN Manager LANman sequel

mspix.exe DOSnp novel wfwg 3.11


NET START NETBEUI/BASIC/FULL/WORKSTATION/REDIR/LIST

Article ID: Q96954

------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

------------------------------------------------------------------

SUMMARY

=======

The Windows for Workgroups NET command contains support for real-mode

network functionality. It includes the real-mode network redirector

and the NetBIOS Extended User Interface (NetBEUI) protocol. This

article discusses the functionality of the following NET commands:

 - NET START NETBEUI

 - NET START BASIC

 - NET START FULL (NET START ENHANCED)

 - NET START WORKSTATION

 - NET START REDIR

 - NET START /LIST

MORE INFORMATION

================

NET START NETBEUI

-----------------

NET START NETBEUI loads the real-mode version of the NetBEUI protocol

into conventional memory. It does not load the real-mode network

redirector. If you start Windows for Workgroups with NetBEUI loaded,

most network virtual device drivers (VxDs) are used (such as

VREDIR.386 and VSERVER.386) except for VNB.386 (the NetBEUI VxD).

NET START NETBEUI hooks into the interrupt vector table at 5CH.

Programs often check 5CH to determine if NetBEUI is present and can do

so with the NET START NETBEUI command.

If you start Windows for Workgroups without using NET START NETBEUI

first, the NetBEUI VxD (VNB.386) loads and provides NetBEUI support

but does not hook 5CH. Applications that use 5CH for NetBEUI detection

fail in this situation.

NOTE: Until you use the NET START WORKSTATION command or start Windows

for Workgroups, the network redirector does not load.

NET START BASIC

---------------

NET START BASIC loads the real-mode network redirector into

conventional memory. If you have not already loaded a static protocol

stack (such as TCP/IP or XNS), NetBEUI also loads into conventional

memory.

NET START BASIC does not load support for named pipes and many LAN

Manager network application programming interfaces (APIs).

NET START FULL (NET START ENHANCED)

-----------------------------------

NET START FULL (synonymous with NET START ENHANCED) loads the real-

mode redirector into conventional memory along with support for named

pipes and other LAN Manager network APIs. As with NET START BASIC,

NetBEUI may install depending on the other protocols in use.

NET START WORKSTATION

---------------------

Using the NET START WORKSTATION command is equivalent to using NET

START FULL (by default). The AutoStart= setting in the SYSTEM.INI file

specifies the redirector loaded by the NET START WORKSTATION command.

NET START REDIR

---------------

The NET START REDIR command starts the default redirector as specified

in SYSTEM.INI.

NET START /LIST

---------------

The NET START /LIST command lists all network services that have

started.

Additional reference words: 3.10 wfwg 3.11


IBM PC Network Baseband Adaptr/A Untested, Not on WDL

Article ID: Q97596

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

SUMMARY

=======

The IBM PC Network Baseband Adapter /A network interface card (NIC)

driver, formerly available from the Microsoft WDL (Windows Driver

Library), is an untested driver. It has been known to have problems

and was removed from the WDL.

MORE INFORMATION

================

The IBMNET.EXE file (which contained the IBM PC Network Baseband Adapter

/A driver) also contained other driver files.  When expanded, IBMNET.EXE

produced driver files for the following:

 - IBM PC Network Baseband Adapter /A

 - IBM PC Network Baseband Adapter

 - IBM PC Network Adapter II

 - IBM PC Network Adapter II/A

IBMNET.EXE was removed from the WDL, and none of these drivers is

available from the WDL at this time.

Additional reference words: 3.1 3.11 wfwg


Paradox for Windows Cannot Access WFWG Shared Directory

Article ID: Q97736

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

SYMPTOMS

========

With Windows for Workgroups, if you try to open a file in a shared

directory on another machine from Paradox for Windows, you may receive

the following error message:

   Network initialization failed, cannot access Network lock file.

WORKAROUND

==========

To access files on other machines in a Windows for Workgroups network,

you need to use the SUBST command locally, at the server machine (the

computer with the shared directory), before you start Windows for

Workgroups. For more information, check your Paradox documentation for

information about using Paradox on a peer-to-peer network.

The SUBST command lets you substitute a string for a path and allows you

to associate a path with a drive letter. For more information on SUBST,

refer to your MS-DOS User's Guide and Reference or online help.

Additional reference words: 3.10 3.11 wfwg


Running Windows for Workgroups on a DEC Pathworks Network

Article ID: Q97737

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 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 described in this article do not function properly, use

a supported configuration or contact the manufacturer of your

third-party product for more information.

SUMMARY

=======

Although Digital Equipment Corporation (DEC) Pathworks has not been

tested with Windows for Workgroups and its use is not supported with

Windows for Workgroups, you can integrate the two networks following

the appropriate procedure in this article.

Please note that separate procedures are provided for Windows for

Workgroups 3.11 and Windows for Workgroups 3.1.

WINDOWS FOR WORKGROUPS 3.11 PROCEDURE

=====================================

To properly set up Windows for Workgroups version 3.11 with DEC

Pathworks, do the following:

1. Get DEC Pathworks version 4.0 or later running at the MS-DOS level.

2. Obtain the file DECNB.386 from DEC.

3. Install Windows for Workgroups 3.11

4. Select DEC Pathworks under the "Install Windows support for the

   following network only" option.

   NOTE: There are two options for DEC Pathworks: Version 4.0 and

   Version 4.1 and later. Be sure to select the correct option.

WINDOWS FOR WORKGROUPS 3.1 PROCEDURE

====================================

The procedure below describes the steps necessary to enable the

Windows for Workgroups 3.1 full redirector to connect to DEC Pathworks

running on an Ethernet network. For additional configuration options

(such as Token Ring, asynchronous DECnet, or the Windows for

Workgroups basic redirector), call DEC Technical Support at (800)

332-8000.

This procedure assumes the following conditions are true:

 - DEC Pathworks is installed in the C:\DECNET directory.

 - Windows for Workgroups is installed in the C:\WINDOWS directory.

 - Your boot drive is drive C.

If your system configuration differs, substitute the correct paths

where necessary.

To Integrate DEC Pathworks and Windows for Workgroups 3.1

---------------------------------------------------------

1. Make backup copies of the following files:

      AUTOEXEC.BAT

      CONFIG.SYS

      STARTNET.BAT

      PROTOCOL.INI

      SYSTEM.INI

   If you encounter any problems during this procedure, you can restore

   these files and return to your original working configuration.

2. In Windows for Workgroups Control Panel, choose the Network icon.

   Choose the Networks button and remove all the networks listed in

   the Other Networks In Use box. Choose the OK button twice to close

   the Compatible Networks and Network Settings dialog boxes. When

   prompted to restart Windows, choose the Continue button. Quit

   Windows for Workgroups, but do not restart your computer.

3. Open your AUTOEXEC.BAT file in a text editor, such as MS-DOS

   Editor, and make the following changes:

   a. Insert the REM command at the beginning of the NET START command

      line. For example, change

         c:\windows\net start

      -to-

         rem c:\windows\net start

   b. If the Pathworks directory is not already included in your PATH

      statement, add it. For example, change

         path c:\windows;c:\dos;

      -to-

         path c:\windows;c:\dos;c:\decnet;

4. Open your CONFIG.SYS file in a text editor and make the following

   changes:

   a. Insert the REM command at the beginning of the PROTMAN.SYS

      DEVICE command line. For example, change

         device=c:\decnet\protman.sys /i:c:\decnet

      -to-

         rem device=c:\decnet\protman.sys /i:c:\decnet

      NOTE: The CONFIG.SYS file contains two files with similar names:

      PROTMAN.SYS and PROTMAN.DOS. PROTMAN.SYS is the protocol manager

      for Pathworks, which you just disabled. PROTMAN.DOS is the

      protocol manager for Windows for Workgroups and should not be

      altered.

   b. Add a DEVICE command line to load the Pathworks file,

      DLLNDIS.EXE, before the line that loads WORKGRP.SYS. For

      example, change

         device=c:\windows\elnkii.dos

         device=c:\windows\workgrp.sys

      -to-

         device=c:\windows\elnkii.dos

         device=c:\decnet\dllndis.exe

         device=c:\windows\workgrp.sys

      NOTE: The file ELNKII.DOS may differ depending on the type of

      network interface card (NIC) you use.

5. The following two steps require that you use a text editor that has

   a cut and paste feature, such as MS-DOS Editor.

   a. Open the C:\DECNET\PROTOCOL.INI file, and cut the [DATALINK]

      section (including its title, [DATALINK]).

   b. Open the C:\WINDOWS\PROTOCOL.INI file, position the insertion

      point at the end of the file and paste in the [DATALINK]

      section. Do not close PROTOCOL.INI or quit the text editor.

6. Make the following additional changes to your

   C:\WINDOWS\PROTOCOL.INI file:

   a. Modify the BINDINGS statement in the [DATALINK] section so that

      it is the same as the BINDINGS statement for your other

      transports. For example, change

         bindings=elnkii.dos

      -to-

         bindings=ms$elnkii

      NOTE: In most cases, NetBEUI is your Windows for Workgroups

      transport. If this is the case, simply copy the BINDINGS

      statement from the [NetBEUI] section to the [DATALINK] section,

      and insert the REM command at the beginning of the original

      BINDINGS statement in the [DATALINK] section. For a more

      complete example of this modification, see the "Sample

      PROTOCOL.INI" section below.

   b. In the [DATALINK] section, make sure that the NI_IRQ statement

      is set to the same value as the INTERRUPT statement in your

      network card section. For example, if your network card section

      appears as follows

         [ms$elnkii]

         drivername=elnkii$

         interrupt=3

         ...

      change the NI_IRQ statement to read

         [DATALINK]

         ni_irq=3

   c. In the [NETWORK.SETUP] section, copy the LANA line for NetBEUI,

      and paste it on the next line. The line you paste should look

      similar to the following:

         lana0=ms$ewtrbtp,1,ms$netbeui

      NOTE: The first parameter, MS$EWTRBTP in this example, varies

      depending on the NIC you use.

   d. In the line you pasted, increase the LANA number by one and

      replace the last parameter, MS$NETBEUI with DATALINK. The

      resulting line should look similar to the following:

         lana1=ms$ewtrbtp,1,datalink

7. Open the STARTNET.BAT file in a text editor and make the following

   changes:

   a. Find the line that contains the NETBIND command and insert the

      REM command at the beginning of the line. For example, change

         %boot%\decnet\netbind

      -to-

         rem %boot%\decnet\netbind

   b. Add the NET START command after the line loading NETBIND. For

      example, change

         rem %boot%\decnet\netbind

      -to-

         rem %boot%\decnet\netbind

         c:\windows\net start

   c. Disable the command that starts the Pathworks redirector,

      REDIR.EXE, using the REM command. For example, change

         %boot%\decnet\redir5.exe

      -to-

         rem %boot%\decnet\redir5.exe

   d. Disable the command that loads the DLLNDIS driver using the REM

      command. For example, change

         %boot%\decnet\dllndis

      -to-

         rem %boot%\decnet\dllndis

   e. Locate the command lines that load DNNETH.EXE and add the /LANA

      switch to specify which LANA the DECnet protocol is using. (This

      is the same number you changed in step 6d; it is the LANA number

      for the DATALINK protocol.) For example, change

         %boot%\decnet\dnneth.exe /rem:2

         if errorlevel 1 %boot%\decnet\dnneth.exe /rem:2

      -to-

         %boot%\decnet\dnneth.exe /rem:2 /lana:1

         if errorlevel 1 %boot%\decnet\dnneth.exe /rem:2 /lana:1

   f. Locate the following section for the Pathworks redirector:

         echo -----------------------------------------------

         echo using basic redirector

         echo -----------------------------------------------

      Insert the line, GOTO TIMEDONE, as follows:

         goto timedone

         echo -----------------------------------------------

         echo using basic redirector

         echo -----------------------------------------------

   g. If you use LAT and/or CTERM, add the appropriate line(s) after

      the :TIMEDONE label. For example, if you want to add LAT, add

      the following lines:

         :timedone

         c:\decnet\lat.exe

      Or, if you want to add CTERM, add the following lines:

         :timedone

         c:\decnet\cterm.exe

      NOTE: If you plan to use LAT, LAD, and/or CTERM, you must copy

      the LAT.EXE, LAD.EXE, and/or CTERM.EXE files from the Pathworks

      PCSAV41 file service before you reboot.

8. Open your SYSTEM.INI file in a text editor and make the following

   changes:

   a. In the [386Enh] section, find the NETWORK statement and add the

      virtual network driver DECNET.386 as follows:

         [386enh]

         network=vnetbios.386,...,decnet.386

      NOTE: The DECNET.386 file is not included with Windows for

      Workgroups. If you have Windows version 3.1, it is located on

      Disk 2. If you are upgrading over a previous Windows

      installation that was set up for Pathworks, this file should

      already be in your WINDOWS\SYSTEM subdirectory. If this is a new

      Windows for Workgroups installation and you do not have Windows

      3.1, DECNET.386 is available from the DECPCI forum on CompuServe

      or from DEC Technical Support.

   b. Add the following statement to the [386Enh] section:

         timercriticalsection=10000

After you restart your machine, you can connect to DEC Pathworks

servers as well as other machines in your Windows for Workgroups

workgroup. If you cannot connect to your DEC Pathworks network,

contact DEC Technical Support.

NOTE: Pathworks servers do not appear in the list of shared

directories because they are not included in the Windows for

Workgroups network browsing system. To connect to a Pathworks server,

you must type the name of the server and share name.

Sample PROTOCOL.INI

-------------------

The sample PROTOCOL.INI file below has been modified by following the

previous steps. Comments on modifications appear in parentheses to the

right of statements. This file was taken from a system using NetBEUI

installed on a 3Com EtherLink II NIC.

[network.setup]

   version=0x0000

   netcard=ms$elnkii,1,MS$ELNKII

   transport=ms$netbeui,MS$NETBEUI

   lana0=ms$elnkii,1,ms$netbeui

   lana1=ms$elnkii,1,DATALINK

[protman]

   DriverName=PROTMAN$

[MS$ELNKII]              (NIC section)

   DriverName=ELNKII$

   INTERRUPT=3

   IOADDRESS=0x300

   MAXTRANSMITS=12

   TRANSCEIVER=onboard   (thin Ethernet cable)

[MS$NETBEUI]             (NetBEUI transport section)

   DriverName=netbeui$

   SESSIONS=6

   NCBS=12

   BINDINGS=MS$ELNKII

   LANABASE=0

[DATALINK]               (DEC Pathworks transport)

   DRIVERNAME=DLL$MAC

   LG_BUFFERS=16

   SM_BUFFERS=6

   OUTSTANDING=32

   HEURISTICS=0

   BINDINGS=MS$ELNKII    (changed to match NetBEUI BINDINGS line)

   NI_IRQ=3              (changed to match NIC INTERRUPT line)

REFERENCES

==========

DEC Technical Support can be reached by calling (800) 332-8000. DEC

provides a detailed document titled "PATHWORKS for DOS and Windows for

Workgroups Installation Guide," which describes how to configure

Windows for Workgroups and a Pathworks network for compatibility. The

document provides information on the following configurations and

topics:

   Physical Media:

      Ethernet

      Token Ring

      Asynchronous DECnet

      DECnet

   Protocols:

      DECnet

      Pathworks NetWare Coexistence

      Digital's LAST/LAD

      Pathworks NetBEUI

      Windows for Workgroups NetBEUI

      Windows for Workgroups Novell

   Miscellaneous:

      Running Windows for Workgroups Novell IPX on Digital's Ethernet

      Connecting to Pathworks for VMS or Pathworks for Ultrix

      Setting up Local Area Disk (LAD) Support

      Using InfoServers

You can download "PATHWORKS for DOS and Windows for Workgroups

Installation Guide" from the DECPCI forum on CompuServe, or you can

call DEC Technical Support.

Additional reference words: 3.10 wfwg 3.11


Using IBM LAN Server 1.3 with Windows for Workgroups

Article ID: Q97766

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 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 IBM LAN Server 1.3 network operating system is a Server Message

Block (SMB) compliant network and can be accessed from Windows for

Workgroups workstations with Microsoft LAN Manager connectivity using

the procedure outlined in this article.

Microsoft can ensure connectivity between Windows for Workgroups and

Microsoft LAN Manager or Novell NetWare only. Although the information

stated in this article may allow Windows for Workgroups and LAN Server

to coexist, Microsoft does not ensure the stability of Windows for

Workgroups running with this configuration.

MORE INFORMATION

================

Use the following procedure to access a LAN Server network:

1. At least one Windows for Workgroups machine on the network MUST use

   the LAN Server Domain name as its Workgroup name.

2. To install Microsoft LAN Manager as a secondary network, open

   Control Panel and choose the Network icon.

   Similar to Microsoft LAN Manager, IBM LAN Server is an SMB-compliant

   network that can interact with Windows for Workgroups as long as the

   same transport protocol (NetBEUI, for example) is used. The LAN

   Manager driver must be selected because Windows for Workgroups does

   not contain a specific LAN Server driver that would allow access and

   logon to a LAN Server Domain.

3. Under Options, select Networks.

4. Select Microsoft LAN Manager and choose the Add button so that it

   appears in the Other Networks In Use section.

5. Select Microsoft LAN Manager, choose the Settings button, and then

   select the appropriate Domain and/or Password settings.

6. The above procedure should permit LAN Server LOGON, but the HOME

   directory may still be inaccessible.

For more information on connecting to a LAN Server HOME directory,

query on the following words in the Microsoft Knowledge Base:

   directory and home and ibm and lan and server and share

Windows for Workgroups will automatically reestablish the connection

to the HOME directory (although it may be inaccessible) and any other

directory that the user has rights to each time Windows for Workgroups

is started. A user can also access two separate servers using the same

user identification without the passwords being identical with Windows

for Workgroups. With a LAN Server-only connection, this function would

require that the passwords be identical.

For additional information, contact IBM Technical Support.

LAN Server is manufactured by IBM, a vendor independent of Microsoft;

we make no warranty, implied or otherwise, regarding this product's

performance or reliability.

Additional reference words: 3.10 3.11 win31 wfwg Lanserver winnet

3rdparty


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\<NE2000.DOS>

      DEVICE=C:\WINDOWS\MSIPX.SYS

   NOTE: If you are using a different network card, the NDIS network

   card driver (<NE2000.DOS> 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:\<PATH>\LSL.COM

         C:\<PATH>\<your netcard's ODI MAC driver>.COM

         C:\<PATH>\ODINSUP.COM

         C:\WINDOWS\Net Start Netbind

         C:\<PATH>\IPXODI.COM

         C:\<PATH>\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 driver, NE2000.COM

      LANABASE=1

      [IPX$]

      DRIVERNAME=IPX$

      MEDIATYPE=NOVELL/ETHERNET

      ;BINDINGS=MS$NE2000  <== NDIS MAC driver, NE2000.DOS

      BINDINGS=NE2000      <== ODI MLID driver, 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.

Additional reference words: 3.10 win31 wfwg winnet 3rdparty tcp/ip

lsl.com


WFWG: Incorrect AutoStart=<Full-or-Base> Entry in SYSINI.WRI

Article ID: Q97768

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

----------------------------------------------------------------------

SYMPTOMS

========

The SYSINI.WRI file incorrectly lists the real-mode component value

"base" for the AutoStart= line of the SYSTEM.INI [network] section. If

you execute the NET START command with the value "base" in the

AutoStart= line, the following error message appears:

   Error 2185: The service name is invalid.

RESOLUTION

==========

To eliminate this error message, use the correct real-mode component

value, which is "basic."

MORE INFORMATION

================

For more information about real-mode values for the AutoStart= line of

the SYSTEM.INI [network] section, refer to page 6-65 of the "Microsoft

Windows for Workgroups Resource Kit" for version 3.1 or query on the

following words in the Microsoft Knowledge Base:

   net start and autostart

Additional reference words: 3.10 win31 wfwg winnet redirector 3.11


Spooling Print Jobs from MS-DOS-based Applications in WFWG

Article ID: Q98585

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

The following article contains information on the use of 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.

SUMMARY

=======

Windows for Workgroups does not have the ability to spool local print

jobs sent to the printer by MS-DOS-based applications. This article

contains a potential workaround for this situation. This workaround

may also alleviate device contention errors.

To spool print jobs from MS-DOS-based applications, you must print

from one machine to another (using a dummy port) and then redirect the

job back to the first machine. The print job is then put in the print

queue. This may eliminate any device conflicts when you try to print

to the local printer.

NOTE: This workaround works only if the application has the ability to

choose the LPT2 port over the LPT1 port.

MORE INFORMATION

================

For simplicity, the following example refers to Machine One and

Machine Two. In this example, Machine One has a shared local printer

on LPT1 that is being accessed over the network by Machine Two.

1. Install a printer driver for the port "LPT1.DOS" on Machine Two and

   share it.

2. From Machine One, connect to the share on Machine Two using LPT2.

3. Print from an MS-DOS-based application to LPT2. Your print job is

   effectively spooled.

Additional reference words: 3.10 wfw wfwg device contention 3.11

printing dos


Windows for Workgroups Mail Issues

Article ID: Q99108

-------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 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.

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.

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,<procedure #>

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 on the Novell naming conventions, check

   your Novell NetWare documentation. For more information on Windows

   for Workgroups naming conventions, see the "Windows for Workgroups

   Server, Share, and Mail Naming Conventions" section in this

   article.

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

(<machinename>\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 occurs:

   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 wish 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=\\newservr\wgpo

4. Save your changes, and restart the system.

The WGPO administrator should be able to administer the postoffice and

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 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 WFW 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 then appears that displays the .MMF

    file that was detected. 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 edit the MMF path in the File box

   from:

      C:\WINDOWS\MSMAIL.MMF

   to:

      C:\WINDOWS\<Mailbox Name>.MMF

   where <Mailbox Name> 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 3 through 6. 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

       <login>.CAL.<=== where <login> 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.

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

Additional reference words: 3.1 3.10 3.11 Wfwg post office novel

LANmanager limit schedule setup


WFWG: Status Bar Option in Chat Shows Incorrect Shortcut Key

Article ID: Q99387

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

SYMPTOMS

========

The Chat application in Windows for Workgroups displays an incorrect

shortcut key for the Status Bar command on the Options menu. The Options

menu indicates the letter "B" is the shortcut key for Status Bar. The

actual shortcut key is the letter "S."

STATUS

======

Microsoft has confirmed this to be a problem in Windows for Workgroups

version 3.1 and version 3.11. We are researching this problem and will post

new information here in the Microsoft Knowledge Base as it becomes

available.

Additional reference words: 3.10 3.11 network operating system


PIF Hot Key Causes Errors or Help to Appear in Mail/Schedule+

Article ID: Q99507

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

SYMPTOMS

========

Creating and using a program information file (PIF) for an MS-DOS-

based application that has a hot key sequence containing the F1 key

may cause the Help programs for both Mail and Schedule+ to appear when

you access the MS-DOS-based application and then return to either Mail

or Schedule+.

WORKAROUND

==========

To work around this problem, you must edit the PIF with the PIF Editor

program and modify the hot key sequence so that it does not include

the F1 key.

MORE INFORMATION

================

When you access an MS-DOS-based application with its hot key sequence

(as defined in its PIF) and the hot key sequence contains the F1 key,

the Help programs for Microsoft Mail and/or Schedule+ may pop up. One

of the following messages may also be displayed:

 - No Help is available for this command

-or-

 - Help Topic does not exist

This situation continues until you quit and restart Microsoft Windows

for Workgroups. Closing the MS-DOS-based application or exiting and

signing out of Mail and/or Schedule+ has no effect on this condition.

Steps to Reproduce Problem

--------------------------

1. Create a PIF for the MS-DOS command prompt that contains F1 in the

   hot key sequence.

2. Execute the MS-DOS command prompt using your PIF.

3. Start Microsoft Mail or Schedule+.

4. Use the hot key sequence to switch back to the MS-DOS command

   prompt.

The next time you enter Mail or Schedule+ and try to access any of the

menus, the Help program will appear. Subsequent attempts to access

Mail or Schedule+ may result in the aforementioned error messages.

Additional reference words: 3.10 3.11 Mail Schedule Plus help wfwg


Windows for Workgroups: Avoiding Hardware Conflicts

Article ID: Q99859

----------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

 - Microsoft Windows operating system version 3.1

----------------------------------------------------------------

SUMMARY

=======

This article summarizes four possible sources of hardware conflicts:

IRQ lines, upper memory address (UMA), base I/O address, and DMA

channels. It also briefly describes the function of each and suggests

a strategy for diagnosing and/or preventing hardware conflicts.

MORE INFORMATION

================

When you install peripheral devices, there are four possible sources

of hardware conflicts. (Not all devices use all four parameters or

settings, although some do. Most use IRQ, base I/O address, and/or

UMA.) The key to avoiding hardware conflicts is to ensure that no two

devices are configured to use any of the same settings.

A wide variety of symptoms may indicate hardware conflicts. These

include system hangs, general protection (GP) faults (and other error

messages), corrupted video displays, corrupted printing, limited

functionality from one or more installed devices, intermittent

performance, and so on.

Diagnostic programs, such as Microsoft Diagnostics (MSD), can

sometimes help determine which IRQs and upper memory ranges are in use

and which are available. Currently, however, computer card

manufacturers do not adhere to any industry standard for reporting the

current status of a card when probed by diagnostic software.

Therefore, the only accurate way to determine the current settings for

a card is to consult the manufacturer's documentation or inspect each

card.

IRQs and DMA channels are single numbers (for example 1, 3, or 7). I/O

base and upper memory addresses include or cover a range (for example,

D000-D800 or 360h-380h). Typically, these settings are chosen through

DIP switches or jumpers on the card. Sometimes the cards are software

configurable or both hardware and software configurable. For more

information, consult your manufacturer's documentation.

IRQ

---

An interrupt request line (IRQ) is a line trace etched on the circuit

board from the expansion slot to the programmable interrupt controller

(PIC) chip through which a peripheral device can notify the CPU. Under

most circumstances, each device must use its own IRQ line. IBM

PC/AT-compatible design architecture provides for a possibility of 16

IRQ lines (0-15), some of which are reserved for standard devices such

as the keyboard, floppy disk drives, the system clock, and so forth.

Communication (COM) ports 1 and 3 typically share IRQ 4; COM ports 2

and 4 share IRQ 3. Therefore, a potential conflict exists if devices

are installed on both COM ports 1 and 3 or on COM ports 2 and 4.

Available IRQ lines (for sound cards, network adapters, scanners, bus

mouse, video adapters, tape drives, SCSI interfaces, and so forth)

usually include IRQs 5, 9, 10, 11, 12, 13, and 15. 8-bit expansion

slots provide access to IRQs through 7. 16-bit slots generally provide

access to IRQs through 15.

Not all devices allow the selection of any IRQ number. Consult the

device's manufacturer or its documentation for information on which

IRQs can be used by a particular device and select an IRQ that does not

conflict with currently installed devices; or, change an installed

device's IRQ to a different one to make available an IRQ for the new

device.

NOTE: You may need to reconfigure application software settings after

changing IRQs of previously installed devices.

UMA

---

A device's upper memory address (UMA) is a range of address space

somewhere between A000 and FFFF for use by the device. This

corresponds to "using" some portion of memory between 640 kilobytes

(K) and 1 megabyte (MB). While physical system RAM cannot be used by

the device, the "addresses" are used and are therefore unavailable to

the system or other devices.

Conflicts can occur if two hardware devices try to occupy the same

address range or if an application, a device driver, or a

terminate-and-stay-resident (TSR) program does not detect that this

address range is already in use and tries to occupy it.

The entire UMA range is the same range shared by the video adapter

(A000-CFFF typically), the system ROM (0FFF-FFFF typically), and any

installed cards that use UMAs. Furthermore, loading device drivers and

TSR programs high places them in this range as well and can increase

the potential for conflicts to occur.

To avoid UMA conflicts, use the following suggestions:

 - Install cards before you optimize your upper memory area. If you

   have already optimized the UMA and need to add a new card, load

   everything low, add the new card, and then try to load items high.

   Optimizing the UMA after installing cards avoids fragmenting the UMA

   range. This may allow more (or larger) TSR programs and/or device

   drivers to be loaded high.

 - Carefully plan the use of the entire UMA range when you install

   several peripherals and/or when you try to maximize conventional

   memory. Consult the manufacturer or the documentation to determine the

   memory range required by each device driver, TSR program, and

   peripheral. Note the options for this range's "starting" address (for

   example, C000, D000, or D800). Ensure that no two devices (device

   drivers or TSR programs loaded high or peripherals) are sharing any

   part of a range within this space.

 - It may be necessary to use the EMM386.EXE "exclude range" switch

   (X=) in the CONFIG.SYS file or the EMMexclude= parameter in the

   [386enh] section of the SYSTEM.INI file. This option prevents software

   from accessing the specified ranges in cases where the software does

   not recognize that the range is already occupied.

Base I/O Address

----------------

Base I/O address (I/O port) is another "address" or path for system-

to-peripheral communication. The address table is 00H through FFFFH

and should not be confused with UMA mentioned above. A device's I/O

port range has a base address (for example, 300 or 320 or 3A0, and so

forth). Each port address covers a range (8, 16, or even 32 bytes);

therefore, there exists a possibility of overlap and conflict with

devices whose starting addresses are close together. Consult the

manufacturer's documentation for range size and starting address

options. Ensure that each card has exclusive use of the range it

occupies.

DMA Channel

-----------

Direct memory access (DMA) channel is a means for peripherals to

directly access RAM memory without requiring the services of the CPU.

Many devices that move large amounts of data (network cards, sound

boards, hard disk drive controllers, and so forth) take advantage of

this feature to enhance overall system performance and increase data

throughput within certain applications.

The DMA channel is designated by a single number (1 through 7). Not

all devices use it. Some can use it as an option. Consult your

manufacturer's documentation for information on how, when, and why to

use this option. Ensure each device has exclusive use of its channel.

NOTE: DMA conflicts are somewhat less likely than UMA and base I/O

address conflicts. Fewer devices use it; and, in the case of a sound

card for example, the card's DMA channel may be in use only when the

application using the card is running.

Managing Complex Systems

------------------------

To help manage complex systems, make a chart like the one below, which

documents the current settings of each device. Keep this chart

available and consult and update it when you install more hardware.

   Hardware         IRQ         Base I/O         UMA      DMA

   -----------------------------------------------------------

   Mouse            Com 2 (3)   COM 2(2F8h)      N/A      N/A

   Device 1         5           300              D000     2

   Device 2         x           x                n/a      x

   Device 3         x           x                x        x

Additional reference words: 3.10 wfwg win31 3.11


WFWG Err Msg: An Error Occurred While Reconnecting...[SYS0000]

Article ID: Q100020

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

----------------------------------------------------------------------

SYMPTOMS

========

If you log on to a Microsoft LAN Manager domain when starting Windows

for Workgroups and you are running a logon script that makes network

drive connections, the following error message may appear:

   An error occurred while reconnecting X: to <\\SERVER\SHARE:>

   [SYS0000]

   Do you want to continue restoring connections?

This error may appear for one or more persistent network connections.

Although this error occurs, any persistent connections should still be

accessible from File Manager.

CAUSE

=====

Using LAN Manager logon scripts for network drive connections in

conjunction with Windows for Workgroups is not recommended since

Windows for Workgroups maintains its own list of persistent network

connections in the CONNECT.DAT file. If you need to use a logon script

for network drive connections, use the workaround detailed below.

WORKAROUND

==========

To work around this error message, rename the CONNECT.DAT file in the

Windows directory to CONNECT.OLD and add the /PERSISTENT:NO (/P:N)

parameter to lines in the logon script that make network drive

connections. The following line is an example:

   net use x: \\server\share /p:n

Any previous Windows for Workgroups persistent network connections

that aren't created with the logon script need to be manually

reconnected, which rewrites the CONNECT.DAT file. Make sure not to

create any network connections that are already in the logon script.

Once the Windows for Workgroups persistent connections are re-created,

you should not have any problems using logon scripts for other network

connections as long as there is a /P:N parameter after the NET USE

command so that it does not write to the CONNECT.DAT file.

MORE INFORMATION

================

This error is caused by the LAN Manager logon script using a NET USE

command, which by default writes the network drive connection to the

CONNECT.DAT file used by Windows for Workgroups for persistent network

connections.

The Windows for Workgroups 386 enhanced mode redirector always looks

for a CONNECT.DAT file for any persistent connections and tries to

establish any connections present in the file. Since a connection was

already created by the NET USE command in the logon script, when the

386 enhanced redirector tries to make the connection, the above error

message appears.

This error does not occur if you start Windows for Workgroups in

standard mode since the real-mode redirector should have already been

started at MS-DOS and any persistent network connections are

established at that point.

Additional reference words: 3.10 win31 wfwg 3.11


How to Use Keystrokes to Insert Special Characters

Article ID: Q100381

-------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows operating system version 3.1

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

-------------------------------------------------------------------

SUMMARY

=======

The Character Map program included with Windows and Windows for

Workgroups provides you with extended characters and special

characters that you can insert into other Windows-based applications.

MORE INFORMATION

================

Characters from Character Map can be inserted into an application by

following the steps listed in Help under the subject "Inserting a

character into a document." You can also do this is by pressing the

key(s) displayed in the bottom-right corner of the the status bar of

Character Map. Numeric keys must be typed on the numeric keypad.

You can use the following steps to insert special characters into a

Windows-based application:

1. Switch to the application in which you want to insert the

   characters.

2. Select the same font that you selected in Character Map.

3. Position the cursor where you want the characters to appear.

4. Press the key(s) listed next to "Keystroke:" in the status bar.

NOTE: The above steps do not work if the CTRL key is part of the

sequence.

Printed results may differ depending on the font you use and the

printer and video drivers installed.

Additional reference words: How to WFW WFWG Win31 Mapper Control 3.10

3,11 online help


Windows for Workgroups and Windows NT Interoperability

Article ID: Q100548

------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows NT operating system version 3.1

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

------------------------------------------------------------------

SUMMARY

=======

To ensure smooth interoperability between Windows NT and Windows for

Workgroups, there are several issues that must be addressed. When

setting up your network, be aware of the following issues:

 - Browsemaster Conflicts

 - Guest Accounts

 - User Name Duplication

This article discusses each of these issues.

MORE INFORMATION

================

Browsemaster Conflicts

----------------------

Browsemaster contentions can occur between Windows for Workgroups

workstations and Windows NT workstations when a workgroup or domain

contains at least one machine of each type. You may have difficulty

seeing servers in a Windows NT network from a Windows for Workgroups

workstation if the workstation is a backup browsemaster and not

registered in the Windows NT network. To work around this problem, add

the following line to the [network] section of the SYSTEM.INI files in

all Windows for Workgroup machines on the network:

   MaintainServerList=no

This workaround stops all Windows for Workgroups workstations from

trying to be browsemasters. If you use this workaround, you need to

ensure that at least one Windows NT machine (workstation or server) in

the workgroup or domain is running at all times. Until a Windows NT

machine is running or a user changes the value of the

MaintainServerList variable to "auto" and reboots, no browsing can

occur (you receive error 6118). Another way to enable browsing in this

situation is to log onto the domain or workgroup with a valid account

(even a guest account works).

Guest Accounts

--------------

Guest accounts should remain enabled on domain controllers. Instead of

removing guest accounts to restrict access to certain services, simply

remove any undesired guest account rights in User Manager.

User Name Duplication

---------------------

There should not be user name duplicates on different domains. If a

user name is duplicated across different domains, there will be

inconsistent results when a logon is attempted from a Windows for

Workgroups workstation on that Windows NT network.

Additional reference words: 3.10 introp wfwg winnet 3.11


Creating a Custom Separator Page for PCL5 Printers

Article ID: Q100730

-----------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

-----------------------------------------------------------------

SYMPTOMS

========

When you print to a shared network printer from Windows for

Workgroups, the printer may not eject the final page of a print job.

WORKAROUND

==========

To work around this problem, you can create a custom separator file

that contains control codes to force the printer to eject the last

page.

NOTE: The custom separator file must be specified in Print Manager on

the machine that is acting as the print server. This file affects only

print jobs that are printing from other workstations, not jobs from

the workstation server itself.

MORE INFORMATION

================

The custom separator file must be in either Clipboard file format or

Windows Metafile format. The easiest method is to create a Clipboard

file as follows:

1. Open Microsoft Write.

2. Turn your NUM Lock key ON, and use the numeric keypad (this

   procedure does not work if you use the number keys at the top of

   your keyboard).

3.  On a clean page, press ALT+027 followed by an uppercase letter E.

   This should give you the escape character and an uppercase letter E.

   The escape character is displayed as a rectangle on the screen. Do not

   place a space between the escape character and the letter E.

   NOTE: The printer control codes typed in step 3 are specific to

   printers that use the PCL5 printer language. Printer control codes

   for your particular printer may vary. Please consult your printer

   documentation for details.

4. Select the two characters you typed. From the Edit menu, choose

   Copy.

5. Open the ClipBook Viewer and select the window titled Clipboard.

6. From the File menu, choose Save As, and save the file as follows:

      c:\windows\formfeed.clp

7. Open Print Manager and choose Separator Pages from the Options

   menu.

8. Select Custom Separator File, and specify your Clipboard file

   (c:\windows\formfeed.clp), and then choose OK.

Documents you print to your Windows for Workgroups shared printer will

now issue a form feed prior to printing.

This custom separator file can be printed on all printers shared on

the Workgroup server.

Additional reference words: 3.10 winprint wfwg


WFWG: Schedule+ Prompts to Archive and Delete Old Appointments

Article ID: Q100792

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

----------------------------------------------------------------------

SUMMARY

=======

By default, at six-month intervals, Schedule+ in Windows for

Workgroups 3.1 displays a message asking if you want to archive and

delete old appointment information. The message reads as follows:

   There is information stored in your schedule file which is older

   than the limit set for discarding data. Would you like to delete

   it?

There is no way to disable this message. The message continues to

display at the start of Schedule+ until you archive and delete the old

information.

MORE INFORMATION

================

The full retail version of Schedule+ has an administrator utility that

allows variable time periods for archiving old appointment

information.

After you archive the Schedule+ data, the data doesn't appear in

Schedule+ anymore. However, you can access this data by selecting the

File menu option, then selecting Open Archive, and then opening the

correct archived data file.

Additional reference words: 3.10 schedule plus error 6 3.11


No Inbox in Windows for Workgroups Mail or Microsoft Mail 3.0

Article ID: Q100977

-------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

 - Microsoft Mail for Windows, version 3.0

-------------------------------------------------------------------

SUMMARY

=======

If you are running Windows for Workgroups Mail or Microsoft Mail for

Windows, version 3.0 and you choose Shared Folders, you can no longer

view the Inbox.

MORE INFORMATION

================

In both Mail products, there are two types of folders: shared and

private. Only one type of folder can be viewed at a time. When you

view the shared folder, the Inbox does not appear because it is a part

of the private folder. When you choose Window on the menu bar, only

two commands appear on the list, Outbox and Shared Folder.

To retrieve the Inbox, do one of the following:

 - From the View menu, choose Private Folders.

   -or-

 - From the View menu, choose Open Inbox. (CTRL+G also opens the

   Inbox.)

   -or-

 - From the Window menu, choose New Window.

Additional reference words: 3.10 wfwg msmail outbox


Files Modified by Workgroup Connections Setup Program

Article ID: Q101173

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Workgroup Connections version 1.0

--------------------------------------------------------------------

The Setup program for Microsoft Workgroup Connections version 1.0

modifies the CONFIG.SYS and AUTOEXEC.BAT files located at the root

directory of the startup drive, regardless of where you are installing

Workgroup Connections. This operation is by design.

Workgroup Connections 1.0 also creates SYSTEM.INI and PROTOCOL.INI

files in the directory where you installed Workgroup Connections. If

you mistakenly installed Workgroup Connections into your Windows for

Workgroups directory, it modifies the SYSTEM.INI and PROTOCOL.INI

files that  are required for Windows for Workgroups. This may cause

errors to occur when you run Windows for Workgroups.

Additional reference words: 3.10 wc wfwg connection remote diskless

1.0


Running PC-NFS 5.0 with Windows for Workgroups

Article ID: Q101177

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.1

---------------------------------------------------------------------

SUMMARY

=======

Sun Microsystems has announced that version 5.0 of its PC-NFS network

operating system software supports connectivity with Microsoft Windows

for Workgroups (WFWG) version 3.1. This article describes how to set

up PC-NFS with Windows for Workgroups. This procedure is designed for

use with PC-NFS version 5.0 only; previous versions of PC-NFS are not

compatible with Windows for Workgroups.

Microsoft will assist in the installation of PC-NFS with Windows

for Workgroups. Sun Microsystems is responsible for supporting the

installation, configuration, and use of PC-NFS. Customers who have

issues that cannot be resolved with standard network troubleshooting

should contact Sun Microsystems for assistance.

MORE INFORMATION

================

Installing WFWG and PC-NFS Version 5.0

--------------------------------------

To use PC-NFS version 5.0 with Windows for Workgroups version 3.1, you

must use the updated WFWNET.DRV driver included with PC-NFS. To update

the driver, simply delete the current version located in your

WINDOWS\SYSTEM subdirectory, and replace it with the current version.

To install and provide connectivity to PC-NFS and Windows for

Workgroups, do the following:

1. Install Windows for Workgroups version 3.1.

2. Run the PC-NFS Install program, and select NDIS as the network

   adapter.

3. Run the QuickNDIS utility, and configure it for Windows for

   Workgroups.

4. Run the Winstall program.

NOTE: For further information about installing and configuring PC-NFS,

refer to your PC-NFS documentation.

The installation program for Sun PC-NFS makes changes to the

AUTOEXEC.BAT, CONFIG.SYS, PROTOCOL.INI, and SYSTEM.INI files. These

changes are documented in your PC-NFS installation guide.

AUTOEXEC.BAT

The following lines are added to the AUTOEXEC.BAT file, but the SET

statements vary with each installation:

   Set TZ=EST5EDT

   Set NFSDRIVE=C

   Set NFSPATH=C:\NFS

   Set TN_DIR=C:\NFS\TELNET

   C:\NFS\PRT *

   C:\NFS\NET INIT

   C:\NFS\RTM

CONFIG.SYS

The following lines are added to the CONFIG.SYS file after the device

drivers installed by Windows for Workgroups. The lines should appear

in this order:

   Device=C:\NFS-NDIS.SYS

   Device=C:\NFS\PCNFS.SYS

   Device=C:\NFS\SOCKDRV.SYS

PROTOCOL.INI

The following section is added to the PROTOCOL.INI file:

   [NFS-NDIS]

   DriverName=NFSLINK$

   Bindings=MS$ELNKII

SYSTEM.INI

The following lines are added to the identified sections of the

SYSTEM.INI file:

   [Boot]

   secondnet.drv=pcnfs.drv

   [386Enh]

   secondnet=pcnfs.386

WFWG and Previous Versions of PC-NFS

------------------------------------

If you install Windows for Workgroups version 3.1 on a network running

a version of PC-NFS earlier than version 5.0, Windows for Workgroups

does not display a warning that this version of PC-NFS is not

supported. (Normally, Windows for Workgroups issues a warning during

setup if the currently installed networking software is not compatible

with Windows for Workgroups.)

Windows for Workgroups version 3.1 Setup does not have the ability to

detect the presence of a PC-NFS network.

To run Windows for Workgroups properly on a Sun PC-NFS workstation,

you must either update your PC-NFS software to version 5.0 or remove

all references to PC-NFS connectivity from the CONFIG.SYS and

AUTOEXEC.BAT files. If you don't remove the references to the Sun

client software before rebooting, the system may stop responding

(hang) as the conflicting network device drivers attempt to load.

The products included here are manufactured by Sun Microsystems, a

vendor independent of Microsoft; we make no warranty, implied or

otherwise, regarding these products' performance or reliability.

Additional reference words: 3.10 3.1 wfwg win31 winnet 3rdparty


WFWG Err Msg with New NETAPI.DLL: Undefined Call to Dynalink

Article ID: Q101238

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

---------------------------------------------------------------

SYMPTOMS

========

If you use the NETAPI.DLL file available as WINUP7.ZIP on Compuserve

and NetWire with Microsoft Windows for Workgroups (WFWG) version 3.1,

you receive the following error message:

   Undefined call to Dynalink

This error also occurs if you use the NETAPI.DLL from WINUP8.ZIP with

Windows for Workgroups version 3.1 or 3.11. This file loads in the \WINROOT

subdirectory.

Novell's WINUP9.ZIP contains a NETAPI.DLL file in the OLDDLLS subdirectory.

If you use this NETAPI.DLL file, the error occurs.

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 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.

Additional reference words: 3.1 3.10 wfw wfwg "Call to Undefined

Dynalink" novel


WFWG: Where Workgroup Mail Finds the Default Account Name

Article ID: Q101846

------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

------------------------------------------------------------------

When you start Workgroup Mail for the first time and choose to set up

your own account, the default account name is the same name you used

when installing Windows for Workgroups version 3.1.

Workgroup Mail in Windows for Workgroups version 3.1 reads the

customer name information from the USER.EXE file located in the

WINDOWS\SYSTEM directory for the default account name.

The account name can be changed during the setup process of

Workgroup Mail.

Additional reference words: 3.10 wfwg wfw31 user 3.11


WFWG Err Msg: Network Name Was Deleted

Article ID: Q102811

--------------------------------------------------------------

 This information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------

SYMPTOMS

========

If you install Windows for WorkGroups over an existing LAN Manager

installation, you may receive the following error message:

   Network name was deleted

CAUSE

=====

This error occurs if you still have the LAN Manager entry for NET.EXE

(something similar to "c:\<lanman dir> net.exe=1,") in a file called

DOSAPP.INI.

RESOLUTION

==========

To correct this problem, rename or delete the DOSAPP.INI file. After

doing so, the error no longer appears.

Additional reference words: 3.10 WFW WFWG 3.11


WFWG: Separator Page Prints First Name of User Only

Article ID: Q102812

------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

------------------------------------------------------------------

SYMPTOMS

========

If you try to print a separator page in Microsoft Windows for

Workgroups version 3.1, the separator page may not print the exact

logon name of the person generating the print job.

CAUSE

=====

The separator page option is designed to print a cover sheet for each

print job sent to the printer. The separator page contains the name of

the document, the user who printed the document, and the time and date

the print job was completed. The user name that the separator page

prints is the same name with which the user logged on to the system.

If the logon name contains a space, however, only the characters

preceding the space are printed on the separator page. For example, if

you log on with your first and last name separated by a space, only

your first name prints on the separator page. This is true for all

three separator page options (Simple, Standard, and Custom).

WORKAROUND

==========

To work around this problem, replace the space in the logon name with

another character, such as an underscore.

Additional reference words: 3.10 wfwg login log in 3.11


FastTips: Troubleshooting Windows for Workgroups Q&A

Article ID: Q104333

----------------------------------------------------------------------

This information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

----------------------------------------------------------------------

1. Q. I have several files with the extension .CLN in my Windows

      subdirectory. What is the purpose of these files?

   A. Three .CLN files (PROTOCOL.CLN, SYSTEM.CLN, and WIN.CLN) are

      created upon completion of the Windows for Workgroups version 3.11

      setup procedure. These files are copies of your PROTOCOL.INI,

      SYSTEM.INI, and WIN.INI files. If you encounter a problem after

      installing and using Windows for Workgroups, you can use these files

      to return to your original installation state. To do this, copy each

      .CLN file to the respective .INI file.

2. Q. I'm receiving the error message, "The Protocol Manager has

      reported an incomplete binding." What is causing this error?

   A. The error "The Protocol Manager has reported an incomplete binding"

      is most often caused by a conflict in the upper memory area or an

      incorrect setting in the PROTOCOL.INI file. To correct this error,

      add the line X=A000-EFFF to the end of the EMM386 line in your

      CONFIG.SYS file.

3. Q. I'm still receiving the "incomplete binding" error message after

      I exclude the upper memory area with EMM386 in the CONFIG.SYS file.

      What should I try next?

   A. If you still receive the "incomplete binding" error message after

      you have excluded the upper memory area, use the following three

      steps to check for possible errors:

      1. Run Network Setup (located in the Network group in Program

         Manager), choose Drivers, and note the brand name and model of

         the network adapter card listed under Network Drivers. If the

         network adapter card is incorrect, choose the Remove button,

         then choose the Add Adapter button to select the correct driver.

      2. In Network Setup, choose Drivers, then choose Setup and note the

         IRQ, I/O Port, and Base Memory address configurations. If any of

         these settings is incorrect, change the entry to its correct

         setting.

      3. The last item to check is protocols. You must have at least one

         protocol selected in the Network Drivers dialog box. Windows for

         Workgroups supports the NetBEUI protocol.

4. Q. I'm still receiving the "incomplete binding" error message even

      after I have confirmed and corrected all the settings in the

      PROTOCOL.INI file. What should I do now?

   A. If you continue to receive the "incomplete binding" error message

      after you verify that all settings in the PROTOCOL.INI file are

      correct and you are using a network adapter with a BNC thinnet

      connector, try the following steps:

      1. Turn off the computer and disconnect any cables from the card.

      2. Attach a T connector to the card with two terminators on the T.

      3. Restart the computer. If the message "The Protocol Manager

         has reported an incomplete binding" no longer displays, there

         is a problem with the cable.

      4. Confirm the I/O port address and IRQ settings in Control Panel

         match the actual settings of the network card.

      5. Verify that there are no I/O port address or IRQ conflicts

         occurring between your network card and other adapters in your

         computer.

5. Q. I'm running Microsoft Windows for Workgroups on a Novell Token

      Ring network and receiving the error message "File server cannot be

      found." What is causing this error?

   A. If you are running on a Novell Token Ring network, the error "File

      server cannot be found" may be caused by loading ROUTE.COM in the

      AUTOEXEC.BAT file. Edit the AUTOEXEC.BAT file and remove the line

      that loads ROUTE.COM. After you save the file, restart your machine.

6. Q. I'm receiving the error message "NetBIOS session limit

      exceeded." What is causing this error?

   A. "NetBIOS session limit exceeded" refers to the number of

      connections that can be made to your server at any one time.

      This limit is affected by the number of sessions set in the

      [MS$NetBEUI] section of the PROTOCOL.INI file. Other protocols

      refer to variables other than SESSIONS. For more information,

      refer to your network protocol documentation. Use the following

      steps to increase the number of sessions:

      1. From the Windows directory, open the PROTOCOL.INI file in an

         ASCII text editor, such as Microsoft Windows Notepad.

      2. Locate the section titled [MS$NetBEUI].

      3. Double the value following SESSIONS=. When you increase the

         value following SESSIONS=, you must also increase the value

         following NCBS=. The NCBS value should be double the value

         of SESSIONS=.

      4. Save the file and restart Windows.

7. Q. What is Microsoft Network Diagnostics?

   A. Microsoft Network Diagnostics is a tool designed to aid network

      administrators and Microsoft support engineers in troubleshooting

      network connectivity problems with networks using an IPX or NetBIOS

      protocol. To most effectively use this tool, exit Microsoft Windows

      and type "net diag" (without the quotation marks) at an MS-DOS

      command prompt. For more information on using NET DIAG, consult the

      "Using Microsoft Network Diagnostics to Troubleshoot Networking

      Problems" section in Appendix E of the "Windows for Workgroups 3.11

      User's Guide."

Additional reference words: 3.11


FastTips: Using Microsoft At Work PC Fax with WFWG 3.11 Q&A

Article ID: Q104396

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

1. Q. What types of fax modems can I use with Microsoft At Work PC Fax?

   A. There are three types of fax modems available: Class One, Class Two,

      and CAS. Microsoft At Work PC Fax supports all three types of fax

      modems. It is important to know which type of fax modem you have

      before you begin troubleshooting any problems. Microsoft At Work

      PC Fax supports different features depending on the type of fax

      modem you are using.

2. Q. I can't send or receive faxes using Microsoft At Work PC Fax.

      What could be causing this problem?

   A. If you cannot send or receive faxes through Microsoft At Work PC

      Fax, make sure that your fax modem is on the list of compatible

      fax modems. Also, check the ROM version in your modem by starting

      Microsoft Windows Terminal and configuring it for the port to

      which the modem is connected. Enter the command ATI3 and press

      ENTER. Compare the ROM version number reported back to the

      terminal screen with the README.WRI file packaged with Windows

      for Workgroups.

3. Q. I have confirmed that my fax modem is on the list of compatible

      fax modems and that the ROM version is compatible, but I still

      can't send or receive faxes using Microsoft At Work PC Fax. What

      should I do?

   A. If your modem and ROM version meet the requirements for use with

      Microsoft At Work PC Fax and you still cannot send or receive

      faxes, try the following steps:

      1. Be sure the fax modem works as a modem under other Microsoft

         Windows applications, such as Terminal or Cardfile. Also, try

         sending to or receiving from a different fax machine to determine

         if the problem is related to your fax modem or your phone

         connection.

      2. If you have a CAS modem, be sure that you have the CAS software

         installed in either your CONFIG.SYS or AUTOEXEC.BAT file. Consult

         your modem user's guide for specific information about installing

         these drivers.

4. Q. I cannot send or receive binary files using Microsoft At Work

      PC Fax and my security features are unavailable (grayed out).

      Why is this occurring?

   A. Binary file transfer and security features are available only

      between machines running Microsoft At Work PC Fax with Class One

      fax modems.

Additional reference words: 3.11 wfwg wfw awfax efax


FastTips: Windows for Workgroups 3.11 Setup Issues Q&A

Article ID: Q104397

-----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

-----------------------------------------------------------------------

1. Q. What are the system requirements for Microsoft Windows for

      Workgroups version 3.11?

   A. Windows for Workgroups 3.11 requires a 386SX or higher machine

      and a minimum of 3 megabytes (MB) of memory (4 MB is recommended).

      Windows for Workgroups requires a minimum of 13 MB of free disk

      space (or 18 MB if you install all components). Upgrading over

      Windows for Workgroups 3.10 reduces these free disk space

      requirements to a minimum of 3.5 MB (or 8.5 MB for all components).

      Upgrading over Windows 3.1 requires a minimum of 6.5 MB (or 9 MB

      for all components). Workgroup Connections require 320 kilobytes (K)

      of free conventional memory and 1 MB of free disk space. Windows for

      Workgroups 3.11 requires a VGA or higher video adapter.

2. Q. How do I start Windows for Workgroups version 3.11 in standard

      mode?

   A. Because Windows for Workgroups 3.11 uses protected-mode drivers and

      NDIS 3.0, it does not support standard mode.

3. Q. How do I set up Windows for Workgroups version 3.11 for an EGA

      display?

   A. Windows for Workgroups 3.11 does not ship with display

      drivers for EGA, CGA, or Hercules Monochrome displays. You can

      download these drivers from the Microsoft Download Service (MSDL)

      by calling (206) 936-6735. The MSDL supports 1200, 2400, and

      14,4000 baud (V.32 and V.42) with 8 data bits, 1 stop bit, and no

      parity. You can download the file WDL.TXT to obtain a list of all

      the display, printer, and network card drivers that are available

      on the MSDL.

4. Q. Can I use Windows for Workgroups version 3.11 without a network?

   A. Windows for Workgroups 3.11 does not require a network

      installation. To install 3.11 and use its non-network enhancements,

      select the No Network option during Setup. This option is available

      for users who want the speed enhancement and Microsoft At Work PC

      Fax features of 3.11 but are not connected to a network. You can

      also start Windows for Workgroups 3.11 without network components

      by simply typing the command WIN /N.

5. Q. I'm having difficulty installing Microsoft Windows for

      Workgroups version 3.11. What should I do?

   A. Complete information on installing Windows for Workgroups 3.11 is

      contained in Chapter 2 of the "Windows for Workgroups 3.11 User's

      Guide." The following are some general setup tips:

      1. Before you run the setup program, start your machine with

         minimal CONFIG.SYS and AUTOEXEC.BAT files.

      2. Set up Windows for Workgroups in a new directory.

      3. Workgroup Connections should be installed to a new directory; do

         not upgrade over Windows.

      4. During Setup, if your machine stops responding (hangs), Setup may

         have recognized your hardware incorrectly. To correct such

         problems, please refer to Chapter 2 of the "User's Guide."

6. Q. Where can I find more information about setup entries and the

      setup of supported network adapter cards?

   A. To properly configure your network adapter card, refer to the

      complete instructions in Appendix D of the "User's Guide."

      The following are some general tips:

      1. Entries referring to Workgroup and Computer names should be

         limited to 15 characters. All other share names should conform

         to the MS-DOS file-naming convention.

      2. Choose Custom Setup so that you can modify the network adapter

         card configuration.

      3. Be aware that some cards may be software configurable. The

         Windows for Workgroups network adapter card installation

         software configures some of these cards. However, most

         software-configurable cards must be reconfigured using the

         software provided with the specific card.

7. Q. Where can I find information on installing third-party network

      protocols and adapters?

   A. Information on installing third-party networks and protocols can

      be found in Appendix C and Chapter 9 of the "User's Guide." The

      following are some general tips:

      1. TCP/IP and DLC are supported protocols under Windows for

         Workgroups 3.11. You can obtain information about using these

         protocols by calling Microsoft Sales at (800) 426-9400.

      2. IPX and IPX ODI protocols are supported under Windows for

         Workgroups 3.11.

      3. If your network adapter card is not on the Network Adapter

         Compatibility List, obtain the NDIS driver specific to your

         network adapter card and the OEMSETUP.INF file from the vendor

         of your network adapter.

8. Q. How can I install Windows for Workgroups 3.11 on all

      workstations from a network server?

   A. To set up Windows for Workgroups 3.11 from a network server, first

      run SETUP /A from the installation disks and specify the network

      drive and directory when prompted. When you have completed this

      step from each workstation, change to the network directory from

      which you ran SETUP /A, and run SETUP /N on each user's workstation.

      (The installation disks are not required at this point.) This

      command sets up the user directory for the user.

Additional reference words: 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

---------------------------------------------------------------------

SUMMARY

=======

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)

 - 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 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\<drivername.xxx>

      device=c:\windows\msipx.sys

   where <drivername.xxx> 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 <XXX>                    This line is set to the I/O base

                                 being used.

   INT <XX>                      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 <XXXXX>                   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.

 - 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 Customer

   Service at (206) 936-8661.

Additional reference words: 3.1 3.10 WFWG


FastTips: Using Novell NetWare with WFWG 3.11 Q&A

Article ID: Q104845

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

1. Q. Where can I get the files I need to set up Novell as a secondary

      network with Windows for Workgroups 3.11?

   A. To obtain the files required to support Novell as a secondary

      network, contact your local Novell authorized reseller or call

      Novell Technical Support at (800) 526-7937. You can also download

      the support files from the Novell CompuServe forum. At the

      CompuServe prompt, type "go novfiles" (without the quotation

      marks). Download the file WINUP7.ZIP. If you are using Novell's

      ODI protocol implementation, also download DOSUP7.ZIP. For more

      information, read the NETWORKS.WRI file located in your Windows

      subdirectory.

2. Q. How do I install support for Novell NetWare if I'm using ODI?

   A. Obtain the necessary Windows support files from Novell and from

      your network adapter manufacturer. Have the Windows support files

      available on a disk or in a subdirectory of the hard disk. Configure

      the workstation for proper NetWare functionality at MS-DOS and

      then use the following steps in Windows for Workgroups:

      1. Run Network Setup and choose Networks.

      2. Select the option button labeled "Other" and then select the

         proper Novell workstation shell.

      3. Choose Drivers, then choose Add Adapter and select your network

         card from the list of adapters.

      4. Ensure the User, Workgroup, and Computer names are correct.

      5. When prompted for the location of the Novell support files and

         the NET.CFG file, specify the appropriate path. When prompted,

         choose Restart Computer.

      For more information, read the NETWORKS.WRI file located in your

      Windows subdirectory.

3. Q. How do I install support for Novell NetWare if I'm using

      IPX.COM?

   A. Configure the workstation for proper NetWare functionality at

      MS-DOS and then use the following steps in Windows for Workgroups:

      1. Run Network Setup, choose Networks, and select the Install

         Microsoft Windows Network option button.

      2. Select the option button labeled "Other," select Novell NetWare

         Workstation Shell 3.X, then choose OK.

      3. Choose Sharing, select the appropriate options, and choose OK.

         Make sure that the option "IPX Support Driver (Monolithic) with

         NetBIOS transport" appears in the Drivers dialog box. This driver

         replaces your specific network adapter driver. Do not add a driver

         for your specific network adapter.

      4. Ensure User, Workstation, and Computer names are correct.

      5. When prompted for the location of the Novell support files,

         specify the appropriate path. When prompted, choose Restart

         Computer.

   For more information, read the NETWORKS.WRI file located in your

   Windows subdirectory.

4. Q. How do I install support for Novell NetWare if I'm using MSIPX?

   A. If your computer is configured to use MSIPX in Windows for

      Workgroups 3.10 and you upgrade to 3.11, the setup program detects

      that you are using MSIPX and preserves this configuration. However,

      once setup is finished, MSIPX is not an installable option. If you

      want to preserve this configuration and prevent overwriting the MSIPX

      configuration, take care not to change the network card settings in

      Network Setup.

5. Q. Does Windows for Workgroups 3.11 support access to Novell

      NetWare servers using ArcNet?

   A. Windows for Workgroups 3.11 supports simultaneous access to

      Novell NetWare servers and 3.11 peer services using ArcNet network

      hardware. This functionality is supported through the use of either

      Novell's monolithic IPX or IPXODI.

6. Q. How do I install support for Novell NetWare if I'm using ArcNet?

   A. To install support for Novell NetWare with ArcNet, you must have

      the Novell NetWare support files for Windows and a fully functioning

      NetWare installation at MS-DOS. Once you do, use the following steps

      in Windows for Workgroups:

      1. Run Network Setup, choose Networks, and select the Install

         Microsoft Windows Network option button.

      2. Select the option button labeled "Other," select Novell

         NetWare Workstation Shell 3.X, then choose OK.

      3. If you are using IPX.COM, choose Drivers, and select the option

         "IPX Support Driver (Monolithic) with NETBIOS transport." This

         driver replaces your specific network adapter driver. If you are

         using ODI, you should install the "IPXODI Support Driver (ArcNet)"

         option instead of your specific network adapter.

      4. When prompted for the location of the Novell files, specify the

         appropriate path.

      For more information, read the NETWORKS.WRI file located in your

      Windows subdirectory.

7. Q. What is the NET.CFG file and why is it important?

   A. NET.CFG is a text file that the Novell ODI implementation uses

      to configure various settings for the workstation network hardware

      and software. The most important things to know about the NET.CFG

      file are that you should have only one and it should be located

      in the same directory as LSL.COM. This file should contain a LINK

      DRIVER section that specifies your network adapter's MLID name,

      hardware configuration, and your Novell Network's frame type.

      For more information on creating a NET.CFG file, consult your

      NetWare documentation.

Additional reference words: 3.11 WG0689


WFWG Mail: DoubleSpace and Highest Security Options

Article ID: Q105138

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

----------------------------------------------------------------------

SUMMARY

=======

In version 3.11 of Microsoft Windows for Workgroups, there are

additional menu items not supplied in the retail package of Microsoft

Mail for PC Networks.

Under the Mail Options menu, there is a section titled "Optimize Local

Mail File." The following new choices are available:

   DoubleSpace

   Highest Security

These two choices are specific to version 3.11 of Microsoft Windows

for Workgroups Mail and are only available when running with MS-DOS

version 6.0 or later.

MORE INFORMATION

================

DoubleSpace is considered to have less encryption (resulting in less

security) but better performance (that is, increased speed) than the

Highest Security option. DoubleSpace is available with MS-DOS version

6.0 or later only.

The Highest Security option uses the same Mail message file (.MMF)

encryption algorithm that Microsoft Mail for PC Network uses. Highest

Security is not as fast as DoubleSpace because time is used to encrypt

and decrypt the .MMF file.

The DoubleSpace encryption is built into DoubleSpace itself. A file

cannot be copied from a DoubleSpace drive, imported to a different

computer, and easily read. Since the file allocation table (FAT)

system is cluster-based, DoubleSpace uses its own FAT (which is called

the Microsoft DoubleSpace FAT [MDFAT]) to achieve sector allocation.

This encryption option is fast, however, it is not as secure as the

encryption algorithm used in the Highest Security setting.

MORE INFORMATION

================

Additional information about DoubleSpace can be found on pages 118-136

in the MS-DOS "User's Guide" and in Chapter 3 of the MS-DOS "Technical

Reference Manual."

Additional reference words: double space WFWG WGPO


Differences Between LAN Manager and WFWG WinPopup

Article ID: Q105276

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SUMMARY

=======

This article describes the differences between Microsoft LAN Manager

versions 2.1 and 2.2 WinPopup and Windows for Workgroups version 3.11

WinPopup.

MORE INFORMATION

================

LAN Manager 2.1 and 2.2

-----------------------

LAN Manager WinPopup can store five messages at a time. When more than

five messages are in the queue, the oldest message is stored in a

MESSAGES.LOG file.

Windows for Workgroups 3.11

---------------------------

Windows for Workgroups WinPopup can store up to 15 messages and does

not use a message log. Windows for Workgroups WinPopup also has

scrolling ability to allow you to view previous messages or jump ahead

in the message list.

Additional reference words: 3.11 wfw wfwg


Net Watcher Audit Log Shows Two Entries for Failed Password

Article ID: Q105277

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SYMPTOMS

========

The Net Watcher event log may show a duplicate entry for each failed

attempt to connect to one of your resources. Each entry shows the

exact same Date/Time, Computer, User, Share, Type, Access, Document,

and Event.

CAUSE

=====

When the Windows for Workgroups redirector on the client machine

receives a message that the attempt to connect failed due to an

invalid password, the redirector tries to establish the connection

again using your logon password. In this situation, the server sees

two logon attempts and logs them both in the Net Watcher event log.

Additional reference words: 3.11


Sharing Printers on Serial Ports in Windows for Workgroups

Article ID: Q105419

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.10 and 3.11

--------------------------------------------------------------------

SUMMARY

=======

Microsoft Windows for Workgroups does not support sharing

communications (COM) ports. However, it is possible to share a printer

connected to a COM port.

When you share a printer, Windows for Workgroups does not share the

printer port. The printer queue is shared. In other words, Windows for

Workgroups is sharing the software supporting the port, not the device

connected to the port.

MORE INFORMATION

================

The mechanism for sharing a printer on a COM port is the same as it

is for a printer on a parallel port:

1. Install the appropriate printer driver and connect it to the

   desired COM port.

2. Open Print Manager.

3. Select the printer on the COM port that you want to share.

4. From the Printer menu, choose Share Printer As.

5. Select Re-share At Startup if desired.

The printer queue is now shared and can be accessed across the network

by other machines.

Additional reference words: 3.10 3.1 wfw wfwg sharing communications

port


CAS Modem Fails to Receive Faxes with WFWG 3.11

Article ID: Q105502

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SYMPTOMS

========

If you are using Microsoft Windows for Workgroups version 3.11 with

32-bit file access enabled and you have an Intel CAS fax modem, your

modem may fail to receive faxes.

CAUSE

=====

Intel CAS fax modems require a driver called CASMGR.EXE, which can be

run from the AUTOEXEC.BAT file or from the MS-DOS command prompt. This

driver is responsible for communicating API calls from fax

applications to the CAS modem and for sending information from the fax

modem to the fax applications. When the CAS fax modem receives a fax,

CASMGR.EXE spools this information to the hard disk drive. CASMGR.EXE

opens the file in a virtual machine (VM) and obtains a handle. It then

uses the handle to write to the file as data comes in from the fax

board (often at interrupt time).

The problem occurs if a second VM is active at the same time. The

second VM is using a handle that is only valid for the first VM.

NOTE: By default, Windows for Workgroups 3.11 starts a second VM to

run the server; therefore, this problem is likely to occur.

WORKAROUND

==========

To work around this problem, you can either:

 - Disable 32-bit file access in Windows for Workgroups.

   -or-

 - Remove the CASMGR.EXE line from your AUTOEXEC.BAT file, and add it

   to your WINSTART.BAT file. To create a WINSTART.BAT file, use a text

   editor, such as Notepad, to create a file with that name; type the

   CASMGR.EXE line that you cut from your AUTOEXEC.BAT file into the new

   WINSTART.BAT file; save the WINSTART.BAT file in your Windows

   directory, and restart your system. WINSTART.BAT loads the CASMGR.EXE

   file into the system VM only, and ensures that all its file input/

   output occurs from that VM.

   NOTE: This workaround prevents any MS-DOS-based applications that

   require CASMGR.EXE from accessing the fax modem.

   WARNING: If you use a WINSTART.BAT file with Microsoft Windows version

   3.1 in 386 enhanced mode, the system may stop responding (hang) when

   you exit Windows. The only solution to this problem is to delete or

   rename WINSTART.BAT and load the programs in WINSTART.BAT from the

   AUTOEXEC.BAT file.

MORE INFORMATION

================

For more information on WINSTART.BAT, refer to page 531 of the

Microsoft Windows "User's Guide" for version 3.1.

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.

Additional reference words: 3.11 WFWG VFAT EFAX AWFAX


Network-Based Installation Issues with WFWG 3.11

Article ID: Q105732

------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

------------------------------------------------------------------

SUMMARY

=======

Microsoft Windows for Workgroups version 3.11 differs from previous

versions of Windows (including Windows for Workgroups 3.1) with

respect to the requirements for, and the limitations of, network

server-based shared installations (that is, SETUP /A and SETUP /N

installations).

This article is intended to provide system administrators with some

guidelines for performing such installations.

MORE INFORMATION

================

When you set up a server-based shared installation of Windows for

Workgroups 3.11, be aware of the following:

 - In the Microsoft LAN Manager and Windows NT environment (or any

   network requiring the installation of the real-mode Windows for

   Workgroups 3.11 redirector prior to accessing the server with the

   shared, SETUP /A, directory), Windows for Workgroups 3.11 nodes have

   client functionality only.

   NOTE: Because Novell NetWare requires its own real-mode redirector

   (giving the node access to the shared directory before loading Windows

   for Workgroups and its peer-to-peer network components), this

   limitation may not exist in integrated Windows for Workgroups 3.11/NetWare

   environments.

 - When running SETUP /N to a workstation from a Novell server, the

   Windows for Workgroups Setup program requires that Novell's Windows

   support files exist in the shared directory on the server (that is,

   the directory created with SETUP /A). The following files need to be

   copied to the shared Windows directory prior to running SETUP /N:

      NETWARE.DRV

      NETWARE.HLP

      NWPOPUP.EXE

      VNETWARE.386

      VIPX.386

   NOTE: Other third-party networks may present the same restrictions;

   refer to your network product documentation or vendor for more

   information.

Novell NetWare is manufactured by Novell, a vendor independent of

Microsoft; we make no warranty, implied or otherwise, regarding this

product's performance or reliability.

Additional reference words: 3.11 winnet novel net set up set-up


HPPCL5E.DRV Does Not Save Paper Tray Selection

Article ID: Q105810

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows operating system version 3.1

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

SUMMARY

=======

The Hewlett-Packard LaserJet 4 printer driver, HPPCL5E.DRV, does not

save paper tray selections.

MORE INFORMATION

================

The HPPCL5E.DRV printer driver supports the Hewlett-Packard LaserJet

4, 4M, 4SI, and 4SI MX printers. If you change the Paper Source

setting for your printer in the Setup dialog box in Control Panel, the

selection remains for that Windows session but reverts back to the

default Auto Select option when you reenter Windows.

WORKAROUND

==========

To work around this situation, edit the WIN.INI file and manually

change the "tray" selection in the [HP LaserJet 4/4M or 4SI/4SI MX]

driver section to one of the following:

   1  MP Tray

   2  Paper Cassette

   4  Manual Feed

   5  Envelope Feeder

   7  Auto Select

   11 Lower Cassette

For example:

   [HP LaserJet 4/4M,LPTx]

   paper=1

   prtcaps=-5240

   prtcps2=4561

   tray=1

The products included here are manufactured by Hewlett-Packard, a

vendor independent of Microsoft; we make no warranty, implied or

otherwise, regarding these products' performance or reliability.

Additional reference words: 3.10 3.1 3.11 win win3 win31 wfw wfwg not

saving won't save lose lost disappear hewlet packard IV LJ4 LJIV


GP fault in MS Mail "Work Offline" Dialog when Exiting WFWG

Article ID: Q105830

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

---------------------------------------------------------------------

SYMPTOMS

========

If the "Would you like to work offline?" dialog box is open when you exit

Windows for Workgroups, Microsoft Mail causes a general protection (GP)

fault.

STATUS

======

Microsoft has confirmed this to be a problem in version 3.1 and version

3.11 of Microsoft Windows for Workgroups Mail. We are researching this

problem and will post new information here as it becomes available.

Additional reference words: 3.10 3.1 3.11


MSD Version 2.1 Does Not Detect Gateway2000 ColorBook

Article ID: Q105926

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

Microsoft Diagnostics (MSD) version 2.1 detects the Gateway2000

ColorBook as an unknown computer. Since the Gateway2000 ColorBook BIOS

does not contain the word Gateway, MSD cannot identify the computer

type.

Additional reference words: 3.11 gateway 2000 color book


WFWG 3.11: UNC Filenames with Word Fail on Novell Network

Article ID: Q106021

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

 - Microsoft Word for Windows, version 2.x

---------------------------------------------------------------------

SYMPTOMS

========

After you install Windows for Workgroups version 3.11, you may not be

able to use universal naming conversion (UNC) filenames with Microsoft

Word for Windows if you use a Novell network.

RESOLUTION

==========

To work around this problem, add the NovellNet=YES entry to the

[Microsoft Word 2.0] section of the WIN.INI file.

MORE INFORMATION

================

NovellNet=Yes specifies how Word for Windows verifies that the

directory is valid. For example, if you have the following directory

structure

   root ----->  users  -----> personal

Word for Windows will verify that the \USERS\PERSONAL directory exists

before it tries to open the file. If that same directory structure

exists on a Novell network, as follows

   root ------------> users -----------> personal

   (read only)        (no privileges)    (read/write privileges)

When Word for Windows tries to access the USERS directory to reach the

USERS\PERSONAL directory, the Novell network replies that you have no

privileges in that directory; therefore, Word for Windows returns an

error message for the task at hand.

The NovellNet setting ensures that Word for Windows changes

directories to USERS\PERSONAL before reading the file and then

performs a DOS call to change the directory back after it is done.

This method works properly because you haven't directly accessed the

USERS directory, which may have no privileges.

Additional reference words: 3.11 winword


Network Dialog Err Msgs Truncated with (Small Fonts)

Article ID: Q106022

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SYMPTOMS

========

If you install the XGA (small fonts) video driver, only part of error

message text may be visible in several of the network dialog boxes.

For example, you may see the following error messages:

 - Access has been

 - The selected server cannot be found on the

 - The specified share name cannot be

 - Invalid

   (instead of "Invalid password")

 - The computer name specified in the network path cannot be

WORKAROUND

==========

To work around this problem, run Windows Setup from the Main group and

install the XGA (large fonts) video driver.

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 as it becomes available.

Additional reference words: 3.11 wfwg wfw


WFWG Setup Leaves Two Sets of Mail and Schedule+ Icons

Article ID: Q106023

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SYMPTOMS

========

When you upgrade from Windows for Workgroups version 3.1 to Windows

for Workgroups version 3.11, you are left with two sets of Microsoft

Mail and Microsoft Schedule+ icons: one set in the Main group and one

set in the Network group.

RESOLUTION

==========

Both sets of icons point to the same programs. You can delete either

set of icons or keep both.

NOTE: Deleting a program icon does not delete the program files.

Additional reference words: 3.11


Windows for Workgroups Hangs at Startup with HP VxD HPVNPD.386

Article ID: Q106024

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SYMPTOMS

========

Windows for Workgroups fails to load if you are using the Hewlett-Packard

(HP) virtual device driver (VxD) HPVNPD.386 with 32-bit file access (VFAT)

enabled.

CAUSE

=====

HPVNPD.386 allows you to print from Windows for Workgroups directly to a

printer connected to the network by an HP JetDirect card. This VxD accepts

data from Print Manager and redirects it over the network using the DLC

protocol.

Unfortunately, when both HPVNPD.386 and VFAT are enabled, Windows for

Workgroups stops responding (hangs) when you attempt to start it.

HPVNPD is calling Exec_VxD_Int. This service does not consistently work

properly under Windows for Workgroups. It works some of the time, but many

times calling Exec_VxD_Int causes the WIN386 event manager to become

confused. Having VFAT installed causes the WIN386 event manager to become

confused every time Exec_VxD_Int is called.

RESOLUTION

==========

To work around this problem, disable VFAT until HP can revise HPVNPD.386.

For more information contact Hewlett-Packard.

Additional reference words: 3.11 jet direct jetdirect


IRQ Option Includes Only IRQs 2-5 for Novell/Anthem NE2000

Article ID: Q106025

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SYMPTOMS

========

When you configure Windows for Workgroups for a Novell/Anthem NE2000

card, you can select an IRQ between 2 and 5 (inclusive)--even though

the newer Novell/Anthem NE2000 cards support IRQs 2-14.

CAUSE

=====

The Windows for Workgroups NETWORKS.INF file contains 2-5 as a valid

IRQ range for Novell/Anthem NE2000 cards to maintain compatibility

with older cards.

RESOLUTION

==========

If you have one of the newer Novell/Anthem cards (or a clone) and you

are using an IRQ in the 6-14 range, do one of the following:

 - Select "NE2000 Compatible" instead of "Novell/Anthem NE2000" when

   configuring Windows for Workgroups.

   -or-

 - Edit the PROTOCOL.INI file and change the IRQ to the correct value.

Additional reference words: 3.11


WFWG Chat Err Msg: No Connection to <Computername>

Article ID: Q106041

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

SYMPTOMS

========

The error message "No connection to <Computername>" (where

<Computername> is the machine you are attempting to use Chat with)

appears when you are using Chat in multiuser mode and attempting to

communicate with a user who has a Windows for Workgroups 3.1 or

Microsoft Windows NT machine.

CAUSE

=====

This error message occurs if you try to add a user to a Chat session

when that user is using an older version of Chat. Neither Windows for

Workgroups nor Windows NT support the multiuser feature of Chat.

NOTE: This error also occurs if a user elects to close Chat before

answering (that is, the user clicks on the "ringing" minimized

phon`and then clicks Close.)

STATUS

======

There is no workaround for this problem.

Additional reference words: Winchat Win Chat


WFWG Err Msg: This Application Was Communicating on...Network

Article ID: Q106042

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

--------------------------------------------------------------------

SYMPTOMS

========

When you exit Microsoft Windows for Workgroups, you may receive the

following error message on a blue screen:

   This application was communicating on the network when you

   terminated it. Although Windows attempted to restore the

   state of the network, you may have problems with network

   communications until you restart your computer.

          Press any key to continue

RESOLUTION

==========

Change the following line in the [Microsoft Mail] section of the MSMAIL.INI

file:

   [Microsoft Mail]

   NetBios=0 (instead of NetBios=1)

NOTE: NetBios=0 disables the automatic new mail notification. You will need

to check for new mail manually.

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 as it becomes available.

MORE INFORMATION

================

Steps to Reproduce Behavior

---------------------------

1. Place the Microsoft Mail icon in the Startup group. Select the icon

   and choose Minimize On Use from the Options menu.

2. Exit Windows and restart.

3. Log on to Windows.

4. After Windows has finished loading, log on to Mail.

5. Do not open Mail, leave it minimized.

6. Exit Windows.

It does not matter how long you wait before exiting. If you leave Mail

minimized, you receive the error message after you exit Windows. If

you open Mail, you should not receive the error message after you exit

Windows.

Additional reference words: 3.11 MSMAIL


Windows for Workgroups 3.11 Hangs with 09-07-93 EXP16ODI.COM

Article ID: Q106043

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SYMPTOMS

========

If Windows for Workgroups version 3.11 is configured to run using ODI

drivers with the Intel Ether Express 16 network adapter, Windows for

Workgroups may stop responding (hang) at the logo screen.

CAUSE

=====

This problem can be caused by using the EXP16ODI.COM driver dated

09-07-93.

RESOLUTION

==========

To correct this problem, update the EXP16ODI.COM driver to a version

more recent than 09-07-93. EXP16ODI.COM can be downloaded from the

Intel bulletin board service (BBS) at (503) 645-6275 or from the Intel

support forum on CompuServe (type "go intelforum" [without the

quotation marks]). For more information, contact Intel Technical

Support at (800) 628-8686.

Additional reference words: 3.11 WFWG EE16


Cannot Attach to NetWare Server After Installing WFWG 3.11

Article ID: Q106053

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SYMPTOMS

========

If the frame type being used on your Novell NetWare server is not set

to Ethernet_802.3, you may not be able to attach to the NetWare server

after you install Windows for Workgroups 3.11. This problem occurs

only if you are running the Novell ODI drivers.

CAUSE

=====

The Windows for Workgroups setup program may change the default frame

type for IPXODI in the NET.CFG file. IPXODI defaults to the first

frame type listed in the Link Driver section of the NET.CFG unless the

frame type is specified on a PROTOCOL line.

RESOLUTION

==========

To correct this problem, change the order of the frame types to

specify the server's frame type first. For example, if the server is

set up to use the Ethernet_802.2 frame type, the NET.CFG file should

look similar to the one below:

Link Driver <MLID>

    Frame Ethernet_802.2

    Frame Ethernet_802.3

    Frame Ethernet_II

    Frame Ethernet_SNAP

Additional reference words: 3.11 wfw wfwg file server not found


SPX-Compatible Applications and Windows for Workgroups 3.11

Article ID: Q106054

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SYMPTOMS

========

If the frame type being used on your Novell NetWare server is not set

to Ethernet_802.3, SPX-compatible applications, such as RConsole, may

not work correctly under Windows for Workgroups 3.11.

For example, if you start the RConsole application, some servers may

be missing from the list of servers to administer. This problem occurs

if the server's frame type is set to Ethernet_II, Ethernet_802.2, or

Ethernet_SNAP.

CAUSE

=====

This problem occurs because the Windows for Workgroups server defaults

to the 802.3 frame type.

RESOLUTION

==========

To correct this problem, choose the Network Setup icon and change the

frame type for the Windows for Workgroups IPX/SPX-compatible protocol

to the same frame type as the NetWare server.

Additional reference words: 3.11 wfw wfwg novel


WFWG Setup May Not Detect Existing 32-Bit Disk Access Drivers

Article ID: Q106082

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SYMPTOMS

========

When you upgrade a Windows 3.1 or Windows for Workgroups 3.1

installation to Windows for Workgroups 3.11, Setup may not detect

existing 32-Bit Disk Access drivers. As a result, Setup may add a

second set of entries for the default 32-Bit Disk Access drivers,

resulting in an error message at startup.

CAUSE

=====

Windows for Workgroups Setup does not check for a path statement when

looking for 32-Bit Disk Access drivers. For example, it would find

DEVICE=CPQWDCTRL.386 but would not find DEVICE=C:\CPQ\CPQWDCTL.386.

RESOLUTION

==========

To work around this problem, edit the SYSTEM.INI file and remove the

following lines from the [386Enh] section:

   device=*wdctrl

   device=*int13

Additional reference words: 3.11 fastdisk


Cannot Run 32-Bit File Access with NE2000 ODI Driver

Article ID: Q106140

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SYMPTOMS

========

When you load the Novell NE2000.COM ODI driver and use 32-bit file

Access with the real mode mapper (RMM.D32), you may experience a five-

second delay when loading applications from the Windows GUI interface.

(This delay does not occur when loading MS-DOS applications from an MS-DOS

virtual machine [VM].) This may also cause Windows for Workgroups to load

more slowly.

CAUSE

=====

This delay occurs because the NE2000.COM driver is causing RMM.D32 to

generate a time-out, and the time-out value is hard coded to be five

seconds. Once the application loads, it then runs as fast as it should

because it has been stored in cache memory (VCACHE.386).

This problem is in the NE2000.COM MLID and only occurs when IPXODI,

which is needed to access NetWare servers, is loaded.

The NE2000 MLIDs known to cause this are from the Novell DOSUP7

client files dated 1/18/93, DOSUP8 client files dated 7/30/93, and

version 1.34 dated 6/3/91.

RESOLUTION

==========

 - Disable 32-Bit File Access.

 - If you are using an NE2000-compatible board, load the MLID that came

   with the network interface card to see if the problem goes away.

MORE INFORMATION

================

Steps to Reproduce Behavior

---------------------------

1. Load the Novell NE2000.COM driver along with IPXODI.COM.

2. Enable 32-Bit File Access on a hard disk drive that requires

   RMM.D32.

Real mode mapper controlled drives include any drive that is not

compatible with 32-Bit Disk Access (for example, SCSI hard drives) or

any drives that have been compressed by a compression program such as

MS-DOS DoubleSpace or Stacker.

Additional reference words: 3.11 wfw wfwg vfat RMM Slow idle scsi

unsupported incompatible hangs locks


Standard Mode Video Grabber May be Deleted from WFWG 3.11

Article ID: Q106233

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

Microsoft Windows for Workgroups version 3.11 does not support

standard mode. However, the standard mode video grabber files from

previous versions of Microsoft Windows or Windows for Workgroups may

remain on the computer after version 3.11 is installed, as these files

are not updated or deleted by Windows for Workgroups Setup.

To increase available disk space, you can delete the standard mode

grabber files from your hard disk. Standard mode grabber files

typically have an extension of .GR2 or .2GR and are located in the

Windows SYSTEM subdirectory.

NOTE: The active enhanced mode video grabber file is identified in the

"386Grabber=" line of the SYSTEM.INI file [Boot] section. This file

must remain in the Windows SYSTEM subdirectory for Windows or Windows

for Workgroups to function properly.

Additional reference words: 286Grabber 3.11 wfwg


Mail Doesn't Remember Password

Article ID: Q106234

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SYMPTOMS

========

You check the "Remember Password" box in Windows for Workgroups Mail,

but it still prompts you for a password when you start Mail.

CAUSE

=====

Workgroups Mail uses the <username>.PWL file to cache (remember) the

mail password. If the network was not started, you have a no-network

installation, or there is no <username>.PWL file, the Workgroups Mail

password cannot be cached.

WORKAROUND

==========

To ensure that the password is remembered regardless of the network

state, add the following entry to your MSMAIL.INI file:

   [Microsoft Mail]

   Password=<password>

This forces Workgroups Mail to bypass the Mail Sign-In; however, this

entry also allows any user to have access to your mail file.

Additional reference words: 3.11 wfwg


File Manager GP Fault on BW-NFS Network

Article ID: Q106235

---------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------

SYMPTOM

=======

You may experience a general protection (GP) fault in Microsoft Windows

for Workgroups File Manager when you access files on a Beame & Whiteside

Network File System (BW-NFS) network drive.

CAUSE

=====

BW-NFS is capable of storing files with names longer than the MS-DOS limit

of 8 characters plus a 3 character extension. You may receive the GP fault

if this long file name support feature is enabled on the BW-NFS server

where BW-NFS is installed as a primary or secondary network for Windows for

Workgroups 3.11.

Note that the name of the file being manipulated does not have to exceed

the MS-DOS file name limits to cause this error.

WORKAROUND

==========

Disable the long file name support on the BW-NFS network server.

Additional reference words: LFN parse longname 3.11 wfwg filename gpf


32-Bit File Access Requires MS-DOS 6.2 DoubleSpace

Article ID: Q106248

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

 - Microsoft MS-DOS operating systems versions 6.0 and 6.2

--------------------------------------------------------------------

SUMMARY

=======

To use 32-bit file access (VFAT) with DoubleSpace, Microsoft Windows

for Workgroups version 3.11 requires that you install MS-DOS 6.2.

MORE INFORMATION

================

Windows for Workgroups 3.11 does not allow 32-bit file access on a

system that has the DBLSPACE.BIN file from MS-DOS 6.0 loaded. MS-DOS

6.2 is required for compatibility with 32-bit file access.

If DBLSPACE.BIN from MS-DOS 6.0 is loaded in memory, the 32-bit file

access option is disabled. If you are using MS-DOS 6.0 and do not have

any compressed drives mounted but DBLSPACE.BIN is loaded in memory,

32-bit file access is still unavailable. You must unload DBLSPACE.BIN

from memory to enable 32-bit file access.

To unload DBLSPACE.BIN, proceed as follows:

1. Remove the system and hidden attributes from the DBLSPACE.INI file

   in the root directory of your startup drive by typing the following

   at the MS-DOS command prompt and then pressing ENTER:

      attrib -s -h -r c:\dblspace.ini

2. Rename the DBLSPACE.INI file by typing the following at the MS-DOS

   command prompt and then pressing ENTER:

      ren c:\dblspace.ini dblspace.ino

3. Restart your computer by pressing CTRL+ALT+DEL.

If you want to use any compressed drives on your system, you must

rename the DBLSPACE.INO file to DBLSPACE.INI and restart your

computer.

For more information on how DBLSPACE.BIN determines if it should

remain in memory, query on the following words in the Microsoft

Knowledge Base:

   dblspace.bin and dblspace.ini and memory

Additional reference words: 3.11 double space dblspace grey greyed

gray grayed


WFWG 3.11 ErrMsg: Error 13: The Data Is Invalid

Article ID: Q106249

---------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------

SYMPTOMS

========

After you type the NET command, you receive the following error

message:

   Error 13: The data is invalid

This error does not occur if you type "net start workstation" or "net

start full" (without the quotation marks).

CAUSE

=====

This problem occurs when the SHARE.EXE program is loaded in the

AUTOEXEC.BAT file.

MORE INFORMATION

================

Steps to Reproduce Problem

--------------------------

1. In your AUTOEXEC.BAT file, add the path to SHARE.EXE. (It does not

   matter where the SHARE command is located in the AUTOEXEC.BAT file.)

2. Restart the computer by pressing CTRL+ALT+DEL.

3. At the MS-DOS command prompt, type "net" (without the quotation

   marks), and then press ENTER.

You are then prompted for your name and password. If there were any

previous connections, they are restored. At this point, the error

message is displayed.

Additional reference words: 3.11 wfwg


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:

 - 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.

 - 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.

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 or Stacker) is used.

   NOTE: VFAT cannot load on a volume compressed with MS-DOS 6.0

   DoubleSpace. This problem was resolved in MS-DOS 6.2.

   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.

Additional reference words: 3.11 fastdisk slow slower slows tshoot


WINVER.EXE Reports Incorrect Version

Article ID: Q106271

-------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

-------------------------------------------------------------------

SUMMARY

========

When WINVER.EXE is executed from within Microsoft Windows for

Workgroups 3.11, it reports "386 Enhanced Mode Windows Version 3.10,"

but when executed from an MS-DOS Prompt or outside of Windows, it

reports "Windows for Workgroups Version 3.11."

MORE INFORMATION

=================

When executed from within Windows, WINVER.EXE does a "GetVersion" API

call, which returns version 3.10 from the kernel. The version that the

kernel reports was not changed for this version of Windows for

Workgroups.

Additional reference words: 3.11 WFWG


NE1500T Network Card Cannot Talk to Network

Article ID: Q106273

------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

------------------------------------------------------------

SYMPTOMS

========

When you exit and then restart Microsoft Windows on a system with an

older AMD NE1500T network interface card (NIC), you cannot

communicate over the network.

CAUSE

=====

This behavior occurs on AM1500T NICs that use the Lance chip. AM1500T

NICs that use the PC-NET chip do not exhibit this behavior.

WORKAROUND

==========

You need to power your system off and then on (cold boot) before

restarting Windows. You should then be able to communicate over the

network.

Additional reference words: 3.11 NE1500T wfw wfwg hangs locks


Most Common Questions and Answers About Microsoft WFW 3.11

Article ID: Q106275

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SUMMARY

=======

The following is the complete text of the Most Common Questions and

Answers about Microsoft Windows for Workgroups that was included as a

single sheet of paper in the shipped product.

MORE INFORMATION

================

Q: What network adapter information do I need to configure Windows for

   Workgroups 3.11?

A: You will need to know the following:

    - Network adapter brand and model

    - Interrupt or IRQ

    - I/O port address

    - Base memory (RAM) address

   For more information about determining these settings, see the section

   "Configuring Your Network Card" in Appendix C "Installing Network

   Hardware," in the Microsoft Workgroup Add-On for Windows User's Guide.

   When Setup is run, it attempts to detect what network adapter (card)

   is installed on the computer, and how it is currently configured. You

   should verify the adapter brand and model as well as the adapter

   settings that Setup detects. If Setup cannot detect a network

   adapter, you should select the correct adapter and settings from the

   list of available drivers. If your adapter is not listed in the

   Network Adapter dialog box, you must obtain the proper NDIS-compliant

   or ODI-compliant driver from your network adapter manufacturer, or

   select a driver that is compatible with your network adapter.  Consult

   your adapter documentation or manufacturer for more information about

   the compatibility of your adapter with other adapter drivers that are

   available in Windows for Workgroups 3.11. Additional or updated

   drivers are also available on the Microsoft Download Service (or MSDL)

   via modem at (206) 936-6735.

   If you are upgrading over Windows for Workgroups 3.1, Setup will

   default to the adapter configuration used in that previous

   installation. Before beginning the upgrade, please check in Control

   Panel, Networks, Adapters, Setup and note the driver name and the

   current adapter settings.

Q: What should I do if my machine hangs or locks up during Setup of

   Windows for Workgroups 3.11?

A: This could mean Setup had difficulty recognizing your hardware, or

   there is a conflict with a TSR or device driver loading in the

   CONFIG.SYS or AUTOEXEC.BAT. You first need to exit Setup by pressing

   the F3 key. If this does not exit Setup, restart the machine. See

   the section "Streamlining Your CONFIG.SYS and AUTOEXEC.BAT Files," in

   Appendix E, "Troubleshooting," in the Microsoft Workgroup Add-On for

   Windows User's Guide, for more information on creating a minimal

   CONFIG.SYS and AUTOEXEC.BAT. You will then need to run Setup again

   and install Windows for Workgroups 3.11 into the same directory.

   Setup will automatically turn off some of its hardware detection

   capability to try to prevent a hardware detection problem from

   occurring again. If you still encounter problems during Setup,

   restart your computer and type the following at the MS-DOS command

   prompt:

      SETUP /I

   and press ENTER. This instructs Setup to disable all of its hardware

   detection capability.

Q: After running Setup successfully, I am unable to start Windows for

   Workgroups 3.11. What could be the problem?

A: If you have completed Setup but cannot start Windows for Workgroups

   3.11, see the section "Windows won't start after a successful Setup,"

   in Appendix E "Troubleshooting," in the Microsoft Workgroup Add-On for

   Windows User's Guide. This section list the most common causes of not

   being able to start Windows for Workgroups 3.11, and how to correct

   these problems.

Q: When I start Windows for Workgroups 3.11, I cannot see other

   computers on the network. What could be the problem?

A: Listed below are some of the most common problems:

    - An IRQ, I/O port address, and/or base memory (RAM) address

      conflict. See Appendix C,  "Installing Network Hardware," in the

      Microsoft Workgroup Add-On for Windows User's Guide for more

      information on configuring your network adapter.  See Appendix D

      "Configuring Network Adapter Drivers, "for information on changing

      the settings in Windows for Workgroups 3.11.

    - A cabling or connector problem.  See Appendix C, "Installing

      Network Hardware," for more information about connecting cables.

      You can also test your network cabling and adapter hardware by

      running the Microsoft Network Diagnostics utility included with

      Windows for Workgroups 3.11.  For more information on using this

      utility, see the section "Using Microsoft Network Diagnostics to

      Troubleshoot Networking Problems," in Appendix E,"Troubleshooting."

Q: How do I configure Windows for Workgroups 3.11 to run with Novell's

   ODI drivers?

A: Windows for Workgroups 3.11 can use the ODI drivers to communicate

   with both Novell Netware servers and other computers using Windows

   for Workgroups 3.11. Before setting up Windows for Workgroups 3.11,

   you must have the ODI drivers loaded and configured properly for your

   network adapter. You will also need to obtain support drivers that

   Novell provides for Netware functionality within Windows operating

   systems. Contact you local Novell reseller or Novell's CompuServe

   forums for information on obtaining these drivers. When installing

   support for Netware connectivity using the ODI drivers, Setup will

   prompt you for these files. If you are upgrading over Windows for

   Workgroups 3.1 or Windows 3.1, and had Netware connectivity enabled,

   these support drivers will already exist in your Windows directory.

   Setup will detect these files and will prompt you to choose to use

   these files, or install the diskette from Novell.  For more

   information on configuring Windows for Workgroups 3.11 with the ODI

   drivers, please refer to the  NETWORKS.WRI file, located in your

   Windows for Workgroups 3.11 directory.  This file can be viewed with

   the Write application in Windows for Workgroups 3.11

Q: What is 32-Bit File Access and how can I get it running on my

   computer?

A: 32-BIT FILE ACCESS provides a faster way to read and write to the

   disk cache in Windows for Workgroups 3.11 than SMARTDrive can provide.

   It provides a much higher disk access performance boost on compatible

   hard drive controllers when running Windows for Workgroups 3.11 by

   utilizing a 32-bit cache as opposed to SMARTDrive's 16-bit cache.

   However, SMARTDrive is still used for caching floppy drives with

   Windows for Workgroups 3.11.

   By default, 32-BIT FILE ACCESS is NOT enabled.  For more information on

   activating this disk performance enhancement utility,  see the section

   "Improving Performance," Chapter 8 of the Microsoft Workgroup Add-On

   for Windows User's Guide.

Q: What are the PROTOCOL.CLN, SYSTEM.CLN, and WIN.CLN files in my

   Windows for Workgroups 3.11 directory?

A: PLEASE NOTE: These files should only be used if Windows for

   Workgroups 3.11 worked properly after its initial install.

   The files listed above are created by Setup after it installs Windows

   for Workgroups 3.11 onto your harddrive. They are to be used if, for

   some reason, Windows for Workgroups 3.11 cannot start, or is not

   functioning properly after a change was made to one of three files:

   PROTOCOL.INI, SYSTEM.INI, and WIN.INI. To restore these files to

   their original settings, you need to first make a backup copy onto a

   floppy diskette of your PROTOCOL.INI, SYSTEM.INI, and WIN.INI files

   from your directory. Next, copy the PROTOCOL.CLN, SYSTEM.CLN, and

   WIN.CLN files in your Windows for Workgroups 3.11 directory to

   PROTOCOL.INI, SYSTEM.INI, and WIN.INI respectively. This will

   restore your files to their original settings.

Q: I have a Hercules Monochrome, CGA,  or EGA video adapter, but this

   driver is not available. Can I run Windows for Workgroups 3.11 with

   this type of display adapter?

A: Yes. If you had a previous version of Windows 3.1 or Windows for

   Workgroups 3.1, and had one of these video drivers installed, Setup

   will recognized this and will keep this driver for use in Windows for

   Workgroups 3.11. If this is a new install, you can obtain these

   drivers by downloading them from the Microsoft Download Service (or

   MSDL) via modem at (206) 936-6735.

Q: I have a computer that I only use for MS-DOS-based applications. Can

   I still have access to my Windows for Workgroups 3.11 network from

   MS-DOS on these computers?

A: Yes. You will need to purchase the Microsoft Workgroup Add-On for

   MS-DOS package from Microsoft, and install a compatible network

   adapter on the computer. This product allows you to connect to

   Windows for Workgroups 3.11 computers and printers, and also allows

   you to share your files with other computers on the network from

   MS-DOS. For more information about this product, please contact

   Microsoft Customer Service at (800) 426-9400.

Q: In the Network Drivers dialog box, it lists "IPX/SPX Compatible

   Transport," or "IPX/SPX Compatible Transport with NETBIOS" as a

   protocol. Why is this installed and how is it used?

A: In the previous version, Windows for Workgroups 3.1, a Windows for

   Workgroups computer communicated with other Windows for Workgroups

   computers using the NetBEUI protocol by default. With Windows for

   Workgroups 3.11, a second protocol, either IPX/SPX Compatible

   Transport or IPX/SPX Compatible Transport with NETBIOS, is installed

   along with NetBEUI, if the computer has six megabytes or more of RAM.

   This allows Windows for Workgroups 3.11 to communicate with other

   computers that use either the NetBEUI protocol or IPX/SPX Compatible

   Transport. The benefit of the IPX/SPX Compatible Transport and the

   IPX/SPX Compatible Transport with NETBIOS is that either of these

   protocols can communicate across a router, whereas the NetBEUI

   protocol cannot. Novell Netware servers can act as routers between

   two different Windows for Workgroups 3.11 networks.

Additional reference words: 3.11 Q&A


WFWG Err Msg: The 32-Bit File System is Incompatible...SUBST

Article ID: Q106276

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SYMPTOMS

========

If you enable 32-bit file access and you use the MS-DOS substitute

command, SUBST, you will receive the following error message on a blue

screen when you start Windows for Workgroups:

   The 32-bit file system is incompatible with the SUBST

   utility. To use 32-bit file access, do not use the SUBST

   utility before starting Windows for Workgroups.

   Press any key to continue

CAUSE

=====

The SUBST utility from MS-DOS allows you to substitute drive letters

for directory names. This method of redirection is incompatible with

32-bit file access. When IFSMGR.386 detects SUBST, it prevents 32-bit

file access from loading to protect against data loss.

IMPORTANT: It is important to note that 32-bit file access is disabled

for all drives, not just the substituted drive.

RESOLUTION

==========

This error message is by design.

If you use 32-bit file access, you cannot use the SUBST command.

To use the SUBST command, you must first disable 32-bit file access.

Additional reference words: 3.11 wfw wfwg vfat 32 bit


The IPX/SPX Compatible Protocol Supports Only One Network Card

Article ID: Q106364

------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

------------------------------------------------------------

When you run Windows for Workgroups 3.11 and are using two network

cards, the IPX/SPX compatible protocol can be used on only one of the

network cards. This is a limitation of the IPX protocol that has been

carried over into Windows for Workgroups. All implementations of the

IPX protocol have this same limitation.

Additional reference words: 3.11 WFW NIC MAC driver netcards


File Manager Doesn't Save Positions of Minimized Icons

Article ID: Q106365

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SYMPTOMS

========

The Microsoft Windows for Workgroups 3.11 File Manager does not save

the position of minimized icons.

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 as it becomes available.

MORE INFORMATION

================

If you minimize the directory tree structure in File Manager, move the icon

somewhere other than the lower-left corner, and then exit File Manager

while Save Settings On Exit is enabled, the minimized icon moves to the

lower-left corner.

Microsoft Windows 3.1 and Microsoft Windows for Workgroups 3.1 correctly

save the positions of icons in File Manager.

Additional reference words: 3.10 3.1 3.11 wfw wfwg won't can't moves

relocate relocated default reverts


WFWG Hangs at Startup with Future Domain 32-Bit Disk Access

Article ID: Q106366

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SYMPTOMS

========

Versions earlier than 1.02 of Future Domain's 32-bit disk access

drivers may cause Windows for Workgroups to stop responding (hang) at

startup.

RESOLUTION

==========

Disable Future Domain's 32-bit disk drivers until you obtain an

updated driver(s).

MORE INFORMATION

================

For more information on obtaining updated 32-bit disk access drivers

for Future Domain controllers, contact Future Domain at one of the

following numbers:

   Software Upgrade Order Line: (800) 879-7599

   Technical Support Hotline:   (714) 253-0440

   Fax Hotline:                 (714) 253-0429

The products included here are manufactured by Future Domain, a vendor

independent of Microsoft; we make no warranty, implied or otherwise,

regarding these products' performance or reliability.

Additional reference words: 3.10 3.11 wfw wfwg v18fcamd.386 int13.386

fdscsi.386 hang lock locks logo screen stops responding


WinPopup Message Incorrectly States Message Was Sent

Article ID: Q106367

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SYMPTOMS

========

If you try to send a WinPopup message to a user or computer that does not

exist on the network or to yourself, you receive the following error

message:

   An error occurred while sending the message. The message alias cannot

   be found on the local-area network.

However, if you send a WinPopup message to a workgroup that is not on the

network, you do not receive an error message; instead, you are informed

that the "message was successfully sent" even though this is not the case.

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 as it becomes available.

MORE INFORMATION

================

Steps to Reproduce Problem

--------------------------

1. Open WinPopup.

2. From the Messages menu, choose Send.

3. In the To box, select Workgroup.

4. In the text box, insert an invalid workgroup name (for example,

   "INVALID").

   NOTE: The Browse button is not accessible for workgroup names; it is

   available only for user and computer names.

5. Choose OK.

The following message appears even though the workgroup INVALID does

not exist:

   The message was successfully sent.

Additional reference words: 3.11 wfw wfwg error message misleading wrong

incorrect confusing nonexistent grey gray greyed grayed


Cursor Remains an Hourglass When Loading Schedule+

Article ID: Q106418

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SYMPTOMS

========

If you force Workgroups Schedule+ to automatically load by placing it

in the Startup group or on the LOAD= line of your WIN.INI file, the

cursor may remain as an hourglass until you move the mouse.

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.

WORKAROUND

==========

This situation does not occur if you start Schedule+ by placing it on

the RUN= line of your WIN.INI file. At this time, the only workarounds

available are to use the RUN= line, move the mouse to restore the

pointer, or not automatically load Workgroups Schedule+.

Additional reference words: 3.11 frozen hang


SmartVu Disabled on Dell Computers with VFAT

Article ID: Q106436

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SYMPTOMS

========

The SmartVu display on Dell computers is bypassed if the virtual file

allocation table (VFAT) is enabled using Windows for Workgroups 3.11.

CAUSE

=====

This occurs because the system BIOS is bypassed when reading and

writing to the hard disk drive if VFAT is enabled. The most recently

accessed cylinder (prior to the loading of VFAT) on the hard disk

drive is displayed in the viewing window.

Additional reference words: 3.11 DE ME 420 425 433 466 333


The F1 Key in Chat and NetWatcher May Not Open Help

Article ID: Q106437

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

---------------------------------------------------------------------

SUMMARY

=======

In most Windows-based applications, you can use the F1 key to open

Help; however, this is not always the case with Chat and NetWatcher.

MORE INFORMATION

================

In Windows for Workgroups 3.1, the F1 key does not open Help for Chat

or NetWatcher.

In Windows for Workgroups 3.11, the F1 key does not open Help for

NetWatcher. It does, however, open Help for Chat.

The only workaround is to open Help using the Help menu within the

application.

Additional reference words: 3.10 3.1 3.11 wfw wfwg


Windows for Workgroups 3.11: How to Disable Printer Alerts

Article ID: Q106438

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SUMMARY

=======

When you share a printer on a Windows for Workgroups 3.11 machine, the

default configuration enables sending printer alerts through Print

Manager. To disable printer alerts, add the following entry to the

[Network] section of the SYSTEM.INI file.

   SendPrintMessages=no

NOTE: Disabling WinPopup does not disable printer alerts since these

messages are sent through Print Manager. Using the SYSTEM.INI entry

above is the only method to disable printer alerts.

Additional reference words: 3.11 how to howto


Extended Characters May Be Displayed Incorrectly in WinPopup

Article ID: Q106439

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

--------------------------------------------------------------------

SYMPTOMS

========

When you type a message in WinPopup, many extended characters do not

display correctly in the message area. For example, typing the

extended character ALT+0149 normally displays a bullet, but in

WinPopUp, a thin block is displayed.

CAUSE

=====

WinPopup uses a predefined original equipment manufacturer (OEM)

character set that is limited to specific characters and cannot be

modified.

Additional reference words: 3.11 language alt font type face


WG0949: Windows for Workgroups 3.11 Setup Information

Article ID: Q106511

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:

 - 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 WG0949

==================

======================================================================

  Microsoft(R) Product Support Services Application Note (Text File)

                       WG0949: SETUP INFORMATION

======================================================================

                                                  Revision Date: 11/93

                                                      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.)

      DRIVERS AND FILES SHIPPED WITH WINDOWS FOR WORKGROUPS 3.11

      ==========================================================

Setup does not delete drivers that were installed with Windows 3.1 but

were not shipped with Windows for Workgroups. The following table

shows the drivers and files that do ship with Windows 3.1 and/or

Windows for Workgroups.

Driver or file               Windows 3.1    Windows for Workgroups 3.11

-----------------------------------------------------------------------

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

and TBMI2.COM file                          an 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 server)   No          Yes

CLIPBRD.EXE (ClipBook Viewer)   No          Yes

WINCHAT.EXE (Chat)              No          Yes

WINMETER.EXE (WinMeter)         No          Yes

MSMAIL.EXE (Mail)               No          Yes

SCHDPLUS.EXE (Schedule)         No          Yes

NETWATCH.EXE (NetWatcher)       No          Yes

MSHEARTS.EXE (Hearts)           No          Yes

CALENDAR.EXE (Calendar)         Yes         No

SSMYST.SCR (Mystify             Yes         No

screen saver)

ARCHES.BMP (Arches wallpaper)   Yes         No

CHITZ.BMP (Chitz wallpaper)     Yes         No

FLOCK.BMP (Flock wallpaper)     Yes         No

MARBLE.BMP (Marble wallpaper)   Yes         No

TARTAN.BMP (Tartan wallpaper)   Yes         No

CHORD.WAV (Chord sound)         Yes         No

TADA.WAV (Trumpet sound)        Yes         No

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

           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

===============================

 - 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.

 - 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.

Additional reference words: 3.11


Windows for Workgroups 3.11: Using the Generic IPXODI Driver

Article ID: Q106712

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SUMMARY

=======

In Windows for Workgroups 3.11, if you install Novell NetWare as a

secondary network using Novell's ODI configuration, you may need to

use one of the generic IPXODI support network adapter drivers if your

adapter has a working ODI driver but does not have a supported NDIS

driver. In such cases, you must manually modify the PROTOCOL.INI and

NET.CFG files to match the ODI MLID that is being used.

MORE INFORMATION

================

Windows for Workgroups 3.11 can use a Novell-certified ODI driver to

communicate with the network adapter. To use the ODI driver with

Windows for Workgroups 3.11, select the network adapter from the list

of adapters in the Network Drivers dialog box of Network Setup.

To install the IPXODI support driver:

1. Start Windows for Workgroups 3.11 and choose the Network Setup icon

   in the Network group.

2. Choose Networks and select the Install Microsoft Windows Network

   option button (if it is not already selected).

3. Select the Other option button, and select the version of NetWare

   in use (either "Workstation Shell 3.X" or "Workstation Shell 4.0 And

   Above") from the list of additional networks. Choose OK.

4. Choose Drivers and then choose Add Adapters.

5. The list of adapters provides three generic drivers:

      IPXODI Support Driver (ArcNet)

      IPXODI Support Driver (Ethernet)

      IPXODI Support Driver (Token Ring)

   Select the driver that matches your network topology and choose OK.

6. Choose Close to exit the Drivers dialog box. Choose Sharing, ensure

   those options are set correctly, and then choose OK.

7. Setup may then prompt you for Network Names. Once you have entered

   the names, Setup copies the files needed and modifies the

   configuration files, including NET.CFG and PROTOCOL.INI, as necessary.

The next step is to manually edit the PROTOCOL.INI file in the Windows

for Workgroups 3.11 directory and the NET.CFG file.

NOTE: The lines you need to edit depend on the number of protocols

that you installed for the IPXODI support driver.

To modify the PROTOCOL.INI file:

1. Open the PROTOCOL.INI file found in the Windows for Workgroups 3.11

   directory using any ASCII editor.

2. Search the PROTOCOL.INI file for the following entries:

      BINDINGS=<XXXX>

      -and-

      [Link Driver <XXXX>]

   NOTE: You may have more than one BINDINGS= line in the PROTOCOL.INI

   file; you must modify all binding lines that contain <XXXX>.

3. Replace <XXXX> with the appropriate MLID name for your ODI driver.

   (Normally, the MLID name is the same as that of the ODI driver.)

   For example, if you are using an Intel EtherExpress 16 card and

   loading the ODI driver EXP16ODI.COM in your AUTOEXEC.BAT file, the

   MLID name is EXP16ODI. Replace any <XXXX> lines in the PROTOCOL.INI

   file with EXP16ODI and then save the file. Refer to the AUTOEXEC.BAT

   file or to the batch file that loads the Novell NetWare ODI drivers

   for the name of the ODI driver. This name (excluding the extension)

   should be the correct MLID name.

4. Edit the NET.CFG file being used by the ODI drivers. This file is

   normally located in the same directory from which the ODI files load.

   If you cannot find NET.CFG, exit Windows and run Microsoft Diagnostics

   (MSD) from the Windows for Workgroups 3.11 directory to find the

   location of NET.CFG. In MSD, choose Network. If the NetWare drivers

   are loaded, there is an entry that reads "PATH to NET.CFG=."

5. In the NET.CFG file, Setup adds the following line:

      LINK DRIVER <XXXX>

   Replace the <XXXX> with the correct MLID name for your ODI driver.

6. After you save the PROTOCOL.INI and NET.CFG files, reboot your

   computer. If the correct MLID name is entered, you should have access

   to the NetWare server(s) at MS-DOS and access to both NetWare servers

   and Windows for Workgroups servers in Windows.

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.

Additional reference words: 3.11 wfw wfwg 3rdparty


Incorrect I/O Address Detected on SMC Elite+ Network Adapter

Article ID: Q106713

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SYMPTOMS

========

If you are upgrading to Windows for Workgroups 3.11 on a system that

is running Microsoft Workgroup Connections 1.0 and has an SMC Elite+

network adapter, the correct I/O address may not be detected for the

SMC adapter.

If the SMC Elite+ network adapter is not configured to use the default

0x280h I/O address, you must select the correct setting when Setup

prompts you for confirmation.

CAUSE

=====

To determine the I/O address for the network adapter, Windows for

Workgroups 3.11 Setup examines the existing PROTOCOL.INI file in use

by Workgroup Connections 1.0. If the network adapter is an SMC Elite+,

the I/O address is not found in the PROTOCOL.INI file. (The SMC Elite+

NDIS2 driver for use with Workgroup Connections 1.0 does not require

that an I/O address be stored in the PROTOCOL.INI file.)

Since an I/O address is not found in the PROTOCOL.INI file, the

default I/O address of the SMC Elite+ network adapter is selected and

you are given an opportunity to confirm this selection.

Additional reference words: 3.11


NET Command Returns Error in VM While Network Setup Is Active

Article ID: Q106714

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SUMMARY

=======

When you are running Windows for Workgroups 3.11, the NET command is

unavailable in MS-DOS virtual machines (VMs) if Network Setup is

active.

MORE INFORMATION

================

When you run any NET command (other than NET/?) at the MS-DOS command

prompt, the following error message is displayed:

   Error 32: The process cannot access the file because it is being

   used by another process.

   An error occurred accessing the security-settings file.

To run NET commands in an MS-DOS VM, first exit the Network Setup

program in Windows for Workgroups.

Additional reference words: 3.11


File Server Hangs Network After Accessing Shared CD-ROM

Article ID: Q107056

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

---------------------------------------------------------------------

SYMPTOMS

========

When a workstation uses File Manager to examine the directory tree of

a CD-ROM mounted on a Windows for Workgroups file server, the Windows

for Workgroups network may stop responding (hang) until the file

server machine is rebooted.

This problem does not occur if you access the CD-ROM from the machine

sharing the disk. Also, this problem may not occur if you are

accessing the shared CD-ROM over the network after the local machine

has read the directory structure.

CAUSE

=====

This problem occurs with specific CD-ROM directory structures. For

example, CD-ROMs included with the following software packages cause

this problem:

   CorelDRAW 3.0b

   SIMTEL20 Collection

   CICA Windows Collection

STATUS

======

Microsoft has confirmed this to be a problem in Microsoft CD-ROM

Extensions (MSCDEX.EXE) versions 2.21 and 2.22. We are researching

this problem and will post new information here in the Microsoft

Knowledge Base as it becomes available.

Additional reference words: 3.11 compact disc


OEM Modems May Be Supported by Windows for Workgroups

Article ID: Q107058

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

Many original equipment manufacturer (OEM) modem vendors sell modems

that are licensed from other vendors. For example, some Gateway

internal modems are actually U.S. Robotics Sportster modems.

If you plan to use an unsupported modem with Windows for Workgroups

Remote Access, you should contact your OEM and determine the true modem

brand and model. Then, choose the actual modem type when you install

Remote Access.

Additional reference words: 3.11 RAS


RAS Returns Poorly Formatted or Unreadable Error Messages

Article ID: Q107059

------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

------------------------------------------------------------------

SYMPTOMS

========

When you use Remote Access with an unsupported modem, you may

encounter poorly formatted or unreadable error messages.

CAUSE

=====

When modems return errors, they usually return unformatted text (which

can vary in length). Remote Access simply displays this text. If the

modem is not on the Windows for Workgroups hardware compatibility

list, Microsoft cannot guarantee it will return usable error messages.

For example, the Dallas FAX modem returns error messages that are

unreadable when displayed by Remote Access.

Additional reference words: 3.11 Remote-Access Services server RAS


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 and 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 may 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 Workgroup 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 Workgroup 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. Select the correct hardware options for your system. (These options

    are blank by default.)

 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=<Boolean>

         device=*int13

         device=*wdctrl

      NOTE: To enable 32-bit disk access, replace <Boolean> with "True"

      (without the quotation marks). If you do not want 32-bit disk access

      enabled, replace <Boolean> with "False" (without the quotation

      marks).

      For more information on 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. 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.

 9. In the Main group, choose Control Panel and then choose the Network

    icon.

10. Add the workgroup and computer names.

11. Choose the Adapters button.

12. Add the network interface card (NIC).

    NOTE: You may need to first remove, 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.

Additional reference words: 3.10 3.11 WIN31


Windows for Workgroups 3.11 Retail Package Options

Article ID: Q107132

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

----------------------------------------------------------------------

SUMMARY

=======

This article describes the two retail packages available for Windows

for Workgroups version 3.11:

 - Windows for Workgroups 3.11

 - Workgroup Add-On for Windows

MORE INFORMATION

================

Windows for Workgroups

----------------------

This package contains the complete software package for machines that

do not have Microsoft Windows operating system version 3.0 or 3.1. It

contains all the Microsoft Windows for Workgroups software, including

Windows 3.1 functionality, file sharing, printer sharing, network

dynamic data exchange (DDE), Microsoft Mail, Microsoft Schedule+,

Microsoft At Work PC Fax, Remote Access Services, 32-bit file and disk

access, and advanced security. This package does not include any

hardware.

Workgroup Add-On for Windows

----------------------------

This package is for machines that already have Microsoft Windows

version 3.1 or Microsoft Windows for Workgroups version 3.1 installed.

It upgrades Windows 3.1 or Windows for Workgroups 3.1 by adding those

files required for the new features of Windows for Workgroups 3.11.

NOTE: The Add-On package disables standard mode; the WIN.COM file was

rewritten to turn off this functionality.

This package does not include any hardware.

Additional reference words: 3.10 3.11 WFW WFWG stock keeping units SKU

point-to-point


WFWG: Scrambled Display Using Generic Super VGA Driver

Article ID: Q107134

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

--------------------------------------------------------------------

SYMPTOMS

========

Using the generic Super VGA 800 x 600 resolution (or higher) 256-color

video driver in Windows for Workgroups version 3.11 may produce an

erratic or scrambled screen display.

CAUSE

=====

This problem is caused by using a video adapter with 512 kilobytes of

video memory.

WORKAROUND

==========

To work around this problem, use the generic Super VGA 640 x 480

256-color video driver.

Additional reference words: 3.11 screen loop looping rollover


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   PM144FXMT                    1   E

Practical Peripheral   PM144FXSA                    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                2   I

U.S. Robotics          Sportster 144                2   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

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.

Additional reference words: 3.11 AWFAX MODEMS works passed failed

faxmodems hardware compatibility list hcl wfwg SatisFAXion


Network Card Drivers That Must Load in Conventional Memory

Article ID: Q107347

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SUMMARY

=======

To operate correctly, certain network card drivers require that you

load them into conventional memory. These cards all use bus-mastering

direct memory access (DMA) for transferring data, which prevents the

drivers from being loaded into the upper memory blocks (UMBs).

Below is a list of these network adapters and the corresponding driver

names.

   Network card                                Driver name

   -------------------------------------------------------

   Advanced Micro Devices AM2100/AM1500T        AM2100.DOS

   Exos 105                                     AM2100.DOS

   Novell/Anthem NE1500T                        AM2100.DOS

   Novell/Anthem NE2100                         AM2100.DOS

   Zenith Data Systems Z-Note                   I82593.DOS

For testing, load the network drivers into conventional memory by

replacing the NET START line in the AUTOEXEC.BAT with the following

line:

   net start /nohi

Additional reference words: 3.11


Windows for Workgroups: 32-Bit File Access Is Slow with MSIPX

Article ID: Q107372

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

--------------------------------------------------------------------

SYMPTOMS

========

If you are running Windows for Workgroups 3.11 with MSIPX, you may

experience a five-second delay when you start applications from the

Windows graphical user interface (GUI). This delay occurs only if you

have 32-bit file access enabled on a hard disk drive controlled by the

real mode mapper (RMM.D32). In this situation, Windows may also load more

slowly. This delay does not occur when you start MS-DOS applications from

an MS-DOS virtual machine (VM).

Real mode mapper controlled drives include drives that are incompatible

with 32-bit disk access and drives that have been  compressed with a disk-

compression program, such as MS-DOS 6.2 DoubleSpace or STAC Electronics'

Stacker. (MS-DOS 6.0 DoubleSpace is incompatible with 32-bit file access).

WORKAROUND

==========

To work around this problem, do one of the following:

 - Upgrade MSIPX to Novell ODI drivers. This is recommended for Windows

   for Workgroups 3.11/Novell NetWare users. ODI should provide faster

   access to NetWare servers and improve Windows for Workgroups

   performance.

   -or-

 - Disable 32-bit file access.

For more information, please query on the following words in the

Microsoft Knowledge Base:

   32-bit file access and ne2000 and odi

Additional reference words: 3.11 wfw wfwg hangs locks hesitates

double-click start launch


WFWG 3.11: Hardware Compatibility List - Computers

Article ID: Q107373

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

--------------------------------------------------------------------

SUMMARY

=======

This article contains a list of computer systems that have been tested

and found to be compatible with Windows for Workgroups 3.11. Microsoft

will add additional information to this article as it becomes

available.

MORE INFORMATION

================

System Name

-----------

Acer Altos 7000/FT66TY

Acer Power 425s

Acer Power 433

Acer Power 433s

Acer Power 433V

Acer Power 450d

Acer Power 466d

Acer/Altos 7000

ACTech ACTion EISA 486DX-50

ACTech ACTion EISA 486DX/2-66

ACTech ACTion ISA 486DX-33

ACTech ACTion ISA 486DX-50

ACTech ACTion ISA 486DX/2-50

ACTech ACTion ISA 486DX/2-66

ACTech ACTion ISA 486SX-25

ACTech ACTion VLB 486DX-33

ACTech ACTion VLB 486DX/2-50

ACTech ACTion VLB 486DX2-66

ACTech ACTion VLB 486DX50

ACTech ACTion VLB 486SX-25

ADI MT486 DX

ADS 486 VESA Upgradeable

Apricot LS Pro 386SX-33

Apricot XEN LS II

Apricot XEN LS II 486SX/33

Apricot XEN PC 486DX/2-66

ASEM DS486II

ASEM ECOPC

AST Bravo LC 4/33s

AST Bravo LC2 4/33

AST Bravo LC2 4/50d

AST Bravo LC2 4/66d

AST Bravo LC2 425s

AST Bravo LP 4/25s

AST Bravo LP 4/33

AST Bravo LP 4/66d

AST Premmia MTE 4/33

AST Premmia MTE 4/66d

Chaplet NBDE

Comapq ProLinea MT CDS (486DX2/66MHz)

Compaq Deskpro 3/25i

Compaq Deskpro 386/25M

Compaq Deskpro 386/33M

Compaq Deskpro 4/25is

Compaq Deskpro 4/33i

Compaq Deskpro 4/33is

Compaq Deskpro 4/66i

Compaq Deskpro 486/33M

Compaq Deskpro 486s/16M

Compaq Deskpro 486s/25M

Compaq Deskpro 486s/33M

Compaq Deskpro 5/60M

Compaq Deskpro 5/66M

Compaq Deskpro 50M

Compaq Deskpro 66M

Compaq Presario 425

Compaq Presario 625

Compaq Presario 633

Compaq Presario 833 CDS

Compaq Presario 850

Compaq Presario 850 CDS

Compaq Presario 866

Compaq ProLinea 3/25zs

Compaq ProLinea 4/25s

Compaq ProLinea 4/33

Compaq ProLinea 4/50

Compaq ProLinea 4/66

Compaq ProLinea CDS

Compaq ProLinea MT 4/33s

Compaq ProLinea MT 4/50

Compaq ProLinea MT 4/66

Compaq ProLinea MT CDS (486SX/33MHz)

Computer Sales Pro 486DX2\66

Computer Sales Pro 486DX33

Computer Sales Pro 486DX50

Computer Sales Pro 486SX25

Daewoo CPC 2600 Desktop

Daewoo CPC 2700U Desktop

Daewoo CPC 2900 Mini Tower

Daewoo Green PC 2500

DEC PC 433dx MT

DECpc 325SL/SLC

DECpc 333sx LP

DECpc 425SL/SLC

DECpc 425sx LP

DECpc 433 ST

DECpc 433dx LP

DECpc 433dx MTE

DECpc 433sx LP

DECpc 450 ST

DECpc 450d2 LP

DECpc 450d2 MT

DECpc 452 ST

DECpc 466 ST

DECpc 466d2 MT

DECpc 466d2 MTE

DECpc 560 ST

DECpc LPv 425sx

DECpc LPv 433dx

DECpc LPv 433sx

DECpc LPv 450d2

DECpc LPv 466d2

DECpc LPv 466d2 LP

DECpc LPx 433dx

DECpc LPx 433dx

DECpc LPx 433sx

DECpc LPx 433sx

DECpc LPx 450d2

DECpc LPx 466d2

Eagle Rohan

Eagle Test

Expo Tech 321E Notebook

Expo Tech 322 Notebook

Expo Tech 386SX/3 Desktop

Expo Tech 386SX/3 Ultra Slim

Expo Tech 486 DX/2 Desktop (w/LBVGA)

Expo Tech 486DX/2 Desktop (w/VLBus)

Expo Tech 486DX/3 Desktop

Expo Tech 486DX/3 Desktop (w/LBVGA)

Expo Tech 486DX/3 Desktop (w/VLBus)

Expo Tech 486DX/3 Tower

Expo Tech 486DX/3 Ultra SLim

Expo Tech 486DX2/4 Desktop

Expo Tech 486DX2/4 Desktop (w/LBVGA)

Expo Tech 486DX2/4 Tower

Expo Tech 486DX2/4 Tower (w/VLBus)

Expo Tech 486DX2/6 Desktop

Expo Tech 486DX2/6 Tower

Expo Tech 486DX2/6 Tower (w/VLBus)

Expo Tech 486DX2/66 Deskto (w/VLBUS)

Expo Tech 486SX/3 Deskto p(w/LBVGA)

Expo Tech 486SX/3 Desktop (w/VLBus)

Expo Tech 486SX/3 Tower

Expo Tech 486SX/3 Tower (w/VLBus)

Expo Tech 486SX/3 Ultra Slim (w/LVBGA)

Expo Tech 486SX/4 Deskto (w/VLBus)

Expo Tech 486SX/4 Desktop

Expo Tech 486SX/4 Desktop (w/LBVGA)

Expo Tech 486SX/4 Tower

Expo Tech 486SX/4 Tower (w/VLBus)

Expo Tech 486SX/4 Ultra Slim(w/LBVGA)

Expo Tech LT 421 Notebook

First International Leo 486-JA

First International Leo-486 KVD

First International Leo-VAC-V

FMC LAN MACHINE

Fountain Tech UMC 486 DX2-66

Fountain Technology 486DX2/50

Fountain Technology 486DX2/66

Fountain Technology 486DX33

Fountain Technology 486DX50

Fountain Technology 486SX25

Fujitsu S-4066

Fujitsu S-366

Fujitsu S-466

GoldStar GS 425SXE

GoldStar GS 486ID66C/66Mhz

GoldStar GS466DXE

GoldStar GS466ID 25C 25Mhz

ICL C4/33B

ICL DL/33

Intercomp DIGIT 486SLC/25

Intercomp Friends 486DX/33

Intercomp Master 486DX2/66

Intercomp Planet 486DX/33

Intercomp Planet II 486 DX2/66

Intercomp Target 486DX/50

IPC Dynasty HE 486DX-33C

IPC Dynasty HE 486DX2-50C

IPC Dynasty HE 486DX2-66c

IPC Dynasty HE 486SX-25C

IPC Dynasty LE 486DX-33C

IPC Dynasty LE 486DX2-50C

IPC Dynasty LE 486DX2-66C

IPC Dynasty SE 486DX-33C

IPC Dynasty SE 486DX2-50C

IPC Dynasty SE 486DX2-66C

IPC Dynasty SE 486SX-25C

IPC Dynsty LE 486SX-25C

KT 486/33 VL-BUS

KT 486/33 VL-BUS/3S

KT 486/50 VL-BUS

Micro Byte Lyrebird 455

Mind 386DX40 ISA

Mind 486 DX-33E

Mind 486 SX-25

Mind 486DX-266 EISA

Mind 486DX250

Mind 486DX266

Mind 486DX50

Mind 486DX50 EISA

Mind 486SX25

NCR 3333-B22

Olivetti M3-30/P

Olivetti M300-15 SX 25 Mhz

Olivetti M300-30

Olivetti M4-40

Olivetti M4-46

Olivetti M4-60

Olivetti M4-64 DX33

Olivetti M4-65

Olivetti M4-82 (KPC 450)

Olivetti M400-60

Olivetti M480-10 486SX25

Olivetti M480-20AT

Olivetti M6-420

Olivetti M6-450 DX2-50Mhz

Olivetti M6-460

Olivetti M6-520

Olivetti M6-540

Olivetti M6-560

Olivetti M6-620 Pentium

Packard Bell  486DX/33

Packard Bell 1110

Packard Bell 1120

Packard Bell 1150(+)

Packard Bell 2066 Minitower (*)

Packard Bell 400DX-33

Packard Bell 400DX-33

Packard Bell 400DX2/50

Packard Bell 400DX2/66

Packard Bell 400SX-25

Packard Bell 400T

Packard Bell 410SX/25

Packard Bell 410SX/33

Packard Bell 420DX/33

Packard Bell 420DX2/66

Packard Bell 420SX/25

Packard Bell 420SX/33

Packard Bell 470

Packard Bell 486CDM(+)

Packard Bell 486SX/25

Packard Bell 486T50

Packard Bell 495

Packard Bell 515E

Packard Bell 525E

Packard Bell 545E

Packard Bell 550(*)

Packard Bell 560

Packard Bell 565E

Packard Bell Axcel 1033

Packard Bell Axcel 105

Packard Bell Axcel 1066(*)

Packard Bell Axcel 130

Packard Bell Axcel 2005(+)

Packard Bell Axcel 2015(+)

Packard Bell Axcel 2033 Minitower (*)

Packard Bell Axcel 205(8)

Packard Bell Axcel 230

Packard Bell Axcel 405

Packard Bell Axcel 405(*)

Packard Bell Axcel 405H

Packard Bell Axcel 430(*)

Packard Bell Axcel 460

Packard Bell Axcel 486A66(*)

Packard Bell Axcel 550

Packard Bell Axcel 550MT/J

Packard Bell Axcel 850(*)

Packard Bell Axcel Minitower (*)

Packard Bell Executive 486/33G

Packard Bell Executive 486/33J

Packard Bell Executive 486SX-EC

Packard Bell Force 1066(*)

Packard Bell Force 107

Packard Bell Force 110

Packard Bell Force 1135

Packard Bell Force 1137

Packard Bell Force 117

Packard Bell Force 200

Packard Bell Force 2010(+)

Packard Bell Force 2020(+)

Packard Bell Force 2040 Minitower (+)

Packard Bell Force 2233 Minitower

Packard Bell Force 2376

Packard Bell Force 2376F(*)

Packard Bell Force 2386 Minitower (*)

Packard Bell Force 250(*)

Packard Bell Force 405

Packard Bell Force 425

Packard Bell Force 486/33G

Packard Bell Force 486/33J

Packard Bell Force 486/33JW

Packard Bell Force 486CDM-1/TV(+)

Packard Bell Force 486MT50J

Packard Bell Force 486SX/25

Packard Bell Force 486SX/25G

Packard Bell Force 486SX/25W

Packard Bell Force 48825

Packard Bell Force 515S

Packard Bell Force 515S Plus

Packard Bell Force 525

Packard Bell Force 525B

Packard Bell Force 525S

Packard Bell Force 545

Packard Bell Force 545B

Packard Bell Force 545S

Packard Bell Force 565

Packard Bell Force 565

Packard Bell Force 565S

Packard Bell Force 600

Packard Bell Force 600B

Packard Bell Force 600S

Packard Bell Force 715 Minitower (*)

Packard Bell Force T66(*)

Packard Bell Legend 102 Elite

Packard Bell Legend 102H

Packard Bell Legend 1134 Elite (*)

Packard Bell Legend 1135

Packard Bell Legend 1136(*)

Packard Bell Legend 1137

Packard Bell Legend 115

Packard Bell Legend 1166(*)

Packard Bell Legend 1176(*)

Packard Bell Legend 120

Packard Bell Legend 125

Packard Bell Legend 126 Elite ((*)

Packard Bell Legend 127(*)

Packard Bell Legend 128

Packard Bell Legend 135(*)

Packard Bell Legend 135H(*)

Packard Bell Legend 140(*)

Packard Bell Legend 1900(+)

Packard Bell Legend 1910(+)

Packard Bell Legend 2000(+)

Packard Bell Legend 2001 (+)

Packard Bell Legend 2002 Elite (+)

Packard Bell Legend 2011 Supreme (+)

Packard Bell Legend 2025(+)

Packard Bell Legend 207(*)

Packard Bell Legend 2133 Minitower (*)

Packard Bell Legend 2135 Minitower (*)

Packard Bell Legend 2176 Elite MT(*)

Packard Bell Legend 2276 Minitower (*)

Packard Bell Legend 2266 Minintower (*)

Packard Bell Legend 2270 Minitower (*)

Packard Bell Legend 2300 Minitower (+)

Packard Bell Legend 233(*)

Packard Bell Legend 234 Elite (*)

Packard Bell Legend 245

Packard Bell Legend 33T Supreme Minitower (*)

Packard Bell Legend 486CDM-1/TV(+)

Packard Bell Legend 486T/50(*)

Packard Bell Legend 625

Packard Bell Legend 660

Packard Bell Legend 660 ELITE (*)

Packard Bell Legend 660H

Packard Bell Legend 66D Supreme(*)

Packard Bell Legend 66D Supreme(*)

Packard Bell Legend 66T Supreme (*)

Packard Bell Legend 670(*)

Packard Bell Legend 695 Supreme

Packard Bell Legend 700

Packard Bell Legend 700 Elite (*)

Packard Bell Legend 740(*)

Packard Bell Legend 747 Minitower (*)

Packard Bell Legend 750 SUPREME

Packard Bell Legend 760 Supreme

Packard Bell Legend 770

Packard Bell Legend 770 ELITE(*)

Packard Bell Legend 780 Supreme (*)

Packard Bell Legend 780(*)

Packard Bell Legend 790

Packard Bell Legend 800 SUPREME(*)

Packard Bell Legend 800 Supreme/50(*)

Packard Bell Legend 800+ SUPREME(*)

Packard Bell Legend 840 Minitower (*)

Packard Bell Legend 845 Minitower (*)

Packard Bell Legend 848 Minitower (*)

Packard Bell Legend 925G

Packard Bell Legend 925G Elite

Packard Bell Legend 925J

Packard Bell Legend 933G

Packard Bell Legend 933G ELITE

Packard Bell Legend 933J

Packard Bell Legend 933J ELITE

Packard Bell Legend 933J+

Packard Bell Legend 950 ELITE(*)

Packard Bell Legend 950(*)

Packard Bell Legend 950J ELITE

Packard Bell Legend M950(*)

Packard Bell Legend MT950J

Packard Bell Legend T66(*)

Packard Bell PackMate 2050(+)

Packard Bell PackMate 486/33(*)

Packard Bell PackMate 486/33G

Packard Bell PackMate 486/33J

Packard Bell PackMate 48625

Packard Bell PackMate 486SX/25G

Packard Bell PackMate 733 C MT (*()

Packard Bell PackMate X225

Packard Bell PackMate X230

Packard Bell PackMate X233

Packard Bell PackMate X240(*)

Packard Bell PackMate X250(*)

Packard Bell PackMate X250Y(*)

Packard Bell PackMate XT266(*)

Panasonic CF1000

Panasonic CF1000A

Pionex 486DX2/50

Pionex 486DX2/66

Pionex 486DX33

Pionex 486DX33

Pionex 486SX25

Quantex 486DX2/50

Quantex 486DX2/66

Quantex 486DX50

Quantex 486SX25

Reply Turbo Processor System Upgrades

Sanyo MBC 19 NC

Seanix ASI 9000 9dx266vm8I

Seanix ASI 9000 9dx50vm4I

Siemens Nixdorf PCD-4G

Siemens Nixdorf PCD-4Hsx

Siemens Nixdorf PCE-4C

Siemens Nixdorf PCE-4L

Siemens Nixdorf PCE-4LSX

Siemens Nixdorf PCE-4T

Siemens Nixdorf PCE-4T/66

Siemens Nixdorf PCE-5s

Toshiba 6600C

Toshiba T1850C

Toshiba T1900C

Toshiba T4400C

Toshiba T4500C

Toshiba T4600C

Toshiba T6400SXC

TriGem 486 DX2/66ME

TriGem 4DX2/66ML

Unidata PD466

Unisys MPI 4163

Unisys MPI 42562

Unisys PW 2 Advantage MPI 43331

Unisys PW2 Advamtage 46662

Unisys PW2 Advantage 42532

Unisys PW2 Advantage 45061

Unisys PW2 Advantage 46634

Unisys PW2 Advantage 46663

Unisys PW2 Advantage MIP 43363

Unisys PW2 Advantage MPE 56061

Unisys Unity PDI 4335

Unisys Unity PSI 3333

Unisys Unity XDE 4666

Video Tech 486SX/3 Desktop (w/LBVGA)

Video Tech Laser 386 SX/3 Desktop

Video Tech Laser 386 SX/3 Ultra Slim

Video Tech Laser 386/3 Desktop

Video Tech Laser 386/3 Tower

Video Tech Laser 386SX/3 Desktop

Video Tech Laser 386SX/3 Ultra Slim

Video Tech Laser 486 DX/3 Desktop w/LBVGA

Video Tech Laser 486 DX/3 Tower

Video Tech Laser 486 DX/6 Tower

Video Tech Laser 486 DX2/4 Desktop

Video Tech Laser 486 DX2/4 Tower

Video Tech Laser 486 DX2/6 Desktop w/ LBVGA

Video Tech Laser 486 SX/3 Desktop

Video Tech Laser 486 SX/3 Desktop w/ LBVGA

Video Tech Laser 486 SX/3 Tower

Video Tech Laser 486 SX/3 Ultra Slim

Video Tech Laser 486 SX/4 Desktop

Video Tech Laser 486 SX/4 Tower

Video Tech Laser 486DX/2 Deskto p(w/LBVGA)

Video Tech Laser 486DX/3 Desktop (w/VLBus)

Video Tech Laser 486DX/3 Tower

Video Tech Laser 486DX/3 Tower (W/VLBus)

Video Tech Laser 486DX/3 Ultra Slim (w/LBVGA)

Video Tech Laser 486DX/4 Tower (w/VLBus)

Video Tech Laser 486DX2 Deskto (w/LBVGA)

Video Tech Laser 486DX2/4 Desktop

Video Tech Laser 486DX2/4 Desktop (w/LBVGA)

Video Tech Laser 486DX2/4 Desktop (w/VLBus)

Video Tech Laser 486DX2/4 Tower

Video Tech Laser 486DX2/6 Desktop

Video Tech Laser 486DX2/6 Tower

Video Tech Laser 486DX2/6 Tower (w/VLBus)

Video Tech Laser 486DX2/66 Desktop (w/VLBus)

Video Tech Laser 486SX.3 Desktop (w/LBVGA)

Video Tech Laser 486sx.3 Tower (w/VLBus)

Video Tech Laser 486SX/3 Desktop

Video Tech Laser 486SX/3 Desktop (w/VLBus)

Video Tech Laser 486SX/3 Tower

Video Tech Laser 486SX/3 Ultra Slim (w/LBVGA)

Video Tech Laser 486SX/4 Desktop

Video Tech Laser 486SX/4 Desktop (VLBus)

Video Tech Laser 486SX/4 Desktop (w/LBVGA)

Video Tech Laser 486SX/4 Tower

Video Tech Laser 486SX/4 Tower (w/VLBus)

Video Tech Laser 486SX/4 Ultr Slim (w/LBVGA)

Video Tech Laser a486DX/3 Desktop

Video Tech Laser LT 321E Notebook

Video Tech Laser LT 421 Notebook

Video Tech Laser SX/4 Desktop w/LBVGA

Video Tech Laser LT 322 Notebook

Viglen Contender 4DX33

Viglen EXC ISA

Viglen Genie

WCWS&S Multi Media VESA 486DX

Wyse Decision 486se

Wyse Decision 486si

Wyse Series 3000i Model 350

Wyse Series 6000i Model 650

Zymos AXXESS 486DX2-66

Zymos AXXESS 486DX33

Additional reference words: 3.11 wfw wfwg HCL incompatible won't work

will works good bad ok compatability


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

Additional reference words: 3.11 wfw wfwg 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 Plus (3C505-B)

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

Additional reference words: 3.11 wfw wfwg incompatible unsupported

supported works won't work good bad HCL


Intel SatisFaxtion 100 & 400E Are Class 1 and CAS Compatible

Article ID: Q107376

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SUMMARY

=======

You can use the Intel SatisFaxtion 100 fax modem as either a Class 1

or CAS modem type with Microsoft At Work PC Fax.

MORE INFORMATION

================

The Intel SatisFaxtion 100 and 400E fax modems are CAS only when either

CASMGR.EXE or CASMODEM.EXE (provided by Intel) is installed in the

AUTOEXEC.BAT file. If neither driver is installed, the fax modem becomes

Class 1 compatible, which is the desired configuration for use with

Microsoft At Work PC Fax.

The advantage to Class 1 is that Microsoft At Work PC Fax can control

more aspects of the fax modem and allow binary file transfer.

CASMGR is a driver supplied by Intel for communicating between MS-DOS

and the CAS hardware on the fax modem.

Additional reference words: 3.11 INTEL CLASS1 100 EFAX AWFAX

satisfaction


Fax Modem Class Required for Binary File Transfers

Article ID: Q107393

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SUMMARY

=======

With Microsoft At Work PC Fax version 1.0 (supplied with Microsoft

Windows for Workgroups 3.11), if you want to perform binary file

transfers or use the advanced security features, you must use a Class

1 fax modem at both ends of the communication. This article provides

instructions to determine what class of fax modem you have.

MORE INFORMATION

================

Use the following procedure to determine what class of fax modem you

are using:

1. Load the Terminal application provided with Windows for Workgroups

   and configure it with the correct settings for your modem.

2. In the Terminal window, type the following:

      AT+FCLASS=?

The modem should respond with one of the following strings of numbers:

   0

   -or-

   0,1

   -or-

   0,1,2

   -or-

   0,2

These strings can be interpreted as follows:

   0 = Data

   1 = Class 1

   2 = Class 2

Class 1 and Class 2 are standards that define an interface with an

asynchronous serial bidirectional data stream between the computer and

the fax modem. Fax modems can be members of more than one fax class.

For example, if the result of the above procedure was "0,1,2," the fax

modem would belong to the Data, Class 1, and Class 2 categories.

Microsoft At Work PC Fax software can send a fax as a graphical image

(facsimile format) or as a Microsoft Mail message in binary form

(electronic mail format).

The ability to send a fax in binary form allows you to send

attachments, such as Word for Windows documents or Microsoft Excel

spreadsheets, to remote locations without having to use communications

software (such as Terminal). These attachments can also be edited,

whereas a fax transmitted in the facsimile format cannot be edited.

Without a Class 1 fax modem on both the sending and receiving ends of

a fax transmission made with At Work PC Fax, faxes always transfer as

graphical images that can be viewed and printed only.

At Work PC Fax also provides advanced security features to ensure the

security of faxes by encrypting them. An encrypted fax cannot be read

by anyone except the intended recipient. These security features

include password encryption, key encryption, and the ability to apply

a digital signature to the fax.

To use the security features provided by At Work PC Fax, both the

sender and the recipient of the fax must be using Microsoft At Work PC

Fax and Class 1 fax modems so that the fax can be transmitted in the

electronic mail binary file format.

Additional reference words: 3.11 type E-Mail wfwg


Meaning of WFWShell Line in the SYSTEM.INI File

Article ID: Q107470

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

--------------------------------------------------------------------

The Setup program for Microsoft Windows for Workgroups 3.11 uses the

WFWShell statement in the [Boot] section of the SYSTEM.INI file to store

the contents of your current Shell line.

After Setup is complete, the WFWShell line is used to reestablish the Shell

setting. Microsoft Windows 3.1 and Windows for Workgroups 3.1 used OldShell

for this same purpose.

Additional reference words: 3.11 wfw wfwg program manager replacement


Fax Monitor Is Idle on CAS Modems While Receiving Faxes

Article ID: Q107472

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

--------------------------------------------------------------------

SUMMARY

=======

With CAS fax modems, the fax monitor feature of Microsoft At Work PC Fax

stays in an idle state while receiving faxes.

MORE INFORMATION

================

CAS-compatible fax modems have their own processors and memory and are

designed to work independently in the background. Commands to CAS fax

modems are issued to CASMGR.EXE or CASMODEM.EXE, depending on the modem and

revision of the CAS modems. This program then issues the appropriate

commands to the CAS modem.

When a CAS modem receives a fax, it does so in the background,

independently of At Work PC Fax. CASMGR does not notify At Work PC Fax that

a fax is arriving. After the fax arrives, CASMGR places the fax in a queue.

At Work PC Fax checks the queue periodically for new faxes. Because this

occurs in the background, At Work PC Fax cannot monitor the progress of an

incoming fax.

At Work PC Fax does monitor sent message rendering status. During a fax

send, fax monitor reports the progress of the fax-rendering process.

Additional reference words: 3.11 AWFAX CAS MONITOR facsimile class wfw wfwg


Setting Up a Shared Copy of WFWG on LAN Manager-Based Servers

Article ID: Q107474

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

--------------------------------------------------------------------

SUMMARY

=======

Windows for Workgroups 3.11 may not install properly when you use the SETUP

/N command from a shared copy that is located on a Microsoft LAN Manager-

or Windows NT-based server. This article explains how to correctly set up a

shared copy of Windows for Workgroups on a LAN Manager-based network.

Please note that when Windows for Workgroups is set up this way, Windows

for Workgroups server capabilities are not available because users must

start the real-mode network redirector to access the shared files on the

server. The Windows for Workgroups server cannot run when the real-mode

redirector is started. This behavior is different from that of Windows for

Workgroups 3.1 (because of changes made in 3.11 to facilitate use of the

Installable File System [IFS] Manager).

MORE INFORMATION

================

Users wanting to set up a shared copy of Windows for Workgroups must first

have a real-mode networking client installed that is able to connect to the

file server where the shared copy of Windows for Workgroups had been

installed. This article describes how to set up Windows for Workgroups with

either Workgroups Connections 1.0 or the Microsoft LAN Manager client,

which is included in the Microsoft Network client. This article assumes

that SETUP /A has already been completed and the shared files are already

located on the file server.

Workgroup Connections

---------------------

Workgroup Connections is a real-mode networking client that is normally

used to connect to Windows for Workgroups servers. Use the following steps

to set up a shared copy of Windows for Workgroups with Workgroup

Connections:

1.Install Workgroup Connections in a clean directory. The Setup program

  defaults to the DOS directory; do NOT install to this directory. If you

  do so, you install Windows for Workgroups user files over the top of this

  directory.

2.Use the Workgroup Connections network to connect to the file server's

  Windows for Workgroups share with drive <W>. (It does not matter which

  drive you use, but you must remember the drive letter because the same

  drive must be used after Windows for Workgroups has been set up.)

3.Run the Windows for Workgroups SETUP /N command and let Windows for

  Workgroups install to the same directory in which you installed

  Workgroup Connections. Setup should automatically choose the Microsoft

  Windows Network, and you should verify that your network card driver is

  set up properly. Be sure to let Setup configure your CONFIG.SYS and

  AUTOEXEC.BAT files.

4.Once Setup is complete, reboot the machine. The real-mode network should

  start and log you on to the network. Use the NET USE command to connect

  drive <W> to the file server's Windows for Workgroups share. (This drive

  letter should be the same one you used in step 2.)

5.Use the WIN command to start Windows for Workgroups. The first time you

  start Windows for Workgroups, a warning message states that you do not

  have sharing capabilities (because the real-mode network is started).

  You can ignore this message and choose the NO button to prevent it from

  coming up again.

Microsoft Network Client (LAN Manager Client)

---------------------------------------------

The Microsoft Network Client is a real-mode LAN Manager client that is

available for download from the Microsoft Download Service (MSDL),

CompuServe (type "go msclient" [without the quotation marks]), and the

Internet server (type "GOWINNT ! AdvSys\MSClient" [without the quotation

marks]). If you can't access these services, the Microsoft Network client

is available for sale from Microsoft Sales and Service at (800) 426-9400.

Use the following steps to set up a shared copy of Windows for Workgroups

with the LAN Manager client:

1.Use the LAN Manager client to connect to the file server's Windows for

  Workgroups share with drive <W>. (It doesn't matter which drive you use,

  but you must remember the drive letter because the same drive must be

  used after Windows for Workgroups has been set up.)

2.Run the Windows for Workgroups SETUP /N command and direct Windows for

  Workgroups to a clean directory. Do not set up Windows for Workgroups in

  the directory that LAN Manager is in. (If you do, the PROTOCOL.INI file

  is not set up correctly.) Setup should automatically choose the

  Microsoft Windows Network, and you should verify that your network card

  driver is set up properly. Be sure to let Setup configure your

  CONFIG.SYS and AUTOEXEC.BAT files, and make sure that all references to

  LAN Manager are removed from both files.

3.Once Setup is complete, reboot the machine. The real-mode network should

  start and log you on to the network. Use the NET USE command to connect

  drive <W> to the file server's Windows for Workgroups share. This drive

  letter should be the same drive letter you used in step 1.

4.Use the WIN command to start Windows for Workgroups. The first time you

  start Windows for Workgroups, a warning message states you do not have

  sharing capabilities (because the real-mode network is started). You can

  ignore this message and choose the NO button to prevent it from coming

  up again.

Additional reference words: 3.11 wfwg setup howto wfw


Total Number of Workgroups That Can Be Displayed

Article ID: Q107475

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

--------------------------------------------------------------------

Microsoft Windows for Workgroups version 3.11 is limited to displaying

1,400 different workgroups simultaneously.

Additional reference words: 3.11 wfw wfwg limit maximum number total

greater than less at one time


Video Seven VRAM II Video Adapter Hangs WFWG 3.11 Setup

Article ID: Q107476

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

--------------------------------------------------------------------

SYMPTOMS

========

If you use the Video Seven VRAM II video adapter and the VGA, Super VGA, or

Super VGA (256 color) video driver with Microsoft Windows for Workgroups,

your computer stop responding (hang) during Setup.

CAUSE

=====

The Video Seven VRAM II video adapter is incompatible with these drivers

in Windows for Workgroups 3.11.

RESOLUTION

==========

Run Setup and select Custom Installation. Select the appropriate Video

Seven display driver to install.

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 as it becomes available.

Additional reference words: 3.11 video seven vram


Comprehensive List of WFW 3.11 User's Guide Doc Errors

Article ID: Q107538

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SUMMARY

=======

This article contains information on the documentation errors in the

Microsoft Windows for Workgroups 3.11 "User's Guide." The following topics

are covered:

 - Incorrect Application Note Reference in Appendix B

MORE INFORMATION

================

Incorrect Application Note Reference in Appendix B

--------------------------------------------------

The "User's Guide" incorrectly states the following on page 5 of Appendix

B:

   For more information relating to customizing Windows for Workgroups for

   people with disabilities, see Application Note WW0787.

Application Note WW0787 covers customizing Windows 3.1 for people with

disabilities. Application Note WG0788 covers customizing Windows for

Workgroups for people with disabilities.

Additional reference words: 3.11 docerr doc err documentation error

errors workgroup add-on


WG0788: Customizing WFWG 3.11 for Individuals w/ Disabilities

Article ID: Q107556

This Application Note, "Customizing Windows for Workgroups for Individuals

with Disabilities" (WG0788) provides information about products and

services available for computer users with special needs:

You can obtain this Application Note from the following sources:

 - Microsoft Download Service (MSDL)

 - Microsoft Product Support Services

For complete information, see the "To Obtain This Application Note"

section at the end of this article.

THE TEXT OF WG0788

==================

--------------------------------------------------------------------

======================================================================

  Microsoft(R) Product Support Services Application Note (Text File)

    WG0788: CUSTOMIZING WINDOWS(TM) FOR WORKGROUPS FOR INDIVIDUALS

                           WITH DISABILITIES

======================================================================

                                                  Revision Date: 11/93

                                                      No Disk Included

The following information applies to Microsoft 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(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 is a     |

|trademark of Microsoft Corporation.                                 |

|--------------------------------------------------------------------|

          CUSTOMIZING WINDOWS FOR WORKGROUPS FOR INDIVIDUALS

          ==================================================

                           WITH DISABILITIES

                           =================

This Application Note provides information about the following

products and services available for computer users with special needs:

 - Support services for people who are deaf or hard-of-hearing

 - Access Pack for Microsoft Windows, a product that makes Windows

   more accessible for people with movement or hearing disabilities

 - Keyboard layouts designed for people who type with a single hand or

   wand

 - Microsoft Mouse driver version 9.0

 - Microsoft documentation on audio cassettes and floppy disks

 - Products available for individuals who are blind or have low vision

 - Help installing Windows for Workgroups

 - Customizing Windows for Workgroups without additional hardware or

   software

 - More information about products and services for people with

   disabilities

    NOTE: The information in this Application Note applies to Windows

    for Workgroups users in the United States only. If you are outside

    the United States, your Windows for Workgroups package contains a

    subsidiary information card listing product support telephone

    numbers and addresses. Contact your subsidiary to find out whether

    the types of products and services described in this Application

    Note are available in your area.

 MICROSOFT SUPPORT SERVICES FOR PEOPLE WHO ARE DEAF OR HARD-OF-HEARING

 =====================================================================

Through text telephone (TT/TDD) services, Microsoft provides people

who are deaf or hard-of-hearing with the same technical product

support and customer service as hearing customers.

For sales information and nontechnical customer service, you can

contact Microsoft Consumer Sales on a text telephone at (800) 892-5234

between 6:30 A.M. and 5:30 P.M. Pacific time. For technical

assistance, you can contact Microsoft Product Support Services (PSS)

on a text telephone at (206) 635-4948 between 6:00 A.M. and 6:00 P.M.

Pacific time. Microsoft support services are subject to Microsoft

prices, terms, and conditions in place at the time the service is

used.

                   ACCESS PACK FOR MICROSOFT WINDOWS

                   =================================

Microsoft distributes Access Pack for Microsoft Windows, which

provides people who have movement or hearing disabilities with better

access to computers running Windows or Windows for Workgroups. With

Access Pack for Microsoft Windows, you can configure your Windows

system to do the following:

 - Allow easier use of SHIFT, CTRL, and ALT key combinations for

   people who type with a single finger, a mouthstick, or a wand.

 - Ignore accidental key presses.

 - Adjust or disable the rate at which a character is repeated on the

   screen when you hold down a key.

 - Prevent extra characters if you unintentionally press a key more

   than once.

 - Allow you to use the keyboard to control the mouse cursor.

    NOTE: If you use this feature with Microsoft Paintbrush, your

    system stops responding (hangs). To work around this problem, use

    Paintbrush keyboard commands. For more information, run Paintbrush

    and press F1--each specific task help topic has information on the

    keyboard equivalent for the mouse action.

 - Allow you to use an alternate input device to control the

   computer's keyboard and mouse.

 - Provide a visual cue when a computer makes sounds.

 - Enable you to turn off these services for people who do not need

   them.

Access Pack for Microsoft Windows, which was developed by the Trace

R&D Center at the University of Wisconsin at Madison, is available on

the Microsoft Windows Driver Library in the file ACCP.EXE.

If you have a modem, you can download Windows Driver Library

components from network services, including CompuServe, GEnie,

Microsoft Online, various user-group bulletin board services (BBSs)

(including BBSs on the Association of PC User Groups [APCUG] network),

and the Microsoft Download Service (MSDL). The MSDL is available seven

days a week from 2:30 A.M. to 1:00 A.M. at (206) 936-MSDL (936-6735).

The modem settings are:

   1200,n,8,1

   2400,n,8,1

   9600,n,8,1 (V.32, V.32bis, V.42, V.42bis)

   14,400,n,8,1 (V.32, V.32bis, V.42, V.42bis)

    NOTE: If you cannot connect at 14,400, lower the baud rate to

    9600 and try again.

Customers who do not have a modem can obtain disks by calling PSS at

(206) 637-7098 (voice telephone) or (206) 635-4948 (text telephone).

           KEYBOARD LAYOUTS FOR SINGLE-HANDED COMPUTER USERS

           =================================================

Microsoft distributes software to modify your keyboard layout. These

keyboard layouts can be useful for people who have difficulty using

the standard QWERTY layout. You can use this software to change your

keyboard configuration without adjusting your physical keyboard.

Windows for Workgroups has built-in support for the two-handed Dvorak

keyboard layout, which may be useful for preventing or coping with

some types of repetitive motion injuries associated with typing. To

use this layout, choose the International icon in Control Panel. Two

additional layouts are designed for people who type with the left hand

only or with the right hand only. These layouts can also be useful for

people who type with a single finger or a wand.

The single-handed layouts are included with the PSS Application Note

GA0650, "Dvorak Keyboard Layouts." If you have a modem, you can

download GA0650 from the network services listed in the previous

section. The filename is GA0650.ZIP, except on MSDL, where this

Application Note is available in the self-extracting file GA0650.EXE.

Customers who do not have a modem can obtain GA0650 by calling

Microsoft Consumer Sales at (800) 426-9400 (voice telephone) or (800)

892-5234 (text telephone).

                  MICROSOFT MOUSE DRIVER VERSION 9.0

                  ==================================

If you have trouble seeing the mouse when you are moving it and you

are using the Microsoft Mouse or the Microsoft BallPoint Mouse, you

can upgrade to version 9.0 of the Microsoft Mouse driver. The optional

utilities included with the 9.0 Microsoft Mouse driver offer the

following features:

 - Larger pointer sizes--You can choose a small, medium, or large

   pointer size.

 - Larger I-beam pointer--The I-beam pointer is larger than the

   regular I-beam.

 - Pointer growth--You can make the pointer increase to the large

   pointer size when you begin to move the mouse.

 - Cursor color choice--You can choose a white, black, or transparent

   mouse pointer.

 - Snap-To--You can configure the mouse pointer to jump to the default

   button when a dialog box opens.

 - Locate--You can make the mouse pointer jump to the middle of the

   screen when you press a specified control key and mouse button.

 - Sensitivity--You can independently adjust the vertical and

   horizontal sensitivity. This can be useful for people whose control

   or range differs for vertical and horizontal movement.

 - Orientation--You can customize the mouse orientation. This can be

   useful for people who need or want to hold the mouse at a

   particular angle.

    NOTE: Mouse driver version 9.0 and the optional utilities

    mentioned above are included with Microsoft Mouse version 2.0.

If you own a Microsoft Mouse, you can order the version 9.0 driver by

calling Microsoft Consumer Sales at (800) 426-9400 (voice telephone)

or (800) 892-5234 (text telephone). There is a charge for the version

9.0 driver.

           DOCUMENTATION ON AUDIO CASSETTES AND FLOPPY DISKS

           =================================================

People who cannot use printed documentation can obtain many of

Microsoft's publications from Recording for the Blind, Inc. (RFB). RFB

distributes these documents on audio cassettes and floppy disks to

registered members of its distribution service. RFB's collection

contains more than 80,000 titles, including Microsoft product

documentation and books from Microsoft Press. You can contact

Recording for the Blind at the following address and phone and fax

numbers:

   Recording for the Blind, Inc.

   20 Roszel Road

   Princeton, NJ  08540

   (800) 221-4792     Voice telephone

   (609) 987-8116     Fax

       PRODUCTS FOR INDIVIDUALS WHO ARE BLIND OR HAVE LOW VISION

       =========================================================

If you are blind or have low vision, many products are available to

help you use Windows. For persons with low vision, there are several

screen-enlargement utilities. For blind individuals, there are screen

readers that provide alternative output by synthesized voice or

refreshable Braille displays.

For more information on the products available, see the "Getting More

Information" section of this Application Note. For more information

about customizing Windows for Workgroups for individuals with low

vision, see the "Customizing Windows for Workgroups Without Additional

Hardware or Software" section below.

                HELP INSTALLING WINDOWS FOR WORKGROUPS

                ======================================

Individuals who rely on some types of accessibility software may have

difficulty installing Windows for Workgroups because the accessibility

software is not loaded during the graphical portion of Setup. If this

presents a problem, you can bypass the graphical portion of Setup by

using the /h switch. The /h switch allows you to specify a text file

that provides answers to all the questions that you would be prompted

for during the graphical portion of Setup. For example, if you create

a text file called MYSETUP.SHH, you would then run Setup with the

following command:

      a:\setup /h:c:\mysetup.shh

For more information on the format of the setup response file, see the

SETUP.SHH file provided on your Windows for Workgroups installation

disks.

              CUSTOMIZING WINDOWS FOR WORKGROUPS WITHOUT

              ==========================================

                    ADDITIONAL HARDWARE OR SOFTWARE

                    ===============================

There are many ways you can adjust the appearance and behavior of

Windows for Workgroups to suit varying eyesight and motor skills

without any additional software or hardware. For example, by changing

settings in your WIN.INI and SYSTEM.INI files, you can control screen

colors, font sizes, and mouse behavior. You can change these settings

in Control Panel or by directly modifying the files. The following

sections describe how to identify which settings to modify to achieve

the desired results and how to safely modify the WIN.INI, SYSTEM.INI,

and other Windows initialization files.

Modifying Initialization Files

==============================

Windows initialization files (.INIs) contain information about your

system environment. For example, the WIN.INI file contains settings

about your Windows environment, and the SYSTEM.INI file contains

settings that tell Windows about your system's hardware needs.

MSMAIL.INI and SCHEDPLUS.INI contain settings that control the

appearance of text and screen colors within the Mail and Schedule+

applications.

You can configure Windows and Windows-based applications to meet your

needs and preferences by modifying the information stored in these

files. For more information about WIN.INI and SYSTEM.INI, refer to the

WININI.WRI and SYSINI.WRI files located in your Windows directory. You

can print or view these files from Microsoft Windows Write.

   IMPORTANT: Errors made when editing initialization files can lead

   to undesirable results when you run Windows. Before changing any

   entry, make a backup copy of your original file. Also, some text

   editors can damage characters that have ANSI values greater than

   127. To avoid these problems, we recommend that you use Control

   Panel or Setup whenever possible to make changes. If you must edit

   the file, use a text editor such as Microsoft Windows Notepad,

   System Configuration Editor (SYSEDIT.EXE), or MS-DOS Editor.

To change .INI file entries with a text editor:

1. Create a backup copy of the .INI file you want to edit. For

   example, run File Manager and copy WIN.INI to WIN.BAK.

2. Open the .INI file with a text editor, such as Notepad.

3. Edit the specific entries and save the file.

4. Restart Windows so that the changes take effect.

The next five sections of this Application Note discuss the

initialization file entries you can change to achieve the specific

results you want. Many of the initialization file entries discussed

below are not present in the WIN.INI file by default but you can

easily add them with a text editor.

Changing Colors

---------------

 - If you have trouble differentiating the system colors, or if they

   cause eyestrain, you can adjust them in the Colors dialog box of

   Control Panel.

 - If you have trouble reading full-screen messages displayed by

   Windows in 386 enhanced mode, you can adjust the colors by using

   the MessageBackColor and MessageTextColor entries in the [386Enh]

   section of the SYSTEM.INI file. For example, the following entries

   generate bright yellow text on a black background in message

   screens (such as the screen that appears when you press

   CTRL+ALT+DEL):

         MessageTextColor=E

         MessageBackColor=0

   The following table defines the color values you can use for the

   MessageBackColor and MessageTextColor entries:

   0 - Black  4 - Red            8 - Gray           C - Bright red

   1 - Blue   5 - Magenta        9 - Bright blue    D - Bright magenta

   2 - Green  6 - Yellow/brown   A - Bright green   E - Bright yellow

   3 - Cyan   7 - White          B - Bright cyan    F - Bright white

 - If the desktop pattern or wallpaper causes eyestrain, you can

   adjust them in the Desktop dialog box of Control Panel.

 - If you have trouble differentiating the colors used by Windows

   Help, you can adjust them by using the IFJumpColor, IFPopupColor,

   JumpColor, MacroColor, and PopupColor entries in the [Windows Help]

   section of the WIN.INI file. The syntax for these entries is

      <entry>=red <value> green <value> blue <value>

   where the <value> is a number from 000 to 999, with 999 giving the

   highest intensity. You must include three digits for each value,

   and you must include each color value. You can experiment with this

   setting to create a color that works best for you. The following

   table lists some colors you can work with:

   Setting          Resulting color

--------------------------------------

   000 000 999      Blue

   000 999 000      Green

   999 000 000      Red

   999 999 000      Yellow

   999 000 999      Magenta

   For more information on these entries, see the WININI.WRI file in

   your Windows directory.

Changing Fonts

--------------

 - If you have trouble reading the Windows for Workgroups system fonts

   (which are used to display window titles, menus, and dialog boxes),

   you can increase the font size using the FIXEDFON.FON, FONTS.FON,

   and OEMFONTS.FON entries in the [boot] section of the SYSTEM.INI

   file. However, you should replace the default fonts only with other

   system font files supplied with Windows for Workgroups. These fonts

   include 8514FIX.FON, 8514SYS.FON, and 8515OEM.FON.

   For example, if you are using a VGA video driver, your .FON files

   are probably set as follows:

      fixedfon.fon=vgafix.fon

      fonts.fon=vgasys.fon

      oemfonts.fon=vgaoem.fon

   To increase the size of the system font, expand 8514FIX.FON,

   8514SYS.FON, and 8515OEM.FON from the original Windows for

   Workgroups disks to your Windows program directory (usually

   C:\WINDOWS). For example, type the following command at the MS-DOS

   command prompt, and then press ENTER:

      expand a:\8514fix.fo_ c:\windows\system\8514fix.fon

   Then, edit the [boot] section of your SYSTEM.INI file to read:

      fixedfon.fon=8514FIX.FON

      fonts.fon=8514SYS.FON

      oemfonts.fon=8515OEM.FON

   WARNING: Do not use font files other than the system .FON fonts

   supplied with Windows for Workgroups. For example, you cannot use

   TrueType (.TTF) fonts.

 - If you have trouble reading the titles of icons, you can adjust the

   appearance of these titles with the IconTitleFaceName and

   IconTitleSize entries in the [desktop] section of the WIN.INI file.

   For example:

      [desktop]

      IconTitleFaceName=Arial

      IconTitleSize=12

 - If you have trouble reading small fonts used by some applications

   and do not want to install a screen enlarger utility, you can

   restrict the fonts available to Windows-based applications by

   removing the fonts you do not want in the Fonts dialog box of

   Control Panel. You do not need to actually delete the font files.

   If you remove all the fonts, only the system fonts remain available

   to applications.

     NOTE: You may also need to adjust the icon spacing in the Desktop

     dialog box of Control Panel and choose Arrange Icons from the

     Window menu in Program Manager to make all your icon titles

     visible.

 - If you have trouble reading the file and directory names in File

   Manager, you can adjust the font settings by choosing Font from the

   Options menu.

 - If you have trouble locating the text-selection cursor (also known

   as the caret or insertion bar) in your applications, you can adjust

   the rate at which it flashes. To do this, choose the Desktop icon

   in Control Panel.

Changing Schedule+ and Mail Settings

------------------------------------

 - If you have trouble reading the text in Schedule+, you can adjust

   the fonts and colors by choosing Display from the Options menu.

 - If you have trouble reading the text in Microsoft Mail, you can

   adjust the fonts using the FixedFont, NormalFont, and PrintFont

   entries in the [Microsoft Mail] section of the MSMAIL.INI file,

   which is located in your Windows for Workgroups directory. Each

   entry has four parts separated by commas: the font name, point

   size, a flag for bold, and a flag for italic. To switch between the

   normal font and the fixed font, choose Change Font from the View

   menu. Each entry is described separately in the following

   paragraphs.

 - FixedFont=<facename>, <size>, 0|1, 0|1

      The above entry identifies a fixed-pitch font you can substitute

      for the one supplied with Microsoft Mail. This font serves as an

      alternative to the Microsoft Mail default (Helvetica 10 point).

      This entry affects only the message body text, not the message

      envelope text or folder lists. In Windows for Workgroups Mail,

      the default is Courier New, 9, 0, 0 (Courier New, 9-point, not

      bold, not italic).

 - NormalFont=<facename>, <size>, 0|1, 0|1

      The above entry identifies the proportionally spaced default

      font used to display Mail messages. This entry affects only the

      message body text, not the message envelope text or folder

      lists. The default value is Helv, 10, 0, 0.

 - PrintFont=<facename>, <size>, 0|1, 0|1

      The above entry identifies the default proportionally spaced

      font used to print Mail messages. The default value is Helv, 10,

      0, 0.

Changing Mouse Behavior

-----------------------

 - If you have difficulty controlling the Microsoft Mouse, you can

   adjust its speed in the Mouse dialog box of Control Panel.

 - If you have trouble seeing the mouse when you are moving it, you

   can try using the Mouse Trails feature in the Mouse dialog box of

   Control Panel. If your third-party video driver does not support

   the Mouse Trails option, contact your video card vendor for more

   information.

 - If you have trouble double-clicking the mouse, you can adjust the

   sensitivity using the Double-Click Speed setting in the Mouse

   dialog box of Control Panel. You can further adjust the double-

   click functionality by adding the DoubleClickHeight and

   DoubleClickWidth entries to the [Windows] section of the WIN.INI

   file. For example, if you add the following entries to your WIN.INI

   file and restart your computer, you no longer have to hold the

   mouse in exactly the same location when you double-click:

      DoubleClickHeight=30

      DoubleClickWidth=30

 - If you have trouble positioning the mouse on window frames so that

   you can adjust the size of the windows, you can increase the window

   border width setting in the Desktop dialog box of Control Panel.

Changing Keyboard Behavior

--------------------------

 - If you have trouble using the keyboard because of the speed at

   which it repeats or the delay time before it begins repeating, you

   can adjust these settings in the Keyboard dialog box of Control

   Panel. (You can adjust keyboard settings even further using Access

   Pack for Microsoft Windows, which is described later on in this

   Application Note.)

   If you cannot use Control Panel to adjust the keyboard, you can

   adjust the corresponding KeyboardDelay and KeyboardSpeed entries in

   the [Windows] section of the WIN.INI file. KeyboardDelay

   establishes how much time elapses after you hold down a key before

   the key starts to repeat (the default is 2 milliseconds).

   KeyboardSpeed establishes how much time elapses between repetitions

   of a character on the display when you hold down a keyboard key

   (the default is 31 milliseconds).

 - You can use Windows Recorder to automate common tasks. For more

   information about using Recorder, run Recorder and choose Contents

   from the Help menu to open Recorder Help.

 - You can use two methods to reduce the number of keystrokes required

   to switch between applications. You can use Task List to display a

   list of all applications currently running, or you can assign a

   shortcut key to each application. Task List can be invoked by

   pressing CTRL+ESC, or by choosing Switch To from any application's

   Control menu. Application shortcut keys can be assigned by creating

   an icon for the application in Program Manager and using the

   Properties command on the File menu. For more information on Task

   List and shortcut keys, see the "Microsoft Windows for Workgroups

   User's Guide."

                       GETTING MORE INFORMATION

                       ========================

Information from Microsoft

==========================

For more information on Microsoft products and services for people

with disabilities, contact Microsoft Consumer Sales at one of the

following numbers:

   (800) 426-9400       Voice telephone

   (800) 892-5234       Text telephone

Third-Party Product Information

================================

The Trace R&D Center at the University of Wisconsin-Madison produces a

book and a compact disc (CD) that describe products that help people

with disabilities use computers. The book is titled "ResourceBook" and

contains nearly 500 pages of descriptions and photographs of

approximately 2,000 aids. The CD provides a database of more than

12,000 products and other information for people with disabilities. It

is issued twice a year and is also available in many public libraries.

You can contact the Trace R&D Center at the following address and

phone and fax numbers:

   Trace R&D Center

   S-151 Waisman Center

   1500 Highland Avenue

   Madison, WI  53705-2280

   (608) 263-2309     Voice telephone

   (608) 263-5408     Text telephone

   (608) 262-8848     Fax

Assistive Technology Programs

=============================

For general information and recommendations about how computers can

help specific individuals, customers should consult a trained

evaluator who can best match the individual's needs with the available

solutions. An assistive technology program in your area can provide

referrals to programs and services available to you. To locate the

assistive technology program nearest you, contact the Center for

Developmental Disabilities at the following address and phone and fax

numbers:

   National Information System

   Center for Developmental Disabilities

   University of South Carolina

   Benson Building

   Columbia, SC  29208

   (800) 922-9234,   Voice or text telephone, outside South Carolina

   extension 301

   (800) 922-1107    Voice or text telephone, in South Carolina

   (803) 777-6222    Voice or text telephone, outside the U.S.

   (803) 777-6058    Fax

TO OBTAIN THIS APPLICATION NOTE

===============================

 - 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 WG0788, download

   WG0788.TXT.

 - 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.

Additional reference words: 3.10 3.11


WFWG 3.11 Err Msg: Error 2138: The Workstation Service...

Article ID: Q107572

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

--------------------------------------------------------------------

SYMPTOMS

========

If you try to run an MS-DOS-based application in an MS-DOS virtual machine

(VM), the program may not start, or you may receive the following error

message:

   Error 2138: The workstation service has not been started.

CAUSE

=====

This error can be caused by running an application that calls the

DosMakeMailslot function after you have started the real-mode redirector.

RESOLUTION

==========

Rather than using the real-mode redirector, use the protected-mode

redirector (virtual redirector).

MORE INFORMATION

================

The error message is misleading since you have started the workstation

services.

When running the real-mode redirector, mailslots are not supported in

virtual machines.

Additional reference words: 3.11 VxD


Err Msg: Error Loading PROTMAN.DOS After Using SETUP /H

Article ID: Q107574

------------------------------------------------------------

The following information applies to:

 - Microsoft Windows for Workgroups version 3.11

------------------------------------------------------------

SUMMARY

=======

After you run SETUP /H with Windows for Workgroups 3.11 and reboot the

machine, you may receive the following error message after the NET START

command is run from the AUTOEXEC.BAT file:

   PRO0011E: Equal sign missing between keyword and value

   Error loading device driver PROTMAN.DOS

MORE INFORMATION

================

SETUP /H:<FILE>, where <FILE> is the name of the system settings file, is a

batch mode setup process that sets up Windows for Workgroups with little or

no user interaction. SETUP.SHH, located on Disk 1, is the systems settings

template that can be copied or modified to create a custom system settings

file.

This error message occurs when the SETUP.SHH file is missing the

[protocol.ini] section, which tells Setup which sections from the SETUP.SHH

file to delete after it creates the new PROTOCOL.INI file. This results in

invalid sections that the NET command cannot read being written to the

PROTOCOL.INI file. Removing these unnecessary sections in the PROTOCOL.INI

file corrects this problem.

The [protocol.ini] section in the SETUP.SHH file was not required in

installations prior to Windows for Workgroups 3.11.

Additional reference words: 3.11 protman setup/h


WFWG: Adapter Media Type Information Is Incorrect

Article ID: Q107575

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

--------------------------------------------------------------------

SUMMARY

=======

On page 146 of the Microsoft Workgroup Add-On for Windows "User's Guide,"

the "Computers or NetWare servers are not listed" section incorrectly

states that an improper Adapter Media Type setting may cause NetWare

servers to be missing from the Connect dialog box.

MORE INFORMATION

================

This information is true only if you are using MSIPX.COM.

The correct frame type is required in order to connect to NetWare servers

or other Windows for Workgroups machines that are running the IPX/SPX

compatible protocol. The frame type should be set to the same type as your

NetWare servers. You must configure both your real-mode protocol (IPXODI)

and, if it is installed, the protected-mode IPX/SPX Compatible protocol.

For example, if your NetWare servers are set up for the ETHERNET_802.2

frame type, you must configure the IPX/SPX Compatible protocol on all

Windows for Workgroups machines for ETHERNET_802.2. You also must configure

your real-mode protocol used to connect to the file server for the

ETHERNET_802.2 frame type. To do this, either place the "Frame Type

ETHERNET_802.2" line first in the Link Driver section of the NET.CFG file,

or specify it on the Protocol line in the Link Driver section.

Additional reference words: 3.11 wfw wfwg frametype frame_type


WFW Mail Will Not Cache a Blank Password

Article ID: Q107576

-----------------------------------------------------------------

The following information applies to:

 - Microsoft Windows for Workgroups version 3.11

-----------------------------------------------------------------

SYMPTOMS

==========

When you start Microsoft Windows for Workgroups Mail and are prompted for

the password, an option called "Remember Password" is available. This

option caches your password so that the password dialog box no longer

appears when you start Mail. However, if the Password box is blank and you

select Remember Password, the password is not cached and you are prompted

for the password each time you start Mail.

CAUSE

=====

In Windows for Workgroups 3.11, Workgroups Mail cannot cache a blank

password.

WORKAROUND

==========

There is currently no resolution other than not using a blank password. If

you choose a valid password, it is cached and you don't have to login each

time you start Mail.

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 as it becomes available.

Additional reference words: 3.11 wfw wfwg


Using Novell NetWare's RPRINTER with WFWG 3.11

Article ID: Q107577

--------------------------------------------------------------------

The information in this article applies to:

- Microsoft Windows for Workgroups version 3.11

--------------------------------------------------------------------

This article contains information about the use of 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.

SUMMARY

=======

With Windows for Workgroups 3.11, RPRINTER can be used successfully under

certain conditions. If you run the RPRINTER utility without print sharing,

RPRINTER, Windows for Workgroups 3.11, and NetWare 3.x or 4.x can coexist

with minimal difficulty, as long as you do not send simultaneous print

jobs. Problems may occur if multiple print jobs are sent from different

workstations and you are sharing printers. On larger networks, this is not

realistic. The only workaround is to use Windows for Workgroups print-

sharing capabilities without RPRINTER or vice versa.

   NOTE: With Windows for Workgroups 3.1, RPRINTER could not be used

   successfully. According to Novell's Tech Bulletin TB.P.303, titled

   "Microsoft Windows for Workgroups and Novell NetWare," using RPRINTER

   with Windows for Workgroups 3.1 would cause the machine to stop

   responding (hang). Novell has no solution or work around at this time.

MORE INFORMATION

================

Although you can use RPRINTER with Windows for Workgroups 3.11, you may

encounter problems. For example, if you share a local printer that is being

serviced by RPRINTER and several Windows for Workgroups workstations send

multiple print jobs simultaneously to this shared printer, the following

error message may appear:

   <Windows File Server> is attempting to use the LPTx device which Windows

   is currently using. Do you want 'Windows File Server' to take control of

   the device?

   YES or NO?

If you respond YES, the jobs queued in Print Manager should continue

printing, followed by those in the NetWare queue; however, choosing YES

causes the screen to turn black (and remain so after the print jobs have

been completed). Pressing CTRL+ALT+DEL and then ESC may restore the video

display.

Even if you don't receive this error message, print jobs may be mixed

together and/or have garbled output from the two separate print queues.

REFERENCES

==========

Novell's Tech Bulletin TB.P.303

Additional reference words: 3.11 wfw wfwg wfw311 incompatible compatible

LPT1 LPT2 LPT3 not supported blue screen


MS-DOS Virtual Machine Hangs with Full Redirector Loaded

Article ID: Q107578

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

--------------------------------------------------------------------

SYMPTOMS

========

If you are using Windows for Workgroups 3.11 with Novell connectivity, an

MS-DOS virtual machine (VM) may stop responding (hang) if a NET START FULL

command is issued before opening Windows for Workgroups in enhanced mode.

WORKAROUND

==========

To work around this problem, do one of the following:

 - Do not start the full real-mode redirector at MS-DOS before loading

   Windows.

   -or-

 - Use the NET START command instead.

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 as it becomes available.

Additional reference words: 3.11 wfw wfwg hangs locks logo screen

novel network 386 enhanced mode


Novell: Direct Hosting Works on ODI Drivers Only

Article ID: Q107579

--------------------------------------------------------------------

The following information applies to:

 - Microsoft Windows for Workgroups version 3.11

--------------------------------------------------------------------

SUMMARY

=======

If you have Windows for Workgroups 3.11 running on a Novell network,

Windows for Workgroups will support direct hosting only on machines

running Novell's ODI drivers.

MORE INFORMATION

================

Direct hosting is a new feature in Windows for Workgroups 3.11 that allows

the virtual redirector to interface with the IPX/SPX Compatible protocol,

bypassing NetBIOS. This new technology allows the redirector to transfer

data faster across the network.

For direct hosting to work correctly, the IPX/SPX Compatible protocol must

be installed. This protocol cannot be installed on machines running IPX.COM

or ArcNet; therefore, direct hosting does not work on these machines.

Additional reference words: 311 novell


Net Watcher Event Log Does Not Clear when Scroll Bars Present

Article ID: Q107580

-------------------------------------------------------------------

The information in this article applies to:

- Microsoft Windows for Workgroups version 3.11

-------------------------------------------------------------------

SYMPTOMS

========

When you press the Clear button in the View Event Log window of Net

Watcher, sometimes the event log may not clear.

This problem occurs only when scrolling is required to see all the events

in the log.

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 as it becomes available.

MORE INFORMATION

================

Steps to Reproduce Problem

--------------------------

1. Open the Net Watcher application.

2. From the Connection menu, choose View Event Log.

3. In the View Event Log window, choose the Clear button.

The hard disk spins, but there is no change in the display. The scroll bar

resets to the top position, but the events still display.

The display should clear when you choose the Clear button. (This does occur

if you move the scroll bar.

Additional reference words: 3.11


NET USE in VM with NetWare Diskless Workstation

Article ID: Q107581

----------------------------------------------------------------

The information in this article applies to:

- Microsoft Windows for Workgroups version 3.11

----------------------------------------------------------------

SUMMARY

=======

If you install Windows for Workgroups 3.11 using the SETUP /N command on a

workstation without a hard disk (a "diskless" workstation), and you then

run a NET USE command in a Windows for Workgroups virtual machine (VM), all

Novell NetWare drive mappings, all Windows for Workgroups drive

connections, and all Windows for Workgroups printer connections are

displayed (in that order).

MORE INFORMATION

================

On a computer with a hard disk drive and a SETUP /N configuration (or a

local installation of Windows for Workgroups with Novell NetWare), a NET

USE command in a Windows for Workgroups VM displays only the existing

Windows for Workgroups drive and printer connections.

However, all network connections (both NetWare mappings and Windows for

Workgroups connections) are displayed in a Windows for Workgroups VM if the

following conditions are true:

 - You have a SETUP /N configuration on a diskless NetWare workstation as a

   second network under Windows for Workgroups.

 - All startup files are on a boot disk image.

 - All startup files are on the network.

 - The Windows directory is located on the network.

 - All Windows files are on the network.

 - All above directories and files must be in the NetWare search

   paths.

Additional reference words: 3.11 wfw311 wfw wfwg environment map

maproot net view


Mail Components Are Always Installed

Article ID: Q107582

--------------------------------------------------------------------

The information in this article applies to:

- Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

SUMMARY

=======

During Microsoft Windows for Workgroups Setup, the Workgroups Mail and

Schedule+ component files (FRAMEWRK.DLL, MSSFS.DLL, and MAILSPL.EXE) are

installed even if the Mail and Schedule+ programs are not.

MORE INFORMATION

================

During installation of Windows for Workgroups 3.11, you can choose the

Custom Install option. With this option, you can elect not to install

certain components of Windows for Workgroups, including Mail and Schedule+.

If you chose not to install these two programs, certain Mail files are

still installed:

 - FRAMEWRK.DLL is the Workgroup Applications framework layer.

 - MSSFS.DLL is the Workgroup Mail Shared File System Transport Provider

   and is used to send and receive messages to and from the Postoffice

   database.

 - MAILSPL.EXE is the program in Workgroups Mail that spools messages from

   the Outbox to the Postoffice and checks for new messages, which it

   places in the Inbox.

These files are considered Windows dynamic link libraries (DLLs) that other

applications depend on and therefore are installed regardless of whether

Mail and Schedule+ are installed.

Additional reference words: 3.11 wfw wfwg remove components install

setup


No Servers If Real-Mode Redirector Started Before WFWG 3.11

Article ID: Q107583

--------------------------------------------------------------------

The information in this article applies to:

- Microsoft Windows for Workgroups version 3.11

--------------------------------------------------------------------

SUMMARY

=======

Server functionality is not available in Windows for Workgroups 3.11 if the

real-mode redirector is started before Windows for Workgroups 3.11 is

started. This behavior differs from that of version 3.1, which does support

running the protected-mode server over the real-mode redirector.

MORE INFORMATION

================

The behavior is different because Windows for Workgroups 3.11 is using a

new protected-mode installable file system manager (IFSHLP.SYS) that does

not work with the real-mode redirector. You must use the NET STOP

WORKSTATION command before you start Windows for Workgroups. (This also

saves conventional memory.)

Additional reference words: 3.11 wfw wfwg net start full realmode share

as not available cannot missing


Windows for Workgroups Protocol Limits

Article ID: Q107597

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

---------------------------------------------------------------------

Windows for Workgroups 3.1 and 3.11 have a limit of four protocols per

network card and a maximum of eight protocols that can be installed at any

given time.

If you are using NDIS 2.0 drivers and the NetBEUI protocol in Windows for

Workgroups 3.11, you can add only two additional protocols. This differs

from version 3.1, in which you can load up to four protocols, including

NetBEUI. If you are using all NDIS 3.0 drivers in Windows for Workgroups

3.11, you can use four protocols per card.

This limitation exists because the Windows for Workgroups 3.11 NetBEUI

protocol requires two bindings to the protocol manager: one binding for

real mode (NDISHLP.SYS) and one for protected mode (NETBEUI.386). If the

NetBEUI protocol is removed, up to four other protocols can be used.

Additional reference words: 3.11 wfw wfwg limit protocols max maximum grey

gray greyed grayed add protocol button total


WFWG Err Msg: Warning: A Serious Disk Error Has Occurred...

Article ID: Q107598

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

--------------------------------------------------------------------

SYMPTOMS

========

In Microsoft Windows for Workgroups, you may encounter the following error

message:

   WARNING: A serious disk error has occurred while reading from/writing to

   your hard disk. Some data may have been corrupted. Your system has been

   stopped to prevent additional data loss. Call product support for

   assistance.

CAUSE

=====

This error may be caused by a corrupted BLOCKDEV driver or 32-bit disk

access driver in your SYSTEM.INI file.

RESOLUTION

==========

To correct this problem, do the following:

1. Disable 32-Bit Disk Access.

2. Reinstall Windows for Workgroups 3.11.

Additional reference words: 3.11 wfw wfwg fastdisk vfat pss error


Using Novell's ODINSUP and NETx with Windows

Article ID: Q107632

------------------------------------------------------------------------

The information in this article applies to:

- Microsoft Windows for Workgroups version 3.11

------------------------------------------------------------------------

SUMMARY

=======

This article provides instructions on how to install the Novell ODINSUP

driver to work with Windows for Workgroups 3.11. Novell's ODINSUP driver

allows NDIS 2 protocols (such as MS TCP/IP) to run on top of Novell's ODI

drivers. This behavior is similar to that of the MSODISUP driver that comes

with Windows for Workgroups 3.11. The only 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 NETx redirector. By doing this, you can use NDIS 2 protocols

(such as MS TCP/IP or 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 3COM 3c509

Etherlink III.

Before You Begin

----------------

Since this configuration requires the Novell IPXODI drivers, you must have

your machine set up and attached to a Novell server using IPXODI.COM at MS-

DOS before proceeding to the "Setup Instructions" section below. You should

also set up a working NET.CFG file in the same directory from which you

load LSL.COM

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 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. (Note that for the

   examples in this article, we chose the Etherlink III network adapter.)

   Next, in the same Network Drivers dialog box, choose Setup and choose

   Real Mode NDIS Driver. This is important because even though you are

   actually running an ODI driver with ODINSUP, Windows for Workgroups

   think you are running an NDIS driver. Choose OK and continue with

   Setup. Ignore the error messages about ODI drivers. After you finish

   Setup, 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 MS TCP/IP package.

   NOTE: If there are any other NDIS 2 protocols (such as MS DLC) you want

   to install, install those 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 the MS TCP/IP installation, edit the SYSTEM.INI file

   and remove the NDIS 2 driver, <ELNK3.DOS>, from the netcard= line of

   the [Network Drivers] section.

   NOTE: If you are using a different network card, the NDIS network card

   driver (<ELNK3.DOS> in the above example) will be different.

3. Edit the CONFIG.SYS file and set LASTDRIVE=P. This allows you to use

   the drive letters before P to connect to other Windows for Workgroups

   servers and driver letters after P to connect to NetWare servers. You

   can adjust this to fit your needs; however, Windows for Workgroups

   drives can map only up to and including the drive to which LASTDRIVE

   has been set.

4. Edit the AUTOEXEC.BAT file so that it contains the following lines:

      C:\WINDOWS\NET INIT

         <==This loads protman and NDIS protocols>

      C:\<PATH>\LSL.COM

      C:\<PATH>\<your network card's ODI MAC driver>.COM

      C:\<PATH>\ODINSUP.COM

      C:\WINDOWS\NET START NETBIND (This binds the protocols to ODINSUP.)

      C:\<PATH>\IPXODI.COM

      C:\<PATH>\NETX.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 <n> (where <n> is the one-digit interrupt number.)

         MEM <nnnnn> (where <nnnnn> is the five-digit memory address.)

         PORT <nnn> (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 have 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_<xxxx>" entries (where <xxxx> will probably be

   <802.3> or <II>).

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=<MS$ELNK3> (where <MS$ELNK3> corresponds to your NDIS MAC

                         driver; in this case, ELINK3.DOS. The semicolon

                         comments out this line.)

   BINDINGS=<x3c509> (where <x3c509> corresponds to your ODI MLID driver;

                      in this case, 3c509.COM. The "x" must be added if the

                      ODI MLID filename begins with a numeral.)

   [NETBEUI]

   ;BINDINGS=<MS$ELNK3> (where <MS$ELNK3> corresponds to your NDIS MAC

                         driver; in this case, ELINK3.DOS. The semicolon

                         comments out this line.)

   BINDINGS=<x3c509> (where <x3c509> corresponds to your ODI MLID driver;

                      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=<MS$ELNK3> (where <MS$ELNK3> corresponds to your NDIS MAC

                         driver; in this case, ELINK3.DOS. The semicolon

                         comments out this line.)

   BINDINGS=<x3c509> (where <x3c509> corresponds to your ODI MLID driver;

                      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=<MS$ELNK3> (where <MS$ELNK3> corresponds to your NDIS MAC

                         driver; in this case, ELINK3.DOS. The semicolon

                         comments out this line.)

   BINDINGS=<x3c509> (where <x3c509> corresponds to your ODI MLID driver;

                      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, 3COM's 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 Network 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 "NWLink 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=P

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\NETX

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

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 the Novell ODINSUP.COM driver,

contact Novell Technical Support or on the Novell CompuServe forums.

The products included here are manufactured by vendors independent of

Microsoft; we make no warranty implied or otherwise regarding these

products' performance or reliability.

Additional reference words: 3.11 wfwg wfw 3rdparty


How to Disable Write Caching for the 32-Bit File System

Article ID: Q107645

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SUMMARY

=======

Windows for Workgroups version 3.11 caches disk writes by default when the

32-bit file system is enabled. This includes MS-DOS DoubleSpace 6.2

volumes; however, it does not include third-party disk-compression systems.

MORE INFORMATION

================

To disable write caching with the 32-bit file system, add the following

line to the [386Enh] section of the SYSTEM.INI

   ForceLazyOff=<drivelist>

where <drivelist> is the list of drives in which you want to disable write

caching. (Do not use any delimiters or spaces.) For example, the line

     ForceLazyOff=CDF

would disable write caching on drives C, D, and F.

For more information about the 32-bit file system, query on the following

words in the Microsoft Knowledge Base:

   wfwg and vfat and 32-bit

Additional reference words: 3.11


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, <ELNK3.DOS>, from the netcard= line of the [Network

   Drivers] section.

   NOTE: If you are using a different network card, the NDIS network card

   driver (<ELNK3.DOS> 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:\<PATH>\LSL.COM

      C:\<PATH>\<your network card's ODI MAC driver>.COM

      C:\<PATH>\ODINSUP.COM

      C:\WINDOWS\NET START NETBIND (This binds the protocols to ODINSUP.)

      C:\<PATH>\IPXODI.COM

      C:\<PATH>\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 <n> (where <n> is the one-digit interrupt number)

         MEM <nnnnn> (where <nnnnn> is the five-digit memory address)

         PORT <nnn> (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

   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_<xxxx>" entries (where <xxxx> will probably be

   <802.2>, <802.3>, or <II>).

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=<MS$ELNK3> (where <MS$ELNK3> corresponds to your NDIS MAC

                            driver; in this case, ELINK3.DOS. The semicolon

                            comments out this line.)

      BINDINGS=<x3c509> (where <x3c509> corresponds to your ODI MLID

                         driver; in this case, 3c509.COM. The "x" must be

                         added if the ODI MLID filename begins with a

                         numeral.)

      [NETBEUI]

      ;BINDINGS=<MS$ELNK3> (where <MS$ELNK3> corresponds to your NDIS MAC

                            driver; in this case, ELINK3.DOS. The semicolon

                            comments out this line.)

      BINDINGS=<x3c509> (where <x3c509> corresponds to your ODI MLID

                         driver; 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=<MS$ELNK3> (where <MS$ELNK3> corresponds to your NDIS MAC

                            driver; in this case, ELINK3.DOS. The semicolon

                            comments out this line.)

      BINDINGS=<x3c509> (where <x3c509> corresponds to your ODI MLID

                         driver; 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=<MS$ELNK3> (where <MS$ELNK3> corresponds to your NDIS MAC

                            driver; in this case, ELINK3.DOS. The semicolon

                            comments out this line.)

      BINDINGS=<x3c509> (where <x3c509> corresponds to your ODI MLID

                         driver; 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.

Additional reference words: 3.11 wfwg wfw 3rdparty


32-Bit File Access Causes ScanDisk to Report Error

Article ID: Q107651

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

--------------------------------------------------------------------

SYMPTOMS

========

After you run Windows for Workgroups version 3.11 on an MS-DOS 6.2

DoubleSpace-compressed drive with 32-bit file access enabled, the MS-DOS

ScanDisk utility may report the following error when run at the MS-DOS

command prompt:

   ScanDisk found <nnnn> bytes of data on drive <x> that might be one or

   more lost files or directories, but which is probably just taking

   up space.

where <nnnn> equals the number of bytes of lost files or directories,

and <x> equals the logical drive ScanDisk was scanning.

   NOTE: ScanDisk should not be run from the MS-DOS command prompt in

   Microsoft Windows or Windows for Workgroups. It should be run directly

   from MS-DOS. If you must run ScanDisk from within Windows, use the

   /CHECKONLY switch. This switch prevents ScanDisk from attempting to

   repair any damage while Windows is running.

CAUSE

=====

This error message is caused by a problem in Windows for Workgroups 3.11.

32-bit file access writes buffers in the order they are used, meaning the

first information into the buffer is the first information out. 32-bit file

access also tries to improve access speed by finding contiguous used

buffers and writing them together. If the two optimization schemes both try

to clean the buffer simultaneously, an erroneous extra entry in the

DoubleSpace file allocation table (MDFAT) can occur.

This problem can also occur when 32-bit file access flushes the entire

volume. Buffers are written sequentially according to their physical

location. This optimization has no effect on a compressed volume (since

there is no physical-to-logical relationship) and can result in erroneous

entries in the MDFAT.

RESOLUTION

==========

No data loss occurs with this error. If you choose to correct the problem,

ScanDisk repairs the volume and creates the standard CHKDSK files

(FILEnnnn.CHK), which can be deleted. ScanDisk may also report that there

are sections of the DoubleSpace volume not being used by any files but

marked as unusable; it can repair these as well.

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 as it becomes available.

Additional reference words: 3.11 vfat mdfat lost entry


WFWG 3.11 Err Msg: Executable Not Found

Article ID: Q107798

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SYMPTOMS

========

The following error message may appear when you use the WIN.COM /D:T

diagnostic switch to load Windows for Workgroups 3.11 without enhanced 386

mode functions.

   Executable not found.

CAUSE

=====

This error occurs if the WSWAP.EXE file is not located in the Windows

SYSTEM subdirectory.

RESOLUTION

==========

Use the EXPAND.EXE utility to expand a new copy of WSWAP.EXE from the

original Windows for Workgroups 3.11 disks. The WSWAP.EXE file is listed as

WSWAP.EX_ on the following disks:

Full Retail Version      Upgrade Version

-------------------      ---------------

1.2-MB  Disk #7          1.2-MB  Disk #7

1.44-MB Disk #6          1.44-MB Disk #6

To obtain more information on using the EXPAND.EXE utility, type the

following at an MS-DOS command prompt and then press ENTER:

   expand /?

MORE INFORMATION

================

Windows for Workgroups 3.11 can be loaded without the 386 enhanced mode

drivers by using the following command:

   WIN /D:T

Loading Windows for Workgroups 3.11 with this command line may be helpful

when troubleshooting issues associated with the 386 enhanced mode drivers.

When 386 enhanced mode drivers are not loaded, the WSWAP.EXE terminate-and-

stay-resident (TSR) program is used to allow Windows to switch between MS-

DOS-based applications and Windows. This file must be present when you load

Windows with the command line shown above.

The WSWAP.EXE is installed to the Windows SYSTEM subdirectory by the

Windows Setup program and should always be present unless it has been

manually deleted from the hard disk.

Additional reference words: 3.11 wfw wfwg error DOSX.EXE hangs locks


RAS May Not Function on a Network Installation

Article ID: Q107809

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

--------------------------------------------------------------------

SYMPTOMS

========

When you run a network installation (SETUP /N) of Microsoft Windows for

Workgroups version 3.11, starting Remote Access Services (RAS) causes the

following error:

   Cannot load phone book or RAS manager data. Error 657: the device .INF

   file could not be opened.

STATUS

======

Microsoft is researching this problem and will post new information here in

the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

================

If the following two files are marked read-only, RAS generates the above

error message:

   pad.inf and switch.inf

RAS functions properly if you remove the read-only attribute on the above

two files. (If the shared directory is located on a server, full

permissions must also be granted.)

Additional reference words: 3.11


Err Msg in MS-DOS Session: Cannot Write to Drive C:/Cancel...?

Article ID: Q107810

--------------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

--------------------------------------------------------------------------

When you type "exit" (without the quotation marks) at an MS-DOS prompt to

end an MS-DOS session within Windows for Workgroups 3.11, you may receive

the following error:

   Cannot Write to Drive C: /Cancel/Retry?

This error is caused by a corrupted DOSAPP.INI file; deleting this file

corrects the problem.

Additional reference words: 3.11 WRITING ERROR RETRY


Several WFW<nn> Files in Your Windows Directory

Article ID: Q107811

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

--------------------------------------------------------------------

WFW<nn> files (where <nn> is a sequential number) may appear in your

Windows directory. These files are copies of your system files (CONFIG.SYS,

AUTOEXEC.BAT, SYSTEM.INI, and WIN.INI). Setup creates these files so that

it can make modifications to your system. When Setup is finished, it

removes these files.

If Setup stops responding (hangs) or you stop Setup before it has completed

installation, Windows does not remove these files from your system. You

should manually remove them after Setup completes successfully.

Additional reference words: 3.10 network setup


NET START FULL Invokes Intel SatisFAXtion Fax Popup

Article ID: Q107815

------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

------------------------------------------------------------

SYMPTOMS

========

If the SatisFAXtion Fax Popup utility (FAXPOP) is loaded in your

AUTOEXEC.BAT file, the NET START FULL command invokes that utility.

Pressing the ESC key to cancel it returns you to the MS-DOS command prompt.

The NET START FULL command then proceeds to run.

CAUSE

=====

The SatisFAXtion Fax Popup utility is a terminate-and-stay-resident program

that allows you to send faxes from any MS-DOS-based application (such as MS-

DOS Editor or MS-DOS Shell). When NET START FULL is run, FAXPOP traps it

and executes its own fax-sending utility.

WORKAROUND

==========

At this time, the only way to work around this problem is to remove FAXPOP

from your AUTOEXEC.BAT file.

NOTE: Changing IRQs or I/O addresses does not correct this problem.

MORE INFORMATION

================

Intel SatisFAXtion is manufactured by Intel, a vendor independent of

Microsoft; we make no warranty, implied or otherwise, regarding this

product's performance or reliability.

Additional reference words: 3.11 wfw wfwg popup cas board


WFWG Setup Installs Older Logitech Mouse Driver

Article ID: Q107816

-------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

-------------------------------------------------------------------

The Logitech Mouse driver supplied with Windows for Workgroups 3.11

is version 6.02. The current version available from Logitech is 6.12

(dated 5/22/92) and supports command-line switches that are needed by

some older MS-DOS-based programs that use three buttons.

The Windows for Workgroups 3.11 Setup program overwrites this newer

driver with version 6.02.

Additional reference words: 3.11 set up wfwg LOGITECH DRIVER 6.02


WFWG: Can't Connect to Share That Has Multiple Passwords

Article ID: Q107820

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

----------------------------------------------------------------------

SYMPTOMS

========

After creating a share with multiple passwords, one password for the

read-only option and the other for the write option for example, you

cannot log on to both shares simultaneously.

CAUSE

=====

This occurs because the redirector is using the same universal naming

convention (UNC) path for both sessions.

This functionality is by design.

WORKAROUND

==========

Disconnect from the share with one option password if you want to connect

to the same share with another option password.

For example, if you have the following shares set up:

 - "D" connecting to \\MYSERVER\MYSHARE with read-only access

   -and-

 - "E" connecting to \\MYSERVER\MYSHARE with read/write access

You must disconnect from "E" if you want to have read-only access.

Conversely, you must disconnect from "D" if you want to have read/write

access.

Additional reference words: 3.11 unc wfwg


Incorrect Sort Order in File Manager with Some Languages

Article ID: Q107823

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows operating system version 3.1

 - Microsoft Windows for Workgroups version 3.1

--------------------------------------------------------------------

SYMPTOMS

========

If you have the Swedish, Norway, Finnish, or Icelandic keyboard drivers

installed for Windows, you may see an incorrect sort order in File Manager.

CAUSE

=====

The incorrect sort order is caused by a problem with the LANGSCA.DLL file

in Windows 3.1 and Windows for Workgroups 3.1. (The LANGSCA.DLL file is the

Finnish, Icelandic, Norwegian, and Swedish language driver used in Windows

and Windows for Workgroups.)

STATUS

======

This problem was corrected in Windows for Workgroups version 3.11.

MORE INFORMATION

================

Steps to Reproduce Problem

--------------------------

1. In Control Panel, choose the International icon.

2. Select Finnish, Icelandic, Norwegian, or Swedish in the Language box,

   then choose OK.

3. Open File Manager and select a directory that contains files beginning

   with the letters "V" and "W."

4. From the View menu, choose Sort By Name.

The letters "V" and "W" are treated the same. For example, you may see a

sort order such as:

   va.txt

   wa.txt

   we.txt

   vi.txt

   wx.txt

   vz.txt

Additional reference words: 3.10 3.11 list winfile


Upgrade over IBM LAN Server Leaves Drivers in Startup Files

Article ID: Q107840

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SYMPTOMS

========

When you run Windows for Workgroups 3.11 for the first time after

installing it on a machine that was previously configured to use IBM LAN

Server networking functionality, you may receive the following message:

   The protocol manager could not be opened.

   The return code is 3.

   Error in loading  -  Press F1 to continue.

   Can not find Protocol Manager

CAUSE

=====

This error occurs if any of the following IBM LAN Server components remain

in the startup files after you install Windows for Workgroups 3.11 and

select Microsoft Windows Network peer-to-peer networking functionality:

   CONFIG.SYS

   ----------

   DEVICE=C:\LSP\DXMA0MOD.SYS XXX

   DEVICE=C:\LSP\DXMJ0MOD.SYS

   AUTOEXEC.BAT

   ------------

   C:\LSP\NETBIND

RESOLUTION

==========

If you find the above items in the startup files after installing Windows

for Workgroups 3.11 and selecting Microsoft Windows Network peer-to-peer

networking functionality, remove them with an ASCII text editor, such as

Microsoft Windows Notepad.

MORE INFORMATION

================

When you install Microsoft Windows for Workgroups 3.11, you can choose to

install Microsoft Windows Network peer-to-peer networking functionality or

Windows client networking functionality for another network (such as IBM

LAN Server). If you decide to install the Microsoft Windows Network, any

recognized components of other networks found in the startup files are

replaced with the equivalent Windows for Workgroups drivers. However, some

components, such as the IBM LAN Server components listed above, may not be

recognized by Setup and therefore must be manually removed.

Additional reference words: 3.11


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=<filename1> <filename2>

   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).

Additional reference words: 3.11 wfwg errors


WFWG Err Msg: There Is Not Enough Memory Available

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 may 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.

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.

Additional reference words: 3.11 wfw wfwg browsemaster unc universal

naming convention browselist


NDIS2 Drivers Load but NDIS3 Drivers Don't--Errors 6200 & 58

Article ID: Q107995

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

--------------------------------------------------------------------

SYMPTOMS

========

When you start Windows for Workgroups, you may receive one of the following

error messages:

 - Error 6200: Adapter <adapter-name> not found

   -or-

 - Error 58: The network has responded incorrectly

NOTE: These errors usually occur in protected mode; real-mode networking

usually loads correctly.

CAUSE

=====

The above error messages may be caused by an incorrect I/O base address, an

incorrect RAM address, or an improper IRQ setting in the PROTOCOL.INI file.

These errors may be generated if the Transport= line in the [386Enh]

section contains protocols that are not in use. For example, if the

Transport= line contains the following:

   Transport=netbeui.386,nwlink.386,nwnblink.386

but the only protocol in use is NetBeui, the errors may occur.

RESOLUTION

==========

Correct the invalid setting.

If the Transport= line contains invalid references, remove them (that is,

remove the references to nwlink.386, nwnblink.386, and IPX/SPX compatible

transport).

MORE INFORMATION

================

The NDIS2 network interface card (NIC) driver may not rely on the

PROTOCOL.INI settings; however, the NDIS3 NIC driver relies almost

exclusively on these settings.

Additional reference words: 3.11 wfw wfwg error message err Msg enhanced

mode protect mode NDIS tshoot


WFWG 3.11: Real-Mode Redirector and Direct Hosting

Article ID: Q107996

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SYMPTOMS

========

If Windows for Workgroups 3.11 has been configured to provide Novell

NetWare connectivity and you try to connect to a Windows for Workgroups

3.1, 3.11, or Windows NT 3.1 server with the real-mode redirector, the

following error may occur:

   Error 53:  The computer name specified in the network path

              cannot be located.

This error may occur when you run a NET USE or NET VIEW command with the

Windows for Workgroups 3.11 real-mode redirector. This error may also occur

when you are using the real-mode redirector even though no error occurs

when you are connected to the same servers from within Windows for

Workgroups 3.11 while using the protected-mode redirector.

CAUSE

=====

When Windows for Workgroups 3.11 is configured to provide Novell NetWare

connectivity, the real-mode redirector uses the IPX transport provided by

the Novell NetWare IPXODI driver.

A relationship called direct hosting is formed between the real-mode

redirector and the IPX transport. Direct hosting allows data to be

transferred between these two layers without requiring the presence of a

NetBIOS interface.

Under this configuration, you cannot use the real-mode redirector to access

a server unless the server is running an IPX/SPX compatible transport.

RESOLUTION

==========

With this configuration, a Windows for Workgroups 3.11 server must be

configured to use the IPX/SPX Compatible Transport or IPX/SPX Compatible

Transport with NetBIOS to be accessible by the real-mode redirector.

There is no resolution available for a Windows NT server because the NWLink

IPX/SPX Compatible Transport provided with Windows NT requires a NetBIOS

interface that is not provided by the real-mode redirector in Windows for

Workgroups when a direct-hosting relationship exists.

MORE INFORMATION

================

When you are using Microsoft Windows for Workgroups 3.11 in a Novell

NetWare environment, you can install support for Novell NetWare

connectivity in addition to the Microsoft Windows Network.

To install support for Novell NetWare connectivity, select Novell NetWare

(Workstation Shell) as an additional network in the Networks dialog box of

Network Setup. This support also requires selecting one of the following

drivers from the Network Driver dialog box of Network Setup:

   IPXODI Support Driver (ArcNet)

   IPXODI Support Driver (Ethernet)

   IPXODI Support Driver (Token Ring)

This configuration allows Windows for Workgroups 3.11 to enable Novell

NetWare connectivity by interfacing with the IPX transport contained in the

Novell NetWare ODI drivers.

When you use this configuration with the Windows for Workgroups real-mode

redirector to connect to Windows for Workgroups servers, one of the

following protocol drivers should be selected in the Network Drivers dialog

box of Network Setup on the Windows for Workgroups server machine.

   IPX/SPX Compatible Transport

   -or-

   IPX/SPX Compatible Transport with NetBIOS

Installing one of these IPX/SPX compatible transports enables the real-mode

redirector to connect to the Windows for Workgroups server.

Additional reference words: 3.11


WFWG 3.11 PIF Editor Has Standard Mode Command

Article ID: Q107997

----------------------------------------------------------------------

The information in this article applies to:

 - Windows for Workgroups version 3.11

----------------------------------------------------------------------

SYMPTOMS

========

Windows for Workgroups 3.11 PIF Editor allows you to choose Standard Mode

from the Mode menu. Windows for Workgroups 3.11 does not support standard

mode.

CAUSE

=====

This command remains in Windows for Workgroups 3.11 even though all

standard-mode settings are ignored when the PIF file is used. If you choose

Standard Mode, the following message is displayed:

   Windows is not running in standard mode.  The PIF information you

   enter may not be appropriate. Are you sure you want to switch to

   this mode?

If you choose OK, PIF Editor changes to the PIF editing screen for standard

mode.

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 as it becomes available.

Additional reference words: 3.11


Using Wollongong TCP/IP with Windows for Workgroups 3.11

Article ID: Q108007

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

----------------------------------------------------------------------

SUMMARY

=======

The Wollongong Group's Pathway Runtime and Pathway Access version 1.2,

which comes with an RFC-compliant NetBIOS interface, can be used with

Windows for Workgroups 3.11. Pathway Runtime is the Wollongong TCP/IP

stack, and Pathway Access is a set of TCP/IP utilities provided by

Wollongong. (The TCP/IP stack is a real-mode stack and operates with NDIS 2

drivers.)

This article provides the steps needed to install Pathway Runtime 1.2 on

Windows for Workgroups 3.11.

MORE INFORMATION

================

To install Pathway Runtime on Windows for Workgroups, do the following:

WARNING: Although this procedure allows you to run Pathway Runtime with

Windows for Workgroups version 3.11, it disables the NetBEUI protocol. As a

result, your machine won't be able to view or access any other Windows for

Workgroups machines or LAN Manager servers on the network that are running

NetBEUI exclusively.

1. Install Windows for Workgroups with the default NetBEUI transport.

2. Install Pathway Runtime using PWSETUP.EXE from the setup disk supplied

   with the Wollongong product.

3. Complete the installation using the complete NDIS installation option.

   (For more information, please refer to the Pathway Runtime manual.)

4. After the installation is complete, change the AUTOEXEC.BAT file so

   that the NET INIT command is executed immediately before the NDIS

   command. Replace the PWBIND command with the NET START NETBIND command,

   which comes before the PWTCP command. Remove the NET START line added

   by Windows for Workgroups. The following is an example of the

   AUTOEXEC.BAT file after these changes:

rem #----------------------- The Wollongong Group --------------------#

rem # The following lines are for Pathway Runtime setup. Please DO NOT#

rem # modify or remove any of them. If you DO want to, please run the #

rem # setup program to modify or deinstall Pathway for DOS.           #

SET PATH=C:\PATHWAY;%PATH%

c:\pathway\PWCONFIG -N:65

net init

c:\pathway\ndis -I:5 -D:3

net start netbind

rem if you are not using the bootp protocol comment out the bootp line.

c:\pathway\bootp -d

c:\pathway\pwtcp

c:\pathway\netbios

rem #----------------------- The Wollongong Group --------------------#

5. Make sure that the -I option for the NDIS command matches the IRQ being

   used by the network card. The -D option refers to the section number in

   the PROTOCOL.INI file referring to the network card.

6. Run NETBIOS.EXE after PWTCP.EXE. (NETBIOS.EXE is the RFC-compliant

   driver.)

7. Edit the SYSTEM.INI file in the Windows directory and make the

   following changes:

    a. In the [386enh] section, change the line

          transport=netbeui.386,nwlink.386,nwnblink.386

       to:

          transport=nwlink.386,nwnblink.386

    b. In the [network drivers] section, change the lines

          transport=ndishlp.sys,*netbeui

          LoadRMDrivers=No

       to:

          transport=ndishlp.sys

          LoadRMDrivers=Yes

These changes indicate that the real-mode protocol stack will use Lana 0.

(Pathway Runtime can use Lana 0 only).

8. Edit the CONFIG.SYS file and remark out (using the REM command) the

   entries added by the Pathway Access installation program:

   rem #---------------------- The Wollongong Group ----------------------#

   rem #  The following lines are for Pathway Runtime setup. Please DO NOT#

   rem #  modify or remove any of them. If you DO want to, please run the#

   rem #  setup program to modify or deinstall Pathway for DOS.          #

   rem DEVICE=C:\PATHWAY\PROTMAN.EXE /i:C:\PATHWAY\LANMAN

   rem DEVICE=C:\PATHWAY\LANMAN\ELNK3.DOS

   rem #---------------------- The Wollongong Group ---------------------#

   The only entry needed is:

      Device=c:\Windows\ifshlp.sys

9. Reboot and start Windows.

You can now install Pathway Access by following the instructions provided

by Wollongong.

REFERENCES

==========

Wollongong Pathway Access Release Notes

Windows for Workgroups Resource Kit

The Wollogong products included here are manufactured by a vendor

independent of Microsoft; we make no warranty, implied or otherwise,

regarding these products' performance or reliability.

Additional reference words: 3.11 TCP 3rdparty


NET USE * /HOME Err Msg: The syntax Is Incorrect

Article ID: Q108014

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SYMPTOMS

========

When you run the NET USE * /HOME command, you may receive the following

error message even though you have used the correct syntax:

   The syntax is incorrect.

   For help, type NET USE /?

CAUSE

=====

If the error message is immediately displayed after typing the command and

pressing ENTER, you are probably using incorrect syntax. If the message is

returned after a brief delay (a few seconds), there is a problem with your

Windows NT or LAN Manager home directory configuration.

RESOLUTION

==========

To work around this problem, contact your network administrator to verify

the home directory configuration.

MORE INFORMATION

================

Using NET USE * /HOME from Multiple MS-DOS Command Prompts

----------------------------------------------------------

If you use the NET USE * /HOME command from more than one MS-DOS command

prompt within Windows for Workgroups, your current directory will not be

set correctly. Your current directory will be the root of the server

containing your home directory instead of your default home directory.

Additional reference words: 3.11 errmsg error message


Suffix String Not Available for Microsoft At Work PC Fax

Article ID: Q108025

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SUMMARY

=======

Microsoft At Work PC Fax, which is included with Windows for Workgroups

version 3.11, does not include a suffix string feature.

MORE INFORMATION

================

To send a string after connecting with Microsoft At Work PC Fax, use commas

for pauses, then add the suffix string to the number, as in the following

example:

   1-800-111-2222,,,333

This would dial 1-800-111-2222, wait 6 seconds, and then dial the number

333. The wait time for a comma can be set in the Fax Setup dialog box in

Control Panel. The default wait time is 2 seconds per comma.

For more information about Microsoft At Work PC Fax, query on the following

words in the Microsoft Knowledge Base:

   w_wfw and wfwg and efax

Additional reference words: 3.11


Installing a Banyan VINES Network with WFWG 3.11

Article ID: Q108034

--------------------------------------------------------------------

The information in this article applies to:

- Microsoft Windows for Workgroups version 3.11

--------------------------------------------------------------------

SUMMARY

=======

This article provides information about installing Windows for Workgroups

version 3.11 with a Banyan VINES network. The following versions of Banyan

VINES network operating system software are supported with Windows for

Workgroups 3.11.

   Banyan VINES 4.11 (rev.5)

   Banyan VINES 5.00 (rev.5)

   Banyan VINES 5.52 (rev.5) (Token Ring and Ethernet Support)

Windows for Workgroups 3.11 provides no files to support connectivity to

the Banyan VINES network. To upgrade your current installation to Windows

for Workgroups 3.11, you must first have an existing working connection to

a Banyan VINES server.

MORE INFORMATION

================

Before installing Windows for Workgroups 3.11, the Banyan server must be

updated with all the appropriate patches and modifications. Banyan patches

are available on CompuServe in the Banyan forum (type "go banyan" [without

the quotation marks] at the ! prompt). If you have any questions about

Banyan-related files, or if you are not sure if you have the latest patches

available for your installation, call Banyan VINES technical support at

(800) 222-6926.

Windows for Workgroups 3.11 Setup recognizes Banyan VINES connectivity and

maintains it as the secondary network. Installation should be seamless with

no further action required by the user.

As with previous versions of Windows, it is necessary to be able to log on

to Banyan VINES from MS-DOS before Windows connectivity can be ensured.

The load order of the drivers in your AUTOEXEC.BAT file is important for

maintaining VINES connectivity. If there are any problems during the

upgrade and/or the Banyan login screen does not appear as usual after

rebooting, check for error messages during the boot process and check the

AUTOEXEC.BAT file to ensure the Banyan VINES files are loading and are in

the correct order. The correct files and their order in the AUTOEXEC.BAT

file are:

C:\WINDOWS\NET INITIALIZE - (This command is for Windows for Workgroups

                            3.11. It allows loading the files into memory

                            without invoking them.)

CD\<BANYAN FILES> - (This command changes to the directory where the

                    Banyan files are located. This is necessary because

                    Banyan cannot read the full path and must be in the

                    appropriate directory to load the file.)

BAN /NC - (Loads BAN.EXE without initializing Banyan's communications

          hardware on the system.)

NDISBAN  - (Loads the NDIS-specific portion of the VINES software.)

REDIRALL - (Loads REDIRALL.EXE, which is redirector support for all

            versions of DOS.)

C:\WINDOWS\NET START - (This command from Windows starts the network

                       software.)

ARSWAIT - (This command "Address Resolution Server Wait," holds further

          processing until your computer has been assigned a network

          address by a server. After it sees that your computer has

          received a network address from the network, it exits and allows

          your computer to continue. This function is normally built into

          VINES native drivers, but NDIS requires that this functionality

          be added after the NDIS driver BAN.EXE is loaded.)

Z:LOGIN - (Brings up the Banyan VINES login screen.)

If there are no error messages at startup, but you are having problems in

Windows for Workgroups with VINES connectivity, check the SYSTEM.INI file.

The following entries should be made to the SYSTEM.INI file when you

install Windows for Workgroups 3.11 with Banyan VINES connectivity:

[boot]

secondnet=Z:vines.drv

[boot.description]

secondnet.drv=Banyan VINES (version x.xx(x))

[386Enh]

secondnet=z:vvinesd.386

[Network]

multinet=vines411

REFERENCES

==========

Additional information on Banyan VINES connectivity can be found in the

NETWORK.WRI file and in the Windows for Workgroups Resource Kit version

3.11.

Banyan VINES Technical Support can be reached at (800) 2-BANYAN. To access

the Banyan VINES forum on CompuServe type "go banyan" (without the

quotation marks) at the ! prompt in CompuServe.

For more information, query on the following words in the Microsoft

Knowledge Base:

   win and banyan and vines

Banyan VINES is manufactured by a vendor independent of Microsoft; we make

no warranty, implied or otherwise, regarding this product's performance or

reliability.

Additional reference words: 3.11 3rdparty wfw wfwg


WFWG Err Msg: Your Network Adapter MS$AE1 Is Not Working...

Article ID: Q108035

--------------------------------------------------------------------

The information in this article applies to:

- Microsoft Windows for Workgroups version 3.11

--------------------------------------------------------------------

SYMPTOMS

========

If an Artisoft AE/1 or AE/2 card network interface card (NIC) is configured

for IRQ 10 or 15, it does not work with the NE1000.386 NDIS 3 NIC driver

that ships with Microsoft Windows for Workgroups 3.11. In this situation,

the following error message appears when you load Windows for Workgroups

3.11:

   Your network adapter MS$AE1 is not working properly. You may need

   to set it up again.

CAUSE

=====

The NE1000.386 NDIS 3 NIC driver that ships with Windows for Workgroups

3.11 does not support extended IRQs. This is because the Novell NE1000

card, for which the driver was written, does not support extended IRQs.

Therefore, NICs that emulate the NE1000 and support IRQ 10 or 15, such as

the Artisoft AE/1 or AE/2 adapter, do not work with the Windows for

Workgroups 3.11 NDIS 3 driver when set to these IRQs.

WORKAROUND

==========

To work around this problem, do one of the following:

 - Use IRQ 2, 3, 4, 5, or 7.

   -or-

 - Use the NDIS 2 driver, which does support extended IRQs.

Additional reference words: 3.11 wfw wfwg won't work incompatible

interrupts ae-1 ae1 ae/1 ae1000 ae-1000 ae-2 ae/2 ae2


3Com Etherlink 16 Network Adapter Unstable in Turbo Mode

Article ID: Q108076

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

--------------------------------------------------------------------

SUMMARY

=======

The 3Com Etherlink 16 network adapter card has configuration settings that

can be changed with a diagnostics setup utility. If the data mode in the

configurations settings is set to Turbo, the network card may not function

correctly with Windows for Workgroups 3.11: network performance may be

unstable.

MORE INFORMATION

================

To correct this problem, reset the data mode on the network adapter card to

Standard. To change this setting, use the following steps:

1. Place the Etherdisk configuration disk in your floppy disk drive.

2. Type the following

      <drive letter>:setup

   where <drive letter> is the letter of the drive containing the

   Etherdisk configuration disk.

3. Type "menu" (without the quotation marks) and press ENTER. From this

   menu, choose Diagnostics Program.

4. Select "Run Diagnostic and Configuration Program"(number 1).

5. Select Set Configuration and press ENTER.

6. Press Y to change the configuration settings.

7. Scroll down to Data Mode and press ENTER.

8. Select Standard and press ENTER, then press ENTER again to save the

   new settings.

9. Press any key other than ENTER to return to the main menu.

Further questions about these steps should be directed to 3Com Corporation

Technical Support.

The 3Com Etherlink 16 network adapter card is manufactured by 3Com, a

vendor independent of Microsoft; we make no warranty, implied or otherwise,

regarding this product's performance or reliability.

REFERENCES

==========

"3Com Etherlink 16 Adapter Guide" (3Com part number 6847-01)

Additional reference words: 3.11 3 three com 3C507 winnet wfwg


WFWG Err Msg: Error 59: An Unexpected Network Error...

Article ID: Q108077

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

----------------------------------------------------------------------

SYMPTOMS

========

When you are running Windows for Workgroups 3.11 in conjunction with a

Windows NT Advanced Server or Microsoft LAN Manager domain controller,

attempts to change a user's domain password may fail and generate the

following error message:

   Error 59: An unexpected network error has occurred.

CAUSE

=====

A domain password change request can be denied because of one or more of

the following reasons:

 - The new password is one character in length.

 - The new password is shorter than the domain controller requires.

 - The new password is on the history list that the domain controller

   maintains.

RESOLUTION

==========

A user can change his or her password from within Windows by using the

Change Domain Password dialog box or by using the NET PASSWORD command at

an MS-DOS command prompt. To do this:

 - From Control Panel, choose the Network icon, Startup, and then Set

   Password. Type the old and new passwords and choose OK.

   -or-

 - At the MS-DOS command prompt, use the following command:

      net password \\<computer> /domain:<name> <user> <oldpassword>

      <newpassword>

   where <computer> specifies your Windows NT or LAN Manager server, <name>

   specifies the Windows NT or LAN Manager domain on which you want to

   change your password, <user> specifies your Windows NT or LAN Manager

   user name, and <oldpassword> and <newpassword> specify your old and new

   passwords.

   For more information on the above command, type the following at the

   MS-DOS command prompt:

      net password /?

MORE INFORMATION

================

Most domain controllers can be preset to require a specified length and

type of password. Also, they can be configured to keep a history of the

last "x" number of passwords for a given user. Normally, the user is not

allowed to use any of the passwords on the history list. With Microsoft

Windows NT and Microsoft LAN Manager 2.2 domain controllers, if the new

password does not satisfy these requirements, the aforementioned error is

displayed.

Additional reference words: 3.11 wfw wfwg error message ntas ntlan

lan man


Dr. Watson Removed in Windows for Workgroups 3.11 Setup

Article ID: Q108078

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

--------------------------------------------------------------------

Microsoft Windows for Workgroups version 3.11 does not ship with the Dr.

Watson (DRWATSON.EXE) utility; however, if you upgrade Windows 3.1 or

Windows for Workgroups 3.1 to Windows for Workgroups 3.11, Dr. Watson

remains installed on your hard disk, however, its icon may no longer

appear. If you created an icon for DRWATSON.EXE and placed it in one the

Windows default program groups, such as the Startup group, the Dr. Watson

icon is removed.

Additional reference words: 3.11 wfw wfwg dr.watson


32-Bit File Access Maximum Cache Size

Article ID: Q108079

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

--------------------------------------------------------------------

SUMMARY

=======

When you use Microsoft Windows for Workgroups 3.11 with 32-bit file access,

the maximum amount of memory that can be set in the 386 Enhanced dialog box

in Control Panel is 24 megabytes (MB)(or 24,576 kilobytes [K]).

MORE INFORMATION

================

Although the user interface is limited to 24 MB, the theoretical maximum

size of the cache is actually 2GB. This cache size is using physical RAM;

therefore, the cache size is limited to the amount of RAM on your computer.

Setting the cache size greater than the physical amount of RAM available

results in the following error message when re-entering the Virtual Memory

settings in the 386 Enhanced dialog box:

   32-bit file access was unable to run. Your hard disk(s) may not

   be compatible with 32-bit file access.

Steps to Manually Increase the Cache Size

-----------------------------------------

1. Open the SYSTEM.INI file in a text editor, such as Microsoft Windows

   Notepad.

2. Go to the [VCache] section.

3. Change the MinFileCache= setting to the desired value.

   NOTE: The value for this setting is in kilobytes. For example, if you

   want to create a 50-MB cache, the line would be as follows:

      [VCache]

      MinFileCache=51200

Please note that Microsoft's testing did not include cache sizes greater

than 40MB. Microsoft makes no guarantees that the cache size will operate

correctly when increased above the user interface. Microsoft is not

responsible for data loss or data corruption due to a cache size larger

than the user interface.

Additional reference words: 3.11 wfw wfwg vfat vcache vcache.386 max

limit amount


PC-NFS Error: NFS903F Missing or Invalid PROTOCOL.INI Data

Article ID: Q108100

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

--------------------------------------------------------------------

SYMPTOMS

========

When using Sun Select's PC-NFS with Windows for Workgroups 3.11, you may

receive the following error message upon executing the PC-NFS files in the

AUTOEXEC.BAT file:

   NFS903F Missing or invalid PROTOCOL.INI data.

CAUSE

=====

This error occurs when the PC-NFS protocol is bound to more than one

network card in the PROTOCOL.INI file. PC-NFS allows for only one binding.

Windows for Workgroups 3.11, when installed on a machine with more than one

network card, adds the PC-NFS protocol to all network adapters listed in

the PROTOCOL.INI file.

RESOLUTION

==========

To eliminate this error message, the PC-NFS protocol should be removed from

all but one of the network cards listed in PROTOCOL.INI. To do this, use

the following steps:

1. If Windows for Workgroups fails to start after receiving the error

   message at startup, start Windows with the following command:

       win /n

   This starts Windows for Workgroups 3.11 without loading the network

   drivers.

2. Double-click the Network Setup icon in the Network group, then choose

   the Drivers button.

3. Locate the network adapter(s) to which you do NOT want to bind the PC-

   NFS protocol. Select PC-NFS Protocol under each of these listed

   adapters and then choose Remove.

4. Choose OK, and allow Windows for Workgroups to make all suggested

   changes to your configuration files. Once this is done, reboot the

   machine.

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 as it becomes available.

Additional reference words: 3.11 pc nfs Sun Select unix WFWG WFW


Comprehensive List of WFWG 3.11 Resource Kit Doc Errors

Article ID: Q108109

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SUMMARY

=======

This article contains information on the documentation errors in the manual

"Microsoft Windows for Workgroups Resource Kit Addendum for Operating

System version 3.11."

The following topics are covered:

 - Page 4-12: DeferBrowsing= Is Not a Valid Entry

 - Page 4-14: LogonDisconnected=Entry in SYSTEM.INI Shows Incorrect

   Default

 - Page 4-25: Log= Entry in EFAXPUMP.INI Should be in [MODEM] Section

 - Page 8-32, 35, 37: Secondnet.drv=Netware.drv Entry Should be in [Boot]

   Section of SYSTEM.INI

MORE INFORMATION

================

Page 4-12: DeferBrowsing= Is Not a Valid Entry

----------------------------------------------

Page 4-12 of the Resource Kit incorrectly lists DeferBrowsing= as a valid

entry for the [Network] section of the SYSTEM.INI file.

The correct entry is DeferBrowse=. DeferBrowsing is not valid and has no

effect on Windows for Workgroups.

Page 4-14: LogonDisconnected=Entry in SYSTEM.INI Shows Incorrect Default

------------------------------------------------------------------------

The LogonDisconnected= entry in the [Network] section of the SYSTEM.INI

file incorrectly states the default for this setting.

The correct default is YES.

Page 4-25: Log= Entry in EFAXPUMP.INI Should be in [MODEM] Section

------------------------------------------------------------------

The Log= entry in the [COMn] section of the EFAXPUMP.INI file has no effect

on the logging of transmission information in the FAXWATCH.LOG file.

However, if you place the Log= entry in the [MODEM] section of the

EFAXPUMP.INI file, the entry generates a FAXWATCH.LOG file, and the

transmission information is saved to FAXWATCH.LOG after you exit mail.

Page 8-32, 35, 37: Secondnet.drv=Netware.drv Entry Should be in

[Boot] Section of SYSTEM.INI

---------------------------------------------------------------

THE Secondnet.drv=Netware.drv entry is incorrectly shown in the [386Enh]

section of the sample SYSTEM.INI files on pages 8-32, 8-35, and 8-37.

This entry should be placed in the [boot] section of the SYSTEM.INI file.

Additional reference words: 3.11 docerr doc err documentation error errors

workgroup add-on LogonDisconnected


IBM ValuePoint with BIOS Date 4/29/93 Hangs at Logo Screen

Article ID: Q108151

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows operating system version 3.1

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

SYMPTOMS

========

Microsoft Windows for Workgroups stops responding (hangs) at the logo

screen during startup on an IBM ValuePoint personal computer.

CAUSE

=====

The Windows keyboard driver (VKD) times out on IBM ValuePoint computers

with a BIOS date of 4/29/93 or earlier, or with an EPROM Flash Revision

Level of 5.1 to 5.3. This behavior also occurs on IBM ValuePoint SI

computers that are Type 6381.

To determine the EPROM Flash Revision Level, press the F1 key when a box

appears in the upper-left portion of the screen as the computer is booting.

This takes you into the Configuration Utilities Screen. The EPROM Revision

Level is listed at the bottom of this screen.

To determine if you have a Type 6381 ValuePoint, look at a label on the

back of the computer.

RESOLUTION

==========

To correct this problem:

 - Contact IBM Technical Support at (800) 772-2227 to receive a patch to

   the VKD.

   -or-

 - Contact the IBM bulletin board service at (919) 517-0001 and download

   the necessary files for your  computer:

      IBMKBFIX.EXE (the VKD replacement for the ValuePoint PC)

      VP2FLxxx.DSK (Flash ROM, where xxx is the latest version number)

      6381WG31.ZIP (the VKD replacement for the ValuePoint SI PC)

      VPSIFL31.DSK (Flash ROM for the ValuePoint SI PCs)

      LDF.COM (used to uncompress the above files)

MORE INFORMATION

================

The IBM products included here are manufactured by a vendor independent

of Microsoft; we make no warranty, implied or otherwise, regarding these

products' performance or reliability.

Additional reference words: 3.11 wfw wfwg incompatible version lock locks

hang value point


32-Bit File Access and Stacker 3.1 Utilities

Article ID: Q108152

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SUMMARY

=======

The utilities that Stacker 3.1 installs in Windows for Workgroups 3.11 File

Manager do not work if 32-bit file access is enabled.

WORKAROUND

==========

To work around this problem, disable 32-bit file access while you are using

the utilities. To do this, choose the 386 Enhanced icon in Control Panel,

Virtual Memory, and Change, then clear the 32-Bit File Access check box.

You can restore 32-bit file access when you are finished using the

utilities without causing any damage to the disk.

MORE INFORMATION

================

Stacker 3.1 adds the following menu to File Manager:

   Stacker

   -------

   File Info

   Disk Info

If you try to choose one of these menu items, the following error message

is displayed:

   Stacker not installed

The Stacker volume file still functions properly with 32-bit bile access

enabled, and all files will be available normally.

Additional reference words: 3.11 stac compression VFAT stackvol


WFWG Err Msg: No Domain Server Was Available to Validate...

Article ID: Q108153

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

SYMPTOMS

========

When you try to log on to a Microsoft Windows NT or Microsoft LAN Manager

domain through Microsoft Windows for Workgroups, you may receive one of the

following error messages:

Windows for Workgroups 3.11

---------------------------

   No domain server was available to validate your password. You were

   logged on without password validation.

Windows for Workgroups 3.1

--------------------------

   No LAN Manager server was available to validate your password. You were

   logged on without password validation.

CAUSE

=====

This error occurs if there is a space included in the computer name.

Microsoft Windows NT supports computer names with spaces, but in order for

validation to occur, the computer name must appear in quotation marks.

Windows for Workgroups does not allow the user to input the computer name

when you log on; therefore, validation fails if you have a space included

in your computer name. The answer to whether or not validation has taken

place never comes back.

RESOLUTION

==========

To correct this problem, remove the space from the computer name.

Additional reference words: 3.11 wfw wfwg Password Validation lanman winnt

authentication ntas ntlan


Problems Accessing B&W NFS Mounted Drives in WFWG 3.11

Article ID: Q108154

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SYMPTOMS

========

If you run Beame and Whiteside's network file system (BW-NFS) for Lan

Workplace on open datalink interface (ODI) with Windows for Workgroups 3.11

and you set an NFS file system as a mounted drive, the drive is visible but

not accessible in Windows. (It appears as a blank disk.)

CAUSE

=====

This behavior is caused by a problem with the Beame and Whiteside NFS

redirector.

RESOLUTION

==========

Although the directory appears empty, the files can be accessed if you know

the name of the file. Beame and Whiteside is aware of this problem.

STATUS

======

Beame and Whiteside has developed new drivers to make Windows for

Workgroups 3.11 work with its product and the ODI stack. The problem in the

redirector will be addressed in a future release. For more information,

contact Beame and Whiteside at (416) 765-0822 (phone)or (416) 765-0815

(fax).

MORE INFORMATION

================

The products included here are manufactured by vendors independent of

Microsoft; we make no warranty, implied or otherwise, regarding these

products' performance or reliability.

Additional reference words: 311 B&W Beam NFS wfwg


WinPopup Cannot Run... Error with VREDIR.386

Article ID: Q108156

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SYMPTOMS

========

When you run WinPopup in Windows for Workgroups 3.11, you may receive the

following error message:

   WinPopup cannot run because the VREDIR.386 redirector is not started.

CAUSE

=====

This error occurs when the MS-DOS redirector loads before Windows for

Workgroups 3.11.

RESOLUTION

==========

To avoid the error message, do not start the MS-DOS redirector before

running Windows for Workgroups 3.11, or remove WinPopup from the LOAD= line

or Startup group.

Additional reference words: 3.11 Workstation pop


32-Bit File Access Cache Size Is Incorrectly Displayed

Article ID: Q108157

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SYMPTOMS

========

When you run Windows for Workgroups 3.11 with 32-bit file access enabled

and a cache size over 9,984 kilobytes (K), the cache size displayed in the

Virtual Memory dialog box of Control Panel is truncated. (To see the cache

size, choose the 386 Enhanced icon in Control Panel, choose Virtual Memory,

and then choose the Change button.)

CAUSE

=====

This is a display error; the actual cache size is still the value that was

entered in the dialog box, provided sufficient physical RAM is available to

allocate to the cache.

Additional reference words: 3.11 vfat


WFWG 3.11 Err Msg: Error 1: An Internal Error Occurred

Article ID: Q108421

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

--------------------------------------------------------------------

SYMPTOMS

========

Running the NET START FULL command at the MS-DOS command prompt or entering

Microsoft Windows for Workgroups yields the following error message:

   Error 1: an internal error occurred.

CAUSE

=====

This error may be caused by:

 - The presence of the DirectHost=No line in the [Network] section of the

   SYSTEM.INI file.

   -or-

 - The absence of IFSHLP.SYS in the CONFIG.SYS file.

RESOLUTION

==========

To correct this problem, do one of the following:

 - If the [Network] section of the SYSTEM.INI file contains the

   DirectHost=No line, change the DirectHost= value to Yes or remove the

   line.

 - If your CONFIG.SYS file is missing the IFSHLP.SYS line, insert the

   following statement in the CONFIG.SYS file

      Device=<C:\WINDOWS>\IFSHLP.SYS

   where <C:\WINDOWS> is the drive and directory containing your Windows

   files.

MORE INFORMATION

================

If you have Microsoft Windows for Workgroups running with IPX and NetBEUI

on a Novell NetWare 4.0 network using ODI, and you try to access Windows

for Workgroups network functionality without first starting protected mode,

you may lose your NetWare drive mappings.

If you then try to return to one of your mapped NetWare drives, you

may receive an "invalid drive specification" message. The Map command shows

that the only available NetWare drive is either the first (for example, f:

or p:) or the last (z:).

If you change to this NetWare drive and look at a directory listing, you

see the login directory (just as if you had logged out). At this point, you

can log on to NetWare normally.

Novell NetWare is manufactured by Novell Inc., a vendor independent of

Microsoft; we make no warranty, implied or otherwise, regarding this

product's performance or reliability.

Additional reference words: 3.11 wfw wfwg map login error


WFWG Err Msg: Selected Server Cannot Be Found on the Network

Article ID: Q108427

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SYMPTOMS

========

In the Connect Network Drive dialog box of File Manager, if you manually

enter the path for the computer you want to connect to, you may receive one

of the following error messages:

   The selected server cannot be found on the network.

   -or-

   You may not be routing through your Novell NetWare servers.

CAUSE

=====

These errors occur when the following conditions exist:

 - You have installed Windows for Workgroups 3.11 over version 3.1 with

   MSIPX and have elected to keep MSIPX rather than use the ODI drivers.

   -and-

 - You remove the NetBEUI protocol from the machine that you are either

   connecting to or from.

   Example of protocols installed on machines:

   Computer 1               Computer 2

   ----------               ----------

   Novell IPX               NetBEUI

   IPX/SPX with NetBIOS     Novell IPX

                            IPX/SPX with NetBIOS

   As long as NetBEUI is on one computer and not the other, the

   workstations cannot communicate.

RESOLUTION

==========

To correct this problem, do one of the following:

 - In Network Setup, restore NetBEUI to the computer it was removed from.

   -or-

 - In Network Setup, remove NetBEUI from the computer(s) that must allow

   NWLink to communicate and route through a Novell server.

Additional reference words: 3.11


Err Msg: An Error Occurred Accessing the Security Settings...

Article ID: Q108428

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

--------------------------------------------------------------------

SYMPTOMS

========

When you run the NET START command, you may receive one of the following

error messages:

   Error 3: The specified path was not found.

   An error occurred accessing the security settings file.

   -or-

   Error 2625: WFWSYS.CFG is Invalid.

CAUSE

=====

These errors may occur when the DEVDIR= line in the [network drivers]

section of the SYSTEM.INI file is set to a directory different from the

directory where the WFWSYS.CFG file is located.

RESOLUTION

==========

To correct this problem, change the DEVDIR line so that it points to the

correct location of the WFWSYS.CFG file.

Additional reference words: 3.11 wfw wfwg admincfg.exe administrator

admin security


ODIHLP.EXE Cannot Be Unloaded

Article ID: Q108477

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SUMMARY

=======

ODIHLP.EXE cannot be loaded and unloaded from the MS-DOS command line. This

ability to dynamically load and unload is available in the Novell ODI

workstation files. Any ODI drivers loaded prior to ODIHLP.EXE (LSL.COM and

the network card driver as a minimum) are not unloadable.

To recover the memory used by these drivers, try using multiple

configurations MS-DOS 6.0 or 6.2 so that you can access boot configurations

with and without the ODI drivers.

MORE INFORMATION

================

Windows for Workgroups 3.11 includes support for Novell NetWare

connectivity by using a NetWare ODI workstation configuration and the

ODIHLP.EXE support file.

ODIHLP.EXE is a real-mode component that allows the protect-mode NDIS 3

protocols used by Windows for Workgroups 3.11 (NetBEUI and the IPX/SPX

compatible transports) to work with the real-mode ODI network card drivers

and LSL.COM.

One benefit of ODI drivers (including MLID, LSL, IPXODI and NETX) is that

they can be unloaded from memory at the command line (for example, IPXODI

/U).

ODIHLP.EXE, however, cannot be unloaded. If you want to unload the protocol

driver(s) and NETX, ODIHLP.EXE must load before them. ODIHLP.EXE binds to

the LSL and MLID and therefore does not allow these drivers to unload.

Additional reference words: 3.11


After Dark AD-DOS.COM and Novell NetWare LSL.COM

Article ID: Q108478

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SUMMARY

=======

Windows for Workgroups 3.11 includes support for Novell NetWare

connectivity using the Novell NetWare ODI workstation configuration files

(including LSL.COM). If you are using this configuration with a version of

the Berkeley Systems MS-DOS-based screen saver After Dark earlier than 2.0,

you may encounter problems.

Early versions of the screen saver terminate-and-stay-resident (TSR)

program, AD-DOS.COM versions 1.0x, do not load if the Novell NetWare

LSL.COM file has been loaded first. LSL.COM does load after AD-DOS.COM,

however, this may cause unreliable network functionality and application

performance.

The AD-DOS.COM file included with After Dark version 2.0 does not appear to

generate these properties. For more information, contact Berkeley Systems

Technical Support at (510) 540-5535.

MORE INFORMATION

================

If LSL.COM is loaded into memory first, it occupies INT 2f/CO; when

AD-DOS.COM detects that this interrupt is in use, it fails to load. The

following message is displayed when the AD-DOS.COM TSR program cannot load:

   Another TSR is currently using our ID code.

If AD-DOS.COM loads first, LSL.COM loads without generating an error

message. LSL.COM may then pass calls to AD-DOS.COM, which may return

inappropriate values and cause network applications to fail to detect the

presence of LSL.COM or otherwise cause the applications to receive

unreliable information (such as pointers to information structures) from

LSL.COM.

The products included here are manufactured by vendors independent of

Microsoft; we make no warranty, implied or otherwise, regarding these

products' performance or reliability.

Additional reference words: 3.11 AD-DOS After Dark 3rd party


Extended Error 53 When Accessing Network Drives from MS-DOS

Article ID: Q108479

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SYMPTOMS

========

When you try to access a connected network drive from the MS-DOS command

prompt using Windows for Workgroups 3.11 and Novell NetWare connectivity,

you may receive the following message:

  Extended Error 53

CAUSE

=====

This error message occurs because the real-mode network, when running

Novell NetWare connectivity, cannot load the same protocols that load in

386 enhanced mode Windows for Workgroups 3.11. Because the real-mode

network is using the IPX or IPXODI driver to communicate with the network

adapter, it cannot load the NDIS2 or NDIS3 protocols. However, it does

allow communication with any Windows for Workgroups 3.11 server running the

IPX/SPX Compatible Transport or IPX/SPX Compatible Transport with NetBIOS

on the network.

It is not possible to access a Windows for Workgroups 3.1 server because it

cannot use the IPX/SPX compatible protocol. Communication with a Windows NT

server is also not possible because the real-mode network does not provide

the NetBIOS interface necessary to communicate with the Windows NT IPX/SPX

Compatible Transport.

If persistent connections are stored in Windows for Workgroups 3.11 and

ghosted connections are enabled, starting the real-mode network in MS-DOS

will seem to connect machines not running the IPX/SPX compatible protocol,

including Windows for Workgroups 3.1 and Windows NT servers. However, if

you try to access files or printers on these servers, you receive the error

message "Extended Error 53." This occurs because ghosted connections have

been enabled in Windows for Workgroups 3.11 and therefore no attempt is

made to connect to the server when the real-mode network is first started.

RESOLUTION

==========

Communication is not possible with a Windows for Workgroups 3.1 or Windows

NT server using the real-mode redirector in conjunction with Novell NetWare

connectivity. If you need to access another Windows for Workgroups 3.11

machine, the computer you are trying to connect to must be running Windows

for Workgroups 3.11 and must have the IPX/SPX Compatible Transport (either

with or without NetBIOS) installed as a protocol.

Additional reference words: wfwg 311 direct host redir real-mode


WFWG Err Msg: The Specified Drive Letter or Device Is Invalid

Article ID: Q108494

-------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.1

-------------------------------------------------------------------

SYMPTOMS

========

Windows for Workgroups 3.1 File Manager allows attempts to connect to a

network drive with a drive letter greater than that specified by the

LASTDRIVE= statement in the CONFIG.SYS file.

If you try to connect to a Windows for Workgroups or LAN Manager share

using such a drive letter, you may receive the following error message:

   The specified drive letter or device is invalid. If you

   specified a drive, it may be past the value specified by

   the LASTDRIVE command in the CONFIG.SYS file.

CAUSE

=====

The Windows for Workgroups 3.1 File Manager allows drive designations

through the letter Z in the Connect Network Drive dialog box regardless of

the value specified by LASTDRIVE=. Because Microsoft LAN Manager and

compatible networks use drive designations up to and including that

specified by LASTDRIVE= only, this may result in an attempt to connect to

an invalid drive letter and the resulting error message above may occur.

Connections to shares on Novell NetWare servers do not result in the error

because NetWare normally reserves drive letters after that specified by the

LASTDRIVE= statement for its connections.

MORE INFORMATION

================

This error message does not occur in later versions of Windows for

Workgroups  because File Manager does not allow a drive designation to be

made past the LASTDRIVE= parameter in the CONFIG.SYS file.

Additional reference words: 3.10 wfwg winfile 15


ODIHLP.EXE Load Error Messages

Article ID: Q108700

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SYMPTOMS

========

This article lists error messages generated by ODIHLP.EXE when it is loaded

out of sequence.

 - The ODIHLP.EXE may produce the following error message if it is loaded

   before the link support layer (LSL.COM):

      ERROR:  cannot load LSL

      ODI/NDIS3 Mapper:  Initialization failure

      Press any key to continue

 - The ODIHLP.EXE file may produce the following error message if it is

   loaded after LSL.COM and before the multiple link interface device

   (MLID) driver:

      ERROR:  not bound to any boards

      ODI/NDIS3 Mapper:  Initialization failure

      Press any key to continue

In both the above scenarios, when you start Windows for Workgroups 3.11, a

text-based and a Windows-based error message appear:

The following text-based error message appears when the SYSTEM.INI file is

read:

      ERROR:      MSODISUP failed to load.

      ODIHLP.EXE must be loaded before starting Windows,

      ODIHLP.EXE should be loaded in AUTOEXEC.BAT after LSL.COM

      Cannot load a device that is specified in SYSTEM.INI.

      The performance of Windows should not be affected without this file.

      C:\WINDOWS\SYSTEM\MSODISUP.386

      Press a key to continue

The Windows-based STOP error message that appears is:

      Networking functionality will not be available. Your network adapter

      or protocols may not be configured properly. Run Network Setup to

      check adapter and protocol settings.

RESOLUTION

==========

To avoid these errors, ODIHLP.EXE must be loaded after LSL.COM and the MLID

driver.

MORE INFORMATION

================

ODIHLP.EXE is the real-mode component that allows LSL to complete its

binding process in real mode (similar to NDISHLP.SYS). This file hooks all

the real-mode entry points so that MSODISUP.386 can use this information

when working in protected mode.

ODIHLP.EXE acts as a default stack for all frame types (that is, ODIHLP

accepts any packet that is of one of the frame types listed in the NET.CFG

file.

Additional reference words: 3.11


Loading NetBEUI or NetPopup in Conventional Memory

Article ID: Q108801

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SYMPTOMS

========

NET START /NOHI and NET START /NETBEUI do not prevent NetBEUI and

POPUP from loading in the upper memory area (UMA). Adding LoadHigh=No

to the [Network] section of the SYSTEM.INI file also does not prevent

NetBEUI and POPUP from loading in the UMA.

CAUSE

=====

NET START /NOHI prevents device drivers from being loaded in the UMA.

For example, NET START /NOHI prevents PROTMAN.DOS, <netcard driver>.DOS,

NDISHLP.SYS, and IFSHLP.SYS from loading in the UMA.

Network services, such as the redirector (Redir), NetBEUI, and POPUP,

automatically attempt to load into the UMA. There is no way to change this

behavior.

Additional reference words: 3.11 conventional memory pop-up pop up


WFW 3.11 may Fail After Upgrading (Missing SlotNumber= Entry)

Article ID: Q108802

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SYMPTOMS

========

If you are using a MicroChannel or EISA network interface card (NIC) and

upgrade from Windows for Workgroups version 3.1 to Windows for Workgroups

3.11, your system may not work correctly if your PROTOCOL.INI file does

not contain a SlotNumber entry.

CAUSE

=====

Under Windows for Workgroups version 3.1 the NDIS version 2.0 driver

scans the slots to determine the correct SlotNumber. Therefore, the

SlotNumber entry in the PROTOCOL.INI file is optional. Under Windows for

Workgroups version 3.11, the NDIS version 3.0 driver does not scan the

slots to determine the correct SlotNumber.

Since you upgraded from Windows for Workgroups 3.1 or 3.11, the network

card detection code was not used during Setup. As a result, your

PROTOCOL.INI file does not contain a SlotNumber entry. If there isn't a

SlotNumber entry in the PROTOCOL.INI file, the NDIS version 3.0 driver

defaults to slot number 1.

WORKAROUND

==========

To work around this problem add the correct SlotNumber= entry to the

network interface card section of the PROTOCOL.INI. For example:

   [MS$IBMTRA]

   SlotNumber=2

Additional reference words: 3.11 UBNEI1 MS$NIUPS UBNEI.386 code


Additional NICs Supported in Windows for Workgroups 3.11

Article ID: Q108807

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SUMMARY

=======

All network interface cards (NIC) supported in Windows for Workgroups 3.10

are also supported in Windows for Workgroups 3.11. Microsoft has added

support for the following additional network cards in version 3.11.

These network interface cards have been broken down by category.

 - NDIS2 support only

 - NDIS2 and ODI support

 - NDIS2, NDIS3, and ODI support

 - ODI support only

 - IPX or RAS support

MORE INFORMATION

================

Support for NDIS2 Only

----------------------

3COM TokenLink

Cabletron E3000 Series DNI

Cabletron E3100 Series DNI

Cabletron T2015 Token Ring DNI

Cabletron T3015 Token Ring DNI

DCA 10Mb

DCA 10Mb Fiber Optic

DCA 10Mb MCA

DCA 10Mb Twisted Pair

Everex SpeedLink

HP Ethertwist MCA Adapter

IBM PC Network Adapter II

IBM PC Network Adapter II/A

IBM PC Network Baseband Adapter

IBM PC Network Baseband Adapter/A

NCR StarCard

NCR Token-Ring 4 Mbs ISA

NCR Token-Ring 16/4 Mbs ISA

NCR Token-Ring 16/4 Mbs MCA

NCR WaveLan AT Adapter

NCR WaveLan MC Adapter

Proteon ISA Token Ring (1340)

Proteon ISA Token Ring (1342)

Proteon ISA Token Ring (1346)

Proteon ISA Token Ring (1347)

Proteon MCA Token Ring (1840)

Proteon ProNET-4/16 p1892

Pure Data PDI508+ (ArcNet)

Pure Data PDI516+ (ArcNet)

Pure Data PDI90211 (Wireless)

Pure Data PDuC90211 (Wireless)

Racal-DATACOM ES3210

Racal NI5210/8

Racal NI5210/16

SMC ARCNETPC

SMC ARCNET PC100, PC200

Tulip NCC-16

UB NIC/ps

Generic NDIS2 Driver

Support for NDIS2 and ODI

-------------------------

3COM EtherLink Plus

ARCNET Compatible

Cabletron E2000 Series DNI

Cabletron E2100 Series DNI

DEC (DE210) EtherWorks MC

DEC (DE210) EtherWorks MC/TP

DEC (DE210) EtherWorks MC/TP_BNC

Intel TokenExpress EISA 16/4

Intel TokenExpress 16/4

Intel TokenExpress MCA 16/4

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

Olicom 16/4 Token-Ring Adapter

Proteon Token Ring (P1390)

Proteon Token Ring (P1392)

Pure Data PDI9025-32 (Token Ring)

Pure Data PDuC9025 (Token Ring)

Racal NI6510

RadiSys EXM-10

SMC ARCNET PC110, PC210 PC250

SMC ARCNET PS110, PS210

SMC ARCNET PC130/E

SMC ARCNET PC120, PC220 PC260

SMC ARCNET PC270/E

SMC ARCNET PC600W,PC650W

SMC 3000 Series

SMC EtherCard PLUS 16 With Boot ROM Socket (WD/8013EBT)

SMC EtherCard PLUS With Boot ROM Socket (WD/8003EBT)

Thomas Conrad (All Arcnet Types)

Thomas Conrad TC6042

Thomas Conrad TC6045

Thomas Conrad TC6142

Thomas Conrad TC6045

Thomas Conrad TC6242

Thomas Conrad TC6245

UB NIU (All Types)

UB NIUpc

UB NIUpc/3270

UB NIUpc/EOTP

UB NIUps or NIUps/EOTP

UB pcNIU

UB pcNIU/ex 128k

UB pc NIU/ex 512k

Xircom Pocket Ethernet I

Xircom Pocket Ethernet II

Zenith Data Systems Z-Note

NDIS2, NDIS3, and ODI Support

-----------------------------

3Com Etherlink 16

3Com Etherlink II or IITP (8 or 16-bit)

3Com Etherlink III

3Com Etherlink/MC

Advanced Micro DevicesAM2100/AM1500T

Amplicard AC 210/XT

Amplicard AC 210/AT

Artisoft AE-1

Artisoft AE-2 or AE-3

Artisoft AE-2 (MCA) or AE-3 (MCA)

Artisoft AE-3

Compaq NE3200

DEC Ethernet (All Types)

DEC DEPCA

DEC EE101 (Built-In)

DEC (DE100) EtherWorks LC

DEC (DE101) EtherWorks LC/TP

DEC (DE102) EtherWorks LC/TP_BNC

DEC (DE200) EtherWorks Turbo

DEC (DE200) EtherWorks Turbo/TP

DEC (DE200) EtherWorks Turbo/TP_BNC

DECpc 433 WS (Built-In)

HP Ethertwist EISA LAN Adaptor/32 (HP27248 or HP27248A)

HP PC LAN Adapter/8 TL (HP27250)

HP PC LAN Adapter/8 TP (HP27245)

HP PC LAN Adapter/16 TP (HP27247A)

HP PC LAN Adapter/16 TL Plus (HP27252)

HP PC LAN Adapter/16 TP Plus (HP27247B)

IBM Token Ring (All Types)

IBM Token Ring

IBM Token Ring (MCA)

IBM Token Ring II

IBM Token Ring II/Short

IBM Token Ring 4/16Mbs

IBM Token Ring 4/16Mbs (MCA)

Intel EtherExpress 16 or 16TP

Intel EtherExpress 16 (MCA)

Intel EtherExpress /32

Exos 105

National Semiconductor AT/LANTIC EtherNODE 16- AT3

National Semiconductor Ethernode *16AT

NE1000 Compatible

NE2000 Compatible

Novell/Anthem NE1000

Novell/Anthem NE2000

Novell/Anthem NE1500T

Novell/Anthem NE2100

Novell/Anthem NE/2

Novell/Anthem NE3200

SMC EtherCard (All Types except 8013/A)

SMC EtherCard PLUS (WD/8003E)

SMC EtherCard PLUS/A (MCA,BNC/AUX) (WD 8013EP/A)

SMC EtherCard PLUS/A (MCA,TP/AUX) (WD 8013EW/A)

SMC EtherCard PLUS 10T/A (MCA) (WD 8003W/A)

SMC EtherCard PLUS/A (MCA) (WD/8003E/A or 8003ET/A)

SMC EtherCard PLUS TP (WD/8003WT)

SMC EtherCard PLUS With Boot ROM Socket (WD/8003EB)

SMC EtherCard PLUS Elite (WD/8003EP)

SMC EtherCard PLUS 10T (WD/8003W)

SMC EtherCard PLUS Elite 16 (WD/8013EP)

SMC EtherCard PLUS Elite 16T (WD/8013W)

SMC EtherCard PLUS Elite 16 Combo (WD/8013EW or 8013EWC)

SMC StarCard PLUS (WD/8003S)

SMC StarCard PLUS/A (MCA) (WD/8003ST/A)

SMC StarCard PLUS With On Board Hub (WD/8003SH)

Zenith Data Systems NE2000 Compatible

ODI Support Only

----------------

IPXODI Support Driver (Ethernet)

IPXODI Support Driver (Token Ring)

IPXODI Support Driver (ArcNet)

IPX Support and RAS

-------------------

IPX Support Driver (Monolithic) with NetBIOS Support

Remote Access Service

Additional reference words: net network.inf


Remote Access Service - Error 714: Configuration error

Article ID: Q108808

--------------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows For Workgroups version 3.11

--------------------------------------------------------------------------

SYMPTOMS

========

When you start the Remote Access Services (RAS) client program for Windows

for Workgroups version  3.11, the following error message may be displayed:

   Error 714: Configuration error.

   Make sure you logged on from Windows and not from MS-DOS.

-or-

   RAS.EXE caused a General Protection Fault in module RASFILE.DLL at

   0001:XXXX.

If you try to start RAS a second time after you receive the general

protection (GP) fault, the following error message will be displayed:

   Cannot start RASPHONE. Make sure the RASPHONE.EXE file is in the

   \WINDOWS  directory, and restart Remote Access.

CAUSE

=====

These errors occur because of a missing or corrupted SERIAL.INI file in

the Windows directory. Error 714 generally occurs when the SERIAL.INI

file is missing, and the GP fault occurs if the SERIAL.INI file is

corrupted.

The SERIAL.INI file is used to store the configuration information for

the RAS client program.

RESOLUTION

==========

Recreate the SERIAL.INI file as follows:

1. From the Network group, start Network Setup.

2. Choose the Drivers button.

3. Select Remote Access Service [NDIS3] and then choose the Setup button.

4. Select the appropriate device for the COM port that you will be using.

5. Choose the OK button, then exit Network Setup.

Additional reference words: RAS WFW


WFWG Hangs on Logo Screen (32-Bit File Access and NoEmmDriver)

Article ID: Q108818

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

--------------------------------------------------------------------

SYMPTOMS

========

If you have the setting NoEMMDriver=On in the [386Enh] section of your

SYSTEM.INI file, your system may stop responding (hang) at startup with the

Windows Logo screen displayed after you enable 32-bit file access.

WORKAROUND

==========

If you delete the NoEMMDriver=ON entry, your system may be able to start

Windows.

NOTE: This works only if your system configuration requires the RMM.D32

file for 32-bit file access. The RMM.D32 file is required for 32-bit file

access with MS-DOS 6.2 DoubleSpace, Stacker, and hard disk drive

controllers that are not INT 13 compatible.

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.

MORE INFORMATION

================

When the entry NoEMMDriver= is set to ON, it prevents Windows 386 enhanced

mode from installing the expanded memory driver. This differs from setting

EMMSize=0, which prevents upper memory blocks (UMBs) from being allocated

but does not prevent the EMM driver from being loaded.

The default value for NoEMMDriver= is OFF.

A number of third-party software applications recommend placing this line

in the SYSTEM.INI file to optimize Windows. If you experience any problems

with your applications after you remove this entry, contact the

manufacturer of the application.

Additional reference words: VFAT PCTOOLS NOEMMDRIVER Noemmdriver=true

Tshoot NDW noemm


Using Windows for Workgroups 3.11 with Beame and Whiteside

Article ID: Q108903

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SUMMARY

=======

Windows for Workgroups 3.11 supports multiple network drivers and can

co-exist with other network products, such as Beame and Whiteside NFS

(BW-NFS), version 3.0c.

After you upgrade to Windows for Workgroups 3.11, your BW-NFS connectivity

may not exist. This article describes procedures to correct this problem

that are based on information provided by Beame and Whiteside. If you want

to use ODI interface (running Novell NetWare, BW-NFS, and Windows for

Workgroups 3.11), contact Beame and Whiteside for configuration

recommendations.

MORE INFORMATION

================

CONFIG.SYS File Changes

-----------------------

Make the following changes in your CONFIG.SYS file by either remarking out

(with the REM command) or deleting the lines shown below.

NOTE: The following information assumes that your BW-NFS files are in a

directory called C:\BW30c.

   rem DEVICE=C:\BW30c\NDIS\PROTMAN.DOS

   rem DEVICE=C:\BW30C\NDIS\<ELNK3.DOS>   (where <ELNK3.DOS> is your

                                          specific network card driver)

   rem DEVICE=C:\BW30C\ETHDEV.SYS

   rem DEVICE=C:\BW30C\TCPIP.SYS 1460

SYSTEM.INI File Changes

-----------------------

Verify that your SYSTEM.INI file contains the following lines.

NOTE: You must copy the ETHDEV.SYS and TCPIP.SYS files to the directory

specified on the DEVDIR= line in the [network drivers] section of your

SYSTEM.INI file. The following is an example and assumes that the Windows

for Workgroups 3.11 network is also installed:

   [boot]

   network.drv=wfwnet.drv

   secondnet=bwnet.drv

   [boot.description]

   network.drv=Microsoft Windows Network (version 3.11)

   secondnet.drv=BW-NFS Network File System (version 3.0)

   [386Enh]

   network=*vnetbios,*vwc,vnetsup.386,vredir.386,vserver.386

   secondnet=bwdosnet.386,bwredir.386

   TimerCriticalSection=1000

   UniqueDOSPSP=TRUE

   PSPIncrement=5

   [Network]

   winnet=wfwnet/00025100

   multinet=bwnfs

   [network drivers]

   transport=ethdev.sys,tcpip.sys 1460,ndishlp.sys,*netbeui

   devdir=C:\Windows

   LoadRMDrivers=Yes

PROTOCOL.INI File Changes

-------------------------

Verify that your PROTOCOL.INI file located in the Windows directory

contains the following lines.

NOTE: The following is an example that uses a Western Digital Plus Family

Adapter. Your network adapter may differ and may have a different section

name and settings under that section.

[protocol manager]

drivername=PROTMAN$

[WD8003XMAC]                  ;This section varies depending on the

drivername=MACWD$             ;network adapter used in your system.

irq=5

ramaddress=CC00

iobase=0X280

[ETHDEV]

drivername=ETHDEV27

bindings=WD8003XMAC           ;This line must be identical to the

                              ;adapter name section in brackets

                              ;above. This line is case sensitive.

AUTOEXEC.BAT File Changes

-------------------------

Remark out any NETBIND= lines in your AUTOEXEC.BAT file.

If you are running only the TCP portion of the BW-NFS software, you should

remove the BWRPC and BWNFS drivers from the AUTOEXEC.BAT file.

If you are using the NFS portion of the BW-NFS software, you should remove

the BWSTART line from your AUTOEXEC.BAT file. There should be a

C:\WINDOWS\NET START line only. If you see another similar line that is

pointing to the BW-NFS directory, either remark out or delete that line.

Rename Your Files

-----------------

Regardless of the installation (ODI or NDIS), in the BW-NFS directory,

rename the NET.EXE file to NFS.EXE and the STARTNET.EXE to BWSTART.EXE.

This eliminates potential conflicts with Windows for Workgroups drivers.

Save Your Changes and Reboot

----------------------------

Save all changes to your files and reboot your computer. Your Beame and

Whiteside connectivity should then be restored.

For more information, contact Beame and Whiteside Software, Inc.

BW-NFS is manufactured by Beame and Whiteside, a vendor independent of

Microsoft; we make no warranty, implied or otherwise, regarding this

product's performance or reliability.

Additional reference words: 3.11 Beam White-side WFWG BWNFS


Games Group Installed Even If Games Are Not Selected

Article ID: Q109054

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

--------------------------------------------------------------------

SYMPTOMS

========

When you install Windows for Workgroups 3.11 by selecting the Custom Setup

option and choosing not to install any of the games, Program Manager still

contains an empty Games group even though you directed Setup not to install

any games.

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.

Additional reference words: 3.11 wfw wfwg progman.exe blank empty

nothing uninstall don't install do not add/remove windows components


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.

Additional reference words: 3.11 wfw wfwg Microsoft pc at work fax

Microsoft at work fax awfax efax q&a qanda issues tshoot


WFWG 3.11: The Network Group and WINSETUP /P

Article ID: Q109057

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

--------------------------------------------------------------------

SUMMARY

=======

Microsoft Windows for Workgroups 3.11 installs a Network group in the

Program Manager. The icons included in this group depend on the network

installation you chose during Setup.

Windows for Workgroups 3.11 allows you to rebuild the default program

groups (Accessories, Games, Main, Startup, and Network). To rebuild the

defaults, follow these steps:

1. From the File menu, choose Run.

2. On the Command Line, type "WINSETUP /P" (without the quotation marks).

3. Choose the OK button.

The contents of the new Network group depends on the network installation

chosen during the initial Setup.

NOTE: Previous versions of Microsoft Windows use SETUP /P to rebuild the

default groups.

MORE INFORMATION

================

Windows for Workgroups 3.11 Setup has several different options. You can

install Windows for Workgroups for no network functionality, for the

Windows for Workgroups network, for a primary network other than the

Windows for Workgroups network, or for the Windows for Workgroups network

and a secondary network. The icons available in the Network group are

dependent on the installation choice you make. The icons re-created by the

WINSETUP /P command are also dependent on your installation choice.

Example 1

---------

If you install Windows for Workgroups 3.11 with the No Windows Support For

Networks option, a Network group containing the following icons is

generated:

   Network Setup, Mail, Schedule+, and Remote Access.

WINSETUP /P re-creates the Network group as listed above.

Example 2

---------

If you install Windows for Workgroups 3.11 with the No Windows Support For

Networks option and choose not to install Mail and Schedule+, a Network

group containing the following icons is generated:

   Network Setup, Mail, and Remote Access.

NOTE: Mail is installed for Microsoft At Work PC Fax support. The only way

to not install Mail is to NOT install At Work PC Fax.

WINSETUP /P re-creates the Network group as mentioned above and adds a

Schedule+ icon with a plain design. (The plain icon is generated because

SCHDPLUS.EXE is not on your computer. If you choose not to install At

Work PC Fax and Mail, a plain Mail icon is also generated.) Microsoft has

confirmed this to be a problem in Windows for Workgroups 3.11.

Example 3

---------

If you install Windows for Workgroups 3.11 with the Microsoft Windows

Network (Version 3.11) option, with or without an additional network, a

Network group containing the following icons is generated:

   Network Setup, Mail, Schedule+, Remote Access, Log On/Off, Net Watcher,

   WinPopUp, WinMeter, and Chat.

WINSETUP /P re-creates the Network group with the following icons:

   Network Setup, Mail, Schedule+, and Remote Access.

Example 4

---------

If you install Windows for Workgroups 3.11 with the Microsoft Windows

Network (Version 3.11) option, with or without an additional network, and

choose not to install Mail and Schedule+, a Network group containing the

following icons is generated:

   Network Setup, Mail, Remote Access, Log On/Off, Net Watcher, WinPopUp,

   WinMeter, and Chat.

(Mail is installed for Microsoft At Work Fax support).

WINSETUP /P re-creates the Network group with the following icons:

   Network Setup, Mail, Schedule+, and Remote Access.

(Schedule+ has a plain icon because SCHDPLUS.EXE is not on your computer.)

Additional reference words: 3.11 wfw wfwg rebuild recreate redo

reset original gone disappeared blank empty setup /p progman.exe


WG0971: NDIS2SUP.386 Corrects Problems Restarting WFWG

Article ID: Q109447

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SUMMARY

=======

Microsoft has an Application Note, "WG0971: NDIS2SUP.386 Corrects Problems

Restarting Windows for Workgroups on Token Ring Machines."

If you have problems quitting and then restarting Windows for Workgroups

version 3.11 on systems using the NDIS version 2 IBM token ring driver,

IBMTOK.DOS, this Application Note may help. The WG0971 disk included with

this Application Note contains a new NDIS 2.0/3 support layer file,

NDIS2SUP.386, to correct these problems.

You can obtain this Application Note from the following sources:

 - CompuServe, GEnie and Microsoft OnLine

 - Microsoft Download Service (MSDL)

 - Microsoft FastTips Technical Library

 - 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 WG0971

==================

======================================================================

  Microsoft(R) Product Support Services Application Note (Text File)

     WG0971: NDIS2SUP.386 CORRECTS PROBLEMS RESTARTING WINDOWS FOR

                  WORKGROUPS ON TOKEN RING MACHINES

======================================================================

                                                  Revision Date: 12/93

                                                       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) 1993 Microsoft Corporation.  All Rights Reserved.    |

| Microsoft and MS-DOS are registered trademarks and Windows is a    |

| trademark of Microsoft Corporation.                                |

| IBM is a registered trademark of International Business Machines   |

| Corporation.                                                       |

 --------------------------------------------------------------------

Introduction

------------

You may have problems quitting Windows for Workgroups version 3.11 on

systems using the NDIS version 2 IBM(R) token ring driver

(IBMTOK.DOS). If you run, quit, and then restart Windows for

Workgroups (without restarting the computer), the computer usually

stops responding (hangs). With this driver, you may also notice that

your video display is reset after you quit Windows for Workgroups. For

example, if your video display is set to 50-line mode before you run

Windows for Workgroups, it may be reset to 25-line mode after you

quit.

The WG0971 disk included with this Application Note contains a new

NDIS 2.0/3 support layer file (NDIS2SUP.386) to correct these

problems.

To install the new NDIS2SUP.386 file

------------------------------------

1. Insert the enclosed WG0971 disk in the appropriate floppy disk

   drive.

2. To copy the file to the Windows SYSTEM directory, type the

   following at the MS-DOS command prompt and then press ENTER

      copy <drive>:\ndis2sup.386 <destination>

   where <drive> is the floppy disk drive containing the WG0971 disk

   and <destination> is the drive and directory of your Windows SYSTEM

   directory.

   For example, if the WG0971 disk is in drive A and your Windows

   directory is C:\WINDOWS, type the following at the MS-DOS command

   prompt and then press ENTER:

      copy a:\ndis2sup.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

   WG0971 in the Software Library by searching on the word WG0971,

   the Q number of this article, or S14497. WG0971 is a compressed,

   self-extracting file. After you download WG0971, 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 WG0971, download

   WG0971.EXE. WG0971.EXE is a compressed, self-extracting file. After

   you download WG0971.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 Customer

   Service at (206) 936-8661.

Additional reference words: 3.1 3.10 WFWG appnote


WG0970: VNETBIOS.386 Corrects Real-Mode Transport Problems

Article ID: Q109448

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SUMMARY

=======

Microsoft has an Application Note, "WG0970: VNETBIOS.386 Corrects

Real-Mode Transport Problems," that corrects problems you may

experience if you run multiple real-mode transports with Windows for

Workgroups when the protected-mode redirector (VREDIR.386) and the

protected-mode server (VSERVER.386) are loaded.

You can obtain this Application Note from the following sources:

 - CompuServe, GEnie, and Microsoft OnLine

 - Microsoft Download Service (MSDL)

 - Microsoft FastTips Technical Library

 - 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 WG0970

==================

======================================================================

  Microsoft(R) Product Support Services Application Note (Text File)

      WG0970: VNETBIOS.386 CORRECTS REAL-MODE TRANSPORT PROBLEMS

======================================================================

                                                   Revision Date: 1/94

                                                         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.                                |

| DEC is a registered trademark and Pathworks is a trademark of      |

| Digital Equipment Corporation.                                     |

 --------------------------------------------------------------------

Introduction

------------

If you run multiple real-mode transports with Windows for Workgroups

when the protected-mode redirector (VREDIR.386) and the protected-

mode server (VSERVER.386) are loaded, you eventually run out of

network control blocks (NCBs). As a result, you receive the following

error message:

   Too many outstanding commands.

The updated VNETBIOS.386 file included with this Application Note

corrects this problem by allotting more hardware control blocks

(HCBs).

To install the updated VNETBIOS.386 file

----------------------------------------

1. Insert the enclosed WG0970 disk in the appropriate floppy disk

   drive. Copy VNETBIOS.386 to your Windows SYSTEM subdirectory using

   the following command

      copy <drive>:\vnetbios.386 <destination>

   where <drive>is the floppy disk drive containing the WG0970 disk

   and <destination> is the drive and directory of your Windows SYSTEM

   subdirectory.

   For example, if the WG0970 disk is in drive A, and your Windows

   directory is C:\WINDOWS, type the following at the MS-DOS command

   prompt and then press ENTER:

      copy a:\vnetbios.386 c:\windows\system

2. Open the SYSTEM.INI file in Microsoft Windows for Workgroups Notepad,

   and edit the Network= entry by changing *vnetbios to vnetbios.386. For

   example, change

      Network=*vnetbios,*vwc,vnetsup.386,vredir.386,vserver.386

   to:

      Network=vnetbios.386,*vwc,vnetsup.386,vredir.386,vserver.386

3. Add the following line to the [386Enh] section:

      NumHCBs=32

   The default for NumHCBs is 32. If you are using DEC(R)

   Pathworks(TM), you must increase this value to 64 to avoid running

   out of NCBs. If other installed network components are using a lot

   of NCBs, you may need to use a value higher than 64. The NumHCBs

   entry has no hard-coded limit, but it is limited by memory. You

   shouldn't need to set NumHCBs higher than 96.

4. Save the SYSTEM.INI file, and then quit and restart Windows.

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

   WG0970 in the Software Library by searching on the word WG0970,

   the Q number of this article, or S14496. WG0970 is a compressed,

   self-extracting file. After you download WG0970, 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 WG0970, download

   WG0970.EXE. WG0970.EXE is a compressed, self-extracting file. After

   you download WG0970.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 Customer

   Service at (206) 936-8661.

Additional reference words: 3.1 3.10 WFWG appnote


Windows for Workgroups Err Msg:  Setup Error #3

Article ID: Q109495

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

SYMPTOMS

========

When you attempt to upgrade to Windows for Workgroups version 3.1 or 3.11,

you may receive the following error during Setup:

   Setup Error #3

   Setup is unable to copy the file

   ...

   For assistance, write down the number of

   this message, and then call product support.

   *To quit setup, press <F3>

CAUSE

=====

The error is generated if the WIN.INI file is larger than approximately 50

kilobytes in size.

After you run Windows or Windows for Workgroups for a period of time, the

WIN.INI file can become quite large, especially if you have installed a

third-party font package.

RESOLUTION

==========

To properly install Windows for Workgroups, reduce the size of the WIN.INI

file.

Additional reference words: 3.11


NETWORKS.WRI from Windows for Workgroups 3.11 (Part 2 of 4)

Article ID: Q109501

---------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------

SUMMARY

=======

The following information was taken from the Microsoft Windows for

Workgroups version 3.11 NETWORKS.WRI file.

MORE INFORMATION

================

2.2 More Information about Using Novell NetWare with Windows for

Workgroups 3.11

 - When you set up NetWare support in Windows for Workgroups, the

   value of the lastdrive command in your CONFIG.SYS file is set to P.

   When you restart your computer, your login directory is drive Q. If

   you have any NetWare login scripts, make sure they reference the

   correct drive letter for your login directory.

   When the lastdrive command is set to P, you can use letters from A to

   P to connect to other Windows for Workgroups computers or Windows NT

   or Microsoft LAN Manager servers. Letters after P are reserved for

   connecting to Novell NetWare servers.

 - Do not try to log in, log out, attach, or detach a Novell server

   from MS-DOS Prompt within Windows. You should log in before you start

   Windows for Workgroups, and attach or detach servers by using File

   Manager or Print Manager.

 - When you set up NetWare support in Windows for Workgroups for

   IPXODI.COM and LSL.COM, Setup adds the odihlp command to your

   AUTOEXEC.BAT file. It inserts it on the line following the ipxodi

   command. Do not change the order of these lines.

 - If you are using a token-ring network and the driver on your Novell

   server does not support source routing (for example, IBM token-ring

   drivers earlier than version 2.4), remove the ROUTE.COM statement

   from your AUTOEXEC.BAT file.

 - If you have problems connecting to a Novell server, make sure the

   Adapter Media Type setting in Network Setup matches your Novell

   NetWare software configuration. For more information, see Appendix C,

   "Troubleshooting," in The Microsoft Workgroup Add-On "User's Guide."

 - By default, NetWare allows you access to only 40 files at a time.

   When you are running applications with Windows, you can exceed this

   limit rather quickly. If you do, you might see unexpected error

   messages. To increase the file access limit, add the following line

   to the beginning of your NET.CFG file:

      file handles=60

   You should also add the following to your CONFIG.SYS file:

      files=60

 - If you get unusable output (such as incorrect fonts, garbled text,

   invalid page breaks, or blank lines) when you try to print to a

   NetWare server, you may need to edit your print-job configuration.

   Try using the NetWare PRINTCON utility to set the Auto Endcap and

   Enable Timeout options to No.

 - Swapping to a drive on a NetWare 286 server might make starting

   Windows for Workgroups take up to a minute. For information about

   controlling the location of your swap file, see Chapter 11, "Managing

   Memory and Performance," in the Microsoft Windows for Workgroups

   "User's Guide."

 - A NetWare file server does not include the directory entries dot

   (.) and double dot (..) as MS-DOS does. However, the NetWare shell

   (version 3.01 or later) can emulate these entries when applications

   attempt to list the files in a directory. If you have problems

   listing files or deleting directories, turn on the Show Dots feature.

   To do this, add the following line to the beginning of your NET.CFG

   file:

      show dots=on

   Turning on Show Dots will cause problems with earlier versions of

   some 80286-based NetWare utilities, such as BINDFIX.EXE and

   MAKEUSER.EXE. Make sure you upgrade these utilities if you upgrade

   your NetWare shell. For more information, contact your Novell dealer.

 - Redirected drives can look different in Windows for Workgroups than

   without Windows for Workgroups. For example, a device mapped as

   FileServerName/Volume:Directory will appear in Windows as

   FileServerName/Volume:\, showing the root of the file server's shared

   volume rather than the subdirectory. You can correct this with the

   MAP ROOT entry, as explained in the following information.

 - In some cases, Windows-based applications may change the default

   directory on a drive. This might cause problems if, for example, your

   path includes the current directory on a network drive (that is, your

   path includes a drive letter without a specific directory, such as z:

   instead of z:\system).

   You can prevent this problem by using MAP.EXE and LOGIN.EXE versions

   3.0 and later to set up false roots, or by choosing the MAP ROOT

   function when you are mapping a connection in File Manager. This

   feature simulates the MS-DOS subst command, which sets the root of a

   given drive to a directory designated by the user instead of to the

   true root of the volume.

   For example, suppose you normally mapped drive F to the HOME\TERRI

   directory on the SERVER\SYS volume, and then included F: in your

   path. You would do this by including the following command in your

   AUTOEXEC.BAT file or by typing the command before you start Windows:

      map f:=server\sys:home\terri

   The default directory on drive F would then be HOME\TERRI. To prevent

   Windows from changing this, you would replace that command with the

   following:

      map root f:=server\sys:home\terri

   This command would make the directory HOME\TERRI appear to be the

   root of drive F.

 - You can adjust the way Windows handles your network drive mappings

   by using the Network option in Control Panel.

   Usually, when you quit Windows for Workgroups, all of your drive

   mappings are restored to the way they were before you started Windows

   for Workgroups, and all changes you made while running Windows are

   lost. If you clear the Restore Drives option in the settings dialog

   box for NetWare, the mappings you made in Windows for Workgroups will

   remain when you quit.

   Typically, each instance of MS-DOS Prompt you start from Windows for

   Workgroups has its own set of drive mappings. Changes you make in one

   instance do not affect another. If you set the NWShareHandles option,

   drive mappings will instead be global, and changes to the mappings or

   the current drive made in one instance of MS-DOS Prompt will affect

   all other applications. If you are running a NetWare 286 server,

   setting NWShareHandles increases the number of workstations that can

   be connected to the server before the server runs out of available

   connections.

   See the Help available in the Network dialog box in Control Panel for

   more information on these options.

 - If you have applications or files that use extended characters

   (ASCII characters above 128) and you have problems viewing or using

   them, try adding the following line to your NET.CFG file:

      special uppercase = on

 - When you connect or disconnect network resources from File Manager,

   Print Manager, or Control Panel, pay attention to the state of the

   Permanent check box. If this option is selected when you make a

   connection, the connection is automatically made each time you

   restart Windows for Workgroups. To stop reconnecting, disconnect from

   the network resource with the Permanent check box selected. If the

   option is not selected when you disconnect, the connection is removed

   for the current Windows session but is reconnected when you restart

   Windows for Workgroups.

 - If you were running Novell NetBIOS before you set up Windows for

   Workgroups, the Setup program attempts to remove it. We do not

   recommend using the Novell NetBIOS protocol. Instead, use the IPX/SPX

   protocol that is compatible with NetBIOS.

   To install the IPX/SPX protocol that is compatible with NetBIOS:

   1. In the Networks group, choose the Network Setup icon.

   2. In the Network Setup dialog box, choose the Drivers button. The

      Network Drivers dialog box appears.

   3. Choose the Add Protocol button. The Add Network Protocol dialog

      box appears.

   4. Choose "IPX/SPX Compatible Transport with NetBIOS"  from the drop

      down list box. Then choose OK.

2.3 Changes to System Files

The following sections describe the changes that Setup makes to your

system files when you set up Windows for Workgroups 3.11 with these

common configurations.

2.3.1 IPXODI.COM and LSL.COM support over Ethernet or Token Ring Networks

When you install Windows for Workgroups 3.11 with IPXODI.COM and

LSL.COM support, the following lines are added to your SYSTEM.INI

file:

[386Enh]

network=*vnetbios,*vwc,vnetsup.386,vredir.386,vserver.386

transport=nwlink.386,nwnblink.386,netbeui.386

secondnet=vnetware.386, vipx.386

netmisc=ndis.386,msodisup.386

netcard=

InDOSPolling=FALSE

netcard3=

OverlappedIO=Off

[network]

multinet=netware3

winnet=wfwnet/00025100

[NetWare]

NWShareHandles=FALSE

RestoreDrives=TRUE

[network drivers]

netcard=

transport=

devdir=C:\WINDOWS

LoadRMDrivers=No

[NWNBLINK]

LANABASE=1

The following sample PROTOCOL.INI file is for a computer that

contains a DEC Etherworks Turbo/TP  Ethernet Network Adapter.

Bold lines designate lines specific to this network adapter and its

configuration.

NOTE: When using Novell's ODI drivers, the "BINDINGS=" should equal

the Novell MLID name.

[network.setup]

version=0x3110

netcard=ms$ewtrbtp,1,MS$EWTRBTP,4

transport=ms$nwlinknb,NWLINK

transport=ms$netbeui,NETBEUI

lana0=ms$ewtrbtp,1,ms$netbeui

lana1=ms$ewtrbtp,1,ms$nwlinknb

[net.cfg]

PATH=C:\NOVELL\net.cfg

[MS$EWTRBTP]

[Link Driver DEPCA]

Frame Ethernet_SNAP

Frame Ethernet_802.2

Frame Ethernet_II

Frame Ethernet_802.3

[NWLINK]

BINDINGS=DEPCA

[NETBEUI]

BINDINGS=DEPCA

LANABASE=0

SESSIONS=10

NCBS=12

The following sample PROTOCOL.INI file is for a computer that

contains a IBM Token Ring 16/4 Network Adapter.

Bold lines designate lines specific to this network adapter and its

configuration.

NOTE: When using Novell's ODI drivers, the "BINDINGS=" should equal

the Novell MLID name.)

[network.setup]

version=0x3110

netcard=ms$ibmtr4,1,MS$IBMTR4,4

transport=ms$nwlinknb,NWLINK

transport=ms$netbeui,NETBEUI

lana0=ms$ibmtr4,1,ms$netbeui

lana1=ms$ibmtr4,1,ms$nwlinknb

[net.cfg]

PATH=C:\NOVELL\net.cfg

[MS$IBMTR4]

[Link Driver TOKEN]

Frame Token-Ring

Link Driver TOKEN

[NWLINK]

BINDINGS=TOKEN

[NETBEUI]

BINDINGS=TOKEN

LANABASE=0

SESSIONS=10

NCBS=12

The following sample NET.CFG is for a computer with a DEC Etherworks

Turbo/TP Ethernet Network Adapter. You may need additional entries in

your NET.CFG file, depending on the way your network is set up.

Lines shown here in bold type are added when you install Windows for

Workgroups 3.11.

SHOW DOTS=ON

FILE HANDLES=60

Link Driver DEPCA

   Frame Ethernet_802.3

   INT 5

   PORT 300

   MEM D8000

   Frame Ethernet_II

   Frame Ethernet_802.2

   Frame Ethernet_SNAP

The following NET.CFG is for a computer with a IBM Token Ring 16/4

Network Adapter. You may need additional entries in your NET.CFG

file, depending on the way your network is set up.

Lines shown here in bold type are added when you install Windows for

Workgroups 3.11.

SHOW DOTS=ON

FILE HANDLES=60

Link Driver TOKEN

   Frame Token-Ring

2.3.2 IPX.COM Support

When you install Windows for Workgroups 3.11 with IPX.COM support,

the following lines are added to your SYSTEM.INI file:

[386Enh]

network=*vnetbios,*vwc,vnetsup.386,vredir.386,vserver.386

transport=

secondnet=vnetware.386,vipx.386

netmisc=

netcard=

InDOSPolling=FALSE

netcard3=nwsup.386,nwnblink.386

OverlappedIO=Off

[network]

multinet=netware3

winnet=wfwnet/00025100

DirectHost=No

[NetWare]

NWShareHandles=FALSE

RestoreDrives=TRUE

[network drivers]

netcard=

transport=

devdir=C:\WINDOWS

LoadRMDrivers=No

[NWNBLINK]

LANABASE=0

The following lines are added to your PROTOCOL.INI file (example for

a NE2000 network adapter):

[network.setup]

version=0x3110

netcard=ms$nwsupnb,1,MS$NWSUPNB,2

lana0=ms$nwsupnb,1,mono

[MS$NWSUPNB]

[NWSUP]

Adapters=MS$NWSUPNB

2.3.3 IPXODI.COM and LSL.COM support over an ArcNet Network

When you install Windows for Workgroups 3.11 with IPXODI.COM and

LSL.COM support over an ArcNet network, the following lines are added

to your SYSTEM.INI file:

[386Enh]

network=*vnetbios,*vwc,vnetsup.386,vredir.386,vserver.386

transport=

secondnet=vnetware.386,vipx.386

netmisc=

netcard=

InDOSPolling=FALSE

netcard3=nwsup.386,nwnblink.386

OverlappedIO=Off

[network]

multinet=netware3

winnet=wfwnet/00025100

directhost=no

[NetWare]

NWShareHandles=FALSE

RestoreDrives=TRUE

[network drivers]

netcard=

transport=

devdir=C:\WINDOWS

LoadRMDrivers=No

[NWNBLINK]

LANABASE=0

The following lines are added to your PROTOCOL.INI file:

[network.setup]

version=0x3110

netcard=ms$nwsupnb,1,MS$NWSUPNB,2

lana0=ms$nwsupnb,1,mono

[MS$NWSUPNB]

[NWSUP]

Adapters=MS$NWSUPNB

2.3.4 IPX.COM Support with an ArcNet Network

When you install Windows for Workgroups 3.11 with IPX/SPX support

over an ArcNet network, the following lines are added to your

SYSTEM.INI file:

[386Enh]

network=*vnetbios,*vwc,vnetsup.386,vredir.386,vserver.386

transport=

secondnet=vnetware.386,vipx.386

netmisc=

netcard=

InDOSPolling=FALSE

netcard3=nwsup.386,nwnblink.386

OverlappedIO=Off

[network]

multinet=netware3

winnet=wfwnet/00025100

directhost=no

[NetWare]

NWShareHandles=FALSE

RestoreDrives=TRUE

[network drivers]

netcard=

transport=

devdir=C:\WINDOWS

LoadRMDrivers=No

[NWNBLINK]

LANABASE=0

The following lines are added to your PROTOCOL.INI file:

[network.setup]

version=0x3110

netcard=ms$nwsupnb,1,MS$NWSUPNB,2

lana0=ms$nwsupnb,1,mono

[MS$NWSUPNB]

[NWSUP]

Adapters=MS$NWSUPNB

2.3.5 MSIPX support

Although we recommend that you upgrade from the MSIPX protocol to

either the IPXODI or IPX/SPX protocol, you can keep your MSIPX

support. This section describes the changes that are made to your

system files if you choose to keep MSIPX support when you upgrade

from Windows for Workgroups 3.1 to Windows for Workgroups 3.11.

The following lines are removed from CONFIG.SYS:

C:\WINDOWS\PROTMAN.DOS /I:C:\WINDOWS

C:\WINDOWS\WORKGRP.SYS

C:\WINDOWS\<NDIS MAC driver>.DOS

C:\WINDOWS\MSIPX.SYS

        The above lines are replaced by:

DEVICE=C:\WINDOWS\IFSHLP.SYS

The following is an example of a typical AUTOEXEC.BAT file once you

have upgraded to Windows for Workgroups 3.11

C:\WINDOWS\SMARTDRV.EXE /X

C:\WINDOWS\net start

C:\WINDOWS\msipx

C:\WINDOWS\netx

PROMPT $p$g

PATH C:\WINDOWS;C:\DOS

SET TEMP=C:\WINDOWS\TEMP

The following lines in SYSTEM.INI affect running Windows for

Workgroups 3.11 with MSIPX:

[386Enh]

network=*vnetbios,*vwc,vnetsup.386,vredir.386,vserver.386

transport=netbeui.386,nwlink.386,nwnblink.386

secondnet=vnetware.386

OverlappedIO=off

netmisc=ndis.386,ndis2sup.386,vipx.386

netcard=declan.386

InDOSPolling=FALSE

[network]

multinet=netware3

winnet=wfwnet/00025100

DirectHost=No

[NetWare]

NWShareHandles=FALSE

RestoreDrives=TRUE

[network drivers]

netcard=depca.dos

transport=*netbeui,msipx.sys,ndishlp.sys

devdir=C:\WINDOWS

LoadRMDrivers=Yes

[NWNBLINK]

LANABASE=1

This is a sample PROTOCOL.INI file for a computer using Windows for

Workgroups 3.11 with MSIPX. The adapter is a DEC Etherworks Turbo/TP

Network Adapter.

[network.setup]

version=0x3110

netcard=ms$ewtrbtp,1,MS$EWTRBTP,3

transport=ms$netbeui,NETBEUI

transport=ms$ipx,MS$IPX

transport=ms$nwlinknb,NWLINK

transport=ms$ndishlp,MS$NDISHLP

lana0=ms$ewtrbtp,1,ms$ipx

lana1=ms$ewtrbtp,1,ms$netbeui

lana2=ms$ewtrbtp,1,ms$nwlinknb

lana3=ms$ewtrbtp,1,ms$ndishlp

[protman]

DriverName=PROTMAN$

PRIORITY=MS$NDISHLP

[MS$EWTRBTP]

DriverName=DEPCA$

RamAddress=0xD800

Interrupt=5

MaxMulticast=8

MaxTransmits=16

IOAddress=0x300

AdapterName=DE200

[MS$IPX]

DriverName=IPX$

MediaType=Novell/Ethernet

BINDINGS=MS$EWTRBTP

[LANCE]

Adapters=MS$EWTRBTP

[NETBEUI]

DriverName=netbeui$

SESSIONS=10

NCBS=12

BINDINGS=MS$EWTRBTP

LANABASE=0

[NWLINK]

BINDINGS=MS$EWTRBTP

[MS$NDISHLP]

DriverName=ndishlp$

BINDINGS=MS$EWTRBTP

NOTE: Windows for Workgroups 3.11 Setup will detect MSIPX when

upgrading from Windows for Workgroups 3.1 and install support for it.

If you change your network configuration after upgrading to Windows

for Workgroups 3.11, however, Setup may remove MSIPX support, and you

will not be able to reinstall support for it. If this is the case,

you will have to upgrade to either IPX.COM, or IPXODI.COM and

LSL.COM.

Additional reference words: 3.11


Err Msg Changing Virtual Memory Setting: 32-Bit File Access...

Article ID: Q109510

-----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

-----------------------------------------------------------------------

SYMPTOMS

========

When you try to change your virtual memory configuration using the Enhanced

button in Control Panel, you may receive one of the following error

messages:

   32-bit File Access is not running because you started a real-mode

   network redirector before starting Windows.

-or-

   32-bit File Access was unable to run. This may be because you started

   the network before starting Windows, because Windows could not find the

   IFSHLP.SYS driver, or your hard disk(s) may be incompatible with 32-bit

   File Access.

CAUSE

=====

This error can occur when Windows for Workgroups 3.11 32-bit file access

(VCACHE) is enabled but the IFSHLP.SYS driver is not loading properly (or

at all) from the CONFIG.SYS file. IFSHLP.SYS must be loaded in order for

32-bit file access to function.

RESOLUTION

==========

To correct this problem, make sure that IFSHLP.SYS is being loaded from the

CONFIG.SYS file. For example, if your Windows directory is called WINDOWS

and is located on drive C, CONFIG.SYS should contain the following line:

   device=c:\windows\ifshlp.sys

If the IFSHLP.SYS driver is already being loaded from the CONFIG.SYS file,

verify that it is being loaded into memory with the MEM /C /P command.

IFSHLP should take up approximately 4 kilobytes of memory.

NOTE: If you are using Multi-Config commands in your CONFIG.SYS file, add

the above device statement to the [COMMON] section of your CONFIG.SYS file.

Additional reference words: 3.11 wfw wfwg


Repeating Window Displays with Microsoft 256-Color SVGA Driver

Article ID: Q109515

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows operating system version 3.1

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

SYMPTOMS

========

Using the generic Microsoft 800 x 600 256-color Super VGA driver with the

ATI VGA Wondercard (or a comparable card) with only 512 kilobytes video

memory creates a repeating window at the bottom of the screen.

WORKAROUND

==========

To work around this problem, use a 16-color video driver or the 256-color

driver that comes with the video card. The Microsoft 800 x 600 256-color

Super VGA video driver requires 1 megabyte of RAM on the video card to

properly display the 800 x 600 resolution with 256 colors.

Additional reference words: 3.11 svga adapter SVGA256


WG0974: VKDA.386 Corrects Keyboard Problems on Ambra Computers

Article ID: Q109561

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SUMMARY

=======

Microsoft has an Application Note, "WG0974: VKDA.386 Corrects Keyboard

Problems on Ambra Computers."

When you start Windows for Workgroups version 3.11 on an Ambra computer,

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

 - Microsoft Download Service (MSDL)

 - Microsoft FastTips Technical Library

 - 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 WG0974

==================

======================================================================

  Microsoft(R) Product Support Services Application Note (Text File)

    WG0974: VKDA.386 CORRECTS KEYBOARD PROBLEMS ON AMBRA COMPUTERS

======================================================================

                                                   Revision Date: 1/94

                                                         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.                                |

 --------------------------------------------------------------------

Introduction

------------

When you start Windows for Workgroups version 3.11 on an Ambra

computer, 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 to correct this problem.

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 <drive>:\vkda.386 <destination>

   where <drive> is the floppy disk drive containing the WG0974 disk

   and <destination> 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.

 - 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.

 - 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 Customer

   Service at (206) 936-8661.

The Ambra products included here are manufactured by vendor

independent of Microsoft; we make no warranty, implied or otherwise,

regarding these products' performance or reliability.

Additional reference words: 3.1 3.10 WFWG appnote hangs freezes lockup

locks up


WG0973: RMM.D32 Corrects 5-Second Delay When Starting Apps

Article ID: Q109562

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SUMMARY

=======

Microsoft has an Application Note, WG0973: RMM.D32 Corrects Five-Second

Delay When Starting Windows-Based Applications.

If you have 32-bit file access enabled and you have an MSIPX or a Novell

NE2000.COM ODI driver and IPXODI configuration, you may experience a delay

when you start a Windows-based application under Windows for Workgroups

3.11. The RMM.D32 file included with his Application Note may correct the

problem.

You can obtain this Application Note from the following sources:

 - CompuServe, GEnie, and Microsoft OnLine

 - Microsoft Download Service (MSDL)

 - Microsoft FastTips Technical Library

 - 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 WG0973

==================

======================================================================

  Microsoft(R) Product Support Services Application Note (Text File)

              WG0973: RMM.D32 CORRECTS FIVE-SECOND DELAY

             WHEN STARTING WINDOWS(TM)-BASED APPLICATIONS

======================================================================

                                                   Revision Date: 1/94

                                                         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.                                |

| Novell is a registered trademark of Novell, Inc.                   |

  -------------------------------------------------------------------

Introduction

------------

When you start a Windows-based application under Windows for

Workgroups 3.11, you may experience a five-second delay before any

disk activity occurs and the application begins to load. This delay

occurs if you have 32-bit file access enabled and you are using one of

the following network configurations:

   MSIPX

   Novell(R) NE2000.COM ODI driver and IPXODI

  NOTE: Microsoft has confirmed this problem occurs with version 1.34

  of the NE2000 multiple link interface device (MLID) driver (dated

  6/3/91) and the versions included in the Novell DOSUP7 and DOSUP8

  client files (dated 1/18/93 and 7/30/93, respectively).

This delay is caused by the 32-bit file access real-mode mapper

(RMM.D32) timing out. Once the application loads, it runs at normal

speed because it is now stored in the 32-bit disk cache (VCACHE.386).

You can work around this delay by disabling 32-bit file access or by

installing the updated RMM.D32 file contained on the WG0973 disk

included with this Application Note. The updated RMM.D32 file is not

hard-coded for a five-second time-out. Instead, it has a one-second

default time-out and can be configured using the RMMTimout= entry in

the SYSTEM.INI file.

To install the updated RMM.D32 file

-----------------------------------

Insert the enclosed WG0973 disk in the appropriate floppy disk drive.

Copy RMM.D32 to your Windows SYSTEM subdirectory using the following

command

   copy <drive>:\rmm.d32 <destination>

where <drive> is the floppy disk drive containing the WG0973 disk and

<destination> is the drive and directory of your Windows SYSTEM

subdirectory. For example, if your WG0973 disk is in drive A, and your

Windows directory is C:\WINDOWS, type the following at the MS-DOS

command prompt and then press ENTER:

   copy a:\rmm.d32 c:\windows\system

Configuring the RMM.D32 Time-Out Setting

----------------------------------------

To change the one-second default time-out value for the updated

RMM.D32 file, open your SYSTEM.INI file in Microsoft Windows for

Workgroups Notepad, locate the [386Enh] section, and add the

RMMTimeout= entry setting (which is expressed in milliseconds). For

example, to increase the time-out for RMM.D32 to two seconds, add the

following entry to the [386Enh] section of your SYSTEM.INI file:

   RMMTimout=2000

To decrease the time-out for RMM.D32 to half a second, change the

setting as follows:

   RMMTimout=500

TO OBTAIN THIS APPLICATION NOTE

===============================

 - On CompuServe, GEnie, and Microsoft OnLine, Application Notes

   are located in the Microsoft Software Library. You can find

   WG0973 in the Software Library by searching on the word WG0973,

   the Q number of this article, or S14508. WG0973 is a compressed,

   self-extracting file. After you download WG0973, 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 WG0973, download

   WG0973.EXE. WG0973.EXE is a compressed, self-extracting file. After

   you download WG0973.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 Customer

   Service at (206) 936-8661.

Additional reference words: 3.1 3.10 WFWG appnote


WFWG Err Msg: The 32-Bit File System Cannot Be Used When...

Article ID: Q109623

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft MS-DOS operating system version 6.2

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SYMPTOMS

========

When you try to use Windows for Workgroups 3.11 32-bit file access, you may

receive the following error message:

   The 32-bit file system cannot be used when DoubleSpace is running

   with MS-DOS 6.0. You can disable 32-bit file access by using

   Control Panel:

   1. Choose the 386 Enhanced icon.

   2. Choose Virtual Memory, and then choose Change.

   3. Clear the check box next to the 32-bit File Access, and then

      choose OK.

   You can use the 32-bit file system and DoubleSpace if you upgrade

   to MS-DOS 6.2.

CAUSE

=====

If you are using MS-DOS version 6.2 and still receive this error message,

either you are still using the MS-DOS 6.0 version of DBLSPACE.BIN, or you

are using AddStor DoubleTools version 1.2.

WORKAROUND

==========

To work around this problem, either run Control Panel and disable 32- bit

file access, or ensure you are using the MS-DOS 6.2 version of

DBLSPACE.BIN. To reinstall the MS-DOS 6.2 version of DBLSPACE.BIN:

1. Run MS-DOS 6.2 Setup with the /M parameter. For example, put your MS-

   DOS 6.2 Setup disk 1 in drive A and type "a:setup /m" (without the

   quotation marks) at the MS-DOS command prompt and then press ENTER.

2. Rename the CONFIG.NEW file (your original CONFIG.SYS file), to

   CONFIG.SYS. For example, type "ren config.new config.sys" (without the

   quotation marks) at the MS-DOS command prompt and then press ENTER.

3. Rename the AUTOEXEC.NEW file (your original AUTOEXEC.BAT file), to

   AUTOEXEC.BAT. For example, type "ren autoexec.new autoexec.bat"

   (without the quotation marks) at the MS-DOS command prompt and then

   press ENTER.

4. Restart your computer.

MORE INFORMATION

================

DoubleTools is manufactured by AddStor, a vendor independent of Microsoft;

we make no warranty, implied or otherwise, regarding this product's

performance or reliability.

Additional reference words: 3.11 wfwg double tools tool 6.00 6.20


Reinstalling the "Microsoft At Work PC Fax on FAX:" Driver

Article ID: Q109795

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SYMPTOMS

========

When you install a fax modem for Microsoft At Work PC Fax using Control

Panel, an additional printer driver called "Microsoft At Work PC Fax on

FAX:" is installed. If you remove this driver using Print Manager or

Control Panel, you cannot restore it. Reinstalling Microsoft At Work PC Fax

does not restore the printer driver to the printer driver list.

RESOLUTION

==========

To reinstall the Microsoft At Work PC Fax printer driver, you must rename

the EFAXPUMP.INI and MSMAIL.INI files before reinstalling Microsoft At Work

PC Fax driver. If you delete the Microsoft At Work PC Fax on FAX driver

from your hard disk (EFAXDRV.DRV), you need to uninstall and reinstall

Microsoft At Work PC Fax using Windows Setup.

If You Delete Microsoft At Work PC Fax Driver (EFAXDRV.DRV)

-----------------------------------------------------------

If you delete the Microsoft At Work PC Fax driver (EFAXDRV.DRV) from your

hard disk, you can use the following procedure to reinstall it:

 1. From the Main group, run Windows Setup (WINSETUP.EXE).

 2. From the Options menu, choose Add/Remove Windows Components.

 3. Choose the Select Files button for Accessories.

 4. From the list box on the right, choose Microsoft At Work PC Fax.

 5. Choose Remove.

 6. Choose OK twice.

 7. Choose Yes.

 8. From the Options menu, choose Add/Remove Windows Components.

 9. Choose the Select Files button for Accessories.

10. From the list box on the left, choose Microsoft At Work PC Fax.

11. Choose Add.

12. Choose OK twice.

13. Follow the procedure in the following section to reinstall the

    "Microsoft At Work PC Fax on FAX:" printer driver.

If You Remove the "Microsoft At Work PC Fax on FAX:" Printer Driver

Using Print Manager or Control Panel

-------------------------------------------------------------------

If you remove the "Microsoft At Work PC Fax on FAX:" printer driver using

Print Manager or Control Panel, use the following procedure to restore it:

1. Rename EFAXPUMP.INI and MSMAIL.INI to other names. For example,

   type the following at the MS-DOS command prompt and press ENTER

   after each line:

      ren c:\windows\efaxpump.ini efaxpump.pss

      ren c:\windows\msmail.ini msmail.pss

2. Reinstall the fax option from Control Panel.

   The fax print driver settings are restored to the WIN.INI file.

3. Restore the EFAXPUMP.INI and MSMAIL.INI files. For example, type the

   following at the MS-DOS command prompt and press ENTER after each line:

      copy c:\windows\efaxpump.pss c:\windows\efaxpump.ini

      copy c:\windows\msmail.pss c:\windows\msmail.ini

Additional reference words: 3.11 awfax efax


How to Flush 32-Bit File Access Cache (VCACHE)

Article ID: Q110092

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

You can commit the contents of the 32-bit file access cache (VCACHE) to

disk by running MS-DOS Prompt from the Main group and the pressing CTRL+C

or CTRL+BREAK.

CTRL+C and CTRL+BREAK cause MS-DOS to issue a disk reset, which causes

32-bit file access to flush, but not invalidate. the cache.

Additional reference words: 3.11 VFAT


Windows for Workgroups 3.11 Disk 8 Contains Disk 1 Files

Article ID: Q110162

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SUMMARY

=======

In several of the 3.5-inch Windows for Workgroups version 3.11 disk sets,

Disk 8 contains the Disk 1 files. Microsoft has made the correct Disk 8

files available on the Microsoft Download Service (MSDL) in the self-

extracting file MSWFW8.EXE.

You can obtain these files by downloading them or by contacting Microsoft

Product Support Services (PSS) Windows for Workgroups support. If you have

a modem, you can call the MSDL at (206) 936-6735 and download the file. For

more information on the MSDL, query on the following words in the Microsoft

Knowledge Base:

   msdl and instructions

MORE INFORMATION

================

The following installation and usage instructions are included on the

READNOW.TXT file included in the MSWFW8.EXE self-extracting EXE file:

To create a Windows for Workgroups version 3.11 3.5-inch, 1.44 megabyte

Disk 8:

 1. Create a temporary directory on your hard disk drive. For example, type

    "MD C:\MSWFW8" (without the quotation marks) at the MS-DOS command

    prompt and then press ENTER.

 2. Copy MSWFW8.EXE to the temporary directory created in step 1. For

    example, type "copy a:mswfw8.exe c:\mswfw8" (without the quotation

    marks) at the MS-DOS command prompt and then press ENTER.

 3. Change to drive C by typing "c:" (without the quotation marks) at the

    MS-DOS command prompt and then press ENTER.

 4. Change to the MSWFW8 directory by typing "cd \mswfw8" (without the

    quotation marks) at the MS-DOS command prompt and then press ENTER.

 5. Run MSWFW8.EXE by typing "c:\mswfw8\mswfw8" (without the quotation

    marks) at the MS-DOS command prompt and then pressing ENTER. This

    expands the Windows for Workgroups 3.11 files.

 6. Delete MSWFW8.EXE from the temporary directory. For example, type

    "del c:\mswfw8\mswfw8.exe" (without the quotation marks) at the MS-DOS

    command prompt and then press ENTER.

 7. Copy the remaining files to newly formatted a high-destiny (1.44

    megabyte), 3.5-inch disk. For example, type "copy c:\mswfw8\*.* a:"

    (without the quotation marks) at the MS-DOS command prompt and then

    press ENTER.

 8. Change the volume label on the floppy disk to MSWFW8 using the LABEL

    program. For example, type "label a: mswfw8" (without the quotation

    marks) at the MS-DOS command prompt and then press ENTER.

 9. Delete the files in the temporary directory on your hard disk drive.

    For example, type "del c:\mswfw8\*.*" (without the quotation marks) at

    the MS-DOS command prompt and then press ENTER.

10. Remove the temporary C:\MSWFW8 directory. For example, type

    "rd c:\mswfw8" (without the quotation marks) at the MS-DOS command

    prompt and then press ENTER.

You should now be able to use your newly created Windows for Workgroups

Disk 8 to install Windows for Workgroups.

Additional reference words: 3.11 disk1 disk8


Incoming Faxes Received but Never Appear in Inbox

Article ID: Q110163

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SYMPTOMS

========

If you are using Windows for Workgroups version 3.11 At Work PC Fax and a

CAS modem, you may receive incoming faxes that do not appear in your Inbox.

CAUSE

=====

This problem occurs when AutoAnswer for At Work PC Fax is set to Off and

AutoAnswer in the CAS manager is set to On. As a result, the CAS board

receives the fax but Microsoft Mail ignores it.

RESOLUTION

==========

To correct this problem, run Control Panel, choose At Work PC Fax, and set

AutoAnswer to On.

Additional reference words: 3.11


Cannot Dial Automatically from Works 2.0 with WFWG 3.11

Article ID: Q110178

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SYMPTOMS

========

When you run Microsoft Works version 2.0 for Windows under Microsoft

Windows for Workgroups version 3.11, the automatic dialing feature does not

work correctly. The modem dials the number correctly, the phone begins to

ring, Works instructs you to pick up the phone and choose Yes; however,

when you do this, Works does not turn off the modem and transfer the call

to the phone. As a result, you hear the person you're calling over the

modem speaker, not the phone speaker.

This problem does not occur with Works version 3.0 for Windows, nor does it

occur with the MS-DOS-based versions of Works.

CAUSE

=====

This problem is caused by a conflict between Works 2.0 and the Windows for

Workgroups 3.11 communication driver (COMM.DRV).

STATUS

======

Microsoft is researching this problem and will post new information here in

the Microsoft Knowledge Base as it becomes available.

Additional reference words: 3.11 dial this number tools menu autodial


MoreFonts Not Supported with Windows for Workgroups

Article ID: Q110190

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

----------------------------------------------------------------------

SYMPTOMS

========

If you use MoreFonts with Windows for Workgroups, the mouse cursor may

disappear but not lose its functionality. However, the opposite may also

occur: the mouse cursor may remain visible but not function. The keyboard

may also lose partial or full functionality.

MORE INFORMATION

================

According to MicroLogic Technical Support, MoreFonts is not supported under

any version of Windows for Workgroups. This applies to both stand-alone and

network versions of MoreFonts.

RESOLUTION

==========

MicroLogic recommends using its MoreType font conversion utility to convert

the MoreFonts fonts to TrueType fonts. Once the conversion is completed,

MoreFonts can be completely removed from the system. Contact MicroLogic

Technical Support for information about the MoreType utility.

MoreFonts is manufactured by MicroLogic, a vendor independent of Microsoft;

we make no warranty, implied or otherwise, regarding this product's

performance or reliability.

Additional reference words: 3.10 more fonts true type more type


Cannot Find NONET.DRV with WordPerfect 6.0 for Windows

Article ID: Q110191

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

----------------------------------------------------------------------

SYMPTOMS

========

During installation of WordPerfect 6.0 for Windows under Microsoft Windows

for Workgroups version 3.11, you may receive the following error

   Cannot find <entry>.DRV

where <entry> is the text referenced on the Multinet= line in the [Network]

section of the SYSTEM.INI file.

CAUSE

=====

This error is referencing a file that does not exist. During the

installation of WordPerfect 6.0 for Windows, the setup program reads the

Multinet= entry and looks for a .DRV file whose name reflects the entry.

Since no such file exists, the above error is generated.

Default installations of Windows for Workgroups contain a Multinet=NONET

entry; therefore, the most common occurrence of the error will be as

follows:

   Cannot find NONET.DRV.

If you ignore the error during installation, it will be reproduced each

time you start WordPerfect 6.0.

WORKAROUND

==========

At an MS-DOS command prompt, you can create a zero-byte file to match the

Multinet= entry by using the following syntax

   type aaa > <entry>.drv

where <entry> matches the filename referenced in the error message. This

generates a "File not found - AAA" error, which can be ignored.

Move the newly created <entry>.DRV file to the Windows SYSTEM subdirectory.

This prevents the error message from occurring.

For more information concerning this error, contact WordPerfect Technical

Support.

MORE INFORMATION

================

WordPerfect is manufactured by WordPerfect Corporation, a vendor

independent of Microsoft; we make no warranty, implied or otherwise,

regarding this product's performance or reliability.

Additional reference words: 3.11 NONET NETWARE3


WFWG 3.11 Err Msg: General Protection Fault in WFWSETUP.DLL

Article ID: Q110318

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SYMPTOMS

========

When you upgrade to Windows for Workgroups 3.11, you may receive the

following error message:

   General Protection fault in WFWSETUP.DLL

If you choose OK, you may receive a general protection (GP) fault in

USER.EXE and then the following error message may be displayed:

    Standard Mode: Bad Fault in MS-DOS Extender.

    Fault: 000D Stack Dump: 0000 0000 0070

    Raw fault frame: EC=0000 IP=5EF7 CS=03AF FL=3087 SP=FFEE SS=02DF

CAUSE

=====

The GP fault occurs because of the number and size of .INF files. The

Windows for Workgroups Setup program loads all of its .INF files when it

starts. However, Setup has only a 32-kilobyte (K) stack allocated for its

use. If the size of all the .INF files exceeds this 32K limit, the stack

boundary is exceeded and you receive a GP fault.

RESOLUTION

==========

To correct this problem, rename (or delete) some of the additional .INF

files in the Windows SYSTEM subdirectory to filenames with extensions other

than .INF. After you have deleted or renamed the files, restart Setup.

NOTE: Never rename or delete the SETUP.INF file in this subdirectory.

Additional reference words: 3.11 wfw wfwg 311 gpf setup gp fault


Recovering Folders from a Corrupted Microsoft Mail File

Article ID: Q110552

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

 - Microsoft Mail for Windows, versions 3.0 and 3.2

--------------------------------------------------------------------

SUMMARY

=======

The following information is provided by Microsoft "as-is," we make no

guarantee that the steps below will retrieve all messages.

If your Microsoft Windows for Workgroups Mail or Microsoft Mail for Windows

mail file (.MMF) becomes corrupted, you may be able to retrieve some or all

of the folders.

MORE INFORMATION

================

To retrieve folders:

1. Rename the corrupted .MMF file to OLD.MMF.

2. Run Mail and allow it to create a new .MMF file.

3. From the File menu, choose Import Folder.

4. Select the OLD.MMF file.

5. Choose OK.

Additional reference words: 3.11 wfw wfwg msmail.mmf msmail export

damaged messages files


At Work PC Fax ErrMsg: Attachment Type Was Not Supported

Article ID: Q110567

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SYMPTOMS

========

When you send files as attachments using Microsoft At Work PC Fax, you may

receive the following error message:

   Error: Attachment type was not supported

CAUSE

=====

This problem occurs if you send a fax with an unprintable attachment using

the Facsimile Format option.

RESOLUTION

==========

Since you cannot send unprintable files using a Group3 fax, you must change

your message format from Facsimile Format to Email Format. For more

information, see the Setting Fax Options in the Microsoft At Work PC Fax

chapter in your Microsoft Workgroup Add-On for Windows "User's Guide."

NOTE: Facsimiles sent with the Email Format option can only be sent to

another Microsoft At Work PC Fax using a Class1 modem.

You may still receive the error message noted above with a printable

document. This problem occurs when there is no associated object-linking-

and-embedding (OLE) server capable of printing your document.

To work around this problem, print the document as follows:

1. From the File menu of your application, choose Print.

2. Choose Setup.

3. Choose Microsoft At Work PC Fax on FAX and then choose OK.

NOTE: These steps may vary slightly, depending on the application from

which you are printing.

MORE INFORMATION

================

To determine if no associated OLE server capable of printing your document

exists, try to drag the document file from File Manager to Print Manager.

If this fails, no associated OLE server capable of printing your document

is available.

Additional reference words: 3.11


Gateway with PCI Bus Hangs with Communication Applications

Article ID: Q110568

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SYMPTOMS

========

Gateway machines with a PCI bus may stop responding (hang) or exhibit other

unexpected behavior if you are using communication applications such as

Microsoft At Work PC Fax or Microsoft Terminal under Windows for Workgroups

version 3.11.

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

=====

These problems occur because 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.

RESOLUTION

==========

To correct this problem, edit the SYSTEM.INI file with a text editor (such

as Microsoft Windows Notepad) and add the COMxFIFO=0 entry (where x is the

COM port your modem is using) to the [386Enh] section. For example, if your

modem is on COM 1, add COM1FIFO=0 to the [386Enh] section of the SYSTEM.INI

file.

Additional reference words: 3.11 gateway2000 exit restarted


Deleting Fax from Outbox Does Not Remove It from the Queue

Article ID: Q110572

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SYMPTOMS

========

If a fax is set for retry, and you delete it from the Outbox, it remains in

the fax queue and Microsoft At Work PC Fax continues trying to send it.

CAUSE

=====

Microsoft At Work PC Fax is not designed to allow faxes to be deleted

from the Outbox. The only supported way to cancel a fax is to use the

queue.

Additional reference words: 3.11


How to Re-Create the Network Group and Its Program Icons

Article ID: Q110739

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SUMMARY

=======

If a program icon in the Network group or the Network group itself is

deleted from Program Manager, you can restore the icons and group by

reinstalling the network software.

MORE INFORMATION

================

To do so:

 1. From the Main group, run Windows Setup.

 2. From the Options menu, choose Change Network Settings, and then choose

    the Networks button.

 3. Note the current selections in this dialog box, and then choose

    "No Windows support for networks." Choose the OK button three times,

    then choose the Continue button.

 4. From the Options menu, choose Change Network Settings, and then choose

    the Networks button.

 5. Choose Install Microsoft Windows Network (or use the settings you noted

    in step 4) and then choose OK.

 6. Configure your Network Settings in the Network Setup dialog box and

    then choose OK.

    NOTE: If you previously chose to share your files or printers with

    others, you must choose the Sharing button and reset these options to

    enable sharing.

 7. Configure Windows for Workgroups for your network card and then choose

    OK. If you don't know what card to select, choose the Detect button.

 8. Ensure the User Name, Workgroup, and Computer Name are correct and then

    choose OK.

 9. Choose No until Windows Setup indicates your AUTOEXEC.BAT, SYSTEM.INI,

    and PROTOCOL.INI files have been updated, then choose OK.

10. Choose Restart Computer.

Additional reference words: 3.11 wfwg


Printer Drivers Included in WFWG 3.1 But Not WFWG 3.11

Article ID: Q110741

----------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

----------------------------------------------------------------

Some of the printer drivers included in Windows for Workgroups version 3.1

are not included in Windows for Workgroups version 3.11. The following list

of printer drivers are included with version 3.1 but are not included in

version 3.11. These printer drivers are available from the Microsoft

Download Service (MSDL) at (206) 936-6735.

   C-Itoh / AT&T 470/475

   C-Itoh 8510

   Hermes H 606 PS (13 fonts)

   Hermes H 606 PS (35 fonts)

   IBM Color Printer

   Olivetti DM 109

   Olivetti DM 309

   TI 850/855

   Triumph Adler SDR 7706 PS13

   Triumph Adler SDR 7706 PS35

   Unisys AP9415

Additional reference words: 3.11 wfwg


Faxes from Server Are Sent Before Faxes from Other Machines

Article ID: Q110742

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SYMPTOMS

========

If several items that have been sent from other machines on the network are

in the Microsoft At Work PC Fax queue, and a fax is sent from the server,

the server blocks all faxes in the queue (regardless of priority) and sends

the local fax job. The faxes in the queue are sent after the local job is

finished.

CAUSE

=====

The design of Microsoft At Work PC Fax does not balance the priority of

faxes sent from other machines on the network with faxes sent from the fax

server. Faxes sent from a fax server always have higher priority than faxes

sent to the server from other machines on the network.

Additional reference words: 3.11 awfax priority


Specifying Command-Line Parameters for NDIS 2 Drivers

Article ID: Q110923

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

--------------------------------------------------------------------

SUMMARY

=======

When you use Windows for Workgroups 3.11 with certain NDIS 2 network

adapter drivers, you must specify command-line parameters to make these

drivers load correctly. These parameters can be added by editing the

SYSTEM.INI file with a text editor such as Microsoft Windows Notepad.

Below is an example in which the real-mode drivers for a Xircom credit card

adapter are loaded in the AUTOEXEC.BAT file:

   CECFG DRIVER=NDIS

   CENDIS

When these NDIS 2 drivers are loaded with Windows for Workgroups 3.11, they

are loaded on the transport= line of the SYSTEM.INI file. To pass the

DRIVER=NDIS parameter to CECFG.EXE, add the following line to the [network

drivers] section of the SYSTEM.INI file:

   [network drivers]

   CECFG.EXE="Driver=NDIS"

Additional reference words: wfw wfwg 3.11 ndis2 cmd line


No Master Browse Server Available with TCP/IP

Article ID: Q110924

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

--------------------------------------------------------------------

SYMPTOMS

========

Browsing in Windows for Workgroups 3.11 may not work if TCP/IP is the only

protocol installed.

CAUSE

=====

When TCP/IP is the only protocol installed, there is no Browse Master

election.

RESOLUTION

==========

To correct this problem:

 - Increase NBSESSIONS in the [TCPIP] section of the PROTOCOL.INI file to

   10. Add a setting called NUMNAMES to the [TCPIP] section of the

   PROTOCOL.INI file and set it to 11.

   -or-

 - Add the line MaintainServerList=YES to the [NETWORK] section of the

   SYSTEM.INI file.

   -or-

 - Use NetBEUI in conjunction with TCP/IP.

Additional reference words: 3.11 wfw tcp ip tc/pip wfwg browsing browser

masterbrowser browsemaster browse master


GVC Ethernet Netcard Requires Updated Driver for WFW 3.11

Article ID: Q110925

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 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.

SUMMARY

=======

To use the GVC 16-bit Ethernet cards with Windows for Workgroups version

3.11, you may need to upgrade to latest GVC NDIS 2.0 driver, which is dated

11/23/93.

If you are using a previously released driver, you may experience various

problems, including inability to see other machines across the network in

Windows for Workgroups even though you can see them from the MS-DOS command

prompt.

MORE INFORMATION

================

GVC has several NIC2000 models and one NIC2003 model that can use its new

NDIS driver in Windows. If you are using Windows for Workgroups 3.10, GVC

recommends using the NE2000 compatible driver; however, this driver does

not work with Windows for Workgroups 3.11. The new GVC driver handles

issues with the upper memory block (UMB) that have surfaced since the

release of MS-DOS 6.0 and Windows for Workgroups 3.11.

You can downloaded the new driver from the GVC bulletin board service at

(201) 579-2380. The name of the driver is NIC2000.DOS and is dated

11/23/93.

The GVC Ethernet Netcard is manufactured by GVC, a vendor independent of

Microsoft; we make no warranty, implied or otherwise, regarding these

products' performance or reliability.

Additional reference words: 3.11 wfwg network card nic


Removing WinFax Pro from Windows for Troubleshooting

Article ID: Q110981

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows operating system version 3.1

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

--------------------------------------------------------------------

SUMMARY

=======

This article lists the items added to the WIN.INI and SYSTEM.INI files by

WinFax Pro products. For testing purposes, you may need to disable WinFax

Pro by commenting out these lines.

MORE INFORMATION

================

WinFax Pro 2.0 and WinFax Lite make the following changes in the WIN.INI

file:

 - Adding a [winfax] section.

 - Adding an entry in the [printerports] and [devices] sections for the

   WinFax printer driver.

 - Adding the following two entries in the [windows] section:

      device=WINFAX,WINFAX,COM1:

      DelrinaAppInstalled=Yes

WinFax Pro 3.0 makes two additional changes to the WIN.INI file:

 - Adding a [wfxpblinks] section.

 - Adding an [anyfax] section.

The SYSTEM.INI file is not changed unless the COMM.DRV is changed to

accommodate a 16550 UART or the COMxFIFO setting is changed in the [386enh]

section to disable FIFO buffering. The COMxFIFO setting is ignored unless

the serial port has a 16550 UART.

NOTE: If the COMM.DRV changed, it equals WFXCOMM.DRV. In this case, comment

out the line by adding a semicolon to its beginning, and then insert a new

line with the setting COMM.DRV=COMM.DRV.

You can comment out all these changes by adding a semicolon before each

line that contains WinFax Pro information, including any section headers in

brackets.

Additional reference words: WFWG 3.10 light


Shiva Support for Windows for Workgroups 3.11

Article ID: Q111002

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SUMMARY

=======

Shiva is incorporating support for Microsoft Windows for Workgroups

version 3.11 in its upcoming Shiva Remote 3.1 client software. Shiva

Remote 3.1 works in Windows 3.1 and Windows for Workgroups 3.11. Shiva

Remote 3.1 will be released as the standard client software shipped

with all Shiva products.

MORE INFORMATION

================

Dial-In Support Included in Shiva Remote 3.1

--------------------------------------------

NetBEUI:

    Windows for Workgroups 3.11 peer-to-peer file sharing

    Microsoft LAN Manager

    Windows NT 1.0

IPX:

    MSIPX - Windows for Workgroups 3.11 peer-to-peer file sharing

    Novell Client Kit version 1.02 (NETX.EXE only)

    Novell Client Kit version 1.1 (VLM) - NetWare 2.2, 3.12, 4.01,

Personal:

    NetWare 1.0

TCP/IP:

    Microsoft TCP/IP for Windows for Workgroups 3.11

    Novell - LAN WorkPlace

    FTP Software - PC/TCP

    SunSelect - PC-NFS

    NetManage - Chameleon

LLC/802.2:

    IBM SNA Connectivity through 5250 terminal emulation

Dial-Out Support Included in Shiva Remote 3.1

---------------------------------------------

Shiva supports shared dial-out from within Windows for Workgroups, using

either IPX or TCP/IP. To connect to a shared communications port across the

LAN, Shiva provides a special communications driver that replaces the

Microsoft communications driver. This driver redirects one of the user's

serial ports to a shared serial port available on the network. These shared

serial ports, on either the Shiva NetModem/E or LanRover, can be pooled to

allow the user to connect to the first available port.

Availability

------------

Shiva Remote 3.1 will be released on March 31, 1994. By the end of April

1994, it will be incorporated into all Shiva products, including

LanRover/E, LanRover/T, and NetModem/E. It will also be available upon

release on the Shiva bulletin board service (BBS) and as a nominally priced

upgrade for Shiva customers. Beta versions of Shiva Remote will be

available in February 1994. To apply to be on the beta list, send

electronic mail to mikef@shiva.com, or send a fax to Mike Feinstein at

(617) 270-8599.

NOTE: The original Shiva Remote 1.0 still supports Windows for Workgroups

3.1 but does not support Windows for Workgroups 3.11. Shiva Remote 1.0 will

only be available on the Shiva BBS in order to support the current

installed base. The Shiva 3.0 MS-DOS client supports remote file sharing

using the Windows for Workgroups 3.11 MS-DOS client software.

Additional reference words: 3.11


List of Hardware Devices and Common I/O Base Address Conflicts

Article ID: Q111019

---------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

---------------------------------------------------------------

SUMMARY

=======

When you install a network adapter card, sound card, or other hardware

adapter, you typically have to choose an input/output (I/O) base address.

If the base address you choose for your network adapter card is currently

being used by another hardware adapter card, Protocol Manager may report an

unsuccessful binding, or your system may stop responding (hang).

This article provides a list of I/O base addresses that may already be in

use on your system and what hardware devices use them.

NOTE: Most network adapter cards have the default I/O base address 300.

MORE INFORMATION

================

The I/O base address for each hardware adapter card installed on your

system must be unique to avoid potential problems. Before you install your

network adapter card, you should know which I/O base addresses are

currently in use by existing hardware adapter cards installed in your

system. I/O base addresses are typically set using jumpers on the card or

using a software configuration program in EPROM.

The following list shows I/O base address ranges commonly used by hardware

devices (other than network adapter cards) and what I/O base address they

would conflict with.

The I/O base address list does not list all available I/O base address. In

addition, some of these addresses may not be supported by your network

adapter card. For more information on I/O base addresses supported by your

network adapter card, consult your hardware documentation or contact the

network adapter card vendor.

Potential Conflicting Devices and Their I/O Base Addresses

                                                   Potential I/O Base

Device                              Range Used       Address Conflict

---------------------------------------------------------------------

Game Controller                      200-20F               200

Expansion unit                       210-217               200

LPT2:                                278-27F               260

LCD display on Wyse 2108 PC                                280

COM4                                 2E8-2EF               2E0

COM2                                 2F8-2FF               2E0

XT Hard drives                                             320

LPT1:                                378-37F               360

Secondary Bi-Sync interface          380-38C               380

Primary Bi-Sync interface            3A0-3A9               3A0

Monochrome Display/Printer Card      3B0-3BF               3A0

EGA Adapter                          3C0-3CF               3C0

CGA Display                          3D0-3DF               3C0

COM3                                 3E8-3EF               3E0

Floppy Controller                    3F0-3F7               3E0

COM1-Asynchronous Communications     3F8-3FF               3E0

NOTE: Some video cards use I/O base address 320. If you are using I/O base

address 320 for your network adapter card and are experiencing problems,

try a different I/O base address.

The information in this article can also be found on page 20 of the SMC

Elite 16 network card manual.

Additional reference words: 3.10 3.11 nic interface board boards


Hardware Failure Errors with RAS & US-Robotics 14400 Sportster

Article ID: Q111093

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

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.

SYMPTOMS

========

When you use Remote Access Services (RAS) with a US-Robotics Internal 14400

Sportster, you may receive the following error messages:

   Error 692: Hardware Failure in attached port or device

RESOLUTION

==========

To correct this problem, edit the modem initialization entry

(COMMAND_INIT=) in the MODEM.INF file and 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 V1 S0=0 S2=128 S7=55 W1 S95=44

This issues a reset command first, and then resets the modem to the factory

defaults.

Additional reference words: 3.11 string


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, you receive the following error message:

   NETBIOS error 640: a netbios error has occurred (with failed code 0x5)

This problem may occur with some modems and not with others.

CAUSE

=====

The "NETBIOS error 640" message can be caused by the following:

 - 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 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.

RESOLUTION

==========

If you receive the "error 640" message several seconds after connecting to

the RAS server, use the following procedure to determine what is causing

the NetBIOS error. After each step, try to establish a RAS connection.

1. Choose Setup and ensure RAS is configured for the correct modem.

2. Ensure you are using the correct cabling. For more information, run RAS

   and check the online help.

3. Ensure you are not logged on to the domain you are trying to connect to

   before connecting with RAS.

4. Ensure 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.

   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 this 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. If you are trying to connect to a Microsoft LAN Manager OS/2 RAS server,

   ensure 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.

Additional reference words: 3.11 err msg errmsg


Windows for Workgroups 3.11 Point-to-Point Server Update

Article ID: Q111292

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SUMMARY

=======

The Windows for Workgroups 3.11 Point-to-Point Server updates the Remote

Access files currently shipping with Windows for Workgroups 3.11. The Point-

to-Point Server enables a Windows for Workgroups 3.11 system to accept

incoming calls from other Remote Access clients (such as those currently

included with Windows for Workgroups 3.11). This allows anyone with the

necessary password to access a computer's shared resources from any remote

PC.

If you have a modem, you can download this update as an executable

file (WFWPTP.EXE) from the following sources:

 - CompuServe, GEnie, and Microsoft OnLine

 - Microsoft Download Service (MSDL)

 - The Internet (Microsoft anonymous ftp server)

For more information, see the "To Obtain This Update" section at the

end of this article. If you don't have a modem, you can obtain this

update from Microsoft Sales Information Center by calling (800)

426-9400 and asking for part number 261-051-005.

MORE INFORMATION

================

The Windows for Workgroups 3.11 Point-to-Point Server enables remote

users to gain access only to the resources shared on the local

machine. If remote users need access to all shared network resources

(such as shared files and printers located elsewhere on the network),

the computer answering the incoming calls must be running Microsoft

Windows NT, Windows NT Advanced Server, or Microsoft LAN Manager in

addition to Remote Access Service. This ensures that greater security

is available before entire network access is granted.

Installing Windows for Workgroups 3.11 Point-to-Point Server

------------------------------------------------------------

Refer to the README.TXT file provided for installation instructions

and release note information.

Addendum to the Microsoft Software License Agreement

----------------------------------------------------

The following is an addendum to the Microsoft software license agreement

for Microsoft Windows for Workgroups version 3.11, Windows 3.1 with built-

in networking:

The files included in WFWPTP.EXE are intended to replace the corresponding

files provided with Microsoft Windows for Workgroups version 3.11. Upon

installation, these files become a part of the Windows for Workgroups

operating system and are subject to the same license terms and conditions

as the Windows for Workgroups version 3.11 product you previously acquired

from Microsoft Corporation. Any other use of these files is prohibited.

To Obtain This Update

---------------------

 - On CompuServe, GEnie, and Microsoft OnLine, this update

   is located in the Microsoft Software Library. You can find

   WFWPTP.EXE in the Software Library by searching on the word WFWPTP.EXE,

   the Q number of this article, or S14540. WFWPTP.EXE is a compressed,

   self-extracting file. After you download WFWPTP.EXE, run it to

   extract the file(s) it contains.

 - This update is also 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 this update, download WFWPTP.EXE.

   WFWPTP.EXE is a compressed, self-extracting file. After you

   download WFWPTP.EXE, run it to extract the file(s) it contains.

 - On the Internet, this update is 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.

Additional reference words: 3.1 3.10 WFWG RAS PTP update


WFWG 3.11 Resource Kit Err Msg: THREED.VBX Is Out of Date

Article ID: Q111296

---------------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups Resource Kit version 3.11

---------------------------------------------------------------------------

SYMPTOMS

========

When you start some of the utilities that come with the Windows for

Workgroups Resource Kit version 3.11, the following error message is

displayed:

   The file THREED.VBX is out of date. This program requires a newer

   version.

CAUSE

=====

This error message is displayed because an older version of THREED.VBX is

on the hard disk drive and still in memory. Some of the utilities in the

Resource Kit use the file THREED.VBX to display 3-dimensional controls.

RESOLUTION

==========

To correct this problem, search the hard disk drive for any THREED.VBX

files that are not 64,544 in size and delete them. The correct THREED.VBX,

which is installed by the Windows for Workgroups Resource Kit, should be

located in the Windows SYSTEM subdirectory. The file date should be the

date that the Windows for Workgroups 3.11 Resource Kit utilities were

installed on the machine.

After you delete any THREED.VBX files that are not 64,544 in size, exit and

reenter Windows for Workgroups.

If there is not a THREED.VBX file with the size 64,544, you should expand

this file from the Resource Kit disk by using the EXPAND.EXE utility. To

expand THREED.VB_ from the Resource Kit disk, type the following from the

Windows directory at an MS-DOS command prompt

   expand <a>:\mail\threed.vb_ <c>:\windows\system\threed.vbx

where <a> is the floppy disk drive containing the Resource Kit disk, <c> is

your hard disk drive, and <windows\system> is your Windows SYSTEM

subdirectory.

Additional reference words: wfwg 311 3d.vbx


WFWG Error Msg: This Postoffice Cannot Be Updated

Article ID: Q111332

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

----------------------------------------------------------------------

SYMPTOMS

========

When you use the Microsoft Extensions for Windows for Workgroups or the

Microsoft Mail Update program, you may receive the following error message:

   This post office cannot be updated. Consult Microsoft Product Support

   Services for more information.

CAUSE

=====

There are two possible causes for this error:

 - You are running the Extend utility on a server post office. Extend can

   be run only on a workgroup post office (WGPO).

   If the post office is not a workgroup post office, you do not need to

   run the Extend utility. The Extend utility is designed for Windows for

   Workgroups workgroup post offices to extend them to the functionality of

   a full Microsoft Mail post office.

 - You are trying to run the Microsoft Mail Update program on a workgroup

   post office without first running the Extend utility.

   If you run the Update program without first running the Extend utility,

   or if you do not have a valid Microsoft Mail post office, you receive

   the above error. If you do not have Windows for Workgroups and have not

   yet created a Microsoft Mail post office, you must run the Install

   program instead of the Update program. If you have any existing

   Microsoft Mail post offices, you should run the Update utility to add

   the features of the new version of Microsoft Mail while retaining the

   definitions of the older post office.

Additional reference words: 3.0 3.00B WFW WFWG Moose MSMail 3.2 postoffice


Errors on Token Ring Network with Banyan Vines 5.52 and WFWG

Article ID: Q111333

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SYMPTOMS

========

Windows for Workgroups adds NDISBAN.COM to your AUTOEXEC.BAT file. If you

have a token ring configuration, this entry causes the following errors to

occur when you start your system:

 - Vines NDIS interface error 1010- NDISBAN.DOC

   -and-

 - Error 5739 the Protocol Manager has reported an incompatible MAC

   driver

CAUSE

=====

Banyan VINES version 5.52 uses NDTOKBAN.COM instead of NDISBAN.COM for NDIS

token ring support. Having both files in your AUTOEXEC.BAT file causes

errors.

RESOLUTION

==========

To work around this problem, remove NDISBAN.COM from your AUTOEXEC.BAT

file.

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 as it becomes available.

Additional reference words: 3.11


Clean Boot for WFWG 3.11 with NetWare Connectivity

Article ID: Q111428

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SUMMARY

=======

A "clean boot" (that is, 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 3.11 and various terminate-and-stay-resident (TSR)

programs and/or 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.

MORE INFORMATION

================

Before Clean Booting

--------------------

Create a bootable floppy disk that contains the MS-DOS system files and any

other files required to make your 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 for Workgroups Setup

---------------------------------------------------------

If you are not using any disk-compression software, disk-partitioning

software, or other third-party drivers necessary to boot the computer, you

can boot your computer from a floppy disk that contains only the MS-DOS

system files (CONFIG.SYS and AUTOEXEC.BAT files are not required).

If you are using 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:

Using ODI Drivers [NetWare 3.x or 4.x Shell]:

   CONFIG.SYS                                AUTOEXEC.BAT

   ------------------------------------------------------

   FILES=45                                  PROMPT $P$G

   BUFFERS=20                                CD\<NetWare dir>

   <Third-party disk-partitioning driver>    LSL

   <Third-party disk-compression driver>     <ODI network card driver>

   <Other required third-party driver>       IPXODI

                                             NETX <or VLM>

                                             CD\

Using IPX.COM (Monolithic) [NetWare 3.x Shell Only]:

   CONFIG.SYS                                 AUTOEXEC.BAT

   -------------------------------------------------------

   FILES=45                                   PROMPT $P$G

   BUFFERS=20                                 IPX

   <Third-party disk-partitioning driver>     NETX

   <Third-party disk-compression driver>

   <Other required third-party driver>

To Clean Boot After Running Windows for Workgroups Setup

--------------------------------------------------------

After Windows for Workgroups 3.11 is installed with Novell NetWare as a

second network, a clean boot should appear as follows:

Using ODI Drivers [NetWare 3.x or 4.x Shell]:

   CONFIG.SYS                                    AUTOEXEC.BAT

   ----------------------------------------------------------

   FILES=45                                    <WFWG 3.11 dir> NET START

   BUFFERS=20                                  PROMPT $P$G

   DEVICE=<WFWG 3.11 dir>\HIMEM.SYS            PATH=C:\WINDOWS;C:\DOS

   <Third-party disk-partitioning driver>      SET TEMP=C:\<valid path>

   <Third-party disk-compression driver>       CD\<NetWare dir>

   <Other required third-party drivers>        LSL

   SHELL=C:\DOS\COMMAND.COM /E:1024 /P         <ODI network card driver>

   LASTDRIVE=P <for NetWare 3.x>               IPXODI

      or                                       <WFWG 3.11 dir>\ODIHLP.EXE

   LASTDRIVE=Z <for NetWare 4.x>               NETX <or VLM>

   STACKS=9,256                                CD\

   DEVICE=<WFWG 3.11 dir>\IFSHLP.SYS

Using IPX.COM (Monolithic) [NetWare 3.x Shell Only]:

   CONFIG.SYS                                     AUTOEXEC.BAT

   -----------------------------------------------------------

   FILES=45                                       <WFWG 3.11 dir> NET START

   BUFFERS=20                                     PROMPT $P$G

   DEVICE=<WFWG 3.11 dir>\HIMEM.SYS               PATH=C:\WINDOWS;C:\DOS

   <Third-party disk-partitioning driver>         SET TEMP=C:\<valid path>

   <Third-party disk-compression driver>          IPX

   <Other required third-party drivers>           NETX

   SHELL=C:\DOS\COMMAND.COM /E:1024 /P

   LASTDRIVE=P

   STACKS=9,256

   DEVICE=<WFWG 3.11 dir>\IFSHLP.SYS

Exceptions

----------

The following are examples of drivers that should NOT be removed; these

drivers are used when you turn on the computer to make the hard disk drive

accessible. Although these are not complete lists, they do 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-Partitioning Drivers:

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, DBLSPACE.SYS

If the purpose of a device driver or program is unknown, do NOT remove it.

Most device drivers and programs display a message describing the purpose

when they are initialized.

A clean boot does NOT include the following:

 - 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 or fax machines

 - Drivers for CD-ROM drives or networks

 - Tape backup spoolers, redirectors, or buffers

 - Data acquisition units

 - Keyboard accelerators or buffers

REFERENCES

==========

You can find more information about clean booting on pages 153-154 of the

"Microsoft Workgroup Add-On for Windows User's Guide" version 3.11 manual

and in chapter 13, pages 9-10 of the "Microsoft Windows for Workgroups

Resource Kit Addendum for Operating System Version 3.11" manual.

For information on clean booting Windows 3.1, query on the following words

in the Microsoft Knowledge Base:

   clean and boot and win31

Additional reference words: 1.0 1.00 3.00 3.10 3.11 LAN Manager LANman

clean-boot novel PRINT.COM RAMDRIVE.SYS JOIN.EXE PRINT.EXE MODE.COM

GRAPHICS.COM SUBST.EXE win31 winnet


Changing to EGA or Hercules Video Support in WFWG 3.11

Article ID: Q111458

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

----------------------------------------------------------------------

SUMMARY

=======

If your system requires EGA or Hercules video support for Windows for

Workgroups version 3.11, you have three options for installing this

support: download the necessary files from the Microsoft Download Service

(MSDL); install Windows 3.1 or Windows for Workgroups 3.1, choose the

correct video support, and then upgrade to Windows for Workgroups 3.11; or,

rename the SETUP.INF file from Windows for Workgroups 3.1 to OEMSETUP.INF

and then select the correct video driver.

MORE INFORMATION

================

Windows for Workgroups 3.11 currently does not include video drivers for

EGA and Hercules monochrome display options. Use one of the options listed

below to provide the video support you need.

Option 1

--------

If you have a modem, you can download the drivers for EGA (EGA311.EXE) and

Hercules monochrome (HERC311.EXE) displays from the MSDL by calling (206)

936-6735. The MSDL supports 1200, 2400, and 14,4000 baud (V.32 and V.42)

with 8 data bits, 1 stop bit, and no parity.

Option 2

--------

Install Windows 3.1 or Windows for Workgroups 3.1, which both have the

video support needed. After you install either operating system with the

video support you require, upgrade your system to Windows for Workgroups

3.11, maintaining the current video driver selected in version 3.1.

Option 3

--------

Before you begin this procedure, create a new directory on your hard disk

drive. (You can also use your TEMP directory.)

1. Copy the SETUP.INF file from Windows for Workgroups 3.1 Disk 1 and

   rename it OEMSETUP.INF in your newly created directory.

2. At the MS-DOS command prompt, run SETUP.EXE from the Windows directory

   (or from Windows for Workgroups 3.11 Disk 1 if this is a new

   installation) and select the Other Display option from the list of video

   drivers. When Setup prompts you for a location, provide the path to the

   directory in which the "new" OEMSETUP.INF file exists. After you select

   the desired driver, Setup prompts you for the appropriate version 3.1

   disks to copy the required files.

3. When Setup is finished copying the files, remove the OEMSETUP.INF file

   from the newly created directory. You must also delete the OEMSETUP.INF

   or OEMx.INF file from the Windows SYSTEM subdirectory that matches the

   "new" OEMSETUP.INF's file size and date in the newly created directory.

   This prevents version 3.11 driver selections from being overwritten with

   similar .INF entries that would incorrectly request version 3.1 disks.

Additional reference words: 3.11 quadvga plasma monochrome mcga olivetti

at&t pvc vip tiga


Err Msg on TI 4000 with DOS 6 BATTERY.PRO & 32-Bit Disk Access

Article ID: Q111463

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

----------------------------------------------------------------------

SYMPTOMS

========

If BATTERY.PRO is being loaded in the CONFIG.SYS file on a Texas

Instruments (TI) model 4000 laptop running TI DOS version 6.0 and 32-bit

disk access is activated, the following error message is displayed when you

try to start Windows for Workgroups:

   This program tried to access your hard disk in a way that is

   incompatible with the 32-bit disk-access feature. (wdctrl)

RESOLUTION

==========

To correct this problem, do one of the following:

 - Turn off 32-bit disk access in Windows Control Panel.

   -or-

 - Edit the CONFIG.SYS file in an ASCII text editor, such as Windows

   Notepad, and either delete or remark out (using the REM command)the line

   that refers to the BATTERY.PRO file.

MORE INFORMATION

================

BATTERY.PRO is the advanced power management (APM) utility for Texas

Instruments laptop computers. It extends battery life when the laptop is

not connected to the docking station.

Additional reference words: 3.11 4000


WFWG: Racal NI6510 Driver Doesn't Work with Etherblaster NIC

Article ID: Q111466

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

--------------------------------------------------------------------

SYMPTOMS

========

If you use the Racal NI6510 network interface card (NIC) driver that ships

with Windows for Workgroup 3.11 and you have the Racal Etherblaster network

card installed in your system, you may receive the following error messages

after you reboot your computer:

   Error 5751: The Network Adapter Could Not Be Found

   -and/or-

   Error 7306: The ILANAT.DOS Driver Failed To Initialize

CAUSE

=====

Although Microsoft does not ship an NDIS 3 driver for this card, the NDIS 2

driver (NI6510.DOS) should work correctly with the Etherblaster. However,

Racal has confirmed that the driver shipped with Windows for Workgroups

3.11 does not work with this NIC.

RESOLUTION

==========

To correct this problem, you must use the NI6510.DOS driver from Racal. If

you have a modem, you can download this driver from the Racal bulletin

board service at (508) 264-4345. The file date is 9/17/93 and the file size

is 11,124 bytes. Racal will have an NDIS 3 driver for this NIC available in

the future.

For more information, call Racal Technical Support at (800) 526-8225.

Additional reference words: 3.10


Error 6101: The String Specified by the Workgroup...

Article ID: Q111467

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

----------------------------------------------------------------------

SUMMARY

=======

When you start Windows for Workgroups 3.11, you receive the following error

message:

   The following error occurred while loading the device VNETSUP:

   Error 6101: The string specified by the WORKGROUP keyword in

   the [Network] section of the SYSTEM.INI file was not found.

CAUSE

=====

This error occurs if the user name, workgroup name, or computer name

specified in the [Network] section of the SYSTEM.INI file is missing or

invalid.

RESOLUTION

==========

To correct this problem, make sure that the Workgroup=, ComputerName=, and

UserName= lines in the [Network] sections of the SYSTEM.INI file are

present and that the names are valid.

Additional reference words: 3.11


WFWG 3.11 and Sun PC-NFS 5.0 Err Msg: Invalid COMMAND.COM

Article ID: Q111472

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

--------------------------------------------------------------------

SYMPTOMS

========

If you have Sun Microsystems PC-NFS 5.0 installed, when you quit Microsoft

Windows for Workgroups 3.11, you may receive the following error message:

   Invalid COMMAND.COM

CAUSE

=====

This error message occurs when the following three conditions exist:

 - Windows for Workgroups 3.11 is running.

 - Sun PC-NFS 5.0 is installed as a secondary network.

 - 32-bit file access is enabled.

RESOLUTION

==========

Sun Microsystems has updated the file NFS-NDIS.SYS to correct this problem.

You can obtain this file directly from Sun Microsystems or from Internet

(ftp.york.ac.uk).

Additional reference words: 3.11 exit wfw wfwg pcnfs vfat command

interpreter


Microsoft Mail Err Msg: Error: Unable to allocate hook...

Article ID: Q111566

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SYMPTOMS

========

When you run Microsoft Mail, you may receive the following error message:

   Error: Unable to allocate hook control block

CAUSE

=====

Microsoft Mail does not understand multiple LANAs; therefore, when a

datagram is received, Mail tries to register the adapter on LANA 0. If

NetBEUI is not on LANA 0 (that is, it is not set as the default protocol),

the above error message is displayed.

WORKAROUND

==========

To work around this problem, set NetBEUI as your default protocol. To

do so, follow these steps:

1. From the Program Manager Main group, run Windows Setup.

2. From the Options menu, choose Change Network Settings.

3. Select the Drivers button.

4. Select Microsoft NetBEUI.

5. Choose the Set as Default Protocol button, and then choose the

   Close button.

6. Choose OK twice, and then choose Restart Windows.

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.

Additional reference words: 3.11 wfw wfwg email


WFWG Setup with HP Ethertwist Cards: No Network Installed

Article ID: Q111567

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SYMPTOMS

========

If you have a Hewlett-Packard (HP) Ethertwist network adapter card

installed when you run Windows for Workgroups (WFWG) 3.11 Setup, Setup

detects that there is "no network installed" on your system.

CAUSE

=====

Windows for Workgroups 3.11 Setup does not have HP Ethertwist network

card detection code.

WORKAROUND

==========

To work around this problem, manually select the HP Ethertwist EISA LAN

Adapter/32 (HP27248 or HP27248A) or HP Ethertwist MCA Adapter (HP27246)

when you run Windows for Workgroups 3.11 Setup.

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 as it becomes available.

Additional reference words: 3.11 wfw interface nic nonet


Video Display Problems with MS-DOS Prompt and Trident Card

Article ID: Q111568

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SYMPTOMS

========

If you use ALT+TAB to switch from, and then back to, an MS-DOS Prompt under

Microsoft Windows for Workgroups, the characters may become garbled. If you

press ALT+ENTER to window the MS-DOS Prompt, the screen is redrawn

correctly.

CAUSE

=====

This problem occurs when you use the Windows for Workgroups 3.11 Super

VGA video driver with a Trident VGA card (with 1 megabyte RAM).

This problem occurs with the following video drivers:

 - Super VGA (800x600, 16 colors)

 - Super VGA (800x600, 256 colors, large fonts)

 - Super VGA (800x600, 256 colors, small fonts)

WORKAROUND

==========

To work around this problem, use the Windows for Workgroups VGA video

display driver or obtain the Super VGA 256-Color Driver (SVGA.EXE) video

drivers from the Windows Drivers Library (WDL).

For a complete listing of the WDL's contents and instructions for obtaining

the WDL, query on "Q82006" (without the quotation marks) in the Microsoft

Knowledge Base.

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 as it becomes available.

Additional reference words: 3.11 messed up repeated deleted truncated


Cannot see Writing with Pen Pointing Device and Super VGA

Article ID: Q111569

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

 - Microsoft Windows for Pen Computing version 1.0

---------------------------------------------------------------------

SYMPTOMS

========

If you use the Super VGA video driver (SVGA256.DRV) included with Microsoft

Windows for Workgroups 3.11 with Microsoft Windows for Pen Computing 1.0,

you cannot see the "ink" as you write with the pen pointing device.

CAUSE

=====

The Windows for Workgroups Super VGA video driver (SVGA256.DRV) does not

support the use of pen pointing devices.

WORKAROUND

==========

To work around this problem use the VGA video driver, or a video driver

supplied by your video card vendor.

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.

Additional reference words: 3.11 penwin ink inking wfw wfwg


System Hangs Using Super VGA driver with Compaq QVision

Article ID: Q111570

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SYMPTOMS

========

If you use any of the Windows for Workgroups Super VGA video drivers with

the Compaq QVision video card, your system will stop responding (hang) when

you attempt to start Windows.

WORKAROUND

==========

To work around this problem, use the VGA video driver or one supplied

from Compaq.

To change your video driver:

1. Change your current directory to the Windows directory. For

   example, type "cd \windows" (without the quotation marks) at the

   MS-DOS command prompt, and then press ENTER.

2. Run Windows Setup by typing "setup" (without the quotation marks)

   at the MS-DOS command prompt, and then press ENTER.

3. Choose a different video driver, and then exit Setup.

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 as it becomes available.

Additional reference words: 3.11 SVGA256.DRV wfw wfwg hang lock freeze


Video Corruption with Diamond Stealth and WFWG VGA Driver

Article ID: Q111571

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SYMPTOMS

========

When you attempt to use the Microsoft Windows for Workgroups version 3.11

standard VGA video driver with a Diamond Stealth VRAM 3.33 video adapter,

you encounter video corruption when you return to Windows from an MS-DOS-

based application or the MS-DOS Prompt.

WORKAROUND

==========

To work around this problem use a video driver supplied by Diamond.

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 as it becomes available.

Additional reference words: 3.11 wfw wfwg garbage


Persistent Connections may not Restore with Basic Redirector

Article ID: Q111572

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

--------------------------------------------------------------------

SYMPTOMS

========

If your user name is greater than 15 characters and you start the basic

redirector, you are not logged on to the network; therefore, your

persistent connections are not restored. Although the basic redirector

displays "The command completed successfully," every subsequent NET command

you use causes the basic redirector to ask you for your user name and

password. This problem occurs because you were not logged on originally.

WORKAROUND

==========

To work around this problem:

 - Use the full redirector.

   -or-

 - Shorten the length of your user name to 15 or fewer characters.

STATUS

======

Microsoft has confirmed this to be a problem in the Windows for Workgroups

version 3.11 basic redirector. We are researching this problem and will

post new information here as it becomes available.

MORE INFORMATION

================

If you load the full redirector (Net Start Full), you can use user names up

to 20 characters. If you use a user name greater than 20 characters, the

following error message is displayed:

   Error 7206: An incorrect user name was specified for the password-list

   file

Windows for Workgroups 3.11 does not allow you to enter more than 20

characters for your user name when logging into the network.

Additional reference words: 3.11 wfw wfwg error message redir username

limitation maximum


Advanced APM, Microsoft Mail, & AT Work Fax can Cause GP Faut

Article ID: Q111573

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SYMPTOMS

========

If you are running Microsoft Mail with Microsoft At Work Fax support when

your Advanced Power Management computer goes into standby mode, you may

receive the following error message:

   PROGMAN caused a General Protection Fault in MOUSE.DRV

CAUSE

=====

The above error message can occur when the computer goes into standby mode

if all of the following conditions are true:

 - Power management is set to Advanced.

 - Hardware power management is set to something other than OFF.

 - Microsoft Mail and Microsoft At Work Fax are running.

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 as it becomes available.

Additional reference words: 3.11 wfw wfwg awfax gpf gp-fault sleep

blank program manager


WFWG May Stop Serving After Several Hours with Intel EE16 ODI

Article ID: Q111574

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

--------------------------------------------------------------------

SYMPTOMS

========

After running Microsoft Windows for Workgroups (WFWG) version 3.11 for

several hours, you can connect to other workstations and other network

features still work, but no one can connect to your workstation.

CAUSE

=====

If you are using the Intel EtherExpress 16 network interface card (NIC)

with the EXP16ODI.COM MAC driver, the server portion of Windows for

Workgroups 3.11 may stop functioning. You can use other network features;

however, your workstation is unable to act as a server until it is

rebooted.

It appears that NWNBLINK.386 resets the NIC and the ODI MAC driver does not

replace the multicast list for the network after the NIC is reset.

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 as it becomes available.

Additional reference words: 3.11 wfw wfwg mbl hangs locks


Security Settings File Error with Shared Windows Installation

Article ID: Q111575

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SYMPTOMS

========

If you used SETUP /N to set up a shared copy of Microsoft Windows for

Workgroups version 3.11 and you have Novell NetWare installed as an

additional network, you may receive one of the following error messages

when you use the NET command:

   Error reading security-settings file.

-or-

   Error 2: The specified file was not found.

   An error occurred accessing the security settings file.

CAUSE

=====

These errors occur when your NetWare search path has the shared Windows

directory before your local Windows directory, or your current directory is

the shared Windows directory.

In both cases, Windows for Workgroups is finding a security settings file

that is not valid for your system.

WORKAROUND

==========

To work around this problem, change your search path so your local Windows

directory is listed before your shared Windows directory, or change your

current directory to something other than the shared Windows directory.

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 as it becomes available.

Additional reference words: 3.11 wfw wfwg networked errmsg err msg

net.exe wfwsys.cfg


WFWG 3.11: How to Obtain Microsoft DLC and Microsoft TCP/IP

Article ID: Q111682

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

 - Microsoft DLC for Windows for Workgroups version 3.11

 - Microsoft TCP/IP for Windows for Workgroups version 3.11

--------------------------------------------------------------------

SUMMARY

=======

Microsoft has updated its TCP/IP and DLC protocols to function with

Microsoft Windows for Workgroups version 3.11. These files can be obtained

from:

 - The Microsoft Download Service (MSDL) in the Microsoft Client

   section

 - CompuServe in the Windows for Workgroups section (go msclient)

 - The Microsoft FTP Server (ftp.microsoft.com) in the /AdvSys/MSClient/WFW

   directory

 - Microsoft Inside Sales

 - Local retailers

The files to download are WFWTCP.EXE for MS-TCP/IP and WFWDLC.EXE for

MS-DLC.

NOTE: The updated protocols are for use with Windows for Workgroups 3.11,

not Windows for Workgroups 3.1.

MORE INFORMATION

================

MS-TCP/IP

---------

The Microsoft TCP/IP for Windows for Workgroups includes the NDIS 2

protocol stack to support connecting computers running Windows for

Workgroups together or computers running Windows for Workgroups to Windows

NT and Windows NT Advanced Server using the TCP/IP protocol. Microsoft

TCP/IP for Windows for Workgroups does not include any TCP/IP utilities;

however, support for the Windows Sockets Interface is provided, which

allows any Windows Sockets-compatible TCP/IP utility (including terminal

emulators and file transfer software) to be used.

NOTE: See the READTCP!.TXT file for initial installation instructions and

the included MSTCPIP.HLP file for detailed installation instructions with

Windows for Workgroups 3.11.

MS-DLC

------

Microsoft Data Link Control (DLC) Protocol for Windows for Workgroups

includes the NDIS 2 protocol stack that allows computers running Windows

for Workgroups to operate in IBM SNA environments and to connect to

mainframes and minicomputers, such as the AS/400. The DLC interface is most

commonly used by 3270 terminal emulators to communicate to IBM mainframes.

Support of these emulators is the main role of the Microsoft DLC protocol.

Products from companies such as DCA, Attachmate, IBM, Microcom, and Wall

Data support the Microsoft DLC protocol.

NOTE: See the READDLC!.TXT file for initial installation instructions and

the included MSDLC.HLP file for detailed installation instructions with

Windows for Workgroups 3.11.

Additional reference words: 3.11 wfw wfwg msdlc mstcpip update download


New Installation of WFWG with IPX.COM Gives Erroneous Dialog

Article ID: Q111683

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SYMPTOMS

========

When you install Windows for Workgroups (WFWG) version 3.11 to a new

directory, and IPX.COM is running, the following message is displayed:

   The files for IPX Support Driver (Monolithic) with NetBIOS

   transport are currently installed on your computer.

   Do you want to replace them with the version you are

   installing now?

   If you want to replace all later files with the version

   you are installing now, press Yes to All.

This message is displayed even though you are installing Windows for

Workgroups to a new directory, and therefore do not have NetWare 3.x

workstation drivers installed that need to be updated.

CAUSE

=====

After Setup copies the NetWare files to your hard disk (including

VIPX.386), the SETUP.INF file instructs Setup to copy them once again. As a

result, Setup detects the files it just copied to your hard disk and

displays the message noted above.

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.

WORKAROUND

==========

To work around this problem, choose Yes to update the files and continue

Setup. Although Setup does not actually update the files, it copies the

same version of VIPX.386 to your hard disk and then continues normally.

Additional reference words: 3.11 wfw wfwg errmsg install installation

misleading dialog box error


Share Fax Modem Dialog Allows Creation of Invalid Directory

Article ID: Q111685

-------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

-------------------------------------------------------------

SYMPTOMS

========

When you are sharing a fax using Microsoft At Work PC Fax, the Share Local

Fax Modem dialog box allows you to type an invalid directory name. When you

choose OK, you receive the following error message:

   The Share directory does not exist

When a valid share directory is entered, At Work PC Fax accepts it, but the

invalid share directory created previously remains on the hard disk. The

directory cannot be deleted by using File Manager or by using the MS-DOS

RMDIR command.

RESOLUTION

==========

You can remove the directory with the MS-DOS 6 DELTREE command. For

example, if the directory was created with spaces between each letter

   C:\F A X

then the following command (executed from the parent directory) removes

the invalid directory:

   DELTREE "F A X"

   NOTE: Use the SPACEBAR to add the spaces and make sure you include the

   quotation marks.

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.

Additional reference words: 3.11 awfax dir shared atwork Create Directory

button pcfax


Incorrect Detection of Artisoft's NodeRunner Network Card

Article ID: Q111686

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

----------------------------------------------------------------------

SYMPTOMS

========

Windows for Workgroups 3.11 automatic detection incorrectly identifies the

Artisoft NodeRunner network adapter card.

CAUSE

=====

The NodeRunner network card works correctly with Microsoft Windows for

Workgroups when it is configured as an NE2000-compatible card. The Artisoft

NodeRunner network adapter card is self-configuring. Sometimes Windows for

Workgroups detection does not properly recognize the card as being NE2000

compatible.

WORKAROUND

==========

If this occurs, manually select the NE2000-compatible network card when you

are setting up the network. This should allow the card to switch to NE2000-

compatibility mode. If problems still exist, manually configure the

NodeRunner as an NE2000-compatible card by changing the jumpers on the card

before you start Windows for Workgroups 3.11 network setup. Consult the

Artisoft documentation to configure the card for NE2000 compatibility.

MORE INFORMATION

================

The Artisoft NodeRunner network card is manufactured by Artisoft, a vendor

independent of Microsoft; we make no warranty, implied or otherwise,

regarding this product's performance or reliability.

Additional reference words: node runer runner wfwg hang nic ne 2000


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 driver (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.

WORKAROUND

==========

To work around 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.

STATUS

======

Microsoft and 3COM are researching this problem together to provide a

solution for our mutual customers. We will post new information here in the

Microsoft Knowledge Base as it becomes available.

Additional reference words: 3.11 wfw wfwg


CD-ROM Always Shows 127 MB Used and Zero Bytes Free

Article ID: Q111757

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows operating system versions 3.0 and 3.1

 - Microsoft Windows for Workgroups versions 3.1 and 3.11

 - Microsoft MS-DOS operating system versions 4.x, 5.0, 6.0, and 6.2

--------------------------------------------------------------------

When you view disk information for a CD-ROM in File Manager, free disk

space is always reported as zero (0) bytes, and total disk space in use is

always reported as approximately 127 megabytes.

Microsoft Mulitmedia CD-ROM Extensions (MSCDEX.EXE) is coded to report a

specific number for both free space and bytes in use. Microsoft has

confirmed this to be a limitation of MSCDEX.EXE (all versions).

Microsoft Windows NT uses a different file system for addressing CD-ROM

drives and does not have this limitation.

Additional reference words: MSDOS DOSSHELL DOS SHELL FILE 131070 134215

130048 winmm mmtitles


WG0988: IBMTOK.386 Corrects Problems with Exiting WFWG

Article ID: Q111796

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SUMMARY

=======

Microsoft has an Application Note, "WG0988: IBMTOK.386 Corrects Problems

with Exiting Windows for Workgroups."

The WG0988 disk included with this Application Note contains a new

IBMTOK.386 driver that corrects the following problems:

 - A stack overflow error message occurs when you exit Windows for

   Workgroups.

 - Your system stops responding (hangs) when you exit Windows for

   Workgroups.

You can obtain this Application Note from the following sources:

 - CompuServe, GEnie, and Microsoft OnLine

 - Microsoft Download Service (MSDL)

 - Microsoft Product Support Services

For complete information, see the "To Obtain This Application Note"

section at the end of this article.

THE TEXT OF WG0988

==================

======================================================================

  Microsoft(R) Product Support Services Application Note (Text File)

           WG0988: IBMTOK.386 CORRECTS PROBLEMS WITH EXITING

                        WINDOWS FOR WORKGROUPS

======================================================================

                                                   Revision Date: 2/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.                                |

| IBM is a registered trademark of International Business Machines   |

| Corporation.                                                       |

----------------------------------------------------------------------

Introduction

------------

When you use the Windows for Workgroups version 3.11 IBMTOK.386

driver, you may experience the following problems:

 - A stack overflow error message occurs when you exit Windows for

   Workgroups.

 - Your system stops responding (hangs) when you exit Windows for

   Workgroups.

The WG0988 disk included with this Application Note contains a new

IBMTOK.386 driver to correct these problems. The new driver allows the

MCA IBM(R) token ring card to correctly disengage from the network

ring when the network interface card (NIC) is set for IRQ 2.

To install the new IBMTOK.386 file

----------------------------------

1. Quit Windows for Workgroups.

2. Make a backup copy of the currently installed IBMTOK.386 file by

   typing the following at the MS-DOS command prompt and then pressing

   ENTER

      ren <drive>:<path>\ibmtok.386 ibmtok.old

   where <drive>:<path> 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\ibmtok.386 ibmtok.old

3. Insert the enclosed WG0988 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 <drive>:\ibmtok.386 <destination>

   where <drive> is the floppy disk drive containing the WG0988 disk

   and <destination> is the drive and directory of your Windows SYSTEM

   subdirectory.

   For example, if the WG0988 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:\ibmtok.386 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

   WG0988 in the Software Library by searching on the word WG0988,

   the Q number of this article, or S14579. WG0988 is a compressed,

   self-extracting file. After you download WG0988, 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 WG0988, download

   WG0988.EXE. WG0988.EXE is a compressed, self-extracting file. After

   you download WG0988.EXE, run it to extract the file(s) it contains.

 - 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 Customer

   Service at (206) 936-8661.

Additional reference words: 3.1 3.10 WFWG appnote


WG0991: Updated NE2000.386 Allows WFWG to Start Correctly

Article ID: Q111797

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SUMMARY

=======

When you use the Windows for Workgroups version 3.11 NE2000.386 driver,

your system may stop responding (hang) when you try to start Windows for

Workgroups. The WG0991 disk included with this Application Note contains an

updated NE2000.386 driver to correct this problem. Microsoft has an

Application Note, "WG0991: Updated NE2000.386 Allows Windows for Workgroups

to Start Correctly," to correct this problem. You can obtain this

Application Note from the following sources:

 - CompuServe, GEnie, and Microsoft OnLine

 - Microsoft Download Service (MSDL)

 - Microsoft Product Support Services

For complete information, see the "To Obtain This Application Note"

section at the end of this article.

THE TEXT OF WG0991

==================

======================================================================

  Microsoft(R) Product Support Services Application Note (Text File)

       WG0991: UPDATED NE2000.386 ALLOWS WINDOWS FOR WORKGROUPS

                           TO START CORRECTLY

======================================================================

                                                   Revision Date: 2/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.                                |

|--------------------------------------------------------------------|

Introduction

------------

When you use the Windows for Workgroups version 3.11 NE2000.386 driver with

a Novell NE/2 network interface card (NIC), your system may stop responding

(hang) when you try to start Windows for Workgroups.

The WG0991 disk included with this Application Note contains an updated

NE2000.386 driver to correct this problem.

To install the updated NE2000.386 file

--------------------------------------

1. Quit Windows for Workgroups.

2. Make a backup copy of the currently installed NE2000.386 file by

   typing the following at the MS-DOS command prompt and then pressing

   ENTER

      ren <drive>:<path>\ne2000.386 ne2000.old

   where <drive>:<path> 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\ne2000.386 ne2000.old

3. Insert the enclosed WG0991 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 <drive>:\ne2000.386 <destination>

   where <drive> is the floppy disk drive containing the WG0991 disk

   and <destination> is the drive and directory of your Windows SYSTEM

   subdirectory.

   For example, if the WG0991 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:\ne2000.386 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

   WG0991 in the Software Library by searching on the word WG0991,

   the Q number of this article, or S14578. WG0991 is a compressed,

   self-extracting file. After you download WG0991, 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 WG0991, download

   WG0991.EXE. WG0991.EXE is a compressed, self-extracting file. After

   you download WG0991.EXE, run it to extract the file(s) it contains.

 - 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 Customer

   Service at (206) 936-8661.

Additional reference words: 3.1 3.10 WFWG appnote


WG0992: Updated Files for Microsoft At Work PC FAX 1.0

Article ID: Q111798

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SUMMARY

=======

Microsoft has an Application Note titled "WG0992: Updated Files for

Microsoft At Work PC Fax Version 1.0" available. The disk included with

this Application Note corrects the following problems:

 - Slow performance when you are using a shared fax device.

 - Extended characters are not rendered on cover pages.

 - The redial level cannot be set from the EFAXPUMP.INI file.

 - Microsoft At Work PC Fax stops responding (hangs) when the

   EFAXPUMP.INI file becomes too large.

 - Timing problems occur when you send a fax in facsimile format from

   an application that does not support running multiple instances

   during printing.

 - Shared CAS modems fail when capability is set to RES_SUPER_SUPER.

You can obtain this Application Note from the following sources:

 - CompuServe, GEnie, and Microsoft OnLine

 - Microsoft Download Service (MSDL)

 - Microsoft Product Support Services

For complete information, see the "To Obtain This Application Note" section

at the end of this article.

THE TEXT OF WG0992

==================

======================================================================

  Microsoft(R) Product Support Services Application Note (Text File)

  WG0992: UPDATED FILES FOR MICROSOFT AT WORK(TM) PC FAX VERSION 1.0

======================================================================

                                                   Revision Date: 2/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 Microsoft At     |

| Work and Windows are trademarks of Microsoft Corporation.           |

|---------------------------------------------------------------------|

Introduction

------------

The WG0992 disk included with this Application Note contains updated files

for Microsoft At Work PC Fax version 1.0. The updated files correct the

following problems:

 - Slow performance when you are using a shared fax device.

   Now when you use a shared fax device, you receive better

   performance because At Work PC Fax polls from the client only when

   pending fax jobs are on the server.

 - Extended characters are not rendered on cover pages.

 - The redial level cannot be set from the EFAXPUMP.INI file.

   You can now set the RedialLevel=<n> entry in the [EfaxPump] section

   of the EFAXPUMP.INI file. If RedialLevel is not set, or is set to 0

   (zero), Microsoft At Work PC Fax redials only when the line is

   busy. If RedialLevel is  set to 1, Microsoft At Work PC Fax redials

   when any dial failure occurs (for example, the line is busy, the

   other party does not answer, or there is no dial tone).

 - Microsoft At Work PC Fax stops responding (hangs) when the

   EFAXPUMP.INI file becomes too large.

   Previously, Microsoft At Work PC Fax would hang when the

   EFAXPUMP.INI file reached approximately 55 kilobytes in size.

   Microsoft At Work PC Fax now displays a warning message when the

   EFAXPUMP.INI file becomes too large.

 - Timing problems occur when you send a fax in facsimile format from

   an application that does not support running multiple instances

   during printing.

   Microsoft At Work PC Fax now recognizes the [PCFaxCompatibility]

   section in the WIN.INI file. This allows Microsoft At Work PC Fax

   to keep track of applications that do not support running multiple

   instances during printing. The format of the [PCFaxCompatibility]

   section is as follows

      [PCFaxCompatibility]

      <AppExeName>=0x0001

   where <AppExeName> is the application's filename (without its

   extension).

 - Shared CAS modems fail when capability is set to RES_SUPER_SUPER.

   Previously, a shared CAS modem would return the unsupported

   capabilities resolution RES_SUPER_SUPER to the client. Shared CAS

   fax modems no longer return capabilities to the fax client since

   these are needed only by the shared fax server.

To install the updated Microsoft At Work PC Fax files

-----------------------------------------------------

1. Quit Windows for Workgroups.

2. Insert the enclosed WG0992 disk in the appropriate floppy disk

   drive.

3. To copy the files to the Windows directory, type the following at

   the MS-DOS command prompt and then press ENTER

      copy <drive>:\*.dll <destination>

   where <drive> is the floppy disk drive containing the WG0992 disk

   and <destination> is your Windows drive and directory.

   For example, if the WG0992 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:\*.dll c:\windows

TO OBTAIN THIS APPLICATION NOTE

===============================

 - On CompuServe, GEnie, and Microsoft OnLine, Application Notes

   are located in the Microsoft Software Library. You can find

   WG0992 in the Software Library by searching on the word WG0992,

   the Q number of this article, or S14577. WG0992 is a compressed,

   self-extracting file. After you download WG0992, 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 WG0992, download

   WG0992.EXE. WG0992.EXE is a compressed, self-extracting file. After

   you download WG0992.EXE, run it to extract the file(s) it contains.

 - 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 Customer

   Service at (206) 936-8661.

Additional reference words: 3.1 3.10 WFWG appnote awfax efax


Using At Work PC Fax with Other Communications Software

Article ID: Q111827

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

--------------------------------------------------------------------

SYMPTOMS

========

After you start Microsoft Mail with Microsoft At Work PC Fax installed, you

may be unable to use other communications programs. By default, At Work PC

Fax is set to Auto Answer. This means that At Work PC Fax takes control of

the serial port so that other communications programs are unable to use it.

WORKAROUND

==========

To work around this problem, use one of the following:

 - Choose the Exit And Sign Out command in Microsoft Mail.

   -or-

 - Turn off At Work PC Fax with one of the following methods:

   Method 1

   --------

   1. In Microsoft Mail, choose Mode from the Fax menu.

   2. Select Off for Answer Mode, then choose OK.

      The Fax icon should now display "Answer Off." This setting is saved;

      the next time you enter Microsoft Mail, At Work PC Fax remains in

      "Off" mode. (The Fax icon displays "Idle.")

   Method 2

   --------

1. Open Control Panel.

2. Choose the Fax icon. Choose Setup, select Off under Answer Mode, and

   choose the OK button.

Additional reference words: 3.11 wfw wfwg efax terminal comm.drv AWFAX


Problems Installing IBM Quietwriter Driver with WFWG 3.11

Article ID: Q111829

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SYMPTOMS

========

If you try to install the IBM Quietwriter printer driver, Setup displays

the following message:

   Insert Microsoft Windows for

   Workgroups 3.11 Disk 6 or a disk

   with the updated QWIII.DRV file in: A:\

When you insert Disk 6 and choose OK, Setup displays the following message:

   Insert the disk with the file in: A:\

If you choose OK, Setup displays the same message and appears to be stuck

in a loop. If you choose Cancel, Setup returns to the Printers dialog box

and the IBM Quietwriter does not appear. However, the QWIII.DRV driver is

copied to the Windows SYSTEM directory. At this point, if you try to load

the IBM Quietwriter printer, Setup repeatedly displays the second message.

CAUSE

=====

The [io.device] section of the CONTROL.INF file contains the driver names

as well as any associated files and driver information for each printer

driver that ships with Windows for Workgroups 3.11. The entry for the IBM

Quietwriter (QWIII.DRV) has two commas after the driver name--all other

drivers have one.

RESOLUTION

==========

To correct this problem, edit the CONTROL.INF file and delete one of the

commas after the QWIII.DRV entry. For example, if the entry currently looks

like this

   L:QWIII.DRV,,"IBM Quietwriter III","DEVICESPECIFIC"

After you remove the comma, the line should appear as follows:

   L:QWIII.DRV,"IBM Quietwriter III","DEVICESPECIFIC"

Save the file and then try installing the printer.

Additional reference words: wfwg 311


Problems Sending Faxes to European Numbers

Article ID: Q111830

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

--------------------------------------------------------------------

SYMPTOMS

========

When you try to send a fax to a European number, Microsoft At Work PC Fax

continues trying to dial the number but never actually send the fax. At

Work PC Fax does not generate an error in this situation.

CAUSE

=====

European phones usually transmit ring signals at the same pitch as a

United States busy signal. Although most modems can distinguish between the

two, some cannot. This prevents the fax from being sent since it detects a

busy signal.

WORKAROUND

==========

To work around this problem, enable the Blind Dialing option in Control

Panel. To do this, choose the Fax icon, choose Setup, and then choose

Dialing. In the Dialing dialog box, select the Blind Dialing option, then

restart Microsoft Mail.

NOTE: A disadvantage to this workaround is that it disables redial for

other numbers.

Additional reference words: 3.11 awfax international country


WFWG Err Msg on Gateway 2000 P5: Microsoft Windows 32-Bit...

Article ID: Q111861

---------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

---------------------------------------------------------------------

SYMPTOMS

========

When you run Windows for Workgroups 3.11 with 32-bit disk access enabled on

Gateway P5-60 with a 540 megabyte IDE drive, you may receive the following

error message:

   Microsoft Windows 32-bit disk driver (WDCTRL) validation failed at

   phase 03,0F.

CAUSE

=====

This situation occurs if your CMOS drive configuration settings are set to

AUTO-CONFIG.

RESOLUTION

==========

To correct this problem, manually set your CMOS drive configuration

parameters.

Additional reference words: 3.11 fastdisk error message err msg


AWFAX Hangs When Faxing a Microsoft Works for Windows Document

Article ID: Q111880

----------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

----------------------------------------------------------------------

SYMPTOMS

========

When you try to send a Microsoft Works for Windows version 3.0 document

using Microsoft At Work PC Fax while Works for Windows is running, the

machine stops responding (hangs).

CAUSE

=====

This problem occurs because Microsoft At Work PC Fax calls a ShellExecute

routine for the Microsoft Works for Windows document while Works for

Windows is still running. ShellExecute launches a new instance of Works for

Windows and returns this instance to Microsoft At Work PC Fax. The new

instance of Works for Windows discovers the previous instance and

terminates after requesting that the previous instance prints on its

behalf. Microsoft At Work PC Fax waits for the instance generated by

ShellExecute to begin printing; therefore, the machine hangs.

WORKAROUND

==========

To work around this problem, do one of the following:

 - If you want to send the document in facsimile format, use the print

   method (that is, choose Print from the File menu in Works for Windows

   and select the Microsoft At Work PC Fax printer driver).

   -or-

 - If you are attaching a Works for Windows document to a Microsoft Mail

   message, make sure that Works for Windows is not already running.

Additional reference words: 3.11 efax awfax wfw wfwg msworks


RAS Err Msg: Error 642: One of Your NetBIOS Names Is...

Article ID: Q111881

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

--------------------------------------------------------------------

SYMPTOMS

========

When you run the Remote Access Services (RAS) client that ships with

Microsoft Windows for Workgroups version 3.11, you may receive the

following error message during RAS authentication

   Error 642: One of your NetBIOS names is already registered on the

   remote network. Name: <xxxxxx>

where <xxxxxx> identifies the duplicate NetBIOS name.

CAUSE

=====

The above error message may occur if:

 - MaintainServerList is set to "Yes" or "Auto" in the [Network] section of

   the SYSTEM.INI file.

   NOTE: The default for this setting is "Auto."

   -or-

 - The workstation is connected to the network when you attempt to logon

   through RAS.

RESOLUTION

==========

To correct this problem:

 - Set the MaintainServerList value to "No" (without the quotation marks).

   -or-

 - Disconnect the workstation from the network.

Additional reference words: 3.11 w_nt lanman wfw wfwg ras error

message login nt


WFWG 3.11: TI MicroLaser May Cause Computer to Hang

Article ID: Q111882

--------------------------------------------------------------------

The information in this article applies to:

 - Microsoft Windows for Workgroups version 3.11

--------------------------------------------------------------------

SYMPTOMS

========

When you print the final pages of a print job to a Texas Instruments (TI)

MicroLaser PS35, the local computer hangs for approximately 15 seconds.

Control of the machine returns after the print job is completed.

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.

Additional reference words: 3.11 wfw wfwg hang lock freeze texas

instruments