Migrate OS to SSD - Questions for Early Adopters

Discussion in 'Paragon Early Adopter Program' started by Paragon_JT, Oct 6, 2010.

Thread Status:
Not open for further replies.
  1. Paragon_JT

    Paragon_JT Paragon Moderator

    Joined:
    Aug 1, 2009
    Posts:
    28
    Location:
    Orange County, CA
    Early Adopter Program members evaluating Migrate OS to SSD, please review and answer the following questions, after you've had an opportunity to use the software.

    1. Was your OS migration successful?
    a. Yes
    b. No. (If No: please send us the following log files: cdb.log, stubact.log, biontlog.txt, fdisk.txt, pwlog.txt)

    2. Was the migration process intuitive?
    a. Yes
    b. No.( If No: please describe the stage that caused major problems for you and what improvements you suggest)

    3. Were all the pogram dialogs clear to you?
    a. Yes
    b. No. (If No: please describe the confusing dialogs, or send screenshot based examples)

    4. Do you think that Migrate OS to SSD needs additional features?
    a. Yes. If Yes: please describe features you want to have in the next version.
    b. No.

    5. Have you found some excess features?
    a. Yes. If Yes: please describe the features you will never need in Migrate OS to SSD
    b. No.

    6. Do you think that Migrate to SSD solution functionality needs to be extended?
    a. Yes. (If yes, what else would you like this solution to do, to extended tasks such as migration to bigger drive, support of complex configurations, etc?)
    b. No. It is good already and complete.

    Thank you for your participation - We'll look forward to your feedback!
     
  2. mickiem

    mickiem Registered Member

    Joined:
    Oct 6, 2010
    Posts:
    17
    1. Was your OS migration successful? -> Yes

    2. Was the migration process intuitive? -> No...
    May just be me, but when I saw the message that the boot track was going to be deleted next step, *before* I even selected a disk/partition, I was very unsure if the app was going to delete the existing track from drive C:, or if it was talking about a potential destination. After taking a lot of precautions I figured out it was the destination. I think it would be improved if the message came later (after target selected) &/or said the track's is going to be deleted on the target.

    3. Were all the pogram dialogs clear to you? -> Yes.

    4. Do you think that Migrate OS to SSD needs additional features? -> No.

    5. Have you found some excess features? -> No.

    6. Do you think that Migrate to SSD solution functionality needs to be extended? -> Yes...
    Personally I'd like to see added support for virtual drives beyond Microsoft's .vhd &/or integrate some of your virtualization tools, but that's me. :)
     
  3. ZamZam

    ZamZam Registered Member

    Joined:
    Oct 5, 2010
    Posts:
    3
    1. Was your OS migration successful?
    a. Yes
    2. Was the migration process intuitive?
    a. Yes
    (please see my reply in the other topic I posted with regard to the screenreader issue, however, it is quite manageable.
    3. Were all the pogram dialogs clear to you?
    b. No.
    Delete bootable partition?Bootable partition is about to be deleted. Your computer may no longer boot
    correctly.
    As the source partition is not going to be replaced, I therefore think that this message is rather unnecessary, and should be left out or changed accordingly.
    4. Do you think that Migrate OS to SSD needs additional features?
    a. Yes.
    Having an option to restore to a partition rather than to the whole disk would be a good choice.
    Also restoring to a virtual hard disk would be good as well.
    5. Have you found some excess features?
    b. No.
    6. Do you think that Migrate to SSD solution functionality needs to be extended?
    a. Yes.
    restoring to different hardware configurations would be nice. But can be optional if restoring to virtual machines as an example.
     
  4. commodore64

    commodore64 Registered Member

    Joined:
    Oct 7, 2010
    Posts:
    5
    1=Yes :D

    2=Yes :D

    3=No---not happy with the dialogue box that kept popping up--boot about to be deleted--to many pop ups--first warning Ok then final warning. :oops:

    4=No--but still evaluating may have more comments later. o_O

    5=No

    6=No--worked without any glitches. :D

    copied 40 gig XP to 500 gig Sata. Booted succesfully.
    amd m3a32-mvp motherboard. am2 x 4core processor. 4 gig ram. windows 7 64 bit.

    the only other comment at this time concerns all Paragon Products--no mouse right click for pasting when entering product number etc. not everyone knows about control-v.
     
  5. commodore64

    commodore64 Registered Member

    Joined:
    Oct 7, 2010
    Posts:
    5
    oops,made a mistake so gonna break the rules here.

    1) copied raid 0(250gigx2 hd) to 500 gig usb by mistake.
    2) copied OK after 1.37 hours.
    3) windows does not boot from usb.
    4) attached HD to external sata slot.
    5) booted succesfully with no problems.
    6) what can i say--awesome program. a few niggles--nothing serious----no linux support--would like system copy to dedicated partion rather than all the disk. does the program automatically detect how many cores running. next up large to small.

    :D :D
     
  6. starfish_001

    starfish_001 Registered Member

    Joined:
    Jan 31, 2005
    Posts:
    1,041
    1. Was your OS migration successful?
    a. Yes


    2. Was the migration process intuitive?
    a. Yes


    3. Were all the program dialogs clear to you?
    a. Yes but too many - odd first message delete boot partition


    4. Do you think that Migrate OS to SSD needs additional features?
    a. Yes. - as others have said restore to other hardware or boot virtual

    5. Have you found some excess features?
    b. No.

    6. Do you think that Migrate to SSD solution functionality needs to be extended?
    a. Yes. as 4
     
  7. bostech

    bostech Registered Member

    Joined:
    Oct 7, 2010
    Posts:
    1
    1. Was your OS migration successful?
    a. No

    2. Was the migration process intuitive?
    a. Yes up to the point where both the source and destination drives were selected but the Copy button remained grayed out. When the Yes button was selected to confirm Bootable Partition Deletion, was returned to the Ready to copy OS to Target screen. When selecting NO to the Delete Bootable Partition prompt, Cannot Copy OS to Target Disk screen appears with error stating - Unfortunately, due to program error we couldn't copy OS. The following error has occured 0x10091


    3. Were all the program dialogs clear to you?
    a. Error page could supply suggestions other than contact support


    4. Do you think that Migrate OS to SSD needs additional features?
    a. No

    5. Have you found some excess features?
    b. No.

    6. Do you think that Migrate to SSD solution functionality needs to be extended?
    a. Just to work and give more error info

    Migrating Vista from 3.5" 80GB USB drive to 120GB 1.8" ZIF PATA drive in USB enclosure.
     
  8. commodore64

    commodore64 Registered Member

    Joined:
    Oct 7, 2010
    Posts:
    5
    1=Yes
    2=Yes
    3=Yes (see previous remarks)
    4=Yes--how many cores supported--ability to select various partions/with or without drive letters.
    5=No
    6=Yes--see 4 + complex configurations a good idea.

    Migrated XP 40 gig to 20 gig Samsung without any problems--booted OK.

    with regards to final success dialogue--most PC's use delete key to enter bios and hard drives have to be configured in order required before setting up boot sequence--or boot menu could be used if available(all pc's i have owned have this facility)

    :thumb: :thumb:
     
  9. Dhebug

    Dhebug Registered Member

    Joined:
    Oct 9, 2010
    Posts:
    1
    1. Was your OS migration successful? -> Yes

    2. Was the migration process intuitive? -> Yes

    3. Were all the program dialogs clear to you? -> The non clear part was about the reboot after the cloning was done. I did not wait for the reboot on the main disk to check the cloning and then have it tell me that I should not shut down the machine, remove the old drive and reboot on the new drive... I did that immediately at the end of the cloning, and fortunately it worked. I think I was confused by the written documentation. My suggestion is to change the wording at the end of the cloning operation from:

    "Press any key to continue"

    to

    "The disk cloning operation was successful, do not change yet your configuration and press a key to continue to the verification sequence" (or whatever like that).


    4. Do you think that Migrate OS to SSD needs additional features? -> Yes, it should at the very least check that the user does not have a dual boot configuration, and warn him that 1) the Migrate to OSS will migrate only the main operating system (windows). Another nice feature (related to the first point) would be that you can actually create a larger target partition: In my case I have a 74 GB Raptor drive with two partitions (half size) one for Windows, and one for Linux. I migrated all that to a 160GB Intel X25-M drive (no problem at all) but of course it created only a partition of the source size, so I have 90GB non partitioned. Would have been nice to have just one single 160GB windows partition after the migration.

    5. Have you found some excess features? -> No

    6. Do you think that Migrate to SSD solution functionality needs to be extended? -> oops, already answered that one: yes support for more complex partition layout. The existing implementation is nice for simpler setups :)

    All in all, I have to say that the whole operation was a non issue: Simple to use, small installation, clear cloning process. Just make the wording more clear about what goes in which order and when things should be done, and you have a winner :)
     
  10. reyn

    reyn Registered Member

    Joined:
    Feb 16, 2007
    Posts:
    2
    Migrated a 250GB Sata 2 containing OS and programs 36GB to Crucial 128GB C300 SSD.
    Selected existing C: drive and copied it to new SSD took 10 minutes, what can I say - brilliant.

    1. Was your OS migration successful?
    a. Yes

    2. Was the migration process intuitive?
    a. Yes

    3. Were all the pogram dialogs clear to you?
    a. Yes

    4. Do you think that Migrate OS to SSD needs additional features?

    b. No. Please keep it simple

    5. Have you found some excess features?

    b. No.

    6. Do you think that Migrate to SSD solution functionality needs to be extended?

    b. No. It is good already and complete.
     
  11. liston

    liston Registered Member

    Joined:
    Oct 5, 2010
    Posts:
    11
    Dear Sir

    here is my reply thanks.
    1. Was your OS migration successful?
    a. Yes

    2. Was the migration process intuitive?
    a. Yes

    3. Were all the pogram dialogs clear to you?
    a. Yes


    4. Do you think that Migrate OS to SSD needs additional features?
    b. No.

    5. Have you found some excess features?
    b. No.

    6. Do you think that Migrate to SSD solution functionality needs to be extended?
    b. No. It is good already and complete.
     
  12. Frank Hoy

    Frank Hoy Registered Member

    Joined:
    Aug 2, 2005
    Posts:
    1
    Migration on an Asus EeePC 1005HAB, existing Seagate 160GB SATA to new Corsair Nova 32GB SSD (used a CoolMax USB to SATA adapter). Migration took just under 30 minutes.


    1. Was your OS migration successful?
    a. Yes.

    2. Was the migration process intuitive?
    a. Yes.

    3. Were all the program dialogs clear to you?
    a. Yes, except the time remaining dialog box needs work (slow, inaccurate updating and no reference as to what the numbers actually mean).

    4. Do you think that Migrate OS to SSD needs additional features?
    b. Yes. Integration into WinPE boot disks (CD and USB) would be handy.

    5. Have you found some excess features?
    b. No.

    6. Do you think that Migrate to SSD solution functionality needs to be extended?
    b. Yes (see #4).
     
  13. Lighbearer

    Lighbearer Registered Member

    Joined:
    Oct 12, 2010
    Posts:
    1
    1. It worked (not perfect see last comment).
    2. Yes
    3. Yes (If considered necessary you could highlight the fact of not deleting Windows files more (See below).
    4. Yes Needs to be able to copy to a partition without deleting all the data on the disk.
    5. No
    6. Yes Export to a bigger drive or a partition.

    Oddly enough I received your new programme on exactly the day as I was about to replace my OS.

    I keep a back up spare OS for the inevitable Windows slow down and failure so I can easily replace it.

    (Having tested a number of "Return your Windows System to as new condition" registration fix programmes I can safely say they are as useful as putting a picture noddy on the PC and the best you can hope for is they don't make things worse, which is usually a vein hope.)

    I've been using Paragon instead for this for years and recommeding my "removable drive backup system" to others. Having a complete system with all my favourite programmes set up as I want them on a spare drive makes life extremely easy. From a dud system to a new system in a hour is perfect compared with the 2 days+ it used to take to wipe the drive and re-install everything.

    Any way, the new progamme. When I read about it I thought "great" and, I have to admit the interface is simple and quick but would I buy it? No.

    I don't mind the warnings (others have mentioned) as I know you have to cater for the lowest common denominator which is the most amateur user. A few extra clicks for me is nothing if it saves a disaster for someone else.

    The problem I have with it is, although it is more simple to use, it's not as good as my Paragon 9 Suite.

    I have a drive with two partitions: the OS and data files. With Paragon 9, I can copy the new OS partition to the old OS partition without having to move my 500 gigs of data off the drive and back on.

    With the new programme I set up a drive with two partitions and ran a transfer, the result was a new OS partition of equal size (I didn't delete anything for the test) and a wiped free space for formatting and installing data.

    So the comparision is: I either find the "partition copy" function in Paragon 9 and select the source and destination partition myself or I use the new, automated, programme, to find the source and destination partitions for me, and move 500 gigs of data twice.

    Paragon 9 = 1 hour.

    New program = 24 hours.

    Not hard to figure out which I'll be using.

    Using the partition copy system in Paragon 9, I can copy 100gig OS partition on a 1.5 tb to a same 100 gig partition on a 250 gig drive then adjust the partition size on the smaller drive by moving or deleting the second partition. Slightly more complicated but nothing compared with moving all the data twice.

    Notwithstanding this, the ability to select what you want to copy is a great idea and a great function.

    Given the amount of warning you provide on what's going to be wiped, it might be an idea to make it clearer that your system will fail if you start deleting Windows files (I know there's a note but I missed it the first time) e.g. I'd like to delete the windows "Users" file to save space because I don't use their folders (as I encrypt all my files) but I doubt that would be successful given you need at least one "User" account to run Windows!

    To summarise: Sorry, good idea but, for me, just not as functional as the current system if it can't do a partition transfer without wiping the rest of the drive.

    p.s. Not of major significance, but it does not copy perfectly. I used to use Net Objects Fusion and this would not copy as a useable programme and Adobe Photoshop CS2 needs it's registration numbers to be re-input, but, no big deal after the fist move I kept a note and spend 5 minuutes clearing up the minor errors.
     
  14. commodore64

    commodore64 Registered Member

    Joined:
    Oct 7, 2010
    Posts:
    5
    :oops: :oops:

    am2 motherboard amd x 2 processor 3.5gig ram

    Windows XP64

    attempted to copy 250gig hd(94gig used) to 80 gig HD. obviously had to sacrifice various files etc and just settled on the operating system. after initial phase informed that the target hd would have 31% used. commenced to copy.

    all seemed to be working until I started getting hd errors on the drive. fair enough, problems with my drive. after managing to get rid of the errors dialogue box and this is not user friendly--- THE PROGRAM WOULD NOT SHUTDOWN-- I had to wait until the program had run its course. I was using my backup unit but this could be frustrating for any one with only 1 PC.

    attached cdb,stubact,biont and pwlog. fdisk not uploading will try with seperate post. sorry but fdisk will not upload.
     

    Attached Files:

    Last edited: Oct 13, 2010
  15. derekreeves

    derekreeves Registered Member

    Joined:
    Oct 13, 2010
    Posts:
    1
    1. Was your OS migration successful?

    b. No. (If No: please send us the following log files: cdb.log, stubact.log, biontlog.txt, fdisk.txt, pwlog.txt).

    It just failed. Tried it three times to a 120 gig hard drive but complete failure. The system does not recognise the drive after the process.

    2. Was the migration process intuitive?

    b. No.( If No: please describe the stage that caused major problems for you and what improvements you suggest)

    On the surface yes but in first case, it rebooted and I did not know what was happening. Had to launch the prog again. BUT still failure after going through the process again.

    3. Were all the pogram dialogs clear to you?

    b. No.

    4. Do you think that Migrate OS to SSD needs additional features?

    a. Yes. it needs to work first.

    5. Have you found some excess features?

    b. No.

    Cannot understand what I am doing wrong. After going through the reboot and the Paragon screen, it did not boot to the planned drive - but not surprising as the drive was not 'live'.
     
  16. greenpsycho

    greenpsycho Registered Member

    Joined:
    Oct 13, 2010
    Posts:
    1
    1. Was your OS migration successful?
    a. Yes
    I used it to transfer a Win7 install on a 500gb drive to a 120GB SSD (Vertex2). Despite the inaccurate count meter and inaccurate timer countdown that everyone else has mentioned, everything was smooth. Note: I was tempted to cancel several times because the bars and timers weren't moving. Its just a bit of safety insurance for the user.

    2. Was the migration process intuitive?
    a. Yes
    Super easy to use, no confusion over features or what button to push.

    3. Were all the program dialogs clear to you?
    a. Yes
    My only issue arose during the initial disk scan, and one of my usb drives gave an I/O error. For a novice, the disk list by numbers only (Disk 1) is not intuitive, you should also list the drive letters associated with it, and make/model.

    4. Do you think that Migrate OS to SSD needs additional features?
    b. No.
    Its pretty perfect as is: wicked simple, straight forward and quick to use. See #6 below for more.

    5. Have you found some excess features?
    b. No.

    6. Do you think that Migrate to SSD solution functionality needs to be extended?
    b. No. It is good already and complete.
    Personally, I don't really want a $100 piece of software with 100 uses, 95 of which I would never use. I would much rather prefer a simple, easy, cheap unitasking piece of software that does 1 thing, but does it the best. I think a lot of people are going to be using something like this in the future as SSD's become more and more prevalent and the switch from mechanical to SSD's become an everyday norm for IT staff and DIY'ers.
     
  17. PParent

    PParent Registered Member

    Joined:
    Aug 18, 2006
    Posts:
    3
    1. Was your OS migration successful? Yes

    2. Was the migration process intuitive? Yes

    3. Were all the pogram dialogs clear to you? Yes

    4. Do you think that Migrate OS to SSD needs additional features? No, the program do what it say to do.

    5. Have you found some excess features? No

    6. Do you think that Migrate to SSD solution functionality needs to be extended? No
     
  18. Bob Hall

    Bob Hall Registered Member

    Joined:
    Oct 11, 2010
    Posts:
    1
    1. Was your OS migration successful?
    a. Yes it was

    2. Was the migration process intuitive?
    b. No - Frightning message about wiping out MBR. Which is not bad in and of itself, but it was not obvious WHICH drive you were talking about. For example: you warned that my system could be made "Unbootable", this implied to me that you might be changing the MBR on my Source disk. I had to assume this was illogical, so I went ahead and allowed the action, however you need to give more information or state things better. Possibly, you should say that the Boot sector on the TARGET drive will be modified and that action may mess things up. In case your intent was to cover the situation where a single physical drive had more than one partition, you guys should simply detect that.

    3. Were all the pogram dialogs clear to you?
    a. / b. Yes they were clear but sparse, I had to always guess the consequences of my response.

    4. Do you think that Migrate OS to SSD needs additional features?
    b. Not really, it was effective in doing what it set out to do. Migrate an OS to an SSD. That's really valuable. More is not better. (you have other products for that.)

    5. Have you found some excess features?
    b. No, you seem to have gotten it right.

    6. Do you think that Migrate to SSD solution functionality needs to be extended?
    a. Yes. Deal with multi-boot.


    I am Happy to participate, I hope my comments are useful.

    My experience with Migrate to SSD was uneventful, which by any measure is good. The interface and workflow was pretty obvious and everthing important seemed to be auto-detected. Wiping a disk is always makes me nervous, I would like to have seen a little more feedback like Volume Names, clear FROM TO dialogs (with reinforcing graphics) that kind of thing. But all in all it is a great little utility and fits well into the Paragon suite.

    bob

    __________________
     
  19. ContFan

    ContFan Registered Member

    Joined:
    Oct 15, 2010
    Posts:
    1
    1. Was your OS migration successful?
    No, maybe because I have a dual OS booting? I have a Windows Vista Professional + Windows 7 Professional systems but I don't think this should be a problem. When I tried the program did find my two Windows and asked me which one I would migrate. Each time I chose Windows 7 and selected a few folders to migrate (Windows, Program Files and Program Files (x86)) to reduce size of files to copy due smaller size of SSD. Each time it ended up failed and program told me there were no enough space on my SSD to copy files. Strange thing was that even I chose to migrate my Windows 7 which was on a larger partition of my HD, the program ended up formatting my SSD into two partitions one of which was a clone of my smaller partition of HD with my Windows Vista files on it. It actually cloned my Vista partition in stead of migrate my Windows 7. I tried 3 times, twice from within Windows 7 and once from my Window Vista but I got same result.

    2. Was the migration process intuitive?
    No, when the program calculated the size of files to copy it took quite a long time to do, maybe because there were too much data to exclude as they said. But at least I hope to know what the progress is and how much time (approximately) it will take to complete. And when it about to start copying files it asked to format the new drive (SSD). The was no option to leave the partition on SSD unchanged but to choose to format the drive. An option to leave the partition unchanged like in Windows installation would be good IMHO.

    3. Were all the program dialogs clear to you?
    No, as other people posted here.

    4. Do you think that Migrate OS to SSD needs additional features?
    Not sure yet, but first I have to see it works and then to think if any other features need to be added.

    5. Have you found some excess features?
    No

    6. Do you think that Migrate to SSD solution functionality needs to be extended?
    No, at this time.


    P.S. I tried to upload those log files but I failed. Here is the message I got:

    This webpage is not available.

    The webpage at https://www.wilderssecurity.com/newattachment.php might be temporarily down or it may have moved permanently to a new web address.

    More information on this error
    Below is the original error message

    Error 101 (net::ERR_CONNECTION_RESET): Unknown error.

    Please help me how I can upload those files. Thanks.
     
    Last edited: Oct 15, 2010
  20. Ray751

    Ray751 Registered Member

    Joined:
    Oct 16, 2010
    Posts:
    1
    1. Was your OS migration successful?
    a. Yes
    2. Was the migration process intuitive?
    a. Yes
    3. Were all the pogram dialogs clear to you?
    a. Yes

    4. Do you think that Migrate OS to SSD needs additional features?
    a. Yes. Need to do a system clean up first. IE the operating system can be full of old junk, shadow and system restore copies. These do not need to be transfered. I got rid of 15GB. This is important if using small SSD.

    5. Have you found some excess features?
    b. No.

    6. Do you think that Migrate to SSD solution functionality needs to be extended?
    b. No. It is good already and complete.
     
  21. mwarnerii

    mwarnerii Registered Member

    Joined:
    Oct 17, 2010
    Posts:
    2
    1. Was your OS migration successful?
    Yes, I think. I only have USB flash drives instead of SSD. I was able to boot to the BOOT.INI menu in my flash drive, then go on to loading Windows XP SP2 (32-bit) until I get STOP ERROR 7B. I got the same stop error for Widows Vista SP1 (32-bit). This makes perfect sense since there is no boot driver for USB flash drives. I assume that you wanted SSD that connects via SATA or PATA, but I can say this is the first utility I have seen that is able to get BOOT.INI menu to work on a USB flash drive. HP's utility only works for booting DOS.

    2. Was the migration process intuitive?
    Yes. I had no problems understanding the process except dialog boxes

    3. Were all the program dialogs clear to you?
    No.
    A pop-up window titled, "Migrate OS to SSD" appears asking you to approve deletion of a bootable partition will be deleted, but which partition is not stated, and this dialog is redundant, since another dialog will come a few steps later to ask again (that time with source and destination information).
    It should be made clear that the source partition you choose needs to have the boot loader and OS on it.

    4. Do you think that Migrate OS to SSD needs additional features?
    Yes. Improve file selection; allow users to deselect hidden files, and get updated size information as you deselect files (EMC Retrospect does this well).

    5. Have you found some excess features?
    No. Are you joking? I found only one feature that is not absolutely necessary to perform the core function of this utility: file selection. But, file selection is great to cut out extra files to make fit onto a smaller drive.

    6. Do you think that Migrate to SSD solution functionality needs to be extended?
    a. Yes. Let users edit BOOT.INI. Allow copying Windows' boot files from one partition and the OS system files from another partition; this essential if you got multiple versions of Windows on different partitions with Windows' own multi booting capability.
    Paragon should write a Windows boot driver for USB flash drives.

    Defects:
    If I choose a system partition that does not have a drive letter, the file selection is showing my C: partition instead.

    Other information:
    I ran the utility on Windows XP Professional Service Pack 1 (32-bit).
     
    Last edited: Oct 19, 2010
  22. tarquinswift

    tarquinswift Registered Member

    Joined:
    Oct 18, 2010
    Posts:
    1
    1. Was your OS migration successful?
    a. Yes - mostly. although it seemed to loose my outlook ost files so rebuilt my mail inboxes. also indexing in outlook was broken. i manually copied the ost files across and rebuilt the wondows index. Not sure if any other apps are affected so will keep testing.


    2. Was the migration process intuitive?
    Yes - but certainly could be improved. For example the wizard could explain more about the process or use diagrams / pictures to explain what is happening. i think non technical users might be scared they could accidentally delete a partition for example.

    3. Were all the pogram dialogs clear to you?
    No - the "Migrating system" dialogue contained inaccurate time left indication. The time left goes up but the progress bar moves - I think it shoudl state time left and count down to zero.

    4. Do you think that Migrate OS to SSD needs additional features?
    a. Yes.
    >1. The Migrating System dialalogue could indicate the transfer size, the transfer rate, files being transfered, read/write status etc. And the time remaining indicator should be accurate (its not currently).
    >2. In the initial folder selection dialogue a good idea might be to automatically highlight files from libraries or user folders - eg Music, Pictures to be included or not from the migration. You could look at Windows Easy Transfer for what I am thinking. This would help non technical people to find those files rather than digging around in user folders.
    >3 In folder selection it would great to show folder size. i realise this could take some time but it would be very handy to find out where the big folders are.
    >4 Clean up utility - as most SSDs are quite small clearing every unneeded file before migration is critical. Perhaps have a button to launch the generic Windows Cleanup before the folder selection dialogue occurs, or even a couple of quick things like empty recyle bin and clear browser caches.

    5. Have you found some excess features?
    b. No.

    6. Do you think that Migrate to SSD solution functionality needs to be extended?
    a. Yes - select cluster size (including Auto mode for non tech users), move other non OS / app files to 3rd drive - eg start with 1 large old drive with OS and user files, then allow to move OS to SSD but user files such as music and pictures to a 3rd drive. this way all the files can be copied from original drive to new system.

    Otherwise so far its a no fuss, easy to use program. Just needs some cleaning up and improving the user interface, amke it more visually appealing, and some of the english dialogues need some improvement
     
    Last edited: Oct 18, 2010
  23. dfan

    dfan Registered Member

    Joined:
    Oct 18, 2010
    Posts:
    5
    1: Yes
    2: Yes, however a thorough summary of actions to be performed would be nice before executing.
    3: Yes
    4: Yes
    a) You need to support multiple partitions!
    My notebook had a rescue partition that I could not copy.
    Not a disaster, but there should be options for such things. Maybe hidden in a menu or under "advanced mode" so that noobs are not confused.
    5: No, I didn't notice any wasted options.
    6: Yes, as stated before, please support complex disks.

    The experience was great. I would recommend this software!!!:thumb:
     
  24. Lacko50

    Lacko50 Registered Member

    Joined:
    Oct 15, 2010
    Posts:
    4
    1. Was your OS migration successful?
    b. No. (The SW hanged. I posted the log files)

    2. Was the migration process intuitive?
    b. No. (No hint of what must be transferred, what could stay on old disk)

    3. Were all the program dialogs clear to you?
    a. Yes.

    4. Do you think that Migrate OS to SSD needs additional features?
    a. Yes. (Easier file/directory selection, back and forth navigation buttons)

    5. Have you found some excess features?
    b. No.

    6. Do you think that Migrate to SSD solution functionality needs to be extended?
    a. Yes. (Besides cloning the boot disk, applications could be moved, too, with automatic update of the registry and ini files, reflecting the changes)
     
  25. Maeghas

    Maeghas Registered Member

    Joined:
    Oct 6, 2010
    Posts:
    6
    Location:
    Orlando, FL
    1. Was your OS migration successful?
    No. See attached files; "fdisk.txt" was too large to send and there was no "cdb.log" file.
    This attempt ran for 28 hours with no sign that anything was happening. I cancelled it because a migration of this type should not take a day to complete when Windows 7 installs in less than 2 hours.

    2. Was the migration process intuitive?
    Yes, to the point of the actual migration process.

    3. Were all the program dialogs clear to you?
    No. In the "Migrating [disk name]" step, the estimate time for completion is way off. In my case, it estimated completion in two minutes when in fact it ran over 28 hours before I chose to abort it.

    4. Do you think that Migrate OS to SSD needs additional features?
    Yes.
    -- When "Calculating copy size", I'd like to be able to cancel out of it.
    -- "Format target disk" should not be necessary if the target disk is already empty and formatted. This feature should be an option. (In my case, I kept getting a formatting error).
    -- "Migrating" step needs much more dialog to let the user know what is happening. (I kept needing to look at my computer's lights to confirm that the program wasn't stalled.)

    5. Have you found some excess features?
    No.

    6. Do you think that Migrate to SSD solution functionality needs to be extended?
    Yes. Migration for virtual drives other than Virtual PC (namely, for VMWorkstation).

    Some additional notes:
    1. Calculating copy size step takes a long time to complete. In my case, it took in excess of three hours to analyze a 500GB drive that was only half full. Perhaps this step needs optimization to speed up the process.
    2. Part of the problem may be that the formatting process reported errors in its attempts to format the target drive. I reformatted the target drive again (NTFS) with the idea that the boot table might have been corrupted. I will submit a followup for my second migration attempt.
     

    Attached Files:

Thread Status:
Not open for further replies.