Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > alt.sys.pdp11 > #5579 > unrolled thread
| Started by | Robin Haberkorn <robin.haberkorn@googlemail.com> |
|---|---|
| First post | 2024-11-12 16:50 +0300 |
| Last post | 2024-11-19 11:51 -0500 |
| Articles | 20 on this page of 92 — 15 participants |
Back to article view | Back to alt.sys.pdp11
Any interesting PDP/TECO photos out there? Robin Haberkorn <robin.haberkorn@googlemail.com> - 2024-11-12 16:50 +0300
Re: Any interesting PDP/TECO photos out there? Paul Rubin <no.email@nospam.invalid> - 2024-11-12 08:03 -0800
Re: Any interesting PDP/TECO photos out there? Robin Haberkorn <robin.haberkorn@googlemail.com> - 2024-11-12 20:49 +0300
Re: Any interesting PDP/TECO photos out there? scott@slp53.sl.home (Scott Lurndal) - 2024-11-12 20:02 +0000
Re: Any interesting PDP/TECO photos out there? Paul Rubin <no.email@nospam.invalid> - 2024-11-12 12:47 -0800
Re: Any interesting PDP/TECO photos out there? Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-11-14 22:20 +0000
Re: Any interesting PDP/TECO photos out there? Kaz Kylheku <643-408-1753@kylheku.com> - 2024-11-14 23:50 +0000
Re: Any interesting PDP/TECO photos out there? Rich Alderson <news@alderson.users.panix.com> - 2024-11-12 15:55 -0500
Re: Any interesting PDP/TECO photos out there? Paul Rubin <no.email@nospam.invalid> - 2024-11-12 20:09 -0800
Re: Any interesting PDP/TECO photos out there? Robin Haberkorn <robin.haberkorn@googlemail.com> - 2024-11-13 11:30 +0300
Re: Any interesting PDP/TECO photos out there? Paul Rubin <no.email@nospam.invalid> - 2024-11-13 10:25 -0800
Re: Any interesting PDP/TECO photos out there? Rich Alderson <news@alderson.users.panix.com> - 2024-11-13 14:36 -0500
Re: Any interesting PDP/TECO photos out there? Paul Rubin <no.email@nospam.invalid> - 2024-11-13 15:12 -0800
Re: Any interesting PDP/TECO photos out there? Lars Brinkhoff <lars.spam@nocrew.org> - 2024-11-14 06:29 +0000
Re: Any interesting PDP/TECO photos out there? Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-11-14 22:24 +0000
Re: Any interesting PDP/TECO photos out there? Robin Haberkorn <robin.haberkorn@googlemail.com> - 2024-11-13 11:46 +0300
Re: Any interesting PDP/TECO photos out there? Bob Eager <news0009@eager.cx> - 2024-11-13 09:00 +0000
Re: Any interesting PDP/TECO photos out there? scott@slp53.sl.home (Scott Lurndal) - 2024-11-13 15:30 +0000
Re: Any interesting PDP/TECO photos out there? Paul Rubin <no.email@nospam.invalid> - 2024-11-13 10:29 -0800
Re: Any interesting PDP/TECO photos out there? Robin Haberkorn <robin.haberkorn@googlemail.com> - 2024-11-13 10:31 +0300
Re: Any interesting PDP/TECO photos out there? Lars Brinkhoff <lars.spam@nocrew.org> - 2024-11-13 19:11 +0000
Re: Any interesting PDP/TECO photos out there? Robin Haberkorn <robin.haberkorn@googlemail.com> - 2024-11-16 10:00 +0300
Re: Any interesting PDP/TECO photos out there? Johnny Billquist <bqt@softjar.se> - 2024-12-02 23:58 +0100
Re: Any interesting PDP/TECO photos out there? Rich Alderson <news@alderson.users.panix.com> - 2024-12-03 16:38 -0500
Re: Any interesting PDP/TECO photos out there? Lars Brinkhoff <lars.spam@nocrew.org> - 2024-12-04 08:24 +0000
Re: Any interesting PDP/TECO photos out there? Johnny Billquist <bqt@softjar.se> - 2024-12-04 17:48 +0100
Re: Any interesting PDP/TECO photos out there? Lars Brinkhoff <lars.spam@nocrew.org> - 2024-12-04 18:36 +0000
Re: Any interesting PDP/TECO photos out there? Johnny Billquist <bqt@softjar.se> - 2025-01-08 17:19 +0100
Re: Any interesting PDP/TECO photos out there? Lars Brinkhoff <lars.spam@nocrew.org> - 2025-01-09 08:29 +0000
Re: Any interesting PDP/TECO photos out there? Lars Brinkhoff <lars.spam@nocrew.org> - 2024-11-13 14:28 +0000
Re: Any interesting PDP/TECO photos out there? Robin Haberkorn <robin.haberkorn@googlemail.com> - 2024-11-14 09:44 +0300
Re: Any interesting PDP/TECO photos out there? Lars Brinkhoff <lars.spam@nocrew.org> - 2024-11-14 07:03 +0000
Re: Any interesting PDP/TECO photos out there? Robin Haberkorn <robin.haberkorn@googlemail.com> - 2024-11-14 10:34 +0300
Re: Any interesting PDP/TECO photos out there? Lars Brinkhoff <lars.spam@nocrew.org> - 2024-11-14 08:05 +0000
Re: Any interesting PDP/TECO photos out there? Lars Brinkhoff <lars.spam@nocrew.org> - 2024-11-14 08:25 +0000
Re: Any interesting PDP/TECO photos out there? Robin Haberkorn <robin.haberkorn@googlemail.com> - 2024-11-14 17:42 +0300
Re: Any interesting PDP/TECO photos out there? Robin Haberkorn <robin.haberkorn@googlemail.com> - 2024-11-14 17:09 +0300
Re: Any interesting PDP/TECO photos out there? Lars Brinkhoff <lars.spam@nocrew.org> - 2024-11-16 15:37 +0000
Re: Any interesting PDP/TECO photos out there? Johnny Billquist <bqt@softjar.se> - 2024-12-03 00:07 +0100
Re: Any interesting PDP/TECO photos out there? Robin Haberkorn <robin.haberkorn@googlemail.com> - 2024-12-03 18:55 +0300
Re: Any interesting PDP/TECO photos out there? Johnny Billquist <bqt@softjar.se> - 2024-12-04 17:45 +0100
Re: Interactive Development (was Re: Any interesting PDP/TECO photos out there?) Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-11-14 22:19 +0000
Re: Interactive Development (was Re: Any interesting PDP/TECO photos out there?) John Ames <commodorejohn@gmail.com> - 2024-11-14 14:34 -0800
Re: Interactive Development (was Re: Any interesting PDP/TECO photos out there?) Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-11-15 00:03 +0000
Re: Interactive Development (was Re: Any interesting PDP/TECO photos out there?) Paul Rubin <no.email@nospam.invalid> - 2024-11-14 16:23 -0800
Re: Interactive Development (was Re: Any interesting PDP/TECO photos out there?) Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-11-15 01:52 +0000
Re: Interactive Development (was Re: Any interesting PDP/TECO photos out there?) Robin Haberkorn <robin.haberkorn@googlemail.com> - 2024-11-15 16:26 +0300
Re: Interactive Development (was Re: Any interesting PDP/TECO photos out there?) Paul Rubin <no.email@nospam.invalid> - 2024-11-15 11:25 -0800
Re: Interactive Development (was Re: Any interesting PDP/TECO photos out there?) Robin Haberkorn <robin.haberkorn@googlemail.com> - 2024-11-16 04:47 +0300
Re: Interactive Development (was Re: Any interesting PDP/TECO photos out there?) Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-11-15 22:13 +0000
Re: Interactive Development (was Re: Any interesting PDP/TECO photos out there?) John Ames <commodorejohn@gmail.com> - 2024-11-15 15:08 -0800
Re: Interactive Development (was Re: Any interesting PDP/TECO photos out there?) Robin Haberkorn <robin.haberkorn@googlemail.com> - 2024-11-16 05:11 +0300
Re: Interactive Development (was Re: Any interesting PDP/TECO photos out there?) Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-11-16 03:28 +0000
Re: Interactive Development (was Re: Any interesting PDP/TECO photos out there?) Robin Haberkorn <robin.haberkorn@googlemail.com> - 2024-11-16 10:33 +0300
Re: Interactive Development (was Re: Any interesting PDP/TECO photos out there?) Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-11-16 21:53 +0000
Re: Any interesting PDP/TECO photos out there? Lars Brinkhoff <lars.spam@nocrew.org> - 2024-11-14 06:51 +0000
Re: Any interesting PDP/TECO photos out there? Robin Haberkorn <robin.haberkorn@googlemail.com> - 2024-11-14 10:35 +0300
Re: Any interesting PDP/TECO photos out there? Lars Brinkhoff <lars.spam@nocrew.org> - 2024-11-14 07:56 +0000
Re: Any interesting PDP/TECO photos out there? Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-11-14 22:26 +0000
Re: Any interesting PDP/TECO photos out there? Aidan Kehoe <kehoea@parhasard.net> - 2024-11-15 07:24 +0000
Re: Any interesting PDP/TECO photos out there? Robin Haberkorn <robin.haberkorn@googlemail.com> - 2024-11-14 10:14 +0300
Re: Any interesting PDP/TECO photos out there? Lars Brinkhoff <lars.spam@nocrew.org> - 2024-11-14 07:55 +0000
Re: Any interesting PDP/TECO photos out there? Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-11-14 22:11 +0000
Re: Any interesting PDP/TECO photos out there? "Carlos E.R." <robin_listas@es.invalid> - 2024-11-15 01:40 +0100
Re: Any interesting PDP/TECO photos out there? Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-11-15 01:56 +0000
Re: Any interesting PDP/TECO photos out there? "Carlos E.R." <robin_listas@es.invalid> - 2024-11-15 14:28 +0100
Re: Any interesting PDP/TECO photos out there? Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-11-15 21:58 +0000
Re: Any interesting PDP/TECO photos out there? "Carlos E.R." <robin_listas@es.invalid> - 2024-11-16 01:18 +0100
Re: Any interesting PDP/TECO photos out there? Lynn Wheeler <lynn@garlic.com> - 2024-11-15 15:21 -1000
Re: Any interesting PDP/TECO photos out there? Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-11-16 01:52 +0000
Re: Any interesting PDP/TECO photos out there? "Carlos E.R." <robin_listas@es.invalid> - 2024-11-16 03:03 +0100
Re: Any interesting PDP/TECO photos out there? Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-11-16 03:33 +0000
Re: Any interesting PDP/TECO photos out there? scott@slp53.sl.home (Scott Lurndal) - 2024-11-16 15:14 +0000
Re: Any interesting PDP/TECO photos out there? Bob Eager <news0009@eager.cx> - 2024-11-16 22:21 +0000
Re: Any interesting PDP/TECO photos out there? "John H. Reinhardt" <johnhreinhardt@thereinhardts.org> - 2024-11-16 18:01 -0600
Re: Any interesting PDP/TECO photos out there? scott@slp53.sl.home (Scott Lurndal) - 2024-11-17 18:12 +0000
Re: Any interesting PDP/TECO photos out there? Bob Eager <news0009@eager.cx> - 2024-11-17 18:57 +0000
Re: Any interesting PDP/TECO photos out there? "Carlos E.R." <robin_listas@es.invalid> - 2024-11-16 21:05 +0100
Re: Any interesting PDP/TECO photos out there? Robin Haberkorn <robin.haberkorn@googlemail.com> - 2024-11-15 15:49 +0300
Re: Any interesting PDP/TECO photos out there? Robin Haberkorn <robin.haberkorn@googlemail.com> - 2024-11-15 16:51 +0300
Re: Any interesting PDP/TECO photos out there? Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-11-15 22:01 +0000
Re: Any interesting PDP/TECO photos out there? Paul Rubin <no.email@nospam.invalid> - 2024-11-15 15:41 -0800
Re: Any interesting PDP/TECO photos out there? Bob Eager <news0009@eager.cx> - 2024-11-16 22:32 +0000
Re: Any interesting PDP/TECO photos out there? Robin Haberkorn <robin.haberkorn@googlemail.com> - 2024-11-16 05:03 +0300
Re: Any interesting PDP/TECO photos out there? Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-11-16 03:35 +0000
Re: Any interesting PDP/TECO photos out there? Robin Haberkorn <robin.haberkorn@googlemail.com> - 2024-11-16 10:20 +0300
Re: Any interesting PDP/TECO photos out there? Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-11-15 22:10 +0000
Re: Any interesting PDP/TECO photos out there? Robin Haberkorn <robin.haberkorn@googlemail.com> - 2024-11-16 05:09 +0300
Re: Any interesting PDP/TECO photos out there? Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-11-16 03:40 +0000
Re: Any interesting PDP/TECO photos out there? Stefan Monnier <monnier@iro.umontreal.ca> - 2024-11-18 16:57 -0500
Re: Any interesting PDP/TECO photos out there? Lars Brinkhoff <lars.spam@nocrew.org> - 2024-11-19 14:26 +0000
Re: Any interesting PDP/TECO photos out there? Stefan Monnier <monnier@iro.umontreal.ca> - 2024-11-19 11:51 -0500
Page 4 of 5 — ← Prev page 1 2 3 [4] 5 Next page →
| From | Robin Haberkorn <robin.haberkorn@googlemail.com> |
|---|---|
| Date | 2024-11-14 10:14 +0300 |
| Message-ID | <6ff999f9-9931-9822-c9ad-7d5b220abb7f@googlemail.com> |
| In reply to | #5579 |
On Tue, 12 Nov 2024, Robin Haberkorn wrote: > Here's a TECO "family tree" I reconstructed from various sources: > > https://github.com/rhaberkorn/sciteco/wiki/The-other-modern-TECO-implementations#teco-family-tree > I found a journal called "Moby Munger" - "The official organ of the TECO Special Interest Group". That's a very interesting read! Google it. There were at least 3 editions. I didn't know there was a real actual TECO journal! It contains information about various TECO dialects. It seems everybody back then "munged" his own dialect or fork. The family tree needs to be extended at least with: * VTECO on TOPS-20 and TV based on that * WPI TECO on TOPS-10 based on TECO(-10?) v23 * Stevens TECO based on TECO v23 * XTEC on TOPS-10 and ITS based on Stevens TECO. That was a real actual TECO compiler! There is also some info here: https://sources.vsta.org:7100/teco/file?name=doc/tecolore.txt&ci=tip I especially find that one interesting because they had to solve the parseability problem of TECO and they did that differently than SciTECO. While in SciTECO I fixed the number of string arguments for each command - which seemed to be least intrusive - XTEC fixed the number of integer arguments, including macro calls. * Multics TECO based on early ITS/MIT TECO. * TEC65 on 6502 CPUs * Harvard UNIX TECO based on 1973 MIT TECO And countless others! By the way, hasn't there been any TECO for MS-DOS? It's interesting to read the "Moby Munger" because it conveys the feeling of a lively "scene". We don't have that today. Even SciTECO is only seriously used by a handful of people. But should it ever "fly" again, we should definitely revive the "Moby Munger" in one way or another. Maybe as a conference handout or just as a PDF. -- Robin
[toc] | [prev] | [next] | [standalone]
| From | Lars Brinkhoff <lars.spam@nocrew.org> |
|---|---|
| Date | 2024-11-14 07:55 +0000 |
| Message-ID | <7w5xoq8d18.fsf@junk.nocrew.org> |
| In reply to | #5601 |
Robin Haberkorn wrote: > * XTEC on TOPS-10 and ITS based on Stevens TECO. > That was a real actual TECO compiler! This one is present on MIT backups, but Krupansky declined requesting a copy. There's also a copy on this DECUS tape: https://pdp-10.trailing-edge.com/decus_20tap4_198111/index.html
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D'Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2024-11-14 22:11 +0000 |
| Message-ID | <vh5sip$310hc$3@dont-email.me> |
| In reply to | #5579 |
On Tue, 12 Nov 2024 16:50:59 +0300, Robin Haberkorn wrote:
> 5<3D ITEST$ L>
Presumably you meant:
5<3D ITEST␛ L>
I remember as a student, a full-screen editor written in TECO, called
VTED, was very popular on our main PDP-11/70 system. Our sysadmin pointed
out that a single VTED user consumed about 10-15% of CPU time. Try scaling
that across 20-30 concurrent users --- you see the problem.
Anyway, hitting CTRL/C (accidentally or otherwise) would exit the full-
screen mode and take you to the TECO prompt. Most users were stuck at this
point, since hitting CTRL/C more times would not get you out of TECO.
The main editor code was stored in the string register named “I”, so the
command “MI” (execute contents of I as macro) would resume full-screen
mode. Of course, you had to end command input with two escapes to tell
TECO to actually execute the command(s) you have entered:
MI␛␛
This would echo on-screen as
MI$$
and so my fellow students, trying to follow my instructions by looking at
the screen output I was producing instead of what I was saying (“emm eye
escape escape”, I said), would type “$” instead of pressing the ESC key,
and they would be mystified why it wouldn’t work.
It took them two or three attempts before I noticed what they were doing
wrong ...
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2024-11-15 01:40 +0100 |
| Message-ID | <6thi0lxi9o.ln2@Telcontar.valinor> |
| In reply to | #5610 |
On 2024-11-14 23:11, Lawrence D'Oliveiro wrote: > I remember as a student, a full-screen editor written in TECO, called > VTED, was very popular on our main PDP-11/70 system. Our sysadmin pointed > out that a single VTED user consumed about 10-15% of CPU time. Try scaling > that across 20-30 concurrent users --- you see the problem. I remember that we students got the VAX on its knees when we were working on our assignments. We had to type blind on the unresponsive terminal, and then, after maybe 20 seconds, it would react. It could run an entire program when it switched to it, though, and fast. It just was unresponsive to the display/keyboard. -- Cheers, Carlos.
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D'Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2024-11-15 01:56 +0000 |
| Message-ID | <vh69o5$33c17$4@dont-email.me> |
| In reply to | #5619 |
On Fri, 15 Nov 2024 01:40:38 +0100, Carlos E.R. wrote: > I remember that we students got the VAX on its knees when we were > working on our assignments. We had to type blind on the unresponsive > terminal, and then, after maybe 20 seconds, it would react. It could run > an entire program when it switched to it, though, and fast. It just was > unresponsive to the display/keyboard. Was this on VMS? See, one nice feature of VMS, that I miss on *nix systems, is that the terminal driver would not echo any user output until the program had actually read it. So you could tell whether the program you were running was actually responsive or not.
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2024-11-15 14:28 +0100 |
| Message-ID | <msuj0lxou9.ln2@Telcontar.valinor> |
| In reply to | #5621 |
On 2024-11-15 02:56, Lawrence D'Oliveiro wrote: > On Fri, 15 Nov 2024 01:40:38 +0100, Carlos E.R. wrote: > >> I remember that we students got the VAX on its knees when we were >> working on our assignments. We had to type blind on the unresponsive >> terminal, and then, after maybe 20 seconds, it would react. It could run >> an entire program when it switched to it, though, and fast. It just was >> unresponsive to the display/keyboard. > > Was this on VMS? Yes. > > See, one nice feature of VMS, that I miss on *nix systems, is that the > terminal driver would not echo any user output until the program had > actually read it. So you could tell whether the program you were running > was actually responsive or not. We would count the lines and characters to move the cursor to, then do the correction blind, then wait for the editor to respond. With luck, the spelling would be good. Then exit, run the pascal compiler, and wait again. We blamed the many instances of the compiler/linker running for the slowness, we never thought of the editor itself. Or both. The difficulty of getting computer time pushed me to get my first computer (paid by my parents, of course). An Amstrad PC1512. I would never have become proficient with programming using the Uni resources only. -- Cheers, Carlos.
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D'Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2024-11-15 21:58 +0000 |
| Message-ID | <vh8g64$3jtlv$4@dont-email.me> |
| In reply to | #5625 |
On Fri, 15 Nov 2024 14:28:22 +0100, Carlos E.R. wrote: > The difficulty of getting computer time pushed me to get my first > computer (paid by my parents, of course). An Amstrad PC1512. I would > never have become proficient with programming using the Uni resources > only. In my day (slightly earlier than yours, with less access to our own computers), the way to get more access to the computer lab was after hours, like in the middle of the night. You could have your choice of terminals.
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2024-11-16 01:18 +0100 |
| Message-ID | <3v4l0lxt7c.ln2@Telcontar.valinor> |
| In reply to | #5628 |
On 2024-11-15 22:58, Lawrence D'Oliveiro wrote: > On Fri, 15 Nov 2024 14:28:22 +0100, Carlos E.R. wrote: > >> The difficulty of getting computer time pushed me to get my first >> computer (paid by my parents, of course). An Amstrad PC1512. I would >> never have become proficient with programming using the Uni resources >> only. > > In my day (slightly earlier than yours, with less access to our own > computers), the way to get more access to the computer lab was after > hours, like in the middle of the night. You could have your choice of > terminals. I don't think our college was open at nights. There was somewhere where they assigned our time, some paper or something. I don't remember. Possibly because some staff had to be there watching us. -- Cheers, Carlos.
[toc] | [prev] | [next] | [standalone]
| From | Lynn Wheeler <lynn@garlic.com> |
|---|---|
| Date | 2024-11-15 15:21 -1000 |
| Message-ID | <878qtkx9ay.fsf@localhost> |
| In reply to | #5634 |
"Carlos E.R." <robin_listas@es.invalid> writes: > I don't think our college was open at nights. There was somewhere > where they assigned our time, some paper or something. I don't > remember. > > Possibly because some staff had to be there watching us. IBM, not DEC ... took 2hr intro to fortran/computers and at the end of the semester the univ hired me to re-implement 1401 MPIO in 360 assembler for 360/30. Univ was getting a 360/67 for tss/360, replacing 709/1401 and got 360/30 replacing 1401 temporarily (until 360/67 was available). Univ shutdown datacenter on weekends and I would have the machine room dedicated all weekend, although 48hrs w/o sleep made monday classes hard. They gave me a bunch of hardware & software manuals and I got to design and implement my own monitor, device drivers, interrupt handlers, error recovery, storage management, etc. and within a few weeks had a 2000 card assembler program. I quickly learned when I 1st came in sat. morning to clean tape drives and 1403 printer and disassemble and clean 2540 card reader/punch. Sometimes when I arrived, the place would be dark, production work had finished early, and they shut the place down. Sometimes the 360/30 wouldn't power up and reading manuals and trial and error, learned to put all controllers in CE mode, power on 360/30 and controllers individually and then take controllers out of CE mode. the 360/67 came in within a year of taking intro class and univ. hires me fulltime responsible of os/360 (tss/360 never came to fruition so ran as 360/65 with os/360, I continue to get the machine room dedicated for weekends). Student fortran ran under a second on 709 but initially over a minute with os/360. I install HASP cutting the time in half. I then start redoing stage2 sysgen to carefully place datasets and PDS members to optimize arm seek and multi-track search, cutting another 2/3rds to 12.9secs. Student fortran never got better than 709 until i install Univ. of Waterlook WATFOR. Then before I graduate, I'm hired fulltime into small group in Boeing CFO office to help with formation of Boeing Computer Services, place all dataprocessing in an independent business unit. I thot Renton datacenter largest in the world, couple hundred million in 360 stuff, 360/65s arriving faster than they could be installed, boxes constantly staged in the hallways around the machine room (somebody joked that Boeing was buying 360/65s like other companies bought keypunches). -- virtualization experience starting Jan1968, online at home since Mar1970
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D'Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2024-11-16 01:52 +0000 |
| Message-ID | <vh8tt9$3mgp1$1@dont-email.me> |
| In reply to | #5634 |
On Sat, 16 Nov 2024 01:18:11 +0100, Carlos E.R. wrote: > I don't think our college was open at nights. I remember we could get keys. The labs had their own exterior doors. > Possibly because some staff had to be there watching us. Security were on patrols. They’d come by, exchange greetings, see that we were up to no good, and then go away again.
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2024-11-16 03:03 +0100 |
| Message-ID | <r3bl0lx3vk.ln2@Telcontar.valinor> |
| In reply to | #5637 |
On 2024-11-16 02:52, Lawrence D'Oliveiro wrote: > On Sat, 16 Nov 2024 01:18:11 +0100, Carlos E.R. wrote: > >> I don't think our college was open at nights. > > I remember we could get keys. The labs had their own exterior doors. Not ours. > >> Possibly because some staff had to be there watching us. > > Security were on patrols. They’d come by, exchange greetings, see that we > were up to no good, and then go away again. No, it would have to be some staff of the computer department. Another problem would be to get to the college without a car, as buses did not run during the night. I didn't hear of anybody doing nights in there, and I did know some students that were deep into the department. -- Cheers, Carlos.
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D'Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2024-11-16 03:33 +0000 |
| Message-ID | <vh93pl$3r5hr$3@dont-email.me> |
| In reply to | #5639 |
On Sat, 16 Nov 2024 03:03:07 +0100, Carlos E.R. wrote: > Another problem would be to get to the college without a car, as buses > did not run during the night. Ah, this is why all the choice student accommodation was close to the University. I recall, from the block of flats I was in, there was a shortcut across an empty section to get there even quicker. Though there was this one winter night, I had neglected to check how cold it was going to get, and I remember going home in the wee hours, shivering in this thin pullover all the way. Later I found the overnight temperature had got as low as 2-3°C.
[toc] | [prev] | [next] | [standalone]
| From | scott@slp53.sl.home (Scott Lurndal) |
|---|---|
| Date | 2024-11-16 15:14 +0000 |
| Message-ID | <EF2_O.13512$OVd1.5378@fx10.iad> |
| In reply to | #5643 |
Lawrence D'Oliveiro <ldo@nz.invalid> writes: >On Sat, 16 Nov 2024 03:03:07 +0100, Carlos E.R. wrote: > >> Another problem would be to get to the college without a car, as buses >> did not run during the night. >Though there was this one winter night, I had neglected to check how cold >it was going to get, and I remember going home in the wee hours, shivering >in this thin pullover all the way. Later I found the overnight temperature >had got as low as 2-3°C. Our computer science building was open 27x7, the coldest day walking to the office had a wind-chill of -80F. 2C is nothing (it's currently -2.78C here in california).
[toc] | [prev] | [next] | [standalone]
| From | Bob Eager <news0009@eager.cx> |
|---|---|
| Date | 2024-11-16 22:21 +0000 |
| Message-ID | <lpsk83F8f6U16@mid.individual.net> |
| In reply to | #5649 |
On Sat, 16 Nov 2024 15:14:44 +0000, Scott Lurndal wrote: > Lawrence D'Oliveiro <ldo@nz.invalid> writes: >>On Sat, 16 Nov 2024 03:03:07 +0100, Carlos E.R. wrote: >> >>> Another problem would be to get to the college without a car, as buses >>> did not run during the night. > >>Though there was this one winter night, I had neglected to check how >>cold it was going to get, and I remember going home in the wee hours, >>shivering in this thin pullover all the way. Later I found the overnight >>temperature had got as low as 2-3°C. > > Our computer science building was open 27x7, the coldest day walking to > the office had a wind-chill of -80F. 2C is nothing (it's currently > -2.78C here in california). My room an campus (for two years) was less than two minutes' walk. It was actually the nearest room on campus to the computer building. -- Using UNIX since v6 (1975)... Use the BIG mirror service in the UK: http://www.mirrorservice.org
[toc] | [prev] | [next] | [standalone]
| From | "John H. Reinhardt" <johnhreinhardt@thereinhardts.org> |
|---|---|
| Date | 2024-11-16 18:01 -0600 |
| Message-ID | <lpsq33FlhmmU3@mid.individual.net> |
| In reply to | #5653 |
On 11/16/2024 4:21 PM, Bob Eager wrote: > > My room an campus (for two years) was less than two minutes' walk. It was > actually the nearest room on campus to the computer building. > About the same for me. Living in Deming Basement it was 30 ft to the East exit, down an embankment and in the back door of the Waters Computing Center and through the room once used for drafting classes but where I learned PASCAL and FORTRAN and into the terminal room. Around 2 minutes depending on how fast you slid down the embankment. ;) The doors locked around 11PM but you could sign up for a waver from the computing center management and be allowed to stay past closing - you just had to stay all night until morning when they opened up again. Once the doors were locked, if you left you could not get back in. -- John H. Reinhardt
[toc] | [prev] | [next] | [standalone]
| From | scott@slp53.sl.home (Scott Lurndal) |
|---|---|
| Date | 2024-11-17 18:12 +0000 |
| Message-ID | <8mq_O.3656$ZXyf.536@fx35.iad> |
| In reply to | #5653 |
Bob Eager <news0009@eager.cx> writes: >On Sat, 16 Nov 2024 15:14:44 +0000, Scott Lurndal wrote: > >> Lawrence D'Oliveiro <ldo@nz.invalid> writes: >>>On Sat, 16 Nov 2024 03:03:07 +0100, Carlos E.R. wrote: >>> >>>> Another problem would be to get to the college without a car, as buses >>>> did not run during the night. >> >>>Though there was this one winter night, I had neglected to check how >>>cold it was going to get, and I remember going home in the wee hours, >>>shivering in this thin pullover all the way. Later I found the overnight >>>temperature had got as low as 2-3°C. >> >> Our computer science building was open 27x7, the coldest day walking to >> the office had a wind-chill of -80F. 2C is nothing (it's currently >> -2.78C here in california). > >My room an campus (for two years) was less than two minutes' walk. It was >actually the nearest room on campus to the computer building. > I had an apartment just on the campus border, about two blocks from the CS building. Had an office in the adjacent Statistics building once I started working part-time for the computer center starting my sophmore year. Convenient place to leave books during between classes. The campus buildings were heated with steam generated at the university power plant, so there were tunnels connecting all the buildings on campus. Exploring the tunnel system was a common passtime in those days (today, I would expect to find far too many cameras), and with the CS building open 24x7, it was a convenient starting point to avoid entering through visible manholes.
[toc] | [prev] | [next] | [standalone]
| From | Bob Eager <news0009@eager.cx> |
|---|---|
| Date | 2024-11-17 18:57 +0000 |
| Message-ID | <lpusk1F8f6U18@mid.individual.net> |
| In reply to | #5656 |
On Sun, 17 Nov 2024 18:12:20 +0000, Scott Lurndal wrote: > Bob Eager <news0009@eager.cx> writes: >>On Sat, 16 Nov 2024 15:14:44 +0000, Scott Lurndal wrote: >> >>> Lawrence D'Oliveiro <ldo@nz.invalid> writes: >>>>On Sat, 16 Nov 2024 03:03:07 +0100, Carlos E.R. wrote: >>>> >>>>> Another problem would be to get to the college without a car, as >>>>> buses did not run during the night. >>> >>>>Though there was this one winter night, I had neglected to check how >>>>cold it was going to get, and I remember going home in the wee hours, >>>>shivering in this thin pullover all the way. Later I found the >>>>overnight temperature had got as low as 2-3°C. >>> >>> Our computer science building was open 27x7, the coldest day walking >>> to the office had a wind-chill of -80F. 2C is nothing (it's >>> currently -2.78C here in california). >> >>My room an campus (for two years) was less than two minutes' walk. It >>was actually the nearest room on campus to the computer building. >> > I had an apartment just on the campus border, about two blocks from the > CS building. Had an office in the adjacent Statistics building once I > started working part-time for the computer center starting my sophmore > year. Convenient place to leave books during between classes. > > The campus buildings were heated with steam generated at the university > power plant, so there were tunnels connecting all the buildings on > campus. Exploring the tunnel system was a common passtime in those > days (today, I would expect to find far too many cameras), and with the > CS building open 24x7, it was a convenient starting point to avoid > entering through visible manholes. I just measured how far it was. 120 yards. -- Using UNIX since v6 (1975)... Use the BIG mirror service in the UK: http://www.mirrorservice.org
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2024-11-16 21:05 +0100 |
| Message-ID | <7ian0lx0ks.ln2@Telcontar.valinor> |
| In reply to | #5643 |
On 2024-11-16 04:33, Lawrence D'Oliveiro wrote: > On Sat, 16 Nov 2024 03:03:07 +0100, Carlos E.R. wrote: > >> Another problem would be to get to the college without a car, as buses >> did not run during the night. > > Ah, this is why all the choice student accommodation was close to the > University. I recall, from the block of flats I was in, there was a > shortcut across an empty section to get there even quicker. Most of the university in Madrid was in the north, what was called "University City". But this college of mine was at the other end of Madrid, in the south, in one of the radial roads out of the city, a few kilometres out. > > Though there was this one winter night, I had neglected to check how cold > it was going to get, and I remember going home in the wee hours, shivering > in this thin pullover all the way. Later I found the overnight temperature > had got as low as 2-3°C. Heh. -- Cheers, Carlos.
[toc] | [prev] | [next] | [standalone]
| From | Robin Haberkorn <robin.haberkorn@googlemail.com> |
|---|---|
| Date | 2024-11-15 15:49 +0300 |
| Message-ID | <a6c98a30-69b4-2e1d-8158-09ee8f5ebc30@googlemail.com> |
| In reply to | #5610 |
[Multipart message — attachments visible in raw view] — view raw
On Thu, 14 Nov 2024, Lawrence D'Oliveiro wrote: > MI␛␛ > > This would echo on-screen as > > MI$$ > > and so my fellow students, trying to follow my instructions by looking at > the screen output I was producing instead of what I was saying (“emm eye > escape escape”, I said), would type “$” instead of pressing the ESC key, > and they would be mystified why it wouldn’t work. > > It took them two or three attempts before I noticed what they were doing > wrong ... > I know that of course. In all of my materials (also in SciTECO itself), I am printing Escape and all ^x control characters in reverse (or at least in bold) in order to visually highlight that they are not to be read verbatim.
[toc] | [prev] | [next] | [standalone]
| From | Robin Haberkorn <robin.haberkorn@googlemail.com> |
|---|---|
| Date | 2024-11-15 16:51 +0300 |
| Message-ID | <716d3d6d-a1d0-efb7-becc-79deb5c60ab8@googlemail.com> |
| In reply to | #5623 |
[Multipart message — attachments visible in raw view] — view raw
On Fri, 15 Nov 2024, Robin Haberkorn wrote: > On Thu, 14 Nov 2024, Lawrence D'Oliveiro wrote: > >> MI␛␛ >> >> This would echo on-screen as >> >> MI$$ >> >> and so my fellow students, trying to follow my instructions by looking at >> the screen output I was producing instead of what I was saying (“emm eye >> escape escape”, I said), would type “$” instead of pressing the ESC key, >> and they would be mystified why it wouldn’t work. >> >> It took them two or three attempts before I noticed what they were doing >> wrong ... >> > I know that of course. In all of my materials (also in SciTECO itself), I am > printing Escape and all ^x control characters in reverse (or at least in > bold) in order to visually highlight that they are not to be read verbatim. By the way, in SciTECO you *can* write MI$$ with dollar signs. Not that you need any kind of command line termination in order to execute macro `I` - that would happen immediately the moment you type `I`. But dollar-dollar would terminate the command line just like Escape-Escape would. The reason is that I made dollar synonymous to Escape as a regular command (not as a string terminator). And Escape-Escape is a regular command in SciTECO instead of an immediate editing construct as it was in classic TECOs. This also means, you don't have to fear accidentally terminating a command line when pressing two Escapes in a row in order to pass an empty string argument. FRfoo$$ is completely safe in SciTECO - the escapes are part of the FR syntax. Only afterwards, parsing resumes with regular commands. So to delete with FR and terminate the command line, you would have to write FRfoo$$$$. But you don't terminate the command line often. You can edit an entire day without $$. The process will grow in size, but it's still a fraction of VS Code, I guarantee you that.
[toc] | [prev] | [next] | [standalone]
Page 4 of 5 — ← Prev page 1 2 3 [4] 5 Next page →
Back to top | Article view | alt.sys.pdp11
csiph-web