Welcome to Vista Banter. You are currently viewing our boards as a guest which gives you limited access to view most discussions, articles and access our other FREE features. By joining our free community you will have access to ask questions and reply to others posts, upload your own photos and access many other special features. Registration is fast, simple and absolutely free so please, join our community today! If you have any problems with the registration process or your account login, please contact contact support. |
|
General Vista Help and Support The general Windows Vista discussion forum, for topics not covered elsewhere. (microsoft.public.windows.vista.general) |
|
LinkBack | Thread Tools | Display Modes |
|
|||
Risk of disableing "user account control"
I have a Konica/Minolta 2430DL network printer on my network with XP and a Vista
PC's. I have had constant problems getting the printer to work with the Vista PC - never a problem with XP. I finally found the following page which indicates the problem is "user account control" (UAC) and disableing that makes it work. Sure enough, it does. http://www.vistax64.com/vista-print-...nistrator.html My question is - what are the risks of doing this on a PC on a home network? Is it something I need to worry about. It seems as though this function is something that was not used in XP at all. Deisableing it did not seem to affa=ect the account login when booting the PC. |
|
|||
Risk of disableing "user account control"
From: "Bob F"
I have a Konica/Minolta 2430DL network printer on my network with XP and a Vista PC's. I have had constant problems getting the printer to work with the Vista PC - never a problem with XP. I finally found the following page which indicates the problem is "user account control" (UAC) and disableing that makes it work. Sure enough, it does. http://www.vistax64.com/vista-print-...nistrator.html My question is - what are the risks of doing this on a PC on a home network? Is it something I need to worry about. It seems as though this function is something that was not used in XP at all. Deisableing it did not seem to affa=ect the account login when booting the PC. Little since I have serviced computers infected with UAC enabled. Therefore I think it is more of an annoyance than anything else. -- Dave Multi-AV Scanning Tool - http://multi-av.thespykiller.co.uk http://www.pctipp.ch/downloads/dl/35905.asp |
|
|||
Risk of disableing "user account control"
On Sun, 8 Sep 2013 18:21:02 -0400, David H. Lipman wrote:
From: "Bob F" I have a Konica/Minolta 2430DL network printer on my network with XP and a Vista PC's. I have had constant problems getting the printer to work with the Vista PC - never a problem with XP. I finally found the following page which indicates the problem is "user account control" (UAC) and disableing that makes it work. Sure enough, it does. http://www.vistax64.com/vista-print-...nistrator.html My question is - what are the risks of doing this on a PC on a home network? Is it something I need to worry about. It seems as though this function is something that was not used in XP at all. Deisableing it did not seem to affa=ect the account login when booting the PC. Little since I have serviced computers infected with UAC enabled. Therefore I think it is more of an annoyance than anything else. That to me reads like "I have known people to get the flu after getting a flu shot, so vaccination is more an annoyance than anything else". -- Gene E. Bloch (Stumbling Bloch) |
|
|||
Risk of disableing "user account control"
From: "Gene E. Bloch"
On Sun, 8 Sep 2013 18:21:02 -0400, David H. Lipman wrote: From: "Bob F" I have a Konica/Minolta 2430DL network printer on my network with XP and a Vista PC's. I have had constant problems getting the printer to work with the Vista PC - never a problem with XP. I finally found the following page which indicates the problem is "user account control" (UAC) and disableing that makes it work. Sure enough, it does. http://www.vistax64.com/vista-print-...nistrator.html My question is - what are the risks of doing this on a PC on a home network? Is it something I need to worry about. It seems as though this function is something that was not used in XP at all. Deisableing it did not seem to affa=ect the account login when booting the PC. Little since I have serviced computers infected with UAC enabled. Therefore I think it is more of an annoyance than anything else. That to me reads like "I have known people to get the flu after getting a flu shot, so vaccination is more an annoyance than anything else". I can see that but I don't see UAC actually helping, only hindering. -- Dave Multi-AV Scanning Tool - http://multi-av.thespykiller.co.uk http://www.pctipp.ch/downloads/dl/35905.asp |
|
|||
Risk of disableing "user account control"
On Mon, 9 Sep 2013 15:10:21 -0400, David H. Lipman wrote:
From: "Gene E. Bloch" On Sun, 8 Sep 2013 18:21:02 -0400, David H. Lipman wrote: From: "Bob F" I have a Konica/Minolta 2430DL network printer on my network with XP and a Vista PC's. I have had constant problems getting the printer to work with the Vista PC - never a problem with XP. I finally found the following page which indicates the problem is "user account control" (UAC) and disableing that makes it work. Sure enough, it does. http://www.vistax64.com/vista-print-...nistrator.html My question is - what are the risks of doing this on a PC on a home network? Is it something I need to worry about. It seems as though this function is something that was not used in XP at all. Deisableing it did not seem to affa=ect the account login when booting the PC. Little since I have serviced computers infected with UAC enabled. Therefore I think it is more of an annoyance than anything else. That to me reads like "I have known people to get the flu after getting a flu shot, so vaccination is more an annoyance than anything else". I can see that but I don't see UAC actually helping, only hindering. Since I don't have any such problems with my system and haven't heard of this sort of problem otherwise, I find that I suspect that the hindrance relates to a bug in the driver, or perhaps not so much a bug as a driver which has not caught up with the latest OS. The forum thread has a link to the latest drivers; the OP has not said that he tried them. That thread also says that "KM blames MS and MS says it's KM's drivers." I believe the latter; YMMV :-) -- Gene E. Bloch (Stumbling Bloch) |