I have an external NTFS formatted hard disk that I use for file transfer between Amiga and PC. It was formatted on a laptop PC and works fine on the PC. It is recognized when I plug it in to my Amiga through USB but file transfer is really slow so I want to access it as an external SATA drive. When I plug it in as an external SATA drive it is not recognized. Media Toolbox sees it but won't access it unless it's installed. My question is: If I install the drive in Media Toolbox will it still work on a PC??

daveyw wrote:It has become semi-regular for me. I was experiencing it every few minutes. Re-plugged the power cable to the motherboard and it largely solved the problem but after a day or so powered up, it will st switch itself off.

Unfortunately, the "subvariants" are the problem. It is not said, that two 8168H chips actually have the same MAC or PHY version. They should, but in reality they don't have to. I had this issue with 8139 and 8169 already. The documentation gives many information, but i heavily depends on the version of the documentation you've got.

If you can't find a chipset, supported properly by all three systems, the suggestion of nbache is probably the way to go for you. Use two network cables, one on the internal NIC for AmigaOS and MOS and the other one for Linux.

Cyborg wrote:This is exactly the kind of issue I (and obviously also the MOS devs) faced when developing network drivers for Realtek chipsets: there are a zillion different versions of each chip. Each with more or less subtle changes and incompatibilities. Setting only a single bit of one of the registers different may cause one chip of the "same" family work and another one fail.

In this case, it is even worse, because you are trying to use a driver for one family (8169) with chips from a different family (8168 - the 8161 is a variant of it).

There are actually a few variants of 8168 chips (those are native PCIe chips), which work similar enough to an 8169 (PCI) variant and hence work with rtl8169.device. The vast majority doesn't however.

The only way to support most (not all) variants of 8168 would be to write a dedicated driver for 8168. As far as I can see from a very quick look, there are at least 9 (!) different configuration paths to follow, depending on the exact variant. So it is not exactly a 5 minute job, if I even could be motivated to take the job .. I don't really see the benefit of it beyond rare special cases. Most of the time the internal NIC is enough or a supported PCI solution can be used.

So, I would actually suggest to get a plain 8169 board for good old PCI if you aren't able to use the internal NIC.