vaylquy waikiki alastryn
Yamila Comejo
This post is now 6 years old, lots of parts of the solution have moved on. What version of IE are you using, have you tried using that in compatibility mode? Check out the out comments, search for fatal as others have the same issue, some of the comments might shine a light on a solutions which works for you. If you do find a solution please let us all know what worked for you. The original post was working when using IE 8 and Windows 7, so do not expect it to work with anything newer.
The repainting of the screen is cause by the version of oracle forms, because it just isnt designed to be ran on Windows 7.
If this is causing issues with you being able to see parts of the screen, then there is not much that you can do.
Spent several days tracking down a jvm.dll crash problem that was affecting these XP machines, I knew it had to be in the Jinitiator 1.3.1.13. Out of desperation I tried it and this fixed it. Thank you so much!
Apart from to get whoever programmed the app/forms to get it running with the latest Java JRE, or any JRE rather than relying on a technology that is years old and basically just an Oracle made dumbed down version Java Runtime.
Hi,
Sadly, I am not able to upgrade the version of jinitiator, and am just trying to get our unsupported version of ebusiness to run on windows 7. I have it working using XP mode, but it would be simpler to deploy if I could get it to work without using XP mode.
As I mentioned, this is not a version supported by Oracle, and with no support I cannot download the e-business patches that would be necessary for the Jinitiator upgrade. Also, as I have no Oracle support, I also have no access to any metalink articles that would explain how to do the upgrade.
Pretty section of content. I just stumbled upon your weblog
and in accession capital to assert that I get in fact enjoyed account your
blog posts. Any way I will be subscribing to your augment and even I achievement you access
consistently quickly.
I like the helpful info you provide in your articles.
I will bookmark your weblog and check again here frequently.
I am quite sure I will learn many new stuff right here!
Good luck for the next!
One other thought, is there any way to put this jvm.dll file in the oajinit.exe so that every time it is installed, it installs with the working jvm.dll?
This would be easier than having to install Jinitiator and then overwriting the jvm.dll file, especially for users in remote locations.
When I originally commented I seem to have clicked on the -Notify
me when new comments are added- checkbox
and from now on each time a comment is added I receive four emails with the same comment.
Perhaps there is an easy method you can remove me from that service?
Thanks!
Oracle provides jinitiator for web based oracle application. Basically jinitiator is a Java virtual machine that allows us to run client applications inside the web browser. If a web based oracle application can be accessed then we call JVM. The working we did with help of plug-in or an active control that is depending on browsers that is netscape or internet explorer. It provides the ability to specify java virtual machine on client machine instead of default browsers JVM. Jinitiator runs as a plug-in for the netscape navigator and different components of internet explorer and it is not able to replace or modify the JVM.
After that client can be downloading Jinitiator form with their viable rendition of working framework. When we introduce prophet Jinitiator effectively on our framework then client need to close down navigator and restart it and return to the landing page it that HTML page. Presently prophet jinitiator will run the application and utilize various boundaries in the tag to deliver the applet. After that navigator discover the page that indicates the prophet jinitiator and navigator will easily load and run the module from the neighborhood circle with any client intercession.
It utilizes storing ActiveX controls and COM segments just as it additionally utilizes the HTML tag and web engineers indicate that ActiveX controls or COM segments that should run as a piece of Web page such sort of segment incorporate the prophet jinitiator. At the point when internet explorer first discovered the HTML document around then it has been changing the record to indicate the utilization of prophet Jinitiator, the internet explorer to client it is alright to download ActiveX control endorsed with VeriSign by prophet company.
In that event the client taps on the yes button, at that point internet explorer will download prophet Jinitiator. After the establishment of prophet jinitiator it runs and uses its boundary in the tag to deliver the applet. After that web voyager discovers the site page adjusted to help prophet jinitiator and it will easily load and run oracle jinitiator from the neighborhood circle with no client intercession.
This website or its third-party tools use cookies, which are necessary to its functioning and required to achieve the purposes illustrated in the cookie policy. By closing this banner, scrolling this page, clicking a link or continuing to browse otherwise, you agree to our Privacy Policy
Working for a school district which, like most school districts, doesn't have the funding to update their Oracle based financial systems that heavily rely on the old school JInitiator app. While the versions of JInitiator like 1.3.1.22 work fine in 32bit versions of Windows 7, there seems to be a problem on systems running the Intel Core i3 and Core i5 processors where the JInitiator will load, but it won't refresh or repaint its windows. In our case, upon the initial load of the app, all we would get is a new IE window with a white page. If we resized the window or double clicked the title bar, it would repaint the screen, refreshing the content in the window. However, we would have to do that step every time we wanted something to happen in the window. Talk about a pain! We researched all sorts of stuff on it and found all sorts of weird fixes like "JIniator doesn't like multiple threads". Weird thing was, we had a Core i7 Quad Core machine running JInitiator on a 32bit Windows 7 without a problem. That had us scratching our heads... "What was different between the i3/i5 and i7 processors?" Well, the difference we found out, was the video. The i3 & i5 both had the new Intel HD Graphics controller whereas the Core i7 had a Nvidia GPU. I tried updating the Intel drivers to the latest and still no luck... Running across the specs of the computer, we noticed that the computers were advertised as having the "Intel HD Graphics with Dynamic Frequency Technology". That made me do some research to figure out what was so special about the Intel HD Graphics and what the heck "Dynamic Frequency" was. This ran me across the following whitepaper for the new Intel HD Graphics.
To save you some time from reading the whitepaper, I'll give you some background on the new iCore processors... Basically, Intel has moved the entire northbridge chip onto the processor. The northbridge in older computers was responsible for talking to the CPU, Memory, Video & Southbridge. Move that onto the processor and you get a blazing fast performance boost. In doing this, Intel has also followed AMD's footsteps by integrating their own GPU directly onto the die of select iCore CPUs (mainly i3 & i5), again providing much faster video performance and reducing overhead. "So what is this Dynamic Frequency?" To compliment their proprietary Turbo Boost technology which raises & lowers CPU frequency depending on CPU load, thus saving power, they have also included Dynamic Frequency which does basically the same thing for the GPU. It raises and lowers the speed of the GPU on the fly, to help conserve energy (longer lasting batteries, put smiles on tree huggers, etc.)
The fix is simple, believe it or not... You basically have to go into the power savings for Windows 7, edit the power plan and set the Intel Graphics to "Maximum Performance" which turns off the Dynamic Frequency.
If you have a computer that has it's own power saving software, I have no idea... You might have to do some playing... BUT, if you are using the stock Windows 7 power settings, you can do the following:
Update 2011/06/20: If the above isn't quite working out in your favor, you might try what was posted in the comments below regarding the manual input of some code to disable the drawing of jinitiator. (It basically shuts off the use of Direct Draw which was changed around quite a bit in Windows 7)
Take a look at RomanH's comment and see if it helps. There are several folks who have commented and said that this DOES work for them and one person mentioned restarting the computer after applying the fix before it worked. Unfortunately I have no easy way of creating a step-by-step process on how to apply the fix so hopefully what's posted below is enough to get you started on figuring it out.
Also...! Thanks to everyone who has posted comments on their fixes! I hate forums with a passion because everyone has the same problem but no one ever has a solid fix. I do my best to create a full proof fix for the problems I've run into on my blog and while the fix may have worked for me at the time, I'm not perfect either so I find it awesome when other's post the things that work for them and contribute to helping someone else. It makes searching for the problem in the future so much easier for everyone!
IF IT'S ANY HELP TO SOMEONE OUT THERE: I tried everything asides from trying a newer video driver. But what fixed it for me was to disable the video card in Device Manager (this makes the resolution massive) but then push the resolution back to your desired setting.
The refresh fix worked great on my HP Probook but now I cannot get Jinitiator 1.3.1.30 to work at all using Win 7 OS 64-bit on a HP 6000 machine. I changed the jvm.dll to ver 6 and still does not work. I think it is because the install cannot create the .jinit folder under users directory for the two files to write to when running JINITIATOR. This question may be better as a new post but I thought I would toss it out there to see if anyone has seen this issue and resolved it.
c01484d022