enable Windows 8 admin shares

you'll need to add this registry key...

Open regedit, and drill down to this key:

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System

Under this key you will need to create a new DWORD value called:

LocalAccountTokenFilterPolicy

Office Pro 2003 - Insert Original installation Disk - can't find SKU111.cab

Old post, but had to wade through a bunch of Google to find it...Thank you Rajalakshmi for solving an age old problem

original post here:  http://en.kioskea.net/forum/affich-4751-sku011-cab

Rajalakshmi Aug 2, 2008 4:21pm BST
To solve this problem
Solution below:

Regedit (start menu -> run -> type regedit)

Expand HKEY_LOCAL_MACHINE -> Software -> Microsoft -> Office -> 11.0 -> Delivery

There should be only 1 directory under Delivery, which is your DownloadCode (mine was 90000409-6000-11D3-8CFE-0150048383C9). Select that directory. On the right side of the screen, right-click on CDCache. Change the value to 0.

block bad bots in htaccess

for bot with user string '*bot' or 'bot*'

#### rewrites to 403 for nastybots ####

RewriteCond %{HTTP_USER_AGENT} ^bot\* [NC]

RewriteRule .* - [F,L]

RewriteCond %{HTTP_USER_AGENT} ^\*bot [NC]

RewriteRule .* - [F,L]

#### end nasty ####

windows 2008 r2 - I/O error backing up to external drive

Basically there are two things that could be causing your backup to fail if it is a removable HD.  I am going to save you the trouble of reading this whole thread and catch you up. 

1.     Your removable HD has bloatware (crapware, extra software, custom bios, etc etc…) that prevents windows from seeing it for what it should be (a removable HD). When you plugged your disk in did you also get a new CDROM drive also?  Did you install some special software in order to get to the disk?  Encryption software maybe?  Your disk is not going to work.  Stop reading any further and return it.  Don't feel bad.  Chances are you didn't know it was going to be that way and the manufacturer did a poor job of telling you about it before you purchased it. Return your drive and go to this site where there is a nice list developing that tracks disks that have been tested:  http://social.technet.microsoft.com/wiki/contents/articles/1780.aspx

 

2.     Your disk has more than 512 bytes per physical sector.  If it new and large (like 1TB or more) it probably has 4096 bytes per physical sector.  The windows backup software was designed to work with disks that have 512 bytes per physical sector.  Again, don't feel bad about getting the wrong disk.  I did a quick check of about 10 disks online and couldn't find a single one where the manufacturer listed the bytes per physical sector in the specs anywhere.  Also, until you have this problem, you will probably never know about the 512 byte design issue. 

Anyhow, now that you do know about it, you can try to fix it using the Microsoft hotfix here: http://support.microsoft.com/kb/982018 which adds support for 4096 byte disks to server 2008 and 2008 R2 (and any SBS versions based on them).  Once the hotfix is applied and you reboot, try assigning the removable HD a drive letter and formatting it.   Once that is done you can check to see if the disk is going to work by using fsutil.  Here is an example showing the command line and the result:

C:\Users\administrator>fsutil fsinfo ntfsinfo f:
NTFS Volume Serial Number :       0x2ebc529bbc525d81
Version :                         3.1
Number Sectors :                  0x000000000e8b4eff
Total Clusters :                  0x000000000e8b4eff
Free Clusters  :                  0x000000000e8aa566
Total Reserved :                  0x0000000000000000
Bytes Per Sector  :               4096
Bytes Per Physical Sector :       <Not Supported>
Bytes Per Cluster :               4096
Bytes Per FileRecord Segment    : 4096
Clusters Per FileRecord Segment : 1
Mft Valid Data Length :           0x0000000000100000
Mft Start Lcn  :                  0x00000000000c0000
Mft2 Start Lcn :                  0x0000000000000002
Mft Zone Start :                  0x00000000000c0000
Mft Zone End   :                  0x00000000000cc820
RM Identifier:        42643033-B240-11E0-9765-3C4A92E16BD6

You see where it says "Bytes Per Physical Sector:" and the result was "<Not Supported>"?  That means this disk will not work with the backup even though the hotfix is installed.  Some disks don't report their bytes per physical sector correctly and therefore won't work.   If you get one that does report 512 or 4096 you should be OK.    

Btw, if you do find one that works, be kind and add it to the list of drives here: http://social.technet.microsoft.com/wiki/contents/articles/1780.aspx with a comment about your test setup and results.

error page to some other page in joomla

My pad: Redirect error page to some other page in joomla: Error page redirect with home page/ custom message give your site more professional than normal joomla site. In joomla we can set via a sin...

Fix Shockwave Crashes in Chrome

It's important to know that the warning has nothing to do with with Adobe Shockwave, which is a separate program/multimedia system from Adobe Flash. To figure out if a Flash conflict is the source of your problems, open your Chrome Web browser, and then in the address bar, type about:plugins. After you press enter, you'll see a list of all the plug-ins installed in Chrome. Look through the list for the Flash entry. If the entry looks like Flash (2 Files), this may indicate that the source of your Flash-related crashes is a conflict between the two files. Of course, you'll want to disable one of these files to ensure that, moving forward, Chrome only utilizes one of these files when it needs to use Flash.

To do this, start by expanding the details of these files by toggling the label [+] Details, found in the upper right-hand corner of the browser window. By clicking on this label, you can expand the entries for all the plug-ins. Then choose the entry for Flash. After selecting Flash, you'll see two entries for Flash: one for the internal Chrome installation, and one for the host OS's installation. We suggest disabling the link for Chrome's internal installation to make sure you don't encounter any future crashes. To do this, click on the Disable link for Chrome's internal installation of Flash. (Just make sure you disable the file located in Chrome's AppData folder and not the separate stand-alone Flash installation).

After you disable Chrome's installation of Flash, close the tab and then close Google Chrome. You should then restart Chrome and and to make sure everything is working normally, visit Adobe's test page. Just keep in mind that you'll no longer be getting automatic updates with each Chrome upgrade; check for updates at Adobe's Flash download page to update Flash regularly.

remove "Sent from my iPhone" from mail to blog post

Sure you could do this in your mobile account or on your phone, but if you don't have that option...add to template.

<script language="javascript">

document.body.innerHTML = document.body.innerHTML.replace( /Sent from my iPhone/g, "");

</script>

enable mapped drives in windows 7 or vista

On Windows Vista when you map a drive under your admin account you will find that your mapped drive is not available after you switch to your full token via a RunAs or Consent dialog. This is by design because there are actually two tokens in play here. What happens is the LSA recognized that you are admin at logon and creates two logons. The first with a "filtered" token or non-admin which is used to render your desktop and the other containing your full token to be available after consent dialogs. 

Because there are two separate logons there are separate logon ID's.  When network shares are mapped they are linked to the current logon session for the current process token. Meaning you don't have access to the network drive from the alternate logon. This can come into play with logon scripts and a number of other areas where you may require access to a network share from both tokens.

If you set the following key it will change how SMB shares are mapped. They will be mapped to a token, which means that LSA will check to see if there is a linked token associated with the user session and add the network share to that location as well. Basically all of this means that after setting this drives will be accessible from both tokens no matter which they are mapped under.

Disclaimer: This is not supported by Microsoft and was never tested. Use at your own risk.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
EnableLinkedConnections = 1 (DWord)