newbieQ: Where and when Rebol tries to install itself ?

On my laptop I am running Rebol/Command [ Win89se ]. %/c/rebol Before buying Command, I ran Rebol/View, then Rebol/ViewPro and have occasionally successfully run the Rebol Plugin in IE 5.5 But Rebol seems far too ready to install itself all over the place. For example, if I open a windows folder and double click on any .r file it will try to install itself in that folder. This creates havoc creating view local and public folders. I don't understand why it tries to do this. Is this 'normal', misconfigured, or perhaps symptoms of a damaged Win32 registry? If I want to create a CDROM with rebol based work, how best to structure the files and handle installation? This also raises the topic of where and how Rebol handles its cache and how to plan for that. Looking for any advice, wisdom strategies to handle these issues.. Thanks - Jason

1) Follow Rebol docs and take care of path issue. However - there is a bug to which I haven't received any confirmation. Running rebo using -i (no-install) switch doesn't prevent you from installation, if rebol doesn't find user-prefs.r and prefs.r on path you start it from. 2) I tried to use Rebol on novell for some automatition. I put into login script following line: #f:\all-users\spy!\update-ini\update-ini.bat In my .bat I put cd F:\all-users\spy!\update-ini on first line, and on second line I start rebol -is update-ini.r If I wouldn't do that, rebol would be started from f:\public directory, so it would pop-up with installation on each machine, even if -i switch would be used. 3) My aproach failed on two machines. I have some suspicion, that if you once let rebol install onto your machine, executable always first try to take your registry info. All damned registry, haven't we asked RT to don't mess with damned MS thing? ;-) Holger, maybe you could confirm, if Rebol executable looks at registry first? -pekr-