I just installed AMPPS 2.0 on an old Windows XP SP3 machine, and I can't get MySQL to start. It looks like Ampps is trying to pass an invalid flag to the server process. The error log appears as follows:
Code
130519 1:47:24 [Note] Plugin 'FEDERATED' is disabled.
130519 1:47:24 InnoDB: The InnoDB memory heap is disabled
130519 1:47:24 InnoDB: Mutexes and rw_locks use Windows interlocked functions
130519 1:47:24 InnoDB: Compressed tables use zlib 1.2.3
130519 1:47:24 InnoDB: Initializing buffer pool, size = 128.0M
130519 1:47:24 InnoDB: Completed initialization of buffer pool
130519 1:47:24 InnoDB: highest supported file format is Barracuda.
130519 1:47:24 InnoDB: Waiting for the background threads to start
130519 1:47:25 InnoDB: 1.1.8 started; log sequence number 1595669
130519 1:47:25 [ERROR] mysql\bin\mysqld.exe: unknown option '--skip-locking'
130519 1:47:25 [ERROR] Aborting
130519 1:47:25 InnoDB: Starting shutdown...
130519 1:47:26 InnoDB: Shutdown completed; log sequence number 1595669
130519 1:47:26 [Note] mysql\bin\mysqld.exe: Shutdown complete
I've never experienced this issue on newer versions of Windows (Server 2008 or Win7). Is there any particular reason that Ampps would be attempting to run MySQL differently on XP?
Is there any way I can manually set the flags Ampps passes to MySQL so that I can avoid this issue?
|