Since when is an update to an application an important update for the Operating System????
On a side note, my desktop PC no longer runs Linux (OpenSuSE). I’ve had it with it. There’s always something that doesn’t work. Or that keeps crashing. Or that suddenly stops working until a reboot. Sound support sucks. After every kernel update I had to do a manual install of the NVidia drivers to get X running. Always waiting for the X64 versions, since the Linux community still thinks we all run 32-bit computers (same on Windows, but at least that let’s me run 32-bit programs without problems).
I bought a new videocard (a Sapphire HD7970 to be exact), bought an SSD (OCZ Vertex4 128GB) and switched to Windows 7. Everything works. Period. And I can now use Adobe software, so I bought Adobe Photoshop Lightroom to finally being able to organize my pictures (lastest count: over 26000) the way I like it (F-spot and Picasa are nice, but not more than that).
Main reason for the videocard was gaming of course. Racing in the first place, FPS as a close second. Bought Deus Ex Human Revolution (FPS-ish) today, more to follow.
I just installed the x64 version of Adobe Flash “Square”. And in Minefield it works. Not perfect (I sometimes see some graphics artifacts), but it works. And that’s nice. After long years of complaining about the x64-support of Adobe (read: the lack thereof) they have finally seen the light. Thumbs up.
Now let’s find all my Firefox-plugins for Minefield.
Update: all-in-one gestures works after you edit the RDF to make the maximum allowed version 4.*.* 🙂
I just installed (well, unzipped) Minefield (non-branded Firefox) 4.0 beta for Windows x64, and must say: it rocks. Too early to give a definitive verdict, but sofar it looks better and really is x64. Which is nice, considering the memory usage of a typical Firefox session 😉
NoScripts works like a charm with the x64 version, I’ll have to test the rest of the plugins.
Update: Oh my, how could I forget? Adobe still lives in the previous century: there is no x64 Flashplayer…..
When using an x64 OS, like Windows 7 x64, you undoubtedly found that most software is still 32-bits. If your computer has a lot of memory, you will find that you run out of memory quickly, since 32-bits software only uses the first 4GBytes. For some reason x64 binaries are still hard to find.
Today I stumbled upon this weblog. It’s a great source for x64 software and info, so check it out.
My new boss called me today, saying he has a job for me. Start: a.s.a.p., but only when I have my own hardware. So he “ordered” me to buy a laptop. One could get worse instructions from upperhand. So I bought a HP Pavilion dv7-3030ed. It’s not the Elitebook I got from my current employer, but the Pavilion is about 1000 euros cheaper.
It’s a great machine, with Win7 x64 on it, very nice wide 17″ LED-screen, 4 GByte of memory and a 640500GByte harddisk. Notefully, the keyboard is better than on the Elitebook, the mousepad is not. Definitely not. So I’ll buy a lasermouse to go with the laptop.
Today I updated my Outlook Unsafe Attachment Unlocker utility. For some reason I noticed the select-all checkmark did not toggle. It only did a Select-All, but not an Unselect-All. Now it does. And the context-menu now points to the correct address of this weblog. Get it here.
When I get my hands on an Office 2007, I’ll see whether the utility can be made Office 2007 compatible.
I still get a lot of search hits from people looking for a way to change the extensions that cannot be viewed in Outlook, because Microsoft decided in all her wisdom to mark a lot of extensions as “unsafe”. In Outlook Express there is a nice dialog to change this behaviour, in Outlook there is not. You can do it by editing the registry by hand, but a lot of people are afraid to do so.
For that reason, I created ouau.exe, or “Outlook Unsafe Attachments Unblocker”. It detects your Office version (which you can override) and lists the extension so you can block/unblock them. There’s a handy “select all” radiobutton that will save you some clicking.
Here is a screenshot.
Click here to download the program. It’s in WinRAR format, so you need to extract it first.
OUAU should now work for all Office versions, and you can select the Office version (if for some reason you have partial Office installations) and it will reread and write the appropriate registry-entry.
Changes
To do
I tried ouau here at work, and we’re using Office 2002/XP. It finds the correct Office version, I’m able to make changes to the blocked extensions, which I can verify by restarting the program: it finds the new settings. But the new registry-setting resort no effect: right-click and send-to-mail-recipient of a unblocked extension (e.g. .EXE) still results in Outlook saying that the attachments are potentially unsafe. What’s going on here? Something to do with (group)policies?
Update: I think I already know: Exchange administrators can add/remove Level 1 and/or Level 2 extensions within the Exchange-server settings. This can not be overruled by the Outlookclient. So, I guess I’ll have to find another way to test other Office versions.