This being achieved by a user with ‘Administrator’ permissions. Secondly after installing update 27, recommending the disabling of Java auto-update. (Aside: with FileHippo the old versions are listed under the latest version, so go to 1.7.0.1 and then you’ll see a list of old versions.) It seems that the USPTO helpful technician could have been a little more helpful:įirstly, they could of advised Windows users, to downgrade by making use of one of the websites: Over and over they played this game, which is why Gates is worth $40bn today. Remember the DOS 1.1 days? Once you got a suite of apps up and running and everything was finally cool, Gates came out with a new ver. Oracle seems to be taking a page out of the MS reverse incompatibility playbook.
JAVA VER 6 UPDATE 31 INSTALL
“If you are unable to authenticate to EFS-Web and Private PAIR due the affected Java updates, please contact your IT department or follow the instructions provided at the Oracle URL below to uninstall the affected Java update and install the supported Java 6 update 26.” Should have sent an email notification to all e-Commerce e-Alert subscribers and provided more detailed information along with the advisory announcement. In retrospect, due to the severity of this problem, the USPTO PAIR systems upon login to warn users not to accept the latest Java update. Furthermore, the same advisory was posted within EFS-Web and Private
“As soon as the problem was identified, the USPTO posted an advisory to the public via EFS-Web and Private PAIR announcement pages. As per your post, BB, today, about 2 weeks after this SNAFU started I get an eAlert from PTO, obviously trying to cover their _ss.