From: Stan Sieler <sieler@allegro.com>
To: adevries@thepuffingroup.com (Alex deVries)
Cc: kirkb@chrome.rose.hp.com, parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] booting problems
Date: Thu, 10 Jun 1999 10:03:59 -0700 (PDT) [thread overview]
Message-ID: <199906101704.KAA33498@bart.allegro.com> (raw)
In-Reply-To: <375F6778.7E2F1385@thepuffingroup.com> from "Alex deVries" at Jun 10, 99 03:21:28 am
Re:
> > Chassis codes, see the PDC_CHASSIS call in your pdc32.pdf
> > documentation), are displayed on the 25th line of an HPTERM compatible
...
> Putting the error on the 25th line is a really good idea, but I can't
> see the 25th line because of the terminal control buttons ("Line
> Modify", "Modify All", etc). I can't seem to get rid of them either.
> What's the trick?
On an 800 system console (i.e., a real HP terminal (or compatible/emulator)),
you'd press control-B and then you'd see the PDC status displayed on
line 25. (you'll also get a command prompt)
To stop seeing it, enter "CO"<return> (no quotes)
I've never tried it via the remote card mentioned earlier...I presume there's
a mechanism for doing the control-B signal...perhaps pressing control-B?
--
Stan Sieler sieler@allegro.com
http://www.allegro.com/sieler.html
next prev parent reply other threads:[~1999-06-10 17:04 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-10 5:07 [parisc-linux] booting problems Alex deVries
1999-06-10 6:20 ` Kirk Bresniker
1999-06-10 7:21 ` Alex deVries
1999-06-10 15:26 ` Kirk Bresniker
1999-06-10 17:08 ` Stan Sieler
1999-06-10 17:03 ` Stan Sieler [this message]
1999-06-10 21:20 ` John David Anglin
1999-06-11 7:36 ` Alex deVries
1999-06-11 8:57 ` Alex deVries
1999-06-11 9:08 ` Jeffrey A Law
1999-06-11 14:06 ` John David Anglin
1999-06-11 17:19 ` Alex deVries
1999-06-11 18:10 ` Kirk Bresniker
[not found] <no.id>
1999-06-10 18:32 ` Stan Sieler
-- strict thread matches above, loose matches on Subject: below --
1999-06-10 21:06 Richard J. Rauenzahn
1999-06-11 18:49 Jason Eckhardt
1999-06-11 19:37 ` Alex deVries
1999-06-12 0:56 ` John David Anglin
1999-06-12 1:25 ` John David Anglin
1999-06-12 3:23 ` John David Anglin
1999-06-12 3:43 ` Jeffrey A Law
1999-06-12 5:10 ` Alex deVries
1999-06-12 5:11 ` Jeffrey A Law
[not found] <3761F335.ADA76678@thepuffingroup.com>
1999-06-12 6:32 ` Jeffrey A Law
1999-06-12 11:15 ` Alex deVries
1999-06-12 16:57 ` John David Anglin
1999-06-12 18:36 ` Alan Cox
1999-06-12 18:53 ` Jeffrey A Law
1999-06-12 19:36 ` Matthew Wilcox
1999-06-12 21:15 ` Jeffrey A Law
1999-06-12 21:09 ` Jeffrey A Law
1999-06-13 19:10 ` John David Anglin
1999-06-14 0:17 ` Alex deVries
2001-08-31 16:06 James Waterhouse
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=199906101704.KAA33498@bart.allegro.com \
--to=sieler@allegro.com \
--cc=adevries@thepuffingroup.com \
--cc=kirkb@chrome.rose.hp.com \
--cc=parisc-linux@thepuffingroup.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.