tmi2_fluffos_v2/
tmi2_fluffos_v2/bin/
tmi2_fluffos_v2/etc/
tmi2_fluffos_v2/fluffos-2.7-ds2.018/
tmi2_fluffos_v2/fluffos-2.7-ds2.018/ChangeLog.old/
tmi2_fluffos_v2/fluffos-2.7-ds2.018/Win32/
tmi2_fluffos_v2/fluffos-2.7-ds2.018/compat/
tmi2_fluffos_v2/fluffos-2.7-ds2.018/compat/simuls/
tmi2_fluffos_v2/fluffos-2.7-ds2.018/include/
tmi2_fluffos_v2/fluffos-2.7-ds2.018/testsuite/
tmi2_fluffos_v2/fluffos-2.7-ds2.018/testsuite/clone/
tmi2_fluffos_v2/fluffos-2.7-ds2.018/testsuite/command/
tmi2_fluffos_v2/fluffos-2.7-ds2.018/testsuite/data/
tmi2_fluffos_v2/fluffos-2.7-ds2.018/testsuite/etc/
tmi2_fluffos_v2/fluffos-2.7-ds2.018/testsuite/include/
tmi2_fluffos_v2/fluffos-2.7-ds2.018/testsuite/inherit/
tmi2_fluffos_v2/fluffos-2.7-ds2.018/testsuite/inherit/master/
tmi2_fluffos_v2/fluffos-2.7-ds2.018/testsuite/log/
tmi2_fluffos_v2/fluffos-2.7-ds2.018/testsuite/single/
tmi2_fluffos_v2/fluffos-2.7-ds2.018/testsuite/single/tests/compiler/
tmi2_fluffos_v2/fluffos-2.7-ds2.018/testsuite/single/tests/efuns/
tmi2_fluffos_v2/fluffos-2.7-ds2.018/testsuite/single/tests/operators/
tmi2_fluffos_v2/fluffos-2.7-ds2.018/testsuite/u/
tmi2_fluffos_v2/fluffos-2.7-ds2.018/tmp/
tmi2_fluffos_v2/fluffos-2.7-ds2.018/windows/
tmi2_fluffos_v2/lib/
tmi2_fluffos_v2/lib/adm/
tmi2_fluffos_v2/lib/adm/daemons/languages/
tmi2_fluffos_v2/lib/adm/daemons/network/I3/
tmi2_fluffos_v2/lib/adm/daemons/virtual/
tmi2_fluffos_v2/lib/adm/daemons/virtual/template/
tmi2_fluffos_v2/lib/adm/news/
tmi2_fluffos_v2/lib/adm/obj/
tmi2_fluffos_v2/lib/adm/obj/master/
tmi2_fluffos_v2/lib/adm/priv/
tmi2_fluffos_v2/lib/adm/shell/
tmi2_fluffos_v2/lib/adm/tmp/
tmi2_fluffos_v2/lib/cmds/
tmi2_fluffos_v2/lib/d/
tmi2_fluffos_v2/lib/d/Conf/
tmi2_fluffos_v2/lib/d/Conf/adm/
tmi2_fluffos_v2/lib/d/Conf/boards/
tmi2_fluffos_v2/lib/d/Conf/cmds/
tmi2_fluffos_v2/lib/d/Conf/data/
tmi2_fluffos_v2/lib/d/Conf/logs/
tmi2_fluffos_v2/lib/d/Conf/obj/
tmi2_fluffos_v2/lib/d/Conf/text/help/
tmi2_fluffos_v2/lib/d/Fooland/adm/
tmi2_fluffos_v2/lib/d/Fooland/data/
tmi2_fluffos_v2/lib/d/Fooland/data/attic/
tmi2_fluffos_v2/lib/d/Fooland/items/
tmi2_fluffos_v2/lib/d/TMI/
tmi2_fluffos_v2/lib/d/TMI/adm/
tmi2_fluffos_v2/lib/d/TMI/boards/
tmi2_fluffos_v2/lib/d/TMI/data/
tmi2_fluffos_v2/lib/d/TMI/rooms/
tmi2_fluffos_v2/lib/d/grid/
tmi2_fluffos_v2/lib/d/grid/adm/
tmi2_fluffos_v2/lib/d/grid/data/
tmi2_fluffos_v2/lib/d/std/
tmi2_fluffos_v2/lib/d/std/adm/
tmi2_fluffos_v2/lib/data/adm/
tmi2_fluffos_v2/lib/data/adm/daemons/
tmi2_fluffos_v2/lib/data/adm/daemons/doc_d/
tmi2_fluffos_v2/lib/data/adm/daemons/emoted/
tmi2_fluffos_v2/lib/data/adm/daemons/network/http/
tmi2_fluffos_v2/lib/data/adm/daemons/network/services/mail_q/
tmi2_fluffos_v2/lib/data/adm/daemons/network/smtp/
tmi2_fluffos_v2/lib/data/adm/daemons/news/archives/
tmi2_fluffos_v2/lib/data/attic/connection/
tmi2_fluffos_v2/lib/data/attic/user/
tmi2_fluffos_v2/lib/data/std/connection/b/
tmi2_fluffos_v2/lib/data/std/connection/l/
tmi2_fluffos_v2/lib/data/std/user/a/
tmi2_fluffos_v2/lib/data/std/user/b/
tmi2_fluffos_v2/lib/data/std/user/d/
tmi2_fluffos_v2/lib/data/std/user/f/
tmi2_fluffos_v2/lib/data/std/user/l/
tmi2_fluffos_v2/lib/data/std/user/x/
tmi2_fluffos_v2/lib/data/u/d/dm/working/doc_d/
tmi2_fluffos_v2/lib/data/u/l/leto/doc_d/
tmi2_fluffos_v2/lib/data/u/l/leto/smtp/
tmi2_fluffos_v2/lib/doc/
tmi2_fluffos_v2/lib/doc/driverdoc/applies/
tmi2_fluffos_v2/lib/doc/driverdoc/applies/interactive/
tmi2_fluffos_v2/lib/doc/driverdoc/concepts/
tmi2_fluffos_v2/lib/doc/driverdoc/driver/
tmi2_fluffos_v2/lib/doc/driverdoc/efuns/arrays/
tmi2_fluffos_v2/lib/doc/driverdoc/efuns/buffers/
tmi2_fluffos_v2/lib/doc/driverdoc/efuns/compile/
tmi2_fluffos_v2/lib/doc/driverdoc/efuns/ed/
tmi2_fluffos_v2/lib/doc/driverdoc/efuns/filesystem/
tmi2_fluffos_v2/lib/doc/driverdoc/efuns/floats/
tmi2_fluffos_v2/lib/doc/driverdoc/efuns/functions/
tmi2_fluffos_v2/lib/doc/driverdoc/efuns/general/
tmi2_fluffos_v2/lib/doc/driverdoc/efuns/mappings/
tmi2_fluffos_v2/lib/doc/driverdoc/efuns/numbers/
tmi2_fluffos_v2/lib/doc/driverdoc/efuns/parsing/
tmi2_fluffos_v2/lib/doc/driverdoc/lpc/constructs/
tmi2_fluffos_v2/lib/doc/driverdoc/lpc/preprocessor/
tmi2_fluffos_v2/lib/doc/driverdoc/lpc/types/
tmi2_fluffos_v2/lib/doc/driverdoc/platforms/
tmi2_fluffos_v2/lib/doc/mudlib/
tmi2_fluffos_v2/lib/ftp/
tmi2_fluffos_v2/lib/include/driver/
tmi2_fluffos_v2/lib/log/
tmi2_fluffos_v2/lib/log/driver/
tmi2_fluffos_v2/lib/obj/net/
tmi2_fluffos_v2/lib/obj/shells/
tmi2_fluffos_v2/lib/obj/tools/
tmi2_fluffos_v2/lib/std/adt/
tmi2_fluffos_v2/lib/std/board/
tmi2_fluffos_v2/lib/std/body/
tmi2_fluffos_v2/lib/std/fun/
tmi2_fluffos_v2/lib/std/living/
tmi2_fluffos_v2/lib/std/object/
tmi2_fluffos_v2/lib/std/shop/
tmi2_fluffos_v2/lib/std/socket/
tmi2_fluffos_v2/lib/std/user/
tmi2_fluffos_v2/lib/std/virtual/
tmi2_fluffos_v2/lib/student/
tmi2_fluffos_v2/lib/student/kalypso/
tmi2_fluffos_v2/lib/student/kalypso/armor/
tmi2_fluffos_v2/lib/student/kalypso/rooms/
tmi2_fluffos_v2/lib/student/kalypso/weapons/
tmi2_fluffos_v2/lib/u/l/leto/
tmi2_fluffos_v2/lib/u/l/leto/cmds/
tmi2_fluffos_v2/lib/www/errors/
tmi2_fluffos_v2/lib/www/gateways/
tmi2_fluffos_v2/lib/www/images/
tmi2_fluffos_v2/old/
tmi2_fluffos_v2/win32/
#d/Fooland/mainboard.c
ob_data (["last_location":0,"silent_look":1,"id":({"board","bulletin board",}),"long.text":"This is a bulletin board. For information on how to use it, use `help board'.
","short":"@@query_short","short.text":"General purpose bulletin board","long":"@@query_long",])
messages ({(["poster":"Armando","time":810257067,"title":"Re: tmi-2","body":"
I think that a lot of people used tmi-2 as a starting place to
find more information about lp-muds. So it should stay up in the
air. There is nothing else like tmi-2 out there.

Ah well, I hope things will work out. I'll go to bed and dream about
a happy world. 

Armando (Edwin)
","id":4,]),(["poster":"Leto","time":810604158,"body":"Seems my linux binary isn't that stable ;)
I'll recompile the driver tomorrow.

Paul
","title":"crashes ;)","id":5,]),(["poster":"Mobydick","time":811182706,"title":"release?","body":"Do we have a target date for a 1.3 release? What needs to be done
before that release can be made?

Moby
","id":6,]),(["poster":"Abigail","time":811219192,"body":"No driver boards, no mudlib boards, no politic board, nothing at all?
Then this mud should not be called TMI-2.

Abigail
","title":"Hmmm.","id":7,]),(["poster":"Tigycho","time":811247679,"title":"I3","body":"Was just wondering if anyone has plans to do something with I3 such
that TMI-lib 1.3 would support I3 and the old DNS behaviour...

Somehting like defaulting to I3 (since its a better protocol), but allowing
you to gwiz -dns message, so that you can still reach muds on the old 
network?  

Or am I silly?
Tigycho
","id":8,]),(["poster":"Leto","time":811250092,"body":"Moby: What needs to be done is /doc should be added, and the new
I3 should be documented. Also, I3 should prob be brought up to
date a bit (What changed the last 2 months?), and it should be
checked on security. The new WWW daemon should be tested for
large binary transfers.
I think that's it.

Abigail: I renamed it after a day to Team-Aye :)
Tigycho: I am prob speaking for all of Tmi-2's admins/board members
if I say that Tmi-2 will NOT support I2 or I1 anymore. It's
a waste of bandwidth and would only prevent people upgrading
to I3. If a mud doesn't have the knowledge to upgrade to I3
with the files that are in here, I seriously wonder what they're
capable of.

Paul

Ps. Oh Moby, intermud channels and the channel daemon needs to
be integrated as well :)
There are more things that would be nice, but not essential.
","title":"Re:moby,abi and tig","id":9,]),(["poster":"Leto","time":811551947,"title":"Re: Re:moby,abi and tig","body":"
Oh,

I am also making Tmi-2 AMCP Compliant, and I will add
an /obj/shells/amcp.c shell.
This will allow it to talk to amcp clients, of which
I'm developing one right now.

(more info see: http://www.imaginary.com/~beek/amcp)

Leto
","id":10,]),(["poster":"Leto","time":811966050,"body":"I've been working on some more fixes at home. Is there anyone
interested in helping me  ? :)

Leto
","title":"Fixes","id":11,]),(["poster":"Shakespeare","time":812259071,"title":"Leto :)","body":"   All the bogus whining about whether someone can call the mud TMI-2
seems to be part and parcel of why the project has been in such
chaos.
 
   You would think TMI was the federal government with all the 
committees, name calling, and growlings over people feeling their 
territory is being infringed upon.
 
   In my opinion, one of the best things about the TMI-2 mud was the
fact that it served as a clearinghouse of information. People knew that
it was one of the main places to go to get info, or assistance on any variety
of mudlibs or drivers.
 
   I know the main goal of the mud was theoretically the development and
further enhancement of the TMI mudlib. However, this helpful aspect that
seemed to develop by accident there should not be ignored and/or discarded.

   Anyway, I applaud Leto for bringing this site up in an attempt to make
steps forward. I don't think criticisms for calling it this name or that
are justified. He seems to have done the best he could, and the renaming
is an obvious attempt to avoid any conflict.
 
   Well, thanks again Leto. If you can, could you throw a few more
boards around. I miss em :)
 
-Shakespeare
","id":12,]),(["poster":"Eyes","time":813978910,"body":"What is the purpose of this place?

-Eyes
orion.tyler.net 6666
","title":"purpse","id":13,]),(["poster":"Leto","time":814015933,"body":"On Wed Oct 18, Eyes wrote:
> What is the purpose of this place?
> 
> -Eyes
> orion.tyler.net 6666

The purpose was to keep the Tmi-2 people together, and maybe even
start developing something again :)
But it seems people lost interest completely.
So, basically, it's here so i can answer Tmi-2 questions for people :)

Leto
","title":"Re: purpse","id":14,]),(["poster":"Winddle","time":814042028,"body":"Perhaps if this place were to have a higher profile, 
(like telling people its here ;-) ) It may be possible to
rekindle some enthusiasm in the TMI-2 lib etc.

Its worth a try ;-) 

Winddle
","title":"RE: purpose","id":15,]),(["poster":"Eyes","time":814051286,"body":"Yeah darkpowers mud is running on tmi 1.1( lib and a on mudos 0.9.19.


We are trying to upgrade to v21 and we need big help!!! 
Our combat system, clan warfare, monsters, weapons, and everything
is extremely extensive. Please drop by at orion.tyler.net 6666
Mudmail eyes when you get there if you want to help.

Oh leto, btw when i was compiling v21 i got this error:

(cd packages; gmake)
	~orion: gmake : command not found

I have checked /src/packages/ but no gmake.  I tried everything, grepped for
gmake and such but to no avail.  Help!!!

ps: Mebbe we can make tmi-2 next project to be converting dp? :)
","title":"of course","id":16,]),(["poster":"Leto","time":814229112,"title":"Re: of course","body":"On Wed Oct 18, Eyes wrote:
> 
> We are trying to upgrade to v21 and we need big help!!! 
> Our combat system, clan warfare, monsters, weapons, and everything
> is extremely extensive. Please drop by at orion.tyler.net 6666
> Mudmail eyes when you get there if you want to help.

Upgrading is not too bad. It's basically only an error or
6, but they tend to come back a lot, so you'll be fixing it
a few dozen times at least :)

> Oh leto, btw when i was compiling v21 i got this error:
> 
> (cd packages; gmake)
> 	~orion: gmake : command not found

Some versions of gmake don't work properly. cd into the package
directory itself and type 'gmake', then cd back one dir, and do
a 'gmake' to continue.

For the most occuring errors you can check the fixes that were made here.

Leto
","id":17,]),(["poster":"Eyes","time":814387687,"body":"Ok
Ok i even got a new v21c2, yet the gmake problem is recurring.
I tried everything.. even in the Makefile it says please
define what type of make do you use: and i put in 'make' instead
of gmake.  I even grep the files.. but still unable to find out
what the problem is!!

Eyes.
","title":"gmake problems.. arggh","id":18,]),(["poster":"Leto","time":814405028,"title":"Re: gmake problems.. arggh","body":"On Sun Oct 22, Eyes wrote:
> Ok
> Ok i even got a new v21c2, yet the gmake problem is recurring.
> I tried everything.. even in the Makefile it says please
> define what type of make do you use: and i put in 'make' instead
> of gmake.  I even grep the files.. but still unable to find out
> what the problem is!!
> 
> Eyes.

The build.mudos script checks your system and creates configure.h and
the Makefiles/GNUmakefiles.
If you got a tarred up copy which has already been used, remove the
configure.h file. It probably contains which make you have.
If you start from a really clean distribution, it should build until it
might fail with the packages subdirs. Then manually cd into them
and type either gmake or make (Whatever you spotted mudos using in the
previous make that just failed).
When it's done, cd .. and type make/gmake again to continue. If that
fails, ask Beek at Idea Exchange :)

Leto
","id":19,]),(["poster":"Eyes","time":814412577,"body":"What is the address for the idea sexchange?

Eyes.
","title":"er idea sexchange","id":20,]),(["poster":"Beek","time":814429914,"title":"Re: Eyes","body":"IdeaExchange is at: imaginary.com 7890

-Beek
","id":22,]),})
id_ref 32