<font size=2 face="sans-serif">Hi Vrf,</font>
<font size=2 face="sans-serif"> I am having trouble installing VEE PRO 7. </font>
<font size=2 face="sans-serif"> Running XP PRO Inc SP1</font>
<font size=2 face="sans-serif"> with 1G Memory.</font>
<font size=2 face="sans-serif"> P4 3Ghz</font>
<font size=2 face="sans-serif"> After installing the software, get the message</font>
<font size=2 face="sans-serif"> No registry values found for this version of VEE.</font>
<font size=2 face="sans-serif"> This is after installing (Under Administrator) , including typing in the supplied product key</font>
<font size=2 face="sans-serif"> from agilent.</font>
<font size=2 face="sans-serif"> Has anybody else out there experienced the same problem?</font>
<font size=2 face="sans-serif"> Help please</font>
<font size=2 face="sans-serif"> Thanks for any help in advance</font>
<font size=2 face="sans-serif"> Best Regards</font>
<font size=2 face="sans-serif"> Gavin Candy.</font>
<font size=2 face="sans-serif"> Quality Engineer.
BHC Components Ltd
20-21 Cumberland Drive
Granby Industrial Estate
Weymouth
DT4 9TE
England
Tel: ++44 1305 830734
Fax: ++44 1305 760670
Email: gavin.candy@bhc.co.uk
website: http://www.bhc.co.uk</font>---You are currently subscribed to vrf as: rsb@soco.agilent.comTo subscribe send a blank email to "join-vrf@it.lists.it.agilent.com".To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".To send messages to this mailing list, email "vrf@agilent.com". If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".
Rufus has a point here. There are generally two locations where applications
store initialization information in the registry. They are under
HKEY_CURRENT_USER and HKEY_LOCAL_MACHINE. The HKLM values are generally for
system-wide init values, while HKCU values are good for storing individual
user's preferences, recent file lists & the like.
Access to HKCU is usually never a problem, but if your IT dept is tightening
the security screws HKLM can sometimes be a problem for restricted users.
I'm sure this is not recommended practice, but this is what I would do:
1. Uninstall VEE.
2. Open the registry with regedit.exe
3. Navigate to HKEY_LOCAL_MACHINESOFTWAREAgilentVEE_Pro
4. With the VEE_Pro folder selected in the left pane, hit del. Confirm that
you want to delete the key and all it's subkeys.
5. Navigate to HKEY_CURRENT_USERSoftwareAgilentVEE_Pro
Note that there may be a "VEE_Pro" and a "VEE Pro" key. Delete whichever or
both if they are both present.
6. Using Windows Explorer, navigate to c:Program FilesAgilent
Delete any subfolders with "VEE" in the name. If explorer complains that it
cannot remove a folder, look in the folder to see what's there. If it's a
program file or a dll or ocx or whatever it probably can't be deleted
because it's running. If that's the case reboot and try again. If you still
can't remove the offending left over let me know. The procedure for getting
rid of these stragglers takes a lot of room to type out.
VEE has now been (more or less) completely removed from your computer.
What's left over will be COM and .NET registry entries, but you'd have to do
a lot of work to ferret them out. They don't matter.
Reinstall VEE, and you shouldn't have any problems.
If for some reason you can't delete values in HKLM have somebody with admin
priv do it. If you can't even *read* values in HKLM, then that's your
problem - your account doesn't have a high enough level of access. Either
get your IT folks to give your account access to HKLM or find another job.
Well, only half kidding...
<ITSoapBox>
IMO, programming of almost any kind requires an Administrator login. You
sometimes have to change all kinds of settings to get things to work right,
and having to run whining to IT to get them to do it really isn't a
productive way to get anything done.
IT can give you Administrator access to your own machine while giving you
restricted access to network resources - in short there's no excuse for not
being an Administrator on your own machine other than IT is snobby and they
have the attitude that they are the ones that are going to have to clean up
your mess if you farkle your computer by changing policies or registry
values or whatever.
You have to make mistakes in order to learn, and you can't learn if you're
not allowed to make mistakes.
A good IT dept is interested in *helping* you get your job done, not in
getting in your way. And in like kind, you should be interested in helping
IT get their job done: if you really have to change something, ask them
about it. Ask them if there are any side effects you should be aware of, or
if the method you're shooting for will open up security holes.
Can outside networks actually exploit web, ftp or telnet servers and gain
access to test or process control machines? That's a big problem, and it's
one that IT depts all over are asking themselves. Remember that "remote
shutdown" thread? That's not all you can do. All one needs is a logon name,
a password and a connection to a remote NT machine to make it completely
useless until a recovery console is run. And there are lots of ways to get
login names and passwords.
Cut IT some slack too. The pressure is on to tighten things up, and many
times the programmer is simply caught in the middle of security paranoia.
Paranoia isn't a good answer to these problems, but it *is* the easiest one
as the Patriot Act demonstrates.
</ITSoapBox>
-SHAWN-
---
You are currently subscribed to vrf as: rsb@soco.agilent.com
To subscribe send a blank email to "join-vrf@it.lists.it.agilent.com".
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".