Dirk, We mostly run v8.x of Hummingbird on the current crop of WinXP machines. When upgraded to the new PCs, we were told by OpenText that v8.x will not run on Windows 7, that's why we have to upgrade to the current version of Hummingbird, v14. And we have not had any problems, especially like this one, with our current version of eXceed connecting to AW51B/Ds and WP51Ds. Duc -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of Dirk Pauwels Sent: Friday, April 20, 2012 12:02 PM To: foxboro@xxxxxxxxxxxxx Subject: Re: [foxboro] Hummingbird eXceed on Windows 7 Hi Duc, We're also on Win7's with exceed 9.0 connecting to Sun AW51 E's and WP51 D's 9.0 works ok, including VT100. No problem installing on Win7. Our exceed's are installed with a default setting, using rlogin , Xwindow and exec /opt/ia/go_dm script. You don't happen to have an older version? If you have the same problem with the old version, the problem is not Exceed related, but maybe win 7 related. Dirk -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of duc.do@xxxxxxxxxxxxxx Sent: vrijdag 20 april 2012 16:49 To: foxboro@xxxxxxxxxxxxx Subject: [foxboro] Hummingbird eXceed on Windows 7 List, We have a peculiar problem trying to implement Hummingbird eXceed v14 on Windows 7 PCs (a mandated upgrade from XP). The I/A side is still Display Managers running on Sun boxes as we have had them for years. (And this combination probably makes ours a unique scenario.) After much tweaking, most everything works for displaying remote DMs on the local Win7 PCs, except for initiating a VT100 session with the "VT100.local" option under "SftMnt" on the top menu bar. The selection executes a short dmcmd script: 04AW01# more VT100.local dmcmd script dmcmd run $FOX/bin/VT100.script and this has always worked reliably since time immemorial. Until now. You click the selection, the usual message "Local Application Startup" appears on the message area at the top, and ... nothing happens. What's peculiar about this problem is all other remote draw applications (Display Build, Display Config, Control Configurator, etc.) work without a hitch. BTW, corporate IT locks these PCs down pretty tight with the local Windows Firewall, but we managed to sweet talk them into completely undo all the restrictions for testing, so I am convinced, at this point, that Windows Firewall is not the culprit. Has any list member encountered such an error? Any solution? Appreciate all hints and suggestions. Regards, Duc _______________________________________________________________________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://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