Gokul's Blog

Leave a comment

Change External Hard Drive Letter

  1. Open Computer Management (Local).
  2. In the console tree, click Disk Management.
  3. Right-click a partition, logical drive, or volume, and then click Change Drive Letter and Paths.
  4. Do one of the following:
    To assign a drive letter, click Add, click the drive letter you want to use, and then click OK.
    To modify a drive letter, click it, click Change, click the drive letter you want to use, and then click OK
  5. To open Computer Management, click Start, and then click Control Panel. Double-click Administrative Tools, and then double-click Computer Management.

Leave a comment

A Blogging website in 10 minutes

My Pre-Requisites

1. Blog Engine shouldn’t use a database (SQL, MY SQL, Access,etc)
2. Should be built using .Net, free, easy to setup and maintain.
3. Integrate with Windows Live Writer

As I had used Das Blog before because it uses XML as the data-store I thought of giving it a try.

Bingo! It just took me 10 minutes to get it installed and start blogging. And in 15 minutes I was ready to post my blog from Windows Live Writer.

Here are the steps to how I got it done.

Setup DasBlog

1. Goto http://www.dasblog.info/. Download the (dasBlog 2.0.7226.0) related file from source forge following this Download link (or) follow the download instructions from DasBlog site to download the latest version.

2. Follow the instructions from this website (http://dasblog.info/SetupInstall.aspx). (or) follow this instructions taken from dasblog.info site

1. Copy files
Copy all files into your "dasblogce" folder or IIS site root keeping the folder structure intact.
2. Important Pemissions & configuration files:
* On IIS 5.0 (Windows 2000), the account used to execute web applications (IWAM_xxx) needs read/write permissions to the content, siteconfig, and logs subdirectories. 
* The ASP.NET worker process identity, usually “{machinename}\ASPNET” on IIS5.0 (Windows 2000 and Windows XP) or “NETWORK SERVICE” on IIS 6.0 (Windows Server 2003) also need read/write access to the content, siteconfig, and logs subdirectories. 
* Go to the siteConfig directory in (likely in c:\inetpub\wwwroot\{sitename}) and open the site.config file. In that file, change the settings (quite obvious when you look at them). The most important change is to set the <Root> value to the proper URL for your weblog
* Open the siteSecurity.config in the same directory and set up your own account with a proper password.

3. Once done you are all set to post your first blog.

Integrating with Windows Live Writer

Scott HanselMan is our hero. He has done all the hard work for us to integrate the Windows Live Writer to DasBlog.
Follow this link for how to do it http://www.hanselman.com/blog/WindowsLiveWriterBeta2DasBlogAndTheCustomizationAPI.aspx

Simple Steps:

1. Download the manifest zip file from "Windows Live Writer DasBlog Integration"
2. Unzip the contents to the Root Folder
3. Open Windows Live Writer and give the Root Url of the blog, then follow the Live writer wizard.

We are all set to post your blog!

Leave a comment

Using Visual Studio “Build Events” scripts to facilitate development

Exposing a pipeline component assembly to the Pipeline Designer with Visual Studio requires copying pipeline component assemblies to the Pipeline Components folder. You can automate this task by taking advantage of the Visual Studio “Build Events” functionality. The following steps explain this procedure.
  1. Inside Visual Studio, right-click the pipeline component project, and then select properties.
  2. In the properties window, select “Build Events” from the left-side navigation pane.
  3. Click the “Edit Post-build” button, and then insert the following script in the “Post build event command line” window. If you want to GAC the assembly make sure its signed or else remove the lines (3, 4) part below in the script
   1:  IF $(ConfigurationName) EQU Release GOTO done 
   3:  call "C:\Program Files\Microsoft Visual Studio 8\VC\vcvarsall.bat" 
   4:  gacutil /if $(TargetPath) /nologo 
   6:  xcopy "$(ProjectDir)$(Outdir)$(TargetFileName)" "C:\Program Files\Microsoft BizTalk Server 2006\Pipeline Components" /R /Y /F 
   8:  IF %ERRORLEVEL% EQU 0 GOTO done 
  10:  net stop "BizTalk Service BizTalk Group : BizTalkServerApplication" 
  12:  iisreset 
  14:  xcopy "$(ProjectDir)$(Outdir)$(TargetFileName)" "C:\Program Files\Microsoft BizTalk Server 2006\Pipeline Components" /R /Y /F 
  16:  net start "BizTalk Service BizTalk Group : BizTalkServerApplication" 
  18:  :done 

.csharpcode, .csharpcode pre
font-size: small;
color: black;
font-family: consolas, “Courier New”, courier, monospace;
background-color: #ffffff;
/*white-space: pre;*/
.csharpcode pre { margin: 0em; }
.csharpcode .rem { color: #008000; }
.csharpcode .kwrd { color: #0000ff; }
.csharpcode .str { color: #006080; }
.csharpcode .op { color: #0000c0; }
.csharpcode .preproc { color: #cc6633; }
.csharpcode .asp { background-color: #ffff00; }
.csharpcode .html { color: #800000; }
.csharpcode .attr { color: #ff0000; }
.csharpcode .alt
background-color: #f4f4f4;
width: 100%;
margin: 0em;
.csharpcode .lnum { color: #606060; }

This removes the need to manually copy the assembly to the “Pipeline Components” folder every time And also stopping and restarting of BizTalk host instances and IIS.


With BizTalk Server 2006 Custom Pipeline components can be placed in GAC. Key can be generated using the command  ">sn -k MykeyFilename"

Refer this link for more information: http://geekswithblogs.net/sthomas/archive/2006/09/27/92513.aspx

Leave a comment

Change Windows XP License Key


‘ WMI Script – ChangeVLKey.vbs

‘ This script changes the product key on the computer



if Wscript.arguments.count<1 then
Wscript.echo "Script can’t run without VolumeProductKey argument"
Wscript.echo "Correct usage: Cscript ChangeVLKey.vbs ABCDE-FGHIJ-KLMNO-PRSTU-WYQZX"
end if

VOL_PROD_KEY = Wscript.arguments.Item(0)
VOL_PROD_KEY = Replace(VOL_PROD_KEY,"-","") ‘remove hyphens if any

for each Obj in GetObject("winmgmts:{impersonationLevel=impersonate}").InstancesOf("win32_WindowsProductActivation")

result = Obj.SetProductKey (VOL_PROD_KEY)

if err <> 0 then
WScript.Echo Err.Description, "0x" & Hex(Err.Number)
end if



Save the above content as a .vbs file and run as follows:

”’ Usage c:\changevlkeysp1.vbs ab123-123ab-ab123-123ab-ab123

Refer this article for more information http://support.microsoft.com/kb/328874