I would not do a database copy in that manner.
I would use the "mysqldump" function to dump the database that you wish to copy to a file, then copy the file to the other machine, and then read in the database to the new machine using the "mysql" function.
When I use mysqldump to dump just one database (as opposed to more than one), I open the file that is created, and add a "USE mydatabase" as the first line, where mydatabase is substituted with the database name, just to make sure I don't accidentally attempt to add the database tables to the wrong database on the target machine.
On the target machine, you may have to first create the database if it isn't already created. Then you can just read in your file using the command line mysql command:
mysql -u myuser -p mydatabase < myfile.sql
where myuser, mydatabase and myfile.sql are substituted for the user name, the database name, and the file name that you created with the mysqldump.
The above works on Linux, I am not sure if you need to change the command line I show above a bit for Windows, as the "< myfile.sql" part is the Linux way of telling mysql to read commands in from the myfile.sql.