Products Applications Support Partners News About Digi Where to Buy
   
 
 
Products
• device servers
• terminal servers
• console management
• USB
• async
 
 
Frequently Asked Questions
Windows NT and the T1 Modem Bank
  • What are the most current driver files for the T1 Modem Bank for Windows NT?
  • Select File Manager (NT 3.51) or Windows Explorer (NT 4.0). In the following path: <WINNT>/System32/Drivers, select the DIGIFEP5.* file. Highlight this file and click on "File", "Properties". A description will be displayed which includes the version number.
  • What driver should I install for my intelligent asynchronous Digi product?
    The drivers that ship with Microsoft Windows NT 3.51, and NT 4.0 are no longer the most current Digi drivers for NT. The current released driver is version 2.1.0, and may be downloaded either from the BBS or the ftp site. The downloadable filename is 4000821R.exe for Windows NT 3.51 and NT 4.0. [4001438K.exe for Windows NT 3.50] You will also need to download installr.txt, which contains installation instructions for both Windows NT 3.51 and Windows NT 4.0.
  • The event viewer error message: "Wait confirmation failed" means?
  • Check the dip switch settings on the board. Typically this error message indicates that the dip switch settings on the board do not match the I/O address chosen in the driver configuration.

    Verify that the correct driver has been installed for the Digi product. An incorrect driver will also cause this error message.

    Verify that the I/O address chosen does not conflict with any other devices in the system.

  • The event viewer error message: "BIOS image failed to load" means?
  • Verify that the memory address chosen does not conflict with any other devices in the system.

    If the system is an ISA machine, verify that shadowing has been disabled in the CMOS setup for the memory range the Digi board is being installed in.

    If the system is an EISA machine, verify that the board has been configured in the system's EISA configuration utility, and that the settings chosen in the ECU match the settings chosen when the driver was configured.

    If the system is a MCA machine, verify that the board has been configured with the reference diskette for the system, and that the settings chosen match the settings chosen when the driver was configured.

    If there are no known memory conflicts, and shadowing has been disabled, run the DOS diagnostic for the Digi product to verify the hardware.

  • The following event viewer error message : "While validating that COMx was really a serial port, the contents of the divisor latch register was identical to the interrupt enable and the receive registers. The device is assumed not to be a serial port and will be deleted" means?
    Most likely conflicting non-intelligent port(s) have been configured. This usually occurs when changes are made in Control Panel, Ports. The conflict must be removed either by changing the names of the Digi ports to avoid the conflict or by removing the conflicting serial port configuration(s).
  • To remove these error messages, follow these steps:
  • Start the registry editor by typing "start regedt32" from the command prompt.
  • Select the following: HKEY_LOCAL_ MACHINE on Local Machine, System, CurrentControlSet, Services, Serial, Parameters. Typically, no keys should be listed beneath Parameters. Check the values of any keys listed to locate the conflicting serial port(s).
  • Delete any conflicting keys under Parameters. Highlight the serial port key and press "Delete". Repeat for each conflicting serial port configuration. Reboot the system and check the event viewer to verify that the error messages do not reoccur. The errors may reappear later if any operations are attempted in Control Panel, Ports.
  • CAUTION: Any mistakes made in editing the registry may have disasterous results requiring you to boot to a different Control Set or to reload Windows NT.
  • The following event viewer error message(s) : "User configuration for parameter ntx*Line1Concentrator1Port1 must have PortAddress." "User configuration for parameter Serial0 must have PortAddress." means?

    These errors are a result of a bug in the Control Panel, Ports applet. The problem has been reported to Microsoft. To remove these error messages, follow these steps:
  • Start the Registry Editor by typing "start regedt32" at a command prompt.
  • Select the following: HKey_Local_Machine on Local Machine, System, CurrentControlSet, Services, Serial, Parameters. Typically, no keys should be listed beneath Parameters. Check the values of any keys listed to locate the conflicting serial port(s).
  • Delete any conflicting keys under Parameters. Highlight the serial port key and press "Delete". Repeat for each conflicting serial port configuration. Reboot the system and check the event viewer to verify that the error messages do not reoccur. The errors may reappear later if any operations are attempted in Control Panel, Ports.
  • CAUTION: Any mistakes made in editing the registry may have disasterous results requiring you to boot to a different Control Set or to reload Windows NT.
  • The following event viewer error message: "Source ntx* could not be found. It contains the following insertion string(s): ntx*" means?

  • Go into Control Panel, Network.
  • Highlight the Digi adapter and click on "Remove".
  • Choose "OK".
  • Choose "Do Not Restart Now".
  • Go into File Manager, choose the <WINNT path>/System32 path. Delete the dgconfig.* file(s).
  • Restart your system and reinstall the Digi driver.
  • RAS Port Status waivers between Hardware Failure, Line Non-Operational and Normal, Waiting for Call.
    This error can result from one of several different causes:
  • 1. Using 8 pin RJ45 cabling instead of 10 pin cabling. 10 pin RJ45 cabling is required for Remote Access Service.

    2. The modem.inf file which shipped with NT 3.51 is not current or not correct. Check with the modem manufacturer to obtain a more current version of the modem.inf file. If you are using the unimodem with NT 4.0, be sure that your modem type is supported by unimodem. Verify this with your modem manufacturer. If the modem is not supported by unimodem, refer to Microsoft Knowledge Base document Q150808 on how to disable unimodem.

    3. Not selecting the correct modem type in RAS.

    4. With US Robotics Sportster modems, the dip switches on the modem are not set correctly for use with RAS. Switches 3, 7, and 8 should be down - different from factory default.

    5. The registry may have the wrong information. To see if this is the case: Start the Registry editor by typing "start regedt32" at a command prompt. From the HKEY_LOCAL_MACHINE subtree, go to the following key: \System\CurrentControlSet\Services\Asyncmac\Parameters\ports

    This entry may be set to a value that is less than the number of incoming ports available. If NetBEUI is not loaded, this entry is not updated properly. If this is the case, first install NetBEUI, then reinstall the Digi driver, and then reinstall RAS. Simply editing the port value in the registry is not suggested and will not correct the problem (refer to Microsoft Knowledge Base document Q138226).

    6. The Digi hardware could be defective.

    7. The system may be running out of resources. If this is the case, disable some or all of the ports for outgoing calls and make them incoming lines only. For each outgoing connection/protocol pair, a Control Block is required. This uses an amount of memory equal to: (Number of ports)*(Protocols per port)*sizeof(Control Block) However, DialIn ports have just one Control Block for 256 connections.

  • Remote Access Service is not yielding expected throughput.

  • For Windows NT 3.51:
  • Edit the modem.inf and serial.ini files to indicate the desired baud rate by following these steps:
    • In the modem.inf file, which can be found in the following subdirectory: <NTpath>/system32/RAS/modem.inf in the section corresponding to your modem type, the specified parameters can be changed to match your desired baud rate:
    • Example:
    • US Robotics Sportster 28800 VFC] <-your modem type
    • CALLBACKTIME=10
    • DEFAULTOFF=compression
    • MAXCARRIERBPS=115200 <- choose baud rate
    • MAXCONNECTBPS=115200 <- choose baud rate
    • <speaker_on>=M1
    • <speaker_off>=M0
    • <hwflowcontrol_on>=&H1&R2
    • <hwflowcontrol_off>=&H0&R1
    • <compression_on>=&K1
    • <compression_off>=&K0
    • .
    • .
    • .
    • Also, in the serial.ini file, which can be found in the following subdirectory: <NTpath>/system32/RAS/serial.ini within each section corresponding to each port on the Digi board, the specified parameters can be changed to match your desired baud rate.
    • Example:
    • [COM2]
    • DEVICETYPE=Modem
    • DEVICENAME=US Robotics Sportster 28800 VFC
    • MAXCONNECTBPS=115200 <- choose baud rate
    • MAXCARRIERBPS=115200 <- choose baud rate
    • USAGE=ClientAndServer
    • DEFAULTOFF=compression
    • CLIENT_DEFAULTOFF=Compression
    • INITIALBPS=115200 <- choose baud rate
    • .
    • .
    • .
  • For Windows NT 4.0:
  • If you are using the unimodem with NT 4.0, go into Control Panel, Modems, highlight the modem and click on Properties. Change the Maximum Speed to the desired baud rate.
  • What type of modem pooling software is available for NT?
    Modem Pooling Applications are listed below:
  • 1. SAPS

    Supported by SpartaCom

    Supports modem pooling on Windows, Windows NT, and OS/2 Servers

    • SpartaCom USA
    • 1951 Airport Road
    • Atlanta, GA 30341
    • 770-946-9149
    • FAX 770-946-5194
    • Compuserve 70613,457
    • SpartaCom Sales Europe B.V.
    • Parelgris 48 STE 211 2718 NV Zoetermeer
    • The Netherlands
    • 31 79 614 140
    • FAX 31 79 619 990
    • Compuserve 100265,1625
    • Email Spartacom@IB.COM

    The SAPS Windows 95 client and server software is downloadable from www.tspco.com.

    2. WINport/FAXport

    • Supported by LANSource
    • Supports modem & faxmodem pooling on WindowsNT, Novell, and OS/2 servers.
    • LANSource
    • 221 Dufferin Street STE 310A
    • Toronto, Canada M6K 3J2
    • 800-677-2727, 416-535-3555
    • FAX 416-535-6225

    Email sales@lansource.com

  • What are the installation instructions for the PC/X and MC/X under Windows NT?

  • The installation instructions are found in the pcx_nt.txt document. This document may be downloaded from the BBS or the ftp site.
  • What options are available for testing the ports under Windows NT?
  • For COM1 through COM9, use the Terminal program located in the Accessories folder. Choose Settings, Communications, and select the port you have connected the modem to. Configure the communications settings to match the modem and choose "OK". A blinking cursor will appear. Type "AT" and hit return. The letters "AT" should be echoed back to the console as well as an "OK". This will show that data was sent to the modem and a response was received back from the modem. If you have a Digi loopback connector on the port, the characters that you type within the terminal session should be echoed back to the console. This will show that data is being both transmitted and received on the port.

    For COM1 through COM256, use Digi's TTY program. This program is available either on the BBS or the ftp site. Choose Settings, and select the port you have connected the modem to. Configure the communications settings to match the modem and choose "OK". Then choose Action, Connect. A blinking cursor will appear. Type "AT" and hit return. The letters "AT" should be echoed back to the console as well as an "OK". This will show that data was sent to the modem and a response was received back from the modem. If you have a Digi loopback connector on the port, the characters that you type within the terminal session should be echoed back to the console. This will show that data is being both transmitted and received on the port.

    NOTE: It is possible to start two instances of TERMINAL or TTY and test the ports by connecting them with a standard "NULL MODEM" cable. Set each to the same baud rate, parity, and stop bits. Try typing some characters in the active window. If you see characters appearing in the opposite window, then the ports are communicating.

  • I'm writing my own application and I am not able to access any ports above COM9.
  • In Windows NT, the ports above COM9 must be addressed with the following naming convention: \\.\COM#. For example, COM10 should be addressed as \\.\COM10. You may also address COM1-9 with the same naming convention. Windows NT will recognize either name.
  • How do you install printers on the Digi ports?
  • Verify that you are using a null modem cable between the Digi port and the printer. To set up the Digi ports for printing, go into Print Manager. If you have not already created a printer, select "Create Printer". Fill in the required information for the new printer (printer name, driver).

    1. For the "Print to :" option, select "Other", then select "Local port".

    2. Type in the Digi port name followed by a colon (for example, COM5:). This will bring up the Ports applet.

    3. Select the port you have just configured from the list displayed, and choose "Settings". Set the baud rate to 9600, data bits to 8, parity to none and stop bits to 1.

    4. Select "OK" and then "Close".

    Repeat these steps for any additional printers you need to add. For printers that have already been created, select "Properties" for that printer, and then follow the above instructions. Once you have configured all the ports you will be using for printing, you must restart NT. You may notice that the ports you have configured do not show up under the "Print to:" list. These will not display until after you restart NT.

    Once you have restarted NT, go back to Print Manager, and select "Properties" for each printer. Go to the "Print to:" option, and select the Digi port from the list displayed.

  • The Modem Xem is not being auto detected by RAS (Windows NT 3.5x).
  • When the Modem Xem driver is installed, the modem.inf entry for this modem type should be written to the existing modem.inf file. However, if RAS is not already installed when the Modem Xem is installed, there is no existing modem.inf file to write to. In this case, once RAS is installed, before adding the Modem Xem ports to RAS, you must first go back into Control Panel, Network, and configure the Modem Xem driver. Once you have viewed the configuration, click on "OK" to exit the Network settings applet. During the rebinding process, the modem.inf entry for the Modem Xem product will be written to the modem.inf file in the /system32/ras directory. Once that is complete, restart NT, and reconfigure RAS. The Modem Xem should now display as a modem option and the modems should now be autodetected by RAS.

Last updated January 3, 1997

93006061 Revision D.


products | applications | support | partners | news | about Digi | where to buy | contact us | site map

Copyright © 1996-2002 Digi International. All rights reserved.
Contact Us Site Map Product Selector Digi Homepage