🚀 go-pugleaf

John

Thanks again.. but I'm not sure what you did..

> You should be able to construct a native executable yourself in JBuilder
> 2005, using the JBuilder executable from JBuilder X.  In fact, as a simple
> test, you can just take the native executable you built, and tack the
> JBuilder X launcher on to the front of it....

How?

Also, do you think this is an issue for Quality Central?

db




"John McGrath [TeamB]" <ng-b@JPMcGrath.net> wrote in message 
news:xn0dzr0ot544akv00a@newsgroups.borland.com...
> On 3/13/2005 at 6:18:43 AM, David Bolsover wrote:
>
>> More detail:
>> 1 Compile using JB2005, JDK1.5 and JDK1.5 specific libraries and run on
>> ME, JVM 1.5  - Exception in Kernel
>> 2 Compile using JB2005, JDK1.5 and JDK1.5 specific libraries and run on
>> XP, JVM 1.5  - OK
>> 3 Compile using JBX, JDK1.4 and JDK1.4 specific libraries and run on ME,
>> JVM 1.5/1.4  - OK
>> 4 Compile using JBX, JDK1.4 and JDK1.4 specific libraries and run on XP,
>> JVM 1.5/1.4  - OK
>
> FYI, I tried:
>  JB2005 + JDK 1.5  /  ME, JRE 1.5 - Error
>  JB2005 + JDK 1.4  /  ME, JRE 1.5 - Error
>
>> I'd like to do more testing - in particular JB2005 + JDK1.4 + ME + JVM
>> 1.4.- but don't have an ME client available locally (yet).
>
> Yes, that would be a useful data point.
>
>> Also, in all cases, the app runs just fine if I launch from the .jar
>> file rather than and .exe.
>
> Yes, that was the same for me.
>
>> It looks like the problem is associated with the JB2005 + JDK1.5 + ME +
>> JVM 1.5 combination - but you also saw this with 1.4 code - could it be
>> that the problem lies in a difference between the .exe generated by
>> JBX/JB2005?
>
> Yes, I suspect that is the case.  It could be that the EXE generated by
> JBuilder 2005 has problems loading both JRE 1.4 and JRE 1.5, or it could
> be isolated to JRE 1.5.  The one additional test you mentioned would clear
> that up.
>
>> Do you know id the .exe code has been changed?
>
> The code has definitely changed, although I do not know what the changes
> involved.  It is not too hard to see that it has changed, if you know how
> the native executable builder works.  Just look at the launcher programs
> used to launch JBuilder in the two different JBuilder versions.  It is the
> same program used to make the native executables.
>
> When JBuilder builds a native executable, what it does is build a JAR
> file, then concatenate the JBuilder launcher and the JAR file, creating a
> single executable file.  Windows executables are built (and read) from the
> front, so if you tack some junk onto the end, it has no effect.  ZIP and
> JAR files are built from the back, so if you tack some junk onto the
> beginning, it has no effect.
>
> When you run the combined executable / JAR, this runs the Java launcher.
> It places the executable file itself (which is also the JAR file) on the
> classpath and starts the JVM.  There are a few more interesting details:
> for example the configuration information, like the JBuilder.config file,
> is stored in the ZIP comment, but that is basically how it works.
>
> You should be able to construct a native executable yourself in JBuilder
> 2005, using the JBuilder executable from JBuilder X.  In fact, as a simple
> test, you can just take the native executable you built, and tack the
> JBuilder X launcher on to the front of it.  With my test program, that
> works fine on Windows ME.
>
> -- 
> Regards,
>
> John McGrath [TeamB]
>
> ---------------------------------------------------
> Before sending me e-mail, please read:
>    http://www.JPMcGrath.net/newsgroups/e-mail.html