Prerequisites:

The printer needs some settings set first.  Log into the printers UI using a web browser and set these settings:

1. NETBIOS name 1 – Must be blank
2. Printer class – PCL/PC Kit

Instructions:

1. Download and install the Xerox Global Print Driver for Windows 7 x64
2. Follow the isntructions to install the printer (eg: enter the IP address, give it a name, choose the Xerox driver, etc)
3. Once installed, under “Devices and Printers” right click the printer and select “Printing Preferences”
4. Under “Paper/Output” tab, change “Ouput Color” to “Black and White”
5. Under “Advanced” tab -> “Document Options” -> “Image Options”, change the “Graphics Mode” to “Raster”
6. Apply that change
7. Right click the printer again in “Devices and Printers” and select “Printer Properties”
8. Go to the “Advanced” tab
9. Uncheck “Enable advanced printing features”
10. Click the “Print Processor” button
11. Select winprint -> NT EMF 1.003 (NOTE THIS MAY NOT BE REQUIRED.  TRY WITHOUT FIRST)

1. Download and install VisualSVN Server version 1.6. It’s very important to install version 1.6 for the purposes of the migration. This version is very old but is required for the VSS2SVN application. VisualSVN luckily make all previous versions available so this is very handy.
2. Download and install VSS2SVN.
3. Make a copy of your SourceSafe database. This is the directory where VSS has been storing all your revision data. In this directory will be a file called “srcsafe.ini”. Don’t work with the original unless you like taking risks.
4. Open the VisualSVN Server interface.
5. Select “Create new user”
6. Create a user account for yourself
7. Right click on “Repositories” and chose “Create New Repository…”
8. Enter a name corresponding to the name of the project you are migrating. Select “Create default structure”.
9. I don’t get it and I don’t know why, but you must set a pre-revision property change hook. Right click your repo and choose “Properties”. Go to the “Hooks” tab, click “Pre-revision property change hook” and click “Edit”. In the textbox enter: exit /b 0
10. Now we need to analyse your VSS repo becuase most of the time there are corruptions and VSS2SVN wont work if thats the case. From the command line enter:
    • "C:\Program Files\Microsoft Visual SourceSafe\analyze.exe" -F -V3 -D "c:\path\to\your\copy\of\the\sourcesafe\database\'data'\directory"
11. If that step fails, your VSS database might be too corrupt to migrate (or even use)
12. Check out a working copy of the Subversion repository you just created. From the command line enter:
    • "C:\Program Files\VisualSVN Server\bin\svn" co http://<HOSTNAME>/svn/<REPO NAME>/trunk/ c:\path\to\working\copy
13. Now open VSS2SVN. Enter the following settings:
    1. Path to Scrsafe.ini: Enter the path to srcsafe.ini in your copy of the VSS database you made
    2. Username: The username you created in VisualSVN
    3. Password: The password you chose when creating the user in VisualSVN
    4. VSS project to use: Enter a dollar symbol ($) followed by a backslash (\) followed by the name of your VSS project as can be found using the Visual SourceSafe Explorer that comes with VSS. Eg: $\MyProject
14. Click “Find files in source safe”. If you get an error saying a weird file like nbaaaaaa.b was not found, your VSS repo is probably corrupt and you need to run the analyse tool as mentioned above.
15. For “Working Directory” enter the path to your Subversion working directory you created when checking out above.
16. For “SVN path to use” enter URL of the trunk of your Subversion repositiory you created. Eg: http://<HOST NAME>/svn/repos/<REPO NAME>/trunk/
17. Click “Migrate to subversion”
18. Sit back; it might take a while

After you’ve migrated all your projects, it would advisable to upgrade your VisualSVN and Subversion.

http://www.bx.com.au/tools/ultimate-php-error-reporting-wizard

Super Mario Bros on guitar – 80s metal style!

http://trend.bz

0499 999 999

If you out that into an Outlook contact record, it will most likely format it in another stupid way.

You can stop Microsoft Outlook from automatically formatting phone numbers in Windows 7 by:

1. Clicking “Start” and search for “dialing rules”
2. Select “Set up dialing rules”
3. Edit the entry for “My location”
4. Set the area code to 1
5. Click ok twice

Outlook will stop formatting phone numbers.  It’s a similar procedure on Windows Vista and XP.

For example, if you are using Notepad:

1. Click File -> Save As
2. Enter the filename as: ".htaccess" (with the double quotes)

For example, to protect “secret.php” using basic auth:

AuthType Basic
AuthName "Authorised users only"
AuthUserFile /path/to/user/file
AuthGroupFile /path/to/group/file
<files secret.php>
Require user xxxx
</files>
 

if(Page_ClientValidate())

From: http://alvinzc.blogspot.com/2006/10/aspnet-requiredfieldvalidator.html