Server.exe Error

Hi everyone. Whenever I try to run the server.exe file in any private server build (As in krazy, zbornox, MMOEmpire original-v3) I get this message:
What is causing this and how do I fix it?

List of Steps Taken To Fix:

Why are you running in compatibility mode for 97?

I mean I've tried every mode from Win 95 to Win 7

C:\Users\Jennifer Garrison\Desktop\NEW SERVER ATTEMPT\_Server>mysql\bin\mysqld --defaults-file=mysql\bin\my.cnf --standalone --console
130604 16:30:36 [Note] Plugin 'FEDERATED' is disabled.
130604 16:30:36 InnoDB: The InnoDB memory heap is disabled
130604 16:30:36 InnoDB: Mutexes and rw_locks use Windows interlocked functions
130604 16:30:36 InnoDB: Compressed tables use zlib 1.2.3
130604 16:30:36 InnoDB: Initializing buffer pool, size = 128.0M
130604 16:30:36 InnoDB: Completed initialization of buffer pool
130604 16:30:36 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 48941
130604 16:30:36 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 1595675
130604 16:30:37 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
130604 16:30:38 InnoDB: Waiting for the background threads to start
130604 16:30:39 InnoDB: 1.1.5 started; log sequence number 1595675
130604 16:30:42 [Note] Event Scheduler: Loaded 0 events
130604 16:30:42 [Note] mysql\bin\mysqld: ready for connections.
Version: '5.5.9-log' socket: '' port: 3306 MySQL Community Server (GPL)

help me this is in mysql server section... dont know what to do :[.

---------- Post added at 04:37 PM ---------- Previous post was at 04:27 PM ----------

I've just tried to open the port 3306 following these steps:
1. Open Control Panel from the Start menu.
2. Select Windows Firewall.
3. Select Advanced settings in the left column of the Windows Firewall window.
4. Select Inbound Rules in the left column of the Windows Firewall with Advanced Security window.
5. Select New Rule in the right column.
6. Select Port in the New Inbound Rule Wizard and then click Next.
7. Select which protocol this rule will apply to (TCP or UDP), select Specific local ports, type a port number (80), port numbers (80,81), or a range of port numbers (5000-5010) and then click Next.
8. Select Allow the connection and then click Next.
9. Select when this rule applies (check all of them for the port to always stay open) and then click Next.
10. Give this rule a name and then click Finish to add the new rule.



which didnt work it gives me a new error code of this in mysql server slot.:

C:\Users\Jennifer Garrison\Desktop\NEW SERVER ATTEMPT\_Server>pause
Press any key to continue . . .
C:\Users\Jennifer Garrison\Desktop\NEW SERVER ATTEMPT\_Server>mysql\bin\mysqld --defaults-file=mysql\bin\my.cnf --standalone --console
130604 16:41:14 [Note] Plugin 'FEDERATED' is disabled.
130604 16:41:14 InnoDB: The InnoDB memory heap is disabled
130604 16:41:14 InnoDB: Mutexes and rw_locks use Windows interlocked functions
130604 16:41:14 InnoDB: Compressed tables use zlib 1.2.3
130604 16:41:14 InnoDB: Initializing buffer pool, size = 128.0M
130604 16:41:14 InnoDB: Completed initialization of buffer pool
130604 16:41:14 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
130604 16:41:14 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
130604 16:41:14 InnoDB: Waiting for the background threads to start
130604 16:41:15 InnoDB: 1.1.5 started; log sequence number 1595675
130604 16:41:15 [Note] Recovering after a crash using mysql-bin
130604 16:41:15 [Note] Starting crash recovery...
130604 16:41:15 [Note] Crash recovery finished.
130604 16:41:16 [Note] Event Scheduler: Loaded 0 events
130604 16:41:16 [Note] mysql\bin\mysqld: ready for connections.
Version: '5.5.9-log' socket: '' port: 3306 MySQL Community Server (GPL)

its an odd thing it is.