I was experiencing very nasty problem for the past months: when I right click a file on the notebook, it took hell lot of a time to display the context menu. Sometimes it took even more than 30 seconds or so. The most nasty thing (apart from this problem) was the fact that I can’t do anything, while I’m in “waiting state” for the context menu – if you click somewhere else, the menu will hide immediately after shown and you will have to right-click and wait again.

Today I made a huge step to the resolution of this problem. Everything started with this forum posting, about which I red in Windows XP Expert Zone Community WebLog. The resolution, which was suggested there, was simple:

> try this…
>
> Go into any folder’s menu
> Click Tools->Folder options
> Go to the “View” tab
> …And uncheck “Automaticaly search for network folders and printers”
> Click OK…

I tried these steps and Ohhh, Miracle – the right click reaction seems much faster now. It will take some time until I confirm my observations, but so far it seems much, much faster.

I’ve still got some delays (for example – in the PDF files), but these are acceptable (and unavoidable) for now.

Another place to look for probable resolution of this problem is the following registry key:

HKEY_CLASSES_ROOT\Drive\shellex\ContextMenuHandlers

This is the registry place, where most of the Context menu handlers are located. If you start removing the handlers one by one, you will most probably see which one of these guys are causing the long delay. And you may switch off the context menu handler (if you can afford).

It’s not bad idea at all to backup your registry before proceeding. If you do so, you will be able to restore the things, if you mess up something! Also, System Restore Point is not a bad idea before proceeding.

I will continue digging in this direction and I will most probably share my findings, if there are any…

Днес успях да преодолея много досаден проблем, който имам от година. Проблемът накратко: при натискане на десния бутон в/у папка или файл, на компютъра му отнемаше от 10 до 30 секунди да ми покаже контекстното меню. Много досадно и дразнещо!

Проблемът се оправи, когато приложих следните инструкции:

> От менюто на Explorer в коя да е папка:
> Избери Tools->Folder options
> Отиди на “View”
> Махни отбелязаното на “Automaticaly search for network folders and printers”
> Натисни ОК…

Това направи нещата доста по-бързи. Все още се наблюдава забавяне при някои файлове, но това засега е поносимо (и неизбежно)…

Recently I was obsessed with the idea to force my Qtec 9090 to use its Bluetooth capabilities for ActiveSync-ing with my notebook. Both gadjets have Bluetooth and both were capable of using it (well, at least I thought so) – making Bluetooth working should not be a big deal.

I made some searches and hit the following resources on the net:

1. Synchronizing HP iPAQ h2210
with Bluetooth (Belkin Dongle) using MS ActiveSync 3.7, which explains in general how to setup Bluetooth from both sides in order to make the synchronization. During my search I noticed these good articles as well:
1. Bluetooth ActiveSync Guide for Windows XP Service Pack 2
2. ActiveSync Troubleshooting Guide : Synchronization Errors
3. Bluetooth AutoSync for Microsoft Smartphone 2003; Bluetooth ActiveSync Guide for i-mate Smartphone2 [These links are just for my reference for the future, when I will need similar procedure for Smartphone]
4. ActiveSync with Bluetooth and Windows XP SP2 (another good explanation with screenshots)

2. Going crazy with ActiveSync via bluetooth at XDA-Developers forum, which explained me how to patch my bluetooth with its latest software release. Actually, I had to download and install Pocket Bluetooth Tools. The latest version (1.1.0.0) works for me so far…

3. Activesync Port Availability Via Bluetooth, How to reassign port numbers ?

4. Auto-start for ActiveSync via Bluetooth?, whicih teached me how to start my Bluetooth ActiveSync with a push of a button

After this reading I decided to step on. The first problem I had was “no serial connection” between the two devices. Reinstalling my Bluetooth notebook drivers fixed that one.

After the successful pairing it took me some time to fix the big mess (because of the previous problem and many changed settings), but as a result now I have working Bluetooth synchronization – just in the way I want it to work. Now I do not need the craddle, but just the power cable, because with this Bluetooth working continuously the device became even more power-hungry…

Current plugin version: 1.0rc2.DA1

Few months ago I found a great plugin SecureImage, which helped me to get out of all nasty spam comments in my blog. However, during the plugin’s usage I found some very nasty problems:

1. Probable and dangerous SQL injection in some parts of the code (original author was already notified)
2. Sometimes the PNG image was not displaying correctly, and also PNG image stream contained the whole blog’s main page after the PNG image. Obviously, this was causing wrong images for some contents of the main page (most of the times the contents were OK and the PNG image was displayable).
3. Pingbacks and trackbacks were disabled. Mike Baptiste’s comments told me how to re-enable this back, and I integrated it in this custom version of the plugin.

As direct result of all the problems above, I decided to create new version of this great plugin. The new version is based at the original plugin, plus the three fixes above. Please feel free to download and use it. Installation instructions are simple – just copy the plugin and enable it – it should be quite sufficient.

Please have in mind that I also changed a bit the form with the secure image – I like the image to be just after the edit box, where the user should enter it. I find it more compact this way.

If you find a problem, or have an idea, or just want to say something, please do not hesitate to comment below!

_Update_: It seems to me that the pingbacks/trackbacks still do not work. Any help with that will be much appreciated!

I was a happy user of the SecureImage plugin for some months, while at some point few of my friends started to complain that they cannot see my “secure image”, which caused them to loose ability to comment, unless they are registered users.

Initially I did not believe my eyes, but after some research I found a very nasty generic problem in the plugin, which could cause some of these “header already sent” errors, about which the users complain in the plugin’s main page. Unfortunately, these warnings were just the tip of the iceberg – the main and most nastiest problem is when my readers cannot see the secure image: both the browsers (IE and FF) were failing to display it.

It was not easy to find the problem, but I finally nailed it down. The problem is in the plugin’s PNG generation code. When the plugin is asked to generate the PNG image, it does all correctly, but after that it passes the control to the standard WordPress processing, which causes your whole main page’s HTML code to be concatenated after the PNG image’s stream. This caused two problems:

1. Depending on your current site’s contents, your readers may or may not see the PNG image, which will definitely cause them not being able to comment at all (sick!)

2. Your traffic will be increased, because instead of serving 30K (the PNG image average size), it will serve 30K+<the contents of your index.html at the time of the serving>. In my case each image went to about 100K because of this.

The solution of this problem is easy: you just have to replace the “print” command of the image generation:

print $wpdb->get_var(“SELECT img_data FROM $wpdb->secureimage
WHERE img_name = ‘$image'”);

with “die” instead:

die ($wpdb->get_var(“SELECT img_data FROM $wpdb->secureimage
WHERE img_name = ‘$image'”));

This will cause your plugin to stop at the very rigth point just after the image is sent to the client.

Recently I installed SecureImage WordPress plugin. Main reason: Comment spam went so high I was absolutely mad and angry, and I decided to give these bastards a lesson.

However, on the same day after installing it I found some problems in the plugin. The plugin itself was working, but the problems were serious. I wrote the following email to the author (Thom Skrtich):

>Hi Thom,
>
> I recently installed 1.0rc2 version of SecureImage plugin.
>
> I have found one minor and one major problem in the code. I am attaching the a file with the “old” version and my modifications. Here is the description of what I’ve found:
>
> __I) SQL Injection Attacks__
> Unfortunately, the plugin contains few places, where SQL injection attacks are possible. Please diff my code and original code – you will find these places. I have added mysql_real_escape_string on these places.
>
> __II) MD5 hash visible__
> This is much minor problem than the one above, because the worst thing, which may happen is to bypass with some logic the protection code. I have modified the code, and now it stores two MD5 hashes: one for the image (completely different than the code word) and the original code word one. Please take a look at the changes – they are minor I suppose – easy to understand. However, please do not hesitate to ask me for information, if you need more explanations.
>
> Please have in mind that I have not yet published this information. I will schedule my post to appear in a week, so the users would have enough time to upgrade. The flaws are serious and they must be resolved, because they might be crucial for the user’s databases, if someone decides to use them.
>
> Best regards,
> \-\-\-
> Doncho

Thom reacted quite quick and he assured me that he will change the plugin. But today there is still no intention of this, so I decided to post this, because the users must be informed for the danger, and also because I have made some additional modifications, which can be outlined as a new, modified version of the SecureImage plugin.