PDA

View Full Version : Is there any official word on JVM.DLL crashing?



XyZspineZyX
08-29-2003, 03:46 AM
If you put "mejoe" into the forum search engine over at the tech support forum you will see in increadable number of posts over a number of months describing my struggles with FB and JVM.DLL crashes. Untold reformats and reinstalls, using both Windows 98se and XP Pro (Pure XP Pro then SP1 with MS Virtual Machine then SP1a with Sun Java). Trying just about every driver available for every device in my machine. Even a new video card. At no time did any of this have the slightest effect on the behavior of the game. It was always the same "jvm.dll" crash.

I dispair of a fix short of a patch but at the same time I realize that the trouble may be so rare as to not be worth notice of UBI/Maddox. In light of this I would like an answer to just two simple questions so I will know weather to continue the struggle or to just give up on FB and move on. I have asked these many times, never have they been answered.

Is jvm.dll crashing a "known issue" recognized by UBI/Maddox?

If yes, is it being addressed in a patch?


Please note that I do not demand a fix, I only ask if there will be one.

XyZspineZyX
08-29-2003, 03:46 AM
If you put "mejoe" into the forum search engine over at the tech support forum you will see in increadable number of posts over a number of months describing my struggles with FB and JVM.DLL crashes. Untold reformats and reinstalls, using both Windows 98se and XP Pro (Pure XP Pro then SP1 with MS Virtual Machine then SP1a with Sun Java). Trying just about every driver available for every device in my machine. Even a new video card. At no time did any of this have the slightest effect on the behavior of the game. It was always the same "jvm.dll" crash.

I dispair of a fix short of a patch but at the same time I realize that the trouble may be so rare as to not be worth notice of UBI/Maddox. In light of this I would like an answer to just two simple questions so I will know weather to continue the struggle or to just give up on FB and move on. I have asked these many times, never have they been answered.

Is jvm.dll crashing a "known issue" recognized by UBI/Maddox?

If yes, is it being addressed in a patch?


Please note that I do not demand a fix, I only ask if there will be one.

XyZspineZyX
08-29-2003, 04:47 AM
Wrong forum.

However, I believe the official word on this matter is "splee".

XyZspineZyX
08-29-2003, 07:59 AM
Baloban wrote:
- Wrong forum.

I would have thought the same. Perhaps you missed the part in my first about all the posts in the tech support fourm?

In a reply to one of the many previously mentioned posts in the tech support forum I was told by one of the "moderators" that since I was asking about some possible fixes in a patch the proper place for that inquiry was not in the Tech Support forum but in "Oleg's Ready Room".


-
- However, I believe the official word on this matter
- is "splee".
-
-

Surprisingly, that is more information than I have gotten from amy of the other posts.

XyZspineZyX
08-29-2003, 10:11 AM
Sorry you got problems, man. I don't mean to be rude, and no doubt everyone has already suggested to you to patch IL-2, or FB, or whitchever version of the game you're talking about. Go ahead and make sure that whatever you're running is patched. Seriously.

Now, once you have applied all the relevant patches go back to the original 1.3.x Sun JVM that came with FB. I have a hunch that in your hacking you've replaced it with 1.4.

DO NOT USE 1.4.x JVM, because it will cause memory errors! If you've been mucking around with nonstandard JVMs already then I assume you know how to put 1.3 back in.

Good luck, and if EURO_Snoopy locks this thread, I'll meet ya back in the tech forum.

XyZspineZyX
08-29-2003, 10:16 AM
http://forums.ubi.com/messages/message_view.asp?name=Olegmaddoxreadyroom&id=zvthr

Oleg: Latest Java works slowly then previous and isn't more stable. Be sure.

Stick with 1.3.x JVM. Be sure.

Also, just to be sure, I hope you realise that installing MSJVM vs. Sun JVM at the OS level has zero effect on the game.

If none of this stuff made any sense to you and you still have problems, you're on your own.

XyZspineZyX
08-29-2003, 06:30 PM
I have the same problem. JVM.dll crashes the game.

don't know why...

....Now, when the game starts I start to pray.

S!*Umaydie*

XyZspineZyX
08-29-2003, 06:40 PM
Thanks for the suggestions.

I tried MANY versions of Java, all available here:

http://java.sun.com/products/archive/index.html

Numerous of the 1.3x series were installed on a fresh format along with changing out the dll in the game directory to ensure no "contamination" from a previous version. Non of these had the slightest effect on the program.

Most of the time when I was testing a different OS/driver/bios configuration I would reformat the drive and install ONLY the operating system, the various drivers and game. NONE of the many combinations of driver verstions and bios setting on either XP or 98SE had any effect whatsoever. Sometime within 15 minutes of booting the game the JVM.DLL crash would happen. Guaranteed.

I cannot try the patch because I no longer have the game. I have purchased the game twice and returned it twice. The first time after many reformats, driver changes, etc, etc. Being unable to fix the trouble and being equally unable to get any word from UBI/Maddox of a possible fix I
returned the game in self defense.

I purchased the game a second time when I got a new Video card. I went from an old but trusty GF2 Pro 32meg to a new ATI 9500 Pro. Again I repeated the reformats, driver changes, etc, etc and got the same results from the game and the same silence from UBI/Maddox. Back the game went to await the patch.

Now the beta patch is out but there is not a breath in the readme of any possible fixes of the jvm.dll problem. Requests for information in the TEch Support forum got the standard silence from UBI/Maddox but there was one reply from a guy who told me that he had no jvm.dll trouble until
after he applied the patch. The patch, he says, has put him in "Java Hell". Because of this reply I have not purchased the game a third time though I likely will after the final version is released. Keeping the car engine running for a quick return to the store if need be.

Sorry if I got a little cranky but this is maddening. If the Origional IL2 were not such a wonderful sim (ran fine btw) and were the promise of FB not so great I would have given up long ago. And it is not really the lack of a fix that is so frustrating.

I have been computing since the Commodore 64 days. realize that there is no such thing as a totally compatable machine and that no matter what kind of machine a person may have or how stable that machine may otherwise be there will be an occasional program that simply refuses to run on that machine. The program may work wonderfully on 99% of the computers in the world but it just dosent like yours.

It is entirely possible that my machine is one of the maybe 1% that FB will never run on without UBI/Maddox spending so much time and money tracking down and fixing the trouble as to make the effort financially insane. If that is indeed the case it is compleatly reasonable for UBI/Maddox to do NOTHING to fix the problem. What is NOT reasonable is for UBI/Maddox to ignore those having the trouble and are struggling to fix that which UBI/Maddox may have decided is not fixable.

It may be my hardware, then again it may be the program. I do not know and I *CANNOT* know without some word from UBI/Maddox. But in spite of my MANY requests UBI/Maddox has said NOTHING and it is THIS SILENCE and NOT the trouble itself that is so maddening.

Perhaps I can make it easy for UBI/Maddox with a multiple choice option.
================================================== ========================================
1. "We have found some bugs that can create a jvm.dll error and are working to resolve the issue."

or

2. We have found nothing in the program code that could cause a jvm.dll error and we are not going to bankrupt our company tracking down the cause of a rare problem only a few are having. If you have a jvm.dll problem that's just hard cheese. Change your hardware.
================================================== ========================================

Pick one. Both are reasonable and eIther will provide the answer I have been begging for. Lacking this I am stuck with trial and error and I will be buying FB for the third time when the final patch comes out. Fingers crossed I will try it again. If it works I keep it, if not then back it goes again to be purchased a fourth time when a new patch comes out or I change some piece of hardware.

XyZspineZyX
08-30-2003, 06:21 AM
Wow. Looks like there is really something funny going on, then. Wish I knew what to tell you /i/smilies/16x16_smiley-sad.gif

XyZspineZyX
09-01-2003, 05:21 AM
bump

XyZspineZyX
09-03-2003, 04:11 AM
bump

XyZspineZyX
09-04-2003, 03:34 AM
As before, continued silence.

Bump

Dark_Knight_667
09-05-2003, 10:13 AM
MeJoe

1. What are your complete system specs, ram, board, cpu, sound card, drivers etc.
2. Have you emailed Oleg a crashlog through the email address found in the 1.1 beta readme or the 1.1 final readme? Crashlog can be copied and pasted from the pop up you get by clicking on details or if using xp going to the xp error report via system information.
3. Have you also tried a copy of the said dll from another person's system?
4. What version of DirectX are you running as well 8.1 or updated to 9.0b which is the latest?


DK

http://members.cox.net/cptdarkknight/bkbanner.jpg


The Knights have arrived. AMD 2700 XP, Radeon 9800 Pro, Turtle Beach Santa Cruz, 30 gig hdd, Gigabyte GA-7VT600-L, 52x cd rom, microsoft intellimouse explorer, Saitek x45 HOTAS

<center><a href="http://www.bloggerheads.com/mash_quiz/" target="mash"><img src="http://www.bloggerheads.com/mash_quiz/images/mash_hawkeye.jpg" width="205" height="95" border="0"

XyZspineZyX
09-08-2003, 08:57 AM
Thanks for the reply

As I said in the second post in this thread I no longer have the game. Please read that post as to why.

Regarding my system and DX Diags please type "mejoe" in the forum search engine in the tech support forum. There are quite a few in there going back to March. Also detailed there is all the increadable gyrations, gymnastics and backflips I have done since March trying to get FB to run.

XyZspineZyX
09-09-2003, 12:16 AM
There is a .dll fix for the java error you are describing, at checksix web site.
http://www.checksix-fr.com/bibliotheque/detail_fichier.php?ID=1196
It may or may not help. One thing i have learned after building and repairing computers for the last several years now is that when a problem comes across the table as severe and unique (rare) as your is i ussually have found it to be hardware related. In other words the m-board, chipset imcompatibility isues possibly, and also there are some known issues with some procesors that have been released.
If go through the grueling process of elimination till I find the culprit causing the probs and often at a cost.
But i usually find it this way, and after the yrs i have into this i have a load of spare "known good" items for swap testing.
and even though an m-board costs a buck and a quarter average it might fix your probs, if i swapped every component out on a test and still had the probs i would go to buying a m-board.
MSI (Micro-Star International) is a really good board.

<CENTER>http://128th.com/128th_Insignia/128thSkullions_red.png <DIV><FONT face=Tahoma color=maroon size=2>"Like Birds of Prey, on Wings
of Steel, We Soar, at the Speed of Death to Prevail"... Gen. Talon-x</FONT>



Message Edited on 09/08/0308:35PM by Sk128th_Talon-x

XyZspineZyX
09-16-2003, 05:59 AM
Thanks for the suggestions. The Check6 DLL's were part of the routine substitutions following a driver change. As with the other stuff tried, there was zero change in program behavior.

As to a chipset incompatility, I would agree were it notfor the fact that some others with KT133a chipsets ar running the game and still others with NForce 2 and Intell P4 machines complaining of the jvm.dll trouble. Also, the original IL2 ran wonderfully on my existing machine.

That does not eliminate the possibility that FB does not like my chipset but it does make the proposition a little dicy without some word from UBI/Maddox as to the possible problem.

Can you think of any legitimate reason why near 70 posts since March have failed to spur the slightest response from UBI/Maddox?



Sk128th_Talon-x wrote:
- There is a .dll fix for the java error you are
- describing, at checksix web site.
- <a
- href="http://www.checksix-fr.com/bibliotheque/deta
- il_fichier.php?ID=1196"
- target=_blank>http://www.checksix-fr.com/bibliothe
- que/detail_fichier.php?ID=1196</a>
-
- It may or may not help. One thing i have learned
- after building and repairing computers for the last
- several years now is that when a problem comes
- across the table as severe and unique (rare) as your
- is i ussually have found it to be hardware related.
- In other words the m-board, chipset imcompatibility