OSI + Gotek (youtube video)

[nama]

Hi guys...any chance one of you could upload a working Hexdos .hfe file and I'll try it in my C1.
Thank you

[bxdanny]

davisgw,
Actually, I didn't use the source code (other than the snippet you posted), but rather a disassembly of the "live" running copy Hexdos generated by my BASIC disassembler program, in conjunction with the WinOSI debugger, which I used to search for a couple of instructions (like C9 7F or CMP #$7F, where it checks for the Rubout key) that I expected to (and did) find.

nama,
Download the file HFEnhdimages.zip from page 4 (next-to-last post on the page) of this thread. The good, working copy of Hexdos is the one with the "v" in the name: hexdosv4nhd.hfe. (The one without the "v" is corrupted.)

[davisgw]

nama,
If you need an image for a C1 with 48 character video activated try danny's BASIC program posted a couple days ago. Also, let us know if you are unable to save the program on track 0 for your Gotek along with the values in 0xFFE0, oxFFE1....I have a patch you might be able to use.

[nama]

Thanks guys, I downloaded the working HexDOS and it seems to work fine with limited use so far. I did try the 48 character mod as described, but as noted I believed the HexDOS image became corrupt when saving the changes back to the gotek.

[nama]

Regarding OS65U image (image number 34) it does not fully boot on my C1 or my C4. I get the same message on both systems 'DEV B not ready. From memory I did have this image working when I had my C2 which had 32k. Unfortunately I no longer have that system. I suspect it needs more RAM as both my C1 and C4 systems have only 24k .

[davisgw]

nama,
Your OS65U boots without errors on my 600D with 32K RAM. But I noticed that during boot it verifies it can open every device including the B floppy. Do you know what is the functional difference to OS65D that would be a reason to use it?

I'm posting an image of Hexdos4 with Danny's video fix on track 0 that is for 600D systems, so you can be the test dummy . I modified it for my 600D but I think it should work on any 600D. Please try it and let us know. I changed the name to .zip for posting but it really is .hfe. Thanks.

[bxdanny]

Yes, OS-65U requires at least 32k to boot (the BASIC workspace starts at $6000). And yes, it always gives that "DEV B not ready" message if there is not a B drive with a disk inserted present.

I was initially puzzled by how nama's C4P was able to boot those five disk images that weren't booting for me. Then I realized that I had an oddball ROM image enabled from $F000 to $F7FF in the C4P configuration. Once I disabled that, those five disk images booted. The relevant thing about that ROM image is that the contents of location $F400 had bit 0 set. So when the routine at $249F was called (which is actually the parallel printer driver, but which is called by the C1P version of BASIC as part of the Control-C check because that's where the "BIT patch" for checking the keyboard is on C1P versions of 65D), that ROM made it look like the printer wasn't ready, so it hung. Whereas without it, reading the empty address space at $F400 returns $F4, which looks like the printer IS ready, so the routine returns and the program continues. But those checks will never detect a Control-C keypress, because they're not in fact looking at the keyboard at all. (Although Control-C can be detected by first pausing output with Control-S, and then hitting Control-C.) Also, if a parallel printer interface were ever added to that C4P, the printer would output an endless stream of "q" characters if one of those disks was booted.

All that may be way more detail than anyone else cares about, but I found it interesting. Aardvark may have left that C1P version of the BASIC overlay on their disks because at least it boots on both the C1P and (most) C4P systems that way, without changing track 12. I actually did the same thing with the 5.25" version of the SEB-3 driver disk (since I prepared it on my C1P). Then i got a call from an annoyed 10-year-old (?) boy whose printer was spitting out all those "q"s.

Correction: they would be "a"s, not "q"s.

[nama]

Hi davisgw,
Thank you very much for sharing that file. I'll give it a go this weekend.
Also regarding OS65U, I never really used it at all, and the only system that was able to run it has now gone to a friend so I am unable to test it further.

[nama]

Sorry for the late reply...finally got time to try this out. Is this what it's supposed to look like?

Screenshot 2024-02-26 at 6.40.29 PM.png (1.18 MiB) Viewed 224 times

[davisgw]

Yes and no. It looks like Hexdos booted but the 48 character video program in track 0 did not execute. Try booting again and type "LOAD/" and then "LIST" to see the directory. The last entry should be "VIDFIX". Then type RUN"VIDFIX" and see if the 48 character mode is activated.

Danny, Any comments?