Archive

Posts Tagged ‘Solution’

Windows 2003 – Login Screen is Black Except for Logo – Part 2

April 14th, 2010

Here are the default registry settings for the instructions mention in the MS KB http://support.microsoft.com/kb/906510.

Windows Registry Editor Version 5.00
[HKEY_USERS\.DEFAULT\Control Panel\Colors]
“ActiveBorder”=”212 208 200″
“ActiveTitle”=”10 36 106″
“AppWorkSpace”=”128 128 128″
“Background”=”102 111 116″
“ButtonAlternateFace”=”181 181 181″
“ButtonDkShadow”=”64 64 64″
“ButtonFace”=”212 208 200″
“ButtonHilight”=”255 255 255″
“ButtonLight”=”212 208 200″
“ButtonShadow”=”128 128 128″
“ButtonText”=”0 0 0″
“GradientActiveTitle”=”166 202 240″
“GradientInactiveTitle”=”192 192 192″
“GrayText”=”128 128 128″
“Hilight”=”10 36 106″
“HilightText”=”255 255 255″
“HotTrackingColor”=”0 0 128″
“InactiveBorder”=”212 208 200″
“InactiveTitle”=”128 128 128″
“InactiveTitleText”=”212 208 200″
“InfoText”=”0 0 0″
“InfoWindow”=”255 255 225″
“Menu”=”212 208 200″
“MenuText”=”0 0 0″
“Scrollbar”=”212 208 200″
“TitleText”=”255 255 255″
“Window”=”255 255 255″
“WindowFrame”=”0 0 0″
“WindowText”=”0 0 0″

Andrew Hosting , , , , ,

map.root :controller => does not work.

January 12th, 2010

I’m working on one of my first apps and I discover that the map.root :controller => does not work.  I verified the controller was spelled correctly, but it kept taking me to the Ruby On Rails intro page.

Solution: delete the index.html out of /public/

Andrew Development , , , ,

The application has failed to start because sqlite.dll was not found.

November 4th, 2009

Ruby on Rails on Windows Vista :: Getting error “The application has failed to start because sqlite.dll was not found.”

Solution:

Copy sqllite3.dll to a directory that is in your %path% variable.

Andrew Ruby on Rails , , , ,

WordPress Permissions and Problems – now a solution!

May 6th, 2009

So you’ve installed WordPress and it’s just not working out.   Maybe you’re getting one of these error messages:

“You need to make this file writable before you can save your changes. See the Codex for more information.”

“The uploaded file could not be moved to…”

“Sorry, I can’t write to the directory. You’ll have to either change the permissions on your WordPress directory or create your wp-config.php manually.”

What to do?  Why not toss the entire kitchen sink at it?  After all, that’s what 90% of solutions I found online suggested.

Just chmod 777 the directory and it will work!

Why not just set your password to the name of your blog?

I’m not a person who uses Linux every day of the week, but I do appreciate it and see it’s use in meeting some business goals.  So, I got a bit  frustrated.  I’d fix one problem, discover another, fix that, discover another.  So, I stopped and thought about the situation – I even phoned a friend (thanks Ron!).

There were two facts I had to deal with before moving forward:

1. Not everyone has these problem.

2. The solution is related to permissions, but the way I was fixing them wasn’t the right way.

Then it hit me.  After I uncompressed the download and moved it into the www directory, I did not change the owner of the folder and all child folders/files.

A bit of background, I’m running WordPress on a Ubuntu LAMP Server.  So, I realize the configuration may differ, but if you’re having the same problems, regardless of distro, the solution is the same.

First, figure out what user and group the folder needs.  For my server, it was www-data for both.  So, I used the following command:

chown -R www-data:www-data wordpress

or

chown -R www-data:www-data www

(depending on where you moved the wordpress directory)

Also, you’ll need to set permissions:

chmod -R -v 755 wordpress

or

chmod -R -v 755 www

(again, depending on where you moved the directory)

After completing this step, then go to http://webserver/wordpress (or whatever URL you’re using) and you won’t have the errors listed above.



Andrew Troubleshooting , , , , , ,