Document ID: 15006
Contents
Introduction
Prerequisites
Requirements
Components Used
Symptom
Reason
Solution
Symptom
Reason
NetPro Discussion Forums - Featured Conversations
Related Information
Introduction
When you run LAN²PC with Microsoft Windows 3.1 in 386 enhanced mode, the conditions in this document apply:
Prerequisites
Requirements
There are no specific requirements for this document.
Components Used
This document is not restricted to specific software and hardware versions.
Symptom
IPX and NETX come up fine, but when you start Windows, your system immediately exits to the DOS prompt.
Reason
Windows tries to use the portion of memory that LAN²PC uses. Windows does not allow LAN²PC to use high memory (640-1024K).
Solution
Prevent Windows from scanning or using the portion of memory that LAN²PC uses. Use any ASCII text editor and open the SYSTEM.INI file. Then complete these steps:
-
Find the [386enh] section of the file.
-
Add the EMMExclude setting to specify a range of memory addresses. For example, to tell Windows not to scan the addresses between D000-DFFF, you would insert this line:
EMMExclude=D000-DFFF
-
Save your changes, exit, and restart Windows.
Symptom
IPX and NETX come up fine, but when you start Windows or Windows applications, LAN²PC hangs, or the line goes out of service.
Reason
You must use the IPX.OBJ file provided by Windows in order to run any Novell network interface. For details, refer to the Windows network read-me file, NETWORKS.WRI.
NetPro Discussion Forums - Featured Conversations
| NetPro Discussion Forums - Featured Conversations for LAN |
| Network Infrastructure: LAN Routing and Switching |
| Network Infrastructure: Getting Started with LANs |
Related Information
| Updated: Oct 06, 2005 | Document ID: 15006 |
