|
|
Optimize with a SATA RAID Storage Solution
Range of capacities as low as $1250 per TB. Ideal if you currently rely on servers/disks/JBODs
Page 5 of 6
Step 0: The following assumptions have been made:
/I "c:\jdk1.1.5\include" /I "c:\jdk1.1.5\include\win32"Step 1: Identify all required files
C++:
Java:
Miscellaneous
Step 2: Create zip.ini and copy this file into the Windows directory
The zip.ini file contains a single section called CONFIG. There is one entry in this section, PATH. The PATH entry contains the path (without a trailing backslash character) where the ZIP application has been installed. This is shown
in the following listing.
[CONFIG] PATH=c:\zip
Step 3: Create a directory for the ZIP application (ex: c:\zip)
Step 4: Copy the following files into this new directory:
Step 5: Test the application
Change to the zip directory and type: zip. The following should appear on the screen:
c:\zip>zip zip v1.0 usage: zip [-x file] zip
If you get to this point, then you've just executed your first dedicated Java/Win32 application. Congratulations!
What comes next? The ZIP example illustrates a console user interface (CUI) Windows application, but Windows can also run graphical user interface (GUI) applications. A next step could be the creation of a standalone Windows GUI application written in Java. If you decide to go this route, however, you'll need some knowledge of various support DLLs that are distributed with the JVM.
The names of the following DLLs are pretty much self-explanatory. The Java Interpreter (or JVM) is stored in the javai.dll file. If you want to create a GUI-style application, you will also need to deploy the winawt.dll file. This file contains awt peer class support code as well as code to handle printing chores.
If you get into the habit of creating lots of Java/Win32 applications, you may find that you are distributing multiple copies of classes.zip, one per application directory. At eight megabytes a pop, this gets rather expensive in terms of disk space usage. A better solution would be to modify the driver C++ file to obtain two separate paths: one from the initialization (ini) file (or even Windows registry) for the application classes, and another for classes.zip. You could then store classes.zip in a common directory.
Sun has made it clear through its JDK license agreements that all runtime files are to be distributed without modification. The ZIP example application required no changes to any runtime files, and it is doubtful that any application would need to have these files modified. However, this does not mean that all of these runtime files need to be distributed with any given application. I hope that Sun will relax this restriction.