Windows 2003 Server Crash - Now on 2008 - MySQL IBData1 File Shows Default Tables Only

Windows 2003 Server Crash - Now on 2008 - MySQL IBData1 File Shows Default
Tables Only

I've looked all through the site and haven't found an answer to this
question, so I'll ask. I apologize if it is somewhere in here.
I had a MySQL 5.5.15 server running on an old Windows 2003 server. That
server finally failed due to hard drive and motherboard issues. I now have
a Windows 2008 server. I made sure to put MySQL 5.5.15 on it, so I had
matching software for the first step.
I moved over all the data files I had. So this includes the my.ini, the
ibdata1 and two log files, a group of mysql-bin files with dates from last
December. I've seen some pages talk about subdirectories with files, but I
don't have any of those. Maybe that is a Linux thing?
I then launch mysqld --console and it starts up fine. No errors.
I then launch mysql separately, and ask to see the databases. All it
reports are the three default ones - information_schema, mysql, and
performance_schema. When I ask about users, it has the default ones.
It seems really odd to me that it would somehow corrupt so that it lost my
personally created databases but kept the default ones. My ibdata1 file is
641mb. It seems likely that somehow I'm just not connecting properly to
this.
I did try launching it with various values for innodb_force_recovery -
with no change. It still starts smoothly, and it still shows just that
data in it.
Any thoughts?
Lisa