1827243 Members
2240 Online
109716 Solutions
New Discussion

dtpad error

 
SOLVED
Go to solution
jerry1
Super Advisor

dtpad error

Does anyone know how to get rid of this error
when running dtpad?

# dtpad
Could not connect to ToolTalk service: TT_ERR_PROCID The process id passed is
not valid.
4 REPLIES 4
Shine_5
Frequent Advisor
Solution

Re: dtpad error

Hi,

WTEC states about dtfile run remotely:

"Regarding dtfile displaying remotely - the dtfile client is not designed
for this type of operation.
dtfile is designed to work within a CDE session - not as a standalone
client. When dtfile runs, it first tries to detect if there is another dtfile
running to which to attach. If one is running, and it can access it, it merely
sends a message to the already running dtfile indicating that it wants a new
window. If one isn't running, then it will attempt to start the 'server' part of
dtfile and run from there. There are also issues having to do with the action
and icon databases that become a problem if dtfile is run outside of a session."


Regards
Shine
Shine_5
Frequent Advisor

Re: dtpad error

Hi,

Final solution:
After moving $HOME/.dt to $HOME/.dt.old the appmanager works fine, again.
So we carefully copied back changes the user had made regarding actions,
frontpanel and window manager to the new ~/.dt directory => Appmanager runs.
BTW: Changing any files at ~/.dt must be done while the user does not have a CDE
session running, because ~/.dt may be overwritten at logout!!


Regards
Shine
Alex Glennie
Honored Contributor

Re: dtpad error

and in case that doesn't work try running dtpad -standAlone

it's interesting is this the same box you had some odd TPS errors on ... anything nasty happen to it recently or could you describe your enviroment in a bit more detail ?

patch level wrt CDE, workstation ? been upgraded from anothe O/S ... just trying to see a bigger picture ...
jerry1
Super Advisor

Re: dtpad error

The system A with the X server print problem is HP-UX 11.0.

The one B with the ToolTalk error is HP-UX 11.0

dtpad comes up fine from command line with
executing just "dtpad" on system A.

On system B according to your directions you
must use "dtpad -standAlone" to bypass
ToolTalk service. Then it comes up. Of course
X print server does not work on this system
either.

The developers are using dtpad since there
was nothing else available. They either don't
know how to use vi or don't want to use vi
so I installed the latest emacs for them to
ween them off of dtpad. They do not run CDE.
They run X on their PC and set DISPLAY to run
dtpad.