Warning: Persons carrying out the instructions in this document should be familiar with the operation of the Windows 98 Control Panel and other functions. Utilizing this information in an incorrect manner may adversely affect the operation of the Windows 98 operating system and your Xircom® CreditCard Ethernet 10/100+Modem 56 Adapter. If you are unfamiliar or uncomfortable with these instructions seek the assistance of your network administrator or someone familiar with Windows 98.
- It is recommended that you verify with the computer's manufacturer that your computer is compatible with
Windows* 98 and that the latest available BIOS version and any required driver updates have been installed. Consult the
documentation included with your computer for the appropriate points of contact.
- Verify that your hardware devices are Windows* 98 compatible by reviewing the HARDWARE.TXT file included with Windows 98 or by consulting the Windows 98 Hardware Compatibility List (HCL) maintained by Microsoft.
Note: If you have previously attempted to install the REM56 adapters without success, it is recommended that you proceed to Section 2 (Xircom® Adapter Removal) first. The instructions in this section will assist with the complete removal of previous installation attempts leaving the computer in a state of readiness conducive to the successful installation of the REM56 adapter. When finished proceed to Section 1 to begin the installation.
This section will assist with the installation of the REM56. It is divided into two subsections:
Follow the instructions in this section in the order they are given. These instructions are designed to ensure that the steps
necessary for a successful installation are fully completed with minimal effort.
- Pre-installation Instructions
- Adapter Installation Instructions
Preinstallation Instructions The following steps should be performed prior to inserting the REM56 adapter into the computer's PC Card slot.
- Check for Real Mode Memory Managers
- Open the System Editor (Start, Run, type SYSEDIT, and click OK).
- Select the CONFIG.SYS file either by clicking on the CONFIG.SYS title bar or by selecting Window (on Toolbar) and then selecting CONFIG.SYS from the displayed list.
- Select Search from the Toolbar
- click Find and type EMM386 in the dialog box
- click Find Now. If found, change the EMM386 line to read as follows:
- DEVICE=C:\WINDOWS\EMM386.EXE NOEMS
- Select the SYSTEM.INIfile either by clicking on the SYSTEM.INI Title Bar or by selecting Window from the Toolbar and selecting SYSTEM.INI from the displayed
- Select Search from the Toolbar, click Find and type EMMEXECLUDE in the dialog box and click Find Now. If found modify the line to read as follows:
- On computers employing Cardbus controllers this line should read: EMMEXCLUDE=C000-CBFF (See Cardbus note in Section 4 Additional Notes)
- Only one EMMEXCLUDE statement should be present. If there are additional statements of this type they should be commented (placing a semi colon at the beginning of the line) or deleted. If the EMMEXCLUDE line is not present then add the above line to the (386Enh) section as follows:
- SYSTEM.INI: (386Enh) EMMEXCLUDE=C000-CFFF (use C000-CBFF on Cardbus computers)
- Save all files and exit the System Editor.
- Remove SystemSoft .INF file references
- Open Windows Explorer (Start, Programs, Windows Explorer)
- Ensure that the Show all files option is selected:
- Select View from the Toolbar
- Select Folder Options
- Click the View tab
- Choose Show all files under the Hidden Files folder
- Click Apply
- Click OK
- Search for SXIR*.INF
- Select Tools from the Toolbar
- Click Find, Choose Files or Folders in the named dialog box type SXIR*.INF
- In the Look in dialog box type C:\WINDOWS\INF Select the Include subfolders box and click Find, Delete this file if present.
- In the C:\WINDOWS\INF directory rename MDMGEN.INF to MDMGEN.ORI.
- Close Windows Explorer
- Reboot your computer.
- You are now ready to install the Xircom multifunction adapter.
All necessary Xircom files are located on the Xircom Installation disk (Disk 1). The Windows 98 source files, which are required during the installation, are typically located on the local hard drive in the WINDOWS\OPTIONS\CABS directory. These files can also be found in the WIN98 directory on the Windows 98 product CDROM.
- Start the computer WITHOUT the REM56 adapter inserted
- Allow Windows 98 to boot fully
- Insert the REM56 adapter into an available PCMCIA slot.
- Windows 98 should automatically detect the presence of the adapter and indicate that it has found new hardware, followed by a dialog box indicating that it is building a driver information database.
- The "Add New Hardware" window appears, click Next.
- Accept the default selection "Search for best driver for your device" and click Next .
- Accept the default search location and click Next.
- The Hardware wizard will search the floppy disk and find "Xircom CreditCard 10/100+Modem 56 (Multifunction Parent Device) also listing the file being used: -- A:\MFREM56.INF.
- Click Next.
- After a moment the Windows 98 Hardware wizard displays Unknown Device and begins the installation process for the modem portion of the adapter followed by the detection of another Unknown device, the network portion of the adapter.
- Again accept the defaults Search for best driver... and CD-ROM drive selections (if asked) by clicking Next. Click Finish and then Yes to restart the computer.
- When the computer boots the Xircom Country Select software will launch and scan the available COM ports for a Xircom modem. If the REM56 modem is detected the Country Select window appears displaying the default country "United States". Click exit if this selection is appropriate. If a different country selection is desired select the desired country, click Save and then Exit .
- The Registration program activates as soon as the CountrySelect software closes, click Cancel. This information can be completed at anytime by executing REG3.EXE from the XIRCOM\XAPPS directory.
When the installation process has completed go to the Windows 98 Device Manager (Control Panel, System icon, Device Manager tab). The Xircom CreditCard Ethernet 10/100+Modem 56 adapter entries should be listed as follows:
- Modem: Modem of Xircom CreditCard 100+56
- Multifunction Adapters: Xircom CreditCard 10/100+Modem 56K (Multifunction Parent Device)
- Network adapters: Network of Xircom CreditCard 10/100+Modem 56
Note: In some instances Windows 98 may locate the Multifunction Parent Device as a second entry in the Modem group, instead of placing it in the Multifunction adapters group, as follows:
- Modem: Modem of Xircom CreditCard 100+56 Xircom CreditCard 10/100+Modem 56K (Multifunction Parent Device)
- Network adapters: Network of Xircom CreditCard 10/100+Modem 56K Adapter
In these cases there may be no Multifunction adapters group listed. This is acceptable and will not affect the functionality of the adapter. The Multifunction Parent Device will behave exactly the same way regardless of the location of its entry in the Device Manager.
Note: If any of these entries are preceded by a yellow exclamation point (!) or red "X" then an error condition exists. In the event that this occurs, try reinstalling the REM56.
This section will
assist with troubleshooting the most common issues that prevent the
Xircom RealPort Ethernet Adapter 10/100+Modem 56 Adapter (REM56)
from installing and functioning correctly. The section is split into
- Troubleshooting the REM56 Network Installation
- Troubleshooting the REM56 Modem Installation
- A Problem, Cause, Resolution format is used in the following descriptions.
Troubleshooting the Network Installation
This subsection includes the steps necessary to troubleshoot the initial adapter installation, as well as determine and modify adapter resources to create a working configuration. Also addressed in this section are the steps necessary to ensure that all network clients and protocols are properly configured.
A hardware problem exists with the
PCMCIA slots or the REM56 adapter. If the previous conditions
have been eliminated as the cause of this issue, it is possible
that a hardware failure exists with the computer sockets or the
REM56 adapter itself. The best way to verify whether the
hardware is at fault is to try installing the adapter in another
computer or try installing a different adapter in this computer.
This will help to pinpoint the faulty device or eliminate a
hardware failure as a possible cause of this
- Problem 1 - When the adapter is inserted into the PCMCIA socket there is no two-tone beep, nor does Windows 98 detect the presence of the REM56 adapter.
- Possible Cause - Corrupted PCMCIA or Cardbus controller configurations.
- Possible Resolution - Occasionally Windows 98 will not detect the REM56 adapter upon insertion and the plug-and-play installation process will not start. This could be caused by one or more of the following items:
- There is a plug-and-play option in the
BIOS that needs to be enabled. Some computers include a
plug-and-play option in the system BIOS that must be enabled for
Windows 98 plug-and-play functionality to operate correctly.
Refer to your computer documentation to see whether your
computer includes such a feature and how to set it correctly.
- The Windows 98 Registry contains
remnants generated by a previously attempted installation and
does not identify the adapter as new hardware.
If a previous attempt at installing the
adapter has failed, or the hardware configuration is corrupted
in some manner, there will be residual entries in both the
Windows 98 Registry and WINDOWS\INF directory. These
remnants affect the installation by informing the operating
system that an adapter of this type is already configured, even
though the configuration is not complete. In such cases the
adapter will not be recognized as new hardware upon insertion.
If this is suspected proceed to REM56 Adapter
Removal Procedures. The instructions in this
section will assist with the complete removal of the REM56
adapter from Windows 98. After completing these steps return to
REM56 Adapter Installation.
- The PCMCIA controller hardware is not fully configured or enabled. Laptop computers are generally shipped with the PCMCIA slots fully configured and enabled. However, in some instances this may not be the case - for example, the Windows 98 Operating System may have been re-installed. If you have checked the BIOS setup and performed the REM56 removal procedure and the adapter is still not being detected, then there is a possibility that the PCMCIA hardware is not completely configured or enabled. To enable the PCMCIA hardware try the following:
- In the Control Panel, double
click the PC Card icon. If this starts the
PCMCIA Installation Wizard it is an indication that PCMCIA
services were not yet configured in Windows 98. Follow the
Windows 98 prompts to allow the Wizard to configure these
services. Accept the default answer No to
each question and Yes to restart the
- If the PC Card Properties
Window is present but the slots are indicated as empty
(even if the adapter is inserted), you may need to re-install
the controller. To do this:
- Go to the Device Manager
- Double click the PCMCIA Socket icon
- Select the PCMCIA controller
listed and click Remove (Important
Note - DO NOT perform this procedure on computers with Cardbus
controllers! For more information on Cardbus controllers refer
to Additional Notes ). Also remove PC Card Services.
- Open a DOS box and
change to the WINDOWS\INF directory. Delete the files
DRVDATA.BIN and DRVIDX.BIN. Type
EXIT to close the DOS box and return to the Windows 98 Desktop.
- After removing the PCMCIA controller perform a complete shutdown of the computer.
- Restart the computer. Windows 98
should detect the PCMCIA controllers as new hardware and
re-install the necessary software to support the controllers.
In some machines this action automatically starts and runs the
PCMCIA Wizard. To verify that this action has occurred open
the PC Card Properties window (Control
Panel, double click the PC Card (PCMCIA)
- If the PC Card Wizard has run, the
PC Card Properties window displays Empty - Socket 1;
Empty - Socket 2; and so forth. If the PCMCIA Wizard appears
accept the default answer No to the two
questions, click Finish to close the wizard and Yes to restart the computer.
- Once Windows 98 has restarted the PC
Card Properties window should display the "Empty - Socket
- Problem 2 -
After installing the REM56 adapter there is a yellow exclamation
point or red "X" over either the Multifunction parent device
entry or the Network adapter device entry; or the
Device Manager entries appear correct but the adapter
fails to initialize and connect to the network.
- Possible Causes - These type of difficulties are usually related to one of the following items, or combination of items:
- Resource allocation issues
- Canceled, incomplete
or corrupted installation
- Possible Resolution
In the following resolution instructions reference will be made to
the REM56 Multifunction Parent Device entry which is normally
located in the Device Manager under Multifunction adapters. In
Windows 98 the Multifunction Parent Device may be listed as a
second entry under Modem instead of being listed under
Multifunction adapters, and in such cases there may be no
Multifunction adapters group listed. All functions and
instructions regarding resource modification remain the same
regardless of the location of the Multifunction Parent Device.
Refer to the entry in the Modem group when reference is made to
the Multifunction Parent Device under Multifunction adapters if
your system exhibits this condition.
- Resource allocation issues
In many cases of this nature, the Windows 98
plug-and-play process has failed to properly detect available
resources and has assigned resources to the REM56 adapter that are
not actually available. This is commonly reflected by the yellow
exclamation point over the network adapter entry. Conflicting
memory resources are usually responsible for this condition. A red
"X" over either of these device entries is indicative of NO
RESOURCES being assigned and is more likely to appear over the
REM56 Multifunction Parent device entry than either of the two
REM56 child device entries.
The appearance of a red "X" at the beginning of any entry in the
Device Manager can be the result of that device being
manually disabled. This can be verified by selecting the device
entry in this state and clicking the Properties button.
The General tab is displayed by default. At the bottom of
this window the Device Usage window is shown with two
options one (should be checked) that indicates "Exists in all
hardware profiles" and the other selection "Disable in
this hardware profile". An active configuration is one that
appears with a check mark to the left of "Exists in all
hardware profiles." If a check mark is not present or a check
mark exists next to the Disable in this hardware profile selection
then the device is not active. This results in the red "X" being
displayed over the device entry in the Device Manager .
to the Xircom adapter are listed on the "Resources" tab
of the REM56 Multifunction Parent Device properties
window. The REM56 parent device entry is found listed in the
under Multifunction adapters. This is the only place that REM56 resource settings can be modified. In a standard installation (even one that may exhibit an error condition) the resource values for the REM56 adapter appear in the following format:
- Input/Output Range 02E8-02EF
- Input/Output Range 0120-013F
- Interrupt Request 10
- Memory Range 000D2000-000D3FFF
- Memory Range 000D4000-000D4FFF
In order to modify any of these
values you must first disable the "Use automatic settings"
option box, which appears above the Resource
settings window. If the box contains a check mark, click it once to disable this feature. This allows the user to modify most of the resource values.
Values that can be modified are based on the Basic Configuration
in use. A more detailed explanation of how the selected Basic
Configuration affects the resource values that can be modified is
contained in Additional Notes.
To change a resource value select the
resource name and click the "Change
settings..." button. This should enable the Edit
(resource) window with the current resource value displayed in the
Value box. To modify the value use the up or down scroll
arrows. Typing the value in the box will not work in most cases.
When the resource is changed to the desired value, verify that the
Conflicting device list indicates no conflicts (or in some cases
words to the effect that It is unknown if any devices conflict),
Canceled, incomplete, or corrupted installation - Canceling the
installation after the adapter has been recognized may produce any
of the above error conditions. If this is the case or if you have
attempted multiple installations without success, proceed to
REM56 Adapter Removal Procedures. Once
the system is properly cleaned refer to REM56 Adapter
Installation for assistance with installing your
adapter. Should these steps fail to produce a working
configuration you will need to contact Technical Support for
Situation 1 - An exclamation point appears over the REM56 device entry
under the Network adapter listing in the Device Manager.
This situation is usually the result of a memory conflict. In most
cases the REM56 memory is set to a memory segment in use by
another device. Using the information above, modify the first and
second memory segments until each reports that it does not
conflict with another device. (Note: this symptom is not necessarily the result of a memory conflict - it can be caused by an interrupt conflict as well.)
Situation 2 - An exclamation point or
red "X" appears over the REM56 entry under Multifunction adapter
in the Device Manager . This situation is more likely to appear if the installation was corrupted. The exclamation point is indicative of a complete installation, but that an error condition exist where one or more resources assigned to the adapter are invalid. On reviewing the adapter resources, it is likely that these resources will appear to be located in the System board range (i.e., lower conventional memory) or set to all 0 (zero). This issue can be resolved by modifying the adapter resources to the ranges identified above.
Once all desired changes have been made,
click the OK button located on the
Resources tab. You should observe a warning
indicating that you have made changes manually and asking if you
want to continue. Click Yes
. Windows 98 will take a few seconds to convert to the new settings. It may necessary to re-boot the computer after performing this action. If the installation was incomplete, as in the case of a red "X" over the REM56 multifunction parent device entry, the installation will continue by installing the two REM56 child devices (modem and network portion of the adapter).
A red "X" is a critical error and is seen
most often when the installation fails early in the process or is
canceled. The REM56 multifunction parent device entry appears in
the Device Manager, but when you attempt to view the
adapter resources a message is displayed to the effect that
"No Resources have been assigned to this device... would you
like to assign them now". If this is the case, the
installation is probably corrupted to the point where resource
modification cannot be performed properly. This is most likely due
to the fact that the needed resources simply are not available
because they are in use by other hardware in the system. Refer to
Additional Notes for more information on
disabling conflicting hardware, and then follow the instructions
in REM56 Adapter Removal Procedures to
remove the failed installation. Then return
to install the adapter
Troubleshooting the Modem Installation - This subsection includes the steps necessary to troubleshoot problems specific to the modem portion of the REM56 adapter.
- Problem 3 -
The adapter appears to initialize properly and there are no
indications in the Device Manager of problems, but
network resources cannot be accessed.
- Possible Cause -
issues of this nature may involve:
- Missing or incorrectly configured network client
- Missing or incorrectly configured network protocols
- REM56 adapter feature
- Possible Resolution - in order
for a Windows 98 computer to make a successful network connection,
three basic components are necessary:
- A network client
- A network adapter
- A suitable protocol
A few simple checks
can often clear up difficulties. The following steps assume that
the REM56 adapter has already been successfully installed and
initializes properly. To view the installed network components
open the Control Panel and double click the
icon. On a correctly configured system a list of items similar to the following should be displayed:
- Client for Microsoft* Networks*
- Network of Xircom 16-bit 10/100 + 56
- By default Windows 98 installs the Client for Microsoft Networks and the TCPIP protocol. The default configuration does not allow the versatility of connecting the computer to a Microsoft or NetWare* client server network, a Microsoft peer-to-peer network unless these services are running the TCPIP protocol and a DHCP server is available to provide IP addresses. To connect to these environments it is necessary to add the NetBEUI or IPX/SPX protocols.
Note: Dial-Up Networking is not addressed here, but is
discussed in more detail under Troubleshooting the
Modem Installation later in this section.
- Missing or incorrectly configured network client - A common problem is
the lack of a network client. This is very important when dealing
with a Novell network. While Windows 98 provides native Novell
support it does not install this support by default. If the first
item listed at the top of the installed network components window
is the Xircom network adapter or the Dial-up adapter then you will
need to add a network client. The following instructions are based
on installing one or both of the default Microsoft network
clients. Other network clients are available and these
instructions apply to their installation as well.
To add a network client:
- Click Add
- Select Client and click
- Select Microsoft from
the Manufacturer window. This allows for the selection of either Client for Microsoft Networks or Client for NetWare Networks.
- If connecting to a Microsoft network
(Windows NT server) or a peer-to-peer network select the
Client for Microsoft Networks. If connecting to
a Novell* NetWare* network select the Client for NetWare
Networks. Click OK after selecting the appropriate client.
- Windows 98 will build a Driver
Information Library. When finished you will return to the
Network Configuration window. Verify that IPX/SPX compatible protocol is installed if the Client for NetWare Networks was selected. If the Client Microsoft Networks was selected then only the TCPIP protocol is installed, NetBEUI must be added if needed.
- Select the Identification
tab. Ensure that the Computer Name field and
Workgroup field are filled in. The computer name must be unique to your network. If connecting to an Windows NT domain enter the Domain name in the Workgroup field. In a peer-to-peer network use Workgroup or the name assigned to the workgroup. Syntax is important - the name in the Workgroup field must match exactly the workgroup name. This field is case sensitive.
- Select the Configuration
tab. Under the installed components window is the
Primary Network Logon window, ensure that the network
client appears in this window then click OK.
Choose Yes to restart the computer.
Note: Peer-to-Peer Networks using
the Microsoft Client for Networks may also require that
Microsoft File and Print Services be added. To do this select
Add, choose Service, click Add, select Microsoft then select
File and Print Services for Microsoft Networks. Click OK and OK
again to accept this service and reboot the computer.
- Missing or incorrectly configured protocols - Certain client and protocol
types are normally associated with each other. A matrix reflective
of the most common associations is contained in
Additional Notes .
Installation of a specific client will normally install the default protocol for that client (IPX/SPX for the NetWare Client and TCPIP for the Microsoft Client. You will need to verify that this is in fact the protocol that is being used on your network and in the case of TCPIP that it is configured correctly. If you are unsure about the protocol type and configuration for your network check with the appropriate network administration personnel at your site. If you find that you need to configure a different protocol you can do so in the network components window in a manner similar to the client configuration as follows:
- Click Add
- Select Protocol and click
- Select Microsoft from
the Manufacturers window. Select the desired protocol
and then click OK. This installs the protocol and then returns to the installed network components window. Verify that the selected protocol is displayed in this window.
- Click OK on the main
network window. Windows 98 will prompt you to restart the
computer. Choose Yes.
Note: The TCP/IP protocol may require configuration before it
will work with your network. By default this protocol installs
with the option "Obtain IP Address from DHCP Server " selected. This will be fine as long as your network is configured to dynamically assign IP addresses to each computer as it logs on to the network. However, if your network relies on static IP addresses (each computer is assigned a fixed IP address) then you will need to configure IP address parameters (the IP address, subnet mask, DNS entries, and other parameters) before your computer will be able to access the network. Consult your network administrator or your Microsoft documentation for assistance with configuration of TCP/IP settings.
If connecting to a Novell network and the IPX/SPX protocol is already installed but you are still unable to access the network, it may be necessary to force the Default Frame Type setting to the default frame type of your Novell network. To do this:
- Select the IPX/SPX compatible
Protocol from the installed network components window and
click Properties .
- Select the Advanced tab.
Select the Frame Type feature in the
Property window. By default this property is set to AUTO. The property options are that we are concerned with are Ethernet 802.2 and Ethernet 802.3 (your network administrator can assist with the correct selection).
- Once correct frame type is selected
click OK , you are returned to the network components page.
- Click OK and then
Yes to restart your computer.
Note: You should get a Network Logon box when booting the
computer. Unless you properly log on to the network you will not
be able to access or browse the network.
- REM56 adapter feature settings - When troubleshooting the network
installation it is prudent to reduce the processing required to
initiate a network connection. To access adapter feature settings
select the Network of Xircom ... entry in the installed
network components window and click Properties.
Choose the Advanced
tab and modify only the following features (the other features should be left in their default state):
- Early Transmit Off
- Full Duplex Off (this is the default setting, but verify that this setting is Off)
- LineSpeed (Set this feature to either 10Mb or 100Mb depending on the speed of your network.)
- Mode (Set to I/O initially; change to
Memory should the other settings not result in a successful
Try disabling or modifying the error correction protocol or data compression protocols used. The following commands apply:
- Problem 1 -
The adapter is detected and installed as a XIRCOM_MODEM... and is
listed as such under the Modem group in the Device Manager. No
REM56 entries are displayed under the Multifunction adapters and
Network adapters groups.
- Possible Cause - This condition is usually caused by the presence of
additional .INF file on the system that identifies the adapter as
a Modem only during the installation process.
- Possible Resolution - Proceed to REM56 Adapter Removal
Procedures and follow the instructions. Then return
to Section 1 and follow the instructions to install the adapter.
When doing so, be sure to delete all specified files under Step 2
of the Pre-installation instructions.
- Problem 2 -
The modem fails to respond when a communications application is
- Possible Cause - A problem exists with the modem installation such
that the modem is not responding to the operating system, or the
application being used requires that the COM port chosen must be
associated with specific resource settings.
- Possible Resolution
- To verify that the modem is responding
properly to the operating system, go to Control Panel,
Modem. Verify that the "Modem of Xircom..."
entry is present. Click Diagnostic, select
the COM port entry associated with the "Modem of Xircom..."
and choose More Info ... A message should be displayed indicating that the computer is communicating with the modem. After a few seconds a window should appear that displays response values similar to the following:
- Port Information
- Port: COM4
- Interrupt: 10
- Address: 2E8
- UART: NS 16550AN
- Highest Speed: 115K Baud
- Modem of Xircom 16-bit 100+56
- ATI1 OK
- ATI3 Xircom CreditCard GSM Ethernet 10/100 ...
- ATI4 17
- ATI5 OK
- ATI6 OK
- ATI7 OK
- AT+FCLASS=? 0,1
- If these values do not appear at all, or
a message such as "Unable to open port" is displayed, the
adapter may need to be re-installed. Proceed to
REM56 Adapter Removal Procedures and
follow the instructions. Then return to Section 1 and follow the
instructions to install the adapter.
- Some older applications may require standard DOS pairings between the COM port specified and the resource parameters assigned. In most cases these will be the following:
- COM port Port Address Interrupt
- COM1 3F8 04
- COM2 2F8 03
- COM3 3E8 04
- COM4 2E8 03
- In most installations the
port address will match the standard value, but Windows 98 will
often assign a different interrupt. If your application requires
these standard settings, use of COM2 or COM4 and interrupt 03 is
recommended (on most computers interrupt 04 is already in use).
Detailed instructions for changing the assigned resource
parameters can be found under Note 3 in Additional
Notes. You may also find that you will need to
disable an internal communications device to free interrupt 03
so that it is available for use. See Note 2 in
Warning: After performing an
upgrade of a Windows* 95 installation to Windows 98, some users
may find that a modem that was previously installed on COM4 has
been moved to COM5. This occurs due to configuration changes
made by Windows 98 that makes COM4 unavailable for the modem.
Some applications (notably AOL) presently are not capable of
using a modem installed on a port higher than COM4. In such
cases it will be necessary to reconfigure the modem so that it
uses either COM1, COM2, or COM3. COM3 is recommended in the vast
majority of cases. See note 3 in the Additional
Notes section for details about modifying the
adapter resources to utilize a different port.
- The adapter installation process
attempts by default to locate the modem on COM4. On some
computers this does not succeed and the modem is placed on COM5.
In this condition, some applications may not be able to access
the modem. If this your situation, refer to Note 3,
"Modifying Adapter Resources" in Additional
Notes, and follow the instructions here regarding
the Basic Configuration setting to move the COM port to COM1,
COM2, or COM3. If all three of these ports are already in use,
you may also need to consult Note 2 as discussed previously.
- Problem 3 -
Connection establishment or data transfer problems are encountered
when using Microsoft Dial-Up Networking.
- Possible Cause - A modem connection is not established, or the
connection is established but login authentication problems are
- Possible Resolution - Xircom recommends that you verify that you have the latest version of firmware installed on your adapter before investigating other possible causes for connection problems. The latest version of firmware can be obtained from the Xircom forums list at the beginning of this document. Contact information for these sites is included at both the beginning and the end of this document.
When the modem initially establishes a connection, it attempts to negotiate the best connection possible with the answering modem. The specifics of this will vary depending on the type of answering modem and the telephone line conditions that prevail at this location. If difficulties in establishing a connection are encountered, the following suggestions can be tried:
Note: A number of the suggestions
here involve one or more modem command string parameters. These
can be specified via the "AT" command in a terminal
emulation application (such as the Windows 98 HyperTerminal
program) or the Xircom Modem Test that is placed in the Xircom
Program Group during the adapter installation, or they can be
invoked globally by configuring them in the "Extra
Settings" field in the modem properties window
(Control Panel, Modem, select the REM56
entry and click Properties, Connection tab,
Advanced, Extra Settings). Note that the "AT" prefix
should NOT be included if they are specified in the "Extra
Settings " field. A complete listing of available modem command string parameters and their functional descriptions is included in the online help documentation supplied with your REM56 adapter.
- If a connection cannot be established at all:
- Try connecting at a lower speed. The following commands apply:
- +MS=V34 Attempts to make a v.34 connection
- +MS=V32B Attempts to make a v.32bis connection
- +MS=V32 Attempts to make a v.32 connection
- S37=19 Attempts to connect at 33600 Kbps
- S37=17 Attempts to connect at 28000 Kbps
- S37=13 Attempts to connect at 19200 Kbps
- S37=11 Attempts to connect at 14400
Kbps (Other S37 values are listed in the online documentation)
Other miscellaneous command string parameters that may help:
- N0 Normal mode - no error correction or compression
- N5 MNP 2-4 error correction
- %C0 MNP 5 data compression
If the modem normally connects but
appears to be unable to negotiate a 56K connection, other
factors may be involved. Refer to "PCM (56 Kbps)
Connections" in Additional Notes
for more detailed information.
If connections are successfully established but difficulties in login authentication are encountered, the following can be checked:
- ATI3 Displays the current firmware revision of the REM56
- ATI11 Displays the call statistics for the last call made
- %E0 Disables auto-retrain
- In some cases phone line conditions
may be so poor that a connection cannot be established. Try
connecting from different locations.
- Ensure your protocol settings are
correct. Verify whether the Dial-Up connection desired is to
be made using NetBEUI, IPX/SPX (Novell), or TCP/IP, and make
sure that the necessary protocol(s) are bound to the Dial-Up
adapter in Control Panel, Network .
- Verify that the proper protocols are
enabled on the Dial-Up Networking connection associated with
the number you are dialing. When you install Dial-Up
Networking and create a new connection, you are prompted to
define the properties for the connection. Once the connection
is defined, go to Start, Accessories, Dial-Up
Networking. Right click the appropriate connection
icon. Click Properties and choose "Server
Type ". The protocols are selected here.
- If you are connecting to an ISP, you
will almost certainly be using TCP/IP and you will need to
configure your TCP/IP settings. In the Server Type
window click TCP/IP settings . Most connections should use Server Assigned IP address and DNS entries, but you might need to define these as static entries. If so, be sure they are correct. Also verify that they do not conflict with TCP/IP settings defined for the Dial-Up adapter in the Control Panel. Consult your Internet Service Provider or network administrator if you require further assistance in configuring TCP/IP for Dial-Up connections.
- For some connections you may find it
necessary to invoke a terminal window in order to manually
perform the login. View the properties for your dial-up
connection as described previously. Click
Configure. Choose Options.
Select the "Bring up a terminal window after dialing
option". You can also try disabling the "Log on to
Network" box on the Server Type window if the
trouble still persists, as this will sometimes prevent logging
on to the ISP host computer.
This section is designed to assist with the complete removal of the REM56 adapter, its associated files and subsequent registry entries caused by the installation. Successful completion of these steps returns the Windows 98 operating system to a state conducive to the proper installation of the Xircom adapter. After completing these steps return to Section 1 REM56 Adapter Installation for assistance with installing the Xircom adapter.
- Start the computer without the REM56 present
- If the computer is already running with the REM56 present, perform a complete shutdown and remove the adapter
- Restart the computer and allow Windows 98 to boot fully
- In the Control Panel, double click the Modems icon
- Remove all references to the REM56 adapter by selecting each entry and clicking Remove
- In the Control Panel , double click the Network icon
- Remove all references to the REM56 adapter by selecting each entry and clicking Remove
- When finished click Close
- Choose No when prompted to restart the computer
- Delete the following files:
- WINDOWS\INF\MDMCM28.INF (original entry)
(only files pertaining to Xircom)
- WINDOWS\INF\OTHER*.INF (only files pertaining to Xircom)
- Using Windows Explorer, delete the following subdirectory tree:
Note: The WINDOWS\INF directory is hidden by default. To view this directory open Windows Explorer, select View from the Toolbar, choose Folder Options from the menu and select the View tab and choose Show all files under the hidden files folder. Click Apply then OK to return to Explorer.
Warning: The following step involves making modifications to the system Registry. The instructions here should be followed exactly, and you should read them through before beginning. Manually making incorrect modifications to the Registry could cause your system to malfunction. If you are unsure about working with the Registry, we recommend that you consult your Microsoft documentation for clarification regarding Registry terminology and use of the Registry editor. It is also recommended that you back up the Registry before proceeding.
In the following registry path descriptions, HKLM refers to the HKEY_LOCAL_MACHINE key.
- Start the Registry Editor (Start, Run, type Regedit, and click OK). Remove from the registry:
- Click on the plus sign beside the following key in the registry path:
- Under this key one or more numerical keys (000x) will be displayed.
- Click on each of these and view the contents of the right pane of the editor to determine if the key in question is making reference to the REM56 adapter.
- If so, remove the key from the Registry.
- Perform this verification for each numerical key listed here.
- REMOVE ONLY THOSE KEYS THAT REFERENCE THE REM56 ADAPTER.
- In a similar manner, perform the same operation for any numerical keys listed under:
- Close the registry editor.
- Shut down the computer and then restart it.
- Open the Control Panel and double click the PC Card (PCMCIA) icon to ensure that the PCMCIA Wizard has run.
- If the PC Card Properties window indicates Empty Socket 1, Empty Socket 2 return to Section 1 REM56 Adapter Installation.
- If the PCMCIA wizard appears accept the default answer No for each question and Yes to restart the computer.
- Return to Section 1 and begin the installation.
- Computers with Cardbus Controllers
- Many new laptop computers are now equipped with Cardbus PC Card slots. Cardbus is a relatively new 32-bit extension of the PCMCIA 16-bit interface standard. Cardbus slots support adapters designed specifically for Cardbus, as well as standard PCMCIA adapters such as the Xircom REM56 adapter. However, in some ways Cardbus slots and their associated controllers behave differently than standard PCMCIA slots, and this can occasionally result in installation difficulties.
The following items should be noted:
- PCMCIA controllers are listed in the Device Manager under the PCMCIA Socket group. Standard PCMCIA controllers will normally indicate one controller for the system (a common type is a PCIC or compatible PCMCIA controller). Cardbus controllers, on the other hand, will indicate a separate controller entry for each slot, so normally there will be two controller entries displayed. Common types of Cardbus controllers include the following:
-Toshiba* TOPIC* controller
-Texas Instruments* 1130 Series* (1130, 1131, 1132)
-Texas Instruments* 1200 Series* (1220, 1250)
-Cirrus* Logic* 6832
- Xircom recommends a SYSTEM.INI memory exclusion range of C000-CBFF with Cardbus controllers instead of the standard PCMCIA adapter range of C000-CFFF
- Computers with Cardbus capability
frequently include Card and Socket Management software of some
kind. While standard PCMCIA slots usually do not require this
software in Windows 98, it often is necessary for Cardbus
- Disabling an infrared serial communications port
-If your computer contains an infrared communications port as well as other additional hardware features, it may be necessary to disable the infrared port to free up an interrupt for the Xircom REM56 adapter to use.
-If this is necessary, the device should be disabled both at the System BIOS level (if possible) and within Windows 98.
-To disable the port at the system BIOS level, you will need to enter the system BIOS menu or run the computer's BIOS setup utility program.
-Refer to your computer's documentation for complete information on disabling an infrared communications port.
-To disable the port in Windows 98:
- Go to the Device Manager (Control Panel, System, Device Manager)
- Double click the Ports (COM and LPT) icon
- Double click the entry for the infrared communications port. At the bottom of the Properties window there will be a section entitled Device Usage.
- Remove the check mark from the box Exists in this hardware profile and place a check mark in Disabled from all hardware profiles box.
- Click OK. If you disabled the device in the current profile (usually this will be the case), a red 'X' should appear on the entry listed for the infrared device.
- If there are multiple infrared device
listings we recommend that you disable all of them, at least
until you have successfully installed the adapter.
- Modifying Adapter Resources - In a standard installation (even one that may exhibit an error condition) the resource values for the REM56 and REM56 adapter appear in the following format:
-Input/Output Range 02E8-02EF
-Input/Output Range 0120-013F
-Interrupt Request 10
-Memory Range 000D2000-000D2FFF
-Memory Range 000D4000-000D7FFF
-The value represented by the first Input/Output range identifies the I/O port addresses assigned to the modem side of the
adapter (this value is discussed in greater detail under Troubleshooting the Modem Installation earlier in this document).
-The value of the second Input/Output range represents the I/O port addresses assigned to the network adapter. These ranges seldom cause difficulties and the REM56 installation is rarely affected by whatever range is assigned here as long as these locations reside somewhere in lower memory (commonly it will fall within the range of 0100h to 04FFh).
-The Interrupt Request values commonly used are 03, 05, 10, 11, and 15. However, with many new computers that include several value added hardware devices many of these (and in some cases all of these) interrupts are already in use before the adapter is inserted. Such as interrupt 03 which is traditionally assigned to COM2 and COM4 can be taken by a Serial IR device. Interrupt 05, traditionally assigned to LPT2 is often taken by the onboard sound card. Interrupts 10, 11, and 15 are regularly taken by devices such as a Digital Sound Processor, Docking Stations and SCSI devices. In order to free an interrupt for the REM56 adapter it may be necessary to disable one of these devices. Additional Notes Section covers the steps necessary to disable the more common devices.
-Memory values can fall anywhere within the range 000C0000 to 000EFFFF, but the REM56 is not the only device that uses memory
segments in these ranges. Xircom recommends using the D-range (000D0000-000DFFFF) memory segment for best results. In some cases
the adapter MUST be assigned to memory blocks in this range in order for the network portion of the adapter to function properly.
As stated above, the characteristics that apply to the first Input/Output range are somewhat different than the rest. This range applies to the modem. The range specified will dictate which COM port the modem is assigned to, and this value cannot be changed directly. This Input/Output range can ONLY be altered by changing the setting listed in the 'Setting based on' box to a different 'Basic configuration'. Normally the associations are as follows:
-Basic Configuration 0000 02E8-02EF COM4
-Basic Configuration 0001 03E8-03EF COM3
-Basic Configuration 0002 02F8-02FF COM2
-Basic Configuration 0003 03F8-03FF COM1
-Basic Configuration 0004 02E8-02EF COM4
-Basic Configuration 0005 03E8-03EF COM3
-Basic Configuration 0006 02F8-02FF COM2
-Basic Configuration 0007 03F8-03FF COM1
The difference between the first group
(0000-0003) and the second (0004- 0007) is that on some computers,
choosing the settings in the first group will prevent the other
resource values (interrupt, memory, and the other Input/Output
range) from being modified. Therefore, if you are making manual
changes and you wish (for example) to use the modem on COM3, we
recommend choosing basic configuration 0005.
- Client to protocol association matrix- Client Type Protocol Type
- Client for Microsoft Networks TCP/IP (default), NetBEUI, or IPX/SPX
- Client for NetWare* Networks* IPX/SPX compatible protocol
- Novell* NetWare* Client32 IPX 32-bit Protocol for NetWare - Client 32
- IPX/SPX compatible protocol
- Other clients Client specific protocols or TCP/IP.
- PCM (56 Kbps) connections
In order to achieve 56Kbps connects, there can be only one digital to analog conversion between the connecting modems. Also, the modems at both ends of the call must be K56Flex compatible to achieve 56K speeds, if not, they will negotiate a standard V.34 rate. Current FCC regulations limit download speeds of the modem to 53Kbps. Failure to make PCM (Pulse Code Modulation) 56K connections could be due to any of the following items:
- Incompatible 56K modem types (i.e., K56flex vs Non-K56Flex modems)
- Poor line quality
- Excessive distance in the analog portion of the connecting line
- More than one digital-to-analog conversion in the connection path.
The ITU has released the V.90 standard, which incorporates aspects of both K56flex and non-K56Flex PCM schemes into a standard that will allow interoperability of all 56K capable modems. Xircom expects to release a free flash upgrade that will bring the REM56 adapter up to the V.90 standard in the near future.
In an attempt to force PCM connections, the following command string values can be used:
+MS=K56,,,##### - where ##### is a five digit number selected from the the following list of values:
- +MS=K56,,,32000 32 Kbps
- +MS=K56,,,34000 34 Kbps
- +MS=K56,,,36000 36 Kbps
- +MS=K56,,,38000 38 Kbps
- +MS=K56,,,40000 40 Kbps
- +MS=K56,,,42000 42 Kbps
- +MS=K56,,,44000 44 Kbps
- +MS=K56,,,46000 46 Kbps
- +MS=K56,,,48000 48 Kbps
- +MS=K56,,,50000 50 Kbps
- +MS=K56,,,52000 52 Kbps
Note: The commas in the above
commands are required. They represent the default values for
that command string position.
This applies to: