Superboard Expanded on S-100 motherboard

[bxdanny]

Mark,

Yes, the C1P keyboard occupies the full address block from $DC00 to $DFFF. Also, the full 2 kB of the Monitor ROM is visible from $F800 to $FFFF, even with the stock SYN600 ROM. OSI wanted to keep costs down, so they didn't add more address decoding than was necessary.

As it is now 24 hours since davisgw posted the rest of his DOS65 images, I have taken the liberty of cleaning them as you described you did with Disk 1, and posting the results. I verified that my result for Disk 1 was identical to yours. It is certainly not my intention to step on your toes by doing so.

The "loader" disk image included here is not derived from the one davisgw posted, since the relevant part of that (Track 0) was entirely corrupted. (I do wonder why that is.) Instead, it is the code of your .LOD version of the DOS65 loader, simply written to track 0 of a floppy image. (The other tracks on the image are completely unrelated to DOS65.)

[davisgw]

The loader disk I uploaded is supposed to be a copy of the original. But since I only need track 39,1 to boot DOS/65 I did not care about the rest of the disk so track 0 is likely corrupted. In fact since I thought it would boot OS65D I tried booting it yesterday and it put my floppy hardware into a state that I needed to power cycle to access the drives after that
I can transfer the original loader disk if either of you is interested. I also find it interesting that the instructions for booting DOS/65 on a C1p state that RETURN will not start the boot but SPACE BAR will.
bxdanny, Did you find any of the other disks corrupted? Doing 9 (OLD) disk transfers required me to clean the drive head because I could not boot 65D without getting errors.

[bxdanny]

davisgw,

I am able to read the directory on all nine "cleaned" disks. Of the "uncleaned" versions, some I could read a directory from, and some I couldn't. I have also been able to TYPE text files (.BAS or .ASM) from a couple of them, which were the only ones I tried that with. So I will assume, for the moment, that they are all good.

I had forgotten that the on-disk loader was on track 39, and required booting 65D first. You don't need it anyway, since you have the DOS/65 option (selection 8) in your boot ROM. Others can boot from the DOS65_loaderC1@2200.img disk image, and then immediately switch to the DOS-65 disk they want to load.

[Mark]

Hey bxdanny, thanks for processing the disk images. I see you also changed the DC00's to DF00's for keyboard read.

I went through the disks and found no obvious errors after cleaning. I was able to load all the files from the last disk without problems as well as a random selection of others.

The original "loader" disk besides having a loader on track39,1 was once a DOS65 disk that contained a number of files

Code: Select all

DOS/65
Recs Bytes Ex Filename.typ
--------------------------
  50    7K  1 ASM.COM
   4    1K  1 MOVE.COM
  11    2K  1 COPY.COM
   7    1K  1 PRINT.COM
   7    1K  1 COMPARE.COM
  28    4K  1 EDIT.COM
   7    1K  1 LOAD.COM
   4    1K  1 ALLOC.COM
   3    1K  1 MORE.COM
   6    1K  1 DISKTEST.COM
   7    1K  1 FORMAT.COM
  16    2K  1 OLVM.COM
  57    8K  1 SYSGEN.COM
   6    1K  1 DIROSI.COM
  17    3K  1 GETBASIC.COM
  75   10K  1 SYSINIT.ASM
   7    1K  1 SYSINIT.COM
  84   11K  1 RUN.COM
  14    2K  1 FILESTAT.INT
   8    1K  1 D65TER.COM
  26    4K  1 DEBUG.COM
   6    1K  1 OB24$2C1.ASM
   1    1K  1 OB24$2C1.KIM
451 blks of 1872, 178K Free

But have all been marked as erased. Except for one file:
OLVM.COM
Most of the deleted files are still intact though, so I "undeleted" them & restored the DOS65 OS tracks. I have not verified that the files are intact, but I did load a few of them.

I've also been updating WinOSI to handle a few issues that turned up running these programs... & the C1P emulation. After looking at the OSI 600D schematics for the keyboard decoding DC00-DFFF I see the video width latch must also decode from D800-DBFF.

Attached is the restored "loader" disk that still has the track 39 boot loader, but is otherwise a complete DOS65 disk once again. It is not OSI bootable, since it is a DOS65 disk.

Cheers,
-Mark

[davisgw]

bxdanny,
I have a dumb question I know you can answer. I made a WP6502 diskette for one of my 600D boards and modified the BEXEC* with a POKE to activate 48 character lines. But the menu the displays when I boot it is like a "split screen" and barely readable because the beginning text is on the left and after 24 characters the rest is on the right. Is there a software setting to print 48 character lines of text? Thanks.

[bxdanny]

In 65D 3.3, the command PRINT!(21); [equivalent to PRINT CHR$(27);CHR$(21);] will put the 600D into 48-character mode and adjust the output driver to use it. Likewise, PRINT!(20); [equivalent to PRINT CHR$(27);CHR$(20);] will put it in 24-character mode and adjust the driver to use that. If this is the 65D version of WP6502 and you are starting it from within 65D 3.3, then that should be all that's needed.

But if you have to reboot to start WP6502, then it is going to load the video driver from its own disk and will not use the 48-character driver from 3.3. I don't think a version of WP6502 for 65D 3.3 was ever released, but it might be possible to modify the video driver on the WP6502 disk to use a 48-x 12 (or 48 x 14) screen. If you send me an image of the disk, I may be able to do it. The program probably expects its workspace to start at $327E rather than $3A7E, so likely wouldn't work correctly under 3.3 even if you could start it from there.

BTW, I probably would like to see an image of that original DOS/65 "loader" disk too. Also, I know you have talked about Hexdos and its utility programs, so if you have a copy of Hexdos complete with utilities, I'd like to see an image of that also. You can post them here or send me a PM.

[bxdanny]

Hi Glenn,

Here is a video driver you can use with your WP6502 disk. It's a little complicated to install it, but once saved on disk you won't have to worry about that.

I will give two methods, for temporary and permanent installation. You can verify that it works with the temporary method, then proceed to the permanent method if it does (which I'm confident it will).

1) Download and save the attached file. I gave it a .txt extension so it could be easily uploaded, and there's no real need to change that, but it is in .lod format for the 65V monitor.

2) Add the statement DISK!"RE M" to the BEXEC* on the WP6502 disk, immediately after the POKE that puts the hardware into 48-character mode. Save it and boot from that disk. [If you are booted from that disk already, you don't have to save the modified BEXEC*, just RUN it.]

3) When the Monitor screen comes up in response to that added statement, press L and transmit the file downloaded in step 1) from the PC to the OSI machine.

4) When the file has been sent, you should see the A* prompt (in the correct position) on the OSI screen. Enter the command RE B and the BEXEC* will resume execution, starting and running WP6502 with the correct video driver now in place.

Assuming the above works, you can go to the permanent installation:

1) Edit the downloaded file on the PC, changing the second character of the file from "2" to "4". Make ONLY that one change, and save it.

3) Boot the system from the standard 65D 3.3 disk, and EXIT to 65D. Then enter CA 0200=39,1 to load the Diskette Utilities.

3) Take out the 65D 3.3 disk and insert the WP6502 disk in Drive A.

4) Enter GO 0200 and select the Track 0 Read/Write Utility.

5) Enter R4200 to read in Track 0, then E to return to 65D.

6) Enter RE M, then press L. Transmit the file modified in step 1).

7) When the file has loaded you will be back at the A* prompt. Again enter GO 0200 and select the Track 0 R/W Utility. This time, enter W4200/2200,8 to write the modified track 0 image to disk.

You can now boot from that disk and WP6502 should load with the 48-character driver. If you saved the BEXEC* with the RE M command, you will of course need to remove that. (.2547G to return to 65D from "RE M".)

I'm still interested in seeing your WP6502 disk, as well as that original "loader" disk and the full Hexdos 4.0 distribution disk with utilities. I e-mailed Steve Hendrix about that, by the way, and he said it's fine to post that.

[davisgw]

bxdanny,
Neither the PRINT!(21) nor PRINT CHR$(27);CHR$(21); statements work, The first one produces an error and the second does not change the screen to 48 lines. So I assume the WP6502 is not built on 65D v3.3.

Is the video driver you posted only for WP6502 or can it be used also for OS65D diskettes? Thanks for posting with the process.
And do you know how to change the BASIC-IN-ROM to be set to 48 character lines? Because I would need that capability for HEXDOS. One source says to POKE 15,XX to change the line length but not sure that works. However I could also modify a ROM.

I have been examining all the articles I have on the OSI and found a process in "The First book of OSI" to change the settings on 65D. I am posting that here.
As requested, I am posting the original DOS/65 Loader disk, the original HEXDOS disk. and the original HEXASM disk.

[bxdanny]

The video driver mod I posted is for any OS-65D 3.1 or 3.2 C1P diskette .

I'm pretty sure WP6502 for 65D always shipped with the 3.2 OS, never with 3.3. I would like to see a copy of your original WP6502 disk also.

If you want the BASIC-in-ROM to always work in 48-character mode, you can change two locations in your Monitor ROM to make that happen. Change $FFE0 and $FFE1 to be $4B and $3F, respectively, instead of $65 and $17. That will do it. If you want the bottom of the text screen to be lower down, giving you one more line of text on screen, you can use $8B instead of $4B at $FFE0.

But making these ROM changes means that games intended for the 24-character screen will generally not work. If you don't mind that, then make the change. I know you are able to reprogram your ROMs. But if you don't want to do that, you can use the VidSwap.bas program from OSI (it may have been originally called just SWAP). It was shipped on cassette, but it should work with Hexdos as well. A copy is attached to this post. Once loaded and RUN, you POKE 251 with 1 to go to 48-character mode, and you POKE 251 with 0 to return to 24-character mode. (Since $D800 is write-only, the program keeps a "shadow" copy. Don't POKE the hardware register directly when using this program.).

[bxdanny]

Actually, that VidSwap program won't work with Hexdos without modification, because it takes over the output vector. But it can be readily modified so that it will. For the Hexdos version, change line 400 to

400 POKE2529,ML:POKE2530,MH