Sponsored Content
Full Discussion: PIII video problems.
Special Forums Hardware PIII video problems. Post 302477821 by Corona688 on Monday 6th of December 2010 12:10:10 PM
Old 12-06-2010
So what you're saying is, the computer doesn't boot, at all, ever, or even react, at all, ever, no matter what you do with it. It may be dead dead, not just dead-video dead. I don't suppose you have a POST card.
 

4 More Discussions You Might Find Interesting

1. Solaris

problems with my M3 video card and my Tatung Ultra 10 clone

i took this Elite 3D M3 video card out of my Ultra 60 machine which was replaced with an M6. the card was working w/o issue in the Ultra 60. however, i'm getting no video when i power the Tatung machine. yes, the M3 is does work with an AXi motherboard. any ideas what's causing the problem? (1 Reply)
Discussion started by: xyyz
1 Replies

2. UNIX and Linux Applications

Kudda has successfully solved the downloading problems for numerous video web

The rise of Video web stimulates more intuitive video feeling of large people, and makes video downloading becomes a popular trend in web times, meanwhile, more and more downloading problems arises correspondingly, in which the first trouble is slow downloading speed and incomplete downloading. It... (0 Replies)
Discussion started by: angelstar
0 Replies

3. Linux

USB video capture? composite, s-video, etc

does anybody have any experience with any of these composite video to usb devices on linux? usb video capture - Google Product Search would like to get one but a linux newbie and having trouble figuring out if any are ported... i've found lots of things that link to freedesktop.org DisplayLink... (1 Reply)
Discussion started by: danpaluska
1 Replies

4. UNIX for Advanced & Expert Users

Video Cards :: Video Memory Intercept and Redirect

I need a broad spectrum understanding on this subject, and any help would be greatly appreciated. First of all, as I understand it... The way the video hardware works is the CPU sends information about input and possible changes to the display, the video card receives these changes, makes the... (2 Replies)
Discussion started by: ciNG
2 Replies
LAMSHRINK(1)							   LAM COMMANDS 						      LAMSHRINK(1)

NAME
lamshrink - Shrink a LAM multicomputer. SYNTAX
lamshrink [-hv] [-w <delay>] [-u <userid>] <node> <hostname> OPTIONS
-h Print useful information on this command. -v Be verbose. <hostname> Remove the LAM node on this host. <node> Remove the LAM node with this ID. -w <delay> Notify processes on the doomed node and pause for <delay> seconds before proceeding. -u <userid> Use this userid to access the host. DESCRIPTION
An existing LAM session, initiated by lamboot(1), can be shrunk to include less nodes with lamshrink. One node is removed for each invoca- tion. At a minimum, the node ID and the associated host name is given on the command line. Once lamshrink completes, the node ID is in- valid across the remaining nodes. If a different userid is required to access the host, it is specified with the -u option. Existing application processes on the target node can be warned of impending shutdown with the -w option. A LAM signal (SIGFUSE) will be sent to these processes and lamshrink will then pause for the given number of seconds before proceeding with removing the node. By de- fault, SIGFUSE is ignored. A different handler can be installed with ksignal(2). All application processes on all remaining nodes are always informed of the death of a node. This is also done with a signal (SIGSHRINK), which by default causes a process's runtime route cache to be flushed (to remove any cached information on the dead node). If this signal is re-vectored for the purpose of fault tolerance, the old handler should be called at the beginning of the new handler. The signal does not, by itself, give the process information on which node has been removed. One technique for getting this information is to query the router for information on all relevant nodes using getroute(2). The dead node will cause this routine to return an error. FAULT TOLERANCE If enabled with lamboot(1), LAM will watch for nodes that fail. The procedure for removing a node that has failed is the same as lamshrink after the warning step. In particular, the SIGSHRINK signal is delivered. EXAMPLES
lamshrink -v newhost n1 Remove LAM on newhost, known within LAM as node 1. Report about important steps as they are done. lamshrink newhost n30 -w 10 Inform all processes on LAM node 30, which is running on newhost, that the node will be dead in 10 seconds. Wait 10 seconds and remove the node. Operate silently. SEE ALSO
lamboot(1), tkill(1), ksignal(2), getroute(2) LAM 6.5.8 November, 2002 LAMSHRINK(1)
All times are GMT -4. The time now is 06:57 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy