Rimage USer Guide Template

Rimage USer Guide Template
Advanced Setup Guide
110721- 000 Revision B
Use this manual to help you:
*
*
*
*
Configure the Control Center and clients for an existing network,
Add a Rimage system to an existing Workgroup network environment,
Add a Networked Client (Windows or Macintosh), and
Change the Default Rimage User Account password.
Rimage Corporation
7725 Washington Avenue South
Minneapolis, MN 55439
FAX: (952) 944-6956
Service: (952) 946-0004 (International)
(800) 553-8312 (North America Only)
Rimage Technical Website:
http://www.rimage.com/Technical/index.html
Rimage Europe GmbH
Hans-Böckler-Straße 7
63128 Dietzenbach, Germany
Tel: +49-(0) 6074-8521-0
FAX: +49-(0) 6074-8521-21
Record of Revisions
Revision
Date
A
3/24/03
B
09/08/03
Description
Initial release.
Revised for Software Suite Version 6.2.30, QuickDisc MultiPlatform, EULA, and the Rimage User Account.
Copyright© 2002-2003, Rimage Corporation
Rimage, the Rimage logo, Producer, OfficeNET, ProNET, and QuickDisc are trademarks of
the Rimage Corporation.
All other trademarks and registered trademarks are the property of their respective owners.
Document Disclaimer
Rimage Corporation reserves the rights to make improvements to the equipment and software
described in this document at any time without any prior notice. Rimage Corporation reserves
the right to revise this publication and to make changes from time to time in the content
hereof without obligation of Rimage Corporation to notify any person or organization of such
revisions or changes.
This document may contain links to web sites that were current at the time of publication, but
may have moved or become inactive since. This document may contain links to sites on the
Internet which are owned and operated by third parties. Rimage Corporation is not
responsible for the content of any such third-party site.
ii
Table of Contents
Introduction ............................................................................................................................... 4
Prerequisites......................................................................................................................... 4
Basic Requirements......................................................................................................... 4
Two Systems.................................................................................................................... 5
Scenario #1 – Most Common ............................................................................................... 6
Scenario #2 – Future Expansion ......................................................................................... 7
File Server ....................................................................................................................... 7
Rimage Server ................................................................................................................. 8
Scenario #3 – Adds Networked Client to Scenario #2 ..................................................... 10
Scenario #4 – Adds Networked Client to Scenario #1 ..................................................... 12
Scenario #5 – Macintosh Client......................................................................................... 14
Macintosh Setup Requirements.................................................................................... 14
Scenario # 5 Sample Procedure.................................................................................... 17
Change Rimage Services Account Password .......................................................................... 18
Change the Default Rimage User Account........................................................................ 18
Appendix A - Licenses.............................................................................................................. 20
Rimage End User License Agreement (EULA) ................................................................. 20
Rimage Java Sample License ............................................................................................. 23
The Apache Software License, Version 1.1 ....................................................................... 24
Sonic Software License - EXHIBIT B................................................................................ 25
ActiveState Community License........................................................................................ 28
Glossary.................................................................................................................................... 30
iii
Introduction
The Rimage Messaging System communicates order requests and passes on completion
notices or possible errors. The system uses a Messaging Server that forwards the
orders to the Image and Production Servers. The Messaging Server runs on the
Control Center. All client applications and Production and Image Servers must have
access to the Messaging Server. The source files and the Working Folder must also be
accessible by the clients and the Rimage Servers for the system to work.
Configuring the software on the Control Center and client applications to process
orders requires the proper steps and planning. This document provides the general
information needed to configure the Control Center and client applications to function
on an existing network. We also included some common scenarios with the steps to get
clients on a workgroup network to process orders successfully.
Prerequisites
1. The Rimage autoloader and printer should be set up and connected to the
Control Center before starting the advanced setup process.
2. When the Control Center is first powered up, follow the on-screen directions to
enter information in the Windows Setup Wizard dialog boxes (e.g., the License
Agreement, Product Key, Computer Name and Administrator Password dialog
boxes). Refer to the Microsoft Windows 2000 Professional Quick Start Guide
manual for additional information. The product key is located on the side cover
of the Rimage Control Center.
3. After the Microsoft Windows product key is entered, the Rimage Production
Server starts. The product activation prompts display. It is recommended to
activate your software right away; however, you could bypass the activation
until the system is completely installed on the network. You have up to 30
days to activate the software. Activating the software provides Rimage with
your system’s information so we can provide you with new software updates
and any helpful or critical information. Our service staff will also have your
equipment information on file so we can provide faster service.
Basic Requirements
•
Source files to be recorded must be accessible to the Control Center and client
applications when using QuickDisc Multi-Platform.
•
Source files from a personal hard drive can be recorded if using the built-in
imaging module of QuickDisc 6, or by sharing the source location to the Image
Server.
•
The Working Folder must be accessible by the Control Center and client
applications. The Working Folder holds all the files required for an order.
•
Multiple client applications can be installed within the building where the
Rimage autoloader is located. See the Rimage Software License on page Error!
Bookmark not defined..
•
Labels should be a CD Designer .btw file, an Acrobat .pdf file, a Print Control
Language .pcl file, or a Print-to-File .prn file (.btw or .pdf files are
recommended).
4
•
Share permissions, file level permissions, and user accounts are important
when client applications are added to remote PCs. Specific information is
provided throughout this document.
•
Rimage recommends only one Messaging Server and one Bridge Server
operating on the network if orders are to be submitted to any Image or
Production Server.
This document includes five example scenarios. Some scenarios change the location of
the Working Folder and the location of the client applications. The first four scenarios
use Windows client applications to submit orders to the Control Center. The fifth
scenario uses a Macintosh computer to submit orders to the Control Center.
Two Systems
If you are just installing a single Rimage System, reading this section is not required.
If you are adding a new Rimage Messaging System to a network that has an existing
Non-Messaging System, Rimage recommends upgrading the Rimage Image and
Production Servers to version 6 as a minimal requirement. To upgrade the Rimage
Servers, refer to the document “Software Suite 6 Upgrade Guide” installed on the new
Rimage Server in the Rimage menus.
5
Scenario #1 – Most Common
This scenario covers the installation of a single Rimage Producer system on an existing
Workgroup network environment. All order requests are processed through the client
applications on the Control Center. The source files are located on the File Server and
the working folder is located on the Control Center. Other client applications could be
added to this configuration. Refer to Scenario #4 to add client applications.
Note: The Rimage system should function right out of the box if orders are submitted
from QuickDisc and QuickDisc Multi-Platform running on the Control Center.
Some companies have a policy that restricts you from using the built-in Local
Administrator account. If this is the case, follow these directions:
1. Create a new user on the Control Center. Then add the new user to the local
administrators group.
Note: The Rimage Server applications require administrative privileges in
order to function.
2. Log on as the new user you just created.
3. Go to Add/Remove Programs and run Repair on the Rimage Producer
Software Suite. This updates the new user profile and registry settings.
4. At the Start Copying Files dialog box, select Next.
5. Continue through the prompts until the updates are complete.
6. If the network configuration is complete, the Bridge Server user account
should be changed (see page 18).
6
Scenario #2 – Future Expansion
This scenario covers the installation of a single Rimage Producer system on an existing
Workgroup network environment. Client applications submit orders from the Rimage
Server. Source files from the File Server can be recorded. The Working folder is
installed on the File Server, which allows other client applications to be added easily.
To add more Rimage Client Applications to this type of environment, refer to Scenario
#3.
Note: The installation of the Rimage autoloader, printer and Control Center must be
completed before performing these procedures.
Gather the following information before you begin:
•
Computer Name of the File Server that will host the Working Folder. You
could use the IP address only if the IP address does not change.
•
The user name and password of the user that is logged on to the Control
Center.
Note: The user logged in to the Control Center must be the local
administrator or a user that is a member of the Local Administrators
Group. If you plan to use a user that is a member of the local
administrators group, you must be logged on as that user.
File Server
1. At the File Server, create a User Account with the same user name and password
as the account that is logged in to the Control Center running the Rimage Server
applications.
2. Create a Folder named “Rimage” on a drive that has sufficient free space for your
disc image files. The Rimage folder should have enough space to hold disc image
files and labels. Full disc image files range from 650 Megabytes to 4.7 Gigabytes
per disc image.
3. Share the “Rimage” folder as “Rimage”.
7
Rimage Server
1. Log on to the Control Center using the user account that will be logged on to run
the Rimage Server applications (Production Server, Image Server, etc.).
Note: This account requires local administrative privileges.
2. Go to Add/Remove Programs and run Repair on the Rimage Producer or
OfficeNet Software Suite.
3. At the Repair screen select Next.
4. The current settings display. To change the working folder, select Back.
5. At the Question - Do you want to go back .. dialog select No.
6. Use the Browse button to select the new location of the working folder. It is
recommended to select the location using Windows' My Network Places to get the
UNC path name.
8
7. After selecting the \Rimage\ path, select OK. The new UNC path is displayed.
8. Select Next and complete the rest of the setup.
9. To add more clients to the network in Scenario #2, go to Scenario #3 on page 10.
10. If the network configuration is complete, it is recommended that you change the
Bridge Server password (refer to page 18).
9
Scenario #3 – Adds Networked Client to Scenario #2
This scenario covers the installation of the client application on an existing Workgroup
Network. Scenario #2 – Future Expansion should be completed before adding the
client applications to the client PCs.
All order requests are processed through Client Applications from Client PCs, and the
Working Folder is located on a File Server. A Client PC submits orders to the Control
Center utilizing the Working Folder. Source files are usually on the File Server;
however, the source files can be located on the Client PC if using QuickDisc.
1. Gather the following information before you begin:
a.
The Computer Name (Host Name) of the Control Center. (Computer
that is running the Rimage Server applications.) You could use the IP
address only if the IP address does not change.
b. The Computer Name (Host Name) of the File Server. (Computer that
is hosting the “Working Folder” and Source Files.)
c.
The Computer Name of the Client PC. (Computer that is running the
Client Applications.)
d. The User Name and Password of the client that sends orders to the
Control Center.
2. Create a user account at the Control Center with the same file access
permissions to the File Server as the user on the Client PC. This allows the
Image Server and Production Server access to the required files on the File
Server.
3. At the File Server, which holds the “Working Folder”, create new users with
the same user name and password as the user that submits orders from the
Client PC and the user or operator at the Control Center. These users must
have Read\Write permissions to the Working Folder and source files.
10
4. At the Client PC, temporarily add the user to the Administrators Local Group.
Note: The setup requires administrative rights in order to be installed. If this
step is not taken, the user profile will not get the proper registry and profile
information. (Do not use the Run As command.)
5. At the Client PC, log on as the user that will be submitting orders to create
discs.
6. Place the Producer or OfficeNet Software Suite disc in the client PC.
7. Run the setup and select the option for Client Applications Only.
8. During the install, you will be asked for the location of the Working Folder.
9. Use the Browse button to select the Working Folder location through
Windows' My Network Places.
Example: “\\FileServer\Rimage\”
10. During the install, you will be asked for the Computer Name (Host Name) of
the Rimage Messaging Server (i.e., the Control Center).
11. Continue with the setup using the default settings.
12. Using the Rimage Software Suite disc, install the print driver on the client PC
if using CD Designer as the label editor. The print driver must match the
printer on the Rimage autoloader. Refer to the printer user guide for the
specific driver installation directions.
13. Move the user on the client from the local Administrators group to the Power
Users group.
Note: The client applications require Power User level permissions.
11
Scenario #4 – Adds Networked Client to Scenario #1
This scenario covers the installation of Rimage Client applications on a Client PC.
Scenario #1 should be completed before adding the Client applications to the client
PCs.
All order requests are processed through client applications from Client PCs, and the
Working Folder is located on a Control Center.
1. Gather the following information before you begin.
a. The Computer Name (Host Name) of the Control Center.
b. The user name and password of the client that is sending orders to the
Control Center.
2. At the Control Center, create a new user with the same user name and
password as the user that will be submitting orders from the Client PC.
3. At the Client PC, temporarily add the user to the administrators local group.
Note: The setup requires administrative rights in order to be installed. If this
step is not taken, the user profile will not get the proper registry and profile
information.
4. Log on as the user that will be using the client applications to submit orders to
create discs.
5. Place the Software Suite disc in the client PC.
6. Run the setup and select the option for Client Applications Only. During
the install, you will be asked for the location of the Working Folder.
7. Enter the Working Folder location on the Rimage Server:
E.g., \\Control Center\Rimage\.
8. During the install, you will be asked for the Computer Name (Host Name) of
the Rimage Messaging Server. This is the Control Center running the Rimage
Messaging Server (the same computer name that was used for the Working
Folder).
12
9. Continue with the setup using default settings.
10. If using CD Designer as the label editor, use Rimage Software Suite disc to
install the print driver on the client PC. The print driver must match the
printer on the Rimage autoloader. Refer to the printer user guide for the
specific procedure.
11. Move the user on the client from the local Administrators group to the Power
Users group.
Note: The client applications require Power User level permissions.
13
Scenario #5 – Macintosh Client
This scenario covers the installation of the Rimage Client Applications on a Macintosh
computer with OS 10.2, to work with an existing Rimage System in a Workgroup
environment. You should have already installed Scenario #2.
This document covers a Macintosh computer connected to a Windows Workgroup
environment, where there are no Macintosh servers on the network.
Note: You should have a good understanding of Windows and Macintosh networking.
Macintosh Setup Requirements
a. The Rimage Client applications only work on Macintosh computers with OS 10.2
(Jaguar).
b. Labels can be created with a Macintosh graphic application that can export an
Acrobat .pdf file.
c.
The Macintosh computer must have a static IP address. This could be either a
reserved or static IP address.
d. The location of the Working Folder must have an IP address that does not change.
This could be either a reserved or static IP address.
e.
The Control Center must have an IP address that does not change.
f.
The user logged onto the Macintosh must have “Full Control” share permissions
for the “Working Folder”. If the working folder is on a Windows PC (which is
recommended and is covered in this scenario) NTFS security permissions must
allow the user on the Macintosh Read/Write permissions for the working folder
and all its contents.
Note: Windows default settings allow everyone “Full Control” Share & NTFS
permissions when they are created.
Note: The recommended location for the Working Folder is on a PC running
14
Windows, preferably a server not located on the same PC as the Rimage Server
applications.
g.
The Control Center must be logged in with the same user name and password that
the Macintosh client is using for submitting orders. There is an alternative, but it
involves enabling the root user account and modifying the Samba config file.
See note (m) for directions on how to enable the Root account. See note (n) for
directions on how to modify the Samba config file.
h. When a user on the Macintosh wants to burn files to a CD/DVD, the logged on user
must only select files from his or her Home Folder. The user’s files located under
the Home Folder are the only files shared, unless you enable the Root account and
modify the config files for Samba. (Public folders under each user’s home folder
are used to share files among other users. The folders named “Drop Box” under
the Public folders are used to drop files and folders to other users.)
i.
Each user on the Macintosh that submits orders to the Control Center must have
the “Enable Windows File Sharing” option enabled.
j.
The Control Center must have access to the files that are selected from QuickDisc
Multi-Platform.
k. Mount a Volume to a windows share. You can mount a windows share by typing
“smb://computerName/shareName” or “smb://IP Address/share name” using the
“Finder” or typing it in the “connect to” dialog box under the Go menu option.
Notes:
l.
o
If you type the path in manually and select to use the computer name instead
of IP Address, then you must use the Computer Name during the installation
of the clients.
o
If you type the path in manually and select to use the IP Address instead of the
Computer Name, then you must use the IP Address during the installation of
the clients.
o
If you use the “Connect To” option under the GO menu and browse to the
computer you are connecting to, you must use the IP Address during the
installation of the clients.
o
If you connect to a mounted volume using an IP address, or browse to the
computer name in the “connect to server” option, you can still use a Computer
Name during the installation of the clients, but you will need to use the Root
account to modify the HOSTS file. See note (o) for direction on how to modify
the HOSTS file. Modifying the HOSTS file only works when NetInfo is not
used to configure the network settings.
If you want to record a disc using files from a remote computer, you must mount a
Volume to a folder under the user’s Home Folder.
o
Create a new folder in your current users Home Folder. You can give it any
name you choose.
o
Run this command from the terminal:
mount –t smbfs //computer2/share /users/administrator/share
o
After the command is run, the folder you chose will contain the files that are
on “\\computer2\share”.
15
m. Enable the Root Account. Open the “NetInfo” program located in the
>Applications>Utilities folder. Click on the padlock and enter your password.
Select the command “Enable Root User” under the menu option “Security”. Give
the root account a strong password as it has the ability to do anything. You can
now logoff and log back on as the Root user if you want.
n. Modify the Samba config file. The smb.conf file is a file that contains information
on how samba is configured. Setup the required shares in this file. Edit the file by
logging on with the root user account. Then open the TextEdit program. From the
file menu, select the Open command. Type in the path to the Hosts file
“/etc/smb.conf” and click Open. Enter the new lines of text as shown in the
example below.
Example: Share a folder named “mystuff” located at the following location on the
hard drive “/applications/mystuff” using a share name of stuff. Enter the following
information in the smb.conf file.
[mystuff]
path = /applications/mystuff
public = yes
only guest = no
writable = yes
printable = no
After you reboot the PC, you will be able to see a new share named “mystuff” from
a Windows PC.
Note: Configure the user permissions so that the user logging on from Windows
has permission to access this folder.
o.
Modify the Hosts file. The Hosts file is used to map a NetBIOS ComputerName to
an IP address. Therefore, when a client tries to connect to a remote computer
using a ComputerName, it is able to resolve the name to a specific IP address.
Log on as the root user account. Then open the TextEdit program. From the file
menu, select the Open command. Type in the path to the Hosts file “/etc/hosts”
and click Open. On a new line in the file, enter the IP address of the PC followed
by a space and then the ComputerName for the IP address you entered. It should
look like this:
“202.253.222.1 Server1”
Click on Save and close the document. Now when you connect to a computer
named Server1, it will point to the IP address 202.253.222.1. If you installed the
Rimage Software Suite using computer names and you are having trouble, try
using the IP address to fix the problem.
16
Scenario # 5 Sample Procedure
This procedure configures a system like Scenario # 5 once Scenario #2 is completed.
1. Gather the following Information before you begin.
a. Both the IP address and Host Name of the computer that hosts (holds) the
Working Folder.
b. Both the IP address and Computer Name (Host Name) of the computer running
the Rimage Messaging Server (most cases the Control Center).
c. The Windows UNC path to the “Working Folder” Example:
“\\servername\Rimage\”
d. Get the user name and password of the user that will be submitting orders to the
Control Center.
2. Use the system setup from Scenario #2.
3. At the Macintosh computer, create a user account with the same user name and password
as the user account that is logged in and running the Rimage Server applications.
Note: User names are case sensitive on a Macintosh.
4. Configure the new user on the Macintosh with administrator privileges and enable the
“Allow Windows file sharing for this user” option.
5. Log off and log back on as the new user you just created on the Macintosh.
6. Before running the Rimage Client Setup, you must mount a Volume to the “Working
Folder”. See note “k” in the “Macintosh Setup Required” section on how to mount a
volume.
7. Run the Rimage Client Setup on the Macintosh.
8. You will be asked for the location to the “Working Folder”. Use the Browse button and
navigate to the mounted volume created in the previous step.
9. A prompt requests the Windows UNC path to the “Working Folder”. This is the path you
would type if you where at a Windows PC (e.g., ”\\\Computer Name\Share Name”).
10. A prompt asks for the host name of the Rimage Messaging server (Control Center).
Enter it based upon how you mounted the volume. Refer to note “k” under “Macintosh
Setup Required” section (using IP addresses is recommended).
11. Finish the setup.
17
Change Rimage Services Account Password
All default installs of Rimage Software Suite 6 are configured at the factory with an
“account” for the Bridge Server and eMS. Rimage recommends the password to be
changed for security reasons. Do not change the user account name!
Account Name:
RimageServices
(not case sensitive)
Password:
password
(case sensitive - all lower case)
The “RimageServices” user account for Bridge Server and eMS must have access to all
applicable file locations in order to operate properly. Otherwise, you will have
difficulty producing discs.
Change the Default Rimage User Account
When the Rimage Software Suite is installed, a default user account is created so the software
is fully functional. The default user account is required for the eMS and Bridge Server to
function. If you are using the Rimage ProNET software configuration, the user account is also
required for ePS, and eIS.
To change the user account password, you must be logged in as the administrator.
1. Stop all orders and exit all Rimage programs.
2. Stop the Messaging Server and Bridge Server. If you have the ProNET configuration,
stop the eIS and ePS services using the same procedure.
3. Right-click on My Computer and select Manage.
4. Expand Local Users and Groups.
5.
Click on Users.
6.
Right-click on the RimageServices account and select Set Password.
7. Enter the new password and enter the same password for confirmation (use lower case
characters) and click on OK.
8. Place the software disc in the CD-ROM drive.
9. Create a shortcut from the software suite setup (Setup.exe) and place on the desktop.
18
10. Right-click on the setup and select Properties.
11. Edit the Target field and add a command line switch at the end of the line: pwd:password (Substitute the "password" text with the new password from step 7.)
12. Select OK to save the changes.
13. Run the new shortcut with the command line switch and select Repair. This updates
all the services that use the "RimageServices" account.
Once the password is changed, anytime you update or modify the Rimage software suite,
you must use the command line switch with the new password. Keep the shortcut or store
it on a floppy disc to keep the new password.
14. Reboot the computer.
Note:
If you updated the software suite from version 6.1.x to 6.2.x or higher, you should delete
the previous user account (ProNetSrvc) since it is no longer used in the newer version of
software. Rimage removed the user account since it did not work with some
International Windows operating systems.
The system is now ready for operation. To get started making disc orders, refer to the
Software Suite 6 Getting Started Guide.
19
Appendix A - Licenses
Rimage End User License Agreement (EULA)
===============================
THIS IS A LEGAL AGREEMENT BETWEEN YOU, THE END USER ("YOU"), AND RIMAGE CORPORATION
("RIMAGE").
IMPORTANT-- READ CAREFULLY: THIS RIMAGE END-USER LICENSE AGREEMENT ("EULA") IS A LEGAL
AGREEMENT BETWEEN YOU (EITHER AN INDIVIDUAL OR A SINGLE ENTITY) AND RIMAGE FOR THE
RIMAGE SOFTWARE PRODUCT IDENTIFIED ABOVE, WHICH INCLUDES COMPUTER SOFTWARE,
ASSOCIATED MEDIA, AND PRINTED MATERIALS, AND MAY INCLUDE "ONLINE" OR ELECTRONIC
DOCUMENTATION ("SOFTWARE PRODUCT" OR "SOFTWARE"). BY INSTALLING, COPYING, OR OTHERWISE
USING THE SOFTWARE PRODUCT, YOU AGREE TO BE BOUND BY THE TERMS OF THIS EULA. IF YOU DO
NOT AGREE TO THE TERMS OF THIS EULA, PROMPTLY RETURN THE UNUSED SOFTWARE PRODUCT
(including all related manuals and documentation), TO THE PLACE FROM WHICH YOU OBTAINED IT FOR A
FULL REFUND WITHIN 30 CALENDAR DAYS OF ACQUIRING THE SOFTWARE.
Software License
================
1. GRANT OF LICENSE. Rimage grants to you the right to use multiple copies of the enclosed Rimage software
program (the "SOFTWARE") within the single building of the organization, to operate the Rimage system(s). You may
network the SOFTWARE and you may use it on more than one computer or computer terminal at the same time, if
and only if the computer, computer terminal, network, and SOFTWARE are used to operate the Rimage system(s).
2. COPYRIGHT. The SOFTWARE is owned by RIMAGE and is protected by United States copyright laws and
international copyright treaty provisions as well as other intellectual property laws and treaties. RIMAGE and its
suppliers shall continue to own and retain all right, title and (except as expressly licensed hereunder) interest in and
to the SOFTWARE, all copies or portions thereof, and any derivative works thereof (by whomever created).
Notwithstanding anything else, the SOFTWARE is licensed and not sold. Therefore, YOU must treat the SOFTWARE
like any other copyrighted material (e.g. a book or musical recording) except that YOU may either (a) make one copy
of the SOFTWARE solely for backup or archival purposes, or (b) transfer the SOFTWARE to a single compact disc
provided YOU keep the original solely for backup or archival purposes. All rights in the SOFTWARE not specifically
granted in this EULA are reserved by RIMAGE and its suppliers. YOU shall not copy the written materials
accompanying the SOFTWARE.
3. TRANSFER OF SOFTWARE. YOU may transfer the SOFTWARE and accompanying written materials on a
permanent basis provided YOU retain no copies and the recipient agrees to the terms of this Agreement. Any transfer
of the SOFTWARE must include the most recent update and all prior versions.
4. GENERAL RESTRICTIONS. YOU shall not (nor shall YOU permit anyone else to) directly or indirectly: (i) use or
copy (except as expressly set forth above), modify, transfer or distribute the SOFTWARE or any portion or copy
thereof; (ii) reverse engineer, disassemble, decompile or otherwise attempt to discover the source code or structure,
sequence and organization of the SOFTWARE or any portion thereof; (iii) rent, lease, or use the SOFTWARE or any
portion thereof for timesharing or service bureau purposes; (iv) remove or obscure any proprietary notices on the
SOFTWARE; (v) post or otherwise make available the SOFTWARE, or any portion thereof, in any form, on the
Internet or the World Wide Web; (vi) distribute copies of the SOFTWARE to others (electronically or otherwise); (vii)
use a previous version of the SOFTWARE after you receive a new version and are asked to discontinue using the
previous version; (viii) export or re-export the SOFTWARE in violation of any laws or regulations. AS A SPECIFIC
CONDITION OF THIS LICENSE, YOU AGREE TO USE THE SOFTWARE IN COMPLIANCE WITH ALL
APPLICABLE LAWS, INCLUDING WITHOUT LIMITATION COPYRIGHT LAWS, AND THAT YOU WILL NOT
COPY, TRANSMIT, PERFORM OR DISTRIBUTE ANY AUDIO, VIDEO OR OTHER CONTENT USING THE
SOFTWARE, NOR WILL YOU USE THE SOFTWARE TO COPY CONTENT WHICH THE SOURCE OF SUCH
CONTENT HAS OR HAS ATTEMPTED TO PUT IN A FORM WHICH IS COPY PROTECTED, WITHOUT
OBTAINING ALL NECESSARY LICENSES OR PERMISSIONS FROM THE OWNER OF THE CONTENT.
20
Limited Warranty
=============
LIMITED WARRANTY. For a period of ninety (90) days from the date YOU purchase the SOFTWARE (the
“Warranty Period”), RIMAGE warrants only that the SOFTWARE will perform substantially in accordance with the
specifications stated for the SOFTWARE in the accompanying written end-user documentation. THIS WARRANTY
SHALL NOT APPLY TO ANY SOFTWARE WHICH HAS BEEN ABUSED, MISUSED, DAMAGED IN TRANSPORT,
ALTERED, NEGLECTED, OR SUBJECTED TO UNAUTHORIZED REPAIR OR INSTALLATION, AS
REASONABLY DETERMINED BY RIMAGE.
CUSTOMER REMEDIES. Rimage's entire liability and your exclusive remedy shall be, at Rimage's option, either (a)
return of the price paid or (b) repair or replacement of the SOFTWARE that does not meet RIMAGE'S Limited
Warranty and which is returned to RIMAGE with a copy of your receipt. This Limited Warranty is void if failure of
the SOFTWARE or hardware has resulted from accident, abuse, or misapplication. Any replacement SOFTWARE will
be warranted for the remainder of the original warranty period or thirty (30) days, whichever is longer.
NO OTHER WARRANTIES. RIMAGE AND ITS SUPPLIERS DISCLAIM ALL OTHER WARRANTIES, EITHER
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE SOFTWARE
AND THE ACCOMPANYING WRITTEN MATERIALS. THIS LIMITED WARRANTY GIVES YOU SPECIFIC
LEGAL RIGHTS. FURTHER, RIMAGE DOES NOT WARRANT RESULTS OF USE OR THAT THE SOFTWARE IS
BUG FREE OR THAT ITS USE WILL BE UNINTERRUPTED. RIMAGE AND ITS SUPPLIERS DO NOT AND
CANNOT WARRANT THE RESULTS YOU MAY OBTAIN BY USING THE SOFTWARE. THIS DISCLAIMER OF
WARRANTY CONSTITUTES AN ESSENTIAL PART OF THIS EULA.
SOME STATES OR JURISDICTIONS DO NOT ALLOW THE EXCLUSION OF IMPLIED WARRANTIES OR
LIMITATIONS ON HOW LONG AN IMPLIED WARRANTY MAY LAST, SO THE ABOVE LIMITATIONS MAY
NOT APPLY TO YOU. THIS WARRANTY GIVES YOU SPECIFIC LEGAL RIGHTS AND YOU MAY ALSO HAVE
OTHER RIGHTS WHICH VARY FROM STATE TO STATE OR JURISDICTION TO JURISDICTION.
LIMITATION OF LIABILITY. NOTWITHSTANDING ANYTHING ELSE HEREIN, UNDER NO
CIRCUMSTANCES AND UNDER NO LEGAL THEORY, INCLUDING, BUT NOT LIMITED TO, TORT,
CONTRACT, NEGLIGENCE, STRICT LIABILITY, OR OTHERWISE, SHALL RIMAGE OR ITS SUPPLIERS BE
LIABLE TO YOU OR ANY OTHER PERSON (I) FOR ANY PUNITIVE, INDIRECT, SPECIAL, INCIDENTAL, OR
CONSEQUENTIAL DAMAGES OF ANY CHARACTER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR
LOST PROFITS, LOSS OF GOODWILL, WORK STOPPAGE, ACCURACY OF RESULTS, COMPUTER FAILURE
OR MALFUNCTION, OR DAMAGES RESULTING FROM YOUR USE OF THE SOFTWARE, OR (II) FOR ANY
MATTER BEYOND RIMAGE’S OR ITS SUPPLIERS’ REASONABLE CONTROL. RIMAGE'S AND ITS
SUPPLIERS’ MAXIMUM LIABILITY FOR DAMAGES OF ANY KIND WHATSOEVER ARISING OUT OF THIS
EULA SHALL BE LIMITED TO THE PURCHASE PRICE PAID BY YOU FOR THE SOFTWARE, EXCEPT WHERE
NOT PERMITTED BY APPLICABLE LAW, IN WHICH CASE RIMAGE'S LIABILITY SHALL BE LIMITED TO
THE MINIMUM AMOUNT PERMITTED BY SUCH APPLICABLE LAW. THE FOREGOING LIMITATIONS
SHALL APPLY EVEN IF RIMAGE HAS BEEN INFORMED OF THE POSSIBILITY OF SUCH DAMAGES.
SOME STATES OR JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF INCIDENTAL OR
CONSEQUENTIAL DAMAGES, SO THE ABOVE LIMITATION AND EXCLUSION MAY NOT APPLY TO YOU.
INDEMNITY. YOU agree that RIMAGE shall have no liability whatsoever for any use YOU make of the SOFTWARE.
YOU shall indemnify and hold harmless RIMAGE from any third party claims, damages, liabilities, costs and fees
(including reasonable attorney fees) arising from YOUR use of the SOFTWARE as well as from YOUR failure to
comply with any term of this EULA.
CONFIDENTIALITY. YOU agree to maintain the SOFTWARE and any data or databases contained therein in
confidence and that YOU will not disclose the SOFTWARE to any third party without the express written consent of
RIMAGE. YOU may not use the SOFTWARE except as set forth herein. You further agree to take all reasonable
precautions to preclude access of unauthorized persons to the SOFTWARE.
TERM AND TERMINATION. This license is effective until terminated hereunder. YOU may terminate the license at
any time by destroying the SOFTWARE (including the related documentation) together with all copies or
modifications in any form. RIMAGE will have the right to terminate the license granted herein immediately if YOU
fail to comply with any term or condition of this EULA. The license granted to YOU herein will terminate
automatically upon any breach of Section 4 of the above software license. Upon termination of this EULA for any
reason, YOU shall immediately stop using the SOFTWARE and shall destroy and remove from all computers, hard
drives, networks, and other storage media all copies of the SOFTWARE. YOUR obligations under this EULA shall
survive any termination of this EULA.
21
US Government Restricted Rights
===============================
If YOU are an agency, department, or other entity of the United States Government ("Government"), the use,
duplication, reproduction, release, modification, disclosure or transfer of the SOFTWARE, or any related
documentation of any kind, including technical data or related manuals, is restricted in accordance with Federal
Acquisition Regulation 12.211 for civilian agencies and Defense Federal Acquisition Regulation Supplement 227.7202
for military agencies. The SOFTWARE is commercial computer software and the related documentation is commercial
computer software documentation. The use of the SOFTWARE and related documentation is further restricted in
accordance with the terms of this Agreement, or any modification hereto. Rimage Corporation is located at 7725
Washington Avenue South, Minneapolis, MN 55439.
General.
------This EULA represents the complete agreement concerning this license between the parties and supersedes all prior
agreements and representations between them. This EULA may be amended only by a writing executed by both
parties. If any provision of this EULA is held to be illegal or unenforceable, that provision shall be limited or
eliminated to the minimum extent necessary to make it legal and enforceable and this EULA shall otherwise remain
in full force and effect and enforceable. The failure of RIMAGE to act with respect to a breach of this EULA by YOU
or others does not constitute a waiver and shall not limit RIMAGE's rights with respect to such breach or any
subsequent breaches. This EULA is personal to YOU and may not be assigned or transferred for any reason
whatsoever without RIMAGE's prior written consent and any action or conduct in violation of the foregoing shall be
void and without effect. RIMAGE expressly reserves the right to assign this EULA and to delegate any of its
obligations hereunder. This EULA shall be governed by and construed under Minnesota law (without regard to its
conflicts of laws provisions) as such law applies to agreements between Minnesota residents entered into and to be
performed within Minnesota. The sole and exclusive jurisdiction and venue for actions arising under this EULA shall
be the State and Federal courts in Hennepin County, Minnesota; YOU hereby agree to service of process in accordance
with the rules of such courts. The party prevailing in any dispute under this EULA shall be entitled to its costs and
legal fees.
EACH PARTY RECOGNIZES AND AGREES THAT THE WARRANTY DISCLAIMERS AND LIABILITY AND
REMEDY LIMITATIONS IN THIS EULA ARE MATERIAL BARGAINED FOR BASES OF THIS EULA AND THAT
THEY HAVE BEEN TAKEN INTO ACCOUNT AND REFLECTED IN DETERMINING THE CONSIDERATION TO
BE GIVEN BY EACH PARTY UNDER THIS EULA AND IN THE DECISION BY EACH PARTY TO ENTER INTO
THIS EULA.
Questions concerning this EULA should be sent to the address set forth below. Any notices or correspondence will
only be effective if sent to such address.
Rimage Corporation
Legal Department
7725 Washington Avenue South
Minneapolis, MN 55439
================================================================
This Rimage End User License Agreement (EULA) may include one or more of the following licenses.
================================================================
22
Rimage Java Sample License
Copyright (c) 2002 Rimage Corporation. All Rights Reserved.
Rimage Corporation ("RIMAGE") grants you ("YOU") a non-exclusive, royalty free, license to use, modify and
redistribute this software ("SOFTWARE") in source and binary code form, provided that:
i) this copyright notice and license appear on all copies of the SOFTWARE; and
ii) YOU do not utilize the SOFTWARE in a manner which is disparaging to RIMAGE.
The SOFTWARE is provided "AS IS," without a warranty of any kind. ALL EXPRESS OR IMPLIED CONDITIONS,
REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE HEREBY EXCLUDED. RIMAGE
AND ITS LICENSORS SHALL NOT BE LIABLE FOR ANY DAMAGES SUFFERED BY LICENSEE AS A RESULT
OF USING, MODIFYING OR DISTRIBUTING THE SOFTWARE OR ITS DERIVATIVES. NOTWITHSTANDING
ANYTHING ELSE HEREIN, UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, INCLUDING,
BUT NOT LIMITED TO, TORT, CONTRACT, NEGLIGENCE, STRICT LIABILITY, OR OTHERWISE, SHALL
RIMAGE OR ITS LICENSORS BE LIABLE TO YOU OR ANY OTHER PERSON (I) FOR ANY PUNITIVE,
INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY CHARACTER INCLUDING,
WITHOUT LIMITATION, DAMAGES FOR LOST PROFITS, LOSS OF GOODWILL, WORK STOPPAGE,
ACCURACY OF RESULTS, COMPUTER FAILURE OR MALFUNCTION, OR DAMAGES RESULTING FROM
YOUR USE OF THE SOFTWARE, OR (II) FOR ANY MATTER BEYOND RIMAGE’S OR ITS LICENSORS’
REASONABLE CONTROL. RIMAGE DISTRIBUTES THE SOFTWARE FREE OF CHARGE; RIMAGE'S AND ITS
LICENSORS’ MAXIMUM LIABILITY FOR DAMAGES OF ANY KIND WHATSOEVER ARISING OUT OF THIS
LICENSE SHALL BE LIMITED TO THE PURCHASE PRICE PAID BY YOU FOR THE SOFTWARE, WHICH IS
ZERO DOLLARS ($0.00), EXCEPT WHERE NOT PERMITTED BY APPLICABLE LAW, IN WHICH CASE
RIMAGE'S LIABILITY SHALL BE LIMITED TO THE MINIMUM AMOUNT PERMITTED BY SUCH APPLICABLE
LAW. THE FOREGOING LIMITATIONS SHALL APPLY EVEN IF RIMAGE HAS BEEN INFORMED OF THE
POSSIBILITY OF SUCH DAMAGES.
SOME STATES OR JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF INCIDENTAL OR
CONSEQUENTIAL DAMAGES, SO THE ABOVE LIMITATION AND EXCLUSION MAY NOT APPLY TO YOU.
YOU agree that RIMAGE shall have no liability whatsoever for any use YOU make of the SOFTWARE. YOU shall
indemnify and hold harmless RIMAGE from any third party claims, damages, liabilities, costs and fees (including
reasonable attorney fees) arising from YOUR use of the SOFTWARE as well as from YOUR failure to comply with any
term of this License.
This SOFTWARE is not designed or intended for use in on-line control of aircraft, air traffic, aircraft navigation or
aircraft communications; or in the design, construction, operation or maintenance of any nuclear facility. YOU
represent and warrant that YOU will not use or redistribute the SOFTWARE for such purposes.
This License represents the complete agreement concerning this license between the parties and supersedes all prior
agreements and representations between them. This License may be amended only by a writing executed by both
parties. If any provision of this License is held to be illegal or unenforceable, that provision shall be limited or
eliminated to the minimum extent necessary to make it legal and enforceable and this License shall otherwise remain
in full force and effect and enforceable. The failure of RIMAGE to act with respect to a breach of this License by YOU
or others does not constitute a waiver and shall not limit RIMAGE's rights with respect to such breach or any
subsequent breaches. This License shall be governed by and construed under Minnesota law (without regard to its
conflicts of laws provisions) as such law applies to agreements between Minnesota residents entered into and to be
performed within Minnesota. The sole and exclusive jurisdiction and venue for actions arising under this License shall
be the State and Federal courts in Hennepin County, Minnesota; YOU hereby agree to service of process in accordance
with the rules of such courts. The party prevailing in any dispute under this License shall be entitled to its costs and
legal fees.
Questions concerning this License should be sent to the address set forth below. Any notices or correspondence will
only be effective if sent to such address.
Rimage Corporation
Legal Department
7725 Washington Avenue South
Minneapolis, MN 55439
================================================================
23
The Apache Software License, Version 1.1
Copyright© 2000 The Apache Software Foundation. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the
following conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following
disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the distribution.
3. The end-user documentation included with the redistribution, if any, must include the following acknowledgment:
"This product includes software developed by the Apache Software Foundation (http://www.apache.org/)."
Alternately, this acknowledgment may appear in the software itself, if and wherever such third-party
acknowledgments normally appear.
4. The names "Apache" and "Apache Software Foundation" must not be used to endorse or promote products derived
from this software without prior written permission. For written permission, please contact [email protected]
5. Products derived from this software may not be called "Apache", nor may "Apache" appear in their name, without
prior written permission of the Apache Software Foundation.
THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING,
BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION
OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY,
OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE
GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
This software consists of voluntary contributions made by many individuals on behalf of the Apache Software
Foundation. For more information on the Apache Software Foundation, please see http://www.apache.org/.
Portions of this software are based upon public domain software originally written at the National Center for
Supercomputing Applications, University of Illinois, Urbana-Champaign.
================================================================
24
Sonic Software License - EXHIBIT B
SONIC SOFTWARE CORPORATION
CUSTOMER LICENSE AGREEMENT
Version 3.5
In accordance with Section 1.7, OEM Partner must include substantially all of the limitations of rights and protections
afforded to SSC and SSC’s licensors as those contained in Section I and the provisions of Section II.
Section I
· Scope of License.
1. Subject to the payment of applicable license fees, end user shall have a non-exclusive, non-transferable license to
use the Licensed Software in conjunction with the OEM Partner Product solely in connection with end user’s own
internal business operations subject to the licensing limitations as set forth within the agreement between the end
user and OEM Partner.
2. The Licensed Software may not be transferred, sold, assigned, leased, rented, licensed, sublicensed, redistributed, or
otherwise conveyed, in whole or part, by end user to another party without SSC's prior written consent. The license
grant automatically terminates if end user transfers possession of any copy of the Licensed Software or Updates to
another party. End user shall have no right to use the Licensed Software to provide time sharing services or operate a
service bureau for others. The Licensed Software is not designed or intended for use in on-line control of aircraft, air
traffic, aircraft navigation or aircraft communications; or in the design, construction, operation or maintenance of any
nuclear facility. End user warrants that it will not use or redistribute the Licensed Software for such purposes.
· Sonic Software's Rights.
3. The Licensed Software is a proprietary product of SSC, or its licensors (if any), and is protected by copyright law.
End user acquires only the non-exclusive right to use the Licensed Software and does not acquire any rights of
ownership in the Licensed Software upon which it is embodied. SSC, or its licensors (if any), shall at all times retain
all rights, title, and interest in the Licensed Software. Except as otherwise expressly provided for herein, end user
acquires no rights of any kind in or to any trade name, logo, or trademark of SSC, or SSC’s parent, subsidiaries,
affiliates, or licensors, or any product designation under which the Licensed Software was or is marketed and shall not
make use of the same for any reason except as expressly authorized herein or otherwise authorized in writing by SSC.
· Non-Disclosure; Copies; Alternations.
4. End user acknowledges that the Licensed Software is the valuable proprietary and trade secret information of SSC
or its licensors (if any). End user shall (i) limit use and disclosure of the Licensed Software to its employees and to its
consultants who agree to be bound by the terms of this Agreement; (ii) not provide or disclose any of the Licensed
Software to another party; (iii) take all reasonable precautions to maintain the confidentiality of the Licensed
Software. End user agrees not to cause or permit the reverse engineering, modification, decryption, extraction,
disassembly, copying, or decompilation of the Licensed Software, except as required by applicable local law or to
reproduce machine-readable object code portions for backup purposes and installation of new releases, under penalty
of license termination but not exclusive of any other remedies. End user may copy the Licensed Software for
installation or backup. End user may copy the documentation (in electronic format) accompanying the Licensed
Software solely for the purpose of facilitating end user’s use of the Licensed Software in accordance with, and subject
to, the terms and conditions contained herein. End user may not copy nor allow others to copy the Licensed Software
or Updates, or any portion thereof, for any other purpose. End user agrees not to remove any product identification,
copyright notices, or other notices or proprietary restrictions from the Licensed Software. End user agrees not to
disclose any benchmark results relating to its use of the Licensed Software without the prior written consent of SSC.
Limited Warranty.
5. THE LICENSED SOFTWARE IS PROVIDED TO THE END USER “AS IS,” WITHOUT WARRANTY OF ANY
KIND. SSC HEREBY EXPRESSLY DISCLAIMS ALL WARRANTIES AND CONDITIONS, EITHER EXPRESS OR
IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES AND REPRESENTATIONS OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT, WITH RESPECT
TO THE LICENSED SOFTWARE THERETO. SSC does not warrant that there are no discrepancies between the
Licensed Software and the Documentation, nor that errors cannot arise during the use of the Licensed Software.
Some jurisdictions do not allow for the exclusion or limitation of implied warranties, so the above limitations or
exclusions may not apply. No SSC employee, supplier, or agent is authorized to make any modification or addition to
this warranty.
· Limitation of Liability.
25
6. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, NEITHER SSC NOR ITS PARENT,
SUBSIDIARIES, AFFILIATES, OR LICENSORS SHALL HAVE LIABILITY TO END USER FOR ANY DAMAGES
SUFFERED BY END USER OR ANY THIRD PARTY AS A RESULT OF USING THE LICENSED SOFTWARE OR
DISTRIBUTING ANY PORTION THEREOF. IN NO EVENT SHALL SSC, ITS PARENT, SUBSIDIARIES,
AFFILIATES, OR LICENSORS, OR ANY OF THEIR RESPECTIVE SUPPLIERS BE LIABLE FOR ANY LOST
REVENUE, PROFIT OR DATA, OR FOR INDIRECT, PUNITIVE, SPECIAL, INCIDENTAL OR CONSEQUENTIAL
DAMAGES OF ANY CHARACTER, INCLUDING, WITHOUT LIMITATION, ANY COMMERCIAL DAMAGES OR
LOSSES, HOWEVER CAUSED AND REGARDLESS OF THE THEORY OF LIABILITY, ARISING OUT OF THE
USE OR INABILITY TO USE THE LICENSED SOFTWARE, OR ANY PORTION THEREOF, EVEN IF SSC, ITS
PARENT, SUBSIDIARIES, AFFILIATES OR LICENSORS AND/OR ANY OF THEIR RESPECTIVE SUPPLIERS
HAVE BEEN INFORMED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE
EXCLUSION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THE ABOVE LIMITATIONS MAY NOT
APPLY.
· Export Regulations.
7. The Licensed Software, including technical data, are subject to U.S. export control laws, including, without
limitation, the U.S. Export Administration Act and its associated regulations, and may be subject to export or import
regulations in other countries. End user shall not directly or indirectly export or re-export the Licensed Software, or
the direct product thereof, without first obtaining SSC’s written approval. End user agrees to comply strictly with all
regulations and acknowledges that it has the responsibility to obtain licenses to export, re-export, or import the
Licensed Software. The Licensed Software may not be downloaded, or otherwise exported or re-exported (i) into, or to
a national or resident of, Cuba, Iraq, Iran, North Korea, Libya, Sudan, Syria, or any country to which the U.S. has
embargoed goods; or (ii) to anyone on the U.S. Treasury Department’s list of Specially Designated Nations or the U.S.
Commerce Department’s Table of Denial Orders.
· U.S. Government Restricted Rights.
8. The Licensed Software is provided with RESTRICTED RIGHTS. Use, duplication or disclosure by the U.S.
Government is subject to restrictions as set forth herein and as provided in DFARS 227.7202-1 (a) and 227.7202-3 (a)
(1995), DFARS 252.227-7013 (c) (1) (ii) (Oct 1988) and 252.227-7014, FAR 12.212 (a) (1995), FAR 52.227-19 (June
1987), or FAR 52.227-14 (ALT III) (June 1987), as applicable. Contractor/manufacturer is Sonic Software
Corporation, 14 Oak Park, Bedford, MA 01730. Unpublished—all rights reserved under the copyright laws of the
United States.
Section II
Redistributable Software
OEM Partner shall be allowed to permit end user to redistribute the portion of the class libraries and other
components (or subsets thereof) expressly designated in the documentation as distributable (the “Redistributable
Software”), but only in conjunction with and as a part of a software application developed by OEM Partner (“OEM
Partner Product”) provided that OEM Partner:
(i) does not modify or alter the Redistributable Software in any way;
(ii) distributes the Redistributable Software in object code only;
(iii) does not use the name, logos, or trademarks of SSC, SSC’s subsidiaries and affiliates including, but not limited to
SonicMQ, or SSC’s licensors, to market such OEM Partner Product;
(iv) indemnifies, holds harmless, and defends SSC and its licensors, and their respective suppliers, from and against
any claims or lawsuits, including attorney’s fees, that arise or result from the use or distribution of such OEM Partner
Product;
(v) prohibits further distribution of the Redistributable Software, by any other party, including any end-user of such
OEM Partner Product without SSC’s prior written consent;
(vi) does not incorporate the Redistributable Software in any OEM Partner Product which is a design tool or other
application which provides substantially similar functionality as the Licensed Software;
(vii) includes in the About Box of the OEM Partner Product all copyright and other proprietary rights notices of SSC,
its licensors and their suppliers listed in the About Box of the Licensed Software;
(viii) does not remove or alter any agreement, trademark notice, copyright notice or other proprietary rights notice of
SSC, its licensors and their suppliers contained in the Redistributable Software or any portion thereof;
26
(ix) includes in the end-user agreement under which User distributes all or a portion of the Redistributable Software,
to be referred to in such end-user agreement as “THIRD PARTY COMPONENTS”, the provisions listed below which
are applicable to all THIRD PARTY COMPONENTS:
1. Disclaimer of Warranty. THE THIRD-PARTY COMPONENTS ARE LICENSED “AS IS” WITHOUT WARRANTY
OF ANY KIND, INCLUDING, WITHOUT LIMITATION, PERFORMANCE, MERCHANTABILITY, FITNESS FOR
ANY PARTICULAR PURPOSE OR NON-INFRINGEMENT. THE ENTIRE RISK AS TO THE RESULTS AND
PERFORMANCE OF THE THIRD-PARTY COMPONENTS IS ASSUMED BY LICENSEE. SHOULD THE THIRDPARTY COMPONENTS PROVE DEFECTIVE, LICENSEE ASSUMES THE ENTIRE COST OF ALL NECESSARY
SERVICING, REPAIR OR CORRECTION.
2. Limitation of Liability. SSC AND ITS LICENSORS, AND THEIR RESPECTIVE SUPPLIERS SHALL NOT BE
LIABLE FOR ANY DAMAGES SUFFERED BY LICENSEE OR ANY THIRD PARTY AS A RESULT OF USING OR
DISTRIBUTING THE THIRD-PARTY COMPONENTS. IN NO EVENT SHALL SSC, ITS LICENSORS, OR ANY OF
THEIR RESPECTIVE SUPPLIERS BE LIABLE FOR ANY LOST REVENUE, PROFIT OR DATA, OR FOR
INDIRECT, PUNITIVE, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES OF ANY CHARACTER,
INCLUDING, WITHOUT LIMITATION, ANY COMMERCIAL DAMAGES OR LOSSES, HOWEVER CAUSED AND
REGARDLESS OF THE THEORY OF LIABILITY, ARISING OUT OF THE USE OR INABILITY TO USE THE
THIRD-PARTY COMPONENTS, OR ANY PORTION THEREOF, EVEN IF SSC, ITS LICENSORS AND/OR ANY
OF THEIR RESPECTIVE SUPPLIERS HAVE BEEN INFORMED OF THE POSSIBILITY OF SUCH DAMAGES.
SOME STATES DO NOT ALLOW THE EXCLUSION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO
THE ABOVE LIMITATIONS MAY NOT APPLY.
3. Restrictions. The THIRD-PARTY COMPONENTS are confidential copyrighted information. Unless enforcement
is prohibited by applicable law, Licensee shall not modify, decompile, disassemble, decrypt, extract, or otherwise
reverse engineer the THIRD-PARTY COMPONENTS. The THIRD-PARTY COMPONENTS may not be leased,
assigned, sublicensed, or otherwise conveyed in whole or in part. The THIRD-PARTY COMPONENTS are not
designed, intended or licensed for use in on-line control of aircraft, air traffic, aircraft navigation or aircraft
communications; or in the design, construction, operation or maintenance of any nuclear facility. Licensee warrants
that it will not use or redistribute the THIRD-PARTY COMPONENTS for such purposes.
4. Export Regulations. The THIRD-PARTY COMPONENTS, including technical data, are subject to U.S. export
control laws, including the U.S. Export Administration Act and its associated regulations, and may be subject to
export or import regulations in other countries. Licensee agrees to comply strictly with all regulations and
acknowledges that it has the responsibility to obtain licenses to export, re-export, or import the THIRD-PARTY
COMPONENTS. The THIRD-PARTY COMPONENTS may not be downloaded, or otherwise exported or re-exported
(i) into, or to a national or resident of, Cuba, Iraq, Iran, North Korea, Libya, Sudan, Syria, or any country to which the
U.S. has embargoed goods; or (ii) to anyone on the U.S. Treasury Department’s list of Specially Designated Nations or
the U.S. Commerce Department’s Table of Denial Orders.
5. Restricted Rights. Use, duplication or disclosure by the United States government is subject to the restrictions as
set forth in the Rights in Technical Data and Computer Software Clauses in DFARS 252.227-7013(c)(1)(ii) and FAR
52.227-19(c)(2) as applicable.
· RSA Component
· The Licensed Software also contains technology of RSA Security, Inc., as such, the following additional provisions
apply: end user agrees not to remove, alter or destroy any proprietary, trademark or copyright notices placed upon or
contained within the RSA software, user manuals or any related materials or documentation. End user acquires no
rights of any kind in or to any RSA trademark, trade name, logo or product designation under which the RSA software
was or is marketed and shall not make any use of the same for any reason.
· THE RSA SOFTWARE AND TECHNOLOGIES LICENSED UNDER THIS AGREEMENT ARE SUBJECT TO
UNITED STATES EXPORT CONTROL LAWS AND REGULATIONS WHICH RESTRICT EXPORTS, REEXPORTS
AND DISCLOSURES TO FOREIGN PERSONS OF CRYPTOGRAPHIC ITEMS AND ARE ALSO SUBJECT TO
CERTAIN FOREIGN LAWS WHICH MAY RESTRICT THE EXPORT, REEXPORT, IMPORT AND/OR USE OF
SUCH ITEMS. PERFORMANCE OF THIS AGREEMENT IS EXPRESSLY MADE SUBJECT TO ANY EXPORT
LAWS, REGULATIONS, ORDERS OR OTHER RESTRICTIONS IMPOSED BY THE UNITED STATES OF
AMERICA, OR BY ANY OTHER COUNTRY OR GOVERNMENTAL ENTITY ON THE RSA SOFTWARE, PRERELEASE SOFTWARE OR OF INFORMATION RELATING TO EITHER. NOTWITHSTANDING ANY OTHER
PROVISION OF THIS AGREEMENT TO THE CONTRARY, LICENSEE SHALL NOT IMPORT, EXPORT, OR
REEXPORT, DIRECTLY OR INDIRECTLY, ANY RSA SOFTWARE OR PRE-RELEASE SOFTWARE OR
INFORMATION PERTAINING THERETO TO ANY COUNTRY OR FOREIGN PERSON TO WHICH SUCH
IMPORT, EXPORT, OR REEXPORT IS RESTRICTED OR PROHIBITED, OR AS TO WHICH SUCH COUNTRY,
GOVERNMENT OR ANY AGENCY THEREOF REQUIRES AN EXPORT LICENSE OR OTHER GOVERNMENTAL
APPROVAL AT THE TIME OF IMPORT, EXPORT, OR REEXPORT WITHOUT FIRST OBTAINING SUCH
27
LICENSE OR APPROVAL. LICENSEE UNCONDITIONALLY ACCEPTS FULL RESPONSIBILITY FOR
LICENSEE’S COMPLIANCE WITH THESE REQUIREMENTS.
· Sun Component
· Java Technology Restrictions. You may not modify the Java Platform Interface ("JPI", identified as classes contained
within the "java" package or any subpackages of the "java" package), by creating additional classes within the JPI or
otherwise causing the addition to or modification of the classes in the JPI. In the event that you create an additional
class and associated API(s) which (i) extends the functionality of a Java platform, and (ii) is exposed to third party
software developers for the purpose of developing additional software which invokes such additional API, you must
promptly publish broadly an accurate specification for such API for free use by all developers. You may not create, or
authorize your licensees to create additional classes, interfaces, or subpackages that are in any way identified as "java",
"javax", "sun" or similar convention as specified by Sun in any class file naming convention. The SSC Software includes
code licensed from RSA Data Security. Sun is a third party beneficiary to this Agreement.
· IBM Component(s)
· The Licensed Software contains IBM technology that is licensed to end user “AS IS” without warranty of any kind,
whether express or implied. Neither SSC nor IBM assume any liability for any claim that may arise regarding the use
of such IBM technology.
· APACHE Component
· The Licensed Software includes software developed by the Apache Software Foundation (http://www.apache.org/).
Copyright Ó 1999-2000 The Apache Software Foundation. All rights reserved. The names “Xerces” and “Apache
Software Foundation” must not be used to endorse or promote products derived from the Licensed Software without
prior written permission. Products derived from the Licensed Software may not be called “Apache”, nor may
“Apache” appear in their name, without prior written permission. For written permission, please contact
[email protected]
· GNU Component(s)
· No GNU public license or similar open source licenses contained within the Licensed Software shall be removed or
modified and no proprietary rights notices or agreements accompanying the Licensed Software shall be deleted.
================================================================
ActiveState Community License
Preamble:
The intent of this document is to state the conditions under which the Package may be copied and distributed, such
that ActiveState maintains control over the development and distribution of the Package, while allowing the users of
the Package to use the Package in a variety of ways. The Package may contain software covered by the Artistic
License. The ActiveState Community License complies with Clause 5 of the Artistic License and does not limit your
rights to software covered by the Artistic License.
Authorized electronic distributors of the Package are:
* Any ActiveState.com site
* Any complete, public CPAN mirror listed at www.perl.com
For more information on CPAN please see http://www.perl.com/.
Definitions:
"ActiveState" refers to ActiveState Tool Corp., the Copyright Holder of the Package.
"Package" refers to those files, including, but not limited to, source code, binary executables, images, and scripts,
which are distributed by the Copyright Holder.
"You" is you, if you're thinking about copying or distributing this Package.
28
1. You may use this Package for commercial or non-commercial purposes without charge.
2. You may make and give away verbatim copies of this Package for personal use, or for use within your organization,
provided that you duplicate all of the original copyright notices and associated disclaimers. You may not distribute
copies of this Package, or copies of packages derived from this Package, to others outside your organization without
specific prior written permission from ActiveState (although you are encouraged to direct them to sources from which
they may obtain it for themselves).
3. You may apply bug fixes, portability fixes, and other modifications derived from ActiveState. A Package modified in
such a way shall still be covered by the terms of this license.
4. ActiveState's name and trademarks may not be used to endorse or promote packages derived from this Package
without specific prior written permission from ActiveState.
5. THIS PACKAGE IS PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES,
INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTIBILITY AND FITNESS
FOR A PARTICULAR PURPOSE.
ActiveState Community License Copyright © 2000 ActiveState Tool Corp. All rights reserved.
29
Glossary
Here is basic terminology used in this setup guide. A more complete glossary is found
in the QuickDisc or QuickDisc Multi-Platform online helps.
Bridge Server: Server Application that runs as a service. Its job is to translate orders
submitted by legacy applications, such as Workstation or WinBurn, into XML orders
for the new messaging system.
Note: Bridge Server runs as a Windows service and it is only required if you
intend to use client applications like Workstation, or custom applications using
the POF and IOF file structure.
Client: The requester of a service.
Client Application: An application requesting for a Control Center to process the
order. These include QuickDisc, QuickDiscJ, Workstation, or a custom application.
Control Center: Refers to the PC that is connected to an Autostar II, Protégé II, Amigo
II, Desktop 4500, etc… This computer will also be running the Rimage Server
applications.
Custom Application: A custom application created by a programmer to submit orders
to the Rimage Servers. A custom application could be generated by using one of
Rimage PowerTools such as XML-API and Network PublisherJ.
File-Based Server: The Rimage Image Server and Production Server versions prior to
version 6.0 that use orders written in the IOF and POF files.
Group: A collection of users used to simplify user management. You can have both
Local and Global groups.
HOST: This is sometimes referred to as the Computer Name. A host name could be a
NetBios or Domain name.
Image Server: A Rimage Server Application that builds CD or DVD image files to be
recorded.
Image File: A disc file that is built by the Image Server and is ready to be recorded.
Local: Meaning the place at which you are currently working.
Local User: This refers to a User Account that was created on the PC that you are
working from.
Message-Based Server – The Rimage Image Server and Production Server version 6.0
that process message-based order requests. The message-based orders are XML files
embedded in a message.
NetworkPublisher Multi-Platform: A Rimage application that provides an order
interface so a custom client application can submit a simple text file to initiate an
order. Previously called " NetworkPublisherJ".
NetBIOS: Network Basic Input-Output System.
Production Server: A Rimage Server Application that controls the autoloader,
recording and printing of discs.
ProNET: A configuration that runs the Rimage software servers as an NT service.
The benefit is the users do not have to log in with administrator rights. Since the
30
Production Server is operating as an NT service, and there is no graphical user
interface, the user can change the parameters from the Configuration Center.
QuickDisc: Client Application that is used to create jobs for the server applications.
QuickDisc Multi-Platform: Client Application that is used to create jobs for the server
applications. (Previously called "QuickDiscJ".)
Remote: Meaning at a different location it is not the current location that you are
working from. This could be 10 feet away or 1,000 miles away.
Rimage Server Applications: These software applications include Production Server,
Image Server, Bridge Server, and Messaging Server.
Server: The provider of a service. A server does not mean it has to be a Windows
Server running a Server Operating System.
Server Applications: This includes Production Server, Image Server, Bridge Server,
and Enterprise Messaging Server.
Source Files: The raw files and folders that are to be burned on to discs. Recommended
location to store source files is on a High Performance File Server.
Standalone Server: This is a scenario where a Rimage producer system is all running
in one Computer see scenario #1.
Working folder: Folder that is to be used as a central location for the Server & Client
applications.
Workgroup Environment: Usually a small network without Domain Controllers. Also
known as a Peer-to-Peer network.
Workstation: a Rimage Client Application used to create jobs for the server
applications.
31
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement