Peer to Peer Cloning

[Migration User]

I have prepared a base machine for our organization and would like to clone it to an identical system (vostro 420) but keep running into difficulties.  I am using Ghost 2.0 and have attempted several methods with no success.  I am running the client on the target machine but have been unsuccessful in pulling an image up to a network folder. The create image task will not execute because the image does not exist. I am quite sure I followed the steps for creating the image source and destination  in the configuration tab, but perhaps user error.
Peer to Peer: I created boot disk and included NDIS2 drivers, decragmented the master boot record, established master on the source disk, slave on the destination disk, established a connection, begin the cloning, and get hung on NTFS MFT table. 
So, Which method would be preferred: Pulling the image over the network using the console-client or peer to peer using boot disks, and has anyone had similar problems

[Migration User]

There is no proffered method - everyone has their own prefs. P2P is useful when you dont need to keep an image and cloning once. Create image from console should be as simple as creating "image create task", creating new image resource and selecting machine(s) to run task on. After this Console will take care of the rest, including NIC drivers for DOS.

If Ghost hangs on NTFS MFT table then run chkdsk first on that volume and make sure it picks no errors. Another problem could be absolutely fragmented volume - it will take very long time for ghost to validate MFT file (main index file) if it's very fragmented.

[Migration User]

Okay, I have defragmented, run CHKDSK, and still hanging up at MFT. I ran a test on another machine and was successful, though that is not the target machine it does mean that I understand the process. Through research I have discovered that a controller conflict could possibly cause this problem and tried including -noide & -nousb switches but it is still hanging up.  The model computer does have a JMB36x raid controller, could that cause a problem? Is it supported? The program sticks whether I am imaging to the network or cloning peer to peer. Any thoughts?