Documentation for RENAME1.CMD.

This is a fairly simple .cmd file will take the java114 files and 
copy them with their final names to another directory. This is 
useful if you are having problems with the Feature Install or just 
don't want to use it. I used it to split up the various components, 
ie. runtime, toolkit, etc. It is a quick-and-dirty and really doesn't 
have anything in the way of error checking. So think about what 
you're doing :)

Following are the steps needed to use it:

1. Download the java114.zip and unzip it into a temporary directory.

2. Modify java114.rsp. Search for all occurances of the following and 
change them to the target directory path using your favorite editor (I 
used e.exe): {SMPPATH}, {TKTPATH}, {DBGPATH}, {TDOCPATH}. These respectively 
are the paths for the samples, toolkit, debugger and toolkit documentation. 
The target directories can all be the same, ie. \Java11 or different if you 
want to split up the components, ie. {SMPPATH} => \Sample, {TKTPATH} => 
\Toolkit, and so on. These paths will be appended to the 'dstpath =' entry 
in the .cmd file. 

3. Modify the rename1.cmd file. Change the 'srcpath =', 'dstpath =' and 
'rspfile =' lines to reflect what you have on your machine. Note that 
the 'dstpath =' entry doesn't have a trailing '\'. For example, if you 
put "dstpath = 'E:'" the runtime files will end up in 'E:\Java11' and if 
you put "dstpath = 'E:\TEMP'" the runtime files will end up in 
'E:\TEMP\Java11'. The other components depend, of course, on what you
did in step 2. Be aware that files are written to 'dstpath||\OS2\DLL' and 
'dstpath||\LANGUAGE\CODEPAGE' so it's probably a good idea to use a temp
directory if your destination is your boot drive.

4. Run the RENAME1.CMD file. All the files from the PACKAGE directory will
now be copied to your destination directory structure, being renamed at the
same time.

The major drawback to this routine is that it needs a lot of disk space
since you wind up with two copies of the Java files on your disk. Also, this 
routine won't update your config.sys or install the Desktop icons which th FI
will. I found that changing all occurances of \JAVAOS2 to \Java11 in the 
config.sys worked for me. If you look through the java114.rsp file and know
what you're doing you can probably extract enough information to create the 
icons yourself. Look for lines containing 'SetupString='.

That's about it. Standard disclaimers apply. You get what you pay for.Feel 
free to modify this code in any way you want. Let me know if it proves in 
any way helpful. I can be reached at lnsmall@fast.net if you have any questions.


Len Small
11-30-97