In case anybody else ever has to do this ---- for WINDOWS only
1 - Stop the service for the database
2 - Copy all OS files associated with the database (datafiles, control files, pfile, spfile, redo, archive - whatever)
3 - Install all the OS files in the exact same directory structure that you copied them from.
4 - Create a new service (same name as the old service, just on a new box)
5 - Start the service
If you do this the correctly the new database will start every time. It doesn't even know that it's been cloned and moved. There are no magic places that Oracle (in Windows) stores information about where it is once the service is stopped. When the service is stopped all the information that Oracle needs to restart has to be written to disk.
To further the clone-ability of Windows Oracle databases I always create every file associated with a particular database until one directory branch. I realize that that goes against OFA but once you've SAMEd your RAID 10 array there's little point in creating the appearance of OFA when the actuality is that, as far as the operating system is concerned, it's just one big disk.
I see no reason to make being an Oracle DBA harder than it already is.