Submitted On 04-DEC-2000
aguntur1
extra information: The error message generated
The instruction at "0x004049eb" referenced memory
at "0x000013a0". The memory could not be read.
work around is as stated above, install the plug-in by hand.
Submitted On 19-DEC-2000
herbersj
I have this same problem. When I use the workaround to
install the plug-in manually, it shows up twice in IE's
Objects list, and is marked "Damaged". It still seems to
work ok, but this is somewhat disconcerting.
Submitted On 20-DEC-2000
adrianjohnson
I get the same results with IE5 (5.00.2014.0216IS 40-bit)
on NT4. After excepting the download and pressing install
button I get an Access violation 0xc0000005 at Address:
0x004049eb.
Submitted On 16-JAN-2001
mjennings
the jinstall.exe in jinstall-130_01_win32.cab is 102484
bytes
the jinstall.exe in jinstall-13-win32.cab is 102492 bytes
the jinstall.exe that is 102484 bytes crashes, the other
does not.
Submitted On 16-JAN-2001
mjennings
When all is said and done, jinstall.exe gets extracted from
jinstall-130_01-win32.cab then gets launched like so:
"jinstall.exe
http://java.sun.com/products/plugin/1.3.0_01/jinstall_1_3_0_
01.ini"
The jinstall.exe I extracted myself from jinstall-130_01-
win32.cab and launched with the above command line gave me
the exact same errors described by this bug id. The problem
seems to be in jinstall.exe
Submitted On 20-JAN-2001
hughallen
TWO VERSIONS IN A ROW of the Java Plug-in have HUGE,
OBVIOUS BUGS related ONLY TO IE. Does Sun QA ever use IE
for testing? If so, these bugs are EASY to find.
Version 1.3 has the "white streaks" problem described in
Bug# 4250240. It IS fixed in 1.3.0_01, BUT IS NOT
DOCUMENTED IN THE LIST OF BUG FIXES FOR 1.3.0_01.
[DOCUMENTATION BUG?]
Plug-in Version 1.3.0_01 CRASHES due to JInstall bug
described above. Appears to ONLY crash on Win98 with IE,
but this is the MAJORITY of my installed user base.
These problems with IE are causing me and my PAYING
CUSTOMERS UNTOLD GRIEF AND FRUSTRATION and limiting
customer acceptance of the product.
It's bad enough that we have to use a plug-in in the first
place. Even Netscape 6, the target of 1.3.0_01, does NOT
install the Java Plug-in in a standard install - you have
to select "custom" or "full" install.
WHEN will we see 1.3.0_02? Will it actually INSTALL???
Submitted On 02-FEB-2001
macgibbon
My users lose interest if they have do something "manually"
so that doesn't work. I could use plugin 1.3 but then
printing the screen doesn't work. What is a decent
workaround is to replace the cab with the jre executable
the cab file points to. The exe seems to be signed so it
will load and run instead of JINSTALL. It's a long download
without much visual feedback, but it does work and avoid
the general protection fault. This JINSTALL bug was
reported weeks ago. I understand the importance of a
managed versioning cycle but this appears to be a problem
with the delivery package (JINSTALL and the CAB file)
rather than the java plugin itself. I don't understand why
the CAB file and the standard download page wasn't fixed
immediately. I don't see why we need to wait for 1.3.0-02.
It is very, very difficult to convince my peers that Java
is a serious tool when the standard installation general
protection faults on 39 of 40 computers in the company.
Java 1.3 is a fine piece of work, but you have muffed the
installation program!!!!!!
Please pardon the football analogy, but the installation
program of 1.3.0.01 is like a football player returning a
kickoff 99 yards and fumbling the ball on the goal line.
html looks like this:
<OBJECT classid="clsid:E19F9330-3110-11d4-991C-005004D3B3DB"
WIDTH = 700 HEIGHT = 500
codebase="http://java.sun.com/products/plugin/1.3.0_01/j2re-
1_3_0_01-win.exe#Version=1,3,0,1">
<PARAM NAME = CODE VALUE =
com.transonic.acquisition.gui.HD01SimpleApplet.class >
<PARAM NAME="cache_option" VALUE="Plugin">
<PARAM NAME="cache_archive" VALUE="HD0213.jar">
<PARAM NAME="type" VALUE="application/x-java-applet;jpi-
version=1.3.0_01">
<PARAM NAME="scriptable" VALUE="false">
<COMMENT>
<EMBED type="application/x-java-applet;jpi-
version=1.3.0_01" CODE =
com.transonic.acquisition.gui.HD01SimpleApplet.class
ARCHIVE = HD0213.jar WIDTH = 700 HEIGHT = 500
scriptable=false
pluginspage="http://java.sun.com/products/plugin/1.3.0_01/pl
ugin-install.html"><NOEMBED>
</NOEMBED>
</EMBED>
</COMMENT>
</OBJECT>
<!--
<APPLET CODE =
com.transonic.acquisition.gui.HD01SimpleApplet.class
ARCHIVE = HD0213.jar WIDTH = 700 HEIGHT = 500>
</APPLET>
Submitted On 23-FEB-2001
jnp11
When will the non-released bug-fix be available?
Being reported first time in december and still not corrected?
Submitted On 21-MAY-2001
toriver
Bug still appears to be present in 1.3.1 final...
We use IE 5.5 under NT, and 1.3.0_01 is already present on the machine.
Submitted On 22-MAY-2001
elingdo
I am also seeing this bug in 1.3.1 final. I'm running IE
5.0 on Win2k.
Submitted On 23-MAY-2001
zgui
This bug appears in version 1.3.1 again!! I tried on five
machines. None of download was successful.
Submitted On 23-MAY-2001
schinzel1
As mjennings mentioned above: the jinstall.exe in jinstall-
13-win32.cab works - but the jinstall.exe of jinstall-131-
win32.cab does not. This is really BAD!
So I did a really _ugly_ work-around:
I took the jinstall.exe of the 1.3-cab and the
jinstall_1_3_1.inf of 1.3.1 final and packaged them into a
new cab...
It works!
The installation works fine, but the .cab does not have a
authentic signature anymore. Therefore you have to reduce
the security-settings in IE...
And the Version Number during download-process says 1.3
instead of 1.3.1 - but thats OK for me :-)
So SUN please tell me: why can't you just fix this ugly
little jinstall.exe??? Even the 1.3.1 final has this bug -
why?
Submitted On 24-MAY-2001
mclain
We're seeing the same bug as well. Note the bytes at Bytes at CS:EIP match the reported bug above:
JINSTALL caused an invalid page fault in
module JINSTALL.EXE at 017f:00404d0b.
Registers:
EAX=00001476 CS=017f EIP=00404d0b EFLGS=00010206
EBX=00000073 SS=0187 ESP=0064ef64 EBP=0064f1b8
ECX=00001476 DS=0187 ESI=7ffffffe FS=0f7f
EDX=7fffffff ES=0187 EDI=0064f253 GS=0000
Bytes at CS:EIP:
80 38 00 74 03 40 eb f1 2b c1 e9 8f 01 00 00 c7
Stack dump:
00000000 0064fd30 bff54efc 00003334 00000005 00000000 0015010c bfb98ea5 000008b8 00000005
00000000 0015010c 0064efb8 00008028 0064f004 00000003
Submitted On 30-MAY-2001
bikestain
I see the same problem with 1.3.1
Crash on plug-in download.
1.3.0.02 seemed to work fine. Unfortunately 1.3.1 has
significant perfromance improvement in signed applet class
loading, so it is really petty to rturn back to 1.3.0.02 ;(
Also, manual installtion is not acceptable by most of our
customers.
Submitted On 21-JUN-2001
mjennings
I did exactly what schinzel1 did, but in addition I
purchased a Thawte digital certificate in order to sign the
resulting CAB file. I put a demo applet up at
http://southgatesoftware.com/plugin/SwingSet2.html
if anyone wants to test it out.
Submitted On 25-JUN-2001
eunger
I was going to demonstrate the power of Java to my
executive department by sending the latter a link to the
Java2D examples page (Available at
http://192.9.48.9/products/plugin/1.3/demos/jfc/Java2D/Java2
Demo.html).
None had the Java Plug-in installed and all had to install
it. The outcome? The installation of the plug-in crashed
for ALL of them (Windows NT or Windows 2000 SP1 users
alike, using IE 5.00.3103.1000).
They all got the "jinstall has generated errors..."
error message.
I was thuis asked to focus my efforts to technologies more
reliable and sound, less "bleeding" edge.
For a bug that was reported back in November, it's almost
scary.
Submitted On 11-JUL-2001
Viltris
Yeah, I have this exact same problem with both Plugin 1.3.1
and Plugin 1.3.0_01 on IE5.5 on both Windows ME and Windows
98.
Submitted On 19-JUL-2001
klchin
This is sad...it's July 19, 2001. This bug having been
reported 9 months ago has yet to be fixed. How are we
supposed to implement an java applet solution for our
customers when the install crashes. We can't! This is
utterly unacceptable considering the amount of time Sun
Microsystems has had to fix this bug. it's been almost a
year??!
Submitted On 25-JUL-2001
rpashula
I with you. Our whole corporation with over 2000 "standard"
NT4 SP6a pc's can't auto install the v1.3.1 Java Plug-in
because the jinstall crashes. Who in sun do I send the bill
for deploying over 2000 JRE v1.3.1 the old fashion way.
This bug should not be closed, because it's not fixed.
Submitted On 26-JUL-2001
sjlegg
Still waiting. Maybe we should be hitting Plugin forum
http://forums.java.sun.com/forum.jsp?forum=30
Submitted On 01-AUG-2001
mattcoz
IIIIT'S BAAAAACK
So you fixed it in 1.3.0_03? Why does it still happen in
the official 1.3.1 release?
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|
