Next: , Previous: , Up: Non-Unix Installation   [Index]


2.2.1 Installation Procedure

  1. Obtain the distribution archive that contains the executable for your platform. (You might already have done this).
  2. Create a subdirectory like for example C:\MSGED, change into this subdiretory, and unzip the distribution archive. Be sure to use the ‘-d’ option when unzipping the archive, because some archives contain subdirectories. (You might already have done this).
  3. Find out which codepage you are using by issueing the CHCP command. It is probably 437, 850 or 866. Then, select the corressponding read map and write map files that are shipped with MsgEd TE (the have names of the form READMAPS.codepagenumber and copy them over to READMAPS.DAT and WRITMAPS.DAT. For example, this could look like this:
    R:\MSGED> CHCP
    Active Codepage:   850
    Prepared System Codepages:   850;  437
    
    R:\MSGED> COPY READMAPS.850 READMAPS.DAT
    R:\MSGED> COPY WRITMAPS.850 WRITMAPS.DAT
    

    Please note that the filenames for the Ukrainian codepage 1125 differ from this naming scheme, they are called READMAPS.UKR and WRITMAPS.UKR.

    If there is no READMAPS.XXX file corresponding to the ‘Active Codepage’ returned by the CHCP command, see if there is a READMAPS.XXX file for one of the prepared codepages. If there is, use that one, and use the CHCP command to change to this code page each time before starting MsgEd TE. In the example above, this command would be CHCP 437. You probably would want to place this command in a batch file, together with the invoation of MsgEd TE.

    If MsgEd TE does not support the codepage that you want to use, please contact the author and ask him to add support for that particular codepage.

    See Using Special Characters like Umlauts or Cyrillics - The Charset Kludge, for more information on read and write map files, charset kludge lines, codepages, and character set recoding.

  4. Rename the file sample.cfg to msged.cfg and modify it according to your needs with your favourite text editor. See Configuration Reference, for detailed descriptions of each keyword that can be used in this file.
  5. You should now refer to the platform specific release notes found below before trying to start MsgEd TE. They can save you from a lot of headaches ;-).
  6. Optionally create an icon on your desktop or a batch file that starts the proper executable (MSGEDP.EXE for OS/2, MSGEDNT.EXE for Windows 95/98/NT, MSGED.EXE for DOS, or MSGED32.EXE for 32-Bit DOS with DOS extender) with the directory you created (C:\MSGED in the example above) as working directory).
  7. Start MsgEd TE.

Next: , Previous: , Up: Non-Unix Installation   [Index]