I have a logitech wireless keyboard and mouse combo. The software that it
uses is SetPoint. This software allows me to customize buttons on the mouse
and keyboard. Every time I startup windows, it blocks the startup of
SetPoint. I have to tell it to allow the program. Is there a way for me to
make Vista always allow the startup of this program? I have constantly run
software updates for SetPoint hoping that Logitech will update it so that it
doesn't need permission to start, but it doesn't work. The Logitech support
was also useless. Thanks in advance.

HI!
I have this problem with another soft. This is not problem. Safety. when you
start your computer, this program (keyboard) make contact
with Logitech. So, your computer by safety blocked it. Your windows asks for
your permission to liberate the program. when you give permission
the responsibility it is your. Microsoft no have responsibility any problem
in your computer. You give permission.

"Dawg53" escreveu na notÃ*cia da
...
I have a logitech wireless keyboard and mouse combo. The software that it
uses is SetPoint. This software allows me to customize buttons on the
mouse
and keyboard. Every time I startup windows, it blocks the startup of
SetPoint. I have to tell it to allow the program. Is there a way for me to
make Vista always allow the startup of this program? I have constantly run
software updates for SetPoint hoping that Logitech will update it so that
it
doesn't need permission to start, but it doesn't work. The Logitech
support
was also useless. Thanks in advance.

Check to see if that program has the Run As Admin box checked in Properties,
Compatibility. If yes, uncheck that box.

"Dawg53" wrote in message
...
I have a logitech wireless keyboard and mouse combo. The software that it
uses is SetPoint. This software allows me to customize buttons on the
mouse
and keyboard. Every time I startup windows, it blocks the startup of
SetPoint. I have to tell it to allow the program. Is there a way for me to
make Vista always allow the startup of this program? I have constantly run
software updates for SetPoint hoping that Logitech will update it so that
it
doesn't need permission to start, but it doesn't work. The Logitech
support
was also useless. Thanks in advance.

"Dawg53" wrote in message
...
I have a logitech wireless keyboard and mouse combo. The software that it
uses is SetPoint. This software allows me to customize buttons on the
mouse
and keyboard. Every time I startup windows, it blocks the startup of
SetPoint. I have to tell it to allow the program. Is there a way for me to
make Vista always allow the startup of this program? I have constantly run
software updates for SetPoint hoping that Logitech will update it so that
it
doesn't need permission to start, but it doesn't work. The Logitech
support
was also useless. Thanks in advance.

As said by others, it's a safety feature against malware. The way round it
is to schedule the program to run at startup or logon but as a "Scheduled
Task", which malware can't set up.

http://www.jimmah.com/vista/Applicat...n_program.aspx

"So... why exactly does Windows block administrative programs from running
when I log on?

Most programs cause themselves to start every time you log in by placing an
entry in your startup folder, your run registry key, or the system-wide
startup folder or run key.

Because your startup folder and personal run registry key can be written to
by non-administrative programs, Windows cannot allow administrative programs
that are started from these locations to run without prompting you. This
would allow untrusted non-administrative programs to place malware in these
locations that would be started with admin privileges when you next logged
on.

However, it is also unacceptable to allow administrative programs that are
started from these locations to prompt for your consent every time you start
up your computer. Besides being extremely annoying, a malicous program could
potentially put hundreds of malicious administrative programs in these
locations, creating an endless series of prompts for you to deal with,
creating a denial-of-service scenario.

Since neither option is desirable, Microsoft decided to disallow
administrative applications from starting automatically from these
locations.

It would also be inappropriate to allow administrative programs to be
launched from the machine-wide startup folder and run registry location,
since administrative programs can only be started inside of administrative
accounts, or from a standard user account with an administrator's
credentials entered on-demand.

The reason the task scheduler solution is allowed to work is because
non-administrative programs cannot create scheduled tasks, so there is no
way for malware to abuse this service in the way that is possible with the
other startup methods."

--
Yorkshire rules, OK