Move Win2k3 to new hardware: STOP 0x0000007B (How can I get PERC drivers installed?)

I have an ancient celeron-based Windows 2003 SBS server on an old Dell machine. It has a very basic IDE non-RAID setup. The server is so old, it takes about 30 minutes to boot up and log in.

A new Dell (ugh!) server was purchased with the intent of doing a ghost from one server to the other. The new server has a PERC6/i RAID controller in in w/ SATA drives.

Copying the data works fine (using linux 'dd'), but the server refuses to boot with 'STOP 0x0000007B (0xF789EA98, 0xC0000034, 0x00000000 0x00000000)'

In my experience, this has been due to Windows not having the drivers for the RAID controller.

To fix this, I would boot the old server, download the drivers for the new server, extract them, right-click on the .inf file and hit 'Install'. Then shutdown and start the copy process.

It's totally not working for me with this new Dell server. I am certain I have the correct drivers--I used the driver from the CD that came with the server, and I also went online and downloaded the correct driver. But the new server refuses to boot.

Does anyone with more experience with this have any pointers?

If you have the option, installing the drivers before ghosting is the preferred method for doing this. Windows SHOULD pick up the new drivers during the boot process on new hardware. This is a large part of how Physical-to-Virtual migrations work driver-wise.