Mature mainframe madness prints Mandlebrot fractal in TWELVE MINUTES A programmer better known for work on Arduino has shown off handy vintage mainframe skills, getting an ancient IBM 1401 to buzz away on its 1403 line printer to produce the classic Mandelbrot fractal image. It's not as trivial as it sounds. In this blog post on the “12-minute Mandelbrot”, Ken Shirriff explains that programming …
I don't have any mainframe experience, but I do have a love for dot matrix printers. I've got a small collection of good ones, and in fact have one hooked up and turned on most of the time. It works fine for printing out personal stuff, and showing up at the odd meeting with a piece of perforated computer paper does garner a comment or two.
We still regularly buy dot matrix printers for our customers.
In the slaughter industry, the scales and Fat-o-Meters are often connected to a DMP in order to print the legal protocol. They are slowly being phased out by tamper-proof memory in the devices, but I guess we order a few dozen Epson FX890s every year. But they are getting darned expensive, because they are made in relatively small batches, due to lack of demand.
In theory it will print a compolete line in one revolution of the drum.
And makes a hell of a noise doing it, while throwing paper feet into the air if it wasn't in the guides properly. The band printers were slightly better, just a permanent ripping-calico noise, still way louder than dot-matrix, even they could get through a 2000-page box of fanfold in no time flat.
When I first saw a high-speed laser printer in action (looked more like an old-style newspaper press) it was truly eerie to hear how quiet it was, despite the paper spewing from the back.
There was a Hewlett-Packard drum printer (back from when HP was still a respected name making well-engineered stuff) that had only 44 rings of characters on its drum, and a matching set of hammers, apparently to save on driver electronics and hammer banks. Printing a full line was achieved by shuffling the paper left and right by way of an excenter crank. This somewhat Rube Goldberg-ish contraption needed three drum rotations per line. The line buffer was implemented using shift registers, one per bit.
(insert cobwebs.ico)
It wasn't always machine gun noise. The chain printer attached to a 1401 in the IBM Data Centre in Newman St., London used to play carols at Christmas. Someone wrote a program with the text to print chosen so the hammers hitting the chain produced the right notes. It was quite a credible rendition...
Also unless my memory isn't what it used to be, assembler didn't seem that hard compared to C++ today!
Modern stuff!
Real mainframes used the old line printers, with individual sets of characters on a band that went round and hit the paper like a typewriter letter. From what I remember when we used them on an IBM 370/148 they did about 600 lines per minute. The technology was handy for doing multiple copies as we had lineflo paper with carbon paper interleaved.
A colleague had worked for the Gas Board as an operator some years before, and one of their people had realised that if you printed certain combinations of characters repeatedly you got different sounds from the printer as the bands vibrated. They then worked on the details, and soon had a set of cards ready which, when run, got the printer to play the National Anthem.
I believe that was the same colleague who had a problem one day: the bosses were bringing important guests to see their ultra-modern machine room, but complained afterwards that it had been very dull and boring - they were all just sitting around doing nothing. Of course they were actually in the middle of a long billing run, and the numbers were being crunched. So before the next official visit they prepared a program which they ran as soon as the visitors were spotted: it suspended the real job, and then started lights flashing, printer lids going up and down, tapes rewinding and unmounting etc etc. Not exactly productive, but it impressed the hell out of the visitors!
Ah, the joys of real computers!
One nice thing about working on billing system for the Gas Board - your work could be made famous by the popular Sunday night consumer affairs show "That's Life".
As I recall, they had regular features about how rubbish computers were, usually because a pensioner had received a gas bill for 2 million quid or whatever.
@Pen-y-gors The national anthem…?! Pah! Kids stuff! Prepare to have your mind blown…
https://youtu.be/u8I6qt_Z0Cg
Krauts are Krazy - and I wanna know how they do it! Check out the rest of their channel, too, their latest 'release' is the Who Wants To Be A Millionaire? theme.
If that link doesn't work, search YT for 'MIDI Desaster'.
My uni was bought out by the borg, all of our CS department had sponsored Dell-Windows kit. The one redeeming aspect was that they took the less decrepit old hardware and gave us a "linux lab", with a daisywheel line printer that was free to use from linux (compared to 10p a page for any other printer). I still have several of the more useful RFCs I spent hours printing out on it...
You're exactly right - standard equipment for a 1401 was a 1403 line printer.
In the early 80s, I worked as a computer operator for about a year - the dinosaur pen had a row of IBM 360/50s, and a bunch of shared devices like tape drives and 3 line printers (not 1403s, a later and even faster model). There is no question that I did permanent damage to my hearing when I ran the printer with the cover up. I don't even remember WHY I would do that - the dang thing spit paper so fast that you couldn't really yank printouts without pausing it. The noise is really indescribable.
One of the fun things the printer had was a "carriage control band" - this was a paper loop that went over two sprockets, and programs could do a form skip to a specific spot on the page, which was nice for printing on forms, or to put the page totals in the same spot on each page without having the program have to count and skip individual lines. If you installed the wrong band, or didn't line it up right, or it slipped off, the printer would yank paper through the tractors so fast that it would fountain up into the air, and it would usually empty an entire box (I want to say 2000 pages but I don't remember) in just a minute or so - you never really wanted to turn your back on the things.
Ah, my early days in the pre-Windows era of IT! Mainframes!
I remember how the programmers used to carefully write code to facilitate the oh, so limited memory these oversized, basement situated systems used..
We had a room dedicated to our noisy band printers and dot matrix printers, which were connected via Centronics or Serial (RS232/422) interfaces.
I recall getting ASCII art on 1200ft reel tape and printing it, whoop! Dot matrix art of a Manga-esque girlie in a bikini...
Life was so simple back then... when multimedia was using a Walkman while in the computer room and gaming was trying to beat the mainframe at "hangman" and "tic-tac-toe"
I still had a tape reel of ASCII art until relatively recently. Think it finally went when I moved house 3 years or so ago. As I'd not had anything with a tape drive since leaving a previous job (with an ageing AS/400) nearly 15 years before there didn't seem much point in keeping it.
Glen
Life was so simple back then... when multimedia was using a Walkman while in the computer room and gaming was trying to beat the mainframe at "hangman" and "tic-tac-toe"
Well you say that. But I found that life soon stopped being simple, when I eschewed the pleasures of Hangman or chess, and decided to play Global Thermonuclear War...
Your code can't have been very good, my Spectrum version took 16 hours.
I used to rewrite my old Spectrum Mandelbrot program for every new system / language I worked on. It was impressivley fast on one of those Casio graph calculators and incredibly slow in Visual Basic v1 on a 386.
Same here....Just getting it sorted in javascript and rendering in 3d using Babylon - a wrapper around webGL.
Sub-second rendering times. How times have changed.
The next step is to convert the mandlebrot code to work as a shader algorithm so that the graphics hardware can do the maths.
You did it in BASIC?
I did it in 6502 assembly code on my Atom, sending the output directly to an Epson LX80, with different grey scales representing different divergence rates to infinity, leaving it chuntering away overnight and the next day, and then reassembling the pages to make poster sized Mandelbrot and Julia set images.
Did it again a few years later in 386/387 assembly code, and what used to take all night to create one image ran as an animation with changing Julia set parameters.
Depending on model the 1403 printer could achieve 1100 lpm (and throw blank paper out at a speed that had a real danger of causing friction fire!).
We (local Electricity Board) were using a 1401 in 1965 as a slave machine to spool bills, final notices & meter sheets 4 times a year for 2.5 million accounts. (From spool tapes produced by the 100k character memory 1410 mainframe). The throughput of the two 1403s was so great that we employed junior operators just to stand behind the printers ready to change boxes of fanfold stationery as soon as they emptied.
@ Catterbutts
I visited a customer, a bank's data center, all IBM and with all that came with it, like raised floors and the like. Around 73 I think. There was one of those "drum" printers, from the printer's last pages of paper there was a string tied to the leg of an operator sitting at his desk warning him about paper out slightly in advance. Hightech, who cares.
Looking at the printout it's very easy to see what kind of printer was used. If the character jump up and down on the line it's made on one of those drums.
The first laser printers where huge too in those years.
@Richard Taylor 2: Your statement deserves 0001 0000 0000 upvotes.
Seriously though, computer arithmetic is a very interesting subject when you see where approximations are made, and how errors can propagate.
Integers can be used for many assumed floating operations that do not change scale. e.g. molecular distance calculations. However, often the hardware is optimised for approximate fixed point calculations, and double precision is a tragedy in GPU computing....
P.
Reminds me of the story of a machine at a certain Establishment in Berkshire that was programmed to run Space Invaders.
It printed out a screen in ASCII (or EBCDIC?) characters, waited for user input of Left, Right or Fire, then printed the next screen.
As immortalised in Dave Langford's "The Leaky Establishment" - but taken from an actual event.
I remember a 5-line piece of BASIC to generate the set ... ran on a BBC micro I believe.
I used Fractint as a performance benchmark for some years - I had a 3.5" floppy with speeds of machines scrawled on the label (initially straight then the writing filled gaps up the side :-) ) starting with an 80186 and finishing at something like the second generation Pentium.
The IBM 1620 I once programmed used binary coded decimal arithmetic. That meant one could manipulate very long numbers. I used it to calculate pi to 300 places.
Part of that calculation involved finding the square root of three to 300 places, which entailed a loop in which a 600 place number was divided by a 300 place number. A single hardware divide instruction took about one second to do that, as shown by the flashing lights.
The real use of BCD is in finance, to represent billions of dollars to the nearest cent without rounding errors for simple addition and subtraction. Percentages and currency conversions still have to be rounded, of course. VAX computers included BCD instructions for use with their COBOL compilers and variables of type COMPUTATIONAL.
Nowadays this long-length arithmetic would be useful for cryptography.
Indeed. The VAX had the usual integer and float types, plus BCD, which, if I remember correctly, stores two decimal digits per byte, plus zoned decimal, which is essentially ASCII, one decimal character per byte with a sign bit added to the least significant digit. Zoned decimals were much used in the DIBOL language.
I'm also reasonably sure that I remember using BCD on a 16-bit microprocessor, but I can't recall which one. There must have been some kind of support for BCD for me to have thought of using it.
Just about every usual description of a CPU will say the 6502 is an 8 bit processor.
While the 6502 did have a BCD mode, it only affected two instructions ADC and SBC (add/subtract with carry) - things like INC and . Many other CPUs (e.g. 6800, 6809, 8080, 80x86, Z80) have a 'decimal adjust accumulator' (DAA) type instruction where, if you want to do BCD arithmetic, you do it in normal binary mode and then do a 'DAA' to fix up the BCD result and carry/overflow flags.
Why would BCD help you "represent billions of dollars to the nearest cent without rounding errors for simple addition and subtraction"? Any fixed-point representation (binary, decimal, duodecimal or whatever) would avoid rounding errors for addition and subtraction. If you also want to avoid overflow then you need arbitrary precision integers, and if you need exact division then you need a proper implementation of rational numbers, but a 64-bit signed integer (or a long long in C) representing a number of cents takes you up to 92233 billions of dollars even if you use proper European billions.
The Register 
Biting the hand that feeds IT
Copyright. All rights reserved © 1998–2024
