Wow. Welcome! Glad you’ve found this list. If you haven’t already been there, we also have a general web page and a wiki (closest we’ve got so far to an FAQ)
https://sebhc.github.io/sebhc/
https://github.com/sebhc/sebhc/wiki
we can definitely help you.
So you’ve got a monitor prompt (“H:”)? If so great! What happened when you enter B for Boot? Does it try to boot from the floppy?
You may want to read an article I wrote in a series I call “REMarks” (still planning to write more of those by the way). See issue #3 for a full description of how to use Dwight Elvey’s approach:
https://sebhc.github.io/sebhc/REMarks/index.html
this assumes, of course, that you’ve got a hard-sectored floppy disk (the media), however we have now found a practical and reliable way to make these by using a punch to add the missing holes. So it is a possibility. If you like we can help get you some disks to play with.
Unfortunately it’s not straightforward to make a “Dwight Elvey” approach that works with the H37. Dwight’s program works because the H89 ROM contains low level routines for accessing the hard-sectored controller (the same can’t be said for the soft-sectored one).
You might want to consider using a GoTek and connecting it to the soft-sectored controller. We have images you could then download and boot from.
The FDD100-5 drive can be used with your H37 (soft-sectored) controller but most of the disk images in our archive are in “H8D” format which is for the hard-sectored drive (i.e. the Elvey approach). The FDD100-5 is also a single-sided drive so that limits you somewhat. You can use any old “PC” style drive that you may have.
I had never seen that cartoon you sent about the robot with the H8 emblem. Interesting!
The H89 was indeed an evolution from the H8. The H89 contains a single-board computer that essentially replicates (and upgrades) the H8 capability, for example it uses a Z80 instead of 8080…
Looking forward to more discussion…
-- 
You received this message because you are subscribed to the Google Groups "SEBHC" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sebhc+un...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/sebhc/CAG1tPesgxA7AmcK3WAM0V0N2%2B8sXVdRF6dZzpdi%3D94DYqHw%2B9Q%40mail.gmail.com.
Wow. Welcome! Glad you’ve found this list. If you haven’t already been there, we also have a general web page and a wiki (closest we’ve got so far to an FAQ)
To view this discussion visit https://groups.google.com/d/msgid/sebhc/0a9401dc4786%2409e20770%241da61650%24%40gmail.com.
At the very top of the SEBHC web page there are links to the Wiki and Google group. We also have an active Discord server if that’s of interest to you.
Not knowing how much you know about Heathkit computers, it’s hard to give you direction. I’ll assume you are starting largely from scratch. There were two primary operating systems. Heathkit first introduced their own OS Heath Disk Operating System (HDOS) and later (due to popular demand) released Digital Research’s CP/M 2.2. You’ll find documentation for both on the site.
As for testing your FDD100-5 drive: I believe you’ll need a 10-hard sectored disk in the drive to test anything (including rotational speed). I suggest you focus on trying to boot HDOS as it contains a program TEST17.ABS that can be used for further testing. My own experience with these drives points to two things: 1) they almost always need some maintenance after 40 years (e.g. bearings and worm gears need cleaning and lubrication); but 2) they almost always can be put into good operating order.
The H8D format is an exact linear copy of the sectors on an H17 (hard sectored) disk so that’s its primary purpose, though there are tools to convert these images to other formats.
The drive density (single or double) is completely a function of the disk controller board, not the drive. The H17 (H88-1?) board: 1) requires hard-sectored media and 2) can only do FM (single density) recording. It can, however, be used with double-sided and 96TPI drives with the appropriate software drivers. The H37 board can do MFM (double density) and requires soft-sectored disks. It also supports double-sided and 96TPI drives.
We have experimented, with mixed results, with punches over the years for creating 10-sectored disks. These designs have used a metal punch and metal backplate, but they almost always leave rough edges and “hanging chads” on the disk holes. Recently a much better approach has been developed using a 3-D printed hole guide and hollow punches available on Amazon. This approach has produced excellent results. I am planning to write this up in the near future. Stay tuned!
To view this discussion visit https://groups.google.com/d/msgid/sebhc/CAG1tPetK5HUyAO7WYaDFXeZ1heytHGYNP_tEgmotCoVQeBoFAg%40mail.gmail.com.
At the very top of the SEBHC web page there are links to the Wiki and Google group. We also have an active Discord server if that’s of interest to you.
Not knowing how much you know about Heathkit computers, it’s hard to give you direction.
I’ll assume you are starting largely from scratch. There were two primary operating systems. Heathkit first introduced their own OS Heath Disk Operating System (HDOS) and later (due to popular demand) released Digital Research’s CP/M 2.2. You’ll find documentation for both on the site.
As for testing your FDD100-5 drive: I believe you’ll need a 10-hard sectored disk in the drive to test anything (including rotational speed). I suggest you focus on trying to boot HDOS as it contains a program TEST17.ABS that can be used for further testing.
My own experience with these drives points to two things: 1) they almost always need some maintenance after 40 years (e.g. bearings and worm gears need cleaning and lubrication); but 2) they almost always can be put into good operating order.
The drive density (single or double) is completely a function of the disk controller board, not the drive. The H17 (H88-1?) board: 1) requires hard-sectored media and 2) can only do FM (single density) recording. It can, however, be used with double-sided and 96TPI drives with the appropriate software drivers. The H37 board can do MFM (double density) and requires soft-sectored disks. It also supports double-sided and 96TPI drives.
The H8D format is an exact linear copy of the sectors on an H17 (hard sectored) disk so that’s its primary purpose, though there are tools to convert these images to other formats.
We have experimented, with mixed results, with punches over the years for creating 10-sectored disks. [...] I am planning to write this up in the near future. Stay tuned!
[...] I thought it might be useful to bootstrap a machine without having a copy of the disk handy as I had the ability to extract information from a disk on the H89 and write data back to a new disk on the H89. So that is why I made the boot loader stuff.
I believe that the soft sectored disk are relatively easier to create on things like a PC with the right controller. [...]
The only thing that I recall that had issues is that the loader had to be done in exactly the right order as there was some setup that needed to be done on the H89 that I never fully looked into. If one doesn't follow the instructions exactly one gets out of order and it hangs.
Interesting that the Tandy200 is “more like an H19”. The H19 is essentially an extended VT-52. Does the Tandy 200 really form a complete (or almost complete) h19 emulator? E.g. does it do all the graphics characters and escape sequences?
There are many pictures of Bill Gates in front of an H19 terminal. They did a lot of cross-development (at least in the early days) off DEC machines using H19 terminals. See his excellent bio (volume 1) “Source Code”. Not so sure about the Z89 though… (?)
Most of us use PIE from Software Toolworks for full screen editing on the H19/89. Once you get an ability to download software you can retrieve it from Mark Garlanger’s site The Software Toolworks or the SEBHC archive.
Most common disk format was probably the H17 (FM, single sided, hard-sectored – 100K total). This was the standard default disk drive for the H89. The Heath User Group (HUG) had a library of disks in this format. Later they disseminated some software in “37” format which was soft-sectored, single sided, double density (160K). I believe they used single-sided format because many users re-purposed their (single-sided) FDD100-5 drives for use with a soft-sectored controller.
Most of the H8D images on the SEBHC site are the 100K variety though some are for double-sided drives (200K) and even a few for double-sided 96TPI (400K). Mark has developed a more comprehensive format for archiving images which saves all of the data plus out-of-band information on a disk Heathkit Floppy Disk Formats, however we don’t have too much archived in those formats (mostly on Mark’s site).
H37 images are probably stored in IMD format. See Mark’s comments to your previous email.
Darrell Pelan’s very useful “H8D Utility” can do format conversions and is very useful for loading images onto a Gotek, for example: https://github.com/sebhc/sebhc/wiki#h8dutility
From: se...@googlegroups.com <se...@googlegroups.com> On Behalf Of B 9
Sent: Wednesday, October 29, 2025 1:43 AM
To: se...@googlegroups.com
Subject: Re: [sebhc] New to Z-89A, chickens & eggs
On Tue, Oct 28, 2025 at 3:53 AM <glenn.f...@gmail.com> wrote:
-- 
You received this message because you are subscribed to the Google Groups "SEBHC" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sebhc+un...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/sebhc/CAG1tPetDM7yNPo9f9Ty2%3DKiWKU6htsEMKfCQT5sVF4XDbLob4g%40mail.gmail.com.
The main reason Dwight’s program is hard-sectored only is because the code to do hard sector access is in ROM. This means you can manually type in a relatively small program to “bootstrap” things. You could do something similar for the soft sectored drive but the program you’d have to manually enter would be quite long I suspect since it would have to include disk access routines. And yes, you’re correct: the vectors to those ROM routines typically are loaded into RAM when you attempt a BOOT (this allows for re-vectoring the code to make enhancements) so a “fake” boot loads those vectors, which are then called by the short program you key in.
From: se...@googlegroups.com <se...@googlegroups.com> On Behalf Of B 9
Sent: Wednesday, October 29, 2025 6:05 AM
To: se...@googlegroups.com
-- 
You received this message because you are subscribed to the Google Groups "SEBHC" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sebhc+un...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/sebhc/CAG1tPetgAwR3RgU0s-TVCbWAKn7rOXoVuNv8RmAV-o3LLOVwFg%40mail.gmail.com.
To view this discussion visit https://groups.google.com/d/msgid/sebhc/004201dc48c3%24b190ed40%2414b2c7c0%24%40gmail.com.
To view this discussion visit https://groups.google.com/d/msgid/sebhc/DS4PPF2F49754B6B3D16EB7259A402BC1CDA3FBA%40DS4PPF2F49754B6.namprd11.prod.outlook.com.