<<
Ouch, I felt a lecture rather than a correction. 
>>
Sorry, it was meant as a correction

Your not the only one to confuse them though, so don't feel bad. Judging by your posts in the HT forum you likely understand a lot more then the majority of the people of AT.
<<
nForce's Twinbank architechure is two seperate memory controller's that combine to provide the bandwidth requirements for both the CPU and Video Card, but also, they are linked together correct? >>
Well I suppose it depends on how you qualify the term 'linked', but pretty much yes they are.
<<
Because Twinbank is effectively the same technology as the Cross bar Memory Controller in the >GF3, there must be load balancing involved correct? >>
So nVidia hype would lead you to believe, the reality of the matter is that the TwinBank memory controller really isnt much more then a typical dual channel memory controller, there is no extra load balancing beyond that. The TwinBank memory controller is similar to that of the GF3's crossbar memory controller in that they both have multiple memory controllers that together make up a theoretical 128bit memory controller... that's all. nVidia's PR documents... and even Anand's own nForce review make it sound as though it's something incredibly innovative and new. I think Anand fell for nVidia's hype and didnt look into the fact that it's not anything new that hasnt been done many times before in past memor controllers on other chipsets. In reality it's just a typical every day dual channel memory controller. The only thing particularly 'innovative' about it is that supports UMA for the integrated GF2 MX core, which so far as I'm aware has never been implemented in a dual channel architecture.
<<
what is the difference between a Dual Channel Memory controller, and the Twinbank Architchure that nForce uses? Are they just the same? >>
The TwinBank memory architecture of the nForce is pretty much just a hyped up name for what's in reality precious little more then a traditional dual channel memory controller supporting UMA. nVidia hypes it up to seem a lot more, but in reality the differences are minimal and the end functionality is the same.
<<
If so, then what is the difference between a 128-bit DDR bus (like the one the Radeon 8500 for example uses) and a Dual Channel 64-bit DDR bus? Which is the most expensive to implement >>
The Radeon8500 like the GF3 does not use a traditional 128bit DDR memory bus, in the GF3 four memory controllers are each 32-bits in width that are essentially interleaved, meaning that they all add up to the 128-bit memory controller we're used to.
The R8500 if I recall correctly has two interleaved memory controllers that are 64bits in width. The GF3 memory controller is clearly more efficient then that of the R8500, which is a large part of the reason that the GF3 tends to perform better then the R8500 despite the theoretical bandwidth disadvantage it has.
When requesting small chunks of data the 'crossbar' memory architecture is much more efficient in it's bandwidth utilization, though in large memory requests it can be a distinct disadvantage.
In a graphics card neither are significantly more expensive to implement, but the 'crossbar' architecture is much more complex which necessitates a larger die size and likely negatively impacts potential clock scalability.... though the relative efficiency gain is more then worth it.
In a memory controller in a NorthBridge chipset, a full 128bit memory bus rather then dual channel 64bit memory bus would be clearly more expensive and more difficult to design and might require a new memory standard.... I'm not certain. It wouldnt be much less inefficient and in fact for a microprocessor it may even be preferable. The biggest advantage IMHO to a true 128bit memory controller though would be that it would remove the necessity for two DIMM's to be installed to utilize both channel's like the nForce needs.
It would likely also be more stable and reliable though, as it would mostly remove all the extra interference and cross-talk inherent in a dual channel memory controller.... one wouldnt have to worry about anything like the nForce's "Super Stability mode" bug, and it would be much easier to maintain stability with multiple memory banks, it's quite viable that 8 memory banks for 4DIMM slots wouldnt be too difficult with a true 128bit memory controller whereas it's
extremely difficult to manage with stability and and fast memory timings in a dual channel memory controller like the nForce.