开云体育

I've created a first version of a Windows installer. I'd like to have somebody try it and tell me how to make it better.

Also, does anybody know how to make a "Windows icon file"? If I can get one of those, the installer can set the various icons to something less generic.

The installer can be downloaded from:



As you can see from the name, this is a new version. Testing is not complete (the installer is really meant to test the _installer_, not the new version). It has the updated decoder selection GUI of the 9.3 test version, with only a little additional tuning. The Lenz LI100 support seems to be working, though, and there are a couple of other minor improvements.

Because this is a test version, it will install "alongside" any existing install you've got. This means that you'll have to set it's preferences, etc, but on the other hand you won't lose your locomotive roster and settings if the installer doesn't work.

Thanks in advance, I appreciate the feedback.

Bob
--
--------------
Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957)
Am working off a huge email backlog, call if it's urgent.

I'm downloading it now...

Alex

Ok, I have installed onto Win2K

Seemed to install ok although I noted that the installer didn't ask which
JVM I wanted to use and stuck the comm.jar file into the JVM under
C:\JBuilder4\jvm Maybe there is a way/option to let the user choose which
JVM to put the comm stuff into

I had to modify the DecoderPro Menu Shortcut and specify a value for the
"Start In" directory to:

"C:\Program Files\JMRI"

I also had to modify the DecoderPro.bat file and change the classpath
definition from:

java -Djava.class.path=".;jmri.jar;lib\collections.jar;lib\log4j.jar;lib\jdo
m-jdk11.jar;lib\crimson.jar;lib\comm.jar;$VFS" apps.DecoderPro.DecoderPro

to

javaw -classpath
".;jmri.jar;lib\collections.jar;lib\log4j.jar;lib\jdom-jdk11.jar;lib\crimson
.jar;lib\comm.jar;$VFS" apps.DecoderPro.DecoderPro

as it was complaining about not finding the main class. Must be a MacOS /
Windows thing...

We have just got JBuilder7 at work and it has the ability to build a native
executable wrapper to lauch Java applications and it is supposed to be able
to setup specific classpath and which JVM to use etc - haven't played with
it yet but maybe I should...

Cheers

Alex

Bob,

I have a simple program that will create a Windows ico file with a set of
icons in different resolutions / color depths. Unfortunately it is old and
will only do up to 16 colors so I can't make the 256 color icons that are
used now. Some of the basic icon format are:

16x16 16 color (small)
32x32 16 color (large)
32x32 2 color (does any have a monochrome display anymore?)
32x16 2 color (old CGA format?)

48x48 256 color seems to be common now but as mentioned I can't make this
one.

The developer supports the icon sizes in the file that they feel like.
Windows is supposed to figure out which one to use. For starters just
"small" and "large" will be more than enough I think.

If you send me a .bmp file that is around 32x32 I can try to make a simple
icon file.

Robin

Robin,
Before I retired I had a program on the computer at work that made
icons. Can't remember the name of it. Real simple program but as it was
some time ago it was probably 16 color also.
Download.com has all sorts of icon creators, like 121 programs. I would
try but am not an artist so not sure how they would turn out. Looks like
some do a picture capture and create an icon out of it.

Jon Miller
AT&SF
For me time has stopped in 1941
Digitrax DCC owner, Chief system
NMRA Life member #2623
Member SFRH&MS

At 10:32 PM +1200 6/28/02, Alex Shepherd wrote:

Ok, I have installed onto Win2K

Thanks!

Seemed to install ok although I noted that the installer didn't ask which
JVM I wanted to use and stuck the comm.jar file into the JVM under
C:\JBuilder4\jvm Maybe there is a way/option to let the user choose which
JVM to put the comm stuff into

The installer currently adds it to the JVM that the "java" command will invoke. It needs to be there because the program is started using "java" or "javaw". The installer gets that info from the registry, using the same keys that the "java" command uses.

It's interesting that JBuilder apparently installed its own JVM.

I could add a prompt to the user to pick the JVM(s) should get the comm stuff, but I'm concerned that's too confusing. I suspect that J. Average User doesn't really want to worry about Java at all.

I had to modify the DecoderPro Menu Shortcut and specify a value for the
"Start In" directory to:

"C:\Program Files\JMRI"

I also had to modify the DecoderPro.bat file and change the classpath
definition from:

java -Djava.class.path=".;jmri.jar;lib\collections.jar;lib\log4j.jar;lib\jdo
m-jdk11.jar;lib\crimson.jar;lib\comm.jar;$VFS" apps.DecoderPro.DecoderPro

to

javaw -classpath
".;jmri.jar;lib\collections.jar;lib\log4j.jar;lib\jdom-jdk11.jar;lib\crimson
.jar;lib\comm.jar;$VFS" apps.DecoderPro.DecoderPro

as it was complaining about not finding the main class. Must be a MacOS /
Windows thing...

These are both the same mistake. I should have set the desktop shortcut and the program menu item to always start in the program directory. Thanks for finding it.

We have just got JBuilder7 at work and it has the ability to build a native
executable wrapper to lauch Java applications and it is supposed to be able
to setup specific classpath and which JVM to use etc - haven't played with
it yet but maybe I should...

That's probably a lot better than the .bat files that are used now.

Bob
--
--------------
Bob Jacobsen (Bob_Jacobsen@..., 510-486-7355, fax 510-495-2957)
Am working off a huge email backlog, call if it's urgent.

The installer currently adds it to the JVM that the "java" command
will invoke. It needs to be there because the program is started
using "java" or "javaw". The installer gets that info from the
registry, using the same keys that the "java" command uses.

Ok, that seems reasonable.

It's interesting that JBuilder apparently installed its own JVM.

I think this is only for the Windows install, but the UNIX installs assume
its already there.

I could add a prompt to the user to pick the JVM(s) should get the
comm stuff, but I'm concerned that's too confusing. I suspect that
J. Average User doesn't really want to worry about Java at all.

It didn't really occure to me that this is what happens. I usually have one
JDK/JRE in my path to ensure it works as I expect. However now that you
mention this, I bet that it has been using the reg setting and ignoring
what's in my path as the java.exe in c:\WINNT\wherever is found before the
others and then it does the reg lookup to know which JVM to load.

I just removed Java from my path and sure enough DP still works fine - you
learn something new each day...

These are both the same mistake. I should have set the desktop
shortcut and the program menu item to always start in the program
directory. Thanks for finding it.

Yeah, I removed DP, reinstalled DP from install file, set the Start in
directory and it worked fine.

We have just got JBuilder7 at work and it has the ability to build a

native

executable wrapper to lauch Java applications and it is supposed to be

able

to setup specific classpath and which JVM to use etc - haven't played

with

it yet but maybe I should...

That's probably a lot better than the .bat files that are used now.

Yes I will look closer at it. It looks to build executables for all
supported platforms ie it has check boxes for Linux and MacOS files as well
as Windows. It also looks like it includes all the JARs and everything in
the native executable as well, kinda sounds like a self extracting ZIP file.
If this is the case, I'm guessing that we could end up with just the native
executable and the XML files for an install. Time will tell...

Cheers

Alex