Hello Gorf ;
I researched error 1772 , and it certainly is a java install error. The fix I read about on
http://www.sysopt.com/forum/showthread.php?threadid=189016
basicly says that you should do 3 things. 1) go to start/settings/control panel/add/remove programes and ensure that java is not already installed, if it is, remove it compleatly. 2) close all running programs, including antivirus, any open browsers, anything located in your taskbar by your clock… all running background processes. 3) reinstall java.
error 1335 as i researched it, seems to be cuased by serveral differant issues, and is a bit more complicated, sometimes caused by Hardware, and sometimes caused by software configurations… the basic advice i saw in most places lays out this way.
The java web site says this about error 1335
CAUSE
These errors are InstallShield error codes, which indicate that an action failed during the installation process.
SOLUTION
Please try to download and install the offline installation package from the manual download page:
Please click here to download the offline package manually
Other advice i saw on the web included:
Redownload your java installation, sometimes a currupt install file will cause this problem.
Do not use a Download manager of any type to dl the file, sometimes these seem to cause a problem when dling from sun/java
When installing ensure that you have nothing at all running just like above.
Belive it or not, some
The following is a quote from one web site i visited concerning error 1335:
" tried taking RAM from socket 2 and placing it in the first socket. Suddenly my computer couldn't even restart. It shows out the RAM I had in socket 2 is defective - but it didn't show when placed in socket 2. Turns out that when placed in socket 2 it causes errors when installing software using .cab files.
Meaning: You might have defective RAM - and not even know it
I use 2 x 512 MB RAM - they are both Samsung 512MB DDR PC3200 CL 3, since one of them works fine I know it's not an error in all Samsung RAM.
My advice - check your RAM - it might be BAD

"
Considering that Authors notes, checking your ram may be a good idea.
I hope this was at least some help. This certainly is a commong problem, and one with out a clear solution … Please let me know how this all turns out for you.
WOLFGAR :hat: