Hard drive problems

SK>> The hard drive is fully functional (checked again on PC)

KF> And the driver? Write the source here yourself, then you will see...

ZXNext controller driver.
I just entered my port numbers there.

Sincerely, Sergey Karachentsev.

SK> ZXNext controller driver.
SK> I just entered my port numbers there.

Are you sure this is correct? There, after all, the principle of reading a sector needs to be
changed a little.

Are you sure that the driver is working? How do other screws behave?

Ask KVA from E-Mage, he redesigned the driver for his Scorpio -
maybe he’ll give it away, and then you’ll add it yourself.

... no day without speccy!

KF> Are you sure this is correct? There, after all, the principle of reading the sector
KF> needs to be changed a little.
I’m sure. Sometimes in IS-DOS it was possible to see the text from the screw.

KF> Are you sure that the driver is working? How do other screws behave?
Unfortunately, no one wants to give me their screw :(

Sincerely, Sergey Karachentsev.

KF>> sectors need to be changed a little.
SK> I’m sure. Sometimes in IS-DOS it was possible to see the text from the screw.

So does it read the sectors or not?

Write everything down from start to finish.
You give a command, what then is in the status register? Always like this or sometimes?

KF> So does it read sectors or not?
It reads, but not always correctly.
More precisely, the correctness of reading depends on the contents of the sector (?!)
For example, some sectors with text (and not only text) written there
are read unambiguously. In some sectors, for some reason, pairs of bytes are lost and some bytes are distorted.
After creating a device with a size of 2000 blocks:
The 0th block is read unambiguously
The 3rd block is read differently all the time
After writing a file to the device, the 3rd block is already read normally
If you try to fill the device, directories begin to disappear,
file names are distorted, etc.

KF> Write everything out inside and out.
KF> Give a command that then in status register? Is it always like this or
KF> from time to time?
After the latest changes on the controller board and outside of it, I haven’t done any experiments
in assembler yet.

Sincerely, Sergey Karachentsev.

SK> Reads, but not always correctly.
SK> More precisely, the correctness of reading depends on the contents of the sector
SK> (?!) For example, some sectors with text written there (and not only
SK> text) are read unambiguously. In some sectors for some reason
SK> pairs of bytes fall out and some bytes are distorted. After creation

TEST #1:

Take the sector number from RND, write #FF there, read a few at a time and compare.

TEST #2:

Same with zero.

But most likely everything is already clear - shitty coordination.