As I have seen some problems with using Java and keeping plugins I decided to put a couple of scripts I have been using to make it easier for those that may decide to use them or modify them to their liking. The first is my launch script launched from c:\programs\warpzilla (my structure): SET MOZILLA_HOME=c:\programs\warpzilla\bin SET PATH=c:\JAVA13\JRE\BIN;%PATH% SET BEGINLIBPATH=c:\JAVA13\JRE\BIN;c:\JAVA13\JRE\DLL SET CLASSPATH= set java_home=c:\java13\jre cd bin start mozilla.exe exit
I have a shadow of this file on my warpcenter. The next file is a script I use to remove my bin directory (as seen above this is where my profiles are so they get zapped in this configuration, if you don't want this you will have to modify the scripts) and then recreate it, unzip the lizard, and then copy the plugins back in. I keep the plugins in a directory under warpzilla. call tg bin (tg is treegone available on hobbes, susbstitute your favorite directory deletion program) md bin cd bin unzip ..\mozilla-os2.zip (this of course requires always saving to the warpzilla directory with the same name, I myself save them with the date and then create a copy with this name) cd.. copy plugins bin\plugins (moves the plugins over) copy moveover bin (this has a copy of warpzilla.cmd above and a mozilla.ico and warpzilla.ico none of which are necessary but wanted to be able to launch the warpzilla.cmd from this directory as well as from warpzilla though I rarely do this) warpzilla (this is optional, I launch it so the profiles are built) Because the warpzilla.cmd and warpzilla.ico are in the warpzilla dircetory up one level from bin they are never deleted thus the shadows are not deleted so I don't have to recreate them. Many people I am sure already have their own methods worked out but I see the occasional question on these things and hopefully this will make it easier for them. Andy
