+ Reply to Thread
Results 1 to 5 of 5

Thread: Crash when opening VEDIT

  1. #1
    Junior Member
    Join Date
    Jan 2015
    Location
    East Lansing, MI
    Posts
    7

    Crash when opening VEDIT

    ...with no chance to do anything but watch it crash.
    I think it happened after editing a text file on a network drive that no longer exists.
    Now, every time I open the program, it simply crashes. Its been a week without any success at figuring out why.
    Greenview Data tech support seems to be non-existent now that it has been acquired. Apparently the new company told Tony that he can't do VEDIT support during his work hours, and that it would have to happen during his spare time.

    I have examined my users/daniel/Appdata/Roaming/Vedit/vedit.ini file and tried to clear the "most recent files" to one good file but it made no difference.

    --
    HomeDir=c:\Program Files (x86)\vedit
    UserHomeDir=C:\Users\burkdani\AppData\Roaming\vedi t
    MacroDir=c:\Program Files (x86)\vedit\macros
    ConvertDir=c:\Program Files (x86)\vedit\convert
    UserCfgDir=C:\Users\burkdani\AppData\Roaming\vedit \config
    UserMacroDir=C:\Users\burkdani\AppData\Roaming\ved it\user-mac
    FileCfgDir=C:\Users\burkdani\AppData\Roaming\vedit \file-cfg
    SyntaxDir=C:\Users\burkdani\AppData\Roaming\vedit\ syntax
    ProjectDir=C:\Users\burkdani\AppData\Roaming\vedit \projects
    BackupDir=C:\Users\burkdani\AppData\Roaming\vedit\ backup
    VeditFtpDir=C:\Users\burkdani\AppData\Roaming\vedi t\ftp
    VeditTempDir=%TEMP%\VeditTmp
    Startup=startup.vdm

    <stuff edited out here>

    [RECENT_FILES]
    ;
    ; The Most Recently Used (edited) files will be listed in the {FILE} menu.
    ; Set "MaxMRU" to the desired number of files (0-10) depending upon your
    ; screen resolution and preferences.
    ;
    ; Other recently edited files will be listed in the File-selector "Recent"
    ; window. Set "MaxRecent" to the desired maximum number of files (0-100)
    ; displayed in this window.
    ;
    MaxMRU=1
    MaxRecent=1
    File1=C:\Pyscripts\PNE2SAC.py

    [FAVORITE_FILES]
    ;
    ; The File-selector "Favorites" window displays the selected favorite files.
    ; Set "MaxFavorite" to the desired maximum number of files (0-100) displayed
    ; in this window.
    ;
    MaxFavorite=1

    <stuff edited out here>

    My hope was that if it was trying to load a non existent file, that this would fix it. However it didn't fix anything. My program is pretty much non functional.
    However, if I launch the "uninstall programs" macro, it stays running long enough for me to cancel.
    I'll likely find my vedit installation CD and try the uninstall for real. My guess though, is that it isn't going to fix it.
    Last edited by TychoAussie; March 21st, 2018 at 01:57 PM.

  2. #2
    Junior Member
    Join Date
    Jan 2015
    Location
    East Lansing, MI
    Posts
    7
    I've tried a bunch of stuff - mostly using the shotgun method, and managed to fix the problem!
    I continued editing vedit.ini, and changed AppMax to 1 in order to launch the application in maximized size:

    AppMax=1
    InitSize=3,7,904,621
    KeepOnTop=0
    MDIScrollBars=0
    FileSelector=-500,1,1,1
    SelectorTab=2
    FileDlgPos=0,127
    Instances=0

    The application came up and I stared at it for a few moments before I realized it wasn't about to crash. There in front of me was an open file in which the font size was set to 18.
    That was actually the last operation I tried, because I was having trouble seeing and "upped" the font size. I didn't have the wherewithal to note WHICH file was opened or whether or not it was a network file,
    because I closed it without noting where it came from.

    I've since restored the font to size 12, un-maximized the window, and it now starts properly.
    Appmax has been returned to zero, and it is still running fine. I have also returned my max MRU and MaxRecent to 10, so that I have an editing history. All seems to be working now.

  3. #3
    Senior Member
    Join Date
    Nov 2014
    Location
    Minneapolis, MN
    Posts
    307
    Hi Tycho,

    I am sorry to hear about your problem. I would uninstall and reinstall the Vedit program.
    Note that the re-installation will not overwrite your USER HOME directory.

    Looking forward to hearing from you.

    -peter

  4. #4
    Senior Member
    Join Date
    Nov 2014
    Location
    Minneapolis, MN
    Posts
    307
    Hi Tycho,

    Congratulations on fixing your problem. Do I understand it correctly ? Your vedit.ini file got corrupted
    For future reference, I would copy it to the USER HOME directory.

    Also, I would run the Vedit menu {Help, Dashboard}. I would appreciate a copy of the result.


    -peter

    -peter
    Last edited by rejto12; March 22nd, 2018 at 11:58 AM. Reason: typos

  5. #5
    Senior Member
    Join Date
    Nov 2014
    Location
    Minneapolis, MN
    Posts
    307
    Quote Originally Posted by rejto12 View Post
    Hi Tycho,

    Congratulations on fixing your problem. Do I understand it correctly ? Your vedit.ini file got corrupted
    For future reference, I would copy it to the USER HOME directory.

    Also, I would run the Vedit menu {Help, Dashboard}. I would appreciate a copy of the result.


    -peter

    -peter
    Dear All,

    Inspired by Tycho's marathon vedit.ini file repair, I did a little bit more thinking about How To Diagnose A Corrupted vedit.ini File. This is that I came up with:

    I would start up Vedit using the invocation command

    c:\vedit\vpw.exe -k

    I have gleaned that answer from the old Vedit User Manual.
    After it was printed the Vedit Installation options have
    been customized. To find out your specific installation, run, {Help,
    Dashboard}. Then edit accordingly the invocation command above.

    If Vedit starts up OK with this invocation option then your original vedit.ini file was corrupted. If not, then something else went wrong.
    Note that the above invocation command also created a new vedit.ini file. Then, edit this new vedit.ini file by invoking Vedit with the
    -z invocation option.


    Here are the details of how I have gleaned my answer:

    ================================================== ========================

    REFERENCES FOR THE c:\vedit\vpw.exe -k INVOCATION COMMAND:
    -------------------------------------------------

    ....
    ....
    VEDIT 6.0
    Fully Configurable
    Multiple File Text Editor
    Universal File Editor
    User’s Manual
    .......
    .......
    Chapter 4
    Editing Guide
    Starting (Invoking) VEDIT Chapter 4 Editing Guide 56
    .....
    .....
    A typical invocation example:
    .....
    .....
    c:\vedit\vpw.exe -x compare.vdm
    .......
    .......
    Chapter 4
    Editing Guide
    Starting (Invoking) VEDIT Chapter 4 Editing Guide 57
    .......
    .......
    Running VEDIT for Windows (and DOS)
    from DOS/NT Command Prompt
    Both the Windows and DOS versions of VEDIT can be run from a DOS/NT
    command prompt. In fact, the most flexible way to run the Windows version
    of VEDIT is from a DOS/NT command prompt—you can specify the file(s)
    to open, any desired invocation options, macros to auto-execute, etc.
    .......
    .......
    Starting (Invoking) VEDIT Chapter 4 Editing Guide 59
    .......
    .......
    -k Disables reading the vedit.ini file on startup and saving
    a newvedit.ini file when exiting. A default size and font
    are used on startup; the final size and font are not saved. Since
    the serial number is stored in the vedit.ini file, VEDIT
    will run as a “trial version”.

    Now three related references:

    -g Disables auto-configuration; the vedit.cfg and
    vedit.key files are not loaded during startup.
    ...
    ...
    -i execfile ‘execfile’ is executed in place of the normal startup.vdm
    startup macro. This file contains the macro language commands
    which control the startup process. The option “-i xxx”,
    where ‘xxx’ is a non-existent file, can be used to start VEDIT
    without any startup file.
    ...
    ...
    -z Suppresses the trial version registration and information dialog
    boxes on startup.


    -peter
    Last edited by rejto12; March 23rd, 2018 at 11:37 AM.

+ Reply to Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts