Hello All,
As has been mentioned in other threads, you can copy ALL but one of the files from your old RENAMED config directory to the new config directory that was created. (You don't need to copy any of the folders over, they will get recreated.) The EXCEPTION is vslick.sta which is where the corruption most likely lies. Yes, I think this is the case for you, however, RonG and srouleau may be seeing the makefile issue that shows the same symptoms.
After you have copied over all of the files, AGAIN, MINUS the vslick.sta file, many of your configuration files will restore themselves on a restart of SlickEdit.
vusrdefs.e, vusrobjs.e, and vusrmacs.e are the files that you will load manually, if they exist. (Not everyone will have a vusrmacs.e file for example.)
With all of the files copied into the newly created directory, start SlickEdit. Then simply enter the full path and name of the above files via the SlickEdit command line and hit Enter. (To bring up the SlickEdit command line, hit ESC in most emulations and be sure to add double quotes around the path and file name if it contains spaces, for it to run successfully) This will reload your most important settings that you had before. The file of note is vusrdefs.e which contains most of your settings including fonts, colors, and key bindings.
In your case, due to the spaces, you would simply enter the path and filename(s) as such:
"C:\Documents and Settings\user_name\My Documents\My SlickEdit Config\12.0.3\vusrdefs.e"
Again, note the double quotes. Do this with the other .e files and you should be back in business.
Regards,
SlickEdit Support