CardWizard(TM) for Windows(R) NT 2.00.07 readme file
February 13, 1997
CardWizard for Windows NT installation diskette
Disk contents:
Readme.Txt --- this file
WizNt.z --- compressed file of drivers, DLL's and wizard
Devices.z --- compressed file of serial and ATA drivers
Sockets.z --- compressed file of socket services
_Setup.lib --- library of bitmaps and utility EXE's
_Inst32i.Ex_ --- compressed Install Shield component
Setup.exe --- Install Shield executable
Setup.Ins --- Install Shield component
Setup.pkg --- Install Shield component
_Setup.Dll --- Install Shield component
Cwksoem.ini --- Install Shield installation options lists.
PCCard.ini --- PCCard (Card Services) registry init file.
SSIntel.ini --- I365 compatible controller registry init file.
SSTI1130.ini --- TI1130 controller registry init file.
SSCL67xx.ini --- Cirrus 6729/6730 controller registry init file.
SSCL6832.ini --- Cirrus 6832 controller registry init file.
SSTI1131.ini --- TI1131 controller registry init file.
SSTcic.ini --- DB68082/DB68072 controller registry init file.
SSVadem.ini --- Vadem 365/465/468/469 controller registry init file.
Resman.ini --- Resource Manager registry init file.
Scsi.sft --- support file for SCSI devices
Devapps1.inf --- INF installation file
TO INSTALL CARDWIZARD FOR WINDOWS NT:
-------------------------------------
The installation and un-installation procedures for CardWizard and for the
combined CardWizard/PowerProfiler products are covered in the manual,
"CardWizard for Windows NT, User Guide".
This release of CardWizard for Windows NT requires, "Windows NT version 4.0
Golden", or greater.
This release of CardWizard is designed to work with the, "SystemSoft,
PowerProfiler for Windows NT", power management system. The version
of PowerProfiler must be 2.10.03 or greater.
Warning! CardWizard for Windows NT cannot be installed/uninstalled properly
if a previous version of CardWizard is active on the machine. If the
machine already contains a copy of CardWizard, make sure that the WizNt.Exe
program is not running and that there are no cards in the PCCard slots
before running the Setup program.
TO CUSTOMIZE PLATFORM SETTINGS:
-------------------------------
Many of the CardWizard's parameters are stored in the Windows NT registry
by the Setup program. Some of these entries can be modified to customize
the CardWizard configuration. Note, after changing the registry, the
machine must be rebooted in order for the customizations to take effect.
The following items can be customized:
- The IRQ mask for possible functional interrupts from the PC Card
card(s) can be changed.
- The address and length of a block of memory can be specified for
memory window usage.
There are three basic methods to customize platform settings:
1. Edit the registry, using regedt32 or regedit.
2. Edit the socket services INI file (as appropriate for the machine)
on the installation diskette, then run the Setup program.
3. Edit the CWKSOEM.INI on the installation diskette, then run the Setup
program.
Method one is recommended (editing the registry) for experimenting with
settings on a single machine. Methods two and three (editing the .INI files)
is recommended for changing the settings on many machines or for customizing
an installation disk for a particular brand of machine.
The socket service parameters that are available for customization can be
found in the registry with the key of:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services
\%SocketService%\Parameters
Note: %SocketService% should be substituted with the name of the socket
service which is installed on your platform. For Intel 365
compatible controllers, this would be SSIntel.
The following parameters in this area of the registry can be changed to
customize on your platform:
Functional IRQ High Mask
WindowAddress
WindowLength
Other parameters in the socket services trees must not be changed!
Examples of customizations which can be done:
1) Avoiding "hidden" usage of IRQ's.
On some systems, peripherals which get configured by the BIOS
use IRQs but don't inform the Windows NT HAL about this usage.
This is particularly true of Plug and Play peripherals, because
Windows NT does not (yet) support Plug and Play.
To keep CardWizard from trying to use these IRQ's, you must change the
"Functional IRQ High Mask". This mask indicates which IRQ's can be
used by CardWizard, with each bit corresponding to an IRQ. A value of
"1" in a bit position indicates that the IRQ can be used and a value of
0 indicates the IRQ cannot be used. The default value for this mask is
"0xDEB8", which includes the IRQ's supported by the I365 controller and
compatible controllers.
For example, if a system contains a sound card which uses IRQ 4. The
user should change the mask from 0xDEB8 to 0xDEA8 to disallow IRQ 4.
2) The size and location of a block address space may be specified by
the "WindowAddress" and "WindowLength" parameters in the socket services
entry in the registry. If this space cannot be obtained through the
HAL the default algorithm for address space will be used. By default,
available system address space is determined by queries to the HAL
starting in the 0xD8000 region. If no address space is available below
the 1MB boundary, address space is scanned starting at the 16MB
boundary moving downward.
3) CWKSOEM.INI can be modified so that the Setup program automatically
installs the correct Socket Services driver for the target platform.
With this modification the user will not see the Socket Services
selection screen, and will not be notified of the selected driver. To
modify the installation program the manufacturer needs to edit the
CWKSOEM.INI file as follows:
Under the header [SocketServices], delete all entries except for
the one which will become the default. Modify the entries SSn
label so that it is SS1.
For example, on a platform which contains the TI1130 chip, the
[SocketServices] section will read as follows:
[SocketServices]
SS1=SSTI1130
4) The SSTCIC.Sys Socket Service driver does not appear in the [SocketServices]
list in CWKSOEM.INI. This is to prevent the inadvertent installation of the
driver on a machine which does not have the appropriate controller.
Manufacturers that ship machines with the TCIC controller must add the TCIC
driver to the [SocketServices] list. Note, all manufacturers should modify
the [SocketServices] list so that only appropriate drivers are offered to
users running the Setup program.
5) CWKSOEM.INI contains a parameter called FirstSlotOnBottom. This parameter
specifies the default order of the PCCard slots. When CardWizard is
first executed it will determine the slot positions (which slot is on top
and which one is on bottom) from this parameter. It is a flag that can
hold the value 0 or 1. If the order is incorrect, on a given machine, the
PC manufacturer should toggle the value of this flag to reverse it.
6) CWKSOEM.INI contains a parameter called FirstSlotNumber. This parameter
specifies the numeric ID of the first slot. It can be 0 or 1. If it is 0,
the slots will be numbered 0 and 1. If it is 1, the slots will be numbered
1 and 2. The PC manufacturer should use this variable to specify the
number scheme when configuring the machine.
7) PC manufacturers can add SlotName parameters to the CWKSOEM.INI file to
specify default names for the PCCard slots. For example, adding the
following statements to the [Defaults] section will result in a system in
which the slots are named, "Top", and, "Bottom".
SlotName0=Top
SlotName1=Bottom
NETWORK CARD CONFIGURATION:
Some network cards require the use of memory windows. The location of
the windows are specified during the network adapter setup. The
address(es) specified must not conflict with the windows in use by
other drivers. To determine which windows are already in use,
run the, "Windows NT Diagnostics", program (which can be found
from the Start menu under "Programs/Administrative Tools"). Click
on the "Resources" tab, then push the "Memory" button at the
bottom of the tab. If a network card is configured with a conflicting
set of resources, the Wizard will notify the user and allow the user
to go to the network control panel applet to change the parameters for
the driver. For further details refer to the, "Card Wizard for
Windows NT Quick Reference Guide".
The PCCard driver uses a memory window at D8000 by default, although
this may be modified by changing the installation (see above).
When a LAN card is first inserted into a system, the Windows NT network
Setup program will be executed. The Setup program requires the user to
select the bus that the LAN card is installed on. The user must be sure
to select the PCMCIA bus. If the wrong bus is selected the LAN card will
not function. Also, the system may trap and present a blue screen of
diagnostic information. Note, that the Setup program offers the ISA bus
as the default.
ANOMALIES:
----------
1) If a PC Card network adapter is installed, and the machine is rebooted
with the card removed from the system or disconnected from the
network, the Service Control Manager may display the following error
message, "At least one service or driver failed during system
startup...". This is caused by limitations in the Windows NT operating
system.
It is safe to ignore this message.
2) If you install a SCSI card, then later remove it, you will receive a
Service Control Manager error message that "At least one service or
driver failed during system startup..." This is caused by limitations
in the Windows NT operating system.
It is safe to ignore this message. To keep this message from recurring,
you must disable the driver for the SCSI card, or you must make
sure the SCSI card is plugged in when you boot your system.
3) PC Card support (from both SystemSoft and Microsoft) may not work
on some platforms which have a Plug and Play (PnP) BIOS because
the BIOS assumes that the operating system will handle setup
issues which are not handled by Windows NT. If PC Card support
does not work on your platform, you might be able to instruct
the BIOS to disable PnP features; the details of how this is
done vary from one platform to the next. Typically this can be
done in the BIOS setup. For example, some setups have a setting
something like:
Plug & Play O/S: [Yes]
Set this to [No] to disable PnP BIOS features.
4) If a PC Card is inserted but does not reset within ten seconds, a
"card removal" event will be reported. This can happen with some
(old) cards which appear to be 3.3 volt cards but which are actually
5 volt cards.
5) The network portion of some Megahertz Ethernet+Modem combo cards
does not work with controllers and adapters in which +5V is hard
wired to the sockets; this includes some older SCM MicroSystems Inc.
Card Readers which use the Vadem 365/465 controller. SystemSoft
is working closely with Megahertz to resolve this issue.
6) Network+modem combo cards which are installed in your system, but
which do not follow the Microsoft specification for such cards, can
interfere with the operation of CardWizard for Windows NT even if
the cards are not plugged in to your system. For example, if the
Olicom GoCard ET/Modem 288 is installed, it will prevent the modem
portion of other network+modem cards from working properly. Be
sure to de-install such cards from your system if you are not
using them.
7) Some combinations of SCSI controllers and SCSI devices do not work together.
The reason is that the SCSI specification does not specify which device,
the SCSI controller or the SCSI device, is required to supply termination
power. If neither device supplies the power, unusual behavior will result.
For example, a CD ROM drive may have many or no drives mapped to it. This
problem can be fixed with an Active Termination Device which can be obtained
from several manufacturers. The most popular example of a SCSI controller
which does not supply termination power is the NewMedia Bus Toaster. The
Bus Toaster has to be used with SCSI devices that provide termination
power or with an Active Termination Device.
8) ATA Disk cards must be stopped, using the Stop Card feature, before they
are removed them from the system. Failure to do so can result in
unpredictable system behavior and/or loss of data.
9) If you use multiple ATA cards in your system, the Windows Explorer or the
"My Computer" window may continue to display the drive letters for some
of the disks after the cards have been removed. This is caused by a
limitation of Windows NT. The presence of these drive letters will not
affect the operation of your system.
10) If you use multiple ATA cards in your system, the Disk Administrator
may display partition information for cards which have been removed.
This is caused by a limitation of Windows NT. If you remove all ATA
cards from your system, these "ghost" partitions will disappear.
11) When CardWizard is installed on machines which have CL6722 PC Card
adapters the user should select the SSIntel Socket Services driver and
not the CL67XX driver. Warning, while the CL6722 controller supports
3.3 volt cards, the SSIntel.Sys driver only supports 5 volt cards.
Do not insert a 3.3 volt card into a machine with a CL6722 adapter.
The card may be damaged.
12) The SSCL6832.Sys driver does not support 3.3 volt cards in this release.
Do not insert a 3.3 volt card into a machine which is using this driver.
The card may be damaged.
13) The following cards have been added to the CardWizard for Windows NT
supported card list. However, users may have to obtain the latest drivers
from the card manufacturers.
o Xircom Ethernet+Modem 28.8
o Ositech Jack of Diamonds
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.