Please Help with Tru64 CDE problem

10 More Discussions You Might Find Interesting

1. Solaris

Solaris 8 CDE Problem

All, I'm running Solaris 8 on a Sparcbook. One of my users, when logging in, defaults to Open Windows desktop rather than CDE. All other users get logged into CDE just fine. Is there a file or something that tells the system what default login is? I'm confused as to why it's just for this one...

2. UNIX Desktop Questions & Answers

How to migrate Solaris 10 CDE config to HP-UX CDE.

Hello, Do you guys by any chance know what is the best (if any ) way to move CDE configuration from a SOLARIS 10 machine to HP-UX? Just the config (actions, text files etc). Thanks in advance!

3. HP-UX

Problem with vdump command on TRU64

Hi all, I have a system with TRU64 system (quite old). I use to run script to make save of important system partitions. The command to save the partition "/" is : /sbin/vdump -0uDf /mnt/Sauvegarde/dump/slash.dump.0 /. (/mnt/Sauvegarde is NFS mounted, but this is no matter) This script ran for...

4. HP-UX

User unlock problem in Tru64 4.0F Server

Hi Friends We have two node trucluster Tru64 4.0F Alpha Servers,In one of Tru64 4.0F Unix Server I am unable to unlock users, when I issue usermod command I will get following error /usr/sbin/usermod -x administrative_lock_applied=0 username account manager has exited unexpectedly - please...

5. Solaris

Solaris 10 CDE problem - The DT messaging system could not be started

A Google search with: +Solaris +"The DT messaging system could not be started" returns 138 hits. All of the relevant possible solutions are in this document. My apologies for such a long document but I thought I would try to minimize the resolution attempts that I've already tried. System...

6. Solaris

Problem Starting CDE

hi, I have installed Solaris 10 from dvd. I have a 1.8GHz processor and 512mb RAM. When I start it, a message is displayed that Xserver cannot be initialised. Please tell me how to start computer in GUI mode, because it logs me into console mode. Regards Rochit

7. HP-UX

root login problem in cde

Hi All, I m facing a problem that, i m not able to login as root user on cde on hp-ux 11.00, i can login as root on commond line as well as telnet. Thanks in Advance for help. Regards, Awadhesh

8. HP-UX

CDE login Problem for root user only

Hi All, I m facing a problem that, i m not able to login as root user on cde on hp-ux 11.00, i can login as root on commond line as well as telnet. Thanks in Advance for help. Regards, Awadhesh

9. UNIX for Dummies Questions & Answers

Tru64 UNIX log in problem

I'm using Tru64 UNIX 4.0 . I restarted the machine and I tried to log in again as an user I get a message saying No directory!. The system log me in as a superuser. I checked and the directory actually is not there. I'm pretty sure that i didn't deleted it. If someone have a clue of what is...

10. UNIX for Dummies Questions & Answers

CDE problem

I created a general use account on my Sparc system. The problem is this: I did a "useradd -g general -G sysadmin -d /usr/home/sameer sameer" (after I made the directories) But it seems that no .profile or other files were written to this directory. Now what's happening is when I try to...

LEARN ABOUT NETBSD

xdestroywindow

XDestroyWindow(3)						  XLIB FUNCTIONS						 XDestroyWindow(3)

NAME

       XDestroyWindow, XDestroySubwindows - destroy windows

SYNTAX

       int XDestroyWindow(Display *display, Window w);

       int XDestroySubwindows(Display *display, Window w);

ARGUMENTS

       display	 Specifies the connection to the X server.

       w	 Specifies the window.

DESCRIPTION

       The XDestroyWindow function destroys the specified window as well as all of its subwindows and causes the X server to generate a DestroyNo-
       tify event for each window.  The window should never be referenced again.  If the window specified by the w argument is mapped, it is
       unmapped automatically.	The ordering of the DestroyNotify events is such that for any given window being destroyed, DestroyNotify is gen-
       erated on any inferiors of the window before being generated on the window itself.  The ordering among siblings and across subhierarchies
       is not otherwise constrained.  If the window you specified is a root window, no windows are destroyed.  Destroying a mapped window will
       generate Expose events on other windows that were obscured by the window being destroyed.

       XDestroyWindow can generate a BadWindow error.

       The XDestroySubwindows function destroys all inferior windows of the specified window, in bottom-to-top stacking order.	It causes the X
       server to generate a DestroyNotify event for each window.  If any mapped subwindows were actually destroyed, XDestroySubwindows causes the
       X server to generate Expose events on the specified window.  This is much more efficient than deleting many windows one at a time because
       much of the work need be performed only once for all of the windows, rather than for each window.  The subwindows should never be refer-
       enced again.

       XDestroySubwindows can generate a BadWindow error.

DIAGNOSTICS

       BadWindow A value for a Window argument does not name a defined Window.

SEE ALSO

       XChangeWindowAttributes(3), XConfigureWindow(3), XCreateWindow(3), XMapWindow(3), XRaiseWindow(3), XUnmapWindow(3)
       Xlib - C Language X Interface

X Version 11							   libX11 1.5.0 						 XDestroyWindow(3)

UNIX for Advanced & Expert Users