> Ok thanks I got it to restart.
>
> So I just @chown each MUF program that I install to W3?
> So to load the MUF programs should I create a new room or use #0 room?

In an ideal world, you'd create a room to serve has a global environment, to
reduce access to #0. In practice, it proves problematic (often requires some
extra massaging to make it work), I would go ahead and upload programs in
#0.

> Ok I can't figure out how to install MUF programs. I followed the
> instructions on the database. I'm using TinyFugue by the way. Is there
> a better one to use? I usually use MUSHclient to connect to MUCKs.

I don't know if MUSHclient would be better or worse. I've never used
MUSHclient. To do this properly, you need a client that is capable of
dumping the contents of a file without making any changes to the file to the
mu*.

Perl programmers would likely write a perl script to do it.

> So to install MUF programs with TinyFugue the database says type:
> /quote -s '~/cmd-register for example. I did that but get this:

Hmm. An imprecise example, it turns out.

You need to replace ~/cmd-register with the path to wherever you have the
MUF programs extracted to.

e.g., if you downloaded the fmglowmuf package, and extracted them all to:
~/fmglowmuf, then you'd want:

/quote -S '~/fmglowmuf/cmd-register

On the other hand, if you are downloading individual files to a download
directory, you'll need to fill in the path to that directory.

Don't forget that on *ix, the tilde ~, in a path means the user's home
directory, the location of which varies by distribution.

Btw, if you want the very latest (possibly buggy) versions of the MUF
programs, I'd go to here:
http://glowmuck.cvs.sourceforge.net/viewvc/glowmuck/fmglowmuf/

And download them individually.