It seems that on Solaris On The Mesh (Solaris 10) P82's, the dmcfg file
(generated by ADMC or edited manually) won't work with environments that are in
/opt/customer/env, only /opt/fox/env. I used full path, tried with both forward
and backward slashes, and the only way it boots into the right environment is
if I use environments in the fox directory. Similarly, the Alarm Manager Change
Env button seems to only pick up environments in the fox directory, even though
FoxView Change Env uses environments that exist in the customer directory. I
thought putting them in customer was preferred to make sure they aren't
overwritten by future upgrades. On Windows, environments in customer seem to
work in dmcfg, but still not for the Alarm Manager Change Env button. Has
anyone had better luck with these or is /opt/fox/env the way to go?
Also, I cannot get an Alarm Manager to come up on boot/login, on either Windows
or Solaris, even though I set it to a boot type in ADMC/dmcfg. Does this work
for anyone else? Does the AM Name need to match the letterbug or logical name
for this to work (mine doesn't)?
The Solaris machine is on IA v8.4, Windows is 9.1.
Thanks,
-Joe
_________________________________________________________________________
This mailing list is neither sponsored nor endorsed by Schneider Electric
(formerly The Foxboro Company). Use the info you obtain here at your own
risks. See the disclaimer at www.thecassandraproject.org/disclaimer.html
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
