1. download and extract the DNN installer.  In my case, I downloaded DotNetNuke_Community_06.01.03_Install and extracted it into a temporary directory.
2. Make sure you add feature .NET Framework 3.5.1 Features, and enable ASP.NET at the same time
3. In my case, I am installing DNN to the root of a new subdomain, so I created a new folder in my website directory named for the domain name.
4. Copy over the DNN files into your website directory
5. Go to the IIS manager and setup a new website and point it to your directory
6. Make sure you add default.aspx as the default document type
7. Make sure you create a new dedicated application pool.  In my case I used DNN as the name of the application pool.
8. on your WWW directory, grant the following permissions.  {machinename}\IUSR (full control), ASPNET (F.C.), Network Service (F.C.)
9. Using SQL manager, create a new database for the site.  An empty database will suffice.  Create a login for the database.
10. Update the SQL server connection strings in the web.config file to point to the database server and using your UN/PW from above.
11. Now try accessing the site you’ve created and you will get this error:
1. Description: The application attempted to perform an operation not allowed by the security policy.  To grant this application the required permission please contact your system administrator or change the application’s trust level in the configuration file.
   Exception Details: System.Security.SecurityException: Request for the permission of type ‘System.Web.AspNetHostingPermission, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089′ failed.
2. 
12. To solve that, go to the Application pool and edit the Application Pool you created for this site, in my case it is DNN
1. Click Advanced Settings
2. Set Managed Pipeline Mode to CLASSIC
3. Set Identity=Network Service.
4. Click OK
5. Click Recycle
6. Go back to the IIS manager and do a restart of the IIS service on the webserver.
7. 
13. Try to access your DNN site again now and it should work properly.
14. Complete the DNN wizard and you should pass all tests (like permissions)

1. Launch iTunes
2. Delete Voice Memos (from the Playlist list on the left side).
3. Unplug your phone
4. Quit iTunes
5. Re-launch iTunes
6. after iTunes is up, connect your iPhone
7. Click SYNC and your voice memos should sync.

We recently updated to the newest NVIDIA drivers for Windows 7 x64 which are version 270.61.

After doing this we noticed the core clock on our NVIDIA Geforce 480 would drop from a standard or overclocked speed, down to 405mhz.  The core clock would stick there and the only way we can get it back is to reboot that machine.  Then after a few minutes again running the BOINC app, the core clock would drop to 405mhz again.  (We can see this because we use the MSI Afterburner 2.1 app, which has a nice real-time graph that shows current clock, memory and GPU utilizations among other things and also allows you to overclock the card.)

It turns out that there is some new “feature” (or bug) in the NVIDIA v. 207.61 drivers that is causing this issue.

Our solution was to uninstall the 270.61 drivers, restart and then install v266.58 drivers (which are the ones that preceeded 270.61).

After a reboot and more testing the core clock speed stay at the factory default speed (700mhz) or at our designated overclocked speed, without ever dropping down to 405mhz.

Apparently this is a widespread issue and users playing 3D based games also experience this issue as dropped frame or sluggish framerates while gaming… those users should also think about reverting to 266.58 until NVIDIA gets this sorted out.

We’ll have more information after we test the next version of NVIDIA’s drivers.

UPDATE 06/22/2011:  The same “clock drop” is also experienced on the most current NVIDIA 275.33 drivers.  Don’t use those if you plan on using CUDA.

This is what it looks like:

ATI 5870 GSOD Grey Screen of Death

We tried everything to eliminate this issue that we could think of, even uninstalling the current video card drivers and going back to the ones on the ASUS site which are from 2009. Nothing would cure this issue, so we RMA’d the laptop back to ASUS. A week later we get the laptop back with “all tests passed, no problems” and the machine had been wiped back to the factory OS defaults for Windows 7 Home Premium.

At that point I reloaded the FURMARK and BURN IN TEST applications on the laptop, and guess what – it did not go into GSOD when running 3D. Now I immediately thought this is a driver issue with the video card, because I was trying to use the latest ATI Cataylist drivers, and this wiped laptop had a clean set of factory drivers. Not wanting to keep 2+ year old drivers on my laptop (which was purchased mid 2010), I set out to try and get to the bottom of the issue.

I found two forum sites with hundreds of pages of user posts on this exact issue. First one Here Second one here

The issue is that the video BIOS on the onboard 5870 video card is old and is not compatible with the latest ATI drivers, so what needs to happen is you have to do is flash update your video card and then install the latest video drivers from ATI (in my case they were version 11.4) from the ATI SITE here.

Here is the path I would recommend:

1. download the modified, fixed video BIOS for the ATI 5870 from this post here
2. Make sure your G73 has the latest system BIOS (current version is 213), if not, update your laptop to the latest system BIOS FIRST
3. Extract the video BIOS files to a bootable USB stick and follow the directions on this page to flash the modified updated video bios
4. At this point your G73 should have the latest video BIOS and system BIOS
5. Boot the laptop. If you are not currently running the ATI Catalyst driver version 11.4, you should go and download the latest AMD Mobility Catalyst Driver from the ATI site. (current version is 11.4 as of today’s date).
6. install the latest drivers and reboot, and your GSOD situation should be history.

Note: if you still experience some other form of glitching with your video card drivers on the G73, use this procedure to completely wipe the ATI drivers, then re-install the latest ones. Try using this procedure below to get a completely fresh install of the ATI drivers.

ATI DRIVER CLEAN START GUIDE

(Modified by The Amixa Web Guru. Original one by steviejones133)

1. Uninstall the current AMD Mobility Catalyst Drivers by going to the control panel, uninstall programs and select everything. Remove. Do not use the EXPRESS removal. Use the one where you pick ALL the items to uninstall.
2. Check in Device Manager that you are back to Standard VGA Drivers.
3. If not back at VGA, uninstall/remove devices manually via device manager. This should get back to VGA.
4. Reboot into safe mode (press F8 when you are at the BIOS to get to the Windows boot menu and pick SAFE MODE)
5. Run Driver Sweeper in safe mode for Ati Display only (run as administrator by right clicking the icon – required) and CLEAN any ATI fragments.
6. Quit Driver Sweeper.
7. Re-run Driver Sweeper a second time (also as administrator), pick ATI again and let it scan once more to make sure all ATI fragments are gone
8. Run CCleaner for both clean up and registry in safe mode.
9. Repeat step 8.
10. Restart normally to windows – the laptop will look bad due using only standard VGA drivers
11. Re-run driver sweeper (admin)
12. Re-run CCleaner
13. At this point, all ATI driver fragments are gone.
14. Go to the ATI site and download the latest AMD Mobility Catalyst Drivers
15. Install the latest ATI drivers. Do not choose CUSTOM. Choose EXPRESS and let it complete.

If you are currently using http://api.recaptcha.net/challenge?k=XXXX and you need to implement reCAPTCHA on an SSL protected page — you need to switch the links to https://www.google.com/recaptcha/api/challenge?k=XXXYYYZZZ.   Per Google, this change went into effect April 2011.

For more information, read this page

The errors would also show up in the SYSTEM event log, called iaStor event ID 9.

The Solution:

In the BIOS, first make sure you are in AHCI mode.  Then choose HOT PLUG=ENABLED for your SSD boot drive (which should be on port #1 of the SATA 6.0 controller).

Save changes and boot up and your problems will be history.

You may have found this issue by looking at the IIS logfiles for your site and seeing 500 errors logged when it’s supposed to be pushing out images.

I will save you a lot of time.

Fixing permissions so that images/media/files uploaded via WordPress will properly render.  This is the fix for the infamous “500″ error that is thrown when your server has wrong file permissions and the visual result is all the images you uploaded are “broken images” and won’t display. Also called HTTP Error 500.50 – URL Rewrite Module Error when you have Detailed errors on.

1. Don’t sweat it, I will save you HOURS of time on this one.   Thanks to the article I found here after HOURS of tracking this issue down, this problem is caused because PHP first uploads the document to a temporary directory (by default C:\Windows\Temp), and then moves it from that directory to the actual /blog/wp-content/uploads/ subdirectory.  What happens is that because IIS does not have any permissions to your “C:\Windows\Temp” directory, when the file is uploaded there, then moved by PHP, the file inherits NO permissions.  So when IIS trys to serve out that file from your /blog/wp-content/uploads/subdirectory it throws a 500 error and that is actually a permissions error.
2. The solution:  on the Windows\Temp folder, grant “modify” permissions to both IUSR and {servername}\IIS_IUSRS user accounts.
3. Now when you upload files via PHP and PHP moves them to the correct directory, the files will have the correct permissions and can be accessed.
4. Important note #1:  If you already have uploaded files and are getting the dreaded broken images issue, go to the /blog/wp-content/uploads/directory and replace/update the permissions to add access for both user accounts noted above.  That will solve that issue.
5. Important note #2: as with any change off the defaults for Windows, you do this AT YOUR OWN RISK.  It’s up to you if you want to grant the Windows\Temp directory permissions for those two accounts.  If you don’t PHP won’t be able to upload without the 500 issue (unless you move the PHP temp folder elsewhere and grant those accounts access to the other folder).  Do these changes at your own risk… I cannot and won’t take any responsiblity for your systems.  Please know what you are doing.

UPDATE: 04/29/2011:  One reader commented to me that he is concerned about changing security permissions on the Windows TEMP directory, and he noted that you can also edit the php.ini file and change the location of the “upload_tmp_dir” variable and point it to another location.  It’s up to you how you want to do this, as long as you have the right permissions mentioned above, your WP images and future uploads will work fine.

The page you requested has generated an error. Please visit our homepage by clicking this link.

The issue is most likely that you are running a 32 bit version of ASPDOTNETSTOREFRONT on a 64 bit server.

to fix this:

1. IIS Manager
2. Application Pools
3. click on the application pool for the ASPDOTNETSTOREFRONT app
4. advanced settings
5. Enable 32-bit applications = TRUE
6. Click recycle

Retry your application.  It should work now.

Here is how to properly configure your server:

1. Install the Sothink Video Encoder for Adobe Flash software and register it using your registration key.
2. In the destination folder for the videos, you will need to grant {machinename}\IUSR full control.
3. the MyRequest.dll file (for ASP) won’t work properly, so if you are using ASP, you will need to use some other method to upload files to the server.  One good choice is ASPUPLOAD.COM
4. Presuming you have already setup a site under the IIS 7.5 management tool, you need to change the pool to LOCAL SYSTEM.  Do this by locating the application pool for this site, then click ADVANCED SETTINGS (on the right nav) and under PROCESS MODEL, for Identity, select LOCALSYSTEM
5. Click OK to close out of the property page above, then click RECYCLE
6. You will need to grant scripts and executables property to the site.  It’s different under IIS 7 and IIS 7.5 to do this… so on the site home, open HANDLER MAPPINGS, and click “edit feature permissions” and check execute.  Then click OK and exit out.
7. I would advise at this point to restart IIS on this box by clicking the server name and then RESTART in the right nav.
8. If you’ve done all the above properly, you should have no problems encoding videos using Sothink Video Encoder for Adobe Flash on a Windows 2008 server.

1. Make sure that ASP is installed on IIS 7 or IIS 7.5 (obviously)
2. Setup your web site
3. Your ASP files should work normally
4. to allow your .htm files to run through the ASP engine, do the following
5. On your IIS 7 or IIS 7.5 server, go into the C:\Windows\System32\inetsrv\config directory and edit the file applicationHost.config (you will need to do this in administrator mode, or do it from a different computer networking over to that server, otherwise Windows will protect that file and won’t allow you to change it.)
6. Scroll all the way to the bottom and look for the section that corresponds to your web site <location path=”Your Web Site”>
7. Change/edit the code block to add in the HANDLERS and HTM map below

8. <location path="Your Web Site">
   <system.webServer>
   <asp appAllowClientDebug="true" scriptErrorSentToBrowser="true" />
   <handlers>
   <add name="htm" path="*.htm" verb="*" modules="IsapiModule"
          scriptProcessor="%windir%\system32\inetsrv\asp.dll" resourceType="File" />
   </handlers>
   </system.webServer>
   </location>

9. Save the file.
10. Restart the web server in the IIS Manager by right clicking the server name.
11. Test your site. .HTM pages should now work as ASP files by running through the ASP.DLL