11-21-2002
Removing CDE and openwindows
Hi,
I have searched the internet and this site and cannot find a way to remove CDE from a sparc Solaris 8 machine.
I could run pkgrm on the individual CDE packages but would like to know if there is a more efficient way. 2.5.1 seemed to have had an uninstall script that 8 does not.
What applications should I leave behind so I can still run x on another host.
The reason for this work is that the Server now runs an asci dumb terminal.
Thanks,
blp001
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Is there such a thing as installing a CDE for use with UNIX? If so, where would I find one, and how would I do it? What kind of info about UNIX would I need to know before going into this? (3 Replies)
Discussion started by: muscleache
3 Replies
2. Solaris
How do I run OpenWindows on a Solaris10 Sparc system?
I know it has been discontinued, but I have some applications that only run on OpenWin. And I would like to run Solaris10 instead of Solaris8, hence the problem. Can I download, install and run it with Solaris10?
Thanks, Mike (5 Replies)
Discussion started by: mndavies
5 Replies
3. UNIX for Dummies Questions & Answers
Hi,
I would like to change the size of the shelltool window when the full size is selected, by clicking on the top of the window.
The issue is... I have a monitor that cannot do 1152x900 resolution format. The monitor can only do 1152x870. Also the frame buffer cannot do any other resolution.... (0 Replies)
Discussion started by: Sean_69
0 Replies
4. Solaris
Hi all!
On my SPARC mashine I have changed the screen resolution from default to: output-device screen r1024x768x75, because the OBP picture too big (e.g. Sun Logo and OBP text).
Now, after the system booting I have the problem with OpenWindows picture (e.g. the window manager does not display... (2 Replies)
Discussion started by: wolfgang
2 Replies
5. UNIX Desktop Questions & Answers
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! (0 Replies)
Discussion started by: binary0x01
0 Replies
6. Solaris
I have two CDE desktop accounts on different server (called this CDE#1, CDE#2) on the same network.
However, my current setup is connecting to the Solaris CDE#1,CDE#2 via Citrix.
My plan is to connect to CD#1 and then somehow connect to CDE#2.
How do I do this? I am just a regular user... (0 Replies)
Discussion started by: tthach830
0 Replies
7. Solaris
Hi guys, Just wondering how I can get
OpenWindows 3 window manager.
I installed SunOS 4.1.4 on Qemu
and when I type Openwin,
I will get a purpleish interface,
which I am not fond of.
I'd like to have the following look and feel...
OpenWindows 3 - SunOS 4.1.4
Thanks Jack (2 Replies)
Discussion started by: lucky7456969
2 Replies
8. UNIX for Dummies Questions & Answers
Hi Everybody! First post! Totally noobie.
I'm using the terminal to read a poorly formatted book.
The text file contains, in the middle of paragraphs, hyphenation to split words that are supposed to be on multiple pages. It looks ve -- ry much like this.
I was hoping to use grep -v " -- "... (5 Replies)
Discussion started by: AxeHandle
5 Replies
9. Solaris
Hi members!
I have installed SunOS 4.1.4 under QEMU.
I would like to use it with xdm. I launch xdm and get login window.
But when I have inputed user name and password,
XDM exited with the message:
"error (334): Unknown session exit code 2817 from process 342"
I have checked:
pid 334 is the... (5 Replies)
Discussion started by: goodbyespy
5 Replies
LEARN ABOUT HPUX
dtwsmgetworkspaceinfo
DtWsmGetWorkspaceInfo(library call) DtWsmGetWorkspaceInfo(library call)
NAME
DtWsmGetWorkspaceInfo -- get detailed workspace information
SYNOPSIS
#include <Dt/Wsm.h>
int DtWsmGetWorkspaceInfo(
Display *display,
Window root,
Atom aWorkspace,
DtWsmWorkspaceInfo **ppWsInfo);
DESCRIPTION
The DtWsmGetWorkspaceInfo function works with the CDE workspace manager, dtwm(1), and returns detailed information on a specific workspace.
The display argument is the X display.
The root argument is the root window of the screen of interest.
The aWorkspace argument is the workspace name (converted to an X atom).
The *ppWsInfo argument is the address of a variable to receive the returned pointer to the workspace information data.
The DtWsmWorkspaceInfo structure contains at least the following members:
Atom workspace The workspace name (con-
verted to an X atom).
unsigned long bg The pixel ID used for the
background color of the
backdrop.
unsigned long fg The pixel ID used for the
foreground color of the
backdrop.
Atom backdropName The backdrop file name
(converted to an X atom).
The file must be in either
X Bitmap file format (with
extension .bm) or X Pixmap
file format (with extension
.pm). The workspace man-
agement services look for
the file along the same
path used for searching
icons. The directory
/usr/dt/backdrops is the
default directory if the
file cannot be found along
the icon search path.
int colorSetId The colorset number used
for this workspace, which
affects the backdrop color
and the button color for
this workspace on the front
panel.
char *pchTitle The title displayed in the
button for this workspace
on the front panel. This
string is interpreted in
the locale in which the CDE
workspace manager, dtwm(1),
is running. The title is
different from the
workspace name. The
workspace name, when con-
verted from an X atom, is
used as the identifier for
a workspace in the
workspace manager function
calls. The CDE workspace
manager, dtwm(1). also uses
the workspace name as a
resource name; thus, the
characters used in a
workspace name are
restricted to the charac-
ters in the X Portable
Character Set. The
workspace name for a
workspace created from the
front panel is generated
automatically by the CDE
workspace manager, dtwm(1).
Window *backdropWindows A pointer to an array of
windows that make up the
backdrop.
int numBackdropWindows The number of elements in
the backdropWindows array.
RETURN VALUE
Upon successful completion, the DtWsmGetWorkspaceInfo function returns Success and the workspace manager returns in *ppWsInfo a pointer to
a DtWsmInfo structure that contains information about the workspace aWorkspace; otherwise, it returns a value not equal to Success.
APPLICATION USAGE
If the DtWsmGetWorkspaceInfo function is not successful, failure may be due to a memory allocation error or failure to find the correct
workspace information (that is, the CDE workspace manager, dtwm(1), is not running). The application must use the DtWsmFreeWorkspaceInfo(3)
function to free the data returned in *ppWsInfo. The *backdropWindows pointer may be useful for applications that are interested in some
events on the root window. Since the backdrop covers the root window, the backdrop catches the button events before they reach the root.
SEE ALSO
Dt/Wsm.h - DtWsm(5), dtwm(1), DtWsmGetWorkspaceList(3), DtWsmFreeWorkspaceInfo(3).
DtWsmGetWorkspaceInfo(library call)