That is a possible solution too. The problem as I see it, is that when changing the security context, the UAC forces a new instance of CMD.EXE with the /C parameter.
Ken was right on the money with his suggestion, and I'm disappointed in myself for not coming to that realization, since I knew that behavior worked in another script I had previously made work on Vista. While perhaps inconvenient at times, it all makes perfect sense from an application security standpoint. -- ME2 On Fri, Nov 7, 2008 at 5:48 PM, Kurt Buff <[EMAIL PROTECTED]> wrote: > On Thu, Nov 6, 2008 at 5:25 PM, Micheal Espinola Jr > <[EMAIL PROTECTED]> wrote: >> From the command prompt (e.g. ala Windows-R -> cmd.exe), every command >> line app/util I try to run prompts the UAC and then opens that >> app/util in a new command line window. I dont mind the UAC prompt, and >> I do know why its prompting and how to avoid it. What I can't deal >> with though, is that the apps keep causing a new window command line >> window to open for which I cant save the results for, etc, and is just >> generally really annoying. How can I stop this behavior? My Google >> skillz are not working... >> >> TIA! >> >> -- >> ME2 > > Possibly stupid suggestion - How about redirecting output to a file? I > mean, that's what the command prompt is all about, right? If you need > both, that is, the output to be in the command prompt and in a text > file, meet my friend Mr. tee.exe, found at http://gnuwin32.source, in > the core utils section. > > Kurt > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
