Phoenix Technologies Ltd 31 May 1995
2575 McCabe Way
Irvine, CA 92714
714/440-8000
================================================================
PCMPlus release version 3.20
================================================================
------------------------------
WHAT CHANGED FROM PCMPlus 3.11
------------------------------
DPMS.EXE will load many drivers into XMS, rather than EMS, yielding
considerable RAM savings under 1 megabyte. The /RM parameter
turns off the DPMS/XMS feature and forces the drivers to load in
low DOS memory, similar to PCMPlus v3.0. The ability to load
all drivers high, using "DEVICEHIGH=" remains unchanged.
Setup/Install will add this line, either to the [COMMON] section
or under the boot configuration name:
...
DEVICE=C:\PCM320\DPMS.EXE
...
All socket services drivers were changed to "chain" controllers
from different vendors to operate in the same system, for example,
an Intel 365 in a laptop system, with a Cirrus Logic 6720 in the
docking station.
PCMWIN, the PCMPlus Windows utility, was modified to allow adding
cards to the PCMSCD database.
---------
ANOMALIES
---------
Setup/Install places all PCMPlus device drivers into CONFIG.SYS.
Although most drivers have an .EXE filename extension, load all drivers
in CONFIG.SYS, rather than from the DOS prompt or AUTOEXEC.BAT. The
PCMPlus utility executables, however, should be run from the DOS prompt.
All PCMPlus drivers may be loaded into upper memory blocks (UMBs) to
conserve low DOS memory. PCMPlus was loaded into upper memory by 1)
editing the CONFIG.SYS file to manually load the drivers high, 2) using
Quarterdeck's QEMM's configuration utility, and 3) using Microsoft's
MEMMAKER. The first two methods successfully loaded the PCMPlus drivers
high and configured a variety of PCMCIA cards. Microsoft's MEMMAKER,
however, failed to load PCMPlus drivers high.
Some older, out-of-date PCMCIA cards, especially those with non-
standard card information structures (CIS), my cause the DOS error
message "Internal Stack Overflow." (Adaptec EZ-SCSI APA-1460).
Early versions of the Xircom Ethernet+Modem II card will not configure
using PCMPlus, as the card information structure (CIS) may not be comply
with existing standards. Xircom is aware of this issue.
Many modern laptops use a considerable number of resources (system
memory, IRQs, and IO ports), especially for card event interrupts and
ATA IO lines. On some systems (eg. TI 4000M) edit PCM.INI to use this
parameter when using a PCMCIA ATA card (eg. Maxtor, Integral Western
Digital, MiniStor, etc). Other parameters may have been added by
Setup/Install.
...
pcmata=/io=170
...
This parameter option will force all ATA devices to use memory range
0170 to 017F for PCMCIA ATA drive activity.
Another resource conflict can occur with IRQs. When a modem or
fax/modem card is inserted, it normally uses IRQ=3 or IRQ=4, depending
on the options chosen during Setup/Install (see PCM.INI file, and the
"COMORDER=x" option). If another hardware device (eg mouse) is already
using an IRQ (eg 3) and the just-inserted fax card also uses that same
IRQ, both hardware devices will fail, until the conflict is resolved.
Under normal operating conditions,serial, modem, fax/modem and PC cards
should beep twice when inserted, one beep for the card insertion event
and one beep when PCMSCD configures the card. With some modems (eg.
EXP 96/24, ROHM 96/24, TNC 96/24 and Quantas) the first insertion beep
can be heard, but on some laptops, the second beep is silenced by the
PCMCIA card's electronics. PCMPlus, however, has configured the card
and the card recognized by software applications. Use PCM.EXE to verify
that your card is configured.
The number of partitions for flash and ATA PC cards must be equal. For
example, if the user selects two partitions for ATA-style cards, flash
cards will also have two partitions.
* * * *
================================================================
PCMPlus release version 3.11a
================================================================
------------------------------
WHAT CHANGED FROM PCMPlus 3.00
------------------------------
PCMSS.EXE, socket services, supports more PCMCIA silicon,
including Intel (82365 and 82092AA/PPEC), Cirrus Logic (6710,
6720, 6729), Databook (86072), Ricoh, Vadem, OKI (802, Intel-
compatible) and VLSI. Socket services will correctly restore all
controller registers during resume from power management suspend.
The default IRQ varies by controller and is automatically detected
and suggested during PCMPlus SETUP, according to the following
chart:
Bus Suggested
Controller and model Type Card Event IRQ
----------------------------- ---- --------------
Intel 82092/PPEC PCI 15
Cirrus Logic 6729 PPHA PCI 10
Cirrus Logic 6710/6720 ISA 10
Databook TCIC-2N (all) ISA 10
Intel 82356SL (A or B step) ISA 15
Ricoh RF5C266/366 ISA 15
Vadem VG-365/465/468 ISA 15
VLSI Logic 82C146 series ISA 15
PCMCS.EXE complies with PCMCIA specification version 2.10. Card
services function GetConfigurationInfo (04H) accurately returns
all required information including the Valid Client bit in the
Attributes field. With this enhancement, nearly all client
drivers, especially those shipped with PCMCIA LAN cards, will
configure correctly.
PCMCSFUL.EXE is a card services drivers superset which includes
partial PCMCIA Memory Technology Driver (also see PCMMTD.EXE)
support and is required for flash memory cards.
PCMMTD.EXE is a new Memory Technology Driver (MTD) required for
flash, and other, memory cards, and is used with PCMCSFUL.EXE,
PCMFFCS.EXE and Microsoft Flash File system.
PCMATA.SYS with the /SRAM option has a reduced upper memory
requirement. Previous versions of PCMATA /SRAM consumed 16K bytes
of upper memory per socket; this version of PCMATA /SRAM required
a constant 16K bytes, usually at memory address C900, no matter
how many sockets. PCMATA was also enhanced to support the Western
Digital Caviar 40mb card and Integral 100mb/170mb drivers
PCMSETUP.EXE, the installation program, is Plug and Play aware and
will register resources with the Configuration Manager, if
present. OEMs can modify and customize the installation process
by editing PCM.NEW and PCMINST.TXT. PCMSETUP also checks the
EMM386 line in CONFIG.SYS and if NOEMS command line option is
present, PCMSETUP bypasses the EMS menu screen.
PCMVCD.386, a Windows virtual communication driver, is updated to
load and work with Windows for Workgroups v3.11 and Windows v3.11.
DEINSTAL.EXE automatically detects previous socket and card
services from Phoenix and others. Deinstallation will optionally
REMark or remove the installation from CONFIG.SYS, AUTOEXEC.BAT
and Windows files. OEMs can modify and customize DEINSTAL by
editing DEINST.TXT.
[EMS description deleted in v3.20]
PCMFFCS.EXE, a flash file driver, supports additional cards
including Intel, AMD, Mitsubishi, SNI, Fujitsu and others. In
addition to PCMFFCS, flash file system drivers from Microsoft
(MS-FLASH.SYS, etc) are available through Phoenix.
PCMINST.TXT and DEINST.TXT are new ASCII text files similar to
PCM.NEW. They allow OEM customers to modify and customize PCMPlus
installation and deinstallation processes, without access
to source code, by using a text editor. Consult the PCMPlus
Technical Reference Manual for line-by-line customization details.
Spanish, German, French, Italian and Swedish language versions
of the PCMPlus executable files are available. The printed
user manuals and Japanese language versions are expected 2Q95.
The 148 page PCMPlus Technical Reference Manual is available in
English and includes topics such as customizing PCM.INI and
PCMINST.TXT/DEINST.TXT, Power Management, ROM bootability,
Writing a Client Driver, Advanced Troubleshooting and other
topics.
---------------------
WHAT REMAINS THE SAME
---------------------
1. The "look and feel," especially from an end user perspective,
remains virtually identical.
2. PCMSSxx.EXE (Intel 365, Cirrus Logic 67x0, and others),
PCMSCD.EXE, PCMWARN, PCMINFO.EXE, PCMWIN.EXE remain unchanged from
PCMPlus 3.0.
---------
ANOMALIES
---------
1. With write-protection enabled on memory cards, including SRAM,
the PCM.EXE tool displays "Status: Unconfigured" or "Status: Write
Protected." This is not an error, as it accurately reflect the
card's status. To display card information, disable its
write-protection.
2. Some SCSI cards (Adaptec and I/O Magic) may cause an "internal
stack overflow" error.
3. Some Xircom multi-function cards (LAN & modem) may need the
PCMCSFUL.EXE, instead of the default PCMCS.EXE. This is a
software work-around for a hardware timing issue.
4. Windows for Worgroups v3.11 on some hardware platforms may
need the following SYSTEM.INI parameter inserted under the
[386Enh] section:
[386Enh]
...
PCMCIATIMER=FALSE
...
This option may increase card recognition time under Windows v3.11,
but it corrects some hardware timing issues, especially if Windows
v3.11 fails to load or intermitantly returns to the DOS prompt.
.end
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.