Sujet : Re: Old printers, Architectural implications of locate mode I/O
De : johnl (at) *nospam* taugh.com (John Levine)
Groupes : comp.archDate : 06. Jul 2024, 03:48:37
Autres entêtes
Organisation : Taughannock Networks
Message-ID : <v6aba5$2dcb$1@gal.iecc.com>
References : 1 2 3 4
User-Agent : trn 4.0-test77 (Sep 1, 2010)
According to MitchAlsup1 <
mitchalsup@aol.com>:
We students, also, figured out that TSS had dumped OS process state in
page 0 (un accessible normally) of the user's address space. We then
figured out that while we could not LD or ST that data, we could queue
up I/O (out) write the data to disk, read it back where we could diddle
with it, write it back to disk, queue up I/O (in) and read it back into
page 0.
>
All we did was to set the privilege bit !!
That was very restrained of you. I was only a visiting high school kid
when I was using TSS at Princeton so I didn't push my luck. But ...
We (students) used to have comment cards that cause the hammers all
fly at the same time. So, instead of a natural z z z z z of the print,
it would go BANG BANG BANG and we knew out stuff was being printed...
Princeton had high end 1403 model N1 printers on the 360/20's they
used for RJE to their 360/91. The /91 crashed a lot, and while waiting
for it to come back up, we might have done some, ah, unofficial stuff
pn the /20's, particularly once someone found a copy of the 360/20
card assembler.
On that model of printer could use different print chains with
different sequences of characters, to handle upper/lower case and
such. The printer had a Universal Character Set (UCS) buffer the
computer could load to tell the printer what characters were where on
the chain. So one day I wondered what would happen if I loaded the UCS
buffer with all the same character, then printed lines of that
character.
Let me just say, Don't Do That. I think it blew a fuse before anything
was seriously damaged.
-- Regards,John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for Dummies",Please consider the environment before reading this e-mail. https://jl.ly
Date | Sujet | # | | Auteur |
2 Jul 24 | Architectural implications of locate mode I/O | 64 | | John Levine |
2 Jul 24 | Re: Architectural implications of locate mode I/O | 38 | | Thomas Koenig |
3 Jul 24 | Re: Architectural implications of locate mode I/O | 1 | | MitchAlsup1 |
3 Jul 24 | Re: Architectural implications of locate mode I/O | 17 | | MitchAlsup1 |
3 Jul 24 | Re: Architectural implications of locate mode I/O | 6 | | Lynn Wheeler |
3 Jul 24 | Re: Architectural implications of locate mode I/O | 2 | | Lawrence D'Oliveiro |
5 Jul 24 | Re: Architectural implications of locate mode I/O | 1 | | Terje Mathisen |
3 Jul 24 | Re: Architectural implications of locate mode I/O | 2 | | MitchAlsup1 |
3 Jul 24 | Re: Architectural implications of locate mode I/O | 1 | | Michael S |
3 Jul 24 | Re: Architectural implications of locate mode I/O | 1 | | Lynn Wheeler |
3 Jul 24 | Re: Architectural implications of locate mode I/O | 9 | | Bill Findlay |
3 Jul 24 | Re: Architectural implications of locate mode I/O | 8 | | Michael S |
3 Jul 24 | Re: Architectural implications of locate mode I/O | 1 | | Bill Findlay |
3 Jul 24 | Re: Architectural implications of locate mode I/O | 6 | | Stephen Fuld |
3 Jul 24 | Re: Architectural implications of locate mode I/O | 5 | | MitchAlsup1 |
4 Jul 24 | Re: wisdom of the ancients, was Architectural implications of locate mode I/O | 4 | | John Levine |
4 Jul 24 | Re: wisdom of the ancients, was Architectural implications of locate mode I/O | 2 | | John Savard |
4 Jul 24 | Re: wisdom of the ancients, was Architectural implications of locate mode I/O | 1 | | John Savard |
4 Jul 24 | Re: wisdom of the ancients, was Architectural implications of locate mode I/O | 1 | | MitchAlsup1 |
3 Jul 24 | Re: Architectural implications of locate mode I/O | 1 | | Stephen Fuld |
3 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 19 | | John Levine |
3 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 9 | | Anton Ertl |
3 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 6 | | Michael S |
3 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 4 | | MitchAlsup1 |
4 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 3 | | Michael S |
4 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 1 | | MitchAlsup1 |
5 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 1 | | Joe Pfeiffer |
3 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 1 | | Michael S |
3 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 1 | | Robert Swindells |
3 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 1 | | John Levine |
4 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 9 | | Thomas Koenig |
4 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 8 | | MitchAlsup1 |
4 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 7 | | Thomas Koenig |
5 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 5 | | John Levine |
5 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 4 | | MitchAlsup1 |
7 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 3 | | Paul A. Clayton |
7 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 1 | | Lynn Wheeler |
7 Jul 24 | Re: patents, Architectural implications of locate mode I/O and channels | 1 | | John Levine |
5 Jul 24 | Re: Architectural implications of locate mode I/O and channels | 1 | | MitchAlsup1 |
3 Jul 24 | Re: Architectural implications of people who don’t understand locate mode I/O | 1 | | Lawrence D'Oliveiro |
5 Jul 24 | Re: Architectural implications of locate mode I/O | 24 | | Joe Pfeiffer |
5 Jul 24 | Re: Architectural implications of locate mode I/O | 21 | | John Levine |
6 Jul 24 | Re: Architectural implications of locate mode I/O | 18 | | Lynn Wheeler |
6 Jul 24 | Re: Architectural implications of locate mode I/O | 1 | | MitchAlsup1 |
6 Jul 24 | Re: Architectural implications of locate mode I/O | 14 | | Stephen Fuld |
6 Jul 24 | Re: ancient disks, Architectural implications of locate mode I/O | 7 | | John Levine |
6 Jul 24 | Re: ancient disks, Architectural implications of locate mode I/O | 6 | | Stephen Fuld |
6 Jul 24 | Re: ancient disks, Architectural implications of locate mode I/O | 5 | | John Levine |
7 Jul 24 | Re: ancient disks, Architectural implications of locate mode I/O | 4 | | Stephen Fuld |
7 Jul 24 | Re: ancient disks, Architectural implications of locate mode I/O | 3 | | Thomas Koenig |
7 Jul 24 | Re: ancient disks, Architectural implications of locate mode I/O | 2 | | Thomas Koenig |
7 Jul 24 | Re: ancient disks, Architectural implications of locate mode I/O | 1 | | Stephen Fuld |
6 Jul 24 | Re: Architectural implications of locate mode I/O | 1 | | Lynn Wheeler |
1 Aug 24 | Re: Architectural implications of locate mode I/O | 5 | | Lawrence D'Oliveiro |
1 Aug 24 | Re: Architectural implications of locate mode I/O | 4 | | Stephen Fuld |
1 Aug 24 | Re: Architectural implications of locate mode I/O | 2 | | John Levine |
2 Aug 24 | Re: Architectural implications of locate mode I/O | 1 | | Stephen Fuld |
11 Aug 24 | Re: Architectural implications of locate mode I/O | 1 | | Lawrence D'Oliveiro |
8 Jul 24 | Re: Architectural implications of locate mode I/O | 2 | | Lawrence D'Oliveiro |
8 Jul 24 | Re: Architectural implications of locate mode I/O | 1 | | Lynn Wheeler |
6 Jul 24 | Re: Architectural implications of locate mode I/O | 2 | | MitchAlsup1 |
6 Jul 24 | Re: Old printers, Architectural implications of locate mode I/O | 1 | | John Levine |
8 Jul 24 | Re: Architectural implications of locate mode I/O | 2 | | Lawrence D'Oliveiro |
1 Aug 24 | Re: Architectural implications of locate mode I/O | 1 | | MitchAlsup1 |