PNPFAQ.TXT 7 OCT 96
Revision 1.1
MATT ALFORD
DIAMOND MULTIMEDIA SYSTEMS, INC.
CONTENTS
1 Introduction
2 Windows 95 PnP Modem Issues
2.1 Modem not configuring properly, not working consistently, or
not being found.
2.2 Win95 not detecting modem except after a reboot or multiple
reboots
2.3 Software can't access modem on Com 5
2.4 Need to manually reconfigure modem
2.5 Need to use keypad for a mouse
2.6 Getting the SupraExpress 288iPnP modem to work in MS-DOS Mode.
3 Windows 3.1x PnP Modem Issues
3.1 Dos Configuration Manager Not Loaded when running Where's The
Modem
3.2 NVS error reported when starting computer
3.3 No ESCD.RF file found when starting computer
3.4 Software cannot find PnP modem - usually Dos software
3.5 Windows not holding address for modem after configuration
3.6 Computer video errors or locking after running install program
3.7 Using PnP with QEMM
3.8 Need to install PnP software to a drive other than C:
3.9 If installing with a clean boot.
3.10 Install software believes it is in a DOS Box when it isn't
3.11 Legacy software will not install or gets stuck at one of the
blue screens
4 Other Platforms with PnP Modem Issues
4.1 OS/2 - How to setup a PnP modem
4.2 Linux
4.3 Windows NT
5 ICU
5.1 About the ICU
5.2 Changes made to in ICU or WinICU do not "take"
6 BIOS Compatibility Issues
6.1 Phoenix 4.04
6.2 Award 4.50PG w/1.0 Extension
7 Software Issues
7.1 America Online Recommended init strings
7.2 COMit for Windows
7.2.1 Not able to maintain connections or getting lots of errors
7.3 Doom
7.3.1 Not finding PnP modem
7.3.2 Win-95 DOS won't recognize modem
8 Flash ROM Issues - Only for SupraFaxModem line - NOT EXPRESS MODEMS
8.1 Modem will not accept flash
8.2 How to detect if modem is stuck in flash mode
8.3 What to do if your modem is stuck in Flash Mode
1 Introduction
The letters FAQ stand for Frequently Asked Questions.
modems. This document is designed to address installation and use
issues that go beyond simple installation and configuration. Periodic
updates to this document are posted on Diamond's online services.
If you are unable to find your answers here, please contact
Technical Support by one of the methods below.
World Wide Web site
USA http://www.diamondmm.com
Germany http://www.spea.com
FTP site
USA ftp.supra.com
ftp.diamondmm.com
E-mail
USA intltech@supra.com (English)
Germany GO SPEA on CompuServe
U.K. 100632.1252@compuserve.com
CompuServe Forum
USA GO SUPRA
Germany GO SPEA
Supra Technical Support BBS
USA +1 541 967 2444 (modem)
Germany +49 81 51 266 333 (modem)
+49 81 51 266 334 (ISDN)
U.K. +44 11 89 44 44 15 (modem)
Fax
USA +1 541 967 2401
Fax Back (call with touch tone phone)
USA +1 541 967 0072 (English)
Germany +49 81 51 26 63 32 (German and English)
Voice
Germany +49 81 51 26 63 30 (German)
U.K. +44 11 89 44 44 44 (English)
+44 11 89 44 44 33 (French)
Updates to this file posted on the Supra BBS, WWW site, and
CompuServe forum.
2 Windows 95 PnP Modem Issues
2.1 Modem not configuring properly, not working consistently,
or not being found
Solution: Force reconfiguration of all serial devices.
1)Go to Win-95 Device Manager (select Control Panel; System;
Device Manager).
2)Go to Modem, double-click; remove any modems defined. Go to
Ports, remove any COM ports defined other than a COM port
which the mouse may be using. Go to Other Devices (if that
group appears), remove any modems or unidentified cards
defined. Remove any listing which contains a yellow exclamation
point. When you remove an item, Windows will give a
warning to confirm, click OK when the warning appears.
3)Go to Control Panel and Modems, remove any modems which may
be defined. If you get the "Add New Hardware Wizard", cancel
out and continue to the next step.
4)Shut down Win-95. Turn off the computer.
5)Turn the computer back on, restart Win-95. It should
automatically detect the "new" hardware and reconfigure any
serial devices. If it asks for a driver from the modem
manufacturer, please insert the disk which lists the Win95
modem driver. Let it read the driver from the disk. Do not
run the install from that disk. The modem should configure
properly.
The above may not always work. In some cases Win-95 may fail
to detect enabled COM Ports and assign the modem to a COM Port
which is in use by the system. If that is the case, everything
will look fine in Device Manager but in Control Panel, Modems,
Diagnostics, More Info, it will not communicate with the modem.
If that happens, remove any modem definitions in Device Manager
under either Modem or Other Devices and then from the Start
Menu, choose MS-DOS Prompt and once there do the following:
1)Type "Debug" and press enter. That should provide a dash "-".
2)Type "D40:0L8" and press enter. That will give a bunch
of numbers which will look basically as follows:
0040:0000 F8 03 F8 02 00 00 00 00
The numbers that matter are the ones starting after the four
zeros. To interpret the ports detected, interpret thusly:
Address Port Address Port
F8 03 COM 1 E8 03 COM 3
F8 02 COM 2 E8 02 COM 4
3)When done type "Q" and press enter to return to a DOS prompt
and then type "Exit" to return to Win-95.
4)Go to Control Panel to choose Add New Hardware.
A)Click "Next"
B)Check "No" and click "Next"
C)Select "Ports" and click "Next"
D)Manufacturer is "Standard Port Types" and Model is
"Communications Port" (those are the defaults). Click
"Next"
E)It will display an I/O Range. If the I/O range does not
match what Debug showed, note the address and the click
"Next"
F)Click "Finish"
G)When asks to shut down, select "No"
H)Repeat as necessary
5)If a port in step 4 did not get the proper address, go to
Device Manager, select the port, select resources and
uncheck "Use automatic settings" and change the resources
being used. You may need to change the basic configuration
option selected.
6)Once the appropriate number of ports have been added, shut
down Win-95, turn off the computer, and then restart the
computer. The modem should properly configure.
The above steps having been taken, supposing the modem still
doesn't want to work, the resources may need to be manually
changed by going to Device Manager, Modem, selecting the modem,
going to Resources and unchecking "Use automatic settings".
IRQ's to try are 5, 10, 11, 12 or 15.
IRQ 5 is often used by soundcards. 15 by CD-ROM's or network
cards. 12 by PS/2 style mice. 10 is also often used by a
soundcard. Several different basic configurations may need
to be tested before getting an appropriate configuration.
2.2 Win95 not detecting modem except after a reboot or multiple
reboots
Solution: Please contact Supra Technical Support. Please have
your computer model, BIOS type & version, COM port and IRQ,
and ROM version ready for a quick response.
2.3 Software can't access modem on COM 5
Reason: Software designed for Windows versions prior to
Win-95 may only support COMs 1-4.
Solution: See first issue (2.1) about modem not configured
properly. If, however, there are four COM Ports in the system
or three COM ports and a video card based on the S3 chip set
(which uses the 02E8, COM 4, address), then there is nothing you
can do to avoid having the modem configure to COM 5 other
than having the user disable a COM Port so the modem can
reconfigure properly.
2.4 Need to manually reconfigure modem
Windows 95 provides an interactive Help file which will walk
you through the reconfiguring process. To learn how to modify
a modem's COM port or IRQ, please look up IRQ in the Help file
found in the START menu.
2.5 Need to use keypad for a mouse
In some cases, Windows 95 configured the Modem to the same
COM port or IRQ as the Mouse. To reconfigure the modem as
described in 2.4 above, you will need to maneuver without
the mouse.
Solution #1: Hold down the Control key and then press the Escape
key: this will open the START menu. Use the down arrow key to
move through the START menu, highlight SETTINGS and press ENTER.
This opens up a sub-menu and press ENTER again to select
CONTROL PANEL. Use the arrow keys to highlight ACCESSIBILITY OPTIONS
and then press ENTER. Use the TAB key to maneuver between the tabs
at the top of the window and select MOUSE; press the SPACEBAR once to
choose MouseKeys. Use the TAB key to select the OK button and then
press ENTER. Be sure that the NUM LOCK option is selected on your
keyboard and then use these keys to move the mouse cursor:
Arrow Keys move the cursor
5 = Click
+ = Double-Click
- = Right Mouse Button
/ = Left Mouse Button
You need to tell it which button you are going to click
before "clicking".
Solution #2: Use the Hot Keys to maneuver.
2.6 Getting the SupraExpress 288iPnP modem to work in MS-DOS Mode.
Option#1
1) Make sure that there is a previous version of DOS on the
computer. If this was an upgrade to Windows 95, then there
should still be a DOS directory on the computer (assuming that
it was not deleted).
2) Open Explorer from the start menu under Programs then choose
View, then options. Click "Show All Files". Click the
right mouse button on the MSDOS.SYS file in the root directory
and choose Properties.
3) Uncheck the hidden and read-only boxes. Click on OK.
Double-click on the MSDOS.SYS icon. Open with Notepad.
4) Under [Options] add the line "BootMulti=1" (minus the quotes).
5) Open Explorer again and change the MSDOS.SYS boxes back to
what they were at before. Click OK.
6) Shutdown Windows and turn off the computer. When you see the
words "Starting Windows 95", press the F8 key. Choose "Boot to
previous version of DOS."
7) Install the Plug and Play Utility disk. Choose DOS only
install. When the installation reboots the machine, allow it to
boot directly into Windows 95.
8) Create a shortcut to the DOS based program by clicking the
right mouse button on a blank section of the Windows 95 desktop.
Follow the instructions to create a shortcut to the program.
When the icon is created, click on the icon with the right mouse
button and choose properties.
9) Click on the Program tab. Click on Advanced. Check the MS-DOS
Mode, Warn before starting MS-DOS Mode, and Specify a new MS-DOS
Configuration boxes. In the boxes that are available for
CONFIG.SYS and AUTOEXEC.BAT, enter the following:
CONFIG.SYS
DEVICE=C:\SUPRA\DWCFGMG.SYS
DEVICE=C:\WINDOWS\Himem.Sys
DOS=HIGH,UMB
AUTOEXEC.BAT
SET winbootdir=D:\WINDOWS
SET PROMPT=$p$g
SET PATH=C:\WINDOWS;C:\WINDOWS\COMMAND
10) Click on OK, OK. Now when you double-click on the icon
created, you will be told that the program needs to shutdown
to MS-DOS mode. Click OK. You machine will reboot and use the
CONFIG.SYS and AUTOEXEC.BAT files furnished in the shortcuts
settings. When you exit out of that program, the machine will
reboot back into Windows 95.
If the program used doesn't support higher IRQs then this will not
solve the problem. But there is Plug and Play support installed at
this point, and COMit for Windows DOES WORK for a modem configured
for COM 3, IRQ 5.
Option#2
1)Boot into Safe Mode, Command Prompt only.
2)Using the PnP Utility Disk, install the PnP Utility for DOS only. All
the default answers to the install's questions are fine.
3)The install program will add the DWCFGMG.SYS (DOS driver for the
modem) line to the Win95 CONFIG.SYS file. If it does not, edit the
config.sys and add as the first line "device=c:\supra\dwcfgmg.sys"
(minus the quotes).
4)Reboot the computer, change to the Supra directory (type CD \Supra and
press enter) and then type "WTM" and press enter. Note the I/O address
and Interrupt reported by WTM.
5)Confirm the I/O Address and IRQ do not conflict with any devices in
the system.
The basic PnP software and drivers are loaded at this point. If desired
or if either the I/O address or IRQ needs to be modified, install the
software on the WinICU disk. Again, boot into Safe Mode, Command Prompt
Only and install for DOS only.
3 Windows 3.1x PnP Modem Issues
3.1 DOS Configuration Manager Not Loaded when running Where's The
Modem
Reason: Generally smartdrv is the culprit. If the computer
reboots without smartdrv flushing its buffers, the last
changes the install made will be lost.
Solution: Add lines which are missing in Window's system.ini
file. The System.ini file is found in the \Windows directory.
Working from DOS
1)Make sure you have a DOS prompt and are in the \Windows
directory. Type "CD \Windows" and press enter to go to the
\Windows directory.
2)Edit the system.ini file. Type "Edit system.ini" and press
enter. This will load the file and allow you the opportunity
to edit the file.
3)Press the Alt-S (hold down the Alt key and press the S key).
This provides the Search Menu. Select "Find". For "Find
What", type in "386Enh" and press enter. This should
position you at the line "[386Enh]".
4)Press the "End" key and then press enter. On the new line
type "device=vcmd.386" and press enter. On the next new
line type "device=vcad.386". DO NOT PRESS ENTER after
typing the second line.
5)Press Alt-F (hold down the Alt key and press the F key).
This will open the File menu. Arrow down to Save or press
"S" to save the file. Press Alt-F again and this time
select the Exit option.
6)Start Windows. The modem should be properly recognized
under Windows as well as DOS at this point.
Working from Windows
1)Open Notepad (usually in the accessories group). Select
"File", then "Open". Notepad will ask for a filename and
will probably have " *.txt " in the filename area. Delete
the *.txt and type in "system.ini" and press enter.
2)Select "Search", then "Find". For "Find What", type in
"386Enh" and press enter. This should position you at the
line "[386Enh]".
3)Close the search box and then press the "End" key and then
press enter. On the new line type "device=vcmd.386" and
press enter. On the next new line type "device=vcad.386".
DO NOT PRESS ENTER after typing the second line.
4)Select "File", then "Save" to save the file. Select "File",
then "Exit".
5)Close Windows. Restart Windows. The modem should be
properly recognized under both DOS and Windows at this point.
3.2 NVS error reported when starting computer
Reason: Some PnP BIOS'd machines only have a limited number
of NVS entries for modifying devices. The Legacy software
may not work with the BIOS.
Solution: In some cases the PnP BIOS may be able to be configured
to have the BIOS automatically configure the modem. If it does
not do it without changing the BIOS. They should contact the
computer manufacturer. Otherwise, there is no workaround.
Version 4.50PG of the Award BIOS will detect and configure a Supra
PnP modem. However, it will not tell you where it is configured.
With this BIOS, you will not want to install the PnP Utility disk.
If you already have, please go into the Supra directory in DOS and
type "uninstal y" without the quotes followed by the enter key.
To find where the modem is configured, you can use the "echo"
command from DOS. Type the following lines at your DOS prompt.
The line which produces a modem dialing, is the one which found
the modem.
echo ATXDT555>Com1
echo ATXDT555>Com2
echo ATXDT555>Com3
echo ATXDT555>Com4
Once we know what port the modem is on, we can go to Windows and
find the IRQ for the modem. If the modem was found on COM 1, the
IRQ is likely 4. If the modem is found on COM 2, the IRQ is likely
3. Some other IRQ settings to try are 5,10,11,12, and 15.
IRQ 5 is often used by Soundcards. 15 by CD-ROM's or network
cards. 12 by PS/2 style mice. 10 is also often used by a
soundcard.
To find what IRQ the modem is using. Go into the Main program group
in Windows. Choose Control Panels. Choose the port which the modem
was found. Choose settings/advance and change the IRQ to one of
the suggested IRQs. Restart Windows. Go to the Accessories
program group and run Terminal. Set the port to the correct port.
At the blank screen type AT followed by the enter key. If you get
OK back on the screen, you have found the IRQ. If you do not get
OK, you will want to try another IRQ. Keep this process going
until you find the correct IRQ.
3.3 No ESCD.RF file found when starting computer
Reason: Many PnP BIOS'd machines use an ESCD.RF file to maintain
the PnP setup information. The Legacy install software
checks the address range F000-FFFF for the letters "PnP".
If it finds those letters, it assumes a PnP BIOS. Some
BIOS's may have those letters yet not be an actual PnP BIOS
causing the Legacy install software to not install all
needed files.
Solution #1: If you have Legacy Installation software v2.2 or later,
re-run the installer and when the software shows you the "PNP BIOS
DETECTED" screen, select "YES" to use "LEGACY PNP" instead of
"BIOS PNP".
Solution #2:In the install.dat file there is a line which says at
the end "force partial install". At the *start* of that line
add "//" (minus the quotes). Save the file then rerun the
install. It will prompt as though it is doing a partial
install but will actually do a full install.
In some cases, in order to get it to work properly even after
forcing a full installation, you may need to change the line
in the config.sys from "device=c:\supra\dwcfgmg.sys" to
"device=c:\supra\dwcfgmg.sys /static". Adding that has
worked in several instances where forcing a full install
alone has not worked.
3.4 Software cannot find PnP modem - usually DOS software
Reason 1: The software does not support non-standard IRQ's and the
modem is at a non-standard IRQ. Some DOS software may allow
support IRQ's up to IRQ 7 but not support the upper IRQs.
Solution 1: Either disable a COM Port so the modem can be
configured at a standard address and IRQ or change software
to software which will support non-standard IRQs. To disable
a COM port, you will need to refer to your computer hardware
manual.
Reason 2: Software is looking for an entry in the system table to
confirm the port exists. Since the modem does not get configured
until the system has booted and taken its readings, an entry for
the modem's address will not show up in the system table.
Solution 2:
Option 1) Do a warm boot (Control-Alt-Delete) and it will then
show up as the modem does not lose its settings with
warm boot.
Option 2) Setup a debug file to write the address of the modem
to the system table. Steps are as follows:
1)Use MSD or Debug (D40:0L8) to determine the addresses of the
COM Ports detected without the modem.
To use Debug:
A)Type "Debug" and press enter. That should provide a
dash "-".
B)Type "D40:0L8" and press enter. That will give a bunch
of numbers which will look basically as follows:
0040:0000 F8 03 F8 02 00 00 00 00
The numbers that matter are the ones starting after the four
zeros. To interpret the ports detected, interpret thusly:
Address Port Address Port
F8 03 COM 1 E8 03 COM 3
F8 02 COM 2 E8 02 COM 4
C)When done type "Q" and press enter to return to a DOS
prompt.
2)Create a file in the root directory ( C:\ ) called
"fixcom.deb". You can use Notepad in Windows or
Edit from DOS to create this file. The file should have
four lines - I would recommend having caps lock on for
consistency.
A)The first line should be "E40:0"
B)The second line depends on what ports are detected without
the modem. If COM 1 is detected as either an existing
COM Port or as the PnP modem, start with "F8 03 ". If
COM 2, add "F8 02 " to the line. If COM 3, add "E8 03 " to
the line. If COM 4, add "E8 02 " to the line. For
example, if COM 1 and COM 2 are detected and the modem is
on COM 3, the line should read "F8 03 F8 02 E8 03"
C)The third line is "Q"
D)The last line should be blank
3)Insert in the autoexec.bat "debug < fixcom.deb > nul"
without the quotes. The arrows are required in order for
debug to work properly.
4)Restart the PC.
3.5 Windows not holding address for modem after configuration
Reason: Windows looks at the system table and determines there
are x number of COM ports. If the system table shows COM 1
and COM 3 and the modem is configured for COM 2, under Windows
COM 1 will report properly, COM 2 will show with COM 3's address
although you may have used "Where's the Modem" to tell it to put
the modem at COM 2. The modem does not get configured until
after the system has booted so there is no entry for the modem's
address in the system table.
1)Use MSD or Debug (D40:0L8) to determine the addresses of the
COM Ports detected without the modem.
To use Debug:
A)Type "Debug" and press enter. That should provide a
dash "-".
B)Type "D40:0L8" and press enter. That will give a bunch
of numbers which will look basically as follows:
0040:0000 F8 03 F8 02 00 00 00 00
The numbers that matter are the ones starting after the four
zeros. To interpret the ports detected, interpret thusly:
Address Port Address Port
F8 03 COM 1 E8 03 COM 3
F8 02 COM 2 E8 02 COM 4
C)When done type "Q" and press enter to return to a DOS
prompt.
2)Create a file in the root directory ( C:\ ) called
"fixcom.deb". You can use Notepad in Windows or
Edit from DOS to create this file. The file should have
four lines - I would recommend having caps lock on for
consistency.
A)The first line should be "E40:0"
B)The second line depends on what ports are detected without
the modem. If COM 1 is detected as either an existing
COM Port or as the PnP modem, start with "F8 03 ". If
COM 2, add "F8 02 " to the line. If COM 3, add "E8 03 " to
the line. If COM 4, add "E8 02 " to the line. For
example, if COM 1 and COM 2 are detected and the modem is
on COM 3, the line should read "F8 03 F8 02 E8 03"
C)The third line is "Q"
D)The last line should be blank
3)Insert in the autoexec.bat "debug < fixcom.deb > nul"
without the quotes. The arrows are required in order for
debug to work properly.
4)Restart the PC.
3.6 Computer video errors or locking after running install program
Solution: Go into the CMOS and turn of video shadowing. Once it
is off, remove and reinstall the PnP software. You may or may
not be able to turn it back on after the install is complete.
To Remove the PnP software, go into the Supra directory in DOS and
type "uninstal y" without the quotes and press enter.
3.7 Using PnP with QEMM
When using our PnP modem under DOS or Windows 3.1x, make sure the
first line in your config.sys file shows
"device=c:\supra\dwcfgmg.sys". QEMM often tries to be listed as
the first entry in the config.sys.
3.8 Need to install PnP software to a drive other than C:
This is not a supported feature, however, the following process
should help.
1.Copy CONFIG.SYS to the drive that windows in on, i.e.: F:\
(this is not always necessary)
2.Edit C:\CONFIG.SYS and manually add the SUPRA line,
device=F:\supra\dwcfgmg.sys, on the first line of the
config.sys, it will be needed later on
- ignore the error you get on boot up since SUPRA is not there
as yet.
3.Edit INSTALL.DAT and INSTALL1.DAT on the PnP Utility disk.
Change the windows drive and the boot drive to the windows
drive letter, i.e.: F
4.Change to the drive where the supra directory is to be found
i.e. F:
5.Go through entire install as if drive F was C.
6.When the system reboots the config.sys on C (the real one)
finds the supra directory that is on F.
7.Delete the config.sys off of F: (it was only there for dummy
reasons)
8.If you need to move the modem location and install the WINICU
disk, do the same steps w/drive letters to the INSTALL.DAT
and INSTALL1.DAT on the Win ICU Diagnostic disk as well.
3.9 If installing with a clean boot.
If installing with a clean boot, do not do a full install. Only
install for DOS.
Once the Plug and Play software is installed for DOS, please navigate
to the Supra directory in DOS. Type WTM followed by the enter key.
Note the I/O Address and the IRQ. These are your modems settings.
The I/O addres refers to a COM port number listed below.
I/O Address COM port
03F8 1
02F8 2
03E8 3
02E8 4
Once you know what COM port the modem is configured to, please run
Windows. Navigate to your "Main" program group and double click on
"Control Panels". Choose "Ports" and select the port which the modem
was configured to. Make sure the address and the IRQ are the same. If
not, make the appropriate changes. If these changes do not "stick" to
the COM port in the Control Panels, you may have a situation similar to
section 3.5.
Restart Windows configure each software package to the COM port which
the I/O address corresponds to.
3.10 Install software believes it is in a DOS Box when it isn't
Before running the install, switch to the floppy disk drive
(a: in most cases) once on that drive, you can type install.
DO NOT type A:\install all on one line.
3.11 Legacy software will not install or gets stuck at one of the
blue screens
Option #1 Before you install the software, at a DOS prompt, type
smartdrv /x followed by the enter key. Now follow the instructions
for the install.
Option #2 Either press F5 when the words "Starting MS-DOS" appear
on-screen to bypass the config.sys and autoexec.bat files or
boot from a clean bootable floppy. Rerun the install. See 3.9
for information regarding a clean boot.
A clean bootable floppy is a boot disk without a config.sys or
autoexec.bat file.
4 Other Platforms with PnP Modem Issues - Note: These platforms are
not directly supported. These are suggestions which may or may
not work.
4.1 OS/2 - How to setup a PnP modem
Some users of OS/2 and our PnP modems have reported to us that
by opening a DOS windows upon booting up OS/2 and running the
DWCFGMG.SYS driver for DOS configures the modem and allows the
modem to work. This works if your system is setup for a dual
boot and the modem was originally installed in DOS for DOS only.
We have tested this with mixed results. It seems to depend if
OS/2 can configure the driver stably in memory.
We have heard reports that the next version of OS/2, nicknamed
Merlin, will support PnP.
4.2 Linux - How to setup a PnP modem
Let the driver configure the modem on bootup by adding the DOS
driver, device=F:\supra\dwcfgmg.sys, to config.sys before running
Linux. This requires the use of LOADLIN to load Linux instead
of LILO however.
4.3 Windows NT - How to setup a PnP modem
There are two possibilities.
1) The BIOS automatically detects and configures the modem.
If it configures the modem without a conflict, you are set.
See 3.2 for information regarding the BIOS configuring the modem.
2) Dual-boot into DOS and have the DOS PnP software loaded.
Once the modem is configured, warm boot into NT. It is important
to not reset or cold boot as the modem configuration will be
lost. Use Cnrl-Alt-Del to reboot. This will work in most cases
but not all.
5 ICU
5.1 About the ICU
The ICU is a utility which will allow you to modify a PnP card's
resources. It is designed for DOS and Windows 3.1x. DO NOT USE
WITH WINDOWS 95.
Complete instructions for the use of the ICU are found in the ICU
Users Guide which gets installed in the Supra program group in
Windows. Please read the section regarding modifying a card
card configuration.
The ICU will only work if the PnP software is installed properly.
5.2 Changes made to in ICU or WinICU do not "take"
Reason: The BIOS does not allow modification to its ESCD.RF file.
This is likely only to happen on a few PnP BIOS'd machine.
Solution: None.
6 Bios Compatibility Issues
6.1 Legacy install with Phoenix 4.04 BIOS
1. In the install.dat file on the PnP Utility Disk, there is a line
which says at the end of the line "force partial install". Edit the
install.dat file and at the start of the line which reads
"force partial install", add "//" (minus the quotes). Rerun the
install. It will prompt as though it is doing a partial install but
will actually do a full install.
2. During the process if the installation, one of the most important
files, the ESCD.RF file gets deleted when the install is working with
this BIOS. Go to the \supra\icu directory and undelete that file. To
do this type "cd \supra\icu" (minus the quotes), and press enter and
then type "undelete" (minus the quotes) and press enter. When the
undelete process prompts to undelete the file "?SCD.RF", press "Y" to
undelete and when it prompts for the first letter, type "E".
3. Finally, the ESCD.RF file needs to be copied to the root directory.
To copy the file type "copy escd.rf c:\" (minus the quotes) and press
enter. Reboot the computer and the modem should be detected and
configure properly.
6.2 Award 4.50PG w/1.0 Extension
See 3.2 for NVS error and solution.
7 Software Issues
7.1 America Online Recommended init strings
Init Strings: 1)AT&F2S95=1^M - generally works
2)AT&F2S95=1\N5^M - works even more often
3)AT&F2S95=1\N5*H-C1-K2- works only with modems
which have MNP10
support (SupraFaxModems).
Will not necessarily
work but will work in
some cases where the
other init strings do not.
7.2 Comit for Windows
7.2.1 Not able to maintain connections or getting lots of errors
Reason: Some copies of Comit for Windows did not have an
&F2 in the init string for some 288i modems.
Solution: Add an additional modem init string of AT&F2 and all
should be well.
7.3 Doom
7.3.1 Not finding PnP modem
Reason: Modem using upper IRQs
Solution: Doom will not work at all with the IRQ of the modem
set higher than IRQ7. If it is higher than that then the
system locks up to the point where Ctl+Alt+Del won't work.
This seemed to work in Win95 from a DOS Window and MSDOS 6.22.
Cutting to the chase, Doom works with non-standard IRQ's but
not Extended IRQ's. No IRQ above 7.
7.3.2 Win-95 DOS won't recognize modem
See 2.6 above.
8 Flash ROM Issues - Only for SupraFaxModem line - NOT EXPRESS MODEMS
8.1 Modem will not accept flash
Solution: In some cases the following will resolve the issue:
Go to a terminal program and in terminal mode issue AT_D1234
to the modem. Once you get OK back from the modem, exit the
program, make sure you are in DOS and reflash the modem.
If it does not work, the modem likely needs to be sent in for
repair.
8.2 How to detect if modem is stuck in flash mode
On an external modem, the display is generally blank and the RD
and SD lights are flashing.
On an Internal modem, you may be able to set the port rate to 9600
and get a "flash me" message cycling in a terminal program.
8.3 What to do if your modem is stuck in Flash Mode
Flash it with the latest Flash ROM update.
Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.