Does your build work OK if you boot up without running ghost? (ie do the SATA drivers mount OK with the bios set to AHCI or SATA mode?). If it does, then we can focus on your ghost process as this is unrelated to sysprep.
Having sysprepped the machine, you now have an image on hard disk that you wish to capture for installation on other machines.
In order to be able to capture this image, the boot system you use from which you run ghost, has to be able to "see" the hard disk.
You don't mention whether you are booting from a DOS or a WinPE environment, but the bottom line is that if you boot your DOS or WinPE system to a command prompt, can you see the files on the laptop hard disk? Switching the bios to IDE mode **may** work, but if you are using a DOS boot system, you may still have problems with disk sizes greater than 132Gb due to the 32 bit LBA addressing limit.
When working with modern SATA hardware, I would strongly recommend using WinPE as the boot environment, as WinPE natively supports many SATA hard disk chipsets, and is easily updated with new drivers for chipsets that are not yet natively supported.
Once you can see the files on the laptop hard disk, getting ghost to work should be quite straightforward. If you contine to have problems with Ghost, WinPE has its own imaging tool called Imagex which creates WIM files. I have found this to be more reliable than Ghost with modern hardware, and its free too. Since it excludes swap files and other irrelevant content automatically, it also generates smaller images than Ghost (in my experience).