NineChime forum

Make sure the oekaki folder itself is writable, because the board cannot write the config files into the folder (it's not a database issue).

Since you have to create the /oekaki folder via FTP, you'll probably have to set permissions to 775.  The default is usually 755.

The checkboxes in the FTP program?  Which program are you using?

Ah, someone on the Wacintaki forum is having a similar problem.  It might be because your account is set up as a subdomain.  If that's the case, then you can't CHMOD the root folder itself.

Open up Notepad, and save two blank files named "config.php" and "dbconn.php".  Upload those files to the oekaki folder and chmod them to 664.  Those are the only two files written to the root of the oekaki folder, and if the server cannot create those files, it should still be able to write to them if they already exist.

Oops.  After you upload those files, you have to run the installer again (ignore any errors about duplicate database entries).  The files are just  blank "placeholders" for the config files.  Do this by viewing "install.php".  With a config file in place, the board will always ask you to run the updater, but in this case, you'll need to run the updater again to actually write the proper info to those blank files.

OK, upload this file to your oekaki folder and run it.  This will tell you the permissions of all the files that need to be writable on your server.  You'll just have to mess with the CHMOD numbers (whatever your server wants) until they work.  At this point, I may need a link to your oekaki to get an idea of how your account is set up.

I find it odd that the base folder on your server is not writable, which is why the config files cannot be written.  This does make some sense if you have a subdomain account ("account.server.com") instead of a normal account ("www.server.com/account").  If you have a control panel for your account, you may have to look around to see if there's a web-based FTP manager that will allow you to change the permissions of the base folder (I seriously doubt it, but we might as well look).

If problems persist, you may have to contact your system administrator, or install your oekaki in a subfolder, and upload an index.html file to the base folder that points to the oekaki.

Also, just in case the files you uploaded manually are an issue, try deleting them.  If the base folder is writable, the installer will be able to create those files.

OK, according to the "perm.php" script you uploaded, the write permissions for all the folders is just fine.  However, I noticed that the language file isn't working quite right.  I tried to access "/language" directly and was promptly shown a 404, while "/language/english.php" works just fine.  If your server has directory listings turned off at the script level (not just the public level), that will be a problem.

Seeing how the main files are now writable, try setting all the folders to a CHMOD of 757 (including the base folder, language and smilies) and then run the installer again.  See what that does.

That's normally a server issue, so I'm not sure.

Lemme see what I can do regarding a custom security file (.htaccess file).  There's a way to override the server's default settings, but it doesn't always work.  I'll get back to you.

OK, try this.  Upload it into each folder of the oekaki, including the base folder:  .htaccess file

Now, I don't know if it will allow access to the files, but it *should* override directory indexing.  If it does, then file access may be a side effect.  However, whether this works or not depends how the security model is set up on the server.  If you just try to access, say, the "/shipainter" folder, and you can't get a directory listing, then ".htaccess" files are disabled on the server, in which case you'll have no choice but to ask the system administrator for help (since CHMODing didn't do anything).  Maybe there's a "magic" CHMOD number you need to use.

Wax runs just fine on a Windows server.  I use Windows myself to test the board.  It's very easy to get most scripts working on a Windows machine, but sadly, many programmers don't bother.

The .htaccess files only work with the Apache web server, though.

Folders that actually exists are returning different 404 errors than folders that don't exist, so this is definately a security lockout issue.  As far as I know, Microsoft IIS doesn't allow security overrides like .htaccess files, so you'll probably have to ask your administrator.  Honestly, I don't know too much about security on IIS.