Uninstalling the drivers and applet in Windows NT4.0 is generally not necessary. They will remain dormant until the time comes that you install another LAVA PCI card. The following procedure is provided in case that you do need to uninstall these drivers.

A) Removing Files

Remove the following files from your hard drive:

detlava.sys and seriallava.sys from winnt\system32\drivers

lavaport.cpl from winnt\system32\

B) Cleaning Registry

NOTE: To run the registry editor go to Start|Run, type “regedt32″ and then click OK.

Go to:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Enum\Root

1) Highlight the LEGACY_SERIALLAVA

2) Go to the Security menu and click the Permissions tab.

3) Check the box for Replace permissions on existing subkeys.

4) Change type of access from Read to Full Control.

5) Highlight the LEGACY_DETECTLAVA

6) Go to the Security menu and click the Permissions tab.

7) Check the box for Replace permissions on existing subkeys.

8) Change type of access from Read to Full Control.

9) Remove the LEGACY_DETECTLAVA and LEGACY_SERIALLAVA keys.

10) Go to:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services

11) Remove the DetectLava and SerialLava keys. You do not have to change security privileges for these folders because they are already set at Full Control.

Question

I have installed my LAVA PCI serial card and then my Modem was installed by Plug and Play. I then looked in Control Panel|Modems and tried to click the properties, but nothing happened.

Answer

When a modem installs in the PnP (Plug and play) manner (at boot-up), the modem installs in Control Panel|Modems but when you click the properties button nothing happens. This is a known problem for which we are endeavouring to find a solution. The solution is:

Go to regedit by entering regedit from Start|Run.

Open up

HKEY_LOCAL_MACHINE System CurrentControlSet Services Class Modem.

Inside there may be several numbers, i.e. 0000,0001,00002….

Open up each of those and look for DriverDesc such as: 3ComImpactIQ or the name of the modem that you are using.

That is the folder that will need the string added to it.

To add the string the following method is followed:

Go to the Edit menu then New and String Value.

Change the name of that new string to the following exactly: AttachedTo

Change the value to COMx where x is the com port number to which the modem is attached. (i.e. COM3) by double-clicking it.

This note applies only to older versions of the LAVA DSerial-PCI and LavaPort-PCI.

Newer versions of these products have a chip with the LAVA logo silkscreened on.

Problem

Neither port works, and the port settings shown under “Multifunction Adapters” do not match those shown under “Ports.”

This “Parent Child Mismatch” problem is handled as follows:

Go to Device manager and write down the addresses for COM5, 6,7 and 8 by double clicking each port in Ports and then going to Resources.

Then go to Multifunction Adapters in Device Manager and double-click the first port entry and enter resources.

Then uncheck Automatic Settings and put in the addresses you wrote down for COM 5 and 6 in there. Click OK and OK again. Go to the next port in Multifunction Adapters and put COM 7 and COM 8 in there.

Question

I am trying to install the LAVA PCI card in an OS other than DOS, Win3.11, Win95/98/Me, NT4.0, or Windows 2000. I have commands or a utility that can configure my port. However, I have no way of knowing how the PCI bus on my system has configured the card. What can I do?

Answer

LAVA provides a utility that reports the I/O address and IRQ assigned by the PCI bus on your system. This utility MUST be run from DOS level.

This utility can be run from a DOS boot disk to report the I/O address range and IRQ that the PCI bus on your system has configured our card to.

Use this utility if you wish to configure a parallel port in an OS other than DOS, Win3.11, Win95/98/Me, NT4.0, or Windows 2000. For example SCO UNIX, Linux… i.e. using the makedev parallel command. Consult the Man Pages or documentation for the OS for the appropriate commands.

Create a DOS boot disk in DOS compatible system (not NT4.0) with the following command:

format a: /s

Copy Lavaconf.exe to that diskette.

(Can be downloaded from the Utilities portion of our web site for your PCI card www.lavalink.com or can be found in the Win3.11 directory on the LAVA Installation and Utilities disk).

Restart the machine that you wish to install the LAVA Parallel-PCI in and boot from that boot disk you created.

Run the Lavaconf.exe program.

If this software reports an address that ends with 0, then the ending address will end in 7.

If this software reports an address that ends with 8, then the ending address will end in F.

i.e. Lavaconf reports:

10F0

then in the OS put 10F0-10F7 for the Input/Output Range.

i.e. Lavaconf reports:

10F8

then in the OS put 10F8-10FF for the Input/Output Range.

1) Remove files from hard drive

a) in Windows System folder:

L650ui.dll

link650.vxd

or

lavasp.inf

lavamf.inf

b) in Windows inf folder:

LavaPCI.inf

LavaMF.inf

c) in Windows inf other folder:

the file with our Manufacturing name (Lava Computer MFG Inc.) as its name.

2) Cleaning Registry

HKLM = HKEY_LOCAL_MACHINE

In HKLM Enum MF Child0000 remove the key that has PCI&VEN_1407&DEV_0200… as its name

In HKLM Enum MF Child0001

remove the key that has PCI&VEN_1407&DEV_0200… as its name

In HKLM Enum PCI

remove the key that has VEN_1407&DEV_0200… as its name

In HKLM System CurrentControlSet Control InstalledFiles

remove the items that have names:

L650ui.dll

link650.vxd

In HKLM System CurrentControlSet Services Class MultiFunction. Open up all the subkeys in here and check for a reference to LAVA and remove that key.

In HKLM System CurrentControlSet Services Class Ports Open up all the subkeys in here and check for a reference to LAVA and remove that key.

Installation

On install during the bootup process, the Linux hardware discovery utility detects the LavaPort-PCI correctly and installs it as ttyS4 and ttyS5. This setting will change depending on how many serial ports you have and how they are configured.

To verify proper installation you must first find out the port information (I/O range, IRQ) for each serial port. To retrieve that information type at the command line:

lspci -v

You will then see two separate entries for a “Serial Controller: Lava Computer MFG”. Below each will be a IRQ number and an I/O port. Write down that information for all ports (for example, IRQ 12, e400, IRQ 12, e800).

First you must verify that the card was installed correctly. To do this at the command line type:

setserial -a /dev/ttyS4

Note: ttyS4 is the first default PCI serial port. This setting may change depending on how many serial ports you have.

If the card was correctly configured by Linux you will see the following information:

/dev/tty4, Line 4, UART 16650V2, Port: 0xe400, IRQ: 12

Baud_base: 460800, close_delay: 256, divisor: 0

closing_wait: 15360

Flags: spd_normal skip_test

Your port and IRQ should match the information collected earlier.

If you find that the information displayed does not match the above (port and IRQ should match your information), then carry on to the next step below. If the data is correct then the installation is complete.

To set the serial port to the correct settings, edit the file:

/etc/rc.d/rc.local

Add the following lines at the end of the file:

setserial /dev/ttyS4 port 0xe400 irq 12 uart 16650v2 baud_base 460800 ^fourport

setserial /dev/ttyS5 port 0xe800 irq 12 uart 16650v2 baud_base 460800 ^fourport

The example above uses the information gained from the lspci -v command. The details of your information may be different. Be sure to save the added changes. On reboot all of the ports should be operational.

Okay. So I wanted to be the fastest kid on the block. I went out and bought a Motorola BitSurfr Pro (or US Robotics Courier I-modem, or Adtran Express XR/XRT, or 3COMImpact IQ, etc.). I rewired my house for ISDN, which cost me a small fortune, and now I’m ready to Surf the Web at blazing speeds! There’s just one problem. According to the packaging and all the advertising, ISDN is supposed to give me 128 KBps digital transmit rates - “over 4 times faster than the fastest analogue modem”. But all I can get right now is barely 80 kbps. My phone company says that I have two 64 kbps “B” (bearer/data) channels and one D (service) channel as part of my basic rate interface (BRI). I should be able to link the two B channels together and achieve 128 kbps. But I can’t even get close to that!

Is there a solution?

Yes! The LavaPort Communications Accelerators.

So what exactly is the Problem?

Simple. Your serial port isn’t fast enough for ISDN.

The documentation for my external ISDN terminal adapter recommends a 16550 UART serial port (which I have). Supposedly, this type of port supports a maximum data rate of 115 200 bits/second.

That’s true. The problem is, that 115.2 kbps is a theoretical maximum. If you’re communicating using Windows, 115.2 kbps is often difficult to achieve.

Why?

Using an analogue modem in DOS (or other single-tasking environment), most users should not have a problem achieving very close that rate over a decent phone line. Windows however, throws another variable into the loop: a Graphical User Interface (GUI) which requires an exorbitant amount of CPU time, and therefore tends to slow everything down.

Furthermore Windows handles the 16550 UART very inefficiently. Because the buffer of the 16550 is relatively small (16-bytes), Windows “tells” the serial port to interrupt the CPU and request service after each byte transferred . Effectively, this causes the whole system to slow down during data transfer.

What’s the solution?

The LavaPorts incorporate 32-byte FIFO buffers (the 16650 UART has twice the buffer of a 16550 UART). In addition, LavaPorts ship with Windows device drivers for Windows 3.1x &, Win95/98/Me/NT/2000/XP which allow the user to configure buffer triggers for most efficient operation. In this way, the port is triggered to interrupt the CPU only when really necessary, leaving the CPU free to perform other tasks. Since the LavaPorts incorporate a large buffer, the CPU can send & retrieve large chunks of data each time it services the port, rather than having to be interrupted for each byte sent or received. For transmission, the size of this “chunk” can actually be configured by the user using the Tx Blk (burst) function of the LAVA driver.

Unlike the 16550 UART, where the CPU must verify the status of the buffer after each byte sent to the serial port, LavaPorts allow the CPU to send a burst of data to the port without fear of error.

Well that’s great, but it still doesn’t get me beyond 115.2 kbps - it just makes me more efficient at the same, slow rate. How can I achieve 128 kbps?

You’ll notice that newer ISDN terminal adapters support 3 high-speed DTE rates: 115.2, 230.4, and 460.8 kbps. Now remember, we’re talking about serial port rates between the computer and terminal adapter - not between terminal adapter and telephone company. The outgoing (to the telephone line) rates can be 56, 64, 112, or 128 kbps - with the last two being key to this discussion. Think of it this way: if your TA is going to be transmitting out through the telephone system at 128 kbps (and probably compressing that data at least a little), shouldn’t you be feeding that transmission at a higher rate? That’s where LavaPorts become key. They support a maximum DTE rate of 460.8 kbps and can also fall back to rates of 230.4, and 115.2 kbps.

How do you do it, when others can’t?

The LavaPorts incorporate an onboard high-speed clock, which allows for DTE speeds faster than 115.2 kbps. Because the standard 16550 UART runs with an 1.8432 MHz clock-crystal, its mathematical maximum baud rate is 115.2 kbps. LavaPorts use a faster onboard clock-crystal (7.3728 MHz) and can therefore generate a faster baud rate. Combined with the its 32-byte buffer and Windows drivers, the Lavaport family breaks the 115.2 kbps barrier, efficiently and reliably.

A final question: One of the big headaches of ISDN is synchronizing flow control between the terminal adapter and serial port. How do LavaPorts handle this?

One of the main features of LavaPorts are their onboard flow control. First, let’s look at how flow control is handled by a 16550 serial port. The 16550 UART is basically a dumb device: it performs only two instructions: a) send what’s in the buffer, and b) if there’s a problem tell the CPU about it.

If the 16550 UART receives a signal from the ISDN adapter to stop sending data (in the form of either a toggling of the RTS/CTS line - hardware flow control - or in the form of an Xoff character - software), it will send this message to the CPU, but will continue sending the data which is in its buffer. Since the ISDN adapter can no longer receive this data, an error occurs and the CPU must find what bytes were not received and retry the transmission. In contrast, LavaPorts handle all flow control functions without intervention from the CPU. If a LavaPort receives a signal to stop transmission (either through hardware or through software flow control), it stops. The CPU is not interrupted needlessly, and no retry is ever required. When the signal to resume transmission is received, the LavaPort resumes, and only notifies the CPU when the data in its buffer has been depleted to the appropriate trigger level.

So if I get a LavaPort, I can use BONDING to actually achieve 128 kbps with my ISDN terminal adapter?

Now let’s get our terminology straight. LavaPorts are not synchronous DTE interfaces. It will not allow you to do what is technically called BONDING. LavaPorts will however support true 128 kbps operation - in asynchronous mode. You may therefore use both Asynchronous Inverse Multiplexing (AIMux) and Multi-Link PPP protocols to “bond” both 64 kbps B-Channels together to achieve 128 kbps. With Multi-Link PPP, you’ll be able to switch from 128 kbps to 64 kbps data + Voice and back seamlessly. Most importantly, a LavaPort will allow you to achieve the data rates which you paid for when you bought your ISDN terminal adapter: 128 kbps direct to your desktop.

Introduction

Dial-up Networking Requirements:

Windows CD

DNS server IP addresses (primary and secondary) from ISP:

Domain Name from ISP

Telephone number to ISP

User name for ISP

If dial-up networking is already installed with dial-up adapter and TCP/IP protocol then go straight to configuration.

Installation:

Verify if Dial-up Networking is installed:

Check Start, Settings, Control Panel, Add Remove Programs, Windows Setup

Then check in Communications, Details

If Dial-up Networking is selected, then it is installed.

Verify if Dial-up Adapter and TCP/IP protocol is installed:

Check Start, Settings, Control Panel, Network, Configuration

If Dial-up Adapter, TCP/IP protocol, and Client for Microsoft Networks is selected then they are installed.

Installation of Network Components:

In Start, Settings, Control Panel, Networks

Client for Microsoft Networks

Click Add Dbl Click Client

Choose Microsoft then Client for Microsoft Networks

Click OK

Dial-up Adapter:

Click Add , double-click Adapter

Choose Microsoft then Dial-up Adapter

Click OK

TCP/IP Stack:

Click Add, double-click Protocol

Choose Microsoft

Choose TCP/IP

Click OK

Click OK from configuration and Restart System

Configuration of TCP/IP:

In Start, Settings, Control Panel, Networks, TCP/IP properties the following settings are selected:

IP Address: Obtain an IP address Automatically

WINS configuration: Use DHCP for WINS Resolution

Gateway: Leave blank

Bindings: Select Client for Microsoft Networks

Advanced: Leave with Defaults

DNS Configuration: Enable DNS

DNS Configuration: Host (username)

Domain Name: (domain name)

DNS server search order: (Primary DNS Server)(Secondary DNS Server)

Setup of Connection Icon:

Double Click My Computer, Dial-up Networking, and Make New Connection Icons

Give Icon a name like the name of the ISP

If modem not displayed select modem from modem area

Select the highest modem speed

Make sure that Only Connect at this Speed is NOT selected

Click OK

Click NEXT in Make New Connection Wizard

Enter phone number to ISP

Setup of Dial-up Properties:

Click on the New Connection Icon just created

Click Server Type, Pick Dial-up Server: Choose PPP as Server Type

In Advanced Options: Enable Software Compression Checked

Log On to Server: Not Checked

Require Encrypted password: Not Checked

TCP/IP: (only Protocol enabled)

(disable IPX & NetBEUI)

TCP/IP settings: Make sure Server assigned IP address and Specify Name Server address are selected

Add Primary and Secondary Server IP addresses

For Primary and secondary WINS Configuration: Leave at 0.0.0.0

Check use IP header Compression and use Default Gateway on Remote Network

I am running an IBM 300 GL computer that has a LAVA PCI card in it. When I boot up I get a Parity error! Is there a BIOS setup setting that I can modify to get the system to boot normally?

This problem occurs on certain IBM machines. There is a BIOS setting that can ensure that the system boots up normally while the card is in the system.

In your BIOS setup go to: Advanced Setup | PCI control and set PCI Parity Control to Disabled.

On some IBM and COMPAQ machines some BIOS (CMOS) setup settings could cause the machine not to boot up completely.

Change BIOS settings without the card in the system.

NOTE: Not all systems have all these settings. Included are a few of the settings that have caused problems on various IBM and COMPAQ machines. Consult your IBM or COMPAQ manual for instructions on how to enter the setup and where to find these settings.

Enter the BIOS and go to Advanced and then BUS Options.

Verify that:

Plug and Play OS Installed is set to NO or DISABLED.

PCI Parity is set to Disabled.

PCI Bus Mastering is set to Enabled.

PCI Adapter Reset is set to Disabled.

PCI Adapter Reset on Warm Boot.

Question:

I have my TA installed on a LavaPort with Windows NT 4.0 and my TA configured and installed using its 230400 modem installation file but Dial Up Networking does not have that 230400 setting. I tried editing the Connection to no avail. What should I do?

Answer:

Dial up Networking takes its initial speed setting from the maximum setting set in Control Panel modems. To make sure that Dial Up Networking has that 230400 setting in it, make sure that you configure the modem to 230400 in Control Panel modems and then add the New Dial Up Networking Connection. If you have already added that connection and it only has that 115200 setting then delete that connection, configure the modem and add a New Dial Up Networking Connection.

Question:

My Terminal Adapter needs to have an AT command sent to it to configure it to 230400. After I send it that command I can’t get a response in my terminal application. What should I do?

Answer:

Many terminal adapters can only autobaud up to 115200 after that they have to be set to a fixed rate of 230400 that is why you have to send it that AT command. The response you are getting when it does not respond in your terminal application is normal. Don’t worry about it. Simply disconnect or hangup after sending that AT command. Configure your baud rate in your application to 230400 and then connect again. At this point you will be getting a response from your TA and you can complete your installation.