Many users have experienced the 'hanging winxp' on the splash screen due to Norton Ghost's failure to address a vital issue of DISK ID.
After doing quite a bit of searching on the web I found that this is a common problem, with many and varied attempted fixes.
I believe the root of my problem came from a combination of XP's drive letter assignment behavior and Ghost's failure to deal with it. If the original XP system ever sees the partition of the new drive (and assigns a drive letter to it) before Ghost clones the old system to the new drive, then the new drive will have a registry entry with its own Partition ID listing it as being something other than Drive C. When you install the new drive in the PC and reboot, the new drive is discovered by the BIOS and starts booting XP as Drive C. Once XP is fully loaded, it thinks the current drive should be some other drive letter, and you lose the boot drive, causing the hang at the Windows Logon screen.
Personally I solved the problem by using the widely recommended Acronis TrueImage. TrueImage deals first with the drive letter assignment and then gets out of Windows proper to perform the disk copy. Then when the system reboots into XP, even if you leave the new drive connected as a hard drive it is OK. Even though the old system will now see the cloned partition and likely assign it a drive letter other than C, the image on the new drive has already been copied without that assignment. When you swap the drives the new drive will boot properly into Windows.
If you really want to use Ghost's Disk Copy function, be sure that the old system does not have a drive letter assigned to the new drive's partition. You may need to go into Control Panel.. Computer Management.. Disk Management to make sure that there is no drive letter assigned to the new drive and even delete the new drive's partition if one exists.
No guarantees on the specifics here, but hopefully that will be helpful to someone. In my experience, Acronis got it right, Symantec didn't.