After a few weeks with Windows 7 I know what I dislike the most - yes equals no
To get the content to run in Windows XP you'd click "yes", not so much in Windows 7.....read the message again if you don't get my drift....see it? In Windows 7 I have to answer "No" to get the content to run.
I'm shocked MS changed this. It took me a while to figure out why LotusLive Meetings would not work as I was automatically choosing "Yes" (to the old XP question, "Do you want to run this content?"). I can only imagine what users will start clicking once Windows 7 starts to roll out in organizations.
In effect the transition from XP to Windows 7 MS have made Yes = No and No = Yes. *shakes head*
Discussion for this entry is now closed.
Comments (5)
@1, so are you saying this is a Java change, not a Windows change?
I saw that Technote #1428715 ({ http://www-01.ibm.com/support/docview.wss?ca=quickrfaq&uid=swg21428715) has a potential solution which involves renaming one of the files in the STLinks folder. I haven't tried it yet however ... } ) has a potential solution which involves renaming one of the files in the STLinks folder. I haven't tried it yet however ...
Yep, same problem here. Having to re-train users to actually read the question (including myself) before clicking.
I am also finding some of the other potentially valuable security safegaurds in Windows 7 to be a headache.
Being an "old school" admin, I always liked the capability to run a script on XP and having write ability to C:\. Why write to the root? Because in a large corporate environment, you always know that 99.9% of the workstations out there will have a mapped C:\ drive.
I had an asset inventory script written to do the same here in my organization, and surprise, surprise-- no write access to C:\ (or any "root" physical or logical partition) on Windows 7. So, I had to add OS detection to the script and choose an output location based accordingly. Not a huge setback, but an annoyance.
...and zero write access to /Program Files running under admin?? What's that about?
in the control panel under java-advanced--security -mixed mode
chose enable hide warning and run with protections.
I think this was actually caused by Java update 19, it can happen in XP too, with that update.
There was also a problem with the ST meeting applet, but there is a fix from IBM for that.