When it comes to the TAG-RAM for a HX setup like this it´s not about the size / capacity of the TAG-RAM but about bus-width.
You could even have a 32Kx8 (256K) TAG-chip annd would still be limited to 64MB cacheable area due to the fact that when you are using just one chip you´re restricted to a 8-bit bus-witdh (=8 I/O lines). This means the whole TAG-bus of the northbridge that consists of 11 bus lines cannot be addressed.
To fulfill this condition you need to add a second TAG-RAM chip that takes care of the additional 3 I/O lines for a total 11-bit bus-width.
In an ideal world the board manufacturer makes sure the wiring makes this possible by
1. providing 2 sockets for TAG-chips
2. connecting all 11 I/O lines to the COAST-slot (if there is one) and - most important - to the northbridge.
- If only condition 1. is not met, the daughter-board solution will work, or, if there´s a COAST-slot present you can use a COAST-stick that brings it´s own additional TAG-chip
- If condition 2. is not met the problems begin, especially when the BGA-pins of the northbridge are not connected to any traces and cannot be reached.
Some manufaturers (like Jetway, Soyo, Aopen...) did a lousy job here by sparing the COAST-slot, sparing the second TAG-socket, sparing the second TAG-chip, just putting 2 x 256K SRAM on the boards and NOT changing the layout. This basically turns the cacheable area of HX back to FX.
The good (Gigabyte, ASUS, Chaintech, Elitegroup and others) did it right.
The attachment Elitegroup.JPG is no longer available
The attachment chaintech.JPG is no longer available
The attachment dtk.JPG is no longer available
The attachment springcircle.JPG is no longer available
The attachment dfi.JPG is no longer available