I'm not 100% sure of all these issues, but this is my understanding:
1 - correct. Similarly if you were just to install another IO package, eg from agilent, they would put c-shared components in there as well.
2 -
- install ivi compliance package. This has the shared libraries and the ivi engine. THis is the bit you need to get IVI 'working'
http://digital.ni.com/softlib.nsf/webcategories/85256410006C055586256BE6007065DD?opendocument&node=132060_US
- SOme (probably all) drivers need NI-VISA. SOme drivers specifically will ask for a later version (usually 2.6). Note, if you want to install the agilent io suite with VISA-com running as a secondary visa driver, you will need NI-visa v3
- I don't think you MUST have NI-max, but it is the easiest way to a) look at the gpib devices and b) configure the ivi configuration store (aka iviconfigstore). THis config store is (I think) installed with the ivi compliance package and with max
- you don't specifically need to install the ivi engine. it comes with the compliance package
You've probably seen this 1000 times before and thought it was confusing! Well, if not you may get something useful from it
http://zone.ni.com/devzone/conceptd.nsf/webmain/706EFD334E77DCCE86256DB50062E903?OpenDocument&node=dz52000_us
3 - I don't think other vendor's 'support max' as such. MAX simply talks to the IVI configuration store which is where all the ivi settings are stored. And your IVI application goes to this configstore to resolve the logical name into the hardware + driver + settings. Max is simply a graphical interface for this config store, at least that is my understanding! SO any IVI driver will 'appear' in max.