Installation and setup of DMapEdit ---------------------------------- To install DMapEdit at the location of you choice, simply copy all the files to the directory of your choice (or unzip the zip file in the directory of your choice). Which directory you choose is up to you, however all of the required files must be placed in the same directory (don't put half in one directory and the other half somewhere else basically). You can put DMapEdit in the same directory with Doom and/or Doom II if you want. If you decide not to, however, you will need to tell DMapEdit where it can find the files for these games (Or more specifically, the IWADs. These are the files 'doom.wad' and 'doom2.wad'). There are 2 ways you can do this. The first is by using command line switches: dmapedit -ic:\doom For Doom dmapedit -i2c:\doom2 For Doom II dmapedit -ic:\doom -i2c:\doom2 If you have both Doom and Doom II If you decide on this method, making a batch file to handle this, and placing that batch file somewhere in DOS's search path would be a good idea. Even if you decide not to do it this way, it would still be a good idea to write a batch file to run DMapEdit, which will be explained below. The second way to specify the paths to Doom and Doom II's IWADs is within the dmapedit.ini file. To do so, use a ASCII text editor (such as MS-DOS's 'edit' command) to change the following 2 lines in the dmapedit.ini file: *doom path = c:\doom *doom 2 path = c:\doom2 Change them so that they point to the proper directories (or the IWAD file itself, if you wish), and remove the '*' in front of the Doom's you have. This '*' in front makes it a comment, which is skipped. So, removing them will allow these settings to be used by DMapEdit. You are also free to change any other setting within this file to your taste. That is all there is to setup, as long as you run DMapEdit from the directory you installed DMapEdit. If you wish to run it from anywhere, you will need to continue on with the next section. -- More advanced setup -- DMapEdit can be run from places other than where it is installed. For example, say you installed DMapEdit in 'c:\dme\' and have Doom in 'c:\doom\' and have all your PWADs in 'd:\pwads\'. You may wish to run DMapEdit while you are in the 'd:\pwads\' directory, so DMapEdit will attempt to load pwads from there instead. With the DJGPP compiled version of DMapEdit (which starting with v4.0 beta 5 or so it has always been) it can't tell where it was run from any longer, unlike the Borland C compiled version. Thus, a command line switch was added to allow you to tell DMapEdit where it is installed at. Thus, it is recommended to use a batch file to run DMapEdit instead of adding DMapEdit's directory into your 'paths' environment variable. Assuming you installed DMapEdit in 'c:\dme\', your batch file would look like so.. c:\dme\dmapedit.exe -d c:\dme %1 %2 %3 %4 %5 %6 %7 %8 %9 Because you may be running this batch file from anywhere on your system, you need to specify the full path of the file you wish to run, which is what the first part is. The '-d' switch indicates the next part will be the path of DMapEdit's files (or instillation directory, in other words). By the way, parts are seperated by spaces, as long as there isn't a '\' in front of the space, in which case the space and next part will become part of the current part. Follow that? :) The remaining '%X' (X being a number) parts simply pass the command line that was passed to the batch file on to DMapEdit. Thus, you only need to put what you need every time in here (and thus won't need to type it out every time you run DMapEdit). You can use other switches and whatnot as the need arrises by passing them to the batch file as you run it. For a full list of command line options available, run DMapEdit with the '-?' switch.