Quote:
|
Originally Posted by sdabbs65
I realize my mistake,
<snip>
I subsequently familiarised myself with FORTRAN, Algol, COBOL, TECO and MIC, stubbornly read the TOPS-10 system call manual, and became addicted to MACRO-10 programming. I began writing serious software; my IRC-like chat program, email system, DECtape control daemon and exploitation of a disk quota bug gained me the not wholly welcome attention I evidently deserved.
<snip>
thanks for the tip and Have a Nice Day.
|
RAOFLMAO!!
I knew that feeling, being dragged into the Provost's Office to explain exactly what I'd done to get that many blocks of storage.
I think so many people knew that bug that it was more of a "optional storage feature for those who actually know how to use the machines".
I still miss those 1970's DEC PDP-10 machines. I wonder when bash/*nix/gnu will become as featurefull and useable as TOPS-20 was. And I still find programming easiest if I can think about it in FORTRAN first.
For you youngsters, TOPS-10 was the OS where .EXE meant "Executable file". it was the first OS where there was built in help using /? or -?, as well as the funky "help by hitting ESC twice" where it would prompt you what arguements a command wanted, including context, and do it inline with the command you were typing. MACRO-10 and MACRO-20 were psuedo assembly languages that let you run the core routines from the ROM Monitor Program (kinda like BIOS, in the same way a skyscraper is kinda like a grass hut, where BIOS is the grass hut!). A complete file copy program was around 6 instructions as I recall, and compiled to about 30 words - about 124 bytes.