( Windows server first start

Info Catalog ( Windows select server ( Windows installation ( Windows start command line
 2.3.10 Starting the Server for the First Time
 On Windows 95, 98, or Me, MySQL clients always connect to the server
 using TCP/IP.  (This allows any machine on your network to connect to
 your MySQL server.)  Because of this, you must make sure that TCP/IP
 support is installed on your machine before starting MySQL.  You can
 find TCP/IP on your Windows CD-ROM.
 Note that if you are using an old Windows 95 release (for example,
 OSR2), it's likely that you have an old Winsock package; MySQL requires
 Winsock 2! You can get the newest Winsock from
 `'.  Windows 98 has the new Winsock 2 library,
 so it is unnecessary to update the library.
 On NT-based systems such as Windows NT, 2000, XP, or 2003, clients have
 two options. They can use TCP/IP, or they can use a named pipe if the
 server supports named pipe connections.
 In MySQL versions 4.1 and higher, Windows servers also support
 shared-memory connections if started with the `--shared-memory' option.
 Clients can connect through shared memory by using the
 `--protocol=memory' option.
 For information about which server binary to run, see  Windows
 select server.
 This section gives a general overview of starting the MySQL server.  The
 following sections provide more specific information for starting the
 MySQL server from the command line or as a Windows service.
 The examples in these sections assume that MySQL is installed under the
 default location of `C:\mysql'. Adjust the pathnames shown in the
 examples if you have MySQL installed in a different location.
 Testing is best done from a command prompt in a console window (a "DOS
 window"). This way you can have the server display status messages in
 the window where they are easy to see.  If something is wrong with your
 configuration, these messages make it easier for you to identify and
 fix any problems.
 To start the server, enter this command:
      C:\> C:\mysql\bin\mysqld --console
 For servers that include `InnoDB' support, you should see the following
 messages as the server starts:
      InnoDB: The first specified datafile c:\ibdata\ibdata1 did not exist:
      InnoDB: a new database to be created!
      InnoDB: Setting file c:\ibdata\ibdata1 size to 209715200
      InnoDB: Database physically writes the file full: wait...
      InnoDB: Log file c:\iblogs\ib_logfile0 did not exist: new to be created
      InnoDB: Setting log file c:\iblogs\ib_logfile0 size to 31457280
      InnoDB: Log file c:\iblogs\ib_logfile1 did not exist: new to be created
      InnoDB: Setting log file c:\iblogs\ib_logfile1 size to 31457280
      InnoDB: Log file c:\iblogs\ib_logfile2 did not exist: new to be created
      InnoDB: Setting log file c:\iblogs\ib_logfile2 size to 31457280
      InnoDB: Doublewrite buffer not found: creating new
      InnoDB: Doublewrite buffer created
      InnoDB: creating foreign key constraint system tables
      InnoDB: foreign key constraint system tables created
      011024 10:58:25  InnoDB: Started
 When the server finishes its startup sequence, you should see something
 like this, which indicates that the server is ready to service client
      mysqld: ready for connections
      Version: '4.0.14-log'  socket: ''  port: 3306
 The server will continue to write to the console any further diagnostic
 output it produces.  You can open a new console window in which to run
 client programs.
 If you omit the `--console' option, the server writes diagnostic output
 to the error log in the data directory (`C:\mysql\data' by default).
 The error log is the file with the `.err' extension.
 * The accounts that are listed in the MySQL grant tables
 initially have no passwords.  After starting the server, you should set
 up passwords for them using the instructions in 
Info Catalog ( Windows select server ( Windows installation ( Windows start command line
automatically generated byinfo2html