Moving Windows to a Different Hard Disk/RAID Controller Without Reinstalling Overview One of the trends in personal computing these days is the prevelance of more options for hard disks and RAID systems than have been available in the past. As a result, many people want to move towards one of these systems as an upgrade, but at the same time want to avoid the hassle of reinstalling Windows and all applications.

While Norton Ghost 15.0 uses a powerful disk-cloning technology, it can also be used to simply back up your data as Norton Save & Restore 2.0 used to do. This is because the ability to backup specific files or folders was added in this latest release over the previous one (12.0), making it more ‘consumer-friendly’.

This has been exceedingly difficult and in some cases even impossible do to. However, with this guide, you'll be able to perform this task in most cases with most hardware configurations. What You Can and Cannot Do With This Guide This guide is applicable to the person who has Windows currently starting up from one hard disk/hard disk controller combination, and wants to start that same Windows installation up from a different hard disk/hard disk controller on the same computer. For instance, you may want to upgrade from a single-disk installation of Windows to a RAID installation, or from an IDE drive to a SCSI drive, or from an IDE drive to a native-mode SATA drive. Portfolio pedagoga psihologa dou obrazec 2.

In general, this guide will work for any situation where the mass storage controller that has to be used for Windows startup is going to change. This guide is NOT for adding another drive or controller to an existing system when the Windows installation doesn't move from it's existing controller. That is a much easier task and can be done with standard driver installation and the Disk Management utility in Windows. This guide is NOT for moving a Windows installation to completely different hardware (like changing your motherboard). There are some procedures posted on the Internet for that already. The guide is NOT for moving a hard drive within a system where the disk controller that is being used either does not change or uses the same drivers as the old one, or where Windows already has built-in drivers for the new controller (like a standard IDE controller).

Windows and Mass Storage Controllers Windows treats all mass storage controllers the same way. Whether it's a standard IDE controller, SATA controller, SCSI controller, or RAID controller, Windows has to have a driver for it in order to use it.

Once Windows has a driver installed for the controller, Windows can start up from a hard drive attached to that controller as long as the machine's BIOS can use the controller as the boot device. When installing Windows for the first time on a system, most of the time no concern need be given to the mass storage controller, because in the past, 90% of the time, the storage controller is a standard IDE controller which Windows already has drivers for on its installation CD. Windows will detect the standard IDE controller and use it's own drivers for it, thus enabling Windows to start up from the IDE controller. If Windows does not have a driver on its CD for your system, the Windows text-mode setup program tells you that Windows cannot find a mass storage controller in your system, and prompts you to insert a manufacturer-supplied driver disk. This is the method to install mass storage controller drivers for most SCSI, RAID, and now some SATA controllers. Windows reads the driver off the floppy disk, and uses that driver to start up after installation.

If any situation arises where Windows does not have a driver installed for the mass storage controller you're starting up from, you will get a blue screen STOP error, usually with the error STOP 0x0000007B (INACCESSIBLE_BOOT_DEVICE). If you've ever tried to copy a Windows installation from one controller to another with one of the partition copy tools and then tried to start it up, this is probably what you got. The key item in this procedure that makes it work is that the procedure loads drivers for a storage controller that Windows will start up on before moving Windows to that storage controller. Once Windows has seen the storage controller and has had drivers loaded for it, Windows can now use that storage controller as the startup controller. Shablon dlya oformleniya yubilejnogo adres. Requirements to Proceed To proceed with this procedure, you will need the following: ■The Windows installation that you want to move must be Windows 2000 Pro, 2000 Server, 2003 Server, or XP. ■The old hard drive controller is currently installed in the system, drivers for it are installed in Windows, and the hard drive holding the current Windows installation is attached to that controller, and Windows currently starts up in this configuration. ■You will need some type of tool to copy a partition from one drive to another if you will be moving the Windows installation to a different hard drive as well as a different controller.