CardBus FireWire Enabler for DOS

CardBus FireWire Enabler
for DOS
Copyright © APSoft, 2004 - 2005
APSoft
Copyright Notice and Disclaimer
Unless otherwise noted, this document and the information herein disclosed are proprietary to APSoft.
Any person or entity to whom this document is furnished or who otherwise has possession thereof, by
acceptance agrees that it will not be copied or reproduced in whole or in part, nor used in any manner
except to meet the purposes for which it was delivered.
The information in this document is subject to change without notice, and should not be considered as a
commitment by APSoft. Although APSoft will make every effort to inform users of substantive errors,
APSoft disclaims all liability for any loss or damage resulting from the use of this document or any
hardware or software described herein, including without limitation contingent, special, or incidental
liability.
Copyright © 2004 - 2005 APSoft. All rights reserved.
Issue date 14-Aug-2005.
CardBus FireWire Enabler for DOS
CardWare and the APSoft logo are registered trademarks of APSoft.
All other products and brand names are trademarks and registered trademarks of their
respective companies.
APSoft.
Siemensstrasse 1b
84405 Dorfen
Germany
ii
Tel:
Fax:
Internet:
+49 (0) 8081 955 89 0
+49 (0) 8081 955 89 11
http://www.tssc.de
CardBus FireWire Enabler for DOS
APSoft
Table of Contents
Introduction........................................................................................................ v
Features and Limitations............................................................................ v
Installation.......................................................................................................... 7
Deployment.................................................................................................. 7
Example of config.sys........................................................................................................... 8
Fine-tuning .................................................................................................. 8
Resource management. .................................................................................... 9
Command Line Options. ................................................................................. 11
Common Command Line Options ........................................................... 11
Resource Management............................................................................. 11
Diagnostics and Fine-tuning.................................................................... 12
ASPI Management..................................................................................... 14
Unloading .................................................................................................. 14
Initialization File............................................................................................... 15
PCI Sections .............................................................................................. 15
MemFilter, PreFilter, MemFilter0, MemFilter1 .................................................................... 16
IoFilter, IoFilter0, IoFilter1................................................................................................... 16
IRQ ..................................................................................................................................... 16
ISAEnable........................................................................................................................... 16
VGAEnable ......................................................................................................................... 17
ExCABase .......................................................................................................................... 17
LegacyBase ........................................................................................................................ 17
PrimaryBus, SecondaryBus, SubordinateBus .................................................................... 17
SkipSocket.......................................................................................................................... 17
IgnoreBridge ....................................................................................................................... 17
BARMask............................................................................................................................ 16
BAR0 - BAR6...................................................................................................................... 18
SkipAdapter ........................................................................................................................ 18
Resources Section.................................................................................... 18
Additional information .................................................................................... 21
How to get Technical Support for CardBus FireWire Enabler .............. 21
CardBus FireWire Enabler for DOS
iii
APSoft
Example of INI file ..................................................................................... 22
iv
CardBus FireWire Enabler for DOS
APSoft
Introduction
This manual provides an overview of the CardBus FireWire Enabler for DOS.
All released versions are collectively named “CardBus FireWire Enabler” or
simple “Enabler” throughout this manual
Enabler is a small, but powerful driver for quickly enable CardBus FireWire
Adapter such as Adaptec AFW-1430 FireWire/CardBus adapter, Orange Micro
Inc. OrangeLink FireWire for Notebooks, etc.
Due to the small memory footprint of the resident part the enabler is an ideal
solution for use in various disk-cloning schemes. Both, Symantec Norton Ghost
and Power Quest Disk Copy, are supported.
Features and Limitations
Enabler supports both, original DOS (e.g. MS-DOS 6.22) as well as DOS
included with Windows 95/98. Resident part of CardBus FireWire Enabler
occupies approximately 1 kB of memory or larger, depend from used features.
Enabler can be loaded via CONFIG.SYS, AUTOEXEC.BAT, or simply started
from DOS command prompt.
Enabler can be unloaded, except if it is loaded from CONFIG.SYS. Besides
Enabler prevents second load of itself.
Enabler may provide support of FireWire CardBus Cards without load
SBP2ASPI driver for DOS.
Enabler may provide support of FireWire devices without load additional driver
for your device (e.g. ASPICD.SYS for CD-ROM device).
Enabler does not provide support of audio CD disks for FireWire CD-ROM
devices without load additional driver for your device.
Enabler may provide full LBA support for disks of any size. Large disks are
supported.
Enabler may provide full INT 13h support, including extension. Most utilities
(FORMAT.COM, FDISK.EXE, Norton Utilities, etc.) are supported.
CardBus FireWire Enabler for DOS
v
APSoft
User may freely assign drive letters to partitions, except if Enabler is loaded
from CONFIG.SYS. Number of supported partitions is limited only by number
of available drive letters.
Enabler does not provide hot-swap support. The FireWire CardBus Card should
be connected to the computer before Enabler is started.
Enabler cannot be loaded in the Windows DOS session.
Enabler provides a set of flexible configuration options via command line or
external .INI file.
In case a CardBus adapter is not properly initialized by BIOS, Enabler is able to
update the CardBus adapter configuration. Most of the required initialization
can be done automatically without user intervention. However, if required, user
will be able to control most settings, either via command line parameters or, in
complicate cases, via external .INI file
vi
CardBus FireWire Enabler for DOS
C
H
A
P
T
E
R
1
Installation
The Enabler may be installed either in CONFIG.SYS, AUTOEXEC.BAT or
started from DOS command line. It’s possible to relocate enabler into upper
memory using DEVICEHIGH or INSTALLHIGH statements in CONFIG.SYS.
The Enabler provides several command line switches allowing fine-tuning of the
driver. In more complicate cases you may create an initialization file with very
detailed configuration instructions.
It is recommended that you fine-tune CardBus Enabler switches starting
CardBus Enabler from the command line. After switches are set, you can place
call of CardBus Enabler either to CONFIG.SYS or to AUTOEXEC.BAT.
Deployment
CardBus FireWire Enabler is able provide support of FireWire cards and
devices without loading any additional drivers.
For use CD-ROM you will also need to load MSCDEX.EXE in your
AUTOEXEC.BAT.
CardBus FireWire Enabler may allocate the required memory automatically (see
“Resource Management” chapter for details).
To be available inside of 1st MB (required if SBP2ASPI driver is used) memory
should not be shadowed by BIOS and should be excluded from memory
management by EMM386.EXE.
If CardBus FireWire Enabler provides support of FireWire cards without
SBP2ASPI driver then there is no need to allocate memory below the 1st MB
(memory anywhere in 4GB address space may be used).
CardBus FireWire Enabler for DOS
7
APSoft
Example of
config.sys
You can invoke CardBus FireWire Enabler in the any point. For example:
SWITCHES
BUFFERS
FILES
BREAK
FCBS
LASTDRIVE
STACKS
DEVICE
DEVICE
DOS
DEVICE
=
=
=
=
=
=
=
=
=
=
=
/F
10,0
99
ON
16,8
Z
9,512
\dos\himem.sys /testmem:off
\dos\emm386.exe noems
HIGH,UMB
\FWENAB.EXE
Fine-tuning
If your BIOS configure CardBus Adapter properly, no command line parameters
are necessary. Otherwise fine-tuning could be required.
The fine-tuning could be performed either in standard installation mode via
command line options, or in advanced installation mode via an external INI file.
Following chapters describe both modes in detail.
In both modes several optional parameters require a numeric value. Any
numeric value could be entered as decimal (default form) or hexadecimal (with
0x prefix) number. For example: /PI:10 and /PI:0x0A both specify IRQ 10.
In both modes several optional parameters require <use> values. Use values
may typically be specified as ON, OFF or AUTO in upper or lower case.
8
CardBus FireWire Enabler for DOS
C
H
A
P
T
E
R
2
Resource management.
During the loading Enabler collects information about resources (IRQ, I/O and
memory) used by PCI, PNP and Option ROMs. Enabler considers such
resources as non-free and excludes them from hardware configuration
procedure.
In non-PnP computer Enabler may be not able detect all used resources (e.g.
resources used by Legacy ISA devices). In such case you can adjust resource
filters manually by adding such resources into [Resource] section of the external
.INI file. The list of all detected resources is displayed if Enabler is started with
/V+ switch.
Algorithm of resource management is as follow:
CardBus FireWire Enabler for DOS
1.
Collect PCI, PnP and Option ROM resource information.
2.
Result is combined with resource information in [Resources] section
of .INI file (if file and section exist).
3.
Resulting resources collection is used as resource filter.
4.
Resource assignment via external .INI file (e.g. bridge filter settings
or ExCA address register) overrides assigned resources
unconditionally, even if specified resource is unavailable. If resource
is unavailable and Enabler is started in verbose mode (with /V
switch) - a warning is issued.
5.
If specific resource is assigned by BIOS, Enabler keeps such
resource (unless otherwise is directed by .INI file).
6.
If specific resource is not assigned by BIOS and there is no .INI file
settings, Enabler will allocate required resource automatically:
a)
Command line settings specify preferable resources to be
used if available.
b)
If preferable resources are not available or if no
preferable resources specified via command line, any
available (according to filters set during the loading)
resource will be used.
9
APSoft
Note: For I/O and memory pools Enabler use preferable resource
from bottom up (in other words, minimal possible address is used
first).
Intel 16-bit PCIC compatible (non-CardBus) PC Card adapters are limited by
using memory inside of 1st MB. PCI and CardBus adapters may use memory
anywhere in 4GB address space.
10
CardBus FireWire Enabler for DOS
C
H
A
P
T
E
R
3
Command Line Options.
Command line options can be specified in any order, either in upper case or in
lower case. Typical parameters start with slash (/) or dash (-) followed by one or
two letters (e.g. /H or /VR).
Some command line options require an additional value. In this case parameters
should be followed by colon (:) or equal (=) then value (e.g. /M:0xEC000).
Command line options are separated by spaces.
Common Command Line Options
Following options are common for all versions of CardBus FireWire Enablers.
/H | ?
/E
Print online help
Silent mode: No display output.
Resource Management
/PI:n
/M:n
/IO:n
CardBus FireWire Enabler for DOS
PCI Interrupt level
(Default: 0x0B)
Start address of memory pool
(Default: 0xD0000)
Start address of I/O pool
(Default: 0x340)
11
APSoft
Diagnostics and Fine-tuning
/F=filename
Specifies the initialization file pathname.
By default the initialization file has the same name as the Enabler, but with
extension .INI (i.e., FWENAB.INI). Enabler will be looking for the .INI file in
the same subdirectory where enabler itself is located.
Using /F parameter user may override path and name of the default
initialization file. (E.g., /F:E:\Settings\fwenab.ini)
/V[:<file>]
Verbose mode: Configuration steps will be outlined on console or to file (if
file pathname is specified).
/FL
Flush log file to disk immediately after each update (may be useful in case of
system hang).
/ID
Displays identified drive information.
/Ln:Letter
Specifies the drive letter assigned to partition 'n', where n could be in range of
0 to 9 (E.g. /L0:M /L1:K /L2:Z.)
Drive letters selected by the user can only be taken into account if the Enabler
is loaded in TSR mode (e.g., from AUTOEXEC.BAT or command line), and
will be ignored if the device driver is loaded from CONFIG.SYS.
User may assign more than 10 drive letters using the .INI file.
/DOSONLY
By default, Enabler assigns drive letters to all found drive partitions regardless
the file system. This mode allows e.g. reformat unrecognized file system to
one supported by DOS.
If /DOSONLY switch is added to the command line, the drive letters will be
assigned only to partitions with file system recognized by DOS (FAT12 &
FAT16 under DOS 6.x and FAT12, FAT16 & FAT32 under DOS.
Use this mode if you plan to install third-party file system driver for non-DOS
partitions. For example, Symantec Norton Ghost 8.x contains a built-in NTFS
driver allowing backup/restore operation to/from NTFS drive under DOS.
12
CardBus FireWire Enabler for DOS
APSoft
/IB:B:D:F,
<use>
Ignore PCI-2-PCI bridge. This switch may be used for subtractive-decode
PCI-2-PCI bridges (bridges which pass all memory and I/O requests behind).
B - bus (0-255), D - device (0-31), F - function (0-7).
ON
OFF
AUTO
Bridge is ignored (i.e. bridge is subtractive).
Bridge is not ignored (even if physically subtractive).
Bridge’s decoding mode should be read out of bridge
/FI
Force updating of PCI IRQ routing table for socket (even if selected IRQ is
already in table.
/BS
Performs PCI bus scan and termination. Information will be displayed on
console
/EC:<use>
ON
OFF
Use external power switch clock for adapter.
Use power switch clock generated by PCI clock
Note: This switch is ignored for all PC Card adapters except Texas
Instruments PCI121x/122x and TI PCI125x/14xx/44xx families.
/IM:m
/MX:<use>
Set interrupt mode. Possible values are:
Par
TI1130/1x31:
TI12xx/14xx/44xx:
CL-6832, OZ6832:
Ricoh RB5C478:
use parallel ISA-type interrupts
use parallel ISA and PCI interrupts
use External-Hardware Interrupt mode
use parallel interrupt mode
Ser
TI1130/1x31:
TI12xx/14xx/44xx:
CL-6832, OZ6832:
Ricoh RB5C478:
use serialized interrupt type scheme
use serialized ISA and PCI interrupts
use PC/PCI Serial Interrupt protocol
use serialized interrupt mode
PPci
TI 12xx/14xx/44xx, Cl-6832, OZ6832: use parallel PCI interrupts
only
ISPP
TI 12xx/14xx/44xx only: use serialized ISA and parallel PCI
interrupts. Will be ignored for all other adapters.
Pway
CL-6832, OZ6832: use PCI/Way Interrupt Signaling mode. Will
be ignored for all other adapters
Initialize the multiplex IRQ routing register. This switch is only used on TI
PCI122x/125x/14xx/44xx adapters and is ignored for all other adapters.
/OZ:97:<use>
O2Micro PC Card adapter only: set/reset PC97 IRQ bit
/OZ:IL:<use>
O2Micro PC Card adapter only: set/reset ISA Legacy bit
/TC:n
CardBus FireWire Enabler for DOS
Maximal time in sec waiting for device connect signal after bus reset (Value 1
- 60, Default 10 sec)
13
APSoft
ASPI Management
/NA
Skip ASPI initialization.
In this case Adaptec ASPI manager and driver for your device is required.
/NU
/I
Do not move part of resident code to upper memory.
Ignore (do not install) INT 13 interface support for ASPI hard disk devices.
Also no drive letter will be created.
In this case driver for your device is required.
/IC
Ignore (do not install) support for ASPI CD-ROM disk devices.
In this case driver for your device is required.
/D:devname
Specifies device name of CD-ROM driver
(Default: ASPICD01)
Can be used by MSCDEX.EXE to support ASPI CD-ROM disk devices.
Unloading
/UL
14
Unload resident part (not supported, if driver is loaded via config.sys)
CardBus FireWire Enabler for DOS
C
H
A
P
T
E
R
4
Initialization File
The initialization file is a text file that contains special settings. These settings
allow you to configure computer hardware components so your CardBus
adapters and/or FireWire CardBus card become functional.
Any text in the .INI file starting after the semicolon (;) to end of the line, is
interpreted as a comment.
Using the INI file you may set PCI-2-PCI Bridges, CardBus bridges and
FireWire CardBus card parameters in any combination.
PCI Sections
PCI Section describes PCI Device. Enabler supports any number of PCI
Sections in the .INI file.
All section names are relative to original PCI subsystem configuration. You can
see that configuration if you switch program to verbose mode. (/V key) or use
the /BS switch.
In order to specify the required configuration of the PCI device, you need to
know the location of the device. This location is specified in
Bus:Device:Function form. Location 0:A:1 describes the first function of PCI
device number 10 (“A” in hexadecimal format) located on PCI bus 0.
Initialization file section used for the configuration of such a device should have
the name [0:A:1].
Value names depend on device type.
For CardBus adapters, following values are defined: 'IoFilter0', 'IoFilter1',
'MemFilter0', 'MemFilter1', ‘ExCABase', 'LegacyBase', ‘IRQ’, ‘ISAEnable’,
‘VGAEnable’, ‘VGAEnable’, ‘SkipSocket’.
For PCI-to-PCI bridges, following values are defined: 'IoFilter', 'MemFilter',
'PreFilter', and ‘IRQ’, ‘ISAEnable’, ‘VGAEnable’, ‘IgnoreBridge’.
For CardBus cards, following values are defined: ‘IRQ’, ‘BARMask’, ‘BAR0’,
‘BAR1’, ‘BAR2’, ‘BAR3’, ‘BAR4’, ‘BAR5’, ‘BAR6’, ‘SkipAdapter’.
CardBus FireWire Enabler for DOS
15
APSoft
These parameters define the CardBus or PCI-to-PCI bridge memory filter base
and limit (or size) both memory filters (prefetcheable and non-prefetcheable).
MemFilter,
PreFilter,
MemFilter0,
MemFilter1
The CardBus base and size values should have 4K alignments according to
Yenta specification and limit (maximum address) should be aligned to 4K minus
one.
Following formats could be used to specify bridge memory filter ranges:
BaseAddress:Limit. This means that we define the first and exactly the last
integer number in a range (e.g., 0xA0000000:0xA0000FFF specifies 4K
ranges). If you wish to disable positive decoding of PCI-to-PCI bridge's filter
range, please specify something like: 200000:1fffff.
If you prefer to specify filter size rather than filter max address you should use
BaseAddress,Size format, where Size by default is a literal decimal number. In
this case you also could use 'M' or 'K' postfixes (e.g., 0xA0000000,1M specifies
1M memory filter starting at 0xA0000000 address).
Attention! All values are treated as hexadecimal even if there is no “0x” prefix.
Examples:
MemFilter0=A0000000h:A0000fffh
MemFilter0=A0000000h,4K
MemFilter0=A1000000h:A1001fffh,Pre
MemFilter0=A1000000h,8K,Pre
IoFilter,
IoFilter0,
IoFilter1
ISAEnable
memory range
memory range
pref. memory
pref. memory
This is the bridge I/O range base and limit (or size). For CardBus base and size
values must have double-word alignment.
Examples:
IoFilter = 0xD000:0xD00F
IRQ
4K
4K
8K
8K
16-bytes I/O range
CardBus interrupt line settings. According to PC/AT architecture this value
must not exceed 15.
IRQ = 10
10th interrupt
IRQ = 10
10th interrupt
Control setting of ISA Enable bit in Bridge Control Register. Valid values are 0
and 1.
Example:
ISAEnabe = 1
16
Set ISA Enable bit
CardBus FireWire Enabler for DOS
APSoft
VGAEnable
Control setting of VGA Enable bit in Bridge Control Register. Valid values are
0 and 1.
Example:
VGAEnabe = 0
ExCABase
Reset VGAEnabl bit
This option is used to mountain CardBus socket register/ExCA registers base
address register. Available values: any 32-bit hexadecimal number aligned to 4K
boundaries.
Example:
ExCABase = D8000000h
LegacyBase
This is PC Card 16-Bit IF legacy mode base address. Available values: any 16bit hexadecimal number aligned to double-word boundary.
Example:
LegacyBase = 3e0h
PrimaryBus,
SecondaryBus,
SubordinateBus
These options control bus number assignments for PCI-to-PCI and CardBus
bridges. Available values: any decimal number not greater than 255.
Example:
[0:A:0]
PrimaryBus
SecondaryBus
SubordinateBus
TI PCI1131 socket
= 0
= 1
= 3
Set sec. bus to 1
Set sub. bus to 3
; Now socket 0 of TI PCI1131 CardBus adapter accepts
; I/O requests to buses from 1 to 3 inclusive
[0:A:1]
PrimaryBus
SecondaryBus
SubordinateBus
SkipSocket
TI PCI1131 socket
= 0
= 4
= 3
Set sec. bus to 4
Set sub. bus to 3
Allows skip (ignore) particular CardBus socket . Valid values are 0 and 1
Example:
SkipSocket = 1
IgnoreBridge
CardBus FireWire Enabler for DOS
Skip socket
Allows ignore PCI-2-PCI bridge. This option may be used for subtractivedecode PCI-2-PCI bridges (bridges which pass all memory and I/O requests
behind). Valid values are ON, OFF and AUTO. ‘ON’ means that bridge is
ignored (i.e. bridge is subtractive). ‘OFF’ means that bridge is not ignored (even
17
APSoft
if physically subtractive). ‘AUTO’ means that bridge’s decoding mode should
be read out of bridge.
Example:
IgnoreBridge = ON
BARMask
Ignore bridge
This option allows specifying mask of BARs that will be initialized by enabler.
If bit in the mask is set, the Enabler will initialize corresponding BAR. If bit is
reset, Enabler will ignore corresponding BAR.
Example:
BARMask
BAR0 - BAR6
= 3
Set BAR0 and BAR1
These options allow specifying values for card base
address registers (BARs).
If Enabler configures BARs by itself then it automatically adjust parent CardBus
bridge filters (if required). However if these options are used then Enabler
assumes that parent CardBus bridge filters were already set to proper values.
Example:
BAR0
BAR1
SkipAdapter
= 0xFFEFE000
= 0xFD00
Set BAR0
Set BAR1
Allows to skip (ignore) particular FireWire Adapter. Valid values are 0 and 1
Example:
SkipAdapter = 1
Skip Adapter
Resources Section
The Enabler INI file offers user an extended control over resource allocation.
Using [Resources] section of the Enabler INI file user can include or exclude
specific resources for use by Enabler.
During the loading Enabler collects information about resources (IRQ, I/O and
memory) used by PCI, PNP and Option ROMs. Enabler considers such
resources as non-free and excludes them from hardware configuration
procedure. In non-PnP computer Enabler may be not able detect all used
18
CardBus FireWire Enabler for DOS
APSoft
resources (e.g. resources used by Legacy ISA devices). Such undetected
resources may cause resource conflict. In such case you can adjust resource
filters manually by adding resources into this [Resources] section for the
Enabler’s INI file.
Only one [Resources] section can be defined in INI file.
To add resource you should define its description in separate line.
Any resource may be either excluded or included to hardware configuration
procedure. To exclude resource its description should start from ‘XMEM’ (for
memory), ‘XIO’ (for I/O) or ‘XIRQ’ (for IRQ). To include resource its
description should start from ‘MEM’ (for memory), ‘IO’ (for I/O) or ‘IRQ’ (for
IRQ).
For memory and I/O you also specify base address and size of resource range
separated by commas. For IRQ you specify only IRQ number separated by
comma.
Finally for any resource you may specify sharable attribute separated by comma.
There are next possible attributes:
•
•
•
E
D
T
-
Resource is available for exclusive (non-shared) use.
Resource is available for dynamic-shared use.
Resource is available for time-shared use.
You may specify sharable attribute for any resource, either excluded or
included. However for excluded resource it makes no sense (since excluded
resource is unavailable for any using) and will be ignored.
If no shared attribute specified, resource is assumed as an exclusive use
resource.
Example:
[Resources]
XMEM = 0xD0000, 0x400
XIO = 0, 0x100
IRQ = 5, D
XIRQ = 6
XMEM = 0x100000, 0x7FF0000
; Exclude memory
; [0xD0000-0xD03FF]
; Exclude I/O [0-0xFF]
; Include IRQ 5 with dynamic
; share
; Exclude IRQ 6
; Exclude memory
; [1MB – 2GB]
; Exclude memory [0xE0000-0xE7FFF] except [0xE1000-0xE2FFF]
XMEM = 0xE0000, 0x8000, E
CardBus FireWire Enabler for DOS
; Exclude [0xE0000-0xE7FFF]
19
APSoft
MEM = 0xE1000, 0x2000, E
[Resources]
XMEM = 0xD0000, 0x400
XIO = 0, 0x100
IRQ = 5, D
XIRQ = 6
XMEM = 0x100000, 0x7FF0000
; Include [0xE1000-0xE2FFF]
; Exclude memory
; [0xD0000-0xD03FF]
; Exclude I/O [0-0xFF]
; Include IRQ 5 with dynamic
; share
; Exclude IRQ 6
; Exclude memory
; [1MB – 2GB]
; Exclude memory [0xE0000-0xE7FFF] except [0xE1000-0xE2FFF]
XMEM = 0xE0000, 0x8000, E
MEM = 0xE1000, 0x2000, E
20
; Exclude [0xE0000-0xE7FFF]
; Include [0xE1000-0xE2FFF]
CardBus FireWire Enabler for DOS
A
P
P
E
N
D
I
X
Additional information
How to get Technical Support for CardBus FireWire Enabler
Please send an E-mail in English (we can’t process technical support questions
in any other language) to technical support (support@tssc.de).
In your request please specify:
1.
Description of your problem.
2.
The card name exactly as it appears on the card.
Please attach to your e-mail following files:
CardBus FireWire Enabler for DOS
1.
Please run CardBus FireWire Enabler with /V+[:<file>] switch (plus
all parameters you normally use), capture the output to the file and
attach it to your e-mail. E.g.
C:\>FWENAB /V+:LOG.TXT
or
DEVICE = FWENAB.EXE /V+:LOG.TXT
2.
CONFIG.SYS
3.
AUTOEXEC.BAT
4.
Enabler initialization file if one exists.
21
APSoft
Example of INI file
Following sample shows an example of FWENAB initialization file for the
system with one CardBus and one PCIC compatible adapter
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;
FWENAB Enabler. Sample of Initialization file
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; PCI-2-PCI Bridge between bus 0 and bus2
[0:1E:0]
PreFilter=0x60000000:0x60FFFFFF
; CardBus socket 0
[2:B:0]
ExCABase
= 0xFF000000
PrimaryBus
= 2
SecindaryBus
= 0x81
SubordinateBus = 0x81
MemFilter0
= 0xFFEFE000,4K
MemFilter1
= 0xFAC00000:0xFEBFFFFF
IOFilter0
= 0xFD00:0xFDFF
IOFilter1
= 0xFC00:0xFCFF
LegacyBase
= 0
IRQ
= 11
ISAEnable
= 0
VGAEnable
= 0
; FireWire Card
[81:0:0]
BARMask
= 1
BAR0
= 0xFD00
IRQ
= 11
22
CardBus FireWire Enabler for DOS
APSoft
This page is intentionally blank.
CardBus FireWire Enabler for DOS
23
CUSTOMER LICENSE AGREEMENT
APSoft thanks you for selecting one of their products for your computer. This is the APSoft Customer
License Agreement which describes APSoft's license terms.
- PLEASE READ THIS NOTICE CAREFULLY DO NOT DOWNLOAD OR USE THE SOFTWARE UNTIL YOU HAVE READ THE
LICENSE AGREEMENT. BY ACCEPTING TO DOWNLOAD THIS SOFTWARE, APSOFT
WILL ASSUME THAT YOU HAVE AGREED TO BE BOUND BY THIS STANDARD
AGREEMENT. IF YOU DO NOT ACCEPT THE TERMS OF THIS LICENSE, YOU MUST
RETURN THE PACKAGE UNUSED AND UNOPENED TO THE PARTY FROM WHOM
YOU RECEIVED IT.
Grant of License. APSoft grants to you and you accept a license to use the programs and
related materials ("Software") delivered with this License Agreement. This software is
licensed for use on one computer at a time. You may run this software on as many
machines as you like provided there is no possibility that it can be run on more than one
machine at a time. The software should never be installed on the hard drive of more than
one computer. If the software is installed on a network hard drive, access must be restricted
to a single user. You agree that you will not transfer or sublicense these rights. If you use
the Software on more than one computer at a time, you must license additional copies or
request a multi-user license from APSoft.
Term. This License Agreement is effective from the day you receive the Software, and
continues until you return the original magnetic media and all copies of the Software to
APSoft. APSoft shall have the right to terminate this license if you violate any of its
provisions. APSoft or its licensors own all rights, title, and interest including all worldwide
copyrights, in the Software and all copies of the Software.
Your Agreement. You agree not to transfer the Software in any form to any party without
the prior written consent of APSoft. You further agree not to copy the Software in whole or
in part, except for backup copies, unless APSoft consents in writing. Each of these copies
must have a label placed on the magnetic media showing the program name, copyright,
and trademark designation in the same form as the original Software. You will use your best
efforts and take all reasonable steps to protect the Software from unauthorized
reproduction, publication, disclosure, or distribution, and you agree not to disassemble,
decompile, reverse engineer, or transmit the Software in any form or by any means. You
understand that the unauthorized reproduction of the Software and/or transfer of any copy
may be a serious crime, as well as subjecting you to damages and attorney fees.
Disclaimer. APSOFT MAKES NO WARRANTIES, EITHER EXPRESS OR IMPLIED,
INCLUDING THE IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR
PURPOSE OR MERCHANTABILITY, AND APSOFT SHALL NOT BE LIABLE FOR
TORT, INDIRECT, SPECIAL OR CONSEQUENTIAL DAMAGES SUCH AS LOSS OF
PROFITS OR LOSS OF GOODWILL FROM THE USE OR INABILITY TO USE THE
SOFTWARE FOR ANY PURPOSE. SOME STATES MAY NOT ALLOW THIS
DISCLAIMER SO THIS LANGUAGE MAY NOT APPLY TO YOU. IN SUCH CASE, OUR
LIABILITY SHALL BE LIMITED TO THE REFUND OF THE APSOFT LIST PRICE.
Updates. APSoft will do its best to notify you of subsequent updates released to the public
or major corrections and the price for which they may be obtained. All updates and
corrections which are provided to you shall become part of the Software and be governed
by the terms of this license agreement.
Miscellaneous. This is the only agreement between you and APSoft and it cannot and
shall not be modified by purchase orders, advertising or other representations of anyone,
unless a written amendment has been signed by one of our company officers.
CardBus FireWire Enabler for DOS
24