Author Topic: VS traps on java first line?  (Read 4525 times)


  • Community Member
  • Posts: 5
  • Hero Points: 0
VS traps on java first line?
« on: May 15, 2009, 04:00:38 am »
I see this forum has little activity, but I'll give this a try - TIA!  I've been a SE / VSE customer a dozen years or more, almost never have a prob. Should I just delete the Configuration directory?

This is the simplest I can make this test case.  I created a file

public class TestClass
I type the first line which gets a error (red X).  When I type the opening brace (and the closing brace gets created by vs,  vs traps.

I’ve done java with this editor install three or four years ago, so wonder if it’s some setting in my VS. 

Error signature: vs.exe  ModName: vsrte.dll  ModVer: Offset:00019de0
Exception information: 0xc0000005  Record: all 0's  Address:0x000000001919de0

Support Info:

SlickEdit Version 10.0.3 Copyright 1988-2005 SlickEdit Inc.

Serial number: WB311102

Technical Support Phone: 1 919.473.0070
Technical Support Email:
Contact Product Support: click here
View Maintenance Details: click here

Build Date: October 27, 2005
Emulation: CUA

OS: Windows XP
Version: 5.01.2600  Service Pack 2

Installation Directory: C:\Program Files\SlickEdit\ (non-removable drive,NTFS)
Configuration Directory: C:\Documents and Settings\Administrator\My Documents\My SlickEdit Config\10.0.3\ (non-removable drive,NTFS)
Configuration Drive Usage: 75822MB / 97682MB

Memory Load: 55%
Physical Memory Usage: 705MB / 2097MB
Page File Usage: 995MB / 4194MB
Virtual Memory Usage: 65MB / 2097MB


  • Senior Community Member
  • Posts: 2524
  • Hero Points: 329
Re: VS traps on java first line?
« Reply #1 on: May 15, 2009, 12:54:46 pm »
You should probably post this in the main slickedit forum.

Instead of deleting your configuration folder, use the -sc switch when you invoke slick  -  vs.exe +new -sc c:/temp/someNewEmptyFolder and a new config will be created.  If you still get the problem, you could think about reinstalling.  If the problem goes away, backup your original config folder, then (with slick closed), delete vslick.sta from your config folder, then run slick using your normal config folder and see if the problem is gone.  vslick.sta will be re-created when you run slick and most of your settings should be retained.

You can use filealyzer to check the MD5 sum of vsrte.dll for V10.0.3  - it should be F1AAD0480B21B7922064982C0C482A6C, 14 July 2005.