By adding "skip-innodb" (minus the quotes) anywhere in the section
"[mysqld]" should work.

For more info look in the "MySQL Technical Reference" section "2.1.2.2
Preparing the Windows MySQL Environment".


Roger



-----Original Message-----
From: gx-inc [mailto:[EMAIL PROTECTED]]
Sent: Monday, November 26, 2001 9:24 PM
To: Delbono Nicola; [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: F/U @ Re: * reiteration re: (re)starting MySQL



I'd appreciate "note-by-note" directions. The "my.cnf" file wasn't to be
found on my system (odd), though I did find the "my.ini" file (in the main
Windows directory).



Some other directions stated that I could edit the my.cnf *or* my.ini
file(s) for essentially the same results, though I wouldn't presume to know
which is which and/or what specific editing particulars are involved.



Appended are the contents of the my.ini file (omitting the user name and
password for display purposes herein):



=========================================



#This File was made using the WinMySQLadmin 1.1 Tool
#9/25/01 11:43:37 AM
#Uncomment or Add only the keys that you know how works.
#Read the MySQL Manual for instructions

[mysqld]
basedir=C:/MYSQL
#bind-address=208.187.244.66
datadir=C:/MYSQL/data
#language=C:/MYSQL/share/your language directory
#slow query log#=
#tmpdir#=
#port=3306
#set-variable=key_buffer=16M

[WinMySQLadmin]
Server=C:/MYSQL/bin/mysqld-opt.exe
user=
password=



=========================================




At this juncture I'd just as soon *not* use InnoDB, but just go with
"plain" MySQL. I do *not* want to use WinMySQLadmin but instead want to use
the DOS prompt for command-line access and database processing (if I'm
being clear?).



Appended below are the specifics that appeared at the DOS prompt when I
tried to access MySQL:



=========================================



C:\WINDOWS>cd c:\mysql\bin\

C:\mysql\bin>mysqld --standalone
Cannot initialize InnoDB as 'innodb_data_file_path' is not set.
If you do not want to use transactional InnoDB tables, add a line
skip-innodb
to the [mysqld] section of init parameters in your my.cnf
or my.ini. If you want to use InnoDB tables, add for example,
innodb_data_file_path = /mysql/data/ibdata1:20M
But to get good performance you should adjust for your hardware
the InnoDB startup options listed in section 7.6 at
http://www.mysql.com/doc/

C:\mysql\bin>



=========================================



Being completely new to MySQL specifically (and relational databases in
general) means I really have no idea just *where* to edit/insert what &
when; even most of the manual is Greek to me (at this preliminary point).



This is very frustrating, especially since I believe MySQL to be an
excellent database to learn by -- if indeed I can get the bugger actually
going for me to learn by!



Thanx to all for all assistance.



:-)  mhw  (-:



+++++++++++++++++++++++++++++++++++++++++++++



At 08:35 AM 11/26/01, you wrote:
>try opening my.cnf  file
>
>and see if you find s.thing with InnoDB
>
>
>----- Original Message -----
>From: "gx-inc" <[EMAIL PROTECTED]>
>To: <[EMAIL PROTECTED]>
>Sent: Monday, November 26, 2001 5:31 PM
>Subject: * reiteration re: (re)starting MySQL
>
>
> >
> > * reiteration re: (re)starting MySQL
> >
> >
> >
> > Just recently started seriously studying the "infernal trio" of Apache,
> > MySQL & PHP and got off to a decent start, but for reasons unknown can
no
> > longer get MySQL to start up from the DOS prompt.
> >
> >
> >
> > I keep getting the following error message when I enter the
> > "C:\mysql\bin>mysqld --standalone" command:
> >
> >
> >
> > Can't initialize InnoDB as 'innodb_data_file_path' is not set
> >
> >
> >
> > This command had previously worked without problems -- e.g., accessing
> > MySQL to commence database construction; now it doesn't. One day it
>worked,
> > and the next it didn't despite not havng "done" anything in the interim
to
> > the best of my knowledge: weird.
> >
> >
> >
> > Rather than using WinMySQLadmin I'd prefer to start up MySQL from the
DOS
> > prompt primarily for the sake of learning proper command-line procedures
>in
> > anticipation of our pending migration to Linux as our primary OS.
> >
> >
> >
> > Would appreciate whatever guidance (debugging?) that the more
experienced
> > users may have to offer. Thanks in advance.
> >
> >
> >
> > :-)  mhw  (-:
> >
> >
> > ---------------------------------------------------------------------
> > Please check "http://www.mysql.com/Manual_chapter/manual_toc.html";
before
> > posting. To request this thread, e-mail [EMAIL PROTECTED]
> >
> > To unsubscribe, send a message to the address shown in the
> > List-Unsubscribe header of this message. If you cannot see it,
> > e-mail [EMAIL PROTECTED] instead.
> >
> >


---------------------------------------------------------------------
Please check "http://www.mysql.com/Manual_chapter/manual_toc.html"; before
posting. To request this thread, e-mail [EMAIL PROTECTED]

To unsubscribe, send a message to the address shown in the
List-Unsubscribe header of this message. If you cannot see it,
e-mail [EMAIL PROTECTED] instead.



---------------------------------------------------------------------
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/           (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Reply via email to