> when the more obvious one (to me at least) 
> seemed to be the vs1782?

i've now tried that one too and monitor=vs1782 also worked for me.

Reply via email to