ICL System 4/70 with MultiJob. COBOL programmer. ICL 2970, 2980, 2988. George 3 under DME on ICL 2960/2966. Then I turned to the dark side and got involved with IBM PCs. Then Unix. Then IBM PC compatibles.
Thankfully all behind me now. :-)
Ah, memories.
Dave R
Didn't find your answer? Ask the community — no account required.
R
Reentrant
25 years at IBM for me, 16 of those in the PC Co. By 2000 there were six large office blocks overflowing with IBMers here in Basingstoke. Today - nothing.
B
Bob Eager
Incomplete as yet, but:
formatting link
B
bert
Aka Multibodge
V
Vir Campestris
My first job was on VME/K development. It should have been canned years before. We'd just about got it working and reliable (SV18) when ICL finally did pull the plug. On a system with a larger order book than installed base... I never went to West Gorton, though Kidsgrove was a frequent trip, all the way from Bracknell.
I'm still developing S/W now. The machines have a thousand times more RAM, and run a thousand times faster. But now they fit in my pocket!
Andy
B
Bob Eager
VME/K was a mess. The last version we used was SV12. SV13 was a big change and it was wholly unsuitable for us. So we moved to the homebrew operating system, which increased the MTBF from 20 hours to about 2000! And was more functional.
You might like to read my anecdotes:
formatting link
some of which are VME/K (or 2900) related.
Also, have you read the 'ICL Anthology' books (which are the source of the story of the middle manager and his car)?
A
Andrew Mawson
T
Tim Streater
Don't forget Elliott Automation and English Electric Leo Marconi (EELM) which were also force-merged into ICL.
A
Andrew Gabriel
ICT also got the data processing parts of English Electric and Elliot Automation and Marconi, as the government tried to merge all the data processing expertise into one British company in the hope it would create a company which could compete in the world.
Likewise, all the process control and military computing from English Electric and Marconi was merged into Elliott Automation, which became Marconi Elliott Computer Systems briefly, and then GEC Computers a year later. GEC later also absorbed the process control and military computing from Ferranti (I think that's all that was left of Ferranti by then).
The agreements around these government driven mergers forbid ICT (ICL) from building process control systems, and forbid Elliott Automation (GEC) from building data processing systems for some years afterwards, so they would both concentrate on their areas of expertise and not try to compete with each other.
M
Martin
Correct!
M
Martin
and the coating fell off in pieces.
B
Broadback
With all that government interference is it any wonder that the UK computer systems manufacturing has failed!
M
Martin
Did you also discover that Honeywell DDP 516 interface hardware had both design and construction faults?
M
Martin
The standard DDP516 had a 8K byte Ram.
M
Martin
The govt. interference was bailing out failed companies.
T
The Other Mike
400Hz I could possibly believe, 400kHz you might find in a modern switch mode power supply, but 400Mhz for a power supply is a load of bollocks.
B
Bob Eager
I did more on hacking the CPU than anything else.
B
Bob Eager
And, going back a bit, The British Tabulating Machine Co. and Powers Samas!
A
algrant109
It was already failing as far back as the mid-60s. There was a fragmented collection of companies who were each failing to produce competitive systems. The government response was two-fold - try and consolidate the industry in an effort to catch up with the Americans, and meanwhile allow the top universities and essential government departments to buy American. I.e. even by the mid-60s it was recognised that a buy-British policy meant the UK's industrial and scientific progress was being held back by substandard equipment.
I've never used an Elliot 803 although I did once win a programming contest on the one at TNMoC. But I do have a manual for it and it's an appalling mess. Absolutely no comparison with IBM manuals of the same vintage or even earlier, for clarity and usability.
M
Martin
I started with a bootstrap loader an assembler and Honeywell diagnostic programmes that in many cases did nothing. Most of the diagnostics didn't use interrupts. In most cases the hardware was wrong and either didn't trigger interrupts or triggered them at the wrong time. I wrote a simple OS and drivers for most devices before getting on with what I really wanted to do
Join the Discussion
Have something to add? Share your thoughts — no account required.
Didn't find your answer?
Ask the community — no account required
Report Content
You are reporting this content to the moderators. They will look at it
ASAP.