Re: How Do You Increase Size of Windows 200x Boot Volume?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance


"Carl Nettelblad" <cnettel@xxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:eycxUP1HGHA.2064@xxxxxxxxxxxxxxxxxxxxxxx
>
> "Pegasus (MVP)" <I.can@xxxxxxx> wrote in message
> news:OOwcPZ0HGHA.2064@xxxxxxxxxxxxxxxxxxxxxxx
> > There are several well-documented processes for this type of thing.
> > Here are a few of them:
> > a) Install a temporary version of Win200 Server on your new disk
> > in a folder other than c:\Windows, then use ntbackup.exe to
> > restore the previously backed up version.
> > b) Use an imaging program such as Acronis, Ghost or DriveImage.
> > c) Boot the server with a Bart PE boot CD, then use xcopy.exe
> > with the appropriate switches to copy all files & folders to the
> > new disk.
> >
> > I think that method a) is a little tedious, so I usually use methods b)
> > or c). Method c) is particularly useful when the source disk is
> > damaged, because imaging programs tend to baulk at them.
> >
> >
>
> It's also possible to "just" image the disk with sysstate and all by
> NTbackup in the current installation, but restoring to the new disk. After
> that, it's only a matter of mounting the SYSTEM hive of the new disk and
> manipulating the volume mappings to make the disk signature of the new
disk
> point to the old drive letter. In the process, one will of course also
have
> to discard or change the drive letter association of the old disk.
>
> (HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices is the relevant registry key --
> note that it has to be in the registry hives of the copy, NOT the source.)
>
> This can also be highly useful if the two disks are on different
> controllers, or anything else that may cause INACCESSIBLE_BOOT_DEVICE when
> only copying.
>
> I would naturally not recommend this to anyone that won't touch regedit in
> general, but I've done it quite a few times. I'm actually kind of
surprised
> that you can use method "c" without this final fix afterwards.
>
> /Carl
>

Method c) works most of the time because Windows will
reassign its drive letters at boot time when it can no longer
find the old volume signatures. It has the same effect as
running fixmbr in Recovery Console mode, which is a method
recommended in some KB articles to fix drive letter assignments.
If the drive letters come out incorrect then your registry hack is
easily applied.

By the way, I thought that ntbackup will restore the System
State to the original disk only, not to some other disk. It's
a little while since I tried but this is my recollection. Any
comments?


.

Relevant Pages

  • Re: Can I boot of an XP System disk, nested in a logical volume
    ... I'll boot of Partition Magic or some other kind of magic and fix it that-a-way. ... It's been a long time since I messed with partitions like this, but in the back of my head I have this fragment about boring registry hands-on editing, 'derived Disk ID's' and the 'Master Boot Sector' -- that's S as in 'Senile'. ... One reason for the drive letter change on cloned drives is to keep the parent drive hooked up the first time the clone is booted, being that the clone has the same Mount Manager database, and being that the Mount Manager *always* respects drive letter assignments, it will see the parent drive and its valid disk signature and assign the C: drive letter to the original C: drive, so there will be no C: letter available for the clone. ...
    (microsoft.public.windowsxp.basics)
  • Re: HD not being read
    ... click Disk Management. ... Right-click the disk you want to initialize, ... Change Drive Letter and Paths. ...
    (microsoft.public.windowsxp.hardware)
  • Re: Boot drive letter
    ... Dave Patrick ....Please no email replies - reply in newsgroup. ... | After a hard disk failure I've installed a new one and loaded WinXP Home ... | online backup utility refuses to install on any drive other than C: ... | I tried changing the drive letter from G: to C: in Disk Management but it ...
    (microsoft.public.windowsxp.configuration_manage)
  • Re: Cloning windows 2000
    ... >> it has booted at least once and rebuilt its drive letter table. ... contents to this first partition. ... If you boot old-2K with the new drive in place and fresh partitions visible, ... old disk has that, so it might end up being 'H' or something else. ...
    (microsoft.public.win2000.general)
  • Re: Windows logon failure
    ... "Pegasus (MVP)" wrote: ... Temporarily install the problem disk as a slave disk in ... Find out the current drive letter for the bad disk's drive C:. ...
    (microsoft.public.windowsxp.general)