Boot disk for c1p

[Klyball]

I have my system up and running with the 610 board, data separator and floppy, I am wondering if there is a way to make a boot disk to test the floppy drive

Thanks

Grant

[Klyball]

I loaded the C1P-OS65D code into memory and the copy track 0 code from track 13 (I had to load at address 300)

if I run the OS at 2547 I get control of the system on my terminal software I can "go 0300" and I get the track 0 software
so I will try to write the os back to a disk, my problem is I only have 1 6850 (for a couple of days) and its running the show right now, I have also been going through the disassembly manual
Question

1. which version of the os displays on the 600 board?
2. Because im using the serial port for load is that why I can't write to 0200
3. Has anyone had success making a boot disk this way


Grant

[Klyball]

I answered most of my questions just need the chip


1. which version of the os displays on the 600 board?
Fixed- needed to load at 2217 and then jump to 2547 at 22b3

2. Because im using the serial port for load is that why I can't write to 0200
Correct -loading from disk to 0200 should be fine

3. Has anyone had success making a boot disk this way

[Klyball]

3. Has anyone had success making a boot disk this way

Success -Boot disk Made!!

[MK14HAK]

3. Has anyone had success making a boot disk this way

Success -Boot disk Made!!

Well done.
Sorry Grant, Ive been to busy to reply earlier. Yes I have v3.2 relocated running in 8k SII RevD. I am using Cegmon and also had to relocate TK0 Util to 0300 and use the $FC06 boot and bypass tk1 load initially. (The monitor overwrites page 2 locations crashing the TK0 util). I only boot to A* and have not bothered with BASIC for the moment. So I have tk0,1 and directory.
65D3.3 will run also with appropriate kybd and video mods depending on your source system C4/C1. Dave posted some images I have created that may be useful to you.
Cheers Mike

[dave]

Nice work, Grant!

Dave

[Klyball]

I thought i would document my boot disk creation for the C1P using 5.25 image using the C1P-OS65D_3.1.65D this should work for C4P using OS-65D V3.2 (NMHZ).65D

** Tutorial disk 5 is a full boot disk with all the utils needed including single or dual disk copy,asm and em**
**Warning Do not try to boot from disk until the disk is finished or you will need to reload the boot file**
Tools Needed
** TESTED ON BOTH 5.25 MPI DRIVE AND TOSHIBA 3.5 720K DRIVE**

hex editor
osilod
working floppy system connected to pc via serial
teminal software
OS-65D V3.2 Dissasembly Manual

First thing to be done is have a working os65 on your machine,this will not be written to a disk but will be used to do all the work and can be used to create any disk image.

Open C1P-OS65D_3.1.65D in hex editor ,strip format info from track 0 and track 1 and combine ,we need to change 2 values so the os won't try to load basic
at 22B3 change 4C E6 2A to 4C 47 25 save as boot.65d
using Osilod make .lod file with -l2200 -x2547(for terminal control) or -x2217(for local control)
load file to system , if everthing worked you should have A* on ethier your teminal or system screen
make .lod files for all the tracks on the disk you want to create (at least up to track 16) using -l3300 -x2547(if making tutorial disk 5 the track 0 write utility is on track 39)
make sure to strip out the format data and make note of sector numbers and page sizes(some tracks have multiple sectors and will need a .lod for each))
place blank disk in drive and type A* ini (your disk should now format)
reset system and enter m and load up track 1, after load you should be returned to the A*
Home head A* HO
save to disk starting at track 1 using A* SAVE 01,1=3300/8
Home head A* HO
reset system and repeat for all tracks and track sectors A* Save TT,S=XXXX/P
Home head A* HO

Final step is to write track 0

load track 0 to memory
Home head A* HO
invoke track 0 write util A* CA 0200=13,1 or CA 0200=39,1
GO 0200
W3300/2200,8

Disk should be done!!
If you made Tutorial disk 5 you can now make copies of the disk with the single drive copy program.

Good luck

[BillO]

According to the OS-65D users manual tracks beyond 0 are identified by $43, $57, <Track number>, $58.

However, this is not what I see when I edit C1P-OS65D-3.1.65D. After track 0, then next track seems to start $24, $00, $51, $85.

So, I am not seeing what I expect to see and cannot determine what is 'format' information at the beginning of a track. In addition the '4C E6 2A' does not seem to occur at $22B3, but at $22C4. Instead I see:

Code: Select all

22B1 D0 F1
22B3 20 73 2D
22B6 0D 0A 4F
22B9 53 2D (53? = SRE - illegal OPCODE?)
22BB 36 35  (sort of falls apart here...)
22BD 44 
22BE 20
22BF 56
22C0 33
22C1 2E
22C2 30
22C3 00 
22C4 4C E6 2A

At this point I'm a bit confused Can anyone set me in the right direction?

[bxdanny]

$2D73 is the in-line print string routine. So $53 is not an opcode, it is part of the message <cr><lf>OS-65D V3.0. Track 0 seems to have loaded to the right place. As for why you don't see the format information on track 1, you just didn't look far enough in. In the online disk image, the track header starts at the 10th byte of the raw track, followed immediately by the sector header, then the data. Everything before the track header on the raw track is ignored by OS sector-read code.

22B3 20 73 2D ; JSR STROUT
22B6 0D 0A 4F ; message $0D, $0A, OS-65D V3.0
22B9 53 2D
22BB 36 35
22BD 44
22BE 20
22BF 56
22C0 33
22C1 2E
22C2 30
22C3 00 ; null = string terminator
22C4 4C E6 2A ; executable code continues here

[BillO]

Doh!

How did I miss that? It's right there in the character pane of the hex editor!

Thanks Danny, that's what I needed.