HELP PLS! Using Partition Magic 2 Try 2 Install WinXP x64 on Top of XP 32

Discussion in 'Windows 64bit' started by MadMax75th, Mar 23, 2007.

  1. MadMax75th

    MadMax75th Guest

    PLEASE HELP!! Trying for months & give up, retry again etc. OK, I have
    XP Home 32 originally installed on puter. I Used Partition Magic 8.0
    to try installing a 2nd OS (XPx64) on a newly created partition. First
    partition is 110 GBs my new partition is 30 GBs. Hard-drive 160 GBs. I
    follow the printed directions & I boot to new partition, it tells me its
    the wrong disk but when I press any key to boot from CD, all starts
    well. I get the blue setup screen & it starts installing the various
    drivers etc & finally gets to a place that informs me that "Windows
    will now restart" but it never does. It just sits there waiting to
    reboot or restart. I try restarting manually but it just re-installs
    drivers until it gets to "Windows will restart" again!! I am going
    nuts! I contacted Symantic Support but they said I have to have x64
    installed first to add XP32 but I have read here & been told that "NO,
    it's XP 32 first & then u can load a partition with XP 64." So Symantic
    is misinformed!
    My specs if it helps are:

    AMD 4800+ Dual Core Processor
    c: (NTFS on drive 0) 160.03 GB 89.88 GB free
    SONY DVD RW DW-D26A [CD-ROM drive]
    SONY DVD RW DW-D26A [CD-ROM drive]
    3.5" format removable media [Floppy drive]
    Windows XP Home Edition Service Pack 2 (build 2600)
    2816 Megabytes Installed Memory
    Slot 'A0' has 1024 MB
    Slot 'A1' has 1024 MB
    Slot 'A2' has 1024 MB
    Slot 'A3' has 1024 MB

    If you need any more info about anything, I will gladly comply. I am
    NOT very knowledgeable about computers so please be specific & basic
    about what I need to do to install this correctly.

    Thank you very much for your assistance!
    MadMax75th, Mar 23, 2007
    1. Advertisements

  2. MadMax75th

    Theo Guest

    Try just resizing your 32-bit partition down to the size you
    want, make sure that OS boots up and functions properly.
    Then boot from the Win x64 CD and create the partition from
    there. You will get a logical drive in an extended
    partition, but x64 works fine in that situation. Although I
    did everything from a clean start, I have XP 32-bit on the
    1st 1/2 half as C: on my primary drive and Win x64 ended up
    as E: on the 2nd 1/2 half. I have no problems with either
    Theo, Mar 23, 2007
    1. Advertisements

  3. MadMax75th

    miso Guest

    I prefer "partition commander". Just boot from the partition commander
    CDROM. It has the features similar to Partition Magic, i.e. you set it
    up in windows then it boots your PC, but I find it simpler just to
    load the CDROM and start from there.

    I had Partition Magic crash under X64.
    miso, Mar 23, 2007
  4. MadMax75th

    Tom Ferguson Guest

    I think Theo's suggestions are sound; however, I would add a couple of

    1. If you boot to your 32 bit system that now runs on the box, go to
    Disk Management and reassign the CD or DVD device lower in the alphabet
    (I use U and V), the new drive letter will be D when you have finished
    creating it and installing XP 64.

    2. You can create the partition for the 64 bit system from PM. I would
    boot from the floppies, shrink the present partition as needed or
    desired and then reboot to assure everything is working. Then I would
    create an extended partition with an NTFS-formatted logical drive.

    Now you can install the XP 64 system.

    You might prefer Theo's plan as being simpler.

    Windows Shell/User
    Tom Ferguson, Mar 23, 2007
  5. MadMax75th

    MadMax75th Guest

    Thank you very much for the advice. If I understand it, you are
    suggesting I reduce the size of the frst partition in oreder to enlarge
    the second. Unfortunately, my first partition is getting pretty full,
    only about 30 GBs unused & I am nervous about having a semi full
    partition. However, I will try what y'all suggest, lord knows my way
    has not worked. I believe partition magic has the ability to reasign
    drive letters but I have never used it b4.

    Does anyone have any idea why my x64 is not restarting itself?
    Thank you so very much for the replies.
    PS- somehow, this got sent to a string I had made a comment on. I wil
    copy this to the original string or request I made & hopefully that
    will make replies less confusing.
    MadMax75th, Mar 24, 2007
  6. MadMax75th

    Bill Guest

    Are you also using BootMagic to manage your boots. The following may help
    if you are. It was posted during the build 5270 timeframe on Vista. I'm
    still using this method but you must have a floppy drive that you can boot
    from. My versions of PM/BM are the PowerQuest versions, I beta tested for
    them for a number of years, but the Symantec versions are identical except
    for the branding. Also, make sure you have either the ver 8.01/8.02 patch
    installed and have created the boot floppies from both BM/PM AFTER the patch
    is installed. The patch you need depends on the ver you have installed.
    The 8.01/2 patches are available at


    On this page you will see two folders. The next step will depend on the
    version of PartitionMagic you have installed.

    --If you have PartitionMagic 8.01, double-click on the folder labeled PM801,
    then download the file ENPM801_H1.ZIP to your desktop.
    --If you have PartitionMagic 8.02, double-click on the folder labeled PM802,
    then download the file ENPM802_H1.ZIP to your desktop.

    The downloaded file is password protected. To extract its contents, use the
    password "pm1513" (without the quotation marks.)

    To install the patch, follow the instructions in the text file "PM 1513 -
    Readme file.txt," which is included in download file.


    From: "Bill Sharpe, BullDawg" <[email protected]>
    Newsgroups: microsoft.beta.longhorn.setup_and_migration
    Sent: Saturday, December 31, 2005 9:13 PM
    Subject: Setup using PowerQuest's BootMagic

    Long read, but worth it to any using PowerQuest's BootMagic 8.01.

    Earlier builds posed no problems, just used the same techniques I had been
    using with XP, but 5270 presented new challenges, finally got them licked.

    My setup includes two hard drives, the first partitioned into four primary
    partitions, no logical or extended partitions and the second drive, one
    primary as FAT32. Was using BootMagic's default partition hiding which hid
    all partitions except the install partition on the boot drive and unhid the
    partition on the non-boot drive. This always kept my OS's on a "C"
    partition and kept the other three OS partitions hid but allowed the second
    drives primary partition to be enumerated as "D" by default. The first
    drives primary partition is a small 24 meg FAT(12) partition with MS DOS 6.2
    as the OS. I copied the 16 bit BM dosrescue disk to this partition and
    edited the autoexec. bat, autexec2.bat and config.sys files accordingly to
    allow it to boot into BootMagic 16 bit. Then I used BootMagic to set
    Primary 2, NTFS, as the default boot which contains Win XP Pro SP2 fully
    patched and up to date as the production OS. Primary 3 and 4 are used to
    test other OS's. Whenever I wanted to install a test OS, I just used
    BootMagic to boot into primary one and configured BootMagic to set one of
    the other (3 or 4) primaries as the default boot. Then would reboot and
    install the test OS to the partition selected. As I said, this all worked
    great prior to 5270.

    5270 wanted to have its own way and install the boot files to primary 2
    which contained Win XP Pro. On the first reboot of setup, I would get an
    error that Bootmgr was missing. That's because it was on primary 2 and not
    4 and with primary 4 set as the boot partition by BootMagic, primary 2 was
    hidden from 4, catch 22. Setup could not continue no matter what I tried.

    I had to enable BootMagic's advanced hiding to finally get the boot files on
    primary 4 where they belonged. I had to configure BootMagic to hide all
    other partitions and drives, set the default boot partition to primary 4 and
    then disable BootMagic. This finally allowed setup to place everything on
    primary 4. After successfully getting 5270 installed, I then used
    BootMagic's rescue floppy to re-enable BootMagic. Booted into BootMagic on
    primary 1, reset the default boot back to primary 2 and set the time on the
    BootMagic boot menu to 10 seconds. I now can boot into the OS's on primary
    2, WinXP Pro; primary 3, other NDA OS; and primary 4, Vista 5270; without
    any interaction between the three and the MS DOS on primary 1. Each OS uses
    it's own boot files without any dependency on the other OS's. And that's
    why I don't want to use Windows XP or Vista's boot manager, my OS's are
    totally independent of each other and don't rely on another to boot. I can
    reformat and install to each primary without fear of affecting another OS

    And the $64k question, why was the way 5270 setup enumerates and unhides
    hidden partitions changed from previous builds? Took me over a week to come
    up with my work around.

    Bill Sharpe

    Bill, Mar 24, 2007
  7. MadMax75th

    Tom Ferguson Guest

    If your drive is getting that full, it is probably a good idea to add a
    second hard drive and install XP 64 to that.

    Which boot manager are you using?

    Windows Shell/User

    Tom Ferguson, Mar 24, 2007
  8. MadMax75th


    Sep 2, 2008
    Likes Received:
    i like EASEUS Partition Manager better. It has the similar functions with Partition Magic, and it works well on my computer.:driver:
    bean123, Sep 2, 2008
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.