- The audio on my H-P is either not working properly or is
significantly delayed. What can I do?
- You must have both of the following system patches in order for audio to
function correctly:
- Audio Kernel Patch: PHKL_5059
- Low-latency Aserver (version 3.16) Patch: PHSS_5073
These patches are available on the MDL CD-ROM (version 2.9.95)
- I have Communique! 4.00 and the audio on my Sun is
periodically inoperative. What is the cause?
- This is a problem that was fixed with Communique! 4.01.
- The audio on my Sun is delayed. Is there a patch available?
- Some systems, especially the SPARC 5, are configured with the audio
buffer size set to too large a value. To reduce the audio buffer size, use the
"install.buf" utility found in the "support" directory of the MDL
CD-ROM (version 2.9.95)
- I have a Solaris 2.4 system and a Parallax board. When I start the
video from the TV Tool in Communique!, the Local Viewer does not display the colors
correctly? What can be done to correct it?
- Parallax drivers for Solaris 2.4 differ from those for Solaris 2.3. In performing system
upgrades, it is possible for the new drivers to be installed without creating the new
video device. In these cases, the following device files must be removed:
/dev/fbs/tvtwo0
/devices/iommu@0,10000000/sbus@0,10001000/PGI,tvtwo@1,0:tvtwo0
After removing the device files, the drivers must be reinstalled.
There are also cases of mismatched colors occurring on fresh installations. This
problem has been fixed and will be available with the Communique! 4.1 release.
- How can I run Communique! on an interface other than the
built-in Ethernet (such as ATM)?
- Beginning with version 4.01, Communique! can be directed to bind to any interface
installed in a system with the configuration file:
/etc/MDL/interfaces
If this file does not exist, it (and the path to it if necessary) can be created. The
file needs only the hostname (or the IP address) associated with the interface that Communique!
should use.
Once this has been done, it will be necessary to restart the Registrar and the
Conference Engine. This is usually accomplished by running the ISSlay script and then
restarting Communique!. Some copies of Communique! 4.0 also have this
functionality. For other copies, the Ethernet interfaces will have to be temporarily
disabled with:
ifconfig [interface name] down
while Communique! is being brought up.
- When I click on the "From Network" button in Communique!
4.0's "Start Conference" window, no names appear in the "Addresses"
list. Why is this so?
- Network scans rely on broadcast addresses for locating potential conferees. Any machine
running the Conference Engine and Registrar will respond to the scan provided their
broadcast addresses are configured properly. If there are no responses to a network scan,
the broadcast configuration can be easily checked with:
ping -s [broadcast address]
Every machine attached to the LAN should respond. If 8 machines are connected
to the LAN, there should be 8 responses (including the machine that issued the ping). If
this is not the case, then the network configuration will need to be checked. The most
common problem is inconsistent values for netmasks and broadcast addresses.
- Why are the colors of a SHAREd application appear different on
the remote side(s)?
- When the remote side(s) experience(s) incorrect colors, it is due to the way that the
X-window system handles colormaps. Client applications simply request a color index number
from the server rather than an actual color (i.e. color #10. For remote servers, there is
no way to guarantee that color #10 is the color the application needs because the server
set up the colors on the local side only. There are, however several options that may
allow you to work around this. If your application provides an Xresource or command line
option to force it into using a private color map, do so. Running in a private colormap
will correct the color-indexing problem because it will rely on internal colors rather
than the default X colormap. Some applications can't be "forced" into using a
private colormap, but will do so when not enough colors are available. In this case you
can run an external program to allocate all the extra colors before running the
application. This will then cause a private colormap resulting in correct colors on the
remote and local sides. ISShareFix does this.
- Why doesn't the White Board support 24-bit images anymore?
- The White Board will still read 24-bit images, but they will be dithered down to 8-bit.
This was done to maximize performance, especially when conferencing with PCs. The Video
and Graphics Tools still support 24-bit displays, which provide some level of workaround.
We now have the Imager available, which is a WhiteBoard that supports 24-bit displays and
includes a Slide Show feature. For details on the Imager, contact your local MDL Sales Representative.
- The White Board on Communique! version 4.0.0 running
under Solaris 2.3 hangs if I double-click on it while the "Load Image" window is
open. What do I do?
- Only local control of the White Board is lost. If in a conference, the White Board
receives input for the other members. The workaround is as follows:
- Find the White Board Plugin process by issuing the command:
ps -ef | grep ISWhiteBoardPlugin
to get the process id of the WhiteBoard.
- Kill the White Board Plugin by issuing the command:
kill PID
Where PID is the number of the process returned by the "ps" command.
- Reopen the White Board via the White Board button.
- If in a conference, have the other members synchronize the current page (found under the
"Edit" menu.
- How do I boot my H-P system in single-user mode?
- To boot an HP-UX 9 system into single user mode, the following 3 steps are necessary:
stop the boot selection process, run the initial system loader, and boot.
- During the initial boot phase of the system, the H-P will search for a boot device.
Press and hold the [Esc] key until you get a prompt.
- Enter the following command to boot from the primary disk (p0):
boot p0 isl
- You are now at an "ISL>" prompt. Enter the following command to boot into
single-user mode on the default kernel
hpux -iS /hp-ux
- Should your kernel be corrupted, the default backup kernel name is SYSBCKUP. To boot
from it, use it's path in place of /hp-ux
hpux -iS /SYSBCKUP
- How do I make BOS diskettes for my AIX system?
- There are now 4 diskettes making up the diskette boot/install package. These are:
- BOS boot diskette
- Optional display extension diskette
- Display diskette
- BOS Install/Maintenance diskette
Diskettes 1, 3, & 4 are roughly equivalent to the diskettes used in AIX v3.1.
Diskette 2 was added to the package in order to support the POWER Gt3 and POWER Gt4
displays (which are on IBM 250 systems) as console devices during the install process. It
also contains the model 730 graphics display support.
The diskettes used in the following procedure must be formatted as high-density (1.44
MB). (Note: If any of the images do not fit on 1 diskette, check the density and format of
the diskette.)
If any of the following "mk" commands are not in your path, look in
/usr/sbin.
- Login in as root
- To create the BOS boot diskette, insert a high density diskette in /dev/rfd0 then enter:
bosboot -a -d /dev/rfd0
- To create the optional display extension diskette (if needed), insert another
high-density diskette in /dev/rfd0 then enter
mkextdskt
- To create the display diskette, insert another high-density diskette in /dev/rfd0 then
enter
mkdispdskt
- To create the BOS Install/Maintenance diskette, insert another high-density diskette in
/dev/rfd0 then enter
mkinstdskt
- How do I boot my RS/6000system in single-user mode?
- You will need BOS diskettes in order to do this, to make these diskettes, see previous
question.
- Power down your machine if it is not already off.
- Turn key to the "Service" position.
- Insert the BOS Boot diskette (disk 1)
- Power on system.
- The machine will boot-access the floppy drive. When the LED display reads
"c07", eject and remove disk 1.
- Insert the Optional Display Extension diskette (disk 2). The system will automatically
recognize and read this disk. When the LED display reads "c07", eject and remove
disk 2.
- Insert the Display diskette (disk 3). The system will automatically recognize and read
this disk. When the LED display reads "c07", eject and remove disk 3.
- You should see characters on the terminal display. Follow the instructions to default
the terminal. It will prompt you to insert disk 4.
- You will see a menu of choices. Select "4 - Start a limited function maintenance
shell".
- At this point there is no disks mounted. To mount the disk enter the following:
getrootfs hdisk0
- You will now be at a shell prompt in single user mode.
- I have a SPARCstation 5. What will I need to do in order to run Communique!?
- Communique! will run on SPARCstation 5s subject to the following conditions:
- Users who wish to use Parallax video boards and run Solaris 1.x must use Parallax
drivers version 3.07 and run under Solaris 1.1.2 (SunOS 4.1.4).
- The Sun SPARCstation 5 audio patches must be installed.
- The MDL Corporation Audio Buffer patch (available on the MDL Corporation CD) must be
installed.
- Why won't pkgadd work correctly in Solaris 2.4?
- Packages for 2.4 have changed, please be aware:
Certain unbundled and 3rd-party
packages are no longer entirely compatible with the latest version of pkgadd. These
packages require user interaction throughout the installation and not just at the very
beginning.
To install these older packages (released prior to Solaris 2.4), set the following
environment variable:
NONABI_SCRIPTS=TRUE
pkgadd will permit keyboard interaction throughout the installation as long as this
environment variable is set.
- What precautions are there when using Parallax boards with
Solaris 1.1.2 (SunOS 4.1.4)?
- Although not officially supported, Communique! should run under Solaris 1.1.2
subject to the following restrictions:
The Parallax OpenWindows drivers version 3.06
will work on a Solaris 1.1.2 system, but will crash the system when exiting OpenWindows
unless you use the following workaround:
When starting OpenWindows, issue the following command (in csh)
[Path to "openwin" command] [arguments to openwin] >&! /dev/null
Parallax is working on this problem.
- Why don't Parallax drivers version 3.06 work properly on my
SPARCstation 5 or SPARCstation 20?
- Parallax drivers version 3.06 contains some incompatibilities with the Parallax device
drivers and these models. Version 3.07 fully supports the SPARC 5 & 20. Support for
SPARC 5 audio is included in this release, but only for Solaris 1.1.2 (SunOS
4.1.4). If you have a SPARC 5 with Solaris 1.1.1 (SunOS 4.1.3) or earlier, you must
upgrade your operating system in order to take advantage of this feature.
- How can I get Communique! to run under TriTeal VUE?
- To enable Communique! to work with TriTeal's TED (CDE) and Solaris 2.3, you
should do the following:
- Backup the original /usr/dt directory with
mv /usr/dt /usr/dt.orig
- Install and start TED (CDE) as per manual.
- Log in as root.
- Create a single symbolic link between libXm.so.2 (the Motif file Communique!
needs) and libDtXm.so.
cd /usr/dt/lib
ln -s libDtXm.so libXm.so.2
- Make sure the LD_LIBRARY_PATH environment variable includes the directory
"/usr/dt/lib".
