I’ve purchased a Windows 8 upgrade for my Windows 7 machine. While upgrading I ran into a problem.

The upgrade came to 100%, and then said “Your computer will reboot in a few moments”. After a few minutes it came up with a general error “Windows 8 Setup could not complete” and then it closed. My computer didn’t reboot, and Windows 7 just kept on running.

After removing some applications like my virus scanner (NOD32) and some other applications i tried again. After about an hour I got exactly the same error.

Then I found the following error:
ConX::Setup::Media::CWorkerProc::SetupThreadProc: An error occurred while servicing the boot files from [C:\$WINDOWS.~BT\Windows\BOOT]; status = [0x80070015][gle=0x00000015]

After a lot of searching I’ve found the following solution:
Add a drive letter to the 100MB system partition which resides at the beginning of your harddisk. I assigned the letter S.

After I did this, the setup continued where it previously stopped with an error, and Windows 8 was installed like it should.

When Windows 8 was completely installed, I removed the drive letter from the partition. After this, Windows 8 was running flawlessly.

tweetdeck-02-676x535I’ve recently upgraded my Windows 7 installation to Windows 8. Unfortunately Tweetdeck wouldn’t connect to my account anymore and showed the not so useful error “Unable to connect”.

After a lot of searching I’ve found a simple and unlogical solution:

  1. Start Internet Explorer
  2. Navigate to https://api.tweetdeck.com
  3. Navigate to https://twitter.com
  4. Close Internet Explorer
  5. Start Tweetdeck
  6. Log in to your account

Now Tweetdeck works like it should, and profile images should appear again.

For Moodle development I occasionally clone a production environment to a temporary test location. This way I know for certain that my custom code works in the environment it should work in.

The downside of this approach is that notifications are still mailed to users. So after a bit of searching in the Moodle docs I have found no solution. So I went digging in the code, and found a configuration option that prevents the Moodle installation to send emails completely. All you have to do is put the following setting in your config.php.
$CFG->noemailever = true;

Tip: A lot of settings are also described in the config-dist.php file in the root folder of your Moodle installation.

If you own a shared hosting server, you probably want to keep the /var/log/messages file as clean as possible, to make searching for errors as easy as possible.

One of our web servers had a messages file filled with Drupal errors and warnings. It al seemed to come from one site.
After a bit of searching, it seemed the syslog module in Drupal was enabled. There are two solutions to this annoyance. You can disable the syslog module in the database used by this site, or make syslog log all Drupal errors to a separate file.

Database solution

The most easy method to check and disable the syslog module is disabling this module in the database as follows:

Checking if the module is enabled:
SELECT * FROM system WHERE name='syslog';
If the status column is 0, the module is disabled, in case of a 1 the module is enabled.

To disable the module:
UPDATE system SET status='0' WHERE name='syslog';

And to check if the module is really disabled:
SELECT * FROM system WHERE name='syslog';
The status column should now say 0.

Separate log solution

Create the file /etc/rsyslog.d/90-drupal.conf with the following content:

# drupal logging
if $programname == 'drupal' and $syslogseverity <= '6' then /var/log/drupal.log if $programname == 'drupal' and $syslogseverity <= '6' then ~

That's it. There should be no more Drupal messages in the /var/log/messages file.