The first thing that comes to mind is memory. How much RAM do you have? Have you run any memory tests? Are you using older RAM boards or something more modern?
--
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 on the web visit https://groups.google.com/d/msgid/sebhc/5a15c0db-e0e0-4825-b0ca-d51941e55e54n%40googlegroups.com.
Awesome! FYI there are a few Morse code apps in the HUG library, but none in BASIC that I could find, in case you’d like to see an example or two.
885-1032 and 885-1052 on Les’ site.
https://sebhc.github.io/sebhc/software/Applications/H8DCATALOG_VOL1.HTML
if you don’t have an ability to pull files from the archive I’m happy to extract these and send to you. perhaps you can make a video once you get this working. good luck!
To view this discussion on the web visit https://groups.google.com/d/msgid/sebhc/bef549ed-3ae8-43d6-bf9d-500909f8c767n%40googlegroups.com.
Cool idea.
Joe: if you’re interested, I did find a couple BH BASIC morse code apps in HUG Volume I listings. But you may prefer the challenge of starting from scratch! Happy to scan those pages if useful to you…
From: se...@googlegroups.com <se...@googlegroups.com> On Behalf Of Tom Wilson
Sent: Tuesday, September 28, 2021 10:56 AM
To: se...@googlegroups.com
Subject: Re: [sebhc] Help with Benton Harbor BASIC
I remember a BH Basic program that keyed the transmitter for morse code
To view this discussion on the web visit https://groups.google.com/d/msgid/sebhc/c15759d1-56fb-5667-16c1-c81173b79eed%40gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sebhc/07a501d7b47e%24e9873430%24bc959c90%24%40gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sebhc/07a501d7b47e%24e9873430%24bc959c90%24%40gmail.com.
Joe: attached are three Morse Code programs written in BH Basic. These were published in “HUG Software Volume I” back when HUG first began. These would have been for an early tape version but should be mostly or completely compatible with the HDOS version.
Not sure if any of these use the front panel LEDs but if useful you could consult my article “Putting the H-8 LEDs to work” in REMark issue 40 (p. 41)
http://pestingers.net/pdfs/remark-scans/1983/remark-issue40-1983.pdf I have a simple example BASIC program in there…
good luck!
To view this discussion on the web visit https://groups.google.com/d/msgid/sebhc/CAGQDgBBfEn7E-y_AFuZakyDCKeQHgcNF%3DTEUSGxT%2BHM-zoVqtw%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sebhc/14bf01d7b546%247f1b9050%247d52b0f0%24%40gmail.com.
If you're running in an environment where the ROM is still controlling the display (I presume HDOS does), then the best way to manipulate the display and beep is to use memory (display) and ROM call (horn). Directly accessing I/O ports is just going to conflict with the ROM.
To view this discussion on the web visit https://groups.google.com/d/msgid/sebhc/CAGQDgBAwTK8iHU9gA0rwSVuh%3D1_dY7y8uypPaV%3DeKFWhhTwexQ%40mail.gmail.com.
Well, most of what you want to do can probably be done via PEEK/POKE. The front panel is I/O mapped but all of the functionality is managed by the 2ms clock interrupt routine, which constantly checks certain documented locations in RAM to determine what to do (e.g. should I refresh the front LEDs or keep them dark, what is the bit pattern to display in each of the 9 locations, etc.)
Take a look at the REMark article for a refresher and post back here if you have any questions.
As for the H9… I have no love for this beast, but it is an important part of the Heathkit computer evolution (I understand the H10 paper tape reader/punch is even more fun to get working reliably!?).
I think I’ve achieved my goal which is to be able to demonstrate what heathkit computing was like in 1977/78. There is still an issue with the H9’s cursor: when the cursor is in column 0 or 1 there is a “duplicate” cursor over to the right (10 spaces I think?). similar behavior occurs in other columns, though sometimes the “ghost” cursor is to the left.
I did spend an hour or so reading the manual, looking at the schematics and replacing some chips but did not manage to track this down. I can’t afford to spend any more time on this now. For now I can do a demonstration, and hopefully the duplicate cursor won’t be too much of a distraction!
For the VCF demo this machine will serve several purposes:
1. download and run the tape utilities (TED, DBUG, HASL, BHBASIC) using a laptop to emulate the tape drive. show a BASIC program or two, and possibly show how to edit and assemble a small program back then. This is ca. 1977 functionality.
2. run HDOS (rev 1.5!) using a single H17 drive system. Maybe show a BASIC program from the HUG book (if your morse code program is done before then [ 8 Oct] I could demo that too!) the H17 came out in the fall of ’78.
3. Demonstrate the front panel functionality via PAM-8. This machine has the large slave LED display which should be fairly visible in the room. I have some “eye candy” software that I can run on that to attract attention … there were also some early HUG programs that could run on a stand alone machine (e.g. chess timer, chase the blip, stuff like that).
4. Demonstrate the early experiments with music. I have a number of music programs I can run on this. these used the internal H8 speaker and required a slight mod (bend out pin 9 on IC 112 ) to work.
Picture:
To view this discussion on the web visit https://groups.google.com/d/msgid/sebhc/CAGQDgBAwTK8iHU9gA0rwSVuh%3D1_dY7y8uypPaV%3DeKFWhhTwexQ%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sebhc/159f01d7b571%24581a27c0%24084e7740%24%40gmail.com.
Not sure what you're using as a terminal for the CIN(0), but some
of the clients buffer input by default, only sending when
RETURN/ENTER is pressed. You might check the settings on the
terminal program, making it unbuffered. That also might change the
behavior of adding the <LF> to the <CR>.
To view this discussion on the web visit https://groups.google.com/d/msgid/sebhc/CAGQDgBC%3D_iGGgGA-qPVc5geMJvanL--k9Eu%3DzF9yqpPwiepOhA%40mail.gmail.com.
You received this message because you are subscribed to a topic in the Google Groups "SEBHC" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/sebhc/2-rRgwwv_iY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to sebhc+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sebhc/d2c407a8-bf9b-671c-9950-49984c52c4d4%40gmail.com.
Joe: nice job! I was able to save this file (remember to save it in “UNIX” format, “NL” for end of line, not CR/LF) and then use the BASIC “OLD” command to open it. Ran fine. Initially I forgot and ran it at 10Mhz CPU speed -you want a Morse code challenge, that’s it!
The reason CIN(0) requires a line feed is not internal to BASIC, it’s an HDOS issue. Here’s the code for CIN:
So it’s really just calling .SCIN. but normally HDOS will buffer console input so that you can make corrections (e.g. backspace). To disable that I believe you need to call .CONSL (see Heath_595-2553-02_HDOS_System_Programmers_Guide.pdf (sebhc.github.io) p. 22) and tell the console to operate in “Character Mode”. But I couldn’t find any way to add machine code calls to BHBASIC (you can do this in MBASIC) so I’m stumped, at least for the moment, on how to do this. I bet there’s an answer out there…
A few suggestions:
Good work…
To view this discussion on the web visit https://groups.google.com/d/msgid/sebhc/CAGQDgBC%3D_iGGgGA-qPVc5geMJvanL--k9Eu%3DzF9yqpPwiepOhA%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sebhc/087ef340-7bef-4096-88d2-34497575612cn%40googlegroups.com.