partition after clone to HDD

Hank, thank you for the detailed information provided for your question above.

I would not recommend using cloning in this scenario.

Create a full disk / partitions backup of your Windows XP hard drive to another drive, then simply restore this backup to your new WD 1TB drive without allowing Acronis to automatically resize the partition(s) size - this will leave the remaining space on the drive as unallocated so that you can create any further partitions later.

The complicated part of what you want to do here is moving that XP drive to your new computer hardware as this will require the use of the Acronis Universal Restore utility which you will need to create on bootable media (CD or USB stick) and run against the XP drive to prepare it to run on the new / different hardware.  If you are still unable to boot the system into Windows XP then you may need to provide any additional device drivers on the AUR media for new hardware present in that system that XP probably knows nothing about.

You will also probably have Windows activation / licensing issues to resolve in moving XP to new hardware unless you have a full Microsoft Retail version of XP or similar license.

Steve - Thanks for response . .

This brings up a couple things - which come to mind - I had forgotten about the licensing issues. I do have WXP SP2  CDs  from Micorosft with the serial numbers .which I am pretty sure do not have any Dell OEM hooks  .There is no "OEM" in the serial Id - I dont remember anymore if SP2 was the last service  pack

I could  just try installing that on the second drive in the new computer and go thru the potential hassle of getting the HASP drivers to work . (This program / drive is NEVER connected to internet - when using it I either turn off the modem / router or simply pull the incoming data line from the wall.

Which leads  me to the  question. - if I put my working XP drive in the new computer and  see if it will be recognized , then select in BIOS sequence  and see if it boots . IS there any chance to hose it just doing that ? I guess for belt and suspenders I should do a full backup to external USB drive before anything .

That would tell if there are any issues right off I would think ????

(I also have the circuit analysis program CD and  license info inputs  - so re installing it in tenew computer/ drive is no problem. )

Thinking out  loud now , Maybe safest thing is to simply try the install of the WXP OS and the HASP for the USB hardware key -  in either case I will have to install drivers for printer , not sure about video since its an Intel XEON with integrated video.  I would have to do all that anyhow even with the old WXP . drive . Now that I think about it - I have not printed any outputs  recently just ran the data . I may not  have a printer driver  for my present laser .I will check that before I do anything .Probablystill have theold inkjet printer driver and its on line too.

Thanks

Hank

Hank, XP SP3 was the last service pack version issued, so you would need to either ignore that this isn't present or update via the internet assuming you can get your XP SP2 installed and working on your new hardware.  Check the requirements for your HASP software / hardware if that needs SP3 or not if the XP system will never be connected online.

I wouldn't recommend just installing your working XP drive in the new computer without having a full backup image - ideally I would suggest restoring the XP backup onto a second (spare) drive purely to do the testing and leaving the original alone.  That way you have no recovery to do if it all goes haywire and the spare drive can just be wiped and used for something else.

Trying a fresh install of XP on a spare drive in the new computer would give you the best indication of whether this is going to get off the ground with the changed hardware, plus if you will hit Windows activation issues, plus you can check whether your printer, video etc will be OK.

HI Steve -

Thanks for help and suggestions - Think I have enough to occupy me this weekend

Regards -- Hank

HI Steve - I made a full disk backup of the WXP drive to my external USB harddrive  .(Based on a ACRONIS note that said that backup and recovery was as good as a clone.)  I put a second hard drive in the new computer , formatted it to get rid of everything on it  - the system recognizes that drive.   Then I thought I would simply move the USB hard drive with the WXP .tib full backup to the new computer and install from there.

I booted with the ACRONIS Bootable Media  dvd I made and  tried to follow instructions - "click RECOVERY" on left pane and select the backup. I did that - then it says right click to select VALIDATE - but nothing happens . So I decided well if it wont validate - Ok I will try to put it on the drive anyhow -- Went to " re cover whole disks and partitions" - selected the WXP two partitions - but see no way to select the new drive to put it on.

At that point I got afraid of what was going on and tried to close the ACRONIS and it started a black screen and started a bunch of gibberish so I forced a power off - removed the external USB drive , started up again , removed the ACRONIS Recovery DVD , and did a F12 until the boot menu came up , it showed the W7 SSD boot drive was selected and I let it go and all is still well but I am at a loss.

I guess next step is to remove the WXP drive from the old computer , put the new drive in and try to restore to it ??? I will ALSO unplug the W7 drive before I try this. 

BTW I DO have  two  WXP  pro SP3 "re-installation" CD 's  that came with  DELL  computers  .- but I do not remember how those re install disks work in terms of selecting  a drive to put the system on. The only re -install I ever did was on a laptop with only one drive.  I do NOT want to remove the SSD  its mounted direct on the MB .As far as I can see there are no  "plugs" to disconnect it - and I am afraid to try to start the reinstallation dsik who knows where it will try to put the system if no choices come up.

Hank

Hank, I would install the new blank drive where the original is/was, leaving the original unplugged and safe and sound. Plug the drive with the backup .tib files in via external USB if you can. Then boot your Acronis media and go to restore... Should not need to validate at all. Pick the source as the .tib from your external and the destination as the new drive. Restore the entire disk/all partitions from the original backup image. When it's done, physically power off the machine, disconnect the USB drive, power up and see if the restored image boots.

Also, make sure you boot your recovery media to match the OS. As this is XP, that should be legacy mode and not UEFI. You may need to make sure your new disk is MBR and not GPT as well. If you're not sure you can use the add new drive option in Acronis to format the new drive and it will be raw. The restore will partition it depending on how the recovery media was booted.

Hi Bobbo -I did virtually exactly as you suggested - made the .tib on the external USB . At least the validate shows up as you go thru the process -not where the tip said - but I did NOT validate . It was a little confusing (for an amateur) to select the partitions  but I selected all three  (one is apparentl;y the Dell stuff) did MBR and legacy.

BTW I had my 1TB W7 drive disconnected thru all this process except when making the  backup  ,tib - soon as that was done I pulled the data line to it - replaced the "good" WXP drive with the blank drive and restored -(it did make new partitions to suit itself)

Soooo - after all this - I tried to boot from the "new" drive -  no  soap - could not get the system to say there was a bootable drive. The drive DID show up in the list of drives , I selected it as boot - but nope . played with various SATA setups - nope.   It WOULD boot if I used F1 in the setup options (F1 F2 F5 ) options - After I did that a couple times all of a sudden a screen popped up saying it was  doing something as IDE drives too fast to read it all before it disappeared. After  that  it would boot up normally . And the program runs , recognizes the HASP drivers and the USB hardware key . I have a feeling some of this blasted funny business is the ##$$%@@&& Intel RAID controller which I have to leave selected as RAID even though the INTEL manager says neither drive is a RAID drive. (This computer was a RAID 1 machine when new and I have been plagued with that ever since- never again)

I did try to install  the Brother 8710DW  printer drivers on the "new" WXP drive but I get an error message which I will pursue with Brother

So next step will be to  put the "new" WXP drive inte new computer . and see if it will boot when I select it from boot menu, (I do not use the WXP program daily so its no big deal to F12 and change boot sequence . )

Nope will not boot - get error message saying "the BIOS in the system is not fully ACPI compliant. Contact system vendor for an updated BIOS."  So will contract Dell.  (I have a suspicion it may also be tied up in a screen that talks about two options - one EUFI with legacy boot and one without legacy boot but did not mess with that as wanted to be SURE I had not somehow hosed the W7on the SSD  )

Thanks for help

Hank

Hank, are you using an IDE drive originally and moving to SATA or are all drives IDE?  If you are swithcing the drive type, you have to also change the SATA mode in the mode (RAID, AHCI, SATA, IDE).  HOWEVER, this also requires a driver change in the OS as well.  Windows XP and even Windows 7 do not play nice when you have to change the controller mode in the bios, even when the physical drives remain SATA, but switching from AHCI to RAID or vice-versa.

If you were going from IDE to IDE or SATA to SATA, this should work fine.  But if switching disk types on Win XP and you've got the bios SATA mode/controller mode set correctly, your best shot is running universal restore to generalize the drivers on the restored disk and see if that allows it to boot with Generic Windows XP drivers, but if you are running in RAID, then you'll also need to add the controller driver with universtal restore too.

If it still doesnt' work, you could then try a startup repair using your Windows installer disc and if that doesnt' help then you can try to run the installer advanced menu command prompt and try a BCD repair, but only after you've used universal restore if switchign from IDE to SATA and setting the SATA mode in the bios to SATA as well.  

Also, that error code could mean a couple of other things:

Do you have hibernation enabled on the original system?  https://support.microsoft.com/en-us/kb/831691

Or if your system is getting long in the tooth, the bios may just not support be up to par:  http://answers.microsoft.com/en-us/windows/forum/windows_7-hardware/stop-bios-not-fully-acpi-compliant/25210db0-5491-4fc8-99c2-ec0361dd8388?auth=1

Hi Bobbo

I have no idea where the IDE came from or why it popped up - both the "source drive" and the" target drive" came out of my T3500 and have been SATA since day 1.. The T3500  came with WXP  and  the cd to upgrade to W7 - that was one reason I bought it , I could still get factory WXP. And yes -- I have had to leave the thing as RAID  even though the Intel Raid  says neither are part of a RAID . 

ANYHOW -- I got tied up with some things today and did not call Dell - but i DID get the Brother printer drivers working on the original WXP drive inthis T3500 - that was an issue with a Norton residual that I have never updated since I don't  ever connect to internet when running the WXP. installation. So I know I canmake tat work whne I get the target drive to boot .

No I have never used any hibernate  on either compouter.

I read all the stuff in the link you gave on bad BIOS .

I think next step is to contact Dell - - (There is a option to select "UPDATS BIOS"  but I will wait to talk to Dell.)

The error message about BIOS also referred to www.hardware-update.com- it also says If f you cannot get an upgraded BIOS you can turn off ACPI mode during text mode setup. (not sure what they mean by that ) but they go on to say ....Simply press F7 key when prompted to install storage drivers . The system will not notify you that the F7 key was pressed  - it will silently disable ACPI and allow you to continue your installation.

So thats  where I am now.

Hank

Bobbo - Whne I looked at that link  www.hardware-update.com-

it was blocked by Norton as being extremely unsafe - strange since it was from a Microsoft blue screen

Hank

Ok, i re-read to get back on track as I was apparently missing some details - completely missed that this was coming from an older T3500 to a new system.

"I have a new computer with working W7 and apps and data - but I want to clone the WXP drive  and install it in the newcomputer so I can use  the same method in the new computer."

You're bascially in the hardest scenario, because you're completely changing hardware, using XP (the least forgiving of OS's when moving to different hardware) and have at least one system that has a RAID controller (the original T3500).  Plus the T3500 uses a Xeon CPU and not sure what your new CPU is, but XP does not like CPU changes because of drivers.  And, e SATA mode in the bios may be different in the old system than the new one and must be the same.

For the purpose of booting and trouble shooting, pull the Win 7 drive on the new system so you're only dealing with XP during testing/repairing to try and get XP to boot on the new system.

1) You will need to run Universal Restore to generalize the drivers in your restored image to make it bootable on the new hardware - XP is horrible at moving systems and this is absoltelynecessary.  I didn't catch if you had done this already or not?

After running UR, just reboot and see if Windows can boot after that or not (assuming things like the bios sata mode were already set).  We're also assuming that your new system supports legacy boot and that the bios is configured for legacy/CSM boot.

2) If it doesn't boot (BSOD) and your new system is using RAID, you will need to add the RAID controller drivers with uinversal restore as well - the IRST drivers may be sufficient, but not sure what your new system is, so you may need to grab specific controller drivers if your system has a dedicated RAID controller as well.

If you need to inject RAID controller drivers, do so and reboot and see if Windows boots, BSOD's or something else. 

3) the SATA mode in the bios on the new system must be set to RAID if it was set to RAID on the original as well.

If all that has been done and it still doesn't boot, then you may have to repair the bootloader to try and force the new bios to detect a bootable OS on the drive.  You'll need your original Windows XP installation disc or recovery disc and will need to boot directly into it.

A) Try running a startup repair and rebooting.

B) If that doesn't work, boot the XP installation/recovery media again and go to the recovery console (command prompt) Then run these commands and reboot and see how it goes. 

fixmbr

fixboot

C) If that doesn't work, then you get into the weeds with this one a bit, but it's step by step.  If you get to this point and complete and it still doesn't boot, I'm out of ideas.   

http://icrontic.com/article/repair_windows_xp

Both computers are XEON --  4 core - the new one inthe T3620 does have integrated graphics - the old one did not .

The T3500 had the RAID which has been killed  it was  RAID 1 mirror . But the INtel RAID controller now agrees neither drive is a RAID drive - BUT I haveto leave BIOS set to RAID . THe T3620 does NOT have RAID - never did  - never will.

The W7 drive  in the T3620 is  a Toshiba SSD - it is screwed to the motherboard and runs from PCIE buss - its not on a seperate board plugged into a PCIE slot .  So I giess I could go into dosk management and disable it  but removing it is not something I want to do.

Do you see any problem with just disableing it (the SSD )  in disk management . ?

I assume your point 3 does not apply as the T3620 does NOT have RAID , was ordered with NO RAID -- (but yes buried in its bowels is the Intel RAID  controller . its just not activated nor has it been )

I dont know if it means anything but the WXP window comes up for a couplke seconmds before the BSOD comes on with the erro message about the non ACPI  BIOS compliance.

I will talk to Dell tomorrow before I start anything else - I have their Pro Support - came with the system - has been pretty good ifyopu get the right guy/gal.

nuff for tonite

Hank

Even though you don't have an actual RAID in use, because the SATA mode is set to RAID in the old system, those are the drivers installed in the OS for bootability so the SATA mode must match on the new PC as well.  If you have AHCI enabled on the new one, this will be a problem and it would need to be set to RAID - no way around this with Windows XP.

Also, even though you don't have an actual RAID in use, because the SATA mode should be set to RAID in the new system, it will require drivers for that SATA controller, which may not be the same on the new system as the old one - this could be where the BSOD is coming from if the RAID controller is different on the new system than the old one.

Regardless, unless the hardware is EXACTLY the same, you will need to run universal restore on the hard drive to give it the chance of being bootable on the new system.  Assuming you get it to boot, you will then need to go back into Windows (once it boots) and manually install other drivers  from computer management >>> device manager.  You can add drivers during the UR process, but should only include the RAID drivers for the new system if it doesn't boot after running UR without adding these drivers.  

LAST - what is the PCIE hard drive in the new system?  Is it a SATA PCIE hard drive or a NVME PCIE hard drive?  The Samsung 951 OEM / 950Pro and Toshiba OCZ R400 (not sure what the OEM version is), are NVME PCIE hard drives.  This technology is not supported in Windows XP and there are no drivers avaialble for XP so could be the true cause for the system not being able to boot since it is physically connected and the OS is trying to find drivers for it at bootup.  If it is an NVME version, for the purpose of testing and trying to get XP to boot, I would pull this drive out and leave it out of the mix until you get XP to boot.  Assuming you get XP to boot OK without it and can successfully boot XP over and over, then put the other PCIE drive back in and see if it causes XP to choke or not.  If it does cause a problem, this may be a physical limitation of XP not having the necessary drivers for the PCIE hard drive - especially if it is the NVME type. If it is a SATA PCIE hard drive, XP should at least be able to see it as a data drive, but most likely, would not be able to use it as boot drive.  

Ok on all the RAID stuff - makes sense - and that is EXACTLY why I will NEVER NEVER have a RAID by INTEL on any system. This damn thing has  gotten to me  for 6 years in every possible way . Intel appears to have made it virtually impossible to complely divorce a system from its RAID  hooks. 

I wonder if I did a fresh install of WXP  on the present T3500  and  de selected RAID and made it AHCI  then installed WXP from scratch if that would get rid of the RAID hooks ? Since I am only using one APP that is not a big problem to start from scratch. Obviously I would disconnect the other  W7 drive while doing this .

To answer your LAST question- the SSD is a Toshiba OEM 256GB  described as M.2 256GB  PCie  NVMe Class 40  SSD .

Pulling the drive is not really an option - I just am very reluctant  unscrew it from the motherboard - it is not on a card plugged into the PCie slots.This is my first experience  with a SSD -and  I thought it would just be on a card plugged into a PCie slot  - but nope.

I am obviously very limited in my understanding and I appreciate your having busted your hump to try to get me going -

I guess I simply do not understand  what the SSD drive has to do with  booting from another drive . In my limited understanding  it seems to me  once I select the WXP drive in the boot sequence   and the SSD is NOT selected why would the system go looking at the SSD ?

I thought I could go into Device manager and disable it but the disable is greyed out- probably because its active and I cant boot to another drive so it is not active.

Hank

I wonder if I did a fresh install of WXP  on the present T3500  and  de selected RAID and made it AHCI  then installed WXP from scratch if that would get rid of the RAID hooks 

Yup - it would.  If you're in AHCI mode already, then yeah, go ahead and install XP "fresh".  You'd be building a fresh install, but you'd be running in AHCI mode with no more RAID hooks.  Windows XP just isn't really driver savvy when it comes to changes.  In Windows 7, Microsoft has a fixit tool that allows you to prepare the OS for a change from RAID to AHCI, but I don't think it would work for XP as I have not seen one.  Windows 8.1 handles this better natively, and Windows 10 does this on the fly now (at least going RAID to AHCI... when going AHCI to RAID, you still need to ensure the IRST drivers are loaded, which may not be there if you installed in AHCI mode to begin with). 

I guess I simply do not understand  what the SSD drive has to do with  booting from another drive . In my limited understanding  it seems to me  once I select the WXP drive in the boot sequence   and the SSD is NOT selected why would the system go looking at the SSD ?

Even though you're booting into a different OS, if the drive is attached, that instance of the OS will still try to connect to that other hard drive.  If you end up buiding a fresh WXP under AHCI mode instead, leave the PCIE NVME drive plugged in - should be OK.  However, there are no XP drives for NVME PCIE hard drives so it will probably just show up as an unknown device, or not at all (hopefully).  I just wanted to rule it out as a culprit in your attempt to import the OS from the old system, but when starting fresh with XP, I think you'll be OK. 

I thought I could go into Device manager and disable it but the disable is greyed out- probably because its active and I cant boot to another drive so it is not active.

You sure this isn't the boot drive of your Win 7 install?  If so, you can't disable it while it has the OS running, if that is where the OS is currently being run from.  In XP, I'd be suprised if this drive even shows up since there are no XP drivers for NVME PCIE hard drives (SATA PCIE hard drives, would not be an issue).  I'm really not sure though, as I don't have an XP system, but my guess is that XP will just disregard it. 

Hi Bobbo --

OK on all down to the last paragraph -- yes  it IS the W7 boot drive and yes it will not let me disable it -- I suspect I COULD disable it if I could boot off the WXP drive !!!

I talked to Dell Pro Support  -  useless --  they refuse to even talk about WXP -- so I said how about putting W7 on the hard drive -- answer blew me awqy - "guess you could try it" . I admit to some avarice beecause if they said ok or  went to how to W7 on hard drive - etc etc . Then they tried to transfer me to Microsoft and after a few of the usual robots they said they would talk to me for $425 .

I  decided to go back for a bot and fight why W7 will not recognize my HASP key when I install the program in W7 . I sent a plea to Keysight again who now have the EESOF/ HP Eagleware software . I alos found a much newer version of the HSASP driver and installed them onthe T3500 W7 disk but still will not recognize the key.

I have some medical isues to attend to for a few  days (I hope just a few days !!!) so hope to work ony our last WXP suggestions over weekend

Thanks again for your patience and efforts onmy behalf -  (ther is lost of interestung stuff inte Micrisft links you sent me and I dug down trough a couplke deeper - may still be a way to do XP but if I can pull something on W7 - that would probably bebetter long term .   There were some hints in some of the W7 registery links.

Hank

I have