Jon, When you run the application from the local "C" drive, it is treated as 1 security zone.
However , wn you run it via a UNC (or any other external location) on the network it is a different, untrusted security zone. To fix this, open the IE settings from Tools, Internet Options. On the Security tab select Local Internet and click Sites. Clear the checkbox for "Automatically detect intranet" and check the other 3 boxes. Click the Advanced button on that same dialog box and add file://ServerName to the list of trusted sites. Clear the checkbox to "Require server verification (https) for all sites in this zone". Dave Crozier -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Jon Westcot Sent: 25 February 2009 19:34 To: [email protected] Subject: Re: Question on Registry in Vista vs Windows XP Hi Dave, Tracy, et al.: Thanks for the suggestions. It seems that SYS(0) works like a champ. HOWEVER.... Now I'm being asked to apparently "sign" the executable to avoid having Vista ask if they really want to run the application. The user sent me the following comment: ~~~~~~~~~~~~~~~~~ windows prompts me to run the software because of it being an unknown publisher, but I think that is an easy fix? Can you change? ~~~~~~~~~~~~~~~~~ Well, I could, if I knew how to do this. Or even what to do to create such a signature or certificate. Can someone enlighten me? This is essentially an in-house application; I just happen to be maintaining it from 1800 or so miles away. ;) Thanks for any help any of you can share. (Oh, I tried to search for this on the ProFox search website but, without knowing exactly what it was I was trying to find, I was having a lot of trouble finding anything useful that wasn't talking about SSL Certificates for web pages.) Jon ----- Original Message ----- From: "Tracy Pearson" <[email protected]> To: <[email protected]> Sent: Wednesday, February 25, 2009 11:25 AM Subject: RE: Question on Registry in Vista vs Windows XP > It might be this: > HKEY_CURRENT_USER\Volatile Environment\UserName > > I searched the registry for things, I do not have a reference to say this is > what you are looking for. > > As Dave said, SYS(0) or a complicated API call might be what you are looking > for. > > GetEnv("UserName") can be dinked with. > > When you start VFP with Run As... who the application is running as from > SYS(0), API, and direct Registry read are all the same. > > Tracy > > -----Original Message----- > From: Jon Westcot > Sent: Wednesday, February 25, 2009 11:45 AM > > Hi all: > > I've got a question regarding retrieving a value from the Registry > within Vista that I hope someone here can help me answer. > > Here's the situation. I've got an existing application that has been > working just fine under Windows XP Pro. At application startup, it queries > the Registry to retrieve the following key value: > > > HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Logon > User Name > > This value is then used to check in a Security table for a match on the > name. (Yes, I know this is an odd logon situation; it's what the client > wanted.) > > The thing is, now they're looking to move to Vista. And, for some > reason, this key value does not exist in Vista. > > Can someone point me to a reference of registry keys for Vista? Or can > someone recommend to me a key value I could use that would return the Logon > User Name? Unfortunately, I don't have direct access to Vista, so I can't > just open up the Registry and browse around to find the appropriate key. > > Any help you can send my way will be greatly appreciated. > > Jon > > > > [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/f17c2683ae844ba7a345fbd163e40...@gozap ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
