LPMUD PARSE 3.1.2-MSDOS - Version 1.2 ------------------------------------- This file is an exact copy of the file readme.1st found inside the ok312exe.exe archive. The idea is that you read at least to Chapter 4. before attempting to extract these archives, thus saving you time and space in case you don't need both archives. Archive name : ok312exe.exe All the files EXCEPT the mudlib. ok312lib.exe A 2.4.5 mudlib. Type : Self extracting LHA archives. Contains : EVERYTHING YOU NEED TO RUN LPmud ON YOUR 386/486 BOX!!!! LPmud parser version 3.1.2 for MSDOS both COMPAT_MODE (for mudlib 2.4.5 or older) and non-COMPAT_MODE (for mudlib 3.0 or newer) A virgin 2.4.5 MUDLIB, already converted to MSDOS. No parser source! Needs : 386sx or better.(Just forget it if you've only got a 286 or less) From 1.8Mb to 3Mb, depending on the low level setup of your hard disk, for the files alone. In addition to this comes the disk space LPmud uses to swap objects out to disk, no idea how much that is, but the more space the better. Introduction ------------ RIGHT! This is it! A complete, up to date(!), LPmud for MSDOS! As some of you might know, John Olson uploaded a complete package to foof a few days ago. This was version 3.0.45 (!) though. Booo, hisss!!!! OLD!!! ANCIENT!!! :-) I take NO (You read it, NO!) responsiblity for whatever might happen when you try to follow these instructions. This archive is provided free of charge. No warranties whatsoever... I tried earlier to just give out the updated parses (3.1.2.) but that turned out to be a semi-disaster... I had tons (well, Kbytes) of E-Mail from people wanting a complete LPmud package for MSDOS and how they should go about getting one. To add insult to injury, I had forgot to include a vital file, causing the parses to be unusable... (Sorry about that... $#%@#% GCC... ;-) So this time, I'm going for the full whack, everything you ever wanted to know about LPmud under MSDOS. (Well, almost..) Table of Contents ================= Chapter 1. What these archives contains. 2. What hardware you need. 3. What software you need. 4. What to do with these archives. 5. What to put in your autoexec.bat/config.sys (and what to remove). (Or, how to get this beast working...) 6. Odds and ends. Appendix A. What to do when something goes wrong, and why. (This usually amounts to running around in circles screaming...) B. Where to go for extra goodies. C. List of (most of the) files in these archives. D. Caveat & Revision history. ******************************************************************************* * 1. What these archives contains. * ******************************************************************************* Basically, everything you need. What it doesn't contain is the SOURCE for the parsers. IF you need them there are plenty of places to get them... It is split into two files, ok312exe.exe and ok312lib.exe. This is to accommodate(sp?) the people that already have either a mudlib and/or an older version of the parser already. ok312exe.exe ------------ This is all the files you need EXCEPT a MUDLIB. Contains the following directories: bin The executables (i.e. the parsers and the extra exes). config Dunno of this is needed or not... Only 45K anyway. doc The docs for setting up and running LPmud. READ THEM!!! drivers Video-drivers used by the parsers. Note that the above is all you need for a full UPGRADE from a previous version of LPmud for DOS. Just read Chapter 4. if you know what you're doing and just want the new parsers.... Note the go32.exe ! ok312lib.exe ------------ This is a 2.4.5 MUDLIB converted to MSDOS. Contains the following directory: mudlib This is a complete, converted 2.4.5 mudlib for MSDOS. Ready to roll... ****************************************************************************** * 2. What hardware you need. * ****************************************************************************** LPmud is not too bad when it comes to hardware requirements. The following is a must: A 386sx or better, i.e. 8088, 8086, 286 are NO GOOD here. A hard disk with at least 3 Meg free. The more the better!!! A VGA card (I think) or better. When it comes to RAM I have no idea at all what it needs. 1 Meg should be sufficient. I've got 8 Meg so I can't check if 1 Meg will work. Things you DON'T need: A maths coprocessor, we use an emulator instead. NOTE that you have to use the emulator that comes with this package, none other will work! ****************************************************************************** * 3. What software you need. * ****************************************************************************** A fairly recent version of DOS. Version 3.1 or newer I think it is. That's about it, the rest is included in these archives. ****************************************************************************** * 4. What to do with these archives. * ****************************************************************************** First of all, the archives have to be extracted. This is where there is a certain scope for misunderstandings. The two files (ok312exe.exe & ok312lib.exe) are ALL you need to run LPmud on your 386/486 box. Users typically fall into one of three categories here: 1) Have got a running LPmud complete with MUDLIB already, just wants the updated parsers. Have a certain knowledge about how things work. Typically done some work on a castle, possibly modified the MUDLIB as well. 2) Have got an old/new version of the LPmud parser, but possibly no MUDLIB. Couldn't get it to run properly. Gave up. 3) Totally green. Haven't got anything working at all, need to be told step by step what to do to set it up. Below are separate instructions for each of the above. Chose the one that fits your description and read the explanation for that. Category 1 ---------- What you need to upgrade to 3.1.2. from an older version of the parser is just a few files. Execute the file ok312exe.exe in a temp-directory somewhere and dig out the bits you need. Hints: bin\pars312c.exe 3.1.2 parser in COMPAT_MODE. (2.4.5 mudlib ) bin\pars312.exe 3.1.2 parser in non-COMPAT_MODE (3.* mudlib ) bin\master.c New master.c (put in mudlib\obj or mudlib\secure depending on type of MUDLIB) bin\simul_efun.c Same as for master.c. bin\go32.exe Needed to run the most of the new exes, including the new parses. Put it somewhere in your path (eg. \lpmud\bin) The rest is mostly the same as before. If you had something running before all you should have to do is insert the 5 files above and play away. Category 2 ---------- Scrap the lpmud stuff you have gathered so far (Just save any work you have done on a castle or similar) Everything you need is included in the files in these two archives. Make backups of anything you have done yourself!!! Read Category 3. Category 3 ---------- Right... Here we go. This is just to install the two archives. We don't start to fiddle with the autoexec.bat or config.sys until Chapter 5. This is a good place to take a backup of any information you don't want to loose. So you can't blame me if something blows up... People seem to like getting numbered instructions : 1. Find a hard disk that has more than 3 Meg free, alternatively MAKE SPACE :-) 2. Create the directory \lpmud I.e. go to your top directory and type mkdir lpmud This new directory should be empty. 3. Move/copy the two files, ok312exe.exe and ok312lib.exe into this new directory. 4. Go into the \lpmud directory. 5. Execute the two files mentioned above. They are self extracting archives and will create a lot of new files and subdirectories. 6. If nothing has gone wrong so far, i.e. no 'disk full' errors or anything you can delete the two files : ok312exe.exe and ok312lib.exe. Make sure you have backups though, in case you screw up later... :-) 7. BROWSE! Have a look around and familiarise yourself with the directories. The most important at the moment is the \lpmud\doc directory. There you can find information about most things, some relevant and some becoming relevant later. 8. This concludes the extraction. Relax, have a Coca Cola. Now comes the tough part... ****************************************************************************** * 5. What to put in your autoexec.bat/config.sys (and what to remove). * ****************************************************************************** First of all, for the newbies and also the rest of you. Create a system boot disk so that you can boot your machine in the case you screw up the autoexec.bat or config.sys. If you don't know how to do this I suggest you read a good DOS book before going any further. Now, back up your autoexec.bat and config.sys. ! The following is a simplification of what actually goes on, but it's ! hopefully not too incorrect and should serve as an explanation for all the ! strange stuff you have to do to your autoexec.bat and config.sys. Anything compiled with DJ's GCC (a C compiler) for MSDOS must obey certain rules. All the programs you got with this archive was compiled with GCC. That means you have to do certain things to your autoexec.bat and config.sys. Read the file \lpmud\doc\copying for a note of what this does to the copyright of the program... As some of you might know, the 386 family of CPUs can EMULATE several 8086s by going into a certain CPU state. Some programs use this state to control the behaviour of other programs. Prime examples are DeskView and Windows. They place the CPU into this special mode so they can control, potentially several, other programs. This trick is also used by most MEMORY MANAGERS like emm386, QEMM, 386MAX and others. So when you run ANY of the above programs, they 'take over' the CPU and only lets you have small parts of it. This is what programs compiled with DJ's GCC complain about. They need the FULL CPU, not just a 8086 emulation. So the programs mentioned above are OUT, can't run them if you want to run LPmud. LPmud will complain if there is such a program running and will print out the following statement before exiting: CPU must be in REAL mode (not V86 mode) to run this program With that background, we should be ready to modify our startup files. Comments on a few DOS programs : SMARTDRV.EXE & SMARTDRV.SYS : I've also heard that the smartdrv is not such a good idea to use. Stay away from disk cache programs in general. SHARE.EXE : It's a MUST, whether it goes in your config.sys, autoexec.bat or you just run it before you start LPmud. MEMORY MANAGERS : No go, remove them from your startup files. This includes emm386, QEMM, 386MAX, Windows, DeskView and others. HIMEM : This works fine for me under DOS 5.0, both DOS high and UMB's no problems at all. autoexec.bat ============ The autoexec.bat should at least contain the following. The paths should remain as they are, but you can change the drive-letters to whatever suits your system best. (You can of course change the paths that doesn't have 'lpmud' in them): PATH c:\;c:\dos;d:\lpmud\bin set GO32TMP=d:/tmp set GO32=emu d:/lpmud/bin/emu387 driver d:/lpmud/drivers/tseng4k.grd gw 1024 gh 768 set SERIAL=d:/lpmud/lines set HOME=d:/ Note the following about the statements above: 1. The PATH should of course be set up to reflect where you have the files you need. Just add wherever you decided to put \lpmud\bin to it. 2. GO32TMP as to point to a valid directory! If you have already got a temp-directory set it to that, otherwise create one! This is the directory LPmud will use to swap objects onto disk to save memory. 3. GO32 requires some explanation, and can be split in two parts: emu d:/lpmud/bin/emu387 This is the maths coprocessor emulation. driver d:/lpmud/drivers/tseng4k gw 1024 gh 768 This is the graphics driver, and must be changed to whatever you have. The different drivers can be found under d:/lpmud/drivers vga.grd is probably a good choice if you are using a vanilla vga board. The gw and gh is default graphics width/height. I'm not totally sure if this driver-part is actually needed or not. Experiment... The segment below is an extract from a document explaining the use of the GO32 variable. Some people might find it useful. The full document is included as \lpmud\drivers\readme.jo ************************ EXTRACT START ************************************ The GO32 environment variable: This variable controls the options available in go32 or debug32. The syntax of this variable is: SET GO32=[parm [value]] [parm [value]] . . . Parameters: ansi Use ANSI commands to control the color in debug32 mono Use the Monochrome monitor for debugging - useful when debugging graphics applications 1rm Redirect stdout (file #1) to the monochrome monitor 2rm Redirect stderr (file #2) to the monochrome monitor 1r2 Redirect stdout (file #1) to stderr (file #2) 2r1 Redirect stderr (file #2) to stdout (file #1) emu [path] Use the specified file as the 80387 emulator driver [path] Use the specified file as the graphics driver gw [width] Default graphics width gh [height] Default graphics height tw [width] Default text width th [height] Default text height These parameters may occur in any order. Note that "1rm" and "2rm" are done before "1r2" and "2r1", so "1rm 2r1" sends stdout to the mono monitor and stderr to any redirection used. Examples: C:\> set GO32=mono driver c:\djgpp\drivers\tseng4k.grd gw 1024 gh 768 tw 132 th 43 C:\> set GO32=ansi C:\> set GO32=driver c:\djgpp\drivers\tseng4k.grd ansi C:\> set GO32=mono 1rm 2rm * The paging mechanism understands how SuperVGA's map their memory onto the AT bus and automatically swaps pages as the program tries to access them. The program sees a linear range from 0xD0000000 to 0xD0100000 that corresponds to each pixel in the 256-color modes of SuperVGAs. To use this feature, you'll have to set the GO32 environment variable like this: C>set go32=driver c:\djgpp\drivers\tseng4k.grd gw 640 gh 480 tw 132 th 43 These parameter pairs can be omitted or rearranged as needed. They are the "driver" name, default graphics width and height, and default text width and height. Libgr.a doesn't have to be recompiled, nor do graphics programs, when a different graphics mode is selected (the extender handles it). It is strongly recommended that the program use the GR_default_graphics and GR_default_text modes to switch to graphics or text. These modes use the parameters specified by the GO32 environment variable, allowing the user to select a favorite graphics and text mode. ******************************* EXTRACT END ******************************** 4. SERIAL is a variable that points to a file where LPmud can find default variables for serial line use. You can connect to LPmud using the serial port as well as the keyboard itself. Even though you don't intend to use this feature, this variable has to point to a (potentially empty) file. Here is the HELP screen in the comdrv.com program: Usage is COMDRV [-C n] [-E n] [-I n] [-M] [-N n] [-O n] [-P n] -C n use COM port n (1<=n<=4). Default is 1 -E n enable line editing in a buffer of n characters -I n set input buffer size to 2^n bytes (4<=n<=15). Default is 4096 (2^12) -M monitor all COM ports (ignores all other options) -N n use interrupt number n (0<=n<=15). Defaults are 4,3,4,3 -O n set output buff. size to 2^n bytes (4<=n<=15). Default is 4096 (2^12) -P n use port base n (0<=n<=FFFE). Defaults are 3F8,2F8,2E8,2E0 Here is John Olson's explanation of the SERIAL stuff: ************************** SERIAL EXPLANATION START *********************** If you plan to support connections over serial lines, you have to load a communications driver for each port. The following command loads a driver for COM2 with local line editing (79 characters buffer) enabled: \LPMUD\BIN\COMDRV -C2 -E79 In addition to that, \LPMUD\LINES has to be edited to reflect the configu- ration, e.g.: # line bps carrier 1 2400 y 2 38400 n \LPMUD\LINES has to be present and the environment variable SERIAL has to point to it even if no serial lines support is desired. Lines can be commented out by prefixing them with a '#'. + + I'm not currently using the serial facilities, so my \lpmud\lines file + has only got the line '# This is a file' in it, nothing more. There + are three files included in this archive you can look at: + \lpmud\lines, \lpmud\lines2 and \lpmud.ser + Choose the one that suits your needs. + -OK **************************** SERIAL EXPLANATION END *********************** 5. The HOME variable. If you are planning to use indent.exe (I've never used it...) then this variable should point to the directory in which the file indent.pro resides. I haven't got this file, nor have I seen it. I assume it's some sort of template for how the indent program should indent your C file... If you don't intend to use the indent program (i.e. since you technically can't :-) just set this variable to point to a VALID directory. That concludes the things you SHOULD have in your autoexec.bat. Whatever more you put into it is your choice. config.sys ========== BUFFERS=30 STACKS=0,0 FILES=40 SHELL=C:\DOS\COMMAND.COM C:\DOS\ /e:1024 /p INSTALL=C:\DOS\SHARE.EXE Some notes on the lines above: 1. Buffers, stacks and files: Doesn't really matter how much you set these to. (I would assume that LPmud use a few open files at the same time though, so a good, high number on buffers and files might be a good idea.) 2. The shell variable has to be set (I think :-). The above line is what I have it set to, your own might be different. Just make sure it's set. 3. The SHARE line should go in somewhere. You can just as easily just start it somewhere else. 4. If you decide to use the 'ansi' option in the GO32 variable (see above) then remember to start up ANSI.SYS as well! I.e. put DEVICE=C:\DOS\ANSI.SYS in your config.sys. 5. Again you can include any other elements in the config.sys you might need, such as device drivers for disks, harddisks, videocards etc etc That should conclude the changes you have to do to your setup files. We're almost ready to roll now... The following are two batch-files I wrote to start up LPmud. You might want to copy them into a directory in your path. lpmud.bat --------- d: d:\lpmud\bin\pars312c >>\lpmud\log lpmud3.bat ---------- d: d:\lpmud\bin\pars312 >>\lpmud\log You might not need the last one, since that requires that you have a 3.* MUDLIB. You are most likely to have a 2.4.5, since that is what comes with this archive... Of course, if you have installed LPmud on another drive, change the drive- letter in the above batch-files. That should be you up and running LPmud 3.1.2. MSDOS version 1.2. Now reboot to make the changes you have made to the autoexec.bat and config.sys take place and type lpmud If you're lucky and everything has gone according to plan, you should see the following line appear after the batch file has been executed and the direcory change has taken place (Inside the batch file): Parse 3.1.2.-MSDOS (COMPAT_MODE) compiled by Aragorn@NANVAENT 29/3-92 o If something else happens then you (or I) have made a mistake somewhere. See Appendix A for troubleshooting. o If that's what you see take two seconds to run around your chair and scream YYYYYYYYYEEEEEEEEESSSSSSSSSSSSSS!!!!!!!!!!!!! Now, after around 5-10 seconds (The parser has to load /obj/armour /obj/weapon and all those...) you should see a reversed line at the botton of the screen saying #1 [AVAILABLE] Hit RETURN, and the text will change to #1 [CONNECTED] A few seconds after that (It now loads /obj/player) the login screen should appear, looking something like this: Welcome to (LPmud 2.4.5). Administrator and supreme ruler : Version : 03.01.02 What is your name : Log in as user 'aragorn', with no password. This is a level 1000 user, but hasn't got a workroom or anything. If you have come so far, it's time to run around that chair again... Now, there are a few special keys you can use: F1 ... F10 switch to the respective console You can have up to 10 people logged in on the console at the same time, swapping between them by pressing a Function key from 1 to 10. Alt-H ("hangup") disconnects the currently active console Alt-S suspends LPmud and spawns a DOS shell. EXIT returns to LPmud. If you haven't got a TSR editor (get one) or are very keen on programming in 'ed' then this is the command you will use a lot when you're editing. The game is shut down with the shutdown command which can be issued by any wizard. The people command shows the connection type in the "IP address": 0.0.0.100 to 0.0.0.109 are virtual consoles (I.e. F1 - F10) 0.0.0.110 to 0.0.0.113 are COM1 ... COM4 THAT'S ALL, FOLKS! ****************************************************************************** * Chapter 6. Odds and ends * ****************************************************************************** As you are well aware of, DOS is rather restricted when it comes to filenames, especially compared to UNIX. This means that some filenames that are written UNIX-style, e.g. this.is.a.file, has to be converted to DOS format. The standard 2.4.5. mudlib contains a lot of these conversions. E.g. mount_top2.c has become mnt_top2.c under DOS This shouldn't inhibit you much, but remember to check if the two filenames are the same in UNIX and in DOS when you are transferring castles to and from your PC to a UNIX box. Typically this should only be necessary for the destination of your castle.c and other object you load outside your castle. ****************************************************************************** * Appendix A. What to do when something goes wrong, and why. * ****************************************************************************** Common problems: Q: Nothing happens when I start the parser! A: The file go32.exe must be somewhere in your path for things to happen. It can be found in \lpmud\bin, and since this directory should be in your path already this problem shouldn't occur if you don't move it. Q: It just comes up with: CPU must be in REAL mode (not V86 mode) to run this program A: You are running a program that puts the CPU in the wrong mode. This can be programs like Memory Managers, Windows, DesqView etc etc Remove these from memory (alternatively remove them from your startup files (autoexec.bat & config.sys)) and try again. Q: It just comes up with Cannot find SERIAL (or something similar) A: There are a number of DOS variables that has to be set, see Chapter 5. Q: It just comes up with No 387 detected! (Or something similar) A: Again, several DOS variables have to be set. The GO32 variable handles 387 emulation, see Chapter 5. Any more common questions??? ****************************************************************************** * Appendix B. Where to go for extra goodies. * ****************************************************************************** There are numerous sites where you can get LPmud specific stuff. Castles, parsers, mudlibs etc etc Here is a list of the most prominent ones, please mail me if you think you know of any that are not on this list but deserve to be. * foof... IP = Dedicated MUD site, check out /MsdosMUD/lp for MSDOS specific LPmud things. * alcazar.cd.chalmers.se IP = THE site... (Hi Lars! :-) I know this is rather weak at the moment, but I'm typing this at home and haven't got my lists here. Will be expanded in the next version (If you send me some info... :-) ****************************************************************************** * Appendix C. List of (most of the) files in these archives. * ****************************************************************************** ok312exe.exe ------------ \lpmud\bin\emu387 : The maths coprocessor emulator \lpmud\bin\comdrv.com : The Serial port driver \lpmud\bin\fundesc.exe : Semi useless program... \lpmud\bin\indent.exe : Semi useless program... \lpmud\bin\go32.exe : 386 Extender (VITAL!) \lpmud\bin\pars312.exe : The new parse, in COMPAT_MODE (2.4.5 ML) \lpmud\bin\pars312c.exe : The new parse, in non-COMPAT_MODE (3.* ML) \lpmud\bin\tarpat.exe : Tar file extracter. \lpmud\bin\compress.exe : Compressor/uncompressor. \lpmud\bin\master.c : LPC file (Master object) \lpmud\bin\simul_ef.c : LPC file (simulates obsolete functions) \lpmud\config\*.c : Some source files, can't see why I should keep these... \lpmud\doc\bugs : Bugs not yet fixed (From the CD gang) \lpmud\doc\compat : What has changed for the COMPAT_MODE \lpmud\doc\compress.doc : Manual for \lpmud\bin\compress.exe \lpmud\doc\tarpat.doc : Manual for \lpmud\bin\tarpat.exe \lpmud\doc\autoxbat.smp : Sample autoexec.bat from John Olson \lpmud\doc\cfgsys.smp : Sample config.sys from John Olson \lpmud\doc\copyrigh : Copyright notice from Lars \lpmud\doc\credits : Credits list from Lars \lpmud\doc\done : What the CD gang has done so far \lpmud\doc\readme : Old readme from Werner Almesberger \lpmud\doc\readme.1st : This file, written by Olav Kolbu \lpmud\doc\copying : FSF Copyright notice (Since this is compiled with GCC...) \lpmud\drivers\aheada.grd : Graphics drivers for use in the GO32 : variable. \lpmud\drivers\aheadb.grd \lpmud\drivers\ati.grd \lpmud\drivers\chips.grd \lpmud\drivers\everex.grd \lpmud\drivers\genoa.grd \lpmud\drivers\oak.grd \lpmud\drivers\paradise.grd \lpmud\drivers\trident.grd \lpmud\drivers\tridnt89.grd \lpmud\drivers\tseng3k.grd \lpmud\drivers\tseng4k.grd \lpmud\drivers\vga.grd \lpmud\drivers\video7.grd \lpmud\lines : The file pointed to by the SERIAL variable \lpmud\lines2 : Sample \lpmud\lines file \lpmud\lines.ser : Sample \lpmud\lines file \lpmud\version.oms : My (Olav Kolbu) version file, please quote this when mailing me a problem. ok312lib.exe ------------ \lpmud\mudlib\* : The complete 2.4.5 MUDLIB ****************************************************************************** * Appendix D. Caveat & Revision history. * ****************************************************************************** CAVEAT ------ As always when converting a new parse to MSDOS there is a whole lot that has to be fiddled, tweaked, added and removed. The usual MSDOS routines by Werner Almesberger has been used (Got any updates Werner?). I've only used it for a couple of hours, but everything seems to be in order. If you find any bugs that might have been caused by the conversion to MSDOS please let me know and I will try to fix them. (They might be Werner Almesbergers fault 8-) File sharing sucks in LPmud. Shelling out to dos (Alt-s) too many times, and the parser will fall over. When you get 'Can't #include "std.h"' or something similar and you know it's there, it's time for a shutdown and reboot. A TSR editor might be a good solution. This behaviour is lessened by the use of SHARE.EXE and keeping the variables FILES and BUFFERS relatively high. RELEASE HISTORY --------------- Release 1.2 : 8/4-92 Name : ok312exe.exe and ok312lib.exe : Added a MUDLIB (2.4.5.) Rewrote the documentation. If you can't follow them now, please tell me what your problem is and I'll include it in the docs. Release 1.11 : 6/4-92 Name : m312-111.exe : Found out that the 1.1 release lacked a file, namely go32.exe. This is the DJ-GCC 386 DOS Extender, i.e. the program that makes room for the parse. It was in my path all the time, so I didn't think the mud needed it at all. Sorry about that... ;-) This release never made it out (Well, it was on foof for about 1 hour before I removed it again. Too many mail messages wanting a mudlib included.) Release 1.1 : 1/4-92 Name : msdos312.exe : Released both 3.1.2 parsers for MSDOS. Included some help in installing LPmud from scratch. No mudlib included. Next version will probably have mudlib(s) included, possibly in separate files. Got swamped again by people that couldn't get it to run properly... 29/3-92 : Released the 3.1.2 COMPAT_MODE parser for MSDOS. Got swamped by people emailing me to put up 3.1.2 non-COMPAT_MODE and also to provide some help in installing it. ??/?-92 : Compiled 3.0.46 - 3.1.1, not released. ??/?-91 : Got a copy of Werner Almesbergers LPmud 3.0.45 port for MSDOS. Release 1.11 : 6/4-92 : Found out that the 1.1 release lacked a file, namely go32.exe. This is the DJ-GCC 386 DOS Extender, i.e. the program that makes room for the parse. It was in my path all the time, so I didn't think the mud needed it at all. Sorry about that... ;-) ---------------------------------------------------------------------------- COMING : 1. The CD versions of the parser (1.0.55?) and mudlib for MSDOS. 2. A complete lpmud for DOS, "extract'n go (tm :-)", including a 2.4.5 mudlib. 3.0 mudlib as well, if I can get hold of a 'standard' one... 3. Well, what do you need? WANTED : Other 3.0 mudlibs... ADDRESSES --------- I can be reached at the following addresses: MUD --- Aragorn on NANVAENT (Administrator) IP=130.159.220.6 Port=3000 - University of Strathclyde, Glasgow, Scotland. Open 5pm-9am Weekdays, all day weekends (GMT) EMAIL ----- o.kolbu@strath.ac.uk (at least until July 1992, probably longer) okolbu@ifi.uio.no (Always) SNAIL-MAIL: ----------- Olav Kolbu (Until July 1992) 45 1/r Bellshaug Gardens Glasgow G12 0SA Scotland Olav Kolbu (Always) Libakkveien 1 A 1184 Oslo 11 Norway Now, this archive is provided free of charge (as most other programs should). All I'm asking for is that if you find this archive/information helpful send me a postcard. :-) (Use the address in Norway...) HAPPY MUDDING!!! The usual Trademarks and Copyrights apply to the commercial products I have mentioned in the text above. ***************************** END OF FILE ************************************