[EMAIL PROTECTED] wrote: > > Hi Pete, > > 1. Upgrading Command: I suspect the REBOL/Command uses an umodified /Core > upgrade function (bug!). That upgrade function (because its unmodified) > does the same thing it would do if it was evaluated under /Core. It > downloads the latest /Core archive. Keep in mind that /Command is an > experimental version. To upgrade it go to > http://www.rebol.com/xpers/xpers.html and download the latest version. > > 2. Upgrading /Core: Which /Core version are you currently using? Does there > exist a newer stable version, or are you trying to upgrade from/to an > experimental version? If that is the case use the above url as well. > > 3. View: When /View is installed it attempts to write a copy of the /View > executable to the target directory. If that target directory is identical > to the directory from which you launched /View, then /View will not be able > to overwrite itself (MS Windows stops it from doing that). You must unpack > /View to a different (for instance temp) directory, and install it from > there. If launched from a different directory /View will successfully > overwrite the old version of /View it finds in the target directory. (I had > a similar problem on my Win95 machine and solved it by unpacking /View to a > different directory). > > Hope this helps. Thanks Elan - As far as the other files associated with Rebol, how do you handle storage? Either I have multiple versions of the same files in different directories, or I overwrite a script intended for use with View with one that only works in Core, etc. Maybe scripts should have command: core: and view: blocks that only get executed depending upon the version of rebol being used... I'm enjoying the book, BTW. -- Pete Wason|"LWATPLOTG"|[EMAIL PROTECTED]|[EMAIL PROTECTED]|CUCUG|TA|PHX
