[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

PDP++ and Redhat 7.0



I recently installed the user's version of the PDP++ on my IBM
Thinkpad running Redhat 7.0, and have been encountering some
relatively minor, though somewhat irritating, windowing problems with
it.  I will describe this behavior below, but first let me be precise
about what I installed.

I first used the rpm file (pdp++-binext-2.0-0.i386.rpm) to install the
software, ignoring the following dependency problems noted by rpm:

    pdp++-binext-2.0-0 requires libc.so.5
    pdp++-binext-2.0-0 requires libreadline.so.3

This lead to some quirky behavior, so rather of trying to get the
various library versions that seemed to be required, I instead
uninstalled the rpm version and installed the version with static
libraries instead (pdp++_2.0_bin_LINUXstat.tar.gz).  I seemed to have
exactly the same quirky behavior, which I will now describe in more
detail.

I tested the software using the Tutorial Introduction (Using Bp),
chapter 4 of the PDP++ Software Users Manual.  Following are the odd
behaviors I encountered:

(1) After opening xor.proj.gz, all the windows become visible for a
    moment, and then automatically iconify.  (The manual says that the
    root window should move to the right and the Project and NetView
    windows become visible and the others iconify, whereas all windows
    in fact iconify.)

(2) After de-iconifying the root window, they all become visible.  At
    this point if I try to iconify any of the windows, then they all
    iconify.  Actually, if I tried to iconify the project window, I
    can't.

(3) Sometimes when I click on a menu in one of the windows, it will
    persist even if I try to close it, and even if I move to another
    virtual desktop (I am using the KDE window manager), it will
    remain visibleon that other desktop.

(4) In some cases, I have found that the when I went to another
    virtual desktop while, for example, a training process is running,
    the process would stop.  In some of these cases, I needed to
    restart bp in order to get the process running.

If anyone could give me some suggestions, I would be greatly
appreciative.  I suspect that the quirkiness might have something to
do with Redhat 7.0, since I did not have these problems when I was
using it last year under Redhat 6.2.  If someone has dealt with these
problems on Redhat 7.0 and wishes to advise me off-line, I will
summarize for the list.

Thanks,

Karl Knight