› Forums › Operating Systems › Windows Server 2008 R2 › Hardware Compatibility › AMD Overdrive v3.1
- This topic has 14 replies, 8 voices, and was last updated 13 years, 8 months ago by
Anonymous.
- AuthorPosts
-
- 23rd March 2010 at 18:39 #44026
So AMD Overdrive v3.1 won’t let me install on win2008R2 it says that the software is not compatable. I extracted the file with 7z but I didn’t find an msi to work with… bummer
Is there another way to get over the you can’t install this on a server error? Has anyone else done this?
- 23rd March 2010 at 19:03 #50528
I dont have AMD, either ATI, but i downloaded it:
http://game.amd.com/us-en/drivers_overdrive.aspxTried to install, seems theres an “error” indeed, or lets say this – software is dependable on OSes, which were included by the manufacturer(developer). But i found a solution for installing it. Go Properties, then Compability Mode -> and choose WIn XP or Win Vista. And woula ^_^
- 23rd March 2010 at 19:03 #60347
Anonymous
I dont have AMD, either ATI, but i downloaded it:
http://game.amd.com/us-en/drivers_overdrive.aspxTried to install, seems theres an “error” indeed, or lets say this – software is dependable on OSes, which were included by the manufacturer(developer). But i found a solution for installing it. Go Properties, then Compability Mode -> and choose WIn XP or Win Vista. And woula ^_^
- 24th March 2010 at 04:12 #50529
WARNING ABOUT USING ANY OVERCLOCKING UTILITIES:
DO NOT USE ANY OF THOSE UTITLIES ON DELL COMPUTER SYSTEMS BECUASE OF BIOS LOCKDOWNS. VOLTAGES AND FREQUENCIES MAY BE INNACRUATLY REPORTED AS OVERCLOCKED!!!! ALSO USING THIS MAY CAUSE OVERHEATING.
- 24th March 2010 at 04:12 #60348
Anonymous
WARNING ABOUT USING ANY OVERCLOCKING UTILITIES:
DO NOT USE ANY OF THOSE UTITLIES ON DELL COMPUTER SYSTEMS BECUASE OF BIOS LOCKDOWNS. VOLTAGES AND FREQUENCIES MAY BE INNACRUATLY REPORTED AS OVERCLOCKED!!!! ALSO USING THIS MAY CAUSE OVERHEATING.
- 24th March 2010 at 04:40 #50530
So I did the compatibility thing and it works if you set the compatibility for all users to vista and allow administer privileges, the utillity starts to install and then it comes up with an error that write permission is not granted on this particular folder called:
C:Windowswinsxsx86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.762_none_10b2f55f9bffb8f8I tried to remove the read only property of this folder and it wouldn’t allow me. It said that I couldn’t so I looked and it says that I have to be a TrustedInstaller to be able to change permissions for the folder. Does anyone know how to become a TrustedInstaller?
I googled it and in my short time searching it seems that programs and programmers are considered TrustedInstaller, but can’t I be one too..
This system was over clocked before…it can handle it but just maybe not under the windows 2008 r2 OS…
- 24th March 2010 at 04:40 #60349
Anonymous
So I did the compatibility thing and it works if you set the compatibility for all users to vista and allow administer privileges, the utillity starts to install and then it comes up with an error that write permission is not granted on this particular folder called:
C:Windowswinsxsx86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.762_none_10b2f55f9bffb8f8I tried to remove the read only property of this folder and it wouldn’t allow me. It said that I couldn’t so I looked and it says that I have to be a TrustedInstaller to be able to change permissions for the folder. Does anyone know how to become a TrustedInstaller?
I googled it and in my short time searching it seems that programs and programmers are considered TrustedInstaller, but can’t I be one too..
This system was over clocked before…it can handle it but just maybe not under the windows 2008 r2 OS…
- 24th March 2010 at 05:43 #50531
mabye it’s because they do not expect a server to be overclocked since the cooling requirements and stability concerns, so MS has locked down this type of thing.
However You can create a new user with admin permissions, and give them the trustedinstaller permission.
You can do with with the users and group management. This is located within the computer/server management MSC control.
You may also do this with the particular file. You can set the ownership as admin, or whatever username you want, and then modify permissions. I actually had a simaler problem today with a certain directory and this worked fine.
I hope this helps.
- 24th March 2010 at 05:43 #60350
Anonymous
mabye it’s because they do not expect a server to be overclocked since the cooling requirements and stability concerns, so MS has locked down this type of thing.
However You can create a new user with admin permissions, and give them the trustedinstaller permission.
You can do with with the users and group management. This is located within the computer/server management MSC control.
You may also do this with the particular file. You can set the ownership as admin, or whatever username you want, and then modify permissions. I actually had a simaler problem today with a certain directory and this worked fine.
I hope this helps.
- 24th March 2010 at 05:44 #50532
Also in WS2008 R1 I do not see trustedinstallers as a group. This may have been a new R2 group, However i will investigate other options….
- 24th March 2010 at 05:44 #60351
Anonymous
Also in WS2008 R1 I do not see trustedinstallers as a group. This may have been a new R2 group, However i will investigate other options….
- 8th April 2010 at 13:32 #50533
It can be installed, i just did it.
You need to modify the MSI file internally.
Do you want a copy? - 8th April 2010 at 13:32 #60352
Anonymous
It can be installed, i just did it.
You need to modify the MSI file internally.
Do you want a copy? - 11th April 2010 at 07:51 #50534
Though i wouldnt waste your time, it doesnt seem to work properly for me, its reporting cpu speeds of 20gig!
(i have a phenom II at 4.01gig) - 11th April 2010 at 07:51 #60353
Anonymous
Though i wouldnt waste your time, it doesnt seem to work properly for me, its reporting cpu speeds of 20gig!
(i have a phenom II at 4.01gig)
- AuthorPosts
- You must be logged in to reply to this topic.