Thanks for that Greg - you're probably right about the boot file - but as you can see ATM we are pushing to get a solution from Paragon - but a macrium or even EaseUS solution is not off the cards by any means.
Appreciate your interest - thanks.
I would not hold my breath waiting for Paragon to reply, but go ahead and try Macrium which has no downside anyway.
Then if ever they reply you can ask for your money back.
Wolfgang - the partition called Images is full of photographs only, and there are no other W7 system files other than on C:
The report from Paragon Migrate I think is quite clear - it announced an intention to copy 22.4GB from C: to an SSD it believes is 119.2GB - the ball is very much in their court ATM.
Greg - I hope you're wrong :) - but then Wolfgang has set the bar very high
I guess you are right. They better come up with a good answer. I am disappointed myself because I have migrated nearly 20 systems of my own and my friends and never had a problem - except once where the SSD was defunct.
Greg is right. Nothing should hold you back to make a clone with Macrium - you can always scrap it later. I just made one the other day (only for testing) and that worked fine. It booted flawlessly from my eSata attached SSD. Mine was from a 60GB SSD to a 60GB SSD. I always have a few of those older SSDs lying around for testing things. Another one I use to run my virtual Mint on my $99 laptop.
The good news - I am now running my Windows 7 off SSD
The not so good news - it was somewhat traumatic getting here
Paragon were very prompt and replied they needed 4 log files (from Migrate installation folder) which I was able to supply. They then promptly replied as per attachment 1 of which my understand is . . . .
Due to the existence of XP(H) and W7(C) MigrateOStoSSD (MIG) reasoned XP had the boot files that W7 needed and MIG in its wisdom thought - to get the boot files I need to copy the XP partition as well but not tell anybody about it - so that explains why it reported the SSD as not large enough!
The solution they suggested was along the lines previously discussed here - namely to ensure W7 partition had the necessary boot files etc. Faced with the choice of doing it our way - or do it the Paragon way I opted to follow Paragon instructions (latter part of image 1).
However it sort of didn't work quite as expected. When rebooting it always hung with
NTLDR is missing
Press Ctrl+Alt+Del to restart
(this was a never ending loop however)
Fortunately I had made a Windows Repair disc last week so I booted off this - it needed running twice but eventually repaired whatever was sick and I was then able to boot into W7(HDD) again.
Ran MIG and all worked as expected - tweaked BIOS boot things and now sys boots to W7(SSD) in around 15s as opposed to 45-60s previously. Impressions are good at this moment.
So did Paragon miss something important off their instructions that caused NTLDR missing problem?
This Bcdboot command is popular but never seems to work. There are another 3 commands that don't seem to work either.
But I am a bit confused. Did we not copy the bootmgr from the XP partition earlier - like this.
I gave you the automated method to move the Bootmgr - Move to C:\ with EasyBCD - Windows 7 Forums, same as Wolfgang had given you five days earlier.
The manual method is to mark the target partition Active then run Startup Repair - Run 3 Separate Times which is apparently what ended up working for you.
Once you have it cloned, let us know what you want to do with the old XP and Windows 7. At least the old Win7 should be bootable using the one-time BIOS Boot menu key at boot. You could add XP to a Dual Boot with it by installing EasyBCD to Win7, or we can help you make XP bootable again if you want to delete the old Win7.
whs: No we did not copy the boot mngr from the XP partition because at the time the Paragon solution was not on the horizon, and then when it was we agreed to try without doing so - what caught us out was that without that data on the C: Drive - Migrate was going to fail in the way that it did.
greg: yes you did - but see above - Migrate failed in a way that fooled us all
My lack of understand/familiarity on this subject probably did not help so apologies for that.
So were Paragon instructions correct? Or was the fact that I had to run the Repair disc 3 times to have been expected?
Thanks to you both for your support.
Again, had you moved the boot files as Wolfgang advised six days ago and I advised again yesterday, this could have been avoided because the Paragon error would not have arose.
I would not give BCD commands because we have more consumer-friendly automated methods that work better, and another manual method that always works - thousands of times here. Paragon is not the top tech forums on the web.
Have you cloned your drive successfully now? What do you wish to do with XP and old Win7?
Quote
