''Backup the Master Boot Record''\n\nSince we are using a potentially dangerous tool to backup the master boot record, first we want to backup the partition table in an easily readable format so we can rewrite the partition table in case of accidental overwriting.\n\n[root@knoppix /home/knoppix/tmp/thirdpart] sfdisk –d /dev/sda >partitiontable\n\nYou can now open the file, ‘partitiontable’ in any text editor and see how the disk was partitioned. Hopefully you will never look at this file. Now backup the master boot record:\n\n[root@knoppix /home/knoppix/tmp/thirdpart] dd if=/dev/sda of=sdambr.mbr count=1\n\nThis will create a file that is a copy of the first sector of the first hard drive. To restore the master boot record later:\n\n[root@knoppix /home/knoppix/tmp/thirdpart] dd if=sdambr.mbr of=/dev/sda count=1\n\nTo restore only the partition table later:\n\n[root@knoppix] dd if=sdambr.mbr of=/dev/sda bs=1 skip=446 seek=446 count=64\n\nThe last two bytes (511 and 512) of the first sector are always ‘55’’AA’ in hexadecimal. \n\nTo restore only the boot code later:\n\n[root@knoppix] dd if=sdambr.mbr of=/dev/sda bs=1 count=440\n\nWhen you restore your master boot record or partition table you are restoring the state when you copied it! So be sure you are comfortable with the hiding scheme and which partition is marked active or be sure to alter them as necessary after you restore it before booting. If you use a boot manager, this should not be a problem – hopefully the boot manager has the ability to alter these items before booting. \n\nIf you installed and tested the boot manager previously you may now want to backup the partition containing the boot manager. The filesystem the boot manager uses does not matter; the dd command operates at the disk level.\n\n[root@knoppix /home/knoppix/tmp/thirdpart] dd if=/dev/whatever | gzip-c > bootmgr_part.img.gz\n\nTo restore:\n\n[root@knoppix /home/knoppix/tmp/thirdpart] dd if=bootmgr_part.img.gz | gunzip –c > /dev/whatever\n\nIf you alter your master boot record (install another bootloader) or the partition table (changing the partitioning scheme) be sure to create another backup of the new master boot record and/or partition table!\n\nNow you have an easily readable partition table, a backup of your master boot record, which includes your partition table, an image of your ntfs filesystem, and possibly, a copy of the boot manager partition. If you put these items on a dvd – you can completely screw up your computer and always get back to a perfect working environment without any worry! But…\n\nYour clone or image file is ''absolutely useless'' until you have restored it and verified everything works appropriately and you can repeat the process! So on to the restore process.\n
''The Basic Idea''\n\nInstall xp on the primary partition #1. Install all drivers, programs and everything else… make it perfect. Clone it to an image file on the logical partition and restore that image onto primary partition #2 (or direct clone to primary partition #2 - either works). Be able to boot into either primary partition and each will be its own separate environment and both will have access to all important files on extended logical partition. If one partition is completely broken - restart and boot into the other and be working again as fast as a restart. Restore the broken partition back to its pristine state and boot into it later at your convenience.\n
''Before Getting Started''\n\nI will begin with the obligatory plead - ensure you have backups of all important files - off working computer backups are preferred! You have heard them before: an ounce of prevention is worth a pound of cure and haste makes waste, these old sayings ring true and take on more weight in a more sensitive computing environment that comes with cloning and multi-booting. Plan Ahead! Know you constraints! For example:\n\n*Oh, I can’t put that 5gb image file on that old fat partition, size issues…\n*Oh, this particular operating system must be booted from a primary partition, which leaves me only two primary partitions hmm…\n*Oh, I can use ntfsclone with my samba server that makes planning easier…\n*Oh, my boot manager can be installed anywhere even in a hidden logical partition just like Xosl. That saves a primary partition. How does that alter my partitioning scheme?\n\nAn explanation of my system is necessary so you may have some clues as to why something works for me, but might not in your case. Also, I’m sure some statements in this guide are not entirely correct and this may help explain things and/or highlight why my viewpoint was limited.\n\nFor this guide: I have two primary partitions (yellow) each exactly the same size and an extended logical partition (blue).\n\n\n|>|>| Unused space 7.8MiB |\n|>|>|bgcolor(#FFFF00): First Primary Partition |\n|>|>|bgcolor(#FFFF00): Second Primary Partition |\n|>|>|bgcolor(#0066FF): The Extended <br> Logical Partition |\n|>|>| Bootmanager |\n\nThe table above is just a quick work around. Not to scale.\n\nYou should understand how xp assigns drive letters. In this case, only one primary partition will be booted at once and the other(s) will be hidden. This way, no matter what partition is booted the xp operating system on that partition will always see itself as c:\s and the extended logical partition, if not hidden, as d:\s. It does not matter which partition you decide to install xp on, each partition in this guide is meant to function independently of others and always be seen as the c:\s drive in xp – because the active partition will always be the first non-hidden primary partition on the computer – even on a two hard drive system. \n\nI put all files not associated with the running of my operating system on a separate partition. I keep all documents, audio, video, software install files, images etc… in an extended logical partition. I use the primary partitions for independent xp installations. If your operating system melts down you can just delete and restore and be back to when you last cloned in minutes – you lose nothing! All important files are fine and you have all your software install files so you can easily re-install new programs since last clone. Or if you are multi-booting the primary partitions just restart and boot into one of the other partitions – as fast as a restart and you are working again! A good boot manager is a necessity. I use Xosl. It allows me to completely customize how I would like to boot each partition – even different ways to boot the same partition. I can save sets of all those settings as ‘boot items’ and easily select any one of those ‘boot items’ at startup! It applies the settings and then passes control to the bootsector of the partition selected. It also works well with other boot managers too and other instances of itself – I guess – multi-bootmanaging. \n
''Best Practices Before Cloning''\n\nBefore we clone we still have some critical steps to execute while we are still in xp.\n
''Clean the Partition''\n\nYou can run Disk Cleanup or any similar utility. I prefer ~CCleaner - the program has worked really well for me in the past. It locates and can delete all sorts of unnecessary files, as well as, clean the registry. You can accept the default settings, allow it to operate and delete everything it finds, or fix the registry issues it discovers without much worry.\n
''Cloning Options''\n\nIn the following sections I refer to commands ntfsclone and ntfsresize. I don’t go into specifics at this point, but basically they perform just as their names imply. One important note, they operate on the filesystem, not the device (partition)! Usually, these terms are confused and often spoke of as if they are the same because the most common situation is a filesystem with the same size as the device (partition). For example, if you use ntfsresize to shrink a “partition” you are actually shrinking the filesystem. The partition will be the same size as it was before. If you boot into xp after shrinking using ntfsresize, xp will only see itself as large as the filesystem, not the partition, which will have unused space that is not part of the filesystem. You must use a partitioning tool to modify devices (partitions). I confess to the same potentially confusing use of terms occasionally. Therefore, please be aware when I state “resize the partition” within the context of ntfsresize, this refers to resizing your filesystem only and not the device (partition). If you use Gparted, QTparted, or Partman to “resize the partition” you should realize these tools resize both the filesystem and the device (partition)! Ntfsresize is used internally with these partitioning tools.\n\nThis is taken directly from the linux-ntfs.org website:\n\n>Ntfsclone will efficiently clone (copy, save, backup, restore) or rescue an ntfs filesystem to a sparse file, image, device (partition) or standard output. It works at disk sector level and copies only the used data. Unused disk space becomes zero (cloning to sparse file), encoded with control codes (saving in special image format), left unchanged (cloning to a disk/partition) or filled with zeros (cloning to standard output).\n\nThis guide will focus on the second and third methods of cloning:\n\n*To an image file (essentially, your entire partition and all files into a single file).\n*Directly to another device or partition (direct clone)\n\nI sometimes default to speaking in term of ‘cloning to an image’ and ‘restoring from image’ because this is my preferred method. Both work equally well. The image file method has a few advantages:\n\n*You can apply compression to that file.\n*You can burn it to dvd for an off computer backup.\n*You can keep a bunch of image files on your hard drive(s) or network for quicker and more flexible restoring.\n
''Cloning XP''\n\nBoot the Linux live cd/dvd.\n\nOpen a root shell. You may have to type “su” at the command prompt.\n\nknoppix@knoppix: su\nroot@knoppix: /ramdisk/home/knoppix:\n\nAt this point, we installed xp on the first primary partition. The filesystem and device (partition) size are the same. If you expect to clone to or restore to other partitions that are:\n\n*Equal or larger in size then no resizing is necessary now. Skip to next paragraph.\n*Smaller than the current partition size, but (obviously) larger than the actual space used in the partition plus a small buffer, then you should use ntfsresize at this point before cloning. \n\n>[root@knoppix] ntfsresize –i –n /dev/sda1\n\n>This will just provide info (-i) and take no action (-n). It will provide the theoretical lower limit for resizing. Add at least 250MB to the theoretical lower limit when resizing.\n\n>[root@knoppix] ntfsresize –s 11000M -n /dev/sda1\n\n>This will also take no action (-n) – it just performs a dry run to see if everything would resize (-s 11000M) successfully. I am assuming the example provided earlier in the resizing section, 25GB partition, 10GB used. In this command I am resizing to 11,000MB I could have substituted 11G for the 11000M in the command, makes no difference. Now for the real thing:\n\n>[root@knoppix] ntfsresize –s 11G /dev/sda1\n\n>Now my filesystem is 11GB and is located in a partition 25GB in size.\n\nNow we are ready to clone. Again, there are many ways to accomplish this and you can have fine grain control over the process if you get familiar with the commands. The explanations and methods were designed for the less experienced. We can clone to an image file and restore from that file to another partition or clone directly to another partition. \n\nContinuing with the assumed partitioning scheme for this guide, to clone to an image file and store that image on the extended logical partition:\n\nFirst mount the partition you wish to save the image file to; assuming this partition is formatted ntfs:\n\n[root@knoppix] cd /home/knoppix/tmp\n[root@knoppix /home/knoppix/tmp] mkdir thirdpart\n\n[root@knoppix] mount –t ntfs-3g /dev/sda3 /home/knoppix/tmp/thirdpart\n\nRun the cloning command:\n\n[root@knoppix /home/knoppix/tmp/thirdpart] ntfsclone –s –o sda1.img /dev/sda1\n\nThis will save the entire ntfs filesystem on the first partition in a special image format; the file ‘sda1.img’ is located on the extended logical partition. The image will be roughly the size of the files in that partition ~ 11GB.\n\nTo clone to a compressed image file:\n\n[root@knoppix /home/knoppix/tmp/thirdpart] ntfsclone –s –o – /dev/sda1 | gzip | - sda1.img.gz\n\nThe same result as above, but the file ‘sda1.img.gz’ may be ~ 6GB.\n\nTo split the compressed image file into pieces to save to a device with restrictions (dvd, filesystem):\n\n[root@knoppix /home/knoppix/tmp/thirdpart] ntfsclone –s –o - /dev/sda1 | gzip | split –b 4500m – sda1.img.gz_\n\nThe same result as above, but now you will have two files, ‘sda1.img.gz_aa’ and ‘sda1.img.gz_ab’ the first will be ~ 4.5GB and the second ~ 1.5GB.\n\nOr, clone directly to another partition:\n\n[root@knoppix] ntfsclone """--overwrite""" /dev/sda2 /dev/sda1\n\nThis command will clone the ntfs filesystem on the first partition on the first hard drive and write it to the second partition on the first hard drive. Notice the order – overwrite the second with the first – may be odd to some, but be certain to have these correct! It’s obvious how dangerous this can be if you do not specify these correctly! As with many commands you can use the shortcut –O or you can use the longhand """--overwrite""", notice that the shortcut for """--overwrite""" is actually capital -O not lowercase -o (which does something different).\n\nSee the man pages for ntfsclone. They have many examples of what is possible - saving to a remote host via ssh, restoring from a webserver, or saving to a samba server. \n\nI would also recommend backing up your master boot record as well. \n
''Cloning to Different Computers''\n\nThis method will work for direct cloning and restorations from images created from the same computer. Otherwise, you will likely run into either HAL errors or your operating system will show you the beautiful blue screen of death. It is possible to create a hardware neutral clone, or even several clones with different HAL’s, but both are beyond the scope of this guide.\n
Background: #fff\nForeground: #000\nPrimaryPale: #8cf\nPrimaryLight: #18f\nPrimaryMid: #04b\nPrimaryDark: #014\nSecondaryPale: #ffc\nSecondaryLight: #fe8\nSecondaryMid: #db4\nSecondaryDark: #841\nTertiaryPale: #eee\nTertiaryLight: #ccc\nTertiaryMid: #999\nTertiaryDark: #666\nError: #f88\n\n\n*@@bgcolor(#fff): #fff - Background@@\n*@@bgcolor(#000): #000 - Foreground@@\n*@@bgcolor(#8cf): #8cf - Primary Pale@@\n*@@bgcolor(#18f): #18f - Primary Light@@\n*@@bgcolor(#04b): #04b - Primary Mid@@\n*@@bgcolor(#014): #014 - Primary Dark@@\n*@@bgcolor(#ffc): #ffc - Secondary Pale@@\n*@@bgcolor(#fe8): #fe8 - Secondary Light@@\n*@@bgcolor(#db4): #db4 - Secondary Mid@@\n*@@bgcolor(#841): #841 - Secondary Dark@@\n*@@bgcolor(#eee): #eee - Tertiary Pale@@\n*@@bgcolor(#ccc): #ccc - Tertiary Light@@\n*@@bgcolor(#999): #999 - Tertiary Mid@@\n*@@bgcolor(#666): #666 - Tertiary Dark@@\n\n\n\n/* my added colors */\n\nPaleWeakBlue: #ccf\nPaleDullBlue: #99f\nLightWeakBlue: #99c\nLightDullBlue: #66c\nLightFadedBlue: #66f\nMediumWeakBlue: #669\nMediumFadedBlue: #66c\nDarkDullBlue: #339\nDarkWeakBlue: #336\nBlueGrayOne: #6f6aa2\nBlueGrayTwo: #625e8f\nBlueGrayThree: #53507a\nBlueGrayFour: #7d7a9e\nHightlightYellow: #fe8\n\n\n*@@bgcolor(#ccf): #ccf - Pale Weak Blue@@\n*@@bgcolor(#99f): #99f - Pale Dull Blue@@\n*@@bgcolor(#99c): #99c - Light Weak Blue@@\n*@@bgcolor(#66c): #66c - Light Dull Blue@@\n*@@bgcolor(#66f): #66f - Light Faded Blue@@\n*@@bgcolor(#669): #669 - Medium Weak Blue@@\n*@@bgcolor(#66c): #33c - Medium Faded Blue@@\n*@@bgcolor(#339): #339 - Dark Dull Blue@@\n*@@bgcolor(#336): #336 - Dark Weak Blue@@\n*@@bgcolor(#6f6aa2): #6f6aa2 - BlueGrayOne@@\n*@@bgcolor(#625e8f): #625e8f - BlueGrayTwo@@\n*@@bgcolor(#53507a): #53507a - BlueGrayThree@@\n*@@bgcolor(#7d7a9e): #7d7a9e - BlueGrayFour@@\n*@@bgcolor(#fe8): #fe8 - Highlight Yellow@@\n
[[Using this Wiki / Webdocument]]\n[[Introduction]]
''Defragment the Partition''\n\nThis is optional. It may speed things up; mainly to keep things clean and orderly. You can do this while in xp or while in the Linux live environment before cloning.\n
Most commercial products designed for the cloning and multi-booting world actually only focus or operate upon a small part of the overall puzzle needed to complete the entire process properly and absolutely none of them tell you how to properly multi-boot let alone with multiple drives. Their manuals are poorly written and usually vague about important subjects!\n\nWell I hope you finally got the whole picture! You won't know how wonderful this method of cloning and backing up is unless you have attempted to do this with similar commercial products... I show you how to do it with completely free software - don't waste money or your time with their commercial counterparts! Consider donating to those who wrote the software or to me for this guide. ; ) which frankly there aren't enough //good// ones out there. If you have specific non-basic questions, suggestions, or constructive criticism, and don't mind waiting, kidclone at google's free email system.\n\n<html>\n<div>\n<form action="https://www.paypal.com/cgi-bin/webscr" method="post">\n<input type="hidden" name="cmd" value="_s-xclick">\n<input type="image" src="https://www.paypal.com/en_US/i/btn/x-click-but21.gif" border="0" name="submit" alt="Make payments with PayPal - it's fast, free and secure!">\n<img alt="" border="0" src="https://www.paypal.com/en_US/i/scr/pixel.gif" width="1" height="1">\n<input type="hidden" name="encrypted" value="-----BEGIN PKCS7-----MIIHTwYJKoZIhvcNAQcEoIIHQDCCBzwCAQExggEwMIIBLAIBADCBlDCBjjELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAkNBMRYwFAYDVQQHEw1Nb3VudGFpbiBWaWV3MRQwEgYDVQQKEwtQYXlQYWwgSW5jLjETMBEGA1UECxQKbGl2ZV9jZXJ0czERMA8GA1UEAxQIbGl2ZV9hcGkxHDAaBgkqhkiG9w0BCQEWDXJlQHBheXBhbC5jb20CAQAwDQYJKoZIhvcNAQEBBQAEgYCGYqhf56kxuu1UYb/Cah2ME44djDApYDzhjFibodEmFEdRLiNhOHfhsm7BulyWximr27RE3JX/CaY2G0muH6gSUZeVYWJfma1f4VqVsTZ1NqZgzfUOw4btUcl6FIpZZ/pa5ZNRwrV3DqUhbj+h73gO8LtKr3u+Sla46SssW5dfajELMAkGBSsOAwIaBQAwgcwGCSqGSIb3DQEHATAUBggqhkiG9w0DBwQI8x7ScV+3+ASAgaiZBH/wlH5mmW9A5FCMl1u0dsgrWNOrU0wID+XkMhfbjT21i8EUrKWPwlRokhhFiXkmdvdomiWtjHV757fNKTDeQxZft3e2wPx8UIm2DTjU1z72VlIPWezrGsIpAeJiEkV0khYHt61gGlwvyM5q5xeJ4H7EBB9zfUEGWe6rGIlInyMdRjkSaKxfSaMPqbiEPqQIIwBmNnEo2SxwWwUHpm1uAJrLnBnwhbmgggOHMIIDgzCCAuygAwIBAgIBADANBgkqhkiG9w0BAQUFADCBjjELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAkNBMRYwFAYDVQQHEw1Nb3VudGFpbiBWaWV3MRQwEgYDVQQKEwtQYXlQYWwgSW5jLjETMBEGA1UECxQKbGl2ZV9jZXJ0czERMA8GA1UEAxQIbGl2ZV9hcGkxHDAaBgkqhkiG9w0BCQEWDXJlQHBheXBhbC5jb20wHhcNMDQwMjEzMTAxMzE1WhcNMzUwMjEzMTAxMzE1WjCBjjELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAkNBMRYwFAYDVQQHEw1Nb3VudGFpbiBWaWV3MRQwEgYDVQQKEwtQYXlQYWwgSW5jLjETMBEGA1UECxQKbGl2ZV9jZXJ0czERMA8GA1UEAxQIbGl2ZV9hcGkxHDAaBgkqhkiG9w0BCQEWDXJlQHBheXBhbC5jb20wgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAMFHTt38RMxLXJyO2SmS+Ndl72T7oKJ4u4uw+6awntALWh03PewmIJuzbALScsTS4sZoS1fKciBGoh11gIfHzylvkdNe/hJl66/RGqrj5rFb08sAABNTzDTiqqNpJeBsYs/c2aiGozptX2RlnBktH+SUNpAajW724Nv2Wvhif6sFAgMBAAGjge4wgeswHQYDVR0OBBYEFJaffLvGbxe9WT9S1wob7BDWZJRrMIG7BgNVHSMEgbMwgbCAFJaffLvGbxe9WT9S1wob7BDWZJRroYGUpIGRMIGOMQswCQYDVQQGEwJVUzELMAkGA1UECBMCQ0ExFjAUBgNVBAcTDU1vdW50YWluIFZpZXcxFDASBgNVBAoTC1BheVBhbCBJbmMuMRMwEQYDVQQLFApsaXZlX2NlcnRzMREwDwYDVQQDFAhsaXZlX2FwaTEcMBoGCSqGSIb3DQEJARYNcmVAcGF5cGFsLmNvbYIBADAMBgNVHRMEBTADAQH/MA0GCSqGSIb3DQEBBQUAA4GBAIFfOlaagFrl71+jq6OKidbWFSE+Q4FqROvdgIONth+8kSK//Y/4ihuE4Ymvzn5ceE3S/iBSQQMjyvb+s2TWbQYDwcp129OPIbD9epdr4tJOUNiSojw7BHwYRiPh58S1xGlFgHFXwrEBb3dgNbMUa+u4qectsMAXpVHnD9wIyfmHMYIBmjCCAZYCAQEwgZQwgY4xCzAJBgNVBAYTAlVTMQswCQYDVQQIEwJDQTEWMBQGA1UEBxMNTW91bnRhaW4gVmlldzEUMBIGA1UEChMLUGF5UGFsIEluYy4xEzARBgNVBAsUCmxpdmVfY2VydHMxETAPBgNVBAMUCGxpdmVfYXBpMRwwGgYJKoZIhvcNAQkBFg1yZUBwYXlwYWwuY29tAgEAMAkGBSsOAwIaBQCgXTAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wNzA0MTAwNTExMjNaMCMGCSqGSIb3DQEJBDEWBBQDpgwts/HVc+ytlEWs08HvAeLutzANBgkqhkiG9w0BAQEFAASBgJWusm/E906XRNPKh4CPshmd8Tjk92E+O2bJL3iFs5LQimiX1L7+q4kg0IKeo4ZKJBboPTL0mfc812pseE1A2jfSMKD16Tpubh3c6wuVnQKur2QBiVqBTAL0mBcisJIniyO8eRq181LOglS4tsAnb8XUhsGQxOB8WjiWn4QBZ9zR-----END PKCS7-----\n">\n</form>\n</div>\n</html>
This site/document was created with [[TiddlyWiki|http://www.tiddlywiki.com]]. <nowiki>TiddlyWiki</nowiki> is a fantastic open source wiki / self-contained single file webdocument / website that supports html, javascript, and css.\n\nTo download this wiki so that you can edit and alter it as you please, right click [[here|http://www.defonso.com/clone/download/clone.html]] and select "save link as" or "save page as". If you select save from the file menu it will not work properly. You can save the file where you prefer and name it what you like, but be sure to save it with the .html extension.\n\nIf you would like to download a blank template of this wiki / webdocument or in tiddlywiki terms, the //theme// then right-click [[here|http://www.defonso.com/clone/download/emptywiki.html]]. Note: I have tagged six tiddlers with systemTiddler. They are: ~ColorPalette, ~PageTemplate, ~SetOptions, ~StyleSheet, ~TopMainMenu, and ~ViewTemplate. You can discard ~SetOptions, I simply use it to alter options when the wiki is opened. The others are necessary for the whole look. This version does have all the default items normally found in the default tiddlywiki 2.1.3 and some more added to it. For example I modified this wiki you are looking at - that is why you don't see a tiddler subtitle or some of the tabs on the right, however when you download this version it has nothing missing.
These are the common editable tiddlers in TiddlyWiki.\n\n\nMarkupPostBody\nMarkupPostHead\nMarkupPreBody\nMarkupPreHead\n---- \nStyleSheet\nPageTemplate\nViewTemplate\nEditTemplate\n----\nSiteTitle\nSiteSubtitle\nSiteUrl\nSideBarTabs\nSideBarOptions\nOptionsPanel\nAdvancedOptions\nColorPalette\nDefaultTiddlers\nMainMenu\n----\nImportTiddlers\nPluginManager\n----\nStyleSheetLayout\nStyleSheetColors
''Finishing Thoughts''\n\nGuess what? You’re finally done! Well, one last thing. Open Gparted and set a few partition flags just in case when you restart your computer, if your boot manager doesn’t work properly, you will boot into the second partition and will not accidentally fall into a situation where the xp partitions accidentally ‘see’ each other. \n\n*Hide all primary partitions except the second primary partition. \n*Mark the second primary partition as active\n\nShutdown and restart the computer (without knoppix in the cd/dvd drive). If using a boot manager then hopefully the boot manager prompts you first. Make sure your boot items are properly set, cross your fingers and boot the second partition. You should receive the normal xp splash screen then Sysprep should begin to work, then it will restart the computer. Boot back into that partition and login (xp may automatically log you in), check everything is okay by looking at Microsoft’s Disk Management – the c:\s drive should be the second partition and it should be marked as ‘System’. If the partition is marked as ‘Boot’ and the first partition is marked ‘System’ or vice versa you missed something. Otherwise, congratulations!\n\nAs you can see cloning and multi booting properly can be quite involved and there are plenty of traps along the way. If you didn’t get the hint, a boot manager is essential to multi-booting. Using boot.ini to ‘multi-boot’ is not really multi-booting at all!\n\nOnce you have a working and tested image of your filesystem, the master boot record, and the partition of your boot manager – then you really have control of your system. You can:\n\n*Completely recover from most any situation in less than 20 minutes!\n\n*Create incremental cloned images. I suggest this. After the initial install of xp and essential programs you don’t expect to replace, clone and make an image. After installation of all other current programs, clone and make another image. This way you can always begin from a fresh install and add to that, clone and make another image. You can build an image library, but always keep the original to add to because other images will age – the programs you installed in that image will eventually have better replacements.\n\n*Extend our simple example of two primary partitions to, for example, three primary partitions on each of two drives and have six copies of your environment each independently bootable (they can never ‘see’ each other though) and each of which you can modify for special purposes, then you can clone all six of those so you have a total of seven different images you can restore to anyone of six partitions! And on and on. Have fun!\n
''Hexedit the NTFS Starting Sector''\n\nFor an NTFS filesystem to boot properly it has to know its starting sector which is located in the boot record of the filesystem (partition). It resides in the first sector of the partition. The bootsector of the newly cloned ntfs filesystem has the first filesystem’s starting sector located in it and we have to change that. Just like boot.ini, if you do not modify this then xp on the first partition will be booted and they will both ‘see’ each other violating the “clean” principle for cloning xp.\n\nFind the starting sector of the second partition:\n\n[root@knoppix] fdisk –ul /dev/sda\n\nYou can easily locate the starting sector of the second partition with the output from this command. Let’s say for example the starting sector of the second partition is sector number 48,211,065.\n\n[root@knoppix] printf “%08X\sn” 48211065\n\nThe output is: 02DFA479\n\nThis converts the decimal number of the starting sector to a hexadecimal number. So the computer can understand it we must pair them and reverse their paired order (Intel based machines use little-endian architechture). For example:\n\n02DFA479 into 02 DF A4 79 into 79 A4 DF 02\n\nEdit the hexadecimal numbers on the hard disk itself. Use hexedit for this:\n\n[root@knoppix] hexedit /dev/sda2\n\nIn the default knoppix consule window there are 16 pairs of numbers, 4 groups of 4. Skip the first 28 pairs of numbers from left to right. Pairs 29, 30, 31, and 32 refer to the ntfs start sector. In the default knoppix consule window it will be the last four pairs of the second row. Replace whatever is there with the four pairs of numbers previously reversed. In this example, the 29th pair would be 79, the 30th pair would be A4, the 31st pair would be DF, and finally the 32nd pair would be 02.\n\nTwo main things to know about hexedit:\n\n*~Control-C = Exit without saving\n*~Control-X = Save and exit\n\nTo confirm all of this before actually doing it is easy and might make you more comfortable. Find the starting sector of the first partition, convert it to hex, then pair them and reverse their order, execute hexedit /dev/sda1 and see if the numbers you paired and reversed their order are the same as what you see in the 29th through 32nd pairs. It should be the same. Notice the same numbers in the second partition (that need changing) before doing so by executing hexedit /dev/sda2 they should be the same as what was in the first partition. \n
''Install the Boot Manager''\n\nAt this point if you plan on using a boot manager I would install it now for two reasons. First, if you were to accidentally boot into xp now, you would have to wait for Sysprep to run, delete the pagefile again, clean the mounted devices registry, and then re-run Sysprep to be ready to clone again. This is a 10 minute wait at least and can have worse consequences if your system has other Microsoft operating systems on it that aren’t properly hidden. The boot manager should prompt you first in case of an accidental reboot and this will allow you to prevent booting xp accidentally. Secondly, you can test whether the boot manager works without actually booting anything. Once, you know it works you can then backup the master boot record and the partition containing the boot manager later in this guide.\n\nFirst and foremost, the boot manager must be on its own partition and I’m assuming you are using a boot manager that can be installed from some sort of boot media rather than installed while in xp; otherwise, install and test while in xp before preparing to clone. I use Xosl 1.1.5. The installation of Xosl works perfectly from a floppy via dos, a win98 startup disk works fine. As of January 2007 someone began working on Xosl2 and the first priority is modifying to install from cd. The problem, I assume, is the program was written to install only from writable media. I know what you are thinking - it is 2007 and this program can’t install from anything other than a floppy? I know. I know. I wasted two hours on the net, 3 years ago, when I first ran in to Xosl because I didn’t believe it. Well, it is worth opening up your computer and connecting a floppy for 5 minutes just to install it – the program is worth it! Hopefully this will be solved soon. In any case, if you do this just one once you can use the ‘dd’ command to backup/restore the master boot record and the partition on which you installed Xosl and never actually have to re-install again. I explain this later in the next section.\n
''Installing and Configuring XP''\n\nAt this point, in our assumed situation for this guide, it is not necessary to hide any partitions because no other windows operating system is present on the hard drive. However, your case may be different and if you did have any windows operating systems installed on other partitions then they should be hidden before installation, when xp boots for the first time after installation, and every time afterwards too. The partition should be the only non-hidden primary partition with a Microsoft operating system on it!\n\nIf you only have a single partition with xp on it and have enough free space, you can repartition and add a second primary partition and if possible, an extended logical partition. You can simply install xp to the new second primary partition and begin this guide right here! \n\nBoot your xp install cd and install xp on the first (or second) primary partition. \n\nConfigure xp as you like. Install all drivers, programs, modify the ‘default’ and ‘all users’ accounts as you prefer, set program preferences, etc… Refrain from creating shortcuts to other partitions, mapped local drives, drive letter dependent items, or in general, associations with other partitions – they will be lost. The reason is I recommend using Sysprep before cloning, which, among other things, results in the rebuilding of mounted devices. I would not recommend this in any case. Keep things clean.\n\nA suggestion: install only the operating system and drivers, subject it to windows update, configure the operating system and users etc… but stop short of installing any programs at this point except essential software you don’t expect to replace and then go on with the cloning. When you restore the image to the second partition then go on installing all other software and setting preferences then clone again and make another image of your freshly installed system with programs, but be sure to keep the original image of just the xp install – this way you can always restore that image and add to a fresh install – your other images will age, that is, the programs you install will eventually have better replacements. Sure you can uninstall this is just cleaner.\n\nWith the partitioning scheme this guide assumes whichever primary partition is booted will be assigned the drive letter c:\s (even on a two+ hard drive system) and the extended logical partition, if not hidden, will be assigned d:\s. So in this special instance, shortcuts, mapped drives etc… to d:\s will work. But I still recommend doing this after cloning to keep things cleaner. Your partitioning scheme may change in the future and therefore potentially (depending upon your hiding of partitions) alter the drive letters that xp assigns. If you keep things clean you can restore this image to any partition, on the same computer without annoyances even if your partitioning scheme changes in the future.\n\nBe careful of some programs that interact with content on another partition! For example, as I mentioned previously in the description of my system, I put all files not associated with the running of my operating system on a separate partition. I keep all documents, audio, video, software install files, images etc… in an extended logical partition. Thus the audio and picture files that iTunes and Picasa interact with are located on another partition. In these cases I install the software iTunes and Picasa and set most of the preferences, but do not allow them to ‘see’ the respective files they will be interacting with until after cloning. This way they don’t build their ‘libraries’ before cloning. You collect music and picture files all the time so when restoring later you have to rebuild those ‘libraries’ anyway to get the new things you have collected to display so it will be cleaner each time after you restore to do this. Keep it clean.\n\nOkay you did all of that and now everything is perfect and you are ready to clone.\n
''Introduction to Cloning and Multi-booting XP''\n\nThis guide was written February 2007.\n\nThis guide explains cloning xp, multi-booting xp, and also provides some helpful tips and some traps to be mindful of when cloning and multi-booting. Some insight on my system and how I accomplish this is also provided.\n\nThis guide assumes you have basic knowledge of the following:\n\n*The computer boot process\n*Partitions, types and partition flags\n*Filesystem types (ntfs, fat, ext3) and their limitations\n*Multi-boot environments\n*How xp assigns drive letters\n*The command line\n\nInvariably some of my instructions will have built in assumptions on your level of experience. I will try to keep the guide accessible to those with less experience than what would otherwise be required. \n\nFor example, if I provide the instruction, ‘boot from cd’ hopefully, you know that implicitly assumes you understand how to modify your computer’s BIOS to enable booting from your cd or dvd drive and it makes no difference whether your boot media is a cd or a dvd. If you didn’t – this guide is probably not for you.\n\nThere are many ways of accomplishing some of the items discussed in this guide. I try to provide instructions that are approachable to the inexperienced. I know there are “better” ways to perform some of the tasks.\n\n''The guide provides a method to clone an xp environment on an ntfs filesystem that resides in a primary partition and restore that entire environment (filesystem (ntfs) and os (xp)) exactly as it was when cloned, to any primary partition, on any disk, on the same computer and boot any primary partition on any disk independently.'' There is a caveat:\n\n*The xp environment to be cloned must be “clean”. In other words, when xp was installed or any time after installation it can never “see” other partitions with xp (or other windows os’s) installed on them as well. Every time a partition with xp installed on it is booted all other partitions with xp (or other windows os’s) installed on them must be hidden at boot time. \n\n***You will have no problems if you have, and only had, a single partition with xp installed on it, regardless of the number of other partitions or even hard drives as long as none of them also have xp (or other windows os’s) installed on them. If other partitions exist with xp (or other windows os’s) installed on them then you must be certain you properly hid those partitions from each other every time anyone of them was booted. \n\n***If you use Microsoft’s boot.ini to boot or if you get a menu (or even if you had one in the past – unless you are sure how to completely fix this, not just no longer prompt you) that allows you to select a windows operating system – watch out! The cloning will go fine and operate exactly as it should, but you will have boot problems! What you are looking for is the partition to boot completely independently and when inside - Disk Management should label the partition (System). No other partition can be labeled (Boot)! And the partition must have drive letter c:\s. \n\n''To complete absolutely everything in this guide you will need only two things!''\n\n*An XP installation source\n*A Linux live cd ([[Knoppix|http://www.knoppix.org]])\n\nYes that’s correct, that’s all you will need! You will only use open source software and it is all FREE! A Linux live cd is just that - a Linux environment that runs from a cd – it does not affect anything on the hard drive unless you specifically use a program or a command that does. Do not fear using either a Linux environment or free software! Hopefully by the end of the guide you will feel much more comfortable with both and also see why these products are not only easy to use, but in fact, function better and provide more control than many, if not all, of their commercial counterparts!\n\nThe multi-booting aspects of this guide focus on multi-booting independent xp installations. I multi-boot several operating systems, but this guide primarily focuses on xp because it may be the most problematic to multi-boot properly.\n
{{mmslider{\n[[Before Getting Started]]\n[[My System]]\n[[Basic Idea]]\n[[Tools and Required Items]]\n}}}
{{mmslider{\n[[Best Practices Before Cloning]]\n[[Prepare Sysprep]]\n[[Remove the Pagefile]]\n[[Clean the Partition]]\n[[Defragment the Partition]]\n[[Wipe the Partition]]\n[[Modify the Registry]]\n[[Run Sysprep]]\n}}}
{{mmslider{\n[[Cloning XP]]\n[[Using the DD Command]]\n[[Backup the Master Boot Record]]\n}}}
{{mmslider {\n[[Modify Boot.ini]]\n[[Modify Boot.ini on the Second Hard Drive]]\n[[Hexedit the NTFS Starting Sector]]\n}}}
{{mmslider{\n[[Starting From Scratch]]\n[[Wipe the Hard Drive]]\n[[Partition the Hard Drive]]\n[[Installing and Configuring XP]]\n}}}
{{mmslider{\n[[Introduction]]\n[[Reasons to Clone]]\n[[Cloning Options]]\n[[Resizing Partitions]]\n[[Partitioning Traps]]\n[[Cloning to Different Computers]]\n}}}
{{mmslider{\n[[Restoring the Image]]\n[[Resize the Partition]]\n}}}
<<slider chkSliderMMIntro MMIntro 'Introduction »'>>\n<<slider chkSliderMMBeforeGS MMBeforeGS 'Before Getting Started »'>>\n<<slider chkSliderMMGettingStarted MMGettingStarted 'Getting Started »'>>\n<<slider chkSliderMMBestPractices MMBestPractices 'Best Practices »'>>\n[[Install the Boot Manager]]\n<<slider chkSliderMMClone MMClone 'Cloning XP »'>>\n<<slider chkSliderMMRestore MMRestore 'Restoring the Image »'>>\n<<slider chkSliderMMFinalizing MMFinalizing 'Finalizing Actions »'>>\n[[Finishing Thoughts]]\n----\n[[The Whole Document|WholeDocument]]\n
''Modify Boot.ini''\n\n[root@knoppix /home/knoppix/tmp] mkdir secondpart\n\n[root@knoppix] mount –t ntfs-3g /dev/sda2 /home/knoppix/tmp/secondpart\n\nNow you can open any text editor in knoppix and browse to /home/knoppix/tmp/secondpart and open boot.ini.\n\nIt will look something like this:\n\n[boot loader]\ntimeout=30\ndefault=multi(0)disk(0)rdisk(0)partition(1)\sWINDOWS\n[operating systems]\nmulti(0)disk(0)rdisk(0)partition(1)\sWINDOWS="Microsoft Windows XP Professional" /fastdetect\n\nThis is obviously the boot.ini from the first partition that you cloned to the second partition. If you don’t modify this then xp on the first partition will be booted and they will both ‘see’ each other and this violates the “clean” principle for cloning xp. Modify the partition(x) number in both sections [boot loader] and [operating systems] so it looks like this:\n\n[boot loader]\ntimeout=30\ndefault=multi(0)disk(0)rdisk(0)partition(2)\sWINDOWS\n[operating systems]\nmulti(0)disk(0)rdisk(0)partition(2)\sWINDOWS="Microsoft Windows XP Professional” /fastdetect\n\nI quick note on arc paths using examples:\n\nmulti(0)disk(0)rdisk(0)partition(1) = first partition of first hard drive\nmulti(0)disk(0)rdisk(0)partition(3) = third partition of first hard drive\nmulti(0)disk(0)rdisk(1)partition(2) = second partition of second hard drive\nmulti(0)disk(0)rdisk(5)partition(7) = seventh partition of sixth hard drive\n
''Modify Boot.ini on the Second Hard Drive''\n\nIf you are modifying the boot.ini for an xp installation on the second hard drive and using a boot manager with a feature that “swaps disks” or modifies the disk number, in order to trick xp into thinking its on the first disk (to enable booting), then be sure to not change the rdisk numbers! For example the boot.ini below is what you might be tempted to set up in order to boot the third partition on the second hard drive:\n\n[boot loader]\ntimeout=30\ndefault=multi(0)disk(0)rdisk(1)partition(3)\sWINDOWS\n[operating systems]\nmulti(0)disk(0)rdisk(1)partition(3)\sWINDOWS="Microsoft Windows XP Professional” /fastdetect\n\n''This would not work if you are using a boot manager with such a feature!'' Xosl has this feature, many don’t even offer it. Essentially what it does is swap the disk numbers of each disk during the boot process and then changes them back. But during the boot process this alters the arc paths that boot.ini uses to boot. So when the boot.ini above goes to boot the arc path specified in it, it will actually boot the third partition of the first hard drive! This is because the arc paths were altered by the boot manager during the boot process and switched - so the real rdisk(0) becomes rdisk(1) and the real rdisk(1) becomes rdisk(0), thus it would boot what it thinks at the moment is rdisk(1) which in reality is rdisk(0) and thus you will be booting the third partition on the first hard drive. So if you happen to have a two hard drive system with xp installations on the second partition on both hard drives and use a boot manager that “swaps disks” then you actually use the exact same boot.ini to boot two separate independent partitions! Leave the rdisk(0) numbers set to ‘0’ regardless of what drive xp is installed on.\n
''Modify the Registry''\n\nOkay one last critical step. Run Regedit and locate: \n\n~HKey Local Machine\sSystem\sMounted Devices \n\nDelete each listing. This won’t harm the system at all - this list is only processed at startup and even if you happen to reboot between now and running Sysprep, it will simply regenerate a new list and this can then be deleted.\n
''My System''\n\nStandard ~IA-32 architecture (x86) with a Pentium 4 processor and Windows XP Professional as the only windows operating system. \n\nSystem has two hard drives. They are both SATA – different manufacturers, approximately the same size. The slightly smaller hard drive is installed as the first hard drive (sda) (this can be handy, but really doesn’t matter) No Raid. \n\nI do not deal with some older things: sata/ide drivers, master/slave configurations - its all cable select these days boys… (ball bearings, fletch).\n\nThe Linux live CD used for this guide is Knoppix 5.1.1, but others will work as well. Simply download the .iso file and burn it to a cd.\n
These options are saved in cookies\n\n<<option txtUserName>>\n----\n<<option chkSaveBackups>> SaveBackups\n<<option chkAutoSave>> AutoSave\n<<option chkRegExpSearch>> RegExpSearch\n<<option chkCaseSensitiveSearch>> CaseSensitiveSearch\n<<option chkAnimate>> EnableAnimations\n----\nAdvancedOptions\nPluginManager\nImportTiddlers
<!--{{{-->\n<div class='header' macro='gradient vert [[ColorPalette::PrimaryLight]] [[ColorPalette::PrimaryMid]]'>\n<div class='headerShadow'>\n<span class='siteTitle' refresh='content' tiddler='SiteTitle'></span> \n<span class='siteSubtitle' refresh='content' tiddler='SiteSubtitle'></span>\n</div>\n<div class='headerForeground'>\n<span class='siteTitle' refresh='content' tiddler='SiteTitle'></span> \n<span class='siteSubtitle' refresh='content' tiddler='SiteSubtitle'></span>\n</div>\n<!-- horizontal TopMainMenu -->\n<div id='topMenu' refresh='content' tiddler='TopMainMenu'>\n</div>\n\n</div>\n<div id='mainMenu' refresh='content' tiddler='MainMenu'></div>\n<div id='sidebar'>\n<div id='sidebarOptions' refresh='content' tiddler='SideBarOptions'></div>\n<div id='sidebarTabs' refresh='content' force='true' tiddler='SideBarTabs'></div>\n</div>\n\n<div id='displayArea'>\n<div id='messageArea'></div>\n<div id='tiddlerDisplay'></div>\n</div>\n<!--}}}-->
''Partition the Hard Drive''\n\nOpen Gparted and partition the hard drive as you like. I included the graphic earlier explaining the partitioning scheme I am assuming for this guide, but you certainly don’t need two primary partitions exactly the same size and I will explain how to handle situations of different size. Please see the traps explained earlier for partitioning too.\n\nShutdown and boot from your xp install cd.\n
''Partitioning Traps''\n\n@@Trap #1@@\n\nBe aware of exactly how your partitioning tools actually partition – they are NOT all the same. Also try to avoid using different partitioning tools interchangeably to alter your system as this too can lead to some unexpected problems. See trap #2. Pick one and stick with it – my suggestion: Gparted. The differences come in where they begin the first partition. For example, Gparted/PM begins the first partition on the second head of the hard drive, but by default other partitions are rounded to cylinders, the result: your first partition will be one head smaller (because your mbr is in the first sector, and they skip the other 62 sectors in that head) than other partitions you create with the same ‘size’ specification during their creation interface, they will also appear to be exactly equal when displayed in the main view, only when you select more detailed information about the partitions can you see their sector count difference. Another partition manager is Ranish. It allows you to directly edit the number of cylinders, heads, and sectors if you wish – you can also manually re-write the partition table if necessary! If you want to specify two or three partitions of exact equal size so that you don’t have to bother with resizing (I do this, but it makes more sense within a two or three hard drive system) a work around using Gparted/PM would be to leave approximately the first 7.8MiB (the first cylinder) unallocated. Gparted/PM will by default round to cylinders (approx. 7.8MiB) in their partition creating interface – you can only increase or decrease partitions in minimum movements of 7.8MiB. Gparted allows you to change this default. So, if you leave the first cylinder unallocated on the hard drive, this will have the effect of starting your first partition on cylinder (1) (the second cylinder of the hard drive) and now all other partitions made with the same ‘size’ specification will be exactly the same. This will save you from some potentially annoying resizing that will be required if you decide in the future you would like to clone from your second or third partition onto your ‘supposedly’ equal sized first partition.\n\n\n@@Trap #2@@\n\nBe aware that Partition Magic does not necessarily number partitions according to their order on disk! PM numbers the partitions according to the order of their creation! Gparted does not suffer from this drawback. You can easily check this with Ranish and then re-order them to match their location on disk. This can be a real problem because Microsoft’s boot.ini uses these numbers in their arc paths to boot a partition. For example, if you have a boot.ini with the following arc path:\n\nmulti(0)disk(0)rdisk(0)partition(2)\swindows\n\nThe partition labeled number two on the hard drive will be booted by boot.ini. But if you started deleting and creating new partitions on your hard drive with PM it could be the case that the second partition on the disk (physically the second partition on the disk) is labeled number three! Even if you did everything correct (except use PM) and properly hid other xp partitions – you may think you are booting the second partition, but in fact, you will be using the second partition as the boot partition and one of two things will happen: you will get an error because there is no operating system on the partition that is labeled number 2, or you will be booting another partition, but it won’t be the second partition – it depends upon the order you created them in PM. This is not cool and can easily lead to a violation of the “clean” principle for cloning if you were to accidentally boot another windows os partition without the others hidden properly just because PM functions in this quirky manner.\n
''Prepare Sysprep''\n\nWe will run Sysprep as the final thing we do before shutting down and rebooting into our Linux live cd to clone. At this point we are just preparing the files to run Sysprep.\n\nSysprep is a Microsoft product. You can find it on the xp install cd in the support\stools folder, the file is called deploy.cab.\n\nCreate a folder on your desktop and extract the cab file to it.\n\nCreate a folder in the root of your drive c:\ssysprep\n\nMove sysprep.exe and setupcl.exe from the folder on your desktop into this newly created sysprep folder. \n\nThis is optional, but I recommend it. In the folder on your desktop where you extracted the deploy.cab you will find setupmgr.exe. This is a simple wizard that will generate an answer file (sysprep.inf) so you won’t be prompted to answer a few basic questions that Sysprep asks the first time you boot into the partition again. When you boot into your clone for the first time Sysprep runs and it looks similar to xp’s installation interface, but only lasts three minutes or so. You will have to answer a few questions unless you generate the answer file by running the wizard setupmgr.exe. Put the answerfile, sysprep.inf, into the sysprep folder at the root of your drive, c:\ssysprep, setupmgr.exe may also copy that file and another over to your sysprep folder automatically if you previously created that folder. You can do quite a bit more with sysprep.inf, much like an unattended installation of xp (winnt.sif). For this guide we will simply accept the default answer file created with the wizard.\n\nDelete the folder on your desktop where the deploy.cab file was extracted.\n\nNow we are ready to run Sysprep, but that will be the last thing we do before shutting down. There are some things that need to be done before we run Sysprep.\n
''Reasons to Clone''\n\nDowntime has real costs! Whether you require multiple environments for backup, safety and security reasons, testing environments, or even if you like to play with an operating system as if were any other file - a method of cloning the operating system is absolutely essential. The whole point of cloning is essentially this: after cloning a partition you can cause a complete meltdown of your operating system and a few clicks and a few minutes later are back to where you where with a perfect environment again as if nothing happened. Why else do we clone? From the basic: So you never have to reinstall ever again. To the slightly more advanced: Cloning your original xp to several different partitions, modify each of them for special purposes and clone all of them – enabling you to restore either your original or any one of a handful of special purpose xp installations to any partition. Cloning an OS X system or most Linux systems is a cakewalk, but some systems aren’t as intuitive. Thus this guide…\n
''Remove the Pagefile''\n\nRemove your pagefile, or virtual memory. Your computer will work just fine without it and this will save considerable space when cloning. When Sysprep runs on first boot it automatically regenerates a pagefile. You can modify your pagefile here: right click my computer, properties, advanced tab, performance section, settings button, advanced tab, virtual memory section, and change button.\n
''Resize the Partition''\n\nIf your partition is exactly the same size as the filesystem you cloned then no resizing is necessary. Otherwise, the partition is likely larger than the filesystem you cloned, to ‘reclaim the extra space’ in the partition, or extend the filesystem to fill the partition:\n\n[root@knoppix] ntfsresize /dev/sda2\n
''Resizing Partitions''\n\nObviously, the ntfs filesystem can not be larger than the device (partition) on which it resides, but the ntfs filesystem can be smaller than the device (partition) on which it resides. The most common case is the ntfs filesystem is exactly the same size as the device (partition) on which it resides.\n\nWhen you clone using ntfsclone the entire ntfs filesystem is cloned and any restoration from image or direct clone will result in an exact replica of the cloned filesystem including its size.\n\nYou can restore from image or direct clone to a partition that is of equal or larger size than the filesystem previously cloned or cloning from (ntfsclone will not function unless the partition you are cloning or restoring to, is at least as large as the filesystem being cloned or restored from – if it is smaller by even a single sector the command will not function).\n\nYou may be cloning or restoring to a partition previously created that is larger than the filesystem you are restoring or cloning from. Your newly cloned or restored filesystem will be exactly the same size as your original filesystem - xp will only recognize its size as that of the previously cloned filesystem even if the partition you restored or cloned directly to is larger. To fix this you must use ntfsresize to “reclaim the extra space”. The ntfsresize command, given without options, will automatically “reclaim the extra space” in that partition or extend the filesystem to fill the entire device (partition).\n\nOne method that works well when your partitions will likely be different sizes is to run ntfsresize before cloning to shrink your filesystem to slightly larger than the actual space used by the files.\n\nFor example, suppose you have a 25GB partition. You installed xp on it and the actual space used in that partition is 10GB. At this point, the filesystem size and device (partition) size are exactly the same, both 25GB. If you clone normally you can only restore that image or clone directly to a partition that is 25GB or larger. If you run ntfsresize before cloning you can shrink the filesystem to say 11GB, the device (partition) will remain 25GB. If you clone this resized ntfs filesystem then you would be able to restore that image or clone directly to any partition 11GB or larger. Don’t confuse image filesize with filesystem file size – the image file created by ntfsclone may be 6GB, if compressed, but your filesystem size will always be 11GB.\n\nIf you restore to or direct clone to a partition of exact equal size you never have to bother with resizing… if you want to make sure your partitions are exactly the same size read the trap below. Please read the second trap if you are using PM!\n
''Restoring the Image''\n\nTo restore the uncompressed image to the second partition:\n\n[root@knoppix /home/knoppix/tmp/thirdpart] ntfsclone """--restore-image""" """--overwrite""" /dev/sda2 sda1.img \n\nTo restore the compressed image to the second partition:\n\n[root@knoppix /home/knoppix/tmp/thirdpart] gunzip –c sda1.img.gz | ntfsclone """--restore-image""" """--overwrite""" /dev/sda2 –\n\nTo restore multiple compressed files to the second partition:\n\n[root@knoppix /home/knoppix/tmp/thirdpart] cat sda1.img.gz_aa sda1.img.gz_ab | gunzip –c | ntfsclone """--restore-image""" """--overwrite""" /dev/sda2 -\n\nNow that you have restored an ntfs filesystem to the second partition there are still some modifications that need to be made in order for this partition to boot properly.\n
''Run Sysprep''\n\nAt this point the partition should be completely organized and configured. When Sysprep is run it will shutdown the computer and we will boot the Linux live cd and begin the cloning process. Make sure everything in the partition is set properly, it can be annoying to wait the three minutes Sysprep takes to complete before you have access to your partition again and if you reboot accidentally don’t forget to delete the pagefile again, clean the mounted devices registry, and then re-run Sysprep to be ready to clone again. Now simply run sysprep.exe inside c:\ssysprep. Select the check-box for ‘mini-setup’ if you created an answer file with setupmgr.exe. Simply click the ‘reseal’ button. That is it. Sysprep will run and shutdown the computer. You are now ready to clone!\n
Type the text for 'SaveBackups'
\nconfig.options.chkRegExpSearch = false; // default false\nconfig.options.chkCaseSensitiveSearch = false; // default false\nconfig.options.chkAnimate = true; // default true\nconfig.options.txtUserName = "YourName"; // default "YourName"\nconfig.options.chkSaveBackups = false; // default true\nconfig.options.chkAutoSave = false; // default false\nconfig.options.chkGenerateAnRssFeed = false; // default false\nconfig.options.chkSaveEmptyTemplate = false; // default false\nconfig.options.chkOpenInNewWindow = true; // default true\nconfig.options.chkToggleLinks = false; // default false\nconfig.options.chkHttpReadOnly = true; // default true\nconfig.options.chkForceMinorUpdate = false; // default false\nconfig.options.chkConfirmDelete = true; // default true\nconfig.options.txtBackupFolder = ""; // default ""\nconfig.options.txtMainTab = "tabTimeline"; // default "tabTimeline"\nconfig.options.txtMoreTab = "moreTabAll"; // default "moreTabAll"\nconfig.options.txtMaxEditRows = "35"; // default "30"\n\n
<<search>><<closeAll>><<saveChanges>>
<<tabs txtMainTab All 'All tiddlers' TabAll Tags 'All tags' TabTags More 'More lists' TabMore>>
thorough, simple, and free
Clone and Multi-boot XP
''Starting From Scratch''\n\nI will start from scratch because it may aid in explaining why something works for me, but might not in your case. Please familiarize yourself with all the commands I use!\n\nBoot your Linux live cd/dvd.\n
/*{{{*/\n\n/* horizontal top main menu */\n\n#topMenu br {\n display: none;\n}\n\n#topMenu {\n float: right;\n color:[[ColorPalette::PrimaryPale]];\n font-weight: bold;\n text-decoration: none;\n padding:10px;\n}\n\n#topMenu .button, #topMenu .tiddlyLink, #topMenu a {\n margin-left: 0.5em;\n margin-right: 0.5em;\n padding-left: 15px;\n padding-right: 15px;\n color: [[ColorPalette::PrimaryPale]];\n font-size: 115%;\n text-decoration: none;\n}\n\n#topMenu .button:hover, #topMenu .tiddlyLink:hover, #topMenu a:hover {\n color: [[ColorPalette::PrimaryLight]];\n}\n\n\n.headerForeground {\n color: [[ColorPalette::PrimaryPale]];\n}\n\n\n.headerShadow, .headerShadow a {\n color: [[ColorPalette::PrimaryMid]];\n}\n\n\n.headerForeground, .headerShadow {\n padding: 1em 1em 0;\n font-family: 'Trebuchet MS' sans-serif;\n font-weight:bold;\n}\n\n\n.headerForeground .siteSubtitle {\n color: [[ColorPalette::PrimaryLight]];\n}\n\n\n.headerShadow .siteSubtitle {\n color: [[ColorPalette::PrimaryMid]];\n}\n\n\n\n/* modifications to everything below the header */\n\nbody {\n background: [[ColorPalette::TertiaryLight]];\n}\n\n\n\n\n#mainMenu {\n position: absolute;\n left: 0px;\n width: 12em;\n text-align: left;\n line-height: 1.6em;\n padding: 1.2em 0.5em 0.5em 0.5em;\n font-size: 1.1em;\n}\n\n#mainMenu a, #mainMenu .tiddlyLink, #mainMenu .button {\n font-weight: bold;\n color: [[ColorPalette::PrimaryMid]];\n background: transparent;\n border: none;\n}\n\n#mainMenu a:hover, #mainMenu .tiddlyLink:hover, #mainMenu .button:hover {\n background: transparent;\n border: none;\n color: [[ColorPalette::PaleDullBlue]];\n}\n\n#mainMenu a:active, #mainMenu .tiddlyLink:active, #mainMenu .button:active {\n background: transparent;\n border: none;\n color: [[ColorPalette::PrimaryMid]];\n}\n\n\n/* personal class designed to slightly indent main menu slider contents */\n\n.mmslider {\n padding-left: 0.5em;\n}\n\n\n#sidebar {\n position: absolute;\n right: 3px;\n padding: 1.2em 0em 0em 0em;\n width: 16em;\n font-size: .9em;\n}\n\n#displayArea {\n margin: 1em 16em 0em 14em;\n}\n\n\n\n\n/* modifications to the look of the tiddler */\n\n\n.tiddler {\n padding: 0.5em 1em 3em 1em;\n background: [[ColorPalette::Background]];\n margin-bottom: 1em;\n}\n\n\n.title {\n font-size: 200%;\n padding: 0px;\n color: [[ColorPalette::PrimaryLight]];\n font-family: 'Trebuchet MS' sans-serif;\n}\n\n\n.subtitle {\n padding:0px;\n margin:0px;\n padding-left:3em;\n font-size: 90%;\n color: [[ColorPalette::TertiaryMid]];\n}\n\n\n\n.button {\n color: [[ColorPalette::PaleDullBlue]];\n border: none;\n}\n\n\n.button:hover {\n color: [[ColorPalette::MediumFadedBlue]];\n background: transparent;\n border-color: transparent;\n}\n\n\n.button:active {\n color: [[ColorPalette::PaleDullBlue]];\n background: transparent;\n border: none;\n}\n\n\n\n\nh1,h2,h3,h4,h5 {\n color: [[ColorPalette::PaleWeakBlue]];\n background: [[ColorPalette::LightFadedBlue]];\n}\n\n\n\n.tagged {\n margin: 0em;\n float: left;\n}\n\n.tagged li, .tagged ul {\n display:inline;\n}\n\n\n\n/* modifications to the sidebar */\n\n#sidebarOptions .sliderPanel {\n background: [[ColorPalette::BlueGrayFour]];\n}\n\n#sidebarOptions .sliderPanel a {\n border: none;\n color: [[ColorPalette::PaleDullBlue]];\n}\n\n#sidebarOptions .sliderPanel a:hover {\n color: [[ColorPalette::MediumFadedBlue]];\n background: transparent;\n}\n\n#sidebarOptions .sliderPanel a:active {\n color: [[ColorPalette::PaleDullBlue]];\n background: transparent;\n}\n\n\n\n\n/* modifications to the message area and popups */\n\n#messageArea {\n border: 1px solid [[ColorPalette::PaleDullBlue]];\n background: [[ColorPalette::BlueGrayFour]];\n color: [[ColorPalette::PaleDullBlue]];\n}\n\n#messageArea .button, #messageArea a {\n padding: 1em 1em 1em 1em;\n color: [[ColorPalette::PaleDullBlue]];\n background: transparent;\n}\n\n\n\n.popup {\n background: [[ColorPalette::BlueGrayFour]];\n border: 1px solid [[ColorPalette::PaleDullBlue]];\n}\n\n.popup hr {\n color: [[ColorPalette::PaleDullBlue]];\n background: transparent;\n border-bottom: 1px;\n}\n\n.popup li.disabled {\n color: [[ColorPalette::PrimaryMid]];\n}\n\n.popup li a, .popup li a:visited {\n color: [[ColorPalette::TertiaryPale]];\n border: none;\n}\n\n.popup li a:hover, .popup li .tiddlyLink:hover {\n background: transparent;\n color: [[ColorPalette::PaleDullBlue]];\n border: none;\n}\n\n\n\n\n/* modifications to the secondary view */\n\n.viewer {\n padding: 1em 0em;\n}\n\n.viewer pre {\n margin-left: 0em;\n border: 1px solid [[ColorPalette::BlueGrayThree]];\n background: [[ColorPalette::TertiaryPale]];\n}\n\n.viewer code {\n color: [[ColorPalette::PrimaryDark]];\n}\n\n.highlight, .marked {\n background: [[ColorPalette::HighlightYellow]];\n}\n\n\n/*}}}*/
/*{{{*/\nbody {\n background: [[ColorPalette::Background]];\n color: [[ColorPalette::Foreground]];\n}\n\na{\n color: [[ColorPalette::PrimaryMid]];\n}\n\na:hover{\n background: [[ColorPalette::PrimaryMid]];\n color: [[ColorPalette::Background]];\n}\n\na img{\n border: 0;\n}\n\nh1,h2,h3,h4,h5 {\n color: [[ColorPalette::SecondaryDark]];\n background: [[ColorPalette::PrimaryPale]];\n}\n\n.button {\n color: [[ColorPalette::PrimaryDark]];\n border: 1px solid [[ColorPalette::Background]];\n}\n\n.button:hover {\n color: [[ColorPalette::PrimaryDark]];\n background: [[ColorPalette::SecondaryLight]];\n border-color: [[ColorPalette::SecondaryMid]];\n}\n\n.button:active {\n color: [[ColorPalette::Background]];\n background: [[ColorPalette::SecondaryMid]];\n border: 1px solid [[ColorPalette::SecondaryDark]];\n}\n\n.header {\n background: [[ColorPalette::PrimaryMid]];\n}\n\n.headerShadow {\n color: [[ColorPalette::Foreground]];\n}\n\n.headerShadow a {\n font-weight: normal;\n color: [[ColorPalette::Foreground]];\n}\n\n.headerForeground {\n color: [[ColorPalette::Background]];\n}\n\n.headerForeground a {\n font-weight: normal;\n color: [[ColorPalette::PrimaryPale]];\n}\n\n.tabSelected{\n color: [[ColorPalette::PrimaryDark]];\n background: [[ColorPalette::TertiaryPale]];\n border-left: 1px solid [[ColorPalette::TertiaryLight]];\n border-top: 1px solid [[ColorPalette::TertiaryLight]];\n border-right: 1px solid [[ColorPalette::TertiaryLight]];\n}\n\n.tabUnselected {\n color: [[ColorPalette::Background]];\n background: [[ColorPalette::TertiaryMid]];\n}\n\n.tabContents {\n color: [[ColorPalette::PrimaryDark]];\n background: [[ColorPalette::TertiaryPale]];\n border: 1px solid [[ColorPalette::TertiaryLight]];\n}\n\n.tabContents .button {\n border: 0;}\n\n#sidebar {\n}\n\n#sidebarOptions input {\n border: 1px solid [[ColorPalette::PrimaryMid]];\n}\n\n#sidebarOptions .sliderPanel {\n background: [[ColorPalette::PrimaryPale]];\n}\n\n#sidebarOptions .sliderPanel a {\n border: none;\n color: [[ColorPalette::PrimaryMid]];\n}\n\n#sidebarOptions .sliderPanel a:hover {\n color: [[ColorPalette::Background]];\n background: [[ColorPalette::PrimaryMid]];\n}\n\n#sidebarOptions .sliderPanel a:active {\n color: [[ColorPalette::PrimaryMid]];\n background: [[ColorPalette::Background]];\n}\n\n.wizard {\n background: [[ColorPalette::SecondaryLight]];\n border-top: 1px solid [[ColorPalette::SecondaryMid]];\n border-left: 1px solid [[ColorPalette::SecondaryMid]];\n}\n\n.wizard h1 {\n color: [[ColorPalette::SecondaryDark]];\n}\n\n.wizard h2 {\n color: [[ColorPalette::Foreground]];\n}\n\n.wizardStep {\n background: [[ColorPalette::Background]];\n border-top: 1px solid [[ColorPalette::SecondaryMid]];\n border-bottom: 1px solid [[ColorPalette::SecondaryMid]];\n border-left: 1px solid [[ColorPalette::SecondaryMid]];\n}\n\n.wizard .button {\n color: [[ColorPalette::Background]];\n background: [[ColorPalette::PrimaryMid]];\n border-top: 1px solid [[ColorPalette::PrimaryLight]];\n border-right: 1px solid [[ColorPalette::PrimaryDark]];\n border-bottom: 1px solid [[ColorPalette::PrimaryDark]];\n border-left: 1px solid [[ColorPalette::PrimaryLight]];\n}\n\n.wizard .button:hover {\n color: [[ColorPalette::PrimaryLight]];\n background: [[ColorPalette::PrimaryDark]];\n border-color: [[ColorPalette::PrimaryLight]];\n}\n\n.wizard .button:active {\n color: [[ColorPalette::Background]];\n background: [[ColorPalette::PrimaryMid]];\n border-top: 1px solid [[ColorPalette::PrimaryLight]];\n border-right: 1px solid [[ColorPalette::PrimaryDark]];\n border-bottom: 1px solid [[ColorPalette::PrimaryDark]];\n border-left: 1px solid [[ColorPalette::PrimaryLight]];\n}\n\n#messageArea {\n border: 1px solid [[ColorPalette::SecondaryDark]];\n background: [[ColorPalette::SecondaryMid]];\n color: [[ColorPalette::PrimaryDark]];\n}\n\n#messageArea .button {\n padding: 0.2em 0.2em 0.2em 0.2em;\n color: [[ColorPalette::PrimaryDark]];\n background: [[ColorPalette::Background]];\n}\n\n.popup {\n background: [[ColorPalette::PrimaryLight]];\n border: 1px solid [[ColorPalette::PrimaryMid]];\n}\n\n.popup hr {\n color: [[ColorPalette::PrimaryDark]];\n background: [[ColorPalette::PrimaryDark]];\n border-bottom: 1px;\n}\n\n.listBreak div{\n border-bottom: 1px solid [[ColorPalette::PrimaryDark]];\n}\n\n.popup li.disabled {\n color: [[ColorPalette::PrimaryMid]];\n}\n\n.popup li a, .popup li a:visited {\n color: [[ColorPalette::TertiaryPale]];\n border: none;\n}\n\n.popup li a:hover {\n background: [[ColorPalette::PrimaryDark]];\n color: [[ColorPalette::Background]];\n border: none;\n}\n\n.tiddler .defaultCommand {\n font-weight: bold;\n}\n\n.shadow .title {\n color: [[ColorPalette::TertiaryDark]];\n}\n\n.title {\n color: [[ColorPalette::SecondaryDark]];\n}\n\n.subtitle {\n color: [[ColorPalette::TertiaryDark]];\n}\n\n.toolbar {\n color: [[ColorPalette::PrimaryMid]];\n}\n\n.tagging, .tagged {\n border: 1px solid [[ColorPalette::TertiaryPale]];\n background-color: [[ColorPalette::TertiaryPale]];\n}\n\n.selected .tagging, .selected .tagged {\n background-color: [[ColorPalette::TertiaryLight]];\n border: 1px solid [[ColorPalette::TertiaryMid]];\n}\n\n.tagging .listTitle, .tagged .listTitle {\n color: [[ColorPalette::PrimaryDark]];\n}\n\n.tagging .button, .tagged .button {\n border: none;\n}\n\n.footer {\n color: [[ColorPalette::TertiaryLight]];\n}\n\n.selected .footer {\n color: [[ColorPalette::TertiaryMid]];\n}\n\n.sparkline {\n background: [[ColorPalette::PrimaryPale]];\n border: 0;\n}\n\n.sparktick {\n background: [[ColorPalette::PrimaryDark]];\n}\n\n.error, .errorButton {\n color: [[ColorPalette::Foreground]];\n background: [[ColorPalette::Error]];\n}\n\n.warning {\n color: [[ColorPalette::Foreground]];\n background: [[ColorPalette::SecondaryPale]];\n}\n\n.cascade {\n background: [[ColorPalette::TertiaryPale]];\n color: [[ColorPalette::TertiaryMid]];\n border: 1px solid [[ColorPalette::TertiaryMid]];\n}\n\n.imageLink, #displayArea .imageLink {\n background: transparent;\n}\n\n.viewer .listTitle {list-style-type: none; margin-left: -2em;}\n\n.viewer .button {\n border: 1px solid [[ColorPalette::SecondaryMid]];\n}\n\n.viewer blockquote {\n border-left: 3px solid [[ColorPalette::TertiaryDark]];\n}\n\n.viewer table {\n border: 2px solid [[ColorPalette::TertiaryDark]];\n}\n\n.viewer th, thead td {\n background: [[ColorPalette::SecondaryMid]];\n border: 1px solid [[ColorPalette::TertiaryDark]];\n color: [[ColorPalette::Background]];\n}\n\n.viewer td, .viewer tr {\n border: 1px solid [[ColorPalette::TertiaryDark]];\n}\n\n.viewer pre {\n border: 1px solid [[ColorPalette::SecondaryLight]];\n background: [[ColorPalette::SecondaryPale]];\n}\n\n.viewer code {\n color: [[ColorPalette::SecondaryDark]];\n}\n\n.viewer hr {\n border: 0;\n border-top: dashed 1px [[ColorPalette::TertiaryDark]];\n color: [[ColorPalette::TertiaryDark]];\n}\n\n.highlight, .marked {\n background: [[ColorPalette::SecondaryLight]];\n}\n\n.editor input {\n border: 1px solid [[ColorPalette::PrimaryMid]];\n}\n\n.editor textarea {\n border: 1px solid [[ColorPalette::PrimaryMid]];\n width: 100%;\n}\n\n.editorFooter {\n color: [[ColorPalette::TertiaryMid]];\n}\n\n/*}}}*/
/*{{{*/\n* html .tiddler {\n height: 1%;\n}\n\nbody {\n font-size: .75em;\n font-family: arial,helvetica,'Trebuchet MS' sans-serif;\n margin: 0;\n padding: 0;\n}\n\nh1,h2,h3,h4,h5 {\n font-weight: bold;\n text-decoration: none;\n padding-left: 0.4em;\n}\n\nh1 {font-size: 1.35em;}\nh2 {font-size: 1.25em;}\nh3 {font-size: 1.1em;}\nh4 {font-size: 1em;}\nh5 {font-size: .9em;}\n\nhr {\n height: 1px;\n}\n\na{\n text-decoration: none;\n}\n\ndt {font-weight: bold;}\n\nol { list-style-type: decimal }\nol ol { list-style-type: lower-alpha }\nol ol ol { list-style-type: lower-roman }\nol ol ol ol { list-style-type: decimal }\nol ol ol ol ol { list-style-type: lower-alpha }\nol ol ol ol ol ol { list-style-type: lower-roman }\nol ol ol ol ol ol ol { list-style-type: decimal }\n\n.txtOptionInput {\n width: 11em;\n}\n\n#contentWrapper .chkOptionInput {\n border: 0;\n}\n\n.externalLink {\n text-decoration: underline;\n}\n\n.indent {margin-left:3em;}\n.outdent {margin-left:3em; text-indent:-3em;}\ncode.escaped {white-space:nowrap;}\n\n.tiddlyLinkExisting {\n font-weight: bold;\n}\n\n.tiddlyLinkNonExisting {\n font-style: italic;\n}\n\n/* the 'a' is required for IE, otherwise it renders the whole tiddler a bold */\na.tiddlyLinkNonExisting.shadow {\n font-weight: bold;\n}\n\n#mainMenu .tiddlyLinkExisting, \n#mainMenu .tiddlyLinkNonExisting,\n#sidebarTabs .tiddlyLinkNonExisting{\n font-weight: normal;\n font-style: normal;\n}\n\n#sidebarTabs .tiddlyLinkExisting {\n font-weight: bold;\n font-style: normal;\n}\n\n.header {\n position: relative;\n}\n\n.header a:hover {\n background: transparent;\n}\n\n.headerShadow {\n position: relative;\n padding: 4.5em 0em 1em 1em;\n left: -1px;\n top: -1px;\n}\n\n.headerForeground {\n position: absolute;\n padding: 4.5em 0em 1em 1em;\n left: 0px;\n top: 0px;\n}\n\n.siteTitle {\n font-size: 3em;\n}\n\n.siteSubtitle {\n font-size: 1.2em;\n}\n\n#mainMenu {\n position: absolute;\n left: 0;\n width: 10em;\n text-align: right;\n line-height: 1.6em;\n padding: 1.5em 0.5em 0.5em 0.5em;\n font-size: 1.1em;\n}\n\n#sidebar {\n position: absolute;\n right: 3px;\n width: 16em;\n font-size: .9em;\n}\n\n#sidebarOptions {\n padding-top: 0.3em;\n}\n\n#sidebarOptions a {\n margin: 0em 0.2em;\n padding: 0.2em 0.3em;\n display: block;\n}\n\n#sidebarOptions input {\n margin: 0.4em 0.5em;\n}\n\n#sidebarOptions .sliderPanel {\n margin-left: 1em;\n padding: 0.5em;\n font-size: .85em;\n}\n\n#sidebarOptions .sliderPanel a {\n font-weight: bold;\n display: inline;\n padding: 0;\n}\n\n#sidebarOptions .sliderPanel input {\n margin: 0 0 .3em 0;\n}\n\n#sidebarTabs .tabContents {\n width: 15em;\n overflow: hidden;\n}\n\n.wizard {\n padding: 0.1em 0em 0em 2em;\n}\n\n.wizard h1 {\n font-size: 2em;\n font-weight: bold;\n background: none;\n padding: 0em 0em 0em 0em;\n margin: 0.4em 0em 0.2em 0em;\n}\n\n.wizard h2 {\n font-size: 1.2em;\n font-weight: bold;\n background: none;\n padding: 0em 0em 0em 0em;\n margin: 0.2em 0em 0.2em 0em;\n}\n\n.wizardStep {\n padding: 1em 1em 1em 1em;\n}\n\n.wizard .button {\n margin: 0.5em 0em 0em 0em;\n font-size: 1.2em;\n}\n\n#messageArea {\nposition:absolute; top:0; right:0; margin: 0.5em; padding: 0.5em;\n}\n\n*[id='messageArea'] {\nposition:fixed !important; z-index:99;}\n\n.messageToolbar {\ndisplay: block;\ntext-align: right;\n}\n\n#messageArea a{\n text-decoration: underline;\n}\n\n.popup {\n font-size: .9em;\n padding: 0.2em;\n list-style: none;\n margin: 0;\n}\n\n.popup hr {\n display: block;\n height: 1px;\n width: auto;\n padding: 0;\n margin: 0.2em 0em;\n}\n\n.listBreak {\n font-size: 1px;\n line-height: 1px;\n}\n\n.listBreak div {\n margin: 2px 0;\n}\n\n.popup li.disabled {\n padding: 0.2em;\n}\n\n.popup li a{\n display: block;\n padding: 0.2em;\n}\n\n.tabset {\n padding: 1em 0em 0em 0.5em;\n}\n\n.tab {\n margin: 0em 0em 0em 0.25em;\n padding: 2px;\n}\n\n.tabContents {\n padding: 0.5em;\n}\n\n.tabContents ul, .tabContents ol {\n margin: 0;\n padding: 0;\n}\n\n.txtMainTab .tabContents li {\n list-style: none;\n}\n\n.tabContents li.listLink {\n margin-left: .75em;\n}\n\n#displayArea {\n margin: 1em 16em 0em 14em;\n}\n\n\n.toolbar {\n text-align: right;\n font-size: .9em;\n visibility: hidden;\n}\n\n.selected .toolbar {\n visibility: visible;\n}\n\n.tiddler {\n padding: 1em 1em 0em 1em;\n}\n\n.missing .viewer,.missing .title {\n font-style: italic;\n}\n\n.title {\n font-size: 1.6em;\n font-weight: bold;\n}\n\n.missing .subtitle {\n display: none;\n}\n\n.subtitle {\n font-size: 1.1em;\n}\n\n.tiddler .button {\n padding: 0.2em 0.4em;\n}\n\n.tagging {\nmargin: 0.5em 0.5em 0.5em 0;\nfloat: left;\ndisplay: none;\n}\n\n.isTag .tagging {\ndisplay: block;\n}\n\n.tagged {\nmargin: 0.5em;\nfloat: right;\n}\n\n.tagging, .tagged {\nfont-size: 0.9em;\npadding: 0.25em;\n}\n\n.tagging ul, .tagged ul {\nlist-style: none;margin: 0.25em;\npadding: 0;\n}\n\n.tagClear {\nclear: both;\n}\n\n.footer {\n font-size: .9em;\n}\n\n.footer li {\ndisplay: inline;\n}\n\n* html .viewer pre {\n width: 99%;\n padding: 0 0 1em 0;\n}\n\n.viewer {\n line-height: 1.4em;\n padding-top: 0.5em;\n}\n\n.viewer .button {\n margin: 0em 0.25em;\n padding: 0em 0.25em;\n}\n\n.viewer blockquote {\n line-height: 1.5em;\n padding-left: 0.8em;\n margin-left: 2.5em;\n}\n\n.viewer ul, .viewer ol{\n margin-left: 0.5em;\n padding-left: 1.5em;\n}\n\n.viewer table {\n border-collapse: collapse;\n margin: 0.8em 1.0em;\n}\n\n.viewer th, .viewer td, .viewer tr,.viewer caption{\n padding: 3px;\n}\n\n.viewer table.listView {\n font-size: 0.85em;\n margin: 0.8em 1.0em;\n}\n\n.viewer table.listView th, .viewer table.listView td, .viewer table.listView tr {\n padding: 0px 3px 0px 3px;\n}\n\n.viewer pre {\n padding: 0.5em;\n margin-left: 0.5em;\n font-size: 1.2em;\n line-height: 1.4em;\n overflow: auto;\n}\n\n.viewer code {\n font-size: 1.2em;\n line-height: 1.4em;\n}\n\n.editor {\nfont-size: 1.1em;\n}\n\n.editor input, .editor textarea {\n display: block;\n width: 100%;\n font: inherit;\n}\n\n.editorFooter {\n padding: 0.25em 0em;\n font-size: .9em;\n}\n\n.editorFooter .button {\npadding-top: 0px; padding-bottom: 0px;}\n\n.fieldsetFix {border: 0;\npadding: 0;\nmargin: 1px 0px 1px 0px;\n}\n\n.sparkline {\n line-height: 1em;\n}\n\n.sparktick {\n outline: 0;\n}\n\n.zoomer {\n font-size: 1.1em;\n position: absolute;\n padding: 1em;\n}\n\n.cascade {\n font-size: 1.1em;\n position: absolute;\n overflow: hidden;\n}\n/*}}}*/
<<tabs txtMoreTab Orphans 'Orphaned tiddlers' TabMoreOrphans Shadowed 'Shadowed tiddlers' TabMoreShadowed>>
This site/document was created with <nowiki>TiddlyWiki.</nowiki> [[TiddlyWiki|http://www.tiddlywiki.com]] is a fantastic open source wiki / self-contained single file webdocument / website that supports html, javascript, and css. It is incredibly versatile. To learn more follow the link.
''Tools and Required Items''\n\nYou will need only two things to complete everything!\n\n*An XP installation source\n*A Linux live CD ([[Knoppix|http://www.knoppix.org]])\n\nYes that’s right that’s all you will need! You will only use open source software and it is all FREE!\n\nAny Linux live cd/dvd will work as long as it supports the ntfsprogs package (might want to create and restore from the same version of ntfsprogs though). The instructions I provide are exactly the same for Knoppix or System Rescue CD, or any other one, although I default to explaining from a Knoppix perspective. Knoppix and System Rescue CD include Gparted. Gparted’s gui is pleasant and easy to understand.\n\nLet me take this opportunity to say that I have used extensively the great majority of the most popular products in the clone/partition software world. I can’t say enough about open source software. It just works. If you are considering a product like Ghost or PM – I can’t implore you enough to NOT buy it! You will pay for software that is not as good as their free counterparts, you will have problems sooner or later, and you will never get any help from their incredibly poorly written guides, but go ahead, especially if you enjoy waiting two hours on a helpline to speak with a nice fellow in India on a two second delayed connection only to have your problem go unsolved. With a good Linux live cd, such as knoppix or the system rescue cd, you can do almost anything and fix almost any problem. Do not misperceive this as complex, it may take some time to feel comfortable using a Linux live environment, but much less than you will inevitably spend fixing the problems that come with using the horrendous commercial software I recently mentioned. \n\nYou may use your xp install cd to install, which is perfectly fine, but an interesting option exists to create your own xp install cd. Allow me to highlight a product and a website that that make this possible – [[nLite|http://www.nliteos.com]] is a wonderful product and [[msfn|http://unattended.msfn.org/unattended.xp]] has a wonderful site for unattended xp installations.\n\nWhen creating your own xp install cd you gain real control over the installation. Some things you can do include: modify your install files to remove unnecessary os items, slipstream service packs, add your own custom items to the install cd, automatically install drivers and other programs, and a slew of other hacks that are really impressive, and it can do all of this without ever prompting you too! I recommend it, even though cloning may reduce the need for such a product.\n
[[Donate / Questions|Donate]]\n[[DownloadWiki]]\n[[TiddlyWiki]]
''Using the DD Command''\n\nI use the ‘dd’ command to backup the master boot record. The ‘dd’ command is extremely powerful! Please familiarize yourself with the man pages first! Triple check you have exactly what you want as in input (if=) and what you will be writing to (of=). One simple tiny mistake with this command and you can really screw things up! That said it is a tremendously useful tool. Since we are using a potentially dangerous tool we want to backup the partition table in an easily readable format so that we can rewrite the partition table in case you accidentally overwrite it. If, you have to re-write the partition table, I recommend using Ranish Partition Manager. Remember it doesn’t support ntfs formatting, but we would not use it for this reason – we use it to simply re-write the partition table which is completely operating system agnostic.\n\nIf you are not familiar with the ‘dd’ command read-on, otherwise, please skip ahead to backup the master boot record.\n\nThe command ‘dd’ operates at the disk level and reads the actual sectors on the hard drive. Some brief and basic details on the command:\n\nif= this is the source, read from, or what will be written.\nof= this is the target, wrote to, or what will be overwritten.\nbs=X the block size to read, the default is 512, or exactly one sector\ncount=X the number of times the block size is read\nskip=X the number of blocks to skip on the input file or device, before reading\nseek=X the number of blocks to skip on the output file or device, before writing\n\nSome examples:\n\ndd if=/dev/sda of=example bs=1 count=512\ndd if=/dev/sda of=example bs=2 count=256\ndd if=/dev/sda of=example count=1\n\nThe three examples above will yield the same results – a file ‘example’ with a copy of the first 512 bytes, or the first sector, of the first hard drive. To make any sense of the output you will have to open the file in a text editor that can convert to hexadecimal.\n \ndd if=/dev/sda of=/dev/sdb bs=1 skip=446 seek=446 count=64\n\nThis example will skip the first 446 blocks or bytes in this case, since I set bs=1, of the first hard drive, and then copy the next 64 blocks (bytes in this case) and write those values to blocks (bytes) 447-510 on the second hard drive. Bytes 511 and 512 are always the same.\n\nPlease familiarize yourself you the man pages if you are not certain.\n
You most likely came here from google or a search engine looking for something specific - you can find exactly what you were looking for - it may take some navigating. This guide is quite thorough and should answer many of your questions. Be patient. \n\nThe entire guide is contained in the left menu in chronologically ordered pieces. To start from the beginning, simply click on [[Introduction » |Introduction]] in the left menu.\n\nIf you would prefer to view the entire document displayed all at once, in a long vertical manner so you can scroll it, then select [[The Whole Document|WholeDocument]] button on the left menu.\n\nThis site / document was created with [[TiddlyWiki|http://www.tiddlywiki.com]]. To learn more click on the link. Basically you can download this entire document, lose none of the functionality while viewing from your desktop, and you can edit and alter it as you like! Simply click the DownloadWiki button in the top menu.\n
<!--{{{-->\n<div class='toolbar' macro='toolbar closeTiddler closeOthers +editTiddler'></div>\n<div class='title' macro='view title'></div>\n<div class='tagging' macro='tagging'></div>\n<div class='viewer' macro='view text wikified'></div>\n<div class='tagClear'></div>\n<!--}}}-->
<<tiddler [[Introduction]]>>\n<<tiddler [[Reasons to Clone]]>>\n<<tiddler [[Resizing Partitions]]>>\n<<tiddler [[Partitioning Traps]]>>\n<<tiddler [[Cloning to Different Computers]]>>\n<<tiddler [[Before Getting Started]]>>\n<<tiddler [[My System]]>>\n<<tiddler [[Basic Idea]]>>\n<<tiddler [[Tools and Required Items]]>>\n<<tiddler [[Starting From Scratch]]>>\n<<tiddler [[Wipe the Hard Drive]]>>\n<<tiddler [[Partition the Hard Drive]]>>\n<<tiddler [[Installing and Configuring XP]]>>\n<<tiddler [[Best Practices Before Cloning]]>>\n<<tiddler [[Prepare Sysprep]]>>\n<<tiddler [[Remove the Pagefile]]>>\n<<tiddler [[Clean the Partition]]>>\n<<tiddler [[Defragment the Partition]]>>\n<<tiddler [[Wipe the Partition]]>>\n<<tiddler [[Modify the Registry]]>>\n<<tiddler [[Run Sysprep]]>>\n<<tiddler [[Install the Boot Manager]]>>\n<<tiddler [[Cloning XP]]>>\n<<tiddler [[Using the DD Command]]>>\n<<tiddler [[Backup the Master Boot Record]]>>\n<<tiddler [[Restoring the Image]]>>\n<<tiddler [[Resize the Partition]]>>\n<<tiddler [[Modify Boot.ini]]>>\n<<tiddler [[Modify Boot.ini on the Second Hard Drive]]>>\n<<tiddler [[Hexedit the NTFS Starting Sector]]>>\n<<tiddler [[Finishing Thoughts]]>>\n
''Wipe the Hard Drive''\n\nOpen a root shell. You may have to type “su” at the command prompt.\n\nknoppix@knoppix:~$ su\nroot@knoppix: /ramdisk/home/knoppix:\n\nWipe your hard drive – delete everything – you will lose everything! If, at this point, you are debating whether to delete that rescue partition that dell, sony, or hp put on your hard drive – you are probably in over your head! Take more time with things. Those partitions are largely useless; you can recreate any of the fixes they were designed for with other boot cd/dvd’s or any xp install cd.\n\nSaving a discussion concerning the thoroughness of properly wiping a hard drive, for simplicity, I recommend:\n\n[root@knoppix] dd if=/dev/zero of=/dev/sda\n\nThis command will write zeros over the first hard drive (as noted in my system description, I have two sata drives, thus /sda, if you use an ide interface then the drive would be /hda). This command will also work:\n\n[root@knoppix] dd if=/dev/urandom of=/dev/sda\n\nAs you might have guessed, this writes random characters on the hard drive. I sometimes prefer to write zeros on the hard drive that way if I’m inspecting parts of the hard drive later to see what was or was not written by some os, boot manager, program, or whatever I can distinguish better because I know it was all zeros at one point.\n\nThe dd command is extremely powerful! Please familiarize yourself with the man pages first! Triple check you have exactly what you want as in input (if=) and what you will be writing to (of=). One simple tiny mistake with this command and you can really screw things up! That said, it is a tremendously useful tool and I use it later as well.\n\nThis command will take a while. If your computer writes 20MB / second and your hard drive is 100GB this will take 5000 seconds. (3600 seconds / hour)\n\nFor a quicker option just open Gparted and delete all partitions. Then run the same command above and just let it run for a minute or so then stop it. This method is not as clean, but will work.\n\nNow you are ready to partition the hard drive!\n
''Wipe the Partition''\n\nThis is optional, but I would recommend this because it will increase the compressability of your image. Wiping has different meanings; in this case, we want something that writes zeros to the free space on the partition. I prefer Eraser, from Heidi Computing, while in xp. Or, execute the following commands in the Linux live environment, in the partition to be cloned, before cloning:\n\n[root@knoppix] dd if=/dev/zero > zerofile.file\n\nThen,\n\n[root@knoppix] rm zerofile.file\n\nThis will have the effect of writing zeros on the free space in the partition until there is no free space left, and then you simply delete the file.\n