CHECKING THE NETWORK PROTOCOLS ON A WINDOWS SYSTEM
To verify that the client is configured for the correct type of networking and networking protocols
on Windows 95, 98, and Me operating systems:
1. From the Windows desktop, click on Start then select Settings→Control Panel.
2. Double-click on Network. Verify that the list of network components includes Client for
Microsoft Networks and, optionally, Client for NetWare Networks.
3. If the item you want is available, click on Cancel and go to the next step. If the items you
require are missing, click on Add and select Add Client to add the client software of the
networking protocol that you want to install.
4. If the proper client software is installed but you do not see the required protocols, click on
Add then follow the on-line instructions.
If this is the first time that networking support is installed on your computer, Windows prompts
you to enter the computer and workgroup names. These names are used to identify your
computer on the Microsoft Network Neighborhood. To enter the computer and workgroup
names:
1. If the Network window is not opened, click on Start, select Settings→Control Panel, then
double click on Network.
2. Click on the Identification tab. The Windows NT version of this window is similar.
3. In the Computer Name field, enter a unique name for your computer.
4. In the Workgroup field, enter the name of your workgroup. The name must be the same for
all computers in the wireless network.
5. Optionally, provide a description of the computer in the Computer Description field.
For more information about setting your Windows network properties, consult the Windows
documentation or Windows on-line help.
DEVICE CONFLICT ON A WINDOWS SYSTEM
A device conflict under Windows NT may be related to the RoamAbout ISA card or PC Card. To
detect which card is causing the conflict, use the Windows NT diagnostics. This problem can also
appear on Windows 98 and the early version of Windows 95 (OSR0).
To help determine if a device conflict exists, check the following:
• If there is a conflicting I/O Base setting, the RoamAbout PC Card usually does not work at all
and both LEDs are off.
• If there is a conflicting IRQ value, LEDs may flicker but you cannot connect to the network. In
a number of cases, the card may succeed in connecting to a wireless device, but fail to connect
to the network operating system.
• Another device in the computer no longer works properly.
Windows NT
To check the I/O port and IRQ values, perform the following:
1. From the Taskbar, click on Start. Select Programs→Administrative Tools→Windows NT
Diagnostics.
2. Click on the Resources tab.
3. Click on the IRQ button to display the Interrupt Request (IRQ) vectors currently in use by
other devices in your computer.
If IRQ value 10 (default value for the PC Card) is not used, write down IRQ 10. If 10 is used,
select a value not listed in the Windows NT Diagnostics window and write it down. Values
include: IRQ 15, 12, 07, 05, 04, 03
4. On the Resources screen, click on I/O Port. If I/O Port value 0400-043F is not used, write down
I/O Port 0400-043F. If this value is used, select an unused value and write that down. I/O port
values are in the range 0300 to FFC0 with increments of 40. Examples:
0300, 0340, 380, 03C0;
0400, 0440, 0480, 04C0;
.
.
FF00, FF40, FF80, FFC0.
If you need to select an address, start with the first unused address after 0400.
5. Open the driver properties, refer to the online help for information.
6. Enter the I/O Port and IRQ values that you wrote down.
A conflict can still occur even after using the Windows NT Diagnostics program to determine
unused I/O port addresses and IRQ values. This can happen when your computer has one or more
devices and/or peripherals installed that claimed an I/O Base Address or IRQ value without
notifying the Windows NT operating system. Therefore, the Windows NT Diagnostics program
does not display these values as used.
If there is a device conflict, select alternative settings for I/O Base Address or IRQ values. You may
need to try multiple values before resolving the problem. To isolate the problem, you should
change only one parameter at a time. For example, try to resolve a possible conflict with the I/O
Base Address. If that does not work, try to resolve a possible IRQ conflict.
If you know which device is conflicting with the PC Card, you have the option of changing that
device’s I/O address or IRQ instead of changing the RoamAbout PC Card or ISA card.
Depending on the computer, you might need to verify the settings of the BIOS which is loaded
when you start your computer.
If the computer previously had a network card installed and the network card was running in 32-
bit operation, you may need to set the BIOS to PCIC - 16 bit. You may also need to disable the
network card in the Control Panel - Devices.