watzman h19 ROMs

192 views
Skip to first unread message

Mark Garlanger

unread,
Feb 25, 2017, 12:47:21 PM2/25/17
to se...@googlegroups.com
Does any have the ROMS associated with the watzman changes for the H19. In mame, there are 2 listed, which changed from the regular H19. "watzman.bin" and "keyboard.bin". I found the watzman.bin file in Les's H19 emulator, so I'm just looking for the keyboard.bin file.

Mark

Glenn Roberts

unread,
Feb 25, 2017, 1:03:20 PM2/25/17
to se...@googlegroups.com

If it helps anyone locate this it was HUG P/N 885-1221 (not in Les’ archive L  )

 

-          Glenn

 

 

--
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 post to this group, send email to se...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sebhc/CAAjkm7_a_GkpXLc8hiaSiC162__nXqtt3Vm-ev5JbJ0yFuO5zw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Terry Gulczynski

unread,
Feb 25, 2017, 1:06:43 PM2/25/17
to se...@googlegroups.com
Mark,

I have 4 files - 2 @ .ASM and 2 @ .HEX for the Watzman ROMs:

MYH19.ASM (& .HEX)  dated 11/19/92 --> "MODIFIED H19 TERMINAL FIRMWARE"
KEYBD.ASM (& .HEX)  dated 05/30/81 --> "REVISED H19 KEYBOARD ROM"

Terry


On 2/25/2017 12:47 PM, Mark Garlanger wrote:
Does any have the ROMS associated with the watzman changes for the H19. In mame, there are 2 listed, which changed from the regular H19. "watzman.bin" and "keyboard.bin". I found the watzman.bin file in Les's H19 emulator, so I'm just looking for the keyboard.bin file.

Mark

Mark Garlanger

unread,
Feb 25, 2017, 1:22:01 PM2/25/17
to se...@googlegroups.com
I found the BIN file on Les's site, guess I didn't look close enough, but if you have ASM files, it would be good to get those available somewhere.

Mark

On Sat, Feb 25, 2017 at 12:06 PM, Terry Gulczynski <terr...@cfl.rr.com> wrote:
Mark,

I have 4 files - 2 @ .ASM and 2 @ .HEX for the Watzman ROMs:

MYH19.ASM (& .HEX)  dated 11/19/92 --> "MODIFIED H19 TERMINAL FIRMWARE"
KEYBD.ASM (& .HEX)  dated 05/30/81 --> "REVISED H19 KEYBOARD ROM"

Terry

On 2/25/2017 12:47 PM, Mark Garlanger wrote:
Does any have the ROMS associated with the watzman changes for the H19. In mame, there are 2 listed, which changed from the regular H19. "watzman.bin" and "keyboard.bin". I found the watzman.bin file in Les's H19 emulator, so I'm just looking for the keyboard.bin file.

Mark

--
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+unsubscribe@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+unsubscribe@googlegroups.com.

To post to this group, send email to se...@googlegroups.com.

Terry Gulczynski

unread,
Feb 25, 2017, 1:32:47 PM2/25/17
to se...@googlegroups.com
Replied to Mark off-site.

Terry
To unsubscribe from this group and stop receiving emails from it, send an email to sebhc+un...@googlegroups.com.

To post to this group, send email to se...@googlegroups.com.

John Toscano

unread,
Feb 25, 2017, 2:40:55 PM2/25/17
to se...@googlegroups.com
If anyone needs the physical ROMs, I came across them recently while looking for something else. There are 2, the code ROM and the keyboard encoder ROM. Let me know if you need them. I don't even remember buying them, particularly because I had a Cleveland Codonics Imaginator graphic board in my Super89 system and was considering modifying its firmware to add new features like those in the Watzman ROM. I never got around to doing anything with that, even though I got the complete source code for the Imaginator board with the Tektronix emulator... I left all that behind in Minnesota when I moved to Texas...

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to se...@googlegroups.com.

Mark Garlanger

unread,
Feb 25, 2017, 3:01:11 PM2/25/17
to se...@googlegroups.com
Maybe you could bring them with you next time you head up to Austin. 😀

Sent from my iPhone
To unsubscribe from this group and stop receiving emails from it, send an email to sebhc+un...@googlegroups.com.

To post to this group, send email to se...@googlegroups.com.

John Toscano

unread,
Feb 25, 2017, 3:58:48 PM2/25/17
to se...@googlegroups.com
Sounds good. I think next Saturday is the first Saturday of the month. I may need your address for my GPS again. I traded in my prior car on a newer model since I saw you last and never thought about my saved locations.

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to se...@googlegroups.com.

Mark Garlanger

unread,
Feb 25, 2017, 8:28:45 PM2/25/17
to se...@googlegroups.com
I now have both the normal h19 ROM set and the Watzman ROM set working under the MAME/MESS emulator.  

I'm going to investigate the Super19 config to try to figure out what needs changing for that.

Lee, your old company TMSI, made the SuperSet ROMs, right? Do you still have any of the technical info, like what the memory layout was, how the keyboard/character generation ROMs were setup? Copies of the ROMs are up on Les's site, so that will be the next one I tackle. But it looks like there was major changes for that, to support a much bigger ROM and all the character sets.

Does anyone have the Ultra ROMs dumped? There was both the program code and the keyboard decoder ROM.

And does anyone have any other replacement ROMs (dumps) for the H19? Or if you were aware of any, let me know so I can make a list of them. It would also be nice if we got an dump of the original H19 ROM which had some bugs which were fixed in the later release, just for completeness.

Thanks,
   Mark


--
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+unsubscribe@googlegroups.com.
To post to this group, send email to se...@googlegroups.com.

Lee Hart

unread,
Feb 25, 2017, 11:18:20 PM2/25/17
to se...@googlegroups.com
Mark Garlanger wrote:
> Lee, your old company TMSI, made the SuperSet ROMs, right? Do you still have any
> of the technical info, like what the memory layout was, how the
> keyboard/character generation ROMs were setup? Copies of the ROMs are up on
> Les's site, so that will be the next one I tackle. But it looks like there was
> major changes for that, to support a much bigger ROM and all the character sets.

Yes, I think I have documentation on most of it. I'll dig it out, and make
copies for you.

As I recall, the H19 address decoder was modified to decode 0-16k for the
program ROM. The chip was a 27C256 EPROM, plugged into a 28-pin IC socket, with
the extra 4 pins cut off and little wires patching them to the remaining 24 so
it plugged into the H19's 24-pin socket. The 27C256's extra address lines had
wire jumpers to pick up the additional address lines needed.

The stock 2k character generator ROM got the same treatment. A 27C256 was
plugged in its place, with the 4 extra address lines controlled by the 4 unused
modem output bits of the 8250 UART.

I don't think the keyboard ROM setup was changed at all. We just programed a
27C16 EPROM to plug right in. It had different codes so the keyboard could
provide 4 different codes for normal, shift+key, control+key, and
control+shift+key. For example, control+ESC was used to call the on-screen help
menus.
>>> send an email to sebhc+un...@googlegroups.com
>>> <mailto:sebhc+un...@googlegroups.com>.
>>> To post to this group, send email to se...@googlegroups.com
>>> <mailto:se...@googlegroups.com>.
>>> <https://groups.google.com/d/msgid/sebhc/CAAjkm7_a_GkpXLc8hiaSiC162__nXqtt3Vm-ev5JbJ0yFuO5zw%40mail.gmail.com?utm_medium=email&utm_source=footer>.
>>> For more options, visit https://groups.google.com/d/optout
>>> <https://groups.google.com/d/optout>.
>>
>>
>> --
>> 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
>> <mailto:sebhc+un...@googlegroups.com>.
>> To post to this group, send email to se...@googlegroups.com
>> <mailto:se...@googlegroups.com>.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/sebhc/e6416a66-a5f6-93c8-cbd5-0c5045d26232%40cfl.rr.com
>> <https://groups.google.com/d/msgid/sebhc/e6416a66-a5f6-93c8-cbd5-0c5045d26232%40cfl.rr.com?utm_medium=email&utm_source=footer>.
>>
>>
>> For more options, visit https://groups.google.com/d/optout
>> <https://groups.google.com/d/optout>.
>>
>>
>> --
>> 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
>> <mailto:sebhc+un...@googlegroups.com>.
>> To post to this group, send email to se...@googlegroups.com
>> <mailto:se...@googlegroups.com>.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/sebhc/CAAjkm7_oxJ1x7zz2MR5G9guBespUWaYVkYoK-UsD127JoCQ6XA%40mail.gmail.com
>> <https://groups.google.com/d/msgid/sebhc/CAAjkm7_oxJ1x7zz2MR5G9guBespUWaYVkYoK-UsD127JoCQ6XA%40mail.gmail.com?utm_medium=email&utm_source=footer>.
>> For more options, visit https://groups.google.com/d/optout
>> <https://groups.google.com/d/optout>.
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "SEBHC" group.


--
Anyone can make the simple complicated. Creativity is making the
complicated simple. -- Charles Mingus
--
Lee Hart, 814 8th Ave N, Sartell MN 56377, www.sunrise-ev.com

Mark Garlanger

unread,
Feb 26, 2017, 12:13:15 AM2/26/17
to se...@googlegroups.com
That would be great, so the ROM has 16K of data, but the 27C256 EPROM is a 32K part. Looking at the dump, it shows only the higher half of each 16k block has data - the first 8k is all 0xff, then the next 8k is the code/data, another 8k of 0xff and finally 8k of code/data.  So I'm guessing any reads of the first 8k, will be pulled from the second 8k, and from the 3rd 8k, it'll read from the 4th 8k block.
Interesting info about using the UART for address lines in for the character ROM. I see that there is an OUT1 & OUT2, I guess it must also be using the DTR and RTS.

Mark


        send an email to sebhc+unsubscribe@googlegroups.com
        <mailto:sebhc+unsubscribe@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+unsubscribe@googlegroups.com
        <mailto:sebhc+unsubscribe@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


    --
    You received this message because you are subscribed to the Google Groups
    "SEBHC" group.


--
Anyone can make the simple complicated. Creativity is making the
complicated simple. -- Charles Mingus
--
Lee Hart, 814 8th Ave N, Sartell MN 56377, www.sunrise-ev.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+unsubscribe@googlegroups.com.
To post to this group, send email to se...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sebhc/58B256B8.80504%40earthlink.net.

For more options, visit https://groups.google.com/d/optout.

Lee Hart

unread,
Feb 26, 2017, 12:30:09 PM2/26/17
to se...@googlegroups.com
Mark Garlanger wrote:
> That would be great, so the ROM has 16K of data, but the 27C256 EPROM is a 32K
> part. Looking at the dump, it shows only the higher half of each 16k block has
> data - the first 8k is all 0xff, then the next 8k is the code/data, another 8k
> of 0xff and finally 8k of code/data. So I'm guessing any reads of the first 8k,
> will be pulled from the second 8k, and from the 3rd 8k, it'll read from the 4th
> 8k block.

Right. This was a consequence of the physical positions of the 27C256 address pins.

> Interesting info about using the UART for address lines in for the character
> ROM. I see that there is an OUT1 & OUT2, I guess it must also be using the DTR
> and RTS.

You are correct! These lines weren't being used for anything else. Might as well
put them to good use. :-)

Garrett Nievin

unread,
May 11, 2017, 8:21:22 PM5/11/17
to SEBHC
I just finished getting an H19 running, and it's got the Ultra ROM set (at least I assume so, because the ROMs have big gold stickers on the EPROMS labeled "THE ULTRA ROM").  Trying to figure out what they were, I came across this thread.

Do you still need dumps of those ROMs?  I'd be happy to do so if that's the case.  Is there documentation on these somewhere?  I can see that they're putting a clock on the right side of line 25, but I don't know what else might be in there.

Cheers,
Garrett 

Mark Garlanger

unread,
May 12, 2017, 1:20:41 AM5/12/17
to se...@googlegroups.com
If you have the equipment to image the ROM and the Keyboard Encoder, that would be great.  I have the manual, and I can put that in the queue to scan.

Mark


--
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+unsubscribe@googlegroups.com.
To post to this group, send email to se...@googlegroups.com.

Garrett Nievin

unread,
May 12, 2017, 5:31:45 PM5/12/17
to SEBHC
Here are the files, I believe.  Let me know if they are okay.

There is another ROM at U437; it seems to be all FFs.  Does that make sense?

Cheers,
Garrett


On Friday, May 12, 2017 at 1:20:41 AM UTC-4, Mark Garlanger wrote:
If you have the equipment to image the ROM and the Keyboard Encoder, that would be great.  I have the manual, and I can put that in the queue to scan.

Mark

On Thu, May 11, 2017 at 7:07 PM, Garrett Nievin <garret...@gmail.com> wrote:
I just finished getting an H19 running, and it's got the Ultra ROM set (at least I assume so, because the ROMs have big gold stickers on the EPROMS labeled "THE ULTRA ROM").  Trying to figure out what they were, I came across this thread.

Do you still need dumps of those ROMs?  I'd be happy to do so if that's the case.  Is there documentation on these somewhere?  I can see that they're putting a clock on the right side of line 25, but I don't know what else might be in there.

Cheers,
Garrett 

--
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 post to this group, send email to se...@googlegroups.com.
h19-keyboard-encoder.BIN
h19-ultra-firmware.BIN

Mark Garlanger

unread,
May 12, 2017, 8:07:16 PM5/12/17
to se...@googlegroups.com
Great, let me try these out. As for the sockets, are you sure it was U437 that was all FFs? The documentation covers both the H-19-A and older H-19 which they put socket numbers in [brackets]. Since there was at least 4 or 5 different "Terminal" boards, I'm not sure which map to the H-19A and which map to the H-19.  So it says that U437 [U422] should be the 2532 Firmware, and U445 [U430] should be the keyboard encoder. There is also an optional chip to enable the "Second Page Display", an HM6116  2k x 8 static RAM, that should be placed in U436 [U423].

Mark


To unsubscribe from this group and stop receiving emails from it, send an email to sebhc+unsubscribe@googlegroups.com.

To post to this group, send email to se...@googlegroups.com.

Garrett Nievin

unread,
May 12, 2017, 9:19:09 PM5/12/17
to SEBHC
You're right, U423.  Not sure where I got U437 from.

Is that documentation online?

Cheers,
Garrett

Mark Garlanger

unread,
May 12, 2017, 10:27:37 PM5/12/17
to se...@googlegroups.com
No, I haven't had a chance to scan it yet.

Mark

To unsubscribe from this group and stop receiving emails from it, send an email to sebhc+unsubscribe@googlegroups.com.

To post to this group, send email to se...@googlegroups.com.

Mark Garlanger

unread,
May 13, 2017, 2:27:36 AM5/13/17
to se...@googlegroups.com
I've scanned and posted the manual on my site: http://museum.heathkit.garlanger.com/items/show/52

I tried updating the MAME h19 source code to use the files, but wasn't successful in getting it running. After looking at the firmware file, it looks like the only the first 2k of data is there. Although the file is 4k, the second 2k just has the same data as the first 2k. The keyboard encoder has a similar issue, but since it should be only 2K, I just cut the file down to 2K (the second 2k was also a copy of the first 2k in that file).

If you are able to capture the second 2k of the firmware, that would be great. I can then try that with the MAME emulator.

Thanks,
Mark

Garrett Nievin

unread,
May 13, 2017, 1:23:49 PM5/13/17
to SEBHC
I'll do so, and get them to you shortly.

Garrett Nievin

unread,
May 13, 2017, 1:49:34 PM5/13/17
to SEBHC
I see my problem.  This is a 2532 part, and I scanned it as a 2732.

Need to figure out how to get my MiniPRO TL866 to read a 2532.

Cheers,
Garrett

Garrett Nievin

unread,
May 14, 2017, 8:23:52 PM5/14/17
to SEBHC
Mark,

This should be a better "THE ULTRA ROM Firmware" image.  I'll re-image the keyboard ROM and the other ROM as well.

I don't think I can read a 2532 in the MiniPRO without making an adapter; I've also got a parallel port 
Needham's EMP-10 I've not used before, and that seems to work well.  That's what I used to get this image.

Does this look okay?

Cheers,
Garrett
h19u.bin

Garrett Nievin

unread,
May 14, 2017, 8:38:02 PM5/14/17
to SEBHC
Upon examining your document a little closer, it looks like the chip at U423 is not at all a ROM, but a RAM chip.

Attached is the image of the keyboard encoder.

Cheers,
Garrett
h19-ultra-rom-keyboard-2716.bin

Mark Garlanger

unread,
May 14, 2017, 11:16:56 PM5/14/17
to se...@googlegroups.com
Thanks, the new dump works and I'm able to enter type characters and press the various Escape sequences.   I tried the "Esc-|" which is the self-test, it passes the RAM test, but says errors for mem and rom, not sure if that issue is something related to the emulator or not. Could you try doing the self-test on the real thing, and let me know what the results are?  See attached screen capture of the emulation.

If anyone has some spare time, and able to disassemble the ROM, that would help too.

Mark



To unsubscribe from this group and stop receiving emails from it, send an email to sebhc+unsubscribe@googlegroups.com.

To post to this group, send email to se...@googlegroups.com.
h19Ultra.png

Mark Garlanger

unread,
May 15, 2017, 1:09:15 AM5/15/17
to se...@googlegroups.com
Also, can you try the "Esc-?" sequence for the send configuration report. From the manual it claims to send several bytes of hex values to the host, including the ROM version. In the emulator, I'm not seeing anything displayed, and assuming I'm using the debugger properly, I didn't see anything sent to the serial port.

Mark

Garrett Nievin

unread,
May 15, 2017, 10:07:30 PM5/15/17
to SEBHC
I did the Esc-|, and it's pretty fun to watch!  It spends some time filling the screen with apparently every possible character, in normal and reverse video, and then starts cycling through characters at the current cursor position.  It ends up saying:

* RAM Ok
* PG2 Ok
* MEM Ok
* ROM Ok

* Test End

, where the * at the front of each line is actually that "paragraph" symbol you see on your Test End in every case.

This appears to be the output of the ESC ? report:
00E920450045E924   

A cursory comparison against the documentation you posted (THANK YOU!) looks like everything here is correct to me.

Cheers,
Garrett

Mark Garlanger

unread,
May 15, 2017, 10:58:40 PM5/15/17
to se...@googlegroups.com
Excellent, glad to see it working on the real H19. Most likely there are some issues with the emulation on why it's not passing. I'll have to investigate some more to try and track it down.

Mark

To unsubscribe from this group and stop receiving emails from it, send an email to sebhc+unsubscribe@googlegroups.com.

To post to this group, send email to se...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages