Home | Online Help | OS/2 | Enhanced E Editor | Enhanced E Editor - Troubleshooting

Enhanced E Editor - Troubleshooting

Sponsored Link:

Trouble?

  • Did you use the install program? Try running it and see if that solves your problems.
  • If things still aren't working right try running the uninstallation script and rerun the installer. Be sure the install directory information box has the correct directory entered.
  • If the install program chokes with an error message that says "routine not found" the most likely cause is a dll conflict with another program. The easiest way to overcome this is to reboot and run the install program before running anything else that may using the "rexxutil.dll" functions. The install program will unload any functions it loads upon its' completion.
  • Is there a dot as the first entry of your LIBPATH statement in the config.sys? example - LIBPATH=.;C:\OS2; This tells OS/2 to check the home directory first.
  • Did you copy over ALL the old files if you had the Enhanced E installed previously? With version .14 a new "Vprexx.dll" was introduced. Some features will not work without this new dll.

All files for the Enhanced E's must reside in the installed directory with the following exceptions:

  • The DLL files can be moved to the \os2\dll directory or to a directory that you have setup in your path for "user.dll's" if you prefer but shouldn't need to be moved. If you have more than one copy of a particular dll, put the newest one in os2/dll or a user/dll directory to save disk space. Before deleting the older dll, make sure all your programs work with the newer one.
  • In order to use the Enhanced E's from the command line, OS/2 needs to know where they are. Rather than adding to your already LONG Path statement or adding an environment variable etc. Try copying the two files EE.EXE & EEE.EXE to your \OS2 directory. They are small and the effect on your freespace will hardly be noticeable.
    <Help Enhanced E Editor