Windows XP -> reset admin pw

On client site I needed to reset the administrative pw of a windows XP box. I used to use a bootable CD w/the chntpw program designed to run on startup, but I didn't have it handy. Here's the steps I followed to reset the pw.

1. Download the bits for the PLD Rescue CD
   
2. boot w/the CD/DVD
3. #mkdir -p /mnt/win
4. #modprobe fuse
5. #ntfsmount /dev/sda2 /mnt/win
6. #cd /mnt/win/WINDOWS/system32/config
7. #chntpw SAM SYSTEM SECURITY
   
1. follow the prompts (defaults worked for me) to blank the Administrator pw
2. Prompts can be confusing -> enter "*" to blank the password (vs. leave blank). You will get a confirmation that the pw is being blanked.
   
8. #shutdown -h now
9. boot into XP and log in as Administrator w/o a pw

Starting w/the Wizard

Last week I met Kurt Stam at a JBoss ESB class and had the chance to get a walkthrough on patch submittals.... Here's what I learned:

1. Start w/the JBoss IDE (I didn't but it may save you time|trouble if you do)
2. Check out the module your wanting to play w/for me it was: http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/tools/esbwizard
3. Modify the build.properties file so that your changes to source code will be available when you debug your changes as a plugin:
1. Use the Plug-in Manifest editor (right click the plugin.xml file -> Open With -> Plug-in Manifest Editor | or double click if the file association already exists) and make the changes in the classpath area on the runtime tab or edit the build.properties file by hand. Either way you will be adding the projects bin directory to bin.includes entry in the build.properties file.
4. Make your changes to the code.
5. When your ready to see how it behaves then run it as an eclipse application
1. Right click project -> run as -> eclipse project

Pushing the (supposed) patch to the people who need to see it was also easy.

1. If you don't have one create a Jira account at:
   
• create one
  
2. Create a bug... I left everything default (except the summary and the details) and they knew what to change.
3. Create a patch file...
• Right click project -> Team -> Create Patch
• This will create a text file that the developer can apply to their project... don't worry about the absolute file names if you go to check out the resultant patch. There's an option when applying the patch to disregard x leading designators.
4. Browse your bug in jira and attach the patch file.
5. Wait to get told what you broke.
   

Anyway, it's a fun start. I'd love to know if this actually helps anyone.