Feeds

The Dragon 32 is 30

Fire starter

Top three mobile application threats

Pippin but no togs

At that stage, Pippin consisted of little more than a motherboard wired up to a keyboard, but it was sufficiently complete for Richard Wadman, Clarke's marketing manager, to begin promoting the micro to journalists and to potential software developers. Wadman would go on to write the Dragon's Basic programming manual.

Pippin, the caseless Dragon 16 prototype. Source: DragonData.co.uk

Pippin, the Dragon 32 - then, the Dragon 16 - caseless prototype
Source: DragonData.co.uk

The Mettoy board approved Clarke's plan, and PAT was asked to oversee the initial production run. Newport-based Race Electronics was contracted to manufacture the first batch of Dragons.

It's unclear quite when Race began punching out machines. However, after production had begun, it was decided by Clarke, now head of Mettoy subsidiary Dragon Data, that the machine would need to ship with 32KB of memory, double that designed into the prototype.

It is said that the change was prompted by the arrival of the 16KB and 48KB Sinclair Spectrum, both of which were cheaper than the Dragon's planned £200 price point. Undoubtedly, Clarke figured the Dragon's full-size keyboard and tough plastic case would make the premium over the £175 48KB Spectrum seem reasonable, but not if the Dragon only shipped with 16KB. Doubling the amount of Ram would also help the Dragon compete with the BBC Micro, by early 1982, also on the market.

Dragon 32

More Ram, please. Designed for 16KB, early Dragons gained an extra 16kB daughtercard before release

PAT's motherboard layout wouldn't accept the extra Ram chips, so the first 10,000 machines, the initial production run, all required a 16KB daughter card to be fitted and wired up to the main board.

The author's Dragon 32 - purchased for Christmas 1982 - contains board number 9977 complete with "piggy-back" memory board.

Microsoft's Basic code didn't incorporate lower-case letters: these appeared on screen as reverse-video capitals, though they printed correctly through the not-quite-standard "Centronics-type" parallel port.

The Dragon 32 supported the customary video output through a TV modulator, but it also had a composite video five-pin Din port for a monitor. Other Din ports were used for the two analogue joystick connectors, and for the obligatory cassette I/O. The Dragon had a Rom cartridge slot that filled 8KB of the 64KB memory map.

Dragon Data R&D team members

Members of Dragon Data's 1983 R&D team: (L-R) Duncan Smeed, Jan Wojna and John Linney
Picture taken in 1985 after they had joined Thorn EMI

64KB? Yes, the Dragon's memory map was plotted across that full range. Only the first 32KB was mapped onto the Ram chips, after which came the 16KB Rom chip then the Rom cartridge allocation - preventing cartridges being hot-swappable - the PIA chip registers, the SAM chip registers, and eight bytes of reset vectors.

Combat fraud and increase customer satisfaction

More from The Register

next story
Feast your PUNY eyes on highest resolution phone display EVER
Too much pixel dust for your strained eyeballs to handle
Samsung Galaxy S5 fingerprint scanner hacked in just 4 DAYS
Sammy's newbie cooked slower than iPhone, also costs more to build
Microsoft lobs pre-release Windows Phone 8.1 at devs who dare
App makers can load it before anyone else, but if they do they're stuck with it
Leaked pics show EMBIGGENED iPhone 6 screen
Fat-fingered fanbois rejoice over Chinternet snaps
Report: Apple seeking to raise iPhone 6 price by a HUNDRED BUCKS
'Well, that 5c experiment didn't go so well – let's try the other direction'
US mobile firms cave on kill switch, agree to install anti-theft code
Slow and kludgy rollout will protect corporate profits
Rounded corners? Pah! Amazon's '3D phone has eye-tracking tech'
Now THAT'S what we call a proper new feature
Zucker punched: Google gobbles Facebook-wooed Titan Aerospace
Up, up and away in my beautiful balloon flying broadband-bot
Sony battery recall as VAIO goes out with a bang, not a whimper
The perils of having Panasonic as a partner
NORKS' own smartmobe pegged as Chinese landfill Android
Fake kit in the hermit kingdom? That's just Kim Jong-un-believable!
prev story

Whitepapers

Designing a defence for mobile apps
In this whitepaper learn the various considerations for defending mobile applications; from the mobile application architecture itself to the myriad testing technologies needed to properly assess mobile applications risk.
3 Big data security analytics techniques
Applying these Big Data security analytics techniques can help you make your business safer by detecting attacks early, before significant damage is done.
Five 3D headsets to be won!
We were so impressed by the Durovis Dive headset we’ve asked the company to give some away to Reg readers.
The benefits of software based PBX
Why you should break free from your proprietary PBX and how to leverage your existing server hardware.
Securing web applications made simple and scalable
In this whitepaper learn how automated security testing can provide a simple and scalable way to protect your web applications.