liyqxtu / droiddraw

Automatically exported from code.google.com/p/droiddraw
0 stars 0 forks source link

This application requires a Java Runtime Environment 1.4.0 #114

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Run Program

What is the expected output? What do you see instead?
The program comes up with that error and doesnt run.

What version of the product are you using? On what operating system?
Windows 7

Please provide any additional information below.
I have the latest JRE already installed

Original issue reported on code.google.com by Vabb10 on 24 Nov 2009 at 6:42

GoogleCodeExporter commented 8 years ago
I too am experiencing this issue.

Original comment by sesmit...@gmail.com on 25 Nov 2009 at 10:54

GoogleCodeExporter commented 8 years ago
I installed jre 1.4.0 as I was getting the error message. After that I am 
getting 
another error "Could not find main class. program will exit."

Original comment by ananthk...@gmail.com on 9 Dec 2009 at 8:19

GoogleCodeExporter commented 8 years ago
I installed the latest version of JDK, showed below:
java version "1.6.0_17"
Java(TM) SE Runtime Environment (build 1.6.0_17-b04)
Java HotSpot(TM) Client VM (build 14.3-b01, mixed mode, sharing)

But when i tried to run"droiddraw.exe", the error" This appication requires a 
Java 
Runtime Environment 1.4.0"?? 

p.s.
1,i tried in another computer with the same environment, and it's ok;
2,i tried to install jre 1.4, but the error still happened

please help us to solve this

Original comment by edwar12...@gmail.com on 11 Jan 2010 at 4:16

GoogleCodeExporter commented 8 years ago
It happened on my computer too.
Windows7 x64 JDK1.6.0_20

Original comment by Zoozy.cn@gmail.com on 5 Jul 2010 at 2:25

GoogleCodeExporter commented 8 years ago
I have this same issue but I believe it has to do with you using x64 version of 
java and therefore droiddraw looks for x86 version. But a work around is to run 
droiddraw.jar. I am running x64 java and droiddraw.jar works.

Original comment by drummond...@gmail.com on 4 Aug 2010 at 2:00

GoogleCodeExporter commented 8 years ago
Issue 134 has been merged into this issue.

Original comment by brendan....@gmail.com on 6 Sep 2010 at 4:46

GoogleCodeExporter commented 8 years ago
Same issue, with windows 7 and x64 jre.  Running the jar works fine for me.

Original comment by jbec...@gmail.com on 16 Oct 2010 at 9:00

GoogleCodeExporter commented 8 years ago
I tried the .jar from google. Then I found droiddrawr1b20.jar. That worked for 
me. 
http://code.google.com/p/droiddraw/downloads/detail?name=droiddrawr1b20.jar&can=
2&q=

Original comment by AndrewAd...@gmail.com on 3 Jul 2011 at 7:31

GoogleCodeExporter commented 8 years ago
only run droiddraw.jar,will be ok!!!(well u can using "java -jar 
droiddraw.jar"...)

my os: win7 ultimate 64bit
Javase 1.6u27 (Oracle)

Original comment by 52mac...@gmail.com on 9 Oct 2011 at 9:09

GoogleCodeExporter commented 8 years ago
failed too, with Windows 7 (x64) JDK 1.7.0

Original comment by celia781...@gmail.com on 15 Nov 2011 at 11:26

GoogleCodeExporter commented 8 years ago
This is a known problem w/ the .exe.  For now, please simply double-click the 
.jar file to run.

I will attempt to build a 64-bit compatible .exe file for the next release.

Original comment by brendan....@gmail.com on 28 Dec 2011 at 6:12

GoogleCodeExporter commented 8 years ago
Issue 225 has been merged into this issue.

Original comment by brendan....@gmail.com on 28 Dec 2011 at 6:13

GoogleCodeExporter commented 8 years ago
I have uploaded a new release candidate (r1b21-rc1).  Can someone with 64bit 
windows try this out and see if it works?

Thanks
--brendan

Original comment by brendan....@gmail.com on 7 Jan 2012 at 9:42

GoogleCodeExporter commented 8 years ago
I have tried, the r1b21-rc1 version has been worked fine.

mine environment

Win7 X64
java version "1.7.0_01"
Java(TM) SE Runtime Environment (build 1.7.0_01-b08)
Java HotSpot(TM) 64-Bit Server VM (build 21.1-b02, mixed mode)

Original comment by herobe...@gmail.com on 10 Jan 2012 at 2:10

GoogleCodeExporter commented 8 years ago
I believe this is fixed in the latest releases.  The old binary was looking for 
a 32-bit JVM.

Original comment by brendan....@gmail.com on 29 Apr 2012 at 4:39