envagyok wrote on 2023-01-21, 17:53:

Thank you, its working.

Well, at least kind of working.

envagyok wrote on 2023-01-21, 17:53:

When i enter to settings, there is every drive empty, i try filled one connected drive's info. Then restart the pc, run hwinfo, […]
Show full quote

When i enter to settings, there is every drive empty, i try filled one connected drive's info.
Then restart the pc, run hwinfo, and there again the old drive settings with 2 drive what i photo from first 2 message this thread.
I try run again setup, i see again every drive empty 🙁 (but with hwinfo there is a 2 old drive sewttings)
Sadly not store the settings, and remain the old settings, and no see f2/f6 login screen at start.

The screenshots you show look like the configuration utility considered the current configuration invalid, and started with all settings as default. This is not unexpected, as you suspected a corrupted configuration EEPROM all along. Did you get asked the question whether you want to save the configuration before you rebooted? And did you answer "Y" to it? In case you use a german keyboard, you need to press the Z key to answer "Y".

envagyok wrote on 2023-01-21, 17:53:

mkarcher wrote:

The EEPROM is only accessible from the 80286 processor on the Tekram card. So you would need to send a "delete the EEPROM" command to the Tekram firmware. There is no simple delete command, but there is an EEPROM write command. I could tell you how to write a program that reprograms the EEPROM with contents with a bad checksum, so the Controller will fall back to a valid default configuration

its not to difficult?

That program would do the same thing as the setup utility does when you answer "Y" to the question. If the setup utility doesn't solve your issue, this program will not solve your issue, too.

I found the issue why the method I suggested didn't work properly. The code at that point I told you to jump to expects the DS register being set to the base address, as well as the CS register. So I extended the suggested debug invocation by the command to set DS to 5000 as well. The G command will set CS to 5000. If DS is wrong, the setup code doesn't receive the correct base address 1F0 of the controller. The all-zero setting you observed is also displayed if communication with the controller fails completely.

1A:\>DEBUG
2-nDC680C.FRM
3-l5000:0
4-rds
5DS 1234
6:5000
7-g=5000:1939

Curious what motherboard model and at what VLB and ISA speed things are set at.
Also Curious if when the settings are altered (and supposedly saved) thru debug and before a reboot, re-running thru debug should show if the new settings were properly saved to the lil eeprom correct ?
One thing that bothers me is that there is no ROM header being displayed at all if I read this all proper, and is not loaded/taking upper memory space as it should .
There should be a rom header followed by a error code number if the adapter is even "half-assed" working according to the manual.
Is it possible the 286 cpu is not functioning due to ram type ? I see in the picture 30 pin simms with a single high density chip + parity. None of my 286 or 386 boards would ever work with that type of ram.
Ok just verbally mulling over things that caught my eye..

mkarcher wrote on 2023-01-22, 00:46:

I found the issue why the method I suggested didn't work properly. The code at that point I told you to jump to expects the DS r […]
Show full quote

I found the issue why the method I suggested didn't work properly. The code at that point I told you to jump to expects the DS register being set to the base address, as well as the CS register. So I extended the suggested debug invocation by the command to set DS to 5000 as well. The G command will set CS to 5000. If DS is wrong, the setup code doesn't receive the correct base address 1F0 of the controller. The all-zero setting you observed is also displayed if communication with the controller fails completely.

Copy code to clipboard

1A:\>DEBUG
2-nDC680C.FRM
3-l5000:0
4-rds
5DS 1234
6:5000
7-g=5000:1939

Thank you very much, already work the controller.
I make suggested orders in dos, at settings i fix hdd settings, and the rom bios adress setting was corrupt. I fix it with change to default settings.
After restart i see the f2/f6 enter settings post, and i can enter.
This faulty was thank to sram?
I need to change it, or it repaired with save settings?

I can partitoon and format disk with copy system files /s command.

Thank you very very very much mkarcher!!!
You are genious.

Now i have only one problem.
I cannot boot from disk.
When i boot with floppy, i can load directory from c drive, and there is command.com, so i don't know why can not boot it.

envagyok wrote on 2023-01-23, 16:20:

Thank you very much, already work the controller. I make suggested orders in dos, at settings i fix hdd settings, and the rom bi […]
Show full quote

mkarcher wrote on 2023-01-22, 00:46:

I found the issue why the method I suggested didn't work properly. The code at that point I told you to jump to expects the DS r […]
Show full quote

I found the issue why the method I suggested didn't work properly. The code at that point I told you to jump to expects the DS register being set to the base address, as well as the CS register. So I extended the suggested debug invocation by the command to set DS to 5000 as well. The G command will set CS to 5000. If DS is wrong, the setup code doesn't receive the correct base address 1F0 of the controller. The all-zero setting you observed is also displayed if communication with the controller fails completely.

Copy code to clipboard

1A:\>DEBUG
2-nDC680C.FRM
3-l5000:0
4-rds
5DS 1234
6:5000
7-g=5000:1939

Thank you very much, already work the controller.
I make suggested orders in dos, at settings i fix hdd settings, and the rom bios adress setting was corrupt. I fix it with change to default settings.
After restart i see the f2/f6 enter settings post, and i can enter.
This faulty was thank to sram?
I need to change it, or it repaired with save settings?

I can partitoon and format disk with copy system files /s command.

Thank you very very very much mkarcher!!!
You are genious.

Now i have only one problem.
I cannot boot from disk.
When i boot with floppy, i can load directory from c drive, and there is command.com, so i don't know why can not boot it.

Its a translation difference.
Just boot from DOS floppy with fdisk, try to fix MR with fdisk /MBR
Then delete all partitions with fdisk and create new partition(s)
Reboot, reformat it with format c: /u /s and install new OS 😀

envagyok wrote on 2023-01-23, 16:20:

I make suggested orders in dos, at settings i fix hdd settings, and the rom bios adress setting was corrupt. I fix it with chang […]
Show full quote

I make suggested orders in dos, at settings i fix hdd settings, and the rom bios adress setting was corrupt. I fix it with change to default settings.
After restart i see the f2/f6 enter settings post, and i can enter.
This faulty was thank to sram?
I need to change it, or it repaired with save settings?

The corrupt settings were stored in the 64-byte EEPROM. After you saved valid settings with the setup tool, the corrupt settings are overwritten. If the issue doesn't reappear, no further action is required.

The message "IDE BUS1 drive0 (D0)BAD drive or drive parameter error!" means that the drive rejected the parameters "2 heads, 40 sectors" when the controller told the drive to use that configuration. While this is listed as the "native geometry" of that drive, it is quite possible that the drive only accepts the parameters listed as "translation", which is 980/5/17. Using the drive while this error message appears on boot will mix up data on the drive and cause spurious errors. You need to configure the drive in a way that this message does not appear, then you should re-format and re-install to get it into a clean state.

envagyok wrote on 2023-01-23, 16:20:

Now i have only one problem.
I cannot boot from disk.
When i boot with floppy, i can load directory from c drive, and there is command.com, so i don't know why can not boot it.

You have to enter a dummy disk in mainboard BIOS.
On my systems I enter a type 1 disk.