From: steve jenkin <sjenkin@canb.auug.org.au>
To: Gavin Tersteeg <gctersteeg@gmail.com>
Cc: TUHS <tuhs@tuhs.org>
Subject: [TUHS] Re: LSX issues and musing
Date: Wed, 3 Aug 2022 14:32:10 +1000 [thread overview]
Message-ID: <496D2B07-8C23-4D2F-ABA7-132E8E2106C6@canb.auug.org.au> (raw)
In-Reply-To: <CA+99DoJHumFEutVP=ZJL33u4AKJFsg7U8iujxrw9MYH3TNUYpw@mail.gmail.com>
> On 3 Aug 2022, at 03:56, Gavin Tersteeg <gctersteeg@gmail.com> wrote:
>
> My target system (A Heathkit H11) does have the full 56K of memory,
I wasn’t aware of the Heathkit H11 in 1980.
Did work with someone circa 1984 that owned a DEC device, a VT71 or VT72, that had an LSI-11 + Q-Bus inside.
The H11 wasn’t that differently priced to the IBM PC 3 years later, at least for an entry system.
Any ideas on why businesses didn’t pick up the H11 in 1980?
[priced too high for hobbyists]
Possibly: Marketing, ’support’, form-factor/physical size, peripherals - no display / keyboard on H11, serial terminal - or ’software’ availability?
Price didn’t win the market. IBM’s 5150 was never “cheapest” or technically “best” at any time - hence rapid rise of (variable quality) clones, built down to a price.
Gates, Allen & Ballmer understood business users wanted “Off the Shelf Software" from Independent Software Vendors (ISV’s).
For ISV's to target/support MS-DOS 1.0, Microsoft provided a mechanical translation tool to convert from CP/M executable to MS-DOS.
Wikipedia says:
1978: H11 US$1295 (kit) or US$1595 fully assembled ("4kword base system”)
display advert <http://www.decodesystems.com/heathkit-h11-ad-1.gif> $1295 kit + postage/freight, bare system, 8KB (4kword), 6 Q-bus slots free. ROM ?
1981: IBM 5150(PC) US$1,565 for "16 KB RAM, Color Graphics Adapter, and no disk drives.”
( I only saw 5150’s with 2x 5.25” 360KB floppies included - otherwise, can’t run programs & store files)
( we had someone buy an almost clone with 2x 8” floppies, @ 1.2MB each to run a database they had, 320/360K didn’t cut it )
--
Steve Jenkin, IT Systems and Design
0412 786 915 (+61 412 786 915)
PO Box 38, Kippax ACT 2615, AUSTRALIA
mailto:sjenkin@canb.auug.org.au http://members.tip.net.au/~sjenkin
next prev parent reply other threads:[~2022-08-03 4:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-31 19:57 Noel Chiappa
2022-08-01 5:37 ` Heinz Lycklama
2022-08-02 17:56 ` Gavin Tersteeg
2022-08-03 4:32 ` steve jenkin [this message]
2022-08-03 4:55 ` Ron Natalie
2022-08-03 5:09 ` G. Branden Robinson
-- strict thread matches above, loose matches on Subject: below --
2022-08-05 4:35 Paul Ruizendaal via TUHS
2022-08-03 15:17 Noel Chiappa
2022-07-11 23:47 Noel Chiappa
2022-07-15 8:07 ` Gavin Tersteeg
2022-07-27 8:02 ` Gavin Tersteeg
2022-07-27 16:24 ` Heinz Lycklama
2022-07-30 4:39 ` Gavin Tersteeg
2022-07-11 21:47 Paul Ruizendaal via TUHS
2022-07-11 21:24 Noel Chiappa
2022-07-11 21:37 ` Gavin Tersteeg
2022-07-11 21:06 Noel Chiappa
2022-07-11 19:47 [TUHS] " Gavin Tersteeg
2022-07-11 20:01 ` [TUHS] " Warner Losh
2022-07-11 20:26 ` Clem Cole
2022-07-11 20:30 ` Warner Losh
2022-07-11 20:37 ` Phil Budne
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=496D2B07-8C23-4D2F-ABA7-132E8E2106C6@canb.auug.org.au \
--to=sjenkin@canb.auug.org.au \
--cc=gctersteeg@gmail.com \
--cc=tuhs@tuhs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).