Boot disk for c1p

[BillO]

Sigh!

I'm not having much luck with this. I have tried making boot files from several of the C1P 5.25" images and I get varying results. I can get the A* prompt, either locally (on the OSI) or on the terminal. The routine entry points I have looked at check out, but some versions just go into space if I enter a command, others just give me errors. None will home the head, or initialize a disk, or execute any other command.

I'm guessing it's my 600 board and whatever is causing the weird memory problems I'm having.

[BillO]

Okay!

I've made some headway.

You first have to reset your machine and select D to initialize the FD hardware, then reset again, enter the monitor, load the OS code and then things start to work properly.

Onwards and upwards, as they say...

[BillO]

Well, my luck was short lived.

Every time I try to save a track I'm greeted with ERR #9. It's like the disks are not formatting.

When I format the disk, everything seems to go as it's supposed to. The SAVE command make the drive step to the right track, then about a second later I get the ERR #9.

So far I have tried:
> Scoping the ACIA - there is TX data while formatting
> Replacing the ACIA
> Replacing the 7400 and the 7404 that make the write data signal
> replacing the disk drive
> replacing the disk

None of that made any difference. Any ideas?

[Jeff]

Yes. I had those exact problems with my setup....lots of error 9's

I don't have any answers at the moment, but here is a short program that will dump what you 'supposably' have written to your disks so far.

It dumps to your serial port.

RAWDUMP.HEX.zip

(1.4 KiB) Downloaded 189 times

If your disks formatted correctly, you should see Track headers and footers on each track except 0.

Track Header: 43 57 TT 58 [optionally some meaningless random bytes]
Sector Header: 76 SS PP
[DATA]
Track Footer: 47 53 [followed by a bunch of 00 00 00 00]

There may be FF's at the start and end... this is normal

Oh, and I am still looking into my new router.... it may be pooched also... it does not want to port forward.

Let me know what is written so far on your disks

/Jeff

[MK14HAK]

Error 9s fixed here with replacement drive and/or media.

[Klyball]

ERR #9 seems to be a common problem when trying to make a disk using boot code, as mike suggested different media has solved it for me, but also switching between starting the boot code at 2217 then 2a51 and back , once the formatting catches all seems to go well, and once you get the disk made all seems to be well .
As Jeff said, checking the formatted disk to see if the track headers are getting written is the next step, I have found it difficult to format some disk and not others , the timing could be slightly off.

Grant

[BillO]

Thanks a ton folks.

Glad to see I'm not alone with getting these errors. I have a brand new, sealed box of diskettes I'll break out for this purpose.

[BillO]

Well, there is definitely something written in trk1 of the disk I tried to write, but a lot of it is not the same as what was supposed to be written there. There are track headers in subsequent tracks with the odd error, so this may be a media problem.

I will now switch to new diskettes and try again.

[Klyball]

Make sure you have good ground between everything, I was using a different supply to power my drives and had all kinds of problems till I grounded everything together