RE: How to Move System from D: to NEW C: ??

#11 01-05-2006, 06:17 AM

Bonobo,

You have created your dual boot with Windows XP and the loader is on the
original DOS disk. So if you do not take
precautions when you throw away the old Dos disk 0 you will not be able to
boot the new disk which has Windows installed on it.
BEFORE making any changes make a backup if you can.

Your boot manager is in boot.ini on disk 0. To edit it boot into Windows
It is a hidden file so to see it in Windows you need to enable hidden and
system files in the folder options view properties and find the file in root
folder of the boot drive For a single disk with a single whole partition
your boot.ini needs to be on that disk.
Uncheck the read only attribute of boot.ini which is on the DOS disk and
copy it into the Windows disk. You should them edit it to look something
like this:

[boot loader]
timeout=5
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOW S
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windo ws XP" /fastdetect
/noexecute=optin
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Safe Mode"
/fastdetect/safeboot:minimal/sos/bootlog
(You should leave in the Recovery Console line in as you already have it.)

After editing the boot.ini, you want to make sure that you can use it
effectively with out the default restrictions applied in the Recovery
Console
Start the Local Security Settings Editor Start > Run and type in
secpol.msc
and navigate to \Security Settings\Local Polices\\Security Options in the
tree.
Then double click and enable the Recovery Console line : Allow floppy copy
and access to all drives and folders.
Close the dialog.

Reboot the computer and boot into the recovery console.
When the welcome message appears
select D:\Windows

You can see all the commands by typing Help

type this command
bootcfg /rebuild

Check the boot.ini so that it is correct as you wrote above in Windows.

type these commands
Map
Bootcfg/scan
to see what you have. Assuming you have C and D
Type fixboot D
Type fixmbr D
You can leave out the Drive if only D is displayed above

Bootcfg /list
to see that the boot .ini now looks OK that is just one drive with options
for normal and safe modes and recovery console.

Reboot and in the bios switch your boot priorities so that you now boot from
the Windows Disk. If everything is OK you can now remove the old disk.

I do not think it is worth trying to change the drive letter of the new
Windows list. The software exists to do it as you say but it is not without
risk and for a full installation not likely to work.

If it is really important to have C as the System Disk, back up your data
using the old Dos Disk. Create the Windows transfer file using the Files and
Settings Transfer Wizard as explained in Start > Help. Then in the bios
Switch the boot order and reinstall Windows from your CD with a clean new
install. Restore the Settings with the Wizard and reinstall the applications
which have not been transferred with the Wizard.

Uncle John
"Bonobo" <Bonobo@discussions.microsoft.com> wrote in message
news:51AD456A-DD32-456D-9BAF-B97D61762B59@microsoft.com...
> The loader is on C:
>
> Original system only had one drive (WD 40GB w/Win98SE). After XP was
> released, bought the 80GB (Now D

and installed XP. Wanted to continue
> to
> use 98, since I had quite a bit of development software loaded there, thus
> the dual-boot.
>
> "Uncle John" wrote:
>
>> Bonobo
>>
>> Where is the boot loader located? Is it on disk 0 or disk 1? Or on a
>> removable media? If you post here I will think about how best to solve
>> your
>> problem, which I now understand, and reply tomorrow.
>>
>> --
>> Uncle John
>> "Bonobo" <Bonobo@discussions.microsoft.com> wrote in message
>> news:2FC82D84-2FFA-4EAE-86E4-A3282F707AC0@microsoft.com...
>> >I do appreciate all the comments that have been given so far. I've
>> >taken
>> > into consideration all the issues raised.
>> >
>> > Will try to answer some of Uncle John's concerns within his post. See
>> > below.
>> >
>> > "Uncle John" wrote:
>> >
>> >> Pegasus
>> >>
>> >> I believe you misunderstood me, I said
>> >>
>> >> " Casper XP or Acronis True Image do routinely copy or clone the old
>> >> drive C
>> >> to the new drive D. It will boot and Windows will of course call the
>> >> new
>> >> drive D and call the old drive C ........."
>> >>
>> >> That is, if the original system disk is
>> >> " Disk 0 'D' " and the new disk is
>> >> " Disk1 'C' "
>> >
>> > The original system disk is Disk0 'C' ; which is a 40GB WD with Win98SE
>> > that
>> > is on the way 'South'
>> > Disk1 'D'; is a 80GB WD with XP Pro.
>> >
>> > The system is set for dual booting; I can select Win98, XP or Recovery
>> > Console. Both drives are formatted Fat32.
>> >
>> >> the drive letter "D" will be maintained if the new disk is booted as
>> >> the
>> >> new
>> >> system disk the drive letters will be reversed. In the management
>> >> Console
>> >> you will then see
>> >> "Disk 1 'D'
>> >> "Disk 0 'C' "
>> >>
>> >> To go further and change the Drive letter of the [new] System Disk to
>> >> 'C'
>> >> I
>> >> would need use software that usually works involving the change of
>> >> mount
>> >> points and registry addresses which is very time consuming and not
>> >> 100%
>> >> certain: I only do this if the drive letter had been corrupted
>> >> already.
>> >>
>> >
>> > I've seen a post (can't recall where) that states that there is some
>> > utility
>> > that will allow 'Find & Replace' on enties in the Registry. Given some
>> > of
>> > the other problems Pegasus has outlined, not sure if this will entirely
>> > fix
>> > all the problems.
>> >
>> > Would like to know if anyone has had experience with this sort of
>> > utility.
>> >
>> >
>> >> Since neither of us saw the original post we do not know why the
>> >> poster
>> >> was
>> >> trying to change the drive letter so may this technical chat is
>> >> irrelevant!
>> >> --
>> >
>> > In a nutshell, I would like to wind up with C: being XP on a 160GB
>> > drive
>> > (New), the current XP disk (which is D

to be used as additional
>> > storage
>> > (after everything has been moved to the new disk and cleaned up to see
>> > all
>> > current programs and Registry entries as belonging on C

. This takes
>> > the
>> > current C: (which is on the way South) out of the equation.
>> >
>> > Didn't think it would be this difficult, but learning everyhour.
>> > Again,
>> > thanks for all the feedback and if there are others who have gone
>> > through
>> > this, would really appreciate hearning about your experience.
>> >
>> > Bonobo1
>> >
>> >
>> >> Uncle John
>> >> "Pegasus" <I.can@fly.com> wrote in message
>> >> news:eQOy3FA%23FHA.1312@TK2MSFTNGP09.phx.gbl...
>> >> >I did not see the "very" original post, hence my reply to what
>> >> > appears to be the first respondent.
>> >> >
>> >> > I have never ever seen a successful move of a Windows
>> >> > installation from one drive to another, unless the drive
>> >> > letter was maintainted (which is, in fact, possible). There
>> >> > are three reasons:
>> >> > - The registry is full of references to the original drive letter.
>> >> > They would have to be fixed, without inadvertently altering
>> >> > strings that do not relate to drive letters (e.g. altering
>> >> > "Office:smarttags" to "Officc:smarttags").
>> >> > - There are a number of binary references in the registry to
>> >> > the system drive letter. They must be changed too, without
>> >> > inadvertent corruption.
>> >> > - There are also some disk files that contain drive letter
>> >> > references.
>> >> >
>> >> > Now I'm not dogmatic about this. When I see a reasonable number
>> >> > of independent reports from competent posters that products like
>> >> > TrueImage can do it reliably then I'll accept it. Your claim is one
>> >> > solitary report - perhaps there will be more.
>> >> >
>> >> >
>> >> > "Uncle John" <unclejohn@uselesnospam.com> wrote in message
>> >> > news:#gbbtz$9FHA.2676@TK2MSFTNGP15.phx.gbl...
>> >> >> Pegasus
>> >> >> Is the original post, which I do not see, talking about changing
>> >> >> drives
>> >> >> or
>> >> >> drive letters?
>> >> >> Of course it is easy simple to move System from Windows Drive "D"
>> >> >> to
>> >> >> "C"
>> >> >> provided the user remembers that Windows does not assign drive
>> >> >> letter
>> >> >> in
>> >> > the
>> >> >> same order as the bios.
>> >> >>
>> >> >> Casper XP or Acronis True Image do routinely copy or clone the old
>> >> >> drive
>> >> > C
>> >> >> to the new drive D. It will boot and Windows will of course call
>> >> >> the
>> >> >> new
>> >> >> drive D and call the old drive C but underneath the GUI it knows
>> >> >> that
>> >> >> what
>> >> >> it says it what it means, a bit like Alice in Wonderland!
>> >> >>
>> >> >> With boot disk switching in the bios it can be tricky, without
>> >> >> using
>> >> >> Explorer, to know which disk has booted unless some prominent new
>> >> >> object
>> >> > it
>> >> >> placed on the original desktop just before rebooting
>> >> >>
>> >> >> --
>> >> >> Uncle John
>> >> >> "Pegasus (MVP)" <I.can@fly.com> wrote in message
>> >> >> news:uJ2ISo99FHA.356@TK2MSFTNGP12.phx.gbl...
>> >> >> > It seems there is some misinformation in this thread. The basic
>> >> >> > facts
>> >> > are:
>> >> >> >
>> >> >> > a) If WinXP saw the light of the day on drive D: then it must
>> >> >> > always
>> >> >> > run off a drive letter D:. The reason is simple: The registry
>> >> >> > is
>> >> >> > full
>> >> >> > of references to drive D:, and if the system drive is C: all
>> >> >> > of a
>> >> >> > sudden
>> >> >> > then you will end up with a very unhappy Windows installation.
>> >> >> >
>> >> >> > b) It is possible to run Windows off the very first partition
>> >> >> > while
>> >> > still
>> >> >> > calling it "Drive C:". Unfortunately it is not an easy matter
>> >> >> > to
>> >> >> > arrange
>> >> >> > this, and the probability of a mistake is high, resulting in
>> >> >> > an
>> >> >> > unbootable system.
>> >> >> >
>> >> >> > To avoid this type of problem in future, use a proper boot loader
>> >> >> > such
>> >> >> > as XOSL. It's free. It lets you install any number of OSs on
>> >> >> > separate
>> >> >> > partitions, each visible as drive C:.
>> >> >> >
>> >> >> > You can resolve your current predicament as follows. It will give
>> >> >> > you
>> >> >> > a large boot disk which you can use to store your data, with
>> >> >> > WinXP
>> >> >> > still running off drive D:.
>> >> >> >
>> >> >> > 1. Install your 160 GByte disk temporarily as the secondary slave
>> >> >> > disk.
>> >> >> > 2. Launch WinXP.
>> >> >> > 3. Partition/format the 160 GByte disk.
>> >> >> > 4. Mark it as "active".
>> >> >> > 5. Copy these hidden files to it:
>> >> >> > c:\ntldr
>> >> >> > c:\ntdetect.com
>> >> >> > c:\boot.ini
>> >> >> > 6. Disconnect the 40 GByte disk.
>> >> >> > 7. Make the 160 GByte disk the primary master disk.
>> >> >> > 8. See if you can boot into WinXP.
>> >> >> > 9. If you can't, use your WinXP CD to boot into the Recovery
>> >> >> > Console,
>> >> >> > then issue these commands:
>> >> >> > fixboot
>> >> >> > fixmbr
>> >> >> >
>> >> >> > This is a safe path to follow, because you keep both existing
>> >> >> > disks
>> >> >> > intact.
>> >> >> >
>> >> >> >
>> >> >> > "BlÄckCaT" <BlckCaT@discussions.microsoft.com> wrote in message
>> >> >> > news:5E632732-55FD-49AF-BD54-4E3B12E4276A@microsoft.com...
>> >> >> >> Hello Bonobo,
>> >> >> >>
>> >> >> >> All that you want to do is possible, there are threads in these
>> >> >> >> forums
>> >> >> >> for
>> >> >> >> doing a repair install of Xp as well as how to go about swapping
>> >> >> >> hard
>> >> >> > drives
>> >> >> >> with Xp already installed.
>> >> >> >>
>> >> >> >> Do a search on "Repair Install Xp" as well as swapping
>> >> >> >> harddrives
>> >> >> >> with
>> >> >> >> Xp
>> >> >> >> already loaded on it ( I've gone through it a few months ago
>> >> >> >>

)
>> >> >> >> all
>> >> >> >> went
>> >> >> >> well the forums here are great....
>> >> >> >>
>> >> >> >> Cheers and good luck, you'll have no problems doing what you
>> >> >> >> have
>> >> >> >> planned.
>> >> >> >>
>> >> >> >> "Bonobo" wrote:
>> >> >> >>
>> >> >> >> > Have somewhat of a problem and not quite sure how to go about
>> >> >> >> > solving
>> >> >> >> > it
>> >> >> > and
>> >> >> >> > remain legal.
>> >> >> >> >
>> >> >> >> > Current system is:
>> >> >> >> > C:\ = Western Digital 40GB (Win98SE) - Going bad
>> >> >> >> > D:\ = Western Digital 80GB (XP Pro) - Used the most
>> >> >> >> >
>> >> >> >> > Current configuration is dual-booted. Very seldom do I use
>> >> >> >> > the
>> >> >> >> > Win98
>> >> >> > and
>> >> >> >> > have copied and save most of the files I'd want to keep. Both
>> >> >> >> > disk
>> >> > are
>> >> >> > FAT32.
>> >> >> >> >
>> >> >> >> > What I would like to wind up with in the end is:
>> >> >> >> > C:\ = Western Digital 160GB (With copied system from D:
>> >> >> >> > above)
>> >> >> >> > NEW
>> >> >> > Drive
>> >> >> >> > D:\ = Western Digital 80GB (Used for additional storage
>> >> >> >> > after
>> >> >> > everthing
>> >> >> >> > has been copied to the NEW C: and verified working correctly
>> >> >> >> > and
>> >> >> >> > old
>> >> > OS
>> >> >> >> > deleted).
>> >> >> >> >
>> >> >> >> > This would then net the original C:\ (WD 40GB) gone.
>> >> >> >> >
>> >> >> >> > I've read in various post that one possible solution to the
>> >> >> >> > above
>> >> >> >> > is
>> >> > to
>> >> >> > use
>> >> >> >> > the Drive manufacturer's copy utility to make the move (if
>> >> >> >> > there
>> >> >> >> > is
>> >> >> > one).
>> >> >> >> > Assuming that one exist and it works, then my question
>> >> >> >> > becomes:
>> >> >> >> >
>> >> >> >> > How will I get the Registry to know that programs now exist on
>> >> >> >> > C:
>> >> >> >> > rather
>> >> >> >> > than D:, and are there any other problems I might have to
>> >> >> >> > worry
>> >> >> >> > about.??
>> >> >> >> >
>> >> >> >> > I'm sure this has been asked numerous of times, but I've
>> >> >> >> > looked
>> >> >> >> > and
>> >> >> >> > have
>> >> >> > not
>> >> >> >> > found an answer that really makes me comfortable with
>> >> >> >> > undertaking
>> >> >> >> > the
>> >> >> > task.
>> >> >> >> > It's not a matter of will the C: die, but when; and I'd like
>> >> >> >> > to
>> >> >> >> > make
>> >> >> >> > the
>> >> >> > move
>> >> >> >> > before it does.
>> >> >> >> >
>> >> >> >> > Thanks for any assistance!
>> >> >> >
>> >> >> >
>> >> >>
>> >> >>
>> >> >
>> >> >
>> >>
>> >>
>> >>
>>
>>
>>

#12 01-05-2006, 06:17 AM

Thank you Uncle John and all the other and future contributors to this
discussion. I've gained a bit more knowledge about the intricate and
sometimes conflicting workings of this OS called "XP".

Now I'm going to sit, digest, and map a step-by-step plan for this task. I
hope this post will not keep others from offering advice if they've
accomplished this task; never too much information.

If I find that I'm totally confused, I'll probably go out and buy another
smaller disk, copy the current C: to it, and then try to plan how to copy the
current D: to the 160GB that I have just purchased. Even this method seems
to present problems that I'd have to really think about.

Again, thanks for all the help; but don't let this stop folk from
contributing to the discussion.

Bonobo

"Uncle John" wrote:

> Bonobo,
>
> You have created your dual boot with Windows XP and the loader is on the
> original DOS disk. So if you do not take
> precautions when you throw away the old Dos disk 0 you will not be able to
> boot the new disk which has Windows installed on it.
> BEFORE making any changes make a backup if you can.
>
> Your boot manager is in boot.ini on disk 0. To edit it boot into Windows
> It is a hidden file so to see it in Windows you need to enable hidden and
> system files in the folder options view properties and find the file in root
> folder of the boot drive For a single disk with a single whole partition
> your boot.ini needs to be on that disk.
> Uncheck the read only attribute of boot.ini which is on the DOS disk and
> copy it into the Windows disk. You should them edit it to look something
> like this:
>
> [boot loader]
> timeout=5
> default=multi(0)disk(0)rdisk(0)partition(1)\WINDOW S
> [operating systems]
> multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windo ws XP" /fastdetect
> /noexecute=optin
> multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Safe Mode"
> /fastdetect/safeboot:minimal/sos/bootlog
> (You should leave in the Recovery Console line in as you already have it.)
>
> After editing the boot.ini, you want to make sure that you can use it
> effectively with out the default restrictions applied in the Recovery
> Console
> Start the Local Security Settings Editor Start > Run and type in
> secpol.msc
> and navigate to \Security Settings\Local Polices\\Security Options in the
> tree.
> Then double click and enable the Recovery Console line : Allow floppy copy
> and access to all drives and folders.
> Close the dialog.
>
> Reboot the computer and boot into the recovery console.
> When the welcome message appears
> select D:\Windows
>
> You can see all the commands by typing Help
>
> type this command
> bootcfg /rebuild
>
> Check the boot.ini so that it is correct as you wrote above in Windows.
>
> type these commands
> Map
> Bootcfg/scan
> to see what you have. Assuming you have C and D
> Type fixboot D
> Type fixmbr D
> You can leave out the Drive if only D is displayed above
>
> Bootcfg /list
> to see that the boot .ini now looks OK that is just one drive with options
> for normal and safe modes and recovery console.
>
> Reboot and in the bios switch your boot priorities so that you now boot from
> the Windows Disk. If everything is OK you can now remove the old disk.
>
> I do not think it is worth trying to change the drive letter of the new
> Windows list. The software exists to do it as you say but it is not without
> risk and for a full installation not likely to work.
>
> If it is really important to have C as the System Disk, back up your data
> using the old Dos Disk. Create the Windows transfer file using the Files and
> Settings Transfer Wizard as explained in Start > Help. Then in the bios
> Switch the boot order and reinstall Windows from your CD with a clean new
> install. Restore the Settings with the Wizard and reinstall the applications
> which have not been transferred with the Wizard.
>
> Uncle John
> "Bonobo" <Bonobo@discussions.microsoft.com> wrote in message
> news:51AD456A-DD32-456D-9BAF-B97D61762B59@microsoft.com...
> > The loader is on C:
> >
> > Original system only had one drive (WD 40GB w/Win98SE). After XP was
> > released, bought the 80GB (Now D

and installed XP. Wanted to continue
> > to
> > use 98, since I had quite a bit of development software loaded there, thus
> > the dual-boot.
> >
> > "Uncle John" wrote:
> >
> >> Bonobo
> >>
> >> Where is the boot loader located? Is it on disk 0 or disk 1? Or on a
> >> removable media? If you post here I will think about how best to solve
> >> your
> >> problem, which I now understand, and reply tomorrow.
> >>
> >> --
> >> Uncle John
> >> "Bonobo" <Bonobo@discussions.microsoft.com> wrote in message
> >> news:2FC82D84-2FFA-4EAE-86E4-A3282F707AC0@microsoft.com...
> >> >I do appreciate all the comments that have been given so far. I've
> >> >taken
> >> > into consideration all the issues raised.
> >> >
> >> > Will try to answer some of Uncle John's concerns within his post. See
> >> > below.
> >> >
> >> > "Uncle John" wrote:
> >> >
> >> >> Pegasus
> >> >>
> >> >> I believe you misunderstood me, I said
> >> >>
> >> >> " Casper XP or Acronis True Image do routinely copy or clone the old
> >> >> drive C
> >> >> to the new drive D. It will boot and Windows will of course call the
> >> >> new
> >> >> drive D and call the old drive C ........."
> >> >>
> >> >> That is, if the original system disk is
> >> >> " Disk 0 'D' " and the new disk is
> >> >> " Disk1 'C' "
> >> >
> >> > The original system disk is Disk0 'C' ; which is a 40GB WD with Win98SE
> >> > that
> >> > is on the way 'South'
> >> > Disk1 'D'; is a 80GB WD with XP Pro.
> >> >
> >> > The system is set for dual booting; I can select Win98, XP or Recovery
> >> > Console. Both drives are formatted Fat32.
> >> >
> >> >> the drive letter "D" will be maintained if the new disk is booted as
> >> >> the
> >> >> new
> >> >> system disk the drive letters will be reversed. In the management
> >> >> Console
> >> >> you will then see
> >> >> "Disk 1 'D'
> >> >> "Disk 0 'C' "
> >> >>
> >> >> To go further and change the Drive letter of the [new] System Disk to
> >> >> 'C'
> >> >> I
> >> >> would need use software that usually works involving the change of
> >> >> mount
> >> >> points and registry addresses which is very time consuming and not
> >> >> 100%
> >> >> certain: I only do this if the drive letter had been corrupted
> >> >> already.
> >> >>
> >> >
> >> > I've seen a post (can't recall where) that states that there is some
> >> > utility
> >> > that will allow 'Find & Replace' on enties in the Registry. Given some
> >> > of
> >> > the other problems Pegasus has outlined, not sure if this will entirely
> >> > fix
> >> > all the problems.
> >> >
> >> > Would like to know if anyone has had experience with this sort of
> >> > utility.
> >> >
> >> >
> >> >> Since neither of us saw the original post we do not know why the
> >> >> poster
> >> >> was
> >> >> trying to change the drive letter so may this technical chat is
> >> >> irrelevant!
> >> >> --
> >> >
> >> > In a nutshell, I would like to wind up with C: being XP on a 160GB
> >> > drive
> >> > (New), the current XP disk (which is D

to be used as additional
> >> > storage
> >> > (after everything has been moved to the new disk and cleaned up to see
> >> > all
> >> > current programs and Registry entries as belonging on C

. This takes
> >> > the
> >> > current C: (which is on the way South) out of the equation.
> >> >
> >> > Didn't think it would be this difficult, but learning everyhour.
> >> > Again,
> >> > thanks for all the feedback and if there are others who have gone
> >> > through
> >> > this, would really appreciate hearning about your experience.
> >> >
> >> > Bonobo1
> >> >
> >> >
> >> >> Uncle John
> >> >> "Pegasus" <I.can@fly.com> wrote in message
> >> >> news:eQOy3FA%23FHA.1312@TK2MSFTNGP09.phx.gbl...
> >> >> >I did not see the "very" original post, hence my reply to what
> >> >> > appears to be the first respondent.
> >> >> >
> >> >> > I have never ever seen a successful move of a Windows
> >> >> > installation from one drive to another, unless the drive
> >> >> > letter was maintainted (which is, in fact, possible). There
> >> >> > are three reasons:
> >> >> > - The registry is full of references to the original drive letter.
> >> >> > They would have to be fixed, without inadvertently altering
> >> >> > strings that do not relate to drive letters (e.g. altering
> >> >> > "Office:smarttags" to "Officc:smarttags").
> >> >> > - There are a number of binary references in the registry to
> >> >> > the system drive letter. They must be changed too, without
> >> >> > inadvertent corruption.
> >> >> > - There are also some disk files that contain drive letter
> >> >> > references.
> >> >> >
> >> >> > Now I'm not dogmatic about this. When I see a reasonable number
> >> >> > of independent reports from competent posters that products like
> >> >> > TrueImage can do it reliably then I'll accept it. Your claim is one
> >> >> > solitary report - perhaps there will be more.
> >> >> >
> >> >> >
> >> >> > "Uncle John" <unclejohn@uselesnospam.com> wrote in message
> >> >> > news:#gbbtz$9FHA.2676@TK2MSFTNGP15.phx.gbl...
> >> >> >> Pegasus
> >> >> >> Is the original post, which I do not see, talking about changing
> >> >> >> drives
> >> >> >> or
> >> >> >> drive letters?
> >> >> >> Of course it is easy simple to move System from Windows Drive "D"
> >> >> >> to
> >> >> >> "C"
> >> >> >> provided the user remembers that Windows does not assign drive
> >> >> >> letter
> >> >> >> in
> >> >> > the
> >> >> >> same order as the bios.
> >> >> >>
> >> >> >> Casper XP or Acronis True Image do routinely copy or clone the old
> >> >> >> drive
> >> >> > C
> >> >> >> to the new drive D. It will boot and Windows will of course call
> >> >> >> the
> >> >> >> new
> >> >> >> drive D and call the old drive C but underneath the GUI it knows
> >> >> >> that
> >> >> >> what
> >> >> >> it says it what it means, a bit like Alice in Wonderland!
> >> >> >>
> >> >> >> With boot disk switching in the bios it can be tricky, without
> >> >> >> using
> >> >> >> Explorer, to know which disk has booted unless some prominent new
> >> >> >> object
> >> >> > it
> >> >> >> placed on the original desktop just before rebooting
> >> >> >>
> >> >> >> --
> >> >> >> Uncle John
> >> >> >> "Pegasus (MVP)" <I.can@fly.com> wrote in message
> >> >> >> news:uJ2ISo99FHA.356@TK2MSFTNGP12.phx.gbl...
> >> >> >> > It seems there is some misinformation in this thread. The basic
> >> >> >> > facts
> >> >> > are:
> >> >> >> >
> >> >> >> > a) If WinXP saw the light of the day on drive D: then it must
> >> >> >> > always
> >> >> >> > run off a drive letter D:. The reason is simple: The registry
> >> >> >> > is
> >> >> >> > full
> >> >> >> > of references to drive D:, and if the system drive is C: all
> >> >> >> > of a
> >> >> >> > sudden
> >> >> >> > then you will end up with a very unhappy Windows installation.
> >> >> >> >
> >> >> >> > b) It is possible to run Windows off the very first partition
> >> >> >> > while
> >> >> > still
> >> >> >> > calling it "Drive C:". Unfortunately it is not an easy matter
> >> >> >> > to
> >> >> >> > arrange
> >> >> >> > this, and the probability of a mistake is high, resulting in
> >> >> >> > an
> >> >> >> > unbootable system.
> >> >> >> >
> >> >> >> > To avoid this type of problem in future, use a proper boot loader
> >> >> >> > such
> >> >> >> > as XOSL. It's free. It lets you install any number of OSs on
> >> >> >> > separate
> >> >> >> > partitions, each visible as drive C:.
> >> >> >> >
> >> >> >> > You can resolve your current predicament as follows. It will give
> >> >> >> > you
> >> >> >> > a large boot disk which you can use to store your data, with
> >> >> >> > WinXP
> >> >> >> > still running off drive D:.
> >> >> >> >
> >> >> >> > 1. Install your 160 GByte disk temporarily as the secondary slave
> >> >> >> > disk.
> >> >> >> > 2. Launch WinXP.
> >> >> >> > 3. Partition/format the 160 GByte disk.
> >> >> >> > 4. Mark it as "active".
> >> >> >> > 5. Copy these hidden files to it:
> >> >> >> > c:\ntldr
> >> >> >> > c:\ntdetect.com
> >> >> >> > c:\boot.ini
> >> >> >> > 6. Disconnect the 40 GByte disk.
> >> >> >> > 7. Make the 160 GByte disk the primary master disk.
> >> >> >> > 8. See if you can boot into WinXP.

#13 01-05-2006, 06:18 AM

Hello all:
After a couple of days of reading, I think I'll just opt to make
a clean install of XP on the 160GB drive and re-install all of my
programs; since I've save the data that's most important to me
(yeah, real boring task).

After reading various papers, I've come up with a schema I hope
will fulfill my needs, but I'd like to get some input relative to
any potential problems one might see based on experience.

My final setup will consist of two drives: Disk0 = 160GB and
Disk1 = 80GB (C: and D; respective), and the partitioning will
look something like the following. This is what I'm asking
advise on:

Drive 0 (160GB) C: 8.0 GB Primary Partition (Active): XP
and as little else as possible

C: 10 GB Alternate primary
(Hidden) for future OS

E: 60 GB Data: "My Documents",
IE Favorites folder & OE data store

F: 30 GB Programs

G: 1.5 GB Downloaded programs:
Original download preserved to assist in future reinstallations

H: 500MB Disposable Temp Files

I: 10 GB Downloads of various
program CDs

J: 40 GB Reserved for future
expansion (Empty space)

Drive 1 (80GB) D: 500MB Swap file / Pagefile (Primary
partition)

K: 18.5GB Multiple backups of
partitions C:, E:, F: G: using MS Backup

L: 61 GB Music files (WMA, WAV
and .ra (Real Player format)

Will be getting an External 160 GB that will hold the backups
from K: on the Drive 1 and periodic backups of L:

From the experience of folk that are "Power Users" as well as the
casual guy, do you see any problems with this proposed schema.
I'm not the type of person that believes that everything has to
be 'born here'. I'm sure there are some partitions that might be
a little too much as well as some that might not be large enough,
but off the top of my head, this is what I came up with.

Sorry for the post being soooo long, but wanted to try and
present without ambiguity.

Bonobo

"Pegasus" <I.can@fly.com> wrote in message
news:eQoxnfF%23FHA.1032@TK2MSFTNGP11.phx.gbl...
|
| "Bonobo" <Bonobo@discussions.microsoft.com> wrote in message
| news:2FC82D84-2FFA-4EAE-86E4-A3282F707AC0@microsoft.com...
| > I do appreciate all the comments that have been given so far.
I've taken
| > into consideration all the issues raised.
| >
| > Will try to answer some of Uncle John's concerns within his
post. See
| below.
| >
| > "Uncle John" wrote:
| >
| > > Pegasus
| > >
| > > I believe you misunderstood me, I said
| > >
| > > " Casper XP or Acronis True Image do routinely copy or
clone the old
| drive C
| > > to the new drive D. It will boot and Windows will of course
call the new
| > > drive D and call the old drive C ........."
| > >
| > > That is, if the original system disk is
| > > " Disk 0 'D' " and the new disk is
| > > " Disk1 'C' "
| >
| > The original system disk is Disk0 'C' ; which is a 40GB WD
with Win98SE
| that
| > is on the way 'South'
| > Disk1 'D'; is a 80GB WD with XP Pro.
| >
| > The system is set for dual booting; I can select Win98, XP or
Recovery
| > Console. Both drives are formatted Fat32.
| >
| > > the drive letter "D" will be maintained if the new disk is
booted as the
| new
| > > system disk the drive letters will be reversed. In the
management
| Console
| > > you will then see
| > > "Disk 1 'D'
| > > "Disk 0 'C' "
| > >
| > > To go further and change the Drive letter of the [new]
System Disk to
| 'C' I
| > > would need use software that usually works involving the
change of mount
| > > points and registry addresses which is very time consuming
and not 100%
| > > certain: I only do this if the drive letter had been
corrupted already.
| > >
| >
| > I've seen a post (can't recall where) that states that there
is some
| utility
| > that will allow 'Find & Replace' on enties in the Registry.
Given some of
| > the other problems Pegasus has outlined, not sure if this
will entirely
| fix
| > all the problems.
| >
| > Would like to know if anyone has had experience with this
sort of utility.
| >
| >
| > > Since neither of us saw the original post we do not know
why the poster
| was
| > > trying to change the drive letter so may this technical
chat is
| irrelevant!
| > > --
| >
| > In a nutshell, I would like to wind up with C: being XP on a
160GB drive
| > (New), the current XP disk (which is D

to be used as
additional storage
| > (after everything has been moved to the new disk and cleaned
up to see all
| > current programs and Registry entries as belonging on C

#14 01-05-2006, 06:18 AM

"Jim" wrote:
> Hello all:
> After a couple of days of reading, I think I'll just opt to make
> a clean install of XP on the 160GB drive and re-install all of my
> programs; since I've save the data that's most important to me
> (yeah, real boring task).
>
> After reading various papers, I've come up with a schema I hope
> will fulfill my needs, but I'd like to get some input relative to
> any potential problems one might see based on experience.
>
> My final setup will consist of two drives: Disk0 = 160GB and
> Disk1 = 80GB (C: and D; respective), and the partitioning will
> look something like the following. This is what I'm asking
> advise on:
>
> Drive 0 (160GB) C: 8.0 GB Primary Partition (Active): XP
> and as little else as possible
>
> C: 10 GB Alternate primary
> (Hidden) for future OS
>
> E: 60 GB Data: "My Documents",
> IE Favorites folder & OE data store
>
> F: 30 GB Programs
>
> G: 1.5 GB Downloaded programs:
> Original download preserved to assist in future reinstallations
>
> H: 500MB Disposable Temp Files
>
> I: 10 GB Downloads of various
> program CDs
>
> J: 40 GB Reserved for future
> expansion (Empty space)
>
> Drive 1 (80GB) D: 500MB Swap file / Pagefile (Primary
> partition)
>
> K: 18.5GB Multiple backups of
> partitions C:, E:, F: G: using MS Backup
>
> L: 61 GB Music files (WMA, WAV
> and .ra (Real Player format)
>
> Will be getting an External 160 GB that will hold the backups
> from K: on the Drive 1 and periodic backups of L:
>
> From the experience of folk that are "Power Users" as well as the
> casual guy, do you see any problems with this proposed schema.
> I'm not the type of person that believes that everything has to
> be 'born here'. I'm sure there are some partitions that might be
> a little too much as well as some that might not be large enough,
> but off the top of my head, this is what I came up with.
>
> Sorry for the post being soooo long, but wanted to try and
> present without ambiguity.
>
> Bonobo

I think it's way too complicated. You'll need a database
to keep track of what's where and when and where it
was backed up. Anything more than a system partition
and a data partition is overkill. Do you *like* to hear the
hard drive access arm clicking back and forth? And *why*
do you plan to put the programs (presumably installed
programs) on a partition separate from the OS? The
only thing that might make some sense (*might* make
some sense) is to put the swap file on the outside tracks
of the 2nd hard drive for speed. But if you have enough
DRAM, the swap file will hardly be used, anyway. Is life
too simple for you?

*TimDaniels*

#15 01-05-2006, 06:18 AM

"Timothy Daniels" <TDaniels@NoSpamDot.com> wrote in message
news:Fs2dnbCLeYzYhAjeRVn-gA@comcast.com...
> "Jim" wrote:
> > Hello all:
> > After a couple of days of reading, I think I'll just opt to make
> > a clean install of XP on the 160GB drive and re-install all of my
> > programs; since I've save the data that's most important to me
> > (yeah, real boring task).
> >
> > After reading various papers, I've come up with a schema I hope
> > will fulfill my needs, but I'd like to get some input relative to
> > any potential problems one might see based on experience.
> >
> > My final setup will consist of two drives: Disk0 = 160GB and
> > Disk1 = 80GB (C: and D; respective), and the partitioning will
> > look something like the following. This is what I'm asking
> > advise on:
> >
> > Drive 0 (160GB) C: 8.0 GB Primary Partition (Active): XP
> > and as little else as possible
> >
> > C: 10 GB Alternate primary
> > (Hidden) for future OS
> >
> > E: 60 GB Data: "My Documents",
> > IE Favorites folder & OE data store
> >
> > F: 30 GB Programs
> >
> > G: 1.5 GB Downloaded programs:
> > Original download preserved to assist in future reinstallations
> >
> > H: 500MB Disposable Temp Files
> >
> > I: 10 GB Downloads of various
> > program CDs
> >
> > J: 40 GB Reserved for future
> > expansion (Empty space)
> >
> > Drive 1 (80GB) D: 500MB Swap file / Pagefile (Primary
> > partition)
> >
> > K: 18.5GB Multiple backups of
> > partitions C:, E:, F: G: using MS Backup
> >
> > L: 61 GB Music files (WMA, WAV
> > and .ra (Real Player format)
> >
> > Will be getting an External 160 GB that will hold the backups
> > from K: on the Drive 1 and periodic backups of L:
> >
> > From the experience of folk that are "Power Users" as well as the
> > casual guy, do you see any problems with this proposed schema.
> > I'm not the type of person that believes that everything has to
> > be 'born here'. I'm sure there are some partitions that might be
> > a little too much as well as some that might not be large enough,
> > but off the top of my head, this is what I came up with.
> >
> > Sorry for the post being soooo long, but wanted to try and
> > present without ambiguity.
> >
> > Bonobo
>
>
> I think it's way too complicated. You'll need a database
> to keep track of what's where and when and where it
> was backed up. Anything more than a system partition
> and a data partition is overkill. Do you *like* to hear the
> hard drive access arm clicking back and forth? And *why*
> do you plan to put the programs (presumably installed
> programs) on a partition separate from the OS? The
> only thing that might make some sense (*might* make
> some sense) is to put the swap file on the outside tracks
> of the 2nd hard drive for speed. But if you have enough
> DRAM, the swap file will hardly be used, anyway. Is life
> too simple for you?
>
> *TimDaniels*

Well said. Two partitions is ideal, more is painful.

#16 01-05-2006, 06:18 AM

Bonobo

I agree with other who say your proposed new set up is too complicated.
There is much to be said for having a separate partition for data and
another for pictures to simplify backup and restore but keep the OS and
Applications together. Use folders, not drives, to separate your stuff as
eye candy.

BTW though I agree a clean install of Windows XP would be good, if you have
not already gone out and bought the new disk, and with Vista round the
corner, there is a nice work around that you could use to save your existing
Windows installation.
Buy a copy of Acronis Disk Director version 10. Custom install the OS
selector, [which I do not think you can buy on its own], and place it on
your Windows Disk 0 assuming Dos is on Disk 1. Remove the Dos disk and put
the new disk in as Disk 1, the old Windows OS should now be disk 0.

When you boot Acronis will select the old OS and you can check it out. If
all is well then you can format the new disk and do what you want with it.
When you install and OS into it the Acronis OS Selector will find it and you
will have your dual boot again.
Reboot and OS Selector will allow you to boot the old windows. From there
you can tailor OS selector to find the

I hope you have fun!
--
Uncle John
"Pegasus" <I.can@fly.com> wrote in message
news:u2Hiwni%23FHA.3708@TK2MSFTNGP10.phx.gbl...
>
> "Timothy Daniels" <TDaniels@NoSpamDot.com> wrote in message
> news:Fs2dnbCLeYzYhAjeRVn-gA@comcast.com...
>> "Jim" wrote:
>> > Hello all:
>> > After a couple of days of reading, I think I'll just opt to make
>> > a clean install of XP on the 160GB drive and re-install all of my
>> > programs; since I've save the data that's most important to me
>> > (yeah, real boring task).
>> >
>> > After reading various papers, I've come up with a schema I hope
>> > will fulfill my needs, but I'd like to get some input relative to
>> > any potential problems one might see based on experience.
>> >
>> > My final setup will consist of two drives: Disk0 = 160GB and
>> > Disk1 = 80GB (C: and D; respective), and the partitioning will
>> > look something like the following. This is what I'm asking
>> > advise on:
>> >
>> > Drive 0 (160GB) C: 8.0 GB Primary Partition (Active): XP
>> > and as little else as possible
>> >
>> > C: 10 GB Alternate primary
>> > (Hidden) for future OS
>> >
>> > E: 60 GB Data: "My Documents",
>> > IE Favorites folder & OE data store
>> >
>> > F: 30 GB Programs
>> >
>> > G: 1.5 GB Downloaded programs:
>> > Original download preserved to assist in future reinstallations
>> >
>> > H: 500MB Disposable Temp Files
>> >
>> > I: 10 GB Downloads of various
>> > program CDs
>> >
>> > J: 40 GB Reserved for future
>> > expansion (Empty space)
>> >
>> > Drive 1 (80GB) D: 500MB Swap file / Pagefile (Primary
>> > partition)
>> >
>> > K: 18.5GB Multiple backups of
>> > partitions C:, E:, F: G: using MS Backup
>> >
>> > L: 61 GB Music files (WMA, WAV
>> > and .ra (Real Player format)
>> >
>> > Will be getting an External 160 GB that will hold the backups
>> > from K: on the Drive 1 and periodic backups of L:
>> >
>> > From the experience of folk that are "Power Users" as well as the
>> > casual guy, do you see any problems with this proposed schema.
>> > I'm not the type of person that believes that everything has to
>> > be 'born here'. I'm sure there are some partitions that might be
>> > a little too much as well as some that might not be large enough,
>> > but off the top of my head, this is what I came up with.
>> >
>> > Sorry for the post being soooo long, but wanted to try and
>> > present without ambiguity.
>> >
>> > Bonobo
>>
>>
>> I think it's way too complicated. You'll need a database
>> to keep track of what's where and when and where it
>> was backed up. Anything more than a system partition
>> and a data partition is overkill. Do you *like* to hear the
>> hard drive access arm clicking back and forth? And *why*
>> do you plan to put the programs (presumably installed
>> programs) on a partition separate from the OS? The
>> only thing that might make some sense (*might* make
>> some sense) is to put the swap file on the outside tracks
>> of the 2nd hard drive for speed. But if you have enough
>> DRAM, the swap file will hardly be used, anyway. Is life
>> too simple for you?
>>
>> *TimDaniels*
>
> Well said. Two partitions is ideal, more is painful.
>
>

#17 01-05-2006, 06:18 AM

"Uncle John" wrote:
> Buy a copy of Acronis Disk Director version 10.
> Custom install the OS selector, [which I do not think
> you can buy on its own]...

Unca John - have you ever made a comparison of
Disk Director and Bootit NG as multi-boot managers?
If so, how do they compare?

*TimDaniels*

#18 01-05-2006, 06:18 AM

Fellows:
After really thinking about my own schema, I've come to agree
with what has been suggested; it really is a little much!! I
think smaller is better.

I do appreciate the feedback from all of you. This exercise has
given me back the faith in mankind that was waning; there are
those that care about their fellow man. I do appreciate all of
the suggestions and maybe one day I'll be in a position to
provide help to someone that is having a problem.

I've pretty much gathered all of the drivers and information
needed to re-install XP from scratch and tomorrow will probably
be the BIG day. I must say, Belarc (sp) is an excellent utility.
I was able to get the keys for all of my Microsoft and certain
other vendor's software; which some of the cases have been long
gone and documents that I had recorded keys in destroyed or
deleted by mistake. It's not very big, but gives valuable info
relative to your system. Just a couple more hours of clean up
and all will be ready.

Again, thanks for all of the kind words and suggestions. Will
post back the out-come.

Geeeeeeeeeeze, I LOVE this place!!!

Bonobo!!

"Timothy Daniels" <TDaniels@NoSpamDot.com> wrote in message
news:b7SdnViC_IpOTAjeRVn-rg@comcast.com...
|
| "Uncle John" wrote:
| > Buy a copy of Acronis Disk Director version 10.
| > Custom install the OS selector, [which I do not think
| > you can buy on its own]...
|
| Unca John - have you ever made a comparison of
| Disk Director and Bootit NG as multi-boot managers?
| If so, how do they compare?
|
| *TimDaniels*

#19 01-05-2006, 06:19 AM

Timothy

Yes I have both but now only use BootitNG if I have an MBR problem and then
the maintenance mode is useful. Otherwise Acronis Disk Director with the new
version 10 has many good features in a clear Graphical Interface and
integrated nicely with True image version 9 for image restore. In Disk
Director the OS Selector does the job of BootitNG and the rest of the suite
is like an upgraded Partition Magic which used to the best package when
Powerquest ran it but now is neglected by its present owner Symantec.
--
Uncle John
"Timothy Daniels" <TDaniels@NoSpamDot.com> wrote in message
news:b7SdnViC_IpOTAjeRVn-rg@comcast.com...
>
> "Uncle John" wrote:
>> Buy a copy of Acronis Disk Director version 10.
>> Custom install the OS selector, [which I do not think
>> you can buy on its own]...
>
> Unca John - have you ever made a comparison of
> Disk Director and Bootit NG as multi-boot managers?
> If so, how do they compare?
>
> *TimDaniels*

#20 01-05-2006, 06:19 AM

From what I continue to read, Acronis outdoes
Symantec - at least in its little niche. If Acronis
would just put the single partition cloning capability
into True Image that Casper XP and Ghost have,
then I would be a convert.

*TimDaniels*

"Uncle John" wrote:
> Yes I have both but now only use BootitNG if I have
> an MBR problem and then the maintenance mode
> is useful. Otherwise Acronis Disk Director with the
> new version 10 has many good features in a clear
> Graphical Interface and integrated nicely with True
> Image version 9 for image restore. In Disk Director
> the OS Selector does the job of BootitNG and the
> rest of the suite is like an upgraded Partition Magic
> which used to the best package when Powerquest
> ran it but now is neglected by its present owner
> Symantec.
>
> "Timothy Daniels" wrote:
>> Unca John - have you ever made a comparison of
>> Disk Director and Bootit NG as multi-boot managers?
>> If so, how do they compare?
>>
>> "Uncle John" wrote:
>>> Buy a copy of Acronis Disk Director version 10.
>>> Custom install the OS selector, [which I do not think
>>> you can buy on its own]...

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode