Hello, Phillip Deackes <[EMAIL PROTECTED]> wrote:
>Syrus, could you please tell us how you got FrameMaker running? I have a >potato system, upgraded weekely using apt-get. FrameMaker will not run >at all, I get no error messages, I just get the $ prompt back again. Am >I perhaps missing some vital library? I added my license OK as described >in the text which came back with the license number. Framemaker runs fine on my potato system. Those who registered with a correct e-mail address, got the appended mail from Adobe this morning. Harald ----------------------------------------------------------------------- Date: Mon, 20 Dec 1999 17:15:23 -0800 To: [EMAIL PROTECTED] From: FM Linux Admin <[EMAIL PROTECTED]> Subject: FrameMaker on Linux Update Late-Breaking FrameMaker Linux News This email is being sent to registered users of FrameMaker on Linux, based on feedback received through [EMAIL PROTECTED] It contains information about three issues that prevent FrameMaker from launching or running on some Linux installations. Details and possible workarounds are noted below. We apologize for any inconvenience these issues may have caused, and appreciate the time you've spent downloading and trying FrameMaker on Linux. As before, please continue sending comments to our feedback address: mailto:[EMAIL PROTECTED] As before, we cannot respond to individual emails. Thanks for trying this beta of FrameMaker on Linux! Lee Richardson FrameMaker Development Manager _________________________________________________ (1) C library incompatibiliy with some distributions of Linux, including Red Hat 5.2 and Debian 2.1. Users will typically see the following message in this case: ./maker: error in loading shared libraries : undefined symbol: __register_frame_info The FrameMaker executable is incompatible with certain releases of version 2.0.7 of the GNU C Library, which are included with some distributions noted above. FrameMaker will not run on systems with this incompatibility, unless access to a different version of the C Library is provided. (2) Lack of portmap/rpcbind services leads to FrameMaker crashing or hanging When 'maker' is started, the following alert appears: "No licenses available. Run in demo mode?". Answering "Yes" may trigger a crash or other undesirable behavior. When running 'demomaker', the application may crash or hang with no alert. As described in the System Requirements, portmap/rpcbind services must be enabled on the local workstation. Otherwise unpredictable behavior may occur including crashes and hangs. Starting a portmap/rpcbind service on the local workstation should fix this problem. (3) FrameMaker crashes trying to display splash screen on 16-bit X servers. When 'maker' or 'demomaker' are started on an X server set to 16-bit depth, the application will generally crash just after displaying a blue window in the middle of the screen. FrameMaker does not currently support 16-bit (or 15-bit) display depth, and is failing to recognize the situation in time to exit gracefully. If the splash screen display is disabled, FrameMaker does not halt immediately, but will eventually crash or corrupt internal data. Running at 16-bit depth is not safe in the current release, even if it seems to be working. Displaying to a server running with a depth of 8, 24, or 32 should work fine. _________________________________________________ -----------------------------------------------------------------------
