On 2 Nov 1999, King Guppy wrote:
> problems; admittedly this was not made clear enough in the installer.
> I'm trying to make a more general observation (rant?), which springs
> from my having to trawl through dozens of useless emails each
> day.
Wow thats a lot of text to add :) I added most of your text...
I also added to the installer a few checks. After I 'update' the vapor
libs to libs: ... I check all 4 libs in libs: and that are resident. If
any of the 4 libs are not = (in libs: and resident) I show the user what
versions are in libs: and are resident. Then show the "please reboot"
info.
Added a check for "ENV:Vapor/CManager_path"+'Default.data' .. if this file
is not there tell the user to reinstall the cmanager package..or if they
did install the cmanager package, but to ram:, they need to reinstall.. so
that the book marks are stored on the HD.. and can live through a reboot.
Also added a check to see if the CManager.key (if using it) is a 'current'
one. If not tell the user that they need to upgrade because an old key
with newer CManager classes/libs can fail thus causing V to fail.
Anything else I missed? :)
Robert
____________________________________________________________
Voyager Mailing List - Info & Archive: http://www.vapor.com/
For Listserver Help: <[EMAIL PROTECTED]>, "HELP"
To Unsubscribe: <[EMAIL PROTECTED]>, "UNSUBSCRIBE"
