The reason for this posting was this comment (in Bulgarian) by Mladen, where he shares his bad time and also some of his desperation with Windows XP after installing the Bulgarian Phonetic keyboard layout, provided by Injinera.

The problem: Windows starts BSOD-ding after installation of one of the keyboard layouts, downloaded by Injinera’s site. The BSOD happens either immediately after logging on, or if you successfully logon, but try to switch the keyboard layout afterwards.

I had almost the same experience after I installed the same set of files (from the same place), which Mladen installed too. My notebook started to throw BSOD’s in about 50% of the system logons: very, very nasty problem, without any sign of hope there. And because I already trust Injinera as a very correct and stable source, I was sure that the problem should be somewhere else and not in the installed files. The provided files contain anyway only some convertion tables, and nothing more…

During my hard time few months ago, I noticed that if I’m not connected to the corporate network, the BSOD does not appear, or appears much rarely than if I was connected to the corpnet. Initially I suspected that somehow the system does not like the newly installed stuff and while trying to restore itself via the automated System Restore, if ends-up with this bad BSOD. Actually, I managed to have a working machine exactly by logging on without being connected to the corpnet (the notebook was undocked), and after logging on I was docking the notebook back.

Luckuly, during the time being this problem started to appear rarely and rarely (healing, magic – call it as you wish :)), and I almost forgot about it (although I was reminded from time to time by a BSOD in similar conditions at least once a month). However, Mladen’s comment raised this issue back.

I decided to try looking for solution, or at least a clue. After some search through Google, I’m almost confident that I have found the initial source of this problem. I will leave Mladen to experiment and report here :), because I am somehow not ready to risk my current stable situation. Fighting with few angry help-desk guys is not the best way 2005 to begin, isn’t it ;)?

Mladen, take a look here (originally I found this quote from this link, which in general has nothing to do with our problem). However, read carefully:

Based on the info you give … it would seem geoShell is choking on one of your startup items, or vise versa. I reckon it’s probably internat.exe that’s causing the trouble. This does nothing more than display that blue icon (with white text) in the system tray, providing you with a mouse interface to change your keyboard layout. internat.exe uses a “non- standard” method for displaying that icon in the systray (the method is actually undocumented), and it won’t display properly or perhaps even at all under geoShell. Luckily you can still switch layouts via the hotkey (left alt-shift I think.) Try disabling internat.exe and see what happens.

As it seems, this is similar behavior to what we do experience. Maybe it could help?

After some more digging out, I have found this (unfortunately, the only source I have about this is that “it was somewhere in MSDN”, and this is not a good way something to be referred to):

Internat.exe – You can end this process from Task Manager.

* Internat.exe runs at startup; it loads the different input locales
specified by the user. The locales to be loaded are taken from the following
registry key:

HKEY_USERS.DEFAULTKeyboard LayoutPreload Internat.exe loads the “EN”
icon into the system tray, allowing the user to easily switch between
locales. This icon disappears when the process is stopped, but the locales
can still be changed through Control Panel.

I am leaving the experiment to you. Remove internat.exe (rename it in safe or rescue mode) and see what happens. Please, if you find a way to kill the problem – report it here as it could be of some else’s use. I will add more to this article, if there is some progress on that issue.

Hmm, long time without posts, ah? For some people, who’re regular readers here it may seem just the same situation as my latest post-crisis this August. Well – that’s not the case, I hope. This long posting gap was just because of “no time”, “no willingness” and similar lame excuses.

Now I have finally found something, which I would like to write about. Few days ago, while reading my latest CodeProject e-mail magazine, my attention was captured by a small tool, published there: Expresso regular-expression’s tool.

In my work (as a programmer), and also in my hobby (the programming) it happens sometimes that I need regexp searches and replaces. Each time when I have to do this stuff I am getting very upset, because:

* Although there are some regular expression’s “standards”, there is no real standard, which defines what regular expression syntax is and what it should contain. There are some “de-facto” standards (PCRE for example), but usually the big companies (such Microsoft) prefer to make their own.

* Sometimes the libraries, which I have(had) to use in the applications, are compatible with these “standards”, but some times they are not.

* I never had the chance (and the willingness too) to become an regexp expert, so each time I have to write a regexp I just start with a long pray, and eventually a slottering, if there are some goats around.

This is because until now I never had the chance to find a really good regexp debugger/tester, at which I just put my regular expression, and some sample text, and I see the results immediately. Few months ago I found something, which I thought will be the tool, but somehow I did not like it and I just had it for reference (when I go home, I will update this article to contain a link to that tool too, if I find a link there).

Well, today I am astonished! Expresso seems to be The One. It contains a bunch of features, which include:

* Detailed tree of your regular expression

* Regular expression builder (for the regexp lamers like me). This builder shows you the (most of the) possible regular expression contents and you may choose what your regexp to contain. No more searching in the net for some specific regexp junc, yeah!

* Detailed tree of what your regexp matches (you provide a sample text, on which the regexp match is performed) – a great regexp debugging feature!

* Nice regexp library – you can choose a bunch of library regexps, and you can learn from there. Of course, if you need to expand the library with your favorite regexps – it’s up to you.

* Code generator: the tool contains a nice code generator, which can give you directly the code, which will match your regular expression. Here is the place non-.NET guys to scream, but yes – the tool itself if .NET based and (I believe – temporarily) it generates only .NET code (Managed C++, C# and Visual Basic). You’ll say – that’s very easy job to do (generating the .NET code), but the most important thing is that it’s already there and you do not have to do it each time yourself, if you want to use your regexp in .NET code.

* Because the tool is .NET based, it has this great feature for .NET programmers – the ability to test how much time it will take on you machine to match your sample against current regular expression. You give the number of the iterations – it gives the result. Nice, if you want to know what’s the performance of your regexp (for example, 100K matches of my simple regexp [ ]*(test)[ ]*(.*) were made for about 3.01 seconds).

* …And more. I was browsing through the functionalities for not so long time, and I’m absolutely sure there are plenty of nice things I still haven’t seen.

The current disadvantages of the tool are:

* It’s available only on Windows. I suppose it’s .NET nature makes this mandatory for now. But maybe the author can take a look over Mono 🙂 ? The Portability is a great thing, isn’t it?

* It’s open, but copyrighted source code. But this is the author’s decision, and we have to respect it. I think it’s fair enough, having in mind that the tool is free to use. Yes, it has free of charge one time registration, but I think we also should respect the author’s right to know who’s using his tool. If you use it – you can take 10 seconds to send a mail to the author with your name and email – I think you will not regret it, because Expresso will save you much more time, if you’re writing regexps frequently.

What is my advice? Take the risk 🙂 – download, install, test and enjoy! I’m really interested if someone could test this tool on Linux with Mono. I’m not sure if Mono is ready enough to run this tool, but why not give it a shot? It would be great if it works there too.

Once again – many thanks, Jim Hollenhorst of Ultrapico. Keep the good work – I am sure many people appreciate it!
– – –
Dec 22nd Update: CodeProject recently published “The 30 Minute Regex Tutorial” – a .NET regular expressions tutorial. A great text to read, if you’re new to these expressions, and to Expresso as well.