22 Nov
2010
22 Nov
'10
5:36 p.m.
I've been trying to execute the TECO commands in Alice's PDP-10
<http://www.hactrn.net/sra/alice/alices.pdp10> and I keep getting an
error saying "?IFC Illegal character "^" after F". The two command
sequences given have the same form:
[1:i*^Yu14<q1&377.f"nir'q1/400.u1>^[[8
.-z(1702117120m81869946983m8w660873337m8w1466458484m8
)+z,.f^@fx*[0:ft^]0^[w^\
and
[1:i*^Yu16<q1&77.+32iq1f"l#-1/100.#-1&7777777777.'"#/100.'u1r>6c^[[6
.(675041640067.m6w416300715765.m6w004445675045.m6
455445440046.m6w576200535144.m6w370000000000.m6),.fx*[0:ft^]0^[w^\
I'm using tecoc.exe from <http://almy.us/files/tecow32.zip>.
From my reading of the documentation for TECO, the f
command is for
flow control and should be one of:
F' Flow to end of conditional
F< Flow to strt of conditional
F> Flow to end of conditional
F| Flow to else part of conditional
I'm guessing that the commands come from some sort of PDP-10 dialect of
TECO and these commands do something else in that dialect.
: is listed as modifying the next command, so is :i*....* an old way
of modifying the insert command to use *'s as the delimiter for the
text?
Would I be better off pasting these commands into the TECO on
pdpplanet?
--
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
<http://legalizeadulthood.wordpress.com/the-direct3d-graphics-pipeline/>
Legalize Adulthood! <http://legalizeadulthood.wordpress.com>
22 Nov
22 Nov
11:45 p.m.
At 12:36 PM 11/22/2010, Richard wrote:
I've been trying to execute the TECO commands in
Alice's PDP-10
<http://www.hactrn.net/sra/alice/alices.pdp10> and I keep getting an
error saying "?IFC Illegal character "^" after F". The two command
sequences given have the same form:
[1:i*^Yu14<q1&377.f"nir'q1/400.u1>^[[8
.-z(1702117120m81869946983m8w660873337m8w1466458484m8
)+z,.f^@fx*[0:ft^]0^[w^\
and
[1:i*^Yu16<q1&77.+32iq1f"l#-1/100.#-1&7777777777.'"#/100.'u1r>6c^[[6
.(675041640067.m6w416300715765.m6w004445675045.m6
455445440046.m6w576200535144.m6w370000000000.m6),.fx*[0:ft^]0^[w^\
I'm using tecoc.exe from <http://almy.us/files/tecow32.zip>.
Those are MIT TECO commands.
<http://pdp-10.trailing-edge.com/mit_emacs_170_teco_1220/01/info/teco.primer.html>http://pdp-10.trailing-edge.com/mit_emacs_170_teco_1220/01/info/teco.primer.html
will help with interpreting it.
From my reading of the documentation for TECO, the
f command is for
flow control and should be one of:
F' Flow to end of conditional
F< Flow to strt of conditional
F> Flow to end of conditional
F| Flow to else part of conditional
I'm guessing that the commands come from some sort of PDP-10 dialect of
TECO and these commands do something else in that dialect. : is listed as modifying the next command, so is
:i*....* an old way
of modifying the insert command to use *'s as the delimiter for the
text?
No, :i is a q-register loading command. :i* "loads" the following
string not into q-register "*" but returns it as a string pointer.
f"n...' is a test command with "not equal" as the test.
Would I be better off pasting these commands into the
TECO on
pdpplanet?
If that machine is running MIT TECO versus TECO-10, yes, perhaps.
I've tried to figure out what the first macro does but no joy. It's too
far from DEC TECO for me to follow.
-Rick
23 Nov
23 Nov
5:39 p.m.
In article <201011222346.oAMNkr1D013887 at rickmurphy.net>,
Rick Murphy <rick at rickmurphy.net> writes:
Those are MIT TECO commands.
<http://pdp-10.trailing-edge.com/mit_emacs_170_teco_1220/01/info/teco.primer.
html>http://pdp-10.trailing-edge.com/mit_emacs_170_teco_1220/01/info/tec…
r.html
will help with interpreting it.
I found a more complete reference here:
<http://pdp-10.trailing-edge.com/mit_emacs_170_teco_1220/01/info/tecord.info.html>
--
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
<http://legalizeadulthood.wordpress.com/the-direct3d-graphics-pipeline/>
Legalize Adulthood! <http://legalizeadulthood.wordpress.com>
7:13 p.m.
From: Richard
Sent: Monday, November 22, 2010 9:36 AM
I've been trying to execute the TECO commands in
Alice's PDP-10
<http://www.hactrn.net/sra/alice/alices.pdp10> and I keep getting an
error saying "?IFC Illegal character "^" after F". The two command
sequences given have the same form:
That's "eff control at" rather than "eff uparrow". From the TECO
ORDER
file:
<m>,<n>F^@
returns 2 values, which are <m> and <n> in numerical order. Thus,
"1,2F^@" and "2,1F^@" both return 1,2.
"<m>,<n>F^@T" is the same as
"<m>,<n>T" except that the former will never cause a
"2<1" error.
Sorry, I do MIT TECO as often as I do TECO-10, and didn't think about that.
[1:i*^Yu14<q1&377.f"nir'q1/400.u1>^[[8
.-z(1702117120m81869946983m8w660873337m8w1466458484m8
)+z,.f^@fx*[0:ft^]0^[w^\
and
[1:i*^Yu16<q1&77.+32iq1f"l#-1/100.#-1&7777777777.'"#/100.'u1r>6c^[[6
.(675041640067.m6w416300715765.m6w004445675045.m6
455445440046.m6w576200535144.m6w370000000000.m6),.fx*[0:ft^]0^[w^\
Ah. Rob has changed the TECO strings a couple of times over the years.
I was thinking of a much earlier version, where the two commands read
.(675041640744.f6w007141004745.f6w643700000000.f6),.fx*[0 at ft^]0$w^\
and
.(675041640067.f6w416300715765.f6w004445675045.f6
455445440046.f6w576200535144.f6w370000000000.f6 ),.fx*[0 at ft^]0$w^\
respectively.
I'm using tecoc.exe from
<http://almy.us/files/tecow32.zip>.
That's Pete Siemsen's program, right? He never did get the MIT command
set in there, although I suggested it to him at the DECUS BOF where he
first showed it off, and he thought it was a good idea. 36 mod 16 is
also 4, and I guess he never got around to that.
From my reading
of the documentation for TECO, the f command is for
flow control and should be one
of: F' Flow to end of conditional
F< Flow to strt of conditional
F> Flow to end of conditional
F| Flow to else part of conditional
I'm guessing that the commands come from some sort
of PDP-10 dialect of
TECO and these commands do something else in that dialect.
: is listed as modifying the next command, so is
:i*....* an old way
of modifying the insert command to use *'s as the delimiter for the
text?
Would I be better off pasting these commands into the
TECO on
pdpplanet?
Just typing TECO on the Toad-1 will get you TECO-10, as will "R TECO" on
the 2065. You need to run EMACS to get into an MIT TECO environment, then
type <ESC><ESC> to get into a TECO command buffer ("minibuffer").
Cut-and-paste does not work, because that's printable character-based, so
you have to type in the strings (at least, the control characters) directly.
Execute by typing <ESC>ESC>.
Rich Alderson
Vintage Computing Sr. Server Engineer
Vulcan, Inc.
505 5th Avenue S, Suite 900
Seattle, WA 98104
mailto:RichA at vulcan.com
mailto:RichA at LivingComputerMuseum.org
http://www.PDPplanet.org/
http://www.LivingComputerMuseum.org/
24 Nov
24 Nov
2:43 a.m.
In article <CC28F43ED4708D489ABCF68D06D7F556040A5CCC67 at 505DENALI.corp.vnw.com>,
Rich Alderson <RichA at vulcan.com> writes:
OK, I will try this. Thanks for not ruining the surprise by telling
me the output :-).
--
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
<http://legalizeadulthood.wordpress.com/the-direct3d-graphics-pipeline/>
Legalize Adulthood! <http://legalizeadulthood.wordpress.com>
From: Richard
Sent: Monday, November 22, 2010 9:36 AM
OK. I tried ^^@ to simulate Ctrl-@ but it still didn't seem to like
it. I think its the dialect more than my inability to type Ctrl-@ and
get something useful.
I've been trying to execute the TECO commands
in Alice's PDP-10
<http://www.hactrn.net/sra/alice/alices.pdp10> and I keep getting an
error saying "?IFC Illegal character "^" after F". The two command
sequences given have the same form:
That's "eff control at" rather than "eff uparrow". From the TECO
ORDER
file:
<m>,<n>F^@
returns 2 values, which are <m> and <n> in numerical order. Thus,
"1,2F^@" and "2,1F^@" both return 1,2.
"<m>,<n>F^@T" is the same as
"<m>,<n>T" except that the former will never cause a
"2<1" error. Would I be
better off pasting these commands into the TECO on
pdpplanet?
Just typing TECO on the Toad-1 will get you TECO-10, as will "R TECO" on
the 2065. You need to run EMACS to get into an MIT TECO environment, then
type <ESC><ESC> to get into a TECO command buffer ("minibuffer").
Cut-and-paste does not work, because that's printable character-based, so
you have to type in the strings (at least, the control characters) directly.
Execute by typing <ESC>ESC>.
2:45 a.m.
In article <CC28F43ED4708D489ABCF68D06D7F556040A5CCC67 at 505DENALI.corp.vnw.com>,
Rich Alderson <RichA at vulcan.com> writes:
Just typing TECO on the Toad-1 will get you TECO-10,
as will "R TECO" on
the 2065. You need to run EMACS to get into an MIT TECO environment
[...]
How do I run EMACS there?
I think once, briefly, we tried some visual editing macros for TECO on
our RSTS/E implementation when we had a borrowed VT52. I don't recall
having much success with the effort though.
We had weird Beehive, LA-36 and Tek4010 terminals. We didn't grok the
TECO macros well enough to understand how to modify them to support
the Beehive, so we didn't pursue it much further than our little
experiement. This would have been around 1979/1980.
--
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
<http://legalizeadulthood.wordpress.com/the-direct3d-graphics-pipeline/>
Legalize Adulthood! <http://legalizeadulthood.wordpress.com>
2:57 a.m.
New subject: Scanning manuals
I believe it is ontopic, since the object of the scam is a service
manual from an old brazilian computer
I have an HP6300C scanner (nice scanner, but it should be able to use
the scsi and the usb ports at same time) and I want to scan some large
schematics. I can scan parts, but is there a GOOD way to scan parts and make
it just one schematic? Any automatic way??
Thanks
Alexandre
---
Enviado do meu Motorola PT550
7:06 a.m.
New subject: Scanning manuals
In article <122a01cb8b85$4b71c6d0$f5f900bd at portajara>,
"Alexandre Souza - Listas" <pu1bzz.listas at gmail.com> writes:
I have an HP6300C scanner (nice scanner, but it
should be able to use
the scsi and the usb ports at same time) and I want to scan some large
schematics. I can scan parts, but is there a GOOD way to scan parts and make
it just one schematic? Any automatic way??
Search for "automatic panorama tools"; they should be able to stitch
together a series of images into a single large panoramic image.
--
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
<http://legalizeadulthood.wordpress.com/the-direct3d-graphics-pipeline/>
Legalize Adulthood! <http://legalizeadulthood.wordpress.com>
8:20 p.m.
From: Richard
Sent: Tuesday, November 23, 2010 6:46 PM
In article
<CC28F43ED4708D489ABCF68D06D7F556040A5CCC67 at 505DENALI.corp.vnw.com>,
Rich Alderson <RichA at vulcan.com> writes:
> Just typing TECO on the Toad-1 will get you
TECO-10, as will "R TECO" on
> the 2065. You need to run EMACS to get into an MIT TECO environment
> [...]
How do I run EMACS there?
After logging in, type "EMACS" at the @ prompt. Or "EDIT", as I have
the
system default editor set to EMACS instead of EDIT (AKA SOS), and the
default terminal type is VT100 instead of PRINTING.
However, something is not right with the F6 command. It's inserting the
value of the string pointer into the buffer, instead of the ASCII string.
I've got some TECO debugging to do! Whoopee!
NB: PDP-10 SIXBIT is easy--add octal 40 to each 6-bit group, beginning
from the left end of the word, and you have the
equivalent ASCII values.
I think once, briefly, we tried some visual editing
macros for TECO on
our RSTS/E implementation when we had a borrowed VT52. I don't recall
having much success with the effort though.
We had weird Beehive, LA-36 and Tek4010 terminals. We
didn't grok the
TECO macros well enough to understand how to modify them to support
the Beehive, so we didn't pursue it much further than our little
experiement. This would have been around 1979/1980.
I've only gotten into the -11 world seriously since coming to work here.
(I did have some experience with an -11 in a phonetics lab when I took a
class on production of speech in grad school, but Fortran is Fortran, and
I didn't have to do any editing.) I think it was running RT-11. I've
used RSX-20F (the variant for the front end on a KL-10), but have never yet
been on a RSTS system. I don't know what the TECO for that would be like.
Rich Alderson
Vintage Computing Sr. Server Engineer
Vulcan, Inc.
505 5th Avenue S, Suite 900
Seattle, WA 98104
mailto:RichA at vulcan.com
mailto:RichA at LivingComputerMuseum.org
http://www.PDPplanet.org/
http://www.LivingComputerMuseum.org/
8:43 p.m.
In article <CC28F43ED4708D489ABCF68D06D7F556040A5CCC6C at 505DENALI.corp.vnw.com>,
Rich Alderson <RichA at vulcan.com> writes:
[...], but have never yet
been on a RSTS system. I don't know what the TECO for that would be like.
I think I have a printout at home of the manual for the implementation
we used. I think it was from DECUS, as TECO was not "officially"
supported for RSTS/E, IIRC.
--
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
<http://legalizeadulthood.wordpress.com/the-direct3d-graphics-pipeline/>
Legalize Adulthood! <http://legalizeadulthood.wordpress.com>
4926
days inactive
4928
days old
9 comments
4 participants
participants (4)
-
legalize＠xmission.com -
pu1bzz.listas＠gmail.com -
RichA＠vulcan.com -
rick＠rickmurphy.net