PDA

View Full Version : location of vedit.ini



rhureau
January 14th, 2012, 10:29 AM
I was having trouble with the vedit font. If I started it normally, it would open with the normal font, but if I started it by double-clicking a file, I would get a much smaller font.

So, I decided to look at the vedit.ini file to see what font was being used. Well, then things got confusing because even though I am using a current version of Vedit (6.21.3), installed in c:\Program Files (x86)\vedit\, the vedit.ini was only found in an old install directory c:\vedit.

So it seemed kind of hard to know exactly what was being used by the program under such cirmcumstances. So I decided to start over. I uninstalled vedit completely using the uninstall procedure under the Start menu, telling it to essentially remove everything (registry entries, etc).

I also copied everything from the old c:\vedit directory into a c:\vedit_save save directory with a different name, so I could get my old keyboard stuff, configs, etc after reinstalling. The I manually deleted the c:\vedit directory.

Then I got the latest install and installed it, using the ALL option, which puts it in c:\Program Files (x86)\vedit.

Meanwhile, I got the latest version of the executable (6.22.1) and put that in the Program Files dir.

OK. So now I want to get my configuration, keyboard, user macros, etc back to normal, presumably by copying stuff from my c:\vedit_save directory. I see in the readme file that vedit.ini is here:

%ALLUSERSPROFILE%\vedit

Here is my question: how do I know what %ALLUSERSPROFILE% resolves to?

I looked on my system and there is no Environment Variable with that name. So I tried doing a search for the vedit/ini file. Alas, I found it in TWO places:

c:\Users\All Users\vedit\vedit.ini
c:\ProgramData\vedit\vedit.ini

Each one of these directories has what looks like a complete set of user configuration files., with the user-mac directory, the config dir, etc. They appear identical.

So I am still unclear which directory I should copy all my saved configuration files, keyboard file, user macros, etc. to.

I'd appreciate any help.

Scott Lambert
January 14th, 2012, 02:27 PM
Hi,

On my system, %allusersprofile% equals c:\programdata. I am using Winows 7 64 bit.

In the Vedit help menu, you should see Dashboard Info, this gives you a report on where stuff is. If not, drop to the vedit command line, and type:

vedit_ini

and press enter. This tells you where the Vedit.ini file is that Vedit reads on startup.

While there also type:

user_home

In the subfolders of this folder is where your macros and config files go.

Scott

rhureau
January 14th, 2012, 03:37 PM
Thanks very much Scott. I will give that a try. I did actually go to the vedit command line, but then didn't know what to try. Doh! Thanks!

rhureau
January 16th, 2012, 11:16 AM
Me again. Gee, I thought I was an experienced Vedit user (since 1989), but I have just spent over an hour trying to get Vedit to pick up my color configuration from the vedit.cfg file, and it absolutely will not do it.

I have one vedit.ini file in the vedit scheme now:

c:\ProgramData\vedit\vedit.ini

it has this in it:

UserCfgDir=C:\ProgramData\vedit\config

In that folder, I have my vedit.cfg file (the only place I have one, either under c:\Program Files (x86)\vedit\ or C:\ProgramData\vedit\

In the vedit.cfg file, I have the following 2 lines (among many others):

Config( C_TEXT, "Color for edited text ", 128 )
Config( U_AUTO_CFG, "Auto-save config", 0 )

And yet, everytime I start Vedit, I get edited text color of 31, and the Auto-save Config check box is checked.

I noticed that the Help file shows C_W_TEXT as the keyword for edited text, so I changed it to that in the vedit.cfg file, but that made no difference either.

Actually, even if I manually load the vedit.cfg file I have in C:\ProgramData\vedit\ (using Config>Load config), it makes no difference in my editing colors. It remains 31.

I guess I am mis-remembering how Vedit works, or maybe there has been some change with the new version in how these files and configs work, but I am totally confused. Can someone point me in the right direction, please. I prefer to not have to reconfigure all my colors using the Config color screens, if I can avoid it).

Scott Lambert
January 16th, 2012, 05:14 PM
Hi,

Remember that the colour values may be changed by commands in the file type config files in user_home\file-cfg folder. May be that is the problem.

I would suggest trying putting the colour config statements in the ustartup.vdm file and see if they work there. (sort of a work-around)

Just 2 quick ideas off the top of my head......

Scott

rhureau
January 16th, 2012, 06:00 PM
OK, I'll check. Another thing is that my vedit.cfg file is quite old. Maybe it doesn't meet current standards and is failing half-way thru or something?

I'm thinking maybe I should just bite the bullet and do it manually (via the config menu in the program), save it, and then I'll have a good latest config file. I did notice that if I make a change via the config menu, it works the next time I run it, and the changed values are in the C:\ProgramData\vedit\vedit.cfg . This is what is making me think that my old vedit.cfg file may be faulty.

Thanks again for the suggestions!

Scott Lambert
January 16th, 2012, 06:57 PM
Hi,

One way, you might get a pristine vedit.cfg is to temp rename your config.cfg file to config.old and rename your ustartup.vdm oldstartup.vdm and then start Vedit and from the config menu do a Save Config. This should give you a config file with only the default values built into Vedit.

What I do is ignore the config file and just do all my customizing in the ustartup.vdm file. Just copy the commands you need from the config.cfg file to the ustartup.vdm. Makes debugging easier because you can see everything you have changed and comment out lines until things work again.

Scott

rhureau
January 17th, 2012, 08:41 AM
Yeah, I see the value of using ustartup. I've been kind of shying away from that because I had multiple ustartup.vdm files all over the place and was not sure which was being used. I have since then carefully read the info in the startup.vdm file about where it looks for ustartup and have whittled it down to ONE ustartup.vdm (I think. Jeeezzz!). So maybe I will use that.

Thanks again!

pal
January 17th, 2012, 03:29 PM
I really do not see any reason to use ustartup.vdm.
Anything you can set there you can set in vedit.cfg.
The advantage of not using ustartup.vdm is that you can change settings from the Config menu.
If you set something in ustartup.vdm, it overrides the settings you try to set from the Config menu.
Maybe that is the problem?
I suggest you uncheck the option Config -> Miscellaneous -> Enable USTARTUP.VDM file.

rhureau
January 18th, 2012, 09:28 AM
I know that the problem isn't in my ustartup file, because I only have used that for loading a user menu and for setting the default Open directory. I never even thought of the idea of putting config statements in it till I read Scott's suggestion.

I do see what you mean about the ustartup file complicating the config picture since it overrides whatever you set in the config menu. Thanks for the suggestions. :)

GreenviewData
January 18th, 2012, 01:01 PM
Having read over this thread, I don't see any obvious problems or solutions. I know that some people who have used VEDIT for a long time have a very unique configuration and setup for many files. Since VEDIT 6.20 changed the file structure to work properly with Windows 7, some of these old custom setups don't transfer easily to the new version.

The main thing to remember is that the vedit.ini file is now in the USER_HOME directory. The very small vpw.ini file in the same directory as the vpw.exe file specifies where the USER_HOME directory is, usually with the %ALLUSERSPROFILE% environment variable. The environment for Windows XP, Vista and 7 should have this set.

Ted.

pal
January 19th, 2012, 10:20 AM
OK, I'll check. Another thing is that my vedit.cfg file is quite old. Maybe it doesn't meet current standards and is failing half-way thru or something?

Do you mean you copied your old .cfg file to new Vedit installation?
That probably does not work. It is likely that the format has changed.
You should instead use Transfer Configuration option while installing Vedit.

rhureau
January 20th, 2012, 10:52 AM
Do you mean you copied your old .cfg file to new Vedit installation?
That probably does not work.
Yes, that is what I was doing. I agree, it was causing problems.

Ted, I agree that there is no problem really. Just an old-timer trying to get up to speed with the latest version. I especially had trouble getting the info about the resolution of %ALLUSERPROFILE%. I have looked in the Windows 7 system settings, but really cannot see any useful info there. Here is a snapshot (hope this works):

53

It has the alluserprofile entry there, but is showing some temp settings, not the real value. But anyway, now that I know what it is and where to find the info, I'm all set. :)

mrvedit
January 20th, 2012, 06:43 PM
To see the environment variables, go to a command prompt and give the command "set".

Ted.

rhureau
January 21st, 2012, 11:45 AM
Hmmm, sounds vaguely familiar. Command prompt and set. A blast from the past! ;) Yes, thanks, I remember that now. Works great!

rejto
December 8th, 2014, 06:09 PM
Dear fellow Vedit users:

Thank you for sharing your ideas on using the Ustartup.vdm file with me. So, let me give you a self-survey:

I am intimidated editing the vedit.cfg file. Oops, I just had an idea.

At the same time, I would feel comfortable creating a USER EDITABLE section of that file and editing that part. For example, I could copy my present Ustartup.vdm file to the end of my Vedit.cfg file and that would be my "editing".

So, far this is a thought experiment only. It should be easy to implement it... Copy the present Vedit.cfg file to Vedit_(present-date).cfg and then edit the present Vedit.cfg file. If it works, great keep it. If not discard it.

-peter

rejto12
February 10th, 2016, 10:19 PM
I really do not see any reason to use ustartup.vdm.
Anything you can set there you can set in vedit.cfg.
The advantage of not using ustartup.vdm is that you can change settings from the Config menu.
If you set something in ustartup.vdm, it overrides the settings you try to set from the Config menu.
Maybe that is the problem?
I suggest you uncheck the option Config -> Miscellaneous -> Enable USTARTUP.VDM file.

Pauli,

My laptop running Win(64) broke. The newer laptops run Win 10. I noticed on your signature that you use both, Win 7 and Win 10.
Did you find any Vedit issues in Win 10 ?

Thanks as always,

-peter

rejto12
March 16th, 2016, 01:05 AM
'On my system, %allusersprofile% equals c:\programdata. I am using Winows 7 64 bit.

In the Vedit help menu, you should see Dashboard Info, this gives you a report on where stuff is. If not, drop to the vedit command line, and type:

vedit_ini

and press enter. This tells you where the Vedit.ini file is that Vedit reads on startup.

While there also type: '


Hi Scott,

I am rereading your email. I just want to make sure that your are still using the %allusersprofile% , DOS/Environment variable in your Vedit installation. I am in the process of following your example.

1.: I did put this environment variable into dashboard, that I did upload to the forum under the name of dashboard_v3.0_pr4.vdm. As per our previous conversation I plan to upload it to the dashboard thread under dashboard_v4.0.vdm and make it explicit that the two treads have been merged.

2.: I also would like to point out that your(our) installation is different from the one of Ted. He is using the single user option, as per his, ustartup.vdm thread.
I also did put that environment variable into dashboard.

3.: I vaguely remember that a Vedit User asked on this forum about this environment variable. Then Ted answered him that via the Set DOS command.
Do you happen to remember the exact location of that thread ? I would like to tell that Vedit User that now it is available from the dashboard.vdm.


-peter



user_home

In the subfolders of this folder is where your macros and config files go.

Scott[/QUOTE]

Scott Lambert
March 16th, 2016, 10:45 AM
Hi Peter,

I only referred to %allusersprofile% because that is what Rhureau referred to in his initial message in this thread.

The env. variable I look at is %userprofile%, and I have recommended people have their user_home off of %userprofile%, so for example if user Bob's %userprofile% has value of c:\users\bob, then Bob's user_home would be c:\users\bob\vedit

That is the way I have done things, and never had a problem with my Vedit installation.

I don't why one would put their user_home off %allusersprofile%, c:\programdata on my system is a hidden directory. Likewise, why bury it deep in the directory tree off %appdata% which on my system is also a hidden directory. This is the way these directories were set when I got the system.

My opinion is use %userprofile% in dashboard, not %allusersprofiles%.

Scott

rejto12
March 17th, 2016, 02:28 PM
Hi Peter,

I only referred to %allusersprofile% because that is what Rhureau referred to in his initial message in this thread.

The env. variable I look at is %userprofile%, and I have recommended people have their user_home off of %userprofile%, so for example if user Bob's %userprofile% has value of c:\users\bob, then Bob's user_home would be c:\users\bob\vedit

That is the way I have done things, and never had a problem with my Vedit installation.

I don't why one would put their user_home off %allusersprofile%, c:\programdata on my system is a hidden directory. Likewise, why bury it deep in the directory tree off %appdata% which on my system is also a hidden directory. This is the way these directories were set when I got the system.

My opinion is use %userprofile% in dashboard, not %allusersprofiles%.

Scott

Hi Scott,

I have completely missed your point saying that:

"I only referred to %allusersprofile% because that is what Rhureau referred to in his initial message in this thread."

I have learned quite a bit from the rest of your message as well. In particular, I learned that

" My opinion is use %userprofile% in dashboard, not %allusersprofiles% "

Here is my reaction to your message:

I shall continue to align the installation part of dashboard with the installw.vdm options. At the same time, I shall add the %userprofile% environment variable to dashboard.

Incidentally, can I refer to this as Scott's preference ?

P.S.
I have already added a reference to Pauli Lindgren into dashboard. Specifically, Pauli does not use ustartup.vdm.
In other words, he prefers to do his customization by editing the various Vedit Configuration files.
( In short I shall continue using ustartup.vdm. At the same time, I shall study Pauli's messages on the subject.)

Thanks again, I have learned quite a lot from your message.


-peter

Scott Lambert
March 17th, 2016, 04:41 PM
Hi Peter,

"Incidentally, can I refer to this as Scott's preference ?"

Up to you Peter, I don't mind either way.

If I remember, the install program allows the user to specify the exact path of the user_home directory, at least under the Multiple User option.

Scott