KlyBall 600D/610/D13 Disk Boot Issues

[GlassTTY]

Thank you, I will try these.

[GlassTTY]

So...

Sadly neither of those images boot on my system even after resetting the Gotek and adding the FF.CFG you posted. This, although not ideal, is good, as it confirms that I still have a hardware issue to resolve.

The only disk that boots is the HexDos disk and whilst I can load the programs from the disk I do have trouble saving programs to the disk, so that gives me something to explore too. However, before I go off exploring, I wonder if you can confirm a couple of things regarding your system.

• Are you using SYN600?

• Are you using the standard 32x32 (24x24) display?

I'm assuming the FF.CFG you sent in your last post is the one you use in your Gotek.

Thanks so much for your help, its really appreciated.

Edit:

New Symptom, not sure it helps though...

I have just noticed that WinOSI states that 24K isn't enough for a disk system. So I got excited and added another (fully tested) 8k, and guess what! It still doesn't boot but... HexDos fails to boot now too it looks like it loads track 1 and fails, could be a 'red herring' of course. Cold starting Basic shows the correct amount of RAM. Hmmm...

[HOWARDHB]

I'm using C1S monitor rom, standard video (24x24, unmodified 600D)

The FF.CFG parameters that I've posted are what I'm using now.

You can try this single track(0) image that Danny made for me to test my system...

tzonly.zip

(101.06 KiB) Downloaded 26 times

[GlassTTY]

Thankyou, I'll let you know how I get on.

[GlassTTY]

Previously Danny had posted...

You can check if track 0 is in fact loading by going into the Monitor and entering .FC06G. That should cause track 0 to be loaded, and the CPU then return to the Monitor program. You can then check the RAM at $2200 to see if what is there is what should be there. The first five bytes at $2200, with either 65D or Pico-Dos, should be A9 01 8D 5E 26.

What I see is the sequence A9, 01, 20, C6, 29... which is the sequence for an OS65D disk starting at byte 64. It looks like the first 64 bytes of track 0 are not being loaded.

This is confirmed if I perform the same exercise on Thomas' track zero disk, in that only the last line of the message seems to be loaded. I.e. the first 64 bytes are missing.

[HOWARDHB]

...faulty RAM issues... $2200 is where I would look...

[GlassTTY]

Having took a little break and bought a cheap logic analyser I decided to re-visit the disk boot issue.

With the logic analyser, I discovered that Address BA6 was permanently low. This was the reason that data stored at $2040 was overwriting $2000 and the reason for it not booting OS65D properly.

After 30 minutes or so with a DM and a magnifying glass I found an almost invisible solder splash and removed it. The system now boots OS65D. Yay!

Thank you for all the help given here, I am most grateful.

The notes I made regarding the D13 build, configuration, Gotek and so on (based on the information given to me in this thread and from a wide selection of posts in this forum) have been turned into a document which I hope will help others. I have placed this in a separate thread so that it can be found more easily etc.

Once again thanks to all.

[HOWARDHB]

Perseverence personified! Well done!