Jump to content
Sign in to follow this  
juxair

win 7 64 bit install

Recommended Posts

helloi don t seem to be able to be running TP on my win 7 64 any help would be appreciatedregardsawePS: here s the error i get

Share this post


Link to post
Share on other sites
Guest trevytt2004
helloi don t seem to be able to be running TP on my win 7 64 any help would be appreciatedregardsawePS: here s the error i get
OK, replied once, but post didn't appear, so i'll try again....This is a well known issue with win7 and vista. The system prevents unsigned drivers from running. To get ound this you can boot up, press F8 and choose to allow unsigned drivers. You would have to do this each time to run FSX, unless you havent shutdown since the last flying session.Alternatively, run DSEO13B.exe to modify the unsigned drivers behaviour and let them run.The following text is from the installer script and explains what is going on in a little more detail. I have put the link to the required exe file below. I use it and have not had any problems since.It seems that Microsoft has forgotten end users when it introduced a very restricted module of driver signature enforcement in Windows Vista and Windows 7. All drivers and system files must be digitally verified or they cannot run when using both 32-bit and 64-bit versions of Windows Vista and Windows 7. In the past, it was possible to turn that feature off in Vista, but due to new kernel security updates, it is impossible to turn it off without degrading security and stability of your operating system or putting your master boot records in risk by using other software alternatives.So what is the problem with digital certificates? Well, the problem is... developers have to pay Microsoft to receive verified certificates, and that makes many applications inaccessible under Windows Vista and Windows 7. However, it is still possible to turn it off by pressing the F8 function key during system boot up, but pressing F8 every time on boot up can be a serious pain in the butt. Others have found workarounds, but most of them are too risky and may trash your master boot records, at least until now thanks to our latest tool.How does it work?Microsoft is aware that developers cannot submit every beta build they are testing. Microsoft has provided a mode inside Windows Vista and Windows 7 that will allow developers to test their software before they submit it to Microsoft’s labs. Unfortunately, even in that test mode drivers and system files must have a test certificate before installation.The good thing is that it does not have to be digitally verified. That means we can load drivers by creating our own unverified certificates. Do not worry! You do not have to do anything; our Driver Signature Enforcement Overrider will do everything for you.Supported OSes* Windows Vista 32-bit* Windows Vista 64-bit* Windows Server 2008 32-bit* Windows Server 2008 64-bit* Windows 7 32-bit* Windows 7 64-I TRIED TO USE A PROFANITY HERE - AREN'T I STUPID!anges* Watermarks Removal Option* Support for Windows 7* Several Bug-fixesSo how do I use it?First and foremost; you are using this software at your own risk, we do not take responsibility for any damages to your system, but we do not believe it can harm anyone anyway. Secondly, User Account Control (UAC) must be disabled in-order to use this tool as well.1. Go ahead download and launch the application from the link below. Inside its main menu, press on the "Enable Test Mode" button and follow the instructions on the screen. This will enable TESTSIGNING mode, which allows unverified system files to be loaded.2. Now all you have to do is to add the unverified signature to the required system files. To do so press on the "Sign a System File" button from the main menu, and enter specific filename including full path. For example: if ATITool64.sys from C:\Windows\System32\drivers refuses to load due to driver signature enforcement, you should type: "C:\Windows\System32\drivers\ATITool64.sys", and if you would like to sign more than a single file, just repeat this procedure until you’re done, and finally reboot.After you enabled Test Mode and added signatures to the required system files, they should bypass Windows’s driver signature enforcement and load without any issues. However, if for some reason you are interested to revert it, you can re-launch the application, choose "Disable Test Mode" from the main menu, and reboot. If you encounter issues or having questions, feel free to post it on our forums.Download herehttp://www.ngohq.com...t&dwn_cat_id=34Greetings from Tobago

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
×
×
  • Create New...