Re: setting policies on WinXP Home
From: Drew Cooper [MSFT] (dcoop_at_online.microsoft.com)
Date: 12/31/03
- Next message: Chris: "system32 trojan"
- Previous message: Chris: "Trojan Horse Invasion!"
- In reply to: Roger Abell: "Re: setting policies on WinXP Home"
- Next in thread: -R-e-h-a-n-: "Re: setting policies on WinXP Home"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Tue, 30 Dec 2003 19:51:44 -0800
"needs to run 24x7" does sound like a service to me. The unstated "needs to
interact with the desktop" does not. Why not run it as a service then have
a front-end app that users can run in their context; something that RPCs
(whichever variant) back and forth with the service.
If we knew more about the app we might be able to offer better feedback.
-- Drew Cooper [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights. "Roger Abell" <mvpNOSpam@asu.edu> wrote in message news:eEKSpHvzDHA.4064@tk2msftngp13.phx.gbl... > Policy tools are not part of, and do not run in, Home > edition. You can effect most policy based registry > setting by direct registry manipulations. > However, contrary to an earlier post, as this app does > apparently have an interactive window, I would say > that this should not run as a service. > Also, I would not buy or run and app that made me > disable any feature of my preferred user interface, > especially right click menuing. > What you should do is make a minor redesign to your > application, so that on launch a small wrapper fires up, > and this spawns off your existing app and sleeps on a > close event from its child, upon receipt of which it > cycles the spawn and sleep on close. > > -- > Roger Abell > Microsoft MVP (Windows Server System: Security) > MCSE (W2k3,W2k,Nt4) MCDBA > "Jeff" <anonymous@discussions.microsoft.com> wrote in message > news:099d01c3cee8$ea766cb0$a601280a@phx.gbl... > > Windows 200 allows me to set a local policy to disallow > > right-clicking. > > Any ideas as to how this can be accomplished? > > > > > > >-----Original Message----- > > >If you app needs to run 24/7 then it should be running as > > a service. > > > > > >It seems a simple programmer fix to implement that > > behaviour. capture > > >WM_CLOSE etc in your app and do whatever. > > > > > >I am puzzled how does it work in windows 2000 differently! > > > > > > > > >-- > > >-R-e-h-a-n- > > > > > >"Jeff" <anonymous@discussions.microsoft.com> wrote in > > message > > >news:08fa01c3cedd$cbe51c70$a601280a@phx.gbl... > > >> I know Win2k inside-out, but WinXP I'm lacking. I'm > > >> implementing stand alone XP Home PCs to customers with > > our > > >> proprietary program set-up on them. The #1 complaint is > > >> that they accidentally close to program (needs to run > > >> 24x7). The users need to access the programs, but I > > need > > >> to disallow them to close the app. Can this be > > done/how? > > >> > > >> thankyou > > >> Jeff > > > > > > > > >. > > > > >
- Next message: Chris: "system32 trojan"
- Previous message: Chris: "Trojan Horse Invasion!"
- In reply to: Roger Abell: "Re: setting policies on WinXP Home"
- Next in thread: -R-e-h-a-n-: "Re: setting policies on WinXP Home"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
