16 Sep
2013
16 Sep
'13
8:31 a.m.
Sander Reiche wrote:
Works like a charm! Thank you very much indeed!
But, I follow DEC-11-UTECA-B-D (PDP-11 TECO User Guide) and the part on the
ET flag (page 78) doesn't state anything about lower/uppercase. Only the EU
flag which I didn't get to work at all.
Where did you find this amazing piece of information?
I thought I found it in my TECO manual - which is probably buried
at the moment. Otherwise, it would have been by reading the source
code.
In any case, I am very pleased that you let me know my
reply was helpful.
Do you have V36 of TECO? One of the other flags will
provide the version number.
I am usually on 60% keyboards so KEX/KED is a bit
unusable for me (no keypad
or more than 80 keys for that matter). EDIT is fairly close to TECO,
though. And using EL on EDIT did work, so I just knew it had to be possible
on TECO ;)
TECO is really powerful. I think TECO can support
a full screen editor like KED by using the *.TEC files,
but I never managed. Since your system does not have
a keyboard with a keypad, KED is out. As for KEX,
which I used for a long time, especially when I used
a system job under RT-11, the RT-11 documentation
is extremely misleading. At this point, I no longer use
KEX except maybe just to test the variant which supports
a VT420 with more than 24 lines. The working memory
and the size of the cut / paste buffer is so much bigger
when using KED that using KEX is out of the question.
I can provide details of why if anyone is interested.
When a background job is running, just use VBGEXE
to start KED and all 64 KB are available. The special
code used to tell the user when KED is "...working"
requires a data buffer in Low Memory which VBGEXE
supports.
When I run as a system job, the choice is to either use
VBGEXE to support that data buffer in Low Memory
or use a customized variant of KED which uses code
that internally supports the allocation of that data buffer
in Low Memory. The disadvantage of using VBGEXE
to initiate KED as a system job is the need for about
1185 words of Low Memory while the advantage is
KED has 64 KB for code and data. The advantage
of the customized variant of KED is the requirement
of as little as 384 words of Low Memory while the
disadvantage is only 56 KB for code and data. The
loss of 8 KB for data was a small cost for reducing
the Low Memory to 384 words since 99% of the time,
I initiate at least FOUR KED system jobs, although
I have yet to add the code to "SRUN" to dispense
with the extra chunk of Low Memory (an extra
32 words) when it is not needed. Thus far, the most
I have done is to set a BPT in that code and modify
the number of words requested, so I know it can be
done. But saving 3072 words of Low Memory
( [ 1185 - 417 ] * 4 ) is a huge advantage. The 417
words are what SRUN requests at the moment until
the code to eliminate the extra chunk is added.
re,
reiche
On Sun, Sep 15, 2013 at 1:12 PM, Jerome H. Fine <jhfinedp3k at compsys.to>wrote:
>518ET$
>
>where the "$" character is the <ESC> character, of course.
>
>The normal setting for ET is 514 which is obtained by:
>
>ET=$
>
>In octal, that is 1002, so you add 4 to get 1006 and
>lowercase characters are enabled. Does that work?
>
Glad to know it works for you.
Which version of TECO are you using? V36?
Do you at least have the binary distribution of V05.03
of RT-11 which most individuals believe is legal to run
under SimH? V05.03 has most of the really nice features
of RT-11 which are found in the most recent version
except perhaps Y2K support - which many users of RT-11
(especially hobby users who do not need dates in the first
place) do not care about. The most important is the support
for MSCP partitions so that large disk drives of more than
32 MB can be used. While the DEC version of V05.03 of
RT-11 can't boot non-zero MSCP partitions, with V05.02
of RT-11, the maximum number of blocks easily available to
a user for an MSCP drive was 65535 blocks.
Jerome Fine