Pingback: Jinitator not working on Windows 7 | Platonic
*Note, I would never normally recommend Internet Explorer, it’s just that this process doesn’t work for me using Chrome or Firefox, my preferred browsers.
See post repaint blog post on how to fix the repaint screen issues, if they are happening to you. Restart IE* and try again, Windows 7 should reduce your colour scheme and your app should now work. Replace the ‘jvm.dll’ in jinitiator directory (C:\Program Files (x86)\Oracle\JInitiator 1.3.1.13\bin\hotspot\) with this file jvm.dll.
Install Jinitiator as normal, if your having problems actually getting it to install, just use the Win7 ‘compatibility mode’ to get it to stay on your machine instead of it annoyingly uninstalling itself at the end of a failed install process. They insist that you must use Jinitiator 1.3.1.13 & windows XP! Joy! We also know that Jinit is no longer supported by Oracle & refuses to work with Windows 7. The applications in-house team havent managed to get it working with JRE, which is the replacement to Jinit. Just for the record, I tested this using Oracle forms 10.1.2 running in IE60 a bit and as Wilfred noticed that there are known issues with 1.5.0 I will see if there are issues running 1.5.0.11.We need ‘Jinitiator 1.3.1.13’ to use a core application. Note that when you do not have JPI 1.5.0.11 installed on your machine you will be prompted to install it the first time you launch your application in the same way you are prompted to install JInitiator the first time you launch your application. Save the file and you are up and running. Jpi_mimetype=application/x-java-applet version=1.5.0.11 # Parameter related to the version of the Java Plugin # (NOTE: you should check this page and possibly change the settings) # Sun’s Java Plugin is typically used for non-Windows clients.
# Page displayed to users to allow them to download Sun’s Java Plugin. In my case I used the download URL of sun but this could also be your local server.Īs last make sure that the jpi_mimetype points to the correct version # System parameter: base HTML file for use with Sun’s Java Plug-InĬhange the jpi_download_page to the proper URL. The different download sites can be found hereĬhange the jpi_classid to the proper version of the Java PluginĬhange the jpi_codebase to the proper place the file is located. # System parameter: base HTML file for use with JInitiator client # System parameter: default base HTML file Make sure that the baseHTML, baseHTMLjinitiator and baseHTMLjpi parameters point to your basejpi.htm Make a backup of your formsweb.cfg file just to make sure you never know.
My goal was to use the static version of the Sun JPI version 1.5.0.11 My customer sells validated software which complies with FDA regulations therefore I did not think it would be a good idea to use dynamic versioning since JPI 1.6 is not supported yet by Oracle. He has a good blog site called OraTransplant in which he had posted an article on how to use dynamic versioning of Sun JPI and Oracle Forms. How did I know? Well I had read the blog of Wilfred van der Deijl. In my opinion a loss which was not needed since you can run Webforms without JInitiator using the SUN JPI. In the real world it is much easier to convince them that the SUN JPI is needed to be installed for your application. And as we all know it’s often quite a challenge to convince a system admin to install something he does not know and doesn’t want to know. A few weeks ago one of my customers told me that he lost a sales opportunity because the customer who he was trying to sell his software too had problems convincing his system administrator to install JInitiator.