TapeWare 6.30 SP2E 17 December 2002
This document includes updated information for the
documentation provided with TapeWare Version 6.30. The
information in this document and in the Help system
may be more up-to-date than the information contained
in the printed manuals. Many of the issues outlined in
this document will be corrected in upcoming releases.
1. CORRECTIONS IN THIS SERVICE PACK 2
1."RESTORED 0 FILES" WHEN DOING DISASTER RECOVERY
UNDER ALL NETWARE VERSIONS 2
2.EXTENDED PARTITIONS AND DISASTER RECOVERY UNDER
WINDOWS NT/2000/XP 2
3.BUILDING BACKUP SELECTION LIST TAKES A LONG TIME
2
4.LINUX CONSOLE MODULE LOAD STATUS INDICATOR 2
5.TAPEWARE FOR LINUX TAKES A LONG TIME TO LOAD 2
6.IDE DEVICES UNDER LINUX 3
7.COMMAND NOT SETUP ERROR 403 3
8.RESTART SERVER DIALOG REAPPEARED AFTER CLICKING
OK3
9.POTENTIAL PROBLEM IF MORE THAN ONE INSTALLED
OBDR DRIVE 3
10.DOUBLED FILE CAPACITY FOR SINGLE DIRECTORIES 3
11.LINUX LOGIN HANGS WHEN USING "ESC" KEY 3
12.GRAPH NOT DISPLAYING PROPERLY WHEN BACKING UP
MORE THAN 8 STREAMS 3
13.SLOW PERFORMANCE WITH DOMAIN CONTROLLER AND
IPX/SPX, BUT NOT ACTIVE DIRECTORY 3
14.UNINSTALLING TAPEWARE OPTIONS SOMETIMES DELETES
ADDITIONAL FILES 3
15.STREAM SYNC ERRORS NO LONGER OCCUR ON SYSTEMS
WITH 1GB RAM OR MORE 3
16.TAPEWARE NOW ASKS FOR A CORRECT TAPE AFTER IT
EJECTS A FULL TAPE 3
17.TAPEWARE WOULD OCCASIONALLY HANG WHEN A MEDIA
BECAME FULL DURING LARGE BACKUP JOBS 3
18.TAPEWARE NOW CORRECTLY MANAGES BACKUP JOBS IN
INSTALLATIONS WITH MULTIPLE TAPE DRIVES 4
19.TAPEWARE COMPLETES PHASE 3 OF DISASTER RECOVERY
IN NETWARE 6 INSTALLATIONS 4
2. FEATURES IN THIS SERVICE PACK 4
1.AUTO DEVICE BUFFER AND TRANSFER SIZE ALLOCATION4
2.BACKING UP TO MULTIPLE TAPE DRIVES WITH AUTO-
VERIFY 4
3."SILENT INSTALL" NOW SUPPORTED 4
4.FLOPPY VERIFICATION AND ERROR DETECTION PHASE 15
5.DISASTER RECOVERY UNDER NETWARE 6.X 5
6.SMTP MAIL CONNECTOR CAN NOW SEND LOGS LARGER
THAN 64K IN SIZE 5
7.F5-F8 KEY MAPPINGS UNDER LINUX CONSOLE 5
8.INSTALLING TAPEWARE AS A SERVICE UNDER LINUX 5
9.LINUX INSTALLATION PROGRAM ERROR REPORTING 5
10.ADDED CAPABILITY TO DISABLE RSM WHENEVER
TAPEWARE LOADS 5
11.TAPEWARE AND THE "FILESNOTTOBACKUP" REGISTRY
ENTRY UNDER WINDOWS NT/2000/XP 5
12.64-BIT FILE SYSTEM SUPPORT UNDER LINUX 6
13.TAPEWARE FOR WINDOWS IS NOW COMPILED WITH THE
MICROSOFT .NET COMPILER 6
14.UPGRADING TAPEWARE ALSO UPGRADES INSTALLED
OPTIONS 6
3. ACCESSING ONLINE DOCUMENTATION 6
1.HOW TO VIEW OR PRINT THE CD BASED DOCUMENTATION6
2.HOW TO VIEW WEBHELP HTML BASED HELP 6
3.LINUX ONLINE DOCUMENTATION/HELP 6
4. GENERAL NOTES 7
1.USING MULTIPLE SCSI BUSES WITH AUTOLOADERS 7
2.DEVICE BUFFER SIZES 7
3.WINDOWS .NET INITIATIVE 8
5. NOTES FOR WINDOWS NT/2000/XP 8
1.WINDOWS 2000 SERVICE PACK 2 REQUIRED FOR
DISASTER RECOVERY OPTION 8
2.WINDOWS 2000 COMPATIBILITY 8
3.INSTALLING TAPEWARE ON WINDOWS TERMINAL SERVER 8
4.LATER PHASES OF DISASTER RECOVERY ON JAPANESE
SYSTEMS IS PARTLY IN ENGLISH 8
5.LOCATION OF UPDATED DRIVERS 8
6.NEW MINIMUM REQUIREMENTS FOR NT 4.0 9
6. NOTES FOR NOVELL NETWARE 9
1.USING NWASPI.CDM AND FIBRE CHANNEL ON THE
NETWARE OPERATING SYSTEM 9
2.NWASPI.CDM MUST BE LOADED 9
3.DISASTER RECOVERY CANNOT FIND AN UPDATED SCSI
DRIVER 9
4.RECOVERING MIRRORED PARTITIONS 9
5.TAPEWARE DISASTER RECOVERY REQUIREMENTS FOR
NETWARE 6 9
6.TAPEWARE DOES NOT BACK UP THE NSS ADMINISTRATION
VOLUME BY DEFAULT 9
7.TAPEWARE SUPPORTS NSS PARTITIONS THAT ARE LARGER
THAN 4GB 9
7. NOTES FOR LINUX 10
1.KEY PROMPTS BEING CUT FROM BOTTOM OF SCREEN 10
2.TERM= ENVIRONMENT VARIABLE NOT CORRECTLY SET 10
3.DEFAULT INSTALLATION PATHS 10
4.ONLINE HELP IS NOT AUTOMATICALLY INSTALLED 10
5.COPYING THE INSTALLATION PROGRAM TO A LOCAL DISK
10
6.TCP/IP MAY NOT SEE OTHER TAPEWARE SERVERS 10
7.SCSI AUTOLOADERS MAY NOT BE DETECTED 10
8.IDE TAPE DEVICES ON DELL POWEREDGE SERVERS 11
9.SGM VERSIONS 11
10.TELNET-ING FROM WINDOWS 11
1. Corrections in this service pack
1. "Restored 0 files" when doing Disaster Recovery under all
NetWare versions
On certain configurations of NetWare, TapeWare would
restore 0 files during phase 4 of Disaster Recovery.
This was due to NWASPI.CDM not being correctly added
to the startup files. This has been fixed.
2. Extended partitions and Disaster Recovery under Windows
NT/2000/XP
On certain partition configurations under Windows
NT/2000/XP, extended partitions would be created
incorrectly when using Disaster Recovery. TapeWare now
restores these partition layouts correctly.
3. Building backup selection list takes a long time
This was due to the overhead of our Encrypted File
System (EFS) support utility, which called a certain
function every time a file was scanned. We now use a
different function, and have set EFS support to OFF by
default. You can re-enable it by adding the following
line to the [configuration] section of TapeWare.ini:
efsEnable=Yes
4. Linux console module load status indicator
Linux console user interface now correctly shows
module load status on initialization.
5. TapeWare for Linux takes a long time to load
TapeWare now scans by default for only 5 devices
instead of 20. This greatly decreases its load time
under Linux systems. If you have more than 5 devices
on your Linux machine, you can enable them by adding
the following line to the [configuration] section of
the TapeWare configuration file:
maxScsiDevices=x
6. IDE devices under Linux
There is a known problem with IDE-SCSI and check
conditions for which we have created a work around.
7. Command not setup error 403
A race condition involving multiple streams and the
Disaster Recovery module was fixed.
8. Restart server dialog reappeared after clicking OK
After a full restore under Windows, the restart server
dialog reappeared after clicking OK, requiring user to
click OK again. Now the dialog only appears once
before restarting server.
9. Potential problem if more than one installed OBDR drive
In installations with more than one OBDR drive, OBDR
generation could result in an unstable backup. Now
OBDR backups are generated sequentially, which may
increase the time to generate an OBDR backup.
10. Doubled file capacity for single directories
In the TapeWare database, doubled the capacity for
total files in a single directory.
11. Linux login hangs when using "Esc" key
During login in Linux installations, using the "Esc"
key no longer causes system to hang.
12. Graph not displaying properly when backing up more than 8
streams
When backing up more than 8 streams, the graph now
displays properly.
13. Slow performance with Domain Controller and IPX/SPX, but
not Active Directory
When checking for active directory in installations
with the IPX/SPX protocol stack and no active
directory, the system would not respond promptly,
resulting in slow performance. Now the system verifies
that the machine is a domain controller before
checking for active directory.
14. Uninstalling TapeWare options sometimes deletes
additional files
When uninstalling one or more TapeWare options, at
times the system would also delete additional files.
15. Stream sync errors no longer occur on systems with 1GB
RAM or more
Some users experienced stream sync errors on systems
with 1GB RAM or more. Now TapeWare computes the device
buffer size differently (see Device buffer sizes
below).
16. TapeWare now asks for a correct tape after it ejects a
full tape
Previously, if you selected Append to all or Append to
first tape, overwrite others for the Write mode for a
backup, the tape correctly ejected the tape if it was
full. Then it prompted you to re-insert the same tape.
Now TapeWare asks for the correct tape.
17. TapeWare would occasionally hang when a media became full
during large backup jobs
Some customers reported that TapeWare would
occasionally hang when a media became full. This
occurred during large backup jobs. TapeWare now
handles full media conditions correctly.
18. TapeWare now correctly manages backup jobs in
installations with multiple tape drives
In installations with more than one tape drive,
TapeWare tries to use all available drives. When a
backup job starts, it determines whether or not it
needs a second drive. Customers with this type of
configuration could experience either of the following
problems:
ú TapeWare allocates two or more tape drives for the job.
The first drive contains a tape, but the second drive is
empty. As the job runs, TapeWare asks the user to insert a
tape in the second drive. If the user clicks Abort, which
temporarily removes the drive from the job, TapeWare would
hang. Now, TapeWare runs the job correctly in this scenario.
ú The media in the first drive becomes full, so TapeWare
ejects the media. Then it continues backing up to the media in
the second drive. When it runs the verification step, an error
message occurs because the media is no longer loaded in the
drive. Now, TapeWare will not eject the first media until it
fills the media in the second drive.
19. TapeWare completes Phase 3 of Disaster Recovery in
NetWare 6 installations
In some NetWare 6 installations, TapeWare could stop
during Phase 3 of Disaster Recovery. Now this phase
finishes properly in these installations.
2. Features in this service pack
1. Auto device buffer and Transfer Size Allocation
TapeWare now automatically allocates a percentage of
free physical memory for device buffers, and better
utilizes device transfer sizes of 64-1kb. This
increases performance across the board.
2. Backing up to multiple tape drives with auto-verify
TapeWare jobs are now more intelligent when dealing
with single streams spanned over multiple devices.
TapeWare will wait until all possible media have been
used before ejecting a tape and prompting the user. In
this way, verifies can function without user
interaction while spanning across multiple devices.
3. "Silent Install" now supported
You can now create custom .inf setup file and have
TapeWare install itself without any user action.
First, create a file called autoinst.inf, place it in
the appropriate installation folder (i.e. win\lin\net)
and run the installation.
Example:
;-----------------------------------------------------
-------------------------
; Auto install options
;-----------------------------------------------------
-------------------------
[license]
document=3DE7FEF9-C7AFE3E7
[configuration]
serviceInstalled=Yes
regComp=Company
regUser=User
createZone=Yes
zone=TapeWare storage zone
node=ComputerName
targetDir=c:\Program Files\TapeWare
protocol=Tcp
4. Floppy verification and error detection Phase 1
TapeWare now verifies floppies upon creation. However,
we still highly recommend using new floppies for
Disaster Recovery.
5. Disaster Recovery under NetWare 6.x
We have addressed many bugs in Novell's initial
release of NetWare 6.x and now fully support disaster
recovery under NetWare 6.0. You must install NetWare
6.0 SP1 or later.
6. SMTP Mail Connector can now send logs larger than 64k in
size
Users can now specify the maximum length of an email
they want TapeWare to be able to send. To enable this
feature, add the following to the TapeWare.ini file:
Example:
Set the email log file size limit to 1 megabyte:
[smt]
sizeLimit=1048576
7. F5-F8 key mappings under Linux console
We added a shortcut key combination (ctrl-k) in the
Linux console which switches between the two possible
mappings for function keys above F5. This allows such
keys as shift-F5 to function properly on most
terminals.
8. Installing TapeWare as a service under Linux
Added the option to let the user choose whether or not
TapeWare will be installed as a service under Linux.
9. Linux installation program error reporting
Added the capability for the installation program to
return error codes if it could not load successfully.
10. Added capability to disable RSM whenever TapeWare loads
Added the capability for TapeWare to automatically
disable the Removable Storage Manager (RSM) service
under Windows 2000/XP. To enable this feature, add the
following to [configuration] section of the
TapeWare.ini file:
disableRsm=Yes/No
11. TapeWare and the "FilesNotToBackup" registry entry under
Windows NT/2000/XP
Added a routine to parse and add the files listed in
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet\Control\BackupRes
tore\FilesNotToBackup to the exclude filters of
TapeWare. To enable this feature, add the following to
the TapeWare.ini file:
[Ods-File System Connector]
filterRegExclude=Yes/No
12. 64-Bit File system Support under Linux
TapeWare now supports files larger then 2 gigabytes
under Linux.
13. TapeWare for Windows is now compiled with the Microsoft
.Net Compiler
TapeWare now works even better with newer versions of
Windows, including the upcoming .NET server platform.
Due to the .NET compiler's new optimizations, TapeWare
for Windows is now also 10% faster than previous
versions.
14. Upgrading TapeWare also upgrades installed options
When upgrading from an earlier service pack, the
TapeWare installer now upgrades all installed options,
whether they are licensed or not. You no longer have
to reinstall your various options.
3. Accessing Online Documentation
1. How to view or print the CD based documentation
Windows - Adobe Acrobat
After installing TapeWare, select
Start|Programs|TapeWare|TapeWare
Documentation|Printable Documents. In order to view or
print this documentation, you must have the Adobe
Acrobat v4.0 reader installed on your system. If you
do not already have this installed, you may install it
from the TapeWare CD by selecting
Documentation|Install Acrobat from the main TapeWare
installation screen.
DOS/NetWare/Linux - Adobe Acrobat
Use a Windows workstation to access the
\DOC\language\ACROBAT subdirectory on the TapeWare CD
where language is the localized language name. You
must have the Adobe Acrobat v4.0 reader installed on
your Windows workstation in order to view or print the
documentation. The localized version of Acrobat Reader
for Windows is also included in the Acrobat
subdirectory in case you do not have Acrobat installed
on your system.
DOS/NetWare/Linux - HTML
You may also use the HTML formatted documentation from
the \DOC\language\HTMLHELP subdirectory. The two files
contained in the directory are identical. One is
compressed with standard DOS/Windows PKZIP while the
other is compressed with Linux GZIP and TAR. Copy this
file over to a separate subdirectory on your hard
disk, and decompress the file. Approximately 1600
files will be extracted which is the HTML version of
TapeWare online help. To start the help system, use a
browser to open the index.htm file. This will open the
TapeWare table of contents and the opening pages.
2. How to view WebHelp HTML based help
HTML Web based help is included in the
\DOC\lng\HTMLHELP\HTMLHELP.ZIP and HTMLHELP.TGZ. Both
files are the same but zipped differently. The TGZ
file uses Linux tar/gzip while the ZIP file uses
standard WinZip. Unzip either of these files to your
local hard disk and launch the index.htm file as the
root of the Help tree.
3. Linux Online Documentation/Help
To use the documentation system for the Linux X-Window
based user interface, unzip either HTMLHELP.TGZ or
HTMLHELP.ZIP to the "installation
"directory/htmlhelp". By default, this would be
/usr/local/TapeWare/htmlhelp.
4. General Notes
1. Using multiple SCSI buses with autoloaders
If your autoloader and the devices within the
autoloader are connected to different SCSI buses, the
driver may become confused as to which device is
contained in the autoloader. If the drives and
autoloader use either the SCSI-2 serial number or the
new SCSI-3 identifier protocol, all devices will be
correctly assigned. However, if the autoloader
supports neither the SCSI-2 serial number nor the SCSI-
3 identifier protocol, you must connect the devices to
the same SCSI bus as the autoloader, or manually
configure the drivers as follows:
1. Run the administrator as you normally would. Note the
name of the device and autoloader. For this example, the
loader will be "Ldr-2.0.3.0: ADIC Scalar" with the two devices
being "Dev-3.0.3.0: DLT 4000" and "Dev-4.0.3.0: DLT 4000".
2. Add a line in the .ini configuration file as follows:
[Ldr-2.0.3.0: ADIC Scalar]
device1=Dev-3.0.3.0: DLT 4000
device2=Dev-4.0.3.0: DLT 4000
3. Restart the service and the administrator, if necessary,.
2. Device Buffer Sizes
With the advent of TapeWare SP2E, it is no longer
necessary to set the devBufferSize in the
configuration section of the TapeWare.ini file.
TapeWare now will automatically adjust the device
buffer size based on a percentage of free physical
memory on the system in question. You can still force
TapeWare to use a specific buffer size, and you can
also change the percentage of free memory you want
TapeWare to use for device buffers. To change these
settings, edit the TapeWare.ini using a standard text
editor. Under the [configuration] section, add the
following:
fixedBufferSize=Yes
devBufferSize=n
where n is the buffer size in Kb. For example, to set
the buffer size to 4Mb, use devBufferSize=4096.
fixedBufferSize=No
usePercentFreeMem=n
where n is the percent of free memory to use. For
example, to set it to 15 percent, use
usePercentFreeMem=15
Setting these values higher can significantly enhance
performance. This causes TapeWare to buffer more data
in memory that is en route to the tape device. By
doing this, TapeWare can read larger amounts of data
from the disk subsystems and fill the buffers faster.
This has the effect of "smoothing" file sizes by
taking advantage of larger files. However, setting
these values too high will cause the operating system
to "page" these data buffers to/from disk when
accessed by TapeWare. This will significantly reduce
the performance since additional disk operations will
be required.
3. Windows .Net Initiative
Yosemite Technologies, Inc is constantly trying to
improve our current product and plan for the future.
Part of this initiative is making sure that TapeWare
is constantly updated in order to be prepared for the
latest and greatest technologies. For this reason
TapeWare is now fully .NET aware with the integration
of the .NET compiler throughout the Windows portion of
TapeWare. The result is a faster, smarter and more
robust backup solution from Yosemite Technologies,
Inc.
5. Notes for Windows NT/2000/XP
1. Windows 2000 Service Pack 2 required for Disaster
Recovery Option
The original release of Windows 2000 has a problem
with registry quotas. When running TapeWare to build a
Disaster Recovery diskette set, CD-R or tape, the
registry quota would soon become exhausted. For this
reason, TapeWare checks the running version of Windows
2000 and specifically disables all Disaster Recovery
functions if Service Pack 2 is not installed. To
obtain this patch, follow this link to obtain SP2:
http://www.microsoft.com/downloads/release.asp?release
id=29423&FeatList=3
Note: This URL is subject to change.
After the update is applied, TapeWare should recognize
the new update and enable the Disaster Recovery option
after it has been installed.
2. Windows 2000 compatibility
TapeWare currently supports most Windows 2000
functionality. However, a couple of areas are not
supported:
1. If you use junction points, TapeWare will consider the
junction as a complete volume; In other words, it will follow
the junction point and backup all the files in the junction
rather than simply backing up the metadata. On restore, if the
junction point is not mounted, TapeWare will create a
subdirectory with the same name as the junction point and
restore to the same disk that was previously hosting the
junction point.
2. RSM - Remote/removable storage manager is not currently
supported. If TapeWare is run, the RSM service is temporarily
disabled, TapeWare will allocate all tape device and tape
loader devices, then RSM is restarted.
3. The TapeWare Disaster Recovery option for Windows NT/2000
will support basic disk configurations only. If you attempt to
restore your system with dynamic disks enabled, TapeWare will
not be able to restore the volume information.
3. Installing TapeWare on Windows Terminal Server
If you are running Terminal Server, you must install
TapeWare as a service. This allows multiple user
interfaces to share the common resources of the
service.
4. Later phases of Disaster Recovery on Japanese systems is
partly in English
The final phases of Disaster Recovery are not
translated into Japanese. All other languages are
supported, but the Japanese will revert to English. In
addition, some non-English characters may be displayed
as black boxes when displayed on the log screen. This
is normal and can be ignored. All files will be
recovered to the correct names.
5. Location of updated drivers
The Windows Disaster Recovery requires all drivers to
be located in the %SYSTEMROOT%\SYSTEM32\DRIVERS
subdirectory. If you have a driver that is required to
run your tape device or disk devices and it installs
to a different location, put a copy of this driver
into the DRIVERS directory.
6. New minimum requirements for NT 4.0
TapeWare now requires that you have the Windows NT
Service Pack 6a or above installed when using NT 4.0.
This is due to the new dependency requirements of MFC
7.0 (oleacc.dll).
6. Notes for Novell NetWare
1. Using NWASPI.CDM and Fibre Channel on the NetWare
operating system
If all devices are not detected during auto detection,
or devices are missing within the device explorer,
make sure that you are loading NWASPI with the /LUN
option as follows:
load NWASPI.CDM /LUN
This line is typically found in your STARTUP.NCF.
2. NWASPI.CDM must be loaded
For systems using .HAM drivers, make sure that
NWASPI.CDM is loaded from your AUTOEXEC.NCF or
STARTUP.NCF. If not, the final phase of Disaster
Recovery will not be able to access the tape device.
3. Disaster Recovery cannot find an updated SCSI driver
TapeWare searches for required drivers, first in the
C:\NWSERVER directory, followed by the SYS:SYSTEM
directory. If you update a driver, make sure the
updated driver is also placed in C:\NWSERVER.
4. Recovering mirrored partitions
All mirrored partitions are now correctly initialized
during the recovery procedure if a full system
recovery is selected. To prevent any data loss on
other partitions, mirror pairs are not automatically
recreated if only the boot disk recovery method is
used.
5. TapeWare Disaster Recovery requirements for NetWare 6
In NetWare 6 installations, you must install NetWare 6
SP1 to support TapeWare Disaster Recovery.
6. TapeWare does not back up the NSS administration volume
by default
TapeWare no longer backs up the NSS administration
volume _ADMIN by default under NetWare 6. This now
matches TapeWare behavior under NetWare 5, which does
not back up the NSS administration volume NSS_ADMIN by
default.
7. TapeWare supports NSS partitions that are larger than 4GB
Many NetWare installations require NSS partitions that
are larger than 4GB under NetWare 6. Now TapeWare
supports all functions, including disaster recovery,
in these installations.
7. Notes for Linux
1. Key prompts being cut from bottom of screen
TapeWare displays key prompts on the bottom of the
screen using logical keys. The terminal you are using
may map these keys differently on your keyboard. For
example, for the Shift-F1 key, some keyboard's drivers
may map this as F11 while others will map this as
Shift-F1. If this is the case, TapeWare's Shift-F1
maps to F11, Shift-F2 maps to F12, Shift-F3 maps to
Shift-F1, etc. In addition, if your screen driver is
setup for less than 25 rows, TapeWare will remove the
bottom line of the screen.
2. TERM= environment variable not correctly set
Under Red Hat Linux, when running the TapeWare
character-based interface under the xterm console in X-
Windows, the screen may be corrupted. This is due to a
bug in the console driver. You can correct this
problem by using the following command prior to
starting TapeWare:
export TERM=xterm-color
3. Default installation paths
You should install to the default /usr/local/tapeware
directory. If you install to any other directory, you
must manually enter the path name when upgrading,
installing options or removing TapeWare as the
installation program will not search for existing
installations except in the default
/usr/local/tapeware directory.
4. Online help is not automatically installed
The online help is not installed by default since it
is rather large. You may find the online documentation
under the /doc directory on the CD. The documentation
is in HTML format and can be viewed with any browser.
See "Accessing Online Documentation" above.
5. Copying the installation program to a local disk
If you copy the installation files from the CD, make
sure you mark the install and lin/DLunxins files with
the executable attribute.
6. TCP/IP may not see other TapeWare servers
Under some conditions, the Linux TCP/IP driver will
not be able to display other Storage Servers on the
TCP/IP network. Make sure that you have entered a
valid TCP/IP default gateway, or specify the server
address in the TapeWare host address dialog box during
installation.
7. SCSI autoloaders may not be detected
By default, most SCSI drivers under Linux do not
enable LUN support, which is required to support
integrated autoloaders. To enable LUN support on
Linux, add the following line to the end of
/etc/lilo.conf:
append= "max_scsi_luns=2"
After this line is added, make sure you run lilo to
update the configuration with the following command:
lilo
After this is completed, reboot your system.
8. IDE tape devices on Dell PowerEdge servers
If using an IDE tape device attached to a Dell
PowerEdge server, please consult the Red Hat
installation notes provided with your server and tape
drive. The documentation contains important
information required for the proper operation of your
PowerEdge server and IDE tape device. For more
information, visit http://www.dell.com/linux.
9. SGM Versions
If you are upgrading from an earlier version of
TapeWare, you must restart your machine so that the
latest version of sgm.o will be loaded. You may also
manually unload any running version of sgm.o by using
the Linux rmmod command.
10. Telnet-ing from Windows
Here are the steps you need to configure in order for
the TapeWare to respond correctly in CRT:
1. Copy the mappings below and save them into a file
called TapeWare.key
2. Select Session Options from the CRT's Options menu
3. Select the Emulation category
4. Select vt100 for the terminal
5. Check ANSI Color
6. Select Custom for the keyboard and enter full path
to TapeWare.key
7. Select the Appearance category and use the vt100
font
Make sure you export the variable TERM to xterm-color
using the command:
export TERM=xterm-color
On some systems, such as CorelLinux, xterm-color is
not available so you must use xterm instead. Unlike
xterm-color, xterm is only back and white.
You can also put "export TERM=xterm-color" in
/etc/profile or ~/.bash_profile for permanent setting.
Key mappings placed in TapeWare.key:
N VK_INSERT "\e[2~"
N VK_F1 VT_PF1
N VK_F2 VT_PF2
N VK_F3 VT_PF3
N VK_F4 VT_PF4
N VK_F5 "\e[15~"
N VK_F6 "\e[17~"
N VK_F7 "\e[18~"
N VK_F8 "\e[19~"
N VK_F9 "\e[20~"
N VK_F10 "\e[21~"
E VK_INSERT "\e[2~"
S VK_F1 "\e[23~"
S VK_F2 "\e[24~"
S VK_F3 "\e[25~"
S VK_F4 "\e[26~"
S VK_F5 "\e[28~"
S VK_F6 "\e[29~"
S VK_F7 "\e[31~"
S VK_F8 "\e[32~"
S VK_F9 "\e[33~"
S VK_F10 "\e[34~"
Notice
Information in this document is subject to change without
notice. Yosemite Technologies, Inc makes no representations or
warranties with respect to the contents of this document and
specifically disclaims any implied warranties of
merchantability or fitness for any particular purpose.
Further, Yosemite Technologies, Inc reserves the right to
revise this publication and to make changes without obligation
to notify any person or organization of such revisions or
changes.
Copyright
Under copyright laws, the contents of this document may not be
copied, photocopied, reproduced, translated or reduced to any
electronic medium or machine-readable form, in whole or in
part, without prior written consent of Yosemite Technologies,
Inc.
Copyright c 2002 Yosemite Technologies, Inc
www.TapeWare.com
Trademarks
TapeWarer is a registered trademark of Yosemite Technologies,
Inc. NetWarer is a registered trademark of Novell, Inc.
Windowsr and Windows NTr are registered trademarks of
Microsoft Corporation. Linuxr is a registered trademark of
Linus Torvalds.
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.