A listening socket is normally blocked by firewalls and virus scanners.
Use named pipes instead.
Paul
- Original Message -
From: Ross Levis
To: delphi@delphi.org.nz
Sent: Saturday, May 01, 2010 4:49 AM
Subject: [DUG] UAC control
I'm back to this subject again.
I
Can this work when one app is elevated and another is not? I had problems
with memory sharing via a virtual memory mapped file not working because of
this.
Ross.
From: delphi-boun...@delphi.org.nz [mailto:delphi-boun...@delphi.org.nz] On
Behalf Of Paul
Sent: Saturday, 1 May 2010 9:32 p.m.
If you can get it working using sockets, then this should work also.
I've never seen named pipes blocked by a firewall
Paul
- Original Message -
From: Ross Levis
To: 'NZ Borland Developers Group - Delphi List'
Sent: Saturday, May 01, 2010 12:59 PM
Subject: Re: [DUG] UAC
Named pipes won't be blocked by a firewall, I'm just concerned about the
Vista and Win7 security system which blocks memory sharing between elevated
and non-elevated programs.
I was thinking of simply using a text file to send data back and forward if
that is the only other option.
I'll
Hi Ross
I'm back to this subject again.
I'm not sure if anyone has already indicated this discussion:
The trick of launching yourself again as elevated with a command line
parameter seems pretty straightforward if you're not comfortable with
writing COM servers.
Relaunching is not really an option, as it could be playing a media file at
the time a user could ask for a specific change which requires elevated
access.
What I may need to do is write all the code into my elevated app and use
command-line parameters to execute the code and send the required
Why not just include an administrator manifest and have you
application run with administrator privileges all the time.
On Sun, May 2, 2010 at 12:53 PM, Ross Levis r...@stationplaylist.com wrote:
Relaunching is not really an option, as it could be playing a media file at
the time a user could