JAVAšluk!

Primećujete igru riječi u naslovu, ne?

Prvo, zašto JAVA. Treba ti jednostavno za sve živo: za e-banking, za razne programčiće na vebu, za razvoj itd. I, ako nije ažurna, ume da pravi problem. A Java je glomazna i bušna ko moldavski budžet i onda treba da se apdejtuje svaki čas. Što ne bi trebalo da je problem, jer se pojavi jedno obaveštenje i tu klikneš i posle još jednom i krene instalacija. S tim što ne krene. I tu stižemo do javašluka Oraklovog. Ali, da se vratim malo.

Da pitaš sad ljude, 95,9 posto koristi Windows pod admin nalogom. To znači da ih komp retko kad pita za nešto, sve se instalira tek tako, prosto juzabiliti na maksimumu. Dok se ne pojavi neka masna malverčina i upropasti SlikeSaLetovanja2010 i sve sejvgejmove Star Wars-a. Dakle: NE KORISTITE KOMP POD ADMIN NALOGOM, no pod standardnim. Kad zatreba neka instalacija ili nešto, unese se lozinka admin-naloga i toeto. Naravno, ne treba stavljati 64 znaka u lozinku.

Međutim, Orakl je po nekim pitanjima ostao u eri Windows 95, pa automatik apdejt Jave neće raditi ako nisi admin. I kapak. Posle višegodišnjeg smaranja i redovne ručne instalacije i par kilo-psovki, nađoh rešeeeinje!

Elem:

It turns out that when the java updater attempts to download new updates, it uses the Windows service called “Background Intelligent Transfer Service” (BITS). If the logged on user is only a standard user, then the java updater fails to correctly use the BITS service to download the new update. However, if the BITS service is not available for use by the java updater (either the service is disabled or permissions are denied to the calling process), the java updater uses an alternate mechanism for downloading and applying updates that works successfully, even if the original user was just a standard user with limited rights (no administrative rights).

In order to elevate the java updater so that standard users can install java updates, we must first set the application compatibility mode of the java updater so that will run in compatibility mode for Windows 2000, which did not have the “Background Intelligent Transfer Service”. This will force the Java updater to use the alternate mechanism to download the java updates.

http://privilegeforum.scriptlogic.com/Forum/aff/3/aft/193/afv/topic.aspx

So what you do is:

  1. find jucheck.exe (mine’s under %PROGRAM_FILES%\Common Files\Java\Java Update)
  2. open it’s properties and set it to run in Windows 2000 compatibility mode (for all users or at least for your elevated one!)
  3. check for updates again through Java Control Panel

The installer will nagg about your OS not being supported, but will allow you to install the update.

Hvala, gdine Predi, gad bles ju.

 

 

Comments

comments

Comments are closed.