HELIOS Mac OS X Release Notes
Release notes for HELIOS products on Mac OS X Version 10.1
Getting acquainted with HELIOS
HELIOS provides very powerful server products and add-ons for prepress customers. These products are very feature rich. First time users will find a good starting point and an overview about what our products can do for them in our product presentation on the HELIOS web site:
http://www.helios.de/products/productshows.html
Differences between HELIOS server products and Mac OS X Server 10.1
Some information about unique HELIOS benefits for file and print services versus Apple services on Mac OS X can be found at:
http://www.helios.de/news/news01/ES_PCS-on-MacOSX2.html


December 2001
Setting up this release
Installing HELIOS products on
Mac OS X
Prerequisites:
For the installation of the HELIOS software it is recommended to log in as a user with administrative rights. Else you may be asked to authorize again when changing e.g. access rights in the system. Administrative rights can be verified as follows:
In System Preferences > Users click Edit User-, select the Password tab and ensure that Allow user to administer this machine is checked.
Making TCP/IP and AppleTalk active
Before you can start the installation it is required that one interface is configured for both AppleTalk and TCP/IP. Use the Preferences panel and select Network to configure TCP/IP and AppleTalk in the respective tabs (Fig. 1).

Important: A correct IP number entry must be specified once and then saved in the Router: field of the TCP/IP tab. Otherwise TCP/IP multicasts will not work.

Fig. 1: Network interface settings

Note: Whenever AppleTalk is not active, starting the HELIOS services (see "HELIOS Services") will automatically enable it on the first network interface "en0".

Insert the HELIOS CD-ROM in the Mac OS X computer and double-click the "HELIOS Network Installer" CD icon, which appears on the desktop.
In the "HELIOS Network Installer" window double-click the "mac-os-x" folder.
Start the installer by double-clicking the "HELIOS.mpkg" icon (Fig. 2).
Fig. 2: Starting the "HELIOS.mpkg" installer

Then click on the padlock symbol in order to be allowed to make changes (even if you are already logged-in as "root").
You must authorize again to install the software. If you have administrative rights on the machine you can use your name and password in the authentication dialog (Fig. 3).
Fig. 3: Install HELIOS - Authorization

The HELIOS Installer shows the Introduction window with the Welcome to the HELIOS Installer message (Fig. 4).
Click Continue to proceed.
Fig. 4: Install HELIOS - Introduction

The Read Me window (Fig. 5) shows important user information which you should read carefully.
During the installation, Go Back lets you jump one step back, e.g. if you need to see the Introduction window again.
Click Continue to proceed.
Fig. 5: Install HELIOS - Read Me

The next window, License, displays the Software License Agreement which you should read carefully.
Follow the instructions and, if you accept the terms and conditions of the software license agreement, click Agree Otherwise leave the installation program with Disagree.
A destination where to install the HELIOS software to
must be selected. The Select Destination window displays all available volumes (Fig. 6). For the installation of the HELIOS Services software, 100 MB of disk space are required. In the example, the selected volume named
"Mac OS X" has 4.9 GB of disk space available.
Select the "Mac OS X" boot partition.
The HELIOS product installation is supported on both HFS and UFS Mac OS X boot partitions.

Important: If the HELIOS products are not installed on the same disk partition as Mac OS X the HELIOS software will not work!

Select the volume and click Continue to proceed.
Fig. 6: Install HELIOS - Select Destination

The next dialog, Installation Type, lets you select whether you want to run an easy or a customized installation.
In the Easy Install window (Fig. 7) click Install for a complete installation. This requires that you have all HELIOS software licenses. Or choose Customize to install only those components of the software which you have a license for.
Fig. 7: Install HELIOS - Installation Type

In the Custom Install window (Fig. 8) mark the components (via checkboxes) of the HELIOS software which you intend to install and click Install. Please note that the HELIOS Base and HELIOS Base Data packages are required and therefore cannot be deselected.
Product
Description
EtherShare
Highest-Performance Server for Macintosh clients
PCShare
Highest-Performance Server for Windows clients
EtherShare OPI
Server-based OPI image replacement with color separation and proof printing support
EtherShare required
PDF Handshake
PDF Printing - PDF OPI and Imposition - Create PDF Server - PDF Internet Printing
EtherShare required
Print Preview
Convenient & reliable production check up to the last minute
EtherShare & PDF Handshake required
Documentation
User manuals and data sheets (PDF)

Fig. 8: Install HELIOS - Installation Type (Custom)

After you have clicked Install you are informed that a restart of the computer is required after the installation.
Click Continue Installation if you want to install the software now (Fig. 9).
Then, the Install Software window opens and a status bar informs you about the progress of the software installation. When the installation is done, the Finish Up window appears (Fig. 10) and the software commences a count-down for automatically reboot the computer, starting at 30 seconds.
Otherwise, click Restart to reboot the computer now.
If there should occur any error during the installation, the Console.log, as described in Error messages and Fig. 33, provides information on what happened.
Fig. 9: Install HELIOS - Continue Installation
Fig. 10: Install HELIOS - Finish Up

After the reboot all HELIOS products will be started automatically.
Fig. 11: Install HELIOS - Applications folder

HELIOS applications in the "Applications" folder
During the installation two applications, "HELIOS Services" and "EtherShare Admin", as well as the folder
"Admin Plug-Ins" are copied into the "Applications" folder on your Mac OS X volume (Fig. 11).
Using EtherShare Admin under Mac OS X
A double-click on the "EtherShare Admin" icon opens the application. A splash-screen appears (Fig. 12) which disappears after a short while, or instantly when you log in to the program.
Fig. 12: EtherShare Admin - Starting the Admin
Fig. 13: EtherShare Admin - HELIOS login dialog

Log in to EtherShare Admin via File > Login.
Holding down the option key during File > Login switches between the HELIOS login dialog (Fig. 13) and the conventional Mac OS X Connect to Server dialog (Fig. 14).
Fig. 14: EtherShare Admin - Connect to Server dialog

"root" and "demouser"
During the installation of EtherShare Admin the users "root" and "demouser" are created. Both of them come without any password, i.e. their AFP-password field is empty. This means a significant lack of security (anybody can log on to the server as user "root" without needing to know the password), and so you should specify a password for "root".

Note: For your own security, provide your user accounts with passwords to prevent them from unauthorized access and abuse!

In order to set a "root" password do the following:
Log in to EtherShare Admin with User Name: "root" (leave the Password: field empty). Then open Lists > Users, select the "root" entry from the list and double-click it.
The Users:root dialog window opens (Fig. 15).
Specify a password for "root" in the Password: field and click Save.
Fig. 15: EtherShare Admin - Users:root dialog

On specifying the password, EtherShare Admin prompts for the new password to be entered once again. This ensures that no typing mistakes have been made. After clicking OK the password will be allocated to user "root".

Note: The password field is always shown empty, even if the user has already allocated a password.

Note: By default, the "root" login is disabled on a Mac OS X machine. Once the "root" password is specified with EtherShare Admin, the "root" login is enabled automatically.

Then set passwords for all other existing users, or add new users (passwords set under EtherShare Admin or PCShare Admin are valid for Mac OS X as well).

Important: Note that if a password is modified via Mac OS X tools our additional password file is not changed.

Note: An optional remote user login (telnet/rlogin) needs to be enabled in "/etc/inetd.conf".
To enable a remote "root" user login the "/etc/ttys" file needs to be configured (insecure option).

HELIOS Services
"HELIOS Services" is a GUI application designed for entering HELIOS software licenses, and for easily starting and stopping HELIOS processes.
Double-click the "HELIOS Services" icon in the "Applications" folder.
The HELIOS Services window appears (Fig. 16) providing information on the HELIOS products status when you click Status. In the example shown below there are currently no HELIOS services running.
Fig. 16: "HELIOS Services" - View Status

Choose the Licenses tab within the "HELIOS Services" window.
The field Machine ID: shows the machine ID of your
Apple computer (Fig. 17). In the other field all HELIOS product licenses are displayed, with Product name, Serial Number, and Expiration Date (Note that the entry in the Expiration Date column remains empty if you are running a full license.).
Fig. 17: "HELIOS Services" - View License

Click View License File- to see the complete license file (Fig. 18).
This may be convenient if you wish to view and extract serial numbers etc. with "copy and paste".
Click Add License- to add a new HELIOS product license.
Fig. 18: "HELIOS Services" - View License
Fig. 19: "HELIOS Services" - Add License

An extra dialog window opens (Fig. 19) which lets you choose the desired product from the pop-up menu Product:, and lets you enter the serial number (Serial: ), the number of Units:, and the Checksum:. As mentioned before, if you are running a full license of the HELIOS products, leave the Expires: field empty. Otherwise, the expiration date of the demo license must be entered in the Expires: field as well.

Note: The EtherShare and PCShare products are licensed for use on a single computer system ("server"). The server has a unique machine identification ("HELIOS MachID") which is provided by a HELIOS USB dongle. The software can only once be licensed for a given USB dongle (MachID). Compare Fig. 17 and 18.

Demo mode
If you do not enter any Activation Key the HELIOS product you have installed will run in a 3-hour demo mode only.
Fig. 20: "HELIOS Services" - Starting services

Click Start within the Status tab window.
Starting the HELIOS services
The Messages: box shows the information that HELIOS services are being started. When all available services are running the display shows Done. (Fig. 20).
A click on the Status button then reveals a listing of all HELIOS processes (Fig. 21) and gives information about their name (Service), their Status, their process ID number (PID), date and time of starting (When), and - if a process has been started more than once - the number of Restarts.
Fig. 21: "HELIOS Services" - View process status

"HELIOS Services" has a feature that lets you specify a shutdown message and the time span to shutdown (Fig. 22).
Specify the shutdown message in the Shutdown message: text box. In the Time to shutdown (minutes): field enter the time after which the services should be stopped.

Note: If you specify "0" for the time to shutdown the services will be stopped immediately.
Fig. 22: "HELIOS Services" - Specifying shutdown options

Stopping the HELIOS services
In order to stop all HELIOS services on Mac OS X do the following:
Click Stop within the Status tab window.
The Messages: box then displays the information that all HELIOS services are being stopped, (Fig. 23).
Fig. 23: "HELIOS Services" - Stopping services

During the installation, the HELIOS software is registered in Mac OS X's "StartupItems" folder for starting automatically at the next OS boot.
Starting the HELIOS software manually
Starting all HELIOS processes on the server manually from a remote shell is done via "/usr/local/helios/bin/start-helios".
# cd /usr/local/helios
# bin/start-helios

Important: Due to a problem in the Mac OS X system library, you must not use the command "bin/start-helios" from the local shell on the Mac OS X machine directly. Instead, use the "exechelper" command:

# cd /usr/local/helios
# sbin/exechelper bin/start-helios

Stopping the HELIOS software manually
Stopping all HELIOS processes on the server is done via the command "/usr/local/helios/bin/stop-helios now".
# cd /usr/local/helios
# bin/stop-helios now
Setting up disk partitions
All HELIOS data volumes should be on a UFS disk partition to allow special characters like "umlauts", etc. Via UTF-8 encoding, UFS will be the only supported volume format. HELIOS volumes on HFS will work as well, but without the support of special characters, e.g. "umlauts".
HFS support should be OK for a simple test drive. The real work, however, should only be done on UFS disk partitions.
Setting up new UFS partitions (overwriting all disk data)
When Mac OS X is started from CD-ROM a menu allows you to partition your disk.
From the menu bar select Installer and then the item
Open Disk Utility... (Fig. 24).
Fig. 24: Open Disk Utility- entry

The Disk Utility window opens and lets you specify the characteristics of the disk you want to partition.
Choose the Partition tab and specify a name for the new partition (or rename it) in the Volume Information section. In the Format pop-up menu select HFS or UFS partition, and specify its desired size in the Size: field. Click OK.
Fig. 25: Erasing disk after booting from Mac OS X CD-ROM

Switching an HFS partition to UFS (preserving data of other disk partitions)
If you have more than one HFS partition on your disk and want to switch one partition to the UNIX File System (UFS) without deleting the data from other HFS partitions, do the following (using the startup disk):
Boot from the Mac OS X CD-ROM, select Installer from the menu bar and then the item Open Disk Utility...
The Disk Utility window (Fig. 25) opens allowing you to specify the characteristics of the disk you want to erase.
Choose the Erase tab, select UNIX File System in the Volume Format pop-up menu, specify a name for the partition (we recommend not to use space characters!) in the Name: field and click Erase.
Creating a UFS Test Drive Image
If you need to have a UFS-partitioned volume e.g. for test purposes, and you do not want to change the partition of an already existing non-UFS volume, you can set up a disk image volume with the desired specifications.

Note: Creating a UFS volume as described here is just a simple workaround since the performance of a volume created in such a way is good but worse than that of a native UFS volume.

Open Applications > Utilities > Disk Copy and select
Image > New blank image- from the pop-up menu.
The configuration window New Blank Image opens.
Specify a name for the volume image file in the Save as: field, choose a location from the pop-up menu Where:, specify a Volume Name:, the size of the volume and select UNIX File System from the Format: pop-up menu (Fig. 26).
In the example the image file is saved as "TestImage" on the desktop of the Mac OS X host. The volume name has been specified as "Test UFS Volume" with a size of 40 MB. The format of the drive is UFS (UNIX File System).
When all settings have been set to meet your requirements click Create.
Fig. 26: New Blank Image configuration window

The disk image file "TestImage.dmg" and the drive
"Test UFS Volume" appear on the desktop (Fig. 27).
Fig. 27: Image file and newly created drive "Test UFS Volume" on Mac OS X desktop

Of course you can specify any location for the disk image file. After double-clicking this file the virtual drive will always appear on the desktop.
The next part describes how the virtual UFS drive can be configured as a HELIOS volume.
Configuring HELIOS volumes
Start EtherShare Admin and open Lists > Volumes. Then open File > New to configure the volume (Fig. 28).
Fig. 28: Configuring volume in EtherShare Admin

In the Directory: field enter the volume path, beginning the string with "/Volumes/" (Fig. 29). Specify an AFP Name: and - if required - a Password: and the AFP Charset:.
If you need to make the volume visible to Windows clients as well, activate the Windows visible checkbox, enter the SMB Name: and select the required character set from the SMB Charset: pop-up menu.
A description of the further checkboxes and fields can be found in the chapter "Server preferences" at the end of this book.
After clicking Save the volume is provided in the specified directory path and can be mounted.
Fig. 29: EtherShare Admin Volumes list

Miscellaneous
Switching to root user id shell
Log in as a user with "System Administrator" rights, which
is set via System Preferences > Users.
Open Applications > Utilities > Terminal and enter:
$ sudo sh
Enter your user password, now you should get the following "root" prompt:
#
The "id" command should now show the user id=0 (root).
Core dumps on Mac OS X
By default Mac OS X will not save or report application core dumps. To enable this add the following two lines to the file "/etc/hostconfig" (the administrator should always be able to monitor all problems on a desktop/server system):
# /etc/hostconfig
COREDUMPS=-YES-
CRASHREPORTER=-YES-
This change can only be done as user "root" (or user id=0). The file can be edited as "root" with the simple editor, e.g.:
# pico /etc/hostconfig
All core files will be saved to the "/cores" directory. To avoid core files filling up your disk, old core files should be removed from time to time.

Important: In order to make the changes valid you must reboot the computer!

Booting in single-user mode
Take the following steps to boot in single-user mode:
Hold down the key combination "Command-S" during booting from CD-ROM.
NetBIOS and PCShare
Due to a Darwin kernel problem with the hardware checksum calculation on UDP broadcast packets, the NetBIOS name server of PCShare will not work properly. To make the NetBIOS name server working, UDP checksums are turned off if PCShare is installed. Please read the script
"/usr/local/helios/etc/startstop/40cksum" for more information and a possible alternative. If the problem is fixed in the Darwin kernel, this script can be removed.
Documentation for HELIOS products
Mount the "HELIOS Applications" volume from the
Mac OS X server and open the folder "Documentation".
es26-e.pdf
EtherShare documentation
ps30-e.pdf
PCShare documentation
opi21-e.pdf
EtherShare OPI documentation
pdfh20-e.pdf
PDF Handshake documentation
ppv11-e.pdf
Print Preview documentation
ReleaseNotes-MacOSX.pdf
HELIOS products on Mac OS X

Welcome message and shutdown message
You can specify a welcome message to output on Macintosh workstations when they log on to EtherShare. There are no preferences to be specified for this feature. Instead, create two text files "login.msg" and "shutdown.msg" with a UNIX editor (or with SimpleText on a Macintosh), and store them in "/usr/local/helios/public/MacOS" (the "MacOS" folder of the Macintosh volume "HELIOS Applications"). The messages will then be used automatically by the File Server during login and shutdown.

Note: If you are running a demo copy of EtherShare on your server you cannot alter the default welcome message.

A maximum of 199 characters will be displayed (excess characters are truncated). If you want to include national accented characters such as "umlauts" in your messages, use SimpleText to write them: since the Umlaut codes are stored here in Macintosh binary format, it is a lot of work to enter the right codes with a UNIX editor.
Specifying host names in EtherShare Admin
As a new feature in EtherShare Admin you can specify EtherShare and PCShare server names for the server you are logged-on to.
In EtherShare Admin open Lists > Server Preferences. In the Macintosh Server Name: and Windows Server Name: respectively enter the name with which you want the server to appear in the network to Macintosh and PC clients and click Save. Then restart "HELIOS Services" in order to make the new names available for EtherShare and PCShare clients.
Service Location Protocol (SLP)
Our software supports the Service Location Protocol (SLP), which allows users under UNIX systems to find available services without any knowledge of host names. Under Mac OS X SLP is preferred over the old AppleTalk Name Binding Protocol (NBP).
SLP is based on three different kinds of agents:
User Agents (UA)
This is basically the software that the user or a service uses to register, deregister and find services. Examples for such User Agents are the "slptool", which you can find in
"/usr/local/helios/bin", or the Network Browser under
Mac OS 9.x or Mac OS X.
Service Agents (SA)
An SLP Service Agent is responsible for storing information of services on a single system, answers User Agent calls and informs Directory Agents of local information changes. Examples of such Service Agents are HELIOS SLP-servers on systems with a single network interface, or Mac OS 9.x and Mac OS X clients with activated File Sharing.
Fig. 30: Server with 1 NIC

Directory Agents (DA)
These agents act as a central repository of a network. It collects the information of Service Agents to build a complete database of the whole network, which can be accessed by User Agents. A HELIOS SLP server on a computer with several network interfaces becomes Directory Agent by default.
Fig. 31: Server with 2 NICs

Service and Directory Agents are initiated by the same program ("slpsrv"), that can be configured to run as a Service or Directory Agent.
In the absence of a Directory Agent, User Agents that look for services will have to ask for Service Agents. Every Service Agent that sends a reply will then be asked for its local services of a certain kind. If a Directory Agent is available a User Agent will only contact the Directory Agent directly and ask for known services. Therefore Directory Agents can significantly reduce network traffic.
But there is a catch: if a Directory Agent was known, and did not deregister itself, User Agents will always try to contact the Directory Agent directly. If a Directory Agent cannot react (due to a server crash or network problems) they will wait for the connection to time out (which can take several minutes) before they start to look for other Directory or Service Agents.
Another difference between Directory and Service Agents arises on systems with multiple network interfaces. By default "slpsrv" works on such systems as a Directory Agent, so it gathers the services on each connected network, and computers in one network can use services in another network. If you want to configure "slpsrv" to work as a Service Agent, so that computers cannot see services in connected networks, please put an empty text file with the name "slp.conf" into the "var/conf" subdirectory of our product directory (normally "/usr/local/helios") and enter the text "net.slp.isDA = false" into this file.
Fig. 32: Service Location entities in the Mac OS X Connect to Server dialog

Using HELIOS printer queues with Mac OS X
Printing from remote Mac OS X client machines to the HELIOS server:
Open Applications > Utilities > Print Center.
Option 1:
In the Printer List window click Add Printer- and select AppleTalk from the pop-up menu.
Option 2:
In the Printer List window click Add Printer- and select LPR Printers using IP (using the HELIOS server TCP/IP address and printer name).
Choosing a printer queue directly on the HELIOS server:
Open Applications > Utilities > Print Center.
Option 1 (Remote LPR):
In the Printer List window click Add Printer- and select
LPR printers using IP (using the TCP/IP loopback address "127.0.0.1") from the pop-up menu.